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

[0-60motorsports]

I haven't tried Matt's tool yet, but I've been using it for many years on almost a daily basis, and it's very reliable.

let us know once you try out, im sure it'll work perfectly. Will be ordering soon.

[Slideways]

Hmm, I haven't tested this app on ARM yet, but my own MSS6x flasher seems to work fine on ARM with any cable I throw at it (whether in CAN or K-line mode).

Might be worth trying COM mode instead of FTDI or vice versa to see if that works better.

I'll give that a try. It defaults to COM for this cable.

[terra]

manwell

Either the cable with USB-A to USB-C adapter (old blue OBD cable supplied by TTFS) is having a connection issue during a fast read or something in the Win11 ARM VMware is interrupting the connection. Slow full read works, but takes 30min.

Hmm, I haven't tested this app on ARM yet, but my own MSS6x flasher seems to work fine on ARM with any cable I throw at it (whether in CAN or K-line mode).

Might be worth trying COM mode instead of FTDI or vice versa to see if that works better.

[Slideways]

Is this a manual or SMG? I know for the models where fast baudrate was officially supported sometimes the transmission module being on the bus sometimes caused issues.

manwell

Either the cable with USB-A to USB-C adapter (old blue OBD cable supplied by TTFS) is having a connection issue during a fast read or something in the Win11 ARM VMware is interrupting the connection. Slow full read works, but takes 30min.

[terra]

Can you do a fast full read with this cable? Current cable stops at 5% and gives an error. Slow full read works though.

Is this a manual or SMG? I know for the models where fast baudrate was officially supported sometimes the transmission module being on the bus sometimes caused issues.

[paulclaude]

Fantastic work! Will try out the tool sometime soon

[bmwfnatic]

Can you do a fast full read with this cable? Current cable stops at 5% and gives an error. Slow full read works though.

I haven't tried Matt's tool yet, but I've been using it for many years on almost a daily basis, and it's very reliable.

[Slideways]

I always use the OSE K-line, small form factor, well built and only 29$
https://www.one-stop-electronics.com...usb-interface/

Can you do a fast full read with this cable? Current cable stops at 5% and gives an error. Slow full read works though.

[bmwfnatic]

That's great, thank you. Do you have a link for a good legitimate one?

Edited my post shortly after

[0-60motorsports]

I always use the OSE K-line, small form factor, well built and only 29,95$

That's great, thank you. Do you have a link for a good legitimate one?

[bmwfnatic]

Gentlemen any links for where to buy a good cable to use with this?

I always use the OSE K-line, small form factor, well built and only 29$

https://www.one-stop-electronics.com/product/bmw-inpa-ediabas-kk-usb-interface/

[karter16]

Awesome work! Will test it soon.

I don't know if you have implemented security checks like flashing CSL bootloader in non CSL boot loader ECU?
I would expect a check between file and actual data in ECU. This would reduce the risk of a brick.

Don't know if you want to implement more diagnostic information? Activate actuators, DMTL checks and VANOS check? I could support you on the VANOS check.

The MSS5x ECU also holds cylinder individual CO trims. I don't know were these are stored yet. Since the ECUs I have read have different values, I suspect these are adjusted in the factory with special manifold or other procedure.
In any case its useless once you don't have extraction points on your exhaust manifolds (Like S38, S15 and S50).
I do have my own INPA IPO file to adjust these on MSS50.

Awesome - yep the software will prevent flashing a program that doesn't match the bootloader, and prevent flashing tune that doesn't match the program.

Yep I'm thinking that diagnostic actions are something that could follow. Probably the common ones like vanos, CSL flap actuation, etc. at least. funny, I was actually looking at the DS2 calls for the VANOS check yesterday!

Re the individual trims are you talking about ti_ll_z1 thru ti_ll_z8? (injection timing adjustments per cylinder to balance out uneven running) If so they're stored in the EEPROM adaptions block and are actually dynamically adapted by the DME. If you mean something else let me know and I can have a look :-)

[Tomba]

Awesome work! Will test it soon.

I don't know if you have implemented security checks like flashing CSL bootloader in non CSL boot loader ECU?
I would expect a check between file and actual data in ECU. This would reduce the risk of a brick.

Don't know if you want to implement more diagnostic information? Activate actuators, DMTL checks and VANOS check? I could support you on the VANOS check.

The MSS5x ECU also holds cylinder individual CO trims. I don't know were these are stored yet. Since the ECUs I have read have different values, I suspect these are adjusted in the factory with special manifold or other procedure.
In any case its useless once you don't have extraction points on your exhaust manifolds (Like S38, S15 and S50).
I do have my own INPA IPO file to adjust these on MSS50.

[terra]

The latter is how I do it in mss6x flasher (minus restoring adaptions etc), but that's also partly because on those DMEs writing a program wipes the tune so it's pretty much necessary. I do like the idea of having a 'one click' solution to accomplishing what is essentially a complete restore from a different backup (minus ISN I guess). Could be useful for those scenarios where one needs to swap back to a stock tune not want to go through the hassle of setting the drive cycles again etc.

Another thought I had was adding a RAM dumping functionality, though again probably mostly useful for us tinkerers out there.

[karter16]

I assume it's a deliberate design choice to not allow flashing a tune from a full bin?

Yeah interesting. It was in that I felt it was unnecessary complexity for the user to understand. But if we think it's a common use case then I t would be easy for me to add. I think probably allow the user to select a full bin when writing tune and then just pop a confirmation to the user to confirm that's what they want to do?

Other option would be to entirely flip the paradigm around and have a single “write” function and based on the source file type the user selects then given them the option of what segment/s they want to write? Maybe that's simpler? (this would also make it easy then if say a user had one DME and swapped back and forth between M3 and CSL progs. They could then choose to restore their Adaptions (EEPROM) block, etc. as well if they wanted.)


Sent from my iPhone using Tapatalk