MVT, T1, T333, T366 and P99 cover vehicle, asset and personal tracking on one protocol. The platform decodes the MEITRACK command set including the sensor and image extensions the range is known for.
One protocol across vehicle, asset and personal units, so a mixed deployment does not mean a mixed integration.
Protocol-level facts from the manufacturer’s own documentation. Model-level behaviour varies within a series, so confirm your exact unit with us rather than assuming.
| Item | Supported | Notes |
|---|---|---|
| Protocol family | MEITRACK ASCII and binary | Shared command set across the range |
| Transport | TCP and UDP | TCP standard for vehicle units |
| Series commonly deployed | MVT / T1 / T333 / T366 (vehicle), P99 (personal), MT90 (asset) | Same protocol across all of them |
| Sensors | Fuel, temperature, door, driver ID | Via digital and analogue inputs |
| Camera-capable models | Image capture on supported units | Event-triggered stills, not continuous video |
| Personal tracking | P99 with SOS and fall detection | Lone-worker and personal-safety deployments |
| Remote configuration | SMS and GPRS commands | Server, interval and alarm settings |
Most platform vendors publish a list of supported model numbers. It looks reassuring and it is usually out of date, because it describes a snapshot of what somebody tested once rather than how the integration actually works. GPS platforms do not implement models; they implement protocols. Meitrack devices report over MEITRACK (ASCII and binary) across TCP and UDP, and the platform decodes that protocol — which is why a new unit in the MVT, T1, T333, T366, P99, MT90 families generally works on the day it ships rather than after a development cycle.
What genuinely varies between models is not the protocol but the hardware: which inputs physically exist, whether a CAN interface is present, whether there is a relay output, how many 1-Wire devices can be attached. That is why we ask for your exact model and firmware version rather than publishing a matrix. It takes us a day to confirm against a live server, and it is the difference between a deployment that works and one that discovers a missing input after the units are installed.
Send the model, the firmware version and what you need to report on. You will get back a straight answer on three things: whether the unit reports into the platform at all, which of your required data points it can actually produce, and whether a cheaper unit in the same range would do the same job. That last one costs us margin and saves you money, which is the point — a fleet that buys the wrong hardware blames the platform.
Meitrack units already in the field can be re-pointed to a new server remotely, so a migration does not mean visiting vehicles. We audit what is connected first, import your historical data, re-point a pilot group, and cut the rest across only once the pilot reconciles cleanly against your old system. The old endpoint stays live through the window. Full detail is on the hosting and migration page.
Send your Meitrack model list and we will confirm compatibility against a live server before you commit. Request a compatibility check or message us on WhatsApp — include firmware versions if you have them, and tell us what you need to report on.
Yes, and this is a genuine advantage of the range — MVT vehicle units and P99 personal units share one protocol, so a security company tracking both patrol vehicles and guards runs a single integration rather than two. Alerting rules differ by device type, which is correct, but the data path is shared.
On camera-capable models, yes. These capture event-triggered stills rather than continuous video, and the platform attaches the image to the event record so a door-open or SOS alert carries its own evidence. Image storage is sized into the hosting plan because it grows faster than position data.
That depends on what you need beyond position. A basic MVT or T1 is sufficient if you want location, ignition and trips. Move up the range when you need multiple sensor inputs, driver identification or image capture. Tell us the reports you need to produce and we will tell you the minimum unit that produces them, which is usually cheaper than the one being quoted.
It is routed as a priority alert with its own escalation path rather than joining the general event queue. A geofence breach can wait for someone to look at a dashboard; a lone-worker SOS cannot, so it triggers notification rules independently of normal alert batching.
Yes. Each protocol has its own listener and all of them normalise into the same position and event model, so geofences, reports and alert rules behave identically whether the data came from a Meitrack, a Teltonika or a Concox unit.
Send us your exact models and firmware versions. We will test them against a live server and tell you what works before you commit to anything.
Check My Device →