N
nemiro
New member
- Joined
- 05.09.2023
- Messages
- 28
- Solutions
- 2
- Reaction score
- 21
I have a problem with coding and flashing modules of ME 9.7 AMG. I have tried many combinations of hardware and software. First I will describe the problem and then the steps I took to fix it. I am trying to perform a coding or flashing operation with Vediamo 4 (AutoGMT version) or Vediamo 5 (AutoGMT version) and I get this error:
This would mean that the ECU is not unlocked. I have tried various variations of DJ_Zugriffsberechtigung, getting the answer "Result: 0", which is what we are looking for. I have tried this with four different ECU modules. Two normal ME97AMG modules (2MB) and two 66 MHz ME97AMG modules (4MB). I have tried direct connection to the ECU on the bench and in cars (via ZGW etc.), always the same results.
Going to DAS (via Xentry or DAS Standalone) results in "Communication Error" dialogs, which also indicate a locked ECU. DTS Monaco returns NRC=22, NRC=44 or NRC=88, depending on which unlock commands were issued previously.
I also tried this on three different laptops, with the software running natively and in virtual machines. No difference. Always the same error.
As for the hardware to connect to, I have already tried C4, Tactrix Openport and SM2Pro. Again, all give the same error.
Finally, a very knowledgeable person connected to my computer, tried it and got the same result.
This makes me think:
All other functions work fine. I can interact with modules. Virginize them via VVDI, and then teach in drive authorization. Reading actual values, performing adaptation reset, camshaft teach in, etc. I just can't flash or code these.
I have read many times that ME 9.7 is a "seedless" ECU. There are seed key options in the menu, but I couldn't get any of them to work. Surely someone has encountered this and knows what to do? Please help!
![full full](https://autogmt.com/data/attachments/1/1216-0e26057355a082bc5216eae89197a052-full.webp)
This would mean that the ECU is not unlocked. I have tried various variations of DJ_Zugriffsberechtigung, getting the answer "Result: 0", which is what we are looking for. I have tried this with four different ECU modules. Two normal ME97AMG modules (2MB) and two 66 MHz ME97AMG modules (4MB). I have tried direct connection to the ECU on the bench and in cars (via ZGW etc.), always the same results.
Going to DAS (via Xentry or DAS Standalone) results in "Communication Error" dialogs, which also indicate a locked ECU. DTS Monaco returns NRC=22, NRC=44 or NRC=88, depending on which unlock commands were issued previously.
I also tried this on three different laptops, with the software running natively and in virtual machines. No difference. Always the same error.
As for the hardware to connect to, I have already tried C4, Tactrix Openport and SM2Pro. Again, all give the same error.
Finally, a very knowledgeable person connected to my computer, tried it and got the same result.
This makes me think:
- Most likely the problem is not with the hardware or the PC, as many combinations give the same result
- This is not necessarily a software issue as DTS Monaco, Xentry, DAS and Vediamo do not work
- It is unlikely that the problem is related to the hardware or firmware of the ECU, since I have four of them (all of which control the engines of the cars they are installed in)
- There are some procedures that I skip or do incorrectly
All other functions work fine. I can interact with modules. Virginize them via VVDI, and then teach in drive authorization. Reading actual values, performing adaptation reset, camshaft teach in, etc. I just can't flash or code these.
I have read many times that ME 9.7 is a "seedless" ECU. There are seed key options in the menu, but I couldn't get any of them to work. Surely someone has encountered this and knows what to do? Please help!