MSS54 DS2 Tool: FREE - DME tune, program, flash counter, codes, adaptions, etc

[Cubieman]

What might be reason(s) that the program will not read a partial of the DME yet is able to read error codes etc.?

I should have taken a photo, but I *think* after it didn't read the partial it said something similar to "5 attempts at reading, timed out".

[oceansize]

First things first, amazing tool, very cool. Encountered something today that I'm not sure if is a bug, or me doing something wrong.

In an attempt to flash the Euro tune like mentioned here, I went and grabbed the 211322001501JD34 program, and the 211322001501J424 tune. My understanding being that the crucial "1501" program being the same between the two was what mattered.

First I did a program and tune read through the DS2 tool to have a backup. When prompted to do a backup as part of the flash I thought "what the hell" and did that backup as well.

Program and tune flashed just fine, but then I had a "Warnings: ZIF Copies Mismatch" on the DME Info tab.

Thinking this was related to the different JD34 vs J424 configurations, I went ahead and flashed the original program and tune that I had previously pulled from the DME Read tab, however the "ZIF Copies Mismatch" message remained.

It wasn't until I went ahead and used the "Write this Program" and "Write this Tune" buttons from the backup made before the flash, that I was able to get rid of the "ZIF Copies Mismatch" warning.

Was I doing something wrong in trying to restore the program and tune that I had previously read? What does a "ZIF Copies Mismatch" actually mean?

There is a ZIF entry that tracks hardware and software variants on your car. There is a back up zif entry that is what it says. I believe the zif copies mismatch is referencing a mismatch between the main entry present in UIF versus the backup entry.

However, its inconsequential as to how the car performs. I noticed that in this post karter16 referenced a "misunderstanding" concerning the backup zifs persistence. I'm sure he can shed some more light.

[Pklauser]

First things first, amazing tool, very cool. Encountered something today that I'm not sure if is a bug, or me doing something wrong.

In an attempt to flash the Euro tune like mentioned here, I went and grabbed the 211322001501JD34 program, and the 211322001501J424 tune. My understanding being that the crucial "1501" program being the same between the two was what mattered.

First I did a program and tune read through the DS2 tool to have a backup. When prompted to do a backup as part of the flash I thought "what the hell" and did that backup as well.

Program and tune flashed just fine, but then I had a "Warnings: ZIF Copies Mismatch" on the DME Info tab.

Thinking this was related to the different JD34 vs J424 configurations, I went ahead and flashed the original program and tune that I had previously pulled from the DME Read tab, however the "ZIF Copies Mismatch" message remained.

It wasn't until I went ahead and used the "Write this Program" and "Write this Tune" buttons from the backup made before the flash, that I was able to get rid of the "ZIF Copies Mismatch" warning.

Was I doing something wrong in trying to restore the program and tune that I had previously read? What does a "ZIF Copies Mismatch" actually mean?

[davkav]

I don't login here often, but I had to today to tell you, you are an f'in legend.
Thanks for creating a great program and sharing it with the community!


Edit:🤣 just noticed this is my first ever post even though I am a member since 2022....

[0-60motorsports]

Quick update - the last couple of months for me have been family with back to back sicknesses, etc. plus starting a new contract at work so I haven't had enormous amounts of spare time. I did publish v1.2.2 today which is a very small change. Both George Hill and ac427 have shared logs with me that contain occasional failures directly after programming mode entry and baud rate elevation. It seems that the root cause is possibly not allowing enough time for the channel to settle after the rate change, so I've extended that waiting period to a more conservative value in the hopes of solving this. The failure occurs at a non-critical point in the various workflows, so no risk to DME integrity, just annoying to have to restart the DME and app and try again.

Thanks mate and We all pray that God Blesses your family with Health and Happiness.

[karter16]

Is there a guide on how to interpret the data? Been thinking of getting my injectors cleaned for a while now.

Essentially non-zero values are compensations to the injection amount (as a result of the injectors not all behaving equally). The caution I'd give is I *think* that if you happened to have a vacuum leak that affected one or more TBs it could also result in compensation, even though the injector isn't the root cause. So I think this can be useful, but is not an entirely causative diagnostic test.

[karter16]

Quick update - the last couple of months for me have been family with back to back sicknesses, etc. plus starting a new contract at work so I haven't had enormous amounts of spare time. I did publish v1.2.2 today which is a very small change. Both George Hill and ac427 have shared logs with me that contain occasional failures directly after programming mode entry and baud rate elevation. It seems that the root cause is possibly not allowing enough time for the channel to settle after the rate change, so I've extended that waiting period to a more conservative value in the hopes of solving this. The failure occurs at a non-critical point in the various workflows, so no risk to DME integrity, just annoying to have to restart the DME and app and try again.

[ac427]

It's already there :-) Data can be interpreted in the same was as you would in DIS/INPA/ISTA

I had forgotten about the rough running data.

There is also an injector activation section in DIS where you can activate individual injectors. I'm not sure how useful this though. Since all you could do would be to listen for the clicking of the injectors solenoid.

Would there be any other use for the injector activation part of DIS?

[E46 M3]

It's already there :-) Data can be interpreted in the same was as you would in DIS/INPA/ISTA

Is there a guide on how to interpret the data? Been thinking of getting my injectors cleaned for a while now.

[karter16]

Is it worth including injector testing from DIS?

It's already there :-) Data can be interpreted in the same was as you would in DIS/INPA/ISTA

[ac427]

Is it worth including injector testing from DIS?

[E46 M3]

Not sure how I missed this, ran out to the car with my laptop from bed...

Can confirn my INPA was all kinds of messed up, I ran the fuel pump test and the sound came from the correct location unlike my INPA copy that activates the SMG pump seemingly. (noise comes from the hood)

After I ran the pump test I tried to start the car and it fired first go so I'm confident my Hella pump checkvalve is faulty.

Many thanks.

[karter16]

Awesome tool !! 🔥
If you only someone could start doing this for the MSS50 DMEs that would be real dope. I guess that'll take continuing the work of Kim Fredding (RIP)

I would imagine it would be possible to extend for the MSS50 given they're based on the same family. Indeed for the MSS52 at least it would be very minimal work to extend (I can't say how much for the MSS50 without digging into it a bit more) I just had to make a scope decision and decided to keep the app focused on the MSS54.

[karter16]

Would it be possible to have an RPM reading from both the E-box fan and Engine cooling fan?

It's just because it is hard to hear the E-box fan when the test active when testing on the driveway.

The rpm of the fan? If so then unfortunately that's not possible. the DME controls the fan via duty cycle, but there's no feedback mechanism to the DME to tell it how fast the fan is spinning.

[ac427]

Would it be possible to have an RPM reading from both the E-box fan and Engine cooling fan?

It's just because it is hard to hear the E-box fan when the test active when testing on the driveway.