W907 VMAX Speed Locked After Coding with DTS

  •  
  • Thread starterkang
  • Start date
K
kang
New member
Joined
29.09.2024
Messages
2
I have a problem with my 2019 MB Sprinter W907.

I used DTS Monaco to code the speed limit in the CPC_NG and CRD 3.2 modules. After coding the maximum speed of the van is 81 km/h, cruise control can also only be set to 81 km/h. Before I made these changes, there was no speed limit.

I have since reverted all coding back to original settings (161 km/h and AMG7 240 km/h), but the van still doesn't want to go faster than 81 km/h. Also, sometimes a code appears that I can delete but it comes back after a while: U010087, communication error indicating "the message is missing". This DTC was not present in the Xentry short test before I made any coding changes.

I have done this before on two 2021 vans with OM654 engines, but in those cases I only adjusted the CPC_NG. Those vans didn't have cruise control or MBUX. This time I thought it would be a good idea to also set VMAX in the CRD 3.2 ECU settings, and maybe that's where I went wrong.

The 2019 Sprinter W907 comes with cruise control and MBUX. I even tried copying the coding from another van with the same model and equipment, but there was no difference.

The problem persists even after reverting all changes. The van still can't go faster than 81 km/h.

Can anyone help?
What could have gone wrong and how can it be fixed?
 
Good evening, maybe my following experience will help you, I usually work like most of those serious programmers, only in the famous Vediamo. However, more or less the processes in Monaco are the same. I had a case at the beginning, when I usually coded only VMAX in the CRD ECU, I remember that I had to configure the channels to be able to communicate with Vediamo and the ECU in general, I configured the speed, and Vediamo wrote something, but also some error, I checked the module and thought that VMAX was set, however, when I restarted the system, the speed was, I think, 120 km/h.

Then I tried the following, at the top of my Vediamo above the symbol I have two options, they are for unlocking the ECU, I pressed those 2 commands there and then set the VMAX, but now I didn't take any more risks and installed it as it was at the original speed, no more, no less, I pressed download for coding, Vediamo downloaded the code and right after that I pressed at the top where those 2 commands were, the option "hardware reset" and when I checked again, the coding went as before. That's how I did it.
 
  • Like [+1]
Reactions:Baran79
I think there is some broken English in your post. I don't want to offend you, but I will try to help.
I believe this is what you mean.
In Vediamo you went to a security unlock function or something similar. Which now allows you to change the variant coding. Then you continued to change the VMAX as usual. "Configuring the channels" makes me think you are talking about changing the behavior of the VCI?

Anyway, this is where I don't understand your post. "I configured the speed (VMAX)". No more, no less. I pressed download (I assume you mean you told it to code the module). Then you reset the module, software or hardware, it doesn't matter which.

That being said, the 907 is a little different than the 906. You will probably have to do something in the EIS/EZS to change the data in the CDI module correctly.
However, people who are smarter than me can probably provide more information. I am still learning myself.
However, I am surprised that you decided to use Vediamo on 907.
Vediamo is an old engineering software, DTS is a newer one. Same as DAS vs. Xentry.
If I'm wrong about anything, please correct me, that's how we learn.
 
  • Like [+1]
Reactions:pascal0615
There is an identifier in the ESP907 module (20 0D) that controls the CC set speed limit. Can you post the data/coding string of that identifier here? You can run the command in DTS Monaco/ESP907 22 20 0D, post the answer here.
 
First of all, Vediamo is a Vector product, it is old, that is true, but at the time I shared it, we had scripts for it, we had a lot of stuff for it, it uses different files like VSB, VSX, CFF, CBF and of course also CBF from the latest Xentry files, because that is the only possible way to code new cars. DTS Monaco, as a barebones program without files from Softing, uses Vediamo files and the new CBF files from Xentry. It is a newer product, but there is nothing new in it except the appearance of the screen!

Most of us learned how to work with Vediamo almost 10 years ago, that's when various calculators like Seed Key, SKT and many others appeared, allowing you to customize these modules, and most of us, including me, still work with Vediamo. DTS is a newer product, but it is not new because it does not have its own files, it uses "Vediamo and Xentry CBF files". I hope you get the idea.

CBF files from Xentry require communication to be established. This requires configuring the CAN bus and baud rate until the connection is established. Once the connection is established, you can go to the settings and learn how to code in simulation mode. So don't say what you don't know, but on the other hand, want to know. And use the Seed Key calculator to adjust this VMAX.
 
I have had to deal with what the original poster state above twice on US version of the W907 sprinter with OM642 engines. There is glitch that happens during the coding of the CPC_NG module, where the identifier 20 0D in the ESP907 module is also modified and it has nothing to do with the seed key calculation. The last byte of the DID 20 0D has to be corrected manually in order to make it all work correctly.

picture
 
  • Like [+1]
Reactions:Peter5 and Mersovod

Similar threads

R
  • ronik
  • Cars and vans
2
Replies
11
Views
1K
Peter5
P
N
  • nenfret90
  • Cars and vans
Replies
3
Views
1K
nenfret90
N
G
  • GeorgeF
  • Cars and vans
Replies
3
Views
241
GeorgeF
G
Back
Top Bottom