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