تێپەڕبوون بۆ ناوەڕۆکی سەرەکی

Telematics & Teltonika ingest

This folder documents how OmniTrack can evolve from a school fleet web app toward a self-hosted telematics ingest path for Teltonika-class devices (e.g. FMC920 family). Design targets (o.a. 600k+ devices, 40M+ users) staan in ../PLATFORM-MASTER.md; de code evolueert gefaseerd — zie roadmap — zonder te pretenderen dat één release een volledige enterprise-cloud is.

What exists in this repo

AreaStatus
Device inventory (IMEI, SIM, profile, desired_config)Implemented (devices table, REST, CSV)
Operator export text for engineersImplemented (teltonikaOperatorExport.ts)
TCP gateway + Codec 8 AVL parsingImplemented (services/telematics-gateway/)
Position / online persistenceImplemented (device_positions, device_online)
Command queue (Codec 12)DB + API + gateway Codec 12 on TCP + retries/backoff (see commands.md)
Geofencing, billing, multi-tenant SaaSNot in scope of this roadmap’s first deliverables

What this repo does not promise without extra work

  • Teltonika cloud FOTA over proprietary GPRS binary services (see root README.md).
  • UDP listener (only TCP gateway is provided here; UDP can be added similarly).
  • Codec 16 / Codec 8 Extended parsing in production quality without device-specific QA (see protocol-codec8.md and Phase 2 in architecture.md).

External references (protocol)

Link to official Teltonika protocol documentation (Codec 8, Codec 12, TCP session) from your own knowledge base or vendor portal. Do not redistribute vendor PDFs in this repo unless your license allows it.

  1. architecture.md — components and data flow
  2. glossary.md — terms
  3. adr/0001-gateway-separate-service.md — why the gateway is a separate process
  4. protocol-codec8.md — parsing and acknowledgements
  5. runbook-gateway.md — how to run and operate
  6. commands.md — command queue lifecycle
  7. scaling.md — growth toward large fleets
  8. FOTA.md — firmware workflow (HTTPS + Configurator; what is not in-app)
  9. OPERATOR_CHECKLIST.md — field rollout checklist