Frsky-D Telemetry protocol bug (0x5D followed by 0x3D)
I should add a non regression test...
This commit is contained in:
@@ -84,7 +84,7 @@ void parseTelemHubByte(uint8_t byte)
|
|||||||
byte = byte ^ 0x60;
|
byte = byte ^ 0x60;
|
||||||
state = (TS_STATE)(state - TS_XOR);
|
state = (TS_STATE)(state - TS_XOR);
|
||||||
}
|
}
|
||||||
if (byte == 0x5d) {
|
else if (byte == 0x5d) {
|
||||||
state = (TS_STATE)(state | TS_XOR);
|
state = (TS_STATE)(state | TS_XOR);
|
||||||
return;
|
return;
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user