DTCController

DTCController is a java application that allows to edit DTC (Diagnostic Trouble Codes) table. It supports only EDC16C34 PSA platforms at the moment. The program tries to find the addresses of the needed tables using the strategy described bellow. It will work only on PSA platform but can be extended to others vehicle. All contributions to this project are welcome.

It is mandatory to open an original dump (not necessary a full dump) to find addresses. Then, if you think the algorithm did a good job you can add your config to the list of know projects in the Dump.findDTCInfo() method. All projects share same addresses independently of the software number. The project is the identifier of the DaMOS (DAtabase for Microcontroller-Oriented Systems) A2L description file (ASAM-MCD-2MC) which contains characteristic addresses and descriptions.

How to use

• Download source code in a directory named DTCController or clone the repository using:

  git clone https://github.com/JeanLucPons/DTCController.git

• Install java JDK (either openJDK or OracleJDK)
• Execute in a command prompt or in a shell:

  cd [my_path]/DTCController
  javac *.java
  cd ..
  java DTCController.EDC16C34

  This will compile and execute the program, if you make modifcation of the source code, you need to recompile using javac.

You can also download the executable and precompiled jar file from releases and create a shorcut on it as below. Change the path to the JDK (or JRE) you are using:

Target: "C:\Program Files\jdk-18.0.1.1\bin\javaw.exe" -jar D:\Downloads\DTCController.jar

To disable a DTC, select disable in the class column (it disables the whole line). To disalbe only one DTC in the line, click on the Env button, and select "Sig unused" for the appropriate DTC. If you change settings of a DTC class, it will be applied to all DTC that belong to this class. The program outputs memory changes on the console.

About checksums

DTCController can correct the checksums when saving a file. You can also display some informations concerning checksums. It is possible, when you open an already modified file, that the 2 32bit checksums are not corresponding to the calculated ones due to wrong checksum calculation by other tools. This 2 32 bits checksums are likely not checked by the ECU. However, both MD5 and RSA signature are checked. In the RSA signature of an orig file, you find the signature date. If you have a correct MD5 and a RSA signature that contains a date (as below) then your file is likely an orig one.

How it works

The address search algorithm is quite simple, it assumes that the first code of the internal code table is P0530 (Address of DSM_CDKDfp_ACCDPresAna_C) and the last one is P1621 (Address of DSM_CDKDfp_WdCom_C). The algorithm can be found in Dump.findDTCInfo() method. When the A2L file is generated, fault characteristics are sorted in alphabetic order (case sensitive). It is unlikely that a fault characteristic is added before DSM_CDKDfp_ACCDPresAna_C or after DSM_CDKDfp_WdCom. However, it might fail. To check if the algorithm did a good job, check the correspondance of DTC internal code and Code #1,#2,#3 and #4. If they are coherent, then you can relie on the result. For instance, on the above example, you can see that P0530 is well related to P0532 and P0533 (Air Conditioning faults).

Note Even for a same engine, a same EDC16C34, DTC table may be different (size and/or content and/or addresses).

Here is an exemple with a known A2L file for a 206 1.6 HDI 110HP (Project C35374A).