[ANBO]

Torque has a problem decoding the message, will try a more modern app.

Torque Pro seems to accept
Byte [0,1,2,3]: INT32(A:B:C)
Byte [4,5,6,7]: INT32(E:F:G:H)
Etc.... to device. Or did you mean something else?

Do you have any idea how to have Torque Pro log the full HEX string?

0x20000

Any idea how to code 0x20000 in Torque Pro, other than entering the DEC value?

 

[dernotte]

I am still looking for elevation and compass.
PID d9b0 is only 1 byte. It is quite flat around here, but the value looks like going down when I drive down to the river, and the value goes up when I go the opposite direction. The value always get back to the same value when I get back home.

I have double checked with a Garmin GPS, and it says elevation = 32m, and PID D9B0 says "1F", quite close... I will try to go in the mountain around here, this afternoon, go get other value, and check again my Garmin.

 

[dernotte]

ok, I was completely wrong. After a few tests, it appears that PID D9B0 is the TCU cell signal quality (between 0 - 32).

 

[ANBO]

ok, I was completely wrong. After a few tests, it appears that PID D9B0 is the TCU cell signal quality (between 0 - 32).

Cannot get them all right at once

 

[Maxwell_400]

Torque has a problem decoding the message, will try a more modern app.

Torque Pro seems to accept
Byte [0,1,2,3]: INT32(A:B:C)
Byte [4,5,6,7]: INT32(E:F:G:H)
Etc.... to device. Or did you mean something else?

Do you have any idea how to have Torque Pro log the full HEX string?

I cannot get Torque to read the first frame, the second is ok. Tried R0, R1, N0, N1, etc. Works with a different app.

Made my own pid scanner script for the windows laptop so I am able to do whatever the ovms box does and thinking about porting it to an android app.

You are not supposed to look at the screen while driving, but I think on the main screen it can be nice to have power, battery temp and estimated remaining range while driving.

 

[Maxwell_400]

ok, I was completely wrong. After a few tests, it appears that PID D9B0 is the TCU cell signal quality (between 0 - 32).

Good to know TCU signal quality anyway.

 

[ANBO]

Torque has a problem decoding the message, will try a more modern app.

Torque Pro seems to accept
Byte [0,1,2,3]: INT32(A:B:C)
Byte [4,5,6,7]: INT32(E:F:G:H)
Etc.... to device. Or did you mean something else?

Do you have any idea how to have Torque Pro log the full HEX string?

I cannot get Torque to read the first frame, the second is ok. Tried R0, R1, N0, N1, etc. Works with a different app.

Made my own pid scanner script for the windows laptop so I am able to do whatever the ovms box does and thinking about porting it to an android app.

You are not supposed to look at the screen while driving, but I think on the main screen it can be nice to have power, battery temp and estimated remaining range while driving.

Doesn't seem to work for me neither

 

[ANBO]

I agree that last byte is probably the number of sattelites,
byte[8] = 0x03 . I have no idea what it is.

It could be the number of constellations used for fix: Gps, Galileo, Glonass.
But it's just a guess....

Suggest it is the GPS accuracy. On my phone, in the car this is 6m.

PS made progress (with kind forum helpers) on getting 3 out of 4 of these working in Torque Pro. Latitude is still giving trouble.

Since these are multi line responses, there is a need for Start and Stop commands:

Start: atd1\nath1
Start: atd0\nath0

Also instead of A:B use R1:R2

Latitude: INT32(Signed(R0):R1:R2:R3)/131072
Longitude: INT32(Signed(R4):R5:R6:R7)/131072
Accuracy: R8
Sattelites: R9

 

[dernotte]

Can you look at : https://ipace.herokuapp.com/static/param.html
What do you read for TU_STATUS_DAYS_SINCE_GNSS_FIX ?
I am pretty sure that byte 8 is that number.

 

[ANBO]

There I am getting 1. Will check again tomorrow, but since I had the car out yesterday as well, I would not expect 3 days since the last fix.

 

[ANBO]

For those interested Torque Pro fixed the reading of the GPS PID.

Latitude: INT32(Signed(A):B:C: D)/131072
Longitude: INT32(Signed(E):F:G:H)/131072
Accuracy?: I
Sattelites?: J

Any successes on Heading and Altitude?

 

[dernotte]

I was not able to find those 2 (Heading and Altitude) in TCU , if I remember correctly.

 

[ANBO]

Have the same recollection. Just checking

 

[Maxwell_400]

For those interested Torque Pro fixed the reading of the GPS PID.

Latitude: INT32(Signed(A):B:C: D)/131072
Longitude: INT32(Signed(E):F:G:H)/131072

Thanks! I thought Torque Pro was abandonware, glad to see it updated.

 

[ANBO]

Not very active neither, but GPS I was interested in to get to ABRP, to be able to get the phone back to the centre console or think about a blackberry PI.

ABRP are looking more at AA/Carplay to pull this from the car, rather than through OBD. We'll see.

At least TorquePro has a fix.

 

[kermit68]

At least TorquePro has a fix.

Unfortunately only for MY19/20, I struggled unsuccessfully to talk to TCU on MY21 .... It's a ghost, it's there but no way to reach it, and not just for GPS. No answer to any PID.

 

[ANBO]

Weird. Have you ever tried the test button in the PID editor?

 

[Grunt]

Super! What is the name of the PID?
The GPS longitude and latitude are just read from the phone, I hope you didn't get confused!

 

[ANBO]

22a0a6 on 754

 

[dernotte]

22a0a6 on 754

Just for info, "22" is the "read canbus command", and "A0A6" is the PID..