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, 0 added, 5 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +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 ... ... @@ -100,7 +100,6 @@ 100 100 101 101 == 1.3 Features == 102 102 103 - 104 104 * LoRaWAN Class A & Class C modes 105 105 * Optional Customized LoRa Protocol 106 106 * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869 ... ... @@ -111,7 +111,6 @@ 111 111 112 112 == 1.4 Applications == 113 113 114 - 115 115 * Smart buildings & home automation 116 116 * Logistics and supply chain management 117 117 * Smart metering ... ... @@ -121,13 +121,11 @@ 121 121 122 122 == 1.5 Hardware Variants == 123 123 124 - 125 -(% border="1" cellspacing="3" style="width:510px" %) 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" %)((( 128 -(% style="text-align:center" %) 129 -[[image:lt33222-l.jpg||height="110" width="95"]] 130 -)))|(% 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" %)((( 131 131 * 2 x Digital Input (Bi-direction) 132 132 * 2 x Digital Output 133 133 * 2 x Relay Output (5A@250VAC / 30VDC) ... ... @@ -140,7 +140,6 @@ 140 140 141 141 == 2.1 Connecting the antenna == 142 142 143 - 144 144 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. 145 145 146 146 {{warning}} ... ... @@ -147,46 +147,42 @@ 147 147 **Warning! Do not power on the device without connecting the antenna.** 148 148 {{/warning}} 149 149 150 - 151 151 == 2.2 Terminals == 152 152 153 - 154 154 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. 155 155 156 156 **Upper screw terminal block (from left to right):** 157 157 158 -(% 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" %)Function160 -|(% style="width: 139px" %)GND|(% style="width:242px" %)Ground161 -|(% style="width: 139px" %)VIN|(% style="width:242px" %)Input Voltage162 -|(% style="width: 139px" %)AVI2|(% style="width:242px" %)Analog Voltage Input Terminal 2163 -|(% style="width: 139px" %)AVI1|(% style="width:242px" %)Analog Voltage Input Terminal 1164 -|(% style="width: 139px" %)ACI2|(% style="width:242px" %)Analog Current Input Terminal 2165 -|(% style="width: 139px" %)ACI1|(% style="width:242px" %)Analog Current Input Terminal 1148 +(% 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 166 166 167 167 **Lower screw terminal block (from left to right):** 168 168 169 -(% 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" %)Function171 -|(% style="width: 125px" %)RO1-2|(% style="width:128px" %)Relay Output 1172 -|(% style="width: 125px" %)RO1-1|(% style="width:128px" %)Relay Output 1173 -|(% style="width: 125px" %)RO2-2|(% style="width:128px" %)Relay Output 2174 -|(% style="width: 125px" %)RO2-1|(% style="width:128px" %)Relay Output 2175 -|(% style="width: 125px" %)DI2+|(% style="width:128px" %)Digital Input 2176 -|(% style="width: 125px" %)DI2-|(% style="width:128px" %)Digital Input 2177 -|(% style="width: 125px" %)DI1+|(% style="width:128px" %)Digital Input 1178 -|(% style="width: 125px" %)DI1-|(% style="width:128px" %)Digital Input 1179 -|(% style="width: 125px" %)DO2|(% style="width:128px" %)Digital Output 2180 -|(% style="width: 125px" %)DO1|(% style="width:128px" %)Digital Output 1159 +(% 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 181 181 182 - 183 183 == 2.3 Connecting LT-22222-L to a Power Source == 184 184 185 - 186 186 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. 187 187 188 188 {{warning}} 189 -**We recommend that you power on the LT-22222-L after adding its registration information to theLoRaWAN 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.** 190 190 {{/warning}} 191 191 192 192 ... ... @@ -195,13 +195,11 @@ 195 195 196 196 = 3. Registering LT-22222-L with a LoRaWAN Network Server = 197 197 198 - 199 199 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. 200 200 201 201 202 202 === 3.2.1 Prerequisites === 203 203 204 - 205 205 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. 206 206 207 207 [[image:image-20230425173427-2.png||height="246" width="530"]] ... ... @@ -212,10 +212,8 @@ 212 212 213 213 The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers. 214 214 215 - 216 216 === 3.2.2 The Things Stack === 217 217 218 - 219 219 This section guides you through how to register your LT-22222-L with The Things Stack Sandbox. 220 220 221 221 {{info}} ... ... @@ -226,7 +226,7 @@ 226 226 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. 227 227 228 228 229 -[[image:dragino-lorawan-nw-lt-22222-n.jpg ||height="374" width="1400"]]213 +[[image:dragino-lorawan-nw-lt-22222-n.jpg]] 230 230 231 231 {{info}} 232 232 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. ... ... @@ -235,7 +235,6 @@ 235 235 236 236 ==== 3.2.2.1 Setting up ==== 237 237 238 - 239 239 * Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet. 240 240 * Log in to your The Things Stack Sandbox account. 241 241 * Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs). ... ... @@ -242,10 +242,8 @@ 242 242 * Go to your application's page and click on the **End devices** in the left menu. 243 243 * On the End devices page, click on **+ Register end device**. Two registration options are available: 244 244 245 - 246 246 ==== 3.2.2.2 Using the LoRaWAN Device Repository ==== 247 247 248 - 249 249 * On the **Register end device** page: 250 250 ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**. 251 251 ** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists. ... ... @@ -256,7 +256,7 @@ 256 256 *** **Profile (Region)**: Select the region that matches your device. 257 257 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 258 258 259 -[[image:lt-22222-l-dev-repo-reg-p1.png]] 240 +[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]] 260 260 261 261 262 262 * Register end device page continued... ... ... @@ -266,12 +266,11 @@ 266 266 ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. 267 267 ** Under **After registration**, select the **View registered end device** option. 268 268 269 -[[image:lt-22222-l-dev-repo-reg-p2.png]] 250 +[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]] 270 270 271 271 272 272 ==== 3.2.2.3 Adding device manually ==== 273 273 274 - 275 275 * On the **Register end device** page: 276 276 ** Select the option **Enter end device specifies manually** under **Input method**. 277 277 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. ... ... @@ -281,7 +281,7 @@ 281 281 ** Select the option **Over the air activation (OTAA)** under the **Activation mode.** 282 282 ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list. 283 283 284 -[[image:lt-22222-l-manually-p1.png]] 264 +[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]] 285 285 286 286 287 287 * Register end device page continued... ... ... @@ -292,24 +292,23 @@ 292 292 ** Under **After registration**, select the **View registered end device** option. 293 293 ** Click the **Register end device** button. 294 294 295 -[[image:lt-22222-l-manually-p2.png]] 275 +[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]] 296 296 297 297 298 298 You will be navigated to the **Device overview** page. 299 299 300 300 301 -[[image:lt-22222-device-overview.png]] 281 +[[image:lt-22222-device-overview.png||height="625" width="1000"]] 302 302 303 303 304 304 ==== 3.2.2.4 Joining ==== 305 305 306 - 307 307 On the Device's page, click on **Live data** tab. The Live data panel for your device will display. 308 308 309 309 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. 310 310 311 311 312 -[[image:lt-22222- l-joining.png]]291 +[[image:lt-22222-join-network.png||height="625" width="1000"]] 313 313 314 314 315 315 ==== 3.2.2.5 Uplinks ==== ... ... @@ -328,18 +328,11 @@ 328 328 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. 329 329 {{/info}} 330 330 331 -[[image:lt-22222-ul-payload-fmt.png]] 310 +[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]] 332 332 333 333 334 -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]]: 335 - 336 -(% class="wikigeneratedid" %) 337 -[[image:lt-22222-l-js-custom-payload-formatter.png]] 338 - 339 - 340 340 ==== 3.2.2.6 Downlinks ==== 341 341 342 - 343 343 When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**. 344 344 345 345 ... ... @@ -362,10 +362,8 @@ 362 362 363 363 The uplink messages are sent over LoRaWAN FPort=2. By default, an uplink message is sent every 10 minutes. 364 364 365 - 366 366 === 3.3.1 AT+MOD~=1, 2ACI+2AVI === 367 367 368 - 369 369 ((( 370 370 This is the default mode. 371 371 ... ... @@ -438,7 +438,6 @@ 438 438 439 439 MOD = 1 440 440 441 - 442 442 === 3.3.2 AT+MOD~=2, (Double DI Counting) === 443 443 444 444 ... ... @@ -517,7 +517,6 @@ 517 517 518 518 === 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI === 519 519 520 - 521 521 (% style="color:red" %)**Note: The maximum count depends on the bytes it is. 522 522 The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 523 523 It starts counting again when it reaches the maximum value.** ... ... @@ -571,7 +571,6 @@ 571 571 572 572 === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting === 573 573 574 - 575 575 (% style="color:red" %)**Note:The maximum count depends on the bytes it is. 576 576 The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 577 577 It starts counting again when it reaches the maximum value.** ... ... @@ -631,17 +631,16 @@ 631 631 632 632 (% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)** 633 633 634 -(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If theAVI1 voltageishigher than VOLMAX (20000mV =20V),thecounter increasesby1)**601 +(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 635 635 636 -(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If theAVI1 voltageislower than VOLMAX (20000mV =20V), counter increasesby1)**603 +(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)** 637 637 638 -(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If theAVI1 voltageishigher than VOLMAX (20000mV =20V), counter increasesby1)**605 +(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 639 639 ))) 640 640 641 641 642 642 === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI === 643 643 644 - 645 645 (% style="color:red" %)**Note:The maximum count depends on the bytes it is. 646 646 The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 647 647 It starts counting again when it reaches the maximum value.** ... ... @@ -755,9 +755,9 @@ 755 755 756 756 (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:** 757 757 758 - **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** 759 759 760 - **Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4726 +Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4 761 761 762 762 AA: Type Code for this downlink Command: 763 763 ... ... @@ -786,7 +786,7 @@ 786 786 787 787 MOD6 Payload: total of 11 bytes 788 788 789 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)755 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 790 790 |(% 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** 791 791 |Value|((( 792 792 TRI_A FLAG ... ... @@ -800,7 +800,7 @@ 800 800 801 801 (% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below 802 802 803 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)769 +(% border="1" cellspacing="4" 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 ... ... @@ -824,12 +824,12 @@ 824 824 825 825 **Example:** 826 826 827 -10100000: This means the systemis configuredto use the triggersAV1_LOW and AV2_LOW.793 +10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW 828 828 829 829 830 830 (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below 831 831 832 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)798 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 833 833 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 834 834 |((( 835 835 AV1_LOW ... ... @@ -853,31 +853,31 @@ 853 853 854 854 **Example:** 855 855 856 -10000000: The uplink is triggered by AV1_LOW,indicatingthatthe voltage is too low.822 +10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low. 857 857 858 858 859 859 (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below 860 860 861 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)862 -|(% 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**863 -|(% style="width:4 9px" %)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_FLAG827 +(% 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 864 864 865 -* Each bit shows which status has been triggered on this uplink. 831 +* Each bits shows which status has been triggered on this uplink. 866 866 867 867 **Example:** 868 868 869 -00000111: This means both DI1 and DI2 triggersare 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. 870 870 871 -00000101: This means both DI1 and DI2 triggersare enabled.837 +00000101: Means both DI1 and DI2 trigger are enabled. 872 872 873 873 874 -(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable d. 0x00: MOD6 is disabled.840 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable. 875 875 876 -Downlink command to poll /requestMOD6 status:842 +Downlink command to poll MOD6 status: 877 877 878 878 **AB 06** 879 879 880 -When device receivesthis command, it will send the MOD6 payload.846 +When device got this command, it will send the MOD6 payload. 881 881 882 882 883 883 === 3.3.7 Payload Decoder === ... ... @@ -891,7 +891,6 @@ 891 891 892 892 == 3.4 Configure LT-22222-L via AT Commands or Downlinks == 893 893 894 - 895 895 ((( 896 896 You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks. 897 897 ))) ... ... @@ -906,25 +906,19 @@ 906 906 907 907 * (% style="color:blue" %)**Sensor-related commands**(%%): 908 908 909 - 910 910 === 3.4.1 Common commands === 911 911 912 - 913 913 ((( 914 914 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. 915 - 916 - 917 917 ))) 918 918 919 919 === 3.4.2 Sensor-related commands === 920 920 921 - 922 922 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. 923 923 924 924 925 925 ==== 3.4.2.1 Set Transmit/Uplink Interval ==== 926 926 927 - 928 928 Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes. 929 929 930 930 (% style="color:#037691" %)**AT command** ... ... @@ -931,15 +931,8 @@ 931 931 932 932 (% border="2" style="width:500px" %) 933 933 |**Command**|AT+TDC=<time> 934 -|**Parameters**|**time **: uplink interval in milliseconds 935 -|**Get**|AT+TDC=? 936 -|**Response**|((( 937 -current uplink interval 938 - 939 -OK 940 -))) 941 -|**Set**|AT+TDC=<time> 942 -|**Response**|OK 893 +|**Response**| 894 +|**Parameters**|**time** : uplink interval is in **milliseconds** 943 943 |**Example**|((( 944 944 AT+TDC=30000 945 945 ... ... @@ -955,7 +955,7 @@ 955 955 |**Parameters**|((( 956 956 **prefix** : 0x01 957 957 958 -**time** : uplink interval in **seconds**, represented by **3 bytes** in **hexadecimal**. 910 +**time** : uplink interval is in **seconds**, represented by **3 bytes** in **hexadecimal**. 959 959 ))) 960 960 |**Example**|((( 961 961 01 **00 00 1E** ... ... @@ -971,13 +971,13 @@ 971 971 972 972 ==== 3.4.2.2 Set the Working Mode (AT+MOD) ==== 973 973 974 - 975 975 Sets the working mode. 976 976 977 977 (% style="color:#037691" %)**AT command** 978 978 979 979 (% border="2" style="width:500px" %) 980 -|(% 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" %) 981 981 |(% style="width:97px" %)**Parameters**|(% style="width:413px" %)((( 982 982 **working_mode** : 983 983 ... ... @@ -993,18 +993,6 @@ 993 993 994 994 6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5 995 995 ))) 996 -|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=? 997 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)((( 998 -Current working mode 999 - 1000 -OK 1001 -))) 1002 -|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode> 1003 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)((( 1004 -Attention:Take effect after ATZ 1005 - 1006 -OK 1007 -))) 1008 1008 |(% style="width:97px" %)**Example**|(% style="width:413px" %)((( 1009 1009 AT+MOD=2 1010 1010 ... ... @@ -1027,9 +1027,8 @@ 1027 1027 Sets the device to working mode 2 (Double DI Counting + DO + RO) 1028 1028 ))) 1029 1029 1030 -==== 3.4.2.3 Requestan uplinkfrom the device====970 +==== 3.4.2.3 Poll an uplink ==== 1031 1031 1032 - 1033 1033 Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode. 1034 1034 1035 1035 (% style="color:#037691" %)**AT command** ... ... @@ -1049,7 +1049,6 @@ 1049 1049 1050 1050 ==== 3.4.2.4 Enable/Disable Trigger Mode ==== 1051 1051 1052 - 1053 1053 Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]). 1054 1054 1055 1055 (% style="color:#037691" %)**AT Command** ... ... @@ -1085,11 +1085,10 @@ 1085 1085 Enable trigger mode for the current working mode 1086 1086 ))) 1087 1087 1088 -==== 3.4.2.5 Requesttrigger settings ====1026 +==== 3.4.2.5 Poll trigger settings ==== 1089 1089 1028 +Polls the trigger settings. 1090 1090 1091 -Requests the trigger settings. 1092 - 1093 1093 (% style="color:#037691" %)**AT Command:** 1094 1094 1095 1095 There is no AT Command available for this feature. ... ... @@ -1107,7 +1107,6 @@ 1107 1107 1108 1108 ==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ==== 1109 1109 1110 - 1111 1111 Enable or disable DI1/DI2/DI3 as a trigger. 1112 1112 1113 1113 (% style="color:#037691" %)**AT Command** ... ... @@ -1162,9 +1162,9 @@ 1162 1162 1163 1163 ==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ==== 1164 1164 1165 - 1166 1166 Sets DI1 or DI3 (for LT-33222-L) as a trigger. 1167 1167 1103 + 1168 1168 (% style="color:#037691" %)**AT Command** 1169 1169 1170 1170 (% border="2" style="width:500px" %) ... ... @@ -1201,9 +1201,9 @@ 1201 1201 1202 1202 ==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ==== 1203 1203 1204 - 1205 1205 Sets DI2 as a trigger. 1206 1206 1142 + 1207 1207 (% style="color:#037691" %)**AT Command** 1208 1208 1209 1209 (% border="2" style="width:500px" %) ... ... @@ -1235,7 +1235,6 @@ 1235 1235 1236 1236 ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ==== 1237 1237 1238 - 1239 1239 Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1240 1240 1241 1241 (% style="color:#037691" %)**AT Command** ... ... @@ -1285,7 +1285,6 @@ 1285 1285 1286 1286 ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ==== 1287 1287 1288 - 1289 1289 Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1290 1290 1291 1291 (% style="color:#037691" %)**AT Command** ... ... @@ -1333,7 +1333,6 @@ 1333 1333 1334 1334 ==== 3.4.2.11 Trigger – Set minimum interval ==== 1335 1335 1336 - 1337 1337 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. 1338 1338 1339 1339 (% style="color:#037691" %)**AT Command** ... ... @@ -1369,7 +1369,6 @@ 1369 1369 1370 1370 ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ==== 1371 1371 1372 - 1373 1373 Controls the digital outputs DO1, DO2, and DO3 1374 1374 1375 1375 (% style="color:#037691" %)**AT Command** ... ... @@ -1400,11 +1400,11 @@ 1400 1400 ((( 1401 1401 01: Low, 00: High, 11: No action 1402 1402 1403 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:383px" %)1404 -|(% 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**1405 -| (% style="width:126px" %)02 01 00 11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action1406 -| (% style="width:126px" %)02 00 11 01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low1407 -| (% style="width:126px" %)02 11 01 00|(% style="width:85px" %)No Action|(% style="width:86px" %)Low|(% style="width:86px" %)High1335 +(% 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 1408 1408 ))) 1409 1409 1410 1410 ((( ... ... @@ -1423,23 +1423,25 @@ 1423 1423 1424 1424 * (% style="color:#037691" %)**AT Command** 1425 1425 1426 -There is no AT command to controlthe digitaloutput.1358 +There is no AT Command to control Digital Output 1427 1427 1428 1428 1429 1429 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)** 1430 1430 1431 -(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Set sDO1/DO2/DO3 outputswith time control1363 +(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Set DO1/DO2/DO3 output with time control 1432 1432 1365 + 1433 1433 This is to control the digital output time of DO pin. Include four bytes: 1434 1434 1435 -(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)1368 +(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9) 1436 1436 1437 -(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode1370 +(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode 1438 1438 1439 -**01:** DO pins revert to their original state after the timeout. 1440 -**00:** DO pins switch to an inverted state after the timeout. 1372 +01: DO pins will change back to original state after timeout. 1441 1441 1374 +00: DO pins will change to an inverter state after timeout 1442 1442 1376 + 1443 1443 (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status: 1444 1444 1445 1445 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) ... ... @@ -1448,7 +1448,7 @@ 1448 1448 |0x00|DO1 set to high 1449 1449 |0x11|DO1 NO Action 1450 1450 1451 -(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:1385 +(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status: 1452 1452 1453 1453 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1454 1454 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1456,7 +1456,7 @@ 1456 1456 |0x00|DO2 set to high 1457 1457 |0x11|DO2 NO Action 1458 1458 1459 -(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:1393 +(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status: 1460 1460 1461 1461 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1462 1462 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1464,7 +1464,7 @@ 1464 1464 |0x00|DO3 set to high 1465 1465 |0x11|DO3 NO Action 1466 1466 1467 -(% 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) 1468 1468 1469 1469 1470 1470 (% style="color:red" %)**Note: ** ... ... @@ -1473,7 +1473,7 @@ 1473 1473 1474 1474 Before firmware v1.6.0, the latch time only supported 2 bytes. 1475 1475 1476 -(% style="color:red" %)** Thedevice will uplinka packet if the downlink code executes successfully.**1410 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.** 1477 1477 1478 1478 1479 1479 **Example payload:** ... ... @@ -1500,16 +1500,16 @@ 1500 1500 1501 1501 * (% style="color:#037691" %)**AT Command:** 1502 1502 1503 -There is no AT Command to control theRelay Output1437 +There is no AT Command to control Relay Output 1504 1504 1505 1505 1506 1506 * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):** 1507 1507 1508 -(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set sRO1/RO2 output1442 +(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set RO1/RO2 output 1509 1509 1510 1510 1511 1511 ((( 1512 -If thepayload 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. 1513 1513 ))) 1514 1514 1515 1515 ((( ... ... @@ -1527,29 +1527,28 @@ 1527 1527 |03 00 01|Open|Close 1528 1528 ))) 1529 1529 1530 -(% style="color:red" %)** Thedevice will uplinka packet ifthedownlink code executes successfully.**1464 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1531 1531 1532 1532 1533 1533 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== 1534 1534 1535 - 1536 1536 Controls the relay output time. 1537 1537 1538 1538 * (% style="color:#037691" %)**AT Command:** 1539 1539 1540 -There is no AT Command to control theRelay Output1473 +There is no AT Command to control Relay Output 1541 1541 1542 1542 1543 1543 * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):** 1544 1544 1545 -(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set sRO1/RO2 relayswith time control1478 +(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set RO1/RO2 relay with time control 1546 1546 1547 1547 1548 -This control sthe relay output timeandincludes4bytes:1481 +This is to control the relay output time. It includes four bytes: 1549 1549 1550 -(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)1483 +(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05) 1551 1551 1552 -(% style="color:#4f81bd" %)**Second byte1485 +(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode 1553 1553 1554 1554 01: Relays will change back to their original state after timeout. 1555 1555 ... ... @@ -1556,12 +1556,12 @@ 1556 1556 00: Relays will change to the inverter state after timeout. 1557 1557 1558 1558 1559 -(% style="color:#4f81bd" %)**Third byte1492 +(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status: 1560 1560 1561 1561 [[image:image-20221008095908-1.png||height="364" width="564"]] 1562 1562 1563 1563 1564 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes1497 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms 1565 1565 1566 1566 1567 1567 (% style="color:red" %)**Note:** ... ... @@ -1571,7 +1571,7 @@ 1571 1571 Before firmware v1.6.0, the latch time only supported 2 bytes. 1572 1572 1573 1573 1574 -(% style="color:red" %)** Thedevice will uplinka packet if the downlink code executes successfully.**1507 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.** 1575 1575 1576 1576 1577 1577 **Example payload:** ... ... @@ -1730,9 +1730,8 @@ 1730 1730 ))) 1731 1731 |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01** 1732 1732 1733 -==== 3.4.2.19 Counting ~-~- Set SavingIntervalfor 'CountingResult'====1666 +==== 3.4.2.19 Counting ~-~- Change counting mode to save time ==== 1734 1734 1735 - 1736 1736 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. 1737 1737 1738 1738 (% style="color:#037691" %)**AT Command** ... ... @@ -1762,9 +1762,8 @@ 1762 1762 Sets the device to save its counting results to the memory every 60 seconds. 1763 1763 ))) 1764 1764 1765 -==== 3.4.2.20 Reset save dROandDO states====1697 +==== 3.4.2.20 Reset save RO DO state ==== 1766 1766 1767 - 1768 1768 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. 1769 1769 1770 1770 (% style="color:#037691" %)**AT Command** ... ... @@ -1789,6 +1789,7 @@ 1789 1789 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. 1790 1790 ))) 1791 1791 1723 + 1792 1792 (% style="color:#037691" %)**Downlink Payload** 1793 1793 1794 1794 (% border="2" style="width:500px" %) ... ... @@ -1814,7 +1814,6 @@ 1814 1814 1815 1815 ==== 3.4.2.21 Encrypted payload ==== 1816 1816 1817 - 1818 1818 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. 1819 1819 1820 1820 (% style="color:#037691" %)**AT Command:** ... ... @@ -1844,7 +1844,6 @@ 1844 1844 1845 1845 ==== 3.4.2.22 Get sensor value ==== 1846 1846 1847 - 1848 1848 This command allows you to retrieve and optionally uplink sensor readings through the serial port. 1849 1849 1850 1850 (% style="color:#037691" %)**AT Command** ... ... @@ -1874,7 +1874,6 @@ 1874 1874 1875 1875 ==== 3.4.2.23 Resetting the downlink packet count ==== 1876 1876 1877 - 1878 1878 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. 1879 1879 1880 1880 (% style="color:#037691" %)**AT Command** ... ... @@ -1953,33 +1953,43 @@ 1953 1953 1954 1954 ==== 3.4.2.25 Copy downlink to uplink ==== 1955 1955 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. 1956 1956 1957 - Thiscommandenableshe device to immediatelyuplink thepayload of a received downlink packet back tothe server.Thecommandallows for quick data replication from downlink to uplink, with a fixed port number of 100.1887 +* (% style="color:#037691" %)**AT Command**(%%)**:** 1958 1958 1959 -(% style="color: #037691" %)**ATCommand**(%%)**:**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. 1960 1960 1961 - (% style="color:blue" %)**AT+RPL=5**(%%)~/~/Afterreceivingadownlink payloadfromtherver,thedevice will immediately uplinkthe payloadback to the serverusingportnumber100.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. 1962 1962 1963 -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. 1964 1964 1965 - 1966 1966 [[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"]] 1967 1967 1968 1968 For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77. 1969 1969 1970 -[[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 1971 1971 1972 -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: 1973 1973 1907 +01 00 02 58 1974 1974 1975 - (% style="color:#037691" %)**DownlinkPayload**(%%)**:**1909 +Uplink: 1976 1976 1977 -There is no downlink option available for this feature. 1911 +01 01 00 02 58 1912 +))) 1978 1978 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"]] 1979 1979 1980 - ====3.4.2.26Queryfirmwareversion,frequency band,subband,andTDCtime====1916 +For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. 1981 1981 1982 1982 1919 + 1920 +==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ==== 1921 + 1983 1983 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. 1984 1984 1985 1985 * ((( ... ... @@ -1998,13 +1998,10 @@ 1998 1998 1999 1999 == 3.5 Integrating with ThingsEye.io == 2000 2000 2001 - 2002 2002 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. 2003 2003 2004 - 2005 2005 === 3.5.1 Configuring The Things Stack === 2006 2006 2007 - 2008 2008 We use The Things Stack Sandbox in this example: 2009 2009 2010 2010 * In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added. ... ... @@ -2016,12 +2016,10 @@ 2016 2016 The username and password (API key) you created here are required in the next section. 2017 2017 {{/info}} 2018 2018 2019 -[[image:tts-mqtt-integration.png]] 1955 +[[image:tts-mqtt-integration.png||height="625" width="1000"]] 2020 2020 2021 - 2022 2022 === 3.5.2 Configuring ThingsEye.io === 2023 2023 2024 - 2025 2025 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. 2026 2026 2027 2027 * Login to your [[ThingsEye.io >>https://thingseye.io]]account. ... ... @@ -2028,7 +2028,7 @@ 2028 2028 * Under the **Integrations center**, click **Integrations**. 2029 2029 * Click the **Add integration** button (the button with the **+** symbol). 2030 2030 2031 -[[image:thingseye-io-step-1.png]] 1965 +[[image:thingseye-io-step-1.png||height="625" width="1000"]] 2032 2032 2033 2033 2034 2034 On the **Add integration** window, configure the following: ... ... @@ -2043,7 +2043,7 @@ 2043 2043 ** Allow create devices or assets 2044 2044 * Click the **Next** button. you will be navigated to the **Uplink data converter** tab. 2045 2045 2046 -[[image:thingseye-io-step-2.png]] 1980 +[[image:thingseye-io-step-2.png||height="625" width="1000"]] 2047 2047 2048 2048 2049 2049 **Uplink data converter:** ... ... @@ -2054,7 +2054,7 @@ 2054 2054 * 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]]. 2055 2055 * Click the **Next** button. You will be navigated to the **Downlink data converter **tab. 2056 2056 2057 -[[image:thingseye-io-step-3.png]] 1991 +[[image:thingseye-io-step-3.png||height="625" width="1000"]] 2058 2058 2059 2059 2060 2060 **Downlink data converter (this is an optional step):** ... ... @@ -2065,7 +2065,7 @@ 2065 2065 * 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]]. 2066 2066 * Click the **Next** button. You will be navigated to the **Connection** tab. 2067 2067 2068 -[[image:thingseye-io-step-4.png]] 2002 +[[image:thingseye-io-step-4.png||height="625" width="1000"]] 2069 2069 2070 2070 2071 2071 **Connection:** ... ... @@ -2080,21 +2080,20 @@ 2080 2080 2081 2081 * Click the **Add** button. 2082 2082 2083 -[[image:thingseye-io-step-5.png]] 2017 +[[image:thingseye-io-step-5.png||height="625" width="1000"]] 2084 2084 2085 2085 2086 2086 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. 2087 2087 2088 2088 2089 -[[image:thingseye.io_integrationsCenter_integrations.png]] 2023 +[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]] 2090 2090 2091 2091 2092 2092 ==== 3.5.2.1 Viewing integration details ==== 2093 2093 2094 - 2095 2095 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. 2096 2096 2097 -[[image:integration-details.png]] 2030 +[[image:integration-details.png||height="686" width="1000"]] 2098 2098 2099 2099 2100 2100 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. ... ... @@ -2103,32 +2103,28 @@ 2103 2103 See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]]. 2104 2104 {{/info}} 2105 2105 2039 +==== **3.5.2.2 Viewing events** ==== 2106 2106 2107 -==== 3.5.2.2 Viewing events ==== 2108 - 2109 - 2110 2110 The **Events **tab displays all the uplink messages from the LT-22222-L. 2111 2111 2112 2112 * Select **Debug **from the **Event type** dropdown. 2113 2113 * Select the** time frame** from the **time window**. 2114 2114 2115 -[[image:thingseye-events.png]] 2046 +[[image:thingseye-events.png||height="686" width="1000"]] 2116 2116 2117 2117 2118 2118 * To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message. 2119 2119 2120 -[[image:thingseye-json.png]] 2051 +[[image:thingseye-json.png||width="1000"]] 2121 2121 2122 2122 2123 -==== 3.5.2.3 Deleting an integration ==== 2054 +==== **3.5.2.3 Deleting an integration** ==== 2124 2124 2125 - 2126 2126 If you want to delete an integration, click the **Delete integratio**n button on the Integrations page. 2127 2127 2128 2128 2129 2129 ==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ==== 2130 2130 2131 - 2132 2132 This will be added soon. 2133 2133 2134 2134 ... ... @@ -2137,7 +2137,7 @@ 2137 2137 === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) === 2138 2138 2139 2139 2140 -Supports **NPN-type**sensors.2069 +Supports NPN-type sensors. 2141 2141 2142 2142 [[image:1653356991268-289.png]] 2143 2143 ... ... @@ -2259,15 +2259,15 @@ 2259 2259 ))) 2260 2260 2261 2261 2262 -(% style="color:blue" %)**Example aDry Contact sensor2191 +(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor 2263 2263 2264 -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. 2265 2265 2266 -To detect a Dry Contact, you can supply a power source to one of thepinsof the Dry Contact.Areference circuit diagramis 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. 2267 2267 2268 2268 [[image:image-20230616235145-1.png]] 2269 2269 2270 -(% style="color:blue" %)**Example 2199 +(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector 2271 2271 2272 2272 [[image:image-20240219115718-1.png]] 2273 2273 ... ... @@ -2343,9 +2343,8 @@ 2343 2343 [[image:image-20220524100215-10.png||height="382" width="723"]] 2344 2344 2345 2345 2346 -== 3.7 LED Indicators == 2275 +== 3.7 LEDs Indicators == 2347 2347 2348 - 2349 2349 The table below lists the behavior of LED indicators for each port function. 2350 2350 2351 2351 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) ... ... @@ -2378,22 +2378,18 @@ 2378 2378 2379 2379 = 4. Using AT Commands = 2380 2380 2381 - 2382 2382 The LT-22222-L supports programming using AT Commands. 2383 2383 2384 - 2385 2385 == 4.1 Connecting the LT-22222-L to a PC == 2386 2386 2387 - 2388 2388 ((( 2389 -You can use a USB-to-TTL adapter /converteralong 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. 2390 2390 2391 -[[image:usb-ttl-audio-jack-connection.jpg]] 2392 - 2393 - 2316 +[[image:usb-ttl-programming.png]] 2394 2394 ))) 2395 2395 2396 2396 2320 + 2397 2397 ((( 2398 2398 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: 2399 2399 ))) ... ... @@ -2404,10 +2404,7 @@ 2404 2404 ((( 2405 2405 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/]] 2406 2406 2407 - 2408 2408 == 4.2 LT-22222-L related AT commands == 2409 - 2410 - 2411 2411 ))) 2412 2412 2413 2413 ((( ... ... @@ -2426,39 +2426,39 @@ 2426 2426 * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey) 2427 2427 * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI) 2428 2428 * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON) 2429 -* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)2430 -* **##AT+DR##**: Get or set the Data Rate. (0-7 corresponding to DR_X)2431 -* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing2432 -* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)2433 -* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency2434 -* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)2435 -* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms2436 -* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms2437 -* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms2438 -* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms2439 -* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)2440 -* ##**AT+NWKID**##: Get or set the Network ID2441 -* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)2442 -* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)2443 -* ##**AT+CLASS**##: Get or set the Device Class2444 -* ##**AT+JOIN**##: Join network2445 -* ##**AT+NJS**##: Get OTAA Join Status2446 -* ##**AT+SENDB**##: Send hexadecimal data along with the application port2447 -* ##**AT+SEND**##: Send text data along with the application port2448 -* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)2449 -* ##**AT+RECV**##: Print last received data in raw format2450 -* ##**AT+VER**##: Get current image version and Frequency Band2451 -* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)2452 -* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)2453 -* ##**AT+SNR**##: Get the SNR of the last received packet2454 -* ##**AT+RSSI**##: Get the RSSI of the last received packet2455 -* ##**AT+TDC**##: Get or set the application data transmission interval in ms2456 -* ##**AT+PORT**##: Get or set the application port2457 -* ##**AT+DISAT**##: Disable AT commands2458 -* ##**AT+PWORD**##: Set password, max 9 digits2459 -* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode2460 -* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN4702461 -* ##**AT+CFG**##: Print all settings2350 +* 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 2462 2462 ))) 2463 2463 2464 2464 ... ... @@ -2604,19 +2604,16 @@ 2604 2604 2605 2605 == 5.1 Counting how many objects pass through the flow line == 2606 2606 2607 - 2608 2608 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]]? 2609 2609 2610 2610 2611 2611 = 6. FAQ = 2612 2612 2613 - 2614 2614 This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly. 2615 2615 2616 2616 2617 2617 == 6.1 How to update the firmware? == 2618 2618 2619 - 2620 2620 Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to: 2621 2621 2622 2622 * Support new features ... ... @@ -2626,7 +2626,7 @@ 2626 2626 You will need the following things before proceeding: 2627 2627 2628 2628 * 3.5mm programming cable (included with the LT-22222-L as an additional accessory) 2629 -* USB to TTL adapter /converter2547 +* USB to TTL adapter 2630 2630 * 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) 2631 2631 * 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. 2632 2632 ... ... @@ -2636,7 +2636,7 @@ 2636 2636 2637 2637 Below is the hardware setup for uploading a firmware image to the LT-22222-L: 2638 2638 2639 -[[image:usb-ttl- audio-jack-connection.jpg]]2557 +[[image:usb-ttl-programming.png]] 2640 2640 2641 2641 2642 2642 ... ... @@ -2669,8 +2669,6 @@ 2669 2669 ((( 2670 2670 ((( 2671 2671 == 6.2 How to change the LoRaWAN frequency band/region? == 2672 - 2673 - 2674 2674 ))) 2675 2675 ))) 2676 2676 ... ... @@ -2682,8 +2682,6 @@ 2682 2682 2683 2683 2684 2684 == 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? == 2685 - 2686 - 2687 2687 ))) 2688 2688 2689 2689 ((( ... ... @@ -2757,13 +2757,11 @@ 2757 2757 2758 2758 == 6.4 How to change the uplink interval? == 2759 2759 2760 - 2761 2761 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/]] 2762 2762 2763 2763 2764 2764 == 6.5 Can I see the counting event in the serial output? == 2765 2765 2766 - 2767 2767 ((( 2768 2768 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. 2769 2769 ... ... @@ -2770,7 +2770,6 @@ 2770 2770 2771 2771 == 6.6 Can I use point-to-point communication with LT-22222-L? == 2772 2772 2773 - 2774 2774 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]]. 2775 2775 2776 2776 ... ... @@ -2779,7 +2779,6 @@ 2779 2779 ((( 2780 2780 == 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? == 2781 2781 2782 - 2783 2783 * If the device is not properly shut down and is directly powered off. 2784 2784 * It will default to a power-off state. 2785 2785 * In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory. ... ... @@ -2787,7 +2787,6 @@ 2787 2787 2788 2788 == 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? == 2789 2789 2790 - 2791 2791 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: 2792 2792 2793 2793 ... ... @@ -2796,19 +2796,16 @@ 2796 2796 2797 2797 == 6.9 Can the LT-22222-L save the RO state? == 2798 2798 2799 - 2800 2800 To enable this feature, the firmware version must be 1.6.0 or higher. 2801 2801 2802 2802 2803 2803 == 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? == 2804 2804 2805 - 2806 2806 It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose. 2807 2807 2808 2808 2809 2809 = 7. Troubleshooting = 2810 2810 2811 - 2812 2812 This section provides some known troubleshooting tips. 2813 2813 2814 2814 ... ... @@ -2817,8 +2817,6 @@ 2817 2817 ((( 2818 2818 ((( 2819 2819 == 7.1 Downlink isn't working. How can I solve this? == 2820 - 2821 - 2822 2822 ))) 2823 2823 ))) 2824 2824 ... ... @@ -2830,8 +2830,6 @@ 2830 2830 2831 2831 2832 2832 == 7.2 Having trouble uploading an image? == 2833 - 2834 - 2835 2835 ))) 2836 2836 2837 2837 ((( ... ... @@ -2842,8 +2842,6 @@ 2842 2842 2843 2843 2844 2844 == 7.3 Why can't I join TTN in the US915 /AU915 bands? == 2845 - 2846 - 2847 2847 ))) 2848 2848 2849 2849 ((( ... ... @@ -2853,7 +2853,6 @@ 2853 2853 2854 2854 == 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? == 2855 2855 2856 - 2857 2857 The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue. 2858 2858 Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]] 2859 2859 ... ... @@ -2860,7 +2860,6 @@ 2860 2860 2861 2861 = 8. Ordering information = 2862 2862 2863 - 2864 2864 (% style="color:#4f81bd" %)**LT-22222-L-XXX:** 2865 2865 2866 2866 (% style="color:#4f81bd" %)**XXX:** ... ... @@ -2877,7 +2877,6 @@ 2877 2877 2878 2878 = 9. Package information = 2879 2879 2880 - 2881 2881 **Package includes**: 2882 2882 2883 2883 * 1 x LT-22222-L I/O Controller ... ... @@ -2894,7 +2894,6 @@ 2894 2894 2895 2895 = 10. Support = 2896 2896 2897 - 2898 2898 * ((( 2899 2899 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. 2900 2900 ))) ... ... @@ -2906,7 +2906,6 @@ 2906 2906 2907 2907 = 11. Reference = 2908 2908 2909 - 2910 2910 * 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]] 2911 2911 * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]] 2912 2912 * [[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