So I was getting ready to start logging my car tonight, I prepared everything, got a wideband installed, got everything ready, tactrix, laptop etc...

So the first time I read my map off the car the car was displaying all sorts of errors while reading the ECU (battery voltage low, oil low, brake fluid low, asc off, check drivetrain, confirm key location(FAST key car)) but it completed reading the ECU without any issues and I had the map loaded in ECUFlash so I didn't pay attention to it because it felt like the same thing as ACD lights flashing in Evo IX. After it was done, I turned the ignition off, put it on again and it fired right up so it left my mind.

So I went on home, read through the Mode23 logging section, updated the XML got my map ready to reflash on to the car. Well, here's where it starts...

I flash the new ROM to the car ready for Mode23, those same errors popped up while flashing the ROM. Except this time... When I turned off the igniton and turned it back on, those errors were still around. I tried starting the car - it cranks but doesn't turn on. Ok, maybe I did something wrong with the XML's. I go back, recheck the XML's and see that everything is spot on. I go back to the car, try to flash my stock unmodified ROM back on to the car. Kernel load... Error. Bam. Tried multiple times, ignition turning on/off, no go - just shoots an error straight at me.

Can't reflash the car back to my old map, can't read off the ECU anymore, can't start the car, can't connect to it with EvoScan to see if those codes are really in the ecu and try to clear them. Nada.

I also tried disconnecting the battery, left it for 30 minutes and it doesn't help. The moment I put the ignition on... Battery voltage low, oil low, brake fluid low,............. And it just keeps scrolling, it doesn't stop.


Any help will be greatly appreciated. It's 3:45 AM here and I'm out of ideas.

Thanks,
Ales

 

Search on here for what others have suggested. I think it's best to not have disconnected the laptop or OP2.0 cable, and then try to reflash again, or "Exit Programming State" in EcuFlash. Hopefully others can help.

 

The error codes cycling on the dash is normal when flashing.

Sounds like you missed a wrong mode23 def.

You will now need to bench the ECU

- Bryan

 

Yeah, need to bench the ECU for sure. There is a how to by tephra on here. Goodluck!

 

^^ +1...

OP when you changed the values for mode23 for ecuflash, did it had same values with the table names? i.e. "IFMODE 0x05 -> 0x023 #1"..if you changed the values and it was not the same values..then i guess.....you really need to bench it...tephra posted a how to for the ecu bench process..


btw, clipse3gt, you have pm on other forums

 

Bench time

As per tonyboy - what romid are you dealing with and did you check the old numbers matched before changing them?

 

messed up during reflashing process or messed the xml up. bench it but be careful and PAY ATTENTION while flashing ! or else it will cost you BIG time. I would advise you to send it to the pros to bench. GL

 

He is in Slovenia.

so fastest + cheapest = self bench :|

 

Oh joy.... Thanks for the help guys, let's see if I can make the ECU survive this...

 

Good luck! Hope you get her together for the race this weekend.

 

 

Good luck. Please keep us updated. I was nearly in your position a few weeks back. I wasn't 100% sure that I updated my XML properly for Mode23 so I decided to have newcomer81 edit the file for me.

 

Going to pull the ECU in a few minutes and start getting there...

Can anyone who has done this before tell me how long the flash takes approx?

 

Longer than a normal flash, but I wouldn't say LONG.

It's just a scary minute that feels like a long time ;


Good luck! Ask lots of questions.

 

flash takes a couple of mins, it has to do a complete ROM write...

then you gotta reflash in normal mode to finish it off - 30 secs or so...