I burned a few chips to find out that I keep getting a CEL that I can't read. The ECU was already socketed running off another rom. I put that rom back in and everything works fine with it. What could I be doing wrong?

 

sounds like it isn't burning the chip.

 

Make sure that you are removing the check sum routine. What program are you using? crome uberdata?


Rob

 

Maybe some sensors need disabling - knock, pa, etc.

 

I'm running uberdata. The car drives fine with the CEL.

I probably still need to disable knock but shouldn't I be able to read that code? What is PA? Are there any other sensors that need disabled?


Modified by hoggy at 9:06 PM 12/1/2003

 

As long as you are running a USDM ECU, then you only need to disable KS for the non-P72 Civic/Integra ECUs.

CEL 0, meaning you can't pull codes, is a sign that your ECU is in limp home mode, you should run a little rough and have a lowered revlimit - if you are actually running fine, then there is something wierd with your jumper wiring that you check codes with.

You may want to verify that you have the willem correctly set up for 27C256 or 29C256, or whatever chip you are using. It was my understanding you had to set the willem unit up funny to get it to work with those.

 

I had the jumper in place for the willem burner which is what I think you are referring to.

My car still engages into VTEC but I can't pull the code. Any other ideas? Could I be doing something wrong while burning?

 

There is something wrong with the program, chip speed, something. Have you tried burning a stock program and seeing how that runs?