On March 9, 2017 at 21:23, huxstable said...
What I'm being told is their preferential protocol for IR remote controls is NEC, RC5 and RC6, is there any way to translate the 3 remotes we need to those requirements?
Pronto Hex could be an option, could that translate to the IR functions we need with each remote?
Your LG codes can easily be translated.
POWER 12 0x88FD NEC(uPD6121G) in your example would become
POWER 08 0x04FB NEC(uPD6121G) from your table, or possibly
POWER 08 0xFB04 NEC(uPD6121G) depending on what they expect for low byte and high byte
ATV and DTV are none of the above protocols. Apple has its own protocol, and DirecTV is Russound protocol. There is no need to translate pronto hex for those. We already know function, low custom and high custom for every ATV and DTV command. Problem is they have no way to use the correct protocol. If you join the JP1 forum and download Remote Master and open these 2 files, then Function = OBC, Low Custom = Subdevice, High Custom = Device (low and high might be reversed).[Link: hifi-remote.com][Link: hifi-remote.com]As I said via PM, the company building your remote is incompetent. You picked the wrong manufacturer if their remote can only do 2 protocols essentially (NEC and RC5/6). Other universal remote makers can do hundreds.
If you only need a few hundred of these, just get some cheap JP1 remotes ($3-$4 ea.) plus a JP1 cable ($8), and you can load all your commands into each in about 3 seconds. Even if you had a few thousand remotes, one of your employees could load all of them in a few hours.
