RBS301-CON-US Indoor LoRaWAN North America RBS306-CON-US Outdoor/Industrial LoRaWAN North America Documentation The following documentation is available at https://www.multitech.com/brands/reveal-wireless-proximity-sensors. Document Description Part Number User Guide This document provides overview, safety and regulatory RB00015 information, design considerations, schematics, and general hardware information.
Use your sensor through either the console or a third-party network. To use the console, use the following steps. To use a third-party network, refer to the Connecting LoRaWAN Sensors on Gateways and Networks (RB00001) , which is available through the sensor page at https://www.multitech.com/products/sensors Create a console account at: https://console.radiobridge.com/ Click on Devices on the left.
PREPARING SENSOR Note: For easy Device ID and Key entry, scan the QR code on the yellow key card included with your device. Then copy and paste data into the console. With the QR code, the first line is the Device ID and the rest is the key.
Refer to the Sensor Battery Estimator.xlsx spreadsheet on the on the sensor's product page for specific battery life estimates: https://www.multitech.com/products/sensors Battery life depends on the number of transmissions per day. Power required for a message transmission is greater than the “sleep current” for high power radio technologies (e.g, LoRaWAN).
Page 9
HARDWARE SPECIFICATIONS AND INFORMATION Remove the battery. Insert the new battery as shown. Close the case. ® Radio Bridge LoRaWAN Wireless Sensor Dry Contact Sensor User Guide...
HARDWARE SPECIFICATIONS AND INFORMATION Mechanical Drawings The mechanical drawings provided in this section are for the main body of the sensor. All dimensions use inches unless specified. Indoor RBSx01 Sensors ® Radio Bridge LoRaWAN Wireless Sensor Dry Contact Sensor User Guide...
HARDWARE SPECIFICATIONS AND INFORMATION Armored Outdoor/Industrial RBSx06 Sensors ® Radio Bridge LoRaWAN Wireless Sensor Dry Contact Sensor User Guide...
Chapter 4 – Common Messages Common Messages This chapter defines the protocol and message definitions common to all MultiTech wireless sensors. Common messages include basic error messages, tamper, supervisory, link quality, and downlink acknowledgments. Sensor specific messages are in the Sensor Specific Messages chapter.
COMMON MESSAGES Message Type Payload Description 0x02 1-byte event A tamper event has occurred. Refer to Tamper Message 0x02for details. Sensor event Sensor events are defined in the Sensor Specific Messages chapter. 0xfb Link quality Sent after each downlink configuration (refer to Link Quality Message) or to periodically ping the network server (refer to Link Quality Check...
COMMON MESSAGES 0x8823 is decoded as Firmware Version 2.1.3 Supervisory Message 0x01 Wireless sensors periodically (19 hours by default) send a supervisory message so the backend system can verify the device is still alive and report error conditions. The supervisory message payload include current sensor status. You can also trigger a supervisory message.
COMMON MESSAGES Link Quality Message 0xfb The link quality message provides a signal strength and a signal to noise measurement at the device itself. The link quality message payload is shown in the following table. Bytes Description Current Sub-Band, sub-band currently joined and used for communication to the gateway and network server.
Page 16
COMMON MESSAGES Disable Sensor Events The following table shows the disable sensor event bit definitions. Description Not used Disable all sensor events Radio Config The following table shows the radio config byte definition. Note: Available in firmware version 1.4 or newer. Bits Description Not used (reserved)
Page 17
COMMON MESSAGES Refer to the Battery Estimator for battery life estimates relative to sampling rate: https://radiobridge.com/documents/Sensor%20Battery%20Estimator.xlsx A value of 0 in this field leaves the sampling rate at the current value. Use the following table to determine the sampling rate if the value is not zero. Note: Sampling period only applies to sensors that take measurements like temperature and tilt, it does not apply to sensors with binary inputs such as door/window sensors or push buttons.
COMMON MESSAGES Device Info Request The Device Info Request command is a downlink to inform the gateway to report its downlink configuration information. Description 0x00 Downlink configuration type to request. 0-254: Request device info for specific downlink type to report. 255: Request device info for all downlink configurations.
COMMON MESSAGES ADR Advanced Configuration The ADR configuration message overrides the LoRaWAN ADR_ACK_LIMIT and ADR_ACK_DELAY parameters. Byte Description 0x00 ADR_ACK_LIMIT value when running in Unconfirmed Mode. The default value is 64. 0x01 ADR_ACK_DELAY value when running in Unconfirmed Mode. The default value is 32. 0x02 ADR_ACK_LIMIT value when running in Confirmed Mode.
COMMON MESSAGES Downlink ACK The cloud app uses this downlink ACK message to verify the that sensor received the downlink message received and it was considered valid. The sensor replies to the downlink data with a 0xFF message (downlink ACK) with the payload shown in the following table.
SENSOR-SPECIFIC MESSAGES Chapter 5 – Sensor-Specific Messages Uplink Messages The uplink message (sensor to web application) specific to the sensor is defined in following table. The common uplink messages are not included in this section (see common messages document). Event Payload Description 0x00 Contacts shorted (connected)
Page 22
Lithium cells and batteries are subject to the Provisions for International Transportation. Multi-Tech Systems, Inc. confirms that the Lithium batteries used in the MultiTech product(s) referenced in this manual comply with Special Provision 188 of the UN Model Regulations, Special Provision A45 of the ICAO-TI/IATA[1]DGR (Air), Special Provision 310 of the IMDG Code, and Special Provision 188 of the ADR and RID (Road and Rail Europe).
Page 23
(1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Per FCC 15.21, Changes or modifications not expressly approved by MultiTech could void authority to operate the devices.
Need help?
Do you have a question about the RBS301-CON-US and is the answer not in the manual?
Questions and answers