Hi guys!, my 1st post after the intro a few days ago. I just got a 1995 F22b1.

Briefly;
I'm getting a MIL code 12, (EGR), so yest. I disassembled the whole deal, cleaned ports etc. they were totally clogged. put it all back together, cleared the MIL with a batt. disconnect, and I'm about to do more on-road tests.
Doing all this because I think, but not sure, that the ECU is going limp mode due to this code. No other codes were stored.

/edit; I'm really only doing this because I think the ECU is going limp mode. If EGR code 12 does not do this, then disregard. The symptom I'm getting is lack of engine RPM's Does not easily go over 3k.

Separate question; Other than tapping a wire +LED to the VTEC solenoid to check operation, is there another way to check that it's functioning? -Would a malfunction on this system put a MIL code on the ECU?

Third and last; Has anyone used a regular OBD scanner, of any kind, using a 3-16 cable adapter or such, to check and monitor ECU/engine in real time? (not just codes).

Thanks for any feedback!

-Superfreak in Narcolandia.

 

Did the check engine light turn on while driving after cleaning the EGR ports?

A code 12 is set regardless if the the ports are clogged or not. Check the vacuum hose going from the EGR valve to the EGR controls. The vacuum hose is labeled #16 (I think) if it is still the OEM hose.

 

No, the test involved 60mph runs, and long downhills coasting (read that the ECU uses deceleration to monitor vacuum operation of EGR related points).

So, it cycled through operational heat level and down about 3 times. no codes. Yeah I read more about the possible causes of a code 12. Mostly it´s wrong vacuum level from any one of the monitored points.
Still, I have this idea that the engine is holding back. On my 2002 F23A1 I could cruise 100mph at just over 3k RPM, (I´m at 5k ft. not sure if that matters),
And this 2.2 seems to struggle to reach 90mph. Filters, spark plugs, oil, etc. has been checked.

Mostly I just want to ensure the ECU does not go into some mode that burns more gas, I didn´t get this car to race around.

Thanks!

-edit; picture of my previous Accord, a 2002, on the Mexican autobahn

 

Alright, so, no takers on the scanner tool. It´s ok Ireturned with gifts;

I found that the F22b1 uses the ISO 9141-2 K line communication standard.
I also found from ELM electronics, that their chip includes this, plus other 9 standards;

Elm Electronics Products - OBD ICs
(This page is their technical data source, not marketing or scanner models).

So, this means that any scanner that includes an ELM 327 or 323 IC (and only these two), is able to communicate with an Accord F22b1 ECU, given the correct OBD connector, (which the Accord does not have, but can be adapted).

2; Further to my EGR service adventures: I got the MIL code 12 again, but only when accelerating rapidly if the engine isn't warm enough. I haven't used a vacuum test to to check hose vacuum, but will.