Documentation paths

These are the first guides serious testers usually need before they connect an adapter or touch a calibration workflow.

Getting Started

First connection checklist

Install the preview, verify the adapter, connect to the car with ignition state correct, and capture a clean baseline scan before deeper work.

  1. Install the current preview build.
  2. Use a supported wired adapter where possible.
  3. Create a vehicle profile before the first scan.

Hardware Prep

Adapter and platform guidance

Windows plus USB ELM327 or STN hardware remains the safest preview path. BLE and Linux workflows are improving, but still need broader validation.

  • Prefer direct USB when stability matters.
  • Avoid unknown clone adapters for tuning sessions.
  • Keep laptop power and sleep settings controlled.

Diagnostics

Baseline scan workflow

Run a full scan, save the DTC state, note environmental context, then move into live telemetry. That gives you a defensible baseline before any changes are made.

  • Read all codes before clearing anything.
  • Capture freeze-frame details for active faults.
  • Log key PIDs before touching calibration.

Tuning Safety

Preview tuning precautions

Do not treat preview tuning features as casual one-click tools. Preserve backups, validate changes incrementally, and keep legal and emissions implications in mind.

Always keep an original backup and test incremental revisions in a controlled environment.

Troubleshooting flow

A good docs page should reduce support load. These are the first checks to run before filing a bug.

1. Connection fails

Check ignition position, cable seating, adapter compatibility, and whether another scan tool has locked the interface.

2. Data stream is unstable

Reduce stream density, prefer wired transport, and retest with fewer active gauges to isolate adapter bottlenecks.

3. Tuning workflow feels risky

Stop, restore the baseline, verify logs, and compare revision-to-revision instead of stacking unverified changes.

Need direct help after working through the docs?

Contact Support