Pages: 1 [2]
Author Topic: ODIS/MCD project explorer (.db .key file parser)  (Read 4705 times)
jcsbanks
Full Member
***

Karma: +20/-3
Offline Offline

Posts: 169


« Reply #15 on: August 28, 2025, 01:57:28 PM »

I did a check for conflicts with an individual ECU file and nothing that is in it is missing in 0.0.0@BL_ECMDFCC.sd.c and the descriptions are functionally identical. Some of the PCBU codes are different but the descriptions are functionally the same, so am going to keep one master file for the ECUs on that platform for now.

For an example individual ECU file, there are 899 common entries, 83 with conflicts in the given PCBU code, and 20384 DTCs only present in 0.0.0@BL_ECMDFCC.sd.c
« Last Edit: August 28, 2025, 01:59:19 PM by jcsbanks » Logged
kartoffelpflanze
Newbie
*

Karma: +5/-0
Offline Offline

Posts: 20



« Reply #16 on: August 28, 2025, 08:51:31 PM »

I prepared my UDS emulator with F19E=EV_ECM18TFS0204G0906264 and F1A2=001000 and configured the response for service 0x19 to send DTCs 14823, 14827, 23147, 14828. Out of them, 23147 is only defined in BL_ECMDFCC and the other 3 are defined for the ECU-VARIANT I mentioned.

I loaded AU57X in VW-MCD Client, selected LL_EnginContrModul1UDS, started communication and went to FAULTREAD. This was the output:


As expected, since the BASE-VARIANT does not have any DTCs defined.

Then, I did variant identification and selection to select the ECU-VARIANT. This was the output of FAULTREAD:


Clearly, the DTC which is defined in BL_ECMDFCC but not in the ECU-VARIANT (3rd one) is not supported (exactly as I expected).



Unrelated note: in VCDS I always noticed DTC descriptions in which 2 words were concatenated towards the middle, such as "Invalid Data Received FromAnti-Lock Brake System Control Module". I just realized it's because there is a newline between them and it's being discarded Grin VW-MCD Client makes the same mistake.
Logged
jcsbanks
Full Member
***

Karma: +20/-3
Offline Offline

Posts: 169


« Reply #17 on: August 29, 2025, 12:21:47 AM »

Thanks, so this suggests if I want to make a unified list for one engine type it would be 20 times smaller if I combined all the individual ECU files rather than use the “big” one. I only did that initially due to Java/jpype problems making the individual ECU files, so would be worth me redoing. It does look like you have all the required data for DTCs in the individual files.
Logged
kartoffelpflanze
Newbie
*

Karma: +5/-0
Offline Offline

Posts: 20



« Reply #18 on: August 29, 2025, 12:55:08 AM »

Something that might help for grouping files is the description provided for every file generated by dumpECUVariantPatterns. Here is the description of GV_ECM30BTD011AU57X_210:
Code:
<p>@@failureclass("1","KD-Fehler (NICHT OBD-relevant) ( mit Priorität 2 "Fehler" für KD-Tester ) [nur KD]","no")</p>
<p>@@failureclass("3","OBD-relevante Fehler (mit Priorität "Fehler" für KD-Tester) [MIL]","yes")</p>
<p>@@failureclass("2","KD-EGAS-Fehler (NICHT OBD-relevant) [KD + SYS/EPCL]","no")</p>
<p>@@failureclass("11","KD-Fehler (NICHT OBD-relevant) ( mit Priorität 6 "Hinweis" für KD-Tester ) [KD Hinweis]","no")</p>
<p>@@failureclass("4","OBD-relevante EGAS-Fehler [MIL + SYS/EPCL]","yes")</p>
<p>@@failureclass("17","MIL und EPCL sofort an (z.B. P-Mode, Deaktivierung Katheizen in der Produktion) [MIL + EPCL]","yes")</p>
<p>@@failureclass("14","OBD-relevante EGAS-Fehler (mit MIL on im 1. DCY) [MIL + SYS/EPCL]","yes")</p>
<p>@@failureclass("7","OBD-relevante Fehler Misfire Monitoring (Otto und Diesel) [MIL + Otto zus. blinkende MIL]","yes")</p>
<p>@@failureclass("13","OBD-relevante Fehler (mit MIL on im 1. DCY) [MIL]","yes")</p>
<p>@@failureclass("5","OBD-relevante Fehler Fuel System Monitoring (Otto und Diesel) [MIL]","yes")</p>
<p>@@failureclass("6","OBD-relevante EGAS-Fehler Fuel System Monitoring (Diesel) [ MIL + SYS/EPCL]","yes")</p>
<p>@@failureclass("9","OBD-relevante Fehler mit schnellem Löschen des Fehlers wie PendingFaultCode [MIL]","yes")</p>
<p>@@failureclass("18","Grobleck-Fehler / Offener Tankdeckel (Tankleckdiagnose) [MIL]","yes")</p>
<p>@@exchange-xml("bosch_exchange_002042.xml")</p>
<p>@@program_version("C1249CDGC")</p>
<p>@@dataset("10SW079892_Logistic_Data.DCM")</p>
<p>@@odx-basispaket("ECM_ODX-Basispaket_KW48_2020.pdx")</p>
<p>@@basevariant("BV_EnginContrModul1UDS_002110.odx")</p>
<p>@@xv("XV_ECMMEDC1710_016040_20.odx")</p>
<p>@@mappinglist("ECM_Bosch_Signal-Mappingliste_V3.0.16a.xml")</p>
<p>@@used_norms(VW80114="",VW80124="",VW80125="4.0",VW80126="",VW80127="")</p>
<p>@@measurement-library(null)</p>
<p>@@ecu_type("EDC17CP44-3.3 neues Speicherlayout C7 PA W37 MJ15")</p>
<p>@@project_description("SW für 4G0 907 589 F")</p>
<p>@@transmission_variant("AL551-8Q")</p>
<p>@@engine_code_letters("CVUA")</p>
<p>@@engine_power("235")</p>
<p>@@modelyear("2015")</p>
<p>@@emission_standard("EU6 plus (+7MM)")</p>

Also, I don't know very much about this, but it seems like variants starting with "GV_" are more of a top-level. I know EV means ECU-VARIANT but no clue about GV, maybe someone can help.
Logged
jcsbanks
Full Member
***

Karma: +20/-3
Offline Offline

Posts: 169


« Reply #19 on: August 29, 2025, 04:27:06 AM »

Think I have a 11KB gzipped unified list that covers the 2.5T, 4.0T and 5.2 our users need. I picked the longest of translated descriptions and they were functionally identical across all versions and engines, and just show the multiple P codes they are listed under.
Logged
jcsbanks
Full Member
***

Karma: +20/-3
Offline Offline

Posts: 169


« Reply #20 on: August 29, 2025, 04:45:36 AM »

Is there a donation link I can include for users to show their appreciation?
Logged
kartoffelpflanze
Newbie
*

Karma: +5/-0
Offline Offline

Posts: 20



« Reply #21 on: August 29, 2025, 08:09:34 AM »

I'm flattered you think anyone would pay for a pretty much completed open source project Shocked
Logged
Pages: 1 [2]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.187 seconds with 15 queries. (Pretty URLs adds 0s, 0q)