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

  • heinzboehmer
    replied
    I like (2) as well.

    Just a thought: maybe add the option to toggle between outputting multiple log files (one per request) or one coalesced one like you showed?

    I genuinely can't decide if that makes it more or less confusing, so feel free to ignore.

    Leave a comment:


  • ac427
    replied
    I think option 2 because it lends itself more to accurately synchronised log comparison, which is essential.

    Leave a comment:


  • karter16
    replied
    Question for the group when it comes to logging live values.

    Because of the way the DS2 live values queries work, there are a number of "blocks" that are queried. These must be done sequentially over the DS2 interface. If a user wants to log values from multiple of these blocks then the app needs to make multiple queries to get the relevant values from each block. Because these are done serially, it means that the exact time block 1 was snapshotted, is different to block 2. etc. How much this matters varies on what is being logged. If you're trying to track ignition timing against other variables for example, or do the CSL fuelling tuning process it's a bigger deal, for other things like logging temps etc. it doesn't really matter.


    There are two ways I can think of to approach this:

    1: Query each block in sequence and when you have all the data from that sweep then write a line to the logs with the current timestamp. At 3-4Hz that means some values might have been capture quarter of a second earlier/later than other values.

    2: Log the values from each block as it comes in on its own log line. This means you get the exact time that those values were snapshotted. Any values not in that block are blank for that row.


    My personal preference is option 2 as it is more exact/correct. However it means then that the user has to understand that is how it works and setup their log viewer accordingly (e.g. in MegaLogViewerHD you have to select the "use last value for NaN" option, etc.). Want to make sure this doesn't end up being too complicated for people to easily use.


    Thoughts?


    Example of option 2 for those of us who are visual:
    Click image for larger version

Name:	Screenshot 2026-05-22 at 10.03.01 AM.png
Views:	250
Size:	247.8 KB
ID:	356105
    Last edited by karter16; 05-21-2026, 03:03 PM.

    Leave a comment:


  • karter16
    replied
    Originally posted by terra View Post
    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.
    Yeah okay - I've been thinking about this and it seems like it could be the more streamlined way to do it for sure. also means where the user wants to write multiple blocks the app can just execute that as a set of sequential actions. Thanks heaps for this, I will look to implement this in a future version.

    Ah RAM dumping is a great idea - I hadn't thought of that one. as you say, less people who will use it, but that doesn't matter, the point is to try to make all these activities as easy as possible (and accessible on modern hardware, Win10/11, ARM, etc.)

    Leave a comment:


  • karter16
    replied
    Originally posted by terra View Post

    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've done all my development on Win11 VM on an M1 MacBook Pro with a USB-C to A adapter and no issues there.

    Leave a comment:


  • karter16
    replied
    Originally posted by Slideways View Post

    I'll give that a try. It defaults to COM for this cable.
    And to confirm, have you set the COM latency time to 1ms in device manager? If you use FTDI driver then the software can do this automatically, if you use COM then you have to make sure it's set to 1ms (defaults to 16ms).

    Leave a comment:


  • ac427
    replied
    Tomba How does the INPA Vanos test compare to the original DIS Vanos test?
    Last edited by ac427; 05-25-2026, 09:59 AM.

    Leave a comment:


  • 0-60motorsports
    replied
    Originally posted by bmwfnatic View Post

    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.

    Leave a comment:


  • Slideways
    replied
    Originally posted by terra View Post

    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.

    Leave a comment:


  • terra
    replied
    Originally posted by Slideways View Post

    ​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.

    Leave a comment:


  • Slideways
    replied
    Originally posted by terra View Post

    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.

    Leave a comment:


  • terra
    replied
    Originally posted by Slideways View Post

    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.

    Leave a comment:


  • paulclaude
    replied
    Fantastic work! Will try out the tool sometime soon

    Leave a comment:


  • bmwfnatic
    replied
    Originally posted by Slideways View Post

    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.

    Leave a comment:


  • Slideways
    replied
    Originally posted by bmwfnatic View Post

    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.

    Leave a comment:

Working...
X