So who wants their ECU's "Chromed"?

[Jesters Deadd]

I just remembered that Aaron had a very similar issue as this and the issue turned out to be his ECU adaptor pins for the front and rear 02 sensors were swapped.

Quick test: disable bit 2 of periphery 0 and flash the ROM to your ECU. Does this make the car run better?

We tested that. John had the same issue on his car.
@Goallie11 It would be faster to test the ECU and make sure its good before going over everything again, and again. And fill up this thread.

[Jesters Deadd]

Disabled that bit and it basically caused the rear o2 to stop cycling. In the 2 minutes or so that I let it run like that the wideband was right on 14.2-14.3 so that's better then the 17's it would be at before.

o2 feedback trims were at 12s though. No change to the fuel trims.

I don't have a multimeter to test the wires, but I should be able to get one easily.

You already tested that when you had the O2 cycling in evoscan and it didn't change the trims.

[Goallie11]

They asked so I let them know the results, but I will be taking it out today to ship to you.

[tfw a-ok]

I am running the Chromed ECU v1.0.1 and now at the point where after a couple of drive cycles the CEL comes on. I've check for errors with MUTIII and OBDII but neither can find a fault. EvoScan doesn't either.

My car is a '96 so I have no gas tank sensor which is turned off in the periphery bits. Full EGR is in place except I don't have the additional sensor true '99s have.

Is anybody else dealing with a similar issue or can offer a solution or diagnostic suggestion?

Thanks,
Tommy

[Monster Stealth]

I am running the Chromed ECU v1.0.1 and now at the point where after a couple of drive cycles the CEL comes on. I've check for errors with MUTIII and OBDII but neither can find a fault. EvoScan doesn't either.

My car is a '96 so I have no gas tank sensor which is turned off in the periphery bits. Full EGR is in place except I don't have the additional sensor true '99s have.

Is anybody else dealing with a similar issue or can offer a solution or diagnostic suggestion?

Thanks,
Tommy

I have had a similar experience pulling codes. What has worked best for me is to start and stop the datalogger in evoscan, then pull the codes. I have no explanation why this works, but I do have a high rate of success doing it that way.

[Greg E]

I have had a similar experience pulling codes. What has worked best for me is to start and stop the datalogger in evoscan, then pull the codes. I have no explanation why this works, but I do have a high rate of success doing it that way.

Same here.

The 2.9 evoscan file is uploaded. I just haven't posted the thread about it yet.

[tfw a-ok]

The 2.9 evoscan file is uploaded. I just haven't posted the thread about it yet.

How do I get it Greg?

[Greg E]

How do I get it Greg?

Click on the link in the first post.

[Jesters Deadd]

I have had a similar experience pulling codes. What has worked best for me is to start and stop the datalogger in evoscan, then pull the codes. I have no explanation why this works, but I do have a high rate of success doing it that way.

Same thing for the actuators.

[Jesters Deadd]

I am running the Chromed ECU v1.0.1 and now at the point where after a couple of drive cycles the CEL comes on. I've check for errors with MUTIII and OBDII but neither can find a fault. EvoScan doesn't either.

My car is a '96 so I have no gas tank sensor which is turned off in the periphery bits. Full EGR is in place except I don't have the additional sensor true '99s have.

Is anybody else dealing with a similar issue or can offer a solution or diagnostic suggestion?

Thanks,
Tommy

Sorry I may be braindead right now... What additional sensor?