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-AG | FW5
Normally Stock
Replaced by
Replaced by
Item codes | FW Released Date | Changes Information |
|---|---|---|
WSLRW-AG-01, WSLRW-AG-02S | 28/01/2023 | Default Alarm off. Add Alarm with the Hysteresis value for the alarm 1 and Alarm 2 (default 1 degree). Add battery type (default battery non-rechargeable). Update payload: X100 for all tilt values. Add CYCLIC_FREQ_FACTOR, ALARM_FREQ_FACTOR |
1
QUICK INSTALLATION GUIDE
1.1 Introduction
WSLRW-AG is a LoRaWAN Tilt Sensor, inclinometer can be used to measure tilt angles X, and Y of any object such as a Tower, Building, Tree, Electricity Tower, Telecom Tower, Bridges... With Ultra-low Power design and smart firmware allow the sensor can last up to 10 years with 02 x AA-type battery (depends on configuration). The sensor will transmit data in kilo-meters distance to the LoRaWAN gateway, any brand on the market.
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
Facility Monitoring, Flood Monitoring, Infrastructure Monitoring, Level Monitoring, Machine Health Monitoring, Safety Monitoring, Tilt Monitoring
Notes
This AG tilt sensor measures the static tilt angle of the static object vs. the Gravity direction. Please do not use it for other angle measurements.
It measures the static tilt angle of stationary objects or slow-moving objects such as Tree, Bridge, Pole, Tower, Crane, and Building...
It does not measure the tilt angle of a quick-moving object like construction equipment...
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 (default is 600 seconds).
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.
1.4 Default Configuration
There is no configuration required for the AG Tilt Sensor. There is only configuration for the main device (Sigfox device, LoRaWAN device, Sub-GHz device...). Please refer to the configuration table of the main device.
1.5 Battery/ Power Supply
The Device uses Solar Panel with an M12-Male connector. Below are the item code, specifications, and pictures of the Solar Panel.
Item code: SOLAR-PN-1W6V-PU-M12F-20-1/4BRK
Description: SOLAR PANEL FOR SENSOR OR DEVICE, 1W 6V, PU COATED, M12-M CONNECTOR, 20CM CABLE, DOUBLE BALL BRACKET 1/4"
Panel lifetime: 10 years
To allow the device to run during the time without the Sun, please insert 02 rechargeable batteries as below into the battery holders.
Battery type: Panasonic Eneloop Standard (rechargeable), size AA
Number of batteries: 02
Battery voltage: 1.2V
Please take note on the Polarity of the batteries as below picture.
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%
Note: To display accurately the remaining energy of battery, please configure the correct BATTERY_TYPE by downlink type 5 or offline cable. Please check the section "Principle of Operation" for more details.
1.6 What's in the Package?
Product package for the LoRaWAN Tilt Sensor powered by Primary Battery
Product package for the LoRaWAN Tilt Sensor with internal antenna and powered by Solar Panel (Exclude Solar Panel)
Product package for the LoRaWAN Tilt Sensor with external antenna and powered by Solar Panel (Exclude Solar Panel)
Product package for the LoRaWAN Tilt Sensor with external antenna and powered by Solar Panel (Include Solar Panel)
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)
The AG sensor is built-in with the main device. Therefore please refer to the installation procedure for the main device as below:
- Install at zero position X=0, Y=0, Z=0 of sensor tilt for AG-01, AG-02 and X=0, Y=0 for AG-03
- Max range of AG-03 are -30~30°
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 Base station. In real life, there may be no LOS condition. However, the LoRaWAN sensor still communicates with the Base station, 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.
Attach the Solar Panel to the Device
Connect the M12 connector from the Panel to the Device;
Connect the bracket of the panel onto the device by 02 screws M3 as in the below pictures;
Mounting the Device on the Wall or Pole
Mount the sensor onto a wall by the mounting bracket as below pictures
Adjust the Solar Panel
Depending on the location of the site, the solar panel needs to be adjusted with the Tilt angle and Azimuth angle so that it can receive the most energy from the Sun in the entire year.
The adjustment will be made by the orange handle, as below sample pictures.
0° of Tilt Angle Position
45° of Tilt Angle Position
-90° of Azimuth Angle Position.
+90° of Azimuth Angle Position
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 the steps to identify the problems from the Communication Part or Sensor Part:
If the device cannot connect to the Gateway, or System, or Coordinator 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 the Sensor part;
If the data coming to the gateway, system, or coordinator is not frequent as expected, the problem would be Communication.
Please refer to the troubleshooting guide for the Communication and Sensor Part below.
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:
The battery needs to be replaced. Please check the battery status via uplink messages;
The Solar Panel needs to be cleaned periodically, depending on the particulate environment;
The mounting bracket of the Solar Panel needs to be verified to make sure the Solar panel is always in the correct tilt angle and azimuth angle;
Sensor, please refer to the maintenance section of the sensor document.
Maintenance for Sensor part (if available)
There are no moving parts or consumed parts in the AG Tilt Sensor. Therefore there is no need to do maintenance.
3
ADVANCED GUIDE
3.1 Principle of Operation
Principle of Operation for Device WSLRW-AG | FW5
The Daviteq LoRaWAN AG Tilt Sensor comprises 02 parts linked internally:
The Daviteq LoRaWAN wireless transmitter;
The Daviteq AG tilt sensor; (measures the Acceleration of the 3-axis. Please check the below section for a detailed description of this sensor)
What are the primary output values?
X-axis tilt angle: parameter in the payload is X_TILT_VALUE_X100
Y-axis tilt angle: parameter in the payload is Y_TILT_VALUE_X100
Z-axis tilt angle: parameter in the payload is Z_TILT_VALUE_X100
Alarm Status: parameter in the payload is ALERT_STATUS
Please check the payload document for more details.
What are the secondary output values?
Below output values are useful for device maintenance and troubleshooting.
Battery level (%), to understand the remaining capacity of the battery: 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.
Sensor error code, to understand whether the sensor is working properly or not: parameter in the payload is SENSOR_ERROR
Sensor current configuration, to understand what is the current setting of the sensor: parameter in the payload is CURRENT_CONFIGURATION
Hardware version and Firmware version, to understand the product version: parameter in the payload is HW_VERSION and FW_VERSION
Principle of operation
Most of the time, the LoRaWAN device will be in sleep mode. When the timer reaches the Measure_Period (for example, 2 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 the tilt angles X, Y, and Z. Then it calculates the more parameters as below:
Delta_X: is the differential between measured tilt angle X with the Reference_Angle_X;
Delta_Y: is the differential between measured tilt angle Y with the Reference_Angle_Y;
Note: after installing the device at field, need to perform a Downlink Type 5 command to write value 1 to parameter SET_REF_POS_FOR_ALARM (please check address in Payload document) to allow device get the Reference Position for Alarming function.
If parameter ALARM_ENABLE = 1
Then the device will compare the Delta_X (and Delta_Y) with Delta2_setpoint and Delta1_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.
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;
How to apply the Alarm function?
The Alarm function is OFF by default (parameter ALARM_ENABLE = 0)
The Alarm function is only working properly for the installation positions as below pictures.
To activate the Alarm function, please follow the below steps:
Install the device at the field as above directions, and fix it on the desired location;
Use one command from Downlink type 5 to write value "1" to parameter SET_REF_POS_FOR_ALARM (please check the address in the Payload document) to allow the device get the Reference Position;
Use one command from Downlink type 0 to write the following parameters:
Delta2_Setpoint: Setpoint for HiHi Alarm threshold (in degree);
Delta1_Setpoint_Factor: a factor to set the Hi Alarm threshold;
Alarm_Enable = 1 to allow alarm function;
Alarm_Period = time interval between sending the repeat alarm message.
How to understand and calculate the Alarm Thresholds?
The parameter Delta2_Setpoint is for setting the threshold of HiHi Alarm, unit is degree.
The parameter Delta1_Setpoint_Factor is for setting the threshold of Hi Alarm, unit is %.
For example:
Delta2_Setpoint = 5 ⇒ HiHi Alarm = 5°;
Delta1_Setpoint_Factor = 100 ⇒ Hi Alarm = 5 x 100/ 200 = 2.5°.
It means:
The device will send Hi Alarm when the Differential between the measured value and Reference position is larger than 2.5° and less than 5.0°;
The device will send HiHi Alarm when the Differential between the measured value and Reference position is larger than 5.0°;
Calibrate the tilt sensor
The LoRaWAN Tilt sensor is factory calibrated at the below position.
Put the sensor at above position and use the Downlink Type 5 to write value "1" to the parameter CALIB_ENABLE for calibration
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)
AG utilizes the three-axis high-accuracy MEMS acceleration sensor to calculate the static Euler angles of the object it is mounted on.
The microprocessor of the Wireless transmitter will capture the raw signal of 3-axis acceleration the calculate the tilt angle of X, Y, and Z. Here are the final output values of the device.
X Tilt value
16-bit signed integer
X_TILT_VALUE = X_TILT_VALUE_X100 / 100 for AG-01 and AG-02
X_TILT_VALUE = X_TILT_VALUE_X1000 / 1000 for AG-03
Range: -90.00 to 90.00 for AG-01 and AG-02; -30.000 to 30.000 for AG-03
Y Tilt value
16-bit signed integer
Y_TILT_VALUE = Y_TILT_VALUE_X100 / 100 for AG-01 and AG-02
Y_TILT_VALUE = Y_TILT_VALUE_X1000 / 1000 for AG-03
Range: -90.00 to 90.00 for AG-01 and AG-02; -30.000 to 30.000 for AG-03
Z Tilt value
16-bit signed integer
Z_TILT_VALUE = Z_TILT_VALUE_X100 / 100 for AG-01 and AG-02
No Z_TILT_VALUE for AG-03
Range: -90.00 to 90.00 for AG-01 and AG-02
Default Configuration Parameters of Sensor part (if available)
There is no configuration required for the AG Tilt Sensor. There is only configuration for the main device (Sigfox device, LoRaWAN device, Sub-GHz device...). Please refer to the configuration table of the main device.
3.2 Configuration
How to configure the device?
Sensor configuration can be configured in 02 methods:
Method 1: Configuring via Downlink messages.
Method 2: Configuring via Offline cable.
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 base station immediately.
Note:
Upon transmitting the data to the base station 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 AG sensor is factory calibrated. The user may need to perform the zero-ing after installation.
For AG-01 and AG-02 sensor:
To do the Zero-ing, the device must be installed in this direction with max ±5° deviation from Gravity direction.
After fixing the device, please perform the Zero-ing command on the main device (depending on the type of device, which is Sigfox or LoRaWAN or Sub-GHz...).
For AG-03 sensor:
The device is calibrated in 3 positions:
1. X tilt and Y tilt equal 0°
2. X tilt equals +30°
3. Y tilt equals +30°
After fixing the device, please perform the CALIBRATION_TILT_ENABLE command on the main device (depending on the type of device, which is Sigfox or LoRaWAN or Sub-GHz...).
4
PRODUCT SPECIFICATIONS
4.1 Specifications
Spec
5
WARRANTY & SUPPORT
5.1 Warranty
Warranty
Below terms and conditions are applied for products manufactured and supplied by Daviteq Technologies Inc.
Free Warranty Conditions
The manufacturer undertakes to guarantee within 12 months from shipment date.
Product failed due to defects in material or workmanship.
Serial number, label, warranty stamp remains intact (not purged, detected, edited, scraped, tore, blurry, spotty, or pasted on top by certain items).
During the warranty period, if any problem of damage occurs due to technical manufacturing, please notify our Support Center for free warranty consultancy. Unauthorized treatments and modifications are not allowed.
Product failed due to the defects from the manufacturer, depending on the actual situation, Daviteq will consider replacement or repairs.
Note: One way shipping cost to the Return center shall be paid by Customers.
Paid Warranty
The warranty period has expired.
The product is not manufactured by Daviteq.
Product failed due to damage caused by disasters such as fire, flood, lightning or explosion, etc.
Product damaged during shipment.
Product damaged due to faulty installation, usage, or power supply.
Product damage caused by the customer.
Product rusted, stained by effects of the environment or due to vandalism, liquid (acids, chemicals, etc.)
Product damage is caused by unauthorized treatments and modifications.
Note: Customers will be subjected to all repairing expenses and 2-way shipping costs. If arises disagreement with the company's determining faults, both parties will have a third party inspection appraise such damage and its decision be and is the final decision.
5.2 Support
Support via Help center
If you need our support for Daviteq device's installation, configuration, test, and decode, please 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.