I programmed a few TSU3000's with number buttons for an RCA DVR40 (DirecTV TiVo box). They work fine when pressed manually, but spit out 3 times if I put them into a macro (e.g. "123" comes out as "111222333").

Has the new firmware changed this at all?

Does anyone know how to edit these codes somehow to prevent them from repeating?

I've tried using a "light touch" when learning; all I get out of the DirecTV remote are fairly long strings like this (number 1 button):

0000 006D 0000 0022 0155 00AA 0016 003F 0016 0013 0016 003F 0016 0013 0016 0013 0016 0013 0016 0013 0016 003F 0016 0013 0016 0013 0016 0013 0016 0013 0016 003F 0016 003F 0016 0013 0016 0013 0016 0013 0016 0013 0016 0013 0016 003F 0016 0013 0016 003F 0016 0013 0016 0013 0016 0013 0016 0013 0016 0013 0016 0013 0016 003F 0016 0013 0016 003F 0016 003F 0016 0300

The Pronto hex string you posted specifies that the command frame should be repeated as long as you hold the button.

Unfortunately, in a macro there is no method to control how long the firmware thinks the button should be held. Various versions of the firmware seem to have various rules for how long the hold each button.

In this case, you probably want the command frame sent exactly once, which is easily done by changing the third and fourth values in the Pronto Hex string from "0000 0022" to "0022 0000".

However, I can't be sure sending that frame just once is really best. Some devices expect a single command to be sent as two or three copies of the command frame. The fact that your TiVo sees the command three times does NOT mean the Pronto sent the frame three times. Probably the Pronto sent the frame far more than three times and the TiVo sees each several copies of the frame as a repeat of the command.

So sending two or three frames might be a more reliable way to send the command once. That may be tricky to do with an NG Pronto (Sending just once is easy. Sending some number of times stupidly chosen by the Firmware is also easy. But sending a controlled number of times is not easy.) However, the following will probably send the command twice correctly, which is a version worth testing:

0000 006D 0044 0000 0155 00AA 0016 003F 0016 0013 0016 003F 0016 0013 0016 0013 0016 0013 0016 0013 0016 003F 0016 0013 0016 0013 0016 0013 0016 0013 0016 003F 0016 003F 0016 0013 0016 0013 0016 0013 0016 0013 0016 0013 0016 003F 0016 0013 0016 003F 0016 0013 0016 0013 0016 0013 0016 0013 0016 0013 0016 0013 0016 003F 0016 0013 0016 003F 0016 003F 0016 0E00 0155 00AA 0016 003F 0016 0013 0016 003F 0016 0013 0016 0013 0016 0013 0016 0013 0016 003F 0016 0013 0016 0013 0016 0013 0016 0013 0016 003F 0016 003F 0016 0013 0016 0013 0016 0013 0016 0013 0016 0013 0016 003F 0016 0013 0016 003F 0016 0013 0016 0013 0016 0013 0016 0013 0016 0013 0016 0013 0016 003F 0016 0013 0016 003F 0016 003F 0016 0E00

Thanks for the info - pretty intimidating stuff, though! I'm completely new to this... Are there any good resources out there that would explain the structure of these hex codes in detail?

You need the current firmware to mostly eliminate this problem.

You can start with this document [Link: remotecentral.com]

or read virtually any post from johnsfine or jarmstrong.

Hopefully the firmware will magically eliminate the problem, but I'm digging into RC Glossary anyway. I sure brought my question to the right place! Very helpful - thanks everyone!