Table of Contents
Advertisement
Quick Links
Advertisement
Table of Contents
Related Manuals for Multitech Reveal RBS301-TILT-US
Summary of Contents for Multitech Reveal RBS301-TILT-US
- Page 1 Reveal™ Wireless Tilt Sensor User Guide...
- 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.
-
Page 3: Table Of Contents
CONTENTS Contents Chapter 1 – Quick Start............................5 Overview ..................................5 Part Numbers ................................5 Documentation ................................5 Chapter 2 – Preparing Sensor........................... 6 Preparing an RBS301 Sensor............................6 Preparing an RBS306 Sensor............................6 Quick Start..................................6 Chapter 3 – Hardware Specifications and Information ..................... 8 Absolute Maximum Ratings ............................ - Page 4 CONTENTS Harmonized Commodity Description (HS Code)......................21 Export Control Classification Number (ECCN)......................21 Reveal™ Wireless Tilt Sensor User Guide...
-
Page 5: Chapter 1 - Quick Start
RBS301-TILT-EU Indoor LoRaWAN Europe RBS301-TILT-AU Indoor LoRaWAN Australia, South America 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 RB00019 information, design considerations, schematics, and general hardware information. -
Page 6: Chapter 2 - Preparing Sensor
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/... - Page 7 PREPARING SENSOR Note: For easy Device ID and Key entry, scan the QR code on the device label. 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. Select the model from the Device Type drop down.
-
Page 8: Chapter 3 - Hardware Specifications And Information
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: Mechanical Drawings
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 Reveal™ Wireless Tilt Sensor User Guide... -
Page 10: Armored Outdoor/Industrial Rbsx06 Sensors
HARDWARE SPECIFICATIONS AND INFORMATION Armored Outdoor/Industrial RBSx06 Sensors Reveal™ Wireless Tilt Sensor User Guide... -
Page 11: Chapter 4 - Common Messages
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. -
Page 12: Reset Message 0X00
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. -
Page 13: Supervisory Message 0X01
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. -
Page 14: Downlink Messages
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.
-
Page 16: Link Quality Configuration
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). Link Quality Configuration The Link Quality configuration command configures the number of failed confirmed message attempts before re- entering the LoRaWAN join state. -
Page 17: Advanced Configuration
COMMON MESSAGES For additional details with usage to ADR_ACK_LIMIT and ADR_ACK_DELAY, refer to LoRaWAN Link Layer Specification v1.0.4 - Section 4.3.1.1: Adaptive data-rate control in frame header. Advanced Configuration Use this command for advanced configuration parameters that apply to all sensor types. The advanced configuration command is defined in the following table. -
Page 18: Downlink Ack
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. -
Page 19: Chapter 5 - Sensor-Specific Messages
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 0x00 Tilt event... -
Page 20: Thresholds
SENSOR-SPECIFIC MESSAGES Thresholds The angle in bytes 1 and 2 define the angle in degrees off of the vertical axis that the sensor needs to be tilted to generate an alert. For example, if the sensor is used to detect garage open/close events, the vertical threshold might be set at 35 degrees and the horizontal threshold may be set at 55 degrees. -
Page 21: Chapter 6 - Regulatory Information
(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.