Strange problem with DSTV remote not working when TV is ON

Quantum Theory said:
The problem is definitely not a poorly designed IR receiver... It is the IR frequencies that are being used that differs. Also, If the TV interferes with your DStv decoder, why are you blaming the decoder?
Click to expand...

Well, everything works except the DSTV decoder. All other remotes / and IR receivers on those devices work fine.

I understand that the IR emissions of the TV are not ideal, and are causing the problem - but only with the PVR :)

How can the IR frequencies be different? You mean different wavelengths? Normally remotes are all 940nm. Or do you mean the modulation frequencies? They should also be the same, otherwise the PVR remote would not work with other devices (universal remote).

Also, the DSTV remote (once programmed) can change settings on the TV just after it is turned on, while the PVR doesn't respond. So once again this points to the IR receiver on the PVR being poorly designed.

This is a problem on many set top boxes, world wide.
 
greg_SA said:
Well, everything works except the DSTV decoder. All other remotes / and IR receivers on those devices work fine.

I understand that the IR emissions of the TV are not ideal, and are causing the problem - but only with the PVR :)

How can the IR frequencies be different? You mean different wavelengths? Normally remotes are all 940nm. Or do you mean the modulation frequencies? They should also be the same, otherwise the PVR remote would not work with other devices (universal remote).

Also, the DSTV remote (once programmed) can change settings on the TV just after it is turned on, while the PVR doesn't respond. So once again this points to the IR receiver on the PVR being poorly designed.

This is a problem on many set top boxes, world wide.
Click to expand...

Protocol bit rate... Higher bit rate is more prone to interference. I remember 8 years ago, when I was still doing high-end AV installs, it was extremely difficult to program the DStv IR remote commands on a Phillips Pronto. Still, the problem is not the DStv decoder.
 
Quantum Theory said:
Protocol bit rate... Higher bit rate is more prone to interference. I remember 8 years ago, when I was still doing high-end AV installs, it was extremely difficult to program the DStv IR remote commands on a Phillips Pronto. Still, the problem is not the DStv decoder.
Click to expand...

Well, you are actually agreeing with me, in saying that the higher bit rate of the DSTV IR is more prone to interference.

I am not sure why they use a higher bitrates than other IR systems. Is it only the DSTV decoders / HD PVR or do some other equipment manufacturers also use higher bitrates?
 
greg_SA said:
Well, you are actually agreeing with me, in saying that the higher bit rate of the DSTV IR is more prone to interference.

I am not sure why they use a higher bitrates than other IR systems. Is it only the DSTV decoders / HD PVR or do some other equipment manufacturers also use higher bitrates?
Click to expand...

My guess is that the electronics companies have saturated the lower end. You can not have different devices using the same codes. For this reason, they had no choice... I'm not agreeing with you. I know that the higher bit rate is more prone to interference, but the product that causes the interference is the problem here.
 
Quantum Theory said:
My guess is that the electronics companies have saturated the lower end. You can not have different devices using the same codes. For this reason, they had no choice... I'm not agreeing with you. I know that the higher bit rate is more prone to interference, but the product that causes the interference is the problem here.
Click to expand...

Well, I think that the receiver should be able to tolerate the noise/interference, just like all the other IR receivers do on my other equipment.

Anyway - neither of us know the exact design of the IR receiver, so we're all just guessing.
 
greg_SA said:
Well, I think that the receiver should be able to tolerate the noise/interference, just like all the other IR receivers do on my other equipment.

Anyway - neither of us know the exact design of the IR receiver, so we're all just guessing.
Click to expand...

Yes, I do not know the exact design. I do not follow the logic... Blaming the decoder for something that is caused by the screen. The decoder's IR is within spec, I'm sure. A screen emitting frequencies in the invisible range is not.
 
Quantum Theory said:
Yes, I do not know the exact design. I do not follow the logic... Blaming the decoder for something that is caused by the screen. The decoder's IR is within spec, I'm sure. A screen emitting frequencies in the invisible range is not.
Click to expand...

The logic is that all the IR devices work fine, except the DSTV decoder.

I believe the decoders IR spec isn't great, and that is why some people also complain that they have problems with the remote when the decoder is in sunlight (as the sun also emits IR).

Anyway, luckily my setup works fine - the interference only lasts for about 10 to 20 seconds.
 
Quantum Theory said:
The problem is definitely not a poorly designed IR receiver... It is the IR frequencies that are being used that differs. Also, If the TV interferes with your DStv decoder, why are you blaming the decoder?
Click to expand...

So as a matter of interest then, using a different TV would perhaps give different results? I'm not buying a new one anytime soon, but it's interesting that some models may either give out more IR, or have a frequency that is scrambling the signal from the remote more than other models.
 
greg_SA said:
The IR emissions don't have to go directly from the TV to the decoder - they bounce off the wall, ceiling, etc. So it probably is still causing the "jamming". My TV is wall mounted, and my PVR is in a cabinet underneath, with only the front of the PVR visible from the front.

You can always test if the TV is the problem, by putting the remote right up against the HD PVR receiver and covering the area with your hand (to block any background IR). Then the remote should work.
Click to expand...

Yep, it does work after about 10 seconds when I switch TV on and then cover the IR receiver with my hand while aiming remote at it, unfortunately I have to get on my knees..
 
chrisc4290 said:
I have had this in customers installations. Solution is always to recess the HD-PVR in a cabinet or deep bookshelves so it cannot receive a signal from another source. Also check the batteries in the remote. Just because it is new it does not mean the batteries were not lying on a shelf for 3 years
Click to expand...

I think my batteries are good,
I pushed the PVR further back into the cabinet and it definitely works a bit better, simple but effective
 
Quantum Theory said:
An installer I know mounted a piece of conduit over the IR receiver position on the decoder. With this McGuyver, signals could only get in from angles straight ahead and he says this worked for him and he's done it a few times. I've never tested this myself...
Click to expand...

I want to try this McGuyver,
My father has kind of settled for leave the TV on all day, and it doesn't take as long for the PVR to respond now with moving the decoder, but if I want it up and running in under ten minutes I still have to get down on my knees and cup my hand over the receiver for several seconds until it starts responding, so I'm going to make a plan with the pipe story most likely..
 
I experienced this issue recently. Nothing changed in my physical setup, which has been the same for years.

Problems started when I began to power the TV/decoder (Samsung LCD 32 inch, HD PVR 2P) via inverter during load shedding. For maximum efficiency I increased the energy saving to max and dropped the brightness to 0.

After a while I noticed that when the TV is powered on from standby (note: DSTV decoder is never switched off or put on standby), the DSTV remote stopped responding or took a few minutes to start responding. Using the remote very close to the decoder only sometimes worked but always with noticeable lag.

The following are some workarounds/permanent fixes to the issue for anyone that may come across this thread in future :

1. Change the picture display from Standard to Dynamic (which is brighter and adapts to the surrounding light)
2, Alternate to 1 : Power the TV on, switch from HDMI to another Source (wait about 10 seconds), go back to HDMI mode. If after doing this once and it still does not work, then try it a 2nd time and almost definitely works.
3. If 1 & 2 also don't work - try turning off energy saving completely. So far 1 above, always works for me, 2 usually works 99% of the time.

I don't believe this to be an infrared interference issue, as my TV and decoder are physically separated by the cabinet design. My TV is connected via HDMI cable to the decoder, it would be interesting to know if people who experience this problem are only those who connect by HDMI (as opposed to RCA etc).

My view is that the energy saving is causing some interference to the decoder via the cable between the two. I tested for infrared in a completely dark room and I didn't detect anything with my camera.
 
Last edited:
I need some advice please same problem as OP only difference is the TV in question is nowhere near the decoders?? This only happens when you switch the TV on and it jams both decoders and for about 20 minutes or so on the Explora 2? Setup 2 Explora's with Xtraview 4 TV's connected with TV links ONLY the TV in the bedroom causes this - any thoughts please (TV in question is a LCD about 10 years old)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X