Backup discipline
Create and verify a known-good baseline before writing or testing any revision. Store the original file and session notes somewhere recoverable.
Core notice
Always keep an original ECU backup, validate changes incrementally, and understand that tuning can affect emissions compliance, drivability, mechanical stress, and warranty coverage depending on your jurisdiction and vehicle use.
Preview software is not a substitute for sound workshop judgment. If a change cannot be explained, logged, and reversed, it should not be treated as safe to apply.
What users are responsible for
The software can help structure a workflow, but it does not remove responsibility from the person connecting to the vehicle and applying changes.
Emissions and road use
Some calibration changes may be illegal for public-road use in certain regions. You are responsible for understanding and complying with local laws.
Mechanical risk
Powertrain changes can increase thermal and mechanical load. Validate hardware condition and monitor the car rather than assuming software alone makes a setup safe.
Preview-use boundaries
The current release posture is aimed at experienced testers and disciplined early adopters, not blind one-click tuning.
- Use preview builds in controlled environments and log before and after every meaningful change.
- Do not rely on intermittent wireless adapters for critical tuning sessions if a wired option is available.
- Stop immediately if telemetry, fault state, or drivability behaves unexpectedly after a revision.
- Review the development page for known limitations before treating an unfinished feature as production-ready.
Need the safer path before testing?
Read Setup Docs