Skip to Content
Last modified by Mengting Qiu on 2025/06/04 18:42
From version 230.13
edited by Xiaoling
on 2024/12/09 10:18
Change comment: There is no comment for this version
To version 215.1
edited by Dilisi S
on 2024/11/24 05:05
Change comment: fix formatting

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.pradeeka
Content
... ... @@ -21,7 +21,6 @@
21 21  
22 22  == 1.1 What is the LT-22222-L I/O Controller? ==
23 23  
24 -
25 25  (((
26 26  (((
27 27  {{info}}
... ... @@ -55,10 +55,8 @@
55 55  (% class="wikigeneratedid" %)
56 56  [[image:lorawan-nw.jpg||height="354" width="900"]]
57 57  
58 -
59 59  == 1.2 Specifications ==
60 60  
61 -
62 62  (% style="color:#037691" %)**Hardware System:**
63 63  
64 64  * STM32L072xxxx MCU
... ... @@ -98,10 +98,8 @@
98 98  * Automatic RF Sense and CAD with ultra-fast AFC.
99 99  * Packet engine up to 256 bytes with CRC.
100 100  
101 -
102 102  == 1.3 Features ==
103 103  
104 -
105 105  * LoRaWAN Class A & Class C modes
106 106  * Optional Customized LoRa Protocol
107 107  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
... ... @@ -110,10 +110,8 @@
110 110  * Firmware upgradable via program port
111 111  * Counting
112 112  
113 -
114 114  == 1.4 Applications ==
115 115  
116 -
117 117  * Smart buildings & home automation
118 118  * Logistics and supply chain management
119 119  * Smart metering
... ... @@ -121,16 +121,13 @@
121 121  * Smart cities
122 122  * Smart factory
123 123  
124 -
125 125  == 1.5 Hardware Variants ==
126 126  
127 -
128 -(% border="1" cellspacing="3" style="width:510px" %)
129 -|(% style="background-color:#4f81bd; color:white; width:94px" %)**Model**|(% style="background-color:#4f81bd; color:white; width:172px" %)**Photo**|(% style="background-color:#4f81bd; color:white; width:244px" %)**Description**
130 -|(% style="width:94px" %)**LT-22222-L**|(% style="width:172px" %)(((
131 -(% style="text-align:center" %)
132 -[[image:lt33222-l.jpg||height="110" width="95"]]
133 -)))|(% style="width:256px" %)(((
119 +(% style="width:524px" %)
120 +|(% style="width:94px" %)**Model**|(% style="width:98px" %)**Photo**|(% style="width:329px" %)**Description**
121 +|(% style="width:94px" %)**LT33222-L**|(% style="width:98px" %)(((
122 +
123 +)))|(% style="width:329px" %)(((
134 134  * 2 x Digital Input (Bi-direction)
135 135  * 2 x Digital Output
136 136  * 2 x Relay Output (5A@250VAC / 30VDC)
... ... @@ -139,12 +139,10 @@
139 139  * 1 x Counting Port
140 140  )))
141 141  
142 -
143 143  = 2. Assembling the device =
144 144  
145 145  == 2.1 Connecting the antenna ==
146 146  
147 -
148 148  Connect the LoRa antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper screw terminal block. Secure the antenna by tightening it clockwise.
149 149  
150 150  {{warning}}
... ... @@ -151,37 +151,35 @@
151 151  **Warning! Do not power on the device without connecting the antenna.**
152 152  {{/warning}}
153 153  
154 -
155 155  == 2.2 Terminals ==
156 156  
157 -
158 158  The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals.
159 159  
160 160  **Upper screw terminal block (from left to right):**
161 161  
162 -(% style="width:385px" %)
163 -|=(% style="width: 139px;" %)Screw Terminal|=(% style="width: 242px;" %)Function
164 -|(% style="width:139px" %)GND|(% style="width:242px" %)Ground
165 -|(% style="width:139px" %)VIN|(% style="width:242px" %)Input Voltage
166 -|(% style="width:139px" %)AVI2|(% style="width:242px" %)Analog Voltage Input Terminal 2
167 -|(% style="width:139px" %)AVI1|(% style="width:242px" %)Analog Voltage Input Terminal 1
168 -|(% style="width:139px" %)ACI2|(% style="width:242px" %)Analog Current Input Terminal 2
169 -|(% style="width:139px" %)ACI1|(% style="width:242px" %)Analog Current Input Terminal 1
148 +(% style="width:634px" %)
149 +|=(% style="width: 295px;" %)Screw Terminal|=(% style="width: 338px;" %)Function
150 +|(% style="width:295px" %)GND|(% style="width:338px" %)Ground
151 +|(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage
152 +|(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2
153 +|(% style="width:295px" %)AVI1|(% style="width:338px" %)Analog Voltage Input Terminal 1
154 +|(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2
155 +|(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1
170 170  
171 171  **Lower screw terminal block (from left to right):**
172 172  
173 -(% style="width:257px" %)
174 -|=(% style="width: 125px;" %)Screw Terminal|=(% style="width: 128px;" %)Function
175 -|(% style="width:125px" %)RO1-2|(% style="width:128px" %)Relay Output 1
176 -|(% style="width:125px" %)RO1-1|(% style="width:128px" %)Relay Output 1
177 -|(% style="width:125px" %)RO2-2|(% style="width:128px" %)Relay Output 2
178 -|(% style="width:125px" %)RO2-1|(% style="width:128px" %)Relay Output 2
179 -|(% style="width:125px" %)DI2+|(% style="width:128px" %)Digital Input 2
180 -|(% style="width:125px" %)DI2-|(% style="width:128px" %)Digital Input 2
181 -|(% style="width:125px" %)DI1+|(% style="width:128px" %)Digital Input 1
182 -|(% style="width:125px" %)DI1-|(% style="width:128px" %)Digital Input 1
183 -|(% style="width:125px" %)DO2|(% style="width:128px" %)Digital Output 2
184 -|(% style="width:125px" %)DO1|(% style="width:128px" %)Digital Output 1
159 +(% style="width:633px" %)
160 +|=(% style="width: 296px;" %)Screw Terminal|=(% style="width: 334px;" %)Function
161 +|(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1
162 +|(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1
163 +|(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2
164 +|(% style="width:296px" %)RO2-1|(% style="width:334px" %)Relay Output 2
165 +|(% style="width:296px" %)DI2+|(% style="width:334px" %)Digital Input 2
166 +|(% style="width:296px" %)DI2-|(% style="width:334px" %)Digital Input 2
167 +|(% style="width:296px" %)DI1+|(% style="width:334px" %)Digital Input 1
168 +|(% style="width:296px" %)DI1-|(% style="width:334px" %)Digital Input 1
169 +|(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
170 +|(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
185 185  
186 186  == 2.3 Connecting LT-22222-L to a Power Source ==
187 187  
... ... @@ -188,7 +188,7 @@
188 188  The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s **positive wire** to the **VIN** and the **negative wire** to the **GND** screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered.
189 189  
190 190  {{warning}}
191 -**We recommend that you power on the LT-22222-L after adding its registration information to the LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.**
177 +**We recommend that you power on the LT-22222-L after configuring its registration information with a LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.**
192 192  {{/warning}}
193 193  
194 194  
... ... @@ -251,7 +251,7 @@
251 251  *** **Profile (Region)**: Select the region that matches your device.
252 252  ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
253 253  
254 -[[image:lt-22222-l-dev-repo-reg-p1.png]]
240 +[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
255 255  
256 256  
257 257  * Register end device page continued...
... ... @@ -261,7 +261,7 @@
261 261  ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
262 262  ** Under **After registration**, select the **View registered end device** option.
263 263  
264 -[[image:lt-22222-l-dev-repo-reg-p2.png]]
250 +[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
265 265  
266 266  
267 267  ==== 3.2.2.3 Adding device manually ====
... ... @@ -275,7 +275,7 @@
275 275  ** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
276 276  ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
277 277  
278 -[[image:lt-22222-l-manually-p1.png]]
264 +[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
279 279  
280 280  
281 281  * Register end device page continued...
... ... @@ -286,13 +286,13 @@
286 286  ** Under **After registration**, select the **View registered end device** option.
287 287  ** Click the **Register end device** button.
288 288  
289 -[[image:lt-22222-l-manually-p2.png]]
275 +[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
290 290  
291 291  
292 292  You will be navigated to the **Device overview** page.
293 293  
294 294  
295 -[[image:lt-22222-device-overview.png]]
281 +[[image:lt-22222-device-overview.png||height="625" width="1000"]]
296 296  
297 297  
298 298  ==== 3.2.2.4 Joining ====
... ... @@ -302,10 +302,9 @@
302 302  Now power on your LT-22222-L. The **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** The Things Stack network server. The **TX LED** will be on for **5 seconds** after joining the network. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server.
303 303  
304 304  
305 -[[image:lt-22222-l-joining.png]]
291 +[[image:lt-22222-join-network.png||height="625" width="1000"]]
306 306  
307 307  
308 -
309 309  ==== 3.2.2.5 Uplinks ====
310 310  
311 311  
... ... @@ -322,15 +322,9 @@
322 322  The Things Stack provides two levels of payload formatters: application level and device level. The device-level payload formatters **override **the application-level payload formatters.
323 323  {{/info}}
324 324  
325 -[[image:lt-22222-ul-payload-fmt.png]]
310 +[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
326 326  
327 327  
328 -We also have a payload formatter that resolves some decoding issues present in the Device Repository formatter. You can add it under the Custom JavaScript formatter. It can be found [[here>>https://github.com/dragino/dragino-end-node-decoder/blob/main/LT22222-L/v1.6_decoder_ttn%20.txt]]:
329 -
330 -(% class="wikigeneratedid" %)
331 -[[image:lt-22222-l-js-custom-payload-formatter.png]]
332 -
333 -
334 334  ==== 3.2.2.6 Downlinks ====
335 335  
336 336  When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
... ... @@ -619,11 +619,11 @@
619 619  
620 620  (% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)**
621 621  
622 -(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), the counter increases by 1)**
601 +(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
623 623  
624 -(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If the AVI1 voltage is lower than VOLMAX (20000mV =20V), counter increases by 1)**
603 +(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
625 625  
626 -(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), counter increases by 1)**
605 +(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
627 627  )))
628 628  
629 629  
... ... @@ -742,9 +742,9 @@
742 742  
743 743  (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
744 744  
745 -**Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
724 +Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
746 746  
747 -**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
726 +Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
748 748  
749 749   AA: Type Code for this downlink Command:
750 750  
... ... @@ -773,7 +773,7 @@
773 773  
774 774  MOD6 Payload: total of 11 bytes
775 775  
776 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
755 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
777 777  |(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:69px" %)**1**|(% style="background-color:#4f81bd; color:white; width:69px" %)**1**|(% style="background-color:#4f81bd; color:white; width:109px" %)**1**|(% style="background-color:#4f81bd; color:white; width:49px" %)**6**|(% style="background-color:#4f81bd; color:white; width:109px" %)**1**|(% style="background-color:#4f81bd; color:white; width:50px" %)**1**
778 778  |Value|(((
779 779  TRI_A FLAG
... ... @@ -787,7 +787,7 @@
787 787  
788 788  (% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
789 789  
790 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
769 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
791 791  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
792 792  |(((
793 793  AV1_LOW
... ... @@ -811,12 +811,12 @@
811 811  
812 812  **Example:**
813 813  
814 -10100000: This means the system is configured to use the triggers AV1_LOW and AV2_LOW.
793 +10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW
815 815  
816 816  
817 817  (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
818 818  
819 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
798 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
820 820  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
821 821  |(((
822 822  AV1_LOW
... ... @@ -840,31 +840,31 @@
840 840  
841 841  **Example:**
842 842  
843 -10000000: The uplink is triggered by AV1_LOW, indicating that the voltage is too low.
822 +10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.
844 844  
845 845  
846 846  (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
847 847  
848 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
849 -|(% style="width:50px" %)**bit 7**|(% style="width:50px" %)**bit 6**|(% style="width:50px" %)**bit 5**|(% style="width:50px" %)**bit 4**|(% style="width:90px" %)**bit 3**|(% style="width:80px" %)**bit 2**|(% style="width:90px" %)**bit 1**|(% style="width:95px" %)**bit 0**
850 -|(% style="width:49px" %)N/A|(% style="width:53px" %)N/A|(% style="width:53px" %)N/A|(% style="width:55px" %)N/A|(% style="width:99px" %)DI2_STATUS|(% style="width:83px" %)DI2_FLAG|(% style="width:98px" %)DI1_STATUS|(% style="width:85px" %)DI1_FLAG
827 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:674px" %)
828 +|(% style="width:64px" %)**bit 7**|(% style="width:68px" %)**bit 6**|(% style="width:63px" %)**bit 5**|(% style="width:66px" %)**bit 4**|(% style="width:109px" %)**bit 3**|(% style="width:93px" %)**bit 2**|(% style="width:109px" %)**bit 1**|(% style="width:99px" %)**bit 0**
829 +|(% style="width:64px" %)N/A|(% style="width:68px" %)N/A|(% style="width:63px" %)N/A|(% style="width:66px" %)N/A|(% style="width:109px" %)DI2_STATUS|(% style="width:93px" %)DI2_FLAG|(% style="width:109px" %)DI1_STATUS|(% style="width:99px" %)DI1_FLAG
851 851  
852 -* Each bit shows which status has been triggered on this uplink.
831 +* Each bits shows which status has been triggered on this uplink.
853 853  
854 854  **Example:**
855 855  
856 -00000111: This means both DI1 and DI2 triggers are enabled, and this packet is trigger by DI1.
835 +00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
857 857  
858 -00000101: This means both DI1 and DI2 triggers are enabled.
837 +00000101: Means both DI1 and DI2 trigger are enabled.
859 859  
860 860  
861 -(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled.
840 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable.
862 862  
863 -Downlink command to poll/request MOD6 status:
842 +Downlink command to poll MOD6 status:
864 864  
865 865  **AB 06**
866 866  
867 -When device receives this command, it will send the MOD6 payload.
846 +When device got this command, it will send the MOD6 payload.
868 868  
869 869  
870 870  === 3.3.7 Payload Decoder ===
... ... @@ -878,7 +878,6 @@
878 878  
879 879  == 3.4 ​Configure LT-22222-L via AT Commands or Downlinks ==
880 880  
881 -
882 882  (((
883 883  You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks.
884 884  )))
... ... @@ -895,22 +895,17 @@
895 895  
896 896  === 3.4.1 Common commands ===
897 897  
898 -
899 899  (((
900 900  These are available for each sensors and include actions such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]s.
901 -
902 -
903 903  )))
904 904  
905 905  === 3.4.2 Sensor-related commands ===
906 906  
907 -
908 908  These commands are specially designed for the LT-22222-L. Commands can be sent to the device using options such as an AT command or a LoRaWAN downlink payload.
909 909  
910 910  
911 911  ==== 3.4.2.1 Set Transmit/Uplink Interval ====
912 912  
913 -
914 914  Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
915 915  
916 916  (% style="color:#037691" %)**AT command**
... ... @@ -917,15 +917,8 @@
917 917  
918 918  (% border="2" style="width:500px" %)
919 919  |**Command**|AT+TDC=<time>
920 -|**Parameters**|**time **: uplink interval in milliseconds
921 -|**Get**|AT+TDC=?
922 -|**Response**|(((
923 -current uplink interval
924 -
925 -OK
926 -)))
927 -|**Set**|AT+TDC=<time>
928 -|**Response**|OK
893 +|**Response**|
894 +|**Parameters**|**time** : uplink interval is in **milliseconds**
929 929  |**Example**|(((
930 930  AT+TDC=30000
931 931  
... ... @@ -941,7 +941,7 @@
941 941  |**Parameters**|(((
942 942  **prefix** : 0x01
943 943  
944 -**time** : uplink interval in **seconds**, represented by **3  bytes** in **hexadecimal**.
910 +**time** : uplink interval is in **seconds**, represented by **3  bytes** in **hexadecimal**.
945 945  )))
946 946  |**Example**|(((
947 947  01 **00 00 1E**
... ... @@ -957,13 +957,13 @@
957 957  
958 958  ==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
959 959  
960 -
961 961  Sets the working mode.
962 962  
963 963  (% style="color:#037691" %)**AT command**
964 964  
965 965  (% border="2" style="width:500px" %)
966 -|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MOD=<working_mode>
931 +|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE=<working_mode>
932 +|(% style="width:97px" %)**Response**|(% style="width:413px" %)
967 967  |(% style="width:97px" %)**Parameters**|(% style="width:413px" %)(((
968 968  **working_mode** :
969 969  
... ... @@ -979,18 +979,6 @@
979 979  
980 980  6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5
981 981  )))
982 -|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=?
983 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
984 -Current working mode
985 -
986 -OK
987 -)))
988 -|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode>
989 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
990 -Attention:Take effect after ATZ
991 -
992 -OK
993 -)))
994 994  |(% style="width:97px" %)**Example**|(% style="width:413px" %)(((
995 995  AT+MOD=2
996 996  
... ... @@ -1013,9 +1013,8 @@
1013 1013  Sets the device to working mode 2 (Double DI Counting + DO + RO)
1014 1014  )))
1015 1015  
1016 -==== 3.4.2.3 Request an uplink from the device ====
970 +==== 3.4.2.3 Poll an uplink ====
1017 1017  
1018 -
1019 1019  Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.
1020 1020  
1021 1021  (% style="color:#037691" %)**AT command**
... ... @@ -1035,7 +1035,6 @@
1035 1035  
1036 1036  ==== 3.4.2.4 Enable/Disable Trigger Mode ====
1037 1037  
1038 -
1039 1039  Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
1040 1040  
1041 1041  (% style="color:#037691" %)**AT Command**
... ... @@ -1071,11 +1071,10 @@
1071 1071  Enable trigger mode for the current working mode
1072 1072  )))
1073 1073  
1074 -==== 3.4.2.5 Request trigger settings ====
1026 +==== 3.4.2.5 Poll trigger settings ====
1075 1075  
1028 +Polls the trigger settings.
1076 1076  
1077 -Requests the trigger settings.
1078 -
1079 1079  (% style="color:#037691" %)**AT Command:**
1080 1080  
1081 1081  There is no AT Command available for this feature.
... ... @@ -1093,7 +1093,6 @@
1093 1093  
1094 1094  ==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ====
1095 1095  
1096 -
1097 1097  Enable or disable DI1/DI2/DI3 as a trigger.
1098 1098  
1099 1099  (% style="color:#037691" %)**AT Command**
... ... @@ -1148,9 +1148,9 @@
1148 1148  
1149 1149  ==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ====
1150 1150  
1151 -
1152 1152  Sets DI1 or DI3 (for LT-33222-L) as a trigger.
1153 1153  
1103 +
1154 1154  (% style="color:#037691" %)**AT Command**
1155 1155  
1156 1156  (% border="2" style="width:500px" %)
... ... @@ -1187,9 +1187,9 @@
1187 1187  
1188 1188  ==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
1189 1189  
1190 -
1191 1191  Sets DI2 as a trigger.
1192 1192  
1142 +
1193 1193  (% style="color:#037691" %)**AT Command**
1194 1194  
1195 1195  (% border="2" style="width:500px" %)
... ... @@ -1221,7 +1221,6 @@
1221 1221  
1222 1222  ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
1223 1223  
1224 -
1225 1225  Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1226 1226  
1227 1227  (% style="color:#037691" %)**AT Command**
... ... @@ -1271,7 +1271,6 @@
1271 1271  
1272 1272  ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
1273 1273  
1274 -
1275 1275  Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1276 1276  
1277 1277  (% style="color:#037691" %)**AT Command**
... ... @@ -1319,7 +1319,6 @@
1319 1319  
1320 1320  ==== 3.4.2.11 Trigger – Set minimum interval ====
1321 1321  
1322 -
1323 1323  Sets the AV and AC trigger minimum interval. The device won't respond to a second trigger within this set time after the first trigger.
1324 1324  
1325 1325  (% style="color:#037691" %)**AT Command**
... ... @@ -1355,7 +1355,6 @@
1355 1355  
1356 1356  ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
1357 1357  
1358 -
1359 1359  Controls the digital outputs DO1, DO2, and DO3
1360 1360  
1361 1361  (% style="color:#037691" %)**AT Command**
... ... @@ -1386,11 +1386,11 @@
1386 1386  (((
1387 1387  01: Low,  00: High,  11: No action
1388 1388  
1389 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:383px" %)
1390 -|(% style="background-color:#4f81bd; color:white; width:126px" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white; width:85px" %)**DO1**|(% style="background-color:#4f81bd; color:white; width:86px" %)**DO2**|(% style="background-color:#4f81bd; color:white; width:86px" %)**DO3**
1391 -|(% style="width:126px" %)02  01  00  11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action
1392 -|(% style="width:126px" %)02  00  11  01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low
1393 -|(% style="width:126px" %)02  11  01  00|(% style="width:85px" %)No Action|(% style="width:86px" %)Low|(% style="width:86px" %)High
1335 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
1336 +|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**DO1**|(% style="background-color:#4f81bd; color:white" %)**DO2**|(% style="background-color:#4f81bd; color:white" %)**DO3**
1337 +|02  01  00  11|Low|High|No Action
1338 +|02  00  11  01|High|No Action|Low
1339 +|02  11  01  00|No Action|Low|High
1394 1394  )))
1395 1395  
1396 1396  (((
... ... @@ -1409,23 +1409,25 @@
1409 1409  
1410 1410  * (% style="color:#037691" %)**AT Command**
1411 1411  
1412 -There is no AT command to control the digital output.
1358 +There is no AT Command to control Digital Output
1413 1413  
1414 1414  
1415 1415  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
1416 1416  
1417 -(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control
1363 +(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Set DO1/DO2/DO3 output with time control
1418 1418  
1365 +
1419 1419  This is to control the digital output time of DO pin. Include four bytes:
1420 1420  
1421 -(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)
1368 +(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
1422 1422  
1423 -(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode
1370 +(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode
1424 1424  
1425 -**01:** DO pins revert to their original state after the timeout.
1426 -**00:** DO pins switch to an inverted state after the timeout.
1372 +01: DO pins will change back to original state after timeout.
1427 1427  
1374 +00: DO pins will change to an inverter state after timeout 
1428 1428  
1376 +
1429 1429  (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
1430 1430  
1431 1431  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
... ... @@ -1434,7 +1434,7 @@
1434 1434  |0x00|DO1 set to high
1435 1435  |0x11|DO1 NO Action
1436 1436  
1437 -(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:
1385 +(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:
1438 1438  
1439 1439  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1440 1440  |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
... ... @@ -1442,7 +1442,7 @@
1442 1442  |0x00|DO2 set to high
1443 1443  |0x11|DO2 NO Action
1444 1444  
1445 -(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:
1393 +(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:
1446 1446  
1447 1447  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1448 1448  |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
... ... @@ -1450,7 +1450,7 @@
1450 1450  |0x00|DO3 set to high
1451 1451  |0x11|DO3 NO Action
1452 1452  
1453 -(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms)
1401 +(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)
1454 1454  
1455 1455  
1456 1456  (% style="color:red" %)**Note: **
... ... @@ -1459,7 +1459,7 @@
1459 1459  
1460 1460   Before firmware v1.6.0, the latch time only supported 2 bytes.
1461 1461  
1462 -(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1410 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1463 1463  
1464 1464  
1465 1465  **Example payload:**
... ... @@ -1486,16 +1486,16 @@
1486 1486  
1487 1487  * (% style="color:#037691" %)**AT Command:**
1488 1488  
1489 -There is no AT Command to control the Relay Output
1437 +There is no AT Command to control Relay Output
1490 1490  
1491 1491  
1492 1492  * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
1493 1493  
1494 -(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Sets RO1/RO2 output
1442 +(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Set RO1/RO2 output
1495 1495  
1496 1496  
1497 1497  (((
1498 -If the payload is 0x030100, it means setting RO1 to close and RO2 to open.
1446 +If payload is 0x030100, it means setting RO1 to close and RO2 to open.
1499 1499  )))
1500 1500  
1501 1501  (((
... ... @@ -1513,29 +1513,28 @@
1513 1513  |03  00  01|Open|Close
1514 1514  )))
1515 1515  
1516 -(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1464 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
1517 1517  
1518 1518  
1519 1519  ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
1520 1520  
1521 -
1522 1522  Controls the relay output time.
1523 1523  
1524 1524  * (% style="color:#037691" %)**AT Command:**
1525 1525  
1526 -There is no AT Command to control the Relay Output
1473 +There is no AT Command to control Relay Output
1527 1527  
1528 1528  
1529 1529  * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1530 1530  
1531 -(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
1478 +(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Set RO1/RO2 relay with time control
1532 1532  
1533 1533  
1534 -This controls the relay output time and includes 4 bytes:
1481 +This is to control the relay output time. It includes four bytes:
1535 1535  
1536 -(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)
1483 +(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
1537 1537  
1538 -(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode
1485 +(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
1539 1539  
1540 1540  01: Relays will change back to their original state after timeout.
1541 1541  
... ... @@ -1542,12 +1542,12 @@
1542 1542  00: Relays will change to the inverter state after timeout.
1543 1543  
1544 1544  
1545 -(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status:
1492 +(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
1546 1546  
1547 1547  [[image:image-20221008095908-1.png||height="364" width="564"]]
1548 1548  
1549 1549  
1550 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes (cc)**(%%): Latching time. Unit: ms
1497 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms
1551 1551  
1552 1552  
1553 1553  (% style="color:red" %)**Note:**
... ... @@ -1557,7 +1557,7 @@
1557 1557   Before firmware v1.6.0, the latch time only supported 2 bytes.
1558 1558  
1559 1559  
1560 -(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1507 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1561 1561  
1562 1562  
1563 1563  **Example payload:**
... ... @@ -1716,9 +1716,8 @@
1716 1716  )))
1717 1717  |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
1718 1718  
1719 -==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ====
1666 +==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1720 1720  
1721 -
1722 1722  This command allows you to configure the device to save its counting result to internal flash memory at specified intervals. By setting a save time, the device will periodically store the counting data to prevent loss in case of power failure. The save interval can be adjusted to suit your requirements, with a minimum value of 30 seconds.
1723 1723  
1724 1724  (% style="color:#037691" %)**AT Command**
... ... @@ -1748,9 +1748,8 @@
1748 1748  Sets the device to save its counting results to the memory every 60 seconds.
1749 1749  )))
1750 1750  
1751 -==== 3.4.2.20 Reset saved RO and DO states ====
1697 +==== 3.4.2.20 Reset save RO DO state ====
1752 1752  
1753 -
1754 1754  This command allows you to reset the saved relay output (RO) and digital output (DO) states when the device joins the network. By configuring this setting, you can control whether the device should retain or reset the relay states after a reset and rejoin to the network.
1755 1755  
1756 1756  (% style="color:#037691" %)**AT Command**
... ... @@ -1775,6 +1775,7 @@
1775 1775  After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network.
1776 1776  )))
1777 1777  
1723 +
1778 1778  (% style="color:#037691" %)**Downlink Payload**
1779 1779  
1780 1780  (% border="2" style="width:500px" %)
... ... @@ -1800,7 +1800,6 @@
1800 1800  
1801 1801  ==== 3.4.2.21 Encrypted payload ====
1802 1802  
1803 -
1804 1804  This command allows you to configure whether the device should upload data in an encrypted format or in plaintext. By default, the device encrypts the payload before uploading. You can toggle this setting to either upload encrypted data or transmit it without encryption.
1805 1805  
1806 1806  (% style="color:#037691" %)**AT Command:**
... ... @@ -1830,7 +1830,6 @@
1830 1830  
1831 1831  ==== 3.4.2.22 Get sensor value ====
1832 1832  
1833 -
1834 1834  This command allows you to retrieve and optionally uplink sensor readings through the serial port.
1835 1835  
1836 1836  (% style="color:#037691" %)**AT Command**
... ... @@ -1860,7 +1860,6 @@
1860 1860  
1861 1861  ==== 3.4.2.23 Resetting the downlink packet count ====
1862 1862  
1863 -
1864 1864  This command manages how the node handles mismatched downlink packet counts. It offers two modes: one disables the reception of further downlink packets if discrepancies occur, while the other resets the downlink packet count to align with the server, ensuring continued communication.
1865 1865  
1866 1866  (% style="color:#037691" %)**AT Command**
... ... @@ -1939,33 +1939,43 @@
1939 1939  
1940 1940  ==== 3.4.2.25 Copy downlink to uplink ====
1941 1941  
1885 +This command enables the device to immediately uplink the content of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100.
1942 1942  
1943 -This command enables the device to immediately uplink the payload of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100.
1887 +* (% style="color:#037691" %)**AT Command**(%%)**:**
1944 1944  
1945 -(% style="color:#037691" %)**AT Command**(%%)**:**
1889 +(% style="color:blue" %)**AT+RPL=5**   (%%) ~/~/ After receiving the package from the server, it will immediately upload the content of the package to the server, the port number is 100.
1946 1946  
1947 -(% style="color:blue" %)**AT+RPL=5**   (%%) ~/~/ After receiving a downlink payload from the server, the device will immediately uplink the payload back to the server using port number 100.
1891 +Example：**aa xx xx xx xx**         ~/~/ aa indicates whether the configuration has changed, 00 is yes, 01 is no; xx xx xx xx are the bytes sent.
1948 1948  
1949 -Example：**aa xx xx xx xx**         ~/~/ **aa** indicates whether the configuration has changed: **00** means YES, and **01** means NO. **xx xx xx xx** are the bytes uplinked back.
1950 1950  
1951 -
1952 1952  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173747-6.png?width=1124&height=165&rev=1.1||alt="image-20220823173747-6.png"]]
1953 1953  
1954 1954  For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
1955 1955  
1956 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]]
1898 +(% border="2" style="width:500px" %)
1899 +|(% style="width:122px" %)**Command**|(% style="width:376px" %)(((
1900 +AT+RPL=5
1957 1957  
1958 -For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
1902 +After receiving a downlink packet from the server, the node immediately uplinks the content of the packet back to the server using port number 100.
1903 +)))
1904 +|(% style="width:122px" %)**Example**|(% style="width:376px" %)(((
1905 +Downlink:
1959 1959  
1907 +01 00 02 58
1960 1960  
1961 -(% style="color:#037691" %)**Downlink Payload**(%%)**:**
1909 +Uplink:
1962 1962  
1963 -There is no downlink option available for this feature.
1911 +01 01 00 02 58
1912 +)))
1964 1964  
1914 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]]
1965 1965  
1966 -==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
1916 +For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
1967 1967  
1968 1968  
1919 +
1920 +==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
1921 +
1969 1969  This command is used to query key information about the device, including its firmware version, frequency band, sub band, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device.
1970 1970  
1971 1971  * (((
... ... @@ -1984,13 +1984,10 @@
1984 1984  
1985 1985  == 3.5 Integrating with ThingsEye.io ==
1986 1986  
1987 -
1988 1988  The Things Stack application supports integration with ThingsEye.io. Once integrated, ThingsEye.io acts as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
1989 1989  
1990 -
1991 1991  === 3.5.1 Configuring The Things Stack ===
1992 1992  
1993 -
1994 1994  We use The Things Stack Sandbox in this example:
1995 1995  
1996 1996  * In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
... ... @@ -2002,12 +2002,10 @@
2002 2002  The username and  password (API key) you created here are required in the next section.
2003 2003  {{/info}}
2004 2004  
2005 -[[image:tts-mqtt-integration.png]]
1955 +[[image:tts-mqtt-integration.png||height="625" width="1000"]]
2006 2006  
2007 -
2008 2008  === 3.5.2 Configuring ThingsEye.io ===
2009 2009  
2010 -
2011 2011  The ThingsEye.io IoT platform is not open for self-registration at the moment. If you are interested in testing the platform, please send your project information to admin@thingseye.io, and we will create an account for you.
2012 2012  
2013 2013  * Login to your [[ThingsEye.io >>https://thingseye.io]]account.
... ... @@ -2014,7 +2014,7 @@
2014 2014  * Under the **Integrations center**, click **Integrations**.
2015 2015  * Click the **Add integration** button (the button with the **+** symbol).
2016 2016  
2017 -[[image:thingseye-io-step-1.png]]
1965 +[[image:thingseye-io-step-1.png||height="625" width="1000"]]
2018 2018  
2019 2019  
2020 2020  On the **Add integration** window, configure the following:
... ... @@ -2029,7 +2029,7 @@
2029 2029  ** Allow create devices or assets
2030 2030  * Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
2031 2031  
2032 -[[image:thingseye-io-step-2.png]]
1980 +[[image:thingseye-io-step-2.png||height="625" width="1000"]]
2033 2033  
2034 2034  
2035 2035  **Uplink data converter:**
... ... @@ -2040,7 +2040,7 @@
2040 2040  * Paste the uplink decoder function into the text area (first, delete the default code). The demo uplink decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Uplink_Converter.js]].
2041 2041  * Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
2042 2042  
2043 -[[image:thingseye-io-step-3.png]]
1991 +[[image:thingseye-io-step-3.png||height="625" width="1000"]]
2044 2044  
2045 2045  
2046 2046  **Downlink data converter (this is an optional step):**
... ... @@ -2051,7 +2051,7 @@
2051 2051  * Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Downlink_Converter.js]].
2052 2052  * Click the **Next** button. You will be navigated to the **Connection** tab.
2053 2053  
2054 -[[image:thingseye-io-step-4.png]]
2002 +[[image:thingseye-io-step-4.png||height="625" width="1000"]]
2055 2055  
2056 2056  
2057 2057  **Connection:**
... ... @@ -2066,21 +2066,20 @@
2066 2066  
2067 2067  * Click the **Add** button.
2068 2068  
2069 -[[image:thingseye-io-step-5.png]]
2017 +[[image:thingseye-io-step-5.png||height="625" width="1000"]]
2070 2070  
2071 2071  
2072 2072  Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings and correct any errors.
2073 2073  
2074 2074  
2075 -[[image:thingseye.io_integrationsCenter_integrations.png]]
2023 +[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
2076 2076  
2077 2077  
2078 2078  ==== 3.5.2.1 Viewing integration details ====
2079 2079  
2080 -
2081 2081  Click on your integration from the list. The **Integration details** window will appear with the **Details **tab selected. The **Details **tab shows all the settings you have provided for this integration.
2082 2082  
2083 -[[image:integration-details.png]]
2030 +[[image:integration-details.png||height="686" width="1000"]]
2084 2084  
2085 2085  
2086 2086  If you want to edit the settings you have provided, click on the **Toggle edit mode** button. Once you have done click on the **Apply changes **button.
... ... @@ -2089,32 +2089,28 @@
2089 2089  See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
2090 2090  {{/info}}
2091 2091  
2039 +==== **3.5.2.2 Viewing events** ====
2092 2092  
2093 -==== 3.5.2.2 Viewing events ====
2094 -
2095 -
2096 2096  The **Events **tab displays all the uplink messages from the LT-22222-L.
2097 2097  
2098 2098  * Select **Debug **from the **Event type** dropdown.
2099 2099  * Select the** time frame** from the **time window**.
2100 2100  
2101 -[[image:thingseye-events.png]]
2046 +[[image:thingseye-events.png||height="686" width="1000"]]
2102 2102  
2103 2103  
2104 2104  * To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
2105 2105  
2106 -[[image:thingseye-json.png]]
2051 +[[image:thingseye-json.png||width="1000"]]
2107 2107  
2108 2108  
2109 -==== 3.5.2.3 Deleting an integration ====
2054 +==== **3.5.2.3 Deleting an integration** ====
2110 2110  
2111 -
2112 2112  If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
2113 2113  
2114 2114  
2115 2115  ==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
2116 2116  
2117 -
2118 2118  This will be added soon.
2119 2119  
2120 2120  
... ... @@ -2123,7 +2123,7 @@
2123 2123  === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
2124 2124  
2125 2125  
2126 -Supports** NPN-type **sensors.
2069 +Supports NPN-type sensors.
2127 2127  
2128 2128  [[image:1653356991268-289.png]]
2129 2129  
... ... @@ -2245,15 +2245,15 @@
2245 2245  )))
2246 2246  
2247 2247  
2248 -(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor
2191 +(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
2249 2249  
2250 -From the DI port circuit above, activating the photocoupler requires a voltage difference between the DI+ and DI- ports. However, the Dry Contact sensor is a passive component and cannot provide this voltage difference on its own.
2193 +From the DI port circuit above, you can see that activating the photocoupler requires a voltage difference between the DI+ and DI- ports. However, the Dry Contact sensor is a passive component and cannot provide this voltage difference.
2251 2251  
2252 -To detect a Dry Contact, you can supply a power source to one of the pins of the Dry Contact. A reference circuit diagram is shown below.
2195 +To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram.
2253 2253  
2254 2254  [[image:image-20230616235145-1.png]]
2255 2255  
2256 -(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector
2199 +(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
2257 2257  
2258 2258  [[image:image-20240219115718-1.png]]
2259 2259  
... ... @@ -2329,9 +2329,8 @@
2329 2329  [[image:image-20220524100215-10.png||height="382" width="723"]]
2330 2330  
2331 2331  
2332 -== 3.7 LED Indicators ==
2275 +== 3.7 LEDs Indicators ==
2333 2333  
2334 -
2335 2335  The table below lists the behavior of LED indicators for each port function.
2336 2336  
2337 2337  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
... ... @@ -2364,22 +2364,18 @@
2364 2364  
2365 2365  = 4. Using AT Commands =
2366 2366  
2367 -
2368 2368  The LT-22222-L supports programming using AT Commands.
2369 2369  
2370 -
2371 2371  == 4.1 Connecting the LT-22222-L to a PC ==
2372 2372  
2373 -
2374 2374  (((
2375 -You can use a USB-to-TTL adapter/converter along with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below.
2314 +You can use a USB-to-TTL adapter along with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below.
2376 2376  
2377 -[[image:usb-ttl-audio-jack-connection.jpg]]
2378 -
2379 -
2316 +[[image:usb-ttl-programming.png]]
2380 2380  )))
2381 2381  
2382 2382  
2320 +
2383 2383  (((
2384 2384  On the PC, you need to set the (% style="color:#4f81bd" %)**serial tool **(%%)(such as [[PuTTY>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]] or [[SecureCRT>>https://www.vandyke.com/cgi-bin/releases.php?product=securecrt]]) to a baud rate of (% style="color:green" %)**9600**(%%) to access the serial console of LT-22222-L. Access to AT commands is disabled by default, and a password (default: (% style="color:green" %)**123456**)(%%) must be entered to enable AT command access, as shown below:
2385 2385  )))
... ... @@ -2390,10 +2390,7 @@
2390 2390  (((
2391 2391  You can find more details in the [[AT Command Manual>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
2392 2392  
2393 -
2394 2394  == 4.2 LT-22222-L related AT commands ==
2395 -
2396 -
2397 2397  )))
2398 2398  
2399 2399  (((
... ... @@ -2412,39 +2412,39 @@
2412 2412  * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
2413 2413  * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
2414 2414  * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
2415 -* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2416 -* **##AT+DR##**:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
2417 -* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2418 -* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)
2419 -* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency
2420 -* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2421 -* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2422 -* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2423 -* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2424 -* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2425 -* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2426 -* ##**AT+NWKID**##: Get or set the Network ID
2427 -* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)
2428 -* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)
2429 -* ##**AT+CLASS**##: Get or set the Device Class
2430 -* ##**AT+JOIN**##: Join network
2431 -* ##**AT+NJS**##: Get OTAA Join Status
2432 -* ##**AT+SENDB**##: Send hexadecimal data along with the application port
2433 -* ##**AT+SEND**##: Send text data along with the application port
2434 -* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)
2435 -* ##**AT+RECV**##: Print last received data in raw format
2436 -* ##**AT+VER**##: Get current image version and Frequency Band
2437 -* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)
2438 -* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)
2439 -* ##**AT+SNR**##: Get the SNR of the last received packet
2440 -* ##**AT+RSSI**##: Get the RSSI of the last received packet
2441 -* ##**AT+TDC**##: Get or set the application data transmission interval in ms
2442 -* ##**AT+PORT**##: Get or set the application port
2443 -* ##**AT+DISAT**##: Disable AT commands
2444 -* ##**AT+PWORD**##: Set password, max 9 digits
2445 -* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2446 -* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN470
2447 -* ##**AT+CFG**##: Print all settings
2350 +* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2351 +* AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
2352 +* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2353 +* AT+PNM: Get or set the public network mode. (0: off, 1: on)
2354 +* AT+RX2FQ: Get or set the Rx2 window frequency
2355 +* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2356 +* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2357 +* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2358 +* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2359 +* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2360 +* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2361 +* AT+NWKID: Get or set the Network ID
2362 +* AT+FCU: Get or set the Frame Counter Uplink (FCntUp)
2363 +* AT+FCD: Get or set the Frame Counter Downlink (FCntDown)
2364 +* AT+CLASS: Get or set the Device Class
2365 +* AT+JOIN: Join network
2366 +* AT+NJS: Get OTAA Join Status
2367 +* AT+SENDB: Send hexadecimal data along with the application port
2368 +* AT+SEND: Send text data along with the application port
2369 +* AT+RECVB: Print last received data in binary format (with hexadecimal values)
2370 +* AT+RECV: Print last received data in raw format
2371 +* AT+VER: Get current image version and Frequency Band
2372 +* AT+CFM: Get or Set the confirmation mode (0-1)
2373 +* AT+CFS: Get confirmation status of the last AT+SEND (0-1)
2374 +* AT+SNR: Get the SNR of the last received packet
2375 +* AT+RSSI: Get the RSSI of the last received packet
2376 +* AT+TDC: Get or set the application data transmission interval in ms
2377 +* AT+PORT: Get or set the application port
2378 +* AT+DISAT: Disable AT commands
2379 +* AT+PWORD: Set password, max 9 digits
2380 +* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2381 +* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470
2382 +* AT+CFG: Print all settings
2448 2448  )))
2449 2449  
2450 2450  
... ... @@ -2590,19 +2590,16 @@
2590 2590  
2591 2591  == 5.1 Counting how many objects pass through the flow line ==
2592 2592  
2593 -
2594 2594  See [[How to set up to setup counting for objects passing through the flow line>>How to set up to count objects pass in flow line]]?
2595 2595  
2596 2596  
2597 2597  = 6. FAQ =
2598 2598  
2599 -
2600 2600  This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
2601 2601  
2602 2602  
2603 2603  == 6.1 How to update the firmware? ==
2604 2604  
2605 -
2606 2606  Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to:
2607 2607  
2608 2608  * Support new features
... ... @@ -2612,7 +2612,7 @@
2612 2612  You will need the following things before proceeding:
2613 2613  
2614 2614  * 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
2615 -* USB to TTL adapter/converter
2547 +* USB to TTL adapter
2616 2616  * Download and install the [[STM32 Flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]]. (replaced by STM32CubeProgrammer)
2617 2617  * Download the latest firmware image from [[LT-22222-L firmware image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]]. Check the file name of the firmware to find the correct region.
2618 2618  
... ... @@ -2622,7 +2622,7 @@
2622 2622  
2623 2623  Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2624 2624  
2625 -[[image:usb-ttl-audio-jack-connection.jpg]]
2557 +[[image:usb-ttl-programming.png]]
2626 2626  
2627 2627  
2628 2628  
... ... @@ -2655,8 +2655,6 @@
2655 2655  (((
2656 2656  (((
2657 2657  == 6.2 How to change the LoRaWAN frequency band/region? ==
2658 -
2659 -
2660 2660  )))
2661 2661  )))
2662 2662  
... ... @@ -2668,8 +2668,6 @@
2668 2668  
2669 2669  
2670 2670  == 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
2671 -
2672 -
2673 2673  )))
2674 2674  
2675 2675  (((
... ... @@ -2743,13 +2743,11 @@
2743 2743  
2744 2744  == 6.4 How to change the uplink interval? ==
2745 2745  
2746 -
2747 2747  Please see this link: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/]]
2748 2748  
2749 2749  
2750 2750  == 6.5 Can I see the counting event in the serial output? ==
2751 2751  
2752 -
2753 2753  (((
2754 2754  You can run the AT command **AT+DEBUG** to view the counting event in the serial output. If the firmware is too old and doesn’t support AT+DEBUG, update to the latest firmware first.
2755 2755  
... ... @@ -2756,7 +2756,6 @@
2756 2756  
2757 2757  == 6.6 Can I use point-to-point communication with LT-22222-L? ==
2758 2758  
2759 -
2760 2760  Yes, you can. Please refer to the [[Point-to-Point Communication of LT-22222-L>>https://wiki.dragino.com/xwiki/bin/view/Main/%20Point%20to%20Point%20Communication%20of%20LT-22222-L/]] page. The firmware that supports point-to-point communication can be found [[here>>https://github.com/dragino/LT-22222-L/releases]].
2761 2761  
2762 2762  
... ... @@ -2765,7 +2765,6 @@
2765 2765  (((
2766 2766  == 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
2767 2767  
2768 -
2769 2769  * If the device is not properly shut down and is directly powered off.
2770 2770  * It will default to a power-off state.
2771 2771  * In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
... ... @@ -2773,7 +2773,6 @@
2773 2773  
2774 2774  == 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
2775 2775  
2776 -
2777 2777  The LT-22222-L's built-in relay is Normally Open (NO). You can use an external relay to achieve a Normally Closed (NC) configuration. The circuit diagram is shown below:
2778 2778  
2779 2779  
... ... @@ -2782,19 +2782,16 @@
2782 2782  
2783 2783  == 6.9 Can the LT-22222-L save the RO state? ==
2784 2784  
2785 -
2786 2786  To enable this feature, the firmware version must be 1.6.0 or higher.
2787 2787  
2788 2788  
2789 2789  == 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
2790 2790  
2791 -
2792 2792  It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
2793 2793  
2794 2794  
2795 2795  = 7. Troubleshooting =
2796 2796  
2797 -
2798 2798  This section provides some known troubleshooting tips.
2799 2799  
2800 2800  
... ... @@ -2803,8 +2803,6 @@
2803 2803  (((
2804 2804  (((
2805 2805  == 7.1 Downlink isn't working. How can I solve this? ==
2806 -
2807 -
2808 2808  )))
2809 2809  )))
2810 2810  
... ... @@ -2816,8 +2816,6 @@
2816 2816  
2817 2817  
2818 2818  == 7.2 Having trouble uploading an image? ==
2819 -
2820 -
2821 2821  )))
2822 2822  
2823 2823  (((
... ... @@ -2828,8 +2828,6 @@
2828 2828  
2829 2829  
2830 2830  == 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
2831 -
2832 -
2833 2833  )))
2834 2834  
2835 2835  (((
... ... @@ -2839,7 +2839,6 @@
2839 2839  
2840 2840  == 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? ==
2841 2841  
2842 -
2843 2843  The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
2844 2844  Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2845 2845  
... ... @@ -2846,7 +2846,6 @@
2846 2846  
2847 2847  = 8. Ordering information =
2848 2848  
2849 -
2850 2850  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
2851 2851  
2852 2852  (% style="color:#4f81bd" %)**XXX:**
... ... @@ -2861,10 +2861,8 @@
2861 2861  * (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865
2862 2862  * (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779
2863 2863  
2864 -
2865 2865  = 9. Package information =
2866 2866  
2867 -
2868 2868  **Package includes**:
2869 2869  
2870 2870  * 1 x LT-22222-L I/O Controller
... ... @@ -2879,10 +2879,8 @@
2879 2879  * Package Size / pcs : 14.5 x 8 x 5 cm
2880 2880  * Weight / pcs : 170 g
2881 2881  
2882 -
2883 2883  = 10. Support =
2884 2884  
2885 -
2886 2886  * (((
2887 2887  Support is available Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different time zones, we cannot offer live support. However, your questions will be answered as soon as possible within the aforementioned schedule.
2888 2888  )))
... ... @@ -2894,7 +2894,6 @@
2894 2894  
2895 2895  = 11. Reference​​​​​ =
2896 2896  
2897 -
2898 2898  * LT-22222-L: [[http:~~/~~/www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html>>url:http://www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html]]
2899 2899  * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]]
2900 2900  * [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]
Screenshot 2024-12-08 193946.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -32.4 KB
Content
lt-22222-l-joining.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -301.9 KB
Content
lt-22222-l-js-custom-payload-formatter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -453.9 KB
Content
lt33222-l.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -31.3 KB
Content
usb-ttl-audio-jack-connection.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -394.4 KB
Content