OBD Port not working with state inspection

[Ford Prefect]

I wanted to post this as a new topic as it doesn’t relate specifically to vagcom.

My car will not connect to a state inspection machine, I can however, connect to with both vagcom and EPL. On the inspections machine (NH) the power light comes on but it won’t talk.

The only thing offhand I can think of is the gauges. I replaced them between this and last inspection but did have component protection removed. I was wondering if this could be part of the problem or if anyone has experienced this before.

I’m kind of at a loss. I did pull the ecu out when I replaced the clutch line cable but didn’t disconnect it. It was just laid over out of the way.

The port also works with scanners and the inspection machine has worked on other cars.

Any ideas would be great!


Sent from my iPhone using Audizine

[onlyaudis]

try a different station. could be them and not you

[Ford Prefect]

That’s on the docket after tomorrow. Seems strange it would work on other cars though.


Sent from my iPhone using Audizine

[Ford Prefect]

I’m guessing this could be the issue. Anyone seen this before?? Vagcom couldn't connect to address 09 central electronics, airbags, or the steering wheel. My understanding is that the state maching verifies the VIN on all modules in the car.


Image1529529228.734753.jpg

Sent from my iPhone using Audizine

[Corradobrit]

Doesn't sound safe. You'd probably want to understand quickly why the signal from the airbag is not being received. Could be a cut wire, loose connector, short. Are the fuses good?

[Ford Prefect]

Doesn't sound safe. You'd probably want to understand quickly why the signal from the airbag is not being received. Could be a cut wire, loose connector, short. Are the fuses good?

Until the inspection I haven’t had any reason to check anything. The car runs flawlessly and has no alarms, warnings, or CEL. That’s what’s so strange.

I wasn’t even thinking that way, I was thinking glitch...damnit!


Sent from my iPhone using Audizine

[kelseysautobody]

Start with fuses but if you’re able to communicate with some modules and not others I don’t think it’s going to be that simple. Why did you change your gauges?


Sent from my iPhone using Audizine

[Ford Prefect]

Start with fuses but if you’re able to communicate with some modules and not others I don’t think it’s going to be that simple. Why did you change your gauges?


Sent from my iPhone using Audizine

I had the red display and hated it. I wanted the color Display. I guess I should say instrument cluster instead.

I need to check logs again to make sure it wasn’t a fluke. I was also thinking of flashing to stoke tune, although the tune is only ecu and shouldn’t really affect other modules. I’m just at a loss. I’ll start looking for fuses.

I appreciate the responses, thanks!


Sent from my iPhone using Audizine

[Ford Prefect]

Hey All,

I need to bump my own thread since I'm having this issue again. I finally realized that the my problem above was the CAN Bus, when I checked Vagcom it's status was NOT OK. It turned out to to be the actual connection at the port, its just not that great. Now I have what appears to be a different problem, the port powers up, CAN OK, but it still will not connect to the state machine. I can go straight to Vagcom and it works, just not the state machine. Its not as easy as going to another station but I won't get into that. Their machine works fine on other cars and this station is actually different than from two years ago.

Any help or ideas are appreciated!

Rich

[MSq5]

Hey All,

I need to bump my own thread since I'm having this issue again. I finally realized that the my problem above was the CAN Bus, when I checked Vagcom it's status was NOT OK. It turned out to to be the actual connection at the port, its just not that great. Now I have what appears to be a different problem, the port powers up, CAN OK, but it still will not connect to the state machine. I can go straight to Vagcom and it works, just not the state machine. Its not as easy as going to another station but I won't get into that. Their machine works fine on other cars and this station is actually different than from two years ago.

Any help or ideas are appreciated!

Rich

I don't understand why you don't try another station. If your VAGCOM connects and scans, the state station may well be the problem.

[Ford Prefect]

I don't understand why you don't try another station. If your VAGCOM cinnects and scans, the state station may well be the problem.

To be clear, this is the second station where I’ve had this problem. The light is lit but no comms. This station overlooks certain items which is hard to find.


Sent from my iPhone using Audizine

[MSq5]

To be clear, this is the second station where I’ve had this problem. The light is lit but no comms. This station overlooks certain items which is hard to find.


Sent from my iPhone using Audizine

You failed at two different stations after getting VAGCOM to connect? I'm just trying to eliminate any confounding variables.

[Ford Prefect]

You failed at two different stations after getting VAGCOM to connect? I'm just trying to eliminate any confounding variables.

Correct. But two one or years apart. It has proven oddly difficult to tell an inspection tech to put a little pressure on the connector like an old head phone jack/cord.

I can change my EPL tune and do everything go vagcom. It’s only the inspection machine. Shows powered but no comms. It’s stupid, really.


Sent from my iPhone using Audizine

[theverge]

As a person with no inspections, what is the purpose of the obd2 connection during the inspection process?

[Ford Prefect]

As a person with no inspections, what is the purpose of the obd2 connection during the inspection process?

They use it to check emissions, O2 sensors and such. We don’t have tail pipe checks where I am.


Sent from my iPhone using Audizine

[Smac770]

https://dmv.ny.gov/brochure/what-do-...cars-not-ready

The engine has a number of OBD-II tests it runs and monitors, when they pass, readiness bit for that test is set. When they fail, I assume the readiness bit for that test is unset. When you clear codes, all readiness bits are unset. Which is why you can't just clear codes to remove the MIL and go straight to your emissions test (here in GA, if your MIL is on, they fail you regardless of your readiness bits status).

So the emissions test computer is just reading the readiness bits and the MIL status as a cheap shortcut to doing an actual tailpipe emissions validation.

[MSq5]

https://dmv.ny.gov/brochure/what-do-...cars-not-ready

The engine has a number of OBD-II tests it runs and monitors, when they pass, readiness bit for that test is set. When they fail, I assume the readiness bit for that test is unset. When you clear codes, all readiness bits are unset. Which is why you can't just clear codes to remove the MIL and go straight to your emissions test (here in GA, if your MIL is on, they fail you regardless of your readiness bits status).

So the emissions test computer is just reading the readiness bits and the MIL status as a cheap shortcut to doing an actual tailpipe emissions validation.

What I think you just said is that after clearing the codes, you need to drive around, perhaps 25-50 miles to allow the ECU to return to readiness set. If a fault still existed, the code would be retriggered, if not, it is ready to be tested.

In OPs case, he seems not to be able to even connect to the state test equipment and "handshake" because of a loose fitting OBD-II port.

[Ford Prefect]

What I think you just said is that after clearing the codes, you need to drive around, perhaps 25-50 miles to allow the ECU to return to readiness set. If a fault still existed, the code would be retriggered, if not, it is ready to be tested.

In OPs case, he seems not to be able to even connect to the state test equipment and "handshake" because of a loose fitting OBD-II port.

You are correct. I’ve hit that snag before and sneezed like 100 miles before everything reset.

The guy even connected with a code reader and it read fine. Just not the state machine. I’m gonna suck it up and take it to another shop and see what happens.


Sent from my iPhone using Audizine

[Smac770]

What I think you just said is that after clearing the codes, you need to drive around, perhaps 25-50 miles to allow the ECU to return to readiness set. If a fault still existed, the code would be retriggered, if not, it is ready to be tested.

I can clear DTCs and be ready by the time I reach the test station 10 miles away because of the type of drive. Key considerations are to have a near full gas tank and do at least a few miles at a steady 45-60 range, or you won't get the EVAP readiness bit.

In OPs case, he seems not to be able to even connect to the state test equipment and "handshake" because of a loose fitting OBD-II port.

I was responding to theverge's question about the point of the OBD-II port in an emissions inspection, rather than the OP.

On the OBD connector, it's 12v on 1 and 16, ground on 4 and 5, airbag module on 15, and CAN bus on 6 and 14. That CAN bus connection goes directly to the J533, so the state of anything else in the car should not create a problem. If the plug is physically worn, it might be worth replacing it, and checking the pins for tightness while they are depinned. plug is 3A0972695A, typical Audi, who knows what the pins are. Or maybe just try an extension cable to see if the state system makes better contact with it, if it's been shown just jiggling it resolves the comms issue:
https://www.ecstuning.com/b-p3-gauge...p3obdflex~p3c/

[Ford Prefect]

@Smac770 thanks, I have an extension and will give that a try.


Sent from my iPhone using Audizine