Something wrong with bytestuffing
|Assignee:||Android Dashboard Developers||% Done:|
|Target version:||2.0 Multiple models|
"End byte" of frames (7E) also gets "decoded" to 7D 5E
This should not happen
Tested without hub
with ad1 connected to sensor
closes #402 added truncating of decoded frame. Added option to print out hex representaton of frame without additional decoding
This does not consistenly reproduce.
When it happened, most frames would end up as corrupt. The frame looked like this:
7e fe 7d 5e a2 58 ac 00 00 00 00 7d 5e 00
I do not know if it got decoded. length seems strange
Happended again this is the frame pattern that it reacts too:
Before: 7e fe 7d 5d a1 62 c8 00 00 00 00 7e
After: 7e fe 7d a1 62 c8 00 00 00 00 7e 00
So, decoding does not change the size of the frame. This will trigger a corrupt frame..
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset r340.
Also available in: Atom