Karter16's Silbergrau E46 M3 Journal

[karter16]

Continuing to make good progress towards getting this releasable.

heinzboehmer and Bry5on have kindly user-tested and given me excellent feedback to help improve the app and make it as user-friendly as possible. Laundry list of updates below:

• Fixed an edge case that cause DS2 commands to be interleaved causing a connection drop
• Added dialog to prevent app closure while DS2 connection active, if a wipe/write action is underway the user must wait until it is finished in order to leave the DME in a clean state, in any other state the user can choose to disconnect and close the app.
• Added the Flash Counter control to the Write page for better visibility, also warn the user if they attempt a write action with less than 5 flash slots remaining.
• Added graceful handling of cable/interface disconnection within the app.
• Found an issue with the Cancel button and ensured it now waits for the current DS2 command to conclude gracefully before cancelling the action.
• Disabled the cancel button while erase/write activities are in progress.
• Added full validation of Data/Program binaries. The source file is checked for version information and the app will not allow writing a program file that doesn't match the bootloader on the DME and likewise won't allow writing a data/tune file that doesn't match the program on the DME.
• Improved coverage of logging messages.
• Finished the Settings page.
• Relaxed validation (with extra user warnings) when restoring the Service segment (AIF, etc.) to allow restoration when the AIF region has been corrupted and the DME variant and VIN cannot be determined.
• Added better handling when the user connects but the car ignition is not on.
• Bryson noted that for a first time user the entry into fast read, and then the subsequent read of a tune file takes about the same amount of time as just reading the tune at 9600 baud. Have expanding settings to allow user to independently toggle fast read on and off for tune/program reads.
• Resolved a misunderstanding on my part about the persistence of the ZIF backup.

So what remains? More testing. The app has been pretty well tested on MSS54HPs, it needs testing with MSS54s. If Heinz gets a chance I think he's going to give it a go on his backup DME, if anyone else has a MSS54, the ability to BDM it if it all goes horribly wrong, and is game to be a guinea pig then let me know :-)

[George Hill]

Id be interested in giving it a shot on an MSS54, but I don't have a way to BDM if needed. BUT I'm not worried about that as I have some spare DMEs and nothing critical in use. What do you need from me? Shoot me an email [email protected] if its easier.

Will there be an option to virginize the EWS, so we can sync a used DME with a "new" to it car?

[karter16]

Id be interested in giving it a shot on an MSS54, but I don't have a way to BDM if needed. BUT I'm not worried about that as I have some spare DMEs and nothing critical in use. What do you need from me? Shoot me an email [email protected] if its easier.

Will there be an option to virginize the EWS, so we can sync a used DME with a "new" to it car?

Awesome that would be great thank you! First round of testing will be read-only anyway, as those logs should give me a fair idea of how it's all looking. After work my time I'll add you to the google drive folder that I'm using for the beta files and will flick you an email with some testing instructions - thanks very much!

Will there be an option to virginize the EWS, so we can sync a used DME with a "new" to it car?

Yep there will be for sure. Not as part of 1.0. I'm trying to quickly finish the current feature set and get it out there and then can iterate with additional features. Virginization and EWS sync are high on the list as appreciate this will be useful for quite a few people.

[0-60motorsports]

karter16 Would the DME be wiped if we reset the flash counter only?

[karter16]

karter16 Would the DME be wiped if we reset the flash counter only?

Nope, the software takes a backup of everything that's in that segment of memory, wipes the segment, and then writes everything back except the bytes specific to the flash counter.


Sent from my iPhone using Tapatalk

[0-60motorsports]

Nope, the software takes a backup of everything that's in that segment of memory, wipes the segment, and then writes everything back except the bytes specific to the flash counter.


Sent from my iPhone using Tapatalk

That is great! Thanks again.