A tracker does not send «the position»: it sends a string of data written in a specific format. That format is the protocol. If the platform does not understand it, the device can be reporting perfectly and nothing shows up on the map.
The exact format in which the device writes what it sends. Two devices can say the same thing in different words.
One manufacturer can use several protocols depending on the model. That is why you search by model, not by brand.
If the protocol is not supported, the device cannot come in until it is integrated. You check first, not after.
The manufacturer's datasheet says so, and usually the model name itself. In the catalogue you search by model.
Each protocol listens on its own port. When you register the device you have to point it at the right one.
Most can be integrated. It is work, not impossible: which is why it is worth asking before you buy the batch.
Exact words you can use on the visit. No jargon.
«The protocol is the device's language. If the server does not speak it, the device sends and nobody understands.»
«That is why I do not ask “does this brand work?” but “does this exact model work?”.»
You resell under your own brand. This is who it works for, and with what argument.
It connects and sends, but the position never changes: almost always the protocol or the port.
Misread coordinates. The hemisphere sign is the classic failure.
It can be coverage, but also a protocol being read only halfway.
The device sends them, but in a format that is not being read.
It is the exact format in which the device writes the data it sends. If the server does not understand that format, the device can be reporting perfectly and nothing shows on the map.
No, on the model. One manufacturer can use several protocols depending on the reference, so you have to check by exact model.
The manufacturer's datasheet states it, and usually the model name itself. You can also look it up in the supported device catalogue.
Most can be integrated. It is work, not impossible, which is why it is worth asking before you buy the batch.
Often yes, or the port it was pointed at. Each protocol listens on its own port, and pointing at the wrong one gives exactly that symptom.
Look it up in the catalogue, or tell us which one it is and we will confirm the same day.