ECU bricks on anything other than stock maps

[X-se]

Evan-

Did the original ROM ID get corrupted when pulling it?
Hard to tell from what was being said with the begining of the thread when OP said just grabbed an MR ROM and also hoped it wasn't caused by trying to load a GSR ROM.
My SE is 55580006 not 55580005 but I'm sure they used both on the SE's. If you didn't get the right ID read out on the set up it could be this one?

Hope you guys get it figured out.

[esevo]

Rich-

No new ecuflash (1.42)or evoscan (2.8) Never had issues with it prior to this car.
As for evoscan I did have it open when flashing, prior to newer research showing that's been causing issues... I cannot conclude if this caused the issue or not.


chetrickerman, and X-se,

My 2 year old tactrix 2.0 failed (usb broke internally) when I was about to pull the tune the first time. I overnight-ed a new cable and 2.0, port so I doubt the cable or the openport was to blame. Also battery voltage was checked and a charger put in place to insure it wasn't a culprit.

I never once tried uploading a GSR map as that is a big no! After benching ecu with the oem 55580006 tune reflashing back into the car with no changes would brick it again allowing me to conclude that the oem 55580006 rom was corrupt. Having tuned enough 2010 mr's I had a good base 55580005 tune at that was the new bench tune I installed and since I could flash via obd2.

Thanks

Evan Smith

[chetrickerman]

Right, the problem may not be with the tactrix cable, it could be the wiring harness from the OBD port to the ECU. If one wire is severed, it will brick everytime.

Great thread in your sig btw.

[X-se]

Yea. Your thread is spot on.
I jumped based on the facts given which were not accurate and I'm glad you set it straight.
Sorry if I gave you bad press because that wasn't justified based on what the real facts were.
You got my respect. I feel for guys like you that have customers that can help or hurt your business without realizing the impact they can make with reviews and posts.

[esevo]

I understand, I also know how forums work so it can be hard to stay level headed. Thank you for your respect.

I used to be a vendor and plan on becoming one again on both forums however, I had to buy a dyno and a shop to do it legit!

The OP is very knowledgeable and takes his time to research and mod his evo correctly. However it can be a concern when someone with experience runs into issues that haven't been seen before (in that way).

Thats tuning tho, no car is ever the same so one cant cookie cut a tune.

I hope the ecu gurus can determine if what the cause off these bricks can be... Ill look and try to flash with evoscan open, on the OP's car next week to see if that was the issue! Also check for wiring to the obd2 being bad.

Thanks guys!

Evan Smith

[gunzo]

there is only a few way to brick the ECU ..

wrong xml def (ie the code is F*kup)
wrong coding on custom ROM
F*kup computer ..yes it happens

You do not need to bench the ECU everytime it bricks

I believe the only time I had to bench the ECU was when my own customised rom was coded wrongly LOL ..

from here you probably can work out whats wrong with the car

Originally Posted by esevo

I understand, I also know how forums work so it can be hard to stay level headed. Thank you for your respect.

I used to be a vendor and plan on becoming one again on both forums however, I had to buy a dyno and a shop to do it legit!

The OP is very knowledgeable and takes his time to research and mod his evo correctly. However it can be a concern when someone with experience runs into issues that haven't been seen before (in that way).

Thats tuning tho, no car is ever the same so one cant cookie cut a tune.

I hope the ecu gurus can determine if what the cause off these bricks can be... Ill look and try to flash with evoscan open, on the OP's car next week to see if that was the issue! Also check for wiring to the obd2 being bad.

Thanks guys!

Evan Smith

[richardh]

Originally Posted by gunzo

I believe the only time I had to bench the ECU was when my own customised rom was coded wrongly LOL ..

That was also the cause of my one "bench" incident. I'd asked the ECU to fetch a 2-byte value from an odd address! And I was off to build that wiring loom, lol.

I've had flashes hit by Glorious Windows Explosion before, too... but they didn't need a bench-flash to fix. I left the ignition on, rebooted the laptop, reconnected, used "Exit Programming State", reflashed. All good.

Rich

[sstevojr]

What if windows decides to change the file extension....say .MAP?? Brick worthy??

[richardh]

Change what when, sstevo??

Rich

[Vutall]

Had a delay on my relays. They should be in tomorrow so hopefully we can retune this weekend or next week.