Custom OEM PIDs: investigate a reading standard OBD2 does not expose
Find vehicle-specific readings beyond standard OBD2: choose OEM PID references, check compatibility, import Torque CSV and record selected parameters.
When this feature helps
A standard OBD2 dashboard does not expose every value a vehicle may report. Custom Vehicle Parameters, available in Labs, provides a separate workflow for manufacturer-specific requests. You can browse references by brand and model, import a Torque CSV file, or define a request and formula. The purpose is to investigate a specific, supported value rather than assume a matching vehicle name unlocks every sensor.
Example: a parameter missing from the standard sensor list
Suppose you want to examine a vehicle-specific temperature that does not appear in standard live data. First check whether a reference exists for your exact model, powertrain and module. Review the request and unit, then try a single read. If the module responds, compare the result with plausible operating conditions before recording it. A smooth chart alone cannot prove that the formula or selected module is correct. If the request receives no response, treat the value as unavailable; do not interpret it as zero or as a faulty component.
A practical workflow
Open Labs and Custom Vehicle Parameters. Browse the available vehicle references or import a Torque CSV. Check the request, header, formula and units before saving parameters. Start with one value and a single read. Once the response is meaningful, select the parameters needed for your question and start a recording. Review its live charts and saved history, then export CSV if you need to compare readings in a spreadsheet. Keep notes of vehicle conditions when comparing sessions; an engine-off reading and a warm running reading answer different questions.
Example: checking an imported Torque CSV
An imported file is a collection of request definitions, not a compatibility certificate. If the displayed value is implausible, verify the intended vehicle variant, responding module, formula and unit against the source of the definition. Do not change a formula merely to make the number look familiar. A successful import proves that the file was accepted; a meaningful vehicle response still needs checking.
Reading rate and compatibility
References are not a guarantee of coverage. Vehicle year, powertrain, protocol, control module and adapter can change the response. Read requests are scheduled, so adding parameters can increase the time between updates. This is not fixed-rate laboratory acquisition. Custom OEM parameters use their own reading and recording flow and are not selectable in the standard dashboard.
Connection and membership
Use a compatible BLE OBD2 adapter and sign in before reading. Browsing reference configurations is free. Adding, saving, reading and recording custom parameters require paid membership. The adapter is sold separately; classic Bluetooth and Wi-Fi adapters are not supported.
Common questions
Can I use a file from another vehicle? Review its definitions first; matching a brand is not enough. Can I export a session? Saved OEM parameter recordings support CSV export. Does a missing reply mean a broken sensor? No: an unsupported request, wrong module or communication issue may also explain it. Use verified measurements and vehicle service information before deciding on repairs.