Just sent the debug file a couple of times.
Without ath1 first, then with it.
Thanks

Vincent,

Just curious… are you seeing mode AA
responses from other modules e.g.,

7E9-200 (hex) = 5E9 (hex) ?
7EA-200 (hex) = 5EA (hex) ?
7E8-200 (hex) = 5E8 (hex) ?

Wondering if there is a pattern with your
non standard messages.

5e8 doesn’t come from my adapter.
Just copied the sequence (atcra5e8 etc.) from another app…

Cintakc,
is your emulator hardware or software?

Ian,
You could just put another set of variables (eg Z0, Z1, …) that just skip the first nibble. I would use it with ath1 and Z0 would be “e8” in my case. I would use from Z1 on…

Cintakc,
is your emulator hardware or software?

emulator hardware-software

I’m guessing it works only with your
emulator since it is sending a standard
can response which the adapter would
know how to parse but not with the 5E8
that vincent’s vehicle is sending.

hi guys…

i also have a chevy aveo (t300) with a13dtr diesel engine. i’m a total noob with these equations and stuff but i have obdlink mx and if there is anything i can help about, just tell me how to do it

i also want to see dpf soot load and if possible force regen for dpf… gm mdi tool can see/do this so why cant torque?

Ian would have to fix by whatever way he
chooses. I don’t know anyway that you can get
get Torque to read the correct data values until
he modifies the app.

From the second byte onward you might be able
to “and” and bit shift to get an answer but that
would take some effort.

I’m sure Ian will figure something out.

Ok. I did it!
At jhf0 is not recognized by my adapter.
I used atd1. It “magically” inserts a “7” after the 5e8. Together with ath1 R0 starts reading from the 5e. R3 is my first useful byte.
I will also try avoiding ath1 bit not sure it works.

Start config: atcra5e8 \n atd1 \n ath1
Stop config: atcra7e8 \n atd0 \n ath0

Not sure if everything is needed. Something in the stop config avoids torque to loose connection.
I also sent debug file out.

Thanks!

Interesting way to slip a data length
digit in between the header and data
bytes.

I thought jhf0/jhf1 are for the J1939
protocol used by commercial vehicles.

Edited.

Thanks Ian.
Do you already know how you’ll address it?

I also noticed few issues:
– when I change the start/stop config in one custom pid, this reflects on all other custom pids.
– if I insert many displays on the real time screen and then I need to change something in the pids definition (e.g. equation, config, unit…) this doesn’t reflect in the real time screen, and I need to re-insert every display from scratch
– it seems there’s no way to import pids, including start/stop config, from csv file