ScanGauge / OBD-II not ready

[ColonelPanic]

I've had my trusty SG-E installed in the Vibe for a couple of weeks. Immediately after instatllation, I scanned for codes (knowing there probably aren't any, no check engine light.) I'm pretty sure it was in ready status. I scanned again today for the heck of it and it now says:

No Codes
1 Not Rdy


Not sure what happened to make one of the monitors show not ready, there hasn't been anything happen to the car that would have caused that... No CEL cleared, no battery disconnect, nothing. I have no idea what exactly isn't ready, the SG will not tell me. I'm wondering if something is a little out of whack and it hasn't alerted us with a CEL yet. I suppose I'll find out soon.

Or maybe the SG just doesn't like this car. Scanning does seem a little weird on this car, I noticed tonight if I scan with the engine off/ignition on, it shows No Codes / Ready, but when engine is running it shows No Codes / 1 Not Ready. Any ScanGauge user care to tell me what mode you're using? It autodetected ISO. Just curious if I need to force some other mode.

And does anyone know off the top of their head what the criteria (drive cycles, etc) to get these things into Ready? It's not a big deal since there's no CEL, and this state does zilch for inspections so it would never put us in fail situation for not being ready. Still kinda curious.

[joatmon]

Can't find my scangauge manual at the moment, but I seem to remember some way to send a custom command, and get back some binary or hex response that could be mapped to identify which of the monitored systems was reporting a not ready status.

The number of cyles and the criteria for setting a code vary from code to code. If you had a specific code, I could say what the GM service manual indicates as the cycles/criteria to set that code, but there is no one size fits all answer, other than it takes a lot more cycles to clear a code than to set it in the first place

[ColonelPanic]

Thanks, Joatmon! Very true on the length of time it takes to clear one. Took my Hyundai about 500 miles one time to go back to ready after the check engine light went out on its own.

Unfortunately my SG-E is missing the piece that lets you send commands. Still have my original brick SG v1.0 around somewhere, it will do that.

This morning it sat there with "? Codes" when scanning for the first 30 seconds or so that the car was running. I kept recanning and eventually it shows "No Codes / Ready. So it fixed itself I suppose.

[joatmon]

Mine was throwing CELs for EVAP, and I tried a new gas cap, and that didn't fix it. Kept clearing the CEL with the SG. Then lately the CEL hasn't been coming on. Not sure what the problem was or what fixed it, but it went away so I won't worry about it. I'd probably take a similar "ignore" approach to your issue

[moongdss]

IIRC that means the carputer hasn't finished it's routine diagnostic cycle...

here's the ScanGuage E manual:
http://www.scangauge.com/wp-content/upl ... UM_101.pdf" onclick="window.open(this.href);return false;

And here's the bit from their FAQs:
When I scan the vehicle, it displays NOT READY
The vehicle has not completed its readiness Tests since the last time it was cleared or the battery was disconnected.

It will continue to say “NOT READY” until all on board diagnostic tests have been completed. This does not mean that it is not ready to be scanned. To get to this screen the vehicle computer reported that no Trouble Codes exist.