My car just started idling wierd. I took it out for a run, and threw a code. As usual, I pulled over, checked the code, and reset the ECU. I drove it on the freeway, and no code came back. When I got to my destination, I noticed that it was idling like total sh*t, but no code was being thrown.

It's an 01 GSR with JRSC running on the FMU and black box. I read that this "sensor" is in the ecu. It seems like I'm still having issues, but no CEL is being displayed.

Ideas on this issue, guys?

 

5 minute search.

https://honda-tech.com/zerothread?id=2074648

https://honda-tech.com/zerothread?id=2070269

https://honda-tech.com/zerothread?id=2067271

https://honda-tech.com/zerothread?id=2064721

 

If you paid any attention to the I think he was stating he was nonplussed with the results - nobody seems to know.

Only time I've experienced a CEL 13 is on 88-89 HF running a non-HF MPFI ECU; people claimed they were plug and play compliant with PM6 and (especially) PR4, but you got a bunch of wierd codes and wierd quirks until a couple of the pins were disconnected. Keep in mind I've probably fixed more CELs, and taken on and fixed more problem wiring cars, than anyone else you're going to get a reply from in this thread - I don't know wtf is wrong with your car, but I do know I'd grab the Helms for your car as my starting point.


I mean, you certainly aren't going to fix the car by demanding answers on message forums and copping attitude when you don't like the response.

 

Well....I took it as a smartass answer suggesting to use the SEARCH function. If it was intended another way, I apologize...but that's how I took it and I reacted that way b/c I HAD searched.

I intend on putting an s300 on it and getting a street tune...damn thing is running PIG rich on the FMU & black box. Maybe that will fix the issue.

 

code 13 barometric error should be generated via the map sensor. I used to get that when I was running OBD2 on the AFC Hack back in the days... I fixed it via switching to OBD1.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by C_Rock77 &raquo;</TD></TR><TR><TD CLASS="quote">Well....I took it as a smartass answer suggesting to use the SEARCH function. If it was intended another way, I apologize...but that's how I took it and I reacted that way b/c I HAD searched.

I intend on putting an s300 on it and getting a street tune...damn thing is running PIG rich on the FMU & black box. Maybe that will fix the issue. </TD></TR></TABLE>

if you are goin with the s300, you can disable the baro anyway.

 

You're fine, bro. Misunderstandings happen.


With the OBD1 conversion I expect you won't even need to disable the PA (baro). It's implemented in a more straight forward fashion in OBD1 than OBD2; OBD2 operation is basically OBD1 with a lot of complex emissions cross-checks and diagnostics programmed in. Look at the bright side, it's just a good excuse to get tuned!

 

I take it a post or two was deleted?

 

Does this code cause the car to go in Limp mode?

 

Not in the limited experience I have with CEL 13 and OBD0 ECUs. Apples to orangutans for your situation... like I said, and I'm still sorry I can't offer a solution, nobody seems to know.