New SMR-D Files 2024

[mbastucoding]

Is there a solution for SMR-D 2024 files? They don't work in DTS Monaco, 2023 files work but won't connect to 2024 vehicle.

 

[alexs3d2]

Since the 2024 files work in Xentry and only seem "corrupt" in DTS Monaco, and the 2023 files work fine in both Xentry and DTS Monaco, will there be any issues using the 2023 files when writing them back to the ECU?
Still trying to figure out how this works.

Depends on what you are trying to do, and as mbastucoding said, it also depends on the ECU variant. If the variant is supported by older files, it doesn't matter if you access it with 2023 in DTS and 2024 in Xentry. But if the ECU variant is too new for the DTS version and it can't detect the variant, some features may work and others may not.

Coding using the DTS template will not work, but if you code using the diagnostic functions and use the _dump version of the appropriate coding function, it might work. In this case, you'll need to enter the coding into a single hex string. But that's a bit like working in the dark.

 

[b0snaaaa]

As many of you have already noticed, SMR-D files from newer versions of Xentry are often corrupted or do not work with the current version of DTS Monaco. Is it possible to mix SMR-D files from different versions of Xentry? For example, can I use a CPC_NG 2023 file and a PARKMAN213 2024 file and HU6 2024 files on the same car?
I'm also trying to figure out how long it takes for SMR-D files to stop working properly.

 

[lordmetro]

This is what I'm doing now. I have a folder with the SMR-D mix, if you go to the file in DTS Monaco by default in offline mode, it will show for which versions of the control unit there are parameters in the list of variant codings. If the correct version of the control unit is SMR-D when coding, the tables will be correct and will produce the correct hex edits.

Luckily we have a pre-facelift W177 so I wouldn't worry, but that's a problem with new cars.