Changes for page LDDS45 - LoRaWAN Distance Detection Sensor User Manual
Last modified by Mengting Qiu on 2025/02/26 15:04
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -4,6 +4,7 @@ 4 4 5 5 **Contents:** 6 6 7 +{{toc/}} 7 7 8 8 9 9 ... ... @@ -10,6 +10,7 @@ 10 10 11 11 12 12 14 + 13 13 = 1. Introduction = 14 14 15 15 == 1.1 What is LoRaWAN LiDAR ToF Distance Sensor == ... ... @@ -17,18 +17,30 @@ 17 17 ((( 18 18 19 19 22 +((( 20 20 The Dragino LLDS12 is a (% style="color:blue" %)**LoRaWAN LiDAR ToF (Time of Flight) Distance Sensor**(%%) for Internet of Things solution. It is capable to measure the distance to an object as close as 10 centimeters (+/- 5cm up to 6m) and as far as 12 meters (+/-1% starting at 6m)!. The LiDAR probe uses laser induction technology for distance measurement. 24 +))) 21 21 26 +((( 22 22 The LLDS12 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc. 28 +))) 23 23 30 +((( 24 24 It detects the distance between the measured object and the sensor, and uploads the value via wireless to LoRaWAN IoT Server. 32 +))) 25 25 34 +((( 26 26 The LoRa wireless technology used in LLDS12 allows device to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. 36 +))) 27 27 38 +((( 28 28 LLDS12 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use up to 5 years. 40 +))) 29 29 42 +((( 30 30 Each LLDS12 is pre-load with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect after power on. 31 31 ))) 45 +))) 32 32 33 33 34 34 [[image:1654826306458-414.png]] ... ... @@ -291,6 +291,8 @@ 291 291 |(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]] 292 292 |(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H3.4GetFirmwareVersionInfo"]] 293 293 308 + 309 + 294 294 === 2.3.8 Decode payload in The Things Network === 295 295 296 296 While using TTN network, you can add the payload format to decode the payload. ... ... @@ -459,7 +459,7 @@ 459 459 * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 460 460 * Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include) 461 461 462 -=== 2.6.3 CN470-510 (CN470) === 478 +=== 2.6.3 CN470-510 (CN470) === 463 463 464 464 ((( 465 465 Used in China, Default use CHE=1 ... ... @@ -548,7 +548,7 @@ 548 548 549 549 550 550 551 -=== 2.6.4 AU915-928(AU915) === 567 +=== 2.6.4 AU915-928(AU915) === 552 552 553 553 ((( 554 554 Frequency band as per definition in LoRaWAN 1.0.3 Regional document. ... ... @@ -569,7 +569,7 @@ 569 569 * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 570 570 * Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include) 571 571 572 -=== 2.6.5 AS920-923 & AS923-925 (AS923) === 588 +=== 2.6.5 AS920-923 & AS923-925 (AS923) === 573 573 574 574 ((( 575 575 (% style="color:blue" %)**Default Uplink channel:** ... ... @@ -678,7 +678,7 @@ 678 678 679 679 680 680 681 -=== 2.6.6 KR920-923 (KR920) === 697 +=== 2.6.6 KR920-923 (KR920) === 682 682 683 683 ((( 684 684 (% style="color:blue" %)**Default channel:** ... ... @@ -751,7 +751,7 @@ 751 751 752 752 753 753 754 -=== 2.6.7 IN865-867 (IN865) === 770 +=== 2.6.7 IN865-867 (IN865) === 755 755 756 756 ((( 757 757 (% style="color:blue" %)**Uplink:**