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
The WSLRW-LPC is a LoRaWAN sensor with a built-in advanced LiDAR sensor that can count people in two directions with an accuracy of over 95%. The sensor is not affected by temperature, humidity, RF noise, and is less affected by ambient light. Its ultra-low power design and smart firmware allow the complete wireless and sensor package to run on AA batteries (1.5V) for many years. The sensor can transmit data for kilometers to any LoRaWAN gateway brand on the market.
Typical applications for this sensor include people counting for public toilets and for stores and shops.
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, Safety Monitoring
Notes
- It counts one person at a time. For indoor only. Floor color must be bright;
- Gate width max 1500mm;
- Gate height from 2000 to 3500mm;
- Walking speed < 1.38 m/s (5 km/h);
1.3 When does device send Uplink messages?
The device will send uplink messages in the following cases:
Case 1: After power-up in the 60s, the device will send the first message called START_UP. The payload will tell the user the HW version, FW version, and current configuration of the device.
Case 2: Then, in every interval time (pre-configured), for example, 30 minutes, it will send the message called CYCLIC_DATA. The payload will tell the user the following data like measured values, battery level, and alarm status...
To change the cycle of data sending, you can change the value of the parameter: CYCLIC_DATA_PERIOD.
Case 3: If ALARM_ENABLED=1, the device will send ALARM message immediately when device switches from Normal state to Alarm state. It will repeat sending ALARM messages in predefined ALARM_PERIOD time interval if the Alarm state still exist.
Case 4: During the commissioning, testing, or calibration sensor, the user can force the device to send the uplink message to get the data immediately. This message is called FORCE_DATA. The payload will provide data like raw measured value, scaled measured values, battery level, and alarm status... It can be forced by applying the magnet key on the reed switch in 1s.
Case 5: If users want to change the configuration immediately, they don't need to wait until the next cyclic data-sending message; instead, they can force the device to send a special uplink message so that the device can get the new downlink message. This uplink message is named PARAMETERS_UPDATE. It can be forced by applying the magnet key in more than 5s.
Case 6: In every interval time (pre-configured), for example, 24 hours, it will send the message called HEARTBEAT. The payload will tell the user the following data like hardware version, firmware version, current sensor configuration.
Case 7: If LNS_CHECK_MODE =1, it will send the confirmed uplink message called LNS_CHECK every 24 hours. This confirmed uplink message is a message where a LoRaWAN device is requesting a LoRaWAN network to confirm the reception of its message. If the device receives no confirmation message from LoraWAN network server, it will re-send the LNS_CHECK message every hour during 3 hours. After 4th hour, if the device still receives no confirmation message, it will reset itself to join the network server. The LNS_CHECK payload will tell the user the following data like hardware version, firmware version, current sensor configuration.
1.4 Default Configuration
This LPC sensor 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: 06
Recommended batteries: Energizer® L91 or equivalent from Duracell;
Steps to install the batteries:
Step 1: Using flat head screws to push into 2 reed joints.
Step 2: Open the housing, then insert 06 x AA 1.5VDC battery, please take note the poles of the battery.
ATTENTION:
REVERSED POLARITY OF BATTERIES IN 10 SECONDS CAN DAMAGE THE SENSOR CIRCUIT!!!
Step 3: Insert the top plastic housing (Please note the 2 reed joint)
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?
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)
Do not install the sensor outdoors or indoors in areas with high intensity of sunlight.
Do not install the sensor in places where high dust particles or steam could affect the optical sensor.
Do not install the sensor near a door, as the door will blind the PIR sensor, preventing it from counting people.
Do not install the sensor in places where people are moving in parallel and nearby, as this will cause the sensor to wake up constantly but not count people. This problem will cause the batteries to drain quickly, in just a few days.
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 LoraWAN gateway. In real life, there may be no LOS condition. However, the LoRaWAN sensor still communicates with the LoRaWAN 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 Ceiling
Locate the mounting position at the entrance where people pass by, and out of direct sunlight.
The direction of the triangle is the direction of counting people entering as specified in the payload.
Determine the correct orientation to install the bottom cover to the ceiling in the correct direction.
WARNING:
Avoid placing hands or heavy objects on the laser sensor surface or the PIR sensor surface, as this may cause damage to the device;
Periodically use a clean cloth moistened with 70 degrees of alcohol to wipe the surface of the 2 sensors to keep the sensor clean and accurate.
Step 1:
Determine the direction of people entering the room of the sensor.
Step 2:
Mount the bottom housing of the sensor to the ceiling by fasten the 2 screws to the ceiling located at the 2 diagonal corners of the bottom cover.
Use the 2 screws that are included to be used to attach the sensor to surfaces such as: Wood, composite plastic.
If the ceiling surface is made of plaster, it is recommended to use a special insert so that the device can firmly adhere to the ceiling surface. Avoid dropping the device.
Step 3:
Attach the top and bottom housings (note the 2 reed joint)
Fit the main body to the bottom cover in the correct direction: the 2 reed joints on the bottom cover should fit into the main body on the side labeled with the device.
Make sure that the main body is fully engaged with the bottom cover, then release the hand.
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)
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)
This Lidar people counter comprises 02 optical parts:
Lidar sensor with optical lense;
PIR sensor with lense;
These 02 parts need to be checked and cleaned periodically, depending on the environment. Use alcohol (70% volume) to clean the surface of the 2 above parts.
After cleaning, force the sensor to send data to check the distance values of the Front and Back zones to confirm the accuracy of distance measurement.
Do not use Acetone or other strong solvents to clean, it will destroy the surface of the sensor and cause malfunctions
3
ADVANCED GUIDE
3.1 Principle of Operation
Principle of Operation for device WSLRW-LPC | FW4
Daviteq LoRaWAN Lidar People Counter (LPC) comprises 02 parts linked internally:
• The Daviteq LoraWAN wireless transmitter;
• The Daviteq LoRaWAN Lidar People Counter (LPC)
What are the primary output values?
• NRC PEOPLE IN: Non-resettable in-people counter. This parameter equals NRC_PEOPLE_IN in the uplink payload.
• NRC PEOPLE OUT: Non-resettable out-people counter. This parameter equals NRC_PEOPLE_OUT in the uplink payload.
• RC PEOPLE IN: Resettable in-people counter, used for alarm. If RC_PEOPLE_IN > COUNT_THRESHOLD to trigger the ALARM event and reset this counter. This parameter equals RC_PEOPLE_IN in the uplink payload
• RC PEOPLE OUT: Resettable out-people counter, used for alarm. If RC_PEOPLE_OUT > COUNT_THRESHOLD to trigger the ALARM event and reset this counter. This parameter equals RC_PEOPLE_OUT in the uplink payload
• DISTANCE FRONT ZONE: Distance from the laser sensor head to the laser front zone, unit of mm. This parameter equals DISTANCE_FRONT_ZONE in the uplink payload
• BACK ZONE DIFFERENCE: Difference between DISTANCE FRONT ZONE and DISTANCE BACK ZONE, unit of cm.
BACK_ZONE_DIFFERENCE = (DISTANCE_BACK_ZONE - DISTANCE_FRONT_ZONE / 10.
This parameter equals BACK_ZONE_DIFFERENCE 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.
• 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
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 parameters for alarm are RC PEOPLE IN and RC PEOPLE OUT
If parameter ALARM_ENABLE = 1
Then the device will compare the main parameter (RC PEOPLE IN and RC PEOPLE OUT) with COUNT_THRESHOLD define the state of the device is No_Alarm or Alarm.
If RC_PEOPLE_IN > COUNT_THRESHOLD to trigger the ALARM event and reset this counter to zero.
If RC_PEOPLE_OUT > COUNT_THRESHOLD to trigger the ALARM event and reset this counter to zero.
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)
Counting people with this Lidar sensor consists of using the multiple zones of the sensor receiving area, and configuring it with two distinct fields of view (FoV), to alternatively get a ranging distance from them and consequently recognize the movements of a person. Using this method, the number of people occupying a meeting room, accessible from reasonably narrow access, is known at all times by detecting the entrances and exits of the attendees.
By measuring and analyzing the distances of targets within the FoVs of a front and back zone (see figure below), an algorithm can detect the direction a person crosses the area under the two FoVs. This algorithm "understands" that someone is under one of the FoV as long as the distance measured by the sensor under this FoV is between 0 and a threshold value specified in mm.
From a timing perspective, the sensor alternatively ranges on each of the two zones, for a very short period of milliseconds. It is possible to determine in which direction a person crosses the area, depending on in which order this person has been detected in the two zones, as shown in the figure below.
Dist_threshold mechanism
- The sensor will measure the distance from the sensor (on the ceiling) to the floor, when there is an obstacle, the person is under the sensor, the sensor will measure the distance from the sensor to the obstacle, and that person => will get the DistX value
- When DistX < Dist_threshold, the sensor detects that someone is standing below
- When DistX > Dist_threshold + dist_hys, the sensor confirms that no one is under
Counting Hysteresis
The algorithm validates a crossing event only when a person has fully crossed the two zones. It does not validate the event when the person remains for a long time under the FoV or when the person decides to return from the place he came from, and hence the counting values are not changed.
Default Configuration Parameters of Sensor part (if available)
This LPC sensor has the default configuration, however, those parameters can be changed. The user can change the configuration on the wireless transmitter so that the complete sensor (transducer + wireless) delivers the proper output value. Please check the Payload document for more information.
3.2 Configuration
How to configure the device?
Sensor configuration can be configured in 02 methods:
Method 1: Configuring via Downlink messages, port 1 (default)
Method 2: Configuring via Offline cable.
To access to the sensor's configuration port, please follow below steps:
Step 1: Open the housing by using flat head screws to push into 2 reed joints;
Step 2: Plug the connector to the configuration port;
Please note the configuration port have 4 pins, next to positive polarity of battery holder, on the left-hand side.
Note: The sensor is only active for offline configuration in the first 60 since power up by battery or plugging the configuration cable.
Which Parameters are configured?
Please check Part G in Section 1.9 Payload Documents above.
Method 1: Configuration via Downlink messages
Please check the Part D & E in Section 1.9 Payload Documents above.
Method 2: Configuration by Offline Cable
Please download the Configuration Template File of this sensor to be used in Step 4 below.
Instructions for offline configuration of the Daviteq LoRaWAN sensors. Please follow the following steps.
Note: The sensor is only active for offline configuration in the first 60 since power up by battery or plugging the configuration cable.
1. Prepare equipment and tools
The following items must be prepared for configuration.
A PC using the Windows OS (Windows 7 or above versions). The PC installed the COM port driver of the Modbus configuration cable (if needed). The driver is at link: Modbus Configuration Cable COM port driver for PC and the instruction to install the driver at link: How to install the driver.
A Modbus configuration cable
Tools to open the plastic housing of LoRaWAN sensors (L hex key or screwdriver)
2. Download and launch Daviteq Modbus configuration software
Click the link below to download Daviteq Modbus configuration software:
https://filerun.daviteq.com/wl/?id=yDOjE5d6kqFlGNVVlMdFg19Aad6aw0Hs
After downloading the software, unzip the file named: Daviteq Modbus Configuration.zip and then copy the extracted folder to the storage drive for long-term use.
Open the folder, double click on the file Daviteq Modbus Configuration Tool Version.exe to launch the software and the software interface as below:
Note: The software only runs on Microsoft Windows OS (Windows 7 and above).
3. Connect the cable and configure the sensor
Step 1:
Connect the PC to the sensor using the configuration cable.
- Use the configuration cable (Item code: TTL-LRW-USB-01).
- Connect the USB-A plug into the USB-A socket of the PC.
Step 2:
On the configuration software, choose the relevant Port (the USB port which is the cable plugged in) and set the BaudRate: 9600, Parity: none
Step 3:
Click Connect button to connect the software to the sensor. After successful connection, the Connected status will show on the software.
Step 4:
Import the configuration template file of the sensor (as above link) to the software: click menu File/ Import New and then browse the relevant sensor template file (csv file) and click Open to import the template file.
Note: The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor.
Each sensor type has its own template file. Refer to the sensor's manual to download the correct file.
Step 5:
Open the housing of the sensor and quickly plug the connector of the configuration cable into sensor's modbus configuration port as below figure. After plugging the connector, the software will read the parameter values automatically.
Plug the cable connector into sensor's modbus configuration port. This port is located at a different location, depends on the sensor type
Note: If the sensor has SKU of WSLRWEX-PPS and hardware version 1 & 2, the sensor must be powered by batteries for configuration
Step 6:
Read the current value of the parameter with Modbus Function 3
At the relevant row of the parameter, check box 3 on column Func to read the value of the parameter. The read value is shown in VALUE ON MEMMAP column.
The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. After 60 seconds, the TIME_OUT text will show on EXCEPTION column of the software.
Step 7:
Write the new setting to the parameter with Modbus Function 16
Double click on the column VALUE TO WRITE of the parameter and input the new setting value of the parameter;
Uncheck the tick on the FC column of the parameter, click on the arrow, select 16 and then check on the FC column to write a new setting to the parameter. The WRITE_OK text will show on EXCEPTION column if the software successfully writes the setting.
Repeat Step 6 to read the setting of the parameter for double-checking.
Note: For some critical parameters of the sensor, the password in "password for setting" must be written before writing the new settings to these parameters.
Only read/ write registers are allowed to write.
The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. After 60 seconds, the TIME_OUT text will show on EXCEPTION column of the software.
4. Troubleshooting
3.3 Calibration/ Validation
How to force sensor to send data for calibration/ validation (if available)
Using the magnet key, the device can be triggered to send data to the gateway immediately.
Note:
Upon transmitting the data to the gateway using the magnetic key, the timer for the transmission time interval will be reset.
The minimum time interval between two manual triggers is 15 seconds. If the interval is less than 15 seconds, data transmission will not occur.
Calibration/ Validation sensor (if available)
Commissioning the Lidar people counting sensor is an important step to getting the sensor working properly.
The Lidar FOV is 27° and the max distance is 3500mm, so please check the width and height dimensions of the gate so that the person must be within the FOV.
After that, checking the floor, the floor must be a flat and bright color. The very dark color (back or near-black color) floor can affect the distance measurement accuracy. In this case, using a light color carpet to gain accuracy.
The reliability of the algorithm relies on the accuracy of the setup which detects the distance between the sensor and the floor. This can be ensured only if nothing (e.g. no obstacle or static object) blocks the front and back FoVs. To assess if a setup is reliable, a significant number of distances can be measured with the sensor. Then, a histogram diagram can be established to confirm that the sensor is correctly set up and that no target is within its FoVs.
A threshold needs to be defined, which is achieved after having ranged the flooring material over a significant number of samples. In fact, the threshold should be chosen so that all the measured distances (when ranging the floor) are greater than this threshold. We recommend that at the installation of the application, the autocalibration routine is launched to calculate the threshold. This is because flooring material can be different in many locations.
Note: This calibration should be performed in the worst ambient light conditions, to maximize the jitter and obtain a threshold that is relevant to all possible ambient lighting conditions the counting setup is exposed to.
4
PRODUCT SPECIFICATIONS
4.1 Specifications
| Sensor technology | Lidar |
| Gate height | 2.2∼4.0m |
| Gate width | 0.75∼1.5m |
| Detection cone | 27° |
| Working temperature | -40∼60℃ |
| Working humidity | 0∼100% RH, non-condensing |
| COMMUNICATION | |
| SF Factor | SF7∼SF12 |
| Antenna | Internal antenna 2.0dbi |
| Power Supply | 6 x Batteries AA Type 1.5VDC (not included) |
| RF Frequency and Power | 860∼930MHz, 14∼20dBm, 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℃ (with Lithium Ultimate AA battery) |
| Dimensions | H120xW80xD45 |
| Net-weight | < 150g |
| Housing | Self-extinguisher ABS, Dust and vapor protection |
| Mounting | Ceiling 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.