OK, I re-decoded the signal by hand and first off, I discovered that the 2nd OBC is actually 173, not 210. But I also spotted the checksum issue that John mentioned.
Normally, these signals come in 4 parts:
a device code
the complement of that device code
a command code
the complement of that command code
In this case, they XOR'd the LSB of the command code complement, so whereas the binary would normally be...
11000101 00111010 10011001 01100110
11110101 00001010 10110101 01001010
in this case, the binary is...
11000101 00111010 10011001 01100110
11110101 00001010 10110101 01001011
(notice that the last bit of the 2nd line is different)
If I get a chance, I may write a new protocol that will handle this, just so we can present an upgrade for others that need it, rather than just creating a one time learned signal for you.
As for the lack of an ADD or EDIT button for learned signals, I've been asking for that for years!
