Game telemetry → tachograph logic
The DTCO tachograph (v4.1.4) runs on Windows as its own desktop window. It never reads the game’s memory directly — everything comes from your local Funbit-compatible JSON telemetry. The LCD, timers, DVSA tooling and print logic are driven from that feed plus your licence state.
What runs, and in what order
- ETS2 (+ Funbit Telemetry Server). The game exposes speed, paused state, headings and optional position through a tiny HTTP endpoint on your machine (default port
25555). The tachograph talks to localhost for telemetry. - Start the tachograph app. On startup it creates or loads a device profile (stored locally alongside settings), registers with the activation portal, and remembers whether your licence is ACTIVE. If not active, timers and driving features stay locked until you resolve activation (F8 shows keys and copy buttons).
- Telemetry loop. A background poll hits your configured URL roughly 10 times per second. The default for Euro Truck Simulator 2 is
http://127.0.0.1:25555/api/ets2/telemetry. In Settings you can switch to American Truck Simulator’s path (…/api/ats/telemetry). The status dot reflects whether JSON is reachable: green when data is flowing, red when it is not. - Optional auto-start Funbit. On builds that ship with the bundled telemetry executable, the app can try to launch it once if the URL is offline and you allow that in settings — useful when you forget to start the server first.
- DTCO behaviour. Speed above a low threshold counts as driving; long stops can arm break logic. Card insert/eject, boot prompts, manual WORK/REST, EU break rules, overspeed handling and the LCD page stack (main, summary, timers, events, print menu, settings page) all run inside the overlay.
- Prints, events, DVSA. Events and inspection-style output are written under your user profile (see Prints & Logs). The p shortcut issues an immediate Driver 1 print when the rules allow; the print menu still offers vehicle, events and DVSA outputs.
Telemetry JSON
Every tick the app merges game fields into tachograph timing: paused vs moving, approximate speed for drive detection, headings and geo when the payload includes them.
http://127.0.0.1:25555/api/ets2/telemetry
ATS: same host, replace with …/api/ats/telemetry.
Firmware-style flow
A DTCO-style state machine drives the LCD: card workflow, boots, timers, BREAK REQUIRED / overspeed acknowledgements and manual modes. Locked licences show a disabled screen instead of advancing timers.
- In-game panel (End): optional second window with break strip and mirrored shortcuts (controls).
- Settings (F3): telemetry URL, bundled Funbit behaviour, fonts, optional local browser dashboard.
Events + DVSA snapshots
Infringements, overspeed episodes and roadside inspection snapshots integrate with logging and printable outputs. Paths are predictable so you can zip them for Discord support.
Background checks
While you play, the app periodically re-checks licence status with the portal (so a newly approved device unlocks without a full reinstall). It can also look for application updates on a schedule and offer a one-click zip-based upgrade when a build is published.
All activation details stay in the app — F8 opens the panel you use for tickets. See Activation.
Tray, LAN UI, visibility
- System tray integration can keep the app reachable when you minimise; F9 toggles hiding the physical overlay.
- An optional local-only web dashboard can be enabled in Settings (token + port) so a phone or tablet on the same LAN can glance at tachograph-derived readouts — still powered by your machine, not cloud-hosted.