R15 Remote Usage - Double Digits (Echo)??

[tfd2424]

Got a new R15. IR remote sucks (unresponsive etc...), upgraded to RF using "Edmunds" RF activation hack from one of the earlier posts. Now using RC32RF with a Dish network RF antenna in receiver RF port. RF works great!

Here's the problem DirecTV of course never heard anything about...

When using either the provided IR remote or new "aftermarket" remote (RC32RF) on the radio spectrum, I have problems entering program channel numbers reliably. This applies to menu navigation in the program guide and othe menues as well.

For example: I try to enter channel number 501, often the receiver will receive command 5501. When navigating down in the guide often the receiver will scroll down 2 programs at a time with one click. - Funny thing is it won't do it all the time. Sometimes it works ok, then all of a sudden it doesn't.

It's obviously not a bad remote or due to the RF hack, as I tried it with the supplied IR and new RF alike. Perhaps a screwy R15?

I even had the thought to cover the IR sensor on the receiver so that it does not receive IR and RF at the same time (as the remote may be sendig both spectrums at the same time to the receiver) that could result in a kind of echo effect, however, this did not resolve the problem.

Can the RF signal channel of the RC32RF remote be changed?

Any help in the matter would be great!

:nono2:

[subeluvr]

Since "RF" is not officially activated on the R15 DTV will not give you any help. It's probably not a good idea that we tell them that it works... if we want RF to continue to work.

I had the same problem and learned how to avoid it. The DTV remotes are very sensitive to button pushes. Way more sensitive than any remote I've ever used. I concentrated on using a very light and quick touch on the buttons and it works fine.

Remember, if you've moved the slider switch there will be one dead button push before the remote will issue commands.

[tfd2424]

Couple of things...

1. I checked the manual that came with the RC32RF last night to see if I can assign a different RF channel to the remote (of course you can't)... But I did find the section "Activating RF on your receiver" - This section intails the EXACT informationon how to activate RF on the R15 as "Edmund" described in this forum. Therefore I have a hard time believing that Direct does not "know"about this (although they fail to officially acknowledge it)... and even though the remotes are not specifically produced for the R15.

2. I also use a very light touch on the RC32RF which seems to help a little. Then I wondered if this the same problem occurs with my RF "approved" H2O receiver with the same remote under the RF spectrum, and guess what - It doesn't. No problems with double digits, echo or anything of the sort... I conclude therefore that the R15 issues must stem from the firmware registering and executing the RF button command (that is probably sent several times in rapid succession when a button is pressed on the remote?) and displaying it on screen.

Example, when holding button "5" for 3 seconds the output on screen is "5555" (not "5"). - I gather that the H20 receiver's firmaware is optimized to ignore RF commands received in to rapid succession(???).

Does anybody know of a way to tell the RC32RF remote to only send a command to the receiver once (while in RF mode) when a button is pressed (and held)? E.g., disable RF command repeat? - I would bet that there is a feature code for the remote for that somewhere.

Good to know that it is not just me having this problem. Perhaps we can find a fix for this one make things easier.

:confused:


Thanks!
Since "RF" is not officially activated on the R15 DTV will not give you any help. It's probably not a good idea that we tell them that it works... if we want RF to continue to work.

I had the same problem and learned how to avoid it. The DTV remotes are very sensitive to button pushes. Way more sensitive than any remote I've ever used. I concentrated on using a very light and quick touch on the buttons and it works fine.

Remember, if you've moved the slider switch there will be one dead button push before the remote will issue commands.

[subeluvr]

Which R15 do you have... 100, 300, or 500?

Some people have reported "double tap" problems with RF and the R15 100.

[tfd2424]

Correct - it's the 100. Other versions of the R15 do not have this problem?




Which R15 do you have... 100, 300, or 500?

Some people have reported "double tap" problems with RF and the R15 100.

[subeluvr]

Correct - it's the 100. Other versions of the R15 do not have this problem?

I have two 300s that work fine and I recall others posting that 500s work as well.

The one poster that sticks in my mind was complaining about exactly the problem you mention with an R15 100 and I don't recall reading that he solved the problem.

You can easily search this forum for "rf remote" and see the threads.

Also, I think (might be wrong) that the RC32RF remote is oem or optional on one of the DTV HD receivers and the instructions included with the remote are intended for those receivers not the R15.

Since "RF" is not officially activated and supported on R15s there is a chance that the RF feature works better on one model R15 versus another R15. There are three models of R15, three hardware platforms, three version of code, and three versions of firmware.

When DTV officially supports RF on the R15 the three models (100, 300, 500) all may work correctly... or all three may have problems ;)

[tfd2424]

...just locally picked up a R15 500 from a retailer will confirm to see if problem still persists on the 500. Will post results.

:)

I have two 300s that work fine and I recall others posting that 500s work as well.

The one poster that sticks in my mind was complaining about exactly the problem you mention.

You can easily search this forum for "rf remote" and see the threads.

Also, I think (might be wrong) that the RC32RF remote is oem or optional on one of the DTV HD receivers and the instructions included with the remote are intended for those receivers not the R15.

Since "RF" is not officially activated and supported on R15s there is a chance that the RF feature works better on one model R15 versus another R15. There are three models of R15, three hardware platforms, three version of code, and three versions of firmware.

When DTV officially supports RF on the R15 the three models (100, 300, 500) all may work correctly... or all three may have problems ;)

[Bobman]

I have 2 500's and have had no RF remote problems like above.

[TigersFanJJ]

I haven't had that problem with my 500.

[DSOUND]

I have the same problem with both my R15-700 and my HR20. The problem is called "switch bounce". When you depress a switch it actually vibrates and "makes and breaks" the contacts. This results in numbers being duplicated. You wanted 501 but get 5001 or 5011 or 55011. Software can delay the next input that the unit sees so that it minimizes this effect. You can stop trying to fix it and hope that the software engineers will get to this simple problem in the next release. I have found that instead of quickly pushing the numbers, I hold the buttons down for a little longer and it works better. Not great, but better.

[GollyGee]

I also have this problem and it is very frustrating.

I'm surprised they shipped a device that does this.

[tfd2424]

So yesterday I picked-up a R15 500 from a local retailer during my lunch break... hooked it up in the evening and activated the RC32RF remote control.

Right from the start the remote now functions without "double tapping" symptoms. Nothing of the sort going on.

The receiver did cause a tense moment when it updated to the newest firmware from DTV, but problems did not re-appear, indicating that this seems to be a hardware based problem with the R15 100?

Solution to the problem (for me) send the R15 100 back to DTV and see if you can still find a retailer that sells the 500's. - DTV will not ship you anything but the 100's if you call in for replacement (tried that).

Thanks everyone for the great input!

:D

I have the same problem with both my R15-700 and my HR20. The problem is called "switch bounce". When you depress a switch it actually vibrates and "makes and breaks" the contacts. This results in numbers being duplicated. You wanted 501 but get 5001 or 5011 or 55011. Software can delay the next input that the unit sees so that it minimizes this effect. You can stop trying to fix it and hope that the software engineers will get to this simple problem in the next release. I have found that instead of quickly pushing the numbers, I hold the buttons down for a little longer and it works better. Not great, but better.

[Xram]

I have the same problems with my r15's and hr20's.