"Not Ready" for OBD Emission test...? Topic is solved

Post by **utilityaudio** » 20 Dec 2016, 10:37

I just tried to get my Maryland Emission test (VEIP) done this morning, and didn't pass because they couldn't get enough information from the OBD Emission monitors.

they asked/said things like:
"are you having battery problems", "have you had any work done recently"
"you need to drive it regularly for a week then come back and get tested again"

I blew a fuse on Thanksgiving that took out all of my lights, I fixed it right away, and have driven 500-800 miles since then.
I don't drive the car regularly, it's a second car for us and I usually only drive it on weekends, typically 100 miles or less in a week.
I haven't disconnected the battery for any reason, though it did take me a few fuses to find the one that blew so maybe I reset something then (why can't fuses blow in the day-time when it's warm and dry out?).

thankfully they gave me an extension, but I've put 1.5~2k on the car since I purchased it, I hope there isn't a larger issue hidden behind the lack of data.

an OBD-II reader is on my list of tools to get, do I need to get it sooner rather than later? if yes, is there a recommended model/brand I should be looking for?

Thanks!

Post by **dyn blin** » 20 Dec 2016, 10:58

The P80 platforms are one of the early OBDII systems that may take some time to collect enough data to show "ready" for testing. Volvo's are not alone in this tendency, and some states maintain flexibility in testing protocols and readiness monitors. Maryland does not appear to be one of them.

Generally, the following driving cycle performed twice is sufficient to reset the monitors:

Start with the vehicle cool, below 122 degrees F.
Turn off the air conditioning.
Select a location where the driving can be done without violating traffic laws and you can stop safely at the side of the road.

1. Start the engine and accelerate to approximately 1500-2000 rpm.
2. Drive for 6 minutes at 1500-2000 rpm.
3. Stop the vehicle and remain at idle in drive for 70 seconds.
4. Accelerate to at least 45mph and drive for 5 minutes at 1800-2200 rpm.
5. Stop the vehicle and remain at idle in drive for 60 seconds.
6. Accelerate to at least 45 mph and drive for 4 minutes at 1800-2200 rpm.
7. Stop the vehicle and remain at idle in drive for 60 seconds.
8. Park the vehicle and turn off the engine.

Alternatively:

1.) Accelerate 0-50 MPH within 30 seconds
2.) Maintain 45-50 MPH for 20 minutes without using cruise control
3.) Park car turn off A/C idle for 5 minutes
4.) Accelerate 0-50 MPH within 30 seconds
5.) Maintain 45-50 MPH for 20 minutes without using cruise control
6.) Shut off car and allow to cool for 30 minutes before repeating cycle ( in some cases the car requires two cycles)

An OBDII reader is a must-have tool for any DIY diagnosis and repair, but unless there is a check-engine light, reading codes isn't your problem here, it's a lack of data from a recent reset.

Post by **utilityaudio** » 20 Dec 2016, 11:40

Thanks!
If I pick up an obd reader, can I double check that the car is ready to test before I go in?

Post by **850 LPT** » 20 Dec 2016, 12:40

utilityaudio wrote:Thanks!
If I pick up an obd reader, can I double check that the car is ready to test before I go in?

Yes you can, good idea.

98' Volvo's are notorious for taking forever to set all the monitors in ready mode. My XC took close to 5k miles to do so a few years ago

. Luckily, 97' and 98' are now totally exempt in my state from any monitor readiness. The last time I passed with 5 monitors not ready.

Post by **utilityaudio** » 20 Dec 2016, 13:06

will this Android/Windows OBD reader work or should I get a standard hand held one?

Post by **abscate** » 20 Dec 2016, 13:12

If you get a really cheap reader it might not let you check 'Monitor Readiness' which is the phrase you are looking for to find out if you are ready to inspect.

From a quick scan of the Maryland DMV website it looks like MD does NOT follow the EPA rule that allows you have to up to 2 monitors NOT READY like NY and most other states do. To clarify this, the EPA sets recommendations in place but not all states follow them in their inspection protocols.

Post by **utilityaudio** » 20 Dec 2016, 14:03

well it's not the cheapest (there's a couple that are <$20), and the amazon reviews are generally pretty good so I'm gonna give it a shot. one of the screen shots of the included software shows a monitor readiness test, so I'm hoping it'll do the trick. I'll know pretty quickly if this will work or not for my car... if not, I'll return it and get a more expensive hand-held model.

beigg · Post by **beigg** » 20 Dec 2016, 14:46

dyn blin wrote:The P80 platforms are one of the early OBDII systems that may take some time to collect enough data to show "ready" for testing. Volvo's are not alone in this tendency, and some states maintain flexibility in testing protocols and readiness monitors. Maryland does not appear to be one of them.

Generally, the following driving cycle performed twice is sufficient to reset the monitors:

Start with the vehicle cool, below 122 degrees F.
Turn off the air conditioning.
Select a location where the driving can be done without violating traffic laws and you can stop safely at the side of the road.

1. Start the engine and accelerate to approximately 1500-2000 rpm.
2. Drive for 6 minutes at 1500-2000 rpm.
3. Stop the vehicle and remain at idle in drive for 70 seconds.
4. Accelerate to at least 45mph and drive for 5 minutes at 1800-2200 rpm.
5. Stop the vehicle and remain at idle in drive for 60 seconds.
6. Accelerate to at least 45 mph and drive for 4 minutes at 1800-2200 rpm.
7. Stop the vehicle and remain at idle in drive for 60 seconds.
8. Park the vehicle and turn off the engine.

Alternatively:

1.) Accelerate 0-50 MPH within 30 seconds
2.) Maintain 45-50 MPH for 20 minutes without using cruise control
3.) Park car turn off A/C idle for 5 minutes
4.) Accelerate 0-50 MPH within 30 seconds
5.) Maintain 45-50 MPH for 20 minutes without using cruise control
6.) Shut off car and allow to cool for 30 minutes before repeating cycle ( in some cases the car requires two cycles)

An OBDII reader is a must-have tool for any DIY diagnosis and repair, but unless there is a check-engine light, reading codes isn't your problem here, it's a lack of data from a recent reset.

All that preemptive measures to exercise the systems in order to engage a readiness status for follow-on testing?

I see nothing wrong in releasing hydrocarbons or even inefficiently burn raw fuel into the environment for a emissions test.

Post by **abscate** » 20 Dec 2016, 14:50

You do the drive cycle only if you are trying " rush" the readiness cycle for an emission test. 99% of cars are driving around ready for emissions test at any time

Post by **utilityaudio** » 23 Dec 2016, 19:08

so, here are screen shots from my OBD scanner & app. sorry they're enormous, if there's a better way to attach photos, please let me know and I'll fix it.
Monitors

monitors continued

O2 Sensors

O2 Sensors continued

I did this before and after driving today (not the forced monitor readiness cycle posted above, I haven't had time for that yet) and they were the same.

how worried should I be that every row has an X for the Monitors?