Torque

Forums

Forums

Guest  

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




Torque » Torque OBD ECU Scanner » Torque Discussion / Ideas » Vauxhall (Opel GM) DPF PID

Pages: 1 [2] 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Author Topic: Vauxhall (Opel GM) DPF PID
piemmm
Administrator
Posts: 6052
Post Re: Vauxhall (Opel GM) DPF PID
on: April 21, 2016 (GMT)

Got it, thanks. Looking into it…

piemmm
Administrator
Posts: 6052
Post Re: Vauxhall (Opel GM) DPF PID
on: April 21, 2016 (GMT)

Hi! Right! – in the 1.8.92 update you’re going to get a new set of variables that you can use in the equation parser…

Torque traditionally takes some of the hard work away when dealing with responses (which is why you don’t immediately need to start of with variable D in a lot of cases). The variables starts from A, B, C, for mode 21, 22, 01, etc where the data headers and response status have already been removed for you. (these are also mirrored by variables N0, N1, N2 (etc) for simplicity)

However, with some awkward manufacturers, they may reply with no header at all (with useful information at the start of the packet that you’ll want to get at).

To get the variables for the *whole* raw data reply, you can now use the following variables:

R0, R1, R2, R3 (etc) where in most cases R3/4 would equate to ‘A’ in normal mode21/22/01 messages (depending if you’re using canbus or an iso protocol like 9141)

So, R0 (‘Raw 0’) will get you the absolute start of the message, which should give you access to the bytes you want

So the equation would now look like:

R0 * 5

For the first value in the reply

cintakc
Member
Posts: 1235
Post Re: Vauxhall (Opel GM) DPF PID
on: April 21, 2016 (GMT)

I also thank the author for this opportunity to be used in the formula bytes from the first byte of the response is very useful changes.
Thank you.

-vincent
Member
Posts: 40
Post Re: Vauxhall (Opel GM) DPF PID
on: April 21, 2016 (GMT)

Very useful.
Thank you!

Cintakc,
do you have any other useful AA PIDs (I saw you mentioned a scanner)?

I discovered other 3 PIDs in mode AA, just looking at the results (and only beeing able to see from the 5th byte on)… it would be nice to have more!

cintakc
Member
Posts: 1235
Post Re: Vauxhall (Opel GM) DPF PID
on: April 21, 2016 (GMT)

Now look at the information, it can help you
the reply address yet 7E8, with that address the scanner is working properly, that then you is obtained the wrong address 5E8
https://yadi.sk/d/A-qU6L6XrBbUD

-vincent
Member
Posts: 40
Post Re: Vauxhall (Opel GM) DPF PID
on: April 21, 2016 (GMT)

Thanks a lot.
I’m trying to understand how to use it…

-vincent
Member
Posts: 40
Post Re: Vauxhall (Opel GM) DPF PID
on: April 22, 2016 (GMT)

ok, maybe I understood.
Unfortunately all the answers are very similar so it’s really hard to map each request from the software to a message in the log file…

cintakc
Member
Posts: 1235
Post Re: Vauxhall (Opel GM) DPF PID
on: April 22, 2016 (GMT)

Give your answer in the terminal supports requests, I will look

Capp777
Member
Posts: 2669
Post Re: Vauxhall (Opel GM) DPF PID
on: April 22, 2016 (GMT)

As a dynamic pid isn’t it true that
the sensors in the response can be
changed? … hence “dynamic”.

piemmm
Administrator
Posts: 6052
Post Re: Vauxhall (Opel GM) DPF PID
on: April 22, 2016 (GMT)

Hi!

1.8.92 has now been sent out – you should get it in about an hour! There are a few improvements to the PID editor ‘test’ button which should hopefully be useful to you!

-vincent
Member
Posts: 40
Post Re: Vauxhall (Opel GM) DPF PID
on: April 22, 2016 (GMT)

Thanks Ian.
Unluckily if I use ath1 R0 variable starts reading from the very beginning… that is 5e8 in my case.
So reaching the useful data I’m shifted 1 nibble.

If I don’t use ath1 it is not shifted but R0 starts from the second useful byte.

I imagine I could do some bit reading, but I’d avoid it if possible.

piemmm
Administrator
Posts: 6052
Post Re: Vauxhall (Opel GM) DPF PID
on: April 22, 2016 (GMT)

Hi

Can you send me a debug file with that instance, there’s obviously something different compared to my testing here – I’ll then get that sorted out)

Though I admit I didn’t try the ath1 command before your request – didn’t expect anyone to do that as it’s better to do the atsh XXX command instead (and let the app handle the headers)

Edit: can you double-check that it’s definitely getting the second value, as all the tests I’ve done show it getting the first value for the:

{AA0118
}826
}0:3261004700

response given as an example, which is 0x32(50 decimal)

Capp777
Member
Posts: 2669
Post Re: Vauxhall (Opel GM) DPF PID
on: April 22, 2016 (GMT)

Im thinking the 8 is part of the dpid (18)?
and 26 should be first data byte?
32 would be second?

piemmm
Administrator
Posts: 6052
Post Re: Vauxhall (Opel GM) DPF PID
on: April 22, 2016 (GMT)

Page 42 of the ELM327DS pdf says that the first numbers are the length of bytes (apparently 0x826 in this case!?) and that the data starts after the 0: (hence 0x32)

in the earlier response I can see that part of the message isn’t chopped off, so I suspect the formatting in the ELM327 has thrown me a little on this one.

Capp777
Member
Posts: 2669
Post Re: Vauxhall (Opel GM) DPF PID
on: April 22, 2016 (GMT)

Length doesn’t make sense in this case
with the small number of bytes in the
message… I would think non standard
response.

My comments are based upon my observation
of the bytes of the previously posted responses
to yours. While the values are slightly different
the pattern is similar.

cintakc
Member
Posts: 1235
Post Re: Vauxhall (Opel GM) DPF PID
on: April 22, 2016 (GMT)

7e0 AA0118
7e8 180102030405…

7e0 AA0117
7e8 17010203040506…

7e0 AA0105
7e8 050102030405…

piemmm
Administrator
Posts: 6052
Post Re: Vauxhall (Opel GM) DPF PID
on: April 22, 2016 (GMT)

Yep and the test case was with can formatting enabled, and this is obviously chopping a nibble off (you miss the starting’1′ in the formatted version)

I’ll get on and sort this out, though you should still be able to access the valid bytes from R0 in the message in this state as it is the sensor data after the 0:

ie: the

826
0:xxxxxx

is missing the 1 (due to the formatting method) – iirc the 1 was used to signify multiline responses as far as the ELM327 is concerned

7e0 AA0118
7e8 1826xxxxxxxx

The other formatted message obviously isn’t correct so I will setup a test case for that and sort out the off-by-one issue

cintakc
Member
Posts: 1235
Post Re: Vauxhall (Opel GM) DPF PID
on: April 22, 2016 (GMT)

I still think in -vinsent defective adapter

piemmm
Administrator
Posts: 6052
Post Re: Vauxhall (Opel GM) DPF PID
on: April 22, 2016 (GMT)

Might be defective – there’s some very odd adapters out there,… I’ve still gotta make it work reliably though :-)

Capp777
Member
Posts: 2669
Post Re: Vauxhall (Opel GM) DPF PID
on: April 22, 2016 (GMT)

Without a leading zero I can see in your
example how the data bytes are shifted
by a nibble.

Edit:

Since this seems to be a non standard
response maybe his adapter is perfectly
fine and the response is returning something
different than the 7E0+8 we would logically
expect?

Vincent’s atcra filters are changing to a
different header then back to what we
would normally expect?

Pages: 1 [2] 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
WP-Forum by: Fredrik Fahlstad, Version: 2.4
Page loaded in: 0.105 seconds.

  Follow me on twitter