When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I have a 2001 C5 z06, i recently bought an OBDII scanner so I could diagnose codes on my own. The OBDII scanner powers on and everything when I plug it into the port, however, when I attempt to diagnose a code, the scanner will display "Communication Error" (as shown below). Typically this means one of three things; either 1) the OBDII port is bad and needs to be fixed/replaced 2) A sensor is shorted out causing the car computer to not communicate with the scanner or 3) All the sensors are fine and its the computer itself that needs to be replaced/re calibrated. I've attempted to fix this on my own.
I know my scanner is fine because I've used it plenty of times on my civic. I tested all the sensors in the engine bay one by one, they all seem to be working fine. I haven't yet opened up the OBDII port itself to see if there's anything wrong with it, but form the outside it looks fine- no corrosion or bent pins.
I'd rather not go to a dealership to get it looked at if I can troubleshoot and fix it myself. Any suggestions? I'm at a bit of a loss here. Not sure if there's anything else I should be checking that I haven't thought of. I really hope its not a computer issue- that would cost a lot of money to deal with. Thanks.
Why not just use the built in diagnostics in the DIC?
That would work fine except im planning on adding some bolt on's in the near future, i'd need a working OBDII if I wanted to get it tuned along with the mods.
That would work fine except im planning on adding some bolt on's in the near future, i'd need a working OBDII if I wanted to get it tuned along with the mods.
Go to Autozone and try theirs. Perhaps you have a communication error with your unit? That’ll tell you if there really is an issue with your port/Z or if it’s the scanner itself.
Go to Autozone and try theirs. Perhaps you have a communication error with your unit? That’ll tell you if there really is an issue with your port/Z or if it’s the scanner itself.
The suggestion got me thinking. I bought my z06 about 7 months ago, the guy I purchased it from got it smoged. As far as im aware, you cant get a smog check unless you have a functioning OBDII port, so maybe my unit is the problem after all. Or, OBD port/ computer malfunctioned in the time since.
I have a Launch creader and on my Mercedes C230 it will not read the codes and gives a communication error when using the generic obd2 mode.The one I have may be a little more advanced as it allows you to run in a manufacturer specific obd2 mode so it's able to read vehicle specific codes. when I use the vehicle specic mode I am able to read the codes. I would try another code reader, maybe bring it to an AutoZone or a auto parts store aand see if they can read the codes for you. If that fails the data line may not be connected or it's open some where since the unit is powering up.
Last edited by C5MSG2004Vert; Jan 28, 2020 at 01:32 PM.
Read the DTCs using the C5 Built in reader and see if that is showing a problem with the car. COMMS ERROR on one or more modules. Clear ALL the DTCs and then see if the comms error still exists.
Read the DTCs using the C5 Built in reader and see if that is showing a problem with the car. COMMS ERROR on one or more modules. Clear ALL the DTCs and then see if the comms error still exists.
This would give you a solid starting point.
Originally Posted by Pdbrains
I have a Launch Creader and on my Mercedes C230 it will not read the codes and gives a communication error when using the generic obd2 mode.The one I have may be a little more advanced as it allows you to run in a manufacturer specific obd2 mode so it's able to read vehicle specific codes. when I use the vehicle specific mode I am able to read the codes...
I have a Launch creader and on my Mercedes C230 it will not read the codes and gives a communication error when using the generic obd2 mode.The one I have may be a little more advanced as it allows you to run in a manufacturer specific obd2 mode so it's able to read vehicle specific codes. when I use the vehicle specic mode I am able to read the codes. I would try another code reader, maybe bring it to an AutoZone or a auto parts store aand see if they can read the codes for you. If that fails the data line may not be connected or it's open some where since the unit is powering up.
As it turns out, it was just my OBDII scanner. I took it to autozone and they were able to read my port just fine. Goes to show a cheaper OBD scanner may not be worth it after all...
I have a 2001 C5 z06, i recently bought an OBDII scanner so I could diagnose codes on my own. The OBDII scanner powers on and everything when I plug it into the port, however, when I attempt to diagnose a code, the scanner will display "Communication Error" (as shown below). Typically this means one of three things; either 1) the OBDII port is bad and needs to be fixed/replaced 2) A sensor is shorted out causing the car computer to not communicate with the scanner or 3) All the sensors are fine and its the computer itself that needs to be replaced/re calibrated. I've attempted to fix this on my own.
I know my scanner is fine because I've used it plenty of times on my civic kwp2000 code. I tested all the sensors in the engine bay one by one, they all seem to be working fine. I haven't yet opened up the OBDII port itself to see if there's anything wrong with it, but form the outside it looks fine- no corrosion or bent pins.
I'd rather not go to a dealership to get it looked at if I can troubleshoot and fix it myself. Any suggestions? I'm at a bit of a loss here. Not sure if there's anything else I should be checking that I haven't thought of. I really hope its not a computer issue- that would cost a lot of money to deal with. Thanks.
Last week I found that the OBD2 was not able to communicate with my car. I ordered a used instrument cluster in effrot to correct this issue, it arrived today. I installed it and nothing is different. so is it time for a new ECU/rebuild? I do know the ECU has been changed, infact I got two others with the car. If im going to get it rebuild I'd like to have the factory ECU back in the car... IS there anything else to check before spending 600 bucks to help the OBD2 communicate? or is it time to break out the wallet? and how might I tell which computer is the "right" one.
OBDII port "Communication Error"
This would give you a solid starting point.
