Problems converting from P9k to OBD1, code20/22

jordancivic

#1 ◈ 2025-12-21

Hi guys,

Having issues with a uk spec B18c4, original ECU is a P9k ( obd2 ) and i have installed a OBD1 ecu from xenocron. Throwing codes 20/22 ELD/VTP. ELD is disabled in Crome but still throwing code, car drives but no vtec. If i try to remove VTP/VTS from the ROM i get a solid CEL and limp mode. Im assuming this is a wiring difference between the 2 ecus? This problem is present without any pass through harness etc.

Engine has no VPS. Crome P72 code. OEM engine.

Another strange issue with the same car, if i try to use my OBD1 passthrough harness the car wont start. The only connection on the harness that is cut is D14 for the wideband input, all other wires are straight through and present.

looking for help on this one guys.


EDIT - Jump d6-a4 for VPS ( i've done this loads of times, no idea why it slipped my mind )

Struggling with the ELD though, and why cutting d14 stops the car from starting.

jordancivic

#2 ◈ 2025-12-21

Hi guys,

Having issues with a uk spec B18c4, original ECU is a P9k ( obd2 ) and i have installed a OBD1 ecu from xenocron. Throwing codes 20/22 ELD/VPS. ELD is disabled in Crome but still throwing code, car drives but no vtec. If i try to remove VPS/VTS from the ROM i get a solid CEL and limp mode. Im assuming this is a wiring difference between the 2 ecus? This problem is present without any pass through harness etc.

Engine has no VPS. Crome P72 code. OEM engine.

Another strange issue with the same car, if i try to use my OBD1 passthrough harness the car wont start. The only connection on the harness that is cut is D14 for the wideband input, all other wires are straight through and present.

looking for help on this one guys.

jordancivic

#3 ◈ 2025-12-21

Re: Problems converting from P9k to OBD1, code20/22

For anyone reading this with the same problem -

Linked d6-a4 inside ecu and cleared ELD cel at the same time.

Anyone using a OBD1 ecu in a vehicle that was originally P9K or simular, IAB pin needs to be moved from A19 to A17


Havent bothered looking at my pass through problem, must be a missing wire and im not worried about it at the moment.

makelaras

#4 ◈ 2025-12-21

Re: Problems converting from P9k to OBD1, code20/22

Hello there,

I' ve done a convertion from obd0 to obd1 reinstalling from the begining a obd1 harness, obd1 engine (B16A Sir II) and jdm p30. I don't have the eld componenet install to my car and I get a code 20 (ELD) even if I disable eld from the Chrome.

You said that if I jumper the d6 with the a4 the problem will go away. Well... it only disables the code or the whole eld plattform on the ecu? Why I'm asking? Well, eld is an additional circuit that jdm cars have (mine is edm) that prevents the engine's rpm to drop at idling when there is varient electric load on the alternator. This is done by riching the mixture according the electric load at idle speed. If the eld component on the ecu continues to work, the mixture at idling will not be the apropriate in resulting high emissions and fail the emission test....

Am I correct?

jordancivic

#5 ◈ 2025-12-21

Re: Problems converting from P9k to OBD1, code20/22

Dont quote me on this, but -

What i got confused with was that i was getting a DASH CEL for VTP but in Crome it was showing 2 CELs ( ELD, VTP ). I spent a while trying to cure the ELD fault, but when i then jumped the ecu connectors to eliminate the VTP CEL, the ELD CEL went away too. When i then switched back to closed loop Crome showed the ELD CEL again, but the dash CEL didnt light up. This must be something to do with the makeup of the US/JDM OBD1 ecus which have ELD. eCtune handles this ELD CEL in the same way, ie will display in software but not light dash CEL, even if deselected in software.

Hope this helps.

gefi

#6 ◈ 2025-12-21

Re: Problems converting from P9k to OBD1, code20/22

Hi
I didn't quite understand is the car original OBD2 or it is something else ? Cause i have a b18c4 in 5gen Eg i did the wiring(obd0>obd1) my self and didn't have any of the above problems .... There were a few things that happened to me too ,one of them was that with the p28 the car works excellent(p30 base on crome) , but when i put the p9k the car won't start , still can't seem to find the problem(but now it doesn't matter :) )

jordancivic

#7 ◈ 2025-12-21

Re: Problems converting from P9k to OBD1, code20/22

I believe the P9K is OBD2, but shares the same plug arrangement as OBD1, you have to shave some tabs of the A plug. If its a UK car then it will have an immobiliser so thats probably why it wont start with the P9K.

If your using a P30 base then i assume your not using the IABs? If you want to use IABs i had to change Pin a19 to a17 and also check that the IAB solenoid has a ignition live instead of permanant ground ( your eg is prob ok as it will most likely be obd1 vehicle ). Also, IAB components need to be installed in the OBD1 ECU, im not sure if you can control IABs with the p30 code, i used the p72.

makelaras

#8 ◈ 2025-12-21

Re: Problems converting from P9k to OBD1, code20/22

Hello there,

I'll tell you what happened to my friends car, trying to help you. He has a '93 civic vti and recently he swaped it to b18c. He kept the obd1 harness and used a chipped p28 obd1 ecu.
When he uses an edm p30 based rom, everything is ok. When he uses a jdm p30 based rom he has check engine light, code 20/22 and no vtec engagging. So, maybe your problem is similar to this. Try different basemaps.

robban32

#9 ◈ 2025-12-21

Re: Problems converting from P9k to OBD1, code20/22

jordancivic wrote:
For anyone reading this with the same problem -

Linked d6-a4 inside ecu and cleared ELD cel at the same time.

Anyone using a OBD1 ecu in a vehicle that was originally P9K or simular, IAB pin needs to be moved from A19 to A17


Havent bothered looking at my pass through problem, must be a missing wire and im not worried about it at the moment.


Where do I find d6-a4 inside the ecu?

Bindegal

#10 ◈ 2025-12-21

Re: Problems converting from P9k to OBD1, code20/22

The 5-door UK made Civic VTI´s I have done needed to have the ignition output (for the distributor/ignitor) moved 1 pin to use a P28/P30.
Probably because the original weird ECU had an immobilizer and the OBD1 part didn´t.

It all seemed very OBD1´ish+immibolizer-like to me...

/Allan