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

Summary

Details

Page properties
Content
... ... @@ -4,7 +4,6 @@
4 4  
5 5  **Contents:**
6 6  
7 -{{toc/}}
8 8  
9 9  
10 10  
... ... @@ -11,7 +11,6 @@
11 11  
12 12  
13 13  
14 -
15 15  = 1.  Introduction =
16 16  
17 17  == 1.1 ​ What is LoRaWAN LiDAR ToF Distance Sensor ==
... ... @@ -253,11 +253,10 @@
253 253  
254 254  
255 255  
256 -=== 2.3.5  Interrupt Pin ===
254 +=== 2.3.5 Interrupt Pin ===
257 257  
258 258  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.
259 259  
260 -Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>path:#pins]].
261 261  
262 262  **Example:**
263 263  
... ... @@ -267,18 +267,8 @@
267 267  
268 268  
269 269  
270 -=== 2.3.6  LiDAR temp ===
267 +=== 2.3.6 Message Type ===
271 271  
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 -
282 282  (((
283 283  For a normal uplink payload, the message type is always 0x01.
284 284  )))
... ... @@ -292,11 +292,10 @@
292 292  |=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
293 293  |(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]]
294 294  |(% 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"]]
295 295  
284 +=== 2.3.7 Decode payload in The Things Network ===
296 296  
297 -
298 -=== 2.3.8  Decode payload in The Things Network ===
299 -
300 300  While using TTN network, you can add the payload format to decode the payload.
301 301  
302 302  
... ... @@ -463,7 +463,7 @@
463 463  * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
464 464  * 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)
465 465  
466 -=== 2.6.3  CN470-510 (CN470) ===
452 +=== 2.6.3 CN470-510 (CN470) ===
467 467  
468 468  (((
469 469  Used in China, Default use CHE=1
... ... @@ -552,7 +552,7 @@
552 552  
553 553  
554 554  
555 -=== 2.6.4  AU915-928(AU915) ===
541 +=== 2.6.4 AU915-928(AU915) ===
556 556  
557 557  (((
558 558  Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
... ... @@ -573,7 +573,7 @@
573 573  * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
574 574  * 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)
575 575  
576 -=== 2.6.5  AS920-923 & AS923-925 (AS923) ===
562 +=== 2.6.5 AS920-923 & AS923-925 (AS923) ===
577 577  
578 578  (((
579 579  (% style="color:blue" %)**Default Uplink channel:**
... ... @@ -682,7 +682,7 @@
682 682  
683 683  
684 684  
685 -=== 2.6.6  KR920-923 (KR920) ===
671 +=== 2.6.6 KR920-923 (KR920) ===
686 686  
687 687  (((
688 688  (% style="color:blue" %)**Default channel:**
... ... @@ -755,7 +755,7 @@
755 755  
756 756  
757 757  
758 -=== 2.6.7  IN865-867 (IN865) ===
744 +=== 2.6.7 IN865-867 (IN865) ===
759 759  
760 760  (((
761 761  (% style="color:blue" %)**Uplink:**
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0