Data Filter for OL nly in ScanTool

[Chalky]

Can someone suggest an easy filter to capture data when in OL and CL? I know I can create a filter based on OL triggers when in CL, but is there a common filter that I can employ whether I am logging in OL or CL?

[joecar]

Would logging the FUELSYS pid work for this...?

[Chalky]

Joe:

I would think so much like CL/OL indicator on a dash page. I just don't know how to configure it.

After looking at a dash page, it looks like a value of 4 would indicate OL when using fuelsys A map. Sound right?

[mr.prick]

i too would like to know how to filter out CL with my RR.
this way fuel can be added or subtracted in the VE table for wot runs.
but left alone during cruising.

[joecar]

Joe:

I would think so much like CL/OL indicator on a dash page. I just don't know how to configure it.

After looking at a dash page, it looks like a value of 4 would indicate OL when using fuelsys A map. Sound right?

Yes, I just played around with it in the status properties of that pid... it seems:

FUELSYS B, Bank 2 (low byte):
1 = OL
2 = CL 
4 = OL-Drive
8 = OL-Fault
16 = CL-Fault

FUELSYS A, Bank 1 (high byte, i.e add 256 to each of these):
1 = OL
2 = CL 
4 = OL-Drive
8 = OL-Fault
16 = CL-Fault

[joecar]

I assume that A = Bank 1 and B = Bank 2.

[SSpdDmon]

If you're monitoring FTC#, you can say...

Exclude data frames where FTC# is less than or equal to 19. Then, CL and OL-decel should be excluded.