Hi to all,

I added a lot of times ago the additional oil temp pid, with these settings:
_______
OBD2 Mode and PID: 2101
Minimum Value: -40
Maximum Value: 190
Scale factor: x1
Unit type: C
Equation: AC-40
OBD Header: 7E0
_______

it work..
but some times the value make errors…
explaining better:
we suppose to be at 90°C, for a 1/2 second the value pass at 150 then 90°..or -24° then 90°..

only this pid do this “flash”..

Torque updated at last version. this problem is not new, always present from the beginning.

car: Subaru BRZ
OBD: OBDLink SX SCANTOOL USB
device: Android HUD T7019A

any idea?

Hi

AC is valid – for long responses (which 2101 may provide) can cause things to get ‘big’ in variable-space. so when torque hits Z, it then goes AA, AB, AC, AD, AE (etc)

The occasional flicker to an incorrect value is caused by the adapter corrupting the data. This exclusively happens with some of the Chinese clones adapters and there’s nothing that can be done about it apart from replacing the adapter

You will likely see after a long time that the error count may sometimes increment as well as the app can sometimes detect this

Quote from admin on April 15, 2016
Hi

AC is valid – for long responses (which 2101 may provide) can cause things to get ‘big’ in variable-space. so when torque hits Z, it then goes AA, AB, AC, AD, AE (etc)

The occasional flicker to an incorrect value is caused by the adapter corrupting the data. This exclusively happens with some of the Chinese clones adapters and there’s nothing that can be done about it apart from replacing the adapter

You will likely see after a long time that the error count may sometimes increment as well as the app can sometimes detect this

no no is not a chinese clone.
is the original by OBDLINK SCANTOOL. Bought directly in USA from the producer

Hi

If it’s a oblink then it’s very unlikely to be corrupt data. This can only be one of two things:

* The app is corrupting the data (if this was happning though, it would happen for all the displays)

* The sensor is genuinely sending those values out, or the ECU, or the OBDLink.

To know further I’d need a debug sent immeiately after that happens. Because teh OBDLink is quick you’ll need to pull the adapter out *immediately* after you see the display glitch like that (so avoid the issue scrolling off the debug logs) and then send me a debug log (with your forum name)

I’ll look at the datastream to see what’s up. I suspect that if your OBDLink is functioning properly that it’s possibly the sensor. seeing the debug will let us know if that’s the case or not

If you can do this with 1.8.88 or version 1.8.89 that’d be great!

No problem – here’s what to do:

Start the app, go into the ‘General settings’, tick ‘Enable debugging’ (at the bottom of the screen)

Then quit and restart the app. It will now be in debugging mode.

Connect and wait for the oil sensor to flash the incorrect value. As soon as it does that, disconnect the adapter (literally pull it out quickly)

Then press the ‘gear/menu’ icon, and from the menu select ‘Send debug logs’ (may take a moment before it pops up the next window)

In the next window put your forum name and then press send. Wait for the ‘sent ok’ message, and then I’ll have a look at the debug here and see what’s going on

Hi! Thanks

Found the issue – here’s what the adapter has sent to the app:

1460795903838 {-- 2101
1460795903849 --}  01F
1460795903849 --} +0:610150003D03
1460795903849 --} +1:48293A3962801D
1460795903849 --} +2:A83501AC0E2B54
1460795903849 --} +3:2E2D086A`A05AD09
1460795903854 --} +4:B5315276000000

The correct response should be:

1460795903910 {-- 2101
1460795903914 --}  01F
1460795903914 --} +0:610150003D03
1460795903917 --} +1:4A293A3962801D
1460795903917 --} +2:BA3501AC0D2B54
1460795903918 --} +3:2E2D086A05AD09
1460795903920 --} +4:B5312276000000

There’s a ` in there which should not be present. It plain should not be there (should only be numbers). At this point in time this would likely be an adapter issue – it may be worth contacting scantool and seeing if there is a firmware update available (specifically one that may relate to this issue)

Unfortunately as this is bad data coming out of the adapter, there’s not much I can do in the app to fix it (as the data is corrupt, from the adapter itself)

checked on my OBDLink LX all your PID 2101 (AC-40) works stably

ok.
I confirm you that other pids work perfectly.
I copied the important parts of this discussion in scantool forum. I wait the answer and I’ll keep you in touch.

concerning the firmware…
in the site seems that last firmware versione is 3.3.0.
mine is 3.4.4.
I do not understand how is possible..

firmware updated succesfully.
the problem persists and is identic

Looks like a whole byte extra A’