[Ovmsdev] DTC code reading

Michael Balzer dexter at expeedo.de
Mon Jun 21 16:14:09 HKT 2021 

Tamás,

your interpretation is correct. The DTC status byte e0 also decodes to…

     warningIndicatorRequested + testNotCompletedThisOperationCycle + 
testFailedSinceLastClear

…and lacks confirmedDTC, so the fault condition did not occur often 
enough to be stored in long term memory.

I would assume 1801ff00 returns all DTC codes supported by the ECU, 
which are 0xdf = 223 codes of 3 bytes each (containing d1 13 e0).

All other DTCs seem to have status 00, so only this DTC occured since 
the last clear.

> OVMS#obd can1 request device 751 752 1802ff00
> 751[752] 1802ff: ERROR: request failed with response error code 12 
> subFunctionNotSupported

You should try some further subfunctions, 02 returning 
subFunctionNotSupported doesn't mean all higher ones are unsupported as 
well. Best would be a loop through all 256 to be sure. That's pretty 
simple using the new Duktape binding:

(function(){

   var cmd = new Uint8Array([0x18, 0x00]);
   var req = { txid: 0x751, rxid: 0x752, request: cmd };
   var res, subfn;

   for (subfn = 0; subfn <= 255; subfn++) {
     cmd[1] = subfn;
     res = OvmsVehicle.ObdRequest(req);
     if (res.error != 0x12)
       print(subfn.toString(16) + ": " + res.errordesc + 
res.response_hex + "\n");
   }

})()

Whereever you get something else than code 12 subFunctionNotSupported is 
worth investigating with parameters.

Some ECUs store snapshots or extended records for DTCs, see the UDS 
command scheme for 19 -- maybe something similar can be found here using 
command 18.

> This is clear of dtc codes?
>
> 1624253725.617633 1R11 751 03 14 ff 00 00 00 00 00
> 1624253725.618253 1R11 752 03 54 ff 00 13 e0 00 8e

Yes, 14ff00, the response is an ACK/OK to that.

Regards,
Michael


Am 21.06.21 um 08:41 schrieb Tamás Kovács:
> Now i create a new log file without dropped frame, with filter.
> https://drive.google.com/file/d/1o477jmllYyntpmLJca_3aTmL2NvYZfsZ/view?usp=sharing 
> <https://drive.google.com/file/d/1o477jmllYyntpmLJca_3aTmL2NvYZfsZ/view?usp=sharing>
>
> Only active error code is U1113.
>
> This is a U1113 Error?
> 1624253728.207555 1R11 751 04 18 00 ff 00 00 00 00
> 1624253728.213037 1R11 752 05 58 01 d1 13 e0 00 8e
>
> OVMS#obd can1 request device 751 752 1800ff00
> 751[752] 1800ff00: Response: 01 d1 13 e0         | ....
> if i decode this
> d1 = 11010001
> bit 6-7 = 11 -» U
> bit 4-5 = 01 -» 1
> bit 0-3 = 0001 -» 1
>  so the error code is: U1113
>
> OVMS#  obd can1 request device 751 752 1801ff00
> 751[752] 1801ff00: Response:
> df 05 62 00 00 b4 00 00 b3 00 21 23 00 21 22 00 | ..b.......!#.!".
> 1a 00 00 21 28 00 21 27 00 1a 01 00 21 38 00 05 | ...!(.!'....!8..
> 58 00 05 57 00 1b 31 00 1a f0 00 1b 19 00 1b 1a | X..W..1.........
> 00 1b 1b 00 28 05 00 07 05 00 1a 02 00 1a 03 00 | ....(...........
> 1a 04 00 1a 2c 00 1a 06 00 1a 07 00 1a 08 00 1a | ....,...........
> 09 00 1a 0a 00 1a 0b 00 1a 0c 00 1a 0d 00 1a 0e | ................
> 00 1a 0f 00 0c 73 00 0c 74 00 0a 05 00 1b 2b 00 | .....s..t.....+.
> 06 91 00 06 92 00 06 93 00 06 94 00 0a 01 00 1a | ................
> 10 00 1a 11 00 1a 12 00 06 46 00 06 47 00 d8 01 | .........F..G...
> 00 d8 02 00 d8 03 00 d8 04 00 d8 05 00 d8 06 00 | ................
> 1a 14 00 1b 0a 00 0a e6 00 0a e7 00 0a e2 00 0a | ................
> db 00 0a a1 00 0a df 00 0a a4 00 0a 0a 00 1a 15 | ................
> 00 1a 16 00 1a 17 00 0a 09 00 0a 10 00 1b 29 00 | ..............).
> 1b 2a 00 1a 18 00 1a 19 00 06 0b 00 06 05 00 06 | .*..............
> 04 00 06 0c 00 16 02 00 06 2f 00 d1 90 00 d0 73 | ........./.....s
> 00 1b 09 00 d1 1b 00 d1 1c 00 d1 1d 00 d1 10 00 | ................
> d1 02 00 d1 04 00 1b 35 00 d1 08 00 d1 09 00 d1 | .......5........
> 05 00 1b 36 00 d1 13 e0 d1 06 00 d1 6a 00 d1 6b | ...6........j..k
> 00 d9 10 00 d9 00 00 d9 11 00 d9 01 00 1a 1a 00 | ................
> 1a f1 00 1a f2 00 1a f3 00 05 60 00 1a 1b 00 1a | ..........`.....
> 1c 00 1a 22 00 1a 1e 00 d0 80 00 d1 60 00 d9 20 | ..."........`..
> 00 0a ba 00 1a 1f 00 0a 2a 00 0a 3d 00 0a ed 00 | ........*..=....
> 0a 51 00 1a 20 00 1a 21 00 1a 23 00 1a 24 00 1a | .Q.. ..!..#..$..
> 25 00 1a 26 00 1a 27 00 1a 28 00 1a 29 00 1a 2a | %..&..'..(..)..*
> 00 0a 90 00 0a 78 00 1a 2b 00 1a 3d 00 1a 3e 00 | .....x..+..=..>.
> 1a 3f 00 1b 1c 00 1b 1d 00 0a bf 00 1a 44 00 1a | .?...........D..
> 45 00 1a 2d 00 1a 2e 00 1a 2f 00 1a 30 00 1a 31 | E..-...../..0..1
> 00 1a 32 00 1b 33 00 1a 33 00 1a 34 00 1b 34 00 | ..2..3..3..4..4.
> 1a 35 00 1a e6 00 d0 81 00 d1 61 00 d0 90 00 1a | .5........a.....
> 38 00 d9 21 00 d9 24 00 1a f4 00 1a f5 00 1a 39 | 8..!..$........9
> 00 1b 1e 00 1b 1f 00 1a c5 00 1b 2f 00 1b 21 00 | .........../..!.
> 1a f6 00 1a f7 00 1a f8 00 1a f9 00 1a fa 00 1a | ................
> fb 00 1a fc 00 1a fd 00 1a fe 00 1a ff 00 1b 00 | ................
> 00 1b 01 00 1b 02 00 1b 03 00 1b 04 00 1b 05 00 | ................
> 1b 06 00 1b 07 00 1b 08 00 1b 0c 00 1b 0d 00 1b | ................
> 0b 00 1b 22 00 1b 23 00 1b 24 00 1b 25 00 1b 26 | ..."..#..$..%..&
> 00 1b 27 00 1b 28 00 1b 2c 00 1b 30 00 1b 2d 00 | ..'..(..,..0..-.
> 1b 32 00 d1 17 00 05 13 00 12 31 00 1b 37 00 91 | .2........1..7..
> 78 00 60 05 00 60 06 00 60 07 00 60 0a 00 60 0e | x.`..`..`..`..`.
> 00 60 0f 00 60 10 00 60 11 00 60 16 00 60 18 00 | .`..`..`..`..`..
> 60 19 00 60 1a 00 60 20 00 60 21 00 60 22 00 60 | `..`..` .`!.`".`
> 2a 00 60 2b 00 60 2c 00 60 2d 00 60 2e 00       | *.`+.`,.`-.`..
> OVMS#obd can1 request device 751 752 1802ff00
> 751[752] 1802ff: ERROR: request failed with response error code 12 
> subFunctionNotSupported
> This is clear of dtc codes?
>
> 1624253725.617633 1R11 751 03 14 ff 00 00 00 00 00
> 1624253725.618253 1R11 752 03 54 ff 00 13 e0 00 8e
>
> Michael Balzer <dexter at expeedo.de <mailto:dexter at expeedo.de>> ezt írta 
> (időpont: 2021. jún. 20., V, 13:54):
>
>     That log file is missing too many frames to be readable, and the
>     logger should have told you that.
>
>     Maybe your OVMS has an SD speed issue? Have you tried raising the
>     optimization hints?
>     https://docs.openvehicles.com/en/latest/crtd/can_logging.html#optimizing-the-performance
>     <https://docs.openvehicles.com/en/latest/crtd/can_logging.html#optimizing-the-performance>
>
>     Anyway, it seems your tool queries at least the four ECUs defined
>     in the source. It uses diag session 0x92 (i.e. request 1092), and
>     then request 1800ff00 to retrieve the DTCs.
>
>     18 is not a standard UDS command, but some VW ECUs (especially the
>     TP2.0 ones) also use this (but there it's 1802ff00).
>
>     You can try other subfunctions, i.e. 1801, 1802, etc. to see if
>     you get something else than "subfunction not supported".
>
>     To clear the DTCs, the tool seems to use the standard command 14,
>     but with non-standard parameters: the log has a request 14ff00 to
>     771 (but the response is missing).
>
>     Due to the missing frames, your DTCs are not readable in the log.
>     Try to get a log without dropped frames.
>
>     Regards,
>     Michael
>
>
>     Am 20.06.21 um 09:02 schrieb Tamás Kovács:
>>     a) a test with another two device
>>     b) nothing working
>>     c) if i use 19 Poll type and vehicle set to trio no response, if
>>     vehicle empty set get 80-error code
>>
>>     If i connect simultaneously another device can i capture the DTC
>>     code reading with ovms using a Y OBD cable?
>>
>>     My car always have a U1113 DTC error because not have a EV-REMOTE
>>     ECU. I have a log file created with ovms when i read and clean
>>     the dtc codes with hobdrive. Another error codes: P1A39 (BMU),
>>     P1A33 (BMU), P1A7E (CMU)
>>     Log file:
>>     https://drive.google.com/file/d/1zcIcMsBYLEoubafO1P6JW_GchZXI7WLD/view?usp=sharing
>>     <https://drive.google.com/file/d/1zcIcMsBYLEoubafO1P6JW_GchZXI7WLD/view?usp=sharing>
>>
>>     Michael Balzer <dexter at expeedo.de <mailto:dexter at expeedo.de>> ezt
>>     írta (időpont: 2021. jún. 19., Szo, 18:55):
>>
>>         Tamás,
>>
>>         a) are you sure the DTC is in device 761/762? There are three
>>         more devices in the i-MiEV source.
>>
>>         b) maybe you need to give another status mask, e.g. 1902ae or
>>         just all DTCs by 1902ff -- did you try that?
>>
>>         c) you can also try the other DTC retrieval subfunctions,
>>         e.g. 1901<mask> to get just the number of DTCs (see ISO spec
>>         for more)
>>
>>         Regards,
>>         Michael
>>
>>         Am 19.06.21 um 18:13 schrieb Tamás Kovács:
>>>         Hi!
>>>
>>>         I would like to create a dtc reading on i-miEV/ Peugeot iOn.
>>>         But if is send the following command:
>>>         OVMS#obd can1 request device 761 762 19020f
>>>         761[762] 19020f: request failed with response error code 80
>>>
>>>         I now use hobdrive app to read dtc code with OBDlink LX
>>>
>>
>>         -- 
>>         Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
>>         Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>>
>>         _______________________________________________
>>         OvmsDev mailing list
>>         OvmsDev at lists.openvehicles.com
>>         <mailto:OvmsDev at lists.openvehicles.com>
>>         http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>>         <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>>
>>
>>
>>     -- 
>>     Üdvözlettel:
>>     Kovács Tamás
>>
>>
>>     _______________________________________________
>>     OvmsDev mailing list
>>     OvmsDev at lists.openvehicles.com  <mailto:OvmsDev at lists.openvehicles.com>
>>     http://lists.openvehicles.com/mailman/listinfo/ovmsdev  <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>
>     -- 
>     Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
>     Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>
>     _______________________________________________
>     OvmsDev mailing list
>     OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>     http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>     <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>
>
>
> -- 
> Üdvözlettel:
> Kovács Tamás
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev

-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20210621/3da04bde/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 203 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20210621/3da04bde/attachment-0001.sig>

More information about the OvmsDev mailing list