OBD2 data logging: keep the evidence a live gauge cannot
Record supported OBD2 sensor charts, compare operating conditions and export CSV. Learn which readings to select and how to avoid misleading comparisons.
Browse supported values while connected.
Save a sensor session, review charts and export CSV.
Configure a focused layout for the values you watch.
When a recording is more useful than a glance
A live gauge tells you what a sensor reports now. A recording helps you look back at how supported values changed together during a session. Use sensor logging when a symptom is intermittent, when you want to compare two operating conditions, or when you need to share a clearer description of an observation with a technician. The app records available vehicle data; it does not identify the faulty component for you.
Example: compare cold and warm idle
Suppose the engine feels different just after starting and once warm. While parked safely, select a small group of relevant supported values, such as engine speed and coolant temperature. Record a session and note when the engine transitions to warm operation. Review the traces together, then repeat under comparable conditions if needed. A change in idle speed during warm-up can be normal; the recording alone does not establish a defect or a vehicle-specific threshold.
Set up a focused session
Sign in and connect a compatible BLE OBD2 adapter. Open sensor data collection, select the supported sensors needed for your question, adjust read intervals and choose a duration. The app remembers the previous settings. Start recording and check that values are arriving. You can stop manually or let the session end at the selected duration. Do not interact with the phone while driving; configure before setting off and review after stopping safely.
Read the timing correctly
Sensors are read sequentially. Selecting more sensors generally makes each sensor update less often. Requested intervals are not a guarantee of exact acquisition timing: adapter speed, protocol and vehicle responses matter. If you need to understand a short event, start with fewer relevant signals and inspect actual timestamps. A flat line, missing reading or interrupted session should not be assumed to mean that the underlying system stayed unchanged.
Use charts, statistics and CSV together
Open a saved session to review charts and statistics, save a full report image or export a CSV file to a spreadsheet. CSV column headings are localized. Check units, timestamps and the conditions of both runs before comparing values. Saved sessions remain useful after disconnecting from the vehicle, after sign-in on the device where the reports were saved.
Example: give a technician a clearer description
Instead of saying that the car sometimes behaves oddly, save a session and note when the symptom occurred, whether the engine was cold or warm, and what you were doing. Share the report or CSV with that context. This can help someone decide what to test next; it is not proof that a particular part should be replaced.
Requirements and common questions
Sensor logging requires sign-in, paid membership and a compatible BLE adapter. Available sensors vary by vehicle. Can every selected signal be recorded at the same instant? No; reads are sequential. Can I record with no car connection? No, but saved reports can be reviewed later. Need manufacturer-specific requests? Use the separate custom OEM parameter recording workflow.