I have an '00 y7 which I converted over to OBDI so that I could use hondata. I am using a p06 ECU. I am currently throwing a CEL but when I try and jump the connector, the CEL will not blink displaying the code. I also had access to a PGM tester that the honda dealerships use and when that was plugged in, it displayed, 'unable to communicate' with the ECU. I was wondering if anyone had any ideas of what could be wrong. Could it be the conversion harness I got for OBDII-ODBI has a wire backwards? Any other ideas are greatly appreciated.

Pfieff

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Pfieffdog &raquo;</TD></TR><TR><TD CLASS="quote">Could it be the conversion harness I got for OBDII-ODBI has a wire backwards? Any other ideas are greatly appreciated.
</TD></TR></TABLE>

All depends on who you got your harness from, the OBD-2 PGM tester will not work on a car that's using an OBD-1 ECU, so you'd need to put the OBD-2 ECU back in for that. Otherwise, you can check the CEL by jumping the pins on the jumper if the plug underneath your glove box doesn't work.

OBD-1 side
D4 to an ECU ground (like D21 or D22)

OBD-2B side
A10 to an ECU ground (like C7 or C18)

D4/A10 pins is your service check signal.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Pfieffdog &raquo;</TD></TR><TR><TD CLASS="quote">I also had access to a PGM tester that the honda dealerships use and when that was plugged in, it displayed, 'unable to communicate' with the ECU. </TD></TR></TABLE>
A scantool won't work with hondatas chip. My p28 wont flash codes either, not sure if it's supposed to with hondata. I just use my laptop to check for sensors out of range.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Chiovnidca &raquo;</TD></TR><TR><TD CLASS="quote">
A scantool won't work with hondatas chip. My p28 wont flash codes either, not sure if it's supposed to with hondata.</TD></TR></TABLE>

I wonder why that is. My hondata tuner told me that my IAC valve was what was throwing the CEL so I replaced that with a different one and the idle is still screwy and the CEL is still displayed. I don't get it.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Pfieffdog &raquo;</TD></TR><TR><TD CLASS="quote">

I wonder why that is. My hondata tuner told me that my IAC valve was what was throwing the CEL so I replaced that with a different one and the idle is still screwy and the CEL is still displayed. I don't get it.</TD></TR></TABLE>
The exact thing happened with my TPS sensor. I replaced it and it still throws the code even after I reset the ECU.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by GTlvr82 &raquo;</TD></TR><TR><TD CLASS="quote">
The exact thing happened with my TPS sensor. I replaced it and it still throws the code even after I reset the ECU.</TD></TR></TABLE>

Are you running hondata?

 

ttt

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Pfieffdog &raquo;</TD></TR><TR><TD CLASS="quote">I also had access to a PGM tester that the honda dealerships use and when that was plugged in, it displayed, 'unable to communicate' with the ECU. Pfieff</TD></TR></TABLE>

FYI, the obd2 scaner will not work when you use a obd1 ecu.