MSB vs. LSB8

[kvthie0]

Hello,

As a beginner I've probably a very, very basic question :

I converted several signals from MSB to LSB8. This is what I found in the help documentation of AnalysIR :

“LSB8 takes the MSB format hex value and turns each 8 bit byte of the overall HEX value into LSB. For example, the MSB HEX (Binary) value below is converted into LSB or LSB8 as follows:”

MSB: 01 02 03 (0000 0001 0000 0010 0000 0011)
LSB: C0 40 80 (1100 0000 0100 0000 1000 0000)
LSB8: 80 40 C0 (1000 0000 0100 0000 1100 0000)

When I translate the signal :

Hex: 0200280176091855C4400C00188000000000EA
Binary:
00000010 00000000 00101000 00000001
01110110 00001001 00011000 01010101
11000100 01000000 00001100 00000000
00011000 10000000 00000000 00000000
00000000 00000000 11101010

from MSB into LSB8 I get :

Hex: 044001E80689A13A2200038011000000007005
Binary:
00000100 01000000 00000001 11101000
00000110 10001001 10100001 00111010
00100010 00000000 00000011 10000000
00010001 00000000 00000000 00000000
00000000 01110000 00000101

I thought (following the help documentation) this would result in :

Hex: 400014806E9018AA2302300018010000000057
Binary:
01000000 00000000 00010100 10000000
01101110 10010000 00011000 10101010
00100011 00000010 00110000 00000000
00011000 00000001 00000000 00000000
00000000 00000000 01010111

Could someone please explain to me where I'm wrong ?

Thanks a lot.

(Sample taken from a Sanyo AC rcs-3pss4e remote with only the AC protocols selected and with Arduino "sketch_AnalysIR_Firmware_801.ino")
Signal recognised by AnalaysIR as SANYO152AC protocol

[AnalysIR]

Hi

something does seem amiss....

Please email me a saved session file (support@....) with that signal via: Menu->File->Save Session and I will investigate.

make sure to include that particular signal & any others you have handy from the same remote.

[AnalysIR]

Thanks for emailing the signals.

You were correct, it was a bug, which seems to occur only when the first byte or value begins with 0x0.

It is strange that this is the first time it has been encountered like this.

I will issue a new 'dev' update in the next few days.

Thank you for identifying & reporting this issue.