OFT Failed to Write - Tune File Erased

[Danklvr]

So I was updating my tune this morning, making MAF scale adjustments to the tune i have been running for about 2500 miles... I have edited this tune file many times, ans I know I am using the correct ecu deff, as i have edited and flashed before with no issues.

I began to flash the update today, everything was going fine.. OFT connected, erased the existing tune file, and wrote 20% of the new tune before giving me the error "Cannot communicate with ECU - Key on and confirm".

Now I cannot flash a new tune - "Cannot communicate with ECU - Key on and Confirm", and I cannot start the car..

I have disconnected the battery for 5 minutes, but to no avail...

Am I fuckzored, or is there anything i can do?

[Danklvr]

Update -
I disconnected the battery again for 10 minutes, and tried to flash the stock rom.
The first 2 times I got the same error message, but the third time the stock rom successfully flashed.

I ran the car for about 5 minutes, and then was able to flash my modded tune file back on the car without issues.

Hope this info helps anyone who may experience similar issues.

[churchx]

My two wild guesses of reasons might be insufficient charge in battery or bad OBD connector contact.

[Vin]

Thanks for sharing. You must have gone crazy when it happened, this is why I'm always a bit scared when flashing.. Good to know it can be fixed

[Danklvr]

Originally Posted by Vin

Thanks for sharing. You must have gone crazy when it happened, this is why I'm always a bit scared when flashing.. Good to know it can be fixed

You can imagine my grin of joy fading into a look of confusion and horror, as I watch the tune upload stop mid stream! Initially I was ready to crap myself! Then I started going down the list of things to try... reset OFT to OBD connection, reflash, reset battery/ecu, flash stock rom, repeat...

Dunno why, but something told me to hookup to Techstream. It pulled in my vin# and ecu info, so I figured all was not lost, and I tried flashing the stock rom back again.

I know Techstream had nothing to do with the fix, most likely was a bad connection to OBD to begin with.

I am always very good about checking the connection, and usually I'll throw it on real time data display for a few minutes and have a once or twice around the neighborhood to warm up to operating temp before flashing just to make sure everything is communicating nicely.

[steve99]

Ok thats good news

Id say check your battery volts, put a litfle load on battery ie jist ignition on or park lights see if volts drops below 12 if so its likely that that may cause flashing issues.
The oft will not flash if car vattery volts falls too far.

Also cgeck your obd conndction safest way is to get logging started on oft. While logging running wiggle cavles and port and see if you get any errors.

Obd port on 2013 amd earlier cars are often bad

Luckly the ecu are cheap like 100 usa and easily replaced with simple proceedure

These ecu are much harder to brick than the old wrx ecu. Generally yo need to flash ecu with badly modified rom to brick it. If rom is good it hsrd to brick, if write fails you will usually recover due boot rom area. Proble is if you write sucessfully and eom send processor off in a loop your screwed nost of the Time