Sentrius RM1xx LoRa + BLE Module

Not Recommended for New Design (NRND)

Overview

NEW: Upgrade firmware from your host microcontroller!

The Sentrius™ RM1xx series of modules offer a powerful, convenient solution for long-range Enterprise IoT (EIoT) deployments. Laird Connectivity innovatively combines Bluetooth® v4.1 with LoRaWAN™, the emerging standard in Low Power Wide Area Networks (LPWAN) into one module. RM1xx modules aggregate and transmit data from Bluetooth® Smart (BLE) devices and sensors over LoRaWAN to gateways as far as 15 km (~10 miles) away. This bridges the personal area network to the wide area network in a unique way. The Sentrius RM1xx will be LoRa® Alliance certified and fully interoperable with any LoRaWAN™-adherent gateway.

  • Designed for the EIoT – Innovative combination of BT™ v4.1 and LoRa® makes the RM1xx the bridge between Bluetooth Smart devices and a network that intelligently uses their data.
  • Ultra-low power usage schemes – Allows years of use on a single battery.
  • Laird Connectivity’s unique smartBASIC language – Makes it extremely easy to create event-driven, hostless applications.
  • Upgradable firmware – Prepare for the future with access to feature and security updates.
  • Compliant with FCC, CE regulations – Available as the RM186 (CE) or RM191 (FCC).
  • Download the NEW UwTerminalX as well as the two companion applications: MultiDeviceLoader and TermNotify

 

Specifications

Antenna Options
Dipole antenna with U.FL (IPEX) connector up to 2 dBi
Wireless Specification
LoRaWAN 1.01 (End Device) and Bluetooth 4.1
Chipset (Wireless)
Semtech SX1272 (LoRa), Nordic nRF51822 (Bluetooth)
Bluetooth Version
V4.1 – Central OR Peripheral Mode
Compliance
FCC, IC, CE, NCC, ASNZS
Interfaces
Bluetooth v4.1 (BLE Central or Peripheral), physical UART, SPI, I2C, GPIO, or ADC.
Max Transmit Power
BLE: 3 dBm (into -1.5 dBi chip antenna)
Protocols
Any that can be implemented using the onboard smartBASIC
Transmit Power
Wireless: 1.5 dBm - 13.5 dBm, Bluetooth: -20 dBm (in four dB steps) with smartBASIC command - 3 dBm (into -1.5 dBi chip antenna)
Product Type Technology OS/Software System Architecture Chipset (Wireless) Antenna Type Logical Interfaces Frequency Range (Min) Frequency Range (Max) Antenna Options Bluetooth Version Chipset Connector Data Rate Development Kit Contents Input Power LoRa Version Class Max Transmit Power Output Power Power Consumption (Rx) Power Consumption (Tx) Protocols Range Receive Sensitivity Wireless Specification
DVK-RM186-SM-01 Development Kit Bluetooth 4.1, Dual Mode (Classic + BLE), LoRaWAN smartBASIC Hostless Semtech SX1272, Nordic nRF51822 External Serial, GPIO, SPI, I2C, ADC 863 MHz 870 MHz Dipole Antenna 4 LoRa: Semtech Sx1272. BLE: Nordic Semiconductor nRF51822 USB Pluggable LoRa: 250 bps - 50 kbps. BLE: 1 Mbps. Development Kit DVK-RM186 and Free Software Tools 2.1V - 3.5V Internal DCDC converter. 1.8V - 2.1V Internal LDO. LoRaWAN 1.01 (End Device) +13.5 dBm 2mW and 25mW 12.7 mA 31.4 mA LoRa Class A and Bluetooth Low Energy LoRa: Up to 15 km. BLE: Up to 100 m. LoRa: -134 dBm. BLE: -91 dBm. LoRa MAC Class A Specification
Product Type Technology OS/Software System Architecture Chipset (Wireless) Antenna Type Logical Interfaces Frequency Range (Min) Frequency Range (Max) Antenna Options Bluetooth Version Chipset Connector Data Rate Development Kit Contents Input Power LoRa Version Class Max Transmit Power Output Power Power Consumption (Rx) Power Consumption (Tx) Protocols Range Receive Sensitivity Wireless Specification
DVK-RM191-SM-01 Development Kit Bluetooth 4.1, Dual Mode (Classic + BLE), LoRaWAN smartBASIC Hostless Semtech SX1272, Nordic nRF51822 External Serial, GPIO, SPI, I2C, ADC 902 MHz 928 MHz Dipole Antenna 4 LoRa: Semtech Sx1272. BLE: Nordic Semiconductor nRF51822 USB Pluggable LoRa: 980 bps - 21.9 kbps. BLE: 1 Mbps. Development Kit DVK-RM191 and Free Software Tools 2.1V - 3.5V Internal DCDC converter. 1.8V - 2.1V Internal LDO. LoRaWAN 1.01 (End Device) +15.5 dBm 2mW and 32mW 15.3 mA 45.7 mA LoRa Class A and Bluetooth Low Energy LoRa: Up to 15 km. BLE: Up to 100 m. LoRa: -126 dBm. BLE: -91 dBm. LoRa MAC Class A Specification
Product Type Technology OS/Software System Architecture Chipset (Wireless) Antenna Type Logical Interfaces Frequency Range (Min) Frequency Range (Max) Compliance Data Rate Development Kit Contents Dimension (Height - mm) Dimension (Length - mm) Dimension (Width - mm) Max Transmit Power Power Consumption (Rx) Power Consumption (Tx) Receive Sensitivity Weight
RM186-SM Development Kit Bluetooth 4.1, Dual Mode (Classic + BLE), LoRaWAN smartBASIC Hostless Semtech SX1272, Nordic nRF51822 External Serial, GPIO, SPI, I2C, ADC 865 MHz 870 MHz CE LoRa: 250 bps - 50 kbps, BLE: 1 Mbps Development Kit DVK-RM186 and Free Software Tools 3.1 mm 25.4 mm 25.4 mm 13.5 dBm 12.7 mA 31.4 mA LoRa: -134 dBm. BLE: -91 dBm typical 3 grams
Product Type Technology OS/Software System Architecture Chipset (Wireless) Antenna Type Logical Interfaces Frequency Range (Min) Frequency Range (Max) Compliance Connector Data Rate Development Kit Contents Dimension (Height - mm) Dimension (Length - mm) Dimension (Width - mm) Max Transmit Power Power Consumption (Rx) Power Consumption (Tx) Receive Sensitivity Weight
RM191-SM Development Kit Bluetooth 4.1, Dual Mode (Classic + BLE), LoRaWAN smartBASIC Hostless Semtech SX1272, Nordic nRF51822 External Serial, GPIO, SPI, I2C, ADC 902 MHz 928 MHz FCC/IC SMT LoRa: 980 bps - 21.9kbps, BLE: 1 Mbps Development Kit DVK-RM1xx and Free Software Tools 3.1 mm 25.4 mm 25.4 mm 15.5 dBm 15.3 mA 45.7 mA LoRa: -126 dBm, BLE: -91 dBm typical 3 grams

Documentation

Name Part Type Last Updated
Using BLE and LoRa - RM1xx Series All Application Note 02/28/2019
Using an LCD Keypad Shield - RM1xx Series All Application Note 02/28/2019
Getting Started with Sample Applications - RM1xx Series All Application Note 02/28/2019
Loading and Running Applications with UwTerminalX - RM1xx Series All Application Note 02/28/2019
Connecting to a Multitech Conduit Gateway - RM1xx Series All Application Note 02/28/2019
UwTerminalX Quick Reference Guide All Application Note 02/28/2019
Debug Features - RM1xx All Application Note 02/28/2019
LoRaWAN Keys and IDs Overview All Application Note 02/28/2019
LoRaWAN Range Testing All Application Note 02/28/2019
Upgrading Firmware from your Host Microcontroller All Application Note 02/28/2019
Interfacing with LoRaWAN - RM191 v1.2 All Application Note 02/28/2019
Using DVK-RM1xx with Laird RG1xx Sentrius Gateway and TTN All Application Note 02/28/2019
Key Differences with v4.4.0 Stack – Affects Laird RM191 FW Versions 101.x.x.x and 102.x.x.x All Application Note 02/28/2019
Integrating Cayenne on TTN - RM1xx v1.1 All Application Note 02/28/2019
Upgrading Firmware via UART - RM1xx Series All Application Note 02/28/2019
Interfacing with LoRaWAN - RM186 v1.3 All Application Note 02/28/2019
Application Note - Updating Firmware and Programming RM1xx Modules with the QPK-NRF5x-01 All Application Note 02/28/2019
PCB Notch Antenna Reference Design - RM1xx - v1 0 All Application Note 02/28/2019
LoRaWAN Certification Test Report - RM1xx All Certification 02/28/2019
Bluetooth SIG Certificate - RM1xx All Certification 02/28/2019
EU Declaration of Conformity - RM186 All Certification 02/28/2019
Radio Equipment Directive (RED) Updates - May 2017 All Certification 10/30/2020
User Guide - RM1xx Development Kit All Documentation 02/28/2019
RM1xx Dipole Antenna Datasheet All Documentation 02/28/2019
Release Notes - RM1xx v4.1.0 All Documentation 02/28/2019
Release Notes - RM1xx PE v18-17-1-0 and v17-17-1-0 All Documentation 02/28/2019
Release Notes - RM1xx Central v17 4 1 0 and 18 4 1 0 All Documentation 02/28/2019
Product Brief - RM1xx Series All Documentation 03/07/2019
Overview - Understanding LoRa All Documentation 02/28/2019
RM1xx BLE Central smartBASIC Extensions Guide v1.1 All Documentation 02/28/2019
RM1xx BLE Peripheral smartBASIC Extensions Guide v1.1 All Documentation 02/28/2019
Release Notes - Peripheral RM186 EU v110.6.1.0 - RM191 US v111.6.1.0 - RM191 AU v112.6.1.0 - RM191 AS v113.6.1.0 All Documentation 02/28/2019
Release Notes - Central RM186 EU v100.6.1.0 - RM191 US v101.6.1.0 - RM191 AU 102.6.1.0 - RM191 AS v103.6.1.0 All Documentation 02/28/2019
Datasheet - RM1xx Series All Datasheet 09/20/2019
RM1xx LoRa smartBASIC Extensions Guide v1.3 All Documentation 02/28/2019
User Guide - smartBASIC Core Functionality v3.4 All Documentation 06/22/2020
RM191 CE US 101.6.1.0-r1.zip All Software 01/17/2019
RM191 PE US 111.6.1.0-r1.zip All Software 01/17/2019
3D Models - RM1xx.zip All Software 01/17/2019
DVK-RM1xx Schematic-V1 All Software 02/28/2019
Release Notes-RM186 Peripheral EUv110.6.1.0-RM191 Peripheral USv111.6.1.0-RM191 PE AUv112.6.1.0-RM191 PE ASv113.6.1.0 All Software 02/28/2019
Release Notes - Central RM186 EU v100.6.1.0 - RM191 US v101.6.1.0 - RM191 AU 102.6.1.0 - RM191 AS v103.6.1.0 All Software 02/28/2019
RM186 CE EU 100.6.1.0-r1.zip All Software 01/17/2019
RM186 PE EU 110.6.1.0-r1.zip All Software 01/17/2019
RM191 CE AS 103.6.1.0-r1 ENGINEERING.zip All Software 01/17/2019
RM191 CE AU 102.6.1.0-r1 ENGINEERING.zip All Software 01/17/2019
RM191 PE AS 113.6.1.0-r1 ENGINEERING.zip All Software 01/17/2019
RM191 PE AU 112.6.1.0-r1 ENGINEERING.zip All Software 01/17/2019
EN Certifications - RM186 All Certification 11/12/2020
FCC and IC Certifications - RM191 All Certification 07/22/2019
AS-NZS Certifications - RM191 All Certification 09/20/2019
NCC Certifications - RM191 All Certification 09/20/2019
UwTerminalX – Serial Terminal Utility All Software 04/27/2020
UwFlashX – Serial Firmware Update Utility All Software 04/27/2020
RoHS 3 - Packaged and Cellular Products All Certification 11/10/2020

FAQ

Can I replace smartbasic in the RM1xx with my own C application using the Nordic SDK?

Laird RM1xx modules are supplied with smartBASIC and have an integrated LoRaWAN stack.Programming the nRF51 directly would mean the loss of the Laird smartBasic engine, the integrated stack and the RM1xx LoRaWAN certification. Please contact support to discuss this further.

Can I run an RM1xx as both BLE Central and BLE Peripheral at the same time?

No, the RM1xx can be purchased with either BLE Central role or Peripheral role support but not both. The RM1xx is loaded with either the Nordic S110 peripheral only BLE soft device or the Nordic S120 central only BLE soft device. To support both peripheral and central on the same module we would need to use Nordic's S130 stack, which is not possible when using smart BASIC. Please contact support for more information. 

How do I buy an RM1xx module with Peripheral firmware?

The RM1xx module is currently only sold with Central role BLE firmware, as it was intended to allow the device to scan for peripheral BLE devices, such as BLE sensors, to enable it to collect the data from those devices and pass it via LoRa to the gateway. However, Peripheral firmware is available to be flashed to the module if this is what the application requires. Peripheral BLE cannot scan for devices, it can only send out advertisements, which can request to connect to central role BLE devices. To clarify, the differences between Central and Peripheral are related to establishing a link between the devices.

As we stated previously peripheral can advertise to let central role devices know they are there, only Central can scan or send a connection request to establish the connection. Some refer to the Central as the Master and the Peripheral as the Slave. With BLE a separate unrelated role to Central and Peripheral is that of the GATT Server and GATT Client. The GATT server is the device that contains the data which can be accessed and read by the GATT Client. Please note, there is no connection between the central/peripheral roles and the GATT Server/GATT client roles. While it is common for a Peripheral to be a  GATT Server and a Central to be a GATT Client , it is perfectly possible to have a Peripheral that is only a GATT Client, or a Central that is both a GATT Server and a  GATT Client. The RM1xx configured as a Central, can be both a GATT Client and a GATT Server., and it would have the ability to scan for IOT peripheral devices in the area advertising that they are there. The BLE role has no bearing on the LoRa connection. Either of roles, Central/Peripheral will be able to connect to a LoRaWAN Gateway.

With the above information in mind, if you still feel that the Peripheral firmware will best meet your application needs, than in order to upgrade the firmware on the DVK-RM1xx-SM-02 it would be necessary to purchase a device for flashing the firmware. We would recommend using our QPK-nRF5x programmer , which includes the J-Link ribbon cable , as it should offer the least expensive and easiest way to upgrade between the Central and Peripheral firmware in following the  Upgrading Firmware via JTAG and QPK-nRF5x (Required for Central to Peripheral) - RM1xx Series  Application Note. If however, you would prefer to use a Segger J-Link Probe or Flasher for flashing the Peripheral firmware feel free to contact support for a list of Segger devices which should work with the RM1xx. However, we do not provide additional support for upgrading with these devices outside of the documentation available on our website (Upgrading Firmware via JTAG (REQUIRED for Central to Peripheral) - RM1xx Series). Additional support for these probes/flashers would need to come directly from Segger.

How do I enable the Built-in VSP functionality on the Peripheral role DVK-RM1xx?

In order to enable the built-in VSP functionality on the DVK-RM1xx, SIO_28 must be tied to VCC. There is a jumper, J6, on the DVK-RM1xx board that brings out SIO_28 but it ties it to GND instead of VCC so some alterations must be made.  Using a red jumper cable, connect J6 pin 1 (SIO_28) to J11 pin 3, VCC_LORA, this enables VSP.  Now, select the nAutorun jumper, J12, depending on which VSP mode is needed: nAutorun (SIO_25) == GND (J12 pins 1-2) puts the module into VSP OTA mode which can be used to download smartBASIC scripts OTA to the module.  nAutorun (SIO_25) == VCC (J12 pins 2-3) puts the module into VSP Bridge mode which can be used as a serial cable replacement to transfer UART data.  Now, reset the DVK-RM1xx or power cycle it and it should begin advertising for a VSP connection. If you do not see the advertisements then remove jumpers J10 (DTR) and J5 (RTS) and reset or power cycle the DVK-RM1xx again.  If you are still having issues getting the board to advertise for a VSP connection, please contact support.

What is the difference between ABP and OTAA?

LoRaWAN supports two ways for a device connect to the network.

  1. OTAA: Over the air activation
  2. ABP: Activation by personalization

When using OTAA a join action results in a join request being sent from the RM1xx to the network. The network then checks the Application Identifier (AppEUI) and Application Key (AppKey) provided by the RM1xx. If the APPEUI and APPKey are valid, a join accept message is sent back to the RM1xx which triggers an EVLORAMACJOINED event to be thrown in smart BASIC.

When using ABP there is no handshaking between the RM1xx and the network. As soon as the RM1xx performs a join action it can start sending data. The Application Session Key (AppSKey) and the Network Session Key are set once in both the RM1xx and the network server and must match.

OTAA is the recommended method to join an RM1xx to a LoRaWAN network as it more secure, with the session keys being derived from the APPEUI and APPKey on each connection. Whereas the session keys for ABP remain the same throughout the life of the RM1xx.

What kind of antenna options are available for the RM1xx module and how much do they cost?

What kind of antenna options are available for the RM1xx module and how much do they cost? Will a PCB traced Antenna work? Please reference the certified antenna list in the Datasheet (HIG) for the LoRa/BLE modules.

To get the most range out of the LoRa module it is recommended that an external dipole antenna is used rather than a PCB trace antenna. However, if range is not going to be an issue and none of the approved antennas will work for you application we do offer EMC testing/certification services and could certify any PCB trace antenna you would like through our in-house certifications lab for an additional service fee. As to the cost of the antenna options and/or EMC services, we ask that you contact support or your Regional Sales Representative for that information.