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-CAP10 | FW4

Normally Stock

Replaced by

Item codes	FW Released Date	Changes Information
WSLRW-CAP10-1000; WSLRW-CAP10-1500	09/01/2025	Update downlink type 5 for LoRaWAN frequency; Add downlink type 3; Update config check uplink for downlink type 3, 5; Add LNS_CHECK, password, PRODUCTION_FREQ_FACTOR _W_PASSWORD, OTHER INFOR, alarm factor, and cyclic factor; Update node hardware; Update RS485 communication

1
QUICK INSTALLATION GUIDE

1.1 Introduction

WSLRW-CAP10 is a LoRaWAN fuel level sensor that utilizes the 10-year experience of Daviteq in digital capacitance measuring technique. It delivers high accuracy and stability with 0.1% of span. Ultra-low power design and smart firmware allow the complete Wireless and Sensor package to run on 2 x AA battery 1.5V for 2-5 years with 15 minutes updates. The sensor will transmit data in kilo-meters distance to LoRaWAN gateway, any brands on the market.

Typical Applications: Monitoring fuel level and fuel consumption in fuel tanks of Genset, Boiler, Heavy equipment or machinery...

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

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

Notes

Monitoring fuel level and fuel consumption in fuel tanks of Genset, Boiler, Heavy equipment or machinery...
Fuel management for Building, Factory, Construction Site, Remote Sites, BTS Tower...
Applicable for many kinds of fluids: diesel, bio-diesel, vegetable oil, or any low viscosity non-conductive liquids
NOT be used with other flammable fluid such as Gasoline, Alcohol, Ethanol, Acetone, Toluene or other solvents.

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: 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 CAP10 sensor module 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 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)

WSLRW-CAP10-H7 LoRaWAN Precision Fuel Level Sensor.jpg

WSLRW-CAP10-H8 LoRaWAN Precision Fuel Level Sensor.jpg

WSLRW-CAP10-H7 LoRaWAN Precision Fuel Level Sensor.jpg

1/2

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)

The technicians who install sensor, must be graduated from college of mechanic or electric.
The mechanical installation staff (drill, cut, grind, etc.) must have skills in mechanical engineering.
The electrical installation staff (connect, etc.) must have skills in electrical engineering.
The technician must be trained before implementing the sensor installation.
CAP10 is intended to use with Diesel Oil, Vegetable Oil.
CAP10 must not be used with other flammable fluid such as Gasoline, Alcohol, Ethanol, Acetone, Toluene or other solvents.
Be careful while drilling, cutting, grinding, etc. The fuel tank or other flammable fluid.
Daviteq is not responsible for compensation in case of explosion to bodily injury or property damage.
Read specifications thoroughly and make sure that its output is suitable to reading devices.
Power supply must be in the permitted range.
Do not take out the label and take off the lid as this will lead to the instability of the sensor and manufacturer could deny warranty. (except cutting of sensor length within the allowed range).
Make sure all the necessary tools are ready before the installation
CAP10 be equipped with screws. We advise customers should use stainless steel rivets to fasten the plastic flange onto tank for all type of tanks and only using screws for the thick and hard ones.

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.

Mounting the Device on the Wall or Pole

Mount the sensor onto a wall by the mounting bracket with provided bracket and screws.

LoraWAN main device connected to fuel sensor via M12 connection cable.

Default Modbus RTU communication of RS485 port for CAP10CNR sensor:

Baudrate : 19200
Data bit : 8
Stop bit : 1
Parity : None
Modbus Slave address : 30

Refer the CAP10CNR installation instruction link for details of CAP10CNR installation and wirings.

The sample installation of WSLRW-CAP10 as below figure

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.

Payload Document and Configuration Table

Sample Decoder

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)

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.

2. Sensor, please refer to the maintenance section of the sensor document.

Maintenance for Sensor part (if available)

Periodically clean the oil tank 2, 3 or 6 months depending on usage and contamination.

Periodically clean the sensor and filter footer 2, 3 or 6 months by:

Cover a sensor's vent before using the air sprayer for another.
Remove and clean the filter footer.

3
ADVANCED GUIDE

3.1 Principle of Operation

Principle of Operation for device WSLRW-CAP10 | FW4

Daviteq LoraWAN Fuel Level (CAP10) Sensor comprises 02 parts linked internally:

• The Daviteq LoraWAN wireless transmitter;

• The Daviteq Fuel Level (CAP10) module

What are the primary output values?

• RAW VALUE: Raw value of CAP10-RS485. This parameter equals RAW_VALUE in the uplink payload.

• SCALED VALUE: Scaled value of CAP10-RS485, fuel level, unit of mm. This parameter equals SCALED_VALUE in the uplink payload.

What are the secondary output values?

Below output values are useful for device maintenance and troubleshooting.

• Battery level (%): the remaining capacity of the battery. The parameter in the payload is BATTERY_LEVEL.

• Number of consecutive Alarm: The number of consecutive alarm message. This parameter in the payload is TENTATIVE. TENTATIVE will be reset to 0 when previous message is alarm and current message is cyclic.

• Alarm: alarm status of the device. The parameter in the payload is ALERT_STATUS

• Sensor error: sensor working properly or not and this parameter in the payload is SENSOR_ERROR

• 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

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

Main parameter for alarm is SCALED VALUE

If parameter ALARM_ENABLE = 1

Then the device will compare the main parameter with the Low Alarm Setpoint, High Alarm Setpoint and Hysteresis. For this device, Hysteresis equal zero.

After comparison, the devices will have 03 statuses:

No_Alarm;
Low_Alarm
High_Alam.

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 Low_Alarm or Hi_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 (Low_Alarm or High_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...

Principle of Operation of Sensor part (if available)

CAP10 is a capacitive level sensor which based on the principle of capacitance sensing. The capacitor is formed by two metal pipes of the sensor and the fuel between the two pipes. When the height of the fuel level change, the capacitance value will be change. The sensor transmitter will convert the change of the capacitance to the change of electric signal

Default Configuration Parameters of Sensor part (if available)

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.

Download CSV File

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.

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)

The Daviteq CAP10 fuel level has been pre-calibrated in the factory.

If the aluminum round pipes of the sensor must be cut to suitable to the height of the tank, the calibration steps as below:

Put the sensor in the ambient air and record the raw value of the sensor (x0). The sensor pipes must be clean to get correct raw value
Put the sensor fully into the fuel (The aluminum round pipe of the sensor are in fuel) and record the raw value of the sensor (x1). The length of aluminum round pipe is L (unit of mm)
Calculate coefficient a, b from the equations:

0 = a * x0 + b

L= a * x1 + b

Write CONSTANT_A = a, and CONSTANT_B =b via offline tool or online downlink

4
PRODUCT SPECIFICATIONS

4.1 Specifications

SENSOR PROBE
Measurement fluids	Diesel (Standard), please contact us for Bio-Diesel, Vegetable Oil, or Non-conductive and low-viscosity fluid etc.
Measurement Range (mm)	Standard Range: 1000, 1500, can be extended up to 3000
Accuracy/ Resolution/ Repeatability	±0.1% of span/ 0.1%/ ±0.1% of span
Thermal drift	< +0.03% of span per 10℃
Connector	M12 male, 4-pin, Coding A
Sensor MTBF	More than 10 years
Sensor wetted materials	Aluminum and engineering plastic
Operating Temperature & Humidity Range	-20∼85℃, 0∼100% RH
Sensor rating	IP67, outdoor
Certification	CE-Marking per EN61236-1 (with test report)
Standard accessories	Filter footer, flange, gasket, o-ring, self-tapping screws
COMMUNICATION
SF Factors	SF7∼SF12
Antenna	Internal Antenna 2.0 dbi
Battery	02 x AA size 1.5VDC, battery not included
RF Frequency and Power	860∼930MHz, 14∼20 dBm, configurable for zones: EU868, IN865, RU864, KR920, AS923, AU915, US915
Protocol	LoRaWAN, class A
Data sending modes	Interval time and when alarm occurred
RF Module complies to	ETSI EN 300 220, EN 303 204 (Europe) FCC CFR47 Part15 (US), ARIB STD-T108 (Japan)
Working temperature	-40∼60℃ (using Energizer® Lithium Ultimate AA battery)
Dimensions and Net-weight	H140xW73xD42, 250g (LoRaWAN Device only)
Housing	Polycarbonate and Aluminum (wall mount bracket included), IP67
Sensor cable	2m sensor cable with M12-male connector

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.