Understand automatic update checks, release channels, verification, failure recovery, and USB flashing requirements.
Automatic checks
When an online Trainer calls the current update service, the server compares its reported version with the version assigned to its release track. Eligibility and staged rollout logic can affect the returned firmware. A single “latest version” is therefore not hard-coded in this guide.
Before an update
- Finish and exit any physical session.
- Place the Trainer securely with no toy in use.
- Use a stable 2.4 GHz connection.
- Ensure adequate battery charge; the repository does not define a required percentage.
- Do not begin when losing power or connectivity is likely.
During and after
Follow the device progress screen and keep it powered. After it restarts, let preflight complete and verify that the expected session can be fetched.
Verification
The Trainer restarts normally, completes its online check, and does not repeat the update or show a recovery error.
Release channels
Dashboard device settings can expose firmware-channel controls for eligible devices. Channel names and eligibility may change. Choose only a channel currently offered to your account, and use Production when you do not intend to test prerelease software.
If an update fails
- Record the screen and any version shown.
- Keep the Trainer out of use.
- Restore a stable network and restart once.
- If normal startup does not recover, use the DTT Web Flasher only with supported hardware, browser, and a data-capable cable.
- Contact support before erasing the device or repeating failed flashes.
Version and rollback limits
The current user-guide repository does not publish a current firmware version, full dated release history, support matrix, or guaranteed rollback path. The update service resolves versions dynamically. Report the version shown by your device or flasher when requesting support.
Last reviewed against dashboard/API source: August 16, 2026.