Exact model
Vendor, product name, IMEI format and firmware revision.
GPS device compatibility
Support begins at the protocol.
A model name alone does not guarantee reliable tracking. TrackOS verifies packet format, firmware behavior and real device samples before production deployment.
Compatibility approach
Device family is the start, not the final answer.
Trackers sold under similar names can use different packet layouts or firmware. TrackOS confirms identity, framing, location fields, status bits and acknowledgements against the exact production hardware.
Features such as ignition, external voltage, relay state or specialised alerts are available only when the device and installation provide reliable source data.
Integration families
Protocols currently handled by TrackOS.
GT06 family
Common Concox-style login, location and status packet families, verified against model and firmware.
Model verification requiredTK103 family
Text and device-specific variants supported through confirmed packet samples and wiring behavior.
Variant verification requiredTeltonika
Compatible codec and telemetry workflows are reviewed against the selected Teltonika configuration.
Configuration review requiredAIS-140
Vendor-specific location and event integration subject to protocol documents, samples and approvals.
Vendor review requiredBefore deployment
Four items remove most integration uncertainty.
Protocol document
Packet framing, fields, bit definitions, checksum and acknowledgements.
Real samples
Login, location, status, ignition and alert packets from the actual unit.
Vehicle wiring
Installation details for ignition, power, relay and any external sensor.