General Question about System Readiness Tests

[joecar]

The N/A monitor means it is not supported...

if this did not report as ready then this adds to the number of not-ready monitors and the OBDII test would fail if you exceed 1 or 2 not-ready.


Each monitor has 2 state parameters: supported state, readiness state...
previous versions of EFILive software/firmware tried to combine both of those together
(which is why you would see N/A);

the newer software/firmware separates those 2 state parameters out...
to see this use the V2 BBL feature to view the monitor supported states and readiness states.


Also, use a 3rd party scanner to see this (all the not-supported monitors report as ready).


I don't have the CARB doc's (too much $$$), but Paul (the software/firmware developer) is following those doc's closely, which is why he made the recent V2 BBL firmware change.

[joecar]

Download/install the latest V7/V8 software, and install the latest V2 firmware, and use the V2 BBL feature to see this (under Scan Tool -> Diagnostics).

[Charles]

Each monitor has 2 state parameters: supported state, readiness state...
previous versions of EFILive software/firmware tried to combine both of those together
(which is why you would see N/A);

the newer software/firmware separates those 2 state parameters out...
to see this use the V2 BBL feature to view the monitor supported states and readiness states.

Ok then, this explains alot, thanks! So what I have inferred is that the setting under Diagnostic Enablers, then Diagnostic Tests affects the "supported state" parameter. Does this sound right?