OBD port no communication with ECU
#1
Honda-Tech Member
Thread Starter
Join Date: Mar 2013
Location: South FL
Posts: 287
Likes: 0
Received 0 Likes
on
0 Posts
OBD port no communication with ECU
Hello, H-T!
I just did an entire B16A swap with EK9 CTR ECU into my 98 hatch.
I swapped motor, transmission and the entire dash with full HVAC system as well. In total, I converted the whole car from OBD2a to OBD2b.
Before the swap, the OBD port communicated with the ECU just fine and I could pull codes with my bluetooth scan tool but now it will not communicate.
Details:
1. OBD port does get power, the bluetooth tool powers up and connects to my phone. Also check photo below.
2. CEL light works on the instrument cluster and does it's normal 'startup check' of the CEL illuminating for a few seconds then turning off again.
3. I know the CEL should be on because I don't have either o2 sensors plugged in.
4. ECU works normally. VTEC engages, everything on instrument cluster works, idles and drives like normal.
It is a genuine EK9 CTR ECU with factory markings and I looked up the serial number identifying it.
I used to pull codes fine but now I can't - maybe I missed a plug when doing all of the interior harnesses?
Need help!
I just did an entire B16A swap with EK9 CTR ECU into my 98 hatch.
I swapped motor, transmission and the entire dash with full HVAC system as well. In total, I converted the whole car from OBD2a to OBD2b.
Before the swap, the OBD port communicated with the ECU just fine and I could pull codes with my bluetooth scan tool but now it will not communicate.
Details:
1. OBD port does get power, the bluetooth tool powers up and connects to my phone. Also check photo below.
2. CEL light works on the instrument cluster and does it's normal 'startup check' of the CEL illuminating for a few seconds then turning off again.
3. I know the CEL should be on because I don't have either o2 sensors plugged in.
4. ECU works normally. VTEC engages, everything on instrument cluster works, idles and drives like normal.
It is a genuine EK9 CTR ECU with factory markings and I looked up the serial number identifying it.
I used to pull codes fine but now I can't - maybe I missed a plug when doing all of the interior harnesses?
Need help!
#3
Honda-Tech Member
Join Date: Jun 2014
Location: St. Louis, Missouri
Posts: 234
Likes: 0
Received 0 Likes
on
0 Posts
Re: OBD port no communication with ECU
When you were able to communicate with the ecu via the obd2 port, what ecu were you using? My understanding is the JDM ecu's won't work with the USDM odb2 ports or scanners.
#4
Honda-Tech Member
Thread Starter
Join Date: Mar 2013
Location: South FL
Posts: 287
Likes: 0
Received 0 Likes
on
0 Posts
Re: OBD port no communication with ECU
It's the same ECU I've always used for this motor. Could it be that the ECU is chipped or reprogrammed and maybe my scanner tool is faulty?
#6
Re: OBD port no communication with ECU
37820-xxx-xxx
Fill in the "x"'s.
Also, you can open the ECU case and see if it's chipped. If it is, that might be good information to provide instead of guessing whether it is or not.
#7
Honda-Tech Member
Thread Starter
Join Date: Mar 2013
Location: South FL
Posts: 287
Likes: 0
Received 0 Likes
on
0 Posts
Re: OBD port no communication with ECU
I am not experienced in ECU's. How can I tell if it's chipped once I look inside?
Trending Topics
#8
Re: OBD port no communication with ECU
Doesn't matter, the J11 says it's a JDM ECU so will not work with USDM OBD2 scanners as was stated earlier.
Thanks for providing the additional info.
But if you are still interested you can goto xenocron.com and see what and where the chipping goes on the ECU board.
Thanks for providing the additional info.
But if you are still interested you can goto xenocron.com and see what and where the chipping goes on the ECU board.
Thread
Thread Starter
Forum
Replies
Last Post
bk7794
Honda CRX / EF Civic (1988 - 1991)
6
05-29-2012 09:32 AM