DecodeIR and Nokia32

Post by **The Robman** » Mon Sep 26, 2011 9:58 am

Would it be possible to change the way that the Nokia32 protocol is decoded by DecodeIR?

Currently it reports the "X" value (in the Misc column) as an 8-bit value, whereas in fact it's really a 7-bit value. The MSB is really a toggle bit.

If you look at the signals learned in this thread you'll see that the X value is reported with values 38 and 166. I would prefer to see it just reported as 38, with an additional entry of T=1 or T=0 depending on the value of the toggle.

3FG · Post by **3FG** » Mon Sep 26, 2011 11:49 am

I'll take a look. Seems like that should be doable.

Post by **vickyg2003** » Mon Sep 26, 2011 12:04 pm

Another way to fix this would be to write up a protocol help/ protocol note for both KM and RM. The "no help available" makes this harder than it needs to be.

NEC1 · Post by **NEC1** » Wed Feb 01, 2012 4:49 am

T=x usually indicates the Toggle bit, as used by certain protocols such as Philips RC-5.

eferz · Post by **eferz** » Wed Feb 01, 2012 9:42 am

NEC1 wrote:T=x usually indicates the Toggle bit, as used by certain protocols such as Philips RC-5.

Rob wants to simplify the user's perception of the information. IR Scope and RMIR will show a high number and a low number when X incorporates the toggle bit. The difference between the two numbers is 128d which is the eighth bit. So, showing the value of the first seven bits as X would disentangle the necessary input in RM for the "X:" and the "High X-bit" entries.

However, I also agree with Vicky that the documentation should also reflect the how the Nokia32 is decoded. Because if the X value was over 128 and constant then that can also pose confusion. Not that I've ever seen these occurrence but it is possible.

JP1 Remotes