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
1
QUICK INSTALLATION GUIDE
1.1 Introduction
WSLRWAL-TC is LoRaWAN wireless transmitter for heavy duty applications, with modular design connected to thermocouple temperature sensor, based on 10-year experience in design and manufacturing Industrial sensor of Daviteq Company. It has been factory pre-calibrated for high accuracy and quick set-up. The Ultra-Low Power Power design and smart firmware allow the sensor to last up to 10 years with 01 x C 3.6V battery (depending on configuration). The sensor will transmit data over kilometers away to the LoRaWAN gateway, any brand on the market. Some typical applications are temperature monitoring for factories, agriculture, boilers,...
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
Temperature Monitoring, Process Monitoring, Safety Monitoring
Notes
When selecting a thermocouple transmitter node, consider the following criteria:
- Temperature Range: Determine the required measurement temperature range for your application.
- Chemical Resistance: Assess the compatibility and durability of the thermocouple wires with the environment where they will be exposed.
- Abrasion and Vibration Resistance: Choose a transmitter that can withstand abrasion and vibration in your specific installation.
- Installation Requirements: Consider existing equipment and available probe hole sizes to determine the appropriate probe diameter
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 (default is 10 minutes) 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.
1.4 Default Configuration
Thermocouple node has the default configuration. The user can change the configuration on the wireless transmitter so that the complete sensor (transducer + wireless) delivers the proper output value.
1.5 Battery/ Power Supply
Use 01 x C-size battery 3.6V LiSOCl2 with 7700mAh;
Recommend to use SAFT LS26500 or equivalent from Tadiran.
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)
Thermocouple Installation Guidelines
Location and Depth Selection:
Carefully choose the installation location and insertion depth where the temperature accurately represents the process conditions.
Avoid stagnant areas with non-representative temperatures.
Position the thermocouple so that the hot end is visible for visual confirmation of the junction location.
Depth of Immersion:
Immerse the thermocouple sufficiently to include the measuring junction entirely within the temperature zone to be measured.
A depth approximately ten times the diameter of the protection tube is recommended.
Heat conducted away from the hot junction can lead to lower readings due to “stem loss.”
Cold Junction and Connecting Head:
Keep the connecting head and cold junction in the coolest ambient temperature available.
Prevent thermal shock by gradually preheating ceramic tubes during installation.
Protection Tube:
Avoid direct flame impingement on the protection tube.
Impingement shortens tube life and affects temperature accuracy.
For high-temperature measurements, consider vertical installation to minimize tube sagging.
Extension Wire Installation Guidelines
Wire Selection:
Ensure you choose the correct type of extension wire based on the thermocouple calibration.
Use the color coding of individual wires as a guide
Avoiding EMF Interference:
To prevent spurious electromotive force (EMF) caused by electrostatic and electromagnetic noise:
Never run thermocouple extension wire in the same conduit as power sources.
Keep the thermocouple wire at least 12 inches away from any power source.
Avoid running the extension wire parallel to the conduit or near power lines.
High-Noise Areas:
In environments with high noise levels:
Use thermocouple extension wire with:
Twisted and shielded conductors: This minimizes interference.
A drainwire for additional protection.
Insulation Selection:
Choose the proper insulation material based on specific operating conditions.
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.
Connect the external thermocouple sensor to Device and install the Device on the Wall/Housing/Structure
Open the housing of thermocouple transmitter by unscrewing 2 screws
Run the cable of the external thermocouple sensor to the hole of PG9 connector and then connect 2-wire of the thermocouple sensor to + and - terminal on the device. Please note the pole of wirings and the terminals
Close the housing of thermocouple transmitter by screwing 2 screws
Mount the sensor onto a wall/housing/structure with provided bracket and screws.
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)
1. The measured value is not within the expected value
The thermocouple sensor is drifted over time: Re-calibrate the sensor.
The thermocouple sensor was spoiled due to some reasons. Replace the new sensor
The DIP switch configurations for thermocouple type or wirings are wrong/changed: Check with manufacturer manual about DIP switch configurations or wirings
Configuration thermocouple type in device memory is wrong/changed: Check and adjust the configuration of correct thermocouple type
2. HW_Error = 1
The thermocouple node got a problem: Please consult the manufacturer for a warranty or replacement.
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)
Implement monthly check and maintenance as below:
Visual Inspection:
Cable and Connections: Examine the thermocouple cable for any signs of wear, fraying, or damage. Check the connectors (if detachable) for tightness and cleanliness.
Junction Area: Inspect the junction (where the two dissimilar metals meet) for any corrosion, oxidation, or physical damage. Clean it gently if needed.
Electrical Continuity:
Use a multimeter to measure the electrical continuity of the thermocouple. Connect the multimeter leads to the thermocouple terminals and verify that the resistance matches the expected values for the specific type (e.g., type K, type J).
Temperature Verification:
Compare the thermocouple reading with a known reference temperature. You can use a calibrated thermometer or another reliable temperature sensor. Ensure that the thermocouple accurately reflects the actual temperature.
Calibration Check:
If possible, perform a calibration check using a certified reference source. This ensures that the thermocouple maintains its accuracy over time.
Note any deviations from the expected values and take corrective action if necessary.
Environmental Factors:
Consider the environmental conditions where the thermocouple is installed. Check for exposure to chemicals, moisture, or extreme temperatures.
Inspect any protection tubes (if used) for cracks or damage.
3
ADVANCED GUIDE
3.1 Principle of Operation
Principle of Operation for device WSLRWAL-TC | FW1
Daviteq LoRaWAN Thermocouple Sensor comprises 02 parts linked internally:
• The Daviteq LoraWAN wireless transmitter;
• The Daviteq LoRaWAN Thermocouple transmitter
What are the primary output values?
• TEMPERATURE: Temperature value, unit of oC, use for alarm. This parameter equals TEMPERATURE in the uplink payload
• TC TYPE: Thermocouple type. If thermocouple module is not connected to the LoRaWAN node, the value will be zero. This parameter equals TC_TYPE 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.
Note: To get the accurate battery level indication, please configure the battery type by Downlink type 5 or via offline cable to the parameter name BATTERY_TYPE.The default type is Primary battery. For Solar powered version, please configure to Rechargeable battery type.
• 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_COM_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
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 TEMPERATURE
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)
A thermocouple comprises two distinct electrical conductors, typically made of different metals or metal alloys. These conductors are joined at both ends to form an ‘electrical junction’. The junction can be created through welding, twisting, or soldering. The fundamental phenomenon behind thermocouples is the ‘Seebeck effect’. When the junction experiences a ‘temperature gradient’ (with one end hotter and the other colder), it generates an ‘electromotive force (EMF)’. This EMF results in a ‘voltage’, known as the ‘Seebeck voltage’ or ‘thermoelectric voltage’. The magnitude of the Seebeck voltage is directly proportional to the ‘temperature difference’ between the hot and cold junctions.
To accurately measure temperature, a reference point is essential. One end of the thermocouple (usually the cold junction) is maintained at a known reference temperature (often room temperature). The voltage across the thermocouple is measured using a ‘voltmeter’. By referencing calibration tables or employing specific equations tailored to the thermocouple type, the actual temperature can be determined.
While the Seebeck voltage is approximately linear with temperature over a limited range, this linearity is not perfect, especially at extreme temperatures. Thermocouples are characterized by their ‘thermoelectric coefficients’, which describe the relationship between temperature and voltage. Since the reference junction (cold junction) is not always at a fixed temperature, compensation techniques are necessary. Modern thermocouples incorporate ‘cold junction compensation’ methods, such as using a ‘thermistor’ or an ‘IC-based sensor’ to measure the reference temperature
Daviteq thermocouple node measures the mV output of thermocouple, compensate the cold junction mV, and convert to the temperature
Default Configuration Parameters of Sensor part (if available)
Thermocouple node has the default configuration. The user can change the configuration on the wireless transmitter so that the complete sensor (transducer + wireless) delivers the proper output value.
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.
The position of the sensor's 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)
By using the magnet key to touch the contact point, the LoRaWAN device can be triggered to send data to the gateway immediately.
Note:
Once sending data to the gateway by magnet key, the timer of sending time interval will be reset;
The shortest time interval between the two manual triggers is 15s. if shorter than 15s, there will be no data sending.
Calibration/ Validation sensor (if available)
To calibrate a complete thermocouple temperature device (Daviteq thermocouple node and thermocouple sensor), follow these steps:
Isolate the sensor (thermocouple) from the process.
Immerse the sensor fully into a dry-well or bath that can cover the required temperature range.
Change CONSTANT_A = 1 and CONSTANT_B =0 on Daviteq thermocouple node memory by offline tool or downlink
Adjust the temperature of the bath or dry-well to each of the test points. At each test point, record the readings of the standard temperature and thermocouple device's temperature. Record 2 test points (calibrated minimum temperature point and calibrated maximum temperature point)
Calculate CONSTANT_A and CONSTANT_B based on the standard temperature and thermocouple device's temperature at minimum temperature point and maximum temperature point.
Standard Temperature = CONSTANT_A * thermocouple device's temperature + CONSTANT_B
Change calculated CONSTANT_A and CONSTANT_B on Daviteq thermocouple node memory by offline tool or downlink
4
PRODUCT SPECIFICATIONS
4.1 Specifications
| Input | Thermocouple Temperature Sensor Type B, Type E, Type J, Type K, Type N, Type R, Type S, Type T |
| Accuracy | ±0.55℃ in ambient temperature range -20∼100℃ ±1.05℃ in ambient temperature range -40∼125℃ **Not included error of Thermocouples |
| Resolution | 0.1℃ |
| Sensor port connector | Internal Connectors via PG9 Cable Gland |
| COMMUNICATION | |
| SF Factors | SF7∼SF12 |
| Antenna | External antenna |
| Power Supply | Primary batteries 01 x C size 3.6VDC (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 V1.0.3 |
| Data sending modes | interval time, alarm and manually triggering by magnetic key |
| Housing | Cast aluminum, IP66 |
| Ambient working temperature | -40∼85℃ (use with SAFT LS26500) |
| Size | Net weight | H190xW100xD75/700g (excluding antenna) |
| Mounting type | Wall mount |
5
WARRANTY & SUPPORT
5.1 Warranty
Warranty
Below terms and conditions are applied for products manufactured and supplied by Daviteq Technologies Inc.
Free Warranty Conditions
The manufacturer undertakes to guarantee within 12 months from shipment date.
Product failed due to defects in material or workmanship.
Serial number, label, warranty stamp remains intact (not purged, detected, edited, scraped, tore, blurry, spotty, or pasted on top by certain items).
During the warranty period, if any problem of damage occurs due to technical manufacturing, please notify our Support Center for free warranty consultancy. Unauthorized treatments and modifications are not allowed.
Product failed due to the defects from the manufacturer, depending on the actual situation, Daviteq will consider replacement or repairs.
Note: One way shipping cost to the Return center shall be paid by Customers.
Paid Warranty
The warranty period has expired.
The product is not manufactured by Daviteq.
Product failed due to damage caused by disasters such as fire, flood, lightning or explosion, etc.
Product damaged during shipment.
Product damaged due to faulty installation, usage, or power supply.
Product damage caused by the customer.
Product rusted, stained by effects of the environment or due to vandalism, liquid (acids, chemicals, etc.)
Product damage is caused by unauthorized treatments and modifications.
Note: Customers will be subjected to all repairing expenses and 2-way shipping costs. If arises disagreement with the company's determining faults, both parties will have a third party inspection appraise such damage and its decision be and is the final decision.
5.2 Support
Support via Help center
If you need our support for Daviteq device's installation, configuration, test, and decode, please email us at: support@daviteq.com OR input support request at link: https://forms.office.com/r/XWHbYG7yy7
Our support engineer will contact you via email or the support ticket system.
If you have any questions about the product, you can search for information on our web (https://www.iot.daviteq.com/). If you can't find the right information, please register an account and send us a request at link Contact us | Daviteq Technologies . We will respond within 24 hours.