[Ovmsdev] DTC code reading

[Michael Balzer]

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

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
> 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/20210620/b0a4eaec/attachment.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/20210620/b0a4eaec/attachment.sig>