Changes for page LT-22222-L -- LoRa I/O Controller User Manual
Last modified by Mengting Qiu on 2025/06/04 18:42
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 3 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.pradeeka - Content
-
... ... @@ -21,6 +21,7 @@ 21 21 22 22 == 1.1 What is the LT-22222-L I/O Controller? == 23 23 24 + 24 24 ((( 25 25 ((( 26 26 {{info}} ... ... @@ -99,6 +99,7 @@ 99 99 100 100 == 1.3 Features == 101 101 103 + 102 102 * LoRaWAN Class A & Class C modes 103 103 * Optional Customized LoRa Protocol 104 104 * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869 ... ... @@ -109,6 +109,7 @@ 109 109 110 110 == 1.4 Applications == 111 111 114 + 112 112 * Smart buildings & home automation 113 113 * Logistics and supply chain management 114 114 * Smart metering ... ... @@ -120,13 +120,13 @@ 120 120 121 121 122 122 (% border="1" cellspacing="3" style="width:510px" %) 123 -|(% style="width:94px" %)**Model**|(% style="width:172px" %)**Photo**|(% style="width:244px" %)**Description** 124 -|(% style="width:94px" %)**LT- 33222-L**|(% style="width:172px" %)(((126 +|(% 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** 127 +|(% style="width:94px" %)**LT-22222-L**|(% style="width:172px" %)((( 125 125 (% style="text-align:center" %) 126 -[[image:lt33222-l.jpg||height="1 39" width="120"]]129 +[[image:lt33222-l.jpg||height="110" width="95"]] 127 127 )))|(% style="width:256px" %)((( 128 -* 3x Digital Input (Bi-direction)129 -* 3x Digital Output131 +* 2 x Digital Input (Bi-direction) 132 +* 2 x Digital Output 130 130 * 2 x Relay Output (5A@250VAC / 30VDC) 131 131 * 2 x 0~~20mA Analog Input (res:0.01mA) 132 132 * 2 x 0~~30V Analog Input (res:0.01v) ... ... @@ -137,6 +137,7 @@ 137 137 138 138 == 2.1 Connecting the antenna == 139 139 143 + 140 140 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. 141 141 142 142 {{warning}} ... ... @@ -143,42 +143,45 @@ 143 143 **Warning! Do not power on the device without connecting the antenna.** 144 144 {{/warning}} 145 145 150 + 146 146 == 2.2 Terminals == 147 147 153 + 148 148 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. 149 149 150 150 **Upper screw terminal block (from left to right):** 151 151 152 -(% style="width: 634px" %)153 -|=(% style="width: 295px;" %)Screw Terminal|=(% style="width:338px;" %)Function154 -|(% style="width: 295px" %)GND|(% style="width:338px" %)Ground155 -|(% style="width: 295px" %)VIN|(% style="width:338px" %)Input Voltage156 -|(% style="width: 295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2157 -|(% style="width: 295px" %)AVI1|(% style="width:338px" %)Analog Voltage Input Terminal 1158 -|(% style="width: 295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2159 -|(% style="width: 295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1158 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:381px" %) 159 +|=(% style="width: 139px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 242px;background-color:#4f81bd;color:white" %)Function 160 +|(% style="width:139px" %)GND|(% style="width:242px" %)Ground 161 +|(% style="width:139px" %)VIN|(% style="width:242px" %)Input Voltage 162 +|(% style="width:139px" %)AVI2|(% style="width:242px" %)Analog Voltage Input Terminal 2 163 +|(% style="width:139px" %)AVI1|(% style="width:242px" %)Analog Voltage Input Terminal 1 164 +|(% style="width:139px" %)ACI2|(% style="width:242px" %)Analog Current Input Terminal 2 165 +|(% style="width:139px" %)ACI1|(% style="width:242px" %)Analog Current Input Terminal 1 160 160 161 161 **Lower screw terminal block (from left to right):** 162 162 163 -(% style="width: 633px" %)164 -|=(% style="width: 2 96px;" %)Screw Terminal|=(% style="width:334px;" %)Function165 -|(% style="width:2 96px" %)RO1-2|(% style="width:334px" %)Relay Output 1166 -|(% style="width:2 96px" %)RO1-1|(% style="width:334px" %)Relay Output 1167 -|(% style="width:2 96px" %)RO2-2|(% style="width:334px" %)Relay Output 2168 -|(% style="width:2 96px" %)RO2-1|(% style="width:334px" %)Relay Output 2169 -|(% style="width:2 96px" %)DI2+|(% style="width:334px" %)Digital Input 2170 -|(% style="width:2 96px" %)DI2-|(% style="width:334px" %)Digital Input 2171 -|(% style="width:2 96px" %)DI1+|(% style="width:334px" %)Digital Input 1172 -|(% style="width:2 96px" %)DI1-|(% style="width:334px" %)Digital Input 1173 -|(% style="width:2 96px" %)DO2|(% style="width:334px" %)Digital Output 2174 -|(% style="width:2 96px" %)DO1|(% style="width:334px" %)Digital Output 1169 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:253px" %) 170 +|=(% style="width: 125px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 128px;background-color:#4f81bd;color:white" %)Function 171 +|(% style="width:125px" %)RO1-2|(% style="width:128px" %)Relay Output 1 172 +|(% style="width:125px" %)RO1-1|(% style="width:128px" %)Relay Output 1 173 +|(% style="width:125px" %)RO2-2|(% style="width:128px" %)Relay Output 2 174 +|(% style="width:125px" %)RO2-1|(% style="width:128px" %)Relay Output 2 175 +|(% style="width:125px" %)DI2+|(% style="width:128px" %)Digital Input 2 176 +|(% style="width:125px" %)DI2-|(% style="width:128px" %)Digital Input 2 177 +|(% style="width:125px" %)DI1+|(% style="width:128px" %)Digital Input 1 178 +|(% style="width:125px" %)DI1-|(% style="width:128px" %)Digital Input 1 179 +|(% style="width:125px" %)DO2|(% style="width:128px" %)Digital Output 2 180 +|(% style="width:125px" %)DO1|(% style="width:128px" %)Digital Output 1 175 175 176 176 == 2.3 Connecting LT-22222-L to a Power Source == 177 177 184 + 178 178 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. 179 179 180 180 {{warning}} 181 -**We recommend that you power on the LT-22222-L after configuring its registration informationwithaLoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.**188 +**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.** 182 182 {{/warning}} 183 183 184 184 ... ... @@ -187,23 +187,27 @@ 187 187 188 188 = 3. Registering LT-22222-L with a LoRaWAN Network Server = 189 189 197 + 190 190 The LT-22222-L supports both OTAA (Over-the-Air Activation) and ABP (Activation By Personalization) methods to activate with a LoRaWAN Network Server. However, OTAA is the most secure method for activating a device with a LoRaWAN Network Server. OTAA regenerates session keys upon initial registration and regenerates new session keys after any subsequent reboots. By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode. 191 191 192 192 193 -== =3.2.1 Prerequisites ===201 +== 3.1 Prerequisites == 194 194 203 + 195 195 The LT-22222-L comes with device registration information such as DevEUI, AppEUI, and AppKey that allows you to register it with a LoRaWAN network. These registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference. 196 196 197 197 [[image:image-20230425173427-2.png||height="246" width="530"]] 198 198 199 199 {{info}} 200 -I ncaseyoucan't set the root key and other identifiers in the network serverandmustusethem fromtheserver,youcanuse[[AT Commands>>||anchor="H4.UseATCommand"]] toconfigure themonthedevice.209 +If you are unable to set the provided root key and other identifiers in the network server, you must generate new keys and identifiers with the network server and configure the device with them using AT commands. 201 201 {{/info}} 202 202 203 203 The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers. 204 204 205 -=== 3.2.2 The Things Stack === 206 206 215 +== 3.2 The Things Stack == 216 + 217 + 207 207 This section guides you through how to register your LT-22222-L with The Things Stack Sandbox. 208 208 209 209 {{info}} ... ... @@ -214,7 +214,7 @@ 214 214 The network diagram below illustrates the connection between the LT-22222-L and The Things Stack, as well as how the data can be integrated with the ThingsEye IoT platform. 215 215 216 216 217 -[[image:dragino-lorawan-nw-lt-22222-n.jpg]] 228 +[[image:dragino-lorawan-nw-lt-22222-n.jpg||height="374" width="1400"]] 218 218 219 219 {{info}} 220 220 You can use a LoRaWAN gateway, such as the [[Dragino LPS8N>>https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]], to expand or create LoRaWAN coverage in your area. ... ... @@ -221,8 +221,9 @@ 221 221 {{/info}} 222 222 223 223 224 -=== =3.2.2.1 Setting up ====235 +=== 3.2.1 Setting up === 225 225 237 + 226 226 * Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet. 227 227 * Log in to your The Things Stack Sandbox account. 228 228 * Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs). ... ... @@ -229,8 +229,9 @@ 229 229 * Go to your application's page and click on the **End devices** in the left menu. 230 230 * On the End devices page, click on **+ Register end device**. Two registration options are available: 231 231 232 -==== 3.2. 2.2Using the LoRaWAN Device Repository ====244 +==== 3.2.1.1 Using the LoRaWAN Device Repository ==== 233 233 246 + 234 234 * On the **Register end device** page: 235 235 ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**. 236 236 ** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists. ... ... @@ -254,8 +254,9 @@ 254 254 [[image:lt-22222-l-dev-repo-reg-p2.png]] 255 255 256 256 257 -==== 3.2. 2.3Adding device manually ====270 +==== 3.2.1.2 Adding device manually ==== 258 258 272 + 259 259 * On the **Register end device** page: 260 260 ** Select the option **Enter end device specifies manually** under **Input method**. 261 261 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. ... ... @@ -285,8 +285,9 @@ 285 285 [[image:lt-22222-device-overview.png]] 286 286 287 287 288 -=== =3.2.2.4Joining ====302 +=== 3.2.2 Joining === 289 289 304 + 290 290 On the Device's page, click on **Live data** tab. The Live data panel for your device will display. 291 291 292 292 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. ... ... @@ -295,10 +295,9 @@ 295 295 [[image:lt-22222-l-joining.png]] 296 296 297 297 313 +=== 3.2.3 Uplinks === 298 298 299 -==== 3.2.2.5 Uplinks ==== 300 300 301 - 302 302 After successfully joining, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**). When the LT-22222-L sends an uplink message to the server, the **TX LED** turns on for **1 second**. By default, you will receive an uplink data message from the device every 10 minutes. 303 303 304 304 Click on one of a **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the decode_payload {} JSON object. ... ... @@ -315,8 +315,15 @@ 315 315 [[image:lt-22222-ul-payload-fmt.png]] 316 316 317 317 318 - ====3.2.2.6Downlinks====332 +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]]: 319 319 334 +(% class="wikigeneratedid" %) 335 +[[image:lt-22222-l-js-custom-payload-formatter.png]] 336 + 337 + 338 +=== 3.2.4 Downlinks === 339 + 340 + 320 320 When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**. 321 321 322 322 ... ... @@ -339,8 +339,10 @@ 339 339 340 340 The uplink messages are sent over LoRaWAN FPort=2. By default, an uplink message is sent every 10 minutes. 341 341 363 + 342 342 === 3.3.1 AT+MOD~=1, 2ACI+2AVI === 343 343 366 + 344 344 ((( 345 345 This is the default mode. 346 346 ... ... @@ -413,6 +413,7 @@ 413 413 414 414 MOD = 1 415 415 439 + 416 416 === 3.3.2 AT+MOD~=2, (Double DI Counting) === 417 417 418 418 ... ... @@ -491,6 +491,7 @@ 491 491 492 492 === 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI === 493 493 518 + 494 494 (% style="color:red" %)**Note: The maximum count depends on the bytes it is. 495 495 The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 496 496 It starts counting again when it reaches the maximum value.** ... ... @@ -544,6 +544,7 @@ 544 544 545 545 === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting === 546 546 572 + 547 547 (% style="color:red" %)**Note:The maximum count depends on the bytes it is. 548 548 The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 549 549 It starts counting again when it reaches the maximum value.** ... ... @@ -613,6 +613,7 @@ 613 613 614 614 === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI === 615 615 642 + 616 616 (% style="color:red" %)**Note:The maximum count depends on the bytes it is. 617 617 The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 618 618 It starts counting again when it reaches the maximum value.** ... ... @@ -757,7 +757,7 @@ 757 757 758 758 MOD6 Payload: total of 11 bytes 759 759 760 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:515px" %)787 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) 761 761 |(% 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** 762 762 |Value|((( 763 763 TRI_A FLAG ... ... @@ -771,7 +771,7 @@ 771 771 772 772 (% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below 773 773 774 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:515px" %)801 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) 775 775 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 776 776 |((( 777 777 AV1_LOW ... ... @@ -800,7 +800,7 @@ 800 800 801 801 (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below 802 802 803 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:515px" %)830 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) 804 804 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 805 805 |((( 806 806 AV1_LOW ... ... @@ -829,9 +829,9 @@ 829 829 830 830 (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below 831 831 832 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:674px" %)833 -|(% 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**834 -|(% 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_FLAG859 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) 860 +|(% 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** 861 +|(% 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 835 835 836 836 * Each bit shows which status has been triggered on this uplink. 837 837 ... ... @@ -862,6 +862,7 @@ 862 862 863 863 == 3.4 Configure LT-22222-L via AT Commands or Downlinks == 864 864 892 + 865 865 ((( 866 866 You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks. 867 867 ))) ... ... @@ -878,17 +878,22 @@ 878 878 879 879 === 3.4.1 Common commands === 880 880 909 + 881 881 ((( 882 882 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. 912 + 913 + 883 883 ))) 884 884 885 885 === 3.4.2 Sensor-related commands === 886 886 918 + 887 887 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. 888 888 889 889 890 890 ==== 3.4.2.1 Set Transmit/Uplink Interval ==== 891 891 924 + 892 892 Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes. 893 893 894 894 (% style="color:#037691" %)**AT command** ... ... @@ -895,8 +895,15 @@ 895 895 896 896 (% border="2" style="width:500px" %) 897 897 |**Command**|AT+TDC=<time> 898 -|**Response**| 899 -|**Parameters**|**time** : uplink interval is in **milliseconds** 931 +|**Parameters**|**time **: uplink interval in milliseconds 932 +|**Get**|AT+TDC=? 933 +|**Response**|((( 934 +current uplink interval 935 + 936 +OK 937 +))) 938 +|**Set**|AT+TDC=<time> 939 +|**Response**|OK 900 900 |**Example**|((( 901 901 AT+TDC=30000 902 902 ... ... @@ -912,7 +912,7 @@ 912 912 |**Parameters**|((( 913 913 **prefix** : 0x01 914 914 915 -**time** : uplink interval i s in **seconds**, represented by **3 bytes** in **hexadecimal**.955 +**time** : uplink interval in **seconds**, represented by **3 bytes** in **hexadecimal**. 916 916 ))) 917 917 |**Example**|((( 918 918 01 **00 00 1E** ... ... @@ -928,13 +928,13 @@ 928 928 929 929 ==== 3.4.2.2 Set the Working Mode (AT+MOD) ==== 930 930 971 + 931 931 Sets the working mode. 932 932 933 933 (% style="color:#037691" %)**AT command** 934 934 935 935 (% border="2" style="width:500px" %) 936 -|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE=<working_mode> 937 -|(% style="width:97px" %)**Response**|(% style="width:413px" %) 977 +|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MOD=<working_mode> 938 938 |(% style="width:97px" %)**Parameters**|(% style="width:413px" %)((( 939 939 **working_mode** : 940 940 ... ... @@ -950,6 +950,18 @@ 950 950 951 951 6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5 952 952 ))) 993 +|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=? 994 +|(% style="width:97px" %)**Response**|(% style="width:413px" %)((( 995 +Current working mode 996 + 997 +OK 998 +))) 999 +|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode> 1000 +|(% style="width:97px" %)**Response**|(% style="width:413px" %)((( 1001 +Attention:Take effect after ATZ 1002 + 1003 +OK 1004 +))) 953 953 |(% style="width:97px" %)**Example**|(% style="width:413px" %)((( 954 954 AT+MOD=2 955 955 ... ... @@ -974,6 +974,7 @@ 974 974 975 975 ==== 3.4.2.3 Request an uplink from the device ==== 976 976 1029 + 977 977 Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode. 978 978 979 979 (% style="color:#037691" %)**AT command** ... ... @@ -993,6 +993,7 @@ 993 993 994 994 ==== 3.4.2.4 Enable/Disable Trigger Mode ==== 995 995 1049 + 996 996 Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]). 997 997 998 998 (% style="color:#037691" %)**AT Command** ... ... @@ -1030,6 +1030,7 @@ 1030 1030 1031 1031 ==== 3.4.2.5 Request trigger settings ==== 1032 1032 1087 + 1033 1033 Requests the trigger settings. 1034 1034 1035 1035 (% style="color:#037691" %)**AT Command:** ... ... @@ -1049,6 +1049,7 @@ 1049 1049 1050 1050 ==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ==== 1051 1051 1107 + 1052 1052 Enable or disable DI1/DI2/DI3 as a trigger. 1053 1053 1054 1054 (% style="color:#037691" %)**AT Command** ... ... @@ -1103,9 +1103,9 @@ 1103 1103 1104 1104 ==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ==== 1105 1105 1162 + 1106 1106 Sets DI1 or DI3 (for LT-33222-L) as a trigger. 1107 1107 1108 - 1109 1109 (% style="color:#037691" %)**AT Command** 1110 1110 1111 1111 (% border="2" style="width:500px" %) ... ... @@ -1142,9 +1142,9 @@ 1142 1142 1143 1143 ==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ==== 1144 1144 1201 + 1145 1145 Sets DI2 as a trigger. 1146 1146 1147 - 1148 1148 (% style="color:#037691" %)**AT Command** 1149 1149 1150 1150 (% border="2" style="width:500px" %) ... ... @@ -1176,6 +1176,7 @@ 1176 1176 1177 1177 ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ==== 1178 1178 1235 + 1179 1179 Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1180 1180 1181 1181 (% style="color:#037691" %)**AT Command** ... ... @@ -1225,6 +1225,7 @@ 1225 1225 1226 1226 ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ==== 1227 1227 1285 + 1228 1228 Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1229 1229 1230 1230 (% style="color:#037691" %)**AT Command** ... ... @@ -1272,6 +1272,7 @@ 1272 1272 1273 1273 ==== 3.4.2.11 Trigger – Set minimum interval ==== 1274 1274 1333 + 1275 1275 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. 1276 1276 1277 1277 (% style="color:#037691" %)**AT Command** ... ... @@ -1307,6 +1307,7 @@ 1307 1307 1308 1308 ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ==== 1309 1309 1369 + 1310 1310 Controls the digital outputs DO1, DO2, and DO3 1311 1311 1312 1312 (% style="color:#037691" %)**AT Command** ... ... @@ -1337,11 +1337,11 @@ 1337 1337 ((( 1338 1338 01: Low, 00: High, 11: No action 1339 1339 1340 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:510px" %)1341 -|(% 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** 1342 -|02 01 00 11|Low|High|No Action 1343 -|02 00 11 01|High|No Action|Low 1344 -|02 11 01 00|No Action|Low|High 1400 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:383px" %) 1401 +|(% 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** 1402 +|(% style="width:126px" %)02 01 00 11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action 1403 +|(% style="width:126px" %)02 00 11 01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low 1404 +|(% style="width:126px" %)02 11 01 00|(% style="width:85px" %)No Action|(% style="width:86px" %)Low|(% style="width:86px" %)High 1345 1345 ))) 1346 1346 1347 1347 ((( ... ... @@ -1358,80 +1358,82 @@ 1358 1358 ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ==== 1359 1359 1360 1360 1361 - *(% style="color:#037691" %)**ATCommand**1421 +(% style="color:#037691" %)**AT command** 1362 1362 1363 1363 There is no AT command to control the digital output. 1364 1364 1365 1365 1366 - *(% style="color:#037691" %)**DownlinkPayload(prefix 0xA9)**1426 +(% style="color:#037691" %)**Downlink payload** 1367 1367 1368 -(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control 1369 1369 1370 -This is to control the digital output time of DO pin. Include four bytes: 1429 +(% border="2" style="width:500px" %) 1430 +|(% style="width:116px" %)**Prefix**|(% style="width:382px" %)0xA9 1431 +|(% style="width:116px" %)**Parameters**|(% style="width:382px" %)((( 1432 +**inverter_mode**: 1 byte in hex. 1371 1371 1372 -(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9) 1373 - 1374 -(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode 1375 - 1376 1376 **01:** DO pins revert to their original state after the timeout. 1377 1377 **00:** DO pins switch to an inverted state after the timeout. 1378 1378 1379 1379 1380 - (% style="color:#4f81bd" %)**Third Byte**(%%): ControlMethodPort:1438 +**DO1_control_method_and_port_status **- 1 byte in hex 1381 1381 1382 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1383 -|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** 1384 -|0x01|DO1 set to low 1385 -|0x00|DO1 set to high 1386 -|0x11|DO1 NO Action 1440 +0x01 : DO1 set to low 1387 1387 1388 - (%style="color:#4f81bd"%)**Fourthbyte**(%%):ControlMethodand Port status:1442 +0x00 : DO1 set to high 1389 1389 1390 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1391 -|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** 1392 -|0x01|DO2 set to low 1393 -|0x00|DO2 set to high 1394 -|0x11|DO2 NO Action 1444 +0x11 : DO1 NO action 1395 1395 1396 -(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status: 1397 1397 1398 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1399 -|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** 1400 -|0x01|DO3 set to low 1401 -|0x00|DO3 set to high 1402 -|0x11|DO3 NO Action 1447 +**DO2_control_method_and_port_status** - 1 byte in hex 1403 1403 1404 - (%style="color:#4f81bd"%)**Sixth,Seventh,Eighth, and Ninth bytes**:(%%) Latchingtime(Unit: ms)1449 +0x01 : DO2 set to low 1405 1405 1451 +0x00 : DO2 set to high 1406 1406 1407 - (%style="color:red"%)**Note:**1453 +0x11 : DO2 NO action 1408 1408 1409 - Since firmware v1.6.0, the latch time support 4 bytes and 2 bytes 1410 1410 1411 - Before firmwarev1.6.0,the latch timeonly supported2bytes.1456 +**DO3_control_method_and_port_status **- 1 byte in hex 1412 1412 1413 - (%style="color:red"%)**Thedevicewill uplink a packetifthe downlinkcode executes successfully.**1458 +0x01 : DO3 set to low 1414 1414 1460 +0x00 : DO3 set to high 1415 1415 1416 - **Examplepayload:**1462 +0x11 : DO3 NO action 1417 1417 1418 -**~1. A9 01 01 01 01 07 D0** 1419 1419 1465 +**latching_time** : 4 bytes in hex 1466 + 1467 +(% style="color:red" %)**Note: ** 1468 + 1469 + Since firmware v1.6.0, the latch time support 4 bytes or 2 bytes 1470 + 1471 + Before firmware v1.6.0, the latch time only supported 2 bytes. 1472 + 1473 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.** 1474 +))) 1475 +|(% style="width:116px" %)**Payload format**|(% style="width:382px" %)<prefix><inverter_mode><DO1_control_method_and_port_status><DO2_control_method_and_port_status><DO2_control_method_and_port_status><latching_time> 1476 +|(% style="width:116px" %)**Example**|(% style="width:382px" %)((( 1477 +**A9 01 01 01 01 07 D0** 1478 + 1420 1420 DO1 pin, DO2 pin, and DO3 pin will be set to low, last for 2 seconds, and then revert to their original state. 1421 1421 1422 -**2. A9 01 00 01 11 07 D0** 1423 1423 1482 +**A9 01 00 01 11 07 D0** 1483 + 1424 1424 DO1 pin is set to high, DO2 pin is set to low, and DO3 pin takes no action. This lasts for 2 seconds and then reverts to the original state. 1425 1425 1426 -**3. A9 00 00 00 00 07 D0** 1427 1427 1487 +**A9 00 00 00 00 07 D0** 1488 + 1428 1428 DO1 pin, DO2 pin, and DO3 pin will be set to high, last for 2 seconds, and then all change to low. 1429 1429 1430 -**4. A9 00 11 01 00 07 D0** 1431 1431 1492 +**A9 00 11 01 00 07 D0** 1493 + 1432 1432 DO1 pin takes no action, DO2 pin is set to low, and DO3 pin is set to high. This lasts for 2 seconds, after which DO1 pin takes no action, DO2 pin is set to high, and DO3 pin is set to low. 1495 +))) 1433 1433 1434 - 1435 1435 ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ==== 1436 1436 1437 1437 ... ... @@ -1469,6 +1469,7 @@ 1469 1469 1470 1470 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== 1471 1471 1534 + 1472 1472 Controls the relay output time. 1473 1473 1474 1474 * (% style="color:#037691" %)**AT Command:** ... ... @@ -1668,6 +1668,7 @@ 1668 1668 1669 1669 ==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ==== 1670 1670 1734 + 1671 1671 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. 1672 1672 1673 1673 (% style="color:#037691" %)**AT Command** ... ... @@ -1699,6 +1699,7 @@ 1699 1699 1700 1700 ==== 3.4.2.20 Reset saved RO and DO states ==== 1701 1701 1766 + 1702 1702 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. 1703 1703 1704 1704 (% style="color:#037691" %)**AT Command** ... ... @@ -1748,6 +1748,7 @@ 1748 1748 1749 1749 ==== 3.4.2.21 Encrypted payload ==== 1750 1750 1816 + 1751 1751 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. 1752 1752 1753 1753 (% style="color:#037691" %)**AT Command:** ... ... @@ -1777,6 +1777,7 @@ 1777 1777 1778 1778 ==== 3.4.2.22 Get sensor value ==== 1779 1779 1846 + 1780 1780 This command allows you to retrieve and optionally uplink sensor readings through the serial port. 1781 1781 1782 1782 (% style="color:#037691" %)**AT Command** ... ... @@ -1806,6 +1806,7 @@ 1806 1806 1807 1807 ==== 3.4.2.23 Resetting the downlink packet count ==== 1808 1808 1876 + 1809 1809 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. 1810 1810 1811 1811 (% style="color:#037691" %)**AT Command** ... ... @@ -1884,43 +1884,33 @@ 1884 1884 1885 1885 ==== 3.4.2.25 Copy downlink to uplink ==== 1886 1886 1887 -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. 1888 1888 1889 - *(%style="color:#037691"%)**ATCommand**(%%)**:**1956 +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. 1890 1890 1891 -(% style="color: blue" %)**AT+RPL=5**(%%) ~/~/ After receiving the package fromthe server, it will immediately upload the content of the package to the server, the port number is 100.1958 +(% style="color:#037691" %)**AT Command**(%%)**:** 1892 1892 1893 - Example:**aa xx xx xx xx**aaindicateswhether the configuration haschanged,00isyes,01 is no;xx xx xx xx arethebytessent.1960 +(% 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. 1894 1894 1962 +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. 1895 1895 1964 + 1896 1896 [[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"]] 1897 1897 1898 1898 For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77. 1899 1899 1900 -(% border="2" style="width:500px" %) 1901 -|(% style="width:122px" %)**Command**|(% style="width:376px" %)((( 1902 -AT+RPL=5 1903 - 1904 -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. 1905 -))) 1906 -|(% style="width:122px" %)**Example**|(% style="width:376px" %)((( 1907 -Downlink: 1908 - 1909 -01 00 02 58 1910 - 1911 -Uplink: 1912 - 1913 -01 01 00 02 58 1914 -))) 1915 - 1916 1916 [[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"]] 1917 1917 1918 1918 For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. 1919 1919 1920 1920 1974 +(% style="color:#037691" %)**Downlink Payload**(%%)**:** 1921 1921 1976 +There is no downlink option available for this feature. 1977 + 1978 + 1922 1922 ==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ==== 1923 1923 1981 + 1924 1924 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. 1925 1925 1926 1926 * ((( ... ... @@ -1939,10 +1939,13 @@ 1939 1939 1940 1940 == 3.5 Integrating with ThingsEye.io == 1941 1941 2000 + 1942 1942 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. 1943 1943 2003 + 1944 1944 === 3.5.1 Configuring The Things Stack === 1945 1945 2006 + 1946 1946 We use The Things Stack Sandbox in this example: 1947 1947 1948 1948 * In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added. ... ... @@ -1956,8 +1956,10 @@ 1956 1956 1957 1957 [[image:tts-mqtt-integration.png]] 1958 1958 2020 + 1959 1959 === 3.5.2 Configuring ThingsEye.io === 1960 1960 2023 + 1961 1961 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. 1962 1962 1963 1963 * Login to your [[ThingsEye.io >>https://thingseye.io]]account. ... ... @@ -2027,6 +2027,7 @@ 2027 2027 2028 2028 ==== 3.5.2.1 Viewing integration details ==== 2029 2029 2093 + 2030 2030 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. 2031 2031 2032 2032 [[image:integration-details.png]] ... ... @@ -2038,8 +2038,10 @@ 2038 2038 See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]]. 2039 2039 {{/info}} 2040 2040 2041 -==== **3.5.2.2 Viewing events** ==== 2042 2042 2106 +==== 3.5.2.2 Viewing events ==== 2107 + 2108 + 2043 2043 The **Events **tab displays all the uplink messages from the LT-22222-L. 2044 2044 2045 2045 * Select **Debug **from the **Event type** dropdown. ... ... @@ -2048,21 +2048,27 @@ 2048 2048 [[image:thingseye-events.png]] 2049 2049 2050 2050 2051 -* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message. 2117 +* To view the **JSON payload** of a message, click on the **three dots (...)** in the **Message** column of the desired message. 2052 2052 2053 2053 [[image:thingseye-json.png]] 2054 2054 2055 2055 2056 -==== **3.5.2.3 Deleting an integration**====2122 +==== 3.5.2.3 Deleting an integration ==== 2057 2057 2124 + 2058 2058 If you want to delete an integration, click the **Delete integratio**n button on the Integrations page. 2059 2059 2060 2060 2061 -==== 3.5.2.4 Creatinga Dashboardto DisplayandAnalyzeLT-22222-L Data ====2128 +==== 3.5.2.4 Viewing sensor data on a dashboard ==== 2062 2062 2063 -This will be added soon. 2064 2064 2131 +You can create a dashboard with ThingsEye to visualize the sensor data coming from the LHT65N-VIB. The following image shows a dashboard created for the LT-22222-L. See **Creating a dashboard** in ThingsEye documentation for more information. 2065 2065 2133 + 2134 + 2135 +[[image:lt-22222-l-dashboard.png]] 2136 + 2137 + 2066 2066 == 3.6 Interface Details == 2067 2067 2068 2068 === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) === ... ... @@ -2276,6 +2276,7 @@ 2276 2276 2277 2277 == 3.7 LED Indicators == 2278 2278 2351 + 2279 2279 The table below lists the behavior of LED indicators for each port function. 2280 2280 2281 2281 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) ... ... @@ -2308,10 +2308,13 @@ 2308 2308 2309 2309 = 4. Using AT Commands = 2310 2310 2384 + 2311 2311 The LT-22222-L supports programming using AT Commands. 2312 2312 2387 + 2313 2313 == 4.1 Connecting the LT-22222-L to a PC == 2314 2314 2390 + 2315 2315 ((( 2316 2316 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. 2317 2317 ... ... @@ -2331,7 +2331,10 @@ 2331 2331 ((( 2332 2332 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/]] 2333 2333 2410 + 2334 2334 == 4.2 LT-22222-L related AT commands == 2412 + 2413 + 2335 2335 ))) 2336 2336 2337 2337 ((( ... ... @@ -2528,16 +2528,19 @@ 2528 2528 2529 2529 == 5.1 Counting how many objects pass through the flow line == 2530 2530 2610 + 2531 2531 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]]? 2532 2532 2533 2533 2534 2534 = 6. FAQ = 2535 2535 2616 + 2536 2536 This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly. 2537 2537 2538 2538 2539 2539 == 6.1 How to update the firmware? == 2540 2540 2622 + 2541 2541 Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to: 2542 2542 2543 2543 * Support new features ... ... @@ -2590,6 +2590,8 @@ 2590 2590 ((( 2591 2591 ((( 2592 2592 == 6.2 How to change the LoRaWAN frequency band/region? == 2675 + 2676 + 2593 2593 ))) 2594 2594 ))) 2595 2595 ... ... @@ -2601,6 +2601,8 @@ 2601 2601 2602 2602 2603 2603 == 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? == 2688 + 2689 + 2604 2604 ))) 2605 2605 2606 2606 ((( ... ... @@ -2674,11 +2674,13 @@ 2674 2674 2675 2675 == 6.4 How to change the uplink interval? == 2676 2676 2763 + 2677 2677 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/]] 2678 2678 2679 2679 2680 2680 == 6.5 Can I see the counting event in the serial output? == 2681 2681 2769 + 2682 2682 ((( 2683 2683 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. 2684 2684 ... ... @@ -2685,6 +2685,7 @@ 2685 2685 2686 2686 == 6.6 Can I use point-to-point communication with LT-22222-L? == 2687 2687 2776 + 2688 2688 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]]. 2689 2689 2690 2690 ... ... @@ -2693,6 +2693,7 @@ 2693 2693 ((( 2694 2694 == 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? == 2695 2695 2785 + 2696 2696 * If the device is not properly shut down and is directly powered off. 2697 2697 * It will default to a power-off state. 2698 2698 * In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory. ... ... @@ -2700,6 +2700,7 @@ 2700 2700 2701 2701 == 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? == 2702 2702 2793 + 2703 2703 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: 2704 2704 2705 2705 ... ... @@ -2708,16 +2708,19 @@ 2708 2708 2709 2709 == 6.9 Can the LT-22222-L save the RO state? == 2710 2710 2802 + 2711 2711 To enable this feature, the firmware version must be 1.6.0 or higher. 2712 2712 2713 2713 2714 2714 == 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? == 2715 2715 2808 + 2716 2716 It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose. 2717 2717 2718 2718 2719 2719 = 7. Troubleshooting = 2720 2720 2814 + 2721 2721 This section provides some known troubleshooting tips. 2722 2722 2723 2723 ... ... @@ -2726,6 +2726,8 @@ 2726 2726 ((( 2727 2727 ((( 2728 2728 == 7.1 Downlink isn't working. How can I solve this? == 2823 + 2824 + 2729 2729 ))) 2730 2730 ))) 2731 2731 ... ... @@ -2737,6 +2737,8 @@ 2737 2737 2738 2738 2739 2739 == 7.2 Having trouble uploading an image? == 2836 + 2837 + 2740 2740 ))) 2741 2741 2742 2742 ((( ... ... @@ -2747,6 +2747,8 @@ 2747 2747 2748 2748 2749 2749 == 7.3 Why can't I join TTN in the US915 /AU915 bands? == 2848 + 2849 + 2750 2750 ))) 2751 2751 2752 2752 ((( ... ... @@ -2756,6 +2756,7 @@ 2756 2756 2757 2757 == 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? == 2758 2758 2859 + 2759 2759 The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue. 2760 2760 Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]] 2761 2761 ... ... @@ -2762,6 +2762,7 @@ 2762 2762 2763 2763 = 8. Ordering information = 2764 2764 2866 + 2765 2765 (% style="color:#4f81bd" %)**LT-22222-L-XXX:** 2766 2766 2767 2767 (% style="color:#4f81bd" %)**XXX:** ... ... @@ -2778,6 +2778,7 @@ 2778 2778 2779 2779 = 9. Package information = 2780 2780 2883 + 2781 2781 **Package includes**: 2782 2782 2783 2783 * 1 x LT-22222-L I/O Controller ... ... @@ -2794,6 +2794,7 @@ 2794 2794 2795 2795 = 10. Support = 2796 2796 2900 + 2797 2797 * ((( 2798 2798 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. 2799 2799 ))) ... ... @@ -2805,6 +2805,7 @@ 2805 2805 2806 2806 = 11. Reference = 2807 2807 2912 + 2808 2808 * 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]] 2809 2809 * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]] 2810 2810 * [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]
- Screenshot 2024-12-08 193946.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +32.4 KB - Content
- lt-22222-l-dashboard.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +352.8 KB - Content
- lt-22222-l-js-custom-payload-formatter.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +453.9 KB - Content