MatterMatt

I have a 96 Civic EX with a 96 JDM ITR Swap (using the ITR OBD2 ECU). When ever I plug in a scan tool or engine sensor monitor I get a no communication message.

Yes, the key is on and the cable is plugged in. I have tried 3 different scan tools and 2 ecus. I ran a new wire for the K-line figuring the wire was likely shorted somewhere, but its still a no go. There is power at the scan tool power line. The only other thing I can think of is the DLC plug connections are bad, but you can't buy a plug only, and I don't know of anyone with a junk harness that would cut one off. I've asked the other techs in my shop and they say bad K-line, but it's working fine. Only one of them has had to fix this problem, but it was the K-line. The helms sucks for troubleshooting this problem, and the tests it does have I have already done and they check out fine.

Has anyone successfully repaired this problem? If so let me know what you did. Please, only post a response if you ACTUALLY have experience repairing this problem. I'm not interested in speculation or guesses. I don't mean to be a jerk, but I need real answers. It's not a huge issue because I can always jump the scs connector to flash DTCs. It just bothers me.

sicones

are you trying JDM ecus?? a JDM ecu will never communicate with a scan tool, totally different protocols

HCivicSi23

The reason it wont read is because your using a Japanese ECU.

MatterMatt

I tried both a JDM and a USDM ecu.

HCivicSi23

The USDM ecu will not work on a JDM motor. You need a conversion harness.

MatterMatt

Yes, I understand that. But I had the same problem with the stock ecu and motor. Anyway, why would you need a conversion harness to run a USDM ecu? Are the connector layouts or plugs that different? Yes, I know the USDM and JDM motors have different VTEC solenoids and so on and so forth...I know the JDM and USDM protocols are different, but didn't know the difference in much detail. Please educate me or point me in the right direction (just for piece of mind).

Another reason I asked is, although the US scan tools won't communicate with JDM ecus, I was told by a pretty big name shop (that will remain anonymous) that a Racer data display would work with my set up because it pretty much just sends a datalist. So that left me with figuring out my no communication fault with the previous and current set up to make the display work.

Has anyone fixed this problem before? Yes or no, and what did you do? To make it a simple question, just a no communication problem on a bone stock 96 civic (because I had it before the swap anyway).

HCivicSi23

When you swap a USDM motor for a JDM motor, you are elimintaing certain sensors that were manufactured specifically for the USDM motor. For example, the oil crank position sensor is in the USDM motor but not the JDM. This is the biggist cause of cars failing there emissions tests.

When you run a JDM motor, you cannot use the USDM ecu. You have to use the JDM ecu that came with it for full functionability. Other people have had this issue and you can buy a conversion harness to change its obd conversion as well as allow a diagnostic scan tool to read the JDM ecu. I am not 100 % positive on all this because I have not had the problem myself, but I have had friends with similar issues.

xXSilentScreamXx

srry 2 thread jack but i have a jdm h22a in my 96 ek can i use a chiped usdm p28 if i get an obd1-obd2a harness ?

01_CLtypeS

iTrader: (1)

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by MatterMatt &raquo;</TD></TR><TR><TD CLASS="quote">I have a 96 Civic EX with a 96 JDM ITR Swap (using the ITR OBD2 ECU). </TD></TR></TABLE>

the ECU should be OBD2a i have the 00 spec itr in my 99 coupe, pretty sure that its OBD2a steve at Hmotorsonline also said it should be OBD2a