Luke Nutkicker

I sent my car to a guy to perform an engine swap for me, he also installed a Rywire OBD1 engine harness for me. When I sent it in both the DLC and the Check engine light worked. When I got it back the Check engine light wouldn't come on even when I knew I was throwing a code. I took it to another shop and they replaced the bulb in the cluster and it still didn't work. They saw the bundle of cut wires by my ECU and pinpointed that as the culprit of my check engine light not illuminating. They reattached the proper wires and the Check engine light began to work.We didn't have the time to take care of all of the cut wires so I left it for later.

Now when I try to connect my OBD2 scanner to the DLC it's unable to read my ecu. Even though I have an obd1 harness I do have a obd1 to obd2a jumper harness, so it should be able to read my ecu but it doesn't. Even when I try to jump the blue dlc the check engine light doesn't blink. Does this bundle of cut wires have anything to do with it?

civic402lx

Uh obd1 does not use the obd2 port. You converted to obd1 therefore, it will not work. Your setup is now consider as an obd1 car. Not obd2 like original.

Rywire have extra wires as aux so you can run extra sensor in the engine bay that way you do not need to run extra wires. Cleaner look.

Luke Nutkicker

Thanks for the reply. However, that would explain why I wouldn't be able to use the port where an OBD2 scanner would hook up to. I can't even jump the blue connector to read the number of CEL flashes.

civic402lx

You should be able to read the code from the blue connector. Im not positive on why you cant.

mk378

The OBD1 blink code jumper is just one wire to the ECU and the other wire is ECU system ground. So that should not be hard to trace out with a schematic.

When the jumper is closed but there are no codes, the CEL should be on steady all the time the key is on whether or not the engine is running.