JP1 Remotes

Hmmm. Interesting that you would assume I meant Kerry's opponent, when I mentioned brain-dead voters.

I feel like detective Columbo. "I never said she was strangled! Only that she had been murdered!"

I'll abstain from the political comments... 8)

I need a little clarification on something from Jon's message in the other thread,

jon_armstrong wrote:

johnsfine wrote:.
bit5: Overrides the subdevice from the selected fixed data to be the no_subdevice value. That's barely ever useful, since no_subdevice is typically done by having RM or KM compute the no_subdevice value for fixed data. But I guess there might be a need for mixing two different devices and having one of those mix a subdevice with no_subdevice.

Yes but 0=>Overrides sub-device, 1=>allows subdevice

When bit5=0, does it ignore the sub-device altogether, or does it just use the complement of the specified device?

Mark Pierson wrote: When bit5=0, does it ignore the sub-device altogether, or does it just use the complement of the specified device?

1) What's the difference? We define having no subdevice (in NEC) as being the same signal as a subdevice equal to 255 minus the device.

2) I don't see any reason for KM to ever clear bit5 of that byte in this combo protocol. I think the four choices end up being 0x20, 0x21, 0xA0 and 0xA1. If a subdevice field is left blank on the setup sheet, KM already knows how to encode that in the fixed data, so it doesn't need to encoded in the hex command.

johnsfine wrote:If a subdevice field is left blank on the setup sheet, KM already knows how to encode that in the fixed data, so it doesn't need to encoded in the hex command.

I just wanted confirmation of that.

BTW, I just wanted to confirm that the NEC 2DEV Combo protocol now works correctly in both RM 1.05 and KM 8.28. I've tested both with my NEC 2DEV Combo device.