I figured as much with the checksums.Įither way, I'm just looking for the raw ecu dump to save me efforts. I'm not going to rattle off programs on an efilive forum but with the binary I can do what I need to do. I don't see why I can't do that here if it comes to that.Įither way, I'm just looking for the raw ecu dump to save me efforts. For all my projects up to this point I have always worked with an engine sim and set break points. I am concerned with making changes that aren't what I want. I am new to the lml and the diesel world in general but I hope this don't make you assume I am incompetent and unaware. You are correct, it is more work without spending the cash but never impossible. I've also made some good friends from around the world who have written their own software that works very well for interpreting structure and processes. But anyways, I've bricked several controllers and I've learned from it. Luckily that platform didn't care about checksums. We used a rom editor with a definition file(we wrote) to mod the bin and the chip's toolkit to flash the modded image. I'm trying to avoid getting on a soapbox but I scratched through the surface of debugging a crotch rocket ecu with a friend of mine who is very handy. the specifics of implementing one can be ironed out in time I'm confident. cax will allow me to do is correct though.

I do believe my interpretation of what the. This does not mean that your *.cax file is correct, nor even that it changed what you intended it to change - so beware.thanks for your input. as long as the changes are made using EFILive (including the use of a custom *.cax file), the checksums are updated accordingly. This does not mean that your *.cax file is correct, nor even that it changed what you intended it to change - so beware. My early ventures into this brave new world cost me several controllers - the price of doing business as they say.

This exercise is not for the uneducated nor inexperienced user. Expensive software can offer some assistance with interpreting the code.

Cost effective binary / hex software will display the code, but will offer little insight beyond this. If you have never worked in hex / binary before, then you are in for a big surprise. Even the *.cax file restrictions that came into place about a year ago caused me some issues. If the *.cax file option is ever eliminated, it would seriously impact the specialty services that I offer. I post this warning as from time to time the good folks at EFILive debate removing the the *.cax file option - due to users making an error, then wanting some form of support from EFILive. This option is 100% 'use at your own risk'. EFILive allows users to augment / personalize their tuning software via the *.cax file option. Sounds like you have never used / written a *.cax file before.

Tuning with bin files