Hi All!

Please help. I used Ecuflash a few time without any problem, now I am able to write but couldn't read I check cable and pin all look good so far any suggestion will help...Thanks.

 

Glad I saw this thread, I was having the same problem and not able to read my stock ROM image. It was that cold in AZ but I did have the car sit in the garage for a few hours when I was attemping to read my stock ROM. Hope this will work out for me since I have been wanting to get a Jestr e-flash

 

Had the same problem as the OP, I have a ix and it has been below freezing in Maryland. Let the car warm up and you'll be good. This thread was very helpful.

 

I had the same problem yesterday and this AM (tried a different cable)....then found this thread....put the charger on and it worked fine ....THANKS AGAIN MJ

 

Yeah, one new bit of info is the ECU itself may be pretty temperature sensitive, so if its freezing out, and the ECU is also very cold, it may be outside its "operating range" for it to flash or read properly.. I know its weird, but there's enough info now that there's enough IX's on the road who are going through cold weather conditions and trying things.

I always work out of a heated shop, either my own or somewhere else, so its never something I had come across. I did have some sporatic read errors back when the IX was released.. I had attributed it to a bug in ECUFlash at the time, but it may be due to the same thing (low battery voltage)

 

OK, so I'm getting the same error message still..
[NO RESPONSE TO ANY KNOWN CODE]

I started the car and drove it around for about an hour, tried it again, and still nothing.
So then I hooked up charger to batt. and still, same error message.

ecuflash 1.30 -- fresh install never had 1.29 or lower.
Temp outside 80* so temp is not an issue.


I also have EVOSCAN and it works perfectly,
I logged a couple runs today and seemed to run fine.
so I'm kinda stuck here.

Please help. i've searched and searched here and tried everything except going to 1.29 and trying it..

Next ? would be, is where to get 1.29 from?

At first I thought ECU might be locked, from my AMS tune in Feb. 07...
SO I called AMS and they do not lock ecu's -- so.???


TIA

 

If it loops through and says "No response to any known code"

It can be one of two things..

The physical connector/wire from the tactrix cable to the white connector that goes to the white diagnostic port or the ECU is locked.

If the unlocker also doesnt work, then you have to look at a problem with the cable or physical connection. Even I got caught up in thinking I had a bad ECU when it turned out the Flash Init wire (the green wire going to the white connector) wasn't connecting to the ECU and triggering the flash mode.

If you never get to the point that it shows it trying to init different codes, then its a software/driver problem.

 

If you hear the clicking under the dash and the engine light comes on, it is safe to say the connections are good right?

 

Yeah if its clicks its probably getting far enough to trigger the flash mode on the ECU

 

Ended up being the "ECU was Locked"
Installed ECU unlocker thanks to aktivematrix.com and it opened right up.
Thank you for your help Malibu and others..

Talked to chris @AMS and he said he remembered it being locked and went around it and just left it that way.
Probably from my last DynoFlash. But it was easy to fix.

Next question, How do i keep it unlocked.
Isn't there a way to change the ID or something?

I remember reading about it somewhere.
Change something to 001 or something like that.
Can you tell me exactly how to do it, step by step.
TIA, Jamie

 

Yes, you can perminently remove it..

There is an item called INIT code I think its in the MISC group..

DO NOT MISTAKE IT FOR IMMOBILIZER CODE!!!

Write the old code down, just in case you inadvertantly changed something you shouldn't have.. then change the code from whatever it was to 0001
flash it to the ECU and the next time you read it, it'll be unlocked.

 

Thanks MJ..
You are the Man..