<
From version < 109.5 >
edited by Xiaoling
on 2022/06/10 13:48
To version < 109.9 >
edited by Xiaoling
on 2022/06/10 13:57
>
Change comment: There is no comment for this version

Summary

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 ==
... ... @@ -238,23 +238,24 @@
238 238  
239 239  
240 240  
241 -=== 2.3.4 Soil Temperature ===
243 +=== 2.3.4  Distance signal strength ===
242 242  
243 -Get Soil Temperature 
245 +Refers to the signal strength, the default output value will be between 0-65535. When the distance measurement gear is fixed, the farther the distance measurement is, the lower the signal strength; the lower the target reflectivity, the lower the signal strength. When Strength is greater than 100 and not equal to 65535, the measured value of Dist is considered credible.
244 244  
245 245  
246 246  **Example**:
247 247  
248 -If payload is: **0105H**:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
250 +If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
249 249  
250 -If payload is: **FF3FH** (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
252 +Customers can judge whether they need to adjust the environment based on the signal strength.
251 251  
252 252  
253 253  
254 -=== 2.3.5 Interrupt Pin ===
256 +=== 2.3.5  Interrupt Pin ===
255 255  
256 256  This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H3.2SetInterruptMode"]] for the hardware and software set up.
257 257  
260 +Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>path:#pins]].
258 258  
259 259  **Example:**
260 260  
... ... @@ -264,8 +264,18 @@
264 264  
265 265  
266 266  
267 -=== 2.3.6 Message Type ===
270 +=== 2.3.6  LiDAR temp ===
268 268  
272 +Characterize the internal temperature value of the sensor.
273 +
274 +**Example: **
275 +If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
276 +If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
277 +
278 +
279 +
280 +=== 2.3.7  Message Type ===
281 +
269 269  (((
270 270  For a normal uplink payload, the message type is always 0x01.
271 271  )))
... ... @@ -279,10 +279,11 @@
279 279  |=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
280 280  |(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]]
281 281  |(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H3.4GetFirmwareVersionInfo"]]
282 -|(% style="width:160px" %)0x03|(% style="width:163px" %)Reply Calibration Info|(% style="width:173px" %)[[Calibration Payload>>||anchor="H2.7Calibration"]]
283 283  
284 -=== 2.3.7 Decode payload in The Things Network ===
285 285  
297 +
298 +=== 2.3.8  Decode payload in The Things Network ===
299 +
286 286  While using TTN network, you can add the payload format to decode the payload.
287 287  
288 288  
... ... @@ -449,7 +449,7 @@
449 449  * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
450 450  * 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)
451 451  
452 -=== 2.6.3 CN470-510 (CN470) ===
466 +=== 2.6.3  CN470-510 (CN470) ===
453 453  
454 454  (((
455 455  Used in China, Default use CHE=1
... ... @@ -538,7 +538,7 @@
538 538  
539 539  
540 540  
541 -=== 2.6.4 AU915-928(AU915) ===
555 +=== 2.6.4  AU915-928(AU915) ===
542 542  
543 543  (((
544 544  Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
... ... @@ -559,7 +559,7 @@
559 559  * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
560 560  * 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)
561 561  
562 -=== 2.6.5 AS920-923 & AS923-925 (AS923) ===
576 +=== 2.6.5  AS920-923 & AS923-925 (AS923) ===
563 563  
564 564  (((
565 565  (% style="color:blue" %)**Default Uplink channel:**
... ... @@ -668,7 +668,7 @@
668 668  
669 669  
670 670  
671 -=== 2.6.6 KR920-923 (KR920) ===
685 +=== 2.6.6  KR920-923 (KR920) ===
672 672  
673 673  (((
674 674  (% style="color:blue" %)**Default channel:**
... ... @@ -741,7 +741,7 @@
741 741  
742 742  
743 743  
744 -=== 2.6.7 IN865-867 (IN865) ===
758 +=== 2.6.7  IN865-867 (IN865) ===
745 745  
746 746  (((
747 747  (% style="color:blue" %)**Uplink:**
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0