DTCO tachograph companion · v4.1.4
InstallControlsGame / real timeActivationPrints & LogsPricingStatusSupport
DTCO Activationby Massy007
How it works

Telemetry → DTCO screens → EU hours

The Windows DTCO overlay (v4.1.6) never reads game memory. It polls local Funbit JSON, runs a firmware-style card/boot flow, and advances drive/break/rest on either game time or PC real time.

Funbit JSONCard + boot LCDGame or real timeEU breaks
Typical session

What runs, and in what order

  1. ETS2 + Funbit Telemetry Server — speed, pause, odometer, and game.time on port 25555.
  2. Start DTCO — device registers with the activation portal. Unlock with F8 / Activate (email + license + device key).
  3. Insert card (c) — self-test → VDO/DTCO → reading card → start country, then the real-style 2-line main LCD.
  4. Timers — same clock drives continuous drive, qualifying breaks (45m or 15+30), daily/weekly EU hours, and trip. See Options.
  5. Evidence — events, prints, DVSA under AppData.

LCD screens

  • MAIN — time · mode · speed / mode · card · odometer (like a real DTCO)
  • SUMMARY — daily drive + shift/break
  • TIMERS — CONT / DUE + clock source (GAME/REAL)
  • WEEK — day, week 56h, 10h extensions, fortnight
  • EVENTS / PRINT / SETTINGS
  • Alerts: overspeed, break required, country prompts, boot/loading

Breaks — game time & real time

  • After 4.5h continuous driving → take 45m (or split 15+30)
  • Game time on: clocks follow the sim; pause = freeze
  • Game time off: PC clock; breaks keep counting offline
  • Park / REST / auto-BREAK all count toward the qualifying break
  • Details: Game time & real time · Drivers’ hours
1) Local feed

Telemetry JSON

http://127.0.0.1:25555/api/ets2/telemetry

ATS: …/api/ats/telemetry

2) On your PC

Firmware-style flow

Boot/self-test, card countries, WORK/REST, overspeed ACK, in-game panel (End), Settings (F3).

3) Evidence

Events + DVSA

EU warnings/infringements, overspeed, Driver 1 / DVSA prints for roleplay checks.

OptionsControlsFeaturesBuy