<
From version < 101.2 >
edited by Xiaoling
on 2022/06/10 11:38
To version < 100.7 >
edited by Xiaoling
on 2022/06/10 11:35
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -485,6 +485,9 @@
485 485  * Reply to the confirmation package: 14 01
486 486  * Reply to non-confirmed packet: 14 00
487 487  
488 +
489 +
490 +
488 488  == 2.6  Frequency Plans ==
489 489  
490 490  (((
... ... @@ -552,7 +552,7 @@
552 552  
553 553  
554 554  
555 -=== 2.6.2  US902-928(US915) ===
558 +=== 2.8.2 US902-928(US915) ===
556 556  
557 557  (((
558 558  Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
... ... @@ -569,10 +569,8 @@
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  
575 +=== 2.8.3 CN470-510 (CN470) ===
572 572  
573 -
574 -=== 2.6.3 CN470-510 (CN470) ===
575 -
576 576  (((
577 577  Used in China, Default use CHE=1
578 578  )))
... ... @@ -659,9 +659,8 @@
659 659  
660 660  
661 661  
663 +=== 2.8.4 AU915-928(AU915) ===
662 662  
663 -=== 2.6.4 AU915-928(AU915) ===
664 -
665 665  (((
666 666  Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
667 667  )))
... ... @@ -681,9 +681,8 @@
681 681  * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
682 682  * 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)
683 683  
684 +=== 2.8.5 AS920-923 & AS923-925 (AS923) ===
684 684  
685 -=== 2.6.5 AS920-923 & AS923-925 (AS923) ===
686 -
687 687  (((
688 688  (% style="color:blue" %)**Default Uplink channel:**
689 689  )))
... ... @@ -790,9 +790,8 @@
790 790  
791 791  
792 792  
792 +=== 2.8.6 KR920-923 (KR920) ===
793 793  
794 -=== 2.6.6 KR920-923 (KR920) ===
795 -
796 796  (((
797 797  (% style="color:blue" %)**Default channel:**
798 798  )))
... ... @@ -863,9 +863,8 @@
863 863  
864 864  
865 865  
864 +=== 2.8.7 IN865-867 (IN865) ===
866 866  
867 -=== 2.6.7 IN865-867 (IN865) ===
868 -
869 869  (((
870 870  (% style="color:blue" %)**Uplink:**
871 871  )))
... ... @@ -900,7 +900,6 @@
900 900  
901 901  
902 902  
903 -
904 904  == 2.7  LED Indicator ==
905 905  
906 906  The LLDS12 has an internal LED which is to show the status of different state.
... ... @@ -910,7 +910,6 @@
910 910  
911 911  
912 912  
913 -
914 914  == 2.8  ​Firmware Change Log ==
915 915  
916 916  
... ... @@ -969,6 +969,7 @@
969 969  * The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
970 970  * The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window.
971 971  
967 +
972 972  = 4.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
973 973  
974 974  (((
... ... @@ -1083,6 +1083,7 @@
1083 1083  Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
1084 1084  )))
1085 1085  
1082 +
1086 1086  == 4.3  Get Firmware Version Info ==
1087 1087  
1088 1088  Feature: use downlink to get firmware version.
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0