Announcement

Collapse
No announcement yet.

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

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Cubieman
    replied
    Hmm, still having the same issue with the flap test. Not sure if it's my tune that is suppressing DTCs or what.

    Leave a comment:


  • karter16
    replied
    Originally posted by ac427 View Post

    Thanks karter16. A silly question but does the "Idle Speed Control" test manipulate the Idle Control Valve?
    Yes it does. Not directly, in that the desired idle target is still measured against the assessed engine and accessory load as a whole, and the ICV then controlled as a result. e.g. it's not a direct "open ICV by this amount or to this position" more a "I want idle to be this speed", and the DME then works out how the ICV should be set accordingly (I only note this because this differs to how the throttle test works which is a "open the throttle bodies to this exact position/percentage").

    Leave a comment:


  • ac427
    replied
    Originally posted by karter16 View Post
    V1.2.1 released. https://github.com/karter16/MSS54-DS...ses/tag/v1.2.1

    bugfix/minor enhancements
    • Fixed an issue with the CSL flap test which caused the test to abort prematurely. The test now sends the DS2 test command twice, as is required.
    • Changed TMOT prerequisite for VANOS test to 75 degrees from 80 degrees.
    • Added display of TDME (DME temperature) to the E-Box Fan test.
    • Added display of TMOT (motor temp) and TKA (radiator outlet temp) to the Electric Fan PWM Control test.
    ​
    Thanks karter16. A silly question but does the "Idle Speed Control" test manipulate the Idle Control Valve?

    Leave a comment:


  • karter16
    replied
    V1.2.1 released. https://github.com/karter16/MSS54-DS...ses/tag/v1.2.1

    bugfix/minor enhancements
    • Fixed an issue with the CSL flap test which caused the test to abort prematurely. The test now sends the DS2 test command twice, as is required.
    • Changed TMOT prerequisite for VANOS test to 75 degrees from 80 degrees.
    • Added display of TDME (DME temperature) to the E-Box Fan test.
    • Added display of TMOT (motor temp) and TKA (radiator outlet temp) to the Electric Fan PWM Control test.
    ​
    Last edited by karter16; 05-31-2026, 01:52 PM.

    Leave a comment:


  • karter16
    replied
    Originally posted by Cubieman View Post
    ​
    I did get the flap to activate using the pictured command in tool32.

    It "buzzes" for ~4 seconds, stops, I command it again and the flap opens/shuts, same as the video I previously linked. I don't know if that person had to command it twice as I did however.

    I wonder if that command is finding the stop points, as "adapt" is in the title?
    Click image for larger version Name:	20260531_145516.jpg Views:	0 Size:	73.5 KB ID:	357051
    Okay great thank you so much - this is it. The test command does indeed need to be sent twice. Found a video on YouTube as well that confirms this. I'll make a fix for this and get it released. Thank you so much for your help with this!!!

    Leave a comment:


  • Cubieman
    replied
    Originally posted by ac427 View Post
    ​
    Is it worth saving the HTE tune with the tool and flashing back to standard to see if the E-Box fan test works or if there are any E-Box fan errors?

    Apparently, you can also activate the E-Box fan with INPA, though the activate section, although my version only had the radiator fan motor.
    ​

    I may just do this, I want to test this stupid fan now, it's odd my DME won't allow the test.



    I opened up my BIN in Martyn's binmod tool to find the option to suppress DTC's for the flap is indeed activated.

    This is likely a very standard setting for tuners as not many people run the CSL flap.

    I did get the flap to activate using the pictured command in tool32.

    It "buzzes" for ~4 seconds, stops, I command it again and the flap opens/shuts, same as the video I previously linked. I don't know if that person had to command it twice as I did however.

    I wonder if that command is finding the stop points, as "adapt" is in the title?

    Also, would having the DTC's suppressed (assuming no flap related codes are present) have an affect on the DS2 Tool's ability to test?

    Side note, still not able to test ebox fan on tool32 or DS2, might need to test it with direct voltage somehow.

    Click image for larger version  Name:	20260531_145516.jpg Views:	0 Size:	73.5 KB ID:	357051
    Last edited by Cubieman; 05-31-2026, 01:11 PM.

    Leave a comment:


  • ac427
    replied
    Originally posted by Cubieman View Post

    This I do not know, the tune was a standard CSL then HTE did some work latter on, that would seem to be an odd DTC to suppress, but I definitely cannot say one way or another.
    ​
    Is it worth saving the HTE tune with the tool and flashing back to standard to see if the E-Box fan test works or if there are any E-Box fan errors?

    Apparently, you can also activate the E-Box fan with INPA, though the activate section, although my version only had the radiator fan motor.
    Last edited by ac427; 05-31-2026, 09:31 AM.

    Leave a comment:


  • Cubieman
    replied
    Originally posted by karter16 View Post

    With the caveat that I haven't experienced it myself, if you watch YouTube videos of the flap test running that electrical arcing noise seems to be a normal part of the process as far as I can tell.

    Re shadow codes 99 and 89, they are normal/expected. To check that the error reporting system is working correctly the DME intentionally triggers those two codes on a regular basis as a test. You can disregard them. I've included them for completeness, but you're the second person that's brought this up, I wonder if maybe better for the app to suppress these two codes (or at least note that they are expected/nothing to be concerned about)



    This is the noise, that makes me feel better as does your explanation of the shadow codes.

    I will try the flap/ebox tests again with tool32 tomorrow using the different prg file, thanks for all the feedback and all this work you have done, this is fantastic.

    Leave a comment:


  • terra
    replied
    Originally posted by karter16 View Post
    Re shadow codes 99 and 89, they are normal/expected. To check that the error reporting system is working correctly the DME intentionally triggers those two codes on a regular basis as a test. You can disregard them. I've included them for completeness, but you're the second person that's brought this up, I wonder if maybe better for the app to suppress these two codes (or at least note that they are expected/nothing to be concerned about)
    IMO it would be best to suppress when the counter is zero. Which I believe is basically what INPA and DIS/ISTA would do

    Leave a comment:


  • karter16
    replied
    Originally posted by Cubieman View Post
    I tried once more and had the same type of almost electrical arcing noise for a moment and incomplete test.

    These shadow errors are indeed now hard faults.

    I'll explore further tomorrow, I'd sure love to get this test working, must be something with my wiring, odd.

    Click image for larger version

Name:	20260531_004241.jpg
Views:	124
Size:	124.5 KB
ID:	357008
    With the caveat that I haven't experienced it myself, if you watch YouTube videos of the flap test running that electrical arcing noise seems to be a normal part of the process as far as I can tell.

    Re shadow codes 99 and 89, they are normal/expected. To check that the error reporting system is working correctly the DME intentionally triggers those two codes on a regular basis as a test. You can disregard them. I've included them for completeness, but you're the second person that's brought this up, I wonder if maybe better for the app to suppress these two codes (or at least note that they are expected/nothing to be concerned about)

    Leave a comment:


  • Cubieman
    replied
    I tried once more and had the same type of almost electrical arcing noise for a moment and incomplete test.

    These shadow errors are indeed now hard faults.

    I'll explore further tomorrow, I'd sure love to get this test working, must be something with my wiring, odd.

    Click image for larger version

Name:	20260531_004241.jpg
Views:	124
Size:	124.5 KB
ID:	357008

    Leave a comment:


  • karter16
    replied
    Originally posted by Cubieman View Post

    This I do not know, the tune was a standard CSL then HTE did some work latter on, that would seem to be an odd DTC to suppress, but I definitely cannot say one way or another.
    yeah agreed that it would be super odd, just thought I'd note it just in case!!

    Leave a comment:


  • Cubieman
    replied
    Originally posted by karter16 View Post

    attached is 12MSS54.PRG. I don't have MSS54HP.PRG.

    Don't suppose you happen to have the DTC for the ebox fan disabled? That could also cause what you're seeing with the test not being able to run.
    This I do not know, the tune was a standard CSL then HTE did some work latter on, that would seem to be an odd DTC to suppress, but I definitely cannot say one way or another.

    Leave a comment:


  • karter16
    replied
    Originally posted by Cubieman View Post

    Interesting, I did have these codes, but cleared them before doing the test, and none were hard faults. I'll give it another shot just to be certain.

    A few months ago I had cracks in my strut tower welded, I removed the DME and also de-pinned all wiring associated with the CSL snorkel as to have the wiring out of the way.

    I have since driven the car and all seems well with the flap but this indeed could be a contributing factor as to why the test didn't run.

    I'll try to sort this out and report back.

    Click image for larger version

Name:	20260530_145613.jpg
Views:	138
Size:	34.2 KB
ID:	357002
    Ah interesting. I'm pretty sure that if you'd cleared them first and they weren't hard faults then it shouldn't have blocked the running of the test, I am fairly sure that the bit 6 in GKS_ED will only be set if the code is active/hard.

    Leave a comment:


  • Cubieman
    replied
    Originally posted by karter16 View Post

    Okay so you got that error because the conditions for the test were not met. The conditions that must be met are:

    Click image for larger version

Name:	Screenshot 2026-05-31 at 4.48.07 PM.png
Views:	133
Size:	6.2 KB
ID:	356998​

    b_diag is definitely !=0 because the app is responsible for setting diagnostic mode over DS2 and the app would have errored out earlier if it couldn't set this.

    N (engine speed) must be less that 1000rpm.

    bit 6 of gks_ed must be 0. Bit 6 identifies whether there are any current (active) CSL flap errors in error memory.

    If you're able to validate you were doing the test with the engine not running, or with it at warm idle less than 1000rpm, and also check error memory and see if you have any CSL flap (GKS) errors would be the next step I think.
    Interesting, I did have these codes, but cleared them before doing the test, and none were hard faults. I'll give it another shot just to be certain.

    A few months ago I had cracks in my strut tower welded, I removed the DME and also de-pinned all wiring associated with the CSL snorkel as to have the wiring out of the way.

    I have since driven the car and all seems well with the flap but this indeed could be a contributing factor as to why the test didn't run.

    I'll try to sort this out and report back.

    Click image for larger version

Name:	20260530_145613.jpg
Views:	138
Size:	34.2 KB
ID:	357002

    Leave a comment:

Working...
X