We are developing a taximeter app and use OBD data to retrieve the speed and then calculate travelled distance. All works fine on cars with an engine, but on electric vehicles the pids to use are obviously different for every manufacturer.

When we use Torque, we see that it is able to retrieve the speed and I found extended PIDs on Github for Torque, like “2101” for a Kia Niro.

When we send this command, we get something strange back, like this:
01B0:6101000000001:1261455A3D00000180:61010061453F2:5F3D00000000003:000000002D7F2B4:5017E7341B2D035:2D29524E17E6346:072D1699000000

On Github it says that w is (Signed(BB)*256)+BC, but there is no explanation on what BB or BC would be.

So, my question really is, how can we retrieve the speed value from the return string.
Help is much appreciated.

Have you tried using the “normal” speed PID but using different response message IDs (headers)?

EVs nearly always support “generic” PIDs but the responses are on different CAN IDs as the ECUs are different.

Do you have any CAN tools or just ELM327?

You essentially need to request PID 010D (actually PID 0D via service 01) using header 7DF and see any responses.

If that doesn’t work then use header 18DB33F1.

you have two blocks 7E8 and 7EA immediately answered
7E800C610302007F83 – here is your byte 0x02

you are using adapter setting ATCRA7E8? to read only responses from the 7E8 engine block?

7E8 00C 610302007F83B2162801807E
7E8 – address ECU engine
00C – number of bytes in response
6103 – positive response to request 2103 (6103=2103+0x4000hex)

B would be 00
C would be 7F
D would be 83? – yes

7E8 21 B2162801807E00
7E8 – the address from which the engine block responds
21 – identifier of the second line of the multiline response
B2 – byte E response
16 – byte F response
…

https://en.wikipedia.org/wiki/ISO_15765-2

Using CAN Extended Addresses
Some vehicles with CAN interfaces use a data
format that is slightly different from what we have
described so far. The data packets look very similar,
except that the first byte is used for the receiver’s (ie
target’s) address. The remaining seven bytes are used
as described previously.
We refer to this type of addressing as ‘CAN
Extended Addressing’, and provide support for it with
the AT CEA command.

We have an hybrid Prius Gen 3 from 2019 and have loaded the predefined PIDs labelled Prius Gen 3 (2010+).
But when we run the 2121 CCS Vehicle Speed with Equation ‘A’, we are not getting the vehicle speed, but heavily jumping values in the A field that are in no way related to the car’s current speed.
What are we doing wrong?

I thought I had understood the format that OBD returns after responses received here. But now I get this:
https://taximeter-gps.com/torque.png
which seems to be yet a different format again?
And why does it say hex=65 when there is no 65 in the response?

we tried with 2 different OBD dongles and the result is always the same. And both are not cheap ones.

Here’s a video showing what Torque does, and on the right our app showing the speed determined with GPS. (look at Geschw., German for speed).
It all looks rather weird and totally wrong:
https://taximeter-gps.com/torque.mp4
What are we doig wrong?