Is it only for benz?

[CCXia1997]

It seems error when use pdx of volkswagen.

[kayoub5]

what's the error you are getting?

[andlaus]

odxtools is most definitely not only for Mercedes cars. That said, I obviously do not have access to diagnostics files made by/for other manufacturers and as @kayoub5 said, we're thus reliant on bug reports/patches from our users. In this case, it is likely that the issue can be fixed if you provided a traceback. also, there is a chance that your files will load if you enable the non-strict mode (in this case your mileage will vary, though).

[Ch4rg3r]

Is it possible that the specification is different? It seems that odxtools is based on version 2.2 and 2.0.1 for example is not fully supported?

[CCXia1997]

what's the error you are getting? @kayoub5 Version is 2.0.1 and error when use odxtools.load_odx_d_file() to resolve PROTOCOL file: KeyError: "ODXLINK reference OdxLinkRef('ES_XXX') could not be resolved for any of the document fragments [OdxDocFragment(doc_name='ES_XXX', doc_type='LAYER')]" ES_XXX is ECU-SHARED-DATA file and PROTOCOL file fragment is: `

`

[andlaus]

Is it possible that the specification is different? It seems that odxtools is based on version 2.2 and 2.0.1 for example is not fully supported?

yes, that's possible: we target odx 2.2, and odx 2.0 is only supported on a "best effort" basis, i.e., we happily accept patches provided that they do not break support for odx 2.2, but I personally do not have any datasets which use this version, so your mileage may vary.

KeyError: "ODXLINK reference OdxLinkRef('ES_XXX') could not be resolved [...]

that does not look like it is related to the ODX version, though. it might be a bug in odxtools (IMPORT-REFs are largely untested), or your datasset might be broken. to test whether the latter is the case, unzip the PDX file (unzip MY_FILE.pdx), grep for ID="ES_XXX" and check whether the short name of that diagnostic layer matches the DOCREF attribute of the IMPORT-REF.

[andlaus]

@CCXia1997: can this issue be closed? If not, it would be great if you provided more information...

[marcodadamo]

explanation is clear

[andlaus]

if you do not provide a (redacted if necessary) traceback or a file exhibiting the issue, we do not stand much of a chance of fixing this...