Page 2
Trademarks and Registered Trademarks MultiTech, the MultiTech logo, DeviceHQ, xDot, and Conduit are registered trademarks and Reveal and mDot are trademarks of Multi-Tech Systems, Inc. All other products and technologies are the trademarks or registered trademarks of their respective holders.
Console, use the following steps. To use a third-party network, refer to the Connecting Radio Bridge LoRaWAN Sensors on Gateways and Networks (RB00001) , which is available through the sensor page at https://www.multitech.com/products/sensors Create a Radio Bridge console account at: https://console.radiobridge.com/...
QUICK START Documentation The following documentation is available at https://www.multitech.com/products/sensors. Document Description Part Number User Guide This document provides overview, safety and regulatory RB00004 information, design considerations, schematics, and general hardware information. Connection Guide This document provides instructions and information on how...
PREPARING SENSOR Chapter 2 – Preparing Sensor Preparing an RBS301 Sensor Sensors ship with batteries installed. There is a plastic tab over the battery, which needs to be removed. Pull the tab out of the sensor to connect the battery. If the tab does not pull out easily, you may need to open the case to remove it.
Page 7
PREPARING SENSOR Insert the new battery and close the case. Wireless Acceleration Sensor User Guide...
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).
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 Wireless Acceleration Sensor User Guide...
Sensor Specific Messages chapter. Message Protocol This section defines the protocol and message definitions for the device. Note: MultiTech provides a web-based console at console.radiobridge.com for configuring and monitoring devices. We recommend using this console rather than the protocols defined in this section.
COMMON MESSAGES Message Payload Description 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 Period). 0xfe Reserved. 0xff 1-byte status Downlink message ACK. Refer to Downlink ACK for more detail.
COMMON MESSAGES Supervisory Message 0x01 Wireless sensors periodically 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. To do this: Place a magnet near the triangular notch on the side of the sensor.
COMMON MESSAGES Bytes Description Current Sub-Band, sub-band currently joined and used for communication to the gateway and network server. Value ranges from 1-8 for US915. For other regions, value depends on available channels. RSSI of last DOWNLINK received, signed integer format values in bytes 1 and 2 in two’s complement format.
Page 15
COMMON MESSAGES 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) Enable duty cycle requirement. LoRaWAN EU868 only. To enforce the EU868 band duty cycle requirements, enable before production deployment.
COMMON MESSAGES Bit 7:6 Bits 5:0 Sampling period defined in increments of 250ms (0.25-15 seconds). Sampling period defined in increments of seconds (1-63 seconds). Sampling period defined in increments of minutes (1-63 minutes). Sampling period defined in increments of hours (1-63 hours). Advanced Configuration Use this command for advanced configuration parameters that apply to all sensor types.
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).. Byte Description Movement event The movement event byte is defined in the following table...
Page 19
SENSOR-SPECIFIC MESSAGES The scaling parameter defines the G-force (1g is the force of gravity) range that the internal accelerometer operates with, and the lower settings will be more sensitive than higher settings. The threshold setting will have units based on the scaling factor as shown in the table above. For example, if the scaling is set to +/- 2g (2x the force of gravity), then the threshold setting can be multiplied by 0.016g to calculate the total G-force threshold.
(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 REVEAL RBS301-ABM and is the answer not in the manual?
Questions and answers