MSS54 DS2 Tool: FREE TOOL for programming DME - Tune, full binary, flash counter, etc

[karter16]

I'm not sure if i am helping but with the latest version of the tool and nothing connected to my laptop but with FTDI drivers loaded, KL30 and KL15 are not illuminated.

However, as soon as i plugged the USB end of the cable in the COM port but without the OBDII connector plugged into the car both KL30 and KL15 illuminated.

What does INPA show when you perform the same steps?

The way that the KL30 and KL15 detection work is that they are connected on specific pins (DSR and RI) on the interface. Some interfaces have one or both of these pins simply connected to supply, so the detection is not accurate. The app uses the same approach as INPA so the behaviour should be the same. If you get a difference between the two that's where it will get interesting. I've been through the relevant code again and can't find anything that suggests a bug (Not to say there isn't one, I just can't find it if there is).

[0-60motorsports]

you can buy windows license for about $10 License Tom


Sent from my iPhone using Tapatalk

Yeah I'll do that and get a dedicated windows laptop too. Thank you.

[fattycharged]

Yeah that's what I thought mate. My cousin has a windows tablet, told him to bring it over and I'll download the tablet and give it a shot once the car is back.

you can buy windows license for about $10 License Tom


Sent from my iPhone using Tapatalk

[ac427]

i just downloaded and installed 1.2.1 to my other laptop and i dont have anything installed driver wise or bmw tool wise other than this DS2 tool from today. when i run it, it shows nothing is connected as i would expect.

my bmw tool laptop which is a lenovo thinkpad, is not a VM and has many things installed along with previous FTDI drivers not the ones you provided but my D CAN USB is not plugged in when that issue happens. normally it show COM1 if it is plugged in.

not a huge deal for me but i will try different scenarios and see if i can nail that one down

for now seems to be an isolated environmental related issue specific to me

I'm not sure if i am helping but with the latest version of the tool and nothing connected to my laptop but with FTDI drivers loaded, KL30 and KL15 are not illuminated.

However, as soon as i plugged the USB end of the cable in the COM port but without the OBDII connector plugged into the car both KL30 and KL15 illuminated.

[nextelbuddy]

Weird. No it's not. Let me investigate. Are you running in a VM?

What happens if you close and reopen the app, it persists?


Edit: I don't seem to be able to reproduce this on my test machines. Is COM3 the COM port your cable is usually on? or a different / virtual COM port?

i just downloaded and installed 1.2.1 to my other laptop and i dont have anything installed driver wise or bmw tool wise other than this DS2 tool from today. when i run it, it shows nothing is connected as i would expect.

my bmw tool laptop which is a lenovo thinkpad, is not a VM and has many things installed along with previous FTDI drivers not the ones you provided but my D CAN USB is not plugged in when that issue happens. normally it show COM1 if it is plugged in.

not a huge deal for me but i will try different scenarios and see if i can nail that one down

for now seems to be an isolated environmental related issue specific to me

[karter16]

is it normal in 1.2.1 to show KL15 ignition on when i just have the application open but no USB cable connected?

i just downloaded and installed over previous version and launched 1.2.1 but saw the status shows KL15 ignition on

Weird. No it's not. Let me investigate. Are you running in a VM?

What happens if you close and reopen the app, it persists?


Edit: I don't seem to be able to reproduce this on my test machines. Is COM3 the COM port your cable is usually on? or a different / virtual COM port?

[nextelbuddy]

is it normal in 1.2.1 to show KL15 ignition on when i just have the application open but no USB cable connected?

i just downloaded and installed over previous version and launched 1.2.1 but saw the status shows KL15 ignition on

[0-60motorsports]

Is there a guide to wiring in the CSL flap motor and sensor available?

https://nam3forum.com/forums/forum/main-forum/e46-2001-2006/13962-diy-oem-csl-map-iat-flap-wiring

[ac427]

Is there a guide to wiring in the CSL flap motor and sensor available?

[ac427]

Nah if it's working for you with tool32 then it'll be the app. There must be something else that's affecting it as well. Just a bit hard to figure out without having one myself to test with


Sent from my iPhone using Tapatalk

Could the tool be trying to close it when it is already closed or vice versa?

It sounds a lot like the throttle actuator at 100%

[headlock]

oh man, this is so good. Thank you!

[karter16]

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

Nah if it's working for you with tool32 then it'll be the app. There must be something else that's affecting it as well. Just a bit hard to figure out without having one myself to test with


Sent from my iPhone using Tapatalk

[Cubieman]

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

[karter16]

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").

[ac427]

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?