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

[terra]

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

[karter16]

Live Values/Logging Proof of Concept (This is not available in the current version)

Modelled on, what I presume is, the same approach that TestO uses which is calling the DS2 I/O sample messages (means you get a whole set of values in a single DS2 call). Essentially select the "sets of values" you want to see on the left and side, and then see the values in the table on the right hand side. From a live-read perspective there's no performance benefit in selecting single values to display. I will definitely be building out the ability to select what specific values to log to CSV though.

The ultimate data rate is limited by the DS2 protocol at 9600 baud. If you select a single set of values like the screenshot below you can see the data frequency is about 10Hz, as you select more sets to include the frequency drops accordingly due more more frames transiting the bus.

[0-60motorsports]

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

[karter16]

Seems to work!

Awesome thanks for the confirmation!!!

[terra]

Seems to work!

[karter16]

KL30 on, KL15 off (I don't have KL15 wired on my bench setup, and honestly I'm not 100% sure if my cable even reports it). It seems just going to any screen and then back to the connect screen causes the behavior. But it was mostly writing that I messed with

I'll recreate and grab a log tonight

Found and fixed! (I think)

v1.0.2 is now published: https://github.com/karter16/MSS54-DS...ublic/releases

Please give it a go when you get a chance and let me know if the issue is now resolved :-)

[karter16]

Awesome thanks guys - I'm pretty sure it's going to be a scenario that isn't properly accounted for. Let me investigate and see what I can come up with. My cable does report KL15 which makes it a bit hard to test that the cases where it isn't are handled properly - I thought I had it nailed but it seems not.

[ac427]

hmmm interesting. Couple of questions:

- Do the KL30 and KL15 lines show as on? or do you see them marked as off? (I wonder if this is it and I have an unaccounted-for scenario in the reconnection logic)
- What sorts of things have you done prior to going back to the connect screen? read/write? or just read?

If you're able to grab the log file from that session and send it to me that would be super-helpful in figuring out what's happened :-)

KL30 on, KL15 off (I don't have KL15 wired on my bench setup, and honestly I'm not 100% sure if my cable even reports it). It seems just going to any screen and then back to the connect screen causes the behavior. But it was mostly writing that I messed with

I'll recreate and grab a log tonight

I think i had this too. When i reset the Flash counter. Once the write was over i am sure had to quit the app to reconnect. I'll try to recreate it.

[terra]

hmmm interesting. Couple of questions:

- Do the KL30 and KL15 lines show as on? or do you see them marked as off? (I wonder if this is it and I have an unaccounted-for scenario in the reconnection logic)
- What sorts of things have you done prior to going back to the connect screen? read/write? or just read?

If you're able to grab the log file from that session and send it to me that would be super-helpful in figuring out what's happened :-)

KL30 on, KL15 off (I don't have KL15 wired on my bench setup, and honestly I'm not 100% sure if my cable even reports it). It seems just going to any screen and then back to the connect screen causes the behavior. But it was mostly writing that I messed with

I'll recreate and grab a log tonight

[karter16]

Overall works great! Potential bug, and I'm not sure if this is a quirk of doing things on the bench with a frankensteined DME (early MSS52 with 0F70K CPUs and 29F400AB flash memory flashed with a CSL binary), but if I go back to the connect screen after doing stuff, the program seems to disconnect from the DME and doesn't successfully reconnect (in either COM mode or D2XX) without closing and restarting.

hmmm interesting. Couple of questions:

- Do the KL30 and KL15 lines show as on? or do you see them marked as off? (I wonder if this is it and I have an unaccounted-for scenario in the reconnection logic)
- What sorts of things have you done prior to going back to the connect screen? read/write? or just read?

If you're able to grab the log file from that session and send it to me that would be super-helpful in figuring out what's happened :-)

[terra]

Overall works great! Potential bug, and I'm not sure if this is a quirk of doing things on the bench with a frankensteined DME (early MSS52 with 0F70K CPUs and 29F400AB flash memory flashed with a CSL binary), but if I go back to the connect screen after doing stuff, the program seems to disconnect from the DME and doesn't successfully reconnect (in either COM mode or D2XX) without closing and restarting.

[Shonky]

Nice work. I like the keep history forever feature.

[Keith_MN]

Amazing. Looking forward to playing with this when I'm back in town.

[0-60motorsports]

This is amazing! Thank you to you and everyone else who tested it. Hopefully in the future versions there will be the options to program and change small things in the tune like in martins tool.

[Tbonem3]

Great work!