Quote:
Originally Posted by stugray
It is not that hard, but did you forget about all the early discussion about:
the conversions in ECU Editor being wrong
the padding or not padding the first X bytes
Checksums being wrong
More than one user "bricking their ECU"
Saving in Bin vs Hex
etc. , etc.
I guess part of my frustration about the tactrix has nothing to do with Flashing and about logging innovate data without an OBD port, so the 50 hours was mostly trying to get the unit to do that.
And I a am C&DH (command & data handling) engineer for NASA spacecraft that cost over $1 billion each. So I have not only "flashed" a LOT of expensive hardware, but I have done it to spacecraft that were a long ways away.
My primary job is writing procedures for loading flight software.
So as I said: maybe due to my job, I am overly anal about getting the instructions right instead of "just do it".
|
I didn't forget, I just DGAF.
- ecu editor is irrelevant, you said you wanted to flash an OTS tune
- padding etc has to do with reading, not writing. The first 0x8000 gets padded and it doesn't matter because that part of the ROM doesn't get written when you flash.
- bin and hex are number systems, not file types.
- those that were bricked were recovered from what I understand. A new ECU is less than one day's pay for a big shot like you anyways
Why don't you use your big smart NASA brain to develop your own tuning platform (or for that matter, your own maps) and then document all the steps so us laymen can follow along.
- AdrianG