Strange 09 inserted in csafe
Posted: October 22nd, 2019, 12:41 pm
Hi,
I have a problem that my pm5 ergometer returns strange 09 values which I think do not follow the csafe definition (or may be there is some thing that I do not know). in am sending the following csafe commands to my pm5 ergometer:
f11a01891a018d1a019f1a018e1a01cf1a01a01a01a31a01a0a1d8f2
And it returns in hex:
f1091a038901031a038d01011a039f01001a038e01ff1a04cf0200001a07a005f3000a0000091a07a30532000000091a07a005f3000a000009a1035e00246af2
I have set all commands on separated lines for clarity. The second byte is the length. The first commands with length 03 and 04 go right. And then a command with length 7 is returned.After these commands I expect the next command , just like the first commands. But here it inserts an extra 09 byte and then the real command follows. I can not find the 09 in any csafe definition and it is the same command with just a different length. It looks like some kind of bug or is it an hidden feature?.
f1
09 status (also strange value first 4 bits has a value from 0-8 and not 9, but not a real problem since I ignore it)
1a 03 89 01 03
1a 03 8d 01 01
1a 03 9f 01 00
1a 03 8e 01 ff
1a 04 cf 02 00 00
1a 07 a0 05 f3 00 0a 00 00
09 <- here it inserts an extra 09 which should not be there
1a 07 a3 05 32 00 00 00
09 <- here it inserts an extra 09 which should not be there
1a 07 a0 05 f3 00 0a 00 00
09 <- here it iserts an extra 09 which should not be there
a1 03 5e 00 24
6a crc
f2
Pm5 with Firmware = 22, Hardware = 340, connected using usb
I hope you can help me with this so I can make more stable connections using ergometer-space.org
Thanks
I have a problem that my pm5 ergometer returns strange 09 values which I think do not follow the csafe definition (or may be there is some thing that I do not know). in am sending the following csafe commands to my pm5 ergometer:
f11a01891a018d1a019f1a018e1a01cf1a01a01a01a31a01a0a1d8f2
And it returns in hex:
f1091a038901031a038d01011a039f01001a038e01ff1a04cf0200001a07a005f3000a0000091a07a30532000000091a07a005f3000a000009a1035e00246af2
I have set all commands on separated lines for clarity. The second byte is the length. The first commands with length 03 and 04 go right. And then a command with length 7 is returned.After these commands I expect the next command , just like the first commands. But here it inserts an extra 09 byte and then the real command follows. I can not find the 09 in any csafe definition and it is the same command with just a different length. It looks like some kind of bug or is it an hidden feature?.
f1
09 status (also strange value first 4 bits has a value from 0-8 and not 9, but not a real problem since I ignore it)
1a 03 89 01 03
1a 03 8d 01 01
1a 03 9f 01 00
1a 03 8e 01 ff
1a 04 cf 02 00 00
1a 07 a0 05 f3 00 0a 00 00
09 <- here it inserts an extra 09 which should not be there
1a 07 a3 05 32 00 00 00
09 <- here it inserts an extra 09 which should not be there
1a 07 a0 05 f3 00 0a 00 00
09 <- here it iserts an extra 09 which should not be there
a1 03 5e 00 24
6a crc
f2
Pm5 with Firmware = 22, Hardware = 340, connected using usb
I hope you can help me with this so I can make more stable connections using ergometer-space.org
Thanks