top of page

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 ​

WSSFCEX-GHC

Manual for WSLRW-DFM | FW1

Build-to-Order

Replaced by

Replaced by

Item codes
FW Released Date
Changes Information
WSLRW-DFM-100-01; WSLRW-DFM-250-01; WSLRW-DFM-500-01
09/12/2024
Initial firmware

1
QUICK INSTALLATION GUIDE

1.1 Introduction

WSLRW-DFM is an advanced devices that use LoRaWAN (Low Power Wide Area Network) technology to measure and transmit fuel flow data over long distances. These meters are particularly useful for remote monitoring and management of fuel usage in various applications, such as industrial processes, fuel distribution, and storage. The meter provides real-time monitoring and optimization of fuel consumption, normalization of fuel quotas, detection and prevention of fuel theft, and fuel consumption testing for engines/genset. LoRaWAN fuel flow meters are used in various industries like manufacturing, agriculture, transportation, and smart cities. The device will transmit data in kilo-meters distance to LoRaWAN gateway, any brands on the market.

How the sensor connect to system?

The architecture of the LoRaWAN system
The architecture of the LoRaWAN system

System components:
  1. The end nodes are LoRaWAN Sensors or Actuators;

  2. The Gateways are LoRaWAN Gateway or Base Station;

  3. The Network Server can be SAAS or On-premise server;

  4. 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:
  1. Adding the Gateways to a Network server. Please refer to the manual of Gateway and Network Server software;

  2. Adding the End nodes to the Network Server;

  3. 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.

  4. 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

Energy Monitoring, Fuel Monitoring, Process Monitoring, Smart Irrigation, Vehicle Tracking

Notes

  • Application: Identify the purpose (industrial, automotive, marine, etc.).

  • Flow Rate & Accuracy: Determine flow rate range and required accuracy.

  • Fluid Compatibility: Ensure compatibility with the fuel type.

  • Measurement Principle: Choose the appropriate type (e.g., turbine, ultrasonic).

  • Environmental Conditions: Evaluate temperature, pressure, and corrosive substances.

  • Installation: Consider space, pipe size, and orientation.

1.3 When does device send Uplink messages?

The device will send uplink messages in the following cases:

Case 1: After power-up in the 60s, the device will send the first message called START_UP. The payload will tell the user the HW version, FW version, and current configuration of the device.


Case 2: Then, in every interval time (pre-configured), for example, 30 minutes, it will send the message called CYCLIC_DATA. The payload will tell the user the following data like measured values, battery level, and alarm status...

To change the cycle of data sending, you can change the value of the parameter: CYCLIC_DATA_PERIOD.


Case 3: If ALARM_ENABLED=1, the device will send ALARM message immediately when device switches from Normal state to Alarm state. It will repeat sending ALARM messages in predefined ALARM_PERIOD time interval if the Alarm state still exist.


Case 4: During the commissioning, testing, or calibration sensor, the user can force the device to send the uplink message to get the data immediately. This message is called FORCE_DATA. The payload will provide data like raw measured value, scaled measured values, battery level, and alarm status... It can be forced by applying the magnet key on the reed switch in 1s.


Case 5: If users want to change the configuration immediately, they don't need to wait until the next cyclic data-sending message; instead, they can force the device to send a special uplink message so that the device can get the new downlink message. This uplink message is named PARAMETERS_UPDATE. It can be forced by applying the magnet key in more than 5s.


Case 6: In every interval time (pre-configured), for example, 24 hours, it will send the message called HEARTBEAT. The payload will tell the user the following data like hardware version, firmware version, current sensor configuration.


Case 7: If LNS_CHECK_MODE =1, it will send the confirmed uplink message called LNS_CHECK every 24 hours. This confirmed uplink message is a message where a LoRaWAN device is requesting a LoRaWAN network to confirm the reception of its message. If the device receives no confirmation message from LoraWAN network server, it will re-send the LNS_CHECK message every hour during 3 hours. After 4th hour, if the device still receives no confirmation message, it will reset itself to join the network server. The LNS_CHECK payload will tell the user the following data like hardware version, firmware version, current sensor configuration.


Case 8: If the application/network server sends downlink 3 to check current value of a configuration parameter or sends downlink type 4 to change value of a configuration parameter, the device will send the CONFIG-CHECK uplink. The payload of CONFIG-CHECK uplink contains the result of the configuration changes/configuration check.

1.4 Default Configuration

This Daviteq DFM meter has the default configuration, however, those parameters can be changed. The user can change the configuration on the wireless transmitter so that the complete sensor (transducer + wireless) delivers the proper output value. Please check the Payload document for more information.

1.5 Battery/ Power Supply

The Device uses the external power supply with below specification:

  • Power voltage: 10 - 48 VDC

  • Consumption: avg 41mA@12VDC max 66mA@12VDC


Wirings



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)

Visual Inspection of Fuel Flowmeter

Before installing the flowmeter, it is essential to perform a visual inspection to identify any potential defects that may have occurred during transportation, storage, or handling. Check for the following:

  • Visible damage to the case, fittings, mounting plate, display, interface cable, and/or connectors.

  • Backlash or gaps between constituent parts.


Prior to installation, it is recommended to verify the connection of the fuel flowmeter to the power supply:

  1. Supply a minimum flow of fuel or air (10-40 l/h, 0.3 bar) to the flowmeter.

  2. Check if the signal LEDs on the flowmeter case blink during fuel/air supply.

If any defects are detected, contact the supplier.


Preparation for Installation

Before installing the flowmeter, thoroughly inspect the vehicle/engine/genset to ensure that the installation is feasible.

  1. Inspect all fuel lines for damage or fuel leakage  and make sure that there is no leakage ;Otherwise, customer eliminates leakage 

  2. Check engine operation for 5-10 minutes at idle  and make sure that the engine runs evenly and does not stall and there is no air in the fuel system ;Otherwise, customer eliminates malfunctions 

  3. Check engine operation for 5-10 minutes under load or when vehicle is moving  and make sure that the engine runs evenly and does not stall ;Otherwise, customer eliminates malfunctions 

  4. Check the onboard voltage with voltmeter  and make sure that a 12-v onboard power system has operating voltage of 10-18 v and a 24-v onboard power system must have operating voltage of 18-32 v ;Otherwise, customer eliminates malfunctions 

  5. During the installation of flowmeter check the presence of gases in the return line  and make sure that no foam or air bubbles in fuel ;Otherwise, deaerator installation or elimination of malfunctions required

  6. Check the amount of excess fuel removed through the return line from injectors  and make sure that the measurement error increases with a significant amount of excess fuel, since excess fuel flows back into the tank and is re- counted by flowmeter ;Otherwise, change the connection of the return line from injectors so that the measurement is correct

  7. Check the pressure in fuel system with manometer  and make sure that hydraulic resistance of the chosen flowmeter in the nominal mode does not reduce the pressure by more than 5% ;Otherwise, compare the values of pressure in fuel system before and after flowmeter installation

  8. Check the “ground” of the vehicle/engine/genset and make sure that the resistance between connection point and clamp “-“ of a battery terminal does not exceed 1 ohm; Otherwise, customer eliminates malfunctions


  • The vehicle/engine/genset inspection protocol should be completed and signed based on the inspection results. The customer must address any malfunctions indicated in the protocol before installing the flowmeter.

  • The maximum and minimum fuel consumption values in the supply and return lines can be found in the technical specifications of the vehicle's pump or by measuring the volume of fuel flowing from the return line into a measuring container.

  • It is not recommended to install a differential flowmeter if there are air bubbles in the supply or return fuel lines. In such cases, a deaerator should be installed.


General Installation Instructions

Required Tools and Materials:

- Fuel flowmeter

- Mounting kit (to be purchased separately)

- Hand tools (sets of box wrenches, socket heads, and screwdrivers)

- Two fuel filters with attached washed hoses and clamping clamps to protect the chambers from contamination during initial installation.

- Flowmeter chamber with transparent cover (optional) to detect the presence of gases in the measured fuel


Installation Guidelines:

- The flowmeter can be mounted vertically, horizontally, or at an angle. For optimal performance, it is recommended to mount the flowmeter horizontally. If the fuel flow direction (indicated by an arrow on the flowmeter case) is not horizontal, ensure the flowmeter's outlet is positioned higher than its inlet.

- Avoid damaging the cable and fuel lines during installation.

- Secure the flowmeter to the surface at a minimum of three points.

- Do not drill the vehicle's base frame when installing the flowmeter. If securing a mounting plate with screws is not possible, use spot welding.

- Ensure the installed flowmeter is not exposed to direct water jets from a high-pressure cleaner.


Installation Rules


1. When installing a flowmeter on any equipment, attach additional plastic fuel filters (or metal ones if there is high pressure in the system) directly in front of each chamber, and perform the initial start. Additional fuel filters will help avoid the ingress of dirt, particles of rubber, cord, and metal resulting from cutting the fuel lines and tightening the threads. Additional filters can be dismantled after half an hour of system operation.


2. If the fuel system is highly contaminated:

- Perform maintenance of the vehicle and replace regular filters.

- Install additional filters if there are no regular ones.


3. When connecting the fuel lines, ensure that flanges and threaded connections are clean.


4. Use only new sealing washers from the mounting kit.


5. Protect the vehicle's fuel lines from external destructive influences.


6. Do not reduce the internal cross-sections of fuel lines at bends.


7. Fasten the fuel lines to the vehicle with ties every 0.3 meters.


8. Ensure fuel lines have a small margin in length to compensate for temperature changes.


9. Do not install the flowmeter on vehicle elements that are subject to strong vibration and heat.


10. Connect rubber fuel lines to the elements of the fuel system using pivot brackets or flow-through fittings and secure them with hose clamps or hose crimps (recommended).


11. Exclude air from the fuel system after the flowmeter is installed.


12. Seal all detachable and threaded connections of the fuel line situated in the sections “engine – flowmeter” and “flowmeter – engine,” including a standard relief valve.


Note:

  • Do not use a fuel flowmeter with a maximum flow rate lower than the actual flow rate of the equipped vehicle or diesel generator.

  • It is not recommended to use internal or external filters with petrol gauze (cell area less than 0.6 microns) in the connection diagram, as this may cause fuel system failures at subzero temperatures.



Installation of Flowmeter on Diesel Engine Using the "Differential" Diagram


The fuel circulation pattern in the system remains unchanged during differential measurement. The supply chamber of the differential flowmeter is installed in the engine's fuel supply line, while the return chamber is installed in the return fuel line. Fuel consumption is calculated as the difference between the measured flow values in the supply and return chambers.


The original fuel system is illustrated in below figures.


where 1 – fuel tank, 2 –supply line, 3 – return line, 4 – return line from injectors

where 3 – return line, 5 – LPFP, 6 – fine filter, 7 – HPFP, 8 – relief valve


Original fuel flow system as below:

  1. Fuel is drawn from tank 1 by the Low-Pressure Fuel Pump (LPFP) 5 through the supply line 2.

  2. The fuel is then pressurized and sent to the fine filter 6.

  3. The purified fuel is delivered to the High-Pressure Fuel Pump (HPFP) inlet 7.

  4. Excess fuel from the HPFP returns to tank 1 through the return line 3, regulated by a relief valve 8, which maintains the required pressure in the fuel supply system.


Installation steps

  • Step 1: Disconnect the fuel lines connected to HPFP: fuel supply from the fine fuel filter and the return line with the relief valve 8

  • Step 2: Install and connect fuel flowmeter  using provided accessories



  • Step 3: Connect the supply chamber inlet (marked as “F” on flowmeter case) to the fine filter outlet.


  • Step 4: Connect the supply chamber outlet to the HPFP inlet.

  • Step 5: Connect the HPFP outlet to the return chamber inlet (marked as “R” on flowmeter case).

  • Step 6: Connect the return chamber outlet to the return fuel line with the help of previously removed relief valve 8.


Note:

  • If the fuel system operates properly, the return line from injectors 4 does not contain a significant amount of fuel and can be ignored. However, it is recommended to check the flow rate in this line.

  • If the fuel consumption in the return line affects the measurement result by more than 2% of the engine's fuel consumption, it is recommended to connect the return line from the injectors to the HPFP inlet.


Deaerator Installation


Air bubbles may be present in the engine's return line. To detect their presence, lower the return pipeline into a transparent container. The presence of air increases fuel consumption in the return line, leading to a higher measurement error in the engine's fuel consumption as determined by the flowmeter.


If there are air bubbles in the return line, they must be removed by installing a deaerator.

Install the deaerator in front of the return measuring chamber of the flowmeter.

Connect the outlet of the engine return line to the deaerator inlet. The purified fuel will then be delivered to the flowmeter inlet.


The separated air contains a small amount of fuel, which could leave stains under the engine. To prevent diesel stains and comply with environmental requirements, it is recommended to connect the gas outlet to the return line behind the flowmeter.



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 sensor 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.


Install flow meter to engine of generator set/machine/vehicle

Connect the flow meter to supply fuel line and return fuel line of generator set/machine/vehicle


Make sure a correct supply flow and return flow


Use provided the accessories for installation

Install the Device on the Wall/Housing/Structure and connect to power supply and load

  • Mount the sensor onto a wall/housing/structure with provided batch and screws.

Connect LoRaWAN node, flow meter and power source

  • Run the provided cable from LoRaWAN node (main device) to the flow meter and then plug the cable's connectors to LoRaWAN node and to the flow meter



  • Run the provided power supply cable of LoRaWAN node to the external power supply terminals and connect 2 wires (GND and 10-48VDC label) of the device power supply cable to the terminals. Then plug M12 connector of the power cable's to the LoRaWAN node.


  • The device need external power supply from 10 to 48 VDC


  • Insert the provided fuse on the positive line between VDC power source and LoRaWAN node

Note:

Power supply for device must off during installation



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.


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.


 

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)

Here are some common issues and troubleshooting steps for fuel flow meters:


1. Obstruction or Blockages:

- Issue: Blockages in the flow path can cause inaccurate or inconsistent readings.

- Solution: Inspect and clean the flow meter and pipeline to remove any debris or obstructions.


2. Unexpected Changes in Fluid Properties:

- Issue: Changes in temperature, pressure, or viscosity can affect measurements.

- Solution: Ensure the flow meter is calibrated for the specific fluid properties and operating conditions.


3. Sensor Fouling:

- Issue: Fouling from scaling, sludge, rust, or slime can reduce sensor accuracy.

- Solution: Regularly clean and maintain the flow meter to prevent fouling.


4. Wear and Tear:

- Issue: Mechanical wear on moving parts can degrade performance over time.

- Solution: Periodically inspect and replace worn components as needed.


5. Electrical Connection Issues:

- Issue: Poor connections or grounding can lead to erratic readings.

- Solution: Verify all electrical connections are secure and the grounding resistance is within acceptable limits.


6. Calibration Errors:

- Issue: Incorrect calibration can result in inaccurate measurements.

- Solution: Regularly calibrate the flow meter according to the manufacturer's guidelines.


7. Air Bubbles in the Fuel Line:

- Issue: Air bubbles can cause measurement errors.

- Solution: Install a deaerator to remove air bubbles from the fuel line.


By addressing these common issues, you can ensure accurate and reliable performance from your fuel flow meter. If problems persist, consult the manufacturer's technical support for further assistance.

2.2 Maintenance

Maintenance for Main device

There is no requirement for maintenance of the Hardware of LoRaWAN Device except:

For fuel flow meter, please refer to the maintenance section of the flow meter document.

Maintenance for Sensor part (if available)

Proper maintenance of fuel flow meters is essential to ensure accurate and reliable performance over time. Here are some best practices for maintaining your fuel flow meter:


1. Regular Calibration:

- Calibrate the flow meter regularly to maintain accuracy. The frequency of calibration depends on the type of flow meter, the fluid being measured, and the application. Generally, calibration should be performed at least once a year.


2. Cleaning:

- Keep the flow meter clean to prevent dirt and debris from affecting its accuracy. Regularly inspect and clean the meter to ensure it remains free of contaminants.


3. Inspection for Wear and Tear:

- Periodically inspect the flow meter for signs of wear and tear, especially on moving parts. Replace any worn components to maintain optimal performance.


4. Check for Obstructions:

- Ensure there are no blockages or obstructions in the flow path. Clean the flow meter and pipeline as needed to remove any debris.


5. Verify Electrical Connections:

- Check all electrical connections to ensure they are secure and free from corrosion. Proper grounding is crucial, especially for electromagnetic flow meters.


6. Monitor Fluid Properties:

- Be aware of changes in fluid properties such as temperature, pressure, and viscosity, as these can affect the flow meter's performance. Adjust calibration settings as necessary to account for these changes.


7. Troubleshooting:

- If the flow meter is not functioning properly, troubleshoot the issue immediately. Common problems include sensor fouling, air bubbles in the fuel line, and electrical connection issues.


8. Record Keeping:

- Maintain accurate records of all maintenance and calibration activities. This helps in tracking the performance of the flow meter and planning future maintenance.

3
ADVANCED GUIDE

3.1 Principle of Operation

Principle of Operation for device WSLRW-DFM | FW1

Daviteq LoRaWAN Diesel Flow Meter (DFM) comprises 02 parts linked internally:

• The Daviteq LoraWAN wireless transmitter;

• The Daviteq LoRaWAN Diesel Flow Meter (DFM)


What are the primary output values?

• FLOW: Fluid flow rate, unit of liter/hour, used for alarm. This is difference between supply flow and return flow. This parameter equals FLOW in the uplink payload

• VOLUME: Fluid volume, unit of liter. This is accumulated consumption volume of engine/machine. This parameter equals VOLUME in the uplink payload

• SUPPLY FLOW: Fluid flow rate of supply line, unit of liter/hour. This parameter equals SUPPLY_FLOW in the uplink payload

• SUPPLY VOLUME: Fluid volume of supply line, unit of liter. This parameter equals SUPPLY_VOLUME in the uplink payload

• SUPPLY TEMPERATURE: Fluid temperature of supply line, unit of oC. This parameter equals SUPPLY_TEMPERATURE in the uplink payload

• RETURN FLOW: Fluid flow rate of return line, unit of liter/hour. This parameter equals RETURN_FLOW in the uplink payload

• RETURN VOLUME: Fluid volume of return line, unit of liter. This parameter equals RETURN_VOLUME in the uplink payload

• RETURN TEMPERATURE: Fluid temperature of return line, unit of oC. This parameter equals RETURN_TEMPERATURE in the uplink payload

• FORCE DATAGRAM ID: Identification code of FORCE_DATAGRAM_CONTENT. This parameter equals FORCE_DATAGRAM_ID in the FORCE uplink payload

• FORCE DATAGRAM CONTENT: Detail of datagram with FORCE_DATAGRAM_ID

*0:FLOW & VOLUME;

*1:SUPPLY_FLOW & SUPPLY_VOLUME;

*2:RETURN_FLOW & RETURN_VOLUME;

*3:SUPPLY_TEMPERATURE & RETURN_TEMPERATURE.

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 CYCLE uplink payload

• CYCLE DATAGRAM CONTENT: Detail of datagram with CYCLE_DATAGRAM_ID

*0:FLOW & VOLUME;

*1:SUPPLY_FLOW & SUPPLY_VOLUME;

*2:RETURN_FLOW & RETURN_VOLUME;

*3:SUPPLY_TEMPERATURE & RETURN_TEMPERATURE.

This parameter equals CYCLE_DATAGRAM_CONTENT in the uplink payload

• ALARM DATAGRAM ID: Identification code of ALARM_DATAGRAM_CONTENT. This parameter equals ALARM_DATAGRAM_ID in the ALARM uplink payload

• ALARM DATAGRAM CONTENT: Detail of datagram with ALARM_DATAGRAM_ID

*0:FLOW & TENTATIVE_FOR_FLOW;

*1:SUPPLY_FLOW & SUPPLY_VOLUME;

*2:RETURN_FLOW & RETURN_VOLUME;

*3:SUPPLY_TEMPERATURE & RETURN_TEMPERATURE;

*4:VOLUME & reserved32.

This parameter equals ALARM_DATAGRAM_CONTENT in the uplink payload


What are the secondary output values?

Below output values are useful for device maintenance and troubleshooting.


• HW VERSION: Hardware version. This parameter equals HW_VERSION in the uplink payload

• FW VERSION: Firmware 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

• ALERT STATUS: Alert status. This parameter equals ALERT_STATUS in the uplink payload

• BATTERY LEVEL: Battery level. This parameter equals BATTERY_LEVEL in the uplink payload

• POWER SOURCE: Power source (battery or solar panel/external power). This parameter equals POWER_SOURCE in the uplink payload

• TENTATIVE FOR FLOW: Tentative number is the number of continuous alarm cycles.. This parameter equals TENTATIVE_FOR_FLOW in the uplink payload

• START ADDRESS: The start address of the configuration to check. This parameter equals START_ADDRESS in the uplink payload

• NUM OF REGISTER: Number of register of the configuration to check. This parameter equals NUM_OF_REGISTER in the uplink payload

• CONTENT OF REGISTER: Content of configuration, in hexadecimal format. This parameter equals CONTENT_OF_REGISTER in the uplink payload


Principle of operation

Most of the time, the device will be in sleep mode. When the timer reaches the Measure_Period (for example, 30 minutes), it will wake up the device to start the measurement.

*** This Measure_Period will affect the energy consumption of the device.

The measurement will take a certain time to finish; it can take milliseconds or seconds to finish the measurement. This measurement time depends on sensor type, required accuracy, and other factors. Shorter measurement time, lower energy consumption, and longer battery life.

After finishing the measurement cycle, the device can read all the measured parameters.

The main parameter is FLOW

If parameter ALARM_ENABLE = 1

Then the device will compare the main parameter with High High Alarm Setpoint and High Alarm Setpoint, together with Hysteresis to define the state of the device is No_Alarm or Hi_Alarm or HiHi_Alarm.


Hysteresis value is to avoid the flickering status (Alarm/No-Alarm toggling quickly) when the measured value close to alarm threshold. Hysteresis is zero for this sensor.


  • If an axis is in Blue color area of above graph, the device is in Normal or No_Alarm state;

  • If an axis is in Red color area, the device is in HiHi Alarm state (Alarm 2);

  • None of above 02 states, the device will be in Hi Alarm state (Alarm 1).


How the device send uplink message base on above 03 states?

If Device state is No_Alarm, it will check the timer to reach the Cyclic_Data_Period to send the CYCLIC_DATA uplink message;


If Device state is changed from No_Alarm to Hi Alarm or HiHi Alarm, it will send alarm message immediately. Please check the below picture to understand the operation flow when finishing the measurement cycle:


Once alarm happened and send the first alarm message, the device will send the next alarm message in the Alarm_Period if the device is still in Alarm states (Hi Alarm or HiHi Alarm). Please check below picture to understand the operation flow when the Alarm timer reaches the Alarm_Period.


If parameter ALARM_ENABLE = 0

The device will check the timer to reach the Cyclic_Data_Period to send the CYCLIC_DATA uplink message;


Please check the Payload document to understand clearly about uplink messages, downlink messages, meaning of parameters for configuration...


Alarm configurations
  • UNSCALED_HIHI_ALARM_SETPOINT: Unscaled high alarm set point to calculate HIGHHIGH_ALARM_SETPOINT for flow rate, unit of liter/hour

  • UNSCALED_HI_ALARM_SETPOINT: Unscaled low alarm set point to calculate HIGH_ALARM_SETPOINT for flow rate, unit of liter/hour

  • HIHI_ALARM_FACTOR: High alarm factor to calculate HIGHHIGH_ALARM_SETPOINT

  • HI_ALARM_FACTOR: Low alarm factor to calculate HIGH1_ALARM_SETPOINT

  • ALARM_ENABLE: Enable/Disable ALARM event

  • ALARM_PERIOD: Period of time to send ALARM event


  • HIGHHIGH_ALARM_SETPOINT:

*If HIHI_ALARM_FACTOR <= 7, HIGHHIGH_ALARM_SETPOINT = UNSCALED_HIHI_ALARM_SETPOINT *(10^HIHI_ALARM_FACTOR)

*If HIHI_ALARM_FACTOR >=8, HIGHHIGH_ALARM_SETPOINT = UNSCALED_HIHI_ALARM_SETPOINT / (10^(16-HIHI_ALARM_FACTOR))


  • HIGHHIGH_ALARM_SETPOINT:

*If HI_ALARM_FACTOR <= 7, HIGH_ALARM_SETPOINT =

UNSCALED_HI_ALARM_SETPOINT * (10^HI_ALARM_FACTOR)

*If HI_ALARM_FACTOR >=8, HIGH1_ALARM_SETPOINT =

UNSCALED_HI_ALARM_SETPOINT / (10^(16-HI_ALARM_FACTOR))

Principle of Operation of Sensor part (if available)

The fuel volume is measured using a ring-shaped piston that moves within the measuring chamber. As liquid enters the chamber through the inlet fitting, the piston moves along the inner surface of the chamber and slides along the jumper link. This movement forces the liquid out of the chamber through the outlet fitting as below figure



Each rotation of the piston displaces a volume of liquid equal to the chamber's volume. As the piston rotates, electronic position sensors generate signals that are processed by the flowmeter's microprocessor unit. The measurement results, including a running total, are available via the external interface, stored in the flowmeter's memory, and can be displayed on the built-in screen.

Default Configuration Parameters of Sensor part (if available) 

This Daviteq DFM meter has the default configuration, however, those parameters can be changed. The user can change the configuration on the wireless transmitter so that the complete sensor (transducer + wireless) delivers the proper output value. Please check the Payload document for more information.

3.2 Configuration

How to configure the device?

Sensor configuration can be configured in 02 methods:

Method 1: Configuring via Downlink messages, port 1 (default).


Method 2: Configuring via Offline cable.

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)

Flowmeter is factory calibrated for use in the most common configurations, eliminating the need for additional calibration in most cases. Fuel flowmeters is calibrated with diesel fuel or equivalent. When measuring other liquids, recalibration of the flowmeter on site might be necessary.

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
  1. The manufacturer undertakes to guarantee within 12 months from shipment date.

  2. Product failed due to defects in material or workmanship.

  3. Serial number, label, warranty stamp remains intact (not purged, detected, edited, scraped, tore, blurry, spotty, or pasted on top by certain items).

  4. 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.

  5. 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
  1. The warranty period has expired.

  2. The product is not manufactured by Daviteq.

  3. Product failed due to damage caused by disasters such as fire, flood, lightning or explosion, etc.

  4. Product damaged during shipment.

  5. Product damaged due to faulty installation, usage, or power supply.

  6. Product damage caused by the customer.

  7. Product rusted, stained by effects of the environment or due to vandalism, liquid (acids, chemicals, etc.)

  8. 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.

bottom of page