JP1 Remotes

Hi, I searched the downloads area and don't see any Zapperbox updates, so I'm trying to create one for a URC3660. According to Zapperbox, they use "NEC protocol with device ID code 0xBD02". I tried learning a few signals and RMIR recognizes most as NEC1 with device 2 and subdevice 189, but in most cases they don't match up with the hex codes Zapperbox provides. The number keys correspond to the hex codes Zapperbox provides, but the rest do not. Is there another protocol I should try, or maybe a different device and sub device? I have managed to get the keys learned using NEC1 with 2 and 189, so this is mostly my curiosity.

landolfi wrote:... in most cases they don't match up with the hex codes Zapperbox provides.

What are the "hex codes Zapperbox provides"? Give one (or more) examples of a learned key, and how the numbers differ.

Barf wrote:What are the "hex codes Zapperbox provides"? Give one (or more) examples of a learned key, and how the numbers differ.

I found them here, in FAQ #13:
https://zapperbox.com/pages/faqs

The ZapperBox remote control uses NEC IR wave forms. The NEC device ID code is 0xBD02. Here are the hex codes for each key:

On/Off: 45
Mute: 80
DVR: D2
Live TV: 5D
Record: 95
BA: D0
Guide: 19
Info: 99
Up: CA
Left: 99
OK: CE
Right: C1
Down: D2
Zap: 42
Menu: 41
1: 43
2: 03
3: 44
4: 46
5: 07
6: 47
7: 55
8: 17
9: 56
Decimal: C3
0: 1B
Back: 11

I have created an upgrade based on those codes here:
https://www.hifi-remote.com/forums/dload ... e_id=27238

The Robman wrote:I have created an upgrade based on those codes here:
https://www.hifi-remote.com/forums/dload ... e_id=27238

Thanks, Rob!

My question is, how did you create an upgrade based on those codes? That is, how did you know to translate their DVR=D4 to DVR=D2, or their Info=99 to Info=66? I know yours work, I'm just curious what I should have done to make an upgrade out of what they provided.

The first step is to understand what their hex codes mean. When you discovered that NEC device ID code is 0xBD02 translates to NEC1 with device 2 and sub-device 189, that confirmed for me that they are simply encoding the decimal device codes and OBCs into hex (as 0x02=02 and 0xBD=189), though I was surprised that it was quoted as 0xBD02, rather than 0x02BD,so I simply converted all of their hex codes into decimal and entered those into the upgrade as the OBC values.

I didn't pay any attention to the hex codes that RM generated because those represent something completely different. In case you're interested (or curious), the hex codes that RM generates are what is required to get the executor to generate the right signals. NEC is an "LSB" protocol, which means the binary is sent "backwards" (least significant bit first). If the OBC was decimal 3, for example (line the number-2 button), the binary is 00000011 but what gets sent by NEC is 11000000. The UEI executor for NEC is a "comp" executor, which means it has the 1s and 0s reversed, so 11000000 becomes 00111111 (or 0x3F in hex).

Thanks, Rob. I was trying to enter these provided codes into the hex column, that's where I went wrong. But I especially appreciate the background on what's happening, explained in a way a casual user can understand. Thanks also for many years of excellent support on this site!