<
From version < 77.75 >
edited by Xiaoling
on 2022/06/10 09:23
To version < 77.59 >
edited by Xiaoling
on 2022/06/10 09:11
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -658,17 +658,14 @@
658 658  
659 659   Yy4 yy4: AC2 or AV2 high limit.
660 660  
661 -
662 662  **Example1**: AA 00 13 88 00 00 00 00 00 00
663 663  
664 664  Same as AT+AVLIM=5000,0,0,0   (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore)
665 665  
666 -
667 667  **Example2**: AA 02 01 00
668 668  
669 669  Same as AT+ DTRI =1,0  (Enable DI1 trigger / disable DI2 trigger)
670 670  
671 -
672 672  (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:**
673 673  
674 674  MOD6 Payload : total 11 bytes payload
... ... @@ -675,7 +675,6 @@
675 675  
676 676  [[image:image-20220524085923-1.png]]
677 677  
678 -
679 679  (% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if trigger is set for this part. Totally 1byte as below
680 680  
681 681  [[image:image-20220524090106-2.png]]
... ... @@ -682,7 +682,6 @@
682 682  
683 683  * Each bits shows if the corresponding trigger has been configured.
684 684  
685 -
686 686  **Example:**
687 687  
688 688  10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW
... ... @@ -694,7 +694,6 @@
694 694  
695 695  * Each bits shows which status has been trigger on this uplink.
696 696  
697 -
698 698  **Example:**
699 699  
700 700  10000000: Means this packet is trigger by AC1_LOW. Means voltage too low.
... ... @@ -706,7 +706,6 @@
706 706  
707 707  * Each bits shows which status has been trigger on this uplink.
708 708  
709 -
710 710  **Example:**
711 711  
712 712  00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
... ... @@ -746,8 +746,6 @@
746 746  
747 747  * (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L.  User can see these commands below:
748 748  
749 -
750 -
751 751  === 3.4.1 Common Commands ===
752 752  
753 753  They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.5.4, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
... ... @@ -769,7 +769,6 @@
769 769  
770 770  **Example: **AT+TDC=30000. Means set interval to 30 seconds
771 771  
772 -
773 773  * Downlink Payload (prefix 0x01):
774 774  
775 775  (% class="box infomessage" %)
... ... @@ -792,7 +792,6 @@
792 792  
793 793  **Example**: AT+MOD=2. Set work mode to Double DI counting mode
794 794  
795 -
796 796  * Downlink Payload (prefix 0x0A):
797 797  
798 798  (% class="box infomessage" %)
... ... @@ -808,7 +808,6 @@
808 808  
809 809  There is no AT Command to poll uplink
810 810  
811 -
812 812  * Downlink Payload (prefix 0x08):
813 813  
814 814  (% class="box infomessage" %)
... ... @@ -835,7 +835,6 @@
835 835  
836 836  0: Disable Trigger Mode
837 837  
838 -
839 839  * Downlink Payload (prefix 0x0A 06):
840 840  
841 841  (% class="box infomessage" %)
... ... @@ -853,7 +853,6 @@
853 853  
854 854  There is no AT Command for this feature.
855 855  
856 -
857 857  * Downlink Payload (prefix 0x AB 06):
858 858  
859 859  (% class="box infomessage" %)
... ... @@ -874,7 +874,6 @@
874 874  **Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
875 875  )))
876 876  
877 -
878 878  **Example:**
879 879  
880 880  AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
... ... @@ -903,12 +903,10 @@
903 903  
904 904  b : delay timing.
905 905  
906 -
907 907  **Example:**
908 908  
909 909  AT+TRIG1=1,100(set DI1 port to trigger on high level, valid signal is 100ms )
910 910  
911 -
912 912  * Downlink Payload (prefix 0x09 01 ):
913 913  
914 914  (% class="box infomessage" %)
... ... @@ -933,12 +933,10 @@
933 933  
934 934  b : delay timing.
935 935  
936 -
937 937  **Example:**
938 938  
939 939  AT+TRIG2=0,100(set DI1 port to trigger on low level, valid signal is 100ms )
940 940  
941 -
942 942  * Downlink Payload (prefix 0x09 02 ):
943 943  
944 944  (% class="box infomessage" %)
... ... @@ -959,7 +959,6 @@
959 959  **AT+ACLIM. **
960 960  )))
961 961  
962 -
963 963  * Downlink Payload (prefix 0xAA 01 ):
964 964  
965 965  (% class="box infomessage" %)
... ... @@ -980,7 +980,6 @@
980 980  **AT+AVLIM. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]**
981 981  )))
982 982  
983 -
984 984  * Downlink Payload (prefix 0xAA 00 ):
985 985  
986 986  (% class="box infomessage" %)
... ... @@ -1001,7 +1001,6 @@
1001 1001  **AT+ATDC=5. Device won’t response the second trigger within 5 minute after the first trigger.**
1002 1002  )))
1003 1003  
1004 -
1005 1005  * Downlink Payload (prefix 0xAC ):
1006 1006  
1007 1007  (% class="box infomessage" %)
... ... @@ -1017,7 +1017,6 @@
1017 1017  
1018 1018  There is no AT Command to control Digital Output
1019 1019  
1020 -
1021 1021  * Downlink Payload (prefix 0x02):
1022 1022  
1023 1023  (% class="box infomessage" %)
... ... @@ -1051,7 +1051,6 @@
1051 1051  
1052 1052  There is no AT Command to control Digital Output
1053 1053  
1054 -
1055 1055  * Downlink Payload (prefix 0xA9):
1056 1056  
1057 1057  (% class="box infomessage" %)
... ... @@ -1071,22 +1071,18 @@
1071 1071  
1072 1072  00: DO pins will change to an inverter state after timeout 
1073 1073  
1074 -
1075 1075  (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Ports status:
1076 1076  
1077 1077  [[image:image-20220524093238-6.png]]
1078 1078  
1079 -
1080 1080  (% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Ports status:
1081 1081  
1082 1082  [[image:image-20220524093328-7.png]]
1083 1083  
1084 -
1085 1085  (% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Ports status:
1086 1086  
1087 1087  [[image:image-20220524093351-8.png]]
1088 1088  
1089 -
1090 1090  (% style="color:#4f81bd" %)**Sixth and Seventh Byte**:
1091 1091  
1092 1092   Latching time. Unit: ms
... ... @@ -1093,7 +1093,6 @@
1093 1093  
1094 1094  Device will upload a packet if downlink code executes successfully.
1095 1095  
1096 -
1097 1097  **Example payload:**
1098 1098  
1099 1099  **~1. A9 01 01 01 01 07 D0**
... ... @@ -1114,13 +1114,12 @@
1114 1114  
1115 1115  
1116 1116  
1117 -==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
1088 +=== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ===
1118 1118  
1119 1119  * AT Command:
1120 1120  
1121 1121  There is no AT Command to control Relay Output
1122 1122  
1123 -
1124 1124  * Downlink Payload (prefix 0x03):
1125 1125  
1126 1126  (% class="box infomessage" %)
... ... @@ -1150,7 +1150,6 @@
1150 1150  
1151 1151  There is no AT Command to control Relay Output
1152 1152  
1153 -
1154 1154  * Downlink Payload (prefix 0x05):
1155 1155  
1156 1156  (% class="box infomessage" %)
... ... @@ -1168,17 +1168,14 @@
1168 1168  
1169 1169  00: Relays will change to an inverter state after timeout
1170 1170  
1171 -
1172 1172  (% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
1173 1173  
1174 1174  [[image:image-20220524093831-10.png]]
1175 1175  
1176 -
1177 1177  (% style="color:#4f81bd" %)**Fourth/Fifth Bytes(cc)**(%%): Latching time. Unit: ms
1178 1178  
1179 1179  Device will upload a packet if downlink code executes successfully.
1180 1180  
1181 -
1182 1182  **Example payload:**
1183 1183  
1184 1184  **~1. 05 01 11 07 D0**
... ... @@ -1210,7 +1210,6 @@
1210 1210  **AT+VOLMAX    ~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]**
1211 1211  )))
1212 1212  
1213 -
1214 1214  * Downlink Payload (prefix 0xA5):
1215 1215  
1216 1216  (% class="box infomessage" %)
... ... @@ -1237,7 +1237,6 @@
1237 1237  
1238 1238  Bb cc dd ee: number to be set
1239 1239  
1240 -
1241 1241  * Downlink Payload (prefix 0xA8):
1242 1242  
1243 1243  (% class="box infomessage" %)
... ... @@ -1290,16 +1290,17 @@
1290 1290  )))
1291 1291  
1292 1292  
1257 +
1293 1293  == 3.5 Integrate with Mydevice ==
1294 1294  
1295 1295  Mydevices provides a human friendly interface to show the sensor data, once we have data in TTN, we can use Mydevices to connect to TTN and see the data in Mydevices. Below are the steps:
1296 1296  
1297 1297  (((
1298 -(% style="color:blue" %)**Step 1**(%%): Be sure that your device is programmed and properly connected to the network at this time.
1263 +**Step 1**: Be sure that your device is programmed and properly connected to the network at this time.
1299 1299  )))
1300 1300  
1301 1301  (((
1302 -(% style="color:blue" %)**Step 2**(%%): To configure the Application to forward data to Mydevices you will need to add integration. To add the Mydevices integration, perform the following steps:
1267 +**Step 2**: To configure the Application to forward data to Mydevices you will need to add integration. To add the Mydevices integration, perform the following steps:
1303 1303  )))
1304 1304  
1305 1305  [[image:1653356737703-362.png||height="232" width="732"]]
... ... @@ -1306,13 +1306,12 @@
1306 1306  
1307 1307  [[image:image-20220524094641-11.png||height="390" width="723"]]
1308 1308  
1309 -
1310 1310  [[image:image-20220524094641-12.png||height="402" width="718"]]
1311 1311  
1312 1312  
1313 -(% style="color:blue" %)**Step 3**(%%): Create an account or log in Mydevices.
1277 +**Step 3**: Create an account or log in Mydevices.
1314 1314  
1315 -(% style="color:blue" %)**Step 4**(%%): Search LT-22222-L(for both LT-22222-L / LT-33222-L) and add DevEUI.(% style="display:none" %)
1279 +**Step 4**: Search LT-22222-L(for both LT-22222-L / LT-33222-L) and add DevEUI.(% style="display:none" %)
1316 1316  
1317 1317  Search under The things network
1318 1318  
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0