LoRa and LoRaWAN – capabilities and limitations
LoRa is designed to transmit small amounts of data over long distances with low power consumption. This makes it well suited to sensors, meters and data logging, where devices need to send short messages and may need to operate on batteries for long periods.
LoRa is the radio technology itself. LoRaWAN is the network protocol used in many sensor installations to connect devices to a gateway and, through it, to a data system. The explanation below focuses on typical LoRaWAN installations.
How much data can you transmit?
LoRa prioritises range and low power consumption. Its data rate is therefore significantly lower than that of technologies such as Wi-Fi and mobile networks.
With common European LoRa settings using a bandwidth of 125 kHz, the approximate radio data rates are:
Radio settingApproximate data rate SF75470 bit/s, SF97 760 bit/s, SF12250 bit/s
SF stands for Spreading Factor. A higher SF allows weaker signals to be received, but transmissions take longer. The same message therefore uses more airtime when the connection requires a slower setting. These figures describe radio data rates. The effective throughput for the customer's data is lower because of protocol overhead and restrictions on transmission time.
Message sizes are also limited. At slower European settings, a LoRaWAN message may, for example, carry around 51 bytes of application data. At faster settings, it may carry more than 200 bytes, depending on the configuration. Temperature, humidity, soil moisture and battery status can normally be packed into a very short message.
For this reason, LoRa is not a practical solution for video transmission, conventional voice calls, large files or continuous data streams. These applications require much greater capacity and more continuous access to the connection.
Limited transmission time – duty cycle
A device cannot necessarily transmit again immediately.
In the European 868 MHz band, many LoRaWAN installations use frequency sub-bands with a 1% duty cycle limit. This means a transmitter may spend no more than 1% of its time transmitting in the relevant sub-band – equivalent to 36 seconds of airtime over one hour. Other sub-bands and channel access methods may have different limits.
As a simple calculation: if a message takes one second to transmit, evenly spreading transmissions under a 1% limit corresponds to a pause of approximately 99 seconds afterwards. The actual implementation depends on the equipment and configuration. The limit does not necessarily apply separately to each channel. Several channels may share the same sub-band and therefore the same airtime allowance.
Why can a reply or command be delayed?
There is a difference between a sensor sending a measurement and the system sending a message back to that sensor.
A typical battery-powered LoRaWAN Class A device spends most of its time asleep. After transmitting, it opens two short receive windows, RX1 and RX2, during which it can receive a message from the network. If the message cannot be delivered then, the network must wait until the device has made a later transmission.
If a sensor transmits every 15 minutes, for example, a command sent to it may have to wait almost 15 minutes for the next receive opportunity – and longer if the transmission or reply is lost. This does not mean every measurement takes 15 minutes to arrive. The waiting time mainly arises when trying to contact a sleeping device.
Standard LoRaWAN does not normally request permission first and receive an assigned transmission slot. The device initiates its own transmission within the constraints of the protocol and radio regulations. Class B provides scheduled receive opportunities called ping slots. Class C listens almost continuously and can therefore receive messages sooner, but consumes more power.
Some LoRa systems also check the channel before transmitting. This is called Listen Before Talk, and Channel Activity Detection (CAD) can be used to detect LoRa activity. This checks channel activity; it does not, by itself, reserve a time slot.
A greenhouse is a good example
In a greenhouse, sensors can measure temperature, humidity and soil moisture and send a short summary every few minutes. It is often more useful to observe trends over hours and days than to receive every individual measurement immediately.
A sensor can also take measurements more frequently locally and, for example, transmit the minimum, maximum and average every five minutes. This reduces the amount of data while retaining useful information about conditions. The actual transmission interval must be adapted to coverage, radio settings, the number of sensors and network constraints.
LoRaWAN is therefore well suited to:
- Periodic logging of temperature, humidity and other environmental data.
- Meter readings and short status messages.
- Occasional position reports.
- Notifications of abnormal conditions where some delay is acceptable.
If ventilation or irrigation must respond quickly and predictably, the necessary control should operate locally. LoRaWAN can still be used for monitoring, historical records and changing settings where delivery time is less critical.
LoRa is particularly useful when the task is to collect a small number of useful measurements from many locations with low power consumption. If the application requires video, large amounts of data or a guaranteed fast response, the connection must be selected to meet those requirements.