Diagnostics and variant coding for VS30+ using Xentry and DTS Monaco - v2.0

[hildeevo]

My mate bought OEM LED taillights, is it possible to code them, since the connector has the same pin layout?
He has halogen rears from the factory.

My sprinter has LED lights from factory so i could copy settings from my files, but i don't know what computers and which code to modify.

Thanks for the help!

View attachment 379771

I assume that the pining is still the same. I try to find the line in Monaco where you must coding the different power consumption. I think you've changed the properties from bulbs to LED in SL (Schlusslicht/Rearlights) and Brakelights. All other lamps are with normal bulbs in both type of rearlights.

Regards Chris

 

[Selter]

I assume that the pining is still the same. I try to find the line in Monaco where you must coding the different power consumption. I think you've changed the properties from bulbs to LED in SL (Schlusslicht/Rearlights) and Brakelights. All other lamps are with normal bulbs in both type of rearlights.

Regards Chris

I see, i found the bulb option in DTS. Now i need to figure out which lines of code to change the voltages.

My mate has halogen right now, and my sprinter has factory LED so i will probably copy most of the “[014] OLC VC Bremslicht Write” to his van.

 

[hildeevo]

I see, i found the bulb option in DTS. Now i need to figure out which lines of code to change the voltages.

My mate has halogen right now, and my sprinter has factory LED so i will probably copy most of the “[014] OLC VC Bremslicht Write” to his van.

I didn't understand why you don't look in your coding to find the different conding between your cars?! I think you've to set the coding to "LED" [1]

Cheers Chris

P.S. There is a option in DTS to check what's the difference between your's and your mate's coding. It shows the different coding in coloured caracters. But I don't know exactly how to check this. Maybe ther is a member who can explain the steps for this workaround?

 

[jmfangio]

Attached a Poc from the actual coding.

Sorry, I think it was a bit unclear from my side:

These are two other codings, which could be relevant (but I‘m not sure):

• BCMFA2
  • [013] OLC VC Blinker Write
    • PLSM_T_FRA_SML_aus > „which value is displayed?“
    • PLSM_T_FRA_SML_an > „which value is displayed?“

 

[hildeevo]

Sorry, I think it was a bit unclear from my side:

These are two other codings, which could be relevant (but I‘m not sure):

• BCMFA2
  • [013] OLC VC Blinker Write
    • PLSM_T_FRA_SML_aus > „which value is displayed?“
    • PLSM_T_FRA_SML_an > „which value is displayed?“

In both lines stands [0.01].
This is correct in my understanding.
It's the delay time in seconds for switch off and on.

Chris

 

[KrellyKryl]

Add an option to start a manual DPF regeneration cycle
This will allow you to add the option to start a DPF regeneration cycle in the DPF menu. Note, DPF levels need to be >50%, the van stationary (to start the cycle - you can drive once started), RPM slightly above idle (hold the gas pedal down slightly), and coolant at temp. The first time I did this, the van turned itself off, I turned it back on and the regeneration was active.

• IC907
  • [099] VAN_Variant_Coding Write
    • Regbox > Manual Regeneration in Standing Vehicle

 

[Ivan Borisovich]

@KrellyKryl can you post the coding from the FSCM Gen5 of your van? Looks like J51 is activated from this module by choosing a different tank variant. See coding below.


No J51





J51 Present

 

[KrellyKryl]

@Ivan Borisovich, you, that's what I'm seeing (and my van has J51):

 

[MMtinker]

I wonder if there is anything we need to change on cpc_ng ecu as well...

 

[Selter]

I ordered a new climate control unit with the button for the HH4 option (automatic climate control). Upgrade to the HH9.

Could someone help me out finding the right coding to activate this button? Which module do i access?

Thanks in advance!

Update:
Button is working, but when i press the “auto” button the fans turn silent. Any suggestions?

 

[MMtinker]

@Ivan Borisovich, you, that's what I'm seeing (and my van has J51):View attachment 381146

Wonder why is it Otto and not Diesel option? Is yours gasoline?

 

[KrellyKryl]

Wonder why is it Otto and not Diesel option? Is yours gasoline?

I assume, German logic (mine's the standard 3.0 V6 Diesel).

 

[bobbertoni]

Has anyone had luck coding on a 2024 907? I bought a version of Monaco 9 off eBay, but when I create a new workspace and select my project I get a “Warning: todo”. I was wondering if Monaco 8 would let me do the Lane Keep Assist and Crosswind Assist changes or if I need to keep looking for a working version of 9 since my van is newer.

 

[Ivan Borisovich]

Has anyone had luck coding on a 2024 907? I bought a version of Monaco 9 off eBay, but when I create a new workspace and select my project I get a “Warning: todo”. I was wondering if Monaco 8 would let me do the Lane Keep Assist and Crosswind Assist changes or if I need to keep looking for a working version of 9 since my van is newer.

DTS Monaco 9.02 does not read and recognize newer versions of smrd files. Use an older (2023) database of smrd files or use DTS Monaco 8.16 with a license to code with newer smrd files. ... Newer doesn't always equal "better"!

 

[anli]

Thank you KrellyKrell and Ivan for the good work! I'm searching for the codings for:
- Start/Stop deactivation or last mode
- Deactivate the acknowledge of locking by turn lights and deactivate coming/leaving home
- Programming the PSM (found the manual at https://sprinter-source.com/forums/index.php?threads/134461/)
It would be great if anybody could guide me to the right codings. Thanks a lot for your help!
Best, André

 

[bobbertoni]

Thank you Ivan and KrellyKrell for all of your resources and answers here. They've helped me so much and I'm getting very close to disabling my Lane Keep Assist. I switched to Monaco 8.16 and it's able to recognize most of my newer smrd files (some of them it complains of being corrupted). I was able to change all of the values I needed for the Variant Coding, but when I got to the step to search for and select “[31] Synchronize to Non-volatile Memory Start” it's not in my list of options. Any suggestions why it wouldn't appear for my 2024 907?

Here's me scrolling through the list of options available when I search [31]: https://www.youtube.com/shorts/ixrlC0vFSy0

And here's a screenshot of what I'm seeing:

 

[Ivan Borisovich]

It looks like you have no communication with the MMPC module. How did you import the database of the smrd files?

 

[bobbertoni]

@Ivan Borisovich, I appreciate you taking a look and helping me debug! That screenshot was taken after I disconnected. I've taken a new screenshot while being connected in case that helps. I imported the SMRD files from 2025.03 Xentry. Looks like MMPC213 is from 2021 in that database. I found another version from 2020 and it had the same issue where Asynchronous Routines doesn't display. I'm using the MBCar_MBVan_SMR_DiagnosticCAN_V_02_05 template for my workspace.

To debug, I connected to a few other modules (HU6 and IC907) and I verified Asynchronous Routines appears for both. I even successfully coded the Fader in HU6 so at least I've been able to make some progress! Now to just figure out what to do to get that Asynchronous Routines option to appear for MMPC.

 

[bobbertoni]

i re-read @KrellyKryl’s instructions and realized that MMPC doesn’t require asynchronous routines and I can skip that step. Sorry to be a bother!

Again, thank you all for the help here. A massive amount of knowledge that’s helped me immensely.

 

[jdubbayew]

Thanks to everyone for this thread!

Has anyone done the coding for re-gear of the rear axle? Going from 3.92 to a 4.18 rear axle.

The best info I found is here: https://sprinter-source.com/forums/index.php?threads/76625/