Hello,
I've recently gotten another bike instead my previous.
Power output on CP Bluetooth service seemed to be working fine on my previous bike, but with current bike there are weird issues.
I noticed that majority of messages from the Bike come without leading bite F1 which ends up being not complete package and messages is not processed, even though message body looks OK.
Example:
18:56:08.857 -> F5 44 39 F6
18:56:08.857 -> 9 44 05 38 34 34 30 30 3A F6
18:56:08.857 -> proc 33224us BT 8us
18:56:08.894 -> logs 14048us
18:56:08.929 -> Invalid header
18:56:08.929 -> hu valid:1, bike valid:0
Interestingly, but there are still some messages with F1 as first byte, very rare but still.
Wondering if some changes happened in bike software or I'm missing something?
Maybe you know what might be the problem ?
Obviously I can change logic so that it won't validate bike response by first bite but rather read first 2 bytes from the body, which actually define message payload, but I'm wondering whether it's only mine problem or something has changed in protocol recently.
Hello,
I've recently gotten another bike instead my previous.
Power output on CP Bluetooth service seemed to be working fine on my previous bike, but with current bike there are weird issues.
I noticed that majority of messages from the Bike come without leading bite
F1which ends up being not complete package and messages is not processed, even though message body looks OK.Example:
18:56:08.857 -> F5 44 39 F618:56:08.857 -> 9 44 05 38 34 34 30 30 3A F618:56:08.857 -> proc 33224us BT 8us18:56:08.894 -> logs 14048us18:56:08.929 -> Invalid header18:56:08.929 -> hu valid:1, bike valid:0Interestingly, but there are still some messages with F1 as first byte, very rare but still.
Wondering if some changes happened in bike software or I'm missing something?
Maybe you know what might be the problem ?
Obviously I can change logic so that it won't validate bike response by first bite but rather read first 2 bytes from the body, which actually define message payload, but I'm wondering whether it's only mine problem or something has changed in protocol recently.