Netvox RA02G Wireless Cigarette Smoke, Vaping, and Bullying Alarm Sensor User Manual

1. Introduction

The RA02G is an indoor sensor capable of detecting smoking, noise, and anti-tamper events. It includes new functionalities such as power outage detection, sensitivity adjustment, audio alerts customization, and PoE splitter connection. The RA02G aims to simplify indoor monitoring.

LoRa Wireless Technology

LoRa is a wireless communication technology known for its long-distance transmission and low power consumption. Its spread spectrum modulation technique significantly extends communication range, making it suitable for long-distance, low-data wireless communications. Applications include automatic meter reading, building automation, wireless security systems, and industrial monitoring. LoRa features small size, low power consumption, long transmission distance, and strong anti-interference capabilities.

LoRaWAN

LoRaWAN utilizes LoRa technology to establish end-to-end standard specifications, ensuring interoperability between devices and gateways from various manufacturers.

2. Appearance

The RA02G sensor features a circular design with several key components:

• Smoking Adjustable Knob: A knob located on the device for adjusting smoking detection sensitivity.
• Noise Adjustable Knob: A knob located on the device for adjusting noise detection sensitivity.
• Indicator: A light indicator providing status feedback.
• Function Key ①: A primary function button.
• Function Key ②: A secondary function button.

The device can be powered by a 12V adapter or a 12V PoE splitter. The PoE splitter is not included with the RA02G purchase.

3. Features

• Power supplied by 12V power adapter and PoE splitter.
• 2x AAA 1.5V Alkaline batteries as backup power.
• Type-C port for audio alerts transmission.
• Smoking, noise, and anti-tamper detection.
• Power outage detection.
• Compatible with LoRaWAN™ Class C.
• Frequency hopping spread spectrum.
• Applicable to third-party platforms: Actility/ThingPark, TTN, MyDevices/Cayenne.

4. Set up Instructions

Function Key Operations

5. Data Report

The device immediately sends a version packet report and a data packet including IncenseSmokeAlarm, HighSoundAlarm, ShockAlarm, and PowerOffAlarm. Data is reported by default settings before any configuration.

Default Setting Parameters

Alarm and Indicator Status

Indicator symbols: ● remain on, ◔ flash slowly, ⚡ flash.

Sensitivity Adjustment of Smoking and Noise Detection

(1) Smoking detection (IncenseSmokeAlarm): Sensitivity levels range from 1 (High) to 4 (Low). Each level corresponds to a 45° turn of the knob.

(2) Noise detection (HighSoundAlarm): The lower the HighSoundAlarmTriggerThreshold, the higher the sensitivity. Sensitivity levels are ordered: Level 1 > Level 2 > Level 3 > Level 4.

Adjusting Sensitivity through Knobs: Turn clockwise to decrease sensitivity for both smoking and noise. The noise knob is typically turned to the middle before shipment.

Adjusting Sensitivity through Commands:

• Set SmokesensorSensitivity: Range 0x01 to 0x14. (Last setting saved on factory reset).
• Set HighSoundAlarmTriggerThreshold and HighSoundAlarmTriggerDuration: Range 0x0001 to 0xFFFE.

Testing Result of Noise Detection (for reference)

Test results obtained at 1 meter horizontal distance between detector and noise source.

(3) Anti-tamper alarm (ShockAlarm)

1. Configuration range: 0x01 to 0x14.
2. When ShockSensorSensitivity = 0xFF, vibration detection is off. Default setting is 0x0A.
3. 10 seconds after turning on, the vibration sensor begins detection.

(4) Power Outage Detection (PowerOffAlarm)

The PowerOffAlarm functions only when backup batteries are inserted.

1. When powered by backup batteries, all audio alerts stop working.
2. Backup batteries can support the device for 1 hour.
3. Check and reconnect the device with DC power to avoid false reports.

For resolving uplink data, visit the Netvox LoRaWAN Application Command document and Netvox LoRa Command Resolver at http://www.netvox.com.cn:8888/cmddoc.

5.1 Example of ReportDataCmd

FPort: 0x06

The ReportDataCmd structure includes CmdID (1 byte), DeviceType (1 byte), ReportType (1 byte), and NetvoxPayLoadData (variable bytes, max 9 bytes).

• CmdID: 1 byte.
• DeviceType: 1 byte – identifies the device type.
• ReportType: 1 byte – indicates the presentation of the NetvoxPayLoadData.
• NetvoxPayLoadData: Variable bytes (Max=9 bytes).

Tips

1. Battery Voltage: If battery value is 0x00, the device is powered by DC.
2. Version Packet: When Report Type is 0x00, it's a version packet (e.g., 01D7000A03202309250000 indicates firmware version 2023.09.25).
3. Data Packet: When Report Type is 0x01, it's a data packet.

Example of Uplink (01D7010000010000000000): This uplink indicates: Version (01), DeviceType RA02G (D7), ReportType (01), DC power supply (00), IncenseSmokeAlarm=noalarm (00), HighSoundAlarm=alarm (01), ShockAlarm=noalarm (00), PowerOffAlarm=noalarm (00), Reserved (000000).

5.2 Example of Report Configuration

FPort: 0x07

Configuration commands also follow a structure of CmdID (1 byte), DeviceType (1 byte), and NetvoxPayLoadData (variable bytes, max 9 bytes).

Command Configuration Examples:

1. Command Configuration (MinTime=15min, MaxTime=15min): Downlink: 01D7038403840000000000. Response: 81D7000000000000000000 (Success) or 81D7010000000000000000 (Failure).
2. Read Configuration: Downlink: 02D7000000000000000000. Response: 82D7038403840000000000 (Current configuration).
3. SetSmokeSensitivityReq (0x02): Downlink: 03D7020000000000000000. Response: 83D7000000000000000000.
4. GetSmokeSensitivityReq: Downlink: 04D7000000000000000000. Response: 84D7020000000000000000.
5. SetShockSensorSensitivityReq (20 / 0x14): Downlink: 05D7140000000000000000. Response: 85D7000000000000000000. Note: Vibration value configurable between 0x01 to 0x14. If 0xFF, vibration detection is off.
6. GetShockSensorSensitivityReq: Downlink: 06D7000000000000000000. Response: 86D7140000000000000000.
7. SetHighSoundAlarmTriggerThresholdTimeReq (Threshold=10 / 0x0A; Duration=10s / 0x0A): Downlink: 07D7000A000A0000000000. Response: 87D7000000000000000000. Note: If Threshold or Duration is 0xFFFF, noise detection is off.
8. GetHighSoundAlarmTriggerThresholdTimeReq: Downlink: 08D7000000000000000000. Response: 88D7000A000A0000000000.
9. SetBeeperDurationReq (DisableBeeper / 0x0000): Downlink: 09D7000000000000000000. Also, BeeperDuration=20s (0x0014), AlarmSoundLevel=10 (0x0A): Downlink: 09D700140A000000000000. Response: 89D7000000000000000000.
10. GetBeeperDurationReq: Downlink: 0AD7000000000000000000. Response: 8AD7014000000000000000.
11. StopCurrentBeeperAlarmReq: Downlink: 0BD7000000000000000000. Response: 8BD7000000000000000000.
12. SetSmokeDebounceandResumeCheckTimeReq (Debounce=5min; Resume=10s): Downlink: 0CD7012C0A000000000000. Response: 8CD7000000000000000000. Device starts detection after debounce time ends. During resume time, device reports no alarm if data is below threshold.
13. GetSmokeDebounceandResumeCheckTimeReq: Downlink: 0DD7000000000000000000. Response: 8DD7012C0A000000000000.

5.3 Example of NetvoxLoRaWANRejoin

This section describes how the device checks if it's still in the network and automatically rejoins if disconnected. FPort: 0x20.

Command Configuration Examples:

1. Command Configuration (RejoinCheckPeriod=60min, RejoinThreshold=3): Downlink: 0100000E1003. Response: 810000000000 (Success) or 810100000000 (Failure).
2. Read current configuration (RejoinCheckPeriod=60min, RejoinThreshold=3): Downlink: 020000000000. Response: 8200000E1003.

5.4 Example for MinTime/MaxTime logic

This logic governs when the device reports data based on time intervals and data variation.

Example #1 (MinTime = 1 Hour, MaxTime = 1 Hour, BatteryVoltageChange = 0.1V): The device wakes up, collects data, and reports 3.6V. Data is reported only according to MaxTime (MinTime) duration, regardless of BatteryVoltageChange value.

Example #2 (MinTime = 15 Minutes, MaxTime = 1 Hour, BatteryVoltageChange = 0.1V): The device wakes up and collects data at 0H, 15thM, 30thM, 45thM, 1H, and 2H. It reports 3.6V at 0H, 1H, and 2H. It does not report at 15thM, 30thM, 45thM if data variation is not significant enough to trigger a report before MaxTime.

Example #3 (MinTime = 15 Minutes, MaxTime = 1 Hour, BatteryVoltageChange = 0.1V): This example illustrates reporting based on data change and button pushes. If data changes significantly (e.g., 3.5V to 3.5-3.6-0.1V), it reports. If a user pushes a button, it reports and recalculates MaxTime. Otherwise, it reports at MaxTime intervals if no significant change or button push occurs.

6. Audio Alerts Customization

1. Connect the computer and device using a TYPE-C cable.
2. Wait 1 to 2 minutes for the virtual USB drive to appear.
3. Right-click the USB Drive and select 'Format'.
4. Click 'OK' to start formatting. A warning will appear stating that formatting will erase all data. Confirm by clicking 'OK'.
5. Once formatting is complete, turn the device off and then on again. The flash drive should now be empty.
6. Create a new folder named '01' in the USB Drive.
7. Place all audio alert files (00x.mp3 or 00x.wav) into the '01' folder. Default names are: 001: anti-tamper detection; 002: noise detection; 003: smoking detection.

7. Installation

• The RA02G has a detection range of 12m². The optimal installation location is the center of the ceiling.
• Avoid installation near vents, electrical appliances, or in environments with extreme temperatures or excessive dust, as these may affect device operation and accuracy.
• The RA02G provides alerts for potential dangers. Users should remain aware of their surroundings to prevent damage and disasters.
• Due to high smoking detection sensitivity, false alarms may occur. Users might need to adjust sensitivity for different environments.

1. Open the battery cover.
2. Remove the battery holder and insert 2x AAA 1.5V Alkaline batteries.
3. Close the battery cover.
4. Mount the base on the ceiling using screws.
5. Align the RA02G with the mounted base and turn clockwise to secure it.
6. Connect the RA02G to a DC12V power supply and plug in the adapter.

8. Important Maintenance Instructions

To ensure optimal product maintenance, observe the following guidelines:

• Keep the device dry. Moisture or liquids containing minerals can corrode electronic circuits. If the device gets wet, dry it completely.
• Do not use or store the device in dusty or dirty environments, as this can damage detachable parts and electronic components.
• Avoid storing the device in excessively hot conditions. High temperatures can shorten the life of electronic devices, destroy batteries, and deform or melt plastic parts.
• Do not store the device in overly cold places. When the temperature rises to normal, moisture may form inside, damaging the circuit board.
• Do not throw, knock, or shake the device. Rough handling can damage internal circuit boards and delicate structures.
• Do not clean the device with strong chemicals, detergents, or strong solvents.
• Do not apply paint to the device, as smudges can block it and affect operation.
• Do not dispose of batteries in fire, as they may explode. Damaged batteries can also explode.

If any device, battery, or accessory is not working properly, take it to the nearest authorized service facility for repair.