Checking for Error Codes

[tox]

Hello,

I apologize in advance if this is in the wrong section or if I've misunderstood something. I was driving along the other day in my Holden Commodore VY and when I gave the car a bit of gas the check engine light came on, there didn't seem to be any obvious problems but I decided to stop the car for a few seconds and turn it off, I turned it back on and off I went no problem. When I got to my destination I checked fluids, everything looked okay.

So I figure no problem probably a failing sensor, I'll just check for error codes. Little did I know that on the VY you can't check for codes the old fashioned way using a paper clip, it requires a tech2.

So in my search for an alternative to buying a tech2 or taking it to a dealer I've come across this site. I've read around and looked at some helpful guides posted on here, but it mostly seems to be about tuning and modifying the on board computers so I wasn't quite sure if it was possible to check for error codes using a USB ALDL connector and some software as there doesn't seem to be a guide to it, or I've misunderstood something.

Basically my question is can I use a USB ALDL connector such as this one, some software such as TunerPro, the VY PCM ADX file, and my laptop to read error codes and diagnose my problem? Also, will that ALDL connector work with a Holden VS?

Both my VY and VS Commodores have the N/A V6 Ecotec engine.

Thanks.

[Holden202T]

yeah that should be fine.

you might find with that code it could be like o2 sensor rich or lean and clears on power cycle, but if you can log and get the code to display then read it before turning the car off should be all good.

either way yes tunerpro with that interface should do what you need.

also down the track if you wanted to tune realtime you can get a nvram for the VS and off you go, and i believe the VY if flash pcm so should be able to do it with just that interface and tools available here (someone can probably confirm this for me ?)

[tox]

yeah that should be fine.

you might find with that code it could be like o2 sensor rich or lean and clears on power cycle, but if you can log and get the code to display then read it before turning the car off should be all good.

either way yes tunerpro with that interface should do what you need.

also down the track if you wanted to tune realtime you can get a nvram for the VS and off you go, and i believe the VY if flash pcm so should be able to do it with just that interface and tools available here (someone can probably confirm this for me ?)

Thanks for the quick reply Holden202T. Are you saying that certain codes clear after the car is switched off? If so, I will have to try and get the Check Engine Light to come on again while TunerPro is connected to my VY, right?

Does TunerPro just grab all the data and then give you the option to save it so that I can investigate it/upload it later or do I have to investigate while the car is still on and my laptop is plugged in?

Thanks for the info.

[Holden202T]

some codes will stay up till cleared and others will self clear after a certain amount of time without the error coming up again ... this depends on how critical they are etc.

but if you have the laptop logging at the time it should show in the logs, or if it comes up just don't turn the car off before you plug in and check it

[tox]

No worries. Thanks for the help mate, appreciate it.

[tox]

Alright so I got the ALDL cable thanks to VL400.

And I think from what I can gather my left 02 sensor is running lean, and there's some communication problems to my fan. If anyone would be kind enough to take a look at my log to see if I'm correct, and if there seems to be any other abnormalities in the way it's running, I would really appreciate it.

Also, is there some figures I can find that my car should be in range of? I'd like to check if there is any sort abnormalities in my VS. Cheers.

[The1]

yes it appears your left, passenger side o2 is faulty, though really need to go for a drive to properly see if the sensor is not working but seeing the fault code is logged is a good indication. Your right side o2 is getting crosscounts and looks ok and the left has none and is just flat lining. So i would be looking at replacing the left o2 sensor.

The fan Fault code is normal when you are datalogging as the bcm cannot talk to the pcm. Once unplugged the fault code will go away.

There is a getting started to datalogging guide here which may give some extra hints.
https://pcmhacking.net/forums/viewtopi ... =10&t=2223

[tox]

yes it appears your left, passenger side o2 is faulty, though really need to go for a drive to properly see if the sensor is not working but seeing the fault code is logged is a good indication. Your right side o2 is getting crosscounts and looks ok and the left has none and is just flat lining. So i would be looking at replacing the left o2 sensor.

The fan Fault code is normal when you are datalogging as the bcm cannot talk to the pcm. Once unplugged the fault code will go away.

There is a getting started to datalogging guide here which may give some extra hints.
https://pcmhacking.net/forums/viewtopi ... =10&t=2223

Thanks for the info The1, I had a feeling it was just a sensor buggering up. And yeah I had a read of the datalogging guide and seemed pretty straight forward. Is there any more documentation that I might be able to find? Something a little more technical so I can get a better idea of what I'm looking at when it comes to some of these graphs and readings? I'd just like to be able to tell if something is outside of operating range for myself without having to bug you lot .

I'd really like to investigate my VS as that seems to be idleing a bit rough and chewing fuel, the fuel pressure regulator is suspect as the tip coming off it that connects to the vacuum hose is a little wet, and my plenum chamber is a extremely clean (I think the intake has been sucking in fuel and in effect "cleaning" my plenum).

[The1]

no other guides yet, we are building a FAQ page as we go which may have some things in it your looking for. But atm just reply in your thread here and we'l endeavour our best and perhaps add reference to things mentioned here in the FAQ

https://pcmhacking.net/forums/view ... f=7&t=1396

[tox]

No worries. Well like I said, the VS seems to be running a bit strange, it has so since I bought it. I was hoping that an ALDL cable and some logging software might be able to point me in the right direction. Maybe some adjustments are needed or there is something a fault code won't tell me. I've taken it for a drive and recorded it. Maybe you or somebody could help me out with this and take a look if you have a bit of time, and hopefully point me in the right direction so that I can investigate further.

It's a N/A V6 Ecotec VS, no mods as far as I know. I used the $51 VS V6 Engine and Trans v1.10 WB 14.7kit.adx logging configuration file. If there's anything notable in the log file please let me know, cheers. Also, the last few minutes of the recording it is in idle for a little while, and I also shifted between all the gears. My trans seems to be a little clunky, or maybe it's normal for the age and K's for the car. 16 years and 172,000ks.