RM126x Ultra-Low Power LoRaWAN Module
Learn more and compare with similar parts on the family page.

Development Kit, RM1261, SX1261, MHF4

Specifications

Type
Development Kit

Documentation

Name Part Type Last Updated
Datasheet - RM126x LoRaWAN Module 453-00140-K1 Datasheet 04/10/2024
Product Brief - RM126X Series 453-00140-K1 Product Brief 05/14/2024

Buy Now

Distributor Part In Stock Region Buy
Mouser 453-00140-K1 22 North America Buy Now
DigiKey 453-00140-K1 20 North America Buy Now
Avnet 453-00140-K1 15 North America Buy Now
Farnell 453-00140-K1 9 EMEA Buy Now
Arrow Electronics 453-00140-K1 5 North America Buy Now
Future Electronics 453-00140-K1 0 North America Buy Now


FAQ

What sort of power consumption should I expect when using Laird RM126x P2P mode?

LoRaWAN has three end device class modes

Class A devices transmit and then open a receive window and outside of these events the radio can be switched off to minimise power consumption. Class A uses the least amount of power

Class B allows for scheduled receive windows, so that the network server will know when the device is awake and able to accept a downlink.

Class C keeps the device radio on permanently , meaning it is able to receive a downlink at any time from the network server. Class C uses the most power

Laird LoRa P2P mode can be thought as working like a hybrid of the above modes. Because it makes use of a beacon, to allow devices to synchronise with dedicated transmit and receive slots, the power consumption will be most like a class B LoRaWAN device as the radio will be on every time the device slot comes around. P2P mode can initially behave like a class C device when looking for a beacon.

Exact power consumption will be specific to an individual use case and it is advised to measure the power consumption for your particular use case but peak consumption values can be found in the datasheet.

 

When using RM126x P2P mode, can I queue multiple messages to be sent?

No, not in the initial release of firmware. Only a single message can be submitted for transmission. If subsequent messages are submitted, they will overwrite the existing message until it has been transmitted.

This might not be an issue for event based reporting but could be an issue if multiple messages or packets need to be sent in quick succession.

We will be adding extra functionality to better manage message queuing in time. Please check the firmware release notes for fuirther information or contact support@lairdconnect.com

When using RM126x P2P mode, what does Class: [Fail] error message mean?

The RM126x P2P mode uses a beacon at the start of a frame to synchronise the devices in the network. Device 0 is always the device that generates the beacon and all other devices listen for the beacon. In a device other than device 0 fails to receive the beacon then it will return the Class: [Fail] error message.

Commons reasons for seeing this error might include

  • Device 0 has not joined the network
  • Device 0 is out of range of the device seeing the error
  • The network has been incorrectly configured, for example more than the defined number of devices on the network