Diagnostic Troubleshooting

[Quinn5150]

So recently I went to start my 10th gen civic and it turns over but doesn't start. I hook up the diagnostic tool and it throws literally 59 codes a lot of them having to do with communication failures so I am wondering what my next step should be? Say I erase the codes but since my car won't start I can't do a test drive after so I'm lost...

 

[dt10g]

I can't speak to the code situation,
but the only time my car has turned on but not started was when the Immobilizer was activated...
I believe after hooking the battery up again after some maintenance.

In that case, I just get out, lock the car & unlock the car with the key fob buttons, get in, give it a sec, step on the brake hard and start the car.

Sorry if that is pretty useless advice, but since it would cost you no time and effort to try it... may as well. Or at least have a look at the immobilizer light on the dash

 

[sbace_hamb]

If what dt10g recommended doesn't work, it could be your battery. The battery running low will cause all sorts of sensors to be unhappy and report issues.

 

[KensBlueGenX]

As a starting point, ignore the U0xxx codes, they are likely just a byproduct of the main issue.

What are all of the Cxxxx and Pxxxx codes found?

 

[Quinn5150]

As a starting point, ignore the U0xxx codes, they are likely just a byproduct of the main issue.

What are all of the Cxxxx and Pxxxx codes found?

Would those Uxxxx codes be able to have an effect on whether my car was able to start though? The only P codes are from before this whole issue started (P0498) attached is the report

 

[KensBlueGenX]

U codes are generally a communications error and are generally just a side symptom. Solve the core issue, e.g. the P0498 code, and generally the U (and C) codes will then clear too.

Sponsored