Skip to content



The ioTracker 3 Pro is equipped with the ublox SARA R412m cellular module. Therefor the ioTracker supports connectivity to LTE-M, NB-IoT and EGPRS cellular networks.

SIM slot

The ioTracker 3 Pro features a mico-sim (3ff) slot which is placed under the battery.

Network selection

The ioTracker 3 Pro by default tries to automatically connect to an available cellular network. Please contact us if you need a static cellular network configuration.

Acces Point Name (APN)

The ioTracker 3 Pro by default tries to ready the correct APN from the simcard. It's also possible to configure a static APN via our ioTracker configuration app.

UDP communication

The ioTracker 3 Pro communicates via the UDP protocol directly to your own application server. You need to open an UDP socket on a self specified port to make communication possible.

Remote Access Technology (RAT) priority

You can configure the number of enabled RATS and the priority of the RATS. By default EGPRS has de lowest priority (backup), after that comes NB-IoT and LTE-M has the lowest priority. It's important to only enable the RAT's which are supported by your cellular service provider. When a certain RAT isn't available, the ioTracker 3 Pro automatically tries the next in line.

No Network Power Optimization (NNPO)

NNPO is enabled by default and ensures that the battery doesn't drain fast when there is no cellular coverage available. The behavior is configurable, but by default it will stop sending uplink messages for 32 times when five times in a row it wasn't possible to connect to the cellular network. When the ioTracker 3 Pro is moving, NNPO will be disabled by default.

An uplink message defines a message from the ioTracker 3 Pro your application server and contains the sensordata. Uplink messages can be send on a pre-configured interval, but can also be triggered by an event (reaching a certain temperature for instance). The uplink messages are "encoded" in a hex value.

The uplink message needs to be decoded to readable data, we have an example javascript decoder available on GitHub which helps you with this process.

An downlink message defines a message from your application server to the ioTracker 3 Pro. The downlink needs to be queued by your application server and it needs to be send, on the same UDP port, within 3 seconds after you have recieved the uplink message. With a downlink message you can make configuration changes to the ioTracker 3 Pro. For instance you can change the uplink interval of enable the GPS.