The good news is that it all worked first time! (to be fair I put a lot of effort into checking and rechecking the code to make sure it was right)
First up I flashed the custom program to the DME and ran it with the standard tune. I've designed this such that if someone uses the custom program with a tune file not designed for it the additional functionality is simply disabled. Likewise if someone uses the custom tune with the standard program it is also gracefully handled.
I then verified that DME functionality was as expected. E.g. normal function and no additional CAN message activity. All was well.
I then added the new parameters to my tune file:
and flashed the tune. Sure enough everything still worked, and the 7D0 CAN message was present on the CANbus.
Here are the values being logged.
I've got some more scenario testing to do. e.g. test the 7D1 message as well, intentionally put bad data into the config parameters and make sure it's handled gracefully etc. but super stoked all is working so far as this is the most complex change I've made to the program so far!
Onwards and upwards - this functionality will be very useful to me as I dive into more refinement of my tune now I have high-frequency CAN logging available!

Leave a comment: