I was using Ecuflash 1.29 with the 1.3 tactrix cable and all was going well. I decide to try out 1.41 and I can flash fine, but now I have an SES light on. When I use the Display DTC function on Evoscan v2.1 after I flash with v1.29 I get a "Evo4 Diagnostic Codes: knock sensor". When I do the same scan after a flash with v1.41 I get: "Evo4 Diagnostic Codes:No Evo4 Diagnostic Trouble Codes Present."

I know Ecuflash v1.41 adds some knock tables that weren't editable in v1.29 so I was thinking the issue may the issue is stemming from that? By the was I have rom v88590015.

Anyone have any ideas?

 

i want to go to 1,41 as well but it keeps saying i need service Pack 3..lol

check the page where u downloaded ecuflash it has a description of the changes.

 

Yeah I checked the openecu.org list of updates (via Ctrl F). I found nothing when I searched for knock.

 

Upgrading EcuFlash doesn't change your ROM image, it just adjusts what you have the ability to change.

Older versions of EvoScan were notorious for not reading DTCs correctly; you might want to get upgraded to 2.5, or try Scantech instead.

 

Yeah I tried the display dtc function with Evoscan 2.5 but I get an error everytime. Logging with 2.5 works fine though so I am no sure what the fault lies with that one.

I am going to give scantech a try.

 

I need to mess around with scantech tomorrow but I tried to read with an accutron at advanced auto parts and it kept giving me an error so i am not sure scantech will yield anything better.

 

I have tried a variety of different things to get scantech to work it still wont connect
with Evoscan 2.5 this is what I get:

Info: Initialize Vehicle ECU...
Info: OBDII ISO Init...
Info: Waiting for vehicle ecu...
Info: Initializing At 5 baud...
Info: Initialization Complete...
Error: No Response from Vehicle ECU
Info: Check DTCs Complete.

I am all out of ideas. I can data log fine and since the car runs properly after flashing i am assuming the cable is fine (i flashed back to stock then reflashed back to current)

all of this started after my second time flashing using Ecuflash 1.41. The only thing I changed with that flash was I pulled one degree of timing in 3 cells. All of my other flashes with 1.29 never yielded any ill results. My most recent mod has been the Evo X Map sensor which I did a day or two prior to the flashing.

Any help would be greatly appreciated.

 

Try flashing in the previous ROM, and then reflashing again to your updated ROM.

 

ok, i will go out and try it and see what happens

I don't know if this helps but:
I know evoscan 2.1 is not known to be accurate for DTC's but this is what it gives me:
Updated: 09:49:26
Evo4 Diagnostic Codes:Barometric pressure sensor
Knock sensor

Updated: 09:49:58
Evo4 Diagnostic Codes:Vehicle speed sensor
Barometric pressure sensor
Knock sensor
EGR sensor

Updated: 09:50:37
Evo4 Diagnostic Codes:Injector circuit

Updated: 09:50:53
Evo4 Diagnostic Codes:Knock sensor
Fuel pump relay

 

I tried the reflash back to the previous and then the current. Still same results: No CEL on initial startup, i shut the car off and start it up again and the CEL reappears.

My dad was thinking it could be a arcing from a spark plug wire to the engine causing random codes the be thrown but I can't investigate this until it gets dark.

 

Could a bad MAP sensor be causing the ECU error that I can't read?

 

Nope. You'll just get a MAP sensor CEL.

 

Here is my modified xml file. It has the JDM MAP and 2-byte load additions. Does this look right?

I am trying to figure out if the error is my own. I can post the rom too if that will help.

 

Bump

What would cause the CEL to go off but the codes to not be readable?

 

The problem that you're having is very strange. You can flash the ECU, but every OBD-II scanner that you've tried to use will not connect? Or is it that the scanner can connect but gives no OBD-II code?