08-22-2010, 07:22 PM | #31 | |
WSB Champion
Join Date: Nov 2008
Location: Anaheim, CA
Moto: 2009 Kawi ZX6R
Posts: 5,570
|
Quote:
The 1999 Expedition is OBD2.
__________________
Train Hard Ron Paul - 2012 Mark of Excellence GM |
|
08-22-2010, 07:32 PM | #32 |
Crotch Rocket Curmudgeon
Join Date: Nov 2008
Location: Here to integrity
Moto: Li'l red baby Ninja
Posts: 7,482
|
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...
__________________
Insert free thought here. Last edited by Avatard; 08-22-2010 at 07:39 PM.. |
08-22-2010, 07:50 PM | #33 |
WSB Champion
Join Date: Nov 2008
Location: Anaheim, CA
Moto: 2009 Kawi ZX6R
Posts: 5,570
|
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.
__________________
Train Hard Ron Paul - 2012 Mark of Excellence GM |
08-28-2010, 06:43 PM | #34 |
Crotch Rocket Curmudgeon
Join Date: Nov 2008
Location: Here to integrity
Moto: Li'l red baby Ninja
Posts: 7,482
|
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: 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?
__________________
Insert free thought here. Last edited by Avatard; 08-28-2010 at 07:07 PM.. |
08-28-2010, 08:10 PM | #35 |
Chaotic Neutral
Join Date: Feb 2008
Location: Cherry Hill NJ
Moto: GV1200 Madura, Hawk gt
Posts: 13,992
|
Convert to carbs, fuck it
|
08-28-2010, 08:32 PM | #36 |
Crotch Rocket Curmudgeon
Join Date: Nov 2008
Location: Here to integrity
Moto: Li'l red baby Ninja
Posts: 7,482
|
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!
__________________
Insert free thought here. |
08-28-2010, 11:43 PM | #37 |
WSB Champion
Join Date: Nov 2008
Location: Anaheim, CA
Moto: 2009 Kawi ZX6R
Posts: 5,570
|
You have a DTC 36...so get a service manual and start diagnosing it.
Man do I have to tell you everyting?
__________________
Train Hard Ron Paul - 2012 Mark of Excellence GM |
08-28-2010, 11:47 PM | #38 |
Crotch Rocket Curmudgeon
Join Date: Nov 2008
Location: Here to integrity
Moto: Li'l red baby Ninja
Posts: 7,482
|
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.
__________________
Insert free thought here. |
Bookmarks |
|
|