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
Replaced by
WSLRW-IEC485 | FW1
Manual for WSLRW-IEC485 | FW1
Replaced by
Item codes | FW Released Date | Changes Information |
|---|---|---|
WSLRW-IEC485-01 | 10/09/2025 | Initial firmware for slave device of Mode C |
1
QUICK INSTALLATION GUIDE
1.1 Introduction
WSLRW-IEC485 is a LoRaWAN node with a RS485 master port to connect to water meter, power meter, gas meter, or flow computer with an RS485 slave port. The device supports IEC 62056-21 protocol. The device is configurable via offline software and downlink messages. It is powered by external power supply. The sensor will transmit data over kilometers to the LoRaWAN gateway, any brand on the market. It supports all LoRaWAN frequency bands.
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
Electric Meter Reading, Gas Meter Reading, Water Meter Reading
Notes
Compatibility: Match voltage levels and protocols
Isolation: Opt for galvanic isolation to protect devices from electrical surges.
Baud Rate: Ensure it supports the required communication speed.
Connector Type: Choose suitable connectors.
Power Supply: Select external grid power or battery power
Distance & Devices: Verify distance limit and maximum connected device
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, 10 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: 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 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.
Case 5: 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 6: 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 7: If the application/network server sends downlink 3 to check current value of a configuration parameter or sends 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.
1.4 Default Configuration
This IEC485 converter 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:
NOTE: If the settings in above table are changed via downlink, the device MUST be reset to make the changed settings take effect. The reset is hard reset (Turn OFF external power supply, wait 3-7 minutes, and then turn ON external power supply OR take out battery, wait 3-7 minutes and then insert battery back ) OR soft reset via downlink 0.
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)
Installation notes for RS485 communication under the IEC 62056-21 standard:
General Setup
Connection Ports: Ensure that the RS485 ports on both the master device and the meter are properly connected. Use shielded twisted-pair cables to minimize electrical noise.
Baud Rates: Configure the baud rate settings on both devices to match. Common baud rates include 300, 600, 1200, 2400, 4800, 9600, and 19200 bits per second.
Protocol Modes: Select the appropriate communication mode (A to E) based on your application needs. Modes A to D use ASCII, while mode E uses HDLC.
Wiring and Connections
Differential Signaling: RS485 uses differential signaling, so ensure that the A and B lines are correctly connected. The A line should be connected to the positive terminal, and the B line to the negative terminal.
Termination Resistors: Install termination resistors (typically 120 ohms) at both ends of the RS485 bus to prevent signal reflections.
Grounding: Proper grounding is essential to avoid communication issues. Connect the ground of the RS485 network to a common ground point.
Device Configuration
Addressing: Assign unique addresses to each device on the RS485 network to avoid conflicts.
Wake-Up Sequence: For battery-powered meters, send a wake-up sequence before initiating communication. This typically involves sending a string of zero characters followed by a pause.
Data Readout and Programming: Use the specified modes for reading data from the meter and programming meter settings. Ensure that the master device is configured to handle these operations correctly.
Testing and Troubleshooting
Communication Test: Perform a communication test to verify that data is being transmitted and received correctly. Check for any errors or interruptions in the data flow.
Error Handling: Implement error handling routines to manage communication failures or data corruption.
Monitoring: Continuously monitor the RS485 network for any signs of issues, such as unexpected noise or signal loss.
Safety and Compliance
Compliance: Ensure that all installations comply with relevant safety standards and regulations.
Documentation: Keep detailed records of the installation process, including wiring diagrams, configuration settings, and test results.
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 Node and the gateway. In real life, there may be no LOS condition. However, the LoRaWAN Node still communicates with the gateway, but the distance will be reduced significantly.
DO NOT install the wireless Node or its antenna inside a completed metallic box or housing because the RF signal can not pass through the metallic wall. The housing is made from Non-metallic materials like plastic, glass, wood, leather, concrete, and cement…is acceptable.
Mounting the Device on the Wall or Pole
Mount the Node onto a wall by 2 provided screws.
Run the cable from LoRaWAN device to external meter and connect RS485 wires. The cable has 2 wire: A label and B label. A wire is to connect to RS485+ signal of the meter and B wire is to connect to RS485- signal of the meter.
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)
Troubleshooting tips for RS485 communication under the IEC 62056-21 standard:
Common Issues and Solutions
1. No Data Received:
- Check Connections: Ensure all RS485 connections are secure and correctly wired. Verify that the A and B lines are properly connected.
- Baud Rate Mismatch: Confirm that the baud rate settings on both the master device and the meter match. Mismatched baud rates can prevent successful communication.
- Termination Resistors: Ensure termination resistors are installed at both ends of the RS485 bus to prevent signal reflections.
2. Data Corruption:
- Noise Interference: Use shielded twisted-pair cables to minimize electrical noise. Ensure proper grounding of the RS485 network.
- Differential Signaling: Verify that the differential signaling is functioning correctly. Check for any issues with the A and B lines.
3. Communication Failures:
- Address Conflicts: Ensure each device on the RS485 network has a unique address to avoid conflicts.
- Wake-Up Sequence: For battery-powered meters, send a wake-up sequence before initiating communication. This typically involves sending a string of zero characters followed by a pause.
4. Intermittent Connectivity:
- Cable Length: RS485 supports communication over long distances, but ensure the cable length does not exceed the maximum limit (typically 1200 meters).
- Environmental Factors: Check for environmental factors that might affect communication, such as extreme temperatures or electromagnetic interference.
Testing and Monitoring
1. Communication Test:
- Perform a communication test to verify data transmission and reception. Use diagnostic tools to check for errors or interruptions in the data flow.
2. Error Handling:
- Implement error handling routines to manage communication failures or data corruption. Ensure the system can recover from errors gracefully.
3. Continuous Monitoring:
- Continuously monitor the RS485 network for any signs of issues. Use monitoring software to track data flow and detect anomalies.
Additional Tips
1. Firmware Updates:
- Ensure that the firmware on both the master device and the meter is up to date. Firmware updates can resolve compatibility issues and improve communication stability.
2. Documentation:
- Keep detailed records of the installation and troubleshooting process. Document wiring diagrams, configuration settings, and test results for future reference.
2.2 Maintenance
Maintenance for Main device
There is no requirement for maintenance of the Hardware of LoRaWAN Device except:
1. The battery needs to be replaced. Please check the battery status via uplink messages;
Note: When the battery indicator shows only one bar (or 10% remaining capacity), please arrange to replace the battery with a new one as soon as possible. If not, the battery will drain completely, and the resulting chemical leakage can cause severe problems with the electronic circuit board.
Maintenance for Sensor part (if available)
Important troubleshooting tips for an IEC485 converter:
Check Wiring and Connections:
Ensure all connections are secure and that A+ and B- communication cables are correctly connected throughout the network.
Verify Termination Resistors:
Confirm that termination resistors (typically 120 ohms) are installed at both ends of the RS485 bus to prevent signal reflections.
Inspect Grounding:
Proper grounding is essential to avoid ground loops and reduce noise. Check that the network is properly grounded.
Check Communication Parameters:
Verify that all devices on the network are configured with the same baud rate, parity, stop bits, and data bits.
Monitor for Noise and Interference:
Use twisted pair cables to minimize electromagnetic interference (EMI). Check for sources of electrical noise that could affect communication.
Test with Known Good Devices:
Replace the RS485 transmitter with a known good device to determine if the issue is with the transmitter or another part of the network.
Check for Biasing Resistors:
Ensure that biasing resistors are correctly installed if required by your network configuration.
Review Device Configuration:
Confirm that each device has a unique address and that there are no address conflicts on the network.
3
ADVANCED GUIDE
3.1 Principle of Operation
Principle of Operation for device WSLRW-IEC485 | FW1
Device components
Daviteq LoRaWAN RS485 IEC 62056-21 Meter Reader comprises 02 parts linked internally:
• The Daviteq LoraWAN wireless transmitter
• The Daviteq LoRaWAN RS485 IEC converter
What are the primary output values?
• FORCE DATAGRAM ID: Identification code of FORCE_DATAGRAM_CONTENT. This parameter equals FORCE_DATAGRAM_ID in the uplink payload
• FORCE DATAGRAM CONTENT: Detail of datagram with FORCE_DATAGRAM_ID. Refer section C.2 DETAILS OF DATAGRAM for details. This parameter equals FORCE_DATAGRAM_CONTENT in the uplink payload
• CYCLE DATAGRAM ID: Identification code of CYCLE_DATAGRAM_CONTENT. This parameter equals CYCLE_DATAGRAM_ID in the uplink payload
• CYCLE DATAGRAM CONTENT: Detail of datagram with CYCLE_DATAGRAM_ID. Refer section C.2 DETAILS OF DATAGRAM for details. This parameter equals CYCLE_DATAGRAM_CONTENT in the uplink payload
• TOTAL IMP KWH: Total Positive Active Energy, unit of kWh . This parameter equals TOTAL_IMP_KWH in the uplink payload
• T1 IMP KWH: T1 Positive Active Energy, unit of kWh . This parameter equals T1_IMP_KWH in the uplink payload
• T2 IMP KWH: T2 Positive Active Energy, unit of kWh . This parameter equals T2_IMP_KWH in the uplink payload
• T3 IMP KWH: T3 Positive Active Energy, unit of kWh . This parameter equals T3_IMP_KWH in the uplink payload
• T4 IMP KWH: T4 Positive Active Energy, unit of kWh . This parameter equals T4_IMP_KWH in the uplink payload
• TOTAL EXP KWH: Total Negative Active Energy, unit of kWh . This parameter equals TOTAL_EXP_KWH in the uplink payload
• T1 EXP KWH: T1 Negative Active Energy, unit of kWh . This parameter equals T1_EXP_KWH in the uplink payload
• T2 EXP KWH: T2 Negative Active Energy, unit of kWh . This parameter equals T2_EXP_KWH in the uplink payload
• T3 EXP KWH: T3 Negative Active Energy, unit of kWh . This parameter equals T3_EXP_KWH in the uplink payload
• T4 EXP KWH: T4 Negative Active Energy, unit of kWh . This parameter equals T4_EXP_KWH in the uplink payload
• IMP IND KVARH: Positive Inductive Reactive Energy, unit of kVArh . This parameter equals IMP_IND_KVARH in the uplink payload
• IMP CAP KVARH: Positive Capacitive Reactive Energy, unit of kVArh . This parameter equals IMP_CAP_KVARH in the uplink payload
• EXP IND KVARH: Negative Inductive Reactive Energy, unit of kVArh . This parameter equals EXP_IND_KVARH in the uplink payload
• EXP CAP KVARH: Negative Capacitive Reactive Energy, unit of kVArh . This parameter equals EXP_CAP_KVARH in the uplink payload
• MAX IMP KW DEM: Maximum Positive Active Power Demand, unit of kW . This parameter equals MAX_IMP_KW_DEM in the uplink payload
• DT OF MAX IMP KW DEM: Date Time of Maximum Positive Active Power Demand. This parameter equals DT_OF_MAX_IMP_KW_DEM in the uplink payload
• MAX EXP KW DEM: Maximum Negative Active Power Demand, unit of kW . This parameter equals MAX_EXP_KW_DEM in the uplink payload
• DT OF MAX EXP KW DEM: Date Time of Maximum Negative Active Power Demand. This parameter equals DT_OF_MAX_EXP_KW_DEM in the uplink payload
• DT OF OPEN TC: Top Cover Opening Date Time. This parameter equals DT_OF_OPEN_TC in the uplink payload
• DT OF OPEN TBC: Terminal Block Cover Opening Date Time. This parameter equals DT_OF_OPEN_TBC in the uplink payload
• SOFWARE VERSION: Software Version No . This parameter equals SOFWARE_VERSION in the uplink payload
• SOFWARE CONTROL: Software Control No. This parameter equals SOFWARE_CONTROL in the uplink payload
• LM OF TOTAL IMP KWH: Previous Month Total Positive Active Energy, unit of kWh . This parameter equals LM_OF_TOTAL_IMP_KWH in the uplink payload
• LM OF T1 IMP KWH: Previous Month T1 Positive Active Energy, unit of kWh . This parameter equals LM_OF_T1_IMP_KWH in the uplink payload
• LM OF T2 IMP KWH: Previous Month T2 Positive Active Energy, unit of kWh . This parameter equals LM_OF_T2_IMP_KWH in the uplink payload
• LM OF T3 IMP KWH: Previous Month T3 Positive Active Energy, unit of kWh . This parameter equals LM_OF_T3_IMP_KWH in the uplink payload
• LM OF IMP IND KVARH: Previous Month Positive Inductive Reactive Energy, unit of kVArh . This parameter equals LM_OF_IMP_IND_KVARH in the uplink payload
• LM OF EXP CAP KVARH: Previous Month Negative Capacitive Reactive Energy, unit of kVArh . This parameter equals LM_OF_EXP_CAP_KVARH in the uplink payload
• LM OF TOTAL EXP KWH: Previous Month Total Negative Active Energy, unit of kWh . This parameter equals LM_OF_TOTAL_EXP_KWH in the uplink payload
• LM OF T1 EXP KWH: Previous Month T1 Negative Active Energy, unit of kWh . This parameter equals LM_OF_T1_EXP_KWH in the uplink payload
• LM OF T2 EXP KWH: Previous Month T2 Negative Active Energy, unit of kWh . This parameter equals LM_OF_T2_EXP_KWH in the uplink payload
• LM OF T3 EXP KWH: Previous Month T3 Negative Active Energy, unit of kWh . This parameter equals LM_OF_T3_EXP_KWH in the uplink payload
• LM OF EXP IND KVARH: Previous Month Negative Inductive Reactive Energy, unit of kVArh . This parameter equals LM_OF_EXP_IND_KVARH in the uplink payload
• LM OF IMP CAP KVARH: Previous Month Positive Capacitive Reactive Energy, unit of kVArh . This parameter equals LM_OF_IMP_CAP_KVARH in the uplink payload
• RMS V1: RMS Voltage L1, unit of V . This parameter equals RMS_V1 in the uplink payload
• RMS V2: RMS Voltage L2, unit of V . This parameter equals RMS_V2 in the uplink payload
• RMS V3: RMS Voltage L3, unit of V . This parameter equals RMS_V3 in the uplink payload
• RMS I0: RMS Current L0, unit of A . This parameter equals RMS_I0 in the uplink payload
• RMS I1: RMS Current L1, unit of A . This parameter equals RMS_I1 in the uplink payload
• RMS I2: RMS Current L2, unit of A . This parameter equals RMS_I2 in the uplink payload
• RMS I3: RMS Current L3, unit of A . This parameter equals RMS_I3 in the uplink payload
• FREQUENCY: Frequency, unit of Hz . This parameter equals FREQUENCY in the uplink payload
• PF1: Power Factor L1. This parameter equals PF1 in the uplink payload
• PF2: Power Factor L2. This parameter equals PF2 in the uplink payload
• PF3: Power Factor L3. This parameter equals PF3 in the uplink payload
• METER DATE: Meter date. This parameter equals METER_DATE in the uplink payload
• METER TIME: Meter time. This parameter equals METER_TIME in the uplink payload
• SERIAL NUMBER: Meter serial number. This parameter equals SERIAL_NUMBER in the uplink payload
• RMS I: RMS Current, unit of A. This parameter equals RMS_I in the uplink payload
• RMS U: RMS Voltage, unit of V. This parameter equals RMS_U in the uplink payload
• PF: Power Factor. This parameter equals PF in the uplink payload
• BAT REMAIN: Remaining battery, unit of %. This parameter equals BAT_REMAIN in the uplink payload
• METER STATUS: Meter status code. This parameter equals METER_STATUS in the uplink payload
• BATT STATUS: Battery Status Code. This parameter equals BATT_STATUS in the uplink payload
Note:
Parameters in uplink could be configured in FORCE_DATAGRAM_CONFIG for FORCE uplink and CYCLE_DATAGRAM_CONFIG for cyclic data uplink
Some slave meters have not all above parameters to read
What are the secondary output values?
Below output values are useful for device maintenance and troubleshooting.
• HW VERSION: Indicate HW version. This parameter equals HW_VERSION in the uplink payload
• FW VERSION: Indicate FW version. This parameter equals FW_VERSION in the uplink payload
• CURRENT CONFIGURATION: Latest received and valid downlink frame;=CURRENT_CONFIGURATION on device memory map. Detail of CURRENT_CONFIGURATION is at G. MODBUS MEMORY MAP section. This parameter equals CURRENT_CONFIGURATION in the uplink payload
• SENSOR COM ERROR: Communication error code for sensor. This parameter equals SENSOR_COM_ERROR in the uplink payload
• BATTERY LEVEL: Battery level. This parameter equals BATTERY_LEVEL in the uplink payload
• START ADDRESS: The start address of the configuration to check. This parameter equals START_ADDRESS in the uplink payload
• NUM OF REGISTER: Number of register of the configuration to check. This parameter equals NUM_OF_REGISTER in the uplink payload
• CONTENT OF REGISTER: Content of configuration, in hexadecimal format. This parameter equals CONTENT_OF_REGISTER in the uplink payload
Principle of operation
Cyclic data uplink
Most of the time, the device will be in sleep mode. When the timer reaches the CYCLIC_DATA_PERIOD (for example, 30 minutes), it will wake up the device to read data and return the result on the Node' memory map and send CYCLIC_DATA uplink to Network Server. The data package is split to multi-datagrams and each time the device send only 1 datagram. The sending interval between datagram are configured in DATAGRAM_INTERVAL. Details of the uplink is in section 1.9 Payload and memory map tables
Note:
Parameters in uplink could be configured CYCLE_DATAGRAM_CONFIG for cyclic data uplink
Force uplink
When the magnetic key touches the reed switch point on the housing, the device will wake up, read data and return the result on the Node' memory map and send FORCE uplink to Network Server. The data package is split to multi-datagrams and each time the device send only 1 datagram. The sending interval between datagram are configured in DATAGRAM_INTERVAL. Details of the uplink is in section 1.9 Payload and memory map tables
Note:
Parameters in uplink could be configured in FORCE_DATAGRAM_CONFIG for FORCE uplink.
Other uplinks
The device send the main configurations in START_UP , PARAMTERS_UPDATE and HEARTBEAT uplinks. In additions, the device send LNS_CHECK uplink to check LoRaWAN network server, and send CONFIG_CHECK uplink to check current value of device's other configurations
Principle of Operation of Sensor part (if available)
The operation principle for RS485 communication under the IEC 62056-21 standard:
Overview of IEC 62056-21 Standard
The IEC 62056-21 standard specifies a protocol for communication with utility meters, such as electricity meters. This protocol is designed to facilitate data exchange between a master device (like a computer) and a meter using various communication media, including RS485.
RS485 Communication
RS485 is a robust serial communication protocol widely used in industrial environments due to its ability to handle long-distance communication and resist electrical noise. It operates using differential signaling, which helps minimize the impact of noise on data transmission.
Key Principles
1. Communication Modes:
- Mode A to D: These modes use ASCII characters for communication, allowing straightforward data exchange.
- Mode E: This mode uses HDLC (High-Level Data Link Control) for more complex and secure data transmission.
2. Data Transmission:
- RS485 enables serial communication between the master device and the meter. It supports both half-duplex and full-duplex communication modes.
- Half-duplex: Data can be sent in one direction at a time, either from the master to the meter or vice versa.
- Full-duplex: Data can be sent and received simultaneously in both directions.
3. Baud Rates:
- The protocol specifies various baud rates to ensure compatibility with different devices. Common baud rates include 300, 600, 1200, 2400, 4800, 9600, and 19200 bits per second.
4. Data Readout and Programming:
- Data Readout Mode: This mode allows the master device to read data from the meter, such as consumption values, meter status, and other relevant information.
- Programming Mode: This mode enables the master device to configure and program the meter settings, such as tariff schedules, time synchronization, and other parameters.
Advantages of RS485:
- Long-Distance Communication: RS485 can handle communication over distances up to 1200 meters, making it ideal for large industrial setups.
- Noise Resistance: The differential signaling used in RS485 helps reduce the impact of electrical noise, ensuring reliable data transmission.
- Multi-Device Communication: RS485 supports communication with multiple devices on the same bus, allowing up to 32 devices to be connected.
Default Configuration Parameters of Sensor part (if available)
This IEC485 converter 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 hex 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 by battery or plugging the configuration cable.
Which Parameters are configured?
Please check Part G in Section 1.9 Payload Documents above.
Method 1: Configuration via Downlink messages
Please check the Part D & E in Section 1.9 Payload Documents above.
Method 2: Configuration by Offline Cable
Please download the Configuration Template File of this sensor to be used in Step 4 below.
Instructions for offline configuration of the Daviteq LoRaWAN sensors. Please follow the following steps.
Note: The sensor is only active for offline configuration in the first 60 since power up by battery or plugging the configuration cable.
1. Prepare equipment and tools
The following items must be prepared for configuration.
A PC using the Windows OS (Windows 7 or above versions). The PC installed the COM port driver of the Modbus configuration cable (if needed). The driver is at link: Modbus Configuration Cable COM port driver for PC and the instruction to install the driver at link: How to install the driver.
A Modbus configuration cable
Tools to open the plastic housing of LoRaWAN sensors (L hex key or screwdriver)
2. Download and launch Daviteq Modbus configuration software
Click the link below to download Daviteq Modbus configuration software:
https://filerun.daviteq.com/wl/?id=yDOjE5d6kqFlGNVVlMdFg19Aad6aw0Hs
After downloading the software, unzip the file named: Daviteq Modbus Configuration.zip and then copy the extracted folder to the storage drive for long-term use.
Open the folder, double click on the file Daviteq Modbus Configuration Tool Version.exe to launch the software and the software interface as below:
Note: The software only runs on Microsoft Windows OS (Windows 7 and above).
3. Connect the cable and configure the sensor
Step 1:
Connect the PC to the sensor using the configuration cable.
- Use the configuration cable (Item code: TTL-LRW-USB-01).
- Connect the USB-A plug into the USB-A socket of the PC.
Step 2:
On the configuration software, choose the relevant Port (the USB port which is the cable plugged in) and set the BaudRate: 9600, Parity: none
Step 3:
Click Connect button to connect the software to the sensor. After successful connection, the Connected status will show on the software.
Step 4:
Import the configuration template file of the sensor (as above link) to the software: click menu File/ Import New and then browse the relevant sensor template file (csv file) and click Open to import the template file.
Note: The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor.
Each sensor type has its own template file. Refer to the sensor's manual to download the correct file.
Step 5:
Open the housing of the sensor and quickly plug the connector of the configuration cable into sensor's modbus configuration port as below figure. After plugging the connector, the software will read the parameter values automatically.
Plug the cable connector into sensor's modbus configuration port. This port is located at a different location, depends on the sensor type
Note: If the sensor has SKU of WSLRWEX-PPS and hardware version 1 & 2, the sensor must be powered by batteries for configuration
Step 6:
Read the current value of the parameter with Modbus Function 3
At the relevant row of the parameter, check box 3 on column Func to read the value of the parameter. The read value is shown in VALUE ON MEMMAP column.
The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. After 60 seconds, the TIME_OUT text will show on EXCEPTION column of the software.
Step 7:
Write the new setting to the parameter with Modbus Function 16
Double click on the column VALUE TO WRITE of the parameter and input the new setting value of the parameter;
Uncheck the tick on the FC column of the parameter, click on the arrow, select 16 and then check on the FC column to write a new setting to the parameter. The WRITE_OK text will show on EXCEPTION column if the software successfully writes the setting.
Repeat Step 6 to read the setting of the parameter for double-checking.
Note: For some critical parameters of the sensor, the password in "password for setting" must be written before writing the new settings to these parameters.
Only read/ write registers are allowed to write.
The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. After 60 seconds, the TIME_OUT text will show on EXCEPTION column of the software.
4. Troubleshooting
3.3 Calibration/ Validation
How to force sensor to send data for calibration/ validation (if available)
Using the magnet key, the device can be triggered to send data to the gateway immediately.
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)
No calibration is required for IEC485 converter
4
PRODUCT SPECIFICATIONS
4.1 Specifications
Spec
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 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.