Fix decoding MSPv2 message codes with high byte != 0
OR the high byte of the MSPv2 code with the "code" variable rather than with this.message_length_expected. This wasn't caught earlier because it would work for MSPv2 commands with the high byte set to zero anyway.pull/271/head
parent
836f72661c
commit
8fd6e93fe2
Loading…
Reference in New Issue