Only available for Logged-in member. Please login or register to access this information.Or use the Temporary User that we have provided to you via email.
expiry time
1
QUICK INSTALLATION GUIDE
1.1 Introduction
WSLRW-GCB is a LoRaWAN sensor designed to measure toxic gas concentrations. It features high-performance, ultra-low-power gas sensing technology to accurately detect specific gas concentrations in the air. Additionally, the sensor includes a built-in siren for local alarm notifications and a button for local alarm acknowledgment. Its ultra-low-power design and smart firmware enable the sensor to operate on a single battery for 5-10 years. It supports all LoRaWAN frequency plans, making it versatile for global use. The sensor is ideal for monitoring gas concentrations in industrial or commercial buildings in the areas of kitchens, parking garages, boiler rooms, laboratories, basements, HVAC rooms, utility rooms, industrial workspaces and more.
How the sensor connect to system?

System components:
The end nodes are LoRaWAN Sensors or Actuators;
The Gateways are LoRaWAN Gateway or Base Station;
The Network Server can be SAAS or On-premise server;
The Application Server is the destination software users want to utilize the data from/ to LoRaWAN sensors/ actuators.
How to set up the LoRaWAN system? Please follow these steps:
Adding the Gateways to a Network server. Please refer to the manual of Gateway and Network Server software;
Adding the End nodes to the Network Server;
Configure the callback or data forwarding from the Network Server to the Application Software by MQTT or HTTPS. Please refer to the manual of the Network Server.
Once the payload is on the Application server, decode data from Payload. Please check Section 1.9 for the Payload document.
1.2 Application Notes
For Applications
Indoor Air Quality Monitor, Gas Analyzing, Warehouse Monitoring, Gas Leakage Detection
Notes
Select the suitable sensor range to get highest accuracy v.s sensor life. Please consult our engineers;
Life time are 1-2 years for Electro-chemical sensors , depends on sensor type and actual operating conditions;
Calibration cycle are 6-12 months for Electro-chemical sensors, depends on actual operating conditions;
Check carefully the working temperature and humidity of the application;
1.3 When does device send Uplink messages?
The device will send uplink messages in the following cases:
Case 1: After power-up in the 60s, the device will send the first message called START_UP. The payload will tell the user the HW version, FW version, and current configuration of the device.
Case 2: Then, in every interval time (pre-configured), for example, 30 minutes, it will send the message called CYCLIC_DATA. The payload will tell the user the following data like measured values, battery level, and alarm status...
To change the cycle of data sending, you can change the value of the parameter: CYCLIC_DATA_PERIOD.
Case 3: If ALARM_ENABLED=1, the device will send ALARM message immediately when device switches from Normal state to Alarm state. It will repeat sending ALARM messages in predefined ALARM_PERIOD time interval if the Alarm state still exist.
Case 4: During the commissioning, testing, or calibration sensor, the user can force the device to send the uplink message to get the data immediately. This message is called FORCE_DATA. The payload will provide data like raw measured value, scaled measured values, battery level, and alarm status... It can be forced by applying the magnet key on the reed switch in 1s.
Case 5: If users want to change the configuration immediately, they don't need to wait until the next cyclic data-sending message; instead, they can force the device to send a special uplink message so that the device can get the new downlink message. This uplink message is named PARAMETERS_UPDATE. It can be forced by applying the magnet key in more than 5s.
Case 6: In every interval time (pre-configured), for example, 24 hours, it will send the message called HEARTBEAT. The payload will tell the user the following data like hardware version, firmware version, current sensor configuration.
Case 7: If LNS_CHECK_MODE =1, it will send the confirmed uplink message called LNS_CHECK every 24 hours. This confirmed uplink message is a message where a LoRaWAN device is requesting a LoRaWAN network to confirm the reception of its message. If the device receives no confirmation message from LoraWAN network server, it will re-send the LNS_CHECK message every hour during 3 hours. After 4th hour, if the device still receives no confirmation message, it will reset itself to join the network server. The LNS_CHECK payload will tell the user the following data like hardware version, firmware version, current sensor configuration.
Case 8: If the application/network server sends downlink 3 to check current value of a configuration parameter or sends downlink type 4 to change value of a configuration parameter, the device will send the CONFIG-CHECK uplink. The payload of CONFIG-CHECK uplink contains the result of the configuration changes/configuration check.
Case 9: During alarm period, if the users press the ALARM_ACKNOWLEDMENT button on the device to turn off the alarm sound/light, the device will send the ALARM_ACK uplink to inform the user's alarm acknowledgement. The uplink contains the alarm acknowledgement period (unit of second) from the time of alarm initiation to the time of pressing the button.
1.4 Default Configuration
This GCBG4 gas sensor module has the default configuration, however, those parameters can be changed. The user can change the configuration on the wireless transmitter so that the complete sensor (transducer + wireless) delivers the proper output value. Please check the Payload document for more information.
1.5 Battery/ Power Supply
The Device uses below batteries:
Battery type: Primary battery
Battery size and Voltage: size D, 3.6 VDC
Number of batteries: 01
Recommended batteries: Saft LS33600

Battery Installation
Step 1: Open upper housing by unscrewing 1 screw and taking the housing out of the slot

Step 2: Identify the correct battery polarity

Step 3: Insert a D-battery with correct polarity

Step 4: Close the upper housing: Insert the upper housing to the slot and fixed with 1 screw.
Understanding the battery levels:
Level 3 (4 bars): battery energy is 60-99%
Level 2 (3 bars): battery energy is 30-60%
Level 1 (2 bars): battery energy is 10-30%
Level 0 (1 bar): battery energy is 0-10%
1.6 What's in the Package?

1.7 Guide for Quick Test
With the default configuration, the device can be connected quickly to the Network Server by the following steps.
Step 1: Prepare the values of communication settings
Frequency zone: Most of the sensor was configured the frequency zone to suit customer application before delivery
DevEUI: Get the DevEUI on the product nameplate
AppEUI Default value: 010203040506070809
AppKey Default value: 0102030405060708090A0B0C0D0E0F10
Activation Mode: OTAA with local join server
Network Mode: Public
LoraWAN Protocol: version1.0.3
Class: A for sensor; C for actuator
If current basic common settings do not match with your region, network server/application, follow below instruction to change them as below:
For changing other settings, please refer to Section 3.2 Sensor configuration to change the other settings
Step 2: Register the device on the LoRaWAN network server
Input the above settings on your device registration page of the network server.
Note: Different network server software will have different device registration processes. Please refer to the manual of the network server software used for more details.
Please visit the below Section 1.10 to get the instructions for adding the LoRaWAN sensors to some common network servers such as Actility, TTN...
Step 3: Install the batteries to the device OR do power wiring and supply external power to the device if applicable
Please refer to Section 1.5 as above for instructions on battery installation OR for instructions to do power wiring and supply external power to the the device if applicable
After installing the battery in 60 seconds, the first data packet will be sent to the LoRaWAN gateway. After receiving the first data packet, the time of another packet depends on the value of the parameter: cycle_send_data. Additionally, you can use a magnet key to touch the magnetic switch point on the housing within 1 second to initiate force packet of the device to send data instantly and the LEDs on the housing will be lit with SKY BLUE color.
Step 4: Decode the payload of receiving package
Please refer to Section 1.9 Payload Document and Configuration Tables for details of decoding the receiving packet to get the measured values.
If the device has local display, measured values are shown on the local display
1.8 Installation
Dimension Drawings and Installation Gallery (Photos and Videos)


Please follow the checklist below for a successful installation:
1. Have you studied the dimensions of the device as above drawings?
2. Have you tested and make sure the device have been connected successfully as Section "1.7 Guide for Quick Test" above?
3. Have the device been configured properly as per Section 3.2 below?
4. Have the device been calibrated or validated as per Section 3.3 below?
5. Then you can start to install the device at site. Please check the following Installation Notes for Sensor Part (if available) before installation.
Installation Notes for Sensor Part (if available)
Notes: If a sensor has been kept in transport containers at temperatures below zero centigrade, leave it at 10∼35℃ for not less than one hour.* if the Sensor is intended to install outdoors, please use a rain guard to protect the sensor from rain and direct sunlight. Please contact us to buy this accessory.
Place the sensor in the area to monitor the target gas concentration. Please always check the gas molecular weight v.s the air.
Do not use a damaged sensor. It must be repaired only by personnel authorized by the manufacturer.
Keep the sensor out of contact with aggressive substances, e.g., acidic environments, which can react with metals, and solvents, which may affect polymeric materials.
Diffusion holes of the sensor should be protected against the ingress of sprayed liquid or waterdrops, buy using the Splash guard or Rain guard.
The sensor is not intended to measure the target gas concentration contained in fluids.
Correct measurement is provided when the ambient temperature changes not faster than 0.6℃/ min.
Inspection and maintenance should be carried out by suitably trained personnel.
Persons, who have studied this guide, must be briefed on safety precautions when operating electrical equipment intended for use in explosive areas in due course.
When dealing with a cylinder containing a gas mixture under pressure, it is necessary to follow safety regulations.
There is no risk of pollution or negative impact on human health. The sensor does not contain any harmful substances that may be released during its normal operation.
Installation Guide for Main Device
Check the Location for the best RF Signal
Make sure the site is good enough for RF signal transmission.
Tip: To maximize the transmission distance, the ideal condition is Line-of-sight (LOS) between the sensor and the Gateway. In real life, there may be no LOS condition. However, the sensor still communicates with the LoRaWAN gateway, but the distance will be reduced significantly.
DO NOT install the wireless sensor or its antenna inside a completed metallic box or housing because the RF signal can not pass through the metallic wall. The housing is made from Non-metallic materials like plastic, glass, wood, leather, concrete, and cement…is acceptable.
Mounting the Device on the Wall
Step 1: Open the rear housing by using flat head screwdriver and take the rear housing out of the slot

Step 2: Mounting rear housing of the sensor on the wall using 2 provided screws. The mounted location is 30-40 mm from the ground

Step 4: Install the top housing to the rear housing, please take note slot of the housing and fixed with 1 screw. The final installation as below


1.9 Payload Document and Configuration Tables
Please click below button for:
-
Payload decoding of Uplink messages;
-
Payload encoding of Downlink messages;
-
Configuration Tables of device.
Note:
If the content of below web payload, memory map, and sample decoder could not be copied, please install the extension of "Enable Copy Paste - E.C.P" for Microsoft Edge and for Google Chrome.
1.10 How to connect device to Back-end/ Network Server/ Coordinator
Please find below the examples of adding Daviteq's LoRaWAN sensor to the following Network servers:
ThingPark Community (of Actility);
Things Stack (of The Things Network).
You can use the similar methods to add LoRaWAN sensors to other Network Server.
1. THINGPARK COMMUNITY (ACTILITY) NETWORK SERVER
1.1. Example to add the Tektelic LoraWAN gateway Model T0005204 to ThingPark Enterprise SaaS Community
1. Log in to your ThingPark Enterprise account via the link: https://community.thingpark.io/tpe/
2. Browse on the left panel to Base Stations, click the drop-down menu, then click Create.

3. Select the base station’s Tektelic.
※ If you do not find the Tektelic, click View More Manufacturers.

4. On the following screen, select the Model: Micro 8-channels from the drop-down list.

5. Fill the form as below table:
Input exactly as above Input field column, except Name field is user-defined and is different from the existing base station name on the network server.
After filling the registration form, click CREATE to complete adding the base station to the network server.
1.2. Add Daviteq's LoRaWAN devices to ThingPark Enterprise SaaS Community
ThingPark Enterprise supports all Classes of LoRaWAN® devices. By default, the sensor supports Over-the-Air Activation (OTAA) with a local Join Server that is programmed at the factory.
Manual provisioning of OTAA devices using a local Join Server. To learn more, see Activation modes.
1. At left panel of the screen of the Thingpark GUI, click Devices > Create from the dashboard.

2. Select the Generic supported by your device on your screen.

3. Select the Model of LoRanWAN 1.0.3 revA - class A with correct frequency plan

4. Fill the form as below table:
In addition to filling out the form, the option to select the connection between ThingPark and Daviteq application (Globiots).

After filling out the registration form, please click CREATE to add devices to the network server.
1.3. Send a downlink frame from Thingpark Network Server to the device
Follow the below steps to send the downlink frame from Thingpark Network Server to the device:
This functionality is active only when a connection is associated to the device (one of the color codes with a green bullet).
1. Navigate to the left panel, click the Devices' drop-down menu, then click List.

2. Browse the right side in the Devices, click the icon of the device and click Send Downlink.

3. Input the downlink code to the Payload field and input 1 to the Port field, and then click Validate.
The downlink data is added to the device downlink queue in network server. The downlink is sent after the network server receive an uplink from the device.

2. THINGS STACK (THE THINGS NETWORK) NETWORK SERVER
2.1. Add Sentrius LoraWAN gateway (Model RG19) to The things Stack network server
1. Log in to you’re The Things Stack account
2. Click the tab Gateways, click Add gateway button

3. Fill out the form as below table:
Input exactly as above Input column, except the Gateway Name field and the Gateway ID field is user-defined. It is different from the existing gateway name and gateway ID on the network server.
After filling the registration form, click Create gateway to complete adding the base station to the network server.

2.2. Add Daviteq's LoRaWAN device to The Things Stack network server
The Things Stack supports all Classes of LoRaWAN® devices. By default, the sensor supports Over-the-Air Activation (OTAA) with a local Join Server programmed at the factory.
1. Browse on the top panel, click the tab Application, and click Add application button to create an application

2. Fill in the information fields as user-defined, then select Create application

3. After the application is created successfully, select Add end device to register end device (LoRaWAN sensor)

4. Fill out the form as below table:
After filling out the registration form, please click the Register end device button to add the device to the network server.


2.3. Send a downlink frame from The Things Stack Network Server to the device
1. Select the device to send downlink
2. Input 1 to the FPort and input the downlink data in the payload field, and then tick Confirmed downlink and click Schedule downlink.

2
MAINTENANCE
2.1 Troubleshooting
Please find below steps to identify the problems from Communication Part or Sensor Part:
* If the device cannot connect to the Gateway or System or Co-ordinator at the first time, it is the Communication Problem;
* If the device status like battery, RSSI level, data status or other communication is normal, but the measured values are not updated or wrong, it would be the problems of Sensor part;
* If the data coming to gateway, system or co-ordinator is not frequently as expected, the problem would be Communication.
Please refer below the troubleshooting guide for Communication and Sensor Part.
Troubleshooting for Communication
Troubleshooting for Sensor Part (if available)
1. The measured value is not within the expected value
The sensor is drifted over time: Re-calibrate the sensor
The sensor was in a high humidity environment (> 90% RH) for more than 03 days continuously: Place the sensor in low humidity for its recovery. It may take up to 30 days to recover. If the sensor cannot recover after 30 days, please replace the new sensor module.
2. The measured value is always zero or near zero
The sensor module was removed: Please check the sensor;
The sensor is at the end of its life: Replace the sensor module.
2.2 Maintenance
Maintenance for Main device
There is no requirement for maintenance of the Hardware of this LoRaWAN Device except for the following:
1. The battery needs to be replaced. Please check the battery status via uplink messages;
Note: When the battery indicator shows only one bar (or 10% remaining capacity), please arrange to replace the battery with a new one as soon as possible. If not, the battery will drain completely, and the resulting chemical leakage can cause severe problems with the electronic circuit board.
2. Sensor, please refer to the maintenance section of the sensor document.
Maintenance for Sensor part (if available)
Cleaning the Filter: Approx. 3-6 months for Electro-chemical sensors
Check and clean the filter every few months, depending on the environment. Clean the filter with warm water and soap, then use compressed air to purge it from the inside out.
Re-calibration: Approx. 6-12 months for Electro-chemical sensors
The gas sensor may be drifting over time. Please check the sensor specification to identify the interval time for the re-calibration sensor.
3
ADVANCED GUIDE
3.1 Principle of Operation
Principle of Operation for device WSLRW-GCBG4 | FW1
Daviteq LoRaWAN G4 Gas Sensor with Siren for Industrial Safety comprises 02 parts linked internally:
• The Daviteq LoraWAN wireless transmitter;
• The Daviteq LoRaWAN G4 Gas module with Siren for Industrial Safety
What are the primary output values?
• GAS CONCENTRATION: Gas concentration, scaled value, used for alarm. Unit of ppm
GAS_CONCENTRATION = (CONSTANT_A x RAW_RAW_GAS_CONCENTRATION) + CONSTANT_B
Where CONSTANT_A, CONSTANT_B are configured in the sensor memory map.
This parameter equals GAS_CONCENTRATION in the uplink payload
• RAW GAS CONCENTRATION: Raw value of GAS_CONCENTRATION. This parameter equals RAW_GAS_CONCENTRATION in the uplink payload
• ALERT STATUS: Alert status. This parameter equals ALERT_STATUS in the uplink payload
• ACK PERIOD: Acknowledgement period since the alarm is initiated, unit of second. If the period is greater than 65535, the ACK_PERIOD equals 65535. The alarm is acknowledged when the button on the device is pressed to turn off alarm buzzer/light.
This parameter equals ACK_PERIOD in the uplink payload
• TENTATIVE: Tentative number is the number of continuous alarm messages. If the number of continuous alarm messages or cyclic messages are greater than 255, the Tentative keeps value of 255. This parameter equals TENTATIVE in the uplink payload
What are the secondary output values?
Below output values are useful for device maintenance and troubleshooting.
• HW VERSION: Indicate hardware version. This parameter equals HW_VERSION in the uplink payload
• FW VERSION: Indicate firmware version. This parameter equals FW_VERSION in the uplink payload
• CURRENT CONFIGURATION: Latest received and valid downlink frame of CURRENT_CONFIGURATION on device memory map. Detail of CURRENT_CONFIGURATION is at G. MODBUS MEMORY MAP section. This parameter equals CURRENT_CONFIGURATION in the uplink payload
• SENSOR COM ERROR: Communication error code for sensor. This parameter equals SENSOR_COM_ERROR in the uplink payload
• ALERT STATUS: Alert status. This parameter equals ALERT_STATUS in the uplink payload
• BATTERY LEVEL: Battery level. This parameter equals BATTERY_LEVEL in the uplink payload
• START ADDRESS: The start address of the configuration to check. This parameter equals START_ADDRESS in the uplink payload
• NUM OF REGISTER: Number of register of the configuration to check. This parameter equals NUM_OF_REGISTER in the uplink payload
• CONTENT OF REGISTER: Content of configuration, in hexadecimal format. This parameter equals CONTENT_OF_REGISTER in the uplink payload
Principle of operation
Most of the time, the device will be in sleep mode. When the timer reaches the Measure_Period (for example, 30 minutes), it will wake up the device to start the measurement.
*** This Measure_Period will affect the energy consumption of the device.
The measurement will take a certain time to finish; it can take milliseconds or seconds to finish the measurement. This measurement time depends on sensor type, required accuracy, and other factors. Shorter measurement time, lower energy consumption, and longer battery life.
After finishing the measurement cycle, the device can read all the measured parameters.
Main parameter for alarm is GAS CONCENTRATION
If parameter ALARM_ENABLE = 1
Then the device will compare the main parameter to HiHi_Alarm_setpoint and Hi_Alarm_setpoint together with Hysteresis to define the state of the device is No_Alarm or Hi_Alarm or HiHi_Alarm.
Hysteresis value is to avoid the flickering status (Alarm/No-Alarm toggling quickly) when the measured value close to alarm threshold. This device, the hysteresis is zero (fixed value).

If value of main paramter is in Blue color area of above graph, the device is in Normal or No_Alarm state;
If value of main parameter is in Red color area, the device is in HiHi Alarm state (Alarm 2);
None of above 02 states (in Yellow color area), the device will be in Hi Alarm state (Alarm 1).
How the device send uplink message base on above 03 states?
If Device state is No_Alarm, it will check the timer to reach the Cyclic_Data_Period to send the CYCLIC_DATA uplink message;
If Device state is changed from No_Alarm to Hi Alarm or HiHi Alarm, it will send alarm message immediately.
Please check the below picture to understand the operation flow when finishing the measurement cycle:

Once the alarm happens and send the first alarm message, the device will send the next alarm message in the Alarm_Period if the device is still in Alarm states (Hi Alarm or HiHi Alarm), and TENTATIVE value will increase one unit . Please check the picture below to understand the operation flow when the Alarm timer reaches the Alarm_Period. Alarm_Period is fixed value of 10 minutes.

If parameter ALARM_ENABLE = 0
The device will check the timer to reach the Cyclic_Data_Period to send the CYCLIC_DATA uplink message.
Please check the Payload document to understand clearly uplink messages, downlink messages, meaning of parameters for configuration...
Alarm configurations
UNSCALED_HIHI_ALARM_SETPOINT: Unscaled too high alarm set point to calculate HIGHHIGH_ALARM_SETPOINT for GAS CONCENTRATION, unit of ppm
UNSCALED_HI_ALARM_SETPOINT: Unscaled high alarm set point to calculate HIGH_ALARM_SETPOINT for GAS CONCENTRATION, unit of ppm
HIHI_ALARM_FACTOR: Too high alarm factor to calculate HIGHHIGH_ALARM_SETPOINT
HI_ALARM_FACTOR: High alarm factor to calculate HIGH_ALARM_SETPOINT
ALARM_ENABLE: Enable/Disable ALARM event
ALARM_PERIOD: Period of time to send ALARM event
HIGHHIGH_ALARM_SETPOINT:
*If HIHI_ALARM_FACTOR <= 7
HIGHHIGH_ALARM_SETPOINT = UNSCALED_HIHI_ALARM_SETPOINT *(10^HIHI_ALARM_FACTOR)
*If HIHI_ALARM_FACTOR >=8
HIGHHIGH_ALARM_SETPOINT = UNSCALED_HIHI_ALARM_SETPOINT / (10^(16-HIHI_ALARM_FACTOR))
HIGHHIGH_ALARM_SETPOINT:
*If HI_ALARM_FACTOR <= 7
HIGH_ALARM_SETPOINT = UNSCALED_HI_ALARM_SETPOINT * (10^HI_ALARM_FACTOR)
*If HI_ALARM_FACTOR >=8
HIGH_ALARM_SETPOINT = UNSCALED_HI_ALARM_SETPOINT / (10^(16-HI_ALARM_FACTOR))
LEDs & buzzer descriptions
Communication LED: will lit in short time when the device is sending a uplink. The color of the LED is based on sent uplink type. Please refer section 1.9 Payload and Configuration Tables for details of color
Alarm LED & buzzer: The alarm LED will blink and buzzer will ON when alarm event is initiated. The LED color is yellow for high alarm and red for too high alarm. The alarm LED and buzzer will be OFF when the ACKNOWLEDGE button on the device is pressed.
The operation of the alarm LED and the buzzer could be checked by pressing and holding 5 seconds the ACKNOWLEDGE button then the alarm LED will blink once and the buzzer will ON once.
Principle of Operation of Sensor part (if available)
Eletro-chemical measurement technology operation principle for CO, Cl₂, H₂S, H₂, NH₃ sensor
The operation principle of an electrochemical sensor involves reacting with a specific gas of interest and producing an electrical signal proportional to the gas concentration. Here’s how it works:
Components:
Working Electrode: This electrode interacts directly with the gas being detected.
Counter Electrode: It balances the current flow in the system.
Reference Electrode: Provides a stable reference potential.
2. Electrolyte Layer:
The sensor has a thin layer of electrolyte through which charged molecules can pass.
3.Gas Interaction:
The target gas diffuses into the sensor through a gas-permeable membrane.
It reaches the working electrode, where it undergoes oxidation or reduction.
4.Electrochemical Reaction:
The oxidation or reduction of the gas at the working electrode generates an electric current.
This current flows through the external circuit.
5.Signal Output:
The magnitude of the current is directly proportional to the gas concentration.
The sensor translates this current into an observable signal, which can be measured and analyzed
Default Configuration Parameters of Sensor part (if available)
This GCBG4 gas sensor module has the default configuration, however, those parameters can be changed. The user can change the configuration on the wireless transmitter so that the complete sensor (transducer + wireless) delivers the proper output value. Please check the Payload document for more information.
3.2 Configuration
How to configure the device?
Sensor configuration can be configured in 02 methods:
Method 1: Configuring via Downlink messages, port 1 (default)
Method 2: Configuring via Offline cable
To access to the configuration port, open the upper housing by unscrewing 1 screw and take the upper housing out of the slot:

Take out the upper housing, the position of configuration port on the upper housing as below figure:

Note:
The sensor is only active for offline configuration in the first 60 since power up by battery or plugging the configuration cable.
Which Parameters are configured?
Please check Part G in Section 1.9 Payload Documents above.
Method 1: Configuration via Downlink messages
Please check the Part D & E in Section 1.9 Payload Documents above.
Method 2: Configuration by Offline Cable
Please download the Configuration Template File of this sensor to be used in Step 4 below.
Instructions for offline configuration of the Daviteq LoRaWAN sensors. Please follow the following steps.
Note: The sensor is only active for offline configuration in the first 60 since power up by battery or plugging the configuration cable.
1. Prepare equipment and tools
The following items must be prepared for configuration.
A PC using the Windows OS (Windows 7 or above versions). The PC installed the COM port driver of the Modbus configuration cable (if needed). The driver is at link: Modbus Configuration Cable COM port driver for PC and the instruction to install the driver at link: How to install the driver.
A Modbus configuration cable
Tools to open the plastic housing of LoRaWAN sensors (L hex key or screwdriver)
2. Download and launch Daviteq Modbus configuration software
Click the link below to download Daviteq Modbus configuration software:
https://filerun.daviteq.com/wl/?id=yDOjE5d6kqFlGNVVlMdFg19Aad6aw0Hs
After downloading the software, unzip the file named: Daviteq Modbus Configuration.zip and then copy the extracted folder to the storage drive for long-term use.
Open the folder, double click on the file Daviteq Modbus Configuration Tool Version.exe to launch the software and the software interface as below:

Note: The software only runs on Microsoft Windows OS (Windows 7 and above).
3. Connect the cable and configure the sensor
Step 1:
Connect the PC to the sensor using the configuration cable.
- Use the configuration cable (Item code: TTL-LRW-USB-01).

- Connect the USB-A plug into the USB-A socket of the PC.

Step 2:
On the configuration software, choose the relevant Port (the USB port which is the cable plugged in) and set the BaudRate: 9600, Parity: none
Step 3:
Click Connect button to connect the software to the sensor. After successful connection, the Connected status will show on the software.

Step 4:
Import the configuration template file of the sensor (as above link) to the software: click menu File/ Import New and then browse the relevant sensor template file (csv file) and click Open to import the template file.
Note: The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor.
Each sensor type has its own template file. Refer to the sensor's manual to download the correct file.
Step 5:
Open the housing of the sensor and quickly plug the connector of the configuration cable into sensor's modbus configuration port as below figure. After plugging the connector, the software will read the parameter values automatically.

Plug the cable connector into sensor's modbus configuration port. This port is located at a different location, depends on the sensor type
Note: If the sensor has SKU of WSLRWEX-PPS and hardware version 1 & 2, the sensor must be powered by batteries for configuration
Step 6:
Read the current value of the parameter with Modbus Function 3
At the relevant row of the parameter, check box 3 on column Func to read the value of the parameter. The read value is shown in VALUE ON MEMMAP column.

The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. After 60 seconds, the TIME_OUT text will show on EXCEPTION column of the software.
Step 7:
Write the new setting to the parameter with Modbus Function 16
Double click on the column VALUE TO WRITE of the parameter and input the new setting value of the parameter;
Uncheck the tick on the FC column of the parameter, click on the arrow, select 16 and then check on the FC column to write a new setting to the parameter. The WRITE_OK text will show on EXCEPTION column if the software successfully writes the setting.

Repeat Step 6 to read the setting of the parameter for double-checking.
Note: For some critical parameters of the sensor, the password in "password for setting" must be written before writing the new settings to these parameters.
Only read/ write registers are allowed to write.
The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. After 60 seconds, the TIME_OUT text will show on EXCEPTION column of the software.
4. Troubleshooting
3.3 Calibration/ Validation
How to force sensor to send data for calibration/ validation (if available)
Using the magnet key, the device can be triggered to send data to the Gateway immediately. Touch the magnet key to magnetic point on the device housing within 1 second to trigger sending force message.


Note:
Upon transmitting the data to the base station using the magnetic key, the timer for the transmission time interval will be reset.
The minimum time interval between two manual triggers is 15 seconds. If the interval is less than 15 seconds, data transmission will not occur.
Calibration/ Validation sensor (if available)
The Daviteq GCBG4 Gas Sensor must be connected to a reading device, it usually is a wireless transmitter like Sub-GHz, Sigfox, or LoRaWAN.
Why do we need to calibrate the gas sensor?
There are some reasons:
- The output value of a sensor is different from the other sensor. It is not the same value for all sensors after manufacturing.
- The output value of a sensor will be changed over time.
Therefore, users need to calibrate the sensor before use or in a pre-defined interval time (30 months for example).
How to calibrate the GCBG4 Toxic Gas sensor?
Please follow steps for Instruction to attach the calibration cap onto the sensor module to get Zero or Span values:
Step 1. Remove the sensor filter by pulling the filter by hand. The filter is attached to the sensor by 2 small magnetic points
Step 2. Prepare calibration cap
Step 3. Attach the calibration cap to the sensor head
Step 4. Installed the Regulator to the Gas cylinder
Step 5. Attach the tube to the regulator and calibration cap
Please select the flow regulator with a flow rate of 2.5 LPM or 5.0 LPM.
With the 2-point calibration method, the user can define the A and B factors. Please find below the steps of calibration.
Step 1. Get the Zero value.
- Power ON the device;
- Place the device in a clean-air environment (the target value is nearly zero) at a temperature from 20∼30℃, in at least 60 minutes.
- After 60 minutes, force the device to send data, read and record the Raw_Gas_Concentration, so now you got the Zero_value = Raw_Gas_Concentration value.
Recommendation: Record many Raw_Gas_Concentration values at least 10 minutes apart (10 values). Zero value is the average of the recorded Raw values.
Note: The Raw_Gas_Concentration values can be positive or negative;
Step 2. Get the Span value
Note: Keep the sensor Power ON all the time
- Use the standard gas cylinder with a known concentration (for example NH3 100ppm ) to supply the gas to the sensor;
- Use the calibration cap as above pictures to attach to the sensor and connect the tubing to the gas cylinder;
- Open the valve on the Cylinder slowly and make sure the gas has reached the sensor. The flow regulator should be 2.5 LPM or 5.0 LPM.
Notes: The tube length is short as possible to reduce the gas loss.
- Press a timer to start counting the time;
- After 2 minutes, force the device to send data once every minute, and stop forcing at 5 minutes;
- The highest Raw_Gas_Concentration is the Span value.
Note: Just get one value for Span.
- After that, immediately turn OFF the valve to save the gas;
- Remove the calibration cap from the sensor;
- Place the sensor in clean air again.
Note: Always keep the sensor Power ON all the time.
Step 3. Calculate the new A and B
The calculation of new A, B value based on basic linear formula:
y = A * x + B
Where:
A, B is calibration coefficients
x is the sensor process value (example gas level in ppm) read on reading device such as on application server/network server, on offline tool. The process value is the RAW_VALUE in the payload
y is the correct value. y is the value of standard gas/standard condition
Which condition of Zero value: y₀ = A * x₀ + B
Which condition of Span value: yₛ = A * xₛ+ B
From the two formulas, the calculation of A, B as below
A = (y₀ - yₛ) / (x₀ - xₛ)
B = (yₛ * x₀ - y₀ * xₛ) / (x₀ - xₛ)
Example of A, B calculation for LoraWAN Ammonia Gas sensor (item code WSLRW-G4-NH3-100-01):
* With condition of clean-air environment at a temperature from 20∼30℃, there is no ammonia gas (y₀ = 0); while the NH₃ level on reading device (RAW_VALUE in the payload) is -0.25 (x₀ = -0.25)
* When the sensor is connected to standard gas cylinder having ammonia level of 25 ppm (yₛ = 25); while the NH₃ level on reading device (RAW_VALUE in the payload) is 18.66 (xₛ = 18.66)
The calculation of A, B for the Ammonia gas sensor:
A = (0 - 25) / (-0.25 - 18.66) = 1.32205
B = (yₛ * x₀ - y₀ * xₛ) / (x₀ - xₛ) = (25 * (-0.25) - 0 * 18.66) / (-0.25 - 18.66) = 0.33051
The factory default A = 1 and default B = 0
The RAW_VALUE in the payload is used for calibration
Step 4. Configure the new A and B into the device
- User can use the off-line tool or downlink to write the values of A and B;
- Writing the new A and B successfully meant you had done the calibration process.
4
PRODUCT SPECIFICATIONS
4.1 Specifications
Type of measuring gas | Choose 1 of CO, CL₂, H₂S, H₂, NH₃ gases |
Measurement technology | High performance Electro-Chemical sensor |
Measuring range | CO 0-500ppm, H₂S 0-100ppm, H₂ 0-1000ppm, NH₃ 0-100ppm, CL₂ 0-20 ppm |
Resolution | 0.1ppm for CO, H₂S, NH₃, H₂ and 0.01ppm for CL₂ |
Reading stability | For CO, Cl₂, H₂S, H₂, NH₃, refer Daviteq's Electro-Chemical gas sensor link : |
Sensor working temperature | -20∼60°C |
Sensor Working humidity | 15-90% RH, non-condensing |
Operating pressure | 80kPa to 120kPa |
Local functions | Alarm sound and alarm acknowledgement |
SF Factors | SF7∼SF12 |
RF Frequency and Power | 860∼930MHz, 14∼20 dBm, configurable for zones: EU868, IN865, RU864, KR920, AS923, AU915, US915 |
Protocol | LoRaWAN, class A |
Antenna | External antenna |
Data sending mode | Cycle, alarm and magnet key. |
RF module compliant | ETSI EN 300 220, EN 303 204 (Europe) FCC CFR47 Part15 (USA), ARIB STD-T108 (Japan) |
Configuration | Via downlink (only for some configurations) or USB cable (PC software provided free of charge) |
Battery | 01 x LiSOCl2 3.6V size D battery |
Housing | ABS, IP40 |
Dimensions | H260xW150xD90 (with external antenna) |
Net weight | 280 grams (without battery) |
Installation | Wall mounting with screws |
5
WARRANTY & SUPPORT
5.1 Warranty
Warranty
Below terms and conditions are applied for products manufactured and supplied by Daviteq Technologies Inc.
Free Warranty Conditions
The manufacturer undertakes to guarantee within 12 months from shipment date.
Product failed due to defects in material or workmanship.
Serial number, label, warranty stamp remains intact (not purged, detected, edited, scraped, tore, blurry, spotty, or pasted on top by certain items).
During the warranty period, if any problem of damage occurs due to technical manufacturing, please notify our Support Center for free warranty consultancy. Unauthorized treatments and modifications are not allowed.
Product failed due to the defects from the manufacturer, depending on the actual situation, Daviteq will consider replacement or repairs.
Note: One way shipping cost to the Return center shall be paid by Customers.
Paid Warranty
The warranty period has expired.
The product is not manufactured by Daviteq.
Product failed due to damage caused by disasters such as fire, flood, lightning or explosion, etc.
Product damaged during shipment.
Product damaged due to faulty installation, usage, or power supply.
Product damage caused by the customer.
Product rusted, stained by effects of the environment or due to vandalism, liquid (acids, chemicals, etc.)
Product damage is caused by unauthorized treatments and modifications.
Note: Customers will be subjected to all repairing expenses and 2-way shipping costs. If arises disagreement with the company's determining faults, both parties will have a third party inspection appraise such damage and its decision be and is the final decision.
5.2 Support
Support via Help center
If you need our support for Daviteq device's installation, configuration, test, and decode, please email us at: support@daviteq.com OR input support request at link: https://forms.office.com/r/XWHbYG7yy7
Our support engineer will contact you via email or the support ticket system.
If you have any questions about the product, you can search for information on our web (https://www.iot.daviteq.com/). If you can't find the right information, please register an account and send us a request at link Contact us | Daviteq Technologies . We will respond within 24 hours.