Device Protocols
Understand how GPS trackers communicate with Open VTS and how to configure device protocols.
Last updated March 15, 2026
Open VTS supports 200+ GPS device protocols out of the box. Each protocol listens on a dedicated TCP or UDP port. Devices connect directly to your server — no cloud relay required.
How Device Communication Works
- The GPS tracker sends position data to your server's IP and the protocol-specific port
- Open VTS decodes the proprietary protocol into a standard position format
- The position is stored in PostgreSQL and forwarded to the real-time engine
- The web interface and API reflect the update immediately
Popular Protocols & Ports
| Protocol | Port | Popular Devices |
|---|---|---|
| Teltonika | 5027 | FMB120, FMB920, FMC130, FMB640 |
| Queclink | 5006 | GL300, GV500, GV75, GL320MG |
| Concox | 5068 | GT06, WeTrack2, JM-VL01, JM-VL02 |
| Ruptela | 5046 | FM-Eco4, FM-Pro4, HCV5, LCV5 |
| Meitrack | 5020 | T333, T366, T366G, T399 |
| GT06 | 5023 | Generic GT06 protocol devices |
| H02 | 5013 | SinoTrack ST-901, ST-906 |
| TK103 | 5002 | Coban TK103, TK104, TK303 |
Configuring a Device
Each physical GPS tracker needs to be configured with your server's address and the correct port. This is typically done via SMS commands, a manufacturer's configuration tool, or an OTA platform.
SMS command example (Teltonika)
# Set server address for a Teltonika device
setparam 2001:your-server-ip
setparam 2002:5027Tip
If you are unsure which protocol your device uses, check the Supported Devices catalog for detailed protocol and configuration information.