fyi – i figured out how to add the PID manually (via Custom PID).

(for reference) Fuels Status is a bitmap within the 1st Byte (“A”) returned from PID 03, Mode 01. Valid returned values are
1 – open loop (cold engine)
2 – closed loop
4 – open (deceleration)
8 – open loop (system failure)
16 – closed loop (partial fault in system)

Custom PID i used was…
OBD2 Mode & PID = 0103
Long Name = Fuel Status (Bitmap)
Short Name = Fuel Status (b)
min value = 1
max value = 16
scale factor = x1
unit type =
Equation = A

I’ve only tested it briefly, but seems to be returning and logging appropriately.

(Ian,) I assume you’ve created and are referencing the same PID for your fuel system “widget”. However, it wasn’t immediately obvious to me how a user (i) could access the Fuel System PID you’d created…. maybe these things will become clearer to me as i play more with the tool.

Basic info, code references & customization guides:
It seems like an organized set of references for the user would help avoid many questions and stumbling of us new torque users. (I know i’ve spent hours cobbling together references
across the web in order to better understand if/how torque may best help me).

Maybe this is a difference in the use model(s) for torque.
a) those looking to use torque to help gain (inexpensive) visibility & help diagnose issues within the auto’s ECM I/O.
and
b) those looking to use torque to produce shiny digital images/gauges for in-car aesthetics.

Clearly there’s some overlap at the surface, but …
i digress….

Very nice tool, by the way. I’m a satisfied customer,
searching for reasons to be even more satisfied….
andy