Two Wheel Fix

Two Wheel Fix (http://www.twowheelfix.com/index.php)
-   Cage Hell (http://www.twowheelfix.com/forumdisplay.php?f=93)
-   -   Anyone here a C4 guy? (http://www.twowheelfix.com/showthread.php?t=15918)

101lifts2 08-22-2010 06:22 PM

Quote:

Originally Posted by Avatard (Post 402792)
Geez, I dunno...the standard D-shaped connector. Same one on my '99 Expedition...the standard ODB2....

1984-1993 Corvettes used the OBD1 12-pin D shaped connector. 1994 and 1995 used the OBD1 system as well, but was equipped with the OBD2 16 pin connector. These cars are still OBD1, not OBD2. I doubt if the Actron scanner will work on your car as I think the controller uses UART communication, not J1850 Class 2.

The 1999 Expedition is OBD2.

Avatard 08-22-2010 06:32 PM

The scanner works, it talks to the animal, it uses the regular ODB2 connector...

Now, I do have the top of the line Actron, which, like I said, even has ODB1 cables and other early proprietary cables in the kit as well, it may fall back to whatever communication standard is required...but it does recognize it by name, and retrieve codes...

101lifts2 08-22-2010 06:50 PM

Unless the codes are designated as PXXXX, it is not OBD2. And I think if all you needed was to flash codes you could have done that through the IP cluster. IIRC.

Avatard 08-28-2010 05:43 PM

Took it out again today. It's nice and warm, and dry, so the likelihood of moisture in the Optispark would be nil.

It ran OK at first, and started running increasingly like shit as it got hotter.

I removed the MAF connector, and restarted. Same shit...only, of course, now it threw a code for the MAF.

I reset the codes.

Did some reading on a Vette forum while the POS cooled.

According to what I read, it could be the ECM, the ICM, the Optispark, the MAF, the O2 sensor, or aliens from space...or a chafed harness, or bad connection.

I pulled every fucking connector I could find, inspected, and sprayed every contact with Deoxit D5 (best contact cleaner on the planet). It seemed to improve a bit, but is still throwing codes:

http://poopnugget.com/files/vettecode1.jpg
http://poopnugget.com/files/vettecode2.jpg
http://poopnugget.com/files/vettecodes.jpg

I'm at wit's end with this piece of crap. To read the Vette forum is to have nothing but pity for LT1 owners. GM owes a lot of people an apology.

This thing is pure fucking crap. I want a 68-72 with no fucking computer.

Anyone wanna trade?

Dave 08-28-2010 07:10 PM

Convert to carbs, fuck it

Avatard 08-28-2010 07:32 PM

Update:

Went out and restarted it. ASR indicator on dash went out, engine still runs rough.

Check engine light is out, but it still throws code 36 (WTF?).

Let's here it for GM's random fucking computer bullshit!

Yay!

101lifts2 08-28-2010 10:43 PM

You have a DTC 36...so get a service manual and start diagnosing it.

Man do I have to tell you everyting?

Avatard 08-28-2010 10:47 PM

It comes and goes...that's the weird thing.

It seems to throw codes (and light the ASR service light) rather fucking randomly.

I'm still not entirely convinced it isn't something else. On the vette forum I was reading, other people with this (and other) codes were reporting it being any number of five or six possible things...ECM, ICM, Opti, etc.

The error messages seem to be about as relevant as MS error msgs.

Did Microsoft write GM's code, by any chance?

This is pure shit.


All times are GMT -4. The time now is 11:52 PM.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, vBulletin Solutions Inc.