97CLgenius

Stats of my car:

-JDM H22
-P13 ECU (Stock) OBD1 connected with a Piggy Back Harness
-So that's OBD 2 converted to OBD1 in simple words
-Field AFC/VTEC Controller (Map sensor currently disconnected)

Maryland emission Law:
97+ years with ODB 2 connections are connected to a diagnostic machine to tell what's wrong with the car. It check for Tampering with ODB plug, CEL Light, and ODB communications.

Where I failed:
My car failed on OBD 2 communications (I am assuming this because of my swap converting the OBD 2 to OBD 1 for the ECU) Basically the computer is trying access an OBD1 ECU and it's failing because the OBD 1 ecu was not made for that type of diagnostics.

Has anyone had this problem? If so, do you know of a way to wire up the OBD 1 ECU to communicate with the OBD 2 adapter/diagnostic machine? I honestly think I am assed out but I was thinking I could purchase a used OBD 2 ecu and connect it to see if that works, but I doubt it because that motor wired up OBD 1.

TexasHonda

You have a better chance at winning the lottery than an OBD1 talking to an OBD2 scanner. Easiest fix is to go back to OBD2 w/ a replacement or original ECU and harness.

good luck