This part is within the family: Sentrius RM1xx LoRa + BLE Module Learn more and compare with similar parts on the family page.

Specifications

Antenna Type
External
Chipset (Wireless)
Semtech SX1272, Nordic nRF51822
Compliance
FCC/IC
Connector
SMT
Data Rate
LoRa: 980 bps - 21.9kbps, BLE: 1 Mbps
Development Kit Contents
Development Kit DVK-RM1xx and Free Software Tools
Dimension (Height - mm)
3.1 mm
Dimension (Length - mm)
25.4 mm
Dimension (Width - mm)
25.4 mm
Frequency Range (Max)
928 MHz
Frequency Range (Min)
902 MHz
Logical Interfaces
Serial, GPIO, SPI, I2C, ADC
OS/Software
smartBASIC
Power Consumption (Rx)
15.3 mA
Power Consumption (Tx)
45.7 mA
Product Type
Development Kit
Receive Sensitivity
LoRa: -126 dBm, BLE: -91 dBm typical
System Architecture
Hostless
Technology
Bluetooth 4.1, Dual Mode (Classic + BLE), LoRaWAN
Transmit Power (Max)
15.5 dBm
Weight
3 grams

Buy Now

Distributor Part In Stock Region Buy
Digi-Key RM191-SM 4894 North America Buy Now
RS RM191-SM 100 EMEA Buy Now
Mouser RM191-SM 20 North America Buy Now

FAQ

Why does LoRa TX not work when using GpioAssignEvent()?

Some of the internal SmartBASIC events are being shared between certain peripherals and hence limitations apply for certain combinations. On the RM186 the SmartBASIC implementation uses the same mechanism internally to trigger both LoRa TX and GPIO assign events.

Simplest workaround would be using GpioBindEvent() instead of GpioAssignEvent(). However, this comes with a slightly higher power consumption.

Another workaround would be clearing the GPIO assign event before triggering a LoRa TX event and vice versa. To ensure this, the following sequence would be needed:
  • In your GpioAssignEvent() callback function disable the assign event with GpioUnassignEvent() and start a short one-shot timer (e.g. some 10msecs).
  • In the callback of that timer trigger the LoRa TX.
  • On completion of the LoRa TX (either successfully or failed or both, depends on your application) re-enable the GPIO assign event in e.g. one (or more) of the following callbacks: EVLORAMACSEQUENCECOMPLETE or EVLORAMACTXCOMPLETE or EVLORAMACRXCOMPLETE (maybe others could be used too, would depend on your application)

Is there a way to extend the shelf life of Laird modules?? If the shelf life cannot be extended in any way, what are the consequences of using modules after shelf life?

The shelf life statements are essentially to prevent mishandling of the product and not storing it properly. If the modules are still sealed in the package, stored at the proper temperature and have not been exposed to moisture they should be fine. However, when working with modules beyond their shelf life you MUST bake the modules before populating the them to your board. Failure to bake the modules could result in the yield rate dropping down lower than expectation due to popcorn or de-lamination on the modules. It is recommended that you follow IPC/JEDEC J-STD-033 which is the general standard for the handling, packing, shipping and use of moisture/reflow sensitive surface mount devices.

Our main concern is around the castellation/pads which solder the module to the board. It is imperative those pads do not get tarnished, as this would cause soldering issues. Humidity can affect solderability as well, as if there is any excess moisture in the solder on the module, during reflow of the module to the board, steam balls can essentially explode the solder and sometimes result in an open circuit (or possibly a short circuit).

As long as all of the moisture handling and temperature guidelines are being followed you will likely have no issues. It is further recommended that when you do the build with modules that have exceeded their shelf life that you start with a handful to perform a test run and do a final test to make sure all is working as expected. As long as there are no issues with the initial test run we would expect that you will not experience any problems.

Can AS923 and AU915 networks coexist in the same area?

Yes, as long as they are operating on different networks such that AS923 sensors talk to the AS923 gateway and vice versa for AU915 devices. 

Can the RS1xx AS923 (455-00063) work with an AU915 gateway which uses overlapping channels to AS923?

No, an RS1xx AS923 sensor will not work with an AU915 gateway because it cannot receive the downlink packets due to differing bandwidth and frequency plans used and therefore will drop off the network.

What is Laird Connectivity's product lifecycle EOL and PCN policy?

Laird Connectivity is committed to the long-term supply of all its standard embedded wireless modules and packaged products. Laird Connectivity’s products are specifically designed to meet the needs of the industrial and medical markets, which typically require 7 – 10 years product lifecycle. Although Laird Connectivity can’t guarantee that a component used in our products will not be obsoleted and cannot be reasonably substituted, Laird Connectivity can assure customers we will continue to sell our product when we have customer demand and can obtain the necessary components to build our products.

View our full policy here.