I had a service call yesterday after DirecTV swapped an HR21 for an HR24. This is the first HR24 i have worked with. All commands worked but the channel +/- and the navigation arrow commands would hit the box and the box would see them as continuous. Example.. I hit channel up and the HR24 channels up forever until i stop it by hitting another button like menu or guide. Same behavior with the other buttons. I learned the new remote and replaced all the commands. Everything worked fine. I just thought it was odd that they have the same hand held remote/layout. Same buttons/commands. But for some reason they changed the behavior of a handful of commands.

DTV hasnt changed their codes. You should be able to take the OEM remote from that HR21 and it work fine on the HR24. It probably was because of the original codes not being learned correctly and the new box may process them slightly different. But there is no way DTV made a change to their code set.

Ha, this has been happening for at least 18 months. I had to deal with this in LA before I left, which next week will be 1 year.

The HR21 was using codes from the Crestron database. They were all programmed to pulse once for 0.1s. Maybe those codes were not learned 'correctly' but they worked on the HR21 but not on the HR24. This was the only change made. Learning the new remote manually worked. If you can confirm that you have swapped HR21's for HR24's and had the programming work on the new box then the issue is with their new box.

The service call was supposed to be 5 minutes to replace a ripped off emitter or hot glue one on because the DirecTV didnt know what to do with it.... Or it would have been a whole day rewiring a system that DirecTV took apart.

Instead it turned into a weird service call where some of the commands would be received and cause the box to continue performing the single action.

Edit...

"If you can confirm that you have swapped HR21's for HR24's and had the programming work on the new box then the issue is with their new box. "

I meant with the specific box that was installed at my clients house.

We partner with a Satellite installation company and we have been spec'n the HR23 because it comes in flat black. The service call i went on was the first one in a long time where the client called DirecTV before calling us. We always warn them to call us first but the original project is about 6 or 7 years old and we haven't seen him since then. I better stop now before i end up in full on rant about DirecTV/Cable/att guys.

I first ran into this issue with a RTI processors for a temp solution while the Crestron system was being built. That was from using RTI's library, but one of the files in their library worked fine.

I have done a few hr24 receivers and used the same codes from urc and rti that I have always used and they worked fine.

The H24 and HR24 are significantly more sensitive to ir. Ive found moving the emitter, relearning codes, modifying pulse times, has solves the issue.

I think there was a thread last year discussing this.

The HR24's are just way more intolerant of dirty codes.

I've had to relear/Redo codes for HR24's for the same issue.. But when I swapped a HR21 back into after I changed the codes, the old box still worked fine.

I've had the same thing happen on a G! (Elan/HomeLogic) system. I've yet to relearn them but I plan on it. Unless someone has "corrected" codes in hex that I can copy and paste

If I recall, it was chan -/+, cursor up and down. May have been others, but I experienced the same behavior ...like someone was Continually pressing the button, until I pressed another button. g! Has a away to look at the ir code to see if it is dirty. I also have URC MX980 remotes in this system and their behavior is normal (pulled from their IRDB). But the Elan/g! Supplied code is slightly corrupt with certain commands.

I have experienced two things lately. I would love to hear from someone who may have solved item #2.

1. Single code pulses causing the box to freak out and act like the control system is sending a continuosly held signal. I tried several different code sets including cleanly generated codes in make hex. I finally found a code set that work that I had never used before and I know nothing of it's origin. I only experienced this with Crestron so far.
2. Navigation commands having difficulty with single pulses. These seem to want to launch into the scroll mode and it will skip two or three items in a menu sporadically. This is a HUGE problem as I have not been able to resolve. I have tried numerous RTI codes sets (including makehex codes) and now a client has been reporting this with a Crestron system as well (seemed to work well before).

Is any of your RF or IR control wiring near any HDMI cables or extenders?
Just eperienced same issue.
Emitter did not look active, but it was enough interference to freeze the DTV box up.

tgrugett,
Problem #2 is solved in Post 1, Post 4, Post 6 (without mention of which file actually worked), and perhaps Post 8.

Ernie,

This specific issue (#2) is quite different from that mentioned in post 1,4 and 6, however, there is the possibility that they are somehow related.

What they are discussing is something I have experienced as well. When a code is issued (in my case just about any code), the box itself launches into a continous loop. The light on the front of the box keeps blinking as if a code was issued sustained. This behavior would stop with the issue of perhaps another code (or then launch into another endless cycle) or as a last result by powering the box off.

My specific issue is with the single pulse navigation commands. This seems to be an issue of the scroll function timing (just a guess really). When trying to navigate just one menu item up, down, left or right, it will often jump two or three items. I have seen this when controlling the box via IP but never IR until recently. I have changed the number of repeats, used different code sets, etc... all with no luck. ALSO... I noticed the other day that with an RTI system, I had no issue with a T2c but I did with two T1b+ remotes. All used the same code set. All were using a ZM24 for communication. One T1B+ was communicating through a second wireless ZM24 which seemed to accentuate the issue.

i had to learn new codes from the new remote.

Seems to follow the latest software update