Torque

Forums

Forums

Guest  

Show or hide header
Welcome Guest, posting in this forum require registration.




Torque » Torque OBD ECU Scanner » Torque Discussion / Ideas » Bytes error in custom PID

Pages: [1]
Author Topic: Bytes error in custom PID
solma
Member
Posts: 6
Post Bytes error in custom PID
on: June 21, 2013 (GMT)

Here what it read when testing this PID 2101.

Response:01F
0:6101 4800 3001
1:1C25 4A41 655A 0B
2:C600 00A6 0524 4E
3:2222 00F’F 2CBA 33
4:B537 5749 0000 00

The caracter ‘ is for sure not hex, it disappear from time to time, but mostly present. I can imagine that its causing a fluctuation in the result I am searching for.

solma
Member
Posts: 6
Post Re: Bytes error in custom PID
on: June 24, 2013 (GMT)

Did more debugging using Hyperterminal(PC), here’s my finding:

The ” ‘ ” is related to torque app or nexus 7 port, do not know why, hyperterminal does not received this caracter from the adapter and I try lowering usb com speed in case it was the OTG cable that would induce noise thus error on the tablet side with no difference, so it as to be tablet side related.

I know now why I am not able to read a correct value(byte) using the formula parameter, if you look the data received by torque in the previous email, my adapter obdlink sx(usb), use the standard 15765 protocol to transmit data, that means, that it can not transmit more than 7 concecutive bytes, so it use multiple message to transmit the complete data, the standard ask for numbering each message follow by ” : “, the bug in torque is that it think that the message number is a data value, here an example:

0:6101 4800 3001
1:1C25 4A41 655A 0B
2:C600 00A6 0524 4E
3:2222 00F’F 2CBA 33
4:B537 5749 0000 00

Formula: AB = 0x53
Formula: AC = 0x75

It cause torque to shift the reading from the end of half a byte(4LSB) and the start of the other(4MSB).

That why bluetooth adapter does not have this problem since the data is reformated before going into torque app.

Pages: [1]
WP-Forum by: Fredrik Fahlstad, Version: 2.4
Page loaded in: 0.035 seconds.

  Follow me on twitter