NB-IoT as uplink

Table of Contents

At the latest since 2G and 3G switch-offs were announced and in some cases have already become reality, the M2M/IoT world has been keeping its eyes open for new technologies. A promising transmission technology for applications with low power requirements at long range and high building penetration is NarrowBand IoT (NB-IoT for short).

The cost-effective Low Power Wide Area (LPWA) technology is becoming more and more widespread. The GSMA’s Mobile IoT Deployment Map shows in which countries NB-IoT and LTE-M are basically available. In a detailed comparison, we shed light on the jungle of abbreviations and ask questions that will help you find the right uplink technology for your application.

Many hardware components provided by Microtronics use modems with multiple transmission technologies. This can be relevant, for example, if you want to operate your applications in many countries. This is because not all technologies are available in all countries. Via the IoT app (programming of the app), for example, the fixation on NB-IoT can be done as an uplink.

By default, the modem automatically decides which technology to use for the uplink. If no connection can be established via the primary uplink technology, the modem automatically switches to a fallback technology.

The primary uplink technology is always LTE-M1 for the devices concerned (see table). The fallback technology varies. It depends on the modem installed in the device.

If you want to select the uplink technology in your application and, for example, select NB-IoT as the primary or only uplink, you can do this in the IoT app.

ATTENTION: It is essential to note that you must take care of an automatic fallback when using manual control yourself. But you also need to set the number of connection attempts. Features and safety mechanisms with regard to an energy-saving uplink are overridden with manual control and you must take these into account in your IoT app (programming logic).

Which units support manual control?

All NB1-capable devices from Microtronics support manual control of the uplink technology.

Specifically, these are myDatalogEASY IoT, myDatalogEASY IoTmini, rapidM2m C32x, rapidM2M M22x each in the 2G/M1/NB1 variant and rapidM2M T32x.

The following table provides information on the standard primary and fallback technology

Primary and fallback technologyDevice(s)
Primary: M1
Fallback: 2G
myDatalogEASY IoT 2G/M1/NB1
myDatalogEASY IoTmini 2G/M1/NB1
rapidM2M C32x 2G/M1/NB1
rapidM2M M22x 2G/M1/NB1
Primary: M1
Fallback: NB1
rapidM2M T32x

In both cases the primary technology is LTE-M1, but the fallback technology differs. 2G/M1/NB1 devices use 2G as fallback, while the rapidM2M T32x uses NB1 as fallback. The modem built into the rapidM2M T32x does not support 2G.

How does manual control work in practice?

To fix the uplink technology used to NB-IoT, for example, a special entry must be added in the APP-FLASH Registery in the device. This is possible via the Device Logic (DLO) in the IoT app programming in the rapidM2M Studio.

The following code fixes the uplink technology to NB-IoT:

registryWriteString(RM2M_REG_APP_FLASH, "mdmProfileCfg", "NB-IoT");

To switch back to automatic technology control:

registryWriteString(RM2M_REG_APP_FLASH, "mdmProfileCfg", "");

ATTENTION: If the control is taken over, the DLO must also ensure that in case of error (e.g.: NB-IoT not available) it is switched back to another technology.

Conclusion

The described function calls show how the uplink of NB-IoT-capable devices can be fixed to this technology. Consider carefully why such a fixation is unavoidable for your application. By fixing the uplink to NB-IoT, for example, you deactivate the automatic control of the uplink technology and are responsible for the fallback management from this moment on.

Would you like to learn more about Microtronics?

C3 im Schaltschrank
Applications

Modbus Master Library – simple, convenient implementation

Modbus is a communication protocol commonly used in industrial automation. The Modbus protocol consists of a client-server architecture in which a client (for example, a control device) sends commands to a server (for example, sensors or actuators) and receives data from it.

The communication is based on a simple command-response mechanism. Modbus is an open protocol, which among other things has led to its great popularity and spread.

NB-IoT from space - Satellite
Blog

NB-IoT in space

Only 10% of the world is accessible via terrestrial networks. Yet there is potential for environmental monitoring stations in the world’s oceans and deserts.

So is NB-IoT in space just a good hook for a story or more? Well, at least it’s good for a few new buzzwords and hashtags. But let’s take a look at what this is all about.

#5GNTN

NTN…Non Terrestrial Network

Maximise device runtime
Blog

Maximise the Runtime of your Devices

The runtime of industrial battery-powered devices is an aspect that plays a relevant role in terms of efficiency and sustainability. If the devices are located in places that are difficult to access, such as in a canal, a device-lifelong runtime is an enormous increase in efficiency – not only for the devices, but also for the employees who maintain and support the systems.

In order to use our live chat, you must agree to the loading of Hubspot cookies. You can find out more about this in our privacy policy.