Manual for LoRaWAN Sensor Manual for LoRaWAN Sensors - Common parts What is LoRaWAN? Understanding the LoRaWAN Connectivity Technologies. Please find this link for understanding the LoRaWAN Connectivity Technologies.Troubleshooting for LoRaWAN communication This is the troubleshooting for the LoRaWAN sensors with FW versions listed below: No. Phenomena Reason Solutions 1 The BLUE LED does not blink when the battery is installed Insert the batteries in the wrong direction Insert the battery in the correct way 2 The RED LED is always on Due to noise, the peripheral components (i2c, spi, uart, ..) of RF module cannot be initialized After the 30s the node will automatically reset. If the noise causes the Watchdog not to initialize, remove the battery and wait for more than 10 seconds, then insert the battery again 3 The RED LED blinks continuously (10ms ON / 2s OFF) and the Node does not send RF. After more than 10 sending cycles, the Node will automatically reset · Operating frequency in that country is prohibited · Operating frequency in that country is limited to Data rate, Tx Power · Reconfigure the allowed frequency of operation · Reconfigure Data rate = DR5 / SF07, Tx Power 4 RED LED blinks continuously (10ms ON / 2s OFF) and Node sends RF continuously 3s / time but no data. After more than 10 sending cycles, the Node will automatically reset Node runs dummy sending mode => sent by Gateway to send Downlink packets when users clear Uplink and Downlink counter values on Network Server (build-in Gateway) when activated by ABP Configuration enabled by OTAA 5 The RED LED flashes 10ms ON / 10s OFF and the Node does not send RF Node activation by OTAA on the Network server has not been successful Using Magnet-Key to force Node to send RF continuously for 3 seconds/time => when activating by OTAA successfully, the GREEN LED will blink after sending RF 6 The node sent RF successfully but the GREEN LED did not blink LED is broken Warranty to replace LED 7 The data packet taken from the Gateway has an incorrect value The data package is encrypted Get the decoded packet on the Application Server 8 The node sends RF and activates by ABP, on Gateway receives data but Application server has no data The application server still stores the counter values of the previous Uplink and Downlink Delete the counter values of Uplink and Downlink on the Application server 9 The node does not send RF and the RF module is hot · Insert the battery in the opposite direction · Short circuit Warranty or replacement 10 Node does not send RF to Gateway according to the alarm, LED does not blink · The alarm configuration is incorrect · Running out of the number of alarms set for the day · Check alarm configuration · Check the configuration for the maximum number of alarms per day 11 Node does not send RF to Gateway when activated by the magnetic switch, LED does not blink The magnetic switch has malfunctioned Read the status of the magnetic switch via Modbus (when powering or attaching the battery) to see if the magnetic switch is working. 12 Node has blinked LED GREEN when sending RF but the Gateway or Application server cannot receive · LoRa module on the Gateway is faulty · The IP connection (4G / WiFi / ...) on the Gateway is faulty · Check Gateway's LoRa status lights on Gateway · Check 4G / WiFi status lights on Gateway 13 The value of the sensor is 0 and sensor_type = 0xFF Lost connection with the sensor · Check sensor connection · Replace the module sensor 14 RSSI is weak and often loses data · Distance between Node and Gateway is far or there are many obstructions · Connection to Antenna problem · Install metal nodes or in metal cabinets · Configure Data rate = DR0 / SF12 · Check Antenna position · Install Node in a well-ventilated location 15 After power-up, the device keeps sending the start-up message in a pre-defined cycle. At least one battery was draining off. Use VOM to check the voltage of the battery. The voltage of each battery must be higher than 1.2V for normal operation. 16 On network server, device's join request package and network server's acceptance package are available, but no data package is received on the network server Wrong configuration of LoraWAN device version/model on network server. Configure correct version/model for LoraWAN device (LoRaWAN 1.0.3 revA -  Class A ) on network server Offline configuration for LoRaWAN sensors 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 (win7 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 Tool.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 (win7 and above). 3. Connect the cable and configure the sensor Step 1: Connect USB plug of Modbus configuration cable to USB socket of the PC - 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 the “ Connect “ button to connect the software to the sensor. After a successful connection, the connected status(green text) will show on the software. Step 4: Import the configuration file for the sensor 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. Each sensor type has its own template file. Refer to the sensor's manual to download the correct file. The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. Step 5: Open the housing of the sensor and quickly plug the connector of the configuration cable into sensor's modbus configuration port. After plugging the connector, the software will read the parameter values automatically. - Open the housing of the sensor. - Plug the cable connector into sensor's modbus configuration port. Note: this port is located at a different location, depends on the sensor type The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. Step 6: Read the current value of the parameter with function 3 At the relevant row of the parameter, check box 3 on column FC to read the value of the parameter. The read value is shown on 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 function 16 Double click on the column VALUE TO WRITE of the parameter and input the new setting 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 checking. 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. 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. 4. Troubleshooting No. Phenomena Reason Solutions 1 The status on the software always shows Disconnected although the configuration cable is connected to the PC The selected COM port is incorrect. The cable is defective Select the correct COM port to which the configuration cable connects to the PC Check the cable 2 The software reads no value after importing the right template and connecting the right cable. The cable is defect or loose connection The USB port is defective There is no power supply to the sensor via configuration cable The sensor is defective Check or replace the new configuration cable Check USB port Check the power line of the cable Check the sensor 3 No COM port appears in the Port list No configuration cable is plugged to the PC The cable driver is not installed on the PC Plug the cable to the PC Install the driver for the PC 4 The parameter table on the software is empty The template file has not been imported Go to File/Import New to import the template file 5 The parameter table on the software does NOT match the memmap table of the sensor. The wrong template file is imported. Go to the correct manual page of the product and download the right template file, then import the template file into the software. 5. List of Configuration Template Files for various LoRaWAN Sensors Because each LoRaWAN sensor has many parameters to configure or read, the number could be up to a hundred. To simplify the process of reading and writing those parameters, we divide the parameters list into multiple files. Please download all the Template files at this link. END.List of Configuration Template Files for various LoRaWAN Sensors THIS IS OBSOLETE MANUAL Please access https://www.iot.daviteq.com/wireless-sensors for updated manual OR Email to support@daviteq.com to open support ticket.Common notes in installation of LoRaWAN Sensors The common instructions for all kinds of Daviteq LoRaWAN Sensor. Please see below. 1. HOW DO YOU GET A STRONG RF SIGNAL? To maximize the distance of transmission, the ideal condition is Line-of-sight (LOS) between the LoRaWAN sensor and the Base station (LoRaWAN Gateway). In real life, there may be no LOS condition. However, the LoRaWAN sensor still communicates with the Base station, 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. 2. INSTALL BATTERIES FOR LORAWAN SENSORS 2.1 INSTALL BATTERIES FOR LORAWAN SENSOR WITH BLUE BOX DESIGN Steps for battery installation: Step 1: Using L hex key to unscrew M4 screws at the side of the housing and carefully pull out the top plastic housing in the vertical direction Step 2: Insert 02 x AA 1.5VDC battery, please take note the poles of the battery ATTENTION:REVERSED POLARITY OF BATTERIES IN 10 SECONDS CAN DAMAGE THE SENSOR CIRCUIT!!! Step 3: Insert the top plastic housing and locking by L hex key ATTENTION:When reinstalling the cover, pay attention to put the PCB edge into the middle slot of the box inside as shown below) 2.2 INSTALL BATTERIES FOR LORAWAN SENSOR WITH RECTANGULAR WHITE PLASTIC HOUSING DESIGN Steps for battery installation: Step 1: Use flat head screws to push into 2 reed joints Step 2: Open the housing, then insert 06 x AA 1.5VDC battery, please take note of the poles of the battery ATTENTION: REVERSED POLARITY OF BATTERIES IN 10 SECONDS CAN DAMAGE THE SENSOR CIRCUIT!!! Step 3: Insert the top plastic housing (Please note the 2 reed joints) 2.3 INSTALL BATTERIES FOR LORAWAN SENSOR WITH CIRCULAR WHITE PLASTIC HOUSING DESIGN 3. MOUNTING FOR LORAWAN SENSOR WITH BLUE BOX HOUSING 3.1 MOUNTING FOR LORAWAN SENSOR WITH BLUE BOX DESIGN The following are the steps for the LoRaWAN sensor with a Blue box housing design. Step 1: Install bracket on the sensor Step 2: Determine the mounting position and secure the sensor with the included screws Step 3:Grounding the sensor 3.2 MOUNTING FOR LORAWAN SENSOR WITH RECTANGULAR WHITE PLASTIC HOUSING DESIGN Step 1: Determine the direction of the sensor If the sensor has a direction, for example, the LoRaWAN Lidar People Counter, please take note of the direction of the sensor before installation Step 2: Mount the bottom housing of the sensor to the ceiling by fastening the 2 screws to the ceiling located at the 2 diagonal corners of the bottom cover. Use the 2 screws that are included to be used to attach the sensor to surfaces such as Wood, and composite plastic. If the ceiling surface is made of plaster, it is recommended to use a special insert so that the device can firmly adhere to the ceiling surface. Avoid dropping the device. Step 3: Attach the top and bottom housings (note the 2 reed joints) Fit the main body to the bottom cover in the correct direction: the 2 reed joints on the bottom cover should fit into the main body on the side labeled with the device. Make sure that the main body is fully engaged with the bottom cover, then release the hand. 3.3 MOUNTING FOR LORAWAN SENSOR WITH EXD-APPROVED HOUSING 3.4 MOUNTING FOR LORAWAN SENSOR WITH CIRCULAR WHITE PLASTIC HOUSING DESIGN Configuration in Network Server 1. THINGPARK COMMUNITY (ACTILITY) NETWORK SERVER 1.1. Add 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: Field Input field Name As user-defined LRR-UUID Contact the Tektelic Support to get LRR-UUID for Thingpark. Details at linkInstruction to get inf... | Online Product Manuals & Datasheets (daviteq.com) RF region Site frequency plan (US915, EU868..) Public Key Contact the Tektelic Support to get LRR-UUID for Thingpark. Details at linkInstruction to get inf... | Online Product Manuals & Datasheets (daviteq.com) Input exactly as above Input field column, except Name field is user-defined and is different from existing base station name on the network server. After filling registration form, click CREATE to complete adding 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 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: Field Input field Name As user-defined DevEUI DevEUI is on label of the device or is on the device memory map Activation mode Over-the-Air Activation (OTAA) with local Join Server JoinEUI Input JoinEUI. This value is read on memory map or is on the label of the device. The default value is 0102030405060708 AppKey Input AppKey.This value read on memory map or on the label of the device. The default value is 0102030405060708090A0B0C0D0E0F10 In addition to filling the form, option to select the connection between Thingpark and Daviteq application (Globiots) After filling 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 below steps to send 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's drop-down menu then click List. 2. Browse the right side in the DEVICES, and click ... icon of the device and click Send Downlink. 3. Input downlink code to 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  LoraWAN gateway to The things Stack network server. Log in to you’re The Things Stack account Click tab Gateways, click Add gateway button Fill the form as below table: FIELD INPUT GatewayEUI EUI of gateway. This information can be found on the gateway's label Gateway name As user-defined Gateway ID As user-defined Frequency plan Input right frequency plan (Ex: Australia 915-928 MHz, FSB 2 (used by TTN)) Input exactly as above Input column, except Gateway Name field and Gateway ID field is user-defined and is different from existing gateway name and gateway ID on the network server. After filling registration form, click CREATE GATEWAY to complete adding 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 local Join Server that is programmed at the factory. Browse on the top panel, click tab Application, click Add application button to create an application Fill in the information fields as user-defined then select Create application After the application is created successfully, select Add end device to register end device ( LoraWAN sensor) Fill the form as below table: FEILD INPUT Frequency name Input correct frequency plan (Ex: Australia 915-928 MHz, FSB 2 (used by TTN)) DevEUI As DevEUI on label of the device or  read from device memory map Activation mode Over-the-Air Activation (OTAA) with local Join Server AppEUI Input AppEUI. This value read on device memory map or on the label of the device. The default value is 0102030405060708 AppKey Input AppKey.This value read on device memory map or on the label of the device. The default value is 0102030405060708090A0B0C0D0E0F10 Lorawan version Must be choose version 1.0.3 After filling the registration form, please click 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 Select the device to send down link Input 1 to the FPort and input the downlink data in the payload field, untick Confirmed downlink  and click Schedule downlink Note:-DON'T check the Confirmed downlink for downlink the message Guide for Firmware Loading of LoRaWAN Sensor Manual for LoRaWAN Sensors - Type 1 LoRaWAN Sensors - Types 1 are Lidar People Counter... Manual for LoRaWAN Lidar People Counter - WSLRW-LPC | FW 1.0 THIS IS OBSOLETE MANUAL Please access https://www.iot.daviteq.com/wireless-sensors for updated manual Thank you very much for choosing Daviteq Wireless Sensors. We are the leading wireless sensor manufacturer in the World. We have a wide range of wireless sensors which support different connectivity like LoRaWAN, Sigfox, Sub-GHz, NB-IoT...Please find out more information at this link. This manual is applied to the following products Item code HW Version Firmware Version Remarks WSLRW-LPC-01 1.0 1.0 Information Changes in this version v.s previous version Item Changes Changed by Changed Date Approved by Approved Date 1 Initial version P.N.Diep 09-05-2022 N.V.Loc 28-05-2022 To use this product, please refer step by step to the below instructions. Operating Principle Uplink Payload Battery Connect to Gateway Installation Troubleshooting Configuration Calibration Specification Warranty and Support 1.  Quick Guide Reading time: 10 minutesFinish this part so you can understand and put the sensor in operation with the default configuration from the factory. 1.1 What is the LoRaWAN Lidar People Counter sensor and its principle of operation? WSLRW-LPC is a LoRaWAN sensor with a built-in advanced Lidar sensor to detect and count people. It can count the people walking thru a gate in 2-way with an accuracy higher than 95%. This sensor utilizes lidar technology, which is not affected by temperature, humidity, and RF noise and is less affected by ambient light... It is battery-operated and able to connect to any LoRaWAN gateways. It supports all frequency zones. For the principle operation of the Lidar people counter, please refer to this link. 1.1.1 What are the typical applications of this sensor? Please refer to this link for typical applications. 1.1.2 When does the device send uplink messages? In most cases, the device will not send the uplink message immediately when there is a person or object passing thru the gate, as this operation will cause the battery to drain off quickly. Instead, it will send uplink messages in the following cases: Case 1: Send an uplink message in the pre-defined cycle For example, every 10 or 30 minutes. In this case, it will send the updated counting values. There are 02 counting values in the payload: - Resettable counter. - Non-resettable counter. Note: we do recommend using a non-resettable counter. To change the cycle of data sending, you can change the value of the parameter: Cycle send data (default is 900 seconds) Case 2: Send an uplink message upon a certain number of people passing thru! In case, if you want the device to send an uplink message upon a certain number of people passing thru the gate then you can configure the following parameter: count_threshold. The default value is 20. What does it mean? It means when the resettable_counter reaches the number 20 (20 people pass thru in one direction, for any direction), the device will send the uplink message. After sending, it will reset the resettable_counter to zero for counting again in the next cycle. The count_threshold can be configured to any value from 1. Case 3: Send uplink on demand! During commissioning the sensor, you can manually trigger the data sending by applying the Magnet key so that the device will send data immediately. Note: the time interval between the 02 triggers must be larger than 15 seconds. In summary, the device will send the uplink messages in 03 cases: - Case 1: when the time of the Data sending cycle is reached. - Case 2: when the value of the resettable counter is larger than the pre-defined count threshold. - Case 3: when the device is forced to send data by a Magnet key. Send uplink as quickly as possible!In some special use cases, if you need the device to send an uplink message upon there is a person or object passing thru the gate, then you need to configure the following parameters:* Count_threshold = 1* Sensor_sampling_rate = 10 (10 seconds is smallest value for battery saving) 1.1.3 The important configuration parameters The sensor was pre-configured at the factory with default values for configuration parameters that meet the most use cases. However, depending on the specific use case, the customer can adjust those parameters. Please refer to section 3.2 for more details. 1.1.4 What kind of battery is used for this sensor? The sensor is smart, thanks to the integrated PIR sensor. If there were no people around it will fall to the sleep stage to save battery. If there were people nearby, it will wake up in a very short time and then be ready to count people passing thru. The sensor is powered by 6 x AA 1.5V batteries for many years of operation. We do recommend using Energizer L91 battery which is very popular and high performance. This battery has a capacity of up to 3500mAh with a working temperature range from -40 to +60 oC. The instruction for installing the batteries is in this link. For Battery life estimation, please refer to this link. 1.2 What's in the package? The package includes:01 x Lidar sensor01 x Magnet key02 x Self-tapping screw M4 1.3 Quick Test for LoRaWAN Sensor 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 version 1.0.3 Class A Note: If the above settings do not match your network server/application, please refer to section 3.2 Sensor configuration to change the 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 processes for registering the device. Please refer to the manual of the network server software being used for more details. Please visit this link 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 Refer to this link for details. 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 force the device to send data instantly. Step 4: Decode the payload of receiving package Please refer to section 1.4 Uplink Payload and Data Decoding for details of decoding the receiving packet. 1.4 Uplink Payload and Data Decoding For the Uplink Payload structure, please refer to this link. Note: Please select the right Payload document to suit the FW version of the sensor 1.5 Sensor Installation ATTENTION:- DO NOT INSTALL THE SENSOR OUTDOOR OR INDOORS WITH HIGH-INTENSITY OF SUNLIGHT;- DO NOT INSTALL THE SENSOR AT A PLACE WHERE HIGH DUST PARTICLES OR STEAM AFFECT THE OPTICAL SENSOR;- DO NOT INSTALL THE SENSOR AT A PLACE WHERE THE PEOPLE MOVING IN PARALLEL AND NEARBY THE SENSOR, THAT WILL CAUSE THE SENSOR TO WAKE UP ALL THE TIME, BUT NOT FOR COUNTING PEOPLE. THIS PROBLEM WILL MAKE THE BATTERIES DRAIN OFF QUICKLY IN A FEW DAYS. WARNING:- Avoid placing hands or heavy objects on the laser sensor surface or the PIR sensor surface, as this may cause damage to the device;- Periodically use a clean cloth moistened with 70 degrees of alcohol to wipe the surface of the 2 sensors to keep the sensor clean and accurate. DEVICE DIMENSIONS 1.5.1 Mounting sensor on the ceiling Please take note of the direction of people entering the room of the sensor Then follow this link for instructions on mounting the sensor on the ceiling. 1.5.2 Battery Installation Please follow the instructions in this link. 1.5.3 Sensor calibration Depending on the height of installation, the distThreshold parameter may need to change to an appropriate value so that the sensor can count accurately. Please follow the steps in this link. 2. Maintenance 2.1 Troubleshooting Problems with LoRaWAN communication like not receiving the packets...please refer to this link to troubleshoot the device. Problems with the sensor functions like not measuring, or inaccurate measuring....please refer to this link to troubleshoot the sensor part. 2.2 Sensor maintenance Maintenance works Yes/No Descriptions Consumable parts replacement No The lidar sensor is not a consumable part, there is no need to replace the sensor module Cleaning sensor or device Yes Check and clean the surface of the lidar sensor and PIR sensor. Please refer to this link; Re-calibration / Re-validation No 3. Advanced Guide 3.1 Operating principle of LoRaWAN Lidar People Counter 3.1.1 Operating principle of the complete device The Daviteq LoRaWAN Lidar People Counter comprises 02 parts linked internally as shown below picture. - The Daviteq LoRaWAN module;- The Daviteq Lidar People Counter; The people counting module is working independently from the wireless module. That means while the counting module is counting people, the wireless module may be in sleep mode to save battery. The wireless module will wake up and read data from the counting module to check the counting value periodically (120 seconds as default, configurable) to see whether the counter increase so that it will decide to send a message or not. The 120 s is the default value of parameter sensor_sampling_rate. You can reduce this value, but smaller value, shorter battery life! The device will send the uplink messages in 03 cases: - Case 1: when the time of the Data sending cycle is reached. - Case 2: when the value of the resettable counter is larger than the pre-defined count threshold. - Case 3: when the device is forced to send data by a Magnet key. 3.1.2 Operating principle of Lidar People Counting Module To understand how Lidar technology can count people, please refer to this link for a complete understanding of this measuring technique. 3.1.3 Some important configuration parameters Below are some important configuration parameters which affect the operation of the device. sampling_rate | Default = 120sThe counting module is working independently from the wireless module. That means while the counting module is counting people, the wireless module may be in sleep mode to save battery. The wireless module will wake up and read data from the counting module to check the counting value periodically (120 seconds as default, configurable) to see whether the counter increase so that it will decide to send a message or not. The 120 s is the default value of parameter sensor_sampling_rate. You can reduce this value, but smaller value, shorter battery life! count_threshold | Default = 20With this threshold, the device will send an uplink message when the resettable_counter reaches this threshold. After sending, the resettable _counter will be reset to zero again. distThreshold | Default = 1600mmChange this parameter to suit the height of the sensor cycle_send_data | Default = 3600sInterval time to send an uplink message regardless of any conditions Those configuration parameters can be changed by downlink or offline tools. For more other configuration parameters, please refer to the next section. 3.2 Sensor Configuration 3.2.1 How to configure the LoRaWAN Lidar People Counter? Sensor configuration can be configured in 02 methods: Method 1: Configuring via Downlink message. Please find the instructions in this link, but please take note of the FW version of the Document. Method 2: Configuring via offline cable. Note: THE SENSOR IS ONLY ACTIVE FOR OFFLINE CONFIGURATION IN THE FIRST 60 SINCE POWER UP BY BATTERY OR PLUGGING THE CONFIGURATION CABLE. 3.2.2 What parameters of the device are configured? Some parameters are read-only, and some are read and writeable. To read the parameters, use the off-line cable as above instruction. To write the parameters, use the off-line cable or downlink as above instructions. Below tables are the lists of the parameters of the device. Read-only Parameter Table Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 0 0 3 5 device info WSLRW-I2C string Read Wireless Sensor LoRaWAN - I2C 5 5 3 4 firmware version 1.00ddmm string Read ddmm = day / month 9 9 3 2 hardware version 1.10 string Read 11 B 3 4 lorawan protocol version 01.01.00 string Read LoRaWAN v1.1.0 15 F 3 6 application version 01.03.00.00 string Read application server v1.3.0.0 21 15 3 6 mac layer version 04.04.02.00 string Read mac layer v4.4.2.0 27 1B 3 4 deviceEUI hex Read End Device's EUI number, used to register the product on the Network Server by OTAA 31 1F 3 4 Lora appEUI hex Read Application server's EUI number is used to register the product on the Network Server by OTAA 35 23 3 8 Lora appKey hex Read The number of keys used to create two security keys of the End Device, used to register the product on the Network Server by OTAA 43 2B 3 8 Lora nwkSkey hex Read key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 51 33 3 8 Lora appSkey hex Read End Device data encryption key number, used to register the product on the Network Server by ABP 59 3B 3 2 device address 0 uint32 Read End Device address created by the Application server, used to register the product on the Network server by ABP 61 3D 3 2 network ID 0 uint32 Read Network server ID number, used to register the product on the Network server by ABP 63 3F 3 2 join mode OTAA string Read OTAA: Over-the-Air activation, ABP: Activation by Personalization 65 41 3 4 network mode PUBLIC string Read PUBLIC, PRIVATE 69 45 3 3 region code AS923 string Read 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 72 48 3 4 data rate DR2:980 string Read DR0:250, DR1:440, DR2:980, DR3:1760, DR4:3125, DR5:5470 76 4C 3 3 bandwidth BW125 string Read BW125, BW250, BW500 79 4F 3 2 spread factor SF10 string Read SF12, SF11, SF10, SF9, SF8, SF7 81 51 3 4 activation of ADR ADR OFF string Read ADR ON, ADR OFF 85 55 3 1 class A string Read 103 67 3 1 sensor type 1-255 uint16 Read 1-254: sensor type, 255: no sensor 104 68 3 1 battery level 0-3 uint16 Read 4 levels of battery capacity status Read/Write Parameter Table Note: Please check the column Property for identifying which parameter request a password for writing a new value. In this case, the user needs to input the password (190577) into the parameter name "password for setting" at address 268. Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 256 100 3 / 16 1 Modbus address 1-247 1 uint16 R/W Modbus address of the device 257 101 3 / 16 1 Modbus baudrate 0-1 0 uint16 R/W 0: 9600, 1: 19200 258 102 3 / 16 1 Modbus parity 0-2 0 uint16 R/W 0: none, 1: odd, 2: even 259 103 3 / 16 9 serial number string R/W (Password) 268 10C 3 / 16 2 password for setting uint32 R/W (Password) password 190577 270 10E 3 / 16 4 Lora appEUI hex R/W (Password) Application server's EUI number, used to register the product on the Network Server by OTAA 274 112 3 / 16 8 Lora appKey hex R/W (Password) The number of keys used to create two security keys of the End Device, used to register the product on the Network server by OTAA 282 11A 3 / 16 8 Lora nwkSkey hex R/W (Password) key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 290 122 3 / 16 8 Lora appSkey hex R/W (Password) End Device data encryption key number, used to register the product on the Network Server by ABP 298 12A 3 / 16 2 device address uint32 R/W (Password) End Device address created by the Application server, used to register the product on the Network server by ABP 300 12C 3 / 16 2 network ID uint32 R/W (Password) Network server ID number, used to register the product on the Network server by ABP 302 12E 3 / 16 1 activation mode 0-1 1 uint16 R/W (Password) 1: OTAA (Over-the-Air Activation), 0: ABP (Activation by Personalization) 304 130 3 / 16 1 application port 1-255 1 uint16 R/W (Password) Port 224 is reserved for certification 305 131 3 16 1 network mode 0-1 1 uint16 1: Public, 0: Private 317 13D 3 / 16 1 region 1-7 1 uint16 Read/Write(Password) 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 318 13E 3 / 16 1 data rate 7 uint16 R/W (Password) 0: 250 bps, 1: 440 bps, 2: 980 bps, 3: 1760 bps, 4: 3125 bps, 5: 5470 bps 319 13F 3 / 16 1 tx power 2-20 16 uint16 R/W (Password) tx power: 2,4,6,8,10,12,14,16,18,20 320 140 3 / 16 1 adaptative data rate 0-1 0 uint16 R/W (Password) Automatically adjust data rate, 0: disable, 1: enable 334 14E 3 / 16 2 cycle send data 900 uint32 R/W sec (data sending cycle) 340 154 3 / 16 2 sensor1: sampling_rate 120 uint32 R/W sec (frequency of data taken from sensor 1) 384 180 3 16 count_threshold 20 uint16 Threshold count on how many people send Gateway 385 181 3 16 dist_threshold 1600 uint16 Threshold setting for laser sensor to distinguish between when people are present and when no one is standing under the sensor.The laser sensor will measure the distance value from the sensor (ceiling) to the floor.+ When there are people, the measured laser sensor value < Dist_threshold+ When there is no person, the measured laser sensor value > Dist_threshold 386 182 3 16 dist_hys 100 uint16 Hysteresis  of Dist_threshold 387 183 3 16 inter_meas_period 48 uint16 The sampling time of the sensor laser 3.3 Calibration or commissioning for Lidar people counting sensor Please refer to this link. 4. Product specification Please refer to the detailed specifications in this link. 5. Warranty and Support For warranty terms and support procedures, please refer to this link. 6. References Use-cases: Case studies: White-papers: END. Manual for LoRaWAN Sensors - Type 2 LoRaWAN Sensors - Type 2 are Tilt sensor, Soil moisture, Humidity, Gas... the sensor with Blue box housing. Manual for LoRaWAN G4 Gas Sensor - WSLRW-G4 | FW 1.0 THIS IS OBSOLETE MANUAL Please access https://www.iot.daviteq.com/wireless-sensors for updated manual Thank you very much for choosing Daviteq Wireless Sensors. We are the leading wireless sensor manufacturer in the World. We have a wide range of wireless sensors which support different connectivity like LoRaWAN, Sigfox, Sub-GHz, NB-IoT...Please find out more information at this link. This manual is applied to the following products Item code HW Version Firmware Version Remarks WSLRW-G4-... 1 1 Information Changes in this version v.s previous version Item Changes Changed by Changed Date Approved by Approved Date 1 Initial version P.N.Diep 22-06-2022 N.V.Loc 24-08-2022 To use this product, please refer step by step to the below instructions. Operating Principle Uplink Payload Battery Connect to the LoRaWAN Gateway Installation Troubleshooting Configuration Calibration Specification Warranty and Support 1.  Quick Guide Reading time: 10 minutesFinish this part so you can understand and put the sensor in operation with the default configuration from the factory. 1.1 What is the LoRaWAN G4 Gas Sensor and its principle of operation? WSLRW-G4 is a LoRaWAN electrochemical-type gas sensor with a high sensitivity to low concentrations of detected gas, high selectivity, and a stable baseline. The device supports different types of gas such as CO, NO, NO2, H2S, NH3, O2, O3, SO2, Cl2, HCHO...Ultra-low Power design and smart firmware allow the sensor to last up to 5 years with a 02 x AA-type battery (depends on configuration). The sensor will transmit data at a kilo-meters distance to the LoRaWAN gateway, any brand on the market. For the principle operation of the G4 Gas Sensor module, please refer to this link. 1.1.1 What are the typical applications of this sensor? Please refer to this link for typical applications. 1.1.2 When does the 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, 10 minutes, it will send the message called CYCLIC_DATA. The payload will tell the user the following data like measured value, battery level, alarm status... To change the cycle of data sending, you can change the value of the parameter: CYCLIC_DATA_PERIOD (default is 600 seconds). Case 3: If the Alarm function was enabled (in the configuration of the sensor), if the measured value passed the threshold, it will send the uplink message immediately. This message is called ALARM. The payload also tells the user the data like measured value, battery level, alarm status... The alarm thresholds can be changed via downlink or offline tools. Case 4: During commissioning, testing, or calibration sensor, the user can force the device to send the uplink message so that they can get the data immediately. This message is called FORCE_DATA. The payload will provide data like raw measured value, scaled measured value, battery level, 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. 1.1.3 The important configuration parameters The sensor was pre-configured at the factory with default values for configuration parameters that meet most use cases. However, depending on the specific use case, the customer can adjust those parameters. Please refer to section 3.2 for more details. 1.1.4 What kind of battery is used for this sensor? The sensor is powered by 2 x AA 1.5V batteries for many years of operation. We do recommend using Energizer L91 battery which is very popular and high performance. This battery has a capacity of up to 3500mAh with a working temperature range from -40 to +60 oC. The instruction for installing the batteries is in this link. For Battery life estimation, please refer to this link. 1.2 What's in the package? The package includes:01 x Main device01 x Magnet key01 x Wall mounting bracket and screws 1.3 Quick Test for LoRaWAN Sensor 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 version 1.0.3 Class A Note: If the above settings do not match your network server/application, please refer to section 3.2 Sensor configuration to change the 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 processes for registering the device. Please refer to the manual of the network server software being used for more details. Please visit this link 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 Refer to this link for details. 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 force the device to send data instantly. Step 4: Decode the payload of receiving package Please refer to section 1.4 Uplink Payload and Data Decoding for details of decoding the receiving packet. 1.4 Uplink Payload and Data Decoding For the Uplink Payload structure, please refer to this link. Note: Please select the right Payload document to suit the FW version of the sensor 1.5 Sensor Installation ATTENTION:- IF INSTALLING THE SENSOR OUTDOORS, PLEASE ATTACH THE RAIN GUARD TO PROTECT THE SENSOR FROM THE RAINDROPS OF SNOW. THE RAIN GUARD IS ALSO A RADIATION SHIELD. PLEASE REFER TO THE BELOW FIGURE. WARNING: DO NOT SPRAY THE WATER DIRECTLY TO THE SENSOR AREA (THE BOTTOM PART AND THE VENTING PARTS OF THE RAIN GUARD) 1.5.1 Dimension drawings 1.5.2 Battery Installation Please follow the instructions in this link. 1.5.3 Sensor calibration and configuration The LoRaWAN G4 Gas sensor needs to be calibrated for the first use and re-calibrated in the next 6 or 12 months. It may be pre-calibrated by the manufacturer before shipping. Please check the details in your Purchase order. If so, you can skip this step and proceed to the next step. 1.5.4 Sensor mounting on wall or pole Please follow this link. 2. Maintenance 2.1 Troubleshooting Problems with LoRaWAN communication like not receiving the packets...please refer to this link to troubleshoot the device. Problems with the sensor functions like not measuring or inaccurate measuring....please refer to this link to troubleshoot the sensor part. 2.2 Sensor maintenance 2.2.1 Maintenance of Wireless transmitter Maintenance works Yes/No Descriptions Consumable parts replacement Yes The battery is the only part need to check the lifetime to replace. Check the battery status on the back-end system. Cleaning device No Re-calibration / Re-validation No No calibration is required for the wireless transmitter BUT is needed for the sensor part. 2.2.2 Maintenance of the G4 Gas sensor module Please refer to this link. 3. Advanced Guide 3.1 Operating principle of LoRaWAN G4 Gas Sensor 3.1.1 Operating principle of the complete device The Daviteq LoRaWAN G4 Gas Sensor comprises 02 parts linked internally as shown below picture. - The Daviteq LoRaWAN wireless transmitter;- The Daviteq G4 Gas sensor module; The G4 gas sensor module measures the gas concentration in the surrounding environment. The LoRaWAN wireless transmitter is to read the measurement values from the G4 sensor and performs the scaling and calculation to deliver the desired output values, then it sends data to the gateway in the following cases: - Case 1: when the time of the Data sending cycle is reached. - Case 2: when the measured value is over the preset threshold. - Case 3: when the device is forced to send data by a Magnet key. 3.1.2 Operating principle of G4 gas sensor module To understand how the G4 gas sensor module work, please refer to this link for a complete understanding of this measuring technique. 3.1.3 Some important configuration parameters Below are some important configuration parameters which affect the operation of the device. measure_period | Default = 600sThis is the time period for the wireless transmitter to wake up and take the measurement from the sensor. The default value is 600s. Users can reduce this value, but smaller value, shorter battery life! cyclic_data_period | Default = 600sInterval time to send an uplink message regardless of any conditions constant_A | Default = calibrated value by factoryThis value will affect the measurement accuracy. DO NOT change this value! constant_B | Default = calibrated value by factoryThis value will affect the measurement accuracy. DO NOT change this value! sensor+amplifier_sensitivity | Default = calibrated value by factoryThis value will affect the measurement accuracy. DO NOT change this value! Those configuration parameters can be changed by downlink or offline tools. For more other configuration parameters, please refer to the next section. 3.2 Sensor Configuration 3.2.1 How to configure the LoRaWAN sensor? Sensor configuration can be configured in 02 methods: Method 1: Configuring via Downlink message. Please find the instructions in this link, but please take note of the FW version of the Document. Method 2: Configuring via offline cable. Note: THE SENSOR IS ONLY ACTIVE FOR OFFLINE CONFIGURATION IN THE FIRST 60 SINCE POWER UP BY BATTERY OR PLUGGING THE CONFIGURATION CABLE. 3.2.2 What parameters of the device are configured? Some parameters are read-only, and some are read and writeable. To read the parameters, use the off-line cable as above instruction. To write the parameters, use the off-line cable or downlink as above instructions. Below tables are the lists of the parameters of the device. Read-only Parameter Table Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 0 0 3 5 device info string Read Wireless Sensor LoRaWAN G4 Gas Sensor 5 5 3 4 firmware version 1.00ddmm string Read ddmm = day / month 9 9 3 2 hardware version 1.10 string Read 11 B 3 4 lorawan protocol version 01.01.00 string Read LoRaWAN v1.0.3 15 F 3 6 application version 01.03.00.00 string Read application server v1.3.0.0 21 15 3 6 mac layer version 04.04.02.00 string Read mac layer v4.4.2.0 27 1B 3 4 deviceEUI hex Read End Device's EUI number, used to register the product on the Network Server by OTAA 31 1F 3 4 Lora appEUI hex Read Application server's EUI number is used to register the product on the Network Server by OTAA 35 23 3 8 Lora appKey hex Read The number of keys used to create two security keys of the End Device, used to register the product on the Network Server by OTAA 43 2B 3 8 Lora nwkSkey hex Read key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 51 33 3 8 Lora appSkey hex Read End Device data encryption key number, used to register the product on the Network Server by ABP 59 3B 3 2 device address 0 uint32 Read End Device address created by the Application server, used to register the product on the Network server by ABP 61 3D 3 2 network ID 0 uint32 Read Network server ID number, used to register the product on the Network server by ABP 63 3F 3 2 join mode OTAA string Read OTAA: Over-the-Air activation, ABP: Activation by Personalization 65 41 3 4 network mode PUBLIC string Read PUBLIC, PRIVATE 69 45 3 3 region code AS923 string Read 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 72 48 3 4 data rate DR2:980 string Read DR0:250, DR1:440, DR2:980, DR3:1760, DR4:3125, DR5:5470 76 4C 3 3 bandwidth BW125 string Read BW125, BW250, BW500 79 4F 3 2 spread factor SF10 string Read SF12, SF11, SF10, SF9, SF8, SF7 81 51 3 4 activation of ADR ADR OFF string Read ADR ON, ADR OFF 85 55 3 1 class A string Read 103 67 3 1 sensor type 1-255 uint16 Read 1-254: sensor type, 255: no sensor 104 68 3 1 battery level 0-3 uint16 Read 4 levels of battery capacity status Read/Write Parameter Table Note: Please check the column Property to identify which parameter requests a password for writing a new value. In this case, the user needs to input the password (190577) into the parameter name "password for setting" at address 268. Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 256 100 3 / 16 1 Modbus address 1-247 1 uint16 R/W Modbus address of the device 257 101 3 / 16 1 Modbus baudrate 0-1 0 uint16 R/W 0: 9600, 1: 19200 258 102 3 / 16 1 Modbus parity 0-2 0 uint16 R/W 0: none, 1: odd, 2: even 259 103 3 / 16 9 serial number string R/W (Password) 268 10C 3 / 16 2 password for setting uint32 R/W (Password) password 190577 270 10E 3 / 16 4 Lora appEUI hex R/W (Password) Application server's EUI number, used to register the product on the Network Server by OTAA 274 112 3 / 16 8 Lora appKey hex R/W (Password) The number of keys used to create two security keys of the End Device, used to register the product on the Network server by OTAA 282 11A 3 / 16 8 Lora nwkSkey hex R/W (Password) key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 290 122 3 / 16 8 Lora appSkey hex R/W (Password) End Device data encryption key number, used to register the product on the Network Server by ABP 298 12A 3 / 16 2 device address uint32 R/W (Password) End Device address created by the Application server, used to register the product on the Network server by ABP 300 12C 3 / 16 2 network ID uint32 R/W (Password) Network server ID number, used to register the product on the Network server by ABP 302 12E 3 / 16 1 activation mode (join mode) 0-1 1 uint16 R/W (Password) 1: OTAA (Over-the-Air Activation), 0: ABP (Activation by Personalization) 303 12F 3/16 1 downlink flag 0-1 1 unint16 R/W 1: Enable0: Disable 304 130 3 / 16 1 application port 1-255 1 uint16 R/W (Password) Port 224 is reserved for certification 305 131 3/16 1 network mode 0-1 1 uint16 R/W 1: Public, 0: Private 317 13D 3 / 16 1 region 1-7 1 uint16 Read/Write(Password) 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 318 13E 3 / 16 1 data rate 7 uint16 R/W (Password) 0: 250 bps, 1: 440 bps, 2: 980 bps, 3: 1760 bps, 4: 3125 bps, 5: 5470 bps 319 13F 3 / 16 1 tx power 2-20 16 uint16 R/W (Password) tx power: 2,4,6,8,10,12,14,16,18,20 320 140 3 / 16 1 adaptative data rate 0-1 0 uint16 R/W (Password) Automatically adjust data rate, 0: disable, 1: enable 330 14A 3/16 4 current_configuration hex R/W current configuration code of the device 334 14E 3 / 16 2 constant_A 1 float R/W constant_A for scaling measured value 336 150 3/16 2 constant_B 0 float R/W constant_B for scaling measured value 338 152 3/16 2 high_cut 1E+09 float R/W High cut value for the scaled value 340 154 3 / 16 2 low-cut 0 float R/W Low cut value for the scaled value 344 158 3/16 2 sensor+amplifier_sensitivity 11 float R/W Sensitivity value of sensor and amplifier circuit. 3.3 Calibration or commissioning for G4 sensor Please refer to this link. 4. Product specification Please refer to the detailed specifications in this link. 5. Warranty and Support For warranty terms and support procedures, please refer to this link. 6. References Use-cases: Case studies: White-papers: END. Manual for LoRaWAN AG Tilt Angle Sensor - WSLRW-AG | FW 2 THIS IS OBSOLETE MANUAL Please access https://www.iot.daviteq.com/wireless-sensors for updated manual Thank you very much for choosing Daviteq Wireless Sensors. We are the leading wireless sensor manufacturer in the World. We have a wide range of wireless sensors which support different connectivity like LoRaWAN, Sigfox, Sub-GHz, NB-IoT...Please find out more information at this link. This manual is applied to the following products Item code HW Version Firmware Version Remarks WSLRW-AG-... 1 2 Information Changes in this version v.s previous version Item Changes Changed by Changed Date Approved by Approved Date 2 Improve accuracy and resolution on FW 2 P.N.Diep 07-09-2022 N.V.Loc 07-09-2022 1 Initial version FW 1 P.N.Diep 01-06-2022 N.V.Loc 02-06-2022 To use this product, please refer step by step to the below instructions. Operating Principle Uplink Payload Battery Connect to the LoRaWAN Gateway Installation Troubleshooting Configuration Calibration Specification Warranty and Support 1.  Quick Guide Reading time: 10 minutesFinish this part so you can understand and put the sensor in operation with the default configuration from the factory. 1.1 What is the LoRaWAN AG Tilt Sensor and its principle of operation? WSLRW-AG is a LoRaWAN Tilt Sensor that can measure 3 tilt angles X, Y, and Z of any object such as a Tower, Building, Tree, Electricity Tower, Telecom Tower, Bridges... The Tilt sensor utilizes the combination of an advanced Accelerometer and Gyro meter to deliver high accuracy and stable measurement of the Tilt angle of 03 axis X, Y, and Z. With Ultra-low Power design and smart firmware allows the sensor can last up to 10 years with 02 x AA-type battery (depends on configuration). The sensor will transmit data in kilo-meters distance to the LoRaWAN gateway, any brand on the market. Please refer to this link for the AG Tilt Sensor's principle operation. 1.1.1 What are the typical applications of this sensor? Please refer to this link for typical applications. 1.1.2 When does the 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, 10 minutes, it will send the message called CYCLIC_DATA. The payload will tell the user the following data like measured values, battery level, alarm status... To change the cycle of data sending, you can change the value of the parameter: CYCLIC_DATA_PERIOD (default is 600 seconds). Case 3: During 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, alarm status... It can be forced by applying the magnet key on the reed switch in 1s; Case 4: 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. 1.1.3 The important configuration parameters The sensor was pre-configured at the factory with default values for configuration parameters that meet most use cases. However, depending on the specific use case, the customer can adjust those parameters. Please refer to section 3.2 for more details. 1.1.4 What kind of battery is used for this sensor? The sensor is powered by 2 x AA 1.5V batteries for many years of operation. We recommend using Energizer L91 battery which is very popular and high performance. This battery has a capacity of up to 3500mAh with a working temperature range from -40 to +60 oC. The instruction for installing the batteries is in this link. For Battery life estimation, please refer to this link. 1.2 What's in the package? The package includes:01 x Main device01 x Magnet key01 x Wall mounting bracket and screws 1.3 Quick Test for LoRaWAN Sensor 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 version 1.0.3 Class A Note: If the above settings do not match your network server/application, please refer to section 3.2 Sensor configuration to change the 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 this link 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 Refer to this link for details. 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 force the device to send data instantly. Step 4: Decode the payload of receiving package Please refer to section 1.4 Uplink Payload and Data Decoding for details of decoding the receiving packet. 1.4 Uplink Payload and Data Decoding For the Uplink Payload structure, please refer to this link. Note: Please select the right Payload document to suit the FW version of the sensor 1.5 Sensor Installation 1.5.1 Dimension drawings 1.5.2 Battery Installation Please follow the instructions in this link. 1.5.3 Sensor calibration and configuration The LoRaWAN AG Tilt sensor is pre-calibrated at the factory. There is no need to re-calibrate it at the field. 1.5.4 Sensor mounting on wall or pole Please follow this link. 2. Maintenance 2.1 Troubleshooting Problems with LoRaWAN communication like not receiving the packets...please refer to this link to troubleshoot the device. Problems with the sensor functions like not measuring or inaccurate measuring....please refer to this link to troubleshoot the sensor part. 2.2 Sensor maintenance 2.2.1 Maintenance of Wireless transmitter Maintenance works Yes/No Descriptions Consumable parts replacement Yes The battery is the only part need to check the lifetime to replace. Check the battery status on the back-end system. Cleaning device No Re-calibration / Re-validation No No calibration is required for the wireless transmitter. 2.2.2 Maintenance of the AG Tilt sensor Please refer to this link. 3. Advanced Guide 3.1 Operating principle of LoRaWAN AG Tilt Sensor 3.1.1 Operating principle of the complete device The Daviteq LoRaWAN AG Tilt Sensor comprises 02 parts linked internally: - The Daviteq LoRaWAN wireless transmitter;- The Daviteq AG tilt sensor; The AG Tilt sensor module measures the Acceleration of the 3-axis. The LoRaWAN wireless transmitter is to read the measurement values from the AG sensor and performs the calculation to deliver the desired output values, then it sends data to the gateway in the following cases: - Case 1: when the time of the Data sending cycle is reached. - Case 2: when the device is forced to send data by a Magnet key. 3.1.2 Operating principle of AG Tilt sensor To understand how the AG Tilt sensor work, please refer to this link for a complete understanding of this measuring technique. 3.1.3 Some important configuration parameters Below are some important configuration parameters which affect the operation of the device. measure_period | Default = 600sThis is the time period for the wireless transmitter to wake up and take the measurement from the sensor. The default value is 600s. Users can reduce this value, but smaller value, shorter battery life! cyclic_data_period | Default = 600sInterval time to send an uplink message regardless of any conditions Those configuration parameters can be changed by downlink or offline tools. For more other configuration parameters, please refer to the next section. 3.2 Sensor Configuration 3.2.1 How to configure the LoRaWAN sensor? Sensor configuration can be configured in 02 methods: Method 1: Configuring via Downlink message. Please find the instructions in this link, but please take note of the FW version of the Document. Method 2: Configuring via offline cable. Note: THE SENSOR IS ONLY ACTIVE FOR OFFLINE CONFIGURATION IN THE FIRST 60 SINCE POWER UP BY BATTERY OR PLUGGING THE CONFIGURATION CABLE. 3.2.2 What parameters of the device are configured? Some parameters are read-only, and some are read and writeable. To read the parameters, use the off-line cable as above instruction. To write the parameters, use the off-line cable or downlink as above instructions. Below tables are the lists of the parameters of the device. Read-only Parameter Table Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 0 0 3 5 device info string Read Wireless Sensor LoRaWAN G4 Gas Sensor 5 5 3 4 firmware version 1.00ddmm string Read ddmm = day / month 9 9 3 2 hardware version 1.10 string Read 11 B 3 4 lorawan protocol version 01.01.00 string Read LoRaWAN v1.0.3 15 F 3 6 application version 01.03.00.00 string Read application server v1.3.0.0 21 15 3 6 mac layer version 04.04.02.00 string Read mac layer v4.4.2.0 27 1B 3 4 deviceEUI hex Read End Device's EUI number, used to register the product on the Network Server by OTAA 31 1F 3 4 Lora appEUI hex Read Application server's EUI number is used to register the product on the Network Server by OTAA 35 23 3 8 Lora appKey hex Read The number of keys used to create two security keys of the End Device, used to register the product on the Network Server by OTAA 43 2B 3 8 Lora nwkSkey hex Read key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 51 33 3 8 Lora appSkey hex Read End Device data encryption key number, used to register the product on the Network Server by ABP 59 3B 3 2 device address 0 uint32 Read End Device address created by the Application server, used to register the product on the Network server by ABP 61 3D 3 2 network ID 0 uint32 Read Network server ID number, used to register the product on the Network server by ABP 63 3F 3 2 join mode OTAA string Read OTAA: Over-the-Air activation, ABP: Activation by Personalization 65 41 3 4 network mode PUBLIC string Read PUBLIC, PRIVATE 69 45 3 3 region code AS923 string Read 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 72 48 3 4 data rate DR2:980 string Read DR0:250, DR1:440, DR2:980, DR3:1760, DR4:3125, DR5:5470 76 4C 3 3 bandwidth BW125 string Read BW125, BW250, BW500 79 4F 3 2 spread factor SF10 string Read SF12, SF11, SF10, SF9, SF8, SF7 81 51 3 4 activation of ADR ADR OFF string Read ADR ON, ADR OFF 85 55 3 1 class A string Read 103 67 3 1 sensor type 1-255 uint16 Read 1-254: sensor type, 255: no sensor Read/Write Parameter Table Note: Please check the column Property to identify which parameter requests a password for writing a new value. In this case, the user needs to input the password (190577) into the parameter name "password for setting" at address 268. Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 256 100 3 / 16 1 Modbus address 1-247 1 uint16 R/W Modbus address of the device 257 101 3 / 16 1 Modbus baudrate 0-1 0 uint16 R/W 0: 9600, 1: 19200 258 102 3 / 16 1 Modbus parity 0-2 0 uint16 R/W 0: none, 1: odd, 2: even 259 103 3 / 16 9 serial number string R/W (Password) 268 10C 3 / 16 2 password for setting uint32 R/W (Password) password 190577 270 10E 3 / 16 4 Lora appEUI hex R/W (Password) Application server's EUI number, used to register the product on the Network Server by OTAA 274 112 3 / 16 8 Lora appKey hex R/W (Password) The number of keys used to create two security keys of the End Device, used to register the product on the Network server by OTAA 282 11A 3 / 16 8 Lora nwkSkey hex R/W (Password) key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 290 122 3 / 16 8 Lora appSkey hex R/W (Password) End Device data encryption key number, used to register the product on the Network Server by ABP 298 12A 3 / 16 2 device address uint32 R/W (Password) End Device address created by the Application server, used to register the product on the Network server by ABP 300 12C 3 / 16 2 network ID uint32 R/W (Password) Network server ID number, used to register the product on the Network server by ABP 302 12E 3 / 16 1 activation mode (join mode) 0-1 1 uint16 R/W (Password) 1: OTAA (Over-the-Air Activation), 0: ABP (Activation by Personalization) 303 12F 3/16 1 downlink flag 0-1 1 unint16 R/W 1: Enable0: Disable 304 130 3 / 16 1 application port 1-255 1 uint16 R/W (Password) Port 224 is reserved for certification 305 131 3/16 1 network mode 0-1 1 uint16 R/W 1: Public, 0: Private 317 13D 3 / 16 1 region 1-7 1 uint16 Read/Write(Password) 1: AS923-1, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: AS923-2, 9: AS923-3, 10: AS923-1 Japan 318 13E 3 / 16 1 data rate 7 uint16 R/W (Password) 0: 250 bps, 1: 440 bps, 2: 980 bps, 3: 1760 bps, 4: 3125 bps, 5: 5470 bps 319 13F 3 / 16 1 tx power 2-20 16 uint16 R/W (Password) tx power: 2,4,6,8,10,12,14,16,18,20 320 140 3 / 16 1 adaptative data rate 0-1 0 uint16 R/W (Password) Automatically adjust data rate, 0: disable, 1: enable 330 14A 3/16 4 current_configuration hex R/W current configuration code of the device 3.3 Calibration or commissioning for AG Tilt sensor Please refer to this link. 4. Product specification Please refer to the detailed specifications in this link. 5. Warranty and Support For warranty terms and support procedures, please refer to this link. 6. References Use-cases: Case studies: White-papers: END. USER GUIDE FOR LORAWAN PROCESS PRESSURE SENSOR WSLRW-PPS THIS IS OBSOLETE MANUAL Please access https://www.iot.daviteq.com/wireless-sensors for updated manual WSLRW-PPS-MN-EN-01 JUL-2020 This document is applied for the following products SKU WSLRW-PPS HW Ver. 1.2 FW Ver. 1.0 Item Code WSLRW-PPS-9-10 Wireless LoRaWAN Gage Process Pressure Sensor, Internal antenna, range 0-10 barg, accuracy 0.5%, process connection G1/4-male, 316SS, Type AA battery 1.5VDC, IP68, 900-930 Mhz WSLRW-PPS-8-10 Wireless LoRaWAN Gage Process Pressure Sensor, Internal antenna, range 0-10 barg, accuracy 0.5%, process connection G1/4-male, 316SS, Type AA battery 1.5VDC, IP68, 860-870 Mhz WSLRW-PPS-9-25 Wireless LoRaWAN Gage Process Pressure Sensor, Internal antenna, range 0-25 barg, accuracy 0.5%, process connection G1/4-male, 316SS, Type AA battery 1.5VDC, IP68, 900-930 Mhz WSLRW-PPS-8-25 Wireless LoRaWAN Gage Process Pressure Sensor, Internal antenna, range 0-25 barg, accuracy 0.5%, process connection G1/4-male, 316SS, Type AA battery 1.5VDC, IP68, 860-870 Mhz 0. Configuration Check List STEP 1: Configure End Device (Using Modbus Configuration Cable) Setting value (Example) 1. Select region AS923, IN865, EU868,.. (refer to register address 317) 2. End Device Operation OTAA or ABP OTAA Write AppEUI information from Application Server to Lorawan End Device; Write AppKey (created by user) information for Lorawan End Device and Application Server. ABP Write DevEUI information from Application Server to Lorawan end device; write Network Session Key and App Session Key (created by user) information to Lorawan end device (and Application Server). 3. Configure "cycle send data" 900 sec (Defaut) 4. Configure "sensor sampling_rate" 120 sec (Defaut) 5. Configure parameters of sensor (Refer to Register table configuration table) STEP 2:  Configure the operation of LoRaWAN Gateway (Ex: URSALINK Gateway) 1. Configure the information in the General tab Server address, Server port (For more information) 2. Configure the information in the Radio tab Select the Region Region (Other parameters to default) STEP 3:  Configure the operation of LoRaWAN Gateway on Network Server (Ex: URSALINK Gateway with Thethingsnetwork) 1. Gateway ID registration Gateway ID is the GatewayEUI information on the Gateway 2. Frequency Plan parameters configuration Asia 920-923MHz, Europe 868MHz,... 3. Router parameters configuration 4. Check the connection of the gateway to the network server The Gateway status LED lights up and displays the message "Status: conneted" on the Thethingsnetwork STEP 4:  Configure the operation of Application Server on Network Server 1. App ID registration 2. Handler parameters configuration STEP 5: Register Lorawan End Device on Application Server on Thethingsnetwork 1. ID Registration 2.Select operation mode OTAA or ABP OTAA Configure parameters DevEUI and AppKEY ABP Configure parameters Device Address, Network Session Key, App Session Key 1. Functions Change Log HW Ver. FW Ver. Release Date Functions Change 1.1 1.0.0 21-July-2020 1.1 1.1.x 05-Oct-2020 Data frame improvements Fix the Watchdog bug 1.1 1.2.0 12-Oct-2020 Improved output WSLRW-PPS The minimum frequency of sending data packets to Gateway is 15 seconds When connecting to network server with OTAA failure, it will not read sensor value 2. Introduction WSLRW-PPS is the LoRaWAN Integrated Process Pressure Sensor, it have different kind of measurement, such as Gage/Absolute/Sealed Gage, range -1 .. + 35 bar, high accuracy and stability. With Ultra-low power design and smart firmware allow the sensor can last up to 10 years with 2 x AA battery (depends on configuration). The sensor will transmit data in kilo-meters distance to LoRaWAN gateway, any brand on the market. 3. Specification SENSORS SPECIFICATION: Sensing Technology Advanced PIEZO/Capacitance technology Measuring range Select from -1 .. + 35 bar Gage/Absolute/Sealed Gage Over pressure protection 1.5 x Span Accuracy 0.5% of span Stability < 0.3% span/year Wetted parts 316SS Measuring Fluids Any fluid which is workable with materials 316SS Working temperature -10 .. + 80 oC Process connection Standard G1/4 or Others (consult factory) LoRaWAN SPECIFICATION: Data rate 250bps .. 5kbps Antenna Internal Antenna 2.67 dbi Battery 02 x AA 1.5 VDC, working time up to 10 years, battery not included RF Frequency and Power 860..930Mhz, +14 .. +20 dBm, configurable Protocol LoRaWAN, class A Data sending modes Interval time and when alarm occurred RF Module complies to ETSI EN 300 220, EN 303 204 (Europe) FCC CFR47 Part15 (US), ARIB STD-T108 (Japan) Vietnam Type Approval Working temperature -40oC..+60oC (with AA L91 Energizer) Dimensions H180xW50xD40 Net-weight 250 grams Housing Polycarbonate & POM plastic, IP68 4. Operation Principle 4.1 LoRaWAN protocol specifications 4.1.1 LoRaWAN Sensor protocol specifications LoRaWAN Protocol Version 1.0.3 Application Server Version 1.3.0.0 MAC Layer Version 4.4.2.0 Radio Standards: LoRa Alliance Certified LoRaWAN Zone: LoRa Alliance AS923, KR920, AU915, US915, EU868, IN865, RU864 Class A Join Active: OTAA / ABP Network Mode: Public Network / Private Network Tx Power: upto 20 dBm Frequency 860 - 930Mhz Date rate 250 bps - 5kbps Spreading factor SF12 - SF7 Bandwidth 125 kHz Unconfirmed-data message LoRaWAN application port for certification: 224 4.1.2 Data rate of LoRaWAN Sensor Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR2 980 SF10 125 AS923, AU915 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 980 SF10 125 US915 DR1 1760 SF9 125 DR2 3125 SF8 125 DR3 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 250 SF12 125 KR920, EU868, IN865, RU864 DR1 440 SF11 125 DR2 980 SF10 125 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 4.1.3 Tx power of LoRaWAN sensor Max EIRP (dBm) Max Tx Power (dBm) Region 16 16 AS923 14 14 KR920 30 20 AU915 30 20 US915 16 16 EU868 30 20 IN865 16 16 RU864 4.2 The principle of operation of the LoRaWAN sensor When starting the power supply, the LoRaWAN sensor has 60 seconds to allow configuration to operate via the Configuration Cable with the Modbus RTU protocol. After 60 seconds, the first packet will be sent, then the LoRaWAN sensor will send the next packets in the following cases: Case 1: When it reaches the frequency of taking data, the LoRaWAN sensor will wake up to measure and calculate. Then: If the measured value exceeds the High or Low setting thresholds, the packet will be sent to the Gateway and then asleep; If NOT then sleep without sending data. NOTE: Once sending the data to Gateway by this alarm event, the timer of sending time interval will be reset; Case 2: When the sending time interval is reached, the LoRaWAN sensor wakes up to measure and calculate and send data to Gateway immediately, regardless of value. Case 3: By using the magnet key, the LoRaWAN sensor can be triggered to send data to Gateway immediately. NOTE: The time between sending data for Class A is at least 3 seconds 4.3 Principle of operation LoRaWAN Network The LoRaWAN Gateway function is Packet Forwarder so: Between Gateway and End Device: Gateway receives data packets from End Device via RF connection, so it is recommended to configure Radio parameters (Note: the packet that Gateway receives is encrypted) Between Gateway and Network Server: Gateway forwards data packets to the Network server via an IP connection, so it is recommended to configure Network parameters such as Server Address, Server Uplink Port, Server Downlink Port, .. LoRaWAN Network is secured as follows: Network section key (NwkSKey) to ensure the security of communications on the Network Application session key (AppSKey) to ensure data security between End Device and Application Server Special keys of the device such as DevEUI, AppEUI, Gateway EUI, Device Address. Therefore, the data packet that the Gateway receives is encrypted and decrypted on the Application server. To End Device connect to the Network server, you need to register in the following two ways: Activation with OTAA (Over-the-Air activation): is the process of joining the Network automatically. Previously, both End Device and Application Server installed the same DevEUI code, AppEUI and AppKey. During activation, AppKey will generate 2 security keys for End Device and Network, which are: Network session key (NwkSKey): is the key to secure communication commands on MAC layer between End Device and Network server. Application session key (AppSKey): is the key to secure data packets between End Device and Application server. ATTENTIONS:* OTAA mode must be successfully activated in order for the End Device to send data packets to the Network through the Gateway;* OTAA mode only need to activate once, if the device is reset or battery replacement, it will activate OTAA again;* When the End Device is connected to the Network server, whether the Gateway is reset or the power is restarted, it will not need to activate OTAA. Activation by ABP (Activation by Personalization): is the process of joining Network manually. Device Address, Network session key (NwkSKey) and Application session key (AppSKey) codes must be stored inside the End Device and Application server, so when the End Device sends data packets to the Network server, it will also send the security codes to activated. 4.4 Configure the LoRaWAN Network 4.4.1 Configure End Device operation according to OTAA Configuration parameters for the End Device to be activated by OTAA as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode OTAA Device activation type on Network Server DevEUI 34 35 31 31 4B 37 75 12 Device ID's unique ID number => Set this ID number for the Application server AppEUI 70 B3 D5 7E D0 02 D5 0B Application server's unique ID number (random or user generated)=> Set this ID number for End Device AppKey 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C Key Number for generating 2 NwkSKey and AppSKey security keys created by the user (factory-created by default)=> Used to install for both the Device and Application Server End ATTENTIONS:* The AppEUI number from Application Server => then installed for the End Device. AppEUI is randomly generated by the Application server or by the user;* The number of AppKeys during OTAA activation will generate two security keys, Lora NwkSKey and AppSKey, which are used for both End Device and Network. 4.4.2 Configure End Device operation according to ABP Configuration parameters for the End Device to be activated by ABP as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode ABP Device activation type on Network Server Device Address 12 34 56 78 End Device Address created by Application server=> Set Device Address for End Device NwkSKey (Network session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C NwkSKey number created by the user to install and use for both End Device and Application Server AppSKey (Application session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C AppSKey number generated by the user to install for both End Device and Application Server 4.4.3 Configure Gateway operations 4.4.3.1 Configure the Gateway to receive data packets from the End Device. Radio settings need to be set as:* Region code: AS923, KR920, AU915, US915, EU868, IN865, RU864* Center Frequency, Channels, Bandwidth (recommends using the default configuration created by the system) Let's take an example to configure the Gateway operation of URSALINK (Model: UG85-L00E-915) 4.4.3.2 Configure the Gateway to communicate with the Public Network Server Let's take an example of configuring Gateway UG85 to connect with "thethingsnetwork.org" in Asia: Currently thethingsnetwork only supports the connection protocol with Gateway is Semtech UDP Packet Forwarder. https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Parameter settings Setting value (example) Description Gateway EUI 24e124fffef038fd Gateway's unique ID number=> Set this ID number for Application server Server Address router.as1.thethings.network Semtech server address: https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Router regional asia: router.as1.thethings.network Router regional india: ttn.thingsconnected.net Ursalink server address: localhost Server Uplink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Server Downlink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Network mode Public LoRaWAN 4.4.4 Register the Application server on the Public Network "thethingsnetwork.org" 4.4.4.1 Register the Gateway on Public Network "thethingsnetwork.org" as shown below: The current network only supports the Gateway connection protocol, "Semtech UDP protocol" is Semtech UDP Packet Forwarder. Then power the Gateway and observe the message "Status: connected" => Registration of the Gateway on the Application successfully. 4.4.4.2 Register Application on Public Network "thethingsnetwork.org" as shown below: 4.4.4.3 Register End Device on Application: 4.5 LED meaning RED LED: Fixed ON: due to noise caused peripheral components (i2c, spi, uart, timer, rtc, wdt, ...) do not initialize. Flashing 10ms ON / 10s OFF: Activation by OTAA on the Network server failed. Flashing 10ms ON / 2s OFF: Sending data packet to Gateway failed. GREEN LED: Flashing 100ms ON / OFF when sending data packet to Gateway. BLUE LED: Flashing 1s ON / 1s OFF for the first 60 seconds when booting (insert batteries or connected external sources), after 60 seconds OFF. ON during the LoRaWAN sensor receives data packets from the Network server and OFF when received. 4.6 Process of measurement When the LoRa sensor wakes up, it will supply power to the external sensor module so that the module can start measuring. After measuring it will turn off the power to the module. The measured value is the raw value of the sensor module, which can be ambient temperature, ambient humidity, etc. The measurement value can be scaled according to the following formula: Y = aX + b X: the raw value from module sensor Y: the calculated value will be sent to Sigfox base station in the payload data. a: constant (default value is 1) b: constant (default value is 0) 4.7 Payload Data The folllowing is the format of payload data will be sent to Sigfox server. Length is 6 bytes, it is future-proof for expansion to 12 bytes. Sensor type (1 byte) Status (1 byte) 1st - Parameter (4 bytes) 2nd - Parameter (4 bytes) Meaning of Data in the Payload Data Size (byte) Bit Format Meaning Sensor type 1 all Uint8 Sensor type = 0x04 means LoRaWAN Node with I2C Process Pressure. Sensor type = 0xFF means no sensor Status: battery level 1 Bit 7 and 6 Uint8 Battery capacity in 04 levels 11: battery level 4 (99%) 10: battery level 3 (60%) 01: battery level 2 (30%) 00: battery level 1 (10%) Status: error Bit 5 and 4 Node status 01: error 00: no error Status: alarm 1 Bit 3 and 2 Alarm status of 1st - Parameter (Y1 value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm Status: alarm 2 Bit 1 and 0 Alarm status of 2nd - Parameter (Y2 value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm 1st - Parameter 4 all Float Y1 value: process pressure value (%) 2nd - Parameter 4 all Float Y2 value: temperature value (oC) 5. Configuration Using the configuration cable to connect to the sensor as below picture. Serial port configuration on the computer:* COMPort, Baudrate: 9600, Parity: None, Stop bit: 1, Data bit: 8* Modbus RTU: Reading data by Function 3 / Writing data by Function 16. 5.1 Step to configure NOTE: The Modbus configuration can only be performed in the first 60s after power up the LoRaWAN sensor. After 60s, if user can not finish the configuration process, user need to reset the power of LoRaWAN sensor again, by removing battery in at least 15s. Step 1: Install the Modbus Configurator Software in the link below https://filerun.daviteq.com/wl/?id=qK0PGNbY1g1fuxTqbFW9SXtEvCw7bpc6 How to use the Modbus configuration software Step 2: Plug the configuration cable to computer via usb port and install the driver; Step 3: Open the plastic housing with L hex key to unscrew M4 screws at the side of housing Step 4: Plug the connector to the configuration port; Step 5:  Import the configuration file by importing the csv file: Go to MENU: FILE / Import New / => select the file with name CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0.csv (in the link below). Then click Connect; CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0 To write new value to the device:First, you need to write the password in "password for setting", after reading the value to check ok, you can write the new value AppEUI, AppKey, ...You only have 60 seconds after plugging the configuration cable or the power supply into the device for configuration. 5.2 Register table Here is the table of Data will be read by Modbus tool Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 0 0 3 5 device info WSLRW-I2C string Read Wireless Sensor LoRaWAN - I2C 5 5 3 4 firmware version 1.00ddmm string Read ddmm = day / month 9 9 3 2 hardware version 1.10 string Read 11 B 3 4 lorawan protocol version 01.00.03 string Read lorawan v1.0.3 15 F 3 6 application version 01.03.00.00 string Read application server v1.3.0.0 21 15 3 6 mac layer version 04.04.02.00 string Read mac layer v4.4.2.0 27 1B 3 4 deviceEUI hex Read End Device's EUI number, used to register the product on the Network Server by OTAA 31 1F 3 4 lora appEUI hex Read Application server's EUI number is used to register the product on the Network Server by OTAA 35 23 3 8 lora appKey hex Read The number of keys used to create two security keys of the End Device, used to register the product on the Network Server by OTAA 43 2B 3 8 lora nwkSkey hex Read key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 51 33 3 8 lora appSkey hex Read End Device data encryption key number, used to register the product on the Network Server by ABP 59 3B 3 2 device address 0 uint32 Read End Device address created by Application server, used to register the product on the Network server by ABP 61 3D 3 2 network ID 0 uint32 Read Network server ID number, used to register the product on the Network server by ABP 63 3F 3 2 join mode OTAA string Read OTAA: Over-the-Air activation, ABP: Activation by Personalization 65 41 3 4 network mode PUBLIC string Read PUBLIC, PRIVATE 69 45 3 3 region code AS923 string Read 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 72 48 3 4 data rate DR2:980 string Read DR0:250, DR1:440, DR2:980, DR3:1760, DR4:3125, DR5:5470 76 4C 3 3 bandwidth BW125 string Read BW125, BW250, BW500 79 4F 3 2 spread factor SF10 string Read SF12, SF11, SF10, SF9, SF8, SF7 81 51 3 4 activation of ADR ADR OFF string Read ADR ON, ADR OFF 85 55 3 1 class A string Read 103 67 3 1 sensor type 1-255 uint16 Read 1-254: sensor type, 255: no sensor 104 68 3 1 battery level 0-3 uint16 Read 4 levels of battery capacity status 105 69 3 1 error status 0-1 uint16 Read Error code of sensor, 0: no error, 1: error 106 6A 3 1 prm1 alarm status 0-2 uint16 Read Alarm status of parameters 1, 0: none, 1: Low, 2: High 107 6B 3 1 prm2 alarm status 0-2 uint16 Read Alarm status of parameter 2 108 6C 3 2 prm1 value float Read Parameter value 1 110 6E 3 2 prm2 value float Read Parameter value 2 112 70 3 1 battery % 10%, 30%, 60%, 99% uint16 Read % Value of battery capacity 113 71 3 2 battery voltage 0-3.67 vdc float Read Value of battery voltage 115 73 3 2 mcu temperature oC float Read Temperature value of RF module 117 75 3 1 mcu vref 0-3.67 vdc uint16 Read Vref value of RF module 118 76 3 1 button1 status 0-1 uint16 Read Button state, 0: No button pressed, 1: Button pressed 119 77 3 1 button2 status 0-1 uint16 Read Button status, 0: No magnetic sensor detected, 1: Magnetic sensor detected Here is the table for Configuration: Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 256 100 3 / 16 1 modbus address 1-247 1 uint16 R/W Modbus address of the device 257 101 3 / 16 1 modbus baudrate 0-1 0 uint16 R/W 0: 9600, 1: 19200 258 102 3 / 16 1 modbus parity 0-2 0 uint16 R/W 0: none, 1: odd, 2: even 259 103 3 / 16 9 serial number string R/W (Password) 268 10C 3 / 16 2 password for setting uint32 R/W (Password) password 190577 270 10E 3 / 16 4 lora appEUI hex R/W (Password) Application server's EUI number, used to register the product on the Network Server by OTAA 274 112 3 / 16 8 lora appKey hex R/W (Password) The number of keys used to create two security keys of the End Device, used to register the product on the Network server by OTAA 282 11A 3 / 16 8 lora nwkSkey hex R/W (Password) key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 290 122 3 / 16 8 lora appSkey hex R/W (Password) End Device data encryption key number, used to register the product on the Network Server by ABP 298 12A 3 / 16 2 device address uint32 R/W (Password) End Device address created by Application server, used to register the product on the Network server by ABP 300 12C 3 / 16 2 network ID uint32 R/W (Password) Network server ID number, used to register the product on the Network server by ABP 302 12E 3 / 16 1 activation mode 0-1 1 uint16 R/W (Password) 1: OTAA (Over-the-Air Activation), 0: ABP (Activation by Personalization) 304 130 3 / 16 1 application port 1-255 1 uint16 R/W (Password) Port 224 is reserved for certification 317 13D 3 / 16 1 region 1-7 1 uint16 Read/Write(Password) 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 318 13E 3 / 16 1 data rate 7 uint16 R/W (Password) 0: 250 bps, 1: 440 bps, 2: 980 bps, 3: 1760 bps, 4: 3125 bps, 5: 5470 bps 319 13F 3 / 16 1 tx power 2-20 16 uint16 R/W (Password) tx power: 2,4,6,8,10,12,14,16,18,20 320 140 3 / 16 1 adaptative data rate 0-1 0 uint16 R/W (Password) Automatically adjust data rate, 0: disable, 1: enable 334 14E 3 / 16 2 cycle send data 900 uint32 R/W sec (data sending cycle) 338 152 3 / 16 1 alarm limt 44 uint16 R/W limit the number of events / day 340 154 3 / 16 2 sensor1: sampling_rate 120 uint32 R/W sec (frequency of data taken from sensor 1) 348 15C 3 / 16 2 prm1: a 1 float R/W Scale parameter "a" of sensor 1 350 15E 3 / 16 2 prm1: b 0 float R/W Scale parameter "b" of sensor 1 354 162 3 / 16 2 prm1: High Threshold 100000 float R/W High threshold value of sensor 1 356 164 3 / 16 2 prm1: High Hysteresis 10000 float R/W High hysteresis value of sensor 1 358 166 3 / 16 2 prm1: Low Threshold 0 float R/W Low threshold value of sensor 1 360 168 3 / 16 2 prm1: Low Hysteresis 10000 float R/W Low hysteresis value of sensor 1 362 16A 3 / 16 2 prm1: High Cut 100000 float R/W Upper limit value of sensor 1 364 16C 3 / 16 2 prm1: Low Cut 0 float R/W Lower limit value of sensor 1 366 16E 3 / 16 2 prm2: a 1 float R/W Scale parameter "a" of sensor 2 368 170 3 / 16 2 prm2: b 0 float R/W Scale parameter "b" of sensor 2 372 174 3 / 16 2 prm2: High Threshold 100000 float R/W High threshold value of sensor 2 374 176 3 / 16 2 prm2: High Hysteresis 10000 float R/W High hysteresis value of sensor 2 376 178 3 / 16 2 prm2: Low Threshold 0 float R/W Low threshold value of sensor 2 378 17A 3 / 16 2 prm2: Low Hysteresis 10000 float R/W Low hysteresis value of sensor 2 380 17C 3 / 16 2 prm2: High Cut 100000 float R/W Upper limit value of sensor 2 382 17E 3 / 16 2 prm2: Low Cut 0 float R/W Lower limit value of sensor 2 6. Installation 6.1 Example application 6.2 Installation location To maximize the distance of transmission, the ideal condition is Line-of-sight (LOS) between the LoRaWAN sensor and Gateway. In real life, there may be no LOS condition. However, the LoRaWAN sensor still communicates with Gateway, but the distance will be reduced significantly. ATTENTION:DO NOT install the LoRaWAN 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, cement…is acceptable. 6.3 Battery installation Steps for battery installation: Step 1: Using L hex key to unscrew M4 screws at the side of housing and carefully pull out the top plastic housing in the vertical direction Step 2: Insert 02 x AA 1.5VDC battery, please take note the poles of battery ATTENTION: REVERSED POLARITY OF BATTERIES IN 10 SECONDS CAN DAMAGE THE SENSOR CIRCUIT!!! Step 3: Insert the top plastic housing and locking by L hex key ATTENTION: When reinstalling the cover, pay attention to put the PCB edge into the middle slot of the box inside as shown below) 7. Troubleshooting No. Phenomena Reason Solutions 1 The BLUE LED does not blink when the battery is installed Insert the battery in the opposite direction Insert the battery in the correct way 2 The RED LED is always on Due to noise, the peripheral components (i2c, spi, uart, ..) of RF module cannot be initialized After 30s the node will automatically reset. If the noise causes the Watchdog not to initialize, remove the battery and wait for more than 10 seconds, then insert the battery again 3 The RED LED blinks continuously (10ms ON / 2s OFF) and the Node does not send RF. After more than 10 sending cycles, the Node will automatically reset Operating frequency in that country is prohibited Operating frequency in that country is limited to Data rate, Tx Power Reconfigure the allowed frequency of operation Reconfigure Data rate = DR5 / SF07, Tx Power 4 RED LED blinks continuously (10ms ON / 2s OFF) and Node sends RF continuously 3s / time but no data. After more than 10 sending cycles, the Node will automatically reset Node runs dummy sending mode => sent by Gateway to send Downlink packets when users clear Uplink and Downlink counter values on Network Server (build in Gateway) when activated by ABP Configuration enabled by OTAA 5 The RED LED flashes 10ms ON / 10s OFF and the Node does not send RF Node activation by OTAA on Network server has not been successful Using Margnet-Key to force Node to send RF continuously for 3 seconds / time => when activating by OTAA successfully, the GREEN LED will blink after sending RF 6 The node sent RF successfully but the GREEN LED did not blink LED is broken Warranty to replace LED 7 The data packet taken from the Gateway has an incorrect value The data package is encrypted Get the decoded packet on the Application Server 8 Node sends RF and activates by ABP, on Gateway receives data but Application server has no data The application server still stores the counter values of the previous Uplink and Downlink Delete the counter values of Uplink and Downlink on the Application server 9 The node does not send RF and the RF module is hot Insert the battery in the opposite direction Short circuit Warranty or replacement 10 Node does not send RF to Gateway according to the alarm, LED does not blink The alarm configuration is incorrect Running out of the number of alarms set for the day Check alarm configuration Check the configuration for the maximum number of alarms per day 11 Node does not send RF to Gateway when activated by the magnetic switch, LED does not blink Magnetic switch has malfunctioned Read the status of the magnetic switch via modbus (when powering or attaching the battery) to see if the magnetic switch is working. 12 Node has blinked LED GREEN when sending RF but the Gateway or Application server cannot received LoRa module on the Gateway is faulty The IP connection (4G / WiFi / ...) on the Gateway is faulty Check Gateway's LoRa status lights on Gateway Check 4G / WiFi status lights on Gateway 13 The value of the sensor is 0 and sensor_type = 0xFF Lost connection with the sensor Check sensor connection Replace the module sensor 14 RSSI is weak and often loses data Distance between Node and Gateway is far or there are many obstructions Connection to Antenna problem Install metal nodes or in metal cabinets Configure Data rate = DR0 / SF12 Check Antenna position Install Node in a well ventilated location 8. Support contacts Manufacturer Daviteq Technologies IncNo.11 Street 2G, Nam Hung Vuong Res., An Lac Ward, Binh Tan Dist., Ho Chi Minh City, Vietnam.Tel: +84-28-6268.2523/4 (ext.122) Email: info@daviteq.com | www.daviteq.com Distributor in Australia and New Zealand Templogger Pty Ltd Tel: 1800 LOGGER Email: contact@templogger.net USER GUIDE FOR LORAWAN INTEGRATED HUMIDITY & TEMPERATURE SENSOR WSLRW-ATH THIS IS OBSOLETE MANUAL Please access https://www.iot.daviteq.com/wireless-sensors for updated manual WSLRW-ATH-MN-EN-01 JUL-2020 This document is applied for the following products SKU WSLRW-ATH HW Ver. 1.2 FW Ver. 1.0 Item Code WSLRW-ATH-9-10 Wireless LoRaWAN Integrated Humidity & Temperature Sensor, Internal antenna, Type AA battery 1.5VDC, IP67, 900-930 Mhz WSLRW-ATH-8-10 Wireless LoRaWAN Integrated Humidity & Temperature Sensor, Internal antenna, Type AA battery 1.5VDC, IP67, 860-870 Mhz 0. Configuration Check List STEP 1: Configure End Device (Using Modbus Configuration Cable) Setting value (Example) 1. Select region AS923, IN865, EU868,.. (refer to register address 317) 2. End Device Operation OTAA or ABP OTAA Write AppEUI information from Application Server to Lorawan End Device; Write AppKey (created by user) information for Lorawan End Device and Application Server. ABP Write DevEUI information from Application Server to Lorawan end device; write Network Session Key and App Session Key (created by user) information to Lorawan end device (and Application Server). 3. Configure "cycle send data" 900 sec (Defaut) 4. Configure "sensor sampling_rate" 120 sec (Defaut) 5. Configure parameters of sensor (Refer to Check data configuration table) STEP 2:  Configure the operation of LoRaWAN Gateway (Ex: URSALINK Gateway) 1. Configure the information in the General tab Server address, Server port (For more information) 2. Configure the information in the Radio tab Select the Region Region (Other parameters to default) STEP 3:  Configure the operation of LoRaWAN Gateway on Network Server (Ex: URSALINK Gateway with Thethingsnetwork) 1. Gateway ID registration Gateway ID is the GatewayEUI information on the Gateway 2. Frequency Plan parameters configuration Asia 920-923MHz, Europe 868MHz,... 3. Router parameters configuration 4. Check the connection of the gateway to the network server The Gateway status LED lights up and displays the message "Status: conneted" on the Thethingsnetwork STEP 4:  Configure the operation of Application Server on Network Server 1. App ID registration 2. Handler parameters configuration STEP 5: Register Lorawan End Device on Application Server on Thethingsnetwork 1. ID Registration 2.Select operation mode OTAA or ABP OTAA Configure parameters DevEUI and AppKEY ABP Configure parameters Device Address, Network Session Key, App Session Key 1. Functions Change Log HW Ver. FW Ver. Release Date Functions Change 1.1 1.0.0 21-July-2020 1.1 1.1.x 05-Oct-2020 Data frame improvements Fix the Watchdog bug 1.1 1.2.0 12-Oct-2020 The minimum frequency of sending data packets to Gateway is 15 seconds When connecting to network server with OTAA failure, it will not read sensor value 2. Introduction WSLRW-ATH is the LoRaWAN Integrated Ambient Humidity & Temperature Sensor, it utilises Digital capacitance humidity sensor to deliver high accuracy and stable measurement. With Ultra-low power design and smart firmware allow the sensor can last up to 10 years with 2 x AA battery (depends on configuration). The sensor will transmit data in kilo-meters distance to LoRaWAN gateway, any brand on the market. There are a lot of applications as environment monitoring for office, warehouse, data center, hospital, agriculture... 3. Specification SENSORS SPECIFICATION: Sensor Digital type, factory calibrated, output both Humidity & Temperature values Humidity measuring range & accuracy 0 .. 100 %RH, +/- 2.0% Humidity resolution 0.1% Temperature measuring range & accuracy -40 .. + 85 oC, +/- 0.2 oC Temperature resolution 0.1 oC Sensor Filter 20um Alloy sintered filter LoRaWAN SPECIFICATION: Data rate 250bps .. 5kbps Antenna Internal Antenna 2.67 dbi Battery 02 x AA 1.5 VDC, working time up to 10 years, battery not included RF Frequency and Power 860..930Mhz, +14 .. +20 dBm, configurable Protocol LoRaWAN, class A Data sending modes Interval time and when alarm occurred RF Module complies to ETSI EN 300 220, EN 303 204 (Europe) FCC CFR47 Part15 (US), ARIB STD-T108 (Japan) Vietnam Type Approval Working temperature -40oC..+60oC (with AA L91 Energizer) Dimensions H137xW73xD42 Net-weight 250 grams Housing Polycarbonate & POM plastic, IP67 4. Operation Principle 4.1 LoRaWAN protocol specifications 4.1.1 LoRaWAN Sensor protocol specifications LoRaWAN Protocol Version 1.0.3 Application Server Version 1.3.0.0 MAC Layer Version 4.4.2.0 Radio Standards: LoRa Alliance Certified LoRaWAN Zone: LoRa Alliance AS923, KR920, AU915, US915, EU868, IN865, RU864 Class A Join Active: OTAA / ABP Network Mode: Public Network / Private Network Tx Power: upto 20 dBm Frequency 860 - 930Mhz Date rate 250 bps - 5kbps Spreading factor SF12 - SF7 Bandwidth 125 kHz Unconfirmed-data message LoRaWAN application port for certification: 224 4.1.2 Data rate of LoRaWAN Sensor Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR2 980 SF10 125 AS923, AU915 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 980 SF10 125 US915 DR1 1760 SF9 125 DR2 3125 SF8 125 DR3 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 250 SF12 125 KR920, EU868, IN865, RU864 DR1 440 SF11 125 DR2 980 SF10 125 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 4.1.3 Tx power of LoRaWAN sensor Max EIRP (dBm) Max Tx Power (dBm) Region 16 16 AS923 14 14 KR920 30 20 AU915 30 20 US915 16 16 EU868 30 20 IN865 16 16 RU864 4.2 The principle of operation of the LoRaWAN sensor When starting the power supply, the LoRaWAN sensor has 60 seconds to allow configuration to operate via the Configuration Cable with the Modbus RTU protocol. After 60 seconds, the first packet will be sent, then the LoRaWAN sensor will send the next packets in the following cases: Case 1: When it reaches the frequency of taking data, the LoRaWAN sensor will wake up to measure and calculate. Then: If the measured value exceeds the High or Low setting thresholds, the packet will be sent to the Gateway and then asleep; If NOT then sleep without sending data. NOTE: Once sending the data to Gateway by this alarm event, the timer of sending time interval will be reset; Case 2: When the sending time interval is reached, the LoRaWAN sensor wakes up to measure and calculate and send data to Gateway immediately, regardless of value. Case 3: By using the magnet key, the LoRaWAN sensor can be triggered to send data to Gateway immediately. NOTE: The time between sending data for Class A is at least 3 seconds 4.3 Principle of operation LoRaWAN Network The LoRaWAN Gateway function is Packet Forwarder so: Between Gateway and End Device: Gateway receives data packets from End Device via RF connection, so it is recommended to configure Radio parameters (Note: the packet that Gateway receives is encrypted) Between Gateway and Network Server: Gateway forwards data packets to the Network server via an IP connection, so it is recommended to configure Network parameters such as Server Address, Server Uplink Port, Server Downlink Port, .. LoRaWAN Network is secured as follows: Network section key (NwkSKey) to ensure the security of communications on the Network Application session key (AppSKey) to ensure data security between End Device and Application Server Special keys of the device such as DevEUI, AppEUI, Gateway EUI, Device Address. Therefore, the data packet that the Gateway receives is encrypted and decrypted on the Application server. To End Device connect to the Network server, you need to register in the following two ways: Activation with OTAA (Over-the-Air activation): is the process of joining the Network automatically. Previously, both End Device and Application Server installed the same DevEUI code, AppEUI and AppKey. During activation, AppKey will generate 2 security keys for End Device and Network, which are: Network session key (NwkSKey): is the key to secure communication commands on MAC layer between End Device and Network server. Application session key (AppSKey): is the key to secure data packets between End Device and Application server. ATTENTIONS:* OTAA mode must be successfully activated in order for the End Device to send data packets to the Network through the Gateway;* OTAA mode only need to activate once, if the device is reset or battery replacement, it will activate OTAA again;* When the End Device is connected to the Network server, whether the Gateway is reset or the power is restarted, it will not need to activate OTAA. Activation by ABP (Activation by Personalization): is the process of joining Network manually. Device Address, Network session key (NwkSKey) and Application session key (AppSKey) codes must be stored inside the End Device and Application server, so when the End Device sends data packets to the Network server, it will also send the security codes to activated. 4.4 Configure the LoRaWAN Network 4.4.1 Configure End Device operation according to OTAA Configuration parameters for the End Device to be activated by OTAA as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode OTAA Device activation type on Network Server DevEUI 34 35 31 31 4B 37 75 12 Device ID's unique ID number => Set this ID number for the Application server AppEUI 70 B3 D5 7E D0 02 D5 0B Application server's unique ID number (random or user generated)=> Set this ID number for End Device AppKey 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C Key Number for generating 2 NwkSKey and AppSKey security keys created by the user (factory-created by default)=> Used to install for both the Device and Application Server End ATTENTIONS:* The AppEUI number from Application Server => then installed for the End Device. AppEUI is randomly generated by the Application server or by the user;* The number of AppKeys during OTAA activation will generate two security keys, Lora NwkSKey and AppSKey, which are used for both End Device and Network. 4.4.2 Configure End Device operation according to ABP Configuration parameters for the End Device to be activated by ABP as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode ABP Device activation type on Network Server Device Address 12 34 56 78 End Device Address created by Application server=> Set Device Address for End Device NwkSKey (Network session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C NwkSKey number created by the user to install and use for both End Device and Application Server AppSKey (Application session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C AppSKey number generated by the user to install for both End Device and Application Server 4.4.3 Configure Gateway operations 4.4.3.1 Configure the Gateway to receive data packets from the End Device. Radio settings need to be set as:* Region code: AS923, KR920, AU915, US915, EU868, IN865, RU864* Center Frequency, Channels, Bandwidth (recommends using the default configuration created by the system) Let's take an example to configure the Gateway operation of URSALINK (Model: UG85-L00E-915) 4.4.3.2 Configure the Gateway to communicate with the Public Network Server Let's take an example of configuring Gateway UG85 to connect with "thethingsnetwork.org" in Asia: Currently thethingsnetwork only supports the connection protocol with Gateway is Semtech UDP Packet Forwarder. https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Parameter settings Setting value (example) Description Gateway EUI 24e124fffef038fd Gateway's unique ID number=> Set this ID number for Application server Server Address router.as1.thethings.network Semtech server address: https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Router regional asia: router.as1.thethings.network Router regional india: ttn.thingsconnected.net Ursalink server address: localhost Server Uplink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Server Downlink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Network mode Public LoRaWAN 4.4.4 Register the Application server on the Public Network "thethingsnetwork.org" 4.4.4.1 Register the Gateway on Public Network "thethingsnetwork.org" as shown below: The current network only supports the Gateway connection protocol, "Semtech UDP protocol" is Semtech UDP Packet Forwarder. Then power the Gateway and observe the message "Status: connected" => Registration of the Gateway on the Application successfully. 4.4.4.2 Register Application on Public Network "thethingsnetwork.org" as shown below: 4.4.4.3 Register End Device on Application: 4.5 LED meaning RED LED: Fixed ON: due to noise caused peripheral components (i2c, spi, uart, timer, rtc, wdt, ...) do not initialize. Flashing 10ms ON / 10s OFF: Activation by OTAA on the Network server failed. Flashing 10ms ON / 2s OFF:  Sending data packet to Gateway failed. GREEN LED: Flashing 100ms ON / OFF when sending data packet to Gateway. BLUE LED: Flashing 1s ON / 1s OFF for the first 60 seconds when booting (insert batteries or connected external sources), after 60 seconds OFF. ON during the LoRaWAN sensor receives data packets from the Network server and OFF when received. 4.6 Process of measurement When the LoRa sensor wakes up, it will supply power to the external sensor module so that the module can start measuring. After measuring it will turn off the power to the module. The measured value is the raw value of the sensor module, which can be ambient temperature, ambient humidity, etc. The measurement value can be scaled according to the following formula: Y = aX + b X: the raw value from module sensor Y: the calculated value will be sent to Sigfox base station in the payload data. a: constant (default value is 1) b: constant (default value is 0) 4.7 Payload Data The folllowing is the format of payload data will be sent to Sigfox server. Length is 6 bytes, it is future-proof for expansion to 12 bytes. Sensor type (1 byte) Status (1 byte) 1st - Parameter (4 bytes) 2nd - Parameter (4 bytes) Meaning of Data in the Payload Data Size (byte) Bit Format Meaning Sensor type 1 all Uint8 Sensor type = 0x02 means LoRaWAN Node with I2C Humidity & TemperatureSensor type = 0xFF means no sensor Status: battery level 1 Bit 7 and 6 Uint8 Battery capacity in 04 levels 11: battery level 4 (99%) 10: battery level 3 (60%) 01: battery level 2 (30%) 00: battery level 1 (10%) Status: error Bit 5 and 4 Node status 01: error 00: no error Status: alarm 1 Bit 3 and 2 Alarm status of 1st - Parameter (Y1 value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm Status: alarm 2 Bit 1 and 0 Alarm status of 2nd - Parameter (Y2 value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm 1st - Parameter 4 all Float Y1 value: humidity value (%) 2nd - Parameter 4 all Float Y2 value: temperature value (oC) 5. Configuration Using the configuration cable to connect to the sensor as below picture. Serial port configuration on the computer:* COMPort, Baudrate: 9600, Parity: None, Stop bit: 1, Data bit: 8* Modbus RTU: Reading data by Function 3 / Writing data by Function 16. 5.1 Step to configure NOTE: The Modbus configuration can only be performed in the first 60s after power up the LoRaWAN sensor. After 60s, if user can not finish the configuration process, user need to reset the power of LoRaWAN sensor again, by removing battery in at least 15s. Step 1: Install the Modbus Configurator Software in the link below https://filerun.daviteq.com/wl/?id=qK0PGNbY1g1fuxTqbFW9SXtEvCw7bpc6 How to use the Modbus configuration software Step 2: Plug the configuration cable to computer via usb port and install the driver; Step 3: Open the plastic housing with L hex key to unscrew M4 screws at the side of housing Step 4: Plug the connector to the configuration port; Step 5:  Import the configuration file by importing the csv file: Go to MENU: FILE / Import New / => select the file with name CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0.csv (in the link below). Then click Connect; CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0 To write new value to the device:First, you need to write the password in "password for setting", after reading the value to check ok, you can write the new value AppEUI, AppKey, ...You only have 60 seconds after plugging the configuration cable or the power supply into the device for configuration. 5.2 Register table Here is the table of Data will be read by Modbus tool Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 0 0 3 5 device info WSLRW-I2C string Read Wireless Sensor LoRaWAN - I2C 5 5 3 4 firmware version 1.00ddmm string Read ddmm = day / month 9 9 3 2 hardware version 1.10 string Read 11 B 3 4 lorawan protocol version 01.00.03 string Read lorawan v1.0.3 15 F 3 6 application version 01.03.00.00 string Read application server v1.3.0.0 21 15 3 6 mac layer version 04.04.02.00 string Read mac layer v4.4.2.0 27 1B 3 4 deviceEUI hex Read End Device's EUI number, used to register the product on the Network Server by OTAA 31 1F 3 4 lora appEUI hex Read Application server's EUI number is used to register the product on the Network Server by OTAA 35 23 3 8 lora appKey hex Read The number of keys used to create two security keys of the End Device, used to register the product on the Network Server by OTAA 43 2B 3 8 lora nwkSkey hex Read key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 51 33 3 8 lora appSkey hex Read End Device data encryption key number, used to register the product on the Network Server by ABP 59 3B 3 2 device address 0 uint32 Read End Device address created by Application server, used to register the product on the Network server by ABP 61 3D 3 2 network ID 0 uint32 Read Network server ID number, used to register the product on the Network server by ABP 63 3F 3 2 join mode OTAA string Read OTAA: Over-the-Air activation, ABP: Activation by Personalization 65 41 3 4 network mode PUBLIC string Read PUBLIC, PRIVATE 69 45 3 3 region code AS923 string Read 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 72 48 3 4 data rate DR2:980 string Read DR0:250, DR1:440, DR2:980, DR3:1760, DR4:3125, DR5:5470 76 4C 3 3 bandwidth BW125 string Read BW125, BW250, BW500 79 4F 3 2 spread factor SF10 string Read SF12, SF11, SF10, SF9, SF8, SF7 81 51 3 4 activation of ADR ADR OFF string Read ADR ON, ADR OFF 85 55 3 1 class A string Read 103 67 3 1 sensor type 1-255 uint16 Read 1-254: sensor type, 255: no sensor 104 68 3 1 battery level 0-3 uint16 Read 4 levels of battery capacity status 105 69 3 1 error status 0-1 uint16 Read Error code of sensor, 0: no error, 1: error 106 6A 3 1 prm1 alarm status 0-2 uint16 Read Alarm status of parameters 1, 0: none, 1: Low, 2: High 107 6B 3 1 prm2 alarm status 0-2 uint16 Read Alarm status of parameter 2 108 6C 3 2 prm1 value float Read Parameter value 1 110 6E 3 2 prm2 value float Read Parameter value 2 112 70 3 1 battery % 10%, 30%, 60%, 99% uint16 Read % Value of battery capacity 113 71 3 2 battery voltage 0-3.67 vdc float Read Value of battery voltage 115 73 3 2 mcu temperature oC float Read Temperature value of RF module 117 75 3 1 mcu vref 0-3.67 vdc uint16 Read Vref value of RF module 118 76 3 1 button1 status 0-1 uint16 Read Button state, 0: No button pressed, 1: Button pressed 119 77 3 1 button2 status 0-1 uint16 Read Button status, 0: No magnetic sensor detected, 1: Magnetic sensor detected Here is the table for Configuration: Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 256 100 3 / 16 1 modbus address 1-247 1 uint16 R/W Modbus address of the device 257 101 3 / 16 1 modbus baudrate 0-1 0 uint16 R/W 0: 9600, 1: 19200 258 102 3 / 16 1 modbus parity 0-2 0 uint16 R/W 0: none, 1: odd, 2: even 259 103 3 / 16 9 serial number string R/W (Password) 268 10C 3 / 16 2 password for setting uint32 R/W (Password) password 190577 270 10E 3 / 16 4 lora appEUI hex R/W (Password) Application server's EUI number, used to register the product on the Network Server by OTAA 274 112 3 / 16 8 lora appKey hex R/W (Password) The number of keys used to create two security keys of the End Device, used to register the product on the Network server by OTAA 282 11A 3 / 16 8 lora nwkSkey hex R/W (Password) key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 290 122 3 / 16 8 lora appSkey hex R/W (Password) End Device data encryption key number, used to register the product on the Network Server by ABP 298 12A 3 / 16 2 device address uint32 R/W (Password) End Device address created by Application server, used to register the product on the Network server by ABP 300 12C 3 / 16 2 network ID uint32 R/W (Password) Network server ID number, used to register the product on the Network server by ABP 302 12E 3 / 16 1 activation mode 0-1 1 uint16 R/W (Password) 1: OTAA (Over-the-Air Activation), 0: ABP (Activation by Personalization) 304 130 3 / 16 1 application port 1-255 1 uint16 R/W (Password) Port 224 is reserved for certification 317 13D 3 / 16 1 region 1-7 1 uint16 Read/Write(Password) 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 318 13E 3 / 16 1 data rate 7 uint16 R/W (Password) 0: 250 bps, 1: 440 bps, 2: 980 bps, 3: 1760 bps, 4: 3125 bps, 5: 5470 bps 319 13F 3 / 16 1 tx power 2-20 16 uint16 R/W (Password) tx power: 2,4,6,8,10,12,14,16,18,20 320 140 3 / 16 1 adaptative data rate 0-1 0 uint16 R/W (Password) Automatically adjust data rate, 0: disable, 1: enable 334 14E 3 / 16 2 cycle send data 900 uint32 R/W sec (data sending cycle) 338 152 3 / 16 1 alarm limt 44 uint16 R/W limit the number of events / day 340 154 3 / 16 2 sensor1: sampling_rate 120 uint32 R/W sec (frequency of data taken from sensor 1) 348 15C 3 / 16 2 prm1: a 1 float R/W Scale parameter "a" of sensor 1 350 15E 3 / 16 2 prm1: b 0 float R/W Scale parameter "b" of sensor 1 354 162 3 / 16 2 prm1: High Threshold 100000 float R/W High threshold value of sensor 1 356 164 3 / 16 2 prm1: High Hysteresis 10000 float R/W High hysteresis value of sensor 1 358 166 3 / 16 2 prm1: Low Threshold 0 float R/W Low threshold value of sensor 1 360 168 3 / 16 2 prm1: Low Hysteresis 10000 float R/W Low hysteresis value of sensor 1 362 16A 3 / 16 2 prm1: High Cut 100000 float R/W Upper limit value of sensor 1 364 16C 3 / 16 2 prm1: Low Cut 0 float R/W Lower limit value of sensor 1 366 16E 3 / 16 2 prm2: a 1 float R/W Scale parameter "a" of sensor 2 368 170 3 / 16 2 prm2: b 0 float R/W Scale parameter "b" of sensor 2 372 174 3 / 16 2 prm2: High Threshold 100000 float R/W High threshold value of sensor 2 374 176 3 / 16 2 prm2: High Hysteresis 10000 float R/W High hysteresis value of sensor 2 376 178 3 / 16 2 prm2: Low Threshold 0 float R/W Low threshold value of sensor 2 378 17A 3 / 16 2 prm2: Low Hysteresis 10000 float R/W Low hysteresis value of sensor 2 380 17C 3 / 16 2 prm2: High Cut 100000 float R/W Upper limit value of sensor 2 382 17E 3 / 16 2 prm2: Low Cut 0 float R/W Lower limit value of sensor 2 6. Installation 6.1 Example application 6.2 Installation location To maximize the distance of transmission, the ideal condition is Line-of-sight (LOS) between the LoRaWAN sensor and Gateway. In real life, there may be no LOS condition. However, the LoRaWAN sensor still communicates with Gateway, but the distance will be reduced significantly. ATTENTION:DO NOT install the LoRaWAN 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, cement…is acceptable. 6.3 Battery installation Steps for battery installation: Step 1: Using L hex key to unscrew M4 screws at the side of housing and carefully pull out the top plastic housing in the vertical direction Step 2: Insert 02 x AA 1.5VDC battery, please take note the poles of battery ATTENTION: REVERSED POLARITY OF BATTERIES IN 10 SECONDS CAN DAMAGE THE SENSOR CIRCUIT!!! Step 3: Insert the top plastic housing and locking by L hex key ATTENTION: When reinstalling the cover, pay attention to put the PCB edge into the middle slot of the box inside as shown below) 7. Troubleshooting No. Phenomena Reason Solutions 1 The BLUE LED does not blink when the battery is installed Insert the battery in the opposite direction Insert the battery in the correct way 2 The RED LED is always on Due to noise, the peripheral components (i2c, spi, uart, ..) of RF module cannot be initialized After 30s the node will automatically reset. If the noise causes the Watchdog not to initialize, remove the battery and wait for more than 10 seconds, then insert the battery again 3 The RED LED blinks continuously (10ms ON / 2s OFF) and the Node does not send RF. After more than 10 sending cycles, the Node will automatically reset Operating frequency in that country is prohibited Operating frequency in that country is limited to Data rate, Tx Power Reconfigure the allowed frequency of operation Reconfigure Data rate = DR5 / SF07, Tx Power 4 RED LED blinks continuously (10ms ON / 2s OFF) and Node sends RF continuously 3s / time but no data. After more than 10 sending cycles, the Node will automatically reset Node runs dummy sending mode => sent by Gateway to send Downlink packets when users clear Uplink and Downlink counter values on Network Server (build in Gateway) when activated by ABP Configuration enabled by OTAA 5 The RED LED flashes 10ms ON / 10s OFF and the Node does not send RF Node activation by OTAA on Network server has not been successful Using Margnet-Key to force Node to send RF continuously for 3 seconds / time => when activating by OTAA successfully, the GREEN LED will blink after sending RF 6 The node sent RF successfully but the GREEN LED did not blink LED is broken Warranty to replace LED 7 The data packet taken from the Gateway has an incorrect value The data package is encrypted Get the decoded packet on the Application Server 8 Node sends RF and activates by ABP, on Gateway receives data but Application server has no data The application server still stores the counter values of the previous Uplink and Downlink Delete the counter values of Uplink and Downlink on the Application server 9 The node does not send RF and the RF module is hot Insert the battery in the opposite direction Short circuit Warranty or replacement 10 Node does not send RF to Gateway according to the alarm, LED does not blink The alarm configuration is incorrect Running out of the number of alarms set for the day Check alarm configuration Check the configuration for the maximum number of alarms per day 11 Node does not send RF to Gateway when activated by the magnetic switch, LED does not blink Magnetic switch has malfunctioned Read the status of the magnetic switch via modbus (when powering or attaching the battery) to see if the magnetic switch is working. 12 Node has blinked LED GREEN when sending RF but the Gateway or Application server cannot received LoRa module on the Gateway is faulty The IP connection (4G / WiFi / ...) on the Gateway is faulty Check Gateway's LoRa status lights on Gateway Check 4G / WiFi status lights on Gateway 13 The value of the sensor is 0 and sensor_type = 0xFF Lost connection with the sensor Check sensor connection Replace the module sensor 14 RSSI is weak and often loses data Distance between Node and Gateway is far or there are many obstructions Connection to Antenna problem Install metal nodes or in metal cabinets Configure Data rate = DR0 / SF12 Check Antenna position Install Node in a well ventilated location 8. Support contacts Manufacturer Daviteq Technologies IncNo.11 Street 2G, Nam Hung Vuong Res., An Lac Ward, Binh Tan Dist., Ho Chi Minh City, Vietnam.Tel: +84-28-6268.2523/4 (ext.122) Email: info@daviteq.com | www.daviteq.com Distributor in Australia and New Zealand Templogger Pty Ltd Tel: 1800 LOGGER Email: contact@templogger.net USER GUIDE FOR LORAWAN TILT SENSOR WSLRW-AG THIS IS OBSOLETE MANUAL Please access https://www.iot.daviteq.com/wireless-sensors for updated manual WSLRW-AG-MN-EN-01 NOV-2022 This document is applied for the following products SKU WSLRW-AG HW Ver. 1.1 FW Ver. 1.3 Item Code WSLRW-AG-8-01 Wireless LoRaWAN XYZ Tilt sensor, Internal antenna, Type AA battery 1.5VDC, IP68, 860-870 Mhz for EU868, IN865, RU864 WSLRW-AG-9-01 Wireless LoRaWAN XYZ Tilt sensor, Internal antenna, Type AA battery 1.5VDC, IP68, 900-930 Mhz for KR920, AS923, AU915, US915 WSLRW-AG-01 Wireless LoRaWAN XYZ Tilt sensor, Internal antenna, 0.1° Resolution, Type AA battery 1.5VDC, IP68, 860-930 MHz WSLRW-AG-02 Wireless LoRaWAN XYZ Tilt sensor, Internal antenna, 0.01° Resolution, Type AA battery 1.5VDC, IP68, 860-930 MHz 0. Configuration Check List STEP 1: Configure End Device (Using Modbus Configuration Cable) Setting value (Example) 1. Select region AS923, IN865, EU868,.. (refer to register address 317) 2. End Device Operation OTAA or ABP OTAA Write AppEUI information from Application Server to Lorawan End Device; Write AppKey (created by user) information for Lorawan End Device and Application Server. ABP Write DevEUI information from Application Server to Lorawan end device; write Network Session Key and App Session Key (created by user) information to Lorawan end device (and Application Server). 3. Configure "cycle send data" 900 sec (Defaut) 4. Configure "sensor sampling_rate" 120 sec (Defaut) 5. Configure parameters of sensor (Refer to Check data configuration table) STEP 2:  Configure the operation of LoRaWAN Gateway (Ex: URSALINK Gateway) 1. Configure the information in the General tab Server address, Server port (For more information) 2. Configure the information in the Radio tab Select the Region Region (Other parameters to default) STEP 3:  Configure the operation of LoRaWAN Gateway on Network Server (Ex: URSALINK Gateway with Thethingsnetwork) 1. Gateway ID registration Gateway ID is the GatewayEUI information on the Gateway 2. Frequency Plan parameters configuration Asia 920-923MHz, Europe 868MHz,... 3. Router parameters configuration 4. Check the connection of the gateway to the network server The Gateway status LED lights up and displays the message "Status: conneted" on the Thethingsnetwork STEP 4:  Configure the operation of Application Server on Network Server 1. App ID registration 2. Handler parameters configuration STEP 5: Register Lorawan End Device on Application Server on Thethingsnetwork 1. ID Registration 2.Select operation mode OTAA or ABP OTAA Configure parameters DevEUI and AppKEY ABP Configure parameters Device Address, Network Session Key, App Session Key 1. Functions Change Log HW Ver. FW Ver. Release Date Functions Change 1.1 1.0.0 21-July-2020 1.1 1.1.x 05-Oct-2020 Data frame improvements Fix the Watchdog bug 1.1 1.2.0 12-Oct-2020 The minimum frequency of sending data packets to Gateway is 15 seconds When connecting to network server with OTAA failure, it will not read sensor value 1.1 1.3 28-July-2022 Update for sample frequency of tilt measurement 2. Introduction WSLRW-AG is LoRaWAN Tilt Sensor, can be used to measure 3 tilt angles X, Y, Z of any object as Tower, Building, Tree, Electricity Tower, Telecom Tower, Bridges... The Tilt sensor utilises the combination of advanced Accelerometer and Gyro meter to deliver high accuracy and stable measurement of Tilt angle of 03 axis X,Y,Z. With Ultra-low Power design and smart firmware allow the sensor can last up to 10 years with 02 x AA-type battery (depends on configuration). The sensor will transmit data in kilo-meters distance to LoRaWAN gateway, any brand on the market. 3. Specification SENSORS SPECIFICATION: Tilt Sensor Built-in advanced accelerometer and gyro meter to deliver tilt angle measurement of X, Y, Z Measurement range ± 90° of XYZ Resolution 0.5° Sensor sampling rate 1Hz max Alarm setting setting the alarm threshold for each angle LoRaWAN SPECIFICATION: Data rate 250bps .. 5470bps Antenna Internal Antenna 2.67 dbi Battery 02 x AA size 1.5VDC, battery not included RF Frequency and Power 860..930Mhz, +14 .. +20 dBm, configurable for zones: EU868, IN865, RU864, KR920, AS923, AU915, US915 Protocol LoRaWAN Data sending modes interval time, alarm occurred and manually triggering by magnetic key RF Module complies to ETSI EN 300 220, EN 303 204 (Europe) FCC CFR47 Part15 (US), ARIB STD-T108 (Japan) Vietnam Type Approval TBA Working temperature -40oC..+60oC (with AA L91 Energizer) Dimensions H106xW73xD42 Net-weight 190 grams Housing Aluminum + Polycarbonate plastic, IP68 4. Operation Principle 4.1 LoRaWAN protocol specifications 4.1.1 LoRaWAN Sensor protocol specifications LoRaWAN Protocol Version 1.0.3 Application Server Version 1.3.0.0 MAC Layer Version 4.4.2.0 Radio Standards: LoRa Alliance Certified LoRaWAN Zone: LoRa Alliance AS923, KR920, AU915, US915, EU868, IN865, RU864 Class A Join Active: OTAA / ABP Network Mode: Public Network / Private Network Tx Power: up to 20 dBm Frequency: 860 - 930Mhz Date rate: 250 bps - 5kbps Spreading factor: SF12 - SF7 Bandwidth: 125 kHz Unconfirmed-data message LoRaWAN application port for certification: 224 4.1.2 Data rate of LoRaWAN Sensor Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR2 980 SF10 125 AS923, AU915 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 980 SF10 125 US915 DR1 1760 SF9 125 DR2 3125 SF8 125 DR3 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 250 SF12 125 KR920, EU868, IN865, RU864 DR1 440 SF11 125 DR2 980 SF10 125 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 4.1.3 Tx power of LoRaWAN sensor Max EIRP (dBm) Max Tx Power (dBm) Region 16 16 AS923 14 14 KR920 30 20 AU915 30 20 US915 16 16 EU868 30 20 IN865 16 16 RU864 4.2 The principle of operation of the LoRaWAN sensor When starting the power supply, the LoRaWAN sensor has 60 seconds to allow configuration to operate via the Configuration Cable with the Modbus RTU protocol. After 60 seconds, the first packet will be sent, then the LoRaWAN sensor will send the next packets in the following cases: Case 1: When it reaches the frequency of taking data, the LoRaWAN sensor will wake up to measure and calculate. Then: If the measured value exceeds the High or Low setting thresholds, the packet will be sent to the Gateway and then asleep; If NOT then sleep without sending data. NOTE: Once sending the data to Gateway by this alarm event, the timer of sending time interval will be reset; Case 2: When the sending time interval is reached, the LoRaWAN sensor wakes up to measure and calculate and send data to Gateway immediately, regardless of value. Case 3: By using the magnet key, the LoRaWAN sensor can be triggered to send data to Gateway immediately. NOTE: The time between sending data for Class A is at least 3 seconds 4.3 Principle of operation LoRaWAN Network The LoRaWAN Gateway function is Packet Forwarder so: Between Gateway and End Device: Gateway receives data packets from End Device via RF connection, so it is recommended to configure Radio parameters (Note: the packet that Gateway receives is encrypted) Between Gateway and Network Server: Gateway forwards data packets to the Network server via an IP connection, so it is recommended to configure Network parameters such as Server Address, Server Uplink Port, Server Downlink Port,... LoRaWAN Network is secured as follows: Network section key (NwkSKey) to ensure the security of communications on the Network The application session key (AppSKey) to ensure data security between End Device and Application Server Special keys of the device such as DevEUI, AppEUI, Gateway EUI, Device Address. Therefore, the data packet that the Gateway receives is encrypted and decrypted on the Application server. To End Device connect to the Network server, you need to register in the following two ways: Activation with OTAA (Over-the-Air activation): is the process of joining the Network automatically. Previously, both End Device and Application Server installed the same DevEUI code, AppEUI, and AppKey. During activation, AppKey will generate 2 security keys for End Device and Network, which are: The network session key (NwkSKey): is the key to secure communication commands on the MAC layer between the End Device and the Network server. The application session key (AppSKey): is the key to secure data packets between the End Device and Application server. ATTENTIONS:* OTAA mode must be successfully activated in order for the End Device to send data packets to the Network through the Gateway;* OTAA mode only need to activate once, if the device is reset or battery replacement, it will activate OTAA again;* When the End Device is connected to the Network server, whether the Gateway is reset or the power is restarted, it will not need to activate OTAA. Activation by ABP (Activation by Personalization): is the process of joining the Network manually. Device Address, Network session key (NwkSKey), and Application session key (AppSKey) codes must be stored inside the End Device and Application server, so when the End Device sends data packets to the network server, it will also send the security codes to activate. 4.4 Configure the LoRaWAN Network 4.4.1 Configure End Device operation according to OTAA Configuration parameters for the End Device to be activated by OTAA as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode OTAA Device activation type on Network Server DevEUI 34 35 31 31 4B 37 75 12 Device ID's unique ID number => Set this ID number for the Application server AppEUI 70 B3 D5 7E D0 02 D5 0B Application server's unique ID number (random or user-generated)=> Set this ID number for End Device AppKey 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C Key Number for generating 2 NwkSKey and AppSKey security keys created by the user (factory-created by default)=> Used to install for both the Device and Application Server End ATTENTIONS:* The AppEUI number from Application Server => then installed for the End Device. AppEUI is randomly generated by the Application server or by the user;* The number of AppKeys during OTAA activation will generate two security keys, Lora NwkSKey and AppSKey, which are used for both End Device and Network. 4.4.2 Configure End Device operation according to ABP Configuration parameters for the End Device to be activated by ABP as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode ABP Device activation type on Network Server Device Address 12 34 56 78 End Device Address created by the Application server=> Set Device Address for End Device NwkSKey (Network session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C NwkSKey number created by the user to install and use for both End Device and Application Server AppSKey (Application session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C AppSKey number generated by the user to install for both End Device and Application Server 4.4.3 Configure Gateway operations 4.4.3.1 Configure the Gateway to receive data packets from the End Device. Radio settings need to be set as:* Region code: AS923, KR920, AU915, US915, EU868, IN865, RU864* Center Frequency, Channels, Bandwidth (recommends using the default configuration created by the system) Let's take an example to configure the Gateway operation of URSALINK (Model: UG85-L00E-915) 4.4.3.2 Configure the Gateway to communicate with the Public Network Server Let's take an example of configuring Gateway UG85 to connect with "thethingsnetwork.org" in Asia: Currently, thethingsnetwork only supports the connection protocol with Gateway is Semtech UDP Packet Forwarder. https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Parameter settings Setting value (example) Description Gateway EUI 24e124fffef038fd Gateway's unique ID number=> Set this ID number for Application server Server Address router.as1.thethings.network Semtech server address: https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Router regional Asia: router.as1.thethings.network Router regional India: ttn.thingsconnected.net Ursalink server address: localhost Server Uplink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Server Downlink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Network mode Public LoRaWAN 4.4.4 Register the Application server on the Public Network "thethingsnetwork.org" 4.4.4.1 Register the Gateway on Public Network "thethingsnetwork.org" as shown below: The current network only supports the Gateway connection protocol, "Semtech UDP protocol" is Semtech UDP Packet Forwarder. Then power the Gateway and observe the message "Status: connected" => Registration of the Gateway on the Application successfully. 4.4.4.2 Register Application on Public Network "thethingsnetwork.org" as shown below: 4.4.4.3 Register End Device on Application: 4.5 LED meaning RED LED: Fixed ON: due to noise caused peripheral components (i2c, spi, uart, timer, rtc, wdt, ...) do not initialize. Flashing 10ms ON / 10s OFF: Activation by OTAA on the Network server failed. Flashing 10ms ON / 2s OFF:  Sending a data packet to Gateway failed. GREEN LED: Flashing 100ms ON / OFF when sending a data packet to Gateway. BLUE LED: Flashing 1s ON / 1s OFF for the first 60 seconds when booting (insert batteries or connected external sources), after 60 seconds OFF. ON during the LoRaWAN sensor receives data packets from the Network server and OFF when received. 4.6 Process of measurement When the LoRa sensor wakes up, it will supply power to the internal or external sensor so that the sensor can start measuring. After measuring successfully it will turn off the power to the sensor for energy saving. The measured value is the raw value of the sensor. The measured value can be scaled according to the following formula: Y = aX + b X: the raw value from the sensor Y: the calculated value will be sent to LoRaWAN Gateway in the payload data. a: constant (default value is 1) b: constant (default value is 0) So, if there is no user setting for a and b ==> Y = X The Y value will be compared with Lo and Hi threshold. Please refer below the graph of alarm processing. 4.7 Payload Data The following is the format of payload data that will be sent to the LoRaWAN Gateway. Sensor type (1 byte) Status1 (1 byte) Status2 (1 byte) 1st - Parameter (Int16) 2nd - Parameter (Int16) 3rd - Parameter (Int16) Meaning of Data in the Payload Data Size (byte) Bit Format Meaning Sensor type 1 all Uint8 Sensor type = 0x0D means LoRaWAN Tilt Sensor. Sensor type = 0xFF means no sensor Status1: battery level 1 Bit 7 and 6 Uint8 Battery capacity in 04 levels 11: battery level 4 (99%) 10: battery level 3 (60%) 01: battery level 2 (30%) 00: battery level 1 (10%) Status1: error Bit 5 and 4 Node status 01: error 00: no error Status1: alarm 1 Bit 3 and 2 Alarm status of 1st - Parameter (X Tilt value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm Status1: alarm 2 Bit 1 and 0 Alarm status of 2nd - Parameter (Y Tilt value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm 1 Bit 7 and 2 Uint8 Not Applicable Status2: alarm 3 Bit 1 and 0 Alarm status of 3rd - Parameter (Z Tilt value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm 1st - Parameter 2 all Int16 X Tilt value = Real X Tilt value * 10  (range: -90o…+90o) 2nd - Parameter 2 all Int16 Y Tilt value = Real Y Tilt value * 10(range: -90o…+90o) 3rd - Parameter 2 all Int16 Z Tilt value = Real Z Tilt value * 10(range: -90o…+90o) 5. Configuration Using the configuration cable to connect to the sensor as below picture. Serial port configuration on the computer:* COMPort, Baudrate: 9600, Parity: None, Stop bit: 1, Data bit: 8* Modbus RTU: Reading data by Function 3 / Writing data by Function 16. 5.1 Step to configure NOTE: The Modbus configuration can only be performed in the first 60s after power up the LoRaWAN sensor. After 60s, if user can not finish the configuration process, user need to reset the power of LoRaWAN sensor again, by removing battery in at least 15s. Step 1: Install the Modbus Configurator Software in the link below https://filerun.daviteq.com/wl/?id=qK0PGNbY1g1fuxTqbFW9SXtEvCw7bpc6 How to use the Modbus configuration software Step 2: Plug the configuration cable to computer via USB port and install the driver; Step 3: Open the plastic housing with L hex key to unscrew M4 screws at the side of the housing Step 4: Plug the connector to the configuration port; Step 5:  Import the configuration file by importing the csv file: Go to MENU: FILE / Import New / => select the file with name CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0.csv (in the link below). Then click Connect; CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0 To write new value to the device:First, you need to write the password in "password for setting", after reading the value to check ok, you can write the new value AppEUI, AppKey, ...You only have 60 seconds after plugging the configuration cable or the power supply into the device for configuration. 5.2 Register table Here is the table of Data will be read by Modbus tool Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 0 0 3 5 device info WSLRW-I2C string Read Wireless Sensor LoRaWAN - I2C 5 5 3 4 firmware version 1.00ddmm string Read ddmm = day / month 9 9 3 2 hardware version 1.10 string Read 11 B 3 4 lorawan protocol version 01.00.03 string Read lorawan v1.0.3 15 F 3 6 application version 01.03.00.00 string Read application server v1.3.0.0 21 15 3 6 mac layer version 04.04.02.00 string Read mac layer v4.4.2.0 27 1B 3 4 deviceEUI hex Read End Device's EUI number, used to register the product on the Network Server by OTAA 31 1F 3 4 lora appEUI hex Read Application server's EUI number is used to register the product on the Network Server by OTAA 35 23 3 8 lora appKey hex Read The number of keys used to create two security keys of the End Device, used to register the product on the Network Server by OTAA 43 2B 3 8 lora nwkSkey hex Read key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 51 33 3 8 lora appSkey hex Read End Device data encryption key number, used to register the product on the Network Server by ABP 59 3B 3 2 device address 0 uint32 Read End Device address created by Application server, used to register the product on the Network server by ABP 61 3D 3 2 network ID 0 uint32 Read Network server ID number, used to register the product on the Network server by ABP 63 3F 3 2 join mode OTAA string Read OTAA: Over-the-Air activation, ABP: Activation by Personalization 65 41 3 4 network mode PUBLIC string Read PUBLIC, PRIVATE 69 45 3 3 region code AS923 string Read 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 72 48 3 4 data rate DR2:980 string Read DR0:250, DR1:440, DR2:980, DR3:1760, DR4:3125, DR5:5470 76 4C 3 3 bandwidth BW125 string Read BW125, BW250, BW500 79 4F 3 2 spread factor SF10 string Read SF12, SF11, SF10, SF9, SF8, SF7 81 51 3 4 activation of ADR ADR OFF string Read ADR ON, ADR OFF 85 55 3 1 class A string Read 103 67 3 1 sensor type 1-255 uint16 Read 1-254: sensor type, 255: no sensor 104 68 3 1 battery level 0-3 uint16 Read 4 levels of battery capacity status 105 69 3 1 error status 0-1 uint16 Read Error code of sensor, 0: no error, 1: error 106 6A 3 1 prm1 alarm status 0-2 uint16 Read Alarm status of parameters 1, 0: none, 1: Low, 2: High 107 6B 3 1 prm2 alarm status 0-2 uint16 Read Alarm status of parameter 2 108 6C 3 2 prm1 value float Read Value of parameter 1 110 6E 3 2 prm2 value float Read Value of parameter 2 112 70 3 1 battery % 10%, 30%, 60%, 99% uint16 Read % Value of battery capacity 113 71 3 2 battery voltage 0-3.67 vdc float Read Value of battery voltage 115 73 3 2 mcu temperature oC float Read Temperature value of RF module 117 75 3 1 mcu vref 0-3.67 vdc uint16 Read Vref value of RF module 118 76 3 1 button1 status 0-1 uint16 Read Button state, 0: No button pressed, 1: Button pressed 119 77 3 1 button2 status 0-1 uint16 Read Button status, 0: No magnetic sensor detected, 1: Magnetic sensor detected 126 78 3 2 prm3 value float Read Value of parameter 3 128 7A 3 1 prm3 alarm status 0-2 uint16 Read Report the alarm status of parameter 3 Here is the table for Configuration: Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 256 100 3 / 16 1 modbus address 1-247 1 uint16 R/W Modbus address of the device 257 101 3 / 16 1 modbus baudrate 0-1 0 uint16 R/W 0: 9600, 1: 19200 258 102 3 / 16 1 modbus parity 0-2 0 uint16 R/W 0: none, 1: odd, 2: even 259 103 3 / 16 9 serial number string R/W (Password) 268 10C 3 / 16 2 password for setting uint32 R/W (Password) password 190577 270 10E 3 / 16 4 lora appEUI hex R/W (Password) Application server's EUI number, used to register the product on the Network Server by OTAA 274 112 3 / 16 8 lora appKey hex R/W (Password) The number of keys used to create two security keys of the End Device, used to register the product on the Network server by OTAA 282 11A 3 / 16 8 lora nwkSkey hex R/W (Password) key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 290 122 3 / 16 8 lora appSkey hex R/W (Password) End Device data encryption key number, used to register the product on the Network Server by ABP 298 12A 3 / 16 2 device address uint32 R/W (Password) End Device address created by Application server, used to register the product on the Network server by ABP 300 12C 3 / 16 2 network ID uint32 R/W (Password) Network server ID number, used to register the product on the Network server by ABP 302 12E 3 / 16 1 activation mode 0-1 1 uint16 R/W (Password) 1: OTAA (Over-the-Air Activation), 0: ABP (Activation by Personalization) 304 130 3 / 16 1 application port 1-255 1 uint16 R/W (Password) Port 224 is reserved for certification 317 13D 3 / 16 1 region 1-7 1 uint16 Read/Write(Password) 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 318 13E 3 / 16 1 data rate 7 uint16 R/W (Password) 0: 250 bps, 1: 440 bps, 2: 980 bps, 3: 1760 bps, 4: 3125 bps, 5: 5470 bps 319 13F 3 / 16 1 tx power 2-20 16 uint16 R/W (Password) tx power: 2,4,6,8,10,12,14,16,18,20 320 140 3 / 16 1 adaptative data rate 0-1 0 uint16 R/W (Password) Automatically adjust data rate, 0: disable, 1: enable 334 14E 3 / 16 2 cycle send data 900 uint32 R/W sec (data sending cycle) 338 152 3 / 16 1 alarm limt 44 uint16 R/W limit the number of events / day 340 154 3 / 16 2 sensor1: sampling_rate 120 uint32 R/W sec (frequency of data taken from sensor 1) 348 15C 3 / 16 2 prm1: a 1 float R/W Scale parameter "a" of X axis 350 15E 3 / 16 2 prm1: b 0 float R/W Scale parameter "b" of X axis 354 162 3 / 16 2 prm1: High Threshold 100000 float R/W High threshold value of X axis 356 164 3 / 16 2 prm1: High Hysteresis 10000 float R/W High hysteresis value of X axis 358 166 3 / 16 2 prm1: Low Threshold 0 float R/W Low threshold value of X axis 360 168 3 / 16 2 prm1: Low Hysteresis 10000 float R/W Low hysteresis value of X axis 362 16A 3 / 16 2 prm1: High Cut 100000 float R/W Upper limit value of X axis 364 16C 3 / 16 2 prm1: Low Cut 0 float R/W Lower limit value of X axis 366 16E 3 / 16 2 prm2: a 1 float R/W Scale parameter "a" of Y axis 368 170 3 / 16 2 prm2: b 0 float R/W Scale parameter "b" of Y axis 372 174 3 / 16 2 prm2: High Threshold 100000 float R/W High threshold value of Y axis 374 176 3 / 16 2 prm2: High Hysteresis 10000 float R/W High hysteresis value of Y axis 376 178 3 / 16 2 prm2: Low Threshold 0 float R/W Low threshold value of Y axis 378 17A 3 / 16 2 prm2: Low Hysteresis 10000 float R/W Low hysteresis value of Y axis 380 17C 3 / 16 2 prm2: High Cut 100000 float R/W Upper limit value of Y axis 382 17E 3 / 16 2 prm2: Low Cut 0 float R/W Lower limit value of Y axis 384 180 3 / 16 2 prm3: a 1 float Read/Write Scale parameter "a" of Z axis 386 182 3 / 16 2 prm3: b 0 float Read/Write Scale parameter "b" of Z axis 388 184 3 / 16 2 prm3: High Threshold 100000 float Read/Write High threshold value of Z axis 390 186 3 / 16 2 prm3: High Hysteresis 10000 float Read/Write High hysteresis value of Z axis 392 188 3 / 16 2 prm3: Low Threshold 0 float Read/Write Low threshold value of Z axis 394 18A 3 / 16 2 prm3: Low Hysteresis 10000 float Read/Write Low hysteresis value of Z axis 396 18C 3 / 16 2 prm3: High Cut 100000 float Read/Write Upper limit value of Z axis 398 18E 3 / 16 2 prm3: Low Cut 0 float Read/Write Lower limit value of Z axis 6. Installation 6.1 Example application 6.2 Installation location To maximize the distance of transmission, the ideal condition is Line-of-sight (LOS) between the LoRaWAN sensor and Gateway. In real life, there may be no LOS condition. However, the LoRaWAN sensor still communicates with Gateway, but the distance will be reduced significantly. ATTENTION:DO NOT install the LoRaWAN 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, cement…is acceptable. 6.3 Battery installation Steps for battery installation: Step 1: Using L hex key to unscrew M4 screws at the side of the housing and carefully pull out the top plastic housing in the vertical direction Step 2: Insert 02 x AA 1.5VDC battery, please take note the poles of the battery ATTENTION: REVERSED POLARITY OF BATTERIES IN 10 SECONDS CAN DAMAGE THE SENSOR CIRCUIT!!! Step 3: Insert the top plastic housing and locking by L hex key ATTENTION: When reinstalling the cover, pay attention to put the PCB edge into the middle slot of the box inside as shown below) 7. Troubleshooting No. Phenomena Reason Solutions 1 The BLUE LED does not blink when the battery is installed Insert the battery in the opposite direction Insert the battery in the correct way 2 The RED LED is always on Due to noise, the peripheral components (i2c, spi, uart, ..) of RF module cannot be initialized After 30s the node will automatically reset. If the noise causes the Watchdog not to initialize, remove the battery and wait for more than 10 seconds, then insert the battery again 3 The RED LED blinks continuously (10ms ON / 2s OFF) and the Node does not send RF. After more than 10 sending cycles, the Node will automatically reset Operating frequency in that country is prohibited Operating frequency in that country is limited to Data rate, Tx Power Reconfigure the allowed frequency of operation Reconfigure Data rate = DR5 / SF07, Tx Power 4 RED LED blinks continuously (10ms ON / 2s OFF) and Node sends RF continuously 3s / time but no data. After more than 10 sending cycles, the Node will automatically reset Node runs dummy sending mode => sent by Gateway to send Downlink packets when users clear Uplink and Downlink counter values on Network Server (build-in Gateway) when activated by ABP Configuration enabled by OTAA 5 The RED LED flashes 10ms ON / 10s OFF and the Node does not send RF Node activation by OTAA on Network server has not been successful Using Magnet-Key to force Node to send RF continuously for 3 seconds/time => when activating by OTAA successfully, the GREEN LED will blink after sending RF 6 The node sent RF successfully but the GREEN LED did not blink LED is broken Warranty to replace LED 7 The data packet taken from the Gateway has an incorrect value The data package is encrypted Get the decoded packet on the Application Server 8 The node sends RF and activates by ABP, on Gateway receives data but the Application server has no data The application server still stores the counter values of the previous Uplink and Downlink Delete the counter values of Uplink and Downlink on the Application server 9 The node does not send RF and the RF module is hot Insert the battery in the opposite direction Short circuit Warranty or replacement 10 The node does not send RF to Gateway according to the alarm, LED does not blink The alarm configuration is incorrect Running out of the number of alarms set for the day Check alarm configuration Check the configuration for the maximum number of alarms per day 11 The node does not send RF to Gateway when activated by the magnetic key, LED does not blink The magnetic sensor has malfunctioned Read the status of the magnetic sensor via Modbus (when powering or attaching the battery) to see if the magnetic sensor is working. 12 Node has blinked LED GREEN when sending RF but the Gateway or Application server cannot receive LoRa module on the Gateway is faulty The IP connection (4G / WiFi / ...) on the Gateway is faulty Check Gateway's LoRa status lights on Gateway Check 4G / WiFi status lights on Gateway 13 The value of the sensor is 0 and sensor_type = 0xFF Lost connection with the sensor Check sensor connection Replace the module sensor 14 RSSI is weak and often loses data The distance between Node and Gateway is far or there are many obstructions Connection to Antenna problem Install metal nodes or in metal cabinets Configure Data rate = DR0 / SF12 Check Antenna position Install Node in a well-ventilated location 8. Support contacts Manufacturer Daviteq Technologies IncNo.11 Street 2G, Nam Hung Vuong Res., An Lac Ward, Binh Tan Dist., Ho Chi Minh City, Vietnam.Tel: +84-28-6268.2523/4 (ext.122) Email: info@daviteq.com | www.daviteq.com Distributor in Australia and New Zealand Templogger Pty Ltd Tel: 1800 LOGGER Email: contact@templogger.net USER GUIDE FOR LORAWAN RADAR 26GHZ LENS LEVEL SENSOR WSLRW-RD26L THIS IS OBSOLETE MANUAL Please access https://www.iot.daviteq.com/wireless-sensors for updated manual WSLRW-RD26L-MN-EN-01 DEC-2020 This document is applied for the following products SKU WSLRW-RD26L HW Ver. 1.2 FW Ver. 1.0 Item Code WSLRW-RD26L-SL-8-01 LORAWAN 26GHZ RADAR LEVEL SENSOR WITH LENS FOR SOLID IN HIGH DUST ENVIRONMENT, SUS304 JIS10K 100A RF FLANGE, 0-30M CALIBRATED RANGE, IP67 ALUMINUM HOUSING, 860-870 MHZ FOR EU868, IN865, RU864 WSLRW-RD26L-SL-9-01 LORAWAN 26GHZ RADAR LEVEL SENSOR WITH LENS FOR SOLID IN HIGH DUST ENVIRONMENT, SUS304 JIS10K 100A RF FLANGE, 0-30M CALIBRATED RANGE, IP67 ALUMINUM HOUSING, 900-930 MHZ FOR KR920, AS923, AU915, US915 0. Configuration Check List STEP 1: Configure End Device (Using Modbus Configuration Cable) Setting value (Example) 1. Select region AS923, IN865, EU868,.. 2. End Device Operation OTAA or ABP OTAA Write AppEUI information from Application Server to Lorawan End Device; Write AppKey (created by user) information for Lorawan End Device and Application Server. ABP Write DevEUI information from Application Server to Lorawan end device; write Network Session Key and App Session Key (created by user) information to Lorawan end device (and Application Server). 3. Configure "cycle send data" 900 sec (Defaut) 4. Configure "sensor sampling_rate" 120 sec (Defaut) 5. Configure parameters of sensor (Refer to Check data configuration table) STEP 2:  Configure the operation of LoRaWAN Gateway (Ex: URSALINK Gateway) 1. Configure the information in the General tab Server address, Server port (For more information) 2. Configure the information in the Radio tab Select the Region Region (Other parameters to default) STEP 3:  Configure the operation of LoRaWAN Gateway on Network Server (Ex: URSALINK Gateway with Thethingsnetwork) 1. Gateway ID registration Gateway ID is the GatewayEUI information on the Gateway 2. Frequency Plan parameters configuration Asia 920-923MHz, Europe 868MHz,... 3. Router parameters configuration 4. Check the connection of the gateway to the network server The Gateway status LED lights up and displays the message "Status: conneted" on the Thethingsnetwork STEP 4:  Configure the operation of Application Server on Network Server 1. App ID registration 2. Handler parameters configuration STEP 5: Register Lorawan End Device on Application Server on Thethingsnetwork 1. ID Registration 2.Select operation mode OTAA or ABP OTAA Configure parameters DevEUI and AppKEY ABP Configure parameters Device Address, Network Session Key, App Session Key 1. Functions Change Log HW Ver. FW Ver. Release Date Functions Change 1.2 1.0.0 21-Nov-2020 The first version 2. Introduction WSLRW-RD26L is K-band radar level sensor with special lens for Solid or Liquid measurement. With special lens design, it will be not affected by coagulation/hanging/operating medium/sediment and dust. It can measure up to 70m range with small beam angle 8 degree. With Ultra-low Power design and smart firmware allow the sensor can last up to years with 12 x AA-type battery (depends on configuration). The sensor will transmit data in kilo-meters distance to LoRaWAN gateway, any brand on the market. 3. Specification SENSORS SPECIFICATION: Sensor technology 26 GHz Pulse radar with lens Measurement range 30, 70m Resolution 1.0 mm Accuracy +/- 5.0 mm Beam angle 8 degree Lens material Nylon/PEEK/PTFE/POM Process temperature -40 .. + 85oC standard, +120 oC optional Process pressure -1 .. + 4 barg Ambient working temperature -40 .. + 85 oC Ambient working humidity 0 .. 95% RH, non-condensing LoRaWAN SPECIFICATION: Data rate 250bps .. 5470bps Antenna Antenna 2.67 dbi Battery 12 x AA size 1.5VDC, battery not included RF Frequency and Power 860..930Mhz, +14 .. +20 dBm, configurable for zones: EU868, IN865, RU864, KR920, AS923, AU915, US915 Protocol LoRaWAN Data sending modes interval time, alarm occurred and manually triggering by magnetic key RF Module complies to ETSI EN 300 220, EN 303 204 (Europe) FCC CFR47 Part15 (US), ARIB STD-T108 (Japan) Vietnam Type Approval TBA Working temperature -40oC..+60oC (with AA L91 Energizer) Dimensions 220x220x450 (without antenna) Net-weight < 10 kgs Housing Aluminum + Polycarbonate plastic, IP67 4. Operation Principle 4.1 LoRaWAN protocol specifications 4.1.1 LoRaWAN Sensor protocol specifications LoRaWAN Protocol Version 1.0.3 Application Server Version 1.3.0.0 MAC Layer Version 4.4.2.0 Radio Standards: LoRa Alliance Certified LoRaWAN Zone: LoRa Alliance AS923, KR920, AU915, US915, EU868, IN865, RU864 Class A Join Active: OTAA / ABP Network Mode: Public Network / Private Network Tx Power: up to 20 dBm Frequency: 860 - 930Mhz Date rate: 250 bps - 5kbps Spreading factor: SF12 - SF7 Bandwidth: 125 kHz Unconfirmed-data message LoRaWAN application port for certification: 224 4.1.2 Data rate of LoRaWAN Sensor Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR2 980 SF10 125 AS923, AU915 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 980 SF10 125 US915 DR1 1760 SF9 125 DR2 3125 SF8 125 DR3 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 250 SF12 125 KR920, EU868, IN865, RU864 DR1 440 SF11 125 DR2 980 SF10 125 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 4.1.3 Tx power of LoRaWAN sensor Max EIRP (dBm) Max Tx Power (dBm) Region 16 16 AS923 14 14 KR920 30 20 AU915 30 20 US915 16 16 EU868 30 20 IN865 16 16 RU864 4.2 The principle of operation of the LoRaWAN sensor When starting the power supply, the LoRaWAN sensor has 60 seconds to allow configuration to operate via the Configuration Cable with the Modbus RTU protocol. After 60 seconds, the first packet will be sent, then the LoRaWAN sensor will send the next packets in the following cases: Case 1: When it reaches the frequency of taking data, the LoRaWAN sensor will wake up to measure and calculate. Then: If the measured value exceeds the High or Low setting thresholds, the packet will be sent to the Gateway and then asleep; If NOT then sleep without sending data. NOTE: Once sending the data to Gateway by this alarm event, the timer of sending time interval will be reset; Case 2: When the sending time interval is reached, the LoRaWAN sensor wakes up to measure and calculate and send data to Gateway immediately, regardless of value. Case 3: By using the magnet key, the LoRaWAN sensor can be triggered to send data to Gateway immediately. NOTE: The time between sending data for Class A is at least 3 seconds 4.3 Principle of operation LoRaWAN Network The LoRaWAN Gateway function is Packet Forwarder so: Between Gateway and End Device: Gateway receives data packets from End Device via RF connection, so it is recommended to configure Radio parameters (Note: the packet that Gateway receives is encrypted) Between Gateway and Network Server: Gateway forwards data packets to the Network server via an IP connection, so it is recommended to configure Network parameters such as Server Address, Server Uplink Port, Server Downlink Port,... LoRaWAN Network is secured as follows: Network section key (NwkSKey) to ensure the security of communications on the Network The application session key (AppSKey) to ensure data security between End Device and Application Server Special keys of the device such as DevEUI, AppEUI, Gateway EUI, Device Address. Therefore, the data packet that the Gateway receives is encrypted and decrypted on the Application server. To End Device connect to the Network server, you need to register in the following two ways: Activation with OTAA (Over-the-Air activation): is the process of joining the Network automatically. Previously, both End Device and Application Server installed the same DevEUI code, AppEUI, and AppKey. During activation, AppKey will generate 2 security keys for End Device and Network, which are: The network session key (NwkSKey): is the key to secure communication commands on the MAC layer between the End Device and the Network server. The application session key (AppSKey): is the key to secure data packets between the End Device and Application server. ATTENTIONS:* OTAA mode must be successfully activated in order for the End Device to send data packets to the Network through the Gateway;* OTAA mode only need to activate once, if the device is reset or battery replacement, it will activate OTAA again;* When the End Device is connected to the Network server, whether the Gateway is reset or the power is restarted, it will not need to activate OTAA. Activation by ABP (Activation by Personalization): is the process of joining the Network manually. Device Address, Network session key (NwkSKey), and Application session key (AppSKey) codes must be stored inside the End Device and Application server, so when the End Device sends data packets to the network server, it will also send the security codes to activate. 4.4 Configure the LoRaWAN Network 4.4.1 Configure End Device operation according to OTAA Configuration parameters for the End Device to be activated by OTAA as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode OTAA Device activation type on Network Server DevEUI 34 35 31 31 4B 37 75 12 Device ID's unique ID number => Set this ID number for the Application server AppEUI 70 B3 D5 7E D0 02 D5 0B Application server's unique ID number (random or user-generated)=> Set this ID number for End Device AppKey 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C Key Number for generating 2 NwkSKey and AppSKey security keys created by the user (factory-created by default)=> Used to install for both the Device and Application Server End ATTENTIONS:* The AppEUI number from Application Server => then installed for the End Device. AppEUI is randomly generated by the Application server or by the user;* The number of AppKeys during OTAA activation will generate two security keys, Lora NwkSKey and AppSKey, which are used for both End Device and Network. 4.4.2 Configure End Device operation according to ABP Configuration parameters for the End Device to be activated by ABP as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode ABP Device activation type on Network Server Device Address 12 34 56 78 End Device Address created by the Application server=> Set Device Address for End Device NwkSKey (Network session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C NwkSKey number created by the user to install and use for both End Device and Application Server AppSKey (Application session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C AppSKey number generated by the user to install for both End Device and Application Server 4.4.3 Configure Gateway operations 4.4.3.1 Configure the Gateway to receive data packets from the End Device. Radio settings need to be set as:* Region code: AS923, KR920, AU915, US915, EU868, IN865, RU864* Center Frequency, Channels, Bandwidth (recommends using the default configuration created by the system) Let's take an example to configure the Gateway operation of URSALINK (Model: UG85-L00E-915) 4.4.3.2 Configure the Gateway to communicate with the Public Network Server Let's take an example of configuring Gateway UG85 to connect with "thethingsnetwork.org" in Asia: Currently, thethingsnetwork only supports the connection protocol with Gateway is Semtech UDP Packet Forwarder. https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Parameter settings Setting value (example) Description Gateway EUI 24e124fffef038fd Gateway's unique ID number=> Set this ID number for Application server Server Address router.as1.thethings.network Semtech server address: https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Router regional Asia: router.as1.thethings.network Router regional India: ttn.thingsconnected.net Ursalink server address: localhost Server Uplink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Server Downlink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Network mode Public LoRaWAN 4.4.4 Register the Application server on the Public Network "thethingsnetwork.org" 4.4.4.1 Register the Gateway on Public Network "thethingsnetwork.org" as shown below: The current network only supports the Gateway connection protocol, "Semtech UDP protocol" is Semtech UDP Packet Forwarder. Then power the Gateway and observe the message "Status: connected" => Registration of the Gateway on the Application successfully. 4.4.4.2 Register Application on Public Network "thethingsnetwork.org" as shown below: 4.4.4.3 Register End Device on Application: 4.5 LED meaning RED LED: Fixed ON: due to noise caused peripheral components (i2c, spi, uart, timer, rtc, wdt, ...) do not initialize. Flashing 10ms ON / 10s OFF: Activation by OTAA on the Network server failed. Flashing 10ms ON / 2s OFF:  Sending a data packet to Gateway failed. GREEN LED: Flashing 100ms ON / OFF when sending a data packet to Gateway. BLUE LED: Flashing 1s ON / 1s OFF for the first 60 seconds when booting (insert batteries or connected external sources), after 60 seconds OFF. ON during the LoRaWAN sensor receives data packets from the Network server and OFF when received. 4.6 Process of measurement When the LoRa sensor wakes up, it will supply power to the internal or external sensor so that the sensor can start measuring. After measuring successfully it will turn off the power to the sensor for energy saving. The measured value is the raw value of the sensor. The measured value can be scaled according to the following formula: Y = aX + b X: the raw value from the sensor Y: the calculated value will be sent to LoRaWAN Gateway in the payload data. a: constant (default value is 1) b: constant (default value is 0) So, if there is no user setting for a and b ==> Y = X The Y value will be compared with Lo and Hi threshold. Please refer below the graph of alarm processing. 4.7 Payload Data The following is the format of payload data that will be sent to the LoRaWAN Gateway. Sensor type (1 byte) Status (1 byte) 1st - Parameter (4 bytes) 2nd - Parameter (4 bytes) Meaning of Data in the Payload Data Size (byte) Bit Format Meaning Sensor type 1 all Uint8 Sensor type = 0xFF means no sensor Status: battery level 1 Bit 7 and 6 Uint8 Battery capacity in 04 levels 11: battery level 4 (99%) 10: battery level 3 (60%) 01: battery level 2 (30%) 00: battery level 1 (10%) Status: error Bit 5 and 4 Node status 01: error 00: no error Status: alarm 1 Bit 3 and 2 Alarm status of 1st - Parameter (Y1 value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm Status: alarm 2 Bit 1 and 0 Alarm status of 2nd - Parameter (Y2 value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm 1st - Parameter 4 all Float Y1 value: Level (x 0.1%) 2nd - Parameter 4 all Float Y2 value: Distance(mm) 5. Configuration Using the configuration cable to connect to the sensor as below picture. Serial port configuration on the computer:* COMPort, Baudrate: 9600, Parity: None, Stop bit: 1, Data bit: 8* Modbus RTU: Reading data by Function 3 / Writing data by Function 16. 5.1 Step to configure NOTE: The Modbus configuration can only be performed in the first 60s after power up the LoRaWAN sensor. After 60s, if user can not finish the configuration process, user need to reset the power of LoRaWAN sensor again, by removing battery in at least 15s. Step 1: Install the Modbus Configurator Software in the link below https://filerun.daviteq.com/wl/?id=qK0PGNbY1g1fuxTqbFW9SXtEvCw7bpc6 How to use the Modbus configuration software Step 2: Plug the configuration cable to computer via USB port and install the driver; Step 3: Open the housing; Step 4: Plug the connector to the configuration port; Step 5:  Import the configuration file by importing the csv file: Go to MENU: FILE / Import New / => select the file with name CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0.csv (in the link below). Then click Connect; CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0 To write new value to the device:First, you need to write the password in "password for setting", after reading the value to check ok, you can write the new value AppEUI, AppKey, ...You only have 60 seconds after plugging the configuration cable or the power supply into the device for configuration. 5.2 Check Data Here is the table of Data will be read by Modbus tool Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 0 0 3 5 device info WSLRW-I2C string Read Wireless Sensor LoRaWAN - I2C 5 5 3 4 firmware version 1.00ddmm string Read ddmm = day / month 9 9 3 2 hardware version 1.10 string Read 11 B 3 4 lorawan protocol version 01.00.03 string Read lorawan v1.0.3 15 F 3 6 application version 01.03.00.00 string Read application server v1.3.0.0 21 15 3 6 mac layer version 04.04.02.00 string Read mac layer v4.4.2.0 27 1B 3 4 deviceEUI hex Read End Device's EUI number, used to register the product on the Network Server by OTAA 31 1F 3 4 lora appEUI hex Read Application server's EUI number is used to register the product on the Network Server by OTAA 35 23 3 8 lora appKey hex Read The number of keys used to create two security keys of the End Device, used to register the product on the Network Server by OTAA 43 2B 3 8 lora nwkSkey hex Read key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 51 33 3 8 lora appSkey hex Read End Device data encryption key number, used to register the product on the Network Server by ABP 59 3B 3 2 device address 0 uint32 Read End Device address created by Application server, used to register the product on the Network server by ABP 61 3D 3 2 network ID 0 uint32 Read Network server ID number, used to register the product on the Network server by ABP 63 3F 3 2 join mode OTAA string Read OTAA: Over-the-Air activation, ABP: Activation by Personalization 65 41 3 4 network mode PUBLIC string Read PUBLIC, PRIVATE 69 45 3 3 region code AS923 string Read 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 72 48 3 4 data rate DR2:980 string Read DR0:250, DR1:440, DR2:980, DR3:1760, DR4:3125, DR5:5470 76 4C 3 3 bandwidth BW125 string Read BW125, BW250, BW500 79 4F 3 2 spread factor SF10 string Read SF12, SF11, SF10, SF9, SF8, SF7 81 51 3 4 activation of ADR ADR OFF string Read ADR ON, ADR OFF 85 55 3 1 class A string Read 103 67 3 1 sensor type 1-255 uint16 Read 1-254: sensor type, 255: no sensor 104 68 3 1 battery level 0-3 uint16 Read 4 levels of battery capacity status 105 69 3 1 error status 0-1 uint16 Read Error code of sensor, 0: no error, 1: error 106 6A 3 1 prm1 alarm status 0-2 uint16 Read Alarm status of parameters 1, 0: none, 1: Low, 2: High 107 6B 3 1 prm2 alarm status 0-2 uint16 Read Alarm status of parameter 2 108 6C 3 2 prm1 value float Read Value of parameter 1 110 6E 3 2 prm2 value float Read Value of parameter 2 112 70 3 1 battery % 10%, 30%, 60%, 99% uint16 Read % Value of battery capacity 113 71 3 2 battery voltage 0-3.67 vdc float Read Value of battery voltage 115 73 3 2 mcu temperature oC float Read Temperature value of RF module 117 75 3 1 mcu vref 0-3.67 vdc uint16 Read Vref value of RF module 118 76 3 1 button1 status 0-1 uint16 Read Button state, 0: No button pressed, 1: Button pressed 119 77 3 1 button2 status 0-1 uint16 Read Button status, 0: No magnetic sensor detected, 1: Magnetic sensor detected Here is the table for Configuration: Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 256 100 3 / 16 1 modbus address 1-247 1 uint16 R/W Modbus address of the device 257 101 3 / 16 1 modbus baudrate 0-1 0 uint16 R/W 0: 9600, 1: 19200 258 102 3 / 16 1 modbus parity 0-2 0 uint16 R/W 0: none, 1: odd, 2: even 259 103 3 / 16 9 serial number string R/W (Password) 268 10C 3 / 16 2 password for setting uint32 R/W (Password) password 190577 270 10E 3 / 16 4 lora appEUI hex R/W (Password) Application server's EUI number, used to register the product on the Network Server by OTAA 274 112 3 / 16 8 lora appKey hex R/W (Password) The number of keys used to create two security keys of the End Device, used to register the product on the Network server by OTAA 282 11A 3 / 16 8 lora nwkSkey hex R/W (Password) key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 290 122 3 / 16 8 lora appSkey hex R/W (Password) End Device data encryption key number, used to register the product on the Network Server by ABP 298 12A 3 / 16 2 device address uint32 R/W (Password) End Device address created by Application server, used to register the product on the Network server by ABP 300 12C 3 / 16 2 network ID uint32 R/W (Password) Network server ID number, used to register the product on the Network server by ABP 302 12E 3 / 16 1 activation mode 0-1 1 uint16 R/W (Password) 1: OTAA (Over-the-Air Activation), 0: ABP (Activation by Personalization) 304 130 3 / 16 1 application port 1-255 1 uint16 R/W (Password) Port 224 is reserved for certification 317 13D 3 / 16 1 region 1-7 1 uint16 Read/Write(Password) 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 318 13E 3 / 16 1 data rate 7 uint16 R/W (Password) 0: 250 bps, 1: 440 bps, 2: 980 bps, 3: 1760 bps, 4: 3125 bps, 5: 5470 bps 319 13F 3 / 16 1 tx power 2-20 16 uint16 R/W (Password) tx power: 2,4,6,8,10,12,14,16,18,20 320 140 3 / 16 1 adaptative data rate 0-1 0 uint16 R/W (Password) Automatically adjust data rate, 0: disable, 1: enable 334 14E 3 / 16 2 cycle send data 900 uint32 R/W sec (data sending cycle) 338 152 3 / 16 1 alarm limt 44 uint16 R/W limit the number of events / day 340 154 3 / 16 2 sensor1: sampling_rate 120 uint32 R/W sec (frequency of data taken from sensor 1) 348 15C 3 / 16 2 prm1: a 1 float R/W Scale parameter "a" of prm1 350 15E 3 / 16 2 prm1: b 0 float R/W Scale parameter "b" of prm1 354 162 3 / 16 2 prm1: High Threshold 100000 float R/W High threshold value of prm1 356 164 3 / 16 2 prm1: High Hysteresis 10000 float R/W High hysteresis value of prm1 358 166 3 / 16 2 prm1: Low Threshold 0 float R/W Low threshold value of prm1 360 168 3 / 16 2 prm1: Low Hysteresis 10000 float R/W Low hysteresis value of prm1 362 16A 3 / 16 2 prm1: High Cut 100000 float R/W Upper limit value of prm1 364 16C 3 / 16 2 prm1: Low Cut 0 float R/W Lower limit value of prm1 366 16E 3 / 16 2 prm2: a 1 float R/W Scale parameter "a" of prm2 368 170 3 / 16 2 prm2: b 0 float R/W Scale parameter "b" of prm2 372 174 3 / 16 2 prm2: High Threshold 100000 float R/W High threshold value of prm2 374 176 3 / 16 2 prm2: High Hysteresis 10000 float R/W High hysteresis value of prm2 376 178 3 / 16 2 prm2: Low Threshold 0 float R/W Low threshold value of prm2 378 17A 3 / 16 2 prm2: Low Hysteresis 10000 float R/W Low hysteresis value of prm2 380 17C 3 / 16 2 prm2: High Cut 100000 float R/W Upper limit value of prm2 382 17E 3 / 16 2 prm2: Low Cut 0 float R/W Lower limit value of prm2 6. Installation 6.1 Dimensions 6.2 Example application 6.3 Installation location 6.3.1 LoRaWAN Node To maximize the distance of transmission, the ideal condition is Line-of-sight (LOS) between the LoRaWAN sensor and Gateway. In real life, there may be no LOS condition. However, the LoRaWAN sensor still communicates with Gateway, but the distance will be reduced significantly. ATTENTION:DO NOT install the LoRaWAN 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, cement…is acceptable. 6.3.2 Radar Sensor The Radar Level Transmitter antenna emits narrower micro wave pulses which will be transmitted via the antenna. The micro wave will be reflected back after touching the surface of a medium, then antenna system will receive it and transmit it into the electrical circuit, which will be automatically turned into the level signals. Note: When using the radar level transmitter, must keep the highest level of medium out of the dead zone (see area D shown in the drawing) A: Setting measuring range B: Low level adjustment C: High level adjustment D: Dead zone Measuring reference: the bottom surface of threads or the sealing surface of a flange. The minimum distance between the symmetrical central line of the transmitter and the inner tank wall should be at least 300mm. 6.4 Battery installation Steps for battery installation: Step 1: Using L hex key to unscrew hex screws at the top of the housing and carefully pull out the top housing in the vertical direction Step 2: Insert 12 x AA 1.5VDC battery, please take note the poles of the battery ATTENTION: REVERSED POLARITY OF BATTERIES IN 10 SECONDS CAN DAMAGE THE SENSOR CIRCUIT!!! Step 3: Insert the top housing and locking by L hex key 7. Troubleshooting No. Phenomena Reason Solutions 1 The BLUE LED does not blink when the battery is installed Insert the battery in the opposite direction Insert the battery in the correct way 2 The RED LED is always on Due to noise, the peripheral components (i2c, spi, uart, ..) of RF module cannot be initialized After 30s the node will automatically reset. If the noise causes the Watchdog not to initialize, remove the battery and wait for more than 10 seconds, then insert the battery again 3 The RED LED blinks continuously (10ms ON / 2s OFF) and the Node does not send RF. After more than 10 sending cycles, the Node will automatically reset Operating frequency in that country is prohibited Operating frequency in that country is limited to Data rate, Tx Power Reconfigure the allowed frequency of operation Reconfigure Data rate = DR5 / SF07, Tx Power 4 RED LED blinks continuously (10ms ON / 2s OFF) and Node sends RF continuously 3s / time but no data. After more than 10 sending cycles, the Node will automatically reset Node runs dummy sending mode => sent by Gateway to send Downlink packets when users clear Uplink and Downlink counter values on Network Server (build-in Gateway) when activated by ABP Configuration enabled by OTAA 5 The RED LED flashes 10ms ON / 10s OFF and the Node does not send RF Node activation by OTAA on Network server has not been successful Using Magnet-Key to force Node to send RF continuously for 3 seconds/time => when activating by OTAA successfully, the GREEN LED will blink after sending RF 6 The node sent RF successfully but the GREEN LED did not blink LED is broken Warranty to replace LED 7 The data packet taken from the Gateway has an incorrect value The data package is encrypted Get the decoded packet on the Application Server 8 The node sends RF and activates by ABP, on Gateway receives data but the Application server has no data The application server still stores the counter values of the previous Uplink and Downlink Delete the counter values of Uplink and Downlink on the Application server 9 The node does not send RF and the RF module is hot Insert the battery in the opposite direction Short circuit Warranty or replacement 10 The node does not send RF to Gateway according to the alarm, LED does not blink The alarm configuration is incorrect Running out of the number of alarms set for the day Check alarm configuration Check the configuration for the maximum number of alarms per day 11 The node does not send RF to Gateway when activated by the magnetic key, LED does not blink The magnetic sensor has malfunctioned Read the status of the magnetic sensor via Modbus (when powering or attaching the battery) to see if the magnetic sensor is working. 12 Node has blinked LED GREEN when sending RF but the Gateway or Application server cannot receive LoRa module on the Gateway is faulty The IP connection (4G / WiFi / ...) on the Gateway is faulty Check Gateway's LoRa status lights on Gateway Check 4G / WiFi status lights on Gateway 13 The value of the sensor is 0 and sensor_type = 0xFF Lost connection with the sensor Check sensor connection Replace the module sensor 14 RSSI is weak and often loses data The distance between Node and Gateway is far or there are many obstructions Connection to Antenna problem Install metal nodes or in metal cabinets Configure Data rate = DR0 / SF12 Check Antenna position Install Node in a well-ventilated location 8. Support contacts Manufacturer Daviteq Technologies IncNo.11 Street 2G, Nam Hung Vuong Res., An Lac Ward, Binh Tan Dist., Ho Chi Minh City, Vietnam.Tel: +84-28-6268.2523/4 (ext.122) Email: info@daviteq.com | www.daviteq.com Distributor in Australia and New Zealand Templogger Pty Ltd Tel: 1800 LOGGER Email: contact@templogger.net USER GUIDE FOR LORAWAN PT100 TEMPERATURE SENSOR WSLRW-PT100 THIS IS OBSOLETE MANUAL Please access https://www.iot.daviteq.com/wireless-sensors for updated manual WSLRW-PT100-MN-EN-01 DEC-2020 This document is applied for the following products SKU WSLRW-DEC HW Ver. 1.1 FW Ver. 1.2 Item Code WSLRW-PT100-9-01 Wireless LoRaWAN PT100 Temperature Sensor, Internal antenna, Type AA battery 1.5VDC, IP67, 900-930 Mhz for KR920, AS923, AU915, US915 WSLRW-PT100-8-01 Wireless LoRaWAN PT100 Temperature Sensor, Internal antenna, Type AA battery 1.5VDC, IP67, 860-870 Mhz for EU868, IN865, RU864 0. Configuration Check List STEP 1: Configure End Device (Using Modbus Configuration Cable) Setting value (Example) 1. Select region AS923, IN865, EU868,.. (refer to register address 317) 2. End Device Operation OTAA or ABP OTAA Write AppEUI information from Application Server to Lorawan End Device; Write AppKey (created by user) information for Lorawan End Device and Application Server. ABP Write DevEUI information from Application Server to Lorawan end device; write Network Session Key and App Session Key (created by user) information to Lorawan end device (and Application Server). 3. Configure "cycle send data" 900 sec (Defaut) 4. Configure "sensor sampling_rate" 120 sec (Defaut) 5. Configure parameters of sensor (Refer to configuration table) STEP 2:  Configure the operation of LoRaWAN Gateway (Ex: URSALINK Gateway) 1. Configure the information in the General tab Server address, Server port (For more information) 2. Configure the information in the Radio tab Select the Region Region (Other parameters to default) STEP 3:  Configure the operation of LoRaWAN Gateway on Network Server (Ex: URSALINK Gateway with Thethingsnetwork) 1. Gateway ID registration Gateway ID is the GatewayEUI information on the Gateway 2. Frequency Plan parameters configuration Asia 920-923MHz, Europe 868MHz,... 3. Router parameters configuration 4. Check the connection of the gateway to the network server The Gateway status LED lights up and displays the message "Status: conneted" on the Thethingsnetwork STEP 4:  Configure the operation of Application Server on Network Server 1. App ID registration 2. Handler parameters configuration STEP 5: Register Lorawan End Device on Application Server on Thethingsnetwork 1. ID Registration 2.Select operation mode OTAA or ABP OTAA Configure parameters DevEUI and AppKEY ABP Configure parameters Device Address, Network Session Key, App Session Key 1. Functions Change Log HW Ver. FW Ver. Release Date Functions Change 1.1 1.0.0 21-July-2020 1.1 1.1.x 05-Oct-2020 Data frame improvements Fix the Watchdog bug 1.1 1.2.0 12-Oct-2020 The minimum frequency of sending data packets to Gateway is 15 seconds When connecting to network server with OTAA failure, it will not read sensor value 2. Introduction WSLRW-PT100 is LoRaWAN wireless sensor with modular design connected to PT100 temperature sensor, based on 10-year experience in design and manufacturing Industrial sensor of Daviteq Company. It has been factory pre-calibrated for high accuracy and quick set-up. The Ultra-Low Power Power design and smart firmware allow the sensor to last up to 10 years with 02 x AA battery (depending on configuration). The sensor will transmit data over kilo-meters away to the LoRaWAN gateway, any brand on the market. Some typical applications are temperature monitoring for factories, agriculture, boilers, ... 3. Specification Input PT100 Temperature Sensor Accuracy 0.05% Sensor port connector PG9 Connector Data rate 250bps .. 5470bps Antenna Internal Antenna 2.67 dbi Battery 02 x AA size 1.5, battery not included RF Frequency and Power 860..930Mhz, +14 .. +20 dBm, configurable for zones: EU868, IN865, RU864, KR920, AS923, AU915, US915 Protocol LoRaWAN, class A Data sending modes Interval time and when alarm occurred RF Module complies to ETSI EN 300 220, EN 303 204 (Europe) FCC CFR47 Part15 (US), ARIB STD-T108 (Japan) Vietnam Type Approval Working temperature -15oC..+60oC (using L91 Energizer battery) Dimensions H180xW50xD40 Net-weight 250 grams Housing Polycarbonate & POM plastic, IP67 4. Operation Principle 4.1 LoRaWAN protocol specifications 4.1.1 LoRaWAN Sensor protocol specifications LoRaWAN Protocol Version 1.0.3 Application Server Version 1.3.0.0 MAC Layer Version 4.4.2.0 Radio Standards: LoRa Alliance Certified LoRaWAN Zone: LoRa Alliance AS923, KR920, AU915, US915, EU868, IN865, RU864 Class A Join Active: OTAA / ABP Network Mode: Public Network / Private Network Tx Power: upto 20 dBm Frequency 860 - 930Mhz Date rate 250 bps - 5kbps Spreading factor SF12 - SF7 Bandwidth 125 kHz Unconfirmed-data message LoRaWAN application port for certification: 224 4.1.2 Data rate of LoRaWAN Sensor Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR2 980 SF10 125 AS923, AU915 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 980 SF10 125 US915 DR1 1760 SF9 125 DR2 3125 SF8 125 DR3 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 250 SF12 125 KR920, EU868, IN865, RU864 DR1 440 SF11 125 DR2 980 SF10 125 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 4.1.3 Tx power of LoRaWAN sensor Max EIRP (dBm) Max Tx Power (dBm) Region 16 16 AS923 14 14 KR920 30 20 AU915 30 20 US915 16 16 EU868 30 20 IN865 16 16 RU864 4.2 The principle of operation of the LoRaWAN sensor When starting the power supply, the LoRaWAN sensor has 60 seconds to allow configuration to operate via the Configuration Cable with the Modbus RTU protocol. After 60 seconds, the first packet will be sent, then the LoRaWAN sensor will send the next packets in the following cases: Case 1: When it reaches the frequency of taking data, the LoRaWAN sensor will wake up to measure and calculate. Then: If the measured value exceeds the High or Low setting thresholds, the packet will be sent to the Gateway and then asleep; If NOT then sleep without sending data. NOTE: Once sending the data to Gateway by this alarm event, the timer of sending time interval will be reset; Case 2: When the sending time interval is reached, the LoRaWAN sensor wakes up to measure and calculate and send data to Gateway immediately, regardless of value. Case 3: By using the magnet key, the LoRaWAN sensor can be triggered to send data to Gateway immediately. NOTE: The time between sending data for Class A is at least 3 seconds 4.3 Principle of operation LoRaWAN Network The LoRaWAN Gateway function is Packet Forwarder so: Between Gateway and End Device: Gateway receives data packets from End Device via RF connection, so it is recommended to configure Radio parameters (Note: the packet that Gateway receives is encrypted) Between Gateway and Network Server: Gateway forwards data packets to the Network server via an IP connection, so it is recommended to configure Network parameters such as Server Address, Server Uplink Port, Server Downlink Port, .. LoRaWAN Network is secured as follows: Network section key (NwkSKey) to ensure the security of communications on the Network Application session key (AppSKey) to ensure data security between End Device and Application Server Special keys of the device such as DevEUI, AppEUI, Gateway EUI, Device Address. Therefore, the data packet that the Gateway receives is encrypted and decrypted on the Application server. To End Device connect to the Network server, you need to register in the following two ways: Activation with OTAA (Over-the-Air activation): is the process of joining the Network automatically. Previously, both End Device and Application Server installed the same DevEUI code, AppEUI and AppKey. During activation, AppKey will generate 2 security keys for End Device and Network, which are: Network session key (NwkSKey): is the key to secure communication commands on MAC layer between End Device and Network server. Application session key (AppSKey): is the key to secure data packets between End Device and Application server. ATTENTIONS:* OTAA mode must be successfully activated in order for the End Device to send data packets to the Network through the Gateway;* OTAA mode only need to activate once, if the device is reset or battery replacement, it will activate OTAA again;* When the End Device is connected to the Network server, whether the Gateway is reset or the power is restarted, it will not need to activate OTAA. Activation by ABP (Activation by Personalization): is the process of joining Network manually. Device Address, Network session key (NwkSKey) and Application session key (AppSKey) codes must be stored inside the End Device and Application server, so when the End Device sends data packets to the Network server, it will also send the security codes to activated. 4.4 Configure the LoRaWAN Network 4.4.1 Configure End Device operation according to OTAA Configuration parameters for the End Device to be activated by OTAA as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode OTAA Device activation type on Network Server DevEUI 34 35 31 31 4B 37 75 12 Device ID's unique ID number => Set this ID number for the Application server AppEUI 70 B3 D5 7E D0 02 D5 0B Application server's unique ID number (random or user generated)=> Set this ID number for End Device AppKey 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C Key Number for generating 2 NwkSKey and AppSKey security keys created by the user (factory-created by default)=> Used to install for both the Device and Application Server End ATTENTIONS:* The AppEUI number from Application Server => then installed for the End Device. AppEUI is randomly generated by the Application server or by the user;* The number of AppKeys during OTAA activation will generate two security keys, Lora NwkSKey and AppSKey, which are used for both End Device and Network. 4.4.2 Configure End Device operation according to ABP Configuration parameters for the End Device to be activated by ABP as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode ABP Device activation type on Network Server Device Address 12 34 56 78 End Device Address created by Application server=> Set Device Address for End Device NwkSKey (Network session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C NwkSKey number created by the user to install and use for both End Device and Application Server AppSKey (Application session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C AppSKey number generated by the user to install for both End Device and Application Server 4.4.3 Configure Gateway operations 4.4.3.1 Configure the Gateway to receive data packets from the End Device. Radio settings need to be set as:* Region code: AS923, KR920, AU915, US915, EU868, IN865, RU864* Center Frequency, Channels, Bandwidth (recommends using the default configuration created by the system) Let's take an example to configure the Gateway operation of URSALINK (Model: UG85-L00E-915) 4.4.3.2 Configure the Gateway to communicate with the Public Network Server Let's take an example of configuring Gateway UG85 to connect with "thethingsnetwork.org" in Asia: Currently thethingsnetwork only supports the connection protocol with Gateway is Semtech UDP Packet Forwarder. https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Parameter settings Setting value (example) Description Gateway EUI 24e124fffef038fd Gateway's unique ID number=> Set this ID number for Application server Server Address router.as1.thethings.network Semtech server address: https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Router regional asia: router.as1.thethings.network Router regional india: ttn.thingsconnected.net Ursalink server address: localhost Server Uplink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Server Downlink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Network mode Public LoRaWAN 4.4.4 Register the Application server on the Public Network "thethingsnetwork.org" 4.4.4.1 Register the Gateway on Public Network "thethingsnetwork.org" as shown below: The current network only supports the Gateway connection protocol, "Semtech UDP protocol" is Semtech UDP Packet Forwarder. Then power the Gateway and observe the message "Status: connected" => Registration of the Gateway on the Application successfully. 4.4.4.2 Register Application on Public Network "thethingsnetwork.org" as shown below: 4.4.4.3 Register End Device on Application: 4.5 LED meaning RED LED: Fixed ON: due to noise caused peripheral components (i2c, spi, uart, timer, rtc, wdt, ...) do not initialize. Flashing 10ms ON / 10s OFF: Activation by OTAA on the Network server failed. Flashing 10ms ON / 2s OFF:  Sending data packet to Gateway failed. GREEN LED: Flashing 100ms ON / OFF when sending data packet to Gateway. BLUE LED: Flashing 1s ON / 1s OFF for the first 60 seconds when booting (insert batteries or connected external sources), after 60 seconds OFF. ON during the LoRaWAN sensor receives data packets from the Network server and OFF when received. 4.6 Process of measurement When the LoRa sensor wakes up, it will supply power to the external sensor module so that the module can start measuring. After measuring it will turn off the power to the module. The measured value is the raw value of the sensor module, which can be ambient temperature, ambient humidity, etc. The measurement value can be scaled according to the following formula: Y = aX + b X: the raw value from module sensor Y: the calculated value will be sent to Sigfox base station in the payload data. a: constant (default value is 1) b: constant (default value is 0) 4.7 Payload Data The folllowing is the format of payload data will be sent to Sigfox server. Length is 6 bytes, it is future-proof for expansion to 12 bytes. Sensor type (1 byte) Status (1 byte) 1st - Parameter (4 bytes) 2nd - Parameter (4 bytes) Meaning of Data in the Payload Data Size (byte) Bit Format Meaning Sensor type 1 all Uint8 Sensor type = 0x15 means LoRaWAN Node with PT100Sensor type = 0xFF means no sensor Status: battery level 1 Bit 7 and 6 Uint8 Battery capacity in 04 levels 11: battery level 4 (99%) 10: battery level 3 (60%) 01: battery level 2 (30%) 00: battery level 1 (10%) Status: error Bit 5 and 4 Node status 01: error 00: no error Status: alarm 1 Bit 3 and 2 Alarm status of 1st - Parameter (Y1 value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm Status: alarm 2 Bit 1 and 0 Alarm status of 2nd - Parameter (Y2 value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm 1st - Parameter 4 all Float Y1 value: temperature value (°C).Range: -200°C…+750°C. 2nd - Parameter 4 all Float Y2 value: resistance value (ohm).Range: 18…360 Ohm. 5. Configuration Using the configuration cable to connect to the sensor as below picture. Serial port configuration on the computer:* COMPort, Baudrate: 9600, Parity: None, Stop bit: 1, Data bit: 8* Modbus RTU: Reading data by Function 3 / Writing data by Function 16. 5.1 Step to configure NOTE: The Modbus configuration can only be performed in the first 60s after power up the LoRaWAN sensor. After 60s, if user can not finish the configuration process, user need to reset the power of LoRaWAN sensor again, by removing battery in at least 15s. Step 1: Install the Modbus Configurator Software in the link below https://filerun.daviteq.com/wl/?id=qK0PGNbY1g1fuxTqbFW9SXtEvCw7bpc6 How to use the Modbus configuration software Step 2: Plug the configuration cable to computer via usb port and install the driver; Step 3: Open the plastic housing with L hex key to unscrew M4 screws at the side of housing Step 4: Plug the connector to the configuration port; Step 5:  Import the configuration file by importing the csv file: Go to MENU: FILE / Import New / => select the file with name CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0.csv (in the link below). Then click Connect; CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0 To write new value to the device:First, you need to write the password in "password for setting", after reading the value to check ok, you can write the new value AppEUI, AppKey, ...You only have 60 seconds after plugging the configuration cable or the power supply into the device for configuration. 5.2 Register table Here is the table of Data will be read by Modbus tool Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 0 0 3 5 device info WSLRW-I2C string Read Wireless Sensor LoRaWAN - I2C 5 5 3 4 firmware version 1.00ddmm string Read ddmm = day / month 9 9 3 2 hardware version 1.10 string Read 11 B 3 4 lorawan protocol version 01.00.03 string Read lorawan v1.0.3 15 F 3 6 application version 01.03.00.00 string Read application server v1.3.0.0 21 15 3 6 mac layer version 04.04.02.00 string Read mac layer v4.4.2.0 27 1B 3 4 deviceEUI hex Read End Device's EUI number, used to register the product on the Network Server by OTAA 31 1F 3 4 lora appEUI hex Read Application server's EUI number is used to register the product on the Network Server by OTAA 35 23 3 8 lora appKey hex Read The number of keys used to create two security keys of the End Device, used to register the product on the Network Server by OTAA 43 2B 3 8 lora nwkSkey hex Read key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 51 33 3 8 lora appSkey hex Read End Device data encryption key number, used to register the product on the Network Server by ABP 59 3B 3 2 device address 0 uint32 Read End Device address created by Application server, used to register the product on the Network server by ABP 61 3D 3 2 network ID 0 uint32 Read Network server ID number, used to register the product on the Network server by ABP 63 3F 3 2 join mode OTAA string Read OTAA: Over-the-Air activation, ABP: Activation by Personalization 65 41 3 4 network mode PUBLIC string Read PUBLIC, PRIVATE 69 45 3 3 region code AS923 string Read 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 72 48 3 4 data rate DR2:980 string Read DR0:250, DR1:440, DR2:980, DR3:1760, DR4:3125, DR5:5470 76 4C 3 3 bandwidth BW125 string Read BW125, BW250, BW500 79 4F 3 2 spread factor SF10 string Read SF12, SF11, SF10, SF9, SF8, SF7 81 51 3 4 activation of ADR ADR OFF string Read ADR ON, ADR OFF 85 55 3 1 class A string Read 103 67 3 1 sensor type 1-255 uint16 Read 1-254: sensor type, 255: no sensor 104 68 3 1 battery level 0-3 uint16 Read 4 levels of battery capacity status 105 69 3 1 error status 0-1 uint16 Read Error code of sensor, 0: no error, 1: error 106 6A 3 1 prm1 alarm status 0-2 uint16 Read Alarm status of parameters 1, 0: none, 1: Low, 2: High 107 6B 3 1 prm2 alarm status 0-2 uint16 Read Alarm status of parameter 2 108 6C 3 2 prm1 value float Read Parameter value 1 110 6E 3 2 prm2 value float Read Parameter value 2 112 70 3 1 battery % 10%, 30%, 60%, 99% uint16 Read % Value of battery capacity 113 71 3 2 battery voltage 0-3.67 vdc float Read Value of battery voltage 115 73 3 2 mcu temperature oC float Read Temperature value of RF module 117 75 3 1 mcu vref 0-3.67 vdc uint16 Read Vref value of RF module 118 76 3 1 button1 status 0-1 uint16 Read Button state, 0: No button pressed, 1: Button pressed 119 77 3 1 button2 status 0-1 uint16 Read Button status, 0: No magnetic sensor detected, 1: Magnetic sensor detected Here is the table for Configuration: Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 256 100 3 / 16 1 modbus address 1-247 1 uint16 R/W Modbus address of the device 257 101 3 / 16 1 modbus baudrate 0-1 0 uint16 R/W 0: 9600, 1: 19200 258 102 3 / 16 1 modbus parity 0-2 0 uint16 R/W 0: none, 1: odd, 2: even 259 103 3 / 16 9 serial number string R/W (Password) 268 10C 3 / 16 2 password for setting uint32 R/W (Password) password 190577 270 10E 3 / 16 4 lora appEUI hex R/W (Password) Application server's EUI number, used to register the product on the Network Server by OTAA 274 112 3 / 16 8 lora appKey hex R/W (Password) The number of keys used to create two security keys of the End Device, used to register the product on the Network server by OTAA 282 11A 3 / 16 8 lora nwkSkey hex R/W (Password) key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 290 122 3 / 16 8 lora appSkey hex R/W (Password) End Device data encryption key number, used to register the product on the Network Server by ABP 298 12A 3 / 16 2 device address uint32 R/W (Password) End Device address created by Application server, used to register the product on the Network server by ABP 300 12C 3 / 16 2 network ID uint32 R/W (Password) Network server ID number, used to register the product on the Network server by ABP 302 12E 3 / 16 1 activation mode 0-1 1 uint16 R/W (Password) 1: OTAA (Over-the-Air Activation), 0: ABP (Activation by Personalization) 304 130 3 / 16 1 application port 1-255 1 uint16 R/W (Password) Port 224 is reserved for certification 317 13D 3 / 16 1 region 1-7 1 uint16 Read/Write(Password) 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 318 13E 3 / 16 1 data rate 7 uint16 R/W (Password) 0: 250 bps, 1: 440 bps, 2: 980 bps, 3: 1760 bps, 4: 3125 bps, 5: 5470 bps 319 13F 3 / 16 1 tx power 2-20 16 uint16 R/W (Password) tx power: 2,4,6,8,10,12,14,16,18,20 320 140 3 / 16 1 adaptative data rate 0-1 0 uint16 R/W (Password) Automatically adjust data rate, 0: disable, 1: enable 334 14E 3 / 16 2 cycle send data 900 uint32 R/W sec (data sending cycle) 338 152 3 / 16 1 alarm limt 44 uint16 R/W limit the number of events / day 340 154 3 / 16 2 sensor1: sampling_rate 120 uint32 R/W sec (frequency of data taken from sensor 1) 348 15C 3 / 16 2 prm1: a 1 float R/W Scale parameter "a" of sensor 1 350 15E 3 / 16 2 prm1: b 0 float R/W Scale parameter "b" of sensor 1 354 162 3 / 16 2 prm1: High Threshold 100000 float R/W High threshold value of sensor 1 356 164 3 / 16 2 prm1: High Hysteresis 10000 float R/W High hysteresis value of sensor 1 358 166 3 / 16 2 prm1: Low Threshold 0 float R/W Low threshold value of sensor 1 360 168 3 / 16 2 prm1: Low Hysteresis 10000 float R/W Low hysteresis value of sensor 1 362 16A 3 / 16 2 prm1: High Cut 100000 float R/W Upper limit value of sensor 1 364 16C 3 / 16 2 prm1: Low Cut 0 float R/W Lower limit value of sensor 1 366 16E 3 / 16 2 prm2: a 1 float R/W Scale parameter "a" of sensor 2 368 170 3 / 16 2 prm2: b 0 float R/W Scale parameter "b" of sensor 2 372 174 3 / 16 2 prm2: High Threshold 100000 float R/W High threshold value of sensor 2 374 176 3 / 16 2 prm2: High Hysteresis 10000 float R/W High hysteresis value of sensor 2 376 178 3 / 16 2 prm2: Low Threshold 0 float R/W Low threshold value of sensor 2 378 17A 3 / 16 2 prm2: Low Hysteresis 10000 float R/W Low hysteresis value of sensor 2 380 17C 3 / 16 2 prm2: High Cut 100000 float R/W Upper limit value of sensor 2 382 17E 3 / 16 2 prm2: Low Cut 0 float R/W Lower limit value of sensor 2 6. Installation 6.1 Installation location To maximize the distance of transmission, the ideal condition is Line-of-sight (LOS) between the LoRaWAN sensor and Gateway. In real life, there may be no LOS condition. However, the LoRaWAN sensor still communicates with Gateway, but the distance will be reduced significantly. ATTENTION:DO NOT install the LoRaWAN 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, cement…is acceptable. 6.2 Sensor connection Connect the sensor to the Pt100 thermal probe Step 1: Using L hex key to unscrew M4 screws at the side of housing and carefully pull out the top plastic housing in the vertical direction Step 2: Put the signal wires through the PG9 port to connect the sensor Step 3: Connect the wires that correspond to the label on the sensor Step 4: Insert the top plastic housing and locking by L hex key 6.3 Battery installation Steps for battery installation: Step 1: Using L hex key to unscrew M4 screws at the side of housing and carefully pull out the top plastic housing in the vertical direction Step 2: Insert 02 x AA 1.5VDC battery, please take note the poles of battery ATTENTION: REVERSED POLARITY OF BATTERIES IN 10 SECONDS CAN DAMAGE THE SENSOR CIRCUIT!!! Step 3: Insert the top plastic housing and locking by L hex key ATTENTION: When reinstalling the cover, pay attention to put the PCB edge into the middle slot of the box inside as shown below) 7. Troubleshooting No. Phenomena Reason Solutions 1 The BLUE LED does not blink when the battery is installed Insert the battery in the opposite direction Insert the battery in the correct way 2 The RED LED is always on Due to noise, the peripheral components (i2c, spi, uart, ..) of RF module cannot be initialized After 30s the node will automatically reset. If the noise causes the Watchdog not to initialize, remove the battery and wait for more than 10 seconds, then insert the battery again 3 The RED LED blinks continuously (10ms ON / 2s OFF) and the Node does not send RF. After more than 10 sending cycles, the Node will automatically reset Operating frequency in that country is prohibited Operating frequency in that country is limited to Data rate, Tx Power Reconfigure the allowed frequency of operation Reconfigure Data rate = DR5 / SF07, Tx Power 4 RED LED blinks continuously (10ms ON / 2s OFF) and Node sends RF continuously 3s / time but no data. After more than 10 sending cycles, the Node will automatically reset Node runs dummy sending mode => sent by Gateway to send Downlink packets when users clear Uplink and Downlink counter values on Network Server (build in Gateway) when activated by ABP Configuration enabled by OTAA 5 The RED LED flashes 10ms ON / 10s OFF and the Node does not send RF Node activation by OTAA on Network server has not been successful Using Margnet-Key to force Node to send RF continuously for 3 seconds / time => when activating by OTAA successfully, the GREEN LED will blink after sending RF 6 The node sent RF successfully but the GREEN LED did not blink LED is broken Warranty to replace LED 7 The data packet taken from the Gateway has an incorrect value The data package is encrypted Get the decoded packet on the Application Server 8 Node sends RF and activates by ABP, on Gateway receives data but Application server has no data The application server still stores the counter values of the previous Uplink and Downlink Delete the counter values of Uplink and Downlink on the Application server 9 The node does not send RF and the RF module is hot Insert the battery in the opposite direction Short circuit Warranty or replacement 10 Node does not send RF to Gateway according to the alarm, LED does not blink The alarm configuration is incorrect Running out of the number of alarms set for the day Check alarm configuration Check the configuration for the maximum number of alarms per day 11 Node does not send RF to Gateway when activated by the magnetic switch, LED does not blink Magnetic switch has malfunctioned Read the status of the magnetic switch via modbus (when powering or attaching the battery) to see if the magnetic switch is working. 12 Node has blinked LED GREEN when sending RF but the Gateway or Application server cannot received LoRa module on the Gateway is faulty The IP connection (4G / WiFi / ...) on the Gateway is faulty Check Gateway's LoRa status lights on Gateway Check 4G / WiFi status lights on Gateway 13 The value of the sensor is 0 and sensor_type = 0xFF Lost connection with the sensor Check sensor connection Replace the module sensor 14 RSSI is weak and often loses data Distance between Node and Gateway is far or there are many obstructions Connection to Antenna problem Install metal nodes or in metal cabinets Configure Data rate = DR0 / SF12 Check Antenna position Install Node in a well ventilated location 8. Support contacts Manufacturer Daviteq Technologies IncNo.11 Street 2G, Nam Hung Vuong Res., An Lac Ward, Binh Tan Dist., Ho Chi Minh City, Vietnam.Tel: +84-28-6268.2523/4 (ext.122) Email: info@daviteq.com | www.daviteq.com Distributor in Australia and New Zealand Templogger Pty Ltd Tel: 1800 LOGGER Email: contact@templogger.net USER GUIDE FOR LORAWAN SOIL MOISTURE SENSOR WSLRW-SMT THIS IS OBSOLETE MANUAL Please access https://www.iot.daviteq.com/wireless-sensors for updated manual WSLRW-SMT-MN-EN-01 DEC-2020 This document is applied for the following products SKU WSLRW-SMT HW Ver. 1.1 FW Ver. 1.0 Item Code WSLRW-SMT-01 LoRaWAN Soil moisture and temperature sensor, pre-calibarted, Type AA battery 1.5VDC, IP67/IP68, sensor cable 2m WSLRW-SMT-02 LoRaWAN Soil moisture and EC sensor, pre-calibarted, Type AA battery 1.5VDC, IP67/IP68, sensor cable 2m 0. Configuration Check List STEP 1: Configure End Device (Using Modbus Configuration Cable) Setting value (Example) 1. Select region AS923, IN865, EU868,.. (refer to register address 317) 2. End Device Operation OTAA or ABP OTAA Write AppEUI information from Application Server to Lorawan End Device; Write AppKey (created by user) information for Lorawan End Device and Application Server. ABP Write DevEUI information from Application Server to Lorawan end device; write Network Session Key and App Session Key (created by user) information to Lorawan end device (and Application Server). 3. Configure "cycle send data" 900 sec (Defaut) 4. Configure "sensor sampling_rate" 120 sec (Defaut) 5. Configure parameters of sensor (Refer to Check data configuration table) STEP 2:  Configure the operation of LoRaWAN Gateway (Ex: URSALINK Gateway) 1. Configure the information in the General tab Server address, Server port (For more information) 2. Configure the information in the Radio tab Select the Region Region (Other parameters to default) STEP 3:  Configure the operation of LoRaWAN Gateway on Network Server (Ex: URSALINK Gateway with Thethingsnetwork) 1. Gateway ID registration Gateway ID is the GatewayEUI information on the Gateway 2. Frequency Plan parameters configuration Asia 920-923MHz, Europe 868MHz,... 3. Router parameters configuration 4. Check the connection of the gateway to the network server The Gateway status LED lights up and displays the message "Status: conneted" on the Thethingsnetwork STEP 4:  Configure the operation of Application Server on Network Server 1. App ID registration 2. Handler parameters configuration STEP 5: Register Lorawan End Device on Application Server on Thethingsnetwork 1. ID Registration 2.Select operation mode OTAA or ABP OTAA Configure parameters DevEUI and AppKEY ABP Configure parameters Device Address, Network Session Key, App Session Key 1. Functions Change Log HW Ver. FW Ver. Release Date Functions Change 1.1 1.0.0 15-Oct-2020 2. Introduction WSLRW-SMT is LoRaWAN Soil Moisture Sensor, can be used to measure the Soil Moisture, Fertilizer and Soil Erosion, too. It is powered by 02 x AA-type batteries and can last up to 10 years. The Moisture sensor utillize the Frequency Domain measuring technique to deliver high accuracy and stable measurment of Soil moisture. The Moisture value is not affected by fertilizer content and temperature like other simple Capacitance Moisture Sensor on the market. The sensor will transmit data in kilometers distance to LoRaWAN gateway, any brand on the market. The typical applications are Smart farm, Smart Agriculture, Automatic Irrigation System, Soil Qualtiy Measurement, Soil Erosion Monitoring... 3. Specification SENSORS SPECIFICATION : Moisture & EC Sensors Advanced technology - Frequency Domain Reflectometry with response time Moisture range / accuracy / resolution 0 .. 100 %, acc +/- 3.0% , res 0.01% Temperature range / accuracy / resolution -30 .. + 70°C, acc +/- 0.3 °C, res 0.1 °C EC range / accuracy / resolution 0 .. 20 mS/cm, acc +/- 2.0% span, res 0.1 mS/cm Measurement Volume Dia. 70mm x Height 70mm Wetted materials 316L SS & thermoplastic Sensor Dimensions 71x45x16mm with probes 70mm and signal cable 2m Optional Soil Erosion Sensor Clinometer type Soil Erosion Probe Dia. 10mm x Length 300mm with signal cable 2m, SS304 material LoRaWAN SPECIFICATION : Data rate 250bps .. 5470bps Antenna External Antenna 0 dbi Battery 02 x AA size 1.5VDC, battery not included RF Frequency and Power 860..930Mhz, +14 .. +20 dBm, configurable for zones: EU868, IN865, RU864, KR920, AS923, AU915, US915 Protocol LoRaWAN RF Module complies to ETSI EN 300 220, EN 303 204 (Europe) FCC CFR47 Part15 (US), ARIB STD-T108 (Japan) Vietnam Type Approval Working temperature -40°C..+60°C (with AA L91 Energizer) Dimensions/Netweight H106xW73xD42, 190 grams (Wireless part only) Housing Aluminum + Polycarbonate plastic, IP67. 4. Operation Principle 4.1 LoRaWAN protocol specifications 4.1.1 LoRaWAN Sensor protocol specifications LoRaWAN Protocol Version 1.0.3 Application Server Version 1.3.0.0 MAC Layer Version 4.4.2.0 Radio Standards: LoRa Alliance Certified LoRaWAN Zone: LoRa Alliance AS923, KR920, AU915, US915, EU868, IN865, RU864 Class A Join Active: OTAA / ABP Network Mode: Public Network / Private Network Tx Power: up to 20 dBm Frequency: 860 - 930Mhz Date rate: 250 bps - 5kbps Spreading factor: SF12 - SF7 Bandwidth: 125 kHz Unconfirmed-data message LoRaWAN application port for certification: 224 4.1.2 Data rate of LoRaWAN Sensor Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR2 980 SF10 125 AS923, AU915 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 980 SF10 125 US915 DR1 1760 SF9 125 DR2 3125 SF8 125 DR3 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 250 SF12 125 KR920, EU868, IN865, RU864 DR1 440 SF11 125 DR2 980 SF10 125 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 4.1.3 Tx power of LoRaWAN sensor Max EIRP (dBm) Max Tx Power (dBm) Region 16 16 AS923 14 14 KR920 30 20 AU915 30 20 US915 16 16 EU868 30 20 IN865 16 16 RU864 4.2 The principle of operation of the LoRaWAN sensor When starting the power supply, the LoRaWAN sensor has 60 seconds to allow configuration to operate via the Configuration Cable with the Modbus RTU protocol. After 60 seconds, the first packet will be sent, then the LoRaWAN sensor will send the next packets in the following cases: Case 1: When it reaches the frequency of taking data, the LoRaWAN sensor will wake up to measure and calculate. Then: If the measured value exceeds the High or Low setting thresholds, the packet will be sent to the Gateway and then asleep; If NOT then sleep without sending data. NOTE: Once sending the data to Gateway by this alarm event, the timer of sending time interval will be reset; Case 2: When the sending time interval is reached, the LoRaWAN sensor wakes up to measure and calculate and send data to Gateway immediately, regardless of value. Case 3: By using the magnet key, the LoRaWAN sensor can be triggered to send data to Gateway immediately. NOTE: The time between sending data for Class A is at least 3 seconds 4.3 Principle of operation LoRaWAN Network The LoRaWAN Gateway function is Packet Forwarder so: Between Gateway and End Device: Gateway receives data packets from End Device via RF connection, so it is recommended to configure Radio parameters (Note: the packet that Gateway receives is encrypted) Between Gateway and Network Server: Gateway forwards data packets to the Network server via an IP connection, so it is recommended to configure Network parameters such as Server Address, Server Uplink Port, Server Downlink Port,... LoRaWAN Network is secured as follows: Network section key (NwkSKey) to ensure the security of communications on the Network The application session key (AppSKey) to ensure data security between End Device and Application Server Special keys of the device such as DevEUI, AppEUI, Gateway EUI, Device Address. Therefore, the data packet that the Gateway receives is encrypted and decrypted on the Application server. To End Device connect to the Network server, you need to register in the following two ways: Activation with OTAA (Over-the-Air activation): is the process of joining the Network automatically. Previously, both End Device and Application Server installed the same DevEUI code, AppEUI, and AppKey. During activation, AppKey will generate 2 security keys for End Device and Network, which are: The network session key (NwkSKey): is the key to secure communication commands on the MAC layer between the End Device and the Network server. The application session key (AppSKey): is the key to secure data packets between the End Device and Application server. ATTENTIONS:* OTAA mode must be successfully activated in order for the End Device to send data packets to the Network through the Gateway;* OTAA mode only need to activate once, if the device is reset or battery replacement, it will activate OTAA again;* When the End Device is connected to the Network server, whether the Gateway is reset or the power is restarted, it will not need to activate OTAA. Activation by ABP (Activation by Personalization): is the process of joining the Network manually. Device Address, Network session key (NwkSKey), and Application session key (AppSKey) codes must be stored inside the End Device and Application server, so when the End Device sends data packets to the network server, it will also send the security codes to activate. 4.4 Configure the LoRaWAN Network 4.4.1 Configure End Device operation according to OTAA Configuration parameters for the End Device to be activated by OTAA as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode OTAA Device activation type on Network Server DevEUI 34 35 31 31 4B 37 75 12 Device ID's unique ID number => Set this ID number for the Application server AppEUI 70 B3 D5 7E D0 02 D5 0B Application server's unique ID number (random or user-generated)=> Set this ID number for End Device AppKey 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C Key Number for generating 2 NwkSKey and AppSKey security keys created by the user (factory-created by default)=> Used to install for both the Device and Application Server End ATTENTIONS:* The AppEUI number from Application Server => then installed for the End Device. AppEUI is randomly generated by the Application server or by the user;* The number of AppKeys during OTAA activation will generate two security keys, Lora NwkSKey and AppSKey, which are used for both End Device and Network. 4.4.2 Configure End Device operation according to ABP Configuration parameters for the End Device to be activated by ABP as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode ABP Device activation type on Network Server Device Address 12 34 56 78 End Device Address created by the Application server=> Set Device Address for End Device NwkSKey (Network session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C NwkSKey number created by the user to install and use for both End Device and Application Server AppSKey (Application session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C AppSKey number generated by the user to install for both End Device and Application Server 4.4.3 Configure Gateway operations 4.4.3.1 Configure the Gateway to receive data packets from the End Device. Radio settings need to be set as:* Region code: AS923, KR920, AU915, US915, EU868, IN865, RU864* Center Frequency, Channels, Bandwidth (recommends using the default configuration created by the system) Let's take an example to configure the Gateway operation of URSALINK (Model: UG85-L00E-915) 4.4.3.2 Configure the Gateway to communicate with the Public Network Server Let's take an example of configuring Gateway UG85 to connect with "thethingsnetwork.org" in Asia: Currently, thethingsnetwork only supports the connection protocol with Gateway is Semtech UDP Packet Forwarder. https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Parameter settings Setting value (example) Description Gateway EUI 24e124fffef038fd Gateway's unique ID number=> Set this ID number for Application server Server Address router.as1.thethings.network Semtech server address: https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Router regional Asia: router.as1.thethings.network Router regional India: ttn.thingsconnected.net Ursalink server address: localhost Server Uplink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Server Downlink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Network mode Public LoRaWAN 4.4.4 Register the Application server on the Public Network "thethingsnetwork.org" 4.4.4.1 Register the Gateway on Public Network "thethingsnetwork.org" as shown below: The current network only supports the Gateway connection protocol, "Semtech UDP protocol" is Semtech UDP Packet Forwarder. Then power the Gateway and observe the message "Status: connected" => Registration of the Gateway on the Application successfully. 4.4.4.2 Register Application on Public Network "thethingsnetwork.org" as shown below: 4.4.4.3 Register End Device on Application: 4.5 LED meaning RED LED: Fixed ON: due to noise caused peripheral components (i2c, spi, uart, timer, rtc, wdt, ...) do not initialize. Flashing 10ms ON / 10s OFF: Activation by OTAA on the Network server failed. Flashing 10ms ON / 2s OFF:  Sending a data packet to Gateway failed. GREEN LED: Flashing 100ms ON / OFF when sending a data packet to Gateway. BLUE LED: Flashing 1s ON / 1s OFF for the first 60 seconds when booting (insert batteries or connected external sources), after 60 seconds OFF. ON during the LoRaWAN sensor receives data packets from the Network server and OFF when received. 4.6 Process of measurement When the LoRa sensor wakes up, it will supply power to the internal or external sensor so that the sensor can start measuring. After measuring successfully it will turn off the power to the sensor for energy saving. The measured value is the raw value of the sensor. The measured value can be scaled according to the following formula: Y = aX + b X: the raw value from the sensor Y: the calculated value will be sent to LoRaWAN Gateway in the payload data. a: constant (default value is 1) b: constant (default value is 0) So, if there is no user setting for a and b ==> Y = X The Y value will be compared with Lo and Hi threshold. Please refer below the graph of alarm processing. 4.7 Payload Data The following is the format of payload data that will be sent to the LoRaWAN Gateway. Sensor type (1 byte) Status1 (1 byte) 1st - Parameter (4 bytes) 2nd - Parameter (4 bytes) Meaning of Data in the Payload Data Size (byte) Bit Format Meaning Sensor type 1 all Uint8 Sensor type = 0x0C means LoRaWAN Node Sensor type = 0xFF means no sensor Status: battery level 1 Bit 7 and 6 Uint8 Battery capacity in 04 levels 11: battery level 4 (99%) 10: battery level 3 (60%) 01: battery level 2 (30%) 00: battery level 1 (10%) Status: error Bit 5 and 4 Node status 01: error 00: no error Status: alarm 1 Bit 3 and 2 Alarm status of 1st - Parameter (Y1 value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm Status: alarm 2 Bit 1 and 0 Alarm status of 2nd - Parameter (Y2 value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm 1st - Parameter 4 all Float 1st - Parameter 4 all Float Y1 value: soil moisture value (0..100%) 2nd - Parameter 4 all Float 2nd - Parameter 4 all Float Y2 value: temperature value ( -30°C..+70°C) 5. Configuration Using the configuration cable to connect to the sensor as below picture. Serial port configuration on the computer:* COMPort, Baudrate: 9600, Parity: None, Stop bit: 1, Data bit: 8* Modbus RTU: Reading data by Function 3 / Writing data by Function 16. 5.1 Step to configure NOTE: The Modbus configuration can only be performed in the first 60s after power up the LoRaWAN sensor. After 60s, if user can not finish the configuration process, user need to reset the power of LoRaWAN sensor again, by removing battery in at least 15s. Step 1: Install the Modbus Configurator Software in the link below https://filerun.daviteq.com/wl/?id=qK0PGNbY1g1fuxTqbFW9SXtEvCw7bpc6 How to use the Modbus configuration software Step 2: Plug the configuration cable to computer via USB port and install the driver; Step 3: Open the plastic housing with L hex key to unscrew M4 screws at the side of the housing Step 4: Plug the connector to the configuration port; Step 5:  Import the configuration file by importing the csv file: Go to MENU: FILE / Import New / => select the file with name CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0.csv (in the link below). Then click Connect; CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0 To write new value to the device:First, you need to write the password in "password for setting", after reading the value to check ok, you can write the new value AppEUI, AppKey, ...You only have 60 seconds after plugging the configuration cable or the power supply into the device for configuration. 5.2 Register table Here is the table of Data will be read by Modbus tool Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 0 0 3 5 device info WSLRW-SMT1 string Read Wireless Sensor LoRaWAN with SMT1 5 5 3 4 firmware version 1.00ddmm string Read ddmm = day / month 9 9 3 2 hardware version 1.10 string Read 11 B 3 4 lorawan protocol version 01.00.03 string Read lorawan v1.0.3 15 F 3 6 application version 01.03.00.00 string Read application server v1.3.0.0 21 15 3 6 mac layer version 04.04.02.00 string Read mac layer v4.4.2.0 27 1B 3 4 deviceEUI hex Read End Device's EUI number, used to register the product on the Network Server by OTAA 31 1F 3 4 lora appEUI hex Read Application server's EUI number is used to register the product on the Network Server by OTAA 35 23 3 8 lora appKey hex Read The number of keys used to create two security keys of the End Device, used to register the product on the Network Server by OTAA 43 2B 3 8 lora nwkSkey hex Read key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 51 33 3 8 lora appSkey hex Read End Device data encryption key number, used to register the product on the Network Server by ABP 59 3B 3 2 device address 0 uint32 Read End Device address created by Application server, used to register the product on the Network server by ABP 61 3D 3 2 network ID 0 uint32 Read Network server ID number, used to register the product on the Network server by ABP 63 3F 3 2 join mode OTAA string Read OTAA: Over-the-Air activation, ABP: Activation by Personalization 65 41 3 4 network mode PUBLIC string Read PUBLIC, PRIVATE 69 45 3 3 region code AS923 string Read 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 72 48 3 4 data rate DR2:980 string Read DR0:250, DR1:440, DR2:980, DR3:1760, DR4:3125, DR5:5470 76 4C 3 3 bandwidth BW125 string Read BW125, BW250, BW500 79 4F 3 2 spread factor SF10 string Read SF12, SF11, SF10, SF9, SF8, SF7 81 51 3 4 activation of ADR ADR OFF string Read ADR ON, ADR OFF 85 55 3 1 class A string Read 103 67 3 1 sensor type 1-255 uint16 Read 1-254: sensor type, 255: no sensor 104 68 3 1 battery level 0-3 uint16 Read 4 levels of battery capacity status 105 69 3 1 error status 0-1 uint16 Read Error code of sensor, 0: no error, 1: error 106 6A 3 1 prm1 alarm status 0-2 uint16 Read Alarm status of parameters 1, 0: none, 1: Low, 2: High 107 6B 3 1 prm2 alarm status 0-2 uint16 Read Alarm status of parameter 2 108 6C 3 2 prm1 value float Read Value of parameter 1 110 6E 3 2 prm2 value float Read Value of parameter 2 112 70 3 1 battery % 10%, 30%, 60%, 99% uint16 Read % Value of battery capacity 113 71 3 2 battery voltage 0-3.67 vdc float Read Value of battery voltage 115 73 3 2 mcu temperature °C float Read Temperature value of RF module 117 75 3 1 mcu vref 0-3.67 vdc uint16 Read Vref value of RF module 118 76 3 1 button1 status 0-1 uint16 Read Button state, 0: No button pressed, 1: Button pressed 119 77 3 1 button2 status 0-1 uint16 Read Button status, 0: No magnetic sensor detected, 1: Magnetic sensor detected Here is the table for Configuration: Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 256 100 3 / 16 1 modbus address 1-247 1 uint16 R/W Modbus address of the device 257 101 3 / 16 1 modbus baudrate 0-1 0 uint16 R/W 0: 9600, 1: 19200 258 102 3 / 16 1 modbus parity 0-2 0 uint16 R/W 0: none, 1: odd, 2: even 259 103 3 / 16 9 serial number string R/W (Password) 268 10C 3 / 16 2 password for setting uint32 R/W (Password) password 190577 270 10E 3 / 16 4 lora appEUI hex R/W (Password) Application server's EUI number, used to register the product on the Network Server by OTAA 274 112 3 / 16 8 lora appKey hex R/W (Password) The number of keys used to create two security keys of the End Device, used to register the product on the Network server by OTAA 282 11A 3 / 16 8 lora nwkSkey hex R/W (Password) key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 290 122 3 / 16 8 lora appSkey hex R/W (Password) End Device data encryption key number, used to register the product on the Network Server by ABP 298 12A 3 / 16 2 device address uint32 R/W (Password) End Device address created by Application server, used to register the product on the Network server by ABP 300 12C 3 / 16 2 network ID uint32 R/W (Password) Network server ID number, used to register the product on the Network server by ABP 302 12E 3 / 16 1 activation mode 0-1 1 uint16 R/W (Password) 1: OTAA (Over-the-Air Activation), 0: ABP (Activation by Personalization) 304 130 3 / 16 1 application port 1-255 1 uint16 R/W (Password) Port 224 is reserved for certification 317 13D 3 / 16 1 region 1-7 1 uint16 Read/Write(Password) 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 318 13E 3 / 16 1 data rate 7 uint16 R/W (Password) 0: 250 bps, 1: 440 bps, 2: 980 bps, 3: 1760 bps, 4: 3125 bps, 5: 5470 bps 319 13F 3 / 16 1 tx power 2-20 16 uint16 R/W (Password) tx power: 2,4,6,8,10,12,14,16,18,20 320 140 3 / 16 1 adaptative data rate 0-1 0 uint16 R/W (Password) Automatically adjust data rate, 0: disable, 1: enable 334 14E 3 / 16 2 cycle send data 900 uint32 R/W sec (data sending cycle) 338 152 3 / 16 1 alarm limt 44 uint16 R/W limit the number of events / day 340 154 3 / 16 2 sensor1: sampling_rate 120 uint32 R/W sec (frequency of data taken from sensor 1) 348 15C 3 / 16 2 prm1: a 1 float R/W Scale parameter "a" of prm1 350 15E 3 / 16 2 prm1: b 0 float R/W Scale parameter "b" of prm1 354 162 3 / 16 2 prm1: High Threshold 100000 float R/W High threshold value of prm1 356 164 3 / 16 2 prm1: High Hysteresis 10000 float R/W High hysteresis value of prm1 358 166 3 / 16 2 prm1: Low Threshold 0 float R/W Low threshold value of prm1 360 168 3 / 16 2 prm1: Low Hysteresis 10000 float R/W Low hysteresis value of prm1 362 16A 3 / 16 2 prm1: High Cut 100000 float R/W Upper limit value of prm1 364 16C 3 / 16 2 prm1: Low Cut 0 float R/W Lower limit value of prm1 366 16E 3 / 16 2 prm2: a 1 float R/W Scale parameter "a" of prm2 368 170 3 / 16 2 prm2: b 0 float R/W Scale parameter "b" of prm2 372 174 3 / 16 2 prm2: High Threshold 100000 float R/W High threshold value of prm2 374 176 3 / 16 2 prm2: High Hysteresis 10000 float R/W High hysteresis value of prm2 376 178 3 / 16 2 prm2: Low Threshold 0 float R/W Low threshold value of prm2 378 17A 3 / 16 2 prm2: Low Hysteresis 10000 float R/W Low hysteresis value of prm2 380 17C 3 / 16 2 prm2: High Cut 100000 float R/W Upper limit value of prm2 382 17E 3 / 16 2 prm2: Low Cut 0 float R/W Lower limit value of prm2 6. Installation 6.1 Example application 6.2 Installation location To maximize the distance of transmission, the ideal condition is Line-of-sight (LOS) between the LoRaWAN sensor and Gateway. In real life, there may be no LOS condition. However, the LoRaWAN sensor still communicates with Gateway, but the distance will be reduced significantly. ATTENTION:DO NOT install the LoRaWAN 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, cement…is acceptable. 6.3 IO Wiring WSLRW-SMT sensor connects to the sensor probe via M12 Connector. Plug the sensor into the ground so that the metal poles of the sensor are deep in the ground. 6.4 Battery installation Steps for battery installation: Step 1: Using L hex key to unscrew M4 screws at the side of the housing and carefully pull out the top plastic housing in the vertical direction Step 2: Insert 02 x AA 1.5VDC battery, please take note the poles of the battery ATTENTION: REVERSED POLARITY OF BATTERIES IN 10 SECONDS CAN DAMAGE THE SENSOR CIRCUIT!!! Step 3: Insert the top plastic housing and locking by L hex key ATTENTION: When reinstalling the cover, pay attention to put the PCB edge into the middle slot of the box inside as shown below) 7. Troubleshooting No. Phenomena Reason Solutions 1 The BLUE LED does not blink when the battery is installed Insert the battery in the opposite direction Insert the battery in the correct way 2 The RED LED is always on Due to noise, the peripheral components (i2c, spi, uart, ..) of RF module cannot be initialized After 30s the node will automatically reset. If the noise causes the Watchdog not to initialize, remove the battery and wait for more than 10 seconds, then insert the battery again 3 The RED LED blinks continuously (10ms ON / 2s OFF) and the Node does not send RF. After more than 10 sending cycles, the Node will automatically reset Operating frequency in that country is prohibited Operating frequency in that country is limited to Data rate, Tx Power Reconfigure the allowed frequency of operation Reconfigure Data rate = DR5 / SF07, Tx Power 4 RED LED blinks continuously (10ms ON / 2s OFF) and Node sends RF continuously 3s / time but no data. After more than 10 sending cycles, the Node will automatically reset Node runs dummy sending mode => sent by Gateway to send Downlink packets when users clear Uplink and Downlink counter values on Network Server (build-in Gateway) when activated by ABP Configuration enabled by OTAA 5 The RED LED flashes 10ms ON / 10s OFF and the Node does not send RF Node activation by OTAA on Network server has not been successful Using Magnet-Key to force Node to send RF continuously for 3 seconds/time => when activating by OTAA successfully, the GREEN LED will blink after sending RF 6 The node sent RF successfully but the GREEN LED did not blink LED is broken Warranty to replace LED 7 The data packet taken from the Gateway has an incorrect value The data package is encrypted Get the decoded packet on the Application Server 8 The node sends RF and activates by ABP, on Gateway receives data but the Application server has no data The application server still stores the counter values of the previous Uplink and Downlink Delete the counter values of Uplink and Downlink on the Application server 9 The node does not send RF and the RF module is hot Insert the battery in the opposite direction Short circuit Warranty or replacement 10 The node does not send RF to Gateway according to the alarm, LED does not blink The alarm configuration is incorrect Running out of the number of alarms set for the day Check alarm configuration Check the configuration for the maximum number of alarms per day 11 The node does not send RF to Gateway when activated by the magnetic key, LED does not blink The magnetic sensor has malfunctioned Read the status of the magnetic sensor via Modbus (when powering or attaching the battery) to see if the magnetic sensor is working. 12 Node has blinked LED GREEN when sending RF but the Gateway or Application server cannot receive LoRa module on the Gateway is faulty The IP connection (4G / WiFi / ...) on the Gateway is faulty Check Gateway's LoRa status lights on Gateway Check 4G / WiFi status lights on Gateway 13 The value of the sensor is 0 and sensor_type = 0xFF Lost connection with the sensor Check sensor connection Replace the module sensor 14 RSSI is weak and often loses data The distance between Node and Gateway is far or there are many obstructions Connection to Antenna problem Install metal nodes or in metal cabinets Configure Data rate = DR0 / SF12 Check Antenna position Install Node in a well-ventilated location 8. Support contacts Manufacturer Daviteq Technologies IncNo.11 Street 2G, Nam Hung Vuong Res., An Lac Ward, Binh Tan Dist., Ho Chi Minh City, Vietnam.Tel: +84-28-6268.2523/4 (ext.122) Email: info@daviteq.com | www.daviteq.com Distributor in Australia and New Zealand Templogger Pty Ltd Tel: 1800 LOGGER Email: contact@templogger.net USER GUIDE FOR LORAWAN ULTRASONIC LIQUID LEVEL SENSOR WSLRW-ULC THIS IS OBSOLETE MANUAL Please access https://www.iot.daviteq.com/wireless-sensors for updated manual WSLRW-ULC-MN-EN-01 DEC-2020 This document is applied for the following products SKU WSLRW-ULC HW Ver. 1.1 FW Ver. 1.1 Item Code WSLRW-ULC-9-01 Wireless LoRaWan Ultrasonic Level Sensor for General Level/Distance Measurement, 30-600cms, Internal antenna, Type AA battery 1.5VDC, IP67, 900-930 Mhz for KR920, AS923, AU915, US915 WSLRW-ULC-8-01 Wireless LoRaWan Ultrasonic Level Sensor for General Level/Distance Measurement, 30-600cms, Internal antenna, Type AA battery 1.5VDC, IP67, 860-870 Mhz for EU868, IN865, RU864 0. Configuration Check List STEP 1: Configure End Device (Using Modbus Configuration Cable) Setting value (Example) 1. Select region AS923, IN865, EU868,.. (refer to register address 317) 2. End Device Operation OTAA or ABP OTAA Write AppEUI information from Application Server to Lorawan End Device; Write AppKey (created by user) information for Lorawan End Device and Application Server. ABP Write DevEUI information from Application Server to Lorawan end device; write Network Session Key and App Session Key (created by user) information to Lorawan end device (and Application Server). 3. Configure "cycle send data" 900 sec (Defaut) 4. Configure "sensor sampling_rate" 120 sec (Defaut) 5. Configure parameters of sensor (Refer to Check data configuration table) STEP 2:  Configure the operation of LoRaWAN Gateway (Ex: URSALINK Gateway) 1. Configure the information in the General tab Server address, Server port (For more information) 2. Configure the information in the Radio tab Select the Region Region (Other parameters to default) STEP 3:  Configure the operation of LoRaWAN Gateway on Network Server (Ex: URSALINK Gateway with Thethingsnetwork) 1. Gateway ID registration Gateway ID is the GatewayEUI information on the Gateway 2. Frequency Plan parameters configuration Asia 920-923MHz, Europe 868MHz,... 3. Router parameters configuration 4. Check the connection of the gateway to the network server The Gateway status LED lights up and displays the message "Status: conneted" on the Thethingsnetwork STEP 4:  Configure the operation of Application Server on Network Server 1. App ID registration 2. Handler parameters configuration STEP 5: Register Lorawan End Device on Application Server on Thethingsnetwork 1. ID Registration 2.Select operation mode OTAA or ABP OTAA Configure parameters DevEUI and AppKEY ABP Configure parameters Device Address, Network Session Key, App Session Key 1. Functions Change Log HW Ver. FW Ver. Release Date Functions Change 1.1 1.0.0 13-OCT-2020 1.1 1.1.0 13-NOV-2020 Payload updates 2. Introduction WSLRW-ULC is LoRaWAN Ultrasonic Level Sensor to measure the level of liquid surface of water, oil... This level sensor utilises the ultrasonic technology to measure the surface of liquid, the principle is to measure the time of flight of the ultrasound pulse in the air environment. The ultrasound pulse will be ejected from ultrasonic transducer, go thru the air and reaching the surface of liquid, then reflected back to the ultrasonic transducer, the measuring circuit will measure the time of flight of the Pulse then calculate the distance from transducer to the surface. With Ultra-low Power design and smart firmware allow the sensor can last up to 10 years with 02 x AA-type batteries (depends on configuration). The sensor will transmit data in kilo-meters distance to LoRaWAN gateway, any brand on the market. 3. Specification SENSORS SPECIFICATION: Sensor Ultrasonic sensor Measurement range 280 .. 7500 mm Resolution ±5.0mm Accuracy ±10 mm + S*0.3% (with S is the measured value) Sensor sampling rate configurable from 10s up to 3600s Alarm setting setting the alarm threshold for calculated value LoRaWAN SPECIFICATION: Data rate 250bps .. 5470bps Antenna Internal Antenna 2.67 dbi Battery 02 x AA size 1.5VDC, battery not included RF Frequency and Power 860..930Mhz, +14 .. +20 dBm, configurable for zones: EU868, IN865, RU864, KR920, AS923, AU915, US915 Protocol LoRaWAN, class A Data sending modes Interval time and when alarm occurred RF Module complies to ETSI EN 300 220, EN 303 204 (Europe) FCC CFR47 Part15 (US), ARIB STD-T108 (Japan) Vietnam Type Approval Working temperature -15°C..+60°C (with AA L91 Energizer) Dimensions H180xW50xD40 Net-weight 250 grams Housing Polycarbonate & POM plastic, IP67 4. Operation Principle 4.1 LoRaWAN protocol specifications 4.1.1 LoRaWAN Sensor protocol specifications LoRaWAN Protocol Version 1.0.3 Application Server Version 1.3.0.0 MAC Layer Version 4.4.2.0 Radio Standards: LoRa Alliance Certified LoRaWAN Zone: LoRa Alliance AS923, KR920, AU915, US915, EU868, IN865, RU864 Class A Join Active: OTAA / ABP Network Mode: Public Network / Private Network Tx Power: up to 20 dBm Frequency: 860 - 930Mhz Date rate: 250 bps - 5kbps Spreading factor: SF12 - SF7 Bandwidth: 125 kHz Unconfirmed-data message LoRaWAN application port for certification: 224 4.1.2 Data rate of LoRaWAN Sensor Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR2 980 SF10 125 AS923, AU915 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 980 SF10 125 US915 DR1 1760 SF9 125 DR2 3125 SF8 125 DR3 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 250 SF12 125 KR920, EU868, IN865, RU864 DR1 440 SF11 125 DR2 980 SF10 125 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 4.1.3 Tx power of LoRaWAN sensor Max EIRP (dBm) Max Tx Power (dBm) Region 16 16 AS923 14 14 KR920 30 20 AU915 30 20 US915 16 16 EU868 30 20 IN865 16 16 RU864 4.2 The principle of operation of the LoRaWAN sensor When starting the power supply, the LoRaWAN sensor has 60 seconds to allow configuration to operate via the Configuration Cable with the Modbus RTU protocol. After 60 seconds, the first packet will be sent, then the LoRaWAN sensor will send the next packets in the following cases: Case 1: When it reaches the frequency of taking data, the LoRaWAN sensor will wake up to measure and calculate. Then: If the measured value exceeds the High or Low setting thresholds, the packet will be sent to the Gateway and then asleep; If NOT then sleep without sending data. NOTE: Once sending the data to Gateway by this alarm event, the timer of sending time interval will be reset; Case 2: When the sending time interval is reached, the LoRaWAN sensor wakes up to measure and calculate and send data to Gateway immediately, regardless of value. Case 3: By using the magnet key, the LoRaWAN sensor can be triggered to send data to Gateway immediately. NOTE: The time between sending data for Class A is at least 3 seconds 4.3 Principle of operation LoRaWAN Network The LoRaWAN Gateway function is Packet Forwarder so: Between Gateway and End Device: Gateway receives data packets from End Device via RF connection, so it is recommended to configure Radio parameters (Note: the packet that Gateway receives is encrypted) Between Gateway and Network Server: Gateway forwards data packets to the Network server via an IP connection, so it is recommended to configure Network parameters such as Server Address, Server Uplink Port, Server Downlink Port,... LoRaWAN Network is secured as follows: Network section key (NwkSKey) to ensure the security of communications on the Network The application session key (AppSKey) to ensure data security between End Device and Application Server Special keys of the device such as DevEUI, AppEUI, Gateway EUI, Device Address. Therefore, the data packet that the Gateway receives is encrypted and decrypted on the Application server. To End Device connect to the Network server, you need to register in the following two ways: Activation with OTAA (Over-the-Air activation): is the process of joining the Network automatically. Previously, both End Device and Application Server installed the same DevEUI code, AppEUI, and AppKey. During activation, AppKey will generate 2 security keys for End Device and Network, which are: The network session key (NwkSKey): is the key to secure communication commands on the MAC layer between the End Device and the Network server. The application session key (AppSKey): is the key to secure data packets between the End Device and Application server. ATTENTIONS:* OTAA mode must be successfully activated in order for the End Device to send data packets to the Network through the Gateway;* OTAA mode only need to activate once, if the device is reset or battery replacement, it will activate OTAA again;* When the End Device is connected to the Network server, whether the Gateway is reset or the power is restarted, it will not need to activate OTAA. Activation by ABP (Activation by Personalization): is the process of joining the Network manually. Device Address, Network session key (NwkSKey), and Application session key (AppSKey) codes must be stored inside the End Device and Application server, so when the End Device sends data packets to the network server, it will also send the security codes to activate. 4.4 Configure the LoRaWAN Network 4.4.1 Configure End Device operation according to OTAA Configuration parameters for the End Device to be activated by OTAA as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode OTAA Device activation type on Network Server DevEUI 34 35 31 31 4B 37 75 12 Device ID's unique ID number => Set this ID number for the Application server AppEUI 70 B3 D5 7E D0 02 D5 0B Application server's unique ID number (random or user-generated)=> Set this ID number for End Device AppKey 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C Key Number for generating 2 NwkSKey and AppSKey security keys created by the user (factory-created by default)=> Used to install for both the Device and Application Server End ATTENTIONS:* The AppEUI number from Application Server => then installed for the End Device. AppEUI is randomly generated by the Application server or by the user;* The number of AppKeys during OTAA activation will generate two security keys, Lora NwkSKey and AppSKey, which are used for both End Device and Network. 4.4.2 Configure End Device operation according to ABP Configuration parameters for the End Device to be activated by ABP as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode ABP Device activation type on Network Server Device Address 12 34 56 78 End Device Address created by the Application server=> Set Device Address for End Device NwkSKey (Network session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C NwkSKey number created by the user to install and use for both End Device and Application Server AppSKey (Application session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C AppSKey number generated by the user to install for both End Device and Application Server 4.4.3 Configure Gateway operations 4.4.3.1 Configure the Gateway to receive data packets from the End Device. Radio settings need to be set as:* Region code: AS923, KR920, AU915, US915, EU868, IN865, RU864* Center Frequency, Channels, Bandwidth (recommends using the default configuration created by the system) Let's take an example to configure the Gateway operation of URSALINK (Model: UG85-L00E-915) 4.4.3.2 Configure the Gateway to communicate with the Public Network Server Let's take an example of configuring Gateway UG85 to connect with "thethingsnetwork.org" in Asia: Currently, thethingsnetwork only supports the connection protocol with Gateway is Semtech UDP Packet Forwarder. https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Parameter settings Setting value (example) Description Gateway EUI 24e124fffef038fd Gateway's unique ID number=> Set this ID number for Application server Server Address router.as1.thethings.network Semtech server address: https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Router regional Asia: router.as1.thethings.network Router regional India: ttn.thingsconnected.net Ursalink server address: localhost Server Uplink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Server Downlink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Network mode Public LoRaWAN 4.4.4 Register the Application server on the Public Network "thethingsnetwork.org" 4.4.4.1 Register the Gateway on Public Network "thethingsnetwork.org" as shown below: The current network only supports the Gateway connection protocol, "Semtech UDP protocol" is Semtech UDP Packet Forwarder. Then power the Gateway and observe the message "Status: connected" => Registration of the Gateway on the Application successfully. 4.4.4.2 Register Application on Public Network "thethingsnetwork.org" as shown below: 4.4.4.3 Register End Device on Application: 4.5 LED meaning RED LED: Fixed ON: due to noise caused peripheral components (i2c, spi, uart, timer, rtc, wdt, ...) do not initialize. Flashing 10ms ON / 10s OFF: Activation by OTAA on the Network server failed. Flashing 10ms ON / 2s OFF:  Sending a data packet to Gateway failed. GREEN LED: Flashing 100ms ON / OFF when sending a data packet to Gateway. BLUE LED: Flashing 1s ON / 1s OFF for the first 60 seconds when booting (insert batteries or connected external sources), after 60 seconds OFF. ON during the LoRaWAN sensor receives data packets from the Network server and OFF when received. 4.6 The Effective Detection Range 4.7 Process of measurement When the LoRa sensor wakes up, it will supply power to the internal or external sensor so that the sensor can start measuring. After measuring successfully it will turn off the power to the sensor for energy saving. The measured value is the raw value of the sensor. The measured value can be scaled according to the following formula: Y = aX + b X: the raw value from the sensor Y: the calculated value will be sent to LoRaWAN Gateway in the payload data. a: constant (default value is 1) b: constant (default value is 0) So, if there is no user setting for a and b ==> Y = X The Y value will be compared with Lo and Hi threshold. Please refer below the graph of alarm processing. 4.8 Calibration Figure – Ultrasonic Level Transmitter Calibration DB: Dead band 0..280 mm (This is a short range in front of the ultrasonic sensor can not measure distances) H: Maximum measuring distance ( Span ) D: Distance For example: Water tank with maximum height to be measured 3000mm (H) and Dead band (DB) is 280 mm, then: From here we can look up the water level corresponding to the measured distance of the sensor by the formula: Y = aX + b. Where: X is the measured distance (mm) and Y is the level (‰) Distance (mm) Level (‰) 280 1000 500 919 1000 735 1500 552 2000 368 2500 184 3000 0 Use the offline configuration tool to configure sigfox sensor. Write in the sensor the parameters a and b. Refer to Resigter table for more details. 4.9 Payload Data The following is the format of payload data that will be sent to the LoRaWAN Gateway. Sensor type (1 byte) Status (1 byte) 1st - Parameter (2 bytes) 2st - Parameter (2 bytes) Meaning of Data in the Payload Data Size (byte) Bit Format Meaning Sensor type 1 all Uint8 Sensor type = 0x0E means LoRaWAN Node ULCSensor type = 0xFF means no sensor Status: battery level 1 Bit 7 and 6 Uint8 Battery capacity in 04 levels 11: battery level 4 (99%) 10: battery level 3 (60%) 01: battery level 2 (30%) 00: battery level 1 (10%) Status: error Bit 5 and 4 Node status 01: error 00: no error Status: alarm 1 Bit 3 and 2 Alarm status of 1st - Parameter (Y1 value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm Status: alarm 2 Bit 1 and 0 Alarm status of 2st - Parameter (Y2 value)11 : Hi alarm01 : Lo alarm00 : No alarm 1st - Parameter 2 all Uint16 Y1 value: Level (x0.1%) Y1 is calculated based on Y2 value by the formula:Y1 = Y2*a1+b1 2st - Parameter 2 all Uint16 Y2 value: Distance value (mm) 5. Configuration Using the configuration cable to connect to the sensor as below picture. Serial port configuration on the computer:* COMPort, Baudrate: 9600, Parity: None, Stop bit: 1, Data bit: 8* Modbus RTU: Reading data by Function 3 / Writing data by Function 16. 5.1 Step to configure NOTE: The Modbus configuration can only be performed in the first 60s after power up the LoRaWAN sensor. After 60s, if user can not finish the configuration process, user need to reset the power of LoRaWAN sensor again, by removing battery in at least 15s. Step 1: Install the Modbus Configurator Software in the link below https://filerun.daviteq.com/wl/?id=qK0PGNbY1g1fuxTqbFW9SXtEvCw7bpc6 How to use the Modbus configuration software Step 2: Plug the configuration cable to computer via USB port and install the driver; Step 3: Open the plastic housing with L hex key to unscrew M4 screws at the side of the housing Step 4: Plug the connector to the configuration port; Step 5:  Import the configuration file by importing the csv file: Go to MENU: FILE / Import New / => select the file with name CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0.csv (in the link below). Then click Connect; CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0 To write new value to the device:First, you need to write the password in "password for setting", after reading the value to check ok, you can write the new value AppEUI, AppKey, ...You only have 60 seconds after plugging the configuration cable or the power supply into the device for configuration. 5.2 Register table Here is the table of Data will be read by Modbus tool Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 0 0 3 5 device info WSLRW-SMT1 string Read Wireless Sensor LoRaWAN with SMT1 5 5 3 4 firmware version 1.00ddmm string Read ddmm = day / month 9 9 3 2 hardware version 1.10 string Read 11 B 3 4 lorawan protocol version 01.00.03 string Read lorawan v1.0.3 15 F 3 6 application version 01.03.00.00 string Read application server v1.3.0.0 21 15 3 6 mac layer version 04.04.02.00 string Read mac layer v4.4.2.0 27 1B 3 4 deviceEUI hex Read End Device's EUI number, used to register the product on the Network Server by OTAA 31 1F 3 4 lora appEUI hex Read Application server's EUI number is used to register the product on the Network Server by OTAA 35 23 3 8 lora appKey hex Read The number of keys used to create two security keys of the End Device, used to register the product on the Network Server by OTAA 43 2B 3 8 lora nwkSkey hex Read key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 51 33 3 8 lora appSkey hex Read End Device data encryption key number, used to register the product on the Network Server by ABP 59 3B 3 2 device address 0 uint32 Read End Device address created by Application server, used to register the product on the Network server by ABP 61 3D 3 2 network ID 0 uint32 Read Network server ID number, used to register the product on the Network server by ABP 63 3F 3 2 join mode OTAA string Read OTAA: Over-the-Air activation, ABP: Activation by Personalization 65 41 3 4 network mode PUBLIC string Read PUBLIC, PRIVATE 69 45 3 3 region code AS923 string Read 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 72 48 3 4 data rate DR2:980 string Read DR0:250, DR1:440, DR2:980, DR3:1760, DR4:3125, DR5:5470 76 4C 3 3 bandwidth BW125 string Read BW125, BW250, BW500 79 4F 3 2 spread factor SF10 string Read SF12, SF11, SF10, SF9, SF8, SF7 81 51 3 4 activation of ADR ADR OFF string Read ADR ON, ADR OFF 85 55 3 1 class A string Read 103 67 3 1 sensor type 1-255 uint16 Read 1-254: sensor type, 255: no sensor 104 68 3 1 battery level 0-3 uint16 Read 4 levels of battery capacity status 105 69 3 1 error status 0-1 uint16 Read Error code of sensor, 0: no error, 1: error 106 6A 3 1 prm1 alarm status 0-2 uint16 Read Alarm status of parameters 1, 0: none, 1: Low, 2: High 107 6B 3 1 prm2 alarm status 0-2 uint16 Read Alarm status of parameter 2 108 6C 3 2 prm1 value float Read Value of parameter 1 110 6E 3 2 prm2 value float Read Value of parameter 2 112 70 3 1 battery % 10%, 30%, 60%, 99% uint16 Read % Value of battery capacity 113 71 3 2 battery voltage 0-3.67 vdc float Read Value of battery voltage 115 73 3 2 mcu temperature °C float Read Temperature value of RF module 117 75 3 1 mcu vref 0-3.67 vdc uint16 Read Vref value of RF module 118 76 3 1 button1 status 0-1 uint16 Read Button state, 0: No button pressed, 1: Button pressed 119 77 3 1 button2 status 0-1 uint16 Read Button status, 0: No magnetic sensor detected, 1: Magnetic sensor detected Here is the table for Configuration: Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 256 100 3 / 16 1 modbus address 1-247 1 uint16 R/W Modbus address of the device 257 101 3 / 16 1 modbus baudrate 0-1 0 uint16 R/W 0: 9600, 1: 19200 258 102 3 / 16 1 modbus parity 0-2 0 uint16 R/W 0: none, 1: odd, 2: even 259 103 3 / 16 9 serial number string R/W (Password) 268 10C 3 / 16 2 password for setting uint32 R/W (Password) password 190577 270 10E 3 / 16 4 lora appEUI hex R/W (Password) Application server's EUI number, used to register the product on the Network Server by OTAA 274 112 3 / 16 8 lora appKey hex R/W (Password) The number of keys used to create two security keys of the End Device, used to register the product on the Network server by OTAA 282 11A 3 / 16 8 lora nwkSkey hex R/W (Password) key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 290 122 3 / 16 8 lora appSkey hex R/W (Password) End Device data encryption key number, used to register the product on the Network Server by ABP 298 12A 3 / 16 2 device address uint32 R/W (Password) End Device address created by Application server, used to register the product on the Network server by ABP 300 12C 3 / 16 2 network ID uint32 R/W (Password) Network server ID number, used to register the product on the Network server by ABP 302 12E 3 / 16 1 activation mode 0-1 1 uint16 R/W (Password) 1: OTAA (Over-the-Air Activation), 0: ABP (Activation by Personalization) 304 130 3 / 16 1 application port 1-255 1 uint16 R/W (Password) Port 224 is reserved for certification 317 13D 3 / 16 1 region 1-7 1 uint16 Read/Write(Password) 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 318 13E 3 / 16 1 data rate 7 uint16 R/W (Password) 0: 250 bps, 1: 440 bps, 2: 980 bps, 3: 1760 bps, 4: 3125 bps, 5: 5470 bps 319 13F 3 / 16 1 tx power 2-20 16 uint16 R/W (Password) tx power: 2,4,6,8,10,12,14,16,18,20 320 140 3 / 16 1 adaptative data rate 0-1 0 uint16 R/W (Password) Automatically adjust data rate, 0: disable, 1: enable 334 14E 3 / 16 2 cycle send data 900 uint32 R/W sec (data sending cycle) 338 152 3 / 16 1 alarm limt 44 uint16 R/W limit the number of events / day 340 154 3 / 16 2 sensor1: sampling_rate 120 uint32 R/W sec (frequency of data taken from sensor 1) 348 15C 3 / 16 2 prm1: a 1 float R/W Scale parameter "a" of prm1 350 15E 3 / 16 2 prm1: b 0 float R/W Scale parameter "b" of prm1 354 162 3 / 16 2 prm1: High Threshold 100000 float R/W High threshold value of prm1 356 164 3 / 16 2 prm1: High Hysteresis 10000 float R/W High hysteresis value of prm1 358 166 3 / 16 2 prm1: Low Threshold 0 float R/W Low threshold value of prm1 360 168 3 / 16 2 prm1: Low Hysteresis 10000 float R/W Low hysteresis value of prm1 362 16A 3 / 16 2 prm1: High Cut 100000 float R/W Upper limit value of prm1 364 16C 3 / 16 2 prm1: Low Cut 0 float R/W Lower limit value of prm1 366 16E 3 / 16 2 prm2: a 1 float R/W Scale parameter "a" of prm2 368 170 3 / 16 2 prm2: b 0 float R/W Scale parameter "b" of prm2 372 174 3 / 16 2 prm2: High Threshold 100000 float R/W High threshold value of prm2 374 176 3 / 16 2 prm2: High Hysteresis 10000 float R/W High hysteresis value of prm2 376 178 3 / 16 2 prm2: Low Threshold 0 float R/W Low threshold value of prm2 378 17A 3 / 16 2 prm2: Low Hysteresis 10000 float R/W Low hysteresis value of prm2 380 17C 3 / 16 2 prm2: High Cut 100000 float R/W Upper limit value of prm2 382 17E 3 / 16 2 prm2: Low Cut 0 float R/W Lower limit value of prm2 6. Installation 6.1 Example application 6.2 Process mounting WARNINGS:1. Please make sure the fluid is suitable with the wetted materials of the sensor. Please refer sensor specification;2. Please make sure that the operating ambient temperature is right for the sensor. Please refer to the sensor's specifications;3. Prepare the professional tools for installation. The inappropriate tools may cause damage to the sensor. 6.3 Installation location To maximize the distance of transmission, the ideal condition is Line-of-sight (LOS) between the LoRaWAN sensor and Gateway. In real life, there may be no LOS condition. However, the LoRaWAN sensor still communicates with Gateway, but the distance will be reduced significantly. ATTENTION:DO NOT install the LoRaWAN 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, cement…is acceptable. 6.4 Battery installation Steps for battery installation: Step 1: Using L hex key to unscrew M4 screws at the side of the housing and carefully pull out the top plastic housing in the vertical direction Step 2: Insert 02 x AA 1.5VDC battery, please take note the poles of the battery ATTENTION: REVERSED POLARITY OF BATTERIES IN 10 SECONDS CAN DAMAGE THE SENSOR CIRCUIT!!! Step 3: Insert the top plastic housing and locking by L hex key ATTENTION: When reinstalling the cover, pay attention to put the PCB edge into the middle slot of the box inside as shown below) 7. Troubleshooting No. Phenomena Reason Solutions 1 The BLUE LED does not blink when the battery is installed Insert the battery in the opposite direction Insert the battery in the correct way 2 The RED LED is always on Due to noise, the peripheral components (i2c, spi, uart, ..) of RF module cannot be initialized After 30s the node will automatically reset. If the noise causes the Watchdog not to initialize, remove the battery and wait for more than 10 seconds, then insert the battery again 3 The RED LED blinks continuously (10ms ON / 2s OFF) and the Node does not send RF. After more than 10 sending cycles, the Node will automatically reset Operating frequency in that country is prohibited Operating frequency in that country is limited to Data rate, Tx Power Reconfigure the allowed frequency of operation Reconfigure Data rate = DR5 / SF07, Tx Power 4 RED LED blinks continuously (10ms ON / 2s OFF) and Node sends RF continuously 3s / time but no data. After more than 10 sending cycles, the Node will automatically reset Node runs dummy sending mode => sent by Gateway to send Downlink packets when users clear Uplink and Downlink counter values on Network Server (build-in Gateway) when activated by ABP Configuration enabled by OTAA 5 The RED LED flashes 10ms ON / 10s OFF and the Node does not send RF Node activation by OTAA on Network server has not been successful Using Magnet-Key to force Node to send RF continuously for 3 seconds/time => when activating by OTAA successfully, the GREEN LED will blink after sending RF 6 The node sent RF successfully but the GREEN LED did not blink LED is broken Warranty to replace LED 7 The data packet taken from the Gateway has an incorrect value The data package is encrypted Get the decoded packet on the Application Server 8 The node sends RF and activates by ABP, on Gateway receives data but the Application server has no data The application server still stores the counter values of the previous Uplink and Downlink Delete the counter values of Uplink and Downlink on the Application server 9 The node does not send RF and the RF module is hot Insert the battery in the opposite direction Short circuit Warranty or replacement 10 The node does not send RF to Gateway according to the alarm, LED does not blink The alarm configuration is incorrect Running out of the number of alarms set for the day Check alarm configuration Check the configuration for the maximum number of alarms per day 11 The node does not send RF to Gateway when activated by the magnetic key, LED does not blink The magnetic sensor has malfunctioned Read the status of the magnetic sensor via Modbus (when powering or attaching the battery) to see if the magnetic sensor is working. 12 Node has blinked LED GREEN when sending RF but the Gateway or Application server cannot receive LoRa module on the Gateway is faulty The IP connection (4G / WiFi / ...) on the Gateway is faulty Check Gateway's LoRa status lights on Gateway Check 4G / WiFi status lights on Gateway 13 The value of the sensor is 0 and sensor_type = 0xFF Lost connection with the sensor Check sensor connection Replace the module sensor 14 RSSI is weak and often loses data The distance between Node and Gateway is far or there are many obstructions Connection to Antenna problem Install metal nodes or in metal cabinets Configure Data rate = DR0 / SF12 Check Antenna position Install Node in a well-ventilated location 8. Support contacts Manufacturer Daviteq Technologies IncNo.11 Street 2G, Nam Hung Vuong Res., An Lac Ward, Binh Tan Dist., Ho Chi Minh City, Vietnam.Tel: +84-28-6268.2523/4 (ext.122) Email: info@daviteq.com | www.daviteq.com Distributor in Australia and New Zealand Templogger Pty Ltd Tel: 1800 LOGGER Email: contact@templogger.net USER GUIDE FOR ULTRASONIC LEVEL SENSOR FOR TRASH BIN WSLRW-ULB THIS IS OBSOLETE MANUAL Please access https://www.iot.daviteq.com/wireless-sensors for updated manual WSLRW-ULB-MN-EN-01 MAR-2021 This document is applied for the following products SKU WSLRW-ULB HW Ver. 1.1 FW Ver. 1.2 Item Code WSLRW-ULB-9-01 Wireless LoRaWAN Ultrasonic Level Sensor for Trash bin, Internal antenna, 4500mm range, Type AA battery 1.5VDC, IP67, 900-930 Mhz for KR920, AS923, AU915, US915 WSLRW-ULB-8-01 Wireless LoRaWAN Ultrasonic Level Sensor for Trash bin, Internal antenna, 4500mm range, Type AA battery 1.5 VDC, IP67, 860-870 Mhz for EU868, IN865, RU864 0. Configuration Check List STEP 1: Configure End Device (Using Modbus Configuration Cable) Setting value (Example) 1. Select region AS923, IN865, EU868,.. (refer to register address 317) 2. End Device Operation OTAA or ABP OTAA Write AppEUI information from Application Server to Lorawan End Device; Write AppKey (created by user) information for Lorawan End Device and Application Server. ABP Write DevEUI information from Application Server to Lorawan end device; write Network Session Key and App Session Key (created by user) information to Lorawan end device (and Application Server). 3. Configure "cycle send data" 900 sec (Defaut) 4. Configure "sensor sampling_rate" 120 sec (Defaut) 5. Configure parameters of sensor (Refer to Check data configuration table) STEP 2:  Configure the operation of LoRaWAN Gateway (Ex: URSALINK Gateway) 1. Configure the information in the General tab Server address, Server port (For more information) 2. Configure the information in the Radio tab Select the Region Region (Other parameters to default) STEP 3:  Configure the operation of LoRaWAN Gateway on Network Server (Ex: URSALINK Gateway with Thethingsnetwork) 1. Gateway ID registration Gateway ID is the GatewayEUI information on the Gateway 2. Frequency Plan parameters configuration Asia 920-923MHz, Europe 868MHz,... 3. Router parameters configuration 4. Check the connection of the gateway to the network server The Gateway status LED lights up and displays the message "Status: conneted" on the Thethingsnetwork STEP 4:  Configure the operation of Application Server on Network Server 1. App ID registration 2. Handler parameters configuration STEP 5: Register Lorawan End Device on Application Server on Thethingsnetwork 1. ID Registration 2.Select operation mode OTAA or ABP OTAA Configure parameters DevEUI and AppKEY ABP Configure parameters Device Address, Network Session Key, App Session Key 1. Functions Change Log HW Ver. FW Ver. Release Date Functions Change 1.1 1.0.0 13-OCT-2020 1.1 1.1.0 13-NOV-2020 Payload updates. 1.1 1.2 MAR-2021 Update new design and firmware improvements. 2. Introduction WSLRW-ULB is a LoRaWAN ultrasonic level sensor to measure solid surface level in trash bin for waste management systems ... This level sensor uses ultrasonic technology to measure the solid surface of waste, the principle is to measure the time of flight of the ultrasound pulse in the air environment. The ultrasound pulse will be ejected from ultrasonic transducer, go thru the air and reach the solid surface of the waste, then reflected back to the ultrasonic transducer, the measuring circuit will measure the flight time of the pulse then calculated distance from the transducer to the surface. The ultra-low power design and smart firmware allow the sensor to last for up to 10 years with just 2 x AA batteries (depending on configuration). The sensor will transmit data over kilo-meters away to the LoRaWAN gateway, any brand on the market. 3. Specification SENSORS SPECIFICATION: Sensor Ultrasonic sensor Measurement range 300 .. 4500 mm Resolution & accuracy 1.0mm, +/- 10 mm Sensor sampling rate configurable from 10s up to 3600s Alarm setting setting the alarm threshold for calculated value LoRaWAN SPECIFICATION: Data rate 250bps .. 5470bps Antenna Internal Antenna 2.67 dbi Battery 02 x AA size 1.5, battery not included RF Frequency and Power 860..930Mhz, +14 .. +20 dBm, configurable for zones: EU868, IN865, RU864, KR920, AS923, AU915, US915 Protocol LoRaWAN, class A Data sending modes Interval time and when alarm occurred RF Module complies to ETSI EN 300 220, EN 303 204 (Europe) FCC CFR47 Part15 (US), ARIB STD-T108 (Japan) Vietnam Type Approval Working temperature -15oC..+60oC (using L91 Energizer battery) Dimensions H180xW50xD40 Net-weight 250 grams Housing Polycarbonate & POM plastic, IP67 4. Operation Principle 4.1 LoRaWAN protocol specifications 4.1.1 LoRaWAN Sensor protocol specifications LoRaWAN Protocol Version 1.0.3 Application Server Version 1.3.0.0 MAC Layer Version 4.4.2.0 Radio Standards: LoRa Alliance Certified LoRaWAN Zone: LoRa Alliance AS923, KR920, AU915, US915, EU868, IN865, RU864 Class A Join Active: OTAA / ABP Network Mode: Public Network / Private Network Tx Power: up to 20 dBm Frequency: 860 - 930Mhz Date rate: 250 bps - 5kbps Spreading factor: SF12 - SF7 Bandwidth: 125 kHz Unconfirmed-data message LoRaWAN application port for certification: 224 4.1.2 Data rate of LoRaWAN Sensor Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR2 980 SF10 125 AS923, AU915 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 980 SF10 125 US915 DR1 1760 SF9 125 DR2 3125 SF8 125 DR3 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 250 SF12 125 KR920, EU868, IN865, RU864 DR1 440 SF11 125 DR2 980 SF10 125 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 4.1.3 Tx power of LoRaWAN sensor Max EIRP (dBm) Max Tx Power (dBm) Region 16 16 AS923 14 14 KR920 30 20 AU915 30 20 US915 16 16 EU868 30 20 IN865 16 16 RU864 4.2 The principle of operation of the LoRaWAN sensor When starting the power supply, the LoRaWAN sensor has 60 seconds to allow configuration to operate via the Configuration Cable with the Modbus RTU protocol. After 60 seconds, the first packet will be sent, then the LoRaWAN sensor will send the next packets in the following cases: Case 1: When it reaches the frequency of taking data, the LoRaWAN sensor will wake up to measure and calculate. Then: If the measured value exceeds the High or Low setting thresholds, the packet will be sent to the Gateway and then asleep; If NOT then sleep without sending data. NOTE: Once sending the data to Gateway by this alarm event, the timer of sending time interval will be reset; Case 2: When the sending time interval is reached, the LoRaWAN sensor wakes up to measure and calculate and send data to Gateway immediately, regardless of value. Case 3: By using the magnet key, the LoRaWAN sensor can be triggered to send data to Gateway immediately. NOTE: The time between sending data for Class A is at least 3 seconds 4.3 Principle of operation LoRaWAN Network The LoRaWAN Gateway function is Packet Forwarder so: Between Gateway and End Device: Gateway receives data packets from End Device via RF connection, so it is recommended to configure Radio parameters (Note: the packet that Gateway receives is encrypted) Between Gateway and Network Server: Gateway forwards data packets to the Network server via an IP connection, so it is recommended to configure Network parameters such as Server Address, Server Uplink Port, Server Downlink Port,... LoRaWAN Network is secured as follows: Network section key (NwkSKey) to ensure the security of communications on the Network The application session key (AppSKey) to ensure data security between End Device and Application Server Special keys of the device such as DevEUI, AppEUI, Gateway EUI, Device Address. Therefore, the data packet that the Gateway receives is encrypted and decrypted on the Application server. To End Device connect to the Network server, you need to register in the following two ways: Activation with OTAA (Over-the-Air activation): is the process of joining the Network automatically. Previously, both End Device and Application Server installed the same DevEUI code, AppEUI, and AppKey. During activation, AppKey will generate 2 security keys for End Device and Network, which are: The network session key (NwkSKey): is the key to secure communication commands on the MAC layer between the End Device and the Network server. The application session key (AppSKey): is the key to secure data packets between the End Device and Application server. ATTENTIONS:* OTAA mode must be successfully activated in order for the End Device to send data packets to the Network through the Gateway;* OTAA mode only need to activate once, if the device is reset or battery replacement, it will activate OTAA again;* When the End Device is connected to the Network server, whether the Gateway is reset or the power is restarted, it will not need to activate OTAA. Activation by ABP (Activation by Personalization): is the process of joining the Network manually. Device Address, Network session key (NwkSKey), and Application session key (AppSKey) codes must be stored inside the End Device and Application server, so when the End Device sends data packets to the network server, it will also send the security codes to activate. 4.4 Configure the LoRaWAN Network 4.4.1 Configure End Device operation according to OTAA Configuration parameters for the End Device to be activated by OTAA as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode OTAA Device activation type on Network Server DevEUI 34 35 31 31 4B 37 75 12 Device ID's unique ID number => Set this ID number for the Application server AppEUI 70 B3 D5 7E D0 02 D5 0B Application server's unique ID number (random or user-generated)=> Set this ID number for End Device AppKey 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C Key Number for generating 2 NwkSKey and AppSKey security keys created by the user (factory-created by default)=> Used to install for both the Device and Application Server End ATTENTIONS:* The AppEUI number from Application Server => then installed for the End Device. AppEUI is randomly generated by the Application server or by the user;* The number of AppKeys during OTAA activation will generate two security keys, Lora NwkSKey and AppSKey, which are used for both End Device and Network. 4.4.2 Configure End Device operation according to ABP Configuration parameters for the End Device to be activated by ABP as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode ABP Device activation type on Network Server Device Address 12 34 56 78 End Device Address created by the Application server=> Set Device Address for End Device NwkSKey (Network session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C NwkSKey number created by the user to install and use for both End Device and Application Server AppSKey (Application session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C AppSKey number generated by the user to install for both End Device and Application Server 4.4.3 Configure Gateway operations 4.4.3.1 Configure the Gateway to receive data packets from the End Device. Radio settings need to be set as:* Region code: AS923, KR920, AU915, US915, EU868, IN865, RU864* Center Frequency, Channels, Bandwidth (recommends using the default configuration created by the system) Let's take an example to configure the Gateway operation of URSALINK (Model: UG85-L00E-915) 4.4.3.2 Configure the Gateway to communicate with the Public Network Server Let's take an example of configuring Gateway UG85 to connect with "thethingsnetwork.org" in Asia: Currently, thethingsnetwork only supports the connection protocol with Gateway is Semtech UDP Packet Forwarder. https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Parameter settings Setting value (example) Description Gateway EUI 24e124fffef038fd Gateway's unique ID number=> Set this ID number for Application server Server Address router.as1.thethings.network Semtech server address: https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Router regional Asia: router.as1.thethings.network Router regional India: ttn.thingsconnected.net Ursalink server address: localhost Server Uplink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Server Downlink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Network mode Public LoRaWAN 4.4.4 Register the Application server on the Public Network "thethingsnetwork.org" 4.4.4.1 Register the Gateway on Public Network "thethingsnetwork.org" as shown below: The current network only supports the Gateway connection protocol, "Semtech UDP protocol" is Semtech UDP Packet Forwarder. Then power the Gateway and observe the message "Status: connected" => Registration of the Gateway on the Application successfully. 4.4.4.2 Register Application on Public Network "thethingsnetwork.org" as shown below: 4.4.4.3 Register End Device on Application: 4.5 LED meaning RED LED: Fixed ON: due to noise caused peripheral components (i2c, spi, uart, timer, rtc, wdt, ...) do not initialize. Flashing 10ms ON / 10s OFF: Activation by OTAA on the Network server failed. Flashing 10ms ON / 2s OFF:  Sending a data packet to Gateway failed. GREEN LED: Flashing 100ms ON / OFF when sending a data packet to Gateway. BLUE LED: Flashing 1s ON / 1s OFF for the first 60 seconds when booting (insert batteries or connected external sources), after 60 seconds OFF. ON during the LoRaWAN sensor receives data packets from the Network server and OFF when received. 4.6 The Effective Detection Range 4.7 Process of measurement When the LoRa sensor wakes up, it will supply power to the internal or external sensor so that the sensor can start measuring. After measuring successfully it will turn off the power to the sensor for energy saving. The measured value is the raw value of the sensor. The measured value can be scaled according to the following formula: Y = aX + b X: the raw value from the sensor Y: the calculated value will be sent to LoRaWAN Gateway in the payload data. a: constant (default value is 1) b: constant (default value is 0) So, if there is no user setting for a and b ==> Y = X The Y value will be compared with Lo and Hi threshold. Please refer below the graph of alarm processing. 4.8 Calibration Figure – Ultrasonic Level Transmitter Calibration DB: Dead band 0..280 mm (This is a short range in front of the ultrasonic sensor can not measure distances) H: Maximum measuring distance ( Span ) D: Distance For example: Trash bin with maximum height to be measured 1200mm (H) and the maximum height to measure is 300mm (larger than DB 280mm), then: From here we can look up the trash level corresponding to the measured distance of the sensor by the formula: Y = aX + b. Where: X is the measured distance (mm) and Y is the level (‰) Distance (mm) Level (‰) 300 1000 400 889 500 778 600 667 700 556 800 445 900 333 1000 222 1100 111 1200 0 Use the offline configuration tool to configure sigfox sensor. Write in the sensor the parameters a1 and b1. Refer to Resigter table for more details. 4.9 Payload Data The following is the format of payload data that will be sent to the LoRaWAN Gateway. Sensor type (1 byte) Status (1 byte) 1st - Parameter (2 bytes) 2st - Parameter (2 bytes) Meaning of Data in the Payload Data Size (byte) Bit Format Meaning Sensor type 1 all Uint8 Sensor type = 0x0E means LoRaWAN Node ULBSensor type = 0xFF means no sensor Status: battery level 1 Bit 7 and 6 Uint8 Battery capacity in 04 levels 11: battery level 4 (99%) 10: battery level 3 (60%) 01: battery level 2 (30%) 00: battery level 1 (10%) Status: error Bit 5 and 4 Node status 01: error 00: no error Status: alarm 1 Bit 3 and 2 Alarm status of 1st - Parameter (Y1 value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm Status: alarm 2 Bit 1 and 0 Alarm status of 2st - Parameter (Y2 value)11 : Hi alarm01 : Lo alarm00 : No alarm 1st - Parameter 2 all Uint16 Y1 value: Level (x0.1%) Y1 is calculated based on Y2 value by the formula:Y1 = Y2*a1+b1 2st - Parameter 2 all Uint16 Y2 value: Distance value (mm) 5. Configuration Using the configuration cable to connect to the sensor as below picture. Serial port configuration on the computer:* COMPort, Baudrate: 9600, Parity: None, Stop bit: 1, Data bit: 8* Modbus RTU: Reading data by Function 3 / Writing data by Function 16. 5.1 Step to configure NOTE: The Modbus configuration can only be performed in the first 60s after power up the LoRaWAN sensor. After 60s, if user can not finish the configuration process, user need to reset the power of LoRaWAN sensor again, by removing battery in at least 15s. Step 1: Install the Modbus Configurator Software in the link below https://filerun.daviteq.com/wl/?id=qK0PGNbY1g1fuxTqbFW9SXtEvCw7bpc6 How to use the Modbus configuration software Step 2: Plug the configuration cable to computer via USB port and install the driver; Step 3: Open the plastic housing with L hex key to unscrew M4 screws at the side of the housing Step 4: Plug the connector to the configuration port; Step 5:  Import the configuration file by importing the csv file: Go to MENU: FILE / Import New / => select the file with name CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0.csv (in the link below). Then click Connect; CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0 To write new value to the device:First, you need to write the password in "password for setting", after reading the value to check ok, you can write the new value AppEUI, AppKey, ...You only have 60 seconds after plugging the configuration cable or the power supply into the device for configuration. 5.2 Register table Here is the table of Data will be read by Modbus tool Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 0 0 3 5 device info WSLRW-SMT1 string Read Wireless Sensor LoRaWAN with SMT1 5 5 3 4 firmware version 1.00ddmm string Read ddmm = day / month 9 9 3 2 hardware version 1.10 string Read 11 B 3 4 lorawan protocol version 01.00.03 string Read lorawan v1.0.3 15 F 3 6 application version 01.03.00.00 string Read application server v1.3.0.0 21 15 3 6 mac layer version 04.04.02.00 string Read mac layer v4.4.2.0 27 1B 3 4 deviceEUI hex Read End Device's EUI number, used to register the product on the Network Server by OTAA 31 1F 3 4 lora appEUI hex Read Application server's EUI number is used to register the product on the Network Server by OTAA 35 23 3 8 lora appKey hex Read The number of keys used to create two security keys of the End Device, used to register the product on the Network Server by OTAA 43 2B 3 8 lora nwkSkey hex Read key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 51 33 3 8 lora appSkey hex Read End Device data encryption key number, used to register the product on the Network Server by ABP 59 3B 3 2 device address 0 uint32 Read End Device address created by Application server, used to register the product on the Network server by ABP 61 3D 3 2 network ID 0 uint32 Read Network server ID number, used to register the product on the Network server by ABP 63 3F 3 2 join mode OTAA string Read OTAA: Over-the-Air activation, ABP: Activation by Personalization 65 41 3 4 network mode PUBLIC string Read PUBLIC, PRIVATE 69 45 3 3 region code AS923 string Read 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 72 48 3 4 data rate DR2:980 string Read DR0:250, DR1:440, DR2:980, DR3:1760, DR4:3125, DR5:5470 76 4C 3 3 bandwidth BW125 string Read BW125, BW250, BW500 79 4F 3 2 spread factor SF10 string Read SF12, SF11, SF10, SF9, SF8, SF7 81 51 3 4 activation of ADR ADR OFF string Read ADR ON, ADR OFF 85 55 3 1 class A string Read 103 67 3 1 sensor type 1-255 uint16 Read 1-254: sensor type, 255: no sensor 104 68 3 1 battery level 0-3 uint16 Read 4 levels of battery capacity status 105 69 3 1 error status 0-1 uint16 Read Error code of sensor, 0: no error, 1: error 106 6A 3 1 prm1 alarm status 0-2 uint16 Read Alarm status of parameters 1, 0: none, 1: Low, 2: High 107 6B 3 1 prm2 alarm status 0-2 uint16 Read Alarm status of parameter 2 108 6C 3 2 prm1 value float Read Value of parameter 1 110 6E 3 2 prm2 value float Read Value of parameter 2 112 70 3 1 battery % 10%, 30%, 60%, 99% uint16 Read % Value of battery capacity 113 71 3 2 battery voltage 0-3.67 vdc float Read Value of battery voltage 115 73 3 2 mcu temperature °C float Read Temperature value of RF module 117 75 3 1 mcu vref 0-3.67 vdc uint16 Read Vref value of RF module 118 76 3 1 button1 status 0-1 uint16 Read Button state, 0: No button pressed, 1: Button pressed 119 77 3 1 button2 status 0-1 uint16 Read Button status, 0: No magnetic sensor detected, 1: Magnetic sensor detected Here is the table for Configuration: Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 256 100 3 / 16 1 modbus address 1-247 1 uint16 R/W Modbus address of the device 257 101 3 / 16 1 modbus baudrate 0-1 0 uint16 R/W 0: 9600, 1: 19200 258 102 3 / 16 1 modbus parity 0-2 0 uint16 R/W 0: none, 1: odd, 2: even 259 103 3 / 16 9 serial number string R/W (Password) 268 10C 3 / 16 2 password for setting uint32 R/W (Password) password 190577 270 10E 3 / 16 4 lora appEUI hex R/W (Password) Application server's EUI number, used to register the product on the Network Server by OTAA 274 112 3 / 16 8 lora appKey hex R/W (Password) The number of keys used to create two security keys of the End Device, used to register the product on the Network server by OTAA 282 11A 3 / 16 8 lora nwkSkey hex R/W (Password) key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 290 122 3 / 16 8 lora appSkey hex R/W (Password) End Device data encryption key number, used to register the product on the Network Server by ABP 298 12A 3 / 16 2 device address uint32 R/W (Password) End Device address created by Application server, used to register the product on the Network server by ABP 300 12C 3 / 16 2 network ID uint32 R/W (Password) Network server ID number, used to register the product on the Network server by ABP 302 12E 3 / 16 1 activation mode 0-1 1 uint16 R/W (Password) 1: OTAA (Over-the-Air Activation), 0: ABP (Activation by Personalization) 304 130 3 / 16 1 application port 1-255 1 uint16 R/W (Password) Port 224 is reserved for certification 317 13D 3 / 16 1 region 1-7 1 uint16 Read/Write(Password) 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 318 13E 3 / 16 1 data rate 7 uint16 R/W (Password) 0: 250 bps, 1: 440 bps, 2: 980 bps, 3: 1760 bps, 4: 3125 bps, 5: 5470 bps 319 13F 3 / 16 1 tx power 2-20 16 uint16 R/W (Password) tx power: 2,4,6,8,10,12,14,16,18,20 320 140 3 / 16 1 adaptative data rate 0-1 0 uint16 R/W (Password) Automatically adjust data rate, 0: disable, 1: enable 334 14E 3 / 16 2 cycle send data 900 uint32 R/W sec (data sending cycle) 338 152 3 / 16 1 alarm limt 44 uint16 R/W limit the number of events / day 340 154 3 / 16 2 sensor1: sampling_rate 120 uint32 R/W sec (frequency of data taken from sensor 1) 348 15C 3 / 16 2 prm1: a 1 float R/W Scale parameter "a" of prm1 350 15E 3 / 16 2 prm1: b 0 float R/W Scale parameter "b" of prm1 354 162 3 / 16 2 prm1: High Threshold 100000 float R/W High threshold value of prm1 356 164 3 / 16 2 prm1: High Hysteresis 10000 float R/W High hysteresis value of prm1 358 166 3 / 16 2 prm1: Low Threshold 0 float R/W Low threshold value of prm1 360 168 3 / 16 2 prm1: Low Hysteresis 10000 float R/W Low hysteresis value of prm1 362 16A 3 / 16 2 prm1: High Cut 100000 float R/W Upper limit value of prm1 364 16C 3 / 16 2 prm1: Low Cut 0 float R/W Lower limit value of prm1 366 16E 3 / 16 2 prm2: a 1 float R/W Scale parameter "a" of prm2 368 170 3 / 16 2 prm2: b 0 float R/W Scale parameter "b" of prm2 372 174 3 / 16 2 prm2: High Threshold 100000 float R/W High threshold value of prm2 374 176 3 / 16 2 prm2: High Hysteresis 10000 float R/W High hysteresis value of prm2 376 178 3 / 16 2 prm2: Low Threshold 0 float R/W Low threshold value of prm2 378 17A 3 / 16 2 prm2: Low Hysteresis 10000 float R/W Low hysteresis value of prm2 380 17C 3 / 16 2 prm2: High Cut 100000 float R/W Upper limit value of prm2 382 17E 3 / 16 2 prm2: Low Cut 0 float R/W Lower limit value of prm2 6. Installation 6.1 Example application 6.2 Dimensions WARNINGS:1. Please make sure the material is suitable with the materials of the sensor. Please refer sensor specification;2. Please make sure that the operating ambient temperature is right for the sensor. Please refer to the sensor's specifications;3. Prepare the professional tools for installation. The inappropriate tools may cause damage to the sensor. 6.3 Bracket mounting 6.4 Installation location To maximize the distance of transmission, the ideal condition is Line-of-sight (LOS) between the LoRaWAN sensor and Gateway. In real life, there may be no LOS condition. However, the LoRaWAN sensor still communicates with Gateway, but the distance will be reduced significantly. ATTENTION:DO NOT install the LoRaWAN 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, cement…is acceptable. 6.4 Battery installation Steps for battery installation: Step 1: Using L hex key to unscrew M4 screws at the side of the housing and carefully pull out the top plastic housing in the vertical direction Step 2: Insert 02 x AA 1.5VDC battery, please take note the poles of the battery ATTENTION: REVERSED POLARITY OF BATTERIES IN 10 SECONDS CAN DAMAGE THE SENSOR CIRCUIT!!! Step 3: Insert the top plastic housing and locking by L hex key ATTENTION: When reinstalling the cover, pay attention to put the PCB edge into the middle slot of the box inside as shown below) 7. Troubleshooting No. Phenomena Reason Solutions 1 The BLUE LED does not blink when the battery is installed Insert the battery in the opposite direction Insert the battery in the correct way 2 The RED LED is always on Due to noise, the peripheral components (i2c, spi, uart, ..) of RF module cannot be initialized After 30s the node will automatically reset. If the noise causes the Watchdog not to initialize, remove the battery and wait for more than 10 seconds, then insert the battery again 3 The RED LED blinks continuously (10ms ON / 2s OFF) and the Node does not send RF. After more than 10 sending cycles, the Node will automatically reset Operating frequency in that country is prohibited Operating frequency in that country is limited to Data rate, Tx Power Reconfigure the allowed frequency of operation Reconfigure Data rate = DR5 / SF07, Tx Power 4 RED LED blinks continuously (10ms ON / 2s OFF) and Node sends RF continuously 3s / time but no data. After more than 10 sending cycles, the Node will automatically reset Node runs dummy sending mode => sent by Gateway to send Downlink packets when users clear Uplink and Downlink counter values on Network Server (build-in Gateway) when activated by ABP Configuration enabled by OTAA 5 The RED LED flashes 10ms ON / 10s OFF and the Node does not send RF Node activation by OTAA on Network server has not been successful Using Magnet-Key to force Node to send RF continuously for 3 seconds/time => when activating by OTAA successfully, the GREEN LED will blink after sending RF 6 The node sent RF successfully but the GREEN LED did not blink LED is broken Warranty to replace LED 7 The data packet taken from the Gateway has an incorrect value The data package is encrypted Get the decoded packet on the Application Server 8 The node sends RF and activates by ABP, on Gateway receives data but the Application server has no data The application server still stores the counter values of the previous Uplink and Downlink Delete the counter values of Uplink and Downlink on the Application server 9 The node does not send RF and the RF module is hot Insert the battery in the opposite direction Short circuit Warranty or replacement 10 The node does not send RF to Gateway according to the alarm, LED does not blink The alarm configuration is incorrect Running out of the number of alarms set for the day Check alarm configuration Check the configuration for the maximum number of alarms per day 11 The node does not send RF to Gateway when activated by the magnetic key, LED does not blink The magnetic sensor has malfunctioned Read the status of the magnetic sensor via Modbus (when powering or attaching the battery) to see if the magnetic sensor is working. 12 Node has blinked LED GREEN when sending RF but the Gateway or Application server cannot receive LoRa module on the Gateway is faulty The IP connection (4G / WiFi / ...) on the Gateway is faulty Check Gateway's LoRa status lights on Gateway Check 4G / WiFi status lights on Gateway 13 The value of the sensor is 0 and sensor_type = 0xFF Lost connection with the sensor Check sensor connection Replace the module sensor 14 RSSI is weak and often loses data The distance between Node and Gateway is far or there are many obstructions Connection to Antenna problem Install metal nodes or in metal cabinets Configure Data rate = DR0 / SF12 Check Antenna position Install Node in a well-ventilated location 8. Support contacts Manufacturer Daviteq Technologies IncNo.11 Street 2G, Nam Hung Vuong Res., An Lac Ward, Binh Tan Dist., Ho Chi Minh City, Vietnam.Tel: +84-28-6268.2523/4 (ext.122) Email: info@daviteq.com | www.daviteq.com Distributor in Australia and New Zealand Templogger Pty Ltd Tel: 1800 LOGGER Email: contact@templogger.net Sample Decoder for Payload of LoRaWAN Sensor WSLRW-MN-EN APR-2020 Sample Decoder for Payload of LoRaWAN Sensor THIS IS OBSOLETE MANUAL Please access https://www.iot.daviteq.com/wireless-sensors for updated manual 1. Decoder sample You can download HERE /* ******************************************* bytes to number* https://docs.microsoft.com/en-us/cpp/cpp/data-type-ranges?view=msvc-160********************************************/function bytesToFloat(bytes) {// Reference link:https://stackoverflow.com/a/37471538 by Ilya Bursovvar bits = bytes[0]<<24 | bytes[1]<<16 | bytes[2]<<8 | bytes[3];var sign = (bits>>>31 === 0) ? 1.0 : -1.0;var e = bits>>>23 & 0xff;var m = (e === 0) ? (bits & 0x7fffff)<<1 : (bits & 0x7fffff) | 0x800000;var f = sign * m * Math.pow(2, e - 150);return f;}function bytesToUnsignedInt32(bytes) {var v = bytes[0] << 24 | bytes[1] << 16 | bytes[2] << 8 | bytes[3];return v;}function bytesToInt32(bytes) {// 0...31: representation bits// 31: sign bitvar v = bytes[0] << 24 | bytes[1] << 16 | bytes[2] << 8 | bytes[3];return v > 0x7FFFFFFF ? v - 0x0100000000 : v; }function bytesToUnsignedInt8(bytes) {var v = bytes[0];return v;}function bytesToInt8(bytes) {// 0...7: representation bits// 8: sign bitvar v = bytes[0];return v > 0x7f ? v - 0x0100 : v;}function bytesToUnsignedInt16(bytes) {var v = bytes[0] << 8 | bytes[1];return v;}function bytesToInt16(bytes) {// 0...14: representation bits// 15: sign bitvar v = (bytes[0] << 8) | bytes[1];return v > 0x7fff ? v - 0x010000 : v;}/**----------------------------------**/ /**------GLOBIOTS SENSOR TYPE-------**/var I2C_ATE_SENSOR_TYPE = 0x01;var I2C_ATH_SENSOR_TYPE = 0x02;var I2C_PPS_SENSOR_TYPE = 0x04;var SMT01_SENSOR_TYPE = 0x0C;var LIQUID_LEVEL_SENSOR_TYPE = 0x0E;var I2C_TILT_SENSOR_TYPE = 0x0D;/**--------------------------------**/var STATUS_BATTERY_BIT_MASK = 0xC0;var STATUS_ERROR_BIT_MASK = 0x30;var STATUS_ALARM_1_BIT_MASK = 0x0C;var STATUS_ALARM_2_BIT_MASK = 0x03;var STATUS_ALARM_3_BIT_MASK = 0x03; var GLOBIOTS_DEFINED_DATA = {};var listParameterMapping = [];var sensorType = bytes[0];var batteryLevel = (bytes[1] & STATUS_BATTERY_BIT_MASK) >> 6;var sensorError = (bytes[1] & STATUS_ERROR_BIT_MASK) >> 4;var parameter1Alarm = (bytes[1] & STATUS_ALARM_1_BIT_MASK) >> 2; //1st - Parameter alarm statusvar parameter2Alarm = bytes[1] & STATUS_ALARM_2_BIT_MASK; //2nd - Parameter alarm status /**-----------------------GLOBIOTS MAPPING DATA-----------------------**/var parameterMapping = {};parameterMapping["PARAMETER_6000"] = batteryLevel;parameterMapping["PARAMETER_6006"] = sensorError;parameterMapping["PARAMETER_6007"] = sensorType;if(sensorType === I2C_ATE_SENSOR_TYPE){var temperature = bytesToFloat(bytes.slice(2, 6)); //1st - ParameterparameterMapping["PARAMETER_6002"] = temperature;parameterMapping["ALARM_6002"] = parameter1Alarm;} else if(sensorType === I2C_ATH_SENSOR_TYPE){var humidity = bytesToFloat(bytes.slice(2, 6)); //1st - Parametervar temperature = bytesToFloat(bytes.slice(6, 11)); //2nd - ParameterparameterMapping["PARAMETER_6002"] = humidity;parameterMapping["PARAMETER_6008"] = temperature;parameterMapping["ALARM_6002"] = parameter1Alarm;parameterMapping["ALARM_6008"] = parameter2Alarm;} else if(sensorType === I2C_PPS_SENSOR_TYPE){var processPressure = bytesToFloat(bytes.slice(2, 6)); //1st - Parametervar temperature = bytesToFloat(bytes.slice(6, 11)); //2nd - ParameterparameterMapping["PARAMETER_6002"] = processPressure;parameterMapping["PARAMETER_6008"] = temperature;parameterMapping["ALARM_6002"] = parameter1Alarm;parameterMapping["ALARM_6008"] = parameter2Alarm;} else if(sensorType === SMT01_SENSOR_TYPE){var soilMoisture = bytesToFloat(bytes.slice(2, 4)); //1st - Parametervar temperature = bytesToFloat(bytes.slice(4, 6)); //2nd - ParameterparameterMapping["PARAMETER_6002"] = soilMoisture;parameterMapping["PARAMETER_6008"] = temperature;parameterMapping["ALARM_6002"] = parameter1Alarm;parameterMapping["ALARM_6008"] = parameter2Alarm;} else if(sensorType === LIQUID_LEVEL_SENSOR_TYPE){var level = bytesToUnsignedInt16(bytes.slice(2, 4)); //1st - Parametervar distance = bytesToUnsignedInt16(bytes.slice(4, 6)); //1st - ParameterparameterMapping["PARAMETER_6002"] = level;parameterMapping["PARAMETER_6008"] = distance;parameterMapping["ALARM_6002"] = parameter1Alarm;parameterMapping["ALARM_6008"] = parameter2Alarm;} else if(sensorType === I2C_TILT_SENSOR_TYPE){var parameter3Alarm = bytes[2] & STATUS_ALARM_3_BIT_MASK;var realX = bytesToInt16(bytes.slice(3, 5)) / 10 ; //1st - Parametervar realY = bytesToInt16(bytes.slice(5, 7)) / 10; //2nd - Parametervar realZ = bytesToInt16(bytes.slice(7, 9)) / 10; //3rd - Parameter parameterMapping["PARAMETER_6002"] = realX;parameterMapping["PARAMETER_6008"] = realY;parameterMapping["PARAMETER_6ACD"] = realZ;parameterMapping["ALARM_6002"] = parameter1Alarm;parameterMapping["ALARM_6008"] = parameter2Alarm;parameterMapping["ALARM_6ACD"] = parameter3Alarm;} listParameterMapping.push(parameterMapping);/**------------------------------------------------------------------**/GLOBIOTS_DEFINED_DATA['parameterMappings'] = listParameterMapping;return GLOBIOTS_DEFINED_DATA; 2. Place to write decoder 3. Test decoder Write in the payload you need to decode and then run the test 4. Support contacts Manufacturer Daviteq Technologies IncNo.11 Street 2G, Nam Hung Vuong Res., An Lac Ward, Binh Tan Dist., Ho Chi Minh City, Vietnam.Tel: +84-28-6268.2523/4 (ext.122) Email: info@daviteq.com | www.daviteq.com Distributor in Australia and New Zealand Templogger Pty Ltd Tel: 1800 LOGGER Email: contact@templogger.net USER GUIDE FOR ULTRASONIC LEVEL SENSOR FOR TRASH BIN WSLRW-ULA THIS IS OBSOLETE MANUAL Please access https://www.iot.daviteq.com/wireless-sensors for updated manual WSLRW-ULA-MN-EN-01 MAR-2021 This document is applied for the following products SKU WSLRW-ULA HW Ver. 1.1 FW Ver. 1.2 Item Code WSLRW-ULA-9-01 Wireless LoRaWAN Ultrasonic Level Sensor for Trash bin, Internal antenna, 1500mm range, Type AA battery 1.5VDC, IP67, 900-930 Mhz for KR920, AS923, AU915, US915 WSLRW-ULA-8-01 Wireless LoRaWAN Ultrasonic Level Sensor for Trash bin, Internal antenna, 1500mm range, Type AA battery 1.5 VDC, IP67, 860-870 Mhz for EU868, IN865, RU864 0. Configuration Check List STEP 1: Configure End Device (Using Modbus Configuration Cable) Setting value (Example) 1. Select region AS923, IN865, EU868,.. (refer to register address 317) 2. End Device Operation OTAA or ABP OTAA Write AppEUI information from Application Server to Lorawan End Device; Write AppKey (created by user) information for Lorawan End Device and Application Server. ABP Write DevEUI information from Application Server to Lorawan end device; write Network Session Key and App Session Key (created by user) information to Lorawan end device (and Application Server). 3. Configure "cycle send data" 900 sec (Defaut) 4. Configure "sensor sampling_rate" 120 sec (Defaut) 5. Configure parameters of sensor (Refer to parameter configuration table) STEP 2:  Configure the operation of LoRaWAN Gateway (Ex: URSALINK Gateway) 1. Configure the information in the General tab Server address, Server port (For more information) 2. Configure the information in the Radio tab Select the Region Region (Other parameters to default) STEP 3:  Configure the operation of LoRaWAN Gateway on Network Server (Ex: URSALINK Gateway with Thethingsnetwork) 1. Gateway ID registration Gateway ID is the GatewayEUI information on the Gateway 2. Frequency Plan parameters configuration Asia 920-923MHz, Europe 868MHz,... 3. Router parameters configuration 4. Check the connection of the gateway to the network server The Gateway status LED lights up and displays the message "Status: conneted" on the Thethingsnetwork STEP 4:  Configure the operation of Application Server on Network Server 1. App ID registration 2. Handler parameters configuration STEP 5: Register Lorawan End Device on Application Server on Thethingsnetwork 1. ID Registration 2.Select operation mode OTAA or ABP OTAA Configure parameters DevEUI and AppKEY ABP Configure parameters Device Address, Network Session Key, App Session Key 1. Functions Change Log HW Ver. FW Ver. Release Date Functions Change 1.1 1.0.0 13-OCT-2020 1.1 1.1.0 13-NOV-2020 Payload updates. 1.1 1.2 MAR-2021 Update new design and firmware improvements. 2. Introduction WSLRW-ULA is a LoRaWAN ultrasonic level sensor to measure solid surface level in trash bin for waste management systems ... This level sensor uses ultrasonic technology to measure the solid surface of waste, the principle is to measure the time of flight of the ultrasound pulse in the air environment. The ultrasound pulse will be ejected from ultrasonic transducer, go thru the air and reach the solid surface of the waste, then reflected back to the ultrasonic transducer, the measuring circuit will measure the flight time of the pulse then calculated distance from the transducer to the surface. The ultra-low power design and smart firmware allow the sensor to last for up to 10 years with just 2 x AA batteries (depending on configuration). The sensor will transmit data over kilo-meters away to the LoRaWAN gateway, any brand on the market. 3. Specification SENSORS SPECIFICATION: Sensor Ultrasonic sensor Measurement range 30 .. 1500 mm Resolution & accuracy 1.0mm, +/- 10 mm Sensor sampling rate configurable from 10s up to 3600s Alarm setting setting the alarm threshold for calculated value LoRaWAN SPECIFICATION: Data rate 250bps .. 5470bps Antenna Internal Antenna 2.67 dbi Battery 02 x AA size 1.5, battery not included RF Frequency and Power 860..930Mhz, +14 .. +20 dBm, configurable for zones: EU868, IN865, RU864, KR920, AS923, AU915, US915 Protocol LoRaWAN, class A Data sending modes Interval time and when alarm occurred RF Module complies to ETSI EN 300 220, EN 303 204 (Europe) FCC CFR47 Part15 (US), ARIB STD-T108 (Japan) Vietnam Type Approval Working temperature -15oC..+60oC (using L91 Energizer battery) Dimensions H110xW56xD46.5 Net-weight 200 grams Housing Polycarbonate & POM plastic, IP67 4. Operation Principle 4.1 LoRaWAN protocol specifications 4.1.1 LoRaWAN Sensor protocol specifications LoRaWAN Protocol Version 1.0.3 Application Server Version 1.3.0.0 MAC Layer Version 4.4.2.0 Radio Standards: LoRa Alliance Certified LoRaWAN Zone: LoRa Alliance AS923, KR920, AU915, US915, EU868, IN865, RU864 Class A Join Active: OTAA / ABP Network Mode: Public Network / Private Network Tx Power: up to 20 dBm Frequency: 860 - 930Mhz Date rate: 250 bps - 5kbps Spreading factor: SF12 - SF7 Bandwidth: 125 kHz Unconfirmed-data message LoRaWAN application port for certification: 224 4.1.2 Data rate of LoRaWAN Sensor Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR2 980 SF10 125 AS923, AU915 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 980 SF10 125 US915 DR1 1760 SF9 125 DR2 3125 SF8 125 DR3 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 250 SF12 125 KR920, EU868, IN865, RU864 DR1 440 SF11 125 DR2 980 SF10 125 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 4.1.3 Tx power of LoRaWAN sensor Max EIRP (dBm) Max Tx Power (dBm) Region 16 16 AS923 14 14 KR920 30 20 AU915 30 20 US915 16 16 EU868 30 20 IN865 16 16 RU864 4.2 The principle of operation of the LoRaWAN sensor When starting the power supply, the LoRaWAN sensor has 60 seconds to allow configuration to operate via the Configuration Cable with the Modbus RTU protocol. After 60 seconds, the first packet will be sent, then the LoRaWAN sensor will send the next packets in the following cases: Case 1: When it reaches the frequency of taking data, the LoRaWAN sensor will wake up to measure and calculate. Then: If the measured value exceeds the High or Low setting thresholds, the packet will be sent to the Gateway and then asleep; If NOT then sleep without sending data. NOTE: Once sending the data to Gateway by this alarm event, the timer of sending time interval will be reset; Case 2: When the sending time interval is reached, the LoRaWAN sensor wakes up to measure and calculate and send data to Gateway immediately, regardless of value. Case 3: By using the magnet key, the LoRaWAN sensor can be triggered to send data to Gateway immediately. NOTE: The time between sending data for Class A is at least 3 seconds 4.3 Principle of operation LoRaWAN Network The LoRaWAN Gateway function is Packet Forwarder so: Between Gateway and End Device: Gateway receives data packets from End Device via RF connection, so it is recommended to configure Radio parameters (Note: the packet that Gateway receives is encrypted) Between Gateway and Network Server: Gateway forwards data packets to the Network server via an IP connection, so it is recommended to configure Network parameters such as Server Address, Server Uplink Port, Server Downlink Port,... LoRaWAN Network is secured as follows: Network section key (NwkSKey) to ensure the security of communications on the Network The application session key (AppSKey) to ensure data security between End Device and Application Server Special keys of the device such as DevEUI, AppEUI, Gateway EUI, Device Address. Therefore, the data packet that the Gateway receives is encrypted and decrypted on the Application server. To End Device connect to the Network server, you need to register in the following two ways: Activation with OTAA (Over-the-Air activation): is the process of joining the Network automatically. Previously, both End Device and Application Server installed the same DevEUI code, AppEUI, and AppKey. During activation, AppKey will generate 2 security keys for End Device and Network, which are: The network session key (NwkSKey): is the key to secure communication commands on the MAC layer between the End Device and the Network server. The application session key (AppSKey): is the key to secure data packets between the End Device and Application server. ATTENTIONS:* OTAA mode must be successfully activated in order for the End Device to send data packets to the Network through the Gateway;* OTAA mode only need to activate once, if the device is reset or battery replacement, it will activate OTAA again;* When the End Device is connected to the Network server, whether the Gateway is reset or the power is restarted, it will not need to activate OTAA. Activation by ABP (Activation by Personalization): is the process of joining the Network manually. Device Address, Network session key (NwkSKey), and Application session key (AppSKey) codes must be stored inside the End Device and Application server, so when the End Device sends data packets to the network server, it will also send the security codes to activate. 4.4 Configure the LoRaWAN Network 4.4.1 Configure End Device operation according to OTAA Configuration parameters for the End Device to be activated by OTAA as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode OTAA Device activation type on Network Server DevEUI 34 35 31 31 4B 37 75 12 Device ID's unique ID number => Set this ID number for the Application server AppEUI 70 B3 D5 7E D0 02 D5 0B Application server's unique ID number (random or user-generated)=> Set this ID number for End Device AppKey 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C Key Number for generating 2 NwkSKey and AppSKey security keys created by the user (factory-created by default)=> Used to install for both the Device and Application Server End ATTENTIONS:* The AppEUI number from Application Server => then installed for the End Device. AppEUI is randomly generated by the Application server or by the user;* The number of AppKeys during OTAA activation will generate two security keys, Lora NwkSKey and AppSKey, which are used for both End Device and Network. 4.4.2 Configure End Device operation according to ABP Configuration parameters for the End Device to be activated by ABP as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode ABP Device activation type on Network Server Device Address 12 34 56 78 End Device Address created by the Application server=> Set Device Address for End Device NwkSKey (Network session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C NwkSKey number created by the user to install and use for both End Device and Application Server AppSKey (Application session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C AppSKey number generated by the user to install for both End Device and Application Server 4.4.3 Configure Gateway operations 4.4.3.1 Configure the Gateway to receive data packets from the End Device. Radio settings need to be set as:* Region code: AS923, KR920, AU915, US915, EU868, IN865, RU864* Center Frequency, Channels, Bandwidth (recommends using the default configuration created by the system) Let's take an example to configure the Gateway operation of URSALINK (Model: UG85-L00E-915) 4.4.3.2 Configure the Gateway to communicate with the Public Network Server Let's take an example of configuring Gateway UG85 to connect with "thethingsnetwork.org" in Asia: Currently, thethingsnetwork only supports the connection protocol with Gateway is Semtech UDP Packet Forwarder. https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Parameter settings Setting value (example) Description Gateway EUI 24e124fffef038fd Gateway's unique ID number=> Set this ID number for Application server Server Address router.as1.thethings.network Semtech server address: https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Router regional Asia: router.as1.thethings.network Router regional India: ttn.thingsconnected.net Ursalink server address: localhost Server Uplink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Server Downlink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Network mode Public LoRaWAN 4.4.4 Register the Application server on the Public Network "thethingsnetwork.org" 4.4.4.1 Register the Gateway on Public Network "thethingsnetwork.org" as shown below: The current network only supports the Gateway connection protocol, "Semtech UDP protocol" is Semtech UDP Packet Forwarder. Then power the Gateway and observe the message "Status: connected" => Registration of the Gateway on the Application successfully. 4.4.4.2 Register Application on Public Network "thethingsnetwork.org" as shown below: 4.4.4.3 Register End Device on Application: 4.5 LED meaning RED LED: Fixed ON: due to noise caused peripheral components (i2c, spi, uart, timer, rtc, wdt, ...) do not initialize. Flashing 10ms ON / 10s OFF: Activation by OTAA on the Network server failed. Flashing 10ms ON / 2s OFF:  Sending a data packet to Gateway failed. GREEN LED: Flashing 100ms ON / OFF when sending a data packet to Gateway. BLUE LED: Flashing 1s ON / 1s OFF for the first 60 seconds when booting (insert batteries or connected external sources), after 60 seconds OFF. ON during the LoRaWAN sensor receives data packets from the Network server and OFF when received. 4.6 The Effective Detection Range 4.7 Process of measurement When the LoRa sensor wakes up, it will supply power to the internal or external sensor so that the sensor can start measuring. After measuring successfully it will turn off the power to the sensor for energy saving. The measured value is the raw value of the sensor. The measured value can be scaled according to the following formula: Y = aX + b X: the raw value from the sensor Y: the calculated value will be sent to LoRaWAN Gateway in the payload data. a: constant (default value is 1) b: constant (default value is 0) So, if there is no user setting for a and b ==> Y = X The Y value will be compared with Lo and Hi threshold. Please refer below the graph of alarm processing. 4.8 Calibration Figure – Ultrasonic Level Transmitter Calibration DB: Dead band 0..300 mm (This is a short range in front of the ultrasonic sensor can not measure distances) H: Maximum measuring distance ( Span ) D: Distance For example: Trash bin with maximum height to be measured 1200mm (H) and the maximum height to measure is 300mm (Recommended to install the lowest point that should be larger than the Deadband 300mm), then: From here we can look up the trash level corresponding to the measured distance of the sensor by the formula: Y = aX + b. Where: X is the measured distance (mm) and Y is the level (‰) Distance (mm) Level (‰) 300 1000 400 889 500 778 600 667 700 556 800 445 900 333 1000 222 1100 111 1200 0 Use the offline configuration tool to configure sigfox sensor. Write in the sensor the parameters a1 and b1. Refer to Resigter table for more details. 4.9 Payload Data The following is the format of payload data that will be sent to the LoRaWAN Gateway. Sensor type (1 byte) Status (1 byte) 1st - Parameter (2 bytes) 2st - Parameter (2 bytes) Meaning of Data in the Payload Data Size (byte) Bit Format Meaning Sensor type 1 all Uint8 Sensor type = 0x0E means LoRaWAN Node ULASensor type = 0xFF means no sensor Status: battery level 1 Bit 7 and 6 Uint8 Battery capacity in 04 levels 11: battery level 4 (99%) 10: battery level 3 (60%) 01: battery level 2 (30%) 00: battery level 1 (10%) Status: error Bit 5 and 4 Node status 01: error 00: no error Status: alarm 1 Bit 3 and 2 Alarm status of 1st - Parameter (Y1 value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm Status: alarm 2 Bit 1 and 0 Alarm status of 2st - Parameter (Y2 value)11 : Hi alarm01 : Lo alarm00 : No alarm 1st - Parameter 2 all Uint16 Y1 value: Level (x0.1%) Y1 is calculated based on Y2 value by the formula:Y1 = Y2*a1+b1 2st - Parameter 2 all Uint16 Y2 value: Distance value (mm) 5. Configuration Using the configuration cable to connect to the sensor as below picture. Serial port configuration on the computer:* COMPort, Baudrate: 9600, Parity: None, Stop bit: 1, Data bit: 8* Modbus RTU: Reading data by Function 3 / Writing data by Function 16. 5.1 Step to configure NOTE: The Modbus configuration can only be performed in the first 60s after power up the LoRaWAN sensor. After 60s, if user can not finish the configuration process, user need to reset the power of LoRaWAN sensor again, by removing battery in at least 15s. Step 1: Install the Modbus Configurator Software in the link below https://filerun.daviteq.com/wl/?id=qK0PGNbY1g1fuxTqbFW9SXtEvCw7bpc6 How to use the Modbus configuration software Step 2: Plug the configuration cable to computer via USB port and install the driver; Step 3: Open the housing with phillips screwdriver to unscrew M3 screws at the side of the housing Step 4: Plug the connector to the configuration port; Step 5:  Import the configuration file by importing the csv file: Go to MENU: FILE / Import New / => select the file with name CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0.csv (in the link below). Then click Connect; CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0 To write new value to the device:First, you need to write the password in "password for setting", after reading the value to check ok, you can write the new value AppEUI, AppKey, ...You only have 60 seconds after plugging the configuration cable or the power supply into the device for configuration. 5.2 Register table Here is the table of Data will be read by Modbus tool Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 0 0 3 5 device info WSLRW-SMT1 string Read Wireless Sensor LoRaWAN with SMT1 5 5 3 4 firmware version 1.00ddmm string Read ddmm = day / month 9 9 3 2 hardware version 1.10 string Read 11 B 3 4 lorawan protocol version 01.00.03 string Read lorawan v1.0.3 15 F 3 6 application version 01.03.00.00 string Read application server v1.3.0.0 21 15 3 6 mac layer version 04.04.02.00 string Read mac layer v4.4.2.0 27 1B 3 4 deviceEUI hex Read End Device's EUI number, used to register the product on the Network Server by OTAA 31 1F 3 4 lora appEUI hex Read Application server's EUI number is used to register the product on the Network Server by OTAA 35 23 3 8 lora appKey hex Read The number of keys used to create two security keys of the End Device, used to register the product on the Network Server by OTAA 43 2B 3 8 lora nwkSkey hex Read key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 51 33 3 8 lora appSkey hex Read End Device data encryption key number, used to register the product on the Network Server by ABP 59 3B 3 2 device address 0 uint32 Read End Device address created by Application server, used to register the product on the Network server by ABP 61 3D 3 2 network ID 0 uint32 Read Network server ID number, used to register the product on the Network server by ABP 63 3F 3 2 join mode OTAA string Read OTAA: Over-the-Air activation, ABP: Activation by Personalization 65 41 3 4 network mode PUBLIC string Read PUBLIC, PRIVATE 69 45 3 3 region code AS923 string Read 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 72 48 3 4 data rate DR2:980 string Read DR0:250, DR1:440, DR2:980, DR3:1760, DR4:3125, DR5:5470 76 4C 3 3 bandwidth BW125 string Read BW125, BW250, BW500 79 4F 3 2 spread factor SF10 string Read SF12, SF11, SF10, SF9, SF8, SF7 81 51 3 4 activation of ADR ADR OFF string Read ADR ON, ADR OFF 85 55 3 1 class A string Read 103 67 3 1 sensor type 1-255 uint16 Read 1-254: sensor type, 255: no sensor 104 68 3 1 battery level 0-3 uint16 Read 4 levels of battery capacity status 105 69 3 1 error status 0-1 uint16 Read Error code of sensor, 0: no error, 1: error 106 6A 3 1 prm1 alarm status 0-2 uint16 Read Alarm status of parameters 1, 0: none, 1: Low, 2: High 107 6B 3 1 prm2 alarm status 0-2 uint16 Read Alarm status of parameter 2 108 6C 3 2 prm1 value float Read Value of parameter 1 110 6E 3 2 prm2 value float Read Value of parameter 2 112 70 3 1 battery % 10%, 30%, 60%, 99% uint16 Read % Value of battery capacity 113 71 3 2 battery voltage 0-3.67 vdc float Read Value of battery voltage 115 73 3 2 mcu temperature °C float Read Temperature value of RF module 117 75 3 1 mcu vref 0-3.67 vdc uint16 Read Vref value of RF module 118 76 3 1 button1 status 0-1 uint16 Read Button state, 0: No button pressed, 1: Button pressed 119 77 3 1 button2 status 0-1 uint16 Read Button status, 0: No magnetic sensor detected, 1: Magnetic sensor detected Here is the table for Configuration: Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 256 100 3 / 16 1 modbus address 1-247 1 uint16 R/W Modbus address of the device 257 101 3 / 16 1 modbus baudrate 0-1 0 uint16 R/W 0: 9600, 1: 19200 258 102 3 / 16 1 modbus parity 0-2 0 uint16 R/W 0: none, 1: odd, 2: even 259 103 3 / 16 9 serial number string R/W (Password) 268 10C 3 / 16 2 password for setting uint32 R/W (Password) password 190577 270 10E 3 / 16 4 lora appEUI hex R/W (Password) Application server's EUI number, used to register the product on the Network Server by OTAA 274 112 3 / 16 8 lora appKey hex R/W (Password) The number of keys used to create two security keys of the End Device, used to register the product on the Network server by OTAA 282 11A 3 / 16 8 lora nwkSkey hex R/W (Password) key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 290 122 3 / 16 8 lora appSkey hex R/W (Password) End Device data encryption key number, used to register the product on the Network Server by ABP 298 12A 3 / 16 2 device address uint32 R/W (Password) End Device address created by Application server, used to register the product on the Network server by ABP 300 12C 3 / 16 2 network ID uint32 R/W (Password) Network server ID number, used to register the product on the Network server by ABP 302 12E 3 / 16 1 activation mode 0-1 1 uint16 R/W (Password) 1: OTAA (Over-the-Air Activation), 0: ABP (Activation by Personalization) 304 130 3 / 16 1 application port 1-255 1 uint16 R/W (Password) Port 224 is reserved for certification 317 13D 3 / 16 1 region 1-7 1 uint16 Read/Write(Password) 1: AS923, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: CN779, 9: CN470, 10: EU433 318 13E 3 / 16 1 data rate 7 uint16 R/W (Password) 0: 250 bps, 1: 440 bps, 2: 980 bps, 3: 1760 bps, 4: 3125 bps, 5: 5470 bps 319 13F 3 / 16 1 tx power 2-20 16 uint16 R/W (Password) tx power: 2,4,6,8,10,12,14,16,18,20 320 140 3 / 16 1 adaptative data rate 0-1 0 uint16 R/W (Password) Automatically adjust data rate, 0: disable, 1: enable 334 14E 3 / 16 2 cycle send data 900 uint32 R/W sec (data sending cycle) 338 152 3 / 16 1 alarm limt 44 uint16 R/W limit the number of events / day 340 154 3 / 16 2 sensor1: sampling_rate 120 uint32 R/W sec (frequency of data taken from sensor 1) 348 15C 3 / 16 2 prm1: a 1 float R/W Scale parameter "a" of prm1 350 15E 3 / 16 2 prm1: b 0 float R/W Scale parameter "b" of prm1 354 162 3 / 16 2 prm1: High Threshold 100000 float R/W High threshold value of prm1 356 164 3 / 16 2 prm1: High Hysteresis 10000 float R/W High hysteresis value of prm1 358 166 3 / 16 2 prm1: Low Threshold 0 float R/W Low threshold value of prm1 360 168 3 / 16 2 prm1: Low Hysteresis 10000 float R/W Low hysteresis value of prm1 362 16A 3 / 16 2 prm1: High Cut 100000 float R/W Upper limit value of prm1 364 16C 3 / 16 2 prm1: Low Cut 0 float R/W Lower limit value of prm1 366 16E 3 / 16 2 prm2: a 1 float R/W Scale parameter "a" of prm2 368 170 3 / 16 2 prm2: b 0 float R/W Scale parameter "b" of prm2 372 174 3 / 16 2 prm2: High Threshold 100000 float R/W High threshold value of prm2 374 176 3 / 16 2 prm2: High Hysteresis 10000 float R/W High hysteresis value of prm2 376 178 3 / 16 2 prm2: Low Threshold 0 float R/W Low threshold value of prm2 378 17A 3 / 16 2 prm2: Low Hysteresis 10000 float R/W Low hysteresis value of prm2 380 17C 3 / 16 2 prm2: High Cut 100000 float R/W Upper limit value of prm2 382 17E 3 / 16 2 prm2: Low Cut 0 float R/W Lower limit value of prm2 6. Installation 6.1 Example application 6.2 Dimensions WARNINGS:1. Please make sure the material is suitable with the materials of the sensor. Please refer sensor specification;2. Please make sure that the operating ambient temperature is right for the sensor. Please refer to the sensor's specifications;3. Prepare the professional tools for installation. The inappropriate tools may cause damage to the sensor. 6.3 Mounting Fix the sensor with the screws provided in the accessory bag. 6.4 Installation location To maximize the distance of transmission, the ideal condition is Line-of-sight (LOS) between the LoRaWAN sensor and Gateway. In real life, there may be no LOS condition. However, the LoRaWAN sensor still communicates with Gateway, but the distance will be reduced significantly. ATTENTION:DO NOT install the LoRaWAN 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, cement…is acceptable. 6.4 Battery installation Steps for battery installation: Step 1:Open the housing with phillips screwdriver to unscrew M3 screws at the side of the housing Step 2: Insert 02 x AA 1.5VDC battery, please take note the poles of the battery ATTENTION: REVERSED POLARITY OF BATTERIES IN 10 SECONDS CAN DAMAGE THE SENSOR CIRCUIT!!! Step 3: Insert the top plastic housing and locking by phillips screwdriver. 7. Troubleshooting No. Phenomena Reason Solutions 1 The BLUE LED does not blink when the battery is installed Insert the battery in the opposite direction Insert the battery in the correct way 2 The RED LED is always on Due to noise, the peripheral components (i2c, spi, uart, ..) of RF module cannot be initialized After 30s the node will automatically reset. If the noise causes the Watchdog not to initialize, remove the battery and wait for more than 10 seconds, then insert the battery again 3 The RED LED blinks continuously (10ms ON / 2s OFF) and the Node does not send RF. After more than 10 sending cycles, the Node will automatically reset Operating frequency in that country is prohibited Operating frequency in that country is limited to Data rate, Tx Power Reconfigure the allowed frequency of operation Reconfigure Data rate = DR5 / SF07, Tx Power 4 RED LED blinks continuously (10ms ON / 2s OFF) and Node sends RF continuously 3s / time but no data. After more than 10 sending cycles, the Node will automatically reset Node runs dummy sending mode => sent by Gateway to send Downlink packets when users clear Uplink and Downlink counter values on Network Server (build-in Gateway) when activated by ABP Configuration enabled by OTAA 5 The RED LED flashes 10ms ON / 10s OFF and the Node does not send RF Node activation by OTAA on Network server has not been successful Using Magnet-Key to force Node to send RF continuously for 3 seconds/time => when activating by OTAA successfully, the GREEN LED will blink after sending RF 6 The node sent RF successfully but the GREEN LED did not blink LED is broken Warranty to replace LED 7 The data packet taken from the Gateway has an incorrect value The data package is encrypted Get the decoded packet on the Application Server 8 The node sends RF and activates by ABP, on Gateway receives data but the Application server has no data The application server still stores the counter values of the previous Uplink and Downlink Delete the counter values of Uplink and Downlink on the Application server 9 The node does not send RF and the RF module is hot Insert the battery in the opposite direction Short circuit Warranty or replacement 10 The node does not send RF to Gateway according to the alarm, LED does not blink The alarm configuration is incorrect Running out of the number of alarms set for the day Check alarm configuration Check the configuration for the maximum number of alarms per day 11 The node does not send RF to Gateway when activated by the magnetic key, LED does not blink The magnetic sensor has malfunctioned Read the status of the magnetic sensor via Modbus (when powering or attaching the battery) to see if the magnetic sensor is working. 12 Node has blinked LED GREEN when sending RF but the Gateway or Application server cannot receive LoRa module on the Gateway is faulty The IP connection (4G / WiFi / ...) on the Gateway is faulty Check Gateway's LoRa status lights on Gateway Check 4G / WiFi status lights on Gateway 13 The value of the sensor is 0 and sensor_type = 0xFF Lost connection with the sensor Check sensor connection Replace the module sensor 14 RSSI is weak and often loses data The distance between Node and Gateway is far or there are many obstructions Connection to Antenna problem Install metal nodes or in metal cabinets Configure Data rate = DR0 / SF12 Check Antenna position Install Node in a well-ventilated location 8. Support contacts Manufacturer Daviteq Technologies IncNo.11 Street 2G, Nam Hung Vuong Res., An Lac Ward, Binh Tan Dist., Ho Chi Minh City, Vietnam.Tel: +84-28-6268.2523/4 (ext.122) Email: info@daviteq.com | www.daviteq.com Distributor in Australia and New Zealand Templogger Pty Ltd Tel: 1800 LOGGER Email: contact@templogger.net Instructions to add the Base Stations and Devices to ThingPark Network Server (ThingParkEnterprise SaaS Community) Community is a SaaS platform that is available for free to test the Actility network server. ThingPark Enterprise users can follow those examples to activate base stations and devices on your account. 1. Add Tektelic Model T0005204 to ThingPark Enterprise SaaS Community. Please contact the Tektelic Support for your target platform that your base station supports LRR packet forwarder. 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: Field Input field Name Base station 1 LRR-UUID 647FDA-647FDA008526 RF region US 915MHz (8 channels: CH0-CH7) Public Key -----BEGIN PUBLIC KEY-----MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC/6v1EEK5fTiZHKEyo4oDEJasoHY3cOWXxMKx6ZSGajzPQzLjcZgmIv82EruclBe8SVuCW4vj92Squ6KbYavmP//tM8G9HiM0BzUrb0s8PAilHyuNIzS6h6So2XfMByf7MuYbC131Uy2y2bLRiZuFq5zOA4ZHxqmBnG+whArjkgQIDAQAB-----END PUBLIC KEY----- Input exactly as above Input field column, except Name field is user-defined and is different from existing base station name on the network server. After filling registration form, click CREATE to complete adding base station to the network server 2. Add Daviteq's LoRaWAN devices ThingPark Enterprise SaaS Community ThingPark Enterprise supports all Classes of LoRaWAN® devices. By default, the sensor supports Over-the-Air Activation (OTAA) with 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 au915 4. Fill the form as below table: Field Input field Name As user-defined DevEUI As DevEUI on label of the device Activation mode Over-the-Air Activation (OTAA) with local Join Server JoinEUI Input JoinEUI. This value read on memory map or on the label of the device. The default value is 0102030405060708 AppKey Input AppKey.This value read on memory map or on the label of the device. The default value is 0102030405060708090A0B0C0D0E0F10 After filling the registration form, please click CREATE to add devices to the network server 3. Send a downlink frame from Thingpark Network Server to the device You may send a downlink frame to the device from the Device table. 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's drop-down menu then List. 2. Browse the right side in the DEVICES, and select your preferred device to give an action. In this case, Send Downlink. 3. Input "1" to the Port in advance, write your downlink data in the field, and then click VALIDATE. The downlink data is added to the device downlink queue, downlinks may be sent only after an uplink from the device. Thanks for the reference link: - Managing your radio access network - Activating a device to your IoT network - Sending a test downlink frameInstruction to get info from the LRR gateway SUPLOG is supported on the following base station brands: Cisco, Kerlink, MultiTech, Ufispace, Gemtek/Browan and Tektelic. In this article, the Kona Micro Gateway is used directly as the instructions provided. We have 02 of the Kona Micro Gateway models T0005204 and T0005206. In order to know how to install the components out of the box, please check Kona Micro Quick Start Guide In order to find out about your model for a Kona Micro Gateway, please visit Kona Micro Gateway User Guide 1. Use KonaFT to find your Tektelic Gateways. After connecting the Ethernet cable to your gateway in a network. We need to locate the gateway IP address in the same network on your PC. Please download: KonaFT Application 1. Go to Tools > Find My Gateway. 2. Click Scan. 2. Use the PuTTY software to join the SUPLOG's interface. To learn more about the gateway models supporting LRR software, see Supported brands of base stations. Please visit Download PuTTY 1. Go to Translation > Click Enable VT100 line drawing even in UTF-8 mode. 2. Click Session > Enter 192.168.1.44 > Click Open 3. Enter support > 5e98ee45a1 4. Click Identifiers > Get LRR UUID > Get public key 5. Collect the information below: Get LRR UUID 647FDA-647FDA009783 Get public key -----BEGIN PUBLIC KEY-----MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDQKn6xRi/nKFRJFkPB3UnvGVFlkgpVvqccDPw5Pvb3M9kkLglPR14zP//qH49OKfFVIAT7LldPWskVt/k6kJRVhVdNu6mJI6KS0CoysC2iudbz/XMxmSMC0B09wvS3Bi+wgE39RXUooLzRLReiMW9/W+Ogqyo6KBDLw9bq8GSRkwIDAQAB-----END PUBLIC KEY----- Thank for the link reference: - Installing the ThingPark image on your base station - Configuring the base station LRR Configuration instructions to forward LoraWAN sensor data from Thingpark to Globiots 1. Add a LoraWAN sensor to Globiots Step 1: Open web-browser and go to link: https://vizuo.globiots.com/login Step 2: Sign in with provided username and password. Step 3: At Organization Chart, right-click to desired Node => Select New => Select Lora. Step 4: Input information of LoraWAN sensor and Acility Network Server At the tab Basic Information, input LoraWAN sensor information in the form: Name: input 12 characters of user-defined sensor name. DevEUI: input sensor DevEUI. The DevEUI (16 characters) is on the sensor label or is read out from sensor memory. Device ID: click Generate button to get device ID At tab Network Sever Config, select category of Actility Thingpark, select relavant LoRa Device type and fill the sensor DevEUI in Downlink Message section. Then click Save button to complete adding the sensor to Globiots 2. Create a connection from Thingpark to Globiots Note: If the connection from Thingpark to Globiots is available, skip section 2 Step 1: Log in to your ThingPark Enterprise account via the link: https://community.thingpark.io/tpe/ and then browse on the left panel to Connections, click the drop-down menu, click Create, click section https:// to create https connection from Thingpark to Globiots Step 2: Input information to setup the connection as below details, and click Create to complete creating the connection. Filled information is from the Uplink Message section of the LoraWAN sensor on Globiots (At the Organization Chart panel of Globiots, click the LoraWAN sensor, click tab Network Server Config) 3. Add Daviteq LoRaWAN devices on ThingPark GUI. ThingPark Enterprise supports all Classes of LoRaWAN® devices. By default, the sensor supports Over-the-Air Activation (OTAA) with 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. Step 1: Log in to your ThingPark Enterprise account via the link: https://community.thingpark.io/tpe/ and then browse on the left panel to Devices, click the drop-down menu, click Create 2. To add a device, 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: Field Input field Name As user-defined DevEUI As DevEUI on label of the device Activation mode Over-the-Air Activation (OTAA) with local Join Server JoinEUI Input JoinEUI. This value read on memory map or on the label of the device. The default value is 0102030405060708 AppKey Input AppKey.This value read on memory map or on the label of the device. The default value is 0102030405060708090A0B0C0D0E0F10 In addition to filling the form, select the connection between Thingpark and Globiots which is created in section 2 After filling the registration form, please click CREATE to add devices to the network server 4. Monitor LoraWAN sensor data on Globiots Step 1: At Organization Chart panel on Globiots, click to the LoraWAN sensor name added in Section 1 Step 2: Click Monitoring tab to view the lastest sensor data. USER GUIDE FOR LORAWAN VIBRATION SENSOR WSLRW-V1A THIS IS OBSOLETE MANUAL Please access https://www.iot.daviteq.com/wireless-sensors for updated manual WSLRW-V1A-MN-EN-01 OCT-2022 This document is applied for the following products SKU WSLRW-V1A HW Ver. 1.2 FW Ver. 1.0 Item Code WSLRW-V1A-9-025 LoRaWAN PIEZO-ELECTRIC 10KHZ VIBRATION SENSOR, +/- 25G, INTERNAL ANTENNA, TYPE AA BATTERY 1.5VDC, IP67, 900-930 Mhz for KR920, AS923, AU915, US915 WSLRW-V1A-8-025 LoRaWAN PIEZO-ELECTRIC 10KHZ VIBRATION SENSOR, +/- 25G, INTERNAL ANTENNA, TYPE AA BATTERY 1.5VDC, IP67, 860-870 Mhz for EU868, IN865, RU864 0. Configuration Check List STEP 1: Configure End Device (Using Modbus Configuration Cable) Setting value (Example) 1. Select region AS923, IN865, EU868,.. (refer to register address 317) 2. End Device Operation OTAA or ABP OTAA Write AppEUI information from Application Server to Lorawan End Device; Write AppKey (created by user) information for Lorawan End Device and Application Server. ABP Write DevEUI information from Application Server to Lorawan end device; write Network Session Key and App Session Key (created by user) information to Lorawan end device (and Application Server). 3. Configure "cycle send data" 900 sec (Defaut) 4. Configure "sensor sampling_rate" 900 sec (Defaut) 5. Configure parameters of sensor (Refer to Check data configuration table) STEP 2:  Configure the operation of LoRaWAN Gateway (Ex: URSALINK Gateway) 1. Configure the information in the General tab Server address, Server port (For more information) 2. Configure the information in the Radio tab Select the Region Region (Other parameters to default) STEP 3:  Configure the operation of LoRaWAN Gateway on Network Server (Ex: URSALINK Gateway with Thethingsnetwork) 1. Gateway ID registration Gateway ID is the GatewayEUI information on the Gateway 2. Frequency Plan parameters configuration Asia 920-923MHz, Europe 868MHz,... 3. Router parameters configuration 4. Check the connection of the gateway to the network server The Gateway status LED lights up and displays the message "Status: conneted" on the Thethingsnetwork STEP 4:  Configure the operation of Application Server on Network Server 1. App ID registration 2. Handler parameters configuration STEP 5: Register Lorawan End Device on Application Server on Thethingsnetwork 1. ID Registration 2.Select operation mode OTAA or ABP OTAA Configure parameters DevEUI and AppKEY ABP Configure parameters Device Address, Network Session Key, App Session Key 1. Functions Change Log HW Ver. FW Ver. Release Date Functions Change 1.1 1.0.0 21-July-2020 1.1 1.1.x 05-Oct-2020 Data frame improvements Fix the Watchdog bug 1.1 1.2.0 12-Oct-2020 Improved output WSLRW-PPS The minimum frequency of sending data packets to Gateway is 15 seconds When connecting to network server with OTAA failure, it will not read sensor value 2. Introduction WSLRW-V1A is a cost effective, LoRaWAN accelerometer single-axis vibration sensor designed for condition monitoring and preventive maintenance applications. The piezo-electric accelerometer is available in ranges ±25g or 50g and features a flat frequency response up to >10kHz. Its accelerometer features a stable piezo-ceramic crystal in shear mode with low power electronics, sealed in a fully hermetic package. The Piezo Electric technology incorporated in the WSLRW-V1A accelerometer has a proven track record for offering the reliable and long-term stable output required for condition monitoring applications. The accelerometer is designed and qualified for machine health monitoring and has superior Resolution, Dynamic Range and Bandwidth to MEMS devices. Beside that it can also measure the temperature at mounting point. The Ultra-Low Power Power design and smart firmware allow the sensor to last up to 10 years with 02 x AA battery (depending on configuration). The sensor will transmit data over kilo-meters away to the LoRaWAN gateway, any brand on the market.Typical Applications: Machine Health Monitoring, Predictive Maintenance Installations, Vibration Monitoring, Impact & Shock Monitoring, Bearing monitoring, … 3. Specification SENSOR SPECIFICATION: (* Note: All below values are typical at +24°C, 80Hz) Sensor technology Hermetically Sealed, Piezo-Ceramic Crystal, Shear Mode 8-Parameter Measurement Acceleration RMS & PeakVelocity RMS & PeakDisplacement RMS & PeakFrequency & Temperature Acceleration Range & Shock Limit (g) ±25 or 50, 10,000 Frequency Response and Resonant (Hz) 2-10000, > 30000 Non-Linearity, Transverse Sensitivity ±2%FSO, < 5% Temperature measuring and operating -40°C.. +85°C, with accuracy: +/- 0.5 and resolution: 0.125 Sensor Material, rating and mounting 304SUS, IP67, M6 Screw Connector M12-M 5-pin (Coding A) with 2m cable, wired to LoRaWAN node LoRaWAN SPECIFICATION: Data rate 250bps .. 5470bps Antenna Internal Antenna 2.67 dbi Battery 02 x AA size 1.5, battery not included RF Frequency and Power 860..930Mhz, +14 .. +20 dBm, configurable for zones: EU868, IN865, RU864, KR920, AS923, AU915, US915 Protocol LoRaWAN, class A Data sending modes Interval time and when alarm occurred RF Module complies to ETSI EN 300 220, EN 303 204 (Europe) FCC CFR47 Part15 (US), ARIB STD-T108 (Japan) Working temperature -40oC..+60oC (using Energizer Lithium Ultimate AA battery) Dimensions & Net-weight H106xW73xD42, 190 grams Housing Aluminum+Polycarbonate, IP67 Mounting Wall mount bracket 4. Operation Principle 4.1 LoRaWAN protocol specifications 4.1.1 LoRaWAN Sensor protocol specifications LoRaWAN Protocol Version 1.0.3 Application Server Version 1.3.0.0 MAC Layer Version 4.4.2.0 Radio Standards: LoRa Alliance Certified LoRaWAN Zone: LoRa Alliance AS923, KR920, AU915, US915, EU868, IN865, RU864 Class A Join Active: OTAA / ABP Network Mode: Public Network / Private Network Tx Power: up to 20 dBm Frequency: 860 - 930Mhz Date rate: 250 bps - 5kbps Spreading factor: SF12 - SF7 Bandwidth: 125 kHz Unconfirmed-data message LoRaWAN application port for certification: 224 4.1.2 Data rate of LoRaWAN Sensor Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR2 980 SF10 125 AS923, AU915 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 980 SF10 125 US915 DR1 1760 SF9 125 DR2 3125 SF8 125 DR3 5470 SF7 125 Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 250 SF12 125 KR920, EU868, IN865, RU864 DR1 440 SF11 125 DR2 980 SF10 125 DR3 1760 SF9 125 DR4 3125 SF8 125 DR5 5470 SF7 125 4.1.3 Tx power of LoRaWAN sensor Max EIRP (dBm) Max Tx Power (dBm) Region 16 16 AS923 14 14 KR920 30 20 AU915 30 20 US915 16 16 EU868 30 20 IN865 16 16 RU864 4.2 The principle of operation of the LoRaWAN sensor When starting the power supply, the LoRaWAN sensor has 60 seconds to allow configuration to operate via the Configuration Cable with the Modbus RTU protocol. After 60 seconds, the first packet will be sent, then the LoRaWAN sensor will send the next packets in the following cases: Case 1: When it reaches the frequency of taking data, the LoRaWAN sensor will wake up to measure and calculate. Then: If the measured value exceeds the High or Low setting thresholds, the packet will be sent to the Gateway and then asleep; If NOT then sleep without sending data. NOTE: Once sending the data to Gateway by this alarm event, the timer of sending time interval will be reset; Case 2: When the sending time interval is reached, the LoRaWAN sensor wakes up to measure and calculate and send data to Gateway immediately, regardless of value. Case 3: By using the magnet key, the LoRaWAN sensor can be triggered to send data to Gateway immediately. NOTE: The time between sending data for Class A is at least 3 seconds 4.3 Principle of operation LoRaWAN Network The LoRaWAN Gateway function is Packet Forwarder so: Between Gateway and End Device: Gateway receives data packets from End Device via RF connection, so it is recommended to configure Radio parameters (Note: the packet that Gateway receives is encrypted) Between Gateway and Network Server: Gateway forwards data packets to the Network server via an IP connection, so it is recommended to configure Network parameters such as Server Address, Server Uplink Port, Server Downlink Port,... LoRaWAN Network is secured as follows: Network section key (NwkSKey) to ensure the security of communications on the Network The application session key (AppSKey) to ensure data security between End Device and Application Server Special keys of the device such as DevEUI, AppEUI, Gateway EUI, Device Address. Therefore, the data packet that the Gateway receives is encrypted and decrypted on the Application server. To End Device connect to the Network server, you need to register in the following two ways: Activation with OTAA (Over-the-Air activation): is the process of joining the Network automatically. Previously, both End Device and Application Server installed the same DevEUI code, AppEUI, and AppKey. During activation, AppKey will generate 2 security keys for End Device and Network, which are: The network session key (NwkSKey): is the key to secure communication commands on the MAC layer between the End Device and the Network server. The application session key (AppSKey): is the key to secure data packets between the End Device and Application server. ATTENTIONS:* OTAA mode must be successfully activated in order for the End Device to send data packets to the Network through the Gateway;* OTAA mode only need to activate once, if the device is reset or battery replacement, it will activate OTAA again;* When the End Device is connected to the Network server, whether the Gateway is reset or the power is restarted, it will not need to activate OTAA. Activation by ABP (Activation by Personalization): is the process of joining the Network manually. Device Address, Network session key (NwkSKey), and Application session key (AppSKey) codes must be stored inside the End Device and Application server, so when the End Device sends data packets to the network server, it will also send the security codes to activate. 4.4 Configure the LoRaWAN Network 4.4.1 Configure End Device operation according to OTAA Configuration parameters for the End Device to be activated by OTAA as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode OTAA Device activation type on Network Server DevEUI 34 35 31 31 4B 37 75 12 Device ID's unique ID number => Set this ID number for the Application server AppEUI 70 B3 D5 7E D0 02 D5 0B Application server's unique ID number (random or user-generated)=> Set this ID number for End Device AppKey 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C Key Number for generating 2 NwkSKey and AppSKey security keys created by the user (factory-created by default)=> Used to install for both the Device and Application Server End ATTENTIONS:* The AppEUI number from Application Server => then installed for the End Device. AppEUI is randomly generated by the Application server or by the user;* The number of AppKeys during OTAA activation will generate two security keys, Lora NwkSKey and AppSKey, which are used for both End Device and Network. 4.4.2 Configure End Device operation according to ABP Configuration parameters for the End Device to be activated by ABP as the table below: Parameter settings Setting value (example) Description Region code AS923 The area is located in the LoRa Alliance Center Frequency 923400000 Center frequency Join Mode ABP Device activation type on Network Server Device Address 12 34 56 78 End Device Address created by the Application server=> Set Device Address for End Device NwkSKey (Network session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C NwkSKey number created by the user to install and use for both End Device and Application Server AppSKey (Application session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C AppSKey number generated by the user to install for both End Device and Application Server 4.4.3 Configure Gateway operations 4.4.3.1 Configure the Gateway to receive data packets from the End Device. Radio settings need to be set as:* Region code: AS923, KR920, AU915, US915, EU868, IN865, RU864* Center Frequency, Channels, Bandwidth (recommends using the default configuration created by the system) Let's take an example to configure the Gateway operation of URSALINK (Model: UG85-L00E-915) 4.4.3.2 Configure the Gateway to communicate with the Public Network Server Let's take an example of configuring Gateway UG85 to connect with "thethingsnetwork.org" in Asia: Currently, thethingsnetwork only supports the connection protocol with Gateway is Semtech UDP Packet Forwarder. https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Parameter settings Setting value (example) Description Gateway EUI 24e124fffef038fd Gateway's unique ID number=> Set this ID number for Application server Server Address router.as1.thethings.network Semtech server address: https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html Router regional Asia: router.as1.thethings.network Router regional India: ttn.thingsconnected.net Ursalink server address: localhost Server Uplink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Server Downlink Port 1700 The port address of the Semtech server: 1700 The port address of the Ursalink server: 1883 The port address of the Loriot server: 1780 Network mode Public LoRaWAN 4.4.4 Register the Application server on the Public Network "thethingsnetwork.org" 4.4.4.1 Register the Gateway on Public Network "thethingsnetwork.org" as shown below: The current network only supports the Gateway connection protocol, "Semtech UDP protocol" is Semtech UDP Packet Forwarder. Then power the Gateway and observe the message "Status: connected" => Registration of the Gateway on the Application successfully. 4.4.4.2 Register Application on Public Network "thethingsnetwork.org" as shown below: 4.4.4.3 Register End Device on Application: 4.5 LED meaning RED LED: Fixed ON: due to noise caused peripheral components (i2c, spi, uart, timer, rtc, wdt, ...) do not initialize. Flashing 10ms ON / 10s OFF: Activation by OTAA on the Network server failed. Flashing 10ms ON / 2s OFF:  Sending a data packet to Gateway failed. GREEN LED: Flashing 100ms ON / OFF when sending a data packet to Gateway. BLUE LED: Flashing 1s ON / 1s OFF for the first 60 seconds when booting (insert batteries or connected external sources), after 60 seconds OFF. ON during the LoRaWAN sensor receives data packets from the Network server and OFF when received. 4.6 Process of measurement When the LoRa sensor wakes up, it will supply power to the internal or external sensor so that the sensor can start measuring. After measuring successfully it will turn off the power to the sensor for energy saving. The measured value is the raw value of the sensor. The measured value can be scaled according to the following formula: Y = aX + b X: the raw value from the sensor Y: the calculated value will be sent to LoRaWAN Gateway in the payload data. a: constant (default value is 1) b: constant (default value is 0) So, if there is no user setting for a and b ==> Y = X The Y value will be compared with Lo and Hi threshold. Please refer below the graph of alarm processing. 4.7 Payload Data The following is the format of payload data that will be sent to the LoRaWAN Gateway. Sensor type (1 byte) Status (1 byte) Parameter 1 (4 bytes) Parameter 2 (4 bytes) Parameter 3 (4 bytes) Parameter 4 (4 bytes) Parameter 5 (4 bytes) Parameter 6 (4 bytes) Parameter 7 (4 bytes) Parameter 8 (2 bytes) Parameter 9 (2 bytes) Meaning of Data in the Payload Data Size Bit Format Meaning Sensor type 1 byte all Uint8 Sensor type = 0x10 means LoRaWAN V1A Status: battery level 2 bits Bit 7 and 6 Battery capacity in 04 levels 11: battery level 4 (99%) 10: battery level 3 (60%) 01: battery level 2 (30%) 00: battery level 1 (10%) Status: error 2 bits Bit 5 and 4 Sensor status 01: error 00: no error Status: NA 4 bits Bit 3 and 0 Not Applicable Parameter 1 4 bytes all Float Acceleration Peak (m/s2) Parameter 2 4 bytes all Float Acceleration RMS (m/s2) Parameter 3 4 bytes all Float Crest factor Parameter 4 4 bytes all Float Velocity Peak (mm/s) Parameter 5 4 bytes all Float Velocity RMS (mm/s) Parameter 6 4 bytes all Float Displacement Peak-Peak (um) Parameter 7 4 bytes all Float Displacement RMS (um) Parameter 8 2 bytes all Uint16 Frequency (Hz) Parameter 9 2 bytes all Int16 Temperature (oC) (Real Temperature = Temperature/10) 5. Configuration Using the configuration cable to connect to the sensor as below picture. Serial port configuration on the computer:* COMPort, Baudrate: 9600, Parity: None, Stop bit: 1, Data bit: 8* Modbus RTU: Reading data by Function 3 / Writing data by Function 16. 5.1 Step to configure NOTE: The Modbus configuration can only be performed in the first 60s after power up the LoRaWAN sensor. After 60s, if user can not finish the configuration process, user need to reset the power of LoRaWAN sensor again, by removing battery in at least 15s. Step 1: Install the Modbus Configurator Software in the link below https://filerun.daviteq.com/wl/?id=qK0PGNbY1g1fuxTqbFW9SXtEvCw7bpc6 How to use the Modbus configuration software Step 2: Plug the configuration cable to computer via USB port and install the driver; Step 3: Open the plastic housing with L hex key to unscrew M4 screws at the side of the housing Step 4: Plug the connector to the configuration port; Step 5:  Import the configuration file by importing the csv file: Go to MENU: FILE / Import New / => select the file with name CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0.csv (in the link below). Then click Connect; CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0 To write new value to the device:First, you need to write the password in "password for setting", after reading the value to check ok, you can write the new value AppEUI, AppKey, ...You only have 60 seconds after plugging the configuration cable or the power supply into the device for configuration. 5.2 Register table Here is the table of Data will be read by Modbus tool Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 0 0 3 5 device info AS923 string Read SKU+FW=WSLRW-V1A-FW1 5 5 3 4 firmware version DR5:5470 string Read ddmm = day / month 9 9 3 2 hardware version BW125 string Read 11 B 3 4 lorawan protocol version SF10 string Read lorawan v1.1.0 15 F 3 6 application version ADR OFF string Read application server v1.3.0.0 21 15 3 6 mac layer version A string Read mac layer v4.4.2.0 27 1B 3 4 deviceEUI uint16 Read EUI of  End Device; for registering on Network Server by OTAA 31 1F 3 4 lora appEUI uint16 Read EUI of  Application server; for registering on Network Server by OTAA 35 23 3 8 lora appKey uint16 Read Key to create 2 security code for End Device; for registering on Network Server by OTAA 43 2B 3 8 lora nwkSkey uint16 Read Key to encrypt data at MAC layer of End Device; for registering on Network Server by ABP 51 33 3 8 lora appSkey uint16 Read Key to encrypt data of End Device; for registering on Network Server by ABP 59 3B 3 2 device address float Read Address of End Device created by Application server; for registering on Network Server by ABP 61 3D 3 2 network ID float Read ID of Network Server; for registering on Network Server by ABP 63 3F 3 2 join mode uint16 Read OTAA: Over-the-Air activation; ABP: Activation by Personalization 65 41 3 4 network mode float Read PUBLIC; PRIVATE 69 45 3 3 region code float Read 1: AS923; 2: KR920; 3: AU915; 4: US915; 5: EU868; 6: IN865; 7: RU864; 8: CN779; 9: CN470; 10: EU433 72 48 3 4 data rate uint16 Read DR0:250; DR1:440; DR2:980; DR3:1760; DR4:3125; DR5:5470 76 4C 3 3 bandwidth uint16 Read BW125; BW250; BW500 79 4F 3 2 spread factor uint16 Read SF12; SF11; SF10; SF9; SF8; SF7 81 51 3 4 activation of ADR Read ADR ON; ADR OFF 85 55 3 1 class Read 103 67 3 1 sensor type Read 1-254: sensor type; 255: no sensor 104 68 3 1 battery level Read 4 level of battery 105 69 3 1 error status Read Sensor error code; 0: no error; 1: error 106 6A 3 1 prm1 alarm status Read Alarm status of parameter 1; 0: none; 1: Low; 2: High 107 6B 3 1 prm2 alarm status Read Alarm status of parameter 2; 0: none; 1: Low; 2: High 108 6C 3 2 prm1 value Read Value of parameter 1 110 6E 3 2 prm2 value Read Value of parameter 2 112 70 3 1 battery % Read Battery (%) 113 71 3 2 battery voltage Read Battery Voltage 115 73 3 2 mcu temperature Read Temperature of  RF module 117 75 3 1 mcu vref Read Value of Vref of RF module 118 76 3 1 button1 status Read Button status; 0: no button; 1: having button 119 77 3 1 button2 status Read Button status; 0: no magnetic sensor; 1: having magnetic sensor Here is the table for Configuration: Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 256 100 3 / 16 1 modbus address 1-247 1 uint16 Read/Write Device modbus address 257 101 3 / 16 1 modbus baudrate 0-1 0 uint16 Read/Write 0: 9600; 1: 19200 258 102 3 / 16 1 modbus parity 0-2 0 uint16 Read/Write 0: none; 1: odd; 2: even 259 103 3 / 16 9 serial number string Read/Write(Password) serial number 268 10C 3 / 16 2 password for setting uint32 Read/Write(Password) password 190577 270 10E 3 / 16 4 lora appEUI hex Read/Write(Password) EUI of  Application server; for registering on Network Server by OTAA 274 112 3 / 16 8 lora appKey hex Read/Write(Password) Key to create 2 security code for End Device; for registering on Network Server by OTAA 282 11A 3 / 16 8 lora nwkSkey hex Read/Write(Password) Key to encrypt data at MAC layer of End Device; for registering on Network Server by ABP 290 122 3 / 16 8 lora appSkey hex Read/Write(Password) Key to encrypt data of End Device; for registering on Network Server by ABP 298 12A 3 / 16 2 device address uint32 Read/Write(Password) Address of End Device created by Application server; for registering on Network Server by ABP 300 12C 3 / 16 2 network ID uint32 Read/Write(Password) ID of Network Server; for registering on Network Server by ABP 302 12E 3 / 16 1 activation mode 0-1 1 uint16 Read/Write(Password) 1: OTAA (Over-the-Air Activation); 0: ABP (Activation by Personalization) 304 130 3 / 16 1 application port 1-255 1 uint16 Read/Write(Password) port 224 only for certification 317 13D 3 / 16 1 region 1-7 1 uint16 Read/Write(Password) 1: AS923; 2: KR920; 3: AU915; 4: US915; 5: EU868; 6: IN865; 7: RU864; 8: CN779; 9: CN470; 10: EU433 318 13E 3 / 16 1 data rate 5 uint16 Read/Write(Password) 0: 250 bps; 1: 440 bps; 2: 980 bps; 3: 1760 bps; 4: 3125 bps; 5: 5470 bps 319 13F 3 / 16 1 tx power 2-20 16 uint16 Read/Write(Password) tx power: 2;4;6;8;10;12;14;16;18;20 320 140 3 / 16 1 adaptative data rate 0-1 0 uint16 Read/Write(Password) Auto change for data rate; 0: disable; 1: enable 334 14E 3 / 16 2 cycle send data 900 uint32 Read/Write second ; cycle of sending data to LoraWAN Gateway without condition 338 152 3 / 16 1 alarm limit 44 uint16 Read/Write Daily limit of  event 340 154 3 / 16 2 sensor sampling rate 900 uint32 Read/Write rate of sensor meaurement in second 342 156 3 / 16 2 sensor boot time 2500 uint32 Read/Write mili second; time for sensor power to be stable 348 15C 3 / 16 2 scale factor 1 float Read/Write Scale factor a for sensor output; Scaled value= measured value * scale_factor 352 160 3 / 16 2 Delta value 1 float Read/Write A threshold value: if the current value of sensor is less or larger than the previous value of the sensor with a threshold value; sensor will send the current data to a Gateway 6. Installation 6.1 Example application 6.2 Installation location To maximize the distance of transmission, the ideal condition is Line-of-sight (LOS) between the LoRaWAN sensor and Gateway. In real life, there may be no LOS condition. However, the LoRaWAN sensor still communicates with Gateway, but the distance will be reduced significantly. ATTENTION:DO NOT install the LoRaWAN 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, cement…is acceptable. 6.3 Battery installation Steps for battery installation: Step 1: Using L hex key to unscrew M4 screws at the side of the housing and carefully pull out the top plastic housing in the vertical direction Step 2: Insert 02 x AA 1.5VDC battery, please take note the poles of the battery ATTENTION: REVERSED POLARITY OF BATTERIES IN 10 SECONDS CAN DAMAGE THE SENSOR CIRCUIT!!! Step 3: Insert the top plastic housing and locking by L hex key ATTENTION: When reinstalling the cover, pay attention to put the PCB edge into the middle slot of the box inside as shown below) 7. Troubleshooting No. Phenomena Reason Solutions 1 The BLUE LED does not blink when the battery is installed Insert the battery in the opposite direction Insert the battery in the correct way 2 The RED LED is always on Due to noise, the peripheral components (i2c, spi, uart, ..) of RF module cannot be initialized After 30s the node will automatically reset. If the noise causes the Watchdog not to initialize, remove the battery and wait for more than 10 seconds, then insert the battery again 3 The RED LED blinks continuously (10ms ON / 2s OFF) and the Node does not send RF. After more than 10 sending cycles, the Node will automatically reset Operating frequency in that country is prohibited Operating frequency in that country is limited to Data rate, Tx Power Reconfigure the allowed frequency of operation Reconfigure Data rate = DR5 / SF07, Tx Power 4 RED LED blinks continuously (10ms ON / 2s OFF) and Node sends RF continuously 3s / time but no data. After more than 10 sending cycles, the Node will automatically reset Node runs dummy sending mode => sent by Gateway to send Downlink packets when users clear Uplink and Downlink counter values on Network Server (build-in Gateway) when activated by ABP Configuration enabled by OTAA 5 The RED LED flashes 10ms ON / 10s OFF and the Node does not send RF Node activation by OTAA on Network server has not been successful Using Magnet-Key to force Node to send RF continuously for 3 seconds/time => when activating by OTAA successfully, the GREEN LED will blink after sending RF 6 The node sent RF successfully but the GREEN LED did not blink LED is broken Warranty to replace LED 7 The data packet taken from the Gateway has an incorrect value The data package is encrypted Get the decoded packet on the Application Server 8 The node sends RF and activates by ABP, on Gateway receives data but the Application server has no data The application server still stores the counter values of the previous Uplink and Downlink Delete the counter values of Uplink and Downlink on the Application server 9 The node does not send RF and the RF module is hot Insert the battery in the opposite direction Short circuit Warranty or replacement 10 The node does not send RF to Gateway according to the alarm, LED does not blink The alarm configuration is incorrect Running out of the number of alarms set for the day Check alarm configuration Check the configuration for the maximum number of alarms per day 11 The node does not send RF to Gateway when activated by the magnetic key, LED does not blink The magnetic sensor has malfunctioned Read the status of the magnetic sensor via Modbus (when powering or attaching the battery) to see if the magnetic sensor is working. 12 Node has blinked LED GREEN when sending RF but the Gateway or Application server cannot receive LoRa module on the Gateway is faulty The IP connection (4G / WiFi / ...) on the Gateway is faulty Check Gateway's LoRa status lights on Gateway Check 4G / WiFi status lights on Gateway 13 The value of the sensor is 0 and sensor_type = 0xFF Lost connection with the sensor Check sensor connection Replace the module sensor 14 RSSI is weak and often loses data The distance between Node and Gateway is far or there are many obstructions Connection to Antenna problem Install metal nodes or in metal cabinets Configure Data rate = DR0 / SF12 Check Antenna position Install Node in a well-ventilated location 8. Support contacts Manufacturer Daviteq Technologies IncNo.11 Street 2G, Nam Hung Vuong Res., An Lac Ward, Binh Tan Dist., Ho Chi Minh City, Vietnam.Tel: +84-28-6268.2523/4 (ext.122) Email: info@daviteq.com | www.daviteq.com Distributor in Australia and New Zealand Templogger Pty Ltd Tel: 1800 LOGGER Email: contact@templogger.net Vizuo Applications LoRAWAN Sensors Manual For LoRaWAN Sensor as the following link: https://daviteq.com/en/manuals/books/manual-for-lorawan-sensor 1. Introduction Vizuo is a web-based software application to remotely configure device, parameter, alarm and event. In addition, Vizuo displays current values, historical values of parameters as well as events, alarms. Values of parameter are stored on database of GLOBIOTS server. Below figure describes the system which uses Vizuo application software: 2. User Information and Actions 2.1 Sign in - Open a web browser (Google Chrome/Firefox/Internet Explorer…).- Enter address in URL: http://vizuo.globiots.com/- Sign-in page displays as follow:  • Enter username and password  • Click “Sign in” button. - For user first time sign-in or reset password, user’s password must be changed after successful sign-in- Screen of change password: 2.2 Configure Node 2.2.1 Node Definition In Organization Chart Panel, Node is used to create Organization Chart. Node name should be geographical area, type of energy or responsible person. A Node includes one or more sub-Node and Device 2.2.2 Organization Chart To close or open “Organization Chart” panel, you can click on left corner of screen Organization Chart page includes all Node and Device in system:  • Node name  • Number using device of account/Max number device of accountRight click on Node name, menu of Node displays:  • New: Create new Node, Device  • Delete: Delete Node  • Assign to account: Assign Node and sub-Node to account  • Rename: Change name of Node 2.2.3 Create a Node To Create a sub-Node:  (1) Select Node  (2) Right click and select “New”  (3) Click “Node” to create new Node  (4) Enter sub-Node name and click button Save, then click button OK to confirm 2.2.4 Rename Node To change name of Node, right click on Node name → select Rename Or double click on Node. Enter new name and click button “Save Changes” to complete 2.2.5 Delete node In Organization Chart, select Node that you want to delete, right click Node name → select “Delete”, click button OK. Enter Username and Password of Account to confirm- Do not delete a Node that is assigned to account- Do not delete a Node that includes sub-node 3. Adding the Daviteq LoRAWAN Sensors to Vizuo Globiots 3.1 Create a new Daviteq LoRAWAN Sensors To create a new Daviteq LoRawan Sensors:  (1) Select Node  (2) Right click and select “New”  (3) Click “LoRa” to create a new Device (4) A box appears: At Basic information tab,  Enter parameters of Device:- Name: Name of Device (require 12 characters)- DevEUI: provided by manufacturer.- Click “Generate” button to create Device ID or enter ID directly At Network Server Config:- Network Server: Select the LoraWan Server are using- LoRa Device: Choose the right LoRa sensor series. Default is Daviteq Raw Payload Sensor- Downlink Message: The fields in this section are taken from the LoraWan Connection Server are using         (5) Click "Save Changes" to finish    o Logging send frequency: Frequency to send logged data from iConnector to server    o Heath send frequency: Frequency to send logged data about iConnector health from iConnector to serverClick “Save” to continue, click button OK to confirm, and enter admin user and password to verify permissionNote: After creating a Daviteq LoraWAN sensor on Vizuo application, the connection between the Network Server and Vizuo to forwarding sensor data must be configured. Refer to the instructions in relevant Network Server document for this configuration. 3.2 Configure Parameter Note: After receiving first uplink message, the default parameters are automatically created. Click on Device, right-click, select ParameterIn List Parameters Page  • “Import Parameter”: click to Import Parameters from excel file. Excel file must have default structure.  • “Export Parameter”: click to export parameter to excel file.  • “Add parameter”: click to add a new parameter.    o Name: parameter name    o Type: Real Parameter or Virtual parameter       Real Parameter: Parameter from LoraWAN sensors       Virtual Parameter: Parameter only in Server. Virtual parameter is create from formula of one or multi real parameter       If type is Virtual parameter, formula in Expression should be added        Mathematical Operators Operator Description + Additive operator / Unary plus - Subtraction operator / Unary minus * Multiplication operator, can be omitted in front of an open bracket / Division operator % Remainder operator (Modulo) ^ Power operator        Boolean Operators Operator Description = Equals == Equals != Not equals <> Not equals < Less than <= Less than or equal to > Greater than >= Greater than or equal to && Boolean and || Boolean or        Bit Operators << Left-shift bit operator in byte >> Right-shift bit operator in byte & AND bit operator in byte | OR bit operator in byte       Mathematical Functions Function* Description RANDOM() Produces a random number between 0 and 1 MIN(e1,e2, ...) Returns the smallest of the given expressions MAX(e1,e2, ...) Returns the biggest of the given expressions ABS(expression) Returns the absolute (non-negative) value of the expression ROUND(expression,precision) Rounds a value to a certain number of digits, uses the current rounding mode FLOOR(expression) Rounds the value down to the nearest integer CEILING(expression) Rounds the value up to the nearest integer LOG(expression) Returns the natural logarithm (base e) of an expression LOG10(expression) Returns the common logarithm (base 10) of an expression SQRT(expression) Returns the square root of an expression SIN(expression) Returns the trigonometric sine of an angle (in degrees) COS(expression) Returns the trigonometric cosine of an angle (in degrees) TAN(expression) Returns the trigonometric tangens of an angle (in degrees) COT(expression) Returns the trigonometric cotangens of an angle (in degrees) ASIN(expression) Returns the angle of asin (in degrees) ACOS(expression) Returns the angle of acos (in degrees) ATAN(expression) Returns the angle of atan (in degrees) ACOT(expression) Returns the angle of acot (in degrees) ATAN2(y,x) Returns the angle of atan2 (in degrees) SINH(expression) Returns the hyperbolic sine of a value COSH(expression) Returns the hyperbolic cosine of a value TANH(expression) Returns the hyperbolic tangens of a value COTH(expression) Returns the hyperbolic cotangens of a value SEC(expression) Returns the secant (in degrees) CSC(expression) Returns the cosecant (in degrees) SECH(expression) Returns the hyperbolic secant (in degrees) CSCH(expression) Returns the hyperbolic cosecant (in degrees) ASINH(expression) Returns the angle of hyperbolic sine (in degrees) ACOSH(expression) Returns the angle of hyperbolic cosine (in degrees) ATANH(expression) Returns the angle of hyperbolic tangens of a value RAD(expression) Converts an angle measured in degrees to an approximately equivalent angle measured in radians DEG(expression) Converts an angle measured in radians to an approximately equivalent angle measured in degrees         Data Type Conversion Functions Function Description FLOAT Converts values into 32-bit floating point numberFLOAT(0x02, 0x02, 0x02, 0x02) FLOAT([2000], [2001], [2002], [2003]) UINT8 Converts values into 8-bit unsigned integer number UINT8(22) UINT8([2000]) INT8 Converts values into 8-bit signed 2's complement numberINT8(22) INT8([2000]) UINT16 Converts values into 16-bit unsigned integer number UINT16(22, 23) UINT16([2000], [2001]) INT16 Converts values into 16-bit signed 2's complement number INT16(22, 23) INT16([2000], [2001]) UINT32 Converts values into 32-bit unsigned integer number UINT32(0x02, 0x02, 0x02, 0x02) UINT32([2000], [2001], [2002], [2003]) INT32 Converts values into 32-bit signed 2's complement number INT32(0x02, 0x02, 0x02, 0x02) INT32([2000], [2001], [2002], [2003]) GETBYTES Get bytes from hexadecimal stringGETBYTES([Address], position, length)POSITION là thứ tự byte, start là 0, index từ trái sang phải, length số byte cần lấyExample:Hexadecimal parameter with start address of [6100] and hexadecimal value of 0001020304 (00 01 02 03 04):byte 0: 00byte 1: 01byte 2: 02byte 3: 03byte 4: 04GETBYTES([6100], 3, 1) => result: 03GETBYTES([6100], 1, 3) => result: 010203          Logical Functions Function* Description NOT(expression) Boolean negation, 1 (means true) if the expression is not zero IF(condition,value_if_true,value_if_false) Returns one value if the condition evaluates to true or the other if it evaluates to false. The IF could be in another IF function AND(expression 1, expression 2, expression 3, …) Returns 1 (means true) if all true expressions, return 0 (mean false) if at least one false expression. OR(expression 1, expression 2, expression 3, …) Returns 1 (means true) if at least one true expression, return 0 (mean false) if all false expressions.   Supported Constants Constant Description e The value of e, exact to 70 digits PI The value of PI, exact to 100 digits TRUE The value one FALSE The value zero NULL The null value         Example 1:            Value of Virtual Parameter have address at 2012 is calculated as follow [2012] = [2000] + [2002. ]In which address 2000 and 2002 are two real parameters          Example 2:           IF [2000]>10 then [2005]=1            IF [2000]<=10 then [2005]=2         Example 3:           IF [2000]=1 And [2005]=2 then [2010]=5            IF [2000]=!1 And [2005]=!2 then [2010]=[2007]+10        Example 4:           IF [2000]>10  then [200A]=1            IF [2000]<10 And [2010]=1 then [200A]=5            IF [2000]<10 And [2010]=!1 then [200A]=10 Example 5: If value from [2000] is 0x40, [2001] is 0xb0, [2002] is 0x00 and [2003] is 0x00. Then result form expression FLOAT([2000], [2001], [2002], [2003]) is 5.5   o Unit: Unit of parameter    o Logged: Tick to permit saving value of parameter into database    o Logging Priority: enter any value    o Time to live: select how long data will be stored in database    o Data Type: Type of parameter    o Data Length: Length of data type, byte unit, display automatically with data type. If data type is String, data length should be input    o Address: Address on the server/cloud to store value of parameter    o Decimal Places: number of decimal after the comma.  • Save: click to finish  • “Delete All”: click to delete selected parameters  • Edit: click to edit this parameter  • Delete: delete parameter 3.3 Delete Daviteq LoRawan Sensors To delete a Device: Right click Device name and select Delete and click OK to confirm 3.4 Clone Daviteq LoRawan Sensors To create a new Device have same Parameters, Alarm Config, Modbus Command, Menmap, Event Configure …, select original Device, right-click, select “clone”. Below page appears Refer to 3.1 “Create a new Device” for more details. 3.5 Replace Daviteq LoRawan Sensors To replace Device:  • Right click Device name and select Replace  • A box displays:   o Enter the DevEUI of new Device    o Click “OK” to continue  • A box appearsClick “Yes” to finish 3.6 Rename Daviteq LoRawan Sensors To change name of Device: Right click Device name, select Rename, and enter new name 3.7 Create and send downlink type 0 and downlink type 5 for LoRaWAN Sensors 3.7.1 Create and send downlink type 0 At the organizational chart, right click on the LoRaWAN Sensor then select Downlink In Downlink configuration page, click tab “Type 00” Input the downlink 0 payload (hexa) for the sensor, then click synchronize Type 00, then select OK to complete inputting the downlink 0 configuration. Note: User could click Copy Latest Configuration button to copy latest configuration and edit this configuration to create new configuration. The below screen will be showed after clicking OK button After that, the downlink type 0 will be sent to Network Sever when there is any uplink message from the Network Server to Globiots. 3.7.2 Create and send Downlink type 5 At the organizational chart, right click on LoRaWAN Sensor then select Downlink. In Downlink configuration page, select tab “Type 05” Input parameter address (following the memory map of sensor) in Address (hex) Fill parameter name in Parameter Name Select data type of the parameter in the drop list at Data Type field. Input value of parameter in Value field. Click Add button to add input data. Click on Synchronize Type 05 button and click OK button confirm the input of downlink type 5. After that, the downlink type 0 will be sent to Network Sever when there is any uplink message from the Network Server to Globiots. 4. Report 4.1 Create a new report - To create a new report:  • In menu Management, select Report  • In Report page select “+ ” to create a new tab  • Report Page will display as follow:Enter full information:    o Name: Name of Report tab    o Report Type: Historical Trending (for parameter trend)    o Parameter Configuration:       Name: Name of parameter which display in report. Name might input text or name of parameter.       Device: select Device       Parameter: select parameter of device which you want show       Click “Add” to add parameter. A report might have some parameters.    o After completing adding parameter, click “save” to finish 4.2 Configure Report - In Report page, select Report name which you want configure  • Click “Delete” to delete report  • Click “Edit” to edit report       To edit available parameter, click in Action column, edit parameter, click Update       To delete parameter, click in Action       To Add new parameter: enter full information and click “Add” 4.3 View report Select Time in “From … To …” and click “Show” to view data of parameters on report tab Click on name of parameter (at the bottom of the report) to temporarily Show/Hide parameter on the report. 4.4 Export report After click button Show to view report, click on top right corner of screen, select Export to Excel or Export to pdf or Export to csv      Click Export to Excel, select version of Excel (2003 or 2007), click Export. The exported file will be store on your PC       Click Export to csv, select version Date Format in csv file, click OK. The exported file will be store on your PC       Click Export to pdf, the exported file will be store on your PC 5. Dashboard 5.1 Dashboard Description Dashboard views input text, current value and value from database. Each Dashboard is organized in one tab. When value is from database, dashboard will update the value after specific time. Dashboard consists of containers which contain widgets inside. 5.2 View Dashboard - In Home screen, select menu Management → select sub-menu Dashboard to display current value of parameters.- Screen of status “Dashboard”: - Screen of status “Stop” of Dashboard: • (1): Display list of Dashboard tabs which user are assigned to view  • Button “Run”: click to run Dashboard.  • Button “Stop”: click to stop selected Dashboard.  • Button “Delete”: click to delete Dashboard  • Button “Edit”: click to edit Dashboard  • Button “Add Container”: click to add new Container in Dashboard  • Button   : click to full screen  • Button “Export”: click to export Dashboard to Excel File  • Button “Import”: Click to import Dashboard to Excel File 5.3 Create new Dashboard - In Dashboard screen, click symbol “+” to create new tab - New window display • Name: Name of new Dashboard tab  • Stop real time after: Running time of Dashboard to get real time data from iConnector. After this period of time, Dashboard will stop to get real time data from iConnector.Click button “Run” on top right corner to continue to get real time data  • Push Interval: Frequency to get real time data from iConnector    Click Save to complete creating new Dashboard 5.4 Create New Container - In Dashboard tab, click Add Container to add new Container • Title: Name of container  • Format: Font size, Style, Text color, Text align, Background.  • Poll Interval: Frequency to get logged data from database to view on Dashboard  • Layout: Select layout of container. There are 07 layouts select    Click Save to complete creating Container 5.5 Configure a Container (1): Edit Container(2): Delete container.Click   to Edit Container. Following screen will appear - Click Add Widget to add new widget Note: Stop Dashboard before configure Container/Widget 5.6 Widget 5.6.1 Widget Description Widget is a basic element of Dashboard to view constant, value of parameter. Currently, Vizuo has below widgets After select widget click Add to add new widget to Container 5.6.2 Widget Table - Paging: Tick to view table more than one page- Border: Select type of border: None, Border and Inside- New Column: Click to add new column- New Row: Click to add new row     : Move column    : Configure cell    : Close/Delete column or row : Copy new row      : Click to select type of border for cell- Configure Row- After clicking , configuration screen for new row will appear   (1): Format    (2): ConfigureChoose Data type: Constant (input text), Data from Database (Device Name, Parameter Name, Unit of Parameter, Last value of parameter in Database, time stamp of last value Mapping: tick Mapping and list out value and mapped text, then click   to add mapping value. Mapping should be used to view meaningful text instead of value 5.6.3 Widget Line Chart Click to configure widget Line Chart, the following screen appear • Title: Line Chart name  • Style: Format of Title  • YAxis: Fixed or Auto. If choose Fixed, enter min & max value. If select Auto, software will specify Max of Y axis based on value of displayed parameter.  • Type: Data type of parameter to view (Data from device or from database)Type Database: Logged data from database, time period include: Today, Yesterday, Last 3 days or Custom (From…To)  • Line configuration: Select displayed parameter and displayed label (input text, parameter name or device name)Click Add button to add parameter to line chart. A line chart could view some parameters 5.6.4 Linear Gauge Click to configure widget Line Gauge, the following screen appear • Title: Name  • Style: Format of title  • Direction: Vertical or Horizontal Linear Gauge  • Min, Max: Range of Gauge  • Range Color: Auto or CustomAuto: Color of Gauge changes according to value of parameterCustom: Configure specific color to specific range of value of parameter  • Data: Select type of display parameter (last logged data from Database)  • Device/Parameter: Select displayed parameter  • Write: Tick to enable to write value to parameter. Writing value to parameter by holding and drag on body of Linear GaugeClick Save Changes to complete configuration 5.6.5 Solid Gauge Click to configure widget Solid Gauge, the following screen appear • Title: Name  • Style: Format of title  • Min, Max: Range of Gauge  • Range Color: Auto or CustomAuto: Color of Gauge changes according to value of parameterCustom: Configure specific color to specific range of value of parameter  • Data: Select type of display parameter (last logged data from Database)  • Device/Parameter: Select displayed parameterClick Save Changes to complete configuration 5.6.6 Circular Chart Click to configure widget Solid Gauge, the following screen appear • Title: Name  • Style: Format of title  • Min, Max: Range of Chart  • Range Color: Auto or Custom  • Auto: Color of Chart changes according to value of parameter  • Custom: Configure specific color to specific range of value of parameter  • Data: Select type of display parameter (last logged data from Database)  • Device/Parameter: Select displayed parameter  • Write: Tick to enable to write value to parameter. Writing value to parameter by holding and drag on body of Circular ChartClick Save Changes to complete configuration 5.6.7 Column Chart Click  to configure widget Solid Gauge, the following screen appears • Title: Column Chart name  • Style: Format of Title  • Type: Data type of parameter to view (Data from database)  • Type Database: Logged data from database, last value or value series in time period include: Today, Yesterday, Last 3 days or Custom (From…To)  • Column configuration: Select displayed parameter and displayed label (input text, parameter name or device name)Click Add button to add parameter to column chart. A column chart could view some parameters 5.6.8 EMS Report EMS Report views report for energy consumption during period of timeClick  to configure widget EMS report, the following screen appears: • Tittle: Report title  • Style: Format of tittle  • Report type: Daily, Weekly, Monthly  • Data range: Today, yesterday, last month, this month, last week, this week  • Column Configuration: Configure displayed value of parameter and displayed name of parameterClick Add to add parameter for report 5.6.9 Pie Chart Pie Chart compares values between some parameters. Click to configure widget EMS report, the following screen appears: • Tittle: Tittle of pie chart  • Style: Format of tittle  • Type: Data type, last value in database  • Configuration: Configure displayed value and displayed name of parameter 5.6.10 HTML Canvas How does the HTML Canvas widget work? When you select the widget, you will find a code editor as depicted in the image below. The widget works with the same HTML/CSS/JS you would code when creating a simple website. There's no need to learn a special API. It also considers the case when you may need to use a 3rd library (e.g. jQuery), so you can add these by inserting an URL containing the library. IMPORTANT NOTE: You should consider when writing code in this widget that all the execution will be made by your browser, we do not do any kind of poly-filling here, so it's up to your browser to support all the features that you make use of. The HTML code will be: The CSS code will be: The Java Script code will be: Full screen editor code. Get embed link: Public link, private link. Preview layout with current code before to save change. HTML Canvas Example Show Last Value Link Show Historical Trending Data Log Link Get Data From API Link 6. Export Raw Data - In menu Management, select Import/Export Raw Data- Select Export tab • Parameter: select Device and Parameter  • Time Zone: select time zone  • Data format: select Data format for export time  • From …To: Duration of time to exportClick “Export” to export value of parameter to csv file 7. Package Configuration In menu Configuration, select package configuration. The List of Packages displays as follow: - Click “Add package” to add new Package • Step 1: Enter basic information and click continue to next step  • Step 2: Select functions for package In Permission, select appropriate authorities and click continue to next step  • Step 3: View information of configuration and click “save changes” to finish- Click “Edit” to Edit available Package- Click “Delete” to Delete Package 8. Administrators 8.1 Account Management - Account might have sub-account to manage and assign authorities.- In Home screen, select menu Administrators → select sub-menu Account Management- In screen of account list, click button “Add account” to create new account. Enter information account into panel (1).Email: enter email address. Email is unique.Click button “Continue” to go to step 2.- Field with mark * must be filled- In email address, uppercase and lowercase are the same.- Select right Time Zone for user.- After click button “Continue”, screen of step 2 should appear: Enter information of admin user into panel (1):  • Username: Enter username. Username is unique.  • Email: Enter email address. Email is unique.  • Contact Number: Enter phone number. Phone number is unique.  • Click button “Continue” to go to step 3.- Screen of step 3 should appear: (1) Select package for account.Click button “Continue” to go to step 4.- Screen of step 4 should appear: (1) Display basic information of account in step 1.  (2) Display information of admin user in step 2.  (3) Display assigned package information in step 3.Click button “Save” to save configuration.After click button “Save”, confirmation screen should appear and click “OK” to finish.- After successfully create new account, an admin user of account is also created.- Number of used user of account increases by one for admin user.- Information of admin user should be in user list. 8.2 User Management 8.2.1 User creation User is created by following steps:- In Home screen, click menu Administrators → select sub-menu User Management- In screen of user list, click button “Add user” to add new user. Enter basic information into panel (1).  • Contact Number: Enter contact number. The number is unique.  • Click button “Continue” to go to step 2.- After click button “Continue”, screen of step 2 should appear:Enter information for user to sign-in into panel (1):  • Email: enter email address. Email is unique.  • Username: enter username for sign in. Username is unique. Username has at least 6 characters.  • Password: default password is “abc@123”. User must change password when user sign in in the first time.  • Click button “Continue” to go to step 3.- Enter full information for user.- Uppercase and lowercase of email and username are the same.Example: username “USERNAME1” is the same as username “username1”.- Screen of step 3 should appear: (1) Display basic information of user in step 1.  (2) Display information for sign in in step 2.Click button “Save” to save information.After click button “Save”, confirmation screen should appear and click button “OK” to finish.- If number of unused user of account > 0, user will be created successfully. Number of used user should increase by 1.- If number of unused user of account is equal to 0, user will not be created successfully.Screen of notification should appear when number of unused user of account is equal to 0: 8.2.2 Email address update Follow below step to update email address: Step 1: Login the Vizuo with user and provided password:- Open a web browser (Google Chrome/Firefox/Internet Explorer…).- Enter address in URL: http://vizuo.globiots.com/- Sign-in page displays as follow:  • Enter username and password   • Click “Sign in” button. - After successful sign-in, Dashboard screen will appearStep 2: Access the menu to update email address and verify - To view User Profile, click user name on right corner screen → select My Profile:- My Profile page displays as follow:- Input updated email to EMAIL field then click corresponding VERIFY BUTTON. After clicking, verification email will be sent to the email. User logs in email, open verification email and click verification button in email to verify email. If verification is successful, button VERIFY in row email should disappear Note: The verification email is valid only 24 hours since clicking VERIFY button. After 24 hours, the clicking verification button does NOT affect. In this case, user must click the VERIFY button again to have new verification email 8.3 Group Management - Group is used to assign authorities to users.- In Home screen, select menu Administrators → select sub-menu Group Management- In screen of group list, click button “Add Group” to create new group of account. Enter basic information of group into panel (1).  • Group Name: Enter group name. Group name is unique.  • Click button “Continue” to go to step 2.- After click button “Continue”, screen of step 2 should appear: • Select assigned functions for group in area  • Only display assigned functions of account.  • Select one function to assign, then click into area (1) to display authorities of selected function. Click authority to add into group.  • Click mark “x” (2) to remove authority.  • Click button “Continue” to go to step 3.- Screen of step 3 should appear: • (1) Display available nodes of account. Tick nodes to assign to group.  • Click button “Continue” to go to step 4.- Screen of step 4 should appear: • (1) Display list of users. The users have not been assigned to the group.  • (2) Display list of users which has already been assigned to the group.  • Button “Assign”: click to assign selected user to group. After click “Assign” button, selected user should be in the list in panel (2).  • Button “Remove”: remove user from group. After click button “Remove”, selected user should be in the list in panel (1).  • Click button “Continue” to go to step 5.- Screen of step 5 should appear: • (1) Display list of Dashboard of signing in group. The Dashboard has not been assigned to group.  • (2) Display list of Dashboard of signing in group. The Dashboard has already been assigned to group.  • Button “Assign”: click to assign dashboard to group. Assigned dashboard should be in panel (2).  • Button “Remove”: remove dashboard out of group. Removed dashboard should appear in panel (1).  • Click button “Continue” to go to step 6.- Screen of step 6 should appear to view Summary information of group from step 1 to step 8.  • Click button “Save” to save information.  • After click button “Save”, confirmation screen should appear and click button “OK” to finish. 9. Support contacts Distributor in Malaysia AVO Technology Sdn. Bhd. Official Website: www.avo.com.my No. 17, Jalan 3/23A, Taman Danau Kota, 53300 Kuala Lumpur, Wilayah Persekutuan Kuala Lumpur, Malaysia General : +603-4143 2288 Mobile : +012-376 7181Fax : +603-4143 3388 Distributor in Australia and New Zealand Templogger Pty Ltd Tel: 1800 LOGGER Email: contact@templogger.net Manufacturer Daviteq Technology Company Ltd.No.11 Street 2G, Nam Hung Vuong Res., An Lac Ward, Binh Tan Dist., Ho Chi Minh City, Vietnam.Tel: +84-28-6268.2523/4 (ext.122) Email: info@daviteq.com | www.daviteq.com Manual for Indoor LoRaWAN Gateway - GWIND Thank you very much for choosing Daviteq Wireless Sensors. We are the leading wireless sensor manufacturer in the World. We have a wide range of wireless sensors which support different connectivity like LoRaWAN, Sigfox, Sub-GHz, NB-IoT...Please find out more information at this link. This manual is applied to the following products Item code HW Version Firmware Version Remarks GWIND-9 1.0 1.0 To use this product, please refer step by step to the below instructions. 1.  Quick Guide Reading time: 10 minutesFinish this part so you can understand and put the sensor in operation with the default configuration from the factory. 1.1 What is the GWIND ? GWIND is a LoRaWAN Gateway designed for indoor installation, used in projects such as Smart Factory, Smart Agriculture, Smart Building, Smart Residential Area, Smart City... It supports simultaneously 8 connection channels to help receive a large number of packets from surrounding LoRaWAN sensors. The connection distance to the LoRaWAN sensors is up to 10 Km (depending on the environment and sensor types). It supports common communications such as Ethernet, LTE, WiFi. LoRa frequency support 863~870 MHz / 902~928 MHz.This LoRaWAN Gateway is widely used in applications such as reading water meters, electricity meters, gas meter, environmental monitoring, smart farms, smart factories... 1.2 What's in the package? The package includes:01 x LoraWAN Gateway01 x Lora Antenna01 x LTE Antenna01 x Adapter 1.3 Product Overview 1.3.1 I/O Ports 1.3.2 LED Functions LED Functions Constant Flashing Off Power Power On Booting /OTA OFF Internet Internet Available Checking Internet RFU Service LNS Connected RFU LNS Not Connected LoRa LoRa Working Initializing LoRa Not Working 1.3.3 Reset Button Reboot:By pressing and holding the RESET Button, the Power LED will start flashing. The “reboot” procedure will be triggered when the RESET Button is released while the Power LED light isflashing. Restore to Default:By pressing and holding the RESET Button, the Power LED will start flashing. The “restore to default” procedure will be triggered when the RESET Button released after the Power LEDlight becomes constant. 1.4 Installation Startup the LoraWAN Gateway through the following steps Step 1: Install the antennas of the LoRaWAN Gateway Install the antennas in the correct position. Make sure the antennas and Gateway are tightly connected. Step 2: Insert the SIM card into the LoRaWAN Gateway Remove the plastic plate in the SIM socket, then insert the SIM card into the socket with correct SIM direction. Pay attention to the direction of the SIM Note: If the gateway use only Ethernet port to connect to Network Sever, skip step 2 Step 3: Connect the Ethernet cable and power up the Gateway Connect the Ethernet cable into RJ45 port. After that, Connect the power adapter provided to the DC jack In. The gateway will automatically turn on after powering up. 1.5  Configure the LoRaWAN Gateway 1.5.1 GUI Access Default mode of Daviteq Gateway is DHCP. Once gateway is turned on through plugging in the DC adapter, it will automatically link to available servers. Gateway’s IP address can be found from the DHCP server. Access Gateway Web UI via the DHCP IP on browser. The default username is “admin”, and the password can be found on the back label. To access the GUI, follow these steps: Step 1: Use a computer to connect to the network that the gateway is connected. The computer can connect to that network via WiFi or Ethernet. Step 2: Use the IP scanning software to find the IP address of the gateway based on its Mac address that can be found on the back label. Access this link  to get a free IP scanning software on the internet Step 3: Enter the IP address of the gateway in the web browser to access the configuration interface. For example, If the IP address of the Gateway is 192.168.1.15 , you should enter exactly that information in web browser, then the GUI will be displayed. 1.5.2 WAN configuration The purpose of this category is to view current WAN settings. This category is further divided into three sectors: WAN Status, Wan Settings and 3G/4G LTE Log. WAN Status The current network status will be shown on this page. WAN Settings Daviteq Gateway supports three WAN Modes: Ethernet WAN, 3G/4G LTE and Dual WAN (Ethernet+3G/4G). Default mode of Daviteq Gateway is Dual WAN. Note: Configure “APN” information according to mobile service provider requirements. 1.5.3 Lora Settings The LoRa menu consists of the following categories: Mode Selection, Channel Scan and Log. Configure some basic fields for the gateway operation. Mode selection At the field, choose the "Packet Forwarder" option and click the "APPLY" button to Enable the Packet Forwarder mode. After applying the setting, the "Packet Forwarder" field can be found on the left menu. Packet Forwarder configuration Select Packet Forwarder in the left menu, then choose Gateway Info. This page is for setting up the LoRa configuration including Gateway ID, Server Address, Server Uplink Port, Server Downlink Port, Keep-Alive Interval, Statistics Display Interval, and Push Timeout. Need to properly configure the Server Address, Server Uplink Port, and Server Downlink Port fields. These information depend on the Network server. Radio and Channel Settings This page is for configuring the radio 0 and radio 1 configurations of Lora, including Central Frequency, Channel Status, and Center frequency offset. The frequencies and channels are regulated by the lora-alliance, region and the network server. Below is an example of the configuration of the frequency AS923-2. 1.6 Add the LoraWAN Gateway to Network Server To give an example, please follow the instructions in this link  to add LoraWAN gateway to The things Stack network server. 2. Product specification LoRaWAN Specification LoRaWAN 1.0.3 Frequency Band Select 863~870 MHz / 902~928 MHz Number of Channels Up to 8 concurrent channels for LoRa transmission LoRa Transmit Power 0.5W (up to 27 dBm) LoRa Receive Sensitivity Down to -142 dBm (conducted) LoRa Software Standard and LRR Actility Operating Temperature -10°C ~ 55°C Storage Temperature -20°C ~ 60°C Power Supply DC 12 V/1.5 A-Power Adaptor / DC 10~30 V 3-Pin Connector Power supply / Passive PoE 10~30 V 4G LTE LTE Cat 4 or Cat M1/NB2 Interfaces 1 WAN RJ45 10/100Mbps (w/ passive PoE capability), 1 SIM card slot (2FF), 1 DC jack in / 1 terminal block Antenna Type 1 x external LoRa antenna, 1 x External antenna for LTE Dimensions L:120 x W:136 x H:35mm Weight 0.4 kg Vietnam Type Approval pending 3. Warranty and Support For warranty terms and support procedures, please refer to this link. 4. References Use-cases: Case studies: White-papers: END. Manual for Outdoor LoRaWAN Gateway - GWLRW Thank you very much for choosing Daviteq Wireless Sensors. We are the leading wireless sensor manufacturer in the World. We have a wide range of wireless sensors which support different connectivity like LoRaWAN, Sigfox, Sub-GHz, NB-IoT...Please find out more information at this link. This manual is applied to the following products Item code HW Version Firmware Version Remarks GWLRW-9 1.0 1.0 To use this product, please refer step by step to the below instructions. 1.  Quick Guide Reading time: 10 minutesFinish this part so you can understand and put the device in operation with the default configuration from the factory. 1.1 What is the GWLRW ? GWLRW is a LoRaWAN Gateway designed for outdoor installation, used in projects such as Smart Factory, Smart Agriculture, Smart Building, Smart Residential Area, Smart City... It supports simultaneously 8 connection channels to help receive a large number of packets from surrounding LoRaWAN sensors. The connection distance to the LoRaWAN sensors is up to 10 Km (depending on the environment and sensor types). It supports common communications such as Ethernet, LTE, WiFi. LoRa frequency support 863~870 MHz / 902~928 MHz. This LoRaWAN Gateway is widely used in applications such as reading water meters, electricity meters, gas meter, environmental monitoring, smart farms, smart factories... 1.2 What's in the package? The package includes:01 x LoraWAN Gateway01 x Lora Antenna01 x LTE Antenna01 x Adapter01 x Accessory set 1.3 Product Overview 1.3.1 I/O Ports 1.3.2 LED Functions LED Functions Constant Flashing Off Power Power On Booting /OTA OFF Internet Internet Available Checking Internet RFU Service LNS Connected RFU LNS Not Connected LoRa LoRa Working Initializing LoRa Not Working 1.3.3 Reset Button Reboot:By pressing and holding the RESET Button, the Power LED will start flashing. The “reboot” procedure will be triggered when the RESET Button is released while the Power LED light isflashing. Restore to Default:By pressing and holding the RESET Button, the Power LED will start flashing. The “restore to default” procedure will be triggered when the RESET Button released after the Power LEDlight becomes constant. 1.4 Installation Startup the LoraWAN Gateway through the following steps Step 1: Install the antennas of the LoRaWAN Gateway Install the LTE antenna and the Lora antenna in the correct position. Make sure the antennas and Gateway are tightly connected. Step 2: Insert the SIM card into the LoRaWAN Gateway Remove the plastic plate in the SIM socket, then insert the SIM card into the socket with correct SIM direction. Pay attention to the direction of the SIM Note: If the gateway use only Ethernet port to connect to Network Sever, skip step 2 Step 3: Connect the Ethernet cable and power up the Gateway Connect the Ethernet cable into RJ45 port. After that, connect the power adapter provided to the Terminal Block ,then the gateway will automatically turn on after powering up. Step 4 : Close the gateway's cover, then use the hex wrench to lock the 4 screws. 1.5 Mounting Step 1: Mount the bracket to the steel pole with a hose clamp or attach it to the wall. Then mount the gateway on the bracket. Step 2: Secure the M4 screw 1.6  Configure the LoRaWAN Gateway 1.6.1 GUI Access Default mode of Daviteq Gateway is DHCP. Once gateway is turned on through plugging in the DC adapter, it will automatically link to available servers. Gateway’s IP address can be found from the DHCP server. Access Gateway Web UI via the DHCP IP on browser. The default username is “admin”, and the password can be found on the inside label. To access the GUI, follow these steps: Step 1: Use a computer to connect to the network that the gateway is connected. The computer can connect to that network via WiFi or Ethernet. Step 2: Use the IP scanning software to find the IP address of the gateway based on its Mac address that can be found on the back label. Access this link  to get a free IP scanning software on the internet Step 3: Enter the IP address of the gateway in the web browser to access the configuration interface. For example, If the IP address of the Gateway is 192.168.1.15 , you should enter exactly that information in web browser, then the GUI will be displayed. 1.6.2 WAN configuration The purpose of this category is to view current WAN settings. This category is further divided into three sectors: WAN Status, Wan Settings and 3G/4G LTE Log. WAN Status The current network status will be shown on this page. WAN Settings Daviteq Gateway supports three WAN Modes: Ethernet WAN, 3G/4G LTE and Dual WAN (Ethernet+3G/4G). Default mode of Daviteq Gateway is Dual WAN. Note: Configure “APN” information according to mobile service provider requirements. 1.6.3 Lora Settings The LoRa menu consists of the following categories: Mode Selection, Channel Scan and Log. Configure some basic fields for the gateway operation. Mode selection At the field, choose the "Packet Forwarder" option and click the "APPLY" button to Enable the Packet Forwarder mode. After applying the setting, the "Packet Forwarder" field can be found on the left menu. Packet Forwarder configuration Select Packet Forwarder in the left menu, then choose Gateway Info. This page is for setting up the LoRa configuration including Gateway ID, Server Address, Server Uplink Port, Server Downlink Port, Keep-Alive Interval, Statistics Display Interval, and Push Timeout. Need to properly configure the Server Address, Server Uplink Port, and Server Downlink Port fields. These information depend on the Network server. Radio and Channel Settings This page is for configuring the radio 0 and radio 1 configurations of Lora, including Central Frequency, Channel Status, and Center frequency offset. The frequencies and channels are regulated by the lora-alliance, region and the network server. Below is an example of the configuration of the frequency AS923-2. 1.7 Add the LoraWAN Gateway to Network Server To give an example, please follow the instructions in this link to add LoraWAN gateway to The things Stack network server. 2. Product specification Please refer to the detailed specifications in this link 3. Warranty and Support For warranty terms and support procedures, please refer to this link. 4. References Use-cases: Case studies: White-papers: END. Manual for Indoor Micro LoRaWAN Gateway - GWIML Thank you very much for choosing Daviteq Wireless Sensors and Gateways. We are the leading wireless sensor manufacturer in the World. We have a wide range of wireless sensors and gateway which support different connectivity like LoRaWAN, Sigfox, Sub-GHz, NB-IoT...Please find out more information at this link. This manual is applied to the following products Item code HW Version Firmware Version Remarks GWIML-8-WF-ETH-01 1.0 1.0 To use this product, please refer step by step to the below instructions. 1.  Quick Guide Reading time: 10 minutesFinish this part so you can understand and put the sensor in operation with the default configuration from the factory. 1.1 What is the GWIML ? GWIML is a Micro LoRaWAN Gateway designed for indoor installation, suitable for small businesses or private area use cases like parking spaces, exhibition centers or campuses, etc. It is also suitable for providing coverage for indoor blind spots. It supports simultaneously 8 connection channels to help receive a large number of packets from surrounding LoRaWAN sensors. It supports host common communications, Ethernet or WiFi. For LoraWAN communication, it supports LoRa frequency 863~870 MHz / 902~928 MHz. 1.2 What's in the package? The package includes:01 x Micro LoraWAN Gateway01 x Lora Antenna01 x Power adapter (USB Charger 100-240VAC 50/60Hz to 5VDC/2A) 01 x USB cable 1.5 meters for charging purpose01 x Ethernet cable 1.3 Product Overview 1.3.1 I/O Ports 1.3.2 LED Functions 1.3.3 Reset Button Only use for troubleshooting 1.4 Installation Startup the LoraWAN Gateway through the following steps Step 1: Install the antennas of the LoRaWAN Gateway Install the antenna in the correct position. Make sure the antenna and Gateway are tightly connected. Step 2: Connect the Ethernet cable and power up the Gateway Connect the Ethernet cable into RJ45 port of the gateway and the port of Ethernet network. After that, connect the power adapter provided to the Micro USB port. The gateway will automatically turn on after powering up. Note: If the gateway use  WiFi mode connect to Network Sever, Skip connect the Ethernet cable 1.5  Configure the LoRaWAN Gateway 1.5.1 GUI Access Once gateway is turned on through plugging in the adapter, it will become a local wifi access point. To access the GUI, follow these steps: Step 1:Connect to Micro Gateway via local wifi (SSID: on the gateway label). Step 2: Enter the default IP address (192.168.55.1) of the gateway in the web browser to access the configuration interface. The default username is “admin” and the password is "admin“. 1.5.2 WAN configuration The purpose of this category is to view current WAN settings. This category is further divided into three sub- sectors: WAN Status, Ethernet Wan and Wireless Extender. These individual options are lodged and labeled above the main content panel. WAN Status The current network status will be shown on this page. Ethernet WAN This page is to set up the connection type in terms of Static IP, DHCP client, or PPPoE. The three different options can be selected in the drop-down menu in “wantype”. Please fill in the respective fields exhibited under each selection. Please make sure the Ethernet cable is connected to a WAN port. Wireless Extender This page is to set up the Wireless Extender Mode for the WAN connection. To activate the extended wireless connection, please select “enable” from the Extender mode drop-down menu. Click the “SCAN” button to obtain the list of available Access Points within your surrounding vicinity. 1.5.3 Lora Settings (Packet Forward) The purpose of this category is to view/edit current Packet Forward settings and logs. Sever Settings Select Packet Forwarder in the left menu, then choose Setting. After that, select Gateway Infor tab. This page is for setting up the LoRa configuration including Gateway ID, Server Address, Server Uplink Port, Server Downlink Port, Keep-Alive Interval, Statistics Display Interval, and Push Timeout. Need to properly configure the Server Address, Server Uplink Port, and Server Downlink Port fields. These information depend on the Network server. Get the Gateway ID to register the device on Network Server in this step. Radio and Channel Settings This page is for configuring the radio 0 and radio 1 configurations of Lora, including Central Frequency, Channel Status, and Center frequency offset. The frequencies and channels are regulated by the lora-alliance, region and the network server. Below is an example of the configuration of the frequency EU868. 1.6 Add the LoraWAN Gateway to Network Server To give an example, please follow the instructions in this link  to add LoraWAN gateway to The things Stack network server. 2. Product specification LoRaWAN Specification LoRaWAN 1.0.3 Frequency Band Select 863~870 MHz / 902~928 MHz Number of Channels Up to 8 concurrent channels for LoRa transmission LoRa Transmit Power 0.5W (up to 27 dBm) LoRa Receive Sensitivity Down to -142 dBm (conducted) LoRa Software Standard and LRR Actility Operating Temperature -10°C ~ 55°C Storage Temperature -20°C ~ 60°C Power Supply 5VDC/2A via mini-USB port Wireless LAN 802.11 b/g/n 2.4G Interfaces LAN 10/100Mbps, 1 USB 2.0 for firmware upgrade, 4 LED indicators Antenna Type Built-in Wi-Fi and LoRa antenna and one (1) external SMA connector for LoRaantenna Dimensions L:116 x W:91 x H:27 mm Weight 0.4 kg 3. Warranty and Support For warranty terms and support procedures, please refer to this link. 4. References Use-cases: Case studies: White-papers: END. Sample HTML table for troubleshooting No. Phenomena Reason Solution   1 Node does not send RF to the base station periodically and LED does not blink There is no power supply or battery is flat Measure the voltage of the battery OR  check the installation of the battery OR check the power supply if applicable The configuration sending cycle is incorrect or is accidentally changed Check the sending cycle configuration by offline tool Hardware node is defective Check with offline tool and/or check visually any burnt mark, disconnection, heat on the hardware. Contact manufacturer for repair or replacement if needed The node is accidentally in black-list of Sigfox operator Check with the Sigfox operator The Sigfox base stations at the node location are out of operation Check the operation of another node at the same location or check with Sigfox operator about status of the Sigfox base station New objects are added between the sensor and Sigfox base station Check and remove the obstruction objects at site   2 Node does not send RF to the base station according to the alarm, LED does not blink The alarm threshold values are incorrect and/or alarm function is disabled Check alarm threshold values and alarm enable on start up message or heartbeat message or parameter update message or on node memory map with offline tool The number of real alarms during 24-hour are greater than daily alarm limit Check the configuration for the maximum number of alarms per day on node memory map   3 Node does not send RF to the base station when activated by the magnetic switch, LED does not blink The magnetic switch has malfunctioned Read the status of the magnetic switch via Modbus (when powering or attaching the battery) to see if the magnetic switch is working OR check the magnetic switch visually Magnet key is not in right touching-position on node housing Put the correct position for the magnet key on the node housing   4 Node has blinked LED when sending RF but the base station cannot receive the data The number of sending message during 24-hour are greater than the limit RF packages of uplink per day (max 140 packages/day) Check on the base station whether the event message exceeds the number of RF packets   5 Node has sent RF but the LED does not blink The LED is malfunctioned Contact manufacturer for repair or replacement   6 The node does not send RF and the RF module is too hot Battery is inserted in the wrong direction Check battery polarity Working environment of the node is too hot Improve ventilation to lower environment temperature Hardware node is defective Contact manufacturer for repair or replacement   7 RSSI is weak and often loses data Distance between Node and Base station is too far Check the location of the Sigfox node and relocate it if applicable There are many obstructions between the node and Sigfox base station Check and remove the obstruction objects at site or re-locate the position of the node if applicable New objects are added between the sensor and Sigfox base station Check and remove the obstruction objects at site There is a problem of Sigfox antenna connection Check the antenna connector on the printed circuit board   8 The measurement values from the sensor do not change and keep constant values for a long time Sensor got failure Check the sensor visually or/and with offline tool. Contact manufacturer for repair or replacement if needed Sensor cable is broken Check sensor cable. Contact manufacturer for repair of replacement if the cable is broken The sensor connector is not connected firmly Check sensor connector and contact manufacture for repair of replacement if the connector is broken Some sensor measurement settings such as CONSTANT_A, CONSTANT_B, LOW_CUT, HIGH_CUT are misconfigured Check and correct right sensor measurement configurations HTML table for default configuration Description Unit Default Format Property Comment CONSTANT_A                   1 Float R/W Constant A for scaling measured value CONSTANT_B                   0 Float R/W Constant B for scaling measured value HIGH_CUT  1000000000 Float R/W High cut value for calculated value LOW_CUT                   0 Float R/W Low cut value for calculated value SENSOR_BOOT_TIME ms             1000 Uint32 R/W Boot time of sensor/input, in ms NUM_OF_SAMPLE                 10 Uint16 R/W A number of samples for filtering function. The higher value, the more filtering Instruction:1, Copy from Excel. paste from row 2 2, Select all cells, configure Top alignment, background color #c6e2ff 3, Select cells in even rows, configure background color #f2f2f2  (light grey) 3, Configure all cell in first row as header type 4, Add SPACE in value of DEFAULT column for left alignment 5, Copy code and paste on wix.com, edit the width of 805px in html editorHTML table for LRW connection Field Input field Name As user-defined LRR-UUID Contact the Tektelic Support to get LRR-UUID for Thingpark. Details at linkInstruction to get info from the LRR gateway RF region Site frequency plan (US915, EU868..) Public Key Contact the Tektelic Support to get LRR-UUID for Thingpark. Details at linkInstruction to get info from the LRR gateway HTML table for LRW configuration Field Input field Frequency name Input correct frequency plan (Ex: Australia 915-928 MHz, FSB 2 (used by TTN)) DevEUI As DevEUI on label of the device or  read from device memory map Activation mode Over-the-Air Activation (OTAA) with local Join Server AppEUI Input AppEUI. This value read on device memory map or on the label of the device. The default value is 0102030405060708 AppKey Input AppKey.This value read on device memory map or on the label of the device. The default value is 0102030405060708090A0B0C0D0E0F10 Lorawan version Must be choose version 1.0.3 HTML table for LED indication Reed Switch Uplink message Pre-condition Action Led Status Activities Post-condition 1 FORCE_DATA Any state Move Magnet Key to contact point of REED SWITCH. Led blink SKY BLUE, move Magnet Key away. Blink SKY BLUE See FW specs Back to previous state 1 PARAMETERS_UPDATE Any state Move Magnet Key to contact point of REED SWITCH. Led blink SKY BLUE, hold Magnet Key 5s. Led blink PURPLE, move Magnet Key away. Blink PURPLE See FW specs Back to previous state Sample HTML table No. Phenomena Reason Solution    1 The distance value always shows 250mm The object/surface is very close to the sensor and within the dead zone of the sensor. Do nothing. This is the standard feature of the sensor. The sensor can only measure the distance from 280mm to 7500mm. The transducer is covered by a thick layer of dust or particles. Clean the transducer surface with a soft detergent and clean water.    2 The distance value always shows distance last time or zero value The object/surface is too far away from the sensor. The object/surface is out of the detection range of the sensor. Make sure the measuring distance to be within the detection range of the sensor (280mm to 7500mm)    3 The distance/level value fluctuates largely. The object's surface is not flat. Try to increase the parameter Num_of_samples to increase the filtering so that the sensor can deliver a stable average value. But this will cause the battery life to be shorter.    4 The level value is not accurate with the actual level of liquid The transducer is covered by a thin layer of dust or particles. Clean the transducer surface with a soft detergent and clean water. The CONSTANT_A and CONSTANT_B settings are wrong. Check the CONSTANT_A and CONSTANT_B settings again    5 The value of HW_Error field equals 1 The connection between the transducer and the main PCB are lost. Open the sensor housing and check the internal wire and connector from the transducer to the wireless PCB. The transducer got a problem. Contact the manufacturer for repair or replacement. Sample HTML table for troubleshooting 2 No. Phenomena Reason Solution 1 The wireless transmitter is still running and sending data, however, all the measurement parameters are not updated with new values The connection between the AG tilt sensor and the wireless transmitter is broken Contact the manufacturer for repair or replacement The battery is almost draining off Check the battery status and replace it when necessary 2 The measured values are not as expected The installation direction is not correct Re-check the installation The sensor is drifting Contact the manufacturer for repair or replacement The calibration position or calibration process is incorrect Re-calibrate the device with right position and right process 3 The reading values are very noisy even though the sensor is in a standstill position. The sensor AG tilt sensor got a problem Contact the manufacturer for repair or replacement External factors at installation location such as wind, vibration, temperature, sun, heat might affect the tilt value External factors such as wind, vibration, temperature, sun, heat at installation location 4 The value of HW_Error equal 1 The lost connection between the AG sensor and the wireless transmitter Contact the manufacturer for repair or replacement The sensor AG sensor got a problem Contact the manufacturer for repair or replacement HTML table for LED indication 2 Uplink message Pre-condition Action Led Status Buzzer Status Activities Post-condition FORCE_DATA Any state Move Magnet Key to contact point of REED SWITCH. Led blink SKY BLUE and buzzer beep 1 time, move Magnet Key away. Blink SKY BLUE Beep 1 time See FW specs Back to previous state PARAMETERS_UPDATE Any state Move Magnet Key to contact point of REED SWITCH. Led blink SKY BLUE and buzzer beep 1 time. Then hold Magnet Key 5s, Led blink PURPLE and buzzer beep 2 times, move Magnet Key away. Blink PURPLE Beep 2 times See FW specs Back to previous state USER GUIDE FOR LORAWAN SENSOR WSLRW WSLRW-MN-EN-01 DEC-2023 This document is applied for the following products SKU WSLRW 1. Configuration Check List STEP 1: Configure End Device (Using Modbus Configuration Cable) Setting value (Example) 1. Select region AS923, IN865, EU868,.. (refer to register address 317) 2. End Device Operation OTAA or ABP OTAA Write AppEUI information from Application Server to Lorawan End Device; Write AppKey (created by user) information for Lorawan End Device and Application Server. ABP Write DevEUI information from Application Server to Lorawan end device; write Network Session Key and App Session Key (created by user) information to Lorawan end device (and Application Server). 3. Configure "cycle send data" 900 sec (Defaut) 4. Configure "sensor sampling_rate" 120 sec (Defaut) 5. Configure parameters of sensor (Refer to Check data configuration table) STEP 2:  Configure the operation of LoRaWAN Gateway (Ex: URSALINK Gateway) 1. Configure the information in the General tab Server address, Server port (For more information) 2. Configure the information in the Radio tab Select the Region Region (Other parameters to default) STEP 3:  Configure the operation of LoRaWAN Gateway on Network Server (Ex: URSALINK Gateway with Thethingsnetwork) 1. Gateway ID registration Gateway ID is the GatewayEUI information on the Gateway 2. Frequency Plan parameters configuration Asia 920-923MHz, Europe 868MHz,... 3. Router parameters configuration 4. Check the connection of the gateway to the network server The Gateway status LED lights up and displays the message "Status: conneted" on the Thethingsnetwork STEP 4:  Configure the operation of Application Server on Network Server 1. App ID registration 2. Handler parameters configuration STEP 5: Register Lorawan End Device on Application Server on Thethingsnetwork 1. ID Registration 2.Select operation mode OTAA or ABP OTAA Configure parameters DevEUI and AppKEY ABP Configure parameters Device Address, Network Session Key, App Session Key 2. Introduction WSLRW is LoRaWAN Sensor that support multiple sensor types via I2C, SPI, UART... input signal. With Ultra-low Power design and smart firmware allow the sensor can last up to 10 years with 02 x AA-type battery (depends on configuration). The sensor will transmit data in kilo-meters distance to LoRaWAN gateway, any brand on the market. 3. Specification Sensor Input I2C, SPI, UART, Digital Input 0-3.3V, Analog input 0-3V Data rate 250bps .. 5470bps Antenna Internal Antenna 2.0 dbi Battery 02 x AA size 1.5VDC, battery not included RF Frequency and Tx Power US915, max +20 dBm Tx Protocol LoRaWAN, class A Data sending modes interval time, alarm occurred and manually triggering by magnetic key Working temperature -40oC..+60oC Dimensions H106xW73xD42 Net-weight 190 grams Housing Aluminum + Polycarbonate plastic 4. Operation Principle 4.1 LoRaWAN protocol specifications 4.1.1 LoRaWAN Sensor protocol specifications LoRaWAN Protocol Version 1.0.3 Application Server Version 1.3.0.0 MAC Layer Version 4.4.2.0 Radio Standards: LoRa Alliance Certified LoRaWAN Zone: US915 Class A Join Active: OTAA / ABP Network Mode: Public Network / Private Network Tx Power: up to 20 dBm Spreading factor: SF10 - SF7 Bandwidth: 125 kHz Unconfirmed-data message LoRaWAN application port for certification: 224 4.1.2 Data rate of LoRaWAN Sensor Data rate name Data rate (bps) Spreading factor (SF) Bandwidth (kHz) Region DR0 980 SF10 125 US915 DR1 1760 SF9 125 DR2 3125 SF8 125 DR3 5470 SF7 125 4.1.3 Tx power of LoRaWAN sensor Max EIRP (dBm) Max Tx Power (dBm) Region 30 20 US915 4.2 The principle of operation of the LoRaWAN sensor When starting the power supply, the LoRaWAN sensor has 60 seconds to allow configuration to operate via the Configuration Cable with the Modbus RTU protocol. After 60 seconds, the first packet will be sent, then the LoRaWAN sensor will send the next packets in the following cases: Case 1: When it reaches the frequency of taking data, the LoRaWAN sensor will wake up to measure and calculate. Then: If the measured value exceeds the High or Low setting thresholds, the packet will be sent to the Gateway and then asleep; If NOT then sleep without sending data. NOTE: Once sending the data to Gateway by this alarm event, the timer of sending time interval will be reset; Case 2: When the sending time interval is reached, the LoRaWAN sensor wakes up to measure and calculate and send data to Gateway immediately, regardless of value. Case 3: By using the magnet key, the LoRaWAN sensor can be triggered to send data to Gateway immediately. NOTE: The time between sending data for Class A is at least 3 seconds 4.3 Principle of operation LoRaWAN Network The LoRaWAN Gateway function is Packet Forwarder so: Between Gateway and End Device: Gateway receives data packets from End Device via RF connection, so it is recommended to configure Radio parameters (Note: the packet that Gateway receives is encrypted) Between Gateway and Network Server: Gateway forwards data packets to the Network server via an IP connection, so it is recommended to configure Network parameters such as Server Address, Server Uplink Port, Server Downlink Port,... LoRaWAN Network is secured as follows: Network section key (NwkSKey) to ensure the security of communications on the Network The application session key (AppSKey) to ensure data security between End Device and Application Server Special keys of the device such as DevEUI, AppEUI, Gateway EUI, Device Address. Therefore, the data packet that the Gateway receives is encrypted and decrypted on the Application server. To End Device connect to the Network server, you need to register in the following two ways: Activation with OTAA (Over-the-Air activation): is the process of joining the Network automatically. Previously, both End Device and Application Server installed the same DevEUI code, AppEUI, and AppKey. During activation, AppKey will generate 2 security keys for End Device and Network, which are: The network session key (NwkSKey): is the key to secure communication commands on the MAC layer between the End Device and the Network server. The application session key (AppSKey): is the key to secure data packets between the End Device and Application server. ATTENTIONS:* OTAA mode must be successfully activated in order for the End Device to send data packets to the Network through the Gateway;* OTAA mode only need to activate once, if the device is reset or battery replacement, it will activate OTAA again;* When the End Device is connected to the Network server, whether the Gateway is reset or the power is restarted, it will not need to activate OTAA. Activation by ABP (Activation by Personalization): is the process of joining the Network manually. Device Address, Network session key (NwkSKey), and Application session key (AppSKey) codes must be stored inside the End Device and Application server, so when the End Device sends data packets to the network server, it will also send the security codes to activate. 4.4 Configure the LoRaWAN Network 4.4.1 Configure End Device operation according to OTAA Configuration parameters for the End Device to be activated by OTAA as the table below: Parameter settings Setting value (example) Description Join Mode OTAA Device activation type on Network Server DevEUI 34 35 31 31 4B 37 75 12 Device ID's unique ID number => Set this ID number for the Application server AppEUI 70 B3 D5 7E D0 02 D5 0B Application server's unique ID number (random or user-generated)=> Set this ID number for End Device AppKey 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C Key Number for generating 2 NwkSKey and AppSKey security keys created by the user (factory-created by default)=> Used to install for both the Device and Application Server End ATTENTIONS:* The AppEUI number from Application Server => then installed for the End Device. AppEUI is randomly generated by the Application server or by the user;* The number of AppKeys during OTAA activation will generate two security keys, Lora NwkSKey and AppSKey, which are used for both End Device and Network. 4.4.2 Configure End Device operation according to ABP Configuration parameters for the End Device to be activated by ABP as the table below: Parameter settings Setting value (example) Description Join Mode ABP Device activation type on Network Server Device Address 12 34 56 78 End Device Address created by the Application server=> Set Device Address for End Device NwkSKey (Network session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C NwkSKey number created by the user to install and use for both End Device and Application Server AppSKey (Application session key) 2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C AppSKey number generated by the user to install for both End Device and Application Server 4.5 LED meaning RED LED: Fixed ON: due to noise caused peripheral components (i2c, spi, uart, timer, rtc, wdt, ...) do not initialize. Flashing 10ms ON / 10s OFF: Activation by OTAA on the Network server failed. Flashing 10ms ON / 2s OFF:  Sending a data packet to Gateway failed. GREEN LED: Flashing 100ms ON / OFF when sending a data packet to Gateway. BLUE LED: Flashing 1s ON / 1s OFF for the first 60 seconds when booting (insert batteries or connected external sources), after 60 seconds OFF. ON during the LoRaWAN sensor receives data packets from the Network server and OFF when received. 4.6 Process of measurement When the LoRa sensor wakes up, it will supply power to the internal or external sensor so that the sensor can start measuring. After measuring successfully it will turn off the power to the sensor for energy saving. The measured value is the raw value of the sensor. The measured value can be scaled according to the following formula: Y = aX + b X: the raw value from the sensor Y: the calculated value will be sent to LoRaWAN Gateway in the payload data. a: constant (default value is 1) b: constant (default value is 0) So, if there is no user setting for a and b ==> Y = X The Y value will be compared with Lo and Hi threshold. Please refer below the graph of alarm processing. 4.7 Payload Data The following is the format of payload data that will be sent to the LoRaWAN Gateway. Sensor type (1 byte) Status1 (1 byte) Status2 (1 byte) 1st - Parameter (Int16) 2nd - Parameter (Int16) 3rd - Parameter (Int16) Meaning of Data in the Payload Data Size (byte) Bit Format Meaning Sensor type 1 all Uint8 Sensor type = 0x0D means LoRaWAN Tilt Sensor. Sensor type = 0xFF means no sensor Status1: battery level 1 Bit 7 and 6 Uint8 Battery capacity in 04 levels 11: battery level 4 (99%) 10: battery level 3 (60%) 01: battery level 2 (30%) 00: battery level 1 (10%) Status1: error Bit 5 and 4 Node status 01: error 00: no error Status1: alarm 1 Bit 3 and 2 Alarm status of 1st - Parameter (X Tilt value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm Status1: alarm 2 Bit 1 and 0 Alarm status of 2nd - Parameter (Y Tilt value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm 1 Bit 7 and 2 Uint8 Not Applicable Status2: alarm 3 Bit 1 and 0 Alarm status of 3rd - Parameter (Z Tilt value) 11 : Hi alarm 01 : Lo alarm 00 : No alarm 1st - Parameter 2 all Int16 Measured value 1 2nd - Parameter 2 all Int16 Measured value 2 3rd - Parameter 2 all Int16 Measured value 3 5. Configuration Using the configuration cable to connect to the sensor as below picture. Serial port configuration on the computer:* COMPort, Baudrate: 9600, Parity: None, Stop bit: 1, Data bit: 8* Modbus RTU: Reading data by Function 3 / Writing data by Function 16. 5.1 Step to configure NOTE: The Modbus configuration can only be performed in the first 60s after power up the LoRaWAN sensor. After 60s, if user can not finish the configuration process, user need to reset the power of LoRaWAN sensor again, by removing battery in at least 15s. Step 1: Install the Modbus Configurator Software in the link below https://filerun.daviteq.com/wl/?id=qK0PGNbY1g1fuxTqbFW9SXtEvCw7bpc6 How to use the Modbus configuration software Step 2: Plug the configuration cable to computer via USB port and install the driver; Step 3: Open the plastic housing with L hex key to unscrew M4 screws at the side of the housing Step 4: Plug the connector to the configuration port; Step 5:  Import the configuration file by importing the csv file: Go to MENU: FILE / Import New / => select the file with name CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0.csv (in the link below). Then click Connect; CONFIGURATION TEMPLATE FILE FOR LORAWAN SENSOR FW1.0 To write new value to the device:First, you need to write the password in "password for setting", after reading the value to check ok, you can write the new value AppEUI, AppKey, ...You only have 60 seconds after plugging the configuration cable or the power supply into the device for configuration. 5.2 Register table Here is the table of Data will be read by Modbus tool Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 0 0 3 5 device info WSLRW-I2C string Read Wireless Sensor LoRaWAN - I2C 5 5 3 4 firmware version 1.00ddmm string Read ddmm = day / month 9 9 3 2 hardware version 1.10 string Read 11 B 3 4 lorawan protocol version 01.00.03 string Read lorawan v1.0.3 15 F 3 6 application version 01.03.00.00 string Read application server v1.3.0.0 21 15 3 6 mac layer version 04.04.02.00 string Read mac layer v4.4.2.0 27 1B 3 4 deviceEUI hex Read End Device's EUI number, used to register the product on the Network Server by OTAA 31 1F 3 4 lora appEUI hex Read Application server's EUI number is used to register the product on the Network Server by OTAA 35 23 3 8 lora appKey hex Read The number of keys used to create two security keys of the End Device, used to register the product on the Network Server by OTAA 43 2B 3 8 lora nwkSkey hex Read key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 51 33 3 8 lora appSkey hex Read End Device data encryption key number, used to register the product on the Network Server by ABP 59 3B 3 2 device address 0 uint32 Read End Device address created by Application server, used to register the product on the Network server by ABP 61 3D 3 2 network ID 0 uint32 Read Network server ID number, used to register the product on the Network server by ABP 63 3F 3 2 join mode OTAA string Read OTAA: Over-the-Air activation, ABP: Activation by Personalization 65 41 3 4 network mode PUBLIC string Read PUBLIC, PRIVATE 76 4C 3 3 bandwidth BW125 string Read BW125 79 4F 3 2 spread factor SF10 string Read SF10, SF9, SF8, SF7 81 51 3 4 activation of ADR ADR OFF string Read ADR ON, ADR OFF 85 55 3 1 class A string Read 103 67 3 1 sensor type 1-255 uint16 Read 1-254: sensor type, 255: no sensor 104 68 3 1 battery level 0-3 uint16 Read 4 levels of battery capacity status 105 69 3 1 error status 0-1 uint16 Read Error code of sensor, 0: no error, 1: error 106 6A 3 1 prm1 alarm status 0-2 uint16 Read Alarm status of parameters 1, 0: none, 1: Low, 2: High 107 6B 3 1 prm2 alarm status 0-2 uint16 Read Alarm status of parameter 2 108 6C 3 2 prm1 value float Read Value of parameter 1 110 6E 3 2 prm2 value float Read Value of parameter 2 112 70 3 1 battery % 10%, 30%, 60%, 99% uint16 Read % Value of battery capacity 113 71 3 2 battery voltage 0-3.67 vdc float Read Value of battery voltage 115 73 3 2 mcu temperature oC float Read Temperature value of RF module 117 75 3 1 mcu vref 0-3.67 vdc uint16 Read Vref value of RF module 118 76 3 1 button1 status 0-1 uint16 Read Button state, 0: No button pressed, 1: Button pressed 119 77 3 1 button2 status 0-1 uint16 Read Button status, 0: No magnetic sensor detected, 1: Magnetic sensor detected 126 78 3 2 prm3 value float Read Value of parameter 3 128 7A 3 1 prm3 alarm status 0-2 uint16 Read Report the alarm status of parameter 3 Here is the table for Configuration: Modbus Register (Decimal) Modbus Register (Hex) Function Code # of Registers Description Range Default Format Property Comment 256 100 3 / 16 1 modbus address 1-247 1 uint16 R/W Modbus address of the device 257 101 3 / 16 1 modbus baudrate 0-1 0 uint16 R/W 0: 9600, 1: 19200 258 102 3 / 16 1 modbus parity 0-2 0 uint16 R/W 0: none, 1: odd, 2: even 259 103 3 / 16 9 serial number string R/W (Password) 268 10C 3 / 16 2 password for setting uint32 R/W (Password) password 190577 270 10E 3 / 16 4 lora appEUI hex R/W (Password) Application server's EUI number, used to register the product on the Network Server by OTAA 274 112 3 / 16 8 lora appKey hex R/W (Password) The number of keys used to create two security keys of the End Device, used to register the product on the Network server by OTAA 282 11A 3 / 16 8 lora nwkSkey hex R/W (Password) key number encrypts the communication command of the MAC layer of the End Device, which is used to register the product on the Network Server by ABP 290 122 3 / 16 8 lora appSkey hex R/W (Password) End Device data encryption key number, used to register the product on the Network Server by ABP 298 12A 3 / 16 2 device address uint32 R/W (Password) End Device address created by Application server, used to register the product on the Network server by ABP 300 12C 3 / 16 2 network ID uint32 R/W (Password) Network server ID number, used to register the product on the Network server by ABP 302 12E 3 / 16 1 activation mode 0-1 1 uint16 R/W (Password) 1: OTAA (Over-the-Air Activation), 0: ABP (Activation by Personalization) 304 130 3 / 16 1 application port 1-255 1 uint16 R/W (Password) Port 224 is reserved for certification 319 13F 3 / 16 1 tx power 2-20 16 uint16 R/W (Password) tx power: 2,4,6,8,10,12,14,16,18,20 320 140 3 / 16 1 adaptative data rate 0-1 0 uint16 R/W (Password) Automatically adjust data rate, 0: disable, 1: enable 334 14E 3 / 16 2 cycle send data 900 uint32 R/W sec (data sending cycle) 338 152 3 / 16 1 alarm limt 44 uint16 R/W limit the number of events / day 340 154 3 / 16 2 sensor1: sampling_rate 120 uint32 R/W sec (frequency of data taken from sensor 1) 348 15C 3 / 16 2 prm1: a 1 float R/W Scale parameter "a" of Measured value 1 350 15E 3 / 16 2 prm1: b 0 float R/W Scale parameter "b" of Measured value 1 354 162 3 / 16 2 prm1: High Threshold 100000 float R/W High threshold value of Measured value 1 356 164 3 / 16 2 prm1: High Hysteresis 10000 float R/W High hysteresis value of Measured value 1 358 166 3 / 16 2 prm1: Low Threshold 0 float R/W Low threshold value of Measured value 1 360 168 3 / 16 2 prm1: Low Hysteresis 10000 float R/W Low hysteresis value of Measured value 1 362 16A 3 / 16 2 prm1: High Cut 100000 float R/W Upper limit value of Measured value 1 364 16C 3 / 16 2 prm1: Low Cut 0 float R/W Lower limit value of Measured value 1 6. Installation 6.1 Installation location To maximize the distance of transmission, the ideal condition is Line-of-sight (LOS) between the LoRaWAN sensor and Gateway. In real life, there may be no LOS condition. However, the LoRaWAN sensor still communicates with Gateway, but the distance will be reduced significantly. ATTENTION:DO NOT install the LoRaWAN 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, cement…is acceptable. 6.2 Battery installation Steps for battery installation: Step 1: Using L hex key to unscrew M4 screws at the side of the housing and carefully pull out the top plastic housing in the vertical direction Step 2: Insert 02 x AA 1.5VDC battery, please take note the poles of the battery ATTENTION: REVERSED POLARITY OF BATTERIES IN 10 SECONDS CAN DAMAGE THE SENSOR CIRCUIT!!! Step 3: Insert the top plastic housing and locking by L hex key ATTENTION: When reinstalling the cover, pay attention to put the PCB edge into the middle slot of the box inside as shown below) 7. Troubleshooting No. Phenomena Reason Solutions 1 The BLUE LED does not blink when the battery is installed Insert the battery in the opposite direction Insert the battery in the correct way 2 The RED LED is always on Due to noise, the peripheral components (i2c, spi, uart, ..) of RF module cannot be initialized After 30s the node will automatically reset. If the noise causes the Watchdog not to initialize, remove the battery and wait for more than 10 seconds, then insert the battery again 3 The RED LED blinks continuously (10ms ON / 2s OFF) and the Node does not send RF. After more than 10 sending cycles, the Node will automatically reset Operating frequency in that country is prohibited Operating frequency in that country is limited to Data rate, Tx Power Reconfigure the allowed frequency of operation Reconfigure Data rate = DR5 / SF07, Tx Power 4 RED LED blinks continuously (10ms ON / 2s OFF) and Node sends RF continuously 3s / time but no data. After more than 10 sending cycles, the Node will automatically reset Node runs dummy sending mode => sent by Gateway to send Downlink packets when users clear Uplink and Downlink counter values on Network Server (build-in Gateway) when activated by ABP Configuration enabled by OTAA 5 The RED LED flashes 10ms ON / 10s OFF and the Node does not send RF Node activation by OTAA on Network server has not been successful Using Magnet-Key to force Node to send RF continuously for 3 seconds/time => when activating by OTAA successfully, the GREEN LED will blink after sending RF 6 The node sent RF successfully but the GREEN LED did not blink LED is broken Warranty to replace LED 7 The data packet taken from the Gateway has an incorrect value The data package is encrypted Get the decoded packet on the Application Server 8 The node sends RF and activates by ABP, on Gateway receives data but the Application server has no data The application server still stores the counter values of the previous Uplink and Downlink Delete the counter values of Uplink and Downlink on the Application server 9 The node does not send RF and the RF module is hot Insert the battery in the opposite direction Short circuit Warranty or replacement 10 The node does not send RF to Gateway according to the alarm, LED does not blink The alarm configuration is incorrect Running out of the number of alarms set for the day Check alarm configuration Check the configuration for the maximum number of alarms per day 11 The node does not send RF to Gateway when activated by the magnetic key, LED does not blink The magnetic sensor has malfunctioned Read the status of the magnetic sensor via Modbus (when powering or attaching the battery) to see if the magnetic sensor is working. 12 Node has blinked LED GREEN when sending RF but the Gateway or Application server cannot receive LoRa module on the Gateway is faulty The IP connection (4G / WiFi / ...) on the Gateway is faulty Check Gateway's LoRa status lights on Gateway Check 4G / WiFi status lights on Gateway 13 The value of the sensor is 0 and sensor_type = 0xFF Lost connection with the sensor Check sensor connection Replace the module sensor 14 RSSI is weak and often loses data The distance between Node and Gateway is far or there are many obstructions Connection to Antenna problem Install metal nodes or in metal cabinets Configure Data rate = DR0 / SF12 Check Antenna position Install Node in a well-ventilated location 8. Support contacts Manufacturer Daviteq Technologies IncNo.11 Street 2G, Nam Hung Vuong Res., An Lac Ward, Binh Tan Dist., Ho Chi Minh City, Vietnam.Tel: +84-28-6268.2523/4 (ext.122) Email: info@daviteq.com | www.daviteq.com Instructions for ABP join mode for Daviteq sensor 1. Steps to register Daviteq LRW sensor on the network server using ABP Mode Step 1 : Register Daviteq sensors on Network server Get Sensor’s DevEUI at the lable in housing of sensors Register sensors on Network Server with ABP join mode Get Device Address, AppsKey, Nwskey which are created on Network server Step 2: Configure sensors via offline tool Write NwkSkey, AppSkey, Device Address into sensors Configure join mode as ABP Step 3: Install batteries for sensors, then check result on Network server. 2.  Example of Register Daviteq sensor onto The Things Stack network server. Step 1: Register Daviteq sensors on Network server Get Sensor’s DevEUI at the lable in housing of sensors Register sensors on Network Server with ABP join mode Get Device Address, AppsKey, Nwskey which are generated on Network server. Step 2: Configure sensors via offline tool. Download and launch Modbus configuration software Click Modbus configuration software to download the software On the configuration software, choose the relevant Port (the USB port which is the cable plugged in) and set the BaudRate: 9600, Parity: none Download, then import the template file in Daviteq Modbus Configuration tool. Click Download CSV file to download the Configuration Template File In CONFIGURATION section, input NwkSkey, AppSkey, Device Address and value 0 for join mode at VALUE TO WRITE Column. Connect the PC to Daviteq sensors using the configuration cable and converter cable Click Connect button then, choose Edit=> Enable All After that, check the values in READ DATA section Note: The sensor is only active for configuration for 60 since connecting the cable to the sensor. Step 3: Install batteries for sensors, then check result on Network server. Instructions for converting Daviteq Sigfox Exd-Pressure device to Daviteq LoraWAN Exd-Pressure device. 1. Prepare tools: 1 pc x Screwdriver 1 pc x 12” Wrench 1 tube x Thread Lock Glue 1 bottle x Cleaning alcohol 1 pc x Cleaning cloth 1 pc x Grinding tool 1 pc x Heat gun Figure 1.1: Tool list 2. Disassemble the Daviteq Sigfox Exd Pressure device: Step 1: Unscrew the antenna by turning the antenna counter-clockwise and open the device housing cover by turning the upper housing cover counter-clockwise as a below figure. Figure 2.1: Unscrew the antenna and open the housing cover of Daviteq Sigfox Exd Pressure device. Step 2: Grind the excess part inside the housing cover to fit with new LoraWAN main board by grinding tool. Figure 2.2: Grind the excess part inside the housing cover. Step 3: Remove the Sigfox mainboard by screwdriver. The position of 3 screws is marked as Figure 2.3. Figure 2.3: Remove the Sigfox mainboard by screwdriver. Step 4: Unscrew the antenna cable and cut out the 2 wires connecting the pressure sensor and Sigfox mainboard. Figure 2.4: Unscrew the antenna cable and cut out the connecting the 2 wires. Step 5: Heat up the connecting thread between the pressure sensor and housing by heat gun (recommended heat with temperature of 300 oC in 20-30 minutes) to melt the thread lock glue for easy disassembling. Then unscrew the sensor by turning counterclockwise using wrench. Figure 2.5: Heat up the connecting thread. Figure 2.6: Unscrew the sensor by turning counterclockwise using wrench. Step 6: Peel off all labels on the housing of Sigfox device. Step 7: Clean the housing and thread by alcohol and cloth. Figure 2.7: Components of Daviteq Sigfox Exd Pressure device after disassembly. 3. Assemble the Daviteq LoraWAN Exd Pressure device: Note: Only re-use housing, antenna for converting from Sigfox device to LoraWAN device. DON’T re-use the Sigfox mainboard and pressure sensor. Step 1: Apply thread lock glue to the connection thread and screw the new pressure sensor to the housing by turn clockwise. Warning: Do not use to too much glue as it will take too long to dry and leak to the mainboard. Recommend using 2-3 drops of glue. Figure 3.1: Apply thread lock glue to the connection thread of sensor. Figure 3.2: Screw the sensor to the housing by turning clockwise using wrench Step 2: Select correct LoraWAN mainboard for the sensor in the step 1:- 10 bar new sensor will be installed with LoraWAN mainboard having item code on the main board label of WSLRWEX-PPS-10-01- 100 bar new sensor will be installed with LoraWAN mainboard having item code on the main board label of WSLRWEX-PPS-100-01 Step 3: Note out the serial number on the selected LoraWAN mainboard label for later usage in labelling step. Step 4: Screw the antenna cable on the LoraWAN mainboard to antenna and plug socket of sensor cable to the socket on the LoraWan mainboard. Warning: Arrange the wires neatly to avoid the wires being stuck. Figure 3.3: Screw the antenna cable and plug socket of sensor cable. Step 5: Fix the LoraWan mainboard to the housing in the position as shown by screwdriver. The position of 2 screws is marked as Figure 3.4. Figure 3.4: Position of 2 screws on to screw the LoraWan mainboard to the housing. Step 6: Stick the sensor manual QRCode label inside the housing cover as Figure 3.5. Figure 3.5: Position of the manual QRCode label inside the housing cover. Step 7: Screw the housing cover and antenna. Make sure Oring is available on housing cover. Figure 3.6: Screw the housing cover and antenna. 4. Stick labels on the housing of Daviteq LoraWAN Exd Pressure device: There are 4 types of labels for the LoraWAN Exd Pressure device: 1 x LoraWAN label, 1 x Device information label1 x Magnet reed-switch label1 x Manual QRCode of Daviteq LoraWAN Exd Pressure firmware3 device label And 4 types of label and LoraWAN mainboard in the package. Step 1: Screw the housing cover tighty then stick the LoraWAN label vertically. The direction of the label as Figure 4.1. Figure 4.1: Position and direction of the LoraWAN label on the housing cover. Step 2: Stick the device information label at the position at Figure 4.2. Note: Make sure the serial number on the label is the same as one on the main board label. The serial number on the mainboard label is noted out in step 3 of section “3. Assemble the Daviteq LoraWAN Exd Pressure device” The the device information label is next to sensor mounting semi-circular hole. Figure 4.2: Position and directon of the device information label on the housing Step 3: Stick the magnet reed-switch label as position as Figure 4.3. Figure 4.3: Position of the magnet reed-switch label on the housing After completing labelling, the sensor will be as below figure 4.4. Figure 4.4: Position of labels after labeling process is completed 5. Check operation of the LoraWAN device after converting Follow instruction at section 1.7 Guide for Quick Test of WSLRWEX-PPS firmware manual. Link of online manual: https://www.iot.daviteq.com//manual-for-wireless-sensors/manual-for-wslrwex-pps-%7C-fw3 Please note that, log in is required to access the online manual of WSLRWEX-PPS firmware 3. The user needs to visit https://www.iot.daviteq.com to register the user for accessing the online manual.Backup - List of Configuration Template Files for various LoRaWAN Sensors THIS IS OBSOLETE MANUAL Please access https://www.iot.daviteq.com/wireless-sensors for updated manual Each LoRaWAN sensor has many parameters to configure or read, the number could be up to a hundred. To simplify the process of reading and writing those parameters, we divide the parameters list into multiple files. Please find below. 1. Template file for Basic connection setup: Link download file: https://filerun.daviteq.com/wl/?id=qC53Hh8D1UdOGPMTFVqdny6okcI4PZHU Note: to write the region code, must write password 190577 in advance Here is the value to write for each region code: 1: AS923-1 | 2: KR920 | 3: AU915 | 4: US915 | 5: EU868 | 6: IN865 | 7: RU864 | 8: CN779 | 9: CN470 | 10: EU433 | 11: AS923-2 What you can do with this template file? - Writing the Region Code; - Writing the Data sending cycle; - Writing the Limit number of alarms per day. Example of configuration screen: 2. Template file for Reading the AppEUI and the AppKey or other LoRaWAN configuration: Link download file: https://filerun.daviteq.com/wl/?id=6kXDV0JAdkSpYtv2GqNkeD5Iu4D5Tt27 Example of configuration screen: 3. Template file for Setting LoRaWAN configuration in OTAA or ABP mode: Link download file: https://filerun.daviteq.com/wl/?id=4DuFRZnB89mYU25opBGQqfBmbl5RDHkW Note: to write these parameters, must write password 190577 in advance Example of configuration screen: 4. Template file for Reading Sensor's operation data: Link download file: https://filerun.daviteq.com/wl/?id=RdTEHgJXQxLXRju0k1BjujzRrZF3STdo Example of configuration screen: 5. Template files for Sensor and Parameter configuration: For each kind of sensor, there will be 02 files: A template file for setting Sensor and Parameter Configuration; A template file for reading Sensor and Parameter Configuration; Example of configuration screen - setting: Example of the configuration screen - reading: Please find below table to download the template files for each kind of sensor: SKU number Product name A template file for Setting Sensor and Parameter A template file for Reading Sensor and Parameter WSLRW-PPS (0-10barg) LoRaWAN Process Pressure Sensor https://filerun.daviteq.com/wl/?id=XRUCQbirqlkyPzpxJkI9Fvjt1C4UvMFk https://filerun.daviteq.com/wl/?id=qHkzVQsI0zQTY0NZjzUcnIA1kj2A1WYN WSLRW-AG LoRaWAN Tilt Sensor https://filerun.daviteq.com/wl/?id=lftgj6cwWOPONWmevhkzBkCM5OjCtHeO https://filerun.daviteq.com/wl/?id=3nCD5mpKNYCQ04vEiAvPWvdzsuXgf6Jo WSLRW-SMT LoRaWAN Soil Moisture Sensor https://filerun.daviteq.com/wl/?id=TscdhX7TQsOSyVhLr6FUbhTR7rUJ782o https://filerun.daviteq.com/wl/?id=Uj27kHQNSOmSdYjjjguVp2Wm08rRzVAk WSLRW-ULB LoRaWAN Ultrasonic Level Sensor https://filerun.daviteq.com/wl/?id=bUbQJhv0G2vDm37gDWkhy9hizaZUsHXn https://filerun.daviteq.com/wl/?id=n4c43PQX5sebL8VZUpcCq080kS1eW9h9 WSLRW-V1A LoRaWAN 10KHz Vibration Sensor https://filerun.daviteq.com/wl/?id=om8R3Jhz27RXFOukLneeoPX8EBsJ2BuW https://filerun.daviteq.com/wl/?id=owWew7e0ti2lYv4fC8OlmLAxHIJrpOwt WSLRW-LPC LoRaWAN Lidar People Counter WSLRW-G4 LoRaWAN Gas Detecting Sensor - Firmware version 2 Download template for Reading sensor and parameter, input value to write at VALUE TO WRITE column of Read/Write parameter and change function code from 3 to 16 https://filerun.daviteq.com/wl/?id=ogWBHaRjRDDHow5s1218irTtHsACrPHM END. Sample HTML table 2 Sensor technology NDIR Gas sampling method Diffusion Gas Acetylene Sensor housing Stainless Steel Body material for Indoor use (buy the optional accessory rain-guard for outdoor installation Sensing range 0 - 100% LEL (0 - 2.5 % vol.) Maximum response time (T90) <40 s Maximum deviation from linearity ±0.1% vol. Maximum variation of zero from −20 to +55 °C ±30 ppm/°C Resolution 0.1% LEL Maximum non-reproducibility of zero at 20 °C ±500 ppm Maximum non-reproducibility of sensitivity at 20 °C <±1000 ppm Long-term zero drift/month ±500 ppm MTBF (lamp dependent only) >10 years for 5 V operation Ambient humidity 0-95% RH (Non-condensing) Temperature From -20 to 60 °C Sensor lifetime 10 years Calibration interval Recommend recalibrating zero and span at least every 30 months Manual for PINEX Outdoor LoRaWAN Gateway - PINEX | FW3 1. GENERAL INFORMATION Thank you very much for choosing Daviteq LoRaWAN gateway. We are the leading wireless sensor manufacturer in the World. We have a wide range of wireless sensors which support different connectivity like LoRaWAN, Sigfox, Sub-GHz, NB-IoT...Please find out more information at this link. This manual is applied to the following products Item code HW Version Firmware Version Remarks PINEX-E9-SINGLE 3H 3F2402 PINEX-E8-SINGLE 3H 3F2402 2. QUICK GUIDE Reading time: 15 minutesFinish this part so you can understand and put the device in operation with the default configuration from the factory. 2.1. What is the PINEX? PineX is an industrial-grade outdoor LoRaWAN® Gateway, designed to operate reliably in the harshest environments—from scorching deserts to freezing Arctic conditions, and even hurricane-force winds up to 200 km/h. With IP67-rated waterproof and dustproof protection, an extended temperature range of -40°C to +70°C, and Dual LoRa Antennas for extended coverage, PineX ensures uninterrupted, long-range connectivity even in extreme weather conditions. Supporting all global LoRaWAN frequency bands, PineX integrates a built-in Network Server, Node-RED, and VPN security, enabling fast, cost-efficient, and secure IoT deployments. Its integrated 4G Router with PoE (802.3at) support allows for seamless Internet access and power supply for IP cameras, sensors, and other connected devices. Designed for Smart Cities, Industrial Facilities, Smart Agriculture, and remote IoT applications, PineX is the ultimate rugged, high-performance LoRaWAN Gateway for mission-critical operations. 2.2. What's in the package? The package includes:01 x LoraWAN PINEX Gateway01 x Lora Antenna01 x Power Adapter 01 x Converter cable01 x Mounting Accessories 2.3. Product Overview LED Functions LED Functions Constant Flashing Off Power Power On None OFF Network Initializing Internet Available Disconnected LoRa LoRa Working Initializing LoRa Not Working RESET Button The button is deactivated in firmware 3 2.4. Installation Startup the LoraWAN Gateway through the following steps Step 1: Install the antenna of the LoRaWAN Gateway Install the Lora antenna in the correct position. Make sure the antenna and Gateway are tightly connected. Step 2 : Use the screw driver to remove the three screws, then open the gateway cover. Step 3: Connect the Ethernet cable to the Gateway Connect the Ethernet cable into LAN port. Step 4 : Close the gateway's cover, then use the screw driver to lock the 3 screws. Step 5 : Power up the Gateway through M12 port 2.5. Mounting Step 1: Select the installation location. The surface must be flat. Step 2: Based on the dimensions of the gateway's base, drill four holes into the wall. Then, insert wall anchors into the drilled holes. Step 3: Use screws to secure the gateway onto the drilled surface. 2.6. Configure the LoRaWAN Gateway 2.6.1 GUI Access Default mode of Daviteq Gateway is DHCP. Once gateway is turned on through plugging in the DC adapter, it will automatically link to available servers. Gateway’s IP address can be found from the DHCP server. Access Gateway Web UI via the DHCP IP on browser. The default username is “admin”, and the password can be found on the inside label. By default, the gateway is configured to use DHCP. Therefore, it must be connected to a network with an active DHCP server in order to access the Web GUI. If the gateway is to be used in a static IP network without DHCP, it must firstly be connected to another active DHCP server to access the configuration interface to configure static IP for the gateway. Once the initial configuration is complete, the gateway can then be moved to the static IP network. Details of static IP configuration for the gateway are in sub-section of WAN SETTINGS in section of 2.2.6.2 Network WAN configuration In some company with strict IT regulations, the gateway MAC address must be added to company network white list for proper connection. To access the GUI, follow these steps: Step 1: Use a computer to connect to the network that the gateway is connected. The computer can connect to that network via WiFi or Ethernet. Step 2: Use the IP scanning software to find the IP address of the gateway based on its Mac address that can be found on the back label. Access this link to get a free IP scanning software on the internet The gateway's default ethernet mode is DHCP. Before scanning its IP address, ensure the network is in active DHCP mode. Therefore, if you want to use a static IP for the gateway, you must first connect it to a network with an active DHCP server to access the gateway's GUI. After that, you can configure a static IP address for it. Step 3: Enter the IP address of the gateway in the web browser to access the configuration interface. Must add port 4050 after the IP address. For example, If the IP address of the Gateway is 192.168.1.21 , you have to enter 192.168.1.21:4050 in web browser, then the GUI will be displayed. The default username is admin and default password is public After login successfully, the general information of the gateway will be display at general information tab. 2.6.2 Network WAN configuration This category shows current WAN settings. This category is further divided into three sectors: WAN Status, Data Statistics and WAN Settings. WAN Status The current network status will be shown on this page. WAN Statistics Statistics on the gateway's used data capacity are shown in this section. WAN Settings Daviteq Gateway supports Ethernet WAN mode . 2.6.3. Lora Settings The LoRa menu consists of the following categories: Package Forwarder and Logs. Configure some basic fields for the gateway operation. Package Forwarder Select Packet Forwarder in the left menu, then choose Gateway Info. This page is for setting up the LoRa configuration including Gateway ID, Server Address, Server Uplink Port, Server Downlink Port, Keep-Alive Interval, Statistics Display Interval, and Push Timeout. Need to properly configure the Server Address, Server Uplink Port, and Server Downlink Port fields. These information depend on the Network server. Choose the channel plan for the gateway, then choose the Apply button at the bottom right to save the current configuration Logs This is the function of monitoring the loRaWAN network. 2.7 Add the LoraWAN Gateway to Network Server To give an example, please follow the instructions in this link to add LoraWAN gateway to The things Stack network server. 3. PRODUCT SPECIFICATION LoRaWAN Specification LoRaWAN 1.0.3 Frequency Band Select 863∼870MHz or 902∼928MHz Number of Channels Up to 8 concurrent channels for LoRa transmission LoRa Transmit Power 0.5W (up to 27 dBm) LoRa Receive Sensitivity Down to -139dBm@SF12, BW 125 kHz. LoRa Software Package Forwarder Advanced Software features OpenVPN, built-in LoRaWAN Network Server & Node-RED, Cellular Internet Routing function Standard Host Communication Ethernet 100Mbps, via outdoor RJ45 connector Optional External Cellular Module LTE Cat 4, supports multi-region and global bands as below Frequency Bands for AU: LTE-FDD (B1/2/3/4/5/7/8/28) LTE-TDD (B40) Frequency Bands for EU: LTE-FDD (B1/3/7/8/20/28A) LTE-TDD (B38/40/41) Frequency Bands for A: LTE-FDD (B2/4/12) Frequency Bands for Global: LTE-FDD (B1/2/3/4/5/7/8/12/13/18/19/20/25/26/28) LTE-TDD (B38/39/40/41) Optional GPS GPS + GLONASS Antenna Type Single/Dual LoRa antenna, optional 4G LTE internal/external antenna Power supply 12 - 24 VDC Ethernet port Optional support PoE+ source 802.3at Housing Anodized Aluminum, IP67, can withstand Wind speeds up to 200 Km/h Working temperature -40 to 70 oC Dimensions Diameter of 70 mm, H:500 mm (include antenna) Weight < 2.0kg 4. WARRANTY & SUPPORT Below terms and conditions are applied for products manufactured and supplied by Daviteq Technologies Inc. 4.1  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 was shipping costs to the Return center shall be paid by Customers. 4.2 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. Notes:* 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. 4.3 Support 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. Manual for PINEX Outdoor LoRaWAN Gateway - PINEX | FW5 1. GENERAL INFORMATION Thank you very much for choosing Daviteq LoRaWAN gateway. We are the leading wireless sensor manufacturer in the World. We have a wide range of wireless sensors which support different connectivity like LoRaWAN, Sigfox, Sub-GHz, NB-IoT...Please find out more information at this link. This manual is applied to the following products Item code HW Version Firmware Version Remarks PINEX-E9-SINGLE 3H 5F0312 PINEX-E8-SINGLE 3H 5F0312 GWODR-8-WET-RN 3H 5F0312 2. QUICK GUIDE Reading time: 15 minutesFinish this part so you can understand and put the device in operation with the default configuration from the factory. 2.1. What is the PINEX? PineX is an industrial-grade outdoor LoRaWAN® Gateway, designed to operate reliably in the harshest environments—from scorching deserts to freezing Arctic conditions, and even hurricane-force winds up to 200 km/h. With IP67-rated waterproof and dustproof protection, an extended temperature range of -40°C to +70°C, and Dual LoRa Antennas for extended coverage, PineX ensures uninterrupted, long-range connectivity even in extreme weather conditions. Supporting all global LoRaWAN frequency bands, PineX integrates a built-in Network Server, Node-RED, and VPN security, enabling fast, cost-efficient, and secure IoT deployments. Designed for Smart Cities, Industrial Facilities, Smart Agriculture, and remote IoT applications, PineX is the ultimate rugged, high-performance LoRaWAN Gateway for mission-critical operations. 2.2. What's in the package? The package includes:01 x LoraWAN PINEX Gateway01 x Lora Antenna01 x WiFi Antenna01 x Power Adapter 01 x Converter cable01 x PoE Injector01 x Mounting Accessories 2.3. Product Overview LED Functions LED Functions Constant Flashing Off Power Power On None OFF Network Initializing Internet Available Disconnected LoRa LoRa Working Initializing LoRa Not Working RESET Button The button is deactivated in firmware 4 2.4. Installation Startup the LoraWAN Gateway through the following steps Step 1: Install the antenna of the LoRaWAN Gateway Install the Lora antenna and WiFi antenna in the correct position. Make sure the antenna and Gateway are tightly connected. Step 2 : Use the screw driver to remove the three screws, then open the gateway cover. Step 3: Connect the Ethernet cable to the Gateway Connect the Ethernet cable into LAN port. Step 4 : Close the gateway's cover, then use the screw driver to lock the 3 screws. Step 5 : Power up the Gateway through M12 port 2.5. Mounting Step 1: Select the installation location. The surface must be flat. Step 2: Based on the dimensions of the gateway's base, drill four holes into the wall. Then, insert wall anchors into the drilled holes. Step 3: Use screws to secure the gateway onto the drilled surface. 2.6. Configure the LoRaWAN Gateway 2.6.1 GUI Access Default mode of Daviteq Gateway is DHCP. Once gateway is turned on through plugging in the DC adapter, it will automatically link to available servers. Gateway’s IP address can be found from the DHCP server. Access Gateway Web UI via the DHCP IP on browser. The default username is “admin”, and the password can be found on the inside label. By default, the gateway is configured to use DHCP. Therefore, it must be connected to a network with an active DHCP server in order to access the Web GUI. If the gateway is to be used in a static IP network without DHCP, it must firstly be connected to another active DHCP server to access the configuration interface to configure static IP for the gateway. Once the initial configuration is complete, the gateway can then be moved to the static IP network. Details of static IP configuration for the gateway are in sub-section of WAN SETTINGS in section of 2.2.6.2 Network WAN configuration In some company with strict IT regulations, the gateway MAC address must be added to company network white list for proper connection. To access the GUI, follow these steps: Step 1: Use a computer to connect to the network that the gateway is connected. The computer can connect to that network via WiFi or Ethernet. Step 2: Use the IP scanning software to find the IP address of the gateway based on its Mac address that can be found on the back label. Access this link to get a free IP scanning software on the internet Step 3: Enter the IP address of the gateway in the web browser to access the configuration interface. Must add port 4050 after the IP address. For example, If the IP address of the Gateway is 192.168.1.21 , you have to enter 192.168.1.21:4050 in web browser, then the GUI will be displayed. The default username is admin and default password is public. Please check updated username and password on the gateway label. After login successfully, the general information of the gateway will be display at general information tab. 2.6.2 Network WAN configuration This category shows current WAN settings. This category is further divided into three sectors: WAN Status, Data Statistics and WAN Settings. WAN Status The current network status will be shown on this page. WAN Statistics Statistics on the gateway's used data capacity are shown in this section. WAN Settings Daviteq Gateway supports internet connectivity via both Ethernet and Wi-Fi. When both Ethernet and Wi-Fi are available, the system will prioritize Ethernet. The network mode will switch automatically based on availability. The default Ethernet mode is DHCP. Follow the steps below to set up the Wi-Fi network for the gateway:Step 1: In the Network section, select WAN.Step 2: Click on the WAN Settings tab at the top.Step 3: In the Configuration field, select Wi-Fi.Step 4: Enter the Wi-Fi information, including SSID (Wi-Fi name), Password, and Wi-Fi Type (default: DHCP Client).Step 5: Click the Apply button to save and apply the new configuration. 2.6.3. Lora Settings The LoRa menu consists of the following categories: Package Forwarder and Logs. Configure some basic fields for the gateway operation. Package Forwarder Select Packet Forwarder in the left menu, then choose Gateway Info. This page is for setting up the LoRa configuration including Channel Plan, Gateway ID, Server Address, Server Uplink Port, Server Downlink Port, Keep-Alive Interval, Statistics Display Interval, and Push Timeout. Need to properly configure the Server Address, Server Uplink Port, and Server Downlink Port fields. These information depend on the Network server. Choose the channel plan for the gateway, then choose the Apply button at the bottom right to save the current configuration Parameter name Description Default value Channel Plan The region refers to the specific geographical area where the gateway operates, following the LoRaWAN Regional Parameters defined by the LoRa Alliance EU868 Gateway ID The Gateway ID (also known as DevEUI) is a unique identifier assigned to a LoRaWAN gateway. Unique value Server Address The server address in a LoRaWAN gateway refers to the network server’s IP address or domain name that the gateway connects to for data transmission and management localhost Server Uplink Port The server uplink port in a LoRaWAN gateway refers to the port number used to send uplink packets 1680 Server Downlink Port The server downlink port in a LoRaWAN gateway is the port number used for receiving downlink packets 1680 Keep alive interval The keep-alive interval is the time interval at which a LoRaWAN gateway sends periodic status messages (heartbeats) to the network server to indicate that it is active and connected. 30 Logs This is the function of monitoring the loRaWAN network. 2.7 Add the LoraWAN Gateway to Network Server To give an example, please follow the instructions in this link to add LoraWAN gateway to The things Stack network server3. PRODUCT SPECIFICATION LoRaWAN Specification LoRaWAN 1.0.3 Frequency Band Select 863∼870MHz or 902∼928MHz Number of Channels Up to 8 concurrent channels for LoRa transmission LoRa Transmit Power 0.5W (up to 27 dBm) LoRa Receive Sensitivity Down to -139dBm@SF12, BW 125 kHz. LoRa Software Package Forwarder Advanced Software features OpenVPN, built-in LoRaWAN Network Server & Node-RED, Cellular Internet Routing function Standard Host Communication Ethernet 100Mbps, via outdoor RJ45 connector Optional External Cellular Module LTE Cat 4, supports multi-region and global bands as below Frequency Bands for AU: LTE-FDD (B1/2/3/4/5/7/8/28) LTE-TDD (B40) Frequency Bands for EU: LTE-FDD (B1/3/7/8/20/28A) LTE-TDD (B38/40/41) Frequency Bands for A: LTE-FDD (B2/4/12) Frequency Bands for Global: LTE-FDD (B1/2/3/4/5/7/8/12/13/18/19/20/25/26/28) LTE-TDD (B38/39/40/41) Optional GPS GPS + GLONASS Antenna Type Single/Dual LoRa antenna, optional 4G LTE internal/external antenna Power supply 12 - 24 VDC Ethernet port Optional support PoE+ source 802.3at Housing Anodized Aluminum, IP67, can withstand Wind speeds up to 200 Km/h Working temperature -40 to 70 oC Dimensions Diameter of 70 mm, H:500 mm (include antenna) Weight < 2.0kg 4. WARRANTY & SUPPORT Below terms and conditions are applied for products manufactured and supplied by Daviteq Technologies Inc. 4.1  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 was shipping costs to the Return center shall be paid by Customers. 4.2 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. Notes:* 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. 4.3 Support 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. New Page Action Settings Start Address (Decimal) Start Address (Hex) Number of Registers Data type How to change offline with configuration cable How to change online with downlink Change LoRaWAN App EUI lora appEUI 270 10E 4 hex Write new value (16 hexadecimal value) to "lora appEUI" setting with function of 16 Unavailable Change LoRaWAN App Key lora appKey 274 112 8 hex Write new value  (32 hexadecimal value) to "lora appKey" setting with function of 16 Unavailable Change LoRaWAN region region 317 13D 1 uint16 Write new value to "region" setting with function of 16. The value list for corresponding region as below1: AS923-1, 2: KR920, 3: AU915, 4: US915, 5: EU868, 6: IN865, 7: RU864, 8: AS923-2, 9: AS923-3, 10: AS923-1 Japan Unavailable Change Spread Factor (SF) or data rate data rate 318 13E 1 uint16 Write new value to "data rate" setting with function of 16. Written value versus SF/data rate based on LoRaWAN region as below: * FOR US915: 0 = 980 bps = SF10, 1 = 1760 bps = SF9, 2 = 3125 bps = SF8, 3 = 5470 bps = SF7* FOR AS923, AU915:2 = 980 bps = SF10, 3 = 1760 bps = SF9, 4 = 3125 bps = SF8, 5 = 5470 bps = SF7* FOR Other Region:0 = 250 bps = SF12, 1 = 440 bps = SF11, 2 = 980 bps = SF10, 3 = 1760 bps = SF9, 4 = 3125 bps = SF8, 5 = 5470 bps = SF7 Send downlink with below new hexadecimal value  using port 1 (default port):3E02000100000005 to write 13E02000200000005 to write 23E02000300000005 to write 33E02000400000005 to write 43E02000500000005 to write 5Written value versus SF/data rate based on LoRaWAN region as below:* FOR US915: 0 = 980 bps = SF10, 1 = 1760 bps = SF9, 2 = 3125 bps = SF8, 3 = 5470 bps = SF7* FOR AS923, AU915:2 = 980 bps = SF10, 3 = 1760 bps = SF9, 4 = 3125 bps = SF8, 5 = 5470 bps = SF7* FOR Other Region:0 = 250 bps = SF12, 1 = 440 bps = SF11, 2 = 980 bps = SF10, 3 = 1760 bps = SF9, 4 = 3125 bps = SF8, 5 = 5470 bps = SF7 Turn ON Adaptive Data Rate (ADR) frequency channels for EU868 IN865 RU864 KR920 AS923 AU915 US915ANDadaptive data rate 321 & 320 141 & 140 1 & 1 uint16 & uint16 Write value of 0 to "frequency channels for EU868 IN865 RU864 KR920 AS923 AU915 US915" setting with function of 16AND then Write value of 1 to "adaptive data rate" setting with function of 16 Send first downlink with hexadecimal value of 4102000000000005 to device then send second downlink with the value of 4002000100000005 using port 1 (default port) Instructions to install the Chirpstack on Edge Computer having Ubuntu OS I. Preparation Laptop/PC having Window OS and Wifi connection Network having Internet access Ethernet cable for Edge PC. They will connect to same network and the network could connect to internet Edge PC & Power Adapter Screen having HDMI port HDMI cable Keyboard Mouse Installation suites of Chirpstack, NodeRED and docker II. Installation steps Download and install bitvis (SSH software) on the Laptop/PC, client version at link https://bitvise.com/download-area Connect Edge PC to peripheral devices Connect Edge PC to Screen with HMI cable via HMI port, to mouse and keyboard via USB port (USB hub), to Internet with Ethernet cable via Ethernet port then power up the Edge PC. The Edge PC already have Ubuntu OS. After power up the PC will be booted and in command-line GUI (Terminal) Note:The instructions for Ubuntu 20.04.6 Update and upgrade Ubuntu OS Login Ubuntu with user of ubuntu and password (default password is ubuntu) Run command: "sudo su", and input  user  "root" and password  (example of password of Admin@!@#) to access root user Run command "sudo apt update" to get updated package of Ubuntu OS to the Edge PC Run command "sudo reboot" to reboot after update. After rebooting, login server, access root user Run command "sudo apt upgrade" to upgrade latest version of OS Run command "sudo reboot" to reboot after upgrade. After rebooting, login server, access root user Open and configure ssh service Run command "sudo apt install -y openssh-server" to install the OpenSSH server on your system. Run command "sudo systemctl status ssh" to show the current status of the SSH service, including whether it is active (running) or inactive (stopped). Run command "sudo systemctl enable ssh"  to configure the SSH service to start automatically at boot. Run command "sudo reboot" to reboot after configuring ssh. After rebooting, login server, access root user Run command "ip a" in the terminal will display the current network interfaces and their configurations. This includes details such as IP addresses, MAC addresses, and the status of each interface. Note out the IP address for later usage Edit ssh configuration file Input command "sudo nano /etc/ssh/sshd_config" to open the SSH server configuration file in the Nano text editor with superuser privileges. Move a cursor on the file by using 4 arrow keys on the keyboard , then delete " #" at "port 22" and at "PermitRootLogin", and change  "PermitRootLogin" to "yes", then click Ctrl  & X, click Y to save ssh configuration file Input command "sudo systemctl restart ssh" to restart the SSH service on your system to apply the change of the SSH configuration file Copy installation suites from PC/laptop to Edge PC Open bitvise   software then input Edge PC IP, port of 22, user root and password  (Example password of Admin@!@# ), click Login, click NEW SFPT WINDOW to transfer files. Click /home on the right section to show all folder in "home" Select installation folder of Chirpstack, NodeRED and docker on the PC/laptop on the left section, click upload to copy to home on Edge PC Link for installation suits: https://filerun.daviteq.com/wl/?id=Pj6oE4zfTl0JUfd2SF1AYateABEYYEhl Install docker for Ubuntu In the bitvis software, click New Terminal console to open the terminal Add Docker's official GPG key by copying  below scripts and paste to terminal on ssh software. The paste is implemented by right-click the mouse. sudo apt-get updatesudo apt-get install ca-certificates curlsudo install -m 0755 -d /etc/apt/keyringssudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.ascsudo chmod a+r /etc/apt/keyrings/docker.asc Add the repository to Apt sources by copying  below scripts and paste to terminal on ssh software. echo \"deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu \$(. /etc/os-release && echo "${UBUNTU_CODENAME:-$VERSION_CODENAME}") stable" | \sudo tee /etc/apt/sources.list.d/docker.list > /dev/nullsudo apt-get update Install the latest Docker packages by implementing command of "sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin" Run the command of "docker ps -a" to list all containers on your system and check the docker is available in the list Note: All above scripts might be updated on link: https://docs.docker.com/engine/install/ubuntu/ Install the Chirpstack Access the folder that contain the Chirpstack installation file with "cd" command and folder path Run the command of "docker compose up -d" to start all the services defined in the docker-compose.yml file in detached mode. Here's a quick breakdown: docker compose: The Docker Compose command. up: Creates and starts containers. -d: Runs the containers in detached mode (in the background). This command is useful for starting your multi-container Docker applications without tying up your terminal. Run the command of "docker compose down" to stop and remove all the containers, networks, and volumes defined in your docker-compose.yml file. After completing the Chirpstack installation, access the web URL of "IP:8080" to view the Chirpstack Network Server Note: These instructions are applied for Chirpstack Version of v4.11.1 Install the NodeRED Access the folder that contain the NodeRED installation file with "cd" command and folder path Run the command of "docker compose up -d" to start all the services defined in the docker-compose.yml file in detached mode. Run the command of "docker compose down" to stop and remove all the containers, networks, and volumes defined in your docker-compose.yml file. Run the command of "chmod -R 777 data" to change the permissions of the data directory and all its contents recursively. Here's a quick breakdown: chmod: The command to change file permissions. -R: Applies the changes recursively to all files and directories within the specified directory. 777: Sets the permissions to read, write, and execute for everyone (owner, group, and others). data: The directory you want to change permissions for. This command grants full access to everyone, which can be useful for certain scenarios but also poses security risks. After completing the NodeRED installation, access the web URL of "IP:1881" to view the NodeREDNote: These instructions are applied for NodeRED Version of NodeRED V3.1.0 Set/change the static IP for the Edge PC (Optional) Run the command of "sudo nano /etc/netplan/50-cloud-init.yaml" to open the Netplan configuration file in the Nano text editor with superuser privileges. Enter your current user password when prompted. Once the file is open, make changes to your network configuration as below example network:      ethernets:               eno1:                       dhcp4: false                       optional: true                       addresses:                           - 192.168.1.81/24                       gateway4: 192.168.1.1                       nameservers:                           addresses:                           - 8.8.8.8               enp1s0:                        dhcp4: true                        optional: trueversion: 2 After editing, press Ctrl + O to save the changes and Ctrl + X to exit Nano. Configure to send uplink of the LoRaWAN sensor to NodeRED application via Chirpstack network server Access gateway web GUI, configure NS host, uplink port of 1700, downlink port of 1700 and obtain gateway EUI for later usage Access Chirpstack Network Server at URL of "IP:8080", add gateway, create device profile, add application, add end-device Access NodeRED at URL of "IP:1881", add MQTT-in in NodeRED with configuration of NS host, port of 1883, uplink topic of "application/+/device/+/event/+" . Manual for PINEX Outdoor LoRaWAN Gateway - PINEX | FW6 1. GENERAL INFORMATION Thank you very much for choosing Daviteq LoRaWAN gateway. We are the leading wireless sensor manufacturer in the World. We have a wide range of wireless sensors which support different connectivity like LoRaWAN, Sigfox, Sub-GHz, NB-IoT...Please find out more information at this link. This manual is applied to the following products Item code HW Version Firmware Version Remarks PINEX-E9-SINGLE 4H 6F0404 PINEX-E8-SINGLE 4H 6F0404 GWODR-8-WET-RN 4H 6F0404 2. QUICK GUIDE Reading time: 15 minutesFinish this part so you can understand and put the device in operation with the default configuration from the factory. 2.1. What is the PINEX? PineX is an industrial-grade outdoor LoRaWAN® Gateway, designed to operate reliably in the harshest environments—from scorching deserts to freezing Arctic conditions, and even hurricane-force winds up to 200 km/h. With IP67-rated waterproof and dustproof protection, an extended temperature range of -40°C to +70°C, and Dual LoRa Antennas for extended coverage, PineX ensures uninterrupted, long-range connectivity even in extreme weather conditions. Supporting all global LoRaWAN frequency bands, PineX integrates a built-in Network Server, Node-RED, and VPN security, enabling fast, cost-efficient, and secure IoT deployments. Designed for Smart Cities, Industrial Facilities, Smart Agriculture, and remote IoT applications, PineX is the ultimate rugged, high-performance LoRaWAN Gateway for mission-critical operations. 2.2. What's in the package? The package includes:01 x LoraWAN PINEX Gateway01 x Lora Antenna01 x WiFi Antenna (optional)01 x Power Adapter 01 x Converter cable01 x PoE Injector01 x Mounting Accessories 2.3. Product Overview LED Functions LED Functions Constant Flashing Off Power Power On None OFF Network Initializing Internet Available Disconnected LoRa LoRa Working Initializing LoRa Not Working RESET Button The button is deactivated in firmware 4 2.4. Installation Startup the LoraWAN Gateway through the following steps Step 1: Install the antenna of the LoRaWAN Gateway Install the Lora antenna and WiFi antenna in the correct position. Make sure the antenna and Gateway are tightly connected. Step 2 : Use the screw driver to remove the three screws, then open the gateway cover. Step 3: Connect the Ethernet cable to the Gateway Connect the Ethernet cable into LAN port. Step 4 : Close the gateway's cover, then use the screw driver to lock the 3 screws. Step 5 : Power up the Gateway through M12 port 2.5. Mounting Step 1: Select the installation location. The surface must be flat. Step 2: Based on the dimensions of the gateway's base, drill four holes into the wall. Then, insert wall anchors into the drilled holes. Step 3: For economy gateway version, use screws to secure the gateway onto the drilled surface as below For standard gateway version, install the bottom frame to the wall/structure first by using 4 provided screws. Then insert the device to the slot then fix by a screw 2.6. Configure the LoRaWAN Gateway 2.6.1 GUI Access Default mode of Daviteq Gateway is DHCP. Once gateway is turned on through plugging in the DC adapter, it will automatically link to available servers. Gateway’s IP address can be found from the DHCP server. Access Gateway Web UI via the DHCP IP on browser. The default username is “admin”, and the password is "public" By default, the gateway is configured to use DHCP. Therefore, it must be connected to a network with an active DHCP server in order to access the Web GUI. If the gateway is to be used in a static IP network without DHCP, it must firstly be connected to another active DHCP server to access the configuration interface to configure static IP for the gateway. Once the initial configuration is complete, the gateway can then be moved to the static IP network. Details of static IP configuration for the gateway are in sub-section of WAN SETTINGS in section of 2.2.6.2 Network WAN configuration In some company with strict IT regulations, the gateway MAC address must be added to company network white list for proper connection. To access the GUI, follow these steps: Step 1: Use a computer to connect to the network that the gateway is connected. The computer can connect to that network via WiFi or Ethernet. Step 2: Use the IP scanning software to find the IP address of the gateway based on its Mac address that can be found on the back label. Access this link to get a free IP scanning software on the internet Step 3: Enter the IP address of the gateway in the web browser to access the configuration interface. Must add port 4050 after the IP address. For example, If the IP address of the Gateway is 192.168.1.21 , you have to enter 192.168.1.21:4050 in web browser, then the GUI will be displayed. The default username is admin and default password is public. Please check updated username and password on the gateway label. After login successfully, the general information of the gateway will be display at general information tab. 2.6.2 Network WAN configuration This category shows current WAN settings. This category is further divided into three sectors: WAN Status, Data Statistics and WAN Settings. WAN Status The current network status will be shown on this page. WAN Statistics Statistics on the gateway's used data capacity are shown in this section. WAN Settings Daviteq Gateway supports internet connectivity via both Ethernet and Wi-Fi (optional). When both Ethernet and Wi-Fi are available, the system will prioritize Ethernet. The network mode will switch automatically based on availability. Follow the steps below to set up the static IP for the gateway:Step 1: In the Network section, select WAN.Step 2: Click on the WAN Settings tab at the top.Step 3: In the Configuration field, select Ethernet WANStep 4: In the WAN type field, select Static IPStep 5: Enter the Static IP information, including IP Address, Subnet Mask, Gateway, DNS ServerStep 6: Click the Apply button to save and apply the new configuration. When the static IP is applied, the Web GUI will be logged out automatically. To connect the gateway to the internet, the Ethernet cable must be switched to a static IP network. After that, in order to access the gateway GUI again, the computer must be connected to the same network as the gateway. Follow the steps below to set up the Wi-Fi network for the gateway ( This feature is only available with the WiFi gateway version)Step 1: In the Network section, select WAN.Step 2: Click on the WAN Settings tab at the top.Step 3: In the Configuration field, select Wi-Fi.Step 4: Enter the Wi-Fi information, including SSID (Wi-Fi name), Password, and Wi-Fi Type (default: DHCP Client).Step 5: Click the Apply button to save and apply the new configuration. 2.6.3. Lora Settings The LoRa menu consists of the following categories: Package Forwarder and Logs. Configure some basic fields for the gateway operation. Package Forwarder Select Packet Forwarder in the left menu, then choose Gateway Info. This page is for setting up the LoRa configuration including Channel Plan, Gateway ID, Server Address, Server Uplink Port, Server Downlink Port, Keep-Alive Interval, Statistics Display Interval, and Push Timeout. Need to properly configure the Server Address, Server Uplink Port, and Server Downlink Port fields. These information depend on the Network server. Choose the channel plan for the gateway, then choose the Apply button at the bottom right to save the current configuration Parameter name Description Default value Channel Plan The region refers to the specific geographical area where the gateway operates, following the LoRaWAN Regional Parameters defined by the LoRa Alliance EU868 Gateway ID The Gateway ID (also known as DevEUI) is a unique identifier assigned to a LoRaWAN gateway. Unique value Server Address The server address in a LoRaWAN gateway refers to the network server’s IP address or domain name that the gateway connects to for data transmission and management localhost Server Uplink Port The server uplink port in a LoRaWAN gateway refers to the port number used to send uplink packets 1680 Server Downlink Port The server downlink port in a LoRaWAN gateway is the port number used for receiving downlink packets 1680 Keep alive interval The keep-alive interval is the time interval at which a LoRaWAN gateway sends periodic status messages (heartbeats) to the network server to indicate that it is active and connected. 30 Logs This is the function of monitoring the loRaWAN network. 2.7 Add the LoraWAN Gateway to Network Server 2.7.1 Add the LoraWAN Gateway to Embedded Chirp Stack Network Server Please follow instruction at link: Instruction to configu... | Online Product Manuals & Datasheets 2.7.2 Add the LoraWAN Gateway to External LoRaWAN Network Server To give an example, please follow the instructions in this link to add LoraWAN gateway to The things Stack network server 2.8 Activate and configure the embedded Node RED development tool Prerequisite: The Embedded Chirp Stack Network Server in the PINEX gateway must be active and configured properly to forward data to embedded Node RED development tool. Details to activate and configure embedded Chirp Stack are at the link: https://daviteq.com/en/manuals/books/manual-for-lorawan-sensor/page/instruction-to-configure-embedded-chirpstack-network-server-in-pinex-firmware-6 Please refer the below link for instruction to add the embedded Node RED  development tool: Instructions to config... | Online Product Manuals & Datasheets 3. PRODUCT SPECIFICATION LoRaWAN Specification LoRaWAN 1.0.3 Frequency Band Select 863∼870MHz or 902∼928MHz Number of Channels Up to 8 concurrent channels for LoRa transmission LoRa Transmit Power 0.5W (up to 27 dBm) LoRa Receive Sensitivity Down to -139dBm@SF12, BW 125 kHz. LoRa Software Package Forwarder Advanced Software features OpenVPN, built-in LoRaWAN Network Server & Node-RED, Cellular Internet Routing function Standard Host Communication Ethernet 100Mbps, via outdoor RJ45 connector Optional External Cellular Module LTE Cat 4, supports multi-region and global bands as below Frequency Bands for AU: LTE-FDD (B1/2/3/4/5/7/8/28) LTE-TDD (B40) Frequency Bands for EU: LTE-FDD (B1/3/7/8/20/28A) LTE-TDD (B38/40/41) Frequency Bands for A: LTE-FDD (B2/4/12) Frequency Bands for Global: LTE-FDD (B1/2/3/4/5/7/8/12/13/18/19/20/25/26/28) LTE-TDD (B38/39/40/41) Optional GPS GPS + GLONASS Antenna Type Single/Dual LoRa antenna, optional 4G LTE internal/external antenna Power supply 12 - 24 VDC Ethernet port Optional support PoE+ source 802.3at Housing Anodized Aluminum, IP67, can withstand Wind speeds up to 200 Km/h Working temperature -40 to 70 oC Dimensions Diameter of 70 mm, H:500 mm (include antenna) Weight < 2.0kg 4. WARRANTY & SUPPORT Below terms and conditions are applied for products manufactured and supplied by Daviteq Technologies Inc. 4.1  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 was shipping costs to the Return center shall be paid by Customers. 4.2 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. Notes:* 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. 4.3 Support 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. 5. ADVANCED TROUBLESHOOTING Problem Possible causes Solution The Ethernet port's LED is not lighting up Gateway is in boost mode Turn off the power supply, wait until all the gateway's LEDs are off, then change the switch from Boost to Run. After that, Power on the gateway. Can not scan the gateway's IP address 1. The computer and the gateway are not on the same network2. The network does not support DHCP. 3. The gateway was configured to use static IP mode 1. Check network of computer and gateway. 2. Use another active DHCP server network to access the configuration interface. 3. Press & hold the reset button within 5 seconds, then wait for 5 minutes before trying again. The gateway is not online on Network Server Wrong configuration Check the Package Forwarder configuration on the gateway and gateway register configuration on Network Server. Instruction to configure embedded Chirpstack Network Server in PINEX Embedded Chirpstack Network Server Information The version of embedded Chirp Stack Network Server in the PINEX gateway firmware 6 is v4. Configure Gateway to forward data from LoRaWAN gateway to Embedded Network Server Access web UI via URL of http://[PINEX_IP]:4050 Where [PINEX_IP] is the IP of the PINEX gateway in the network Navigate to LoRa menu on the left panel → Packet Forwarder Configure the following and click Apply to save settings Server Address: localhost Uplink Port: 1700 Downlink Port: 1700 LoRaWAN Region: Depend on your region e.g., EU868, US915, AS923… Other settings: keep default values Turn on Network Server Navigate to Network Server on the left panel → click Start Network Server then click Open New Tab Add Gateway Log in to the Chirp Stack web interface: After clicking Open New Tab, web UI to login appear, and login to Chirpstack  with user of admin and password of admin From the left menu, go to Gateways. Click on the “Add gateway” button in the top right corner. Fill in the following fields: Gateway ID: Enter the unique EUI (e.g., c0ee40ffff29abcd) of the gateway. Name: fill name of gateway (e.g., My Gateway). Scroll down to click SUBMIT to save Add Device Profiles From the left menu, go to Device Profiles. Click on the “Add device profiles” button in the top right corner. Fill in the following fields: Name: fill name of profile(e.g., AS923_2_PROFILE). Region: Select LoRaWAN region (e.g., AS923-2)MAC version: Select LoRaWAN 1.0.3 Regional parameters revision: Select A Scroll down to click submit to save Add Application From the left menu, go to Applications. Click on the “Add Application” button in the top right corner. Fill in the following fields: fill name of application (e.g., TEST_APP). Click submit to save Add Device From the right menu of application, click Add device. Fill in the following fields: Name: fill name of device(e.g., PPS). Device EUI (EUI64): Enter device EUI of device (e.g., 353138315130ABCD) Join EUI (EUI64) Enter appEUI of device (e.g., 0102030405060708) Device Profile: Select device profile (e.g., AS9232_2_PROFILE) Click SUBMIT to save Further reference For further reference on Chirp  Stack Network Server, please access the referenced document at link ChirpStack open-source LoRaWAN Network Server Instructions to configure embedded Node RED development tool in PINEX Node-RED Version The embedded version Node-RED in the PINEX gateway firmware 6 is  v3.x Turn on Node Red Navigate to Tool on the left panel→ click Node Red → click Star Node-Red then click Open New Tab Setup Connection Prerequisite: The Embedded Chirp Stack Network Server in the PINEX gateway must be active and configured properly to forward data to embedded Node RED development tool. Details to activate and configure embedded Chirp Stack are at the link: https://daviteq.com/en/manuals/books/manual-for-lorawan-sensor/page/instruction-to-configure-embedded-chirpstack-network-server-in-pinex-firmware-6 Use the  MQTT-in node to receive data from embedded Chirp Stack Network Server Double click mqtt node → click + Add new mqtt-broker config node and Fill in the following fields Server: localhost Port: 1883 Protocol: Select MQTT V3.1.1 Client ID: Leave blank for auto generated Click Add to save settings Configure mqtt node following field (after adding mqtt broker) Topic: application/+/device/+/event/+ QoS: 0 Output: auto-detect Add debug node and click deploy Further reference For further reference on Node RED development tool, please access the referenced document at link: Low-code programming for event-driven applications : Node-RED Manual for PINEX Outdoor LoRaWAN Gateway - PINEX | FW7 1. GENERAL INFORMATION Thank you very much for choosing Daviteq LoRaWAN gateway. We are the leading wireless sensor manufacturer in the World. We have a wide range of wireless sensors which support different connectivity like LoRaWAN, Sigfox, Sub-GHz, NB-IoT...Please find out more information at this link.This manual is applied to the following products Item code HW Version Firmware Version Remarks PINEX-E9-SINGLE 4H 7F0624 PINEX-E8-SINGLE 4H 7F0624 GWODR-8-WET-RN 4H 7F0624 PINEX-8-GPS-DUAL-POE 4H 7F0624 2. QUICK GUIDE Reading time: 20 minutesFinish this part so you can understand and put the device in operation with the default configuration from the factory. 2.1. What is the PINEX? PineX is an industrial-grade outdoor LoRaWAN® Gateway, designed to operate reliably in the harshest environments—from scorching deserts to freezing Arctic conditions, and even hurricane-force winds up to 200 km/h. With IP67-rated waterproof and dustproof protection, an extended temperature range of -40°C to +70°C, and Dual LoRa Antennas for extended coverage, PineX ensures uninterrupted, long-range connectivity even in extreme weather conditions. Supporting all global LoRaWAN frequency bands, PineX integrates a built-in Network Server, Node-RED, and VPN security, enabling fast, cost-efficient, and secure IoT deployments. Designed for Smart Cities, Industrial Facilities, Smart Agriculture, and remote IoT applications, PineX is the ultimate rugged, high-performance LoRaWAN Gateway for mission-critical operations. 2.2. What's in the package? 2.2.1. Advanced version The package includes:01 x LoraWAN PINEX Gateway02 x Lora Antenna01 x Cellular & GPS module (optional)01 x Power Adapter 01 x Converter cable01 x PoE Injector01 x Mounting Accessories 2.2.2. Economy version The package includes:01 x LoraWAN PINEX Gateway01 x Lora Antenna01 x WiFi Antenna (optional)01 x Power Adapter 01 x Converter cable01 x PoE Injector01 x Mounting Accessories 2.3. Product Overview LED Functions LED Functions Constant Flashing Off Power Power On None OFF Network Initializing, High network traffic Internet Available Disconnected LoRa LoRa Working Initializing LoRa Not Working RESET Button Some configuration such as Packet Forwarder settings, VPN settings, WAN settings will be restored to factory defaults when reset process completely taken. Use a pointed stick to poke the button inside the hole and hold for 5 seconds. The gateway will automatically perform reset process. The whole process will take a few minutes. Reset the device only when absolutely necessary Function switch The switch have to be in Run position in normal operation. Boost mode uses for firmware update. Jumpers There are four jumpers. Default position of four is connecting port 1 and 2. Only change the jumper position when the gateway doesn't support PoE+ source 802.3atbut you want to power the gateway through ethernet cable as the below diagram. To power the gateway through Ethernet cable as the above diagram, four jumpers have to change to connecting port 2 and port 3 as below WARNING:If gateway is powered through Ethernet cable as the above diagram BUT four jumpers ARE NOT be changed to connecting port 2 and port 3 as below, the gateway will be damage/defective It is only applied for the gateway version that doesn't support PoE+ source 802.3at 2.4. Installation Startup the LoraWAN Gateway through the following steps Step 1: Install the antenna of the LoRaWAN Gateway Install the Lora antenna and WiFi antenna (optional) in the correct position. Make sure the antenna and Gateway are tightly connected. Step 2 :Use the screw driver to remove the three screws, then open the gateway cover. Step 3: Connect the Ethernet cable to the Gateway Connect the Ethernet cable into LAN port. Step 4: Close the gateway's cover, then use the screw driver to lock the 3 screws. Step 5: Install the SIM card to Cellular & GPS module (optional) Use the screw driver to remove the screw in the module, then carefully open the cap Insert the SIM card into the slot, pay attention to the direction of the Sim card Step 6: Install the Cellular & GPS module to the gateway (optional) Plug the Cellular & GPS module to the M12-FM port at the top of the gateway, then tighten the connector Install the connection protection accessories Step 7 : Power up the Gateway through M12 port 2.5. Mounting Economy version Step 1: Select the installation location. The surface must be flat. Step 2: Based on the dimensions of the gateway's base, drill four holes into the wall. Then, insert wall anchors into the drilled holes. Step 3: Use screws to secure the gateway onto the drilled surface. Advanced version There are two methods for mounting the gateway1. Mount the gateway to the steel pole with a hose clamp 2. Attach the bracket to the wall, then mount the gateway on the bracket. 2.6. Configure the LoRaWAN Gateway 2.6.1 GUI Access Default mode of Daviteq Gateway is DHCP. Once gateway is turned on through plugging in the DC adapter, it will automatically link to available servers. Gateway’s IP address can be found from the DHCP server. Access Gateway Web UI via the DHCP IP on browser. The default username is “admin”, and the password can be found on the inside label. By default, the gateway is configured to use DHCP. Therefore, it must be connected to a network with an active DHCP server in order to access the Web GUI. If the gateway is to be used in a static IP network without DHCP, it must firstly be connected to another active DHCP server to access the configuration interface to configure static IP for the gateway. Once the initial configuration is complete, the gateway can then be moved to the static IP network. Details of static IP configuration for the gateway are in sub-section of WAN SETTINGS in section of 2.2.6.2 Network WAN configuration In some company with strict IT regulations, the gateway MAC address must be added to company network white list for proper connection. To access the GUI, follow these steps: Step 1: Use a computer to connect to the network that the gateway is connected. The computer can connect to that network via WiFi or Ethernet. Step 2: Use the IP scanning software to find the IP address of the gateway based on its Mac address that can be found on the back label. Access this link to get a free IP scanning software on the internet Step 3: Enter the IP address of the gateway in the web browser to access the configuration interface. Must add port 4050 after the IP address. For example, If the IP address of the Gateway is 192.168.1.21 , you have to enter 192.168.1.21:4050 in web browser, then the GUI will be displayed. The default username is admin and default password is public. Please check updated username and password on the gateway label. After login successfully, the general information of the gateway will be display at general information tab. 2.6.2 Network WAN configuration This category shows current WAN settings. This category is further divided into three sectors: WAN Status, Data Statistics and WAN Settings. WAN Status The current network status will be shown on this page. WAN Statistics Statistics on the gateway's used data capacity are shown in this section WAN Settings Daviteq Gateway supports internet connectivity via both Ethernet , Wi-Fi (optional) or Cellular (optional). The default Ethernet mode is DHCP. Follow the steps below to set up the Ethernet network to static mode. Step 1: In the Network section, select WAN.Step 2: Click on the WAN Settings tab at the top.Step 3: In the Configuration field, select Ethernet WANStep 4: Enter the Ethernet WAN information, including WAN Type, IP address, Subnet Mask, Gateway and DNS server Step 5: Click the Apply button to save and apply the new configuration. Follow the steps below to set up the Wi-Fi network for the gateway: Step 1: In the Network section, select WAN.Step 2: Click on the WAN Settings tab at the top.Step 3: In the Configuration field, select Wi-Fi.Step 4: Enter the Wi-Fi information, including SSID (Wi-Fi name), Password, and Wi-Fi Type (default: DHCP Client).Step 5: Click the Apply button to save and apply the new configuration. Follow the steps below to set up the Cellular network for the gateway: Step 1: In the Network section, select WAN.Step 2: Click on the WAN Settings tab at the top.Step 3: In the Configuration field, select 3G/4G LTEStep 4: Enter the 3G/4G LTE information, including APN, Username, Password, and Authentication Method (base on the SIM card provider).Step 5: Click the Apply button to save and apply the new configuration. Follow the steps below to set up network priority The metric in routing determines the priority of a network route. A lower metric value means higher priority when multiple routes to the same destination exist. For example, 100 is higher priority than 101. Step 1: In the Network section, select WAN.Step 2: Click on the Metric settings tab at the top.Step 3: Enter the the metric factor for available network.Step 4: Click the Apply button to save and apply the new configuration. 2.6.3. Lora Settings The LoRa menu consists of the following categories: Package Forwarder and Logs. Configure some basic fields for the gateway operation. Package Forwarder Select Packet Forwarder in the left menu, then choose Gateway Info. This page is for setting up the LoRa configuration including Channel Plan, Gateway ID, Server Address, Server Uplink Port, Server Downlink Port, Keep-Alive Interval, Statistics Display Interval, and Push Timeout Need to properly configure the Server Address, Server Uplink Port, and Server Downlink Port fields. These information depend on the Network server. Choose the channel plan for the gateway, then choose the Apply button at the bottom right to save the current configuration. Parameter name Description Default value Channel Plan The region refers to the specific geographical area where the gateway operates, following the LoRaWAN Regional Parameters defined by the LoRa Alliance EU868 Gateway ID The Gateway ID (also known as DevEUI) is a unique identifier assigned to a LoRaWAN gateway. Unique value Server Address The server address in a LoRaWAN gateway refers to the network server’s IP address or domain name that the gateway connects to for data transmission and management localhost Server Uplink Port The server uplink port in a LoRaWAN gateway refers to the port number used to send uplink packets 1680 Server Downlink Port The server downlink port in a LoRaWAN gateway is the port number used for receiving downlink packets 1680 Keep alive interval The keep-alive interval is the time interval at which a LoRaWAN gateway sends periodic status messages (heartbeats) to the network server to indicate that it is active and connected. 30 Watcher Packet Forwarder: - Interval: Interval for checking the system log to verify successful uplink to the network server. - Packet Forwarder Reset Threshold: Number of consecutive uplink failures before resetting the packet forwarder - Gateway Reboot Threshold: Number of packet forwarder resets before resetting the gateway. 3G/4G LTE - Check 3G/4G LTE Connection: Enable/disable checking 3G/4G LTE connection              - Ping Address: IP address or domain name for sending ping packets - Ping Packets: Number of ping packets sent from the gateway to a specified IP address or domain name - Ping Packet Timeout: Timeout duration for a ping packet with no response - LTE Drop Threshold: Number of failed LTE module reconfiguration attempts before resetting the gateway - Downtime Due to Power Reset: Delay time between powering off and powering on the LTE module. Logs This is the function of monitoring the loRaWAN network. 2.7 Add the LoraWAN Gateway to Network Server 2.7.1 Add the LoraWAN Gateway to Embedded Chirp Stack Network Server Please follow instruction at link: Instruction to configu... | Online Product Manuals & Datasheets 2.7.2 Add the LoraWAN Gateway to External LoRaWAN Network Server To give an example, please follow the instructions in this link to add LoraWAN gateway to The things Stack network server 2.8 Activate and configure the embedded Node RED development tool Prerequisite: The Embedded Chirp Stack Network Server in the PINEX gateway must be active and configured properly to forward data to embedded Node RED development tool. Details to activate and configure embedded Chirp Stack are at the link: https://daviteq.com/en/manuals/books/manual-for-lorawan-sensor/page/instruction-to-configure-embedded-chirpstack-network-server-in-pinex-firmware-6 Please refer the below link for instruction to add the embedded Node RED  development tool: Instructions to config... | Online Product Manuals & Datasheets 3. PRODUCT SPECIFICATION LoRaWAN Specification LoRaWAN 1.0.3 Frequency Band Select 863∼870MHz or 902∼928MHz Number of Channels Up to 8 concurrent channels for LoRa transmission LoRa Transmit Power 0.5W (up to 27 dBm) LoRa Receive Sensitivity Down to -139dBm@SF12, BW 125 kHz. LoRa Software Package Forwarder Advanced Software features OpenVPN, built-in LoRaWAN Network Server & Node-RED, Cellular Internet Routing function Standard Host Communication Ethernet 100Mbps, via outdoor RJ45 connector Optional External Cellular Module LTE Cat 4, supports multi-region and global bands as below Frequency Bands for AU: LTE-FDD (B1/2/3/4/5/7/8/28) LTE-TDD (B40) Frequency Bands for EU: LTE-FDD (B1/3/7/8/20/28A) LTE-TDD (B38/40/41) Frequency Bands for A: LTE-FDD (B2/4/12) Frequency Bands for Global: LTE-FDD (B1/2/3/4/5/7/8/12/13/18/19/20/25/26/28) LTE-TDD (B38/39/40/41) Optional GPS GPS + GLONASS Antenna Type Single/Dual LoRa antenna, optional 4G LTE internal/external antenna Power supply 12 - 24 VDC Ethernet port Optional support PoE+ source 802.3at Housing Anodized Aluminum, IP67, can withstand Wind speeds up to 200 Km/h Working temperature -40 to 70 oC Dimensions Diameter of 70 mm, H:500 mm (include antenna) Weight < 2.0kg 4. WARRANTY & SUPPORT Below terms and conditions are applied for products manufactured and supplied by Daviteq Technologies Inc. 4.1  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 was shipping costs to the Return center shall be paid by Customers. 4.2 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. Notes:* 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. 4.3 Support 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. 5. ADVANCED TROUBLESHOOTING Problem Possible causes Solution The Ethernet port's LED is not lighting up Gateway is in boost mode Turn off the power supply, wait until all the gateway's LEDs are off, then change the switch from Boost to Run. After that, Power on the gateway. Can not scan the gateway's IP address 1. The computer and the gateway are not on the same network2. The network does not support DHCP. 3. The gateway was configured to use static IP mode 1. Check network of computer and gateway. 2. Use another active DHCP server network to access the configuration interface. 3. Press & hold the reset button within 5 seconds, then wait for 5 minutes before trying again. The gateway is not online on Network Server Wrong configuration Check the Package Forwarder configuration on the gateway and gateway register configuration on Network Server. OPERATION INSTRUCTION OPERATION INSTRUCTION FOR RMC SYSTEM-AEON DELIGHT 1. Overview of the Operating Principle The LRW-DI sensor is connected to the contacts that output the alarm signals. When the LRW-DI sensor receives an alarm signal from the field devices, it will send a data packet to the Gateway via a wireless signal. The Gateway will then forward it to the server through the internet connection (4G SIM). The supervisor will observe the alarm signal on the software. 2. Overview of the System Hardware Main device list No. Item code Description 1 GWIND-8 GATEWAY LORAWAN - INDOOR, POE 2 BP-11V-28AH-01 Battery Pack 11V 28AH 3 WSLRW-DI-12 LORAWAN NODE WITH DIGITAL INPUT 4 CONVT-ACDC-OPTO-01 Converter for AC100-220VAC and 10-30VDC to open collector 5 L91-ENERGIZER BATTERY AA ENERGIZER LITHIUM 6 SIM3G-BIGDATA SIM3G-BIGDATA 3. Software Features Guide 3.1. Login Instructions Step 1: Access the software via the link: https://vizuo.globiots.com Step 2: Log in with the account: 3.2. Main Monitoring Dashboard After successfully logging into the software, navigate to Management => Dashboard => AEON-DELIGHT-RV00002 to access the main monitoring interface. Feature Description: Each dot on the map represents the status of one site Normal: Green Alarm: Flashing Red Each site will have a alarm information table that includes the alarm Each circle with the corresponding name below indicates the status of that point. Normal: Green Alarm: Red When clicking on the alarm information table, a history of alarms will be displayed. This table contains the historical alarm information for all points in the corresponding site, allowing for time selection to retrieve data. When a alarm occurs, the site dot will flash red, and the circle of the alarm point will also turn red. An alarm will sound through the computer speaker. Users can acknowledge the alarm to silence the sound, but the dot and circle will still display red. 3.3. Instructions for Reports Step 1: Navigate to Management => Report => AEON BÌNH DƯƠNG NEW CITY_ALARM TRENDING to access the historical alarm report.Step 2: Select the time frame for data retrieval (From... To...).Step 3: Click the Show button in the top right corner of the screen to retrieve the data. The vertical axis represents the status of the signal (1 = Alarm; 0 = Normal). The horizontal axis is the timeline. Step 4: Click to the symbol at the top right corner, select Export to CSV to export the data as a .csv file 3.4. Alarm Management The feature allows for retrieving the historical alarm data of each monitoring point. The retrieval time is optional and allows exporting the report as a .xls file. Step 1: Navigate to Management => Alarm Management => HistoryStep 2: Select the device you want to retrieve data from.Step 3: Choose the time frame you want to retrieve and click the Show button. Step 4: Click the Export button to export the file in .xls format. 3.5. Other Features 3.5.1 Device management: allows to expand additional sites (Nodes) and monitoring points (LoRa). 3.5.2. User management User is created by following steps: In Home screen, click menu Administrators → select sub-menu User Management In screen of user list, click button “Add user” to add new user. Enter basic information into panel (1). Click button “Continue” to go to step 2. After click button “Continue”, screen of step 2 should appear: Enter information for user to sign-in into panel (1): Email: enter email address. Email is unique. Username: enter username for sign in. Username is unique. Username has at least 6 characters. Password: default password is “abc@123”. User must change password when user sign in in the first time. Click button “Continue” to go to step 3.Enter full information for user. Uppercase and lowercase of email and username are the same. Example: username “USERNAME1” is the same as username “username1”. Screen of step 3 should appear: (1) Display basic information of user in step 1.(2) Display information for sign in in step 2. Click button “Save” to save information. After click button “Save”, confirmation screen should appear: Click button “OK” to finish. 3.5.3. Group management Group is used to assign authorities to users. In Home screen, select menu Administrators → select sub-menu Group Management In screen of group list, click button “Add Group” to create new group of account. Enter basic information of group into panel (1). Group Name: Enter group name. Group name is unique. Click button “Continue” to go to step 2. After click button “Continue”, screen of step 2 should appear: Select assigned functions for group in area Only display assigned functions of account. Click button “Continue” to go to step 3.Screen of step 3 should appear: (1) Display available nodes of account. Tick nodes to assign to group. Click button “Continue” to go to step 4.Screen of step 4 should appear: Display list of users. The users have not been assigned to the group. Display list of users which has already been assigned to the group. Button “Assign”: click to assign selected user to group. After click “Assign” button, selected user should be in the list in panel (2). Button “Remove”: remove user from group. After click button “Remove”, selected user should be in the list in panel (1). Click button “Continue” to go to step 5.Screen of step 5 should appear: (1) Display list of Dashboard of signing in group. The Dashboard has not been assigned to group.  (2) Display list of Dashboard of signing in group. The Dashboard has already been assigned to group. Button “Assign”: click to assign dashboard to group. Assigned dashboard should be in panel (2). Button “Remove”: remove dashboard out of group. Removed dashboard should appear in panel (1). Click button “Continue” to go to step 6. Screen of step 6 should appear to view Summary information of group from step 1 to step 8. Click button “Save” to save information.After click button “Save”, confirmation screen should appear: Click button “OK” to finish. 3.5.3. Send notification emails to the account set up prior to receiving alarm signals 4. Troubleshooting No. Common Errors Solution 1 There is an alarm signal at the field device, but it is not reporting to the software Step 1. Check the output signal contacts on the field device. Step 2. Check the connection between the alarm device and the LRW-DI sensor. Step 3. Contact Daviteq Technical Support (via Zalo or hotline). 2 Disconnection at a single point Step 1. Check for abnormalities at the sensor of the disconnected point (e.g. physical impact, obstruction, etc.)Step 2. Check the power LED of all gateways at the siteStep 3. Contact Daviteq Technical Support (via Zalo or hotline) 3 Disconnection at a site Step 1. Check the power LED of all gateways at the siteStep 2. Contact Daviteq Technical Support (via Zalo or hotline) 4 Disconnection at multiple sites Step 1. Contact Daviteq Technical Support (via Zalo or hotline) 5. Hardware Connect 5.1. Instructions for replacing the DI node 5.2. Instructions for replacing the battery X Manual for PINEX Outdoor LoRaWAN Gateway - PINEX | FW8 I. QUICK GUIDE 1.1 Introduction PineX is an industrial-grade outdoor LoRaWAN® Gateway, designed to operate reliably in the harshest environments—from scorching deserts to freezing Arctic conditions, and even hurricane-force winds up to 200 km/h. With IP67-rated waterproof and dustproof protection, an extended temperature range of -40°C to +70°C, and Dual LoRa Antennas for extended coverage, PineX ensures uninterrupted, long-range connectivity even in extreme weather conditions. Supporting all global LoRaWAN frequency bands, PineX integrates a built-in Network Server, Node-RED, and VPN security, enabling fast, cost-efficient, and secure IoT deployments. Designed for Smart Cities, Industrial Facilities, Smart Agriculture, and remote IoT applications, PineX is the ultimate rugged, high-performance LoRaWAN Gateway for mission-critical operations. 1.2 Application Notes For Applications Ambient Air Quality Monitor, Indoor Air Quality Monitor, Gas Analyzing, Warehouse Monitoring, Gas Leakage Detection Notes When selecting a LoRaWAN gateway, it is essential to choose the correct frequency band based on your region (e.g., 920–925 MHz or 863–870 MHz depending on local regulations). Ensure the gateway supports suitable network connectivity options such as Ethernet, Wi-Fi, or 4G/LTE, depending on the availability and reliability of internet access at the installation site. Also, consider whether the deployment is indoor or outdoor. The indoor gateways are compact and economy, while outdoor gateways should be weatherproof (e.g., IP67-rated) and capable of wider coverage. Choosing the right version ensures stable performance and long-term reliability. 1.3 What's in the Package? 1.3.1 Advanced version The package includes:01 x LoraWAN PINEX Gateway02 x Lora Antenna01 x Cellular & GPS module (optional)01 x Power Adapter 01 x Converter cable01 x PoE Injector01 x Mounting Accessories 1.3.2 Economy version The package includes:01 x LoraWAN PINEX Gateway01 x Lora Antenna01 x WiFi Antenna (optional)01 x Power Adapter 01 x Converter cable01 x PoE Injector01 x Mounting Accessories 1.4 Product Overview LED Functions LED Functions Constant Flashing Off Power Power On None OFF Network Initializing, High network traffic Internet Available Disconnected LoRa LoRa Working Initializing LoRa Not Working RESET Button Some configuration such as Packet Forwarder settings, VPN settings, WAN settings will be restored to factory defaults when reset process completely taken. Use a pointed stick to poke the button inside the hole and hold for 5 seconds. The gateway will automatically perform reset process. The whole process will take a few minutes. Reset the device only when absolutely necessary Function switch The switch have to be in Run position in normal operation. Boost mode uses for firmware update. Jumpers There are four jumpers. Default position of four is connecting port 1 and 2. Only change the jumper position when the gateway doesn't support PoE+ source 802.3at but you want to power the gateway through ethernet cable as the below diagram. To power the gateway through Ethernet cable as the above diagram, four jumpers have to change to connecting port 2 and port 3 as below WARNING:If gateway is powered through Ethernet cable as the above diagram BUT four jumpers ARE NOT be changed to connecting port 2 and port 3 as below, the gateway will be damage/defective It is only applied for the gateway version that doesn't support PoE+ source 802.3at 1.5 Power Supply There are two ways to power the PineX Gateway. It is recommended to use the included power adapter ( 12VDC@2A) to power the gateway. Power the PineX gateway through the M12 Port Power the PineX gateway via Ethernet port If the gateway does not support PoE+ (802.3at), but you want to power it through the Ethernet cable, the jumpers must be changed as instructed in the "Jumpers" section of 1.4 Product Overview.Ensure that you understand the principle before powering the device in this way. 1.6 Guide for Quick Test Startup the LoraWAN Gateway through the following steps Step 1: Install the antenna of the LoRaWAN Gateway Install the Lora antenna and WiFi antenna (optional) in the correct position. Make sure the antenna and Gateway are tightly connected. Step 2 :Use the screw driver to remove the three screws, then open the gateway cover. Step 3: Connect the Ethernet cable to the Gateway Connect the Ethernet cable into LAN port. Step 4: Close the gateway's cover, then use the screw driver to lock the 3 screws. Step 5: Install the SIM card to Cellular module (optional) Use the screw driver to remove the screw in the module, then carefully open the cap Insert the SIM card into the slot, pay attention to the direction of the Sim card Step 6: Install the Cellular module to the gateway (optional) Plug the Cellular module to the M12-FM port at the top of the gateway, then tighten the connector Install the connection protection accessories Step 7 : Power up the Gateway through M12 port Step 8 : Access Gateway'sGUI Default mode of Daviteq Gateway is DHCP. Once gateway is turned on through plugging in the DC adapter, it will automatically link to available servers. Gateway’s IP address can be found from the DHCP server. Access Gateway Web UI via the DHCP IP on browser. The default username is “admin”, and the password can be found on the inside label. By default, the gateway is configured to use DHCP. Therefore, it must be connected to a network with an active DHCP server in order to access the Web GUI. If the gateway is to be used in a static IP network without DHCP, it must firstly be connected to another active DHCP server to access the configuration interface to configure static IP for the gateway. Once the initial configuration is complete, the gateway can then be moved to the static IP network. Details of static IP configuration for the gateway are in sub-section of WAN SETTINGS in section of 2.2.6.2 Network WAN configuration In some company with strict IT regulations, the gateway MAC address must be added to company network white list for proper connection. Use a computer to connect to the network that the gateway is connected. The computer can connect to that network via WiFi or Ethernet. Use the IP scanning software to find the IP address of the gateway based on its Mac address that can be found on the back label. Access this link to get a free IP scanning software on the internet Enter the IP address of the gateway in the web browser to access the configuration interface. Must add port 4050 after the IP address. For example, If the IP address of the Gateway is 192.168.1.21 , you have to enter 192.168.1.21:4050 in web browser, then the GUI will be displayed. The default username is admin and default password is public. Please check updated username and password on the gateway label. After login successfully, the general information of the gateway will be display at general information tab. Step 9: Lora Settings The LoRa menu consists of the following categories: Package Forwarder and Logs. Configure some basic fields for the gateway operation. Package Forwarder Select Packet Forwarder in the left menu, then choose Gateway Info. This page is for setting up the LoRa configuration including Channel Plan, Gateway ID, Server Address, Server Uplink Port, Server Downlink Port, Keep-Alive Interval, Statistics Display Interval, and Push Timeout Need to properly configure the Server Address, Server Uplink Port, and Server Downlink Port fields. These information depend on the Network server. Choose the channel plan for the gateway, then choose the Apply button at the bottom right to save the current configuration. Parameter name Description Default value Channel Plan The region refers to the specific geographical area where the gateway operates, following the LoRaWAN Regional Parameters defined by the LoRa Alliance EU868 Gateway ID The Gateway ID (also known as DevEUI) is a unique identifier assigned to a LoRaWAN gateway. Unique value Server Address The server address in a LoRaWAN gateway refers to the network server’s IP address or domain name that the gateway connects to for data transmission and management localhost Server Uplink Port The server uplink port in a LoRaWAN gateway refers to the port number used to send uplink packets 1680 Server Downlink Port The server downlink port in a LoRaWAN gateway is the port number used for receiving downlink packets 1680 Keep alive interval The keep-alive interval is the time interval at which a LoRaWAN gateway sends periodic status messages (heartbeats) to the network server to indicate that it is active and connected. 30 Watcher Packet Forwarder: - Interval: Interval for checking the system log to verify successful uplink to the network server. - Packet Forwarder Reset Threshold: Number of consecutive uplink failures before resetting the packet forwarder - Gateway Reboot Threshold: Number of packet forwarder resets before resetting the gateway. Step 10: Network WAN configuration This category shows current WAN settings. This category is further divided into three sectors: WAN Status, Data Statistics and WAN Settings. WAN Status The current network status will be shown on this page. WAN Statistics Statistics on the gateway's used data capacity are shown in this section WAN Settings Daviteq Gateway supports internet connectivity via both Ethernet , Wi-Fi (optional) or Cellular (optional). The default Ethernet mode is DHCP. Follow the steps below to set up the Ethernet network to static mode. Step 1: In the Network section, select WAN.Step 2: Click on the WAN Settings tab at the top.Step 3: In the Configuration field, select Ethernet WANStep 4: Enter the Ethernet WAN information, including WAN Type, IP address, Subnet Mask, Gateway and DNS server Step 5: Click the Apply button to save and apply the new configuration. Follow the steps below to set up the Wi-Fi network for the gateway: Step 1: In the Network section, select WAN.Step 2: Click on the WAN Settings tab at the top.Step 3: In the Configuration field, select Wi-Fi.Step 4: Enter the Wi-Fi information, including SSID (Wi-Fi name), Password, and Wi-Fi Type (default: DHCP Client).Step 5: Click the Apply button to save and apply the new configuration. Follow the steps below to set up the Cellular network for the gateway: Step 1: In the Network section, select WAN.Step 2: Click on the WAN Settings tab at the top.Step 3: In the Configuration field, select 3G/4G LTEStep 4: Enter the 3G/4G LTE information, including APN, Username, Password, and Authentication Method (base on the SIM card provider).Step 5: Click the Apply button to save and apply the new configuration. Follow the steps below to set up network priority The metric in routing determines the priority of a network route. A lower metric value means higher priority when multiple routes to the same destination exist. For example, 100 is higher priority than 101. Step 1: In the Network section, select WAN.Step 2: Click on the Metric settings tab at the top.Step 3: Enter the the metric factor for available network.Step 4: Click the Apply button to save and apply the new configuration. 1.7 Gateway Communication 1.7.1 Gateway communication to LoRaWAN device 1.7.2 Gateway communication to Network Server 1.7.2.1 Add the LoraWAN Gateway to Embedded Chirp Stack Network Server Please follow instruction at link: Instruction to configu... | Online Product Manuals & Datasheets 2.7.2 Add the LoraWAN Gateway to External LoRaWAN Network Server To give an example, please follow the instructions in this link to add LoraWAN gateway to The things Stack network server 1.7.3 Activate and configure the embedded Node RED development tool Prerequisite: The Embedded Chirp Stack Network Server in the PINEX gateway must be active and configured properly to forward data to embedded Node RED development tool. Details to activate and configure embedded Chirp Stack are at the link: https://daviteq.com/en/manuals/books/manual-for-lorawan-sensor/page/instruction-to-configure-embedded-chirpstack-network-server-in-pinex-firmware-6 Please refer the below link for instruction to add the embedded Node RED  development tool: Instructions to config... | Online Product Manuals & Datasheets To give an example, please follow the instructions in this link to add LoraWAN gateway to The things Stack network server 1.8 Default Communication Configuration Default value Time zone UTC LoRaWAN Frequency plan EU868 Network Server host localhost NS uplink port 1700 NS downlink port 1700 Network Server Settings description OFF NS integration descriptions OFF NodeRED Settings descriptions OFF IP forwarding OFF WAN Ethernet Settings DHCP Client VPN setting OFF Ethernet Interface Metric 100 3G/4G LTE Interface Metric 101 WIFI Interface Metric DISABLED Lora Watcher Service ENABLE Packet Forwarder Interval 15 Packet Forwarder Reset Threshold 20 Gateway Reboot Threshold 5 1.9 Installation and Wiring Economy version Step 1: Select the installation location. The surface must be flat. Step 2: Based on the dimensions of the gateway's base, drill four holes into the wall. Then, insert wall anchors into the drilled holes. Step 3: Use screws to secure the gateway onto the drilled surface. Advanced version There are two methods for mounting the gateway1. Mount the gateway to the steel pole with a hose clamp 2. Attach the bracket to the wall, then mount the gateway on the bracket. II. MAINTENANCE 2.1 Maintenance There is no requirement for maintenance of the Hardware of LoRaWAN Gateway. 2.2 Troubleshooting Problem Possible causes Solution The Ethernet port's LED is not lighting up Gateway is in boost mode Turn off the power supply, wait until all the gateway's LEDs are off, then change the switch from Boost to Run. After that, Power on the gateway. Can not scan the gateway's IP address 1. The computer and the gateway are not on the same network2. The network does not support DHCP. 3. The gateway was configured to use static IP mode 1. Check network of computer and gateway. 2. Use another active DHCP server network to access the configuration interface. 3. Press & hold the reset button within 5 seconds, then wait for 5 minutes before trying again. The gateway is not online on Network Server Wrong configuration Check the Package Forwarder configuration on the gateway and gateway register configuration on Network Server. III. ADVANCE GUIDE 3.1 Operation Principle A LoRaWAN gateway functions as a transparent bridge between LoRa end devices and the LoRaWAN network server. It receives uplink packets from end devices via LoRa radio signals and forwards them to the network server over an IP-based backhaul (e.g., Ethernet, Wi-Fi, or cellular).The gateway also receives downlink messages from the network server and transmits them to the appropriate end devices. It does not process or modify the payload data, ensuring secure and efficient communication between devices and the server. 3.2 Firmware update 3.2.1 Preparation - Prepare a Windows PC. - Prepare a USB-C cable for connecting the PC and the gateway. - Download and unzip the firmware file 3.2.2 Download and Install Software Download & Install Win32DiskImage from the link Download & Install Raspberry USB Boot Visit the link and download rpiboot_setup.exe. Then, install Raspberry USB Boot in the PC 3.2.3 Flashing Firmware to PineX Gateway Step 1: Make sure the gateway is completely powered off (all three LEDs are off).Use a screwdriver to remove the three screws and open the gateway cover. Then, remove the plastic cover to access the USB-C port. Step 2: Change the switch mode from Run to Boost as shown in the picture. Step 3: Power on the gateway and wait for about 15 seconds. Then, connect the gateway to the PC via the USB-C cable. Step 4: Open rpiboot-CM4-CM5-Mass Storage Gadget. Open This PC on the PC and check whether a new drive named "bootfs" appears. If "bootfs" appears as shown in the image below, the connection is successful. If "bootfs" does not appear, go back and repeat the process from Step 1. Take note of the drive letter assigned to "bootfs" — for example, Drive E: Step 5: Open Win32DiskImage software. Browse to the firmware file and select correct Device (the drive letter assigned to "bootfs" in step 4). Then click the Write button to flash the firmware to the gateway. Wait a few minutes until a "Write successful" message is displayed. This means the firmware flashing process has completed successfully. 3.3 Connect directly from window PC to gateway through ethernet cable for configuration 3.3.1 PREPARATION Hareware A Daviteq gateway A window laptop A USB-to-LAN adapter ( if the laptop does not have ethernet port) A traight ethernet cable Software Download and Install Tftdp64 software (attached file) 3.3.2 DETAILED INSTRUCTIONS Step 1: Type “Network Connections” in the search bar, then select “View network connections.” Step 2: Plug the USB-to-LAN adapter into the laptop. Wait for a few seconds, and the Ethernet connection of the adapter will appear. Step 3: Right click the Ethernet connection of the adapter, then select Properties Step 4: In the Networking tab, select Internet Protocol Version 4(TCP/IPv4). Then, select Use the following IP address and input the imformation as shown in the picture below IP address : 192.168.10.1 Subnet mask: 255.255.255.0 Press OK button to save the configuration Step 5: Run Command Prompt as administrator Copy and paste command below to the Command Promt to temporarily turn off the Firewall netsh advfirewall set allprofiles state off Step 6: Open the Tftpd64 Software, click the Settings button, then configure it as shown in the pictures below. After that, click OK to save the new settings. (Only change the settings in the red box, leave the rest as default) Step 7:  Power on the gateway, then connect the Ethernet cabble from the gateway to the laptop through the adapter. Wait for a few seconds, the IP address of the gateway will be displayed in DHCP server tab of the Tftpd64 software Step 8: Access the gateway’s GUI via the IP address and port 4050 (e.g., 192.168.10.3:4050).If the web browser displays as shown in the image below, it means you have successfully accessed the gateway. Next, refer to the user guide to configure the Wi-Fi and the LoRaWAN Package Forwarder for the gateway. Step 9:After finishing the configuration, please turn the firewall back on for your computer. Run Command Prompt as administrator, then copy and paste the command below to the Command Promt netsh advfirewall set allprofiles state on IV. PRODUCT SPECIFICATIONS LoRaWAN Specification LoRaWAN 1.0.3 Frequency Band Select 863∼870MHz or 902∼928MHz Number of Channels Up to 8 concurrent channels for LoRa transmission LoRa Transmit Power 0.5W (up to 27 dBm) LoRa Receive Sensitivity Down to -139dBm@SF12, BW 125 kHz. LoRa Software Package Forwarder Advanced Software features OpenVPN, built-in LoRaWAN Network Server & Node-RED, Cellular Internet Routing function Standard Host Communication Ethernet 100Mbps, via outdoor RJ45 connector Optional External Cellular Module LTE Cat 4, supports multi-region and global bands as below Frequency Bands for AU: LTE-FDD (B1/2/3/4/5/7/8/28) LTE-TDD (B40) Frequency Bands for EU: LTE-FDD (B1/3/7/8/20/28A) LTE-TDD (B38/40/41) Frequency Bands for A: LTE-FDD (B2/4/12) Frequency Bands for Global: LTE-FDD (B1/2/3/4/5/7/8/12/13/18/19/20/25/26/28) LTE-TDD (B38/39/40/41) Optional GPS GPS + GLONASS Antenna Type Single/Dual LoRa antenna, optional 4G LTE internal/external antenna Power supply 12 - 24 VDC Ethernet port Optional support PoE+ source 802.3at Housing Anodized Aluminum, IP67, can withstand Wind speeds up to 200 Km/h Working temperature -40 to 70 oC Dimensions Diameter of 70 mm, H:500 mm (include antenna) Weight < 2.0kg V. WARRANTY & SUPPORT Below terms and conditions are applied for products manufactured and supplied by Daviteq Technologies Inc. 5.1 Warranty 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 was shipping costs 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. Notes:* 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 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.