Only available for Logged-in member. Please login or register to access this information.Or use the Temporary User that we have provided to you via email.
expiry time
Manual for WSLRW-LRO | FW2
Build-to-Order
Replaced by
Replaced by
Item codes | FW Released Date | Changes Information |
|---|---|---|
WSLRW-LRO-01-RN; WSLRW-LRO-01 | 22/01/2025 | Update for latching relay; Add RELAY_TYPE, POWER_SOURCE, and POWER_LEVEL on uplink; Add relay type, pulse width, power source type; Add CONFIG_CHECK uplink and downlink type 3 |
1
QUICK INSTALLATION GUIDE
1.1 Introduction
WSLRW-LRO is a LoRaWAN node with latching relay output to electrically operate switch that uses a small electrical signal to control a larger electrical circuit. It works by energizing a ON relay coil or OFF relay coil, which creates a magnetic field that moves an armature to open or close contacts, allowing or interrupting the flow of electricity. This makes relays essential for controlling high-power devices with low-power signals.
The node will transmit data in kilo-meters distance to the LoRaWAN gateway from any brand on the market. LoRaWAN relay nodes are used in various applications to remotely control devices with low power consumption over long distances. Latching relays are commonly used in applications where it is necessary to maintain the last state after a power failure such as industrial machinery, automate home systems like lighting and heating, regulate pumps and valves in water treatment plants, optimize irrigation in agriculture, control energy distribution in buildings, and operate urban infrastructure such as streetlights and traffic signals.
How the sensor connect to system?
System components:
The end nodes are LoRaWAN Sensors or Actuators;
The Gateways are LoRaWAN Gateway or Base Station;
The Network Server can be SAAS or On-premise server;
The Application Server is the destination software users want to utilize the data from/ to LoRaWAN sensors/ actuators.
How to set up the LoRaWAN system? Please follow these steps:
Adding the Gateways to a Network server. Please refer to the manual of Gateway and Network Server software;
Adding the End nodes to the Network Server;
Configure the callback or data forwarding from the Network Server to the Application Software by MQTT or HTTPS. Please refer to the manual of the Network Server.
Once the payload is on the Application server, decode data from Payload. Please check Section 1.9 for the Payload document.
1.2 Application Notes
For Applications
Smart Irrigation, Water Supply System, Water Level Control, Oil Level Control, Home Automation, Industrial Automation, Energy Distribution, Urban Infrastructure
Notes
Load Requirements: Match the relay’s voltage and current ratings to the load.
Contact Configuration: Select the appropriate contact form (SPST, SPDT, etc.) and rating.
Environmental Conditions: Verify the relay can operate within your temperature and humidity ranges.
Additional Features: Look for necessary features like electrical isolation and suitable mounting style.
Application: Only for application to maintain the last state after a power failure
1.3 When does device send Uplink messages?
The device will send uplink messages in the following cases:
Case 1: After power-up in the 60s, the device will send the first message called START_UP. The payload will tell the user the HW version, FW version, and current configuration of the device.
Case 2: Then, in every interval time (pre-configured), for example, 30 minutes, it will send the message called CYCLIC_DATA. The payload will tell the user the following data like measured values, battery level, and alarm status...
To change the cycle of data sending, you can change the value of the parameter: CYCLIC_DATA_PERIOD.
Case 3: The device will send ALARM message immediately when the relay control command switches from OFF relay to ON relay and vice versa. The alarm uplink contains information of relay control command (ON relay/OFF relay), total remaining schedule in the schedule queue, command status, schedule status, schedule start time, power supply/battery level, valve status, total open time, total close time, and control voltage.
Case 4: During the commissioning, testing, or calibration sensor, the user can force the device to send the uplink message to get the data immediately. This message is called FORCE_DATA. The payload will provide data like raw measured value, scaled measured values, battery level, and alarm status... It can be forced by applying the magnet key on the reed switch in 1s.
Case 5: If users want to change the configuration immediately, they don't need to wait until the next cyclic data-sending message; instead, they can force the device to send a special uplink message so that the device can get the new downlink message. This uplink message is named PARAMETERS_UPDATE. It can be forced by applying the magnet key in more than 5s.
Case 6: In every interval time (pre-configured), for example, 24 hours, it will send the message called HEARTBEAT. The payload will tell the user the following data like hardware version, firmware version, current sensor configuration.
Case 7: If LNS_CHECK_MODE =1, it will send the confirmed uplink message called LNS_CHECK every 24 hours. This confirmed uplink message is a message where a LoRaWAN device is requesting a LoRaWAN network to confirm the reception of its message. If the device receives no confirmation message from LoraWAN network server, it will re-send the LNS_CHECK message every hour during 3 hours. After 4th hour, if the device still receives no confirmation message, it will reset itself to join the network server. The LNS_CHECK payload will tell the user the following data like hardware version, firmware version, current sensor configuration.
Case 8: If the application/network server sends downlink 3 to check current value of a configuration parameter or sends downlink type 4 or downlink type 5 to change value of a configuration parameter, the device will send the CONFIG-CHECK uplink. The payload of CONFIG-CHECK uplink contains the result of the configuration changes/configuration check.
Case 9: When the device receive the control schedule via downlink type 2, it will send SCHEDULE_ACK uplink to acknowledge the receive of the schedule. The uplink contains the received schedule content and ordinal number of the schedule in the schedule queue.
1.4 Default Configuration
This LRO has the default configuration, however, those parameters can be changed. The user can change the configuration on the wireless transmitter so that the complete node (converter + wireless) delivers the proper output value. Please check the Payload document for more information.
1.5 Battery/ Power Supply
The Device uses below batteries:
Battery type: Primary battery
Battery size and Voltage: AA 1.5 VDC
Number of batteries: 02
Recommended batteries: Energizer® L91 or equivalent from Duracell;
Please take note on the Polarity of the batteries as below picture.
Re-install the housing, pay attention to put the PCB edge into the middle guiding slot of the box inside as shown below)
Understanding the battery levels:
Level 3 (4 bars): battery energy is 60-99%
Level 2 (3 bars): battery energy is 30-60%
Level 1 (2 bars): battery energy is 10-30%
Level 0 (1 bar): battery energy is 0-10%
1.6 What's in the Package?
1.7 Guide for Quick Test
With the default configuration, the device can be connected quickly to the Network Server by the following steps.
Step 1: Prepare the values of communication settings
Frequency zone: Most of the sensor was configured the frequency zone to suit customer application before delivery
DevEUI: Get the DevEUI on the product nameplate
AppEUI Default value: 010203040506070809
AppKey Default value: 0102030405060708090A0B0C0D0E0F10
Activation Mode: OTAA with local join server
Network Mode: Public
LoraWAN Protocol: version1.0.3
Class: A for sensor; C for actuator
If current basic common settings do not match with your region, network server/application, follow below instruction to change them as below:
For changing other settings, please refer to Section 3.2 Sensor configuration to change the other settings
Step 2: Register the device on the LoRaWAN network server
Input the above settings on your device registration page of the network server.
Note: Different network server software will have different device registration processes. Please refer to the manual of the network server software used for more details.
Please visit the below Section 1.10 to get the instructions for adding the LoRaWAN sensors to some common network servers such as Actility, TTN...
Step 3: Install the batteries to the device OR do power wiring and supply external power to the device if applicable
Please refer to Section 1.5 as above for instructions on battery installation OR for instructions to do power wiring and supply external power to the the device if applicable
After installing the battery in 60 seconds, the first data packet will be sent to the LoRaWAN gateway. After receiving the first data packet, the time of another packet depends on the value of the parameter: cycle_send_data. Additionally, you can use a magnet key to touch the magnetic switch point on the housing within 1 second to initiate force packet of the device to send data instantly and the LEDs on the housing will be lit with SKY BLUE color.
Step 4: Decode the payload of receiving package
Please refer to Section 1.9 Payload Document and Configuration Tables for details of decoding the receiving packet to get the measured values.
If the device has local display, measured values are shown on the local display
1.8 Installation
Dimension Drawings and Installation Gallery (Photos and Videos)
Please follow the checklist below for a successful installation:
1. Have you studied the dimensions of the device as above drawings?
2. Have you tested and make sure the device have been connected successfully as Section "1.7 Guide for Quick Test" above?
3. Have the device been configured properly as per Section 3.2 below?
4. Have the device been calibrated or validated as per Section 3.3 below?
5. Then you can start to install the device at site. Please check the following Installation Notes for Sensor Part (if available) before installation.
Installation Notes for Sensor Part (if available)
Some important notes for installing a latching relay:
Read the Manual: Always start by reading the manufacturer's installation manual for specific instructions and safety guidelines.
Power Supply: Ensure the power supply voltage matches the relay's contact specifications. Incorrect voltage can damage the relay contact or cause it to malfunction.
Wiring: Follow the wiring diagram provided by the manufacturer. Properly connect the control signals, power supply, and load. Double-check all connections to avoid short circuits or incorrect operation.
Mounting: Securely mount the relay in a suitable location. Ensure it is protected from dust, moisture, and excessive vibration.
Testing: After installation, test the relay by applying control signals to ensure it latches and unlatches correctly. Verify that the relay maintains its state without continuous power.
Safety Precautions: Always turn off the power before making any connections or adjustments. Use appropriate personal protective equipment (PPE) to avoid electrical hazards.
Environment: Ensure the relay is installed in an environment within its operating temperature and humidity range. Extreme conditions can affect its performance.
Maintenance: Periodically check the relay for signs of wear or damage. Clean any dust or debris that may accumulate on the contacts or housing.
Installation Guide for Main Device
Check the Location for the best RF Signal
Make sure the site is good enough for RF signal transmission.
Tip: To maximize the transmission distance, the ideal condition is Line-of-sight (LOS) between the LoRaWAN sensor and the gateway. In real life, there may be no LOS condition. However, the LoRaWAN sensor still communicates with the gateway, but the distance will be reduced significantly.
DO NOT install the wireless sensor or its antenna inside a completed metallic box or housing because the RF signal can not pass through the metallic wall. The housing is made from Non-metallic materials like plastic, glass, wood, leather, concrete, and cement…is acceptable.
Install the Device on the Wall/Housing/Structure and connect to the load
Mount the sensor onto a wall/housing/structure with provided screws.
Connect the first wire (NO label) of the cable to PWR+ of 12 VDC/24VDC/220VAC and connect the second wire (COM label) of the cable to the load. The load must match with specification of the contact (max 220 VAC/8A resistive load/24VDC/5A resistive load). The wirings as below figure
Note:
Device batteries must be not available and external power for relay contact and load must be off during installation and wiring.
1.9 Payload Document and Configuration Tables
Please click below button for:
-
Payload decoding of Uplink messages;
-
Payload encoding of Downlink messages;
-
Configuration Tables of device.
Note:
If the content of below web payload, memory map, and sample decoder could not be copied, please install the extension of "Enable Copy Paste - E.C.P" for Microsoft Edge and for Google Chrome.
1.10 How to connect device to Back-end/ Network Server/ Coordinator
Please find below the examples of adding Daviteq's LoRaWAN sensor to the following Network servers:
ThingPark Community (of Actility);
Things Stack (of The Things Network).
You can use the similar methods to add LoRaWAN sensors to other Network Server.
1. THINGPARK COMMUNITY (ACTILITY) NETWORK SERVER
1.1. Example to add the Tektelic LoraWAN gateway Model T0005204 to ThingPark Enterprise SaaS Community
1. Log in to your ThingPark Enterprise account via the link: https://community.thingpark.io/tpe/
2. Browse on the left panel to Base Stations, click the drop-down menu, then click Create.
3. Select the base station’s Tektelic.
※ If you do not find the Tektelic, click View More Manufacturers.
4. On the following screen, select the Model: Micro 8-channels from the drop-down list.
5. Fill the form as below table:
Input exactly as above Input field column, except Name field is user-defined and is different from the existing base station name on the network server.
After filling the registration form, click CREATE to complete adding the base station to the network server.
1.2. Add Daviteq's LoRaWAN devices to ThingPark Enterprise SaaS Community
ThingPark Enterprise supports all Classes of LoRaWAN® devices. By default, the sensor supports Over-the-Air Activation (OTAA) with a local Join Server that is programmed at the factory.
Manual provisioning of OTAA devices using a local Join Server. To learn more, see Activation modes.
1. At left panel of the screen of the Thingpark GUI, click Devices > Create from the dashboard.
2. Select the Generic supported by your device on your screen.
3. Select the Model of LoRanWAN 1.0.3 revA - class A with correct frequency plan
4. Fill the form as below table:
In addition to filling out the form, the option to select the connection between ThingPark and Daviteq application (Globiots).
After filling out the registration form, please click CREATE to add devices to the network server.
1.3. Send a downlink frame from Thingpark Network Server to the device
Follow the below steps to send the downlink frame from Thingpark Network Server to the device:
This functionality is active only when a connection is associated to the device (one of the color codes with a green bullet).
1. Navigate to the left panel, click the Devices' drop-down menu, then click List.
2. Browse the right side in the Devices, click the icon of the device and click Send Downlink.
3. Input the downlink code to the Payload field and input 1 to the Port field, and then click Validate.
The downlink data is added to the device downlink queue in network server. The downlink is sent after the network server receive an uplink from the device.
2. THINGS STACK (THE THINGS NETWORK) NETWORK SERVER
2.1. Add Sentrius LoraWAN gateway (Model RG19) to The things Stack network server
1. Log in to you’re The Things Stack account
2. Click the tab Gateways, click Add gateway button
3. Fill out the form as below table:
Input exactly as above Input column, except the Gateway Name field and the Gateway ID field is user-defined. It is different from the existing gateway name and gateway ID on the network server.
After filling the registration form, click Create gateway to complete adding the base station to the network server.
2.2. Add Daviteq's LoRaWAN device to The Things Stack network server
The Things Stack supports all Classes of LoRaWAN® devices. By default, the sensor supports Over-the-Air Activation (OTAA) with a local Join Server programmed at the factory.
1. Browse on the top panel, click the tab Application, and click Add application button to create an application
2. Fill in the information fields as user-defined, then select Create application
3. After the application is created successfully, select Add end device to register end device (LoRaWAN sensor)
4. Fill out the form as below table:
After filling out the registration form, please click the Register end device button to add the device to the network server.
2.3. Send a downlink frame from The Things Stack Network Server to the device
1. Select the device to send downlink
2. Input 1 to the FPort and input the downlink data in the payload field, and then tick Confirmed downlink and click Schedule downlink.
2
MAINTENANCE
2.1 Troubleshooting
Please find below steps to identify the problems from Communication Part or Sensor Part:
* If the device cannot connect to the Gateway or System or Co-ordinator at the first time, it is the Communication Problem;
* If the device status like battery, RSSI level, data status or other communication is normal, but the measured values are not updated or wrong, it would be the problems of Sensor part;
* If the data coming to gateway, system or co-ordinator is not frequently as expected, the problem would be Communication.
Please refer below the troubleshooting guide for Communication and Sensor Part.
Troubleshooting for Communication
Troubleshooting for Sensor Part (if available)
Common troubleshooting steps for latching relays:
Check Power Supply: Ensure the relay contact is receiving the correct voltage and current. An unstable or incorrect power supply can cause the relay to malfunction.
Inspect Connections: Verify that all wiring connections are secure and free from corrosion. Loose or corroded connections can prevent the relay from operating correctly.
Test Control Signals: Use a multimeter to check that the control signals are reaching the relay properly. Incorrect or weak signals can cause the relay to fail to latch or unlatch.
Examine Relay Contacts: Look for signs of wear, dirt, or oxidation on the relay contacts. Clean them with a suitable contact cleaner if necessary. Worn or dirty contacts can lead to poor performance.
Look for Mechanical Obstructions: Ensure there are no mechanical obstructions preventing the relay from switching. Sometimes, debris or misalignment can cause the relay to stick.
Test in Isolation: If possible, test the relay in isolation from the rest of the circuit. This can help identify whether the issue is with the relay itself or another component in the circuit.
Replace Faulty Components: If any components are found to be faulty, replace them with new ones that meet the manufacturer's specifications.
Regular maintenance and periodic testing can help prevent issues with latching relays and ensure they operate reliably. If you encounter persistent problems, consulting the manufacturer's documentation or seeking professional assistance may be necessary.
2.2 Maintenance
Maintenance for Main device
There is no requirement for maintenance of the Hardware of LoRaWAN Device except:
For relay, please refer to the maintenance section of the relay document.
Maintenance for Sensor part (if available)
Maintaining a latching relay is crucial for ensuring its longevity and reliable performance. Here are some key maintenance steps:
Regular Inspection: Periodically inspect the relay for any signs of wear, damage, or overheating. Check the housing and connections to ensure everything is intact.
Clean Contacts: Clean the relay contacts to remove any dirt, dust, or oxidation that may accumulate over time. Use a suitable contact cleaner and a soft brush to gently clean the contacts.
Check Connections: Ensure all wiring connections are secure and free from corrosion. Loose or corroded connections can lead to poor performance or failure.
Test Operation: Regularly test the relay's operation by applying control signals and verifying that it latches and unlatches correctly. This helps ensure the relay is functioning as expected.
Monitor Environment: Ensure the relay is operating within its specified temperature and humidity range. Extreme conditions can affect its performance and lifespan.
Replace Worn Components: If any components show signs of wear or damage, replace them with new ones that meet the manufacturer's specifications.
By following these maintenance steps, you can help ensure your latching relay operates reliably and efficiently.
3
ADVANCED GUIDE
3.1 Principle of Operation
Principle of Operation for device WSLRW-LRO | FW2
Device components
Daviteq LoRaWAN Relay Output Node comprises 02 parts linked internally:
• The Daviteq LoraWAN wireless transmitter;
• The Daviteq LoRaWAN Latching Relay Output
What are the primary output values?
• RELAY CONTROL COMMAND: Relay control command. This parameter equals RELAY_CONTROL_COMMAND in the uplink payload
• SCHEDULE STATUS: Schedule implementation status (started, complete). This parameter equals SCHEDULE_STATUS in the uplink payload
• SCHEDULE CONTROL COMMAND: Schedule's control command: on relay/off relay/clear schedule queue. This parameter equals SCHEDULE_CONTROL_COMMAND in the uplink payload
• SCHEDULE START TIME: Schedule's start time for controlling ON relay/OFF relay, in format of epoch time since 1/1/2020 00:00:00 GMT+0. It represents the number of seconds that have elapsed since January 1, 2020 00:00:00 GMT+0. If SCHEDULE_START_TIME equal zero, the control command will be implemented immediately and the schedule will not be put into the device memory queue. This parameter equals SCHEDULE_START_TIME in the uplink payload
• SCHEDULE DURATION: Schedule's duration for controlling ON relay/OFF relay command, unit of second. If the duration equal zero, the command will be implemented until next control command. This parameter equals SCHEDULE_DURATION in the uplink payload
• SCHEDULE ORDINAL NUMBER: Schedule's ordinal number in the valve's memory queue. If the SCHEDULE_START_TIME equal 0, the SCHEDULE_ORGINAL_NUMBER will be equal zero. This parameter equals SCHEDULE_ORDINAL_NUMBER in the uplink payload
• TOTAL SCHEDULE: Total available schedules in the device memory queue. This parameter equals TOTAL_SCHEDULE in the uplink payload
What are the secondary output values?
Below output values are useful for device maintenance and troubleshooting:
• Alarm: alarm status of the device. The parameter in the payload is ALERT_STATUS
• Sensor current configurations: current main settings of the sensor and this parameter in the payload is CURRENT_CONFIGURATION
• Sensor hardware version: hardware version of the sensor and this parameter in the payload is HW_VERSION
• Sensor firmware version: firmware version of the sensor and this parameter in the payload is FW_VERSION
• POWER LEVEL: Power supply level (battery or external power), unit of %. This parameter equals POWER_LEVEL in the uplink payload
• POWER SOURCE: Power source (battery or external power). This parameter equals POWER_SOURCE in the uplink payload
• RELAY TYPE: Relay type. This parameter equals RELAY_TYPE in the uplink payload
• START ADDRESS: The start address of the configuration to check. This parameter equals START_ADDRESS in the uplink payload
• NUM OF REGISTER: Number of register of the configuration to check. This parameter equals NUM_OF_REGISTER in the uplink payload
• CONTENT OF REGISTER: Content of configuration, in hexadecimal format. This parameter equals CONTENT_OF_REGISTER in the uplink payload
Principle of operation
Device power on / power reset operation
When the relay output node is power on or power reset, the VALVE CONTROL COMMAND will equal DEFAULT_COMMAND. DEFAULT_COMMAND might have one of following values:
1: Command to ON relay
2: Command to OFF relay (default value)
3: Last control command.
If the last control command is different from DEFAULT_COMMAND, the DEFAULT_COMMAND control command will be implemented and ALARM uplink message will be sent to Network Server after the control command implementation is completed. The result of control is ALERT_STATUS and might be one of following:
1: Command to control ON relay
2: Command to control OFF relay
Scheduled control
Principle of scheduled control
The scheduled control that is configured in real time, allowing for up to 15 control commands to be stored in the node's memory.
The necessary steps involve synchronizing the real-time clock for the node and setting up control schedules. Configuring the real-time clock for the node is set through Downlink type 5, and scheduled control commands for the node are set through Downlink type 2. These control commands will be stored in the valve’s memory and executed when the start time of a command matches the real-time.
Configure the Real-Time Clock
The device has its own real-time clock. The real-time clock only runs when the device is powered. The value of the real-time clock increases by 1 every second. The device schedule in device queue operate based on device real-time clock. When start time of the schedule in the queue equals to the value of device's real-time clock, the schedule's command will be implemented. When the node receives a valid control schedule, the current real-time clock value will be stored in EEPROM. When the device is powered up, the device read the stored time clock value in the EEPROM, assign this value to real-time clock and the real-time clock start to run ( increase by 1 every second).
When device receives downlink to write the value to SYNC_E_TIME parameter/configuration/setting on the memory device, the device will write the time value in the downlink to the SYNC_E_TIME parameter as well as write this value to the device's real-time clock. The downlink for SYNC_E_TIME should be sent after the device is power up OR/AND before the schedule's downlink is sent. SYNC_E_TIME value remains in the memory when the node is disconnected from the power supply.
Use downlink type 5 to set the real-time clock on the relay output node. This step is crucial for ensuring that the node operates according to the correct time. The Real-time clock is Synchronized time from network server, in format of Epoch time since 1/1/2020.
The synchronized time is equal difference in seconds between current time and original point (00:00:00 01/01/2020)
Example: the current time is 12:00:00 29-04-2024 so the synchronized time is 136555200 (Decimal) = 0823AAC0 (Hex)
Free online tool to calculate the difference between two dates:
https://www.epochconverter.com/date-difference
Use downlink type 5 to write synchronized time to parameter SYNC_E_TIME of valve.
Here is the format of downlink type 5:
Example: the current time is 12:00:00 29-04-2024 so the synchronized time is 136555200 (Decimal) = 0823AAC0 (Hex)
The final downlink payload of example is 63040823AAC00005
Note:
• The real-time clock may run inaccurately when the node loses power. Therefore, we recommend periodically synchronizing the real-time clock, ideally before scheduling control commands for the node.
• According to the principles of LoRaWAN network for class A, the node will receive a downlink message after it sends an uplink message. Therefore, it’s necessary to determine the timing of when the node sends an uplink message in order to calculate the synchronized time accurately. For example, if you intend to send a downlink to synchronize the time at 9:30, but according to the cycle, the valve only sends an uplink at 10:00, then you must use the synchronized time at 10:00 to calculate synchronized time in downlink. However, when the node is configured to operate in C class, the node will receive the downlink right-after the downlink is sent out the network server.
Set Up Control Commands
Use downlink type 2 to send control commands to the node. These commands include the specific parameters you want the node to perform. Here is the format of Downlink type 2
SCHEDULE_START_TIME (0-4294967296):
Schedule's start time for SCHEDULE_CONTROL_COMMAND, in format of epoch time since 1/1/2020 00:00:00 GMT+0. It represents the number of seconds that have elapsed since January 1, 2020 00:00:00 GMT+0. If SCHEDULE_START_TIME equal zero, the control command will be implemented immediately and the schedule will not be put into the sensor memory queue. The synchronized time in downlink from the network server must be also in the same format as one of SCHEDULE_START_TIME.
- SCHEDULE_DURATION (0-65536):
Schedule's duration for relay to control on/off command, unit of second. If the duration equal zero, the command will be implemented until next control command.
- Reserved: Reserved for future usage
- SCHEDULE_CONTROL_COMMAND (1: Control ON relay ; 2: Control OFF relay; 3: clear all schedule in queue): Schedule's control command: control ON relay/control OFF relay/clear schedule queue.
Example 1:
Create a schedule control command to control ON relay at 11:30:00 on April 29, 2024, then control OFF relay after 60 minutes.
SCHEDULE_START_TIME = 136553400 (DEC) = 0823A3B8
SCHEDULE_DURATION = 3600(DEC)= 0E10 (HEX)
Reserved: 00 (HEX)
SCHEDULE_CONTROL_COMMAND = 1
DOWNLINK_TYPE = 2
FINAL DOWNLINK : 0823A3B80E100012
Example 2:
Create a schedule control command to control ON relay immediately upon receiving the downlink, then control OFF relay after 30 minutes.
SCHEDULE_START_TIME = 00000000 (DEC) = 00000000 (HEX)
SCHEDULE_DURATION = 1800(DEC)= 0708 (HEX)
Reserved: 00 (HEX)
SCHEDULE_CONTROL_COMMAND = 1
DOWNLINK_TYPE = 2
FINAL DOWNLINK : 0000000007080012
Example 3:
Create a control command to control ON relay at 13:00:00 on April 29, 2024, then keep it ON until the next control command.
SCHEDULE_START_TIME = 136558800 (DEC) = 0823B8D0 (HEX)
SCHEDULE_DURATION = 0000(DEC)= 0000 (HEX)
Reserved: 00 (HEX)
SCHEDULE_CONTROL_COMMAND = 1
DOWNLINK_TYPE = 2
FINAL DOWNLINK : 0823B8D000000012
Example 4:
Create a downlink to clear all schedule commands in valve’s memory
SCHEDULE_START_TIME = 00000000 (DEC) = 00000000 (HEX)
SCHEDULE_DURATION = 0000(DEC)= 0000 (HEX)
Reserved: 00 (HEX)
SCHEDULE_CONTROL_COMMAND = 3
DOWNLINK_TYPE = 2
FINAL DOWNLINK : 0000000000000032
Example 5:
Create a control command to ON the relay immediately upon receiving the downlink, then keep it ON until the next control command.
SCHEDULE_START_TIME = 00000000 (DEC) = 00000000 (HEX)
SCHEDULE_DURATION = 0000(DEC)= 0000 (HEX)
Reserved: 00 (HEX)
SCHEDULE_CONTROL_COMMAND = 1
DOWNLINK_TYPE = 2
FINAL DOWNLINK : 0000000000000012
Example 6:
Create a control command to OFF the relay immediately upon receiving the downlink, then keep it OFF until the next control command.
SCHEDULE_START_TIME = 00000000 (DEC) = 00000000 (HEX)
SCHEDULE_DURATION = 0000(DEC)= 0000 (HEX)
Reserved: 00 (HEX)
SCHEDULE_CONTROL_COMMAND = 2
DOWNLINK_TYPE = 2
FINAL DOWNLINK : 0000000000000022
Note:
• The schedule control commands will be stored in the memory of the device and executed in chronological order base on the SCHEDULE_START_TIME.
• The maximum number of schedule control commands is 15. If the number of commands exceeds 15, the device will automatically delete the earliest commands and overwrite them with new ones.
• Two schedules are defined as duplicate if their start times are the same. When a schedule duplicate with another schedule in memory, the latter schedule will overwrite the former one
Note:
The downlink process need strong LoRaWAN signals than uplink process
Fallback control
Principle of Fall-back control
With this function, the relay could be limited by the maximum relay ON time or the maximum relay OFF time of the device. Here are two parameters that can be set for this function:
• FALLBACK_ON_PERIOD
Maximum allowable period for controlling ON relay, unit of second. If the controlling ON relay period is greater than FALLBACK_ON_PERIOD, the relay will be control OFF automatically and the alarm event will occur. If FALLBACK_ON_PERIOD =0, no fallback function for controlling ON relay is available
• FALLBACK_OFF_PERIOD
Maximum allowable period for controlling OFF relay, unit of second. If the controlling OFF relay period is greater than FALLBACK_OFF_PERIOD, the relay will be controlled ON automatically and the alarm event will occur.
If FALLBACK_OFF_PERIOD =0, no fallback function for controlling OFF relay is available
Use downlink type 5 to set FALLBACK_ON_PERIOD or FALLBACK_OFF_PERIOD.
Here is an example of downlink for Fallback function.
FALLBACK_ON_PERIOD = 7200s (DEC) = 00001C20 (HEX)
FALLBACK_OFF_PERIOD = 3600s (DEC) = 00000E10 (HEX)
LED indication
There is only a LED on the housing to show both sent uplinks and relay statuses.
The color of the LED is based on uplink type. Refer the PAYLOAD AND MEMORY MAP DOCUMENT for LED color of each uplink type. In addition, this LED also blinks white color for ON relay status and purple color for OFF relay status of relay control
Configuration for LATCHING RELAY
For LATCHING RELAY type with primary battery, the configurations must be:
CONTROL_TYPE = 1: Relay control type of latching Relay
POWER_CONFIG = 1: Configuration for device power supply of only primary battery
class mode = 0: End-Device Class of class A
Principle of Operation of Sensor part (if available)
A latching relay works as below:
Activation: When a control signal (usually a pulse) is applied to the relay coil, it energizes the coil and changes the state of the relay contacts (from open to closed or vice versa). This state is maintained even after the control signal is removed.
Latched State: The relay remains in this state without requiring continuous power, making it energy efficient. It stays latched until another control signal is applied to change its state again.
Deactivation: To reset the relay, a second control signal is applied to a different coil which changes the state of the contacts back to their original position.
Latching relays are commonly used in applications where it is necessary to maintain the last state after a power failure.
Default Configuration Parameters of Sensor part (if available)
This LRO has the default configuration, however, those parameters can be changed. The user can change the configuration on the wireless transmitter so that the complete node (converter + wireless) delivers the proper output value. Please check the Payload document for more information.
3.2 Configuration
How to configure the device?
Sensor configuration can be configured in 02 methods:
Method 1: Configuring via Downlink messages, port 1 (default).
Method 2: Configuring via Offline cable.
Step to access configuration port: Open housing by turning counter-clockwise 2 screws, then remove the anti-interference shield, the configuration port as below figure:
Note: The sensor is only active for offline configuration in the first 60 since power up
Which Parameters are configured?
Please check Part G in Section 1.9 Payload Documents above.
Method 1: Configuration via Downlink messages
Please check the Part D & E in Section 1.9 Payload Documents above.
Method 2: Configuration by Offline Cable
Please download the Configuration Template File of this sensor to be used in Step 4 below.
Instructions for offline configuration of the Daviteq LoRaWAN sensors. Please follow the following steps.
Note: The sensor is only active for offline configuration in the first 60 since power up by battery or plugging the configuration cable.
1. Prepare equipment and tools
The following items must be prepared for configuration.
A PC using the Windows OS (Windows 7 or above versions). The PC installed the COM port driver of the Modbus configuration cable (if needed). The driver is at link: Modbus Configuration Cable COM port driver for PC and the instruction to install the driver at link: How to install the driver.
A Modbus configuration cable
Tools to open the plastic housing of LoRaWAN sensors (L hex key or screwdriver)
2. Download and launch Daviteq Modbus configuration software
Click the link below to download Daviteq Modbus configuration software:
https://filerun.daviteq.com/wl/?id=yDOjE5d6kqFlGNVVlMdFg19Aad6aw0Hs
After downloading the software, unzip the file named: Daviteq Modbus Configuration.zip and then copy the extracted folder to the storage drive for long-term use.
Open the folder, double click on the file Daviteq Modbus Configuration Tool Version.exe to launch the software and the software interface as below:
Note: The software only runs on Microsoft Windows OS (Windows 7 and above).
3. Connect the cable and configure the sensor
Step 1:
Connect the PC to the sensor using the configuration cable.
- Use the configuration cable (Item code: TTL-LRW-USB-01).
- Connect the USB-A plug into the USB-A socket of the PC.
Step 2:
On the configuration software, choose the relevant Port (the USB port which is the cable plugged in) and set the BaudRate: 9600, Parity: none
Step 3:
Click Connect button to connect the software to the sensor. After successful connection, the Connected status will show on the software.
Step 4:
Import the configuration template file of the sensor (as above link) to the software: click menu File/ Import New and then browse the relevant sensor template file (csv file) and click Open to import the template file.
Note: The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor.
Each sensor type has its own template file. Refer to the sensor's manual to download the correct file.
Step 5:
Open the housing of the sensor and quickly plug the connector of the configuration cable into sensor's modbus configuration port as below figure. After plugging the connector, the software will read the parameter values automatically.
Plug the cable connector into sensor's modbus configuration port. This port is located at a different location, depends on the sensor type
Note: If the sensor has SKU of WSLRWEX-PPS and hardware version 1 & 2, the sensor must be powered by batteries for configuration
Step 6:
Read the current value of the parameter with Modbus Function 3
At the relevant row of the parameter, check box 3 on column Func to read the value of the parameter. The read value is shown in VALUE ON MEMMAP column.
The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. After 60 seconds, the TIME_OUT text will show on EXCEPTION column of the software.
Step 7:
Write the new setting to the parameter with Modbus Function 16
Double click on the column VALUE TO WRITE of the parameter and input the new setting value of the parameter;
Uncheck the tick on the FC column of the parameter, click on the arrow, select 16 and then check on the FC column to write a new setting to the parameter. The WRITE_OK text will show on EXCEPTION column if the software successfully writes the setting.
Repeat Step 6 to read the setting of the parameter for double-checking.
Note: For some critical parameters of the sensor, the password in "password for setting" must be written before writing the new settings to these parameters.
Only read/ write registers are allowed to write.
The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. After 60 seconds, the TIME_OUT text will show on EXCEPTION column of the software.
4. Troubleshooting
3.3 Calibration/ Validation
How to force sensor to send data for calibration/ validation (if available)
Using the magnet key, the device can be triggered to send data to the gateway immediately.
Note:
Upon transmitting the data to the gateway using the magnetic key, the timer for the transmission time interval will be reset.
The minimum time interval between two manual triggers is 15 seconds. If the interval is less than 15 seconds, data transmission will not occur.
Calibration/ Validation sensor (if available)
Calibrating a latching relay involves several steps to ensure it operates correctly and reliably. Here's a general guide:
Initial Inspection: Check the relay for any physical damage or wear. Ensure all connections are secure.
Setup: Connect the relay to a testing circuit. This typically includes a power supply, control signals, and measurement instruments like a multimeter or oscilloscope.
Apply Control Signals: Send the appropriate control pulses to the relay to switch its state. Verify that the relay latches and unlatches correctly with each pulse.
Measure Contact Resistance: Measure the resistance across the relay contacts in both latched and unlatched states. Ensure the resistance is within the specified range for your relay.
Check Coil Resistance: Measure the resistance of the relay coil to ensure it matches the manufacturer's specifications.
Functional Testing: Perform a series of functional tests to ensure the relay operates correctly under
different conditions. This may include varying the input voltage and checking the relay's response time.
Document Results: Record all measurements and observations. Compare them with the manufacturer's specifications to ensure the relay is calibrated correctly.
4
PRODUCT SPECIFICATIONS
4.1 Specifications
| Number of relay channel | 1 channel/2 channel/4 channel |
| Contact rating | Electro-mechanical relays, SPST (NO) 250 VAC@8A (resistive load) 24 VDC@5A (resistive load), 10,000,000 operations min. (at 18,000 operations/h) |
| Relay contact connection | PG9 with 90 cm length, 2x 1.0 mm2 cable, |
| Control functions | On/Off based on control schedule, powerup, fall back mode |
| COMMUNICATION | |
| SF Factors | SF7∼SF12 |
| Antenna | Internal Antenna 2 dbi |
| Power supply | 2 x AA 1.5 VDC primary battery |
| RF Frequency and Power | 860∼930MHz, 14∼20 dBm, configurable for zones: EU868, IN865, RU864, KR920, AS923, AU915, US915 |
| Protocol | LoRaWAN Class A or Class C (default) V1.0.3 |
| Data sending modes | cycle, alarm and manually triggering by magnetic key |
| Alarm function | Yes |
| Remote control via schedule downlink | Class A |
| RF Module complies to | ETSI EN 300 220, EN 303 204 (Europe) FCC CFR47 Part15 (US), ARIB STD-T108 (Japan) |
| Vietnam Type Approval | |
| Ambient working temperature | -40∼85℃ |
| Dimensions | H106xW73xD42 |
| Net-weight | 200g |
| Housing | Engineering plastic, IP65 |
| Mounting | Wall mount |
5
WARRANTY & SUPPORT
5.1 Warranty
Warranty
Below terms and conditions are applied for products manufactured and supplied by Daviteq Technologies Inc.
Free Warranty Conditions
The manufacturer undertakes to guarantee within 12 months from shipment date.
Product failed due to defects in material or workmanship.
Serial number, label, warranty stamp remains intact (not purged, detected, edited, scraped, tore, blurry, spotty, or pasted on top by certain items).
During the warranty period, if any problem of damage occurs due to technical manufacturing, please notify our Support Center for free warranty consultancy. Unauthorized treatments and modifications are not allowed.
Product failed due to the defects from the manufacturer, depending on the actual situation, Daviteq will consider replacement or repairs.
Note: One way shipping cost to the Return center shall be paid by Customers.
Paid Warranty
The warranty period has expired.
The product is not manufactured by Daviteq.
Product failed due to damage caused by disasters such as fire, flood, lightning or explosion, etc.
Product damaged during shipment.
Product damaged due to faulty installation, usage, or power supply.
Product damage caused by the customer.
Product rusted, stained by effects of the environment or due to vandalism, liquid (acids, chemicals, etc.)
Product damage is caused by unauthorized treatments and modifications.
Note: Customers will be subjected to all repairing expenses and 2-way shipping costs. If arises disagreement with the company's determining faults, both parties will have a third party inspection appraise such damage and its decision be and is the final decision.
5.2 Support
Support via Help center
If you need our support for Daviteq device's installation, configuration, test, and decode, please email us at: support@daviteq.com OR input support request at link: https://forms.office.com/r/XWHbYG7yy7
Our support engineer will contact you via email or the support ticket system.
If you have any questions about the product, you can search for information on our web (https://www.iot.daviteq.com/). If you can't find the right information, please register an account and send us a request at link Contact us | Daviteq Technologies . We will respond within 24 hours.