GPS trackers and cameras that work with the platform.

Trackers, dashcams and sensors connect to your server over the mobile network, and each protocol has its own port. The platform handles 11 protocols natively and 258 more through a protocol bridge. Between them, they cover the 4,800 device types on the supported list.
A truck selected on the live map, its card showing odometer, fuel level and CAN engine values

How to connect a tracker.

Connecting a new unit takes four steps. The documentation in the portal has the details for each brand.

  1. Before fitting

    Set the server and port

    Program the unit with your server's host name and the port for its protocol. Use an SMS command or the maker's configuration tool. The Tracker ports page lists the ports by brand.

  2. In the portal

    Add the IMEI

    Create the device in the portal with its IMEI or ID and assign it to a client account. If a unit reports before you add it, it appears in the list of unregistered devices.

  3. First report

    Check the first report

    Filter the connection log by IMEI to see raw data and decoded positions as they arrive. A wrong port or protocol is obvious straight away.

  4. Day to day

    Send commands

    Send an engine cut, a new reporting interval or other commands from the portal. If the unit is offline, the command waits in a queue until it reconnects.

Native listeners and the bridge.

The 11 protocols in the table run on native listeners. They cover the hardware most fleets use, and all of the video.

The protocol bridge adds 258 more. Among them are Queclink's GL200 family, Ruptela, Meitrack, Suntech, CalAmp, ATrack, Galileosky, Cellocator, Wialon IPS and OsmAnd, which phone tracking apps use. Each bridged protocol also gets a port of its own.

Protocols with native listeners
ProtocolTypical devices
TeltonikaFMB, FMC and FMU trackers, including CAN-ready installs
Teltonika DualCamRoad and cabin camera paired with a Teltonika tracker
GT06Concox units and the many trackers built on the same protocol
H02SinoTrack, TKSTAR and other H02 trackers
Cantrack H02Cantrack units that need a listener able to send commands
JT/T 808Trackers and mobile DVRs built to the Chinese transport standard
JT/T 1078Live video from dashcams that use the 1078 standard
WatchSeTracker and Wonlex wearables
EV07Eview EV07 vehicle trackers
DMTDigital Matter devices
ReachfarReachfar personal trackers

Mixing brands on one server

Units from different makers report side by side. A client might have Teltonika units in its trucks, GT06 trackers in its cars and a JT/T 1078 camera on a bus. All of them show up on one map and in one set of reports.

Moving from another platform

We can import from supported platforms, so ask us whether yours is one. The import copies accounts, devices and stored positions. Then the units are pointed at your server a batch at a time. Units from other platforms move over in batches the same way.

Questions about devices

How do I check whether my tracker model works?

Search for it in the device list. The search covers popular models only, and the supported set is larger. If yours isn't there, send us the make, model and firmware and we'll check the protocol.

Can a phone work as a tracker?

Yes, with a tracking app that reports over the OsmAnd protocol. A phone is less reliable than a fitted unit, so it's better for tracking staff and for trials than for vehicles.

What happens to positions if the server can't be reached?

Most trackers store records in memory and send them when the connection is back. The server confirms a record only after saving it, so anything that wasn't stored gets sent again.

Try it on a server of your own.

Order online and we'll usually have your server live within a day, with your domain, your logo and the tracker ports all set up.

Talk to us