Pages: [1]
Author Topic: OLS to XDF Converter with Translator  (Read 533 times)
blairdude
Jr. Member
**

Karma: +6/-0
Offline Offline

Posts: 41


« on: June 02, 2026, 11:00:20 AM »

I have been working on an OLS to XDF converter lately to make it much easier to utilize DAMOS files without paying for WinOLS.  This supports A2L, OLS, KP, and HEX file formats, and includes binary extraction from OLS and HEX files as well, and translation of parameter names and descriptions.  As I've been mostly working with EDC16 and 6HP files, this is mostly what I've tested it on.  There are very likely still bugs, use at your own risk.

Windows EXE and Python source code are available below:
https://bbear3d.ca/misc-projects/ols-to-xdf-converter/
Logged
grayjay
Full Member
***

Karma: +4/-4
Offline Offline

Posts: 56


« Reply #1 on: June 03, 2026, 09:41:35 AM »

Great effort, this should be really helpful for generating .xdf for more obscure ECUs. I ran it on a TT ME7.1 file and it produced a huge list of scalar parameters that seem reasonably valid but relatively few tables and even fewer of those key tables that would be needed for actual tuning. I am not sure if this is due to the .kp I used or if the converter just did not find typical tuning tables. 
The converter ran fine from the .exe file first time I tried, then next time it gave an error something like "cannot find OLS_to_KP.py" . Deleting the .json settings file it had created fixed to allow it to run again.

Description translations were helpful. One feature request/suggestion is that it would be great if resulting .xdf parameter descriptions included option to have the FR abbreviation code (example KFLDIMX) instead of just the longer text descriptions, it would be easier to match parameters to FR and nefmoto discussion if the abbreviation code were included.
Thanks!
Logged
blairdude
Jr. Member
**

Karma: +6/-0
Offline Offline

Posts: 41


« Reply #2 on: June 03, 2026, 03:05:16 PM »

Great effort, this should be really helpful for generating .xdf for more obscure ECUs. I ran it on a TT ME7.1 file and it produced a huge list of scalar parameters that seem reasonably valid but relatively few tables and even fewer of those key tables that would be needed for actual tuning. I am not sure if this is due to the .kp I used or if the converter just did not find typical tuning tables. 
The converter ran fine from the .exe file first time I tried, then next time it gave an error something like "cannot find OLS_to_KP.py" . Deleting the .json settings file it had created fixed to allow it to run again.

Description translations were helpful. One feature request/suggestion is that it would be great if resulting .xdf parameter descriptions included option to have the FR abbreviation code (example KFLDIMX) instead of just the longer text descriptions, it would be easier to match parameters to FR and nefmoto discussion if the abbreviation code were included.
Thanks!

Can you please PM me the .kp file you're using?  When using an OLS or A2L file it should automatically be placing names like KFLDIMX in the parameter description, I'll need your KP file to find out why it's not finding those names.  If it's not finding the tables you're looking for, I'm inclined to say they are just not present in the KP file you're using.  It's not designed at all to find maps in the binary that are not defined already in the definition file.  TunerPro does allow sorting parameters by parameter type in addition to category placement, sorting by parameter type should easily locate all of the tables that were defined in the KP.  I'll look into and try to fix the 'Cannot find' bug.  Thanks for the feedback!
Logged
grayjay
Full Member
***

Karma: +4/-4
Offline Offline

Posts: 56


« Reply #3 on: June 03, 2026, 09:44:59 PM »

The ols file I tried converting as test was; Audi TT 1.8T BAM 225 PS 8N0 906 018 CB.ols from first post of thread
http://nefariousmotorsports.com/forum/index.php?topic=467.0

I also tried converting Audi TT 1.8T ARY 180 PS 8N0 906 018 BR 0261206439.ols from same post, got similar xdf result

Later in same thread indicated that these ols might be from "fully defined" pre-production calibrator files so perhaps that is why they are missing some of the typical tables?

I do see that the FR codes are included within the more detailed parameter description, It would just be nice to have those FR codes available to be populated as the title of the table or scaler parameter, rather than just available within the deeper parameter description.   
Logged
blairdude
Jr. Member
**

Karma: +6/-0
Offline Offline

Posts: 41


« Reply #4 on: June 03, 2026, 10:06:47 PM »

The ols file I tried converting as test was; Audi TT 1.8T BAM 225 PS 8N0 906 018 CB.ols from first post of thread
http://nefariousmotorsports.com/forum/index.php?topic=467.0

I also tried converting Audi TT 1.8T ARY 180 PS 8N0 906 018 BR 0261206439.ols from same post, got similar xdf result

Later in same thread indicated that these ols might be from "fully defined" pre-production calibrator files so perhaps that is why they are missing some of the typical tables?

I do see that the FR codes are included within the more detailed parameter description, It would just be nice to have those FR codes available to be populated as the title of the table or scaler parameter, rather than just available within the deeper parameter description.   


The OLS file converts well for me.  If you want the FR code as the parameter name, select the option 'Use OLS/A2L/KP Name as XDF Title'.  I have that off by default because the descriptors are what WinOLS uses as the parameter name by default, and the TunerPro Parameter Finder (under the Tools menu) can't search by parameter name anyway, but can search for words in the parameter description (which makes it a lot easier to find a parameter if you know its name).

EDIT:  I loaded the OLS in WinOLS and it does indeed look like many parameters and Folder names are getting missed.  Working on fixing it tonight.
« Last Edit: June 03, 2026, 10:35:43 PM by blairdude » Logged
blairdude
Jr. Member
**

Karma: +6/-0
Offline Offline

Posts: 41


« Reply #5 on: Today at 12:32:54 AM »

I am close to a clean conversion on that Audi TT OLS.  Hopefully just a few more days before I release an update.
Logged
Pages: [1]
  Print  
 
Jump to:  

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