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, 7 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. pradeeka1 +XWiki.Xiaoling - 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}} ... ... @@ -27,7 +27,7 @@ 27 27 **This manual is also applicable to the LT-33222-L.** 28 28 {{/info}} 29 29 30 -The Dragino (% style="color:blue" %)**LT-22222-L I/O Controller**(%%) is an advanced LoRaWAN device designed to provide seamless wireless long-range connectivity with various I/O options, including analog current and voltage inputs, digital inputs and outputs, and relay outputs. 31 +The Dragino (% style="color:blue" %)**LT-22222-L I/O Controller**(%%) is an advanced LoRaWAN end device designed to provide seamless wireless long-range connectivity with various I/O options, including analog current and voltage inputs, digital inputs and outputs, and relay outputs. 31 31 32 32 The LT-22222-L I/O Controller simplifies and enhances I/O monitoring and controlling. It is ideal for professional applications in wireless sensor networks, including irrigation systems, smart metering, smart cities, building automation, and more. These controllers are designed for easy, cost-effective deployment using LoRa wireless technology. 33 33 ))) ... ... @@ -43,23 +43,21 @@ 43 43 * If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Stack Community Network), you can select a network and register the LT-22222-L I/O controller with it. 44 44 * If there is no public LoRaWAN coverage in your area, you can set up a LoRaWAN gateway, or multiple gateways, and connect them to a LoRaWAN network server to create adequate coverage. Then, register the LT-22222-L I/O controller with this network. 45 45 * Setup your own private LoRaWAN network. 46 - 47 -{{info}} 48 - You can use a LoRaWAN gateway, such as the [[Dragino LG308>>https://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], to expand or create LoRaWAN coverage in your area. 49 -{{/info}} 50 50 ))) 51 51 52 52 ((( 53 53 54 54 55 -The network diagram below s hows how the LT-22222-Lisconnectedtoa typical LoRaWAN network.52 +The network diagram below illustrates how the LT-22222-L communicates with a typical LoRaWAN network. 56 56 ))) 57 57 58 58 (% class="wikigeneratedid" %) 59 59 [[image:lorawan-nw.jpg||height="354" width="900"]] 60 60 58 + 61 61 == 1.2 Specifications == 62 62 61 + 63 63 (% style="color:#037691" %)**Hardware System:** 64 64 65 65 * STM32L072xxxx MCU ... ... @@ -99,8 +99,10 @@ 99 99 * Automatic RF Sense and CAD with ultra-fast AFC. 100 100 * Packet engine up to 256 bytes with CRC. 101 101 101 + 102 102 == 1.3 Features == 103 103 104 + 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 ... ... @@ -109,8 +109,10 @@ 109 109 * Firmware upgradable via program port 110 110 * Counting 111 111 113 + 112 112 == 1.4 Applications == 113 113 116 + 114 114 * Smart buildings & home automation 115 115 * Logistics and supply chain management 116 116 * Smart metering ... ... @@ -118,13 +118,16 @@ 118 118 * Smart cities 119 119 * Smart factory 120 120 124 + 121 121 == 1.5 Hardware Variants == 122 122 123 -(% style="width:524px" %) 124 -|(% style="width:94px" %)**Model**|(% style="width:98px" %)**Photo**|(% style="width:329px" %)**Description** 125 -|(% style="width:94px" %)**LT33222-L**|(% style="width:98px" %)((( 126 - 127 -)))|(% style="width:329px" %)((( 127 + 128 +(% border="1" cellspacing="3" style="width:510px" %) 129 +|(% style="background-color:#4f81bd; color:white; width:94px" %)**Model**|(% style="background-color:#4f81bd; color:white; width:172px" %)**Photo**|(% style="background-color:#4f81bd; color:white; width:244px" %)**Description** 130 +|(% style="width:94px" %)**LT-22222-L**|(% style="width:172px" %)((( 131 +(% style="text-align:center" %) 132 +[[image:lt33222-l.jpg||height="110" width="95"]] 133 +)))|(% style="width:256px" %)((( 128 128 * 2 x Digital Input (Bi-direction) 129 129 * 2 x Digital Output 130 130 * 2 x Relay Output (5A@250VAC / 30VDC) ... ... @@ -134,54 +134,55 @@ 134 134 ))) 135 135 136 136 137 -= =2. Assembling the device ==143 += 2. Assembling the device = 138 138 139 139 == 2.1 Connecting the antenna == 140 140 147 + 141 141 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. 142 142 143 143 {{warning}} 144 -Warning! Do not power on the device without connecting the antenna. 151 +**Warning! Do not power on the device without connecting the antenna.** 145 145 {{/warning}} 146 146 154 + 147 147 == 2.2 Terminals == 148 148 149 -The LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 terminals and the lower screw terminal block has 10 terminals. 150 150 151 - Upperscrew terminal block(from left to right):158 +The LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals. 152 152 153 -(% style="width:634px" %) 154 -|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function 155 -|(% style="width:295px" %)GND|(% style="width:338px" %)Ground 156 -|(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage 157 -|(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2 158 -|(% style="width:295px" %)AVI1|(% style="width:338px" %)Analog Voltage Input Terminal 1 159 -|(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2 160 -|(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1 160 +**Upper screw terminal block (from left to right):** 161 161 162 -Lower screw terminal block (from left to right): 162 +(% border="1" cellspacing="3" style="width:381px;background-color:#f2f2f2" %) 163 +|=(% style="width: 139px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 242px;background-color:#4f81bd" %)Function 164 +|(% style="width:139px" %)GND|(% style="width:242px" %)Ground 165 +|(% style="width:139px" %)VIN|(% style="width:242px" %)Input Voltage 166 +|(% style="width:139px" %)AVI2|(% style="width:242px" %)Analog Voltage Input Terminal 2 167 +|(% style="width:139px" %)AVI1|(% style="width:242px" %)Analog Voltage Input Terminal 1 168 +|(% style="width:139px" %)ACI2|(% style="width:242px" %)Analog Current Input Terminal 2 169 +|(% style="width:139px" %)ACI1|(% style="width:242px" %)Analog Current Input Terminal 1 163 163 164 -(% style="width:633px" %) 165 -|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function 166 -|(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1 167 -|(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1 168 -|(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2 169 -|(% style="width:296px" %)RO2-1|(% style="width:334px" %)Relay Output 2 170 -|(% style="width:296px" %)DI2+|(% style="width:334px" %)Digital Input 2 171 -|(% style="width:296px" %)DI2-|(% style="width:334px" %)Digital Input 2 172 -|(% style="width:296px" %)DI1+|(% style="width:334px" %)Digital Input 1 173 -|(% style="width:296px" %)DI1-|(% style="width:334px" %)Digital Input 1 174 -|(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2 175 -|(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1 171 +**Lower screw terminal block (from left to right):** 176 176 173 +(% border="1" cellspacing="3" style="width:253px;background-color:#f2f2f2" %) 174 +|=(% style="width: 125px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 128px;background-color:#4f81bd;color:white" %)Function 175 +|(% style="width:125px" %)RO1-2|(% style="width:128px" %)Relay Output 1 176 +|(% style="width:125px" %)RO1-1|(% style="width:128px" %)Relay Output 1 177 +|(% style="width:125px" %)RO2-2|(% style="width:128px" %)Relay Output 2 178 +|(% style="width:125px" %)RO2-1|(% style="width:128px" %)Relay Output 2 179 +|(% style="width:125px" %)DI2+|(% style="width:128px" %)Digital Input 2 180 +|(% style="width:125px" %)DI2-|(% style="width:128px" %)Digital Input 2 181 +|(% style="width:125px" %)DI1+|(% style="width:128px" %)Digital Input 1 182 +|(% style="width:125px" %)DI1-|(% style="width:128px" %)Digital Input 1 183 +|(% style="width:125px" %)DO2|(% style="width:128px" %)Digital Output 2 184 +|(% style="width:125px" %)DO1|(% style="width:128px" %)Digital Output 1 185 + 177 177 == 2.3 Connecting LT-22222-L to a Power Source == 178 178 179 179 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. 180 180 181 -Once powered, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** with the Network Server. 182 - 183 183 {{warning}} 184 -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.191 +**We recommend that you power on the LT-22222-L after adding its registration information to the LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.** 185 185 {{/warning}} 186 186 187 187 ... ... @@ -190,16 +190,13 @@ 190 190 191 191 = 3. Registering LT-22222-L with a LoRaWAN Network Server = 192 192 193 - By default, the LT-22222-Lisconfigured to operate in LoRaWAN Class C mode. It 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.200 +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. 194 194 195 195 196 - 197 197 === 3.2.1 Prerequisites === 198 198 199 -The LT-22222-L comes with device registration information that allows you to register it with a LoRaWAN network ,enabling thedevicetoperformOTAAactivationwiththe network serverupon initial power-upandafteranysubsequentreboots.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. 200 200 201 -Make sure you have the device registration information such as DevEUI, AppEUI, and AppKey with you. 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. 202 - 203 203 [[image:image-20230425173427-2.png||height="246" width="530"]] 204 204 205 205 {{info}} ... ... @@ -208,27 +208,35 @@ 208 208 209 209 The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers. 210 210 211 -=== 3.2.2 Registering withThe Things Stack ===215 +=== 3.2.2 The Things Stack === 212 212 217 +This section guides you through how to register your LT-22222-L with The Things Stack Sandbox. 218 + 213 213 {{info}} 214 214 The Things Stack Sandbox was formally called The Things Stack Community Edition. 215 215 {{/info}} 216 216 217 217 218 -The network diagram below s hows how the LT-22222-Lis connectedtoThe Things Stack and integrates itsdatawith the ThingsEye IoT platform.224 +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. 219 219 220 -[[image:dragino-ttn-te.jpg]] 221 221 227 +[[image:dragino-lorawan-nw-lt-22222-n.jpg]] 222 222 223 -* Create a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have a one yet. 229 +{{info}} 230 + 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. 231 +{{/info}} 232 + 233 + 234 +==== 3.2.2.1 Setting up ==== 235 + 236 +* Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet. 224 224 * Log in to your The Things Stack Sandbox account. 225 -* Create an application with The Things Stack if you do not have one yet. 226 -* Go to your application page and click on the **End devices** in the left menu. 238 +* Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs). 239 +* Go to your application's page and click on the **End devices** in the left menu. 227 227 * On the End devices page, click on **+ Register end device**. Two registration options are available: 228 228 242 +==== 3.2.2.2 Using the LoRaWAN Device Repository ==== 229 229 230 -==== 3.2.2.1 Using the LoRaWAN Device Repository ==== 231 - 232 232 * On the **Register end device** page: 233 233 ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**. 234 234 ** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists. ... ... @@ -239,10 +239,9 @@ 239 239 *** **Profile (Region)**: Select the region that matches your device. 240 240 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 241 241 254 +[[image:lt-22222-l-dev-repo-reg-p1.png]] 242 242 243 -[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]] 244 244 245 - 246 246 * Register end device page continued... 247 247 ** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network'. 248 248 ** In the **DevEUI** field, enter the **DevEUI**. ... ... @@ -250,11 +250,10 @@ 250 250 ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. 251 251 ** Under **After registration**, select the **View registered end device** option. 252 252 253 -[[image:lt-22222-l-dev-repo-reg-p2.png ||height="625" width="1000"]]264 +[[image:lt-22222-l-dev-repo-reg-p2.png]] 254 254 255 -==== ==== 256 256 257 -==== 3.2.2. 2Adding device manually ====267 +==== 3.2.2.3 Adding device manually ==== 258 258 259 259 * On the **Register end device** page: 260 260 ** Select the option **Enter end device specifies manually** under **Input method**. ... ... @@ -265,11 +265,11 @@ 265 265 ** Select the option **Over the air activation (OTAA)** under the **Activation mode.** 266 266 ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list. 267 267 268 -[[image:lt-22222-l-manually-p1.png ||height="625" width="1000"]]278 +[[image:lt-22222-l-manually-p1.png]] 269 269 270 270 271 271 * Register end device page continued... 272 -** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network' 282 +** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message '//**This end device can be registered on the network**//' 273 273 ** In the **DevEUI** field, enter the **DevEUI**. 274 274 ** In the **AppKey** field, enter the **AppKey**. 275 275 ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. ... ... @@ -276,28 +276,29 @@ 276 276 ** Under **After registration**, select the **View registered end device** option. 277 277 ** Click the **Register end device** button. 278 278 279 -[[image:lt-22222-l-manually-p2.png ||height="625" width="1000"]]289 +[[image:lt-22222-l-manually-p2.png]] 280 280 281 281 282 282 You will be navigated to the **Device overview** page. 283 283 284 284 285 -[[image:lt-22222-device-overview.png ||height="625" width="1000"]]295 +[[image:lt-22222-device-overview.png]] 286 286 287 287 288 -==== 3.2.2. 3Joining ====298 +==== 3.2.2.4 Joining ==== 289 289 290 -On the Device overviewpage, click on **Live data** tab. The Live data panel for your device will display.300 +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. 293 293 294 294 295 -[[image:lt-22222-join -network.png||height="625" width="1000"]]305 +[[image:lt-22222-l-joining.png]] 296 296 297 297 298 -==== 3.2.2.4 Uplinks ==== 299 299 309 +==== 3.2.2.5 Uplinks ==== 300 300 311 + 301 301 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. 302 302 303 303 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. ... ... @@ -305,17 +305,23 @@ 305 305 [[image:lt-22222-ul-payload-decoded.png]] 306 306 307 307 308 -If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **End devices** > ** LT-22222-L**319 +If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **Applications > your application > End devices** > **your end device** > **Payload formatters** > **Uplink**. Then select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes. 309 309 310 310 {{info}} 311 311 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. 312 312 {{/info}} 313 313 314 -[[image:lt-22222-ul-payload-fmt.png ||height="686" width="1000"]]325 +[[image:lt-22222-ul-payload-fmt.png]] 315 315 316 316 317 - ====3.2.2.4Uplinks====328 +We also have a payload formatter that resolves some decoding issues present in the Device Repository formatter. You can add it under the Custom JavaScript formatter. It can be found [[here>>https://github.com/dragino/dragino-end-node-decoder/blob/main/LT22222-L/v1.6_decoder_ttn%20.txt]]: 318 318 330 +(% class="wikigeneratedid" %) 331 +[[image:lt-22222-l-js-custom-payload-formatter.png]] 332 + 333 + 334 +==== 3.2.2.6 Downlinks ==== 335 + 319 319 When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**. 320 320 321 321 ... ... @@ -602,11 +602,11 @@ 602 602 603 603 (% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)** 604 604 605 -(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20 v), counter increase 1)**622 +(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), the counter increases by 1)** 606 606 607 -(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20 v), counter increase 1)**624 +(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If the AVI1 voltage is lower than VOLMAX (20000mV =20V), counter increases by 1)** 608 608 609 -(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20 v), counter increase 1)**626 +(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), counter increases by 1)** 610 610 ))) 611 611 612 612 ... ... @@ -725,9 +725,9 @@ 725 725 726 726 (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:** 727 727 728 -Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 745 +**Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 729 729 730 -Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4 747 +**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4 731 731 732 732 AA: Type Code for this downlink Command: 733 733 ... ... @@ -756,7 +756,7 @@ 756 756 757 757 MOD6 Payload: total of 11 bytes 758 758 759 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:515px" %)776 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) 760 760 |(% 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** 761 761 |Value|((( 762 762 TRI_A FLAG ... ... @@ -770,7 +770,7 @@ 770 770 771 771 (% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below 772 772 773 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:515px" %)790 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) 774 774 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 775 775 |((( 776 776 AV1_LOW ... ... @@ -794,12 +794,12 @@ 794 794 795 795 **Example:** 796 796 797 -10100000: Means the systemhas configure to use the trigger:AV1_LOW and AV2_LOW814 +10100000: This means the system is configured to use the triggers AV1_LOW and AV2_LOW. 798 798 799 799 800 800 (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below 801 801 802 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:515px" %)819 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) 803 803 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 804 804 |((( 805 805 AV1_LOW ... ... @@ -823,31 +823,31 @@ 823 823 824 824 **Example:** 825 825 826 -10000000: Meansthisuplink is triggered by AV1_LOW.Thatmeansthe voltage is too low.843 +10000000: The uplink is triggered by AV1_LOW, indicating that the voltage is too low. 827 827 828 828 829 829 (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below 830 830 831 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:674px" %)832 -|(% 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**833 -|(% 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_FLAG848 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) 849 +|(% style="width:50px" %)**bit 7**|(% style="width:50px" %)**bit 6**|(% style="width:50px" %)**bit 5**|(% style="width:50px" %)**bit 4**|(% style="width:90px" %)**bit 3**|(% style="width:80px" %)**bit 2**|(% style="width:90px" %)**bit 1**|(% style="width:95px" %)**bit 0** 850 +|(% style="width:49px" %)N/A|(% style="width:53px" %)N/A|(% style="width:53px" %)N/A|(% style="width:55px" %)N/A|(% style="width:99px" %)DI2_STATUS|(% style="width:83px" %)DI2_FLAG|(% style="width:98px" %)DI1_STATUS|(% style="width:85px" %)DI1_FLAG 834 834 835 -* Each bit sshows which status has been triggered on this uplink.852 +* Each bit shows which status has been triggered on this uplink. 836 836 837 837 **Example:** 838 838 839 -00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.856 +00000111: This means both DI1 and DI2 triggers are enabled, and this packet is trigger by DI1. 840 840 841 -00000101: Means both DI1 and DI2 trigger are enabled.858 +00000101: This means both DI1 and DI2 triggers are enabled. 842 842 843 843 844 -(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable. 861 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled. 845 845 846 -Downlink command to poll MOD6 status: 863 +Downlink command to poll/request MOD6 status: 847 847 848 848 **AB 06** 849 849 850 -When device gotthis command, it will send the MOD6 payload.867 +When device receives this command, it will send the MOD6 payload. 851 851 852 852 853 853 === 3.3.7 Payload Decoder === ... ... @@ -861,6 +861,7 @@ 861 861 862 862 == 3.4 Configure LT-22222-L via AT Commands or Downlinks == 863 863 881 + 864 864 ((( 865 865 You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks. 866 866 ))) ... ... @@ -877,17 +877,22 @@ 877 877 878 878 === 3.4.1 Common commands === 879 879 898 + 880 880 ((( 881 881 These are available for each sensors and include actions such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]s. 901 + 902 + 882 882 ))) 883 883 884 884 === 3.4.2 Sensor-related commands === 885 885 907 + 886 886 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. 887 887 888 888 889 -==== 3.4.2.1 Set Transmit Interval ==== 911 +==== 3.4.2.1 Set Transmit/Uplink Interval ==== 890 890 913 + 891 891 Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes. 892 892 893 893 (% style="color:#037691" %)**AT command** ... ... @@ -894,12 +894,19 @@ 894 894 895 895 (% border="2" style="width:500px" %) 896 896 |**Command**|AT+TDC=<time> 897 -|**Response**| 898 -|**Parameters**|**time** : uplink interval is in milliseconds 920 +|**Parameters**|**time **: uplink interval in milliseconds 921 +|**Get**|AT+TDC=? 922 +|**Response**|((( 923 +current uplink interval 924 + 925 +OK 926 +))) 927 +|**Set**|AT+TDC=<time> 928 +|**Response**|OK 899 899 |**Example**|((( 900 900 AT+TDC=30000 901 901 902 -Sets the uplink interval to 30 ,000milliseconds (30 seconds)932 +Sets the uplink interval to **30 seconds** (30000 milliseconds) 903 903 ))) 904 904 905 905 (% style="color:#037691" %)**Downlink payload** ... ... @@ -911,27 +911,29 @@ 911 911 |**Parameters**|((( 912 912 **prefix** : 0x01 913 913 914 -**time** : uplink interval i s inmilliseconds, represented by 3 bytes in hexadecimal.944 +**time** : uplink interval in **seconds**, represented by **3 bytes** in **hexadecimal**. 915 915 ))) 916 916 |**Example**|((( 917 -01 **00 75 30**947 +01 **00 00 1E** 918 918 919 -Sets the uplink interval to 30 ,000milliseconds(30 seconds)949 +Sets the uplink interval to **30 seconds** 920 920 921 -Conversion: 30 000(dec) = 0075 30 (hex)951 +Conversion: 30 (dec) = 00 00 1E (hex) 922 922 923 -See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]] 953 +See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30]] 954 + 955 +[[image:Screenshot 2024-11-23 at 18.27.11.png]] 924 924 ))) 925 925 926 926 ==== 3.4.2.2 Set the Working Mode (AT+MOD) ==== 927 927 960 + 928 928 Sets the working mode. 929 929 930 930 (% style="color:#037691" %)**AT command** 931 931 932 932 (% border="2" style="width:500px" %) 933 -|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE=<working_mode> 934 -|(% style="width:97px" %)**Response**|(% style="width:413px" %) 966 +|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MOD=<working_mode> 935 935 |(% style="width:97px" %)**Parameters**|(% style="width:413px" %)((( 936 936 **working_mode** : 937 937 ... ... @@ -947,6 +947,18 @@ 947 947 948 948 6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5 949 949 ))) 982 +|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=? 983 +|(% style="width:97px" %)**Response**|(% style="width:413px" %)((( 984 +Current working mode 985 + 986 +OK 987 +))) 988 +|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode> 989 +|(% style="width:97px" %)**Response**|(% style="width:413px" %)((( 990 +Attention:Take effect after ATZ 991 + 992 +OK 993 +))) 950 950 |(% style="width:97px" %)**Example**|(% style="width:413px" %)((( 951 951 AT+MOD=2 952 952 ... ... @@ -969,13 +969,14 @@ 969 969 Sets the device to working mode 2 (Double DI Counting + DO + RO) 970 970 ))) 971 971 972 -==== 3.4.2.3 Pollan uplink ====1016 +==== 3.4.2.3 Request an uplink from the device ==== 973 973 974 -Requests an uplink from LT-22222-L. 975 975 1019 +Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode. 1020 + 976 976 (% style="color:#037691" %)**AT command** 977 977 978 -There is no AT Command torequestan uplinkfrom LT-22222-L1023 +There is no AT Command available for this feature. 979 979 980 980 (% style="color:#037691" %)**Downlink payload** 981 981 ... ... @@ -983,7 +983,7 @@ 983 983 |(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF 984 984 |(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08 985 985 |(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 986 -08 FF 1031 +08 **FF** 987 987 988 988 Requests an uplink from LT-22222-L. 989 989 ))) ... ... @@ -990,6 +990,7 @@ 990 990 991 991 ==== 3.4.2.4 Enable/Disable Trigger Mode ==== 992 992 1038 + 993 993 Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]). 994 994 995 995 (% style="color:#037691" %)**AT Command** ... ... @@ -1017,7 +1017,7 @@ 1017 1017 |(% style="width:97px" %)**Parameters**|(% style="width:401px" %)((( 1018 1018 **prefix** : 0x0A 06 (two bytes in hexadecimal) 1019 1019 1020 -** working1066 +**enable/disable trigger_mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal. 1021 1021 ))) 1022 1022 |(% style="width:97px" %)**Example**|(% style="width:401px" %)((( 1023 1023 0A 06 **01** ... ... @@ -1025,13 +1025,14 @@ 1025 1025 Enable trigger mode for the current working mode 1026 1026 ))) 1027 1027 1028 -==== 3.4.2.5 Polltrigger settings ====1074 +==== 3.4.2.5 Request trigger settings ==== 1029 1029 1030 -Polls the trigger settings. 1031 1031 1077 +Requests the trigger settings. 1078 + 1032 1032 (% style="color:#037691" %)**AT Command:** 1033 1033 1034 -There is no AT Command for this feature. 1081 +There is no AT Command available for this feature. 1035 1035 1036 1036 (% style="color:#037691" %)**Downlink Payload** 1037 1037 ... ... @@ -1046,6 +1046,7 @@ 1046 1046 1047 1047 ==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ==== 1048 1048 1096 + 1049 1049 Enable or disable DI1/DI2/DI3 as a trigger. 1050 1050 1051 1051 (% style="color:#037691" %)**AT Command** ... ... @@ -1100,9 +1100,9 @@ 1100 1100 1101 1101 ==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ==== 1102 1102 1151 + 1103 1103 Sets DI1 or DI3 (for LT-33222-L) as a trigger. 1104 1104 1105 - 1106 1106 (% style="color:#037691" %)**AT Command** 1107 1107 1108 1108 (% border="2" style="width:500px" %) ... ... @@ -1139,9 +1139,9 @@ 1139 1139 1140 1140 ==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ==== 1141 1141 1190 + 1142 1142 Sets DI2 as a trigger. 1143 1143 1144 - 1145 1145 (% style="color:#037691" %)**AT Command** 1146 1146 1147 1147 (% border="2" style="width:500px" %) ... ... @@ -1171,10 +1171,9 @@ 1171 1171 ))) 1172 1172 |(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64** 1173 1173 1174 -==== ==== 1175 - 1176 1176 ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ==== 1177 1177 1224 + 1178 1178 Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1179 1179 1180 1180 (% style="color:#037691" %)**AT Command** ... ... @@ -1224,6 +1224,7 @@ 1224 1224 1225 1225 ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ==== 1226 1226 1274 + 1227 1227 Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1228 1228 1229 1229 (% style="color:#037691" %)**AT Command** ... ... @@ -1271,6 +1271,7 @@ 1271 1271 1272 1272 ==== 3.4.2.11 Trigger – Set minimum interval ==== 1273 1273 1322 + 1274 1274 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. 1275 1275 1276 1276 (% style="color:#037691" %)**AT Command** ... ... @@ -1306,6 +1306,7 @@ 1306 1306 1307 1307 ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ==== 1308 1308 1358 + 1309 1309 Controls the digital outputs DO1, DO2, and DO3 1310 1310 1311 1311 (% style="color:#037691" %)**AT Command** ... ... @@ -1336,11 +1336,11 @@ 1336 1336 ((( 1337 1337 01: Low, 00: High, 11: No action 1338 1338 1339 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:510px" %)1340 -|(% 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** 1341 -|02 01 00 11|Low|High|No Action 1342 -|02 00 11 01|High|No Action|Low 1343 -|02 11 01 00|No Action|Low|High 1389 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:383px" %) 1390 +|(% style="background-color:#4f81bd; color:white; width:126px" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white; width:85px" %)**DO1**|(% style="background-color:#4f81bd; color:white; width:86px" %)**DO2**|(% style="background-color:#4f81bd; color:white; width:86px" %)**DO3** 1391 +|(% style="width:126px" %)02 01 00 11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action 1392 +|(% style="width:126px" %)02 00 11 01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low 1393 +|(% style="width:126px" %)02 11 01 00|(% style="width:85px" %)No Action|(% style="width:86px" %)Low|(% style="width:86px" %)High 1344 1344 ))) 1345 1345 1346 1346 ((( ... ... @@ -1354,32 +1354,28 @@ 1354 1354 ))) 1355 1355 ))) 1356 1356 1357 -==== ==== 1358 - 1359 1359 ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ==== 1360 1360 1361 1361 1362 1362 * (% style="color:#037691" %)**AT Command** 1363 1363 1364 -There is no AT Command to controlDigitalOutput1412 +There is no AT command to control the digital output. 1365 1365 1366 1366 1367 1367 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)** 1368 1368 1369 -(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Set DO1/DO2/DO3 output with time control 1417 +(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control 1370 1370 1371 - 1372 1372 This is to control the digital output time of DO pin. Include four bytes: 1373 1373 1374 -(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)1421 +(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9) 1375 1375 1376 -(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode1423 +(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode 1377 1377 1378 -01: DO pins will change back to original state after timeout. 1425 +**01:** DO pins revert to their original state after the timeout. 1426 +**00:** DO pins switch to an inverted state after the timeout. 1379 1379 1380 -00: DO pins will change to an inverter state after timeout 1381 1381 1382 - 1383 1383 (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status: 1384 1384 1385 1385 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) ... ... @@ -1388,7 +1388,7 @@ 1388 1388 |0x00|DO1 set to high 1389 1389 |0x11|DO1 NO Action 1390 1390 1391 -(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:1437 +(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status: 1392 1392 1393 1393 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1394 1394 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1396,7 +1396,7 @@ 1396 1396 |0x00|DO2 set to high 1397 1397 |0x11|DO2 NO Action 1398 1398 1399 -(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:1445 +(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status: 1400 1400 1401 1401 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1402 1402 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1404,7 +1404,7 @@ 1404 1404 |0x00|DO3 set to high 1405 1405 |0x11|DO3 NO Action 1406 1406 1407 -(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)1453 +(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms) 1408 1408 1409 1409 1410 1410 (% style="color:red" %)**Note: ** ... ... @@ -1413,7 +1413,7 @@ 1413 1413 1414 1414 Before firmware v1.6.0, the latch time only supported 2 bytes. 1415 1415 1416 -(% style="color:red" %)** Device will uploada packet if the downlink code executes successfully.**1462 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.** 1417 1417 1418 1418 1419 1419 **Example payload:** ... ... @@ -1440,16 +1440,16 @@ 1440 1440 1441 1441 * (% style="color:#037691" %)**AT Command:** 1442 1442 1443 -There is no AT Command to control Relay Output 1489 +There is no AT Command to control the Relay Output 1444 1444 1445 1445 1446 1446 * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):** 1447 1447 1448 -(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set RO1/RO2 output 1494 +(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Sets RO1/RO2 output 1449 1449 1450 1450 1451 1451 ((( 1452 -If payload is 0x030100, it means setting RO1 to close and RO2 to open. 1498 +If the payload is 0x030100, it means setting RO1 to close and RO2 to open. 1453 1453 ))) 1454 1454 1455 1455 ((( ... ... @@ -1467,28 +1467,29 @@ 1467 1467 |03 00 01|Open|Close 1468 1468 ))) 1469 1469 1470 -(% style="color:red" %)** Device will uploada packet if downlink code executes successfully.**1516 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.** 1471 1471 1472 1472 1473 1473 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== 1474 1474 1521 + 1475 1475 Controls the relay output time. 1476 1476 1477 1477 * (% style="color:#037691" %)**AT Command:** 1478 1478 1479 -There is no AT Command to control Relay Output 1526 +There is no AT Command to control the Relay Output 1480 1480 1481 1481 1482 1482 * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):** 1483 1483 1484 -(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set RO1/RO2 relay with time control 1531 +(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Sets RO1/RO2 relays with time control 1485 1485 1486 1486 1487 -This is tocontrol the relay output time.Itincludesfourbytes:1534 +This controls the relay output time and includes 4 bytes: 1488 1488 1489 -(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)1536 +(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05) 1490 1490 1491 -(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode1538 +(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode 1492 1492 1493 1493 01: Relays will change back to their original state after timeout. 1494 1494 ... ... @@ -1495,12 +1495,12 @@ 1495 1495 00: Relays will change to the inverter state after timeout. 1496 1496 1497 1497 1498 -(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:1545 +(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status: 1499 1499 1500 1500 [[image:image-20221008095908-1.png||height="364" width="564"]] 1501 1501 1502 1502 1503 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms1550 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes (cc)**(%%): Latching time. Unit: ms 1504 1504 1505 1505 1506 1506 (% style="color:red" %)**Note:** ... ... @@ -1510,7 +1510,7 @@ 1510 1510 Before firmware v1.6.0, the latch time only supported 2 bytes. 1511 1511 1512 1512 1513 -(% style="color:red" %)** Device will uploada packet if the downlink code executes successfully.**1560 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.** 1514 1514 1515 1515 1516 1516 **Example payload:** ... ... @@ -1538,17 +1538,10 @@ 1538 1538 1539 1539 When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1540 1540 1541 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1542 - 1543 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):** 1544 - 1545 -(% style="color:blue" %)**0xA5 aa bb cc ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc 1546 - 1547 - 1548 1548 (% style="color:#037691" %)**AT Command** 1549 1549 1550 1550 (% border="2" style="width:500px" %) 1551 -|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage><logic> 1591 +|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage>,<logic> 1552 1552 |(% style="width:137px" %)**Response**|(% style="width:361px" %) 1553 1553 |(% style="width:137px" %)**Parameters**|(% style="width:361px" %)((( 1554 1554 **voltage** : voltage threshold in mV ... ... @@ -1555,9 +1555,9 @@ 1555 1555 1556 1556 **logic**: 1557 1557 1558 -0 : lower than 1598 +**0** : lower than 1559 1559 1560 -1: higher than 1600 +**1**: higher than 1561 1561 1562 1562 if you leave logic parameter blank, it is considered 0 1563 1563 ))) ... ... @@ -1586,9 +1586,9 @@ 1586 1586 1587 1587 **logic**: (1 byte in hexadecimal) 1588 1588 1589 -0 : lower than 1629 +**0** : lower than 1590 1590 1591 -1: higher than 1631 +**1**: higher than 1592 1592 1593 1593 if you leave logic parameter blank, it is considered 1 (higher than) 1594 1594 ))) ... ... @@ -1608,24 +1608,12 @@ 1608 1608 1609 1609 ==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ==== 1610 1610 1611 -This featureallows users to pre-configure specific count numbers for various counting parameters such as Count1, Count2, or AVI1 Count. Use the AT command to set the desired count number for each configuration.1651 +This command allows users to pre-configure specific count numbers for various counting parameters such as Count1, Count2, or AVI1 Count. Use the AT command to set the desired count number for each configuration. 1612 1612 1613 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) ** 1614 - 1615 -(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count 1616 - 1617 -(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set 1618 - 1619 - 1620 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):** 1621 - 1622 -(% style="color:blue" %)**0x A8 aa bb cc dd ee ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee) 1623 - 1624 - 1625 1625 (% style="color:#037691" %)**AT Command** 1626 1626 1627 1627 (% border="2" style="width:500px" %) 1628 -|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter><number> 1656 +|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter>,<number> 1629 1629 |(% style="width:134px" %)**Response**|(% style="width:364px" %) 1630 1630 |(% style="width:134px" %)**Parameters**|(% style="width:364px" %)((( 1631 1631 **counting_parameter** : ... ... @@ -1669,14 +1669,8 @@ 1669 1669 1670 1670 ==== 3.4.2.18 Counting ~-~- Clear Counting ==== 1671 1671 1672 -This featureclears the counting in counting mode.1700 +This command clears the counting in counting mode. 1673 1673 1674 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT **(%%) ~/~/ clear all counting 1675 - 1676 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):** 1677 - 1678 -(% style="color:blue" %)**0x A6 01 ** (%%)~/~/ clear all counting 1679 - 1680 1680 (% style="color:#037691" %)**AT Command** 1681 1681 1682 1682 (% border="2" style="width:500px" %) ... ... @@ -1694,122 +1694,264 @@ 1694 1694 ))) 1695 1695 |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01** 1696 1696 1697 -==== 3.4.2.19 Counting ~-~- Changecountingmodetosavetime====1719 +==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ==== 1698 1698 1699 -This feature 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. 1700 1700 1701 - *(%style="color:#037691"%)**ATCommand:**1722 +This command allows you to configure the device to save its counting result to internal flash memory at specified intervals. By setting a save time, the device will periodically store the counting data to prevent loss in case of power failure. The save interval can be adjusted to suit your requirements, with a minimum value of 30 seconds. 1702 1702 1703 -(% style="color: blue" %)**AT+COUTIME=60**(%%)~/~/ Sets the save time to60 seconds. The device will save the counting result in internal flash every 60 seconds. (Min value: 30 seconds)1724 +(% style="color:#037691" %)**AT Command** 1704 1704 1726 +(% border="2" style="width:500px" %) 1727 +|(% style="width:124px" %)**Command**|(% style="width:374px" %)AT+COUTIME=<time> 1728 +|(% style="width:124px" %)**Response**|(% style="width:374px" %) 1729 +|(% style="width:124px" %)**Parameters**|(% style="width:374px" %)time : seconds (0 to 16777215) 1730 +|(% style="width:124px" %)**Example**|(% style="width:374px" %)((( 1731 +AT+COUTIME=60 1705 1705 1706 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):** 1733 +Sets the device to save its counting results to the memory every 60 seconds. 1734 +))) 1707 1707 1708 -(% style="color: blue" %)**0xA7aabb cc**(%%)~/~/ same as AT+COUTIME =aa bb cc,1736 +(% style="color:#037691" %)**Downlink Payload** 1709 1709 1710 -((( 1711 -Range: aa bb cc:0 to 16777215, (unit: seconds) 1738 +(% border="2" style="width:500px" %) 1739 +|(% style="width:123px" %)**Payload**|(% style="width:375px" %)<prefix><time> 1740 +|(% style="width:123px" %)**Parameters**|(% style="width:375px" %)((( 1741 +prefix : A7 1742 + 1743 +time : seconds, 3 bytes in hexadecimal 1712 1712 ))) 1745 +|(% style="width:123px" %)**Example**|(% style="width:375px" %)((( 1746 +A7 **00 00 3C** 1713 1713 1748 +Sets the device to save its counting results to the memory every 60 seconds. 1749 +))) 1714 1714 1751 +==== 3.4.2.20 Reset saved RO and DO states ==== 1715 1715 1716 -==== 3.4.2.20 Reset save RO DO state ==== 1717 1717 1718 -This featureallows 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.1754 +This command allows you to reset the saved relay output (RO) and digital output (DO) states when the device joins the network. By configuring this setting, you can control whether the device should retain or reset the relay states after a reset and rejoin to the network. 1719 1719 1720 - *(% style="color:#037691" %)**AT Command:**1756 +(% style="color:#037691" %)**AT Command** 1721 1721 1722 -(% style="color:blue" %)**AT+RODORESET=1 **(%%)~/~/ RODO will close when the device joining the network. (default) 1758 +(% border="2" style="width:500px" %) 1759 +|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state> 1760 +|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1761 +|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1762 +**state** : 1723 1723 1724 - (% style="color:blue" %)**AT+RODORESET=0(%%)~/~/After the device is reset, the previously savedRODOstate (only MOD2 to MOD5) is read, and its statewillnotchange when the devicereconnects to the network.1764 +**0** : RODO will close when the device joins the network. (default) 1725 1725 1766 +**1**: 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. 1767 +))) 1768 +|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1769 +(% style="color:blue" %)**AT+RODORESET=1 ** 1726 1726 1727 - *(% style="color:#037691"%)**DownlinkPayload(prefix 0xAD):**1771 +RODO will close when the device joins the network. (default) 1728 1728 1729 -(% style="color:blue" %)** 0xAD aa ** (%%)~/~/ same as AT+RODORETaa1773 +(% style="color:blue" %)**AT+RODORESET=0 ** 1730 1730 1775 +After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network. 1776 +))) 1731 1731 1778 +(% style="color:#037691" %)**Downlink Payload** 1732 1732 1780 +(% border="2" style="width:500px" %) 1781 +|(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state> 1782 +|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1783 +**prefix** : AD 1784 + 1785 +**state** : 1786 + 1787 +**0** : RODO will close when the device joins the network. (default), represents as 1 byte in hexadecimal. 1788 + 1789 +**1**: 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. - represents as 1 byte in hexadecimal 1790 +))) 1791 +|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1792 +AD **01** 1793 + 1794 +RODO will close when the device joins the network. (default) 1795 + 1796 +AD **00** 1797 + 1798 +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. 1799 +))) 1800 + 1733 1733 ==== 3.4.2.21 Encrypted payload ==== 1734 1734 1735 -This feature 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. 1736 1736 1737 - *(%style="color:#037691"%)**ATCommand:**1804 +This command allows you to configure whether the device should upload data in an encrypted format or in plaintext. By default, the device encrypts the payload before uploading. You can toggle this setting to either upload encrypted data or transmit it without encryption. 1738 1738 1739 -(% style="color: blue" %)**AT+DECRYPT=1** (%%)~/~/ The payload is uploaded without encryption1806 +(% style="color:#037691" %)**AT Command:** 1740 1740 1741 -(% style="color:blue" %)**AT+DECRYPT=0 **(%%)~/~/ Encrypt when uploading payload (default) 1808 +(% border="2" style="width:500px" %) 1809 +|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state> 1810 +|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1811 +|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1812 +**state** : 1742 1742 1814 +**1** : The payload is uploaded without encryption 1743 1743 1816 +**0** : The payload is encrypted when uploaded (default) 1817 +))) 1818 +|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1819 +AT+DECRYPT=1 1744 1744 1821 +The payload is uploaded without encryption 1822 + 1823 +AT+DECRYPT=0 1824 + 1825 +The payload is encrypted when uploaded (default) 1826 +))) 1827 + 1828 +There is no downlink payload for this configuration. 1829 + 1830 + 1745 1745 ==== 3.4.2.22 Get sensor value ==== 1746 1746 1747 1747 1748 - *(%style="color:#037691"%)**ATCommand:**1834 +This command allows you to retrieve and optionally uplink sensor readings through the serial port. 1749 1749 1750 -(% style="color: blue" %)**AT+GETSENSORVALUE=0**(%%)~/~/ The serial port retrieves the reading of the current sensor.1836 +(% style="color:#037691" %)**AT Command** 1751 1751 1752 -(% style="color:blue" %)**AT+GETSENSORVALUE=1 **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it. 1838 +(% border="2" style="width:500px" %) 1839 +|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state> 1840 +|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1841 +|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1842 +**state** : 1753 1753 1844 +**0 **: Retrieves the current sensor reading via the serial port. 1754 1754 1846 +**1 **: Retrieves and uploads the current sensor reading via the serial port. 1847 +))) 1848 +|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1849 +AT+GETSENSORVALUE=0 1755 1755 1756 - ==== 3.4.2.23Resets thedownlinkpacketcount====1851 +Retrieves the current sensor reading via the serial port. 1757 1757 1853 +AT+GETSENSORVALUE=1 1758 1758 1759 -* (% style="color:#037691" %)**AT Command:** 1855 +Retrieves and uplinks the current sensor reading via the serial port. 1856 +))) 1760 1760 1761 - (% style="color:blue" %)**AT+DISFCNTCHECK=0 **(%%)~/~/ When the downlink packet count sent by the serverisless thanthe nodedownlink packet countorexceeds 16384,the node willnolongerreceive downlink packets (default)1858 +There is no downlink payload for this configuration. 1762 1762 1763 -(% style="color:blue" %)**AT+DISFCNTCHECK=1 **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node resets the downlink packet count and keeps it consistent with the server downlink packet count. 1764 1764 1861 +==== 3.4.2.23 Resetting the downlink packet count ==== 1765 1765 1766 1766 1864 +This command manages how the node handles mismatched downlink packet counts. It offers two modes: one disables the reception of further downlink packets if discrepancies occur, while the other resets the downlink packet count to align with the server, ensuring continued communication. 1865 + 1866 +(% style="color:#037691" %)**AT Command** 1867 + 1868 +(% border="2" style="width:500px" %) 1869 +|(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state> 1870 +|(% style="width:130px" %)**Response**|(% style="width:368px" %)((( 1871 + 1872 +))) 1873 +|(% style="width:130px" %)**Parameters**|(% style="width:368px" %)((( 1874 +**state **: 1875 + 1876 +**0** : When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node stops receiving further downlink packets (default). 1877 + 1878 + 1879 +**1** : When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node resets its downlink packet count to match the server's, ensuring consistency. 1880 +))) 1881 +|(% style="width:130px" %)**Example**|(% style="width:368px" %)((( 1882 +AT+DISFCNTCHECK=0 1883 + 1884 +When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node stops receiving further downlink packets (default). 1885 + 1886 +AT+DISFCNTCHECK=1 1887 + 1888 +When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node resets its downlink packet count to match the server's, ensuring consistency. 1889 +))) 1890 + 1891 +There is no downlink payload for this configuration. 1892 + 1893 + 1767 1767 ==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ==== 1768 1768 1769 1769 1770 - *(%style="color:#037691"%)**ATCommand:**1897 +This command controls the behavior of the node when the combined size of the MAC commands (MACANS) from the server and the payload exceeds the allowed byte limit for the current data rate (DR). The command provides two modes: one enables splitting the data into batches to ensure compliance with the byte limit, while the other prioritizes the payload and ignores the MACANS in cases of overflow. 1771 1771 1772 -(% style="color: blue" %)**AT+DISMACANS=0**(%%) ~/~/ When the MACANSof the reply server plus the payload exceeds themaximum number of bytes of 11 bytes (DR0 of US915, DR2 of AS923, DR2 of AU195), the node will sendapacket with a payload of 00 anda port of 4. (default)1899 +(% style="color:#037691" %)**AT Command** 1773 1773 1774 -(% style="color:blue" %)**AT+DISMACANS=1** (%%) ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of the DR, the node will ignore the MACANS and not reply, and only upload the payload part. 1901 +(% border="2" style="width:500px" %) 1902 +|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DISMACANS=<state> 1903 +|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1904 +|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1905 +**state** : 1775 1775 1907 +**0** : When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default) 1776 1776 1777 -* (% style="color:#037691" %)**Downlink Payload **(%%)**:** 1909 +**1** : When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload. 1910 +))) 1911 +|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1912 +AT+DISMACANS=0 1778 1778 1779 - (%style="color:blue"%)**0x210001**(%%)~/~/SeteDISMACANS=11914 +When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default) 1780 1780 1916 +AT+DISMACANS=1 1781 1781 1918 +When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload. 1919 +))) 1782 1782 1921 +(% style="color:#037691" %)**Downlink Payload** 1922 + 1923 +(% border="2" style="width:500px" %) 1924 +|(% style="width:126px" %)**Payload**|(% style="width:372px" %)<prefix><state> 1925 +|(% style="width:126px" %)**Parameters**|(% style="width:372px" %)((( 1926 +**prefix** : 21 1927 + 1928 +**state** : (2 bytes in hexadecimal) 1929 + 1930 +**0** : When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default) 1931 + 1932 +**1 **: When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload. 1933 +))) 1934 +|(% style="width:126px" %)**Example**|(% style="width:372px" %)((( 1935 +21 **00 01** 1936 + 1937 +Set DISMACANS=1 1938 +))) 1939 + 1783 1783 ==== 3.4.2.25 Copy downlink to uplink ==== 1784 1784 1785 1785 1786 - *(%style="color:#037691"%)**ATCommand**(%%)**:**1943 +This command enables the device to immediately uplink the payload of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100. 1787 1787 1788 -(% 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.1945 +(% style="color:#037691" %)**AT Command**(%%)**:** 1789 1789 1790 - Example:**aa xx xx xx xx**aaindicateswhether the configuration haschanged,00isyes,01 is no;xx xx xx xx arethebytessent.1947 +(% style="color:blue" %)**AT+RPL=5** (%%) ~/~/ After receiving a downlink payload from the server, the device will immediately uplink the payload back to the server using port number 100. 1791 1791 1949 +Example:**aa xx xx xx xx** ~/~/ **aa** indicates whether the configuration has changed: **00** means YES, and **01** means NO. **xx xx xx xx** are the bytes uplinked back. 1792 1792 1951 + 1793 1793 [[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"]] 1794 1794 1795 1795 For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77. 1796 1796 1797 - 1798 - 1799 1799 [[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"]] 1800 1800 1801 1801 For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. 1802 1802 1803 1803 1961 +(% style="color:#037691" %)**Downlink Payload**(%%)**:** 1804 1804 1805 - ==== 3.4.2.26 Query version numberandfrequency band 、TDC ====1963 +There is no downlink option available for this feature. 1806 1806 1807 1807 1966 +==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ==== 1967 + 1968 + 1969 +This command is used to query key information about the device, including its firmware version, frequency band, sub band, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device. 1970 + 1808 1808 * ((( 1809 1809 (% style="color:#037691" %)**Downlink Payload**(%%)**:** 1810 1810 1811 -(% style="color:blue" %)**26 01 ** (%%) ~/~/ Downlink 26 01canquery deviceuploadfrequency, frequency band, softwareversion number,TDC time.1974 +(% style="color:blue" %)**26 01 ** (%%) ~/~/ The downlink payload 26 01 is used to query the device's firmware version, frequency band, sub band, and TDC time. 1812 1812 1976 + 1813 1813 1814 1814 ))) 1815 1815 ... ... @@ -1820,10 +1820,13 @@ 1820 1820 1821 1821 == 3.5 Integrating with ThingsEye.io == 1822 1822 1987 + 1823 1823 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. 1824 1824 1990 + 1825 1825 === 3.5.1 Configuring The Things Stack === 1826 1826 1993 + 1827 1827 We use The Things Stack Sandbox in this example: 1828 1828 1829 1829 * In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added. ... ... @@ -1835,15 +1835,19 @@ 1835 1835 The username and password (API key) you created here are required in the next section. 1836 1836 {{/info}} 1837 1837 1838 -[[image:tts-mqtt-integration.png ||height="625" width="1000"]]2005 +[[image:tts-mqtt-integration.png]] 1839 1839 2007 + 1840 1840 === 3.5.2 Configuring ThingsEye.io === 1841 1841 2010 + 2011 +The ThingsEye.io IoT platform is not open for self-registration at the moment. If you are interested in testing the platform, please send your project information to admin@thingseye.io, and we will create an account for you. 2012 + 1842 1842 * Login to your [[ThingsEye.io >>https://thingseye.io]]account. 1843 1843 * Under the **Integrations center**, click **Integrations**. 1844 1844 * Click the **Add integration** button (the button with the **+** symbol). 1845 1845 1846 -[[image:thingseye-io-step-1.png ||height="625" width="1000"]]2017 +[[image:thingseye-io-step-1.png]] 1847 1847 1848 1848 1849 1849 On the **Add integration** window, configure the following: ... ... @@ -1858,7 +1858,7 @@ 1858 1858 ** Allow create devices or assets 1859 1859 * Click the **Next** button. you will be navigated to the **Uplink data converter** tab. 1860 1860 1861 -[[image:thingseye-io-step-2.png ||height="625" width="1000"]]2032 +[[image:thingseye-io-step-2.png]] 1862 1862 1863 1863 1864 1864 **Uplink data converter:** ... ... @@ -1869,7 +1869,7 @@ 1869 1869 * 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]]. 1870 1870 * Click the **Next** button. You will be navigated to the **Downlink data converter **tab. 1871 1871 1872 -[[image:thingseye-io-step-3.png ||height="625" width="1000"]]2043 +[[image:thingseye-io-step-3.png]] 1873 1873 1874 1874 1875 1875 **Downlink data converter (this is an optional step):** ... ... @@ -1880,7 +1880,7 @@ 1880 1880 * 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]]. 1881 1881 * Click the **Next** button. You will be navigated to the **Connection** tab. 1882 1882 1883 -[[image:thingseye-io-step-4.png ||height="625" width="1000"]]2054 +[[image:thingseye-io-step-4.png]] 1884 1884 1885 1885 1886 1886 **Connection:** ... ... @@ -1887,7 +1887,7 @@ 1887 1887 1888 1888 * Choose **Region** from the **Host type**. 1889 1889 * Enter the **cluster** of your **The Things Stack** in the **Region** textbox. You can find the cluster in the url (e.g., https:~/~/**eu1**.cloud.thethings.network/...). 1890 -* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The **username **and **password **can be found on the MQTT integration page of your The Things Stack account (see Configuring The Things Stack). 2061 +* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The **username **and **password **can be found on the MQTT integration page of your The Things Stack account (see **3.5.1 Configuring The Things Stack**). 1891 1891 * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**. 1892 1892 1893 1893 [[image:message-1.png]] ... ... @@ -1895,54 +1895,64 @@ 1895 1895 1896 1896 * Click the **Add** button. 1897 1897 1898 -[[image:thingseye-io-step-5.png ||height="625" width="1000"]]2069 +[[image:thingseye-io-step-5.png]] 1899 1899 1900 1900 1901 -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. 2072 +Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings and correct any errors. 1902 1902 1903 1903 1904 -[[image:thingseye.io_integrationsCenter_integrations.png ||height="686" width="1000"]]2075 +[[image:thingseye.io_integrationsCenter_integrations.png]] 1905 1905 1906 1906 1907 1907 ==== 3.5.2.1 Viewing integration details ==== 1908 1908 2080 + 1909 1909 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. 1910 1910 1911 -[[image:integration-details.png ||height="686" width="1000"]]2083 +[[image:integration-details.png]] 1912 1912 1913 1913 1914 1914 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. 1915 1915 1916 1916 {{info}} 1917 -See also ThingsEye documentation. 2089 +See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]]. 1918 1918 {{/info}} 1919 1919 1920 -==== **3.5.2.2 Viewing events** ==== 1921 1921 2093 +==== 3.5.2.2 Viewing events ==== 2094 + 2095 + 1922 1922 The **Events **tab displays all the uplink messages from the LT-22222-L. 1923 1923 1924 1924 * Select **Debug **from the **Event type** dropdown. 1925 1925 * Select the** time frame** from the **time window**. 1926 1926 1927 -[[image:thingseye-events.png ||height="686" width="1000"]]2101 +[[image:thingseye-events.png]] 1928 1928 1929 1929 1930 -* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message. 2104 +* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message. 1931 1931 1932 -[[image:thingseye-json.png ||width="1000"]]2106 +[[image:thingseye-json.png]] 1933 1933 1934 1934 1935 -==== **3.5.2.3 Deleting an integration**====2109 +==== 3.5.2.3 Deleting an integration ==== 1936 1936 2111 + 1937 1937 If you want to delete an integration, click the **Delete integratio**n button on the Integrations page. 1938 1938 1939 1939 2115 +==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ==== 2116 + 2117 + 2118 +This will be added soon. 2119 + 2120 + 1940 1940 == 3.6 Interface Details == 1941 1941 1942 1942 === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) === 1943 1943 1944 1944 1945 -Supports 2126 +Supports** NPN-type **sensors. 1946 1946 1947 1947 [[image:1653356991268-289.png]] 1948 1948 ... ... @@ -2064,15 +2064,15 @@ 2064 2064 ))) 2065 2065 2066 2066 2067 -(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor 2248 +(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor 2068 2068 2069 -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.2250 +From the DI port circuit above, activating the photocoupler requires a voltage difference between the DI+ and DI- ports. However, the Dry Contact sensor is a passive component and cannot provide this voltage difference on its own. 2070 2070 2071 -To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Belowis areference circuit diagram.2252 +To detect a Dry Contact, you can supply a power source to one of the pins of the Dry Contact. A reference circuit diagram is shown below. 2072 2072 2073 2073 [[image:image-20230616235145-1.png]] 2074 2074 2075 -(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector 2256 +(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector 2076 2076 2077 2077 [[image:image-20240219115718-1.png]] 2078 2078 ... ... @@ -2148,8 +2148,9 @@ 2148 2148 [[image:image-20220524100215-10.png||height="382" width="723"]] 2149 2149 2150 2150 2151 -== 3.7 LED sIndicators ==2332 +== 3.7 LED Indicators == 2152 2152 2334 + 2153 2153 The table below lists the behavior of LED indicators for each port function. 2154 2154 2155 2155 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) ... ... @@ -2182,18 +2182,22 @@ 2182 2182 2183 2183 = 4. Using AT Commands = 2184 2184 2367 + 2185 2185 The LT-22222-L supports programming using AT Commands. 2186 2186 2370 + 2187 2187 == 4.1 Connecting the LT-22222-L to a PC == 2188 2188 2373 + 2189 2189 ((( 2190 -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. 2375 +You can use a USB-to-TTL adapter/converter along with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below. 2191 2191 2192 -[[image:usb-ttl-programming.png]] 2377 +[[image:usb-ttl-audio-jack-connection.jpg]] 2378 + 2379 + 2193 2193 ))) 2194 2194 2195 2195 2196 - 2197 2197 ((( 2198 2198 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: 2199 2199 ))) ... ... @@ -2204,7 +2204,10 @@ 2204 2204 ((( 2205 2205 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/]] 2206 2206 2393 + 2207 2207 == 4.2 LT-22222-L related AT commands == 2395 + 2396 + 2208 2208 ))) 2209 2209 2210 2210 ((( ... ... @@ -2223,39 +2223,39 @@ 2223 2223 * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey) 2224 2224 * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI) 2225 2225 * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON) 2226 -* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification) 2227 -* AT+DR: Get or set the Data Rate. (0-7 corresponding to DR_X) 2228 -* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing 2229 -* AT+PNM: Get or set the public network mode. (0: off, 1: on) 2230 -* AT+RX2FQ: Get or set the Rx2 window frequency 2231 -* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X) 2232 -* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms 2233 -* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms 2234 -* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms 2235 -* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms 2236 -* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA) 2237 -* AT+NWKID: Get or set the Network ID 2238 -* AT+FCU: Get or set the Frame Counter Uplink (FCntUp) 2239 -* AT+FCD: Get or set the Frame Counter Downlink (FCntDown) 2240 -* AT+CLASS: Get or set the Device Class 2241 -* AT+JOIN: Join network 2242 -* AT+NJS: Get OTAA Join Status 2243 -* AT+SENDB: Send hexadecimal data along with the application port 2244 -* AT+SEND: Send text data along with the application port 2245 -* AT+RECVB: Print last received data in binary format (with hexadecimal values) 2246 -* AT+RECV: Print last received data in raw format 2247 -* AT+VER: Get current image version and Frequency Band 2248 -* AT+CFM: Get or Set the confirmation mode (0-1) 2249 -* AT+CFS: Get confirmation status of the last AT+SEND (0-1) 2250 -* AT+SNR: Get the SNR of the last received packet 2251 -* AT+RSSI: Get the RSSI of the last received packet 2252 -* AT+TDC: Get or set the application data transmission interval in ms 2253 -* AT+PORT: Get or set the application port 2254 -* AT+DISAT: Disable AT commands 2255 -* AT+PWORD: Set password, max 9 digits 2256 -* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode 2257 -* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470 2258 -* AT+CFG: Print all settings 2415 +* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification) 2416 +* **##AT+DR##**: Get or set the Data Rate. (0-7 corresponding to DR_X) 2417 +* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing 2418 +* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on) 2419 +* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency 2420 +* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X) 2421 +* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms 2422 +* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms 2423 +* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms 2424 +* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms 2425 +* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA) 2426 +* ##**AT+NWKID**##: Get or set the Network ID 2427 +* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp) 2428 +* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown) 2429 +* ##**AT+CLASS**##: Get or set the Device Class 2430 +* ##**AT+JOIN**##: Join network 2431 +* ##**AT+NJS**##: Get OTAA Join Status 2432 +* ##**AT+SENDB**##: Send hexadecimal data along with the application port 2433 +* ##**AT+SEND**##: Send text data along with the application port 2434 +* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values) 2435 +* ##**AT+RECV**##: Print last received data in raw format 2436 +* ##**AT+VER**##: Get current image version and Frequency Band 2437 +* ##**AT+CFM**##: Get or Set the confirmation mode (0-1) 2438 +* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1) 2439 +* ##**AT+SNR**##: Get the SNR of the last received packet 2440 +* ##**AT+RSSI**##: Get the RSSI of the last received packet 2441 +* ##**AT+TDC**##: Get or set the application data transmission interval in ms 2442 +* ##**AT+PORT**##: Get or set the application port 2443 +* ##**AT+DISAT**##: Disable AT commands 2444 +* ##**AT+PWORD**##: Set password, max 9 digits 2445 +* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode 2446 +* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN470 2447 +* ##**AT+CFG**##: Print all settings 2259 2259 ))) 2260 2260 2261 2261 ... ... @@ -2401,16 +2401,19 @@ 2401 2401 2402 2402 == 5.1 Counting how many objects pass through the flow line == 2403 2403 2593 + 2404 2404 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]]? 2405 2405 2406 2406 2407 2407 = 6. FAQ = 2408 2408 2599 + 2409 2409 This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly. 2410 2410 2411 2411 2412 2412 == 6.1 How to update the firmware? == 2413 2413 2605 + 2414 2414 Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to: 2415 2415 2416 2416 * Support new features ... ... @@ -2420,7 +2420,7 @@ 2420 2420 You will need the following things before proceeding: 2421 2421 2422 2422 * 3.5mm programming cable (included with the LT-22222-L as an additional accessory) 2423 -* USB to TTL adapter 2615 +* USB to TTL adapter/converter 2424 2424 * 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) 2425 2425 * 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. 2426 2426 ... ... @@ -2430,7 +2430,7 @@ 2430 2430 2431 2431 Below is the hardware setup for uploading a firmware image to the LT-22222-L: 2432 2432 2433 -[[image:usb-ttl- programming.png]]2625 +[[image:usb-ttl-audio-jack-connection.jpg]] 2434 2434 2435 2435 2436 2436 ... ... @@ -2463,6 +2463,8 @@ 2463 2463 ((( 2464 2464 ((( 2465 2465 == 6.2 How to change the LoRaWAN frequency band/region? == 2658 + 2659 + 2466 2466 ))) 2467 2467 ))) 2468 2468 ... ... @@ -2474,6 +2474,8 @@ 2474 2474 2475 2475 2476 2476 == 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? == 2671 + 2672 + 2477 2477 ))) 2478 2478 2479 2479 ((( ... ... @@ -2547,11 +2547,13 @@ 2547 2547 2548 2548 == 6.4 How to change the uplink interval? == 2549 2549 2746 + 2550 2550 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/]] 2551 2551 2552 2552 2553 2553 == 6.5 Can I see the counting event in the serial output? == 2554 2554 2752 + 2555 2555 ((( 2556 2556 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. 2557 2557 ... ... @@ -2558,6 +2558,7 @@ 2558 2558 2559 2559 == 6.6 Can I use point-to-point communication with LT-22222-L? == 2560 2560 2759 + 2561 2561 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]]. 2562 2562 2563 2563 ... ... @@ -2566,6 +2566,7 @@ 2566 2566 ((( 2567 2567 == 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? == 2568 2568 2768 + 2569 2569 * If the device is not properly shut down and is directly powered off. 2570 2570 * It will default to a power-off state. 2571 2571 * In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory. ... ... @@ -2573,6 +2573,7 @@ 2573 2573 2574 2574 == 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? == 2575 2575 2776 + 2576 2576 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: 2577 2577 2578 2578 ... ... @@ -2581,16 +2581,19 @@ 2581 2581 2582 2582 == 6.9 Can the LT-22222-L save the RO state? == 2583 2583 2785 + 2584 2584 To enable this feature, the firmware version must be 1.6.0 or higher. 2585 2585 2586 2586 2587 2587 == 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? == 2588 2588 2791 + 2589 2589 It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose. 2590 2590 2591 2591 2592 2592 = 7. Troubleshooting = 2593 2593 2797 + 2594 2594 This section provides some known troubleshooting tips. 2595 2595 2596 2596 ... ... @@ -2599,6 +2599,8 @@ 2599 2599 ((( 2600 2600 ((( 2601 2601 == 7.1 Downlink isn't working. How can I solve this? == 2806 + 2807 + 2602 2602 ))) 2603 2603 ))) 2604 2604 ... ... @@ -2610,6 +2610,8 @@ 2610 2610 2611 2611 2612 2612 == 7.2 Having trouble uploading an image? == 2819 + 2820 + 2613 2613 ))) 2614 2614 2615 2615 ((( ... ... @@ -2620,6 +2620,8 @@ 2620 2620 2621 2621 2622 2622 == 7.3 Why can't I join TTN in the US915 /AU915 bands? == 2831 + 2832 + 2623 2623 ))) 2624 2624 2625 2625 ((( ... ... @@ -2629,6 +2629,7 @@ 2629 2629 2630 2630 == 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? == 2631 2631 2842 + 2632 2632 The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue. 2633 2633 Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]] 2634 2634 ... ... @@ -2635,6 +2635,7 @@ 2635 2635 2636 2636 = 8. Ordering information = 2637 2637 2849 + 2638 2638 (% style="color:#4f81bd" %)**LT-22222-L-XXX:** 2639 2639 2640 2640 (% style="color:#4f81bd" %)**XXX:** ... ... @@ -2649,8 +2649,10 @@ 2649 2649 * (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865 2650 2650 * (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779 2651 2651 2864 + 2652 2652 = 9. Package information = 2653 2653 2867 + 2654 2654 **Package includes**: 2655 2655 2656 2656 * 1 x LT-22222-L I/O Controller ... ... @@ -2665,8 +2665,10 @@ 2665 2665 * Package Size / pcs : 14.5 x 8 x 5 cm 2666 2666 * Weight / pcs : 170 g 2667 2667 2882 + 2668 2668 = 10. Support = 2669 2669 2885 + 2670 2670 * ((( 2671 2671 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. 2672 2672 ))) ... ... @@ -2678,6 +2678,7 @@ 2678 2678 2679 2679 = 11. Reference = 2680 2680 2897 + 2681 2681 * 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]] 2682 2682 * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]] 2683 2683 * [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]
- Screenshot 2024-11-23 at 18.27.11.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +143.4 KB - Content
- Screenshot 2024-12-08 193946.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +32.4 KB - Content
- dragino-lorawan-nw-lt-22222-n.jpg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +267.3 KB - Content
- lt-22222-l-joining.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +301.9 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
- lt33222-l.jpg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +31.3 KB - Content
- usb-ttl-audio-jack-connection.jpg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +394.4 KB - Content