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
-
... ... @@ -63,6 +63,9 @@ 63 63 * Downlink to change configure 64 64 * 8500mAh Battery for long term use 65 65 66 + 67 + 68 + 66 66 == 1.3 Probe Specification == 67 67 68 68 * Storage temperature :-20℃~~75℃ ... ... @@ -78,6 +78,9 @@ 78 78 * Material of enclosure - ABS+PC 79 79 * Wire length - 25cm 80 80 84 + 85 + 86 + 81 81 == 1.4 Probe Dimension == 82 82 83 83 ... ... @@ -94,6 +94,9 @@ 94 94 * Automatic control 95 95 * Sewer 96 96 103 + 104 + 105 + 97 97 == 1.6 Pin mapping and power on == 98 98 99 99 ... ... @@ -300,6 +300,9 @@ 300 300 |(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]] 301 301 |(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]] 302 302 312 + 313 + 314 + 303 303 === 2.3.8 Decode payload in The Things Network === 304 304 305 305 While using TTN network, you can add the payload format to decode the payload. ... ... @@ -468,6 +468,9 @@ 468 468 * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 469 469 * 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) 470 470 483 + 484 + 485 + 471 471 === 2.6.3 CN470-510 (CN470) === 472 472 473 473 ((( ... ... @@ -578,6 +578,9 @@ 578 578 * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 579 579 * 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) 580 580 596 + 597 + 598 + 581 581 === 2.6.5 AS920-923 & AS923-925 (AS923) === 582 582 583 583 ((( ... ... @@ -804,6 +804,9 @@ 804 804 * The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected. 805 805 * Blink once when device transmit a packet. 806 806 825 + 826 + 827 + 807 807 == 2.8 Firmware Change Log == 808 808 809 809 ... ... @@ -876,6 +876,7 @@ 876 876 877 877 878 878 900 + 879 879 = 4. Configure LLDS12 via AT Command or LoRaWAN Downlink = 880 880 881 881 ((( ... ... @@ -963,7 +963,6 @@ 963 963 [[image:image-20220607171554-8.png]] 964 964 965 965 966 - 967 967 ((( 968 968 (% style="color:#037691" %)**Downlink Command: 0x01** 969 969 ))) ... ... @@ -986,6 +986,9 @@ 986 986 987 987 ))) 988 988 1010 + 1011 + 1012 + 989 989 == 4.2 Set Interrupt Mode == 990 990 991 991 Feature, Set Interrupt mode for GPIO_EXIT. ... ... @@ -1014,6 +1014,9 @@ 1014 1014 Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger 1015 1015 ))) 1016 1016 1041 + 1042 + 1043 + 1017 1017 == 4.3 Get Firmware Version Info == 1018 1018 1019 1019 Feature: use downlink to get firmware version. ... ... @@ -1238,7 +1238,9 @@ 1238 1238 == 8.1 AT Commands input doesn’t work == 1239 1239 1240 1240 1268 +((( 1241 1241 In the case if user can see the console output but can’t type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn’t send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string. 1270 +))) 1242 1242 1243 1243 1244 1244 == 8.2 Significant error between the output distant value of LiDAR and actual distance == ... ... @@ -1283,6 +1283,9 @@ 1283 1283 * (% style="color:red" %)**IN865**(%%): LoRaWAN IN865 band 1284 1284 * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band 1285 1285 1315 + 1316 + 1317 + 1286 1286 = 10. Packing Info = 1287 1287 1288 1288 ... ... @@ -1297,6 +1297,9 @@ 1297 1297 * Package Size / pcs : cm 1298 1298 * Weight / pcs : g 1299 1299 1332 + 1333 + 1334 + 1300 1300 = 11. Support = 1301 1301 1302 1302 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.