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 ))) ... ... @@ -40,23 +40,24 @@ 40 40 ((( 41 41 You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways: 42 42 43 -* If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Network), you can select a network and register the LT-22222-L I/O controller with it. 44 +* 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 -[[image:1653295757274-912.png]] 54 - 55 55 51 + 52 +The network diagram below illustrates how the LT-22222-L communicates with a typical LoRaWAN network. 56 56 ))) 57 57 55 +(% class="wikigeneratedid" %) 56 +[[image:lorawan-nw.jpg||height="354" width="900"]] 57 + 58 + 58 58 == 1.2 Specifications == 59 59 61 + 60 60 (% style="color:#037691" %)**Hardware System:** 61 61 62 62 * STM32L072xxxx MCU ... ... @@ -96,8 +96,10 @@ 96 96 * Automatic RF Sense and CAD with ultra-fast AFC. 97 97 * Packet engine up to 256 bytes with CRC. 98 98 101 + 99 99 == 1.3 Features == 100 100 104 + 101 101 * LoRaWAN Class A & Class C modes 102 102 * Optional Customized LoRa Protocol 103 103 * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869 ... ... @@ -106,8 +106,10 @@ 106 106 * Firmware upgradable via program port 107 107 * Counting 108 108 113 + 109 109 == 1.4 Applications == 110 110 116 + 111 111 * Smart buildings & home automation 112 112 * Logistics and supply chain management 113 113 * Smart metering ... ... @@ -115,13 +115,16 @@ 115 115 * Smart cities 116 116 * Smart factory 117 117 124 + 118 118 == 1.5 Hardware Variants == 119 119 120 -(% style="width:524px" %) 121 -|(% style="width:94px" %)**Model**|(% style="width:98px" %)**Photo**|(% style="width:329px" %)**Description** 122 -|(% style="width:94px" %)**LT33222-L**|(% style="width:98px" %)((( 123 -[[image:/xwiki/bin/downloadrev/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LT-22222-L/WebHome/image-20230424115112-1.png?rev=1.1&width=58&height=106||alt="image-20230424115112-1.png" height="106" width="58"]] 124 -)))|(% 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" %)((( 125 125 * 2 x Digital Input (Bi-direction) 126 126 * 2 x Digital Output 127 127 * 2 x Relay Output (5A@250VAC / 30VDC) ... ... @@ -131,55 +131,55 @@ 131 131 ))) 132 132 133 133 143 += 2. Assembling the device = 134 134 135 -== 2. Assembling the device == 136 - 137 137 == 2.1 Connecting the antenna == 138 138 147 + 139 139 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. 140 140 141 141 {{warning}} 142 -Warning! Do not power on the device without connecting the antenna. 151 +**Warning! Do not power on the device without connecting the antenna.** 143 143 {{/warning}} 144 144 154 + 145 145 == 2.2 Terminals == 146 146 147 -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. 148 148 149 - 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. 150 150 151 -(% style="width:634px" %) 152 -|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function 153 -|(% style="width:295px" %)GND|(% style="width:338px" %)Ground 154 -|(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage 155 -|(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2 156 -|(% style="width:295px" %)AVI1|(% style="width:338px" %)Analog Voltage Input Terminal 1 157 -|(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2 158 -|(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1 160 +**Upper screw terminal block (from left to right):** 159 159 160 -Lower screw terminal block (from left to right): 162 +(% style="width:385px" %) 163 +|=(% style="width: 139px;" %)Screw Terminal|=(% style="width: 242px;" %)Function 164 +|(% style="width:139px" %)GND|(% style="width:242px" %)Ground 165 +|(% style="width:139px" %)VIN|(% style="width:242px" %)Input Voltage 166 +|(% style="width:139px" %)AVI2|(% style="width:242px" %)Analog Voltage Input Terminal 2 167 +|(% style="width:139px" %)AVI1|(% style="width:242px" %)Analog Voltage Input Terminal 1 168 +|(% style="width:139px" %)ACI2|(% style="width:242px" %)Analog Current Input Terminal 2 169 +|(% style="width:139px" %)ACI1|(% style="width:242px" %)Analog Current Input Terminal 1 161 161 162 -(% style="width:633px" %) 163 -|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function 164 -|(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1 165 -|(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1 166 -|(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2 167 -|(% style="width:296px" %)RO2-1|(% style="width:334px" %)Relay Output 2 168 -|(% style="width:296px" %)DI2+|(% style="width:334px" %)Digital Input 2 169 -|(% style="width:296px" %)DI2-|(% style="width:334px" %)Digital Input 2 170 -|(% style="width:296px" %)DI1+|(% style="width:334px" %)Digital Input 1 171 -|(% style="width:296px" %)DI1-|(% style="width:334px" %)Digital Input 1 172 -|(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2 173 -|(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1 171 +**Lower screw terminal block (from left to right):** 174 174 175 -== 2.3 Powering the device == 173 +(% style="width:257px" %) 174 +|=(% style="width: 125px;" %)Screw Terminal|=(% style="width: 128px;" %)Function 175 +|(% style="width:125px" %)RO1-2|(% style="width:128px" %)Relay Output 1 176 +|(% style="width:125px" %)RO1-1|(% style="width:128px" %)Relay Output 1 177 +|(% style="width:125px" %)RO2-2|(% style="width:128px" %)Relay Output 2 178 +|(% style="width:125px" %)RO2-1|(% style="width:128px" %)Relay Output 2 179 +|(% style="width:125px" %)DI2+|(% style="width:128px" %)Digital Input 2 180 +|(% style="width:125px" %)DI2-|(% style="width:128px" %)Digital Input 2 181 +|(% style="width:125px" %)DI1+|(% style="width:128px" %)Digital Input 1 182 +|(% style="width:125px" %)DI1-|(% style="width:128px" %)Digital Input 1 183 +|(% style="width:125px" %)DO2|(% style="width:128px" %)Digital Output 2 184 +|(% style="width:125px" %)DO1|(% style="width:128px" %)Digital Output 1 176 176 177 - TheLT-22222-LI/OController canbepowered by a **7–24V DC** power source. Connectyour power supply’s positive wire to the VIN and the negativewiretothe GND screw terminals.The powerindicator **(PWR) LED** will turn on when the deviceis properly powered.186 +== 2.3 Connecting LT-22222-L to a Power Source == 178 178 179 -Once powered ,the**TXLED** will**fast-blink5times**which meansheLT-22222-Lwillenterthe **work mode** andstartto**join** TheThingsStack.The **TX LED**will be on for **5seconds**afterjoiningthenetwork. When thereis a **downlink** message fromthe server,the**RXLED** willbe onfor **1 second**.When the device issending an uplink message totheserver, the **TX LED** willbeon for**1 second**.See also LED status.188 +The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s **positive wire** to the **VIN** and the **negative wire** to the **GND** screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered. 180 180 181 181 {{warning}} 182 -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.** 183 183 {{/warning}} 184 184 185 185 ... ... @@ -186,36 +186,51 @@ 186 186 [[image:1653297104069-180.png]] 187 187 188 188 189 -= 3. Registering with a LoRaWAN Network Server = 198 += 3. Registering LT-22222-L with a LoRaWAN Network Server = 190 190 191 - By default, the LT-22222-Lisconfigured to operate in LoRaWAN ClassC mode. ItsupportsOTAA (Over-the-Air Activation),themostsecuremethodforactivating a devicewith a LoRaWANnetworkserver.TheLT-22222-Lcomeswithdeviceregistrationinformation that allowsyou to registeritwith a LoRaWANnetwork,enabling the deviceto performOTAA activation with thenetworkserverupon initialpower-upand after any subsequent reboots.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. 192 192 193 -After powering on, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** the LoRaWAN network. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LED** will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status. 194 194 195 -In case you can't set the root key and other identifiers in the network server and must use them from the server, you can use [[AT Commands>>||anchor="H4.UseATCommand"]] to configure them on the device. 196 - 197 -The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network. 198 - 199 -[[image:image-20220523172350-1.png||height="266" width="864"]] 200 - 201 201 === 3.2.1 Prerequisites === 202 202 203 - Makesureyou have thedevice registration information such as DevEUI, AppEUI, and AppKeywith you. The 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.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. 204 204 205 205 [[image:image-20230425173427-2.png||height="246" width="530"]] 206 206 209 +{{info}} 210 +In case you can't set the root key and other identifiers in the network server and must use them from the server, you can use [[AT Commands>>||anchor="H4.UseATCommand"]] to configure them on the device. 211 +{{/info}} 212 + 207 207 The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers. 208 208 209 -=== 3.2.2 The Things Stack Sandbox (TTSS)===215 +=== 3.2.2 The Things Stack === 210 210 217 +This section guides you through how to register your LT-22222-L with The Things Stack Sandbox. 218 + 219 +{{info}} 211 211 The Things Stack Sandbox was formally called The Things Stack Community Edition. 221 +{{/info}} 212 212 213 -* Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account. 214 -* Create an application with The Things Stack if you do not have one yet. 215 -* Go to your application page and click on the **End devices** in the left menu. 223 + 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. 225 + 226 + 227 +[[image:dragino-lorawan-nw-lt-22222-n.jpg]] 228 + 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. 237 +* Log in to your The Things Stack Sandbox account. 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. 216 216 * On the End devices page, click on **+ Register end device**. Two registration options are available: 217 217 218 -==== 3.2.2. 1Using the LoRaWAN Device Repository ====242 +==== 3.2.2.2 Using the LoRaWAN Device Repository ==== 219 219 220 220 * On the **Register end device** page: 221 221 ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**. ... ... @@ -227,7 +227,7 @@ 227 227 *** **Profile (Region)**: Select the region that matches your device. 228 228 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 229 229 230 -[[image:lt-22222-l-dev-repo-reg-p1.png ||height="625" width="1000"]]254 +[[image:lt-22222-l-dev-repo-reg-p1.png]] 231 231 232 232 233 233 * Register end device page continued... ... ... @@ -237,11 +237,10 @@ 237 237 ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. 238 238 ** Under **After registration**, select the **View registered end device** option. 239 239 240 -[[image:lt-22222-l-dev-repo-reg-p2.png ||height="625" width="1000"]]264 +[[image:lt-22222-l-dev-repo-reg-p2.png]] 241 241 242 -==== ==== 243 243 244 -==== 3.2.2. 2Adding device manually ====267 +==== 3.2.2.3 Adding device manually ==== 245 245 246 246 * On the **Register end device** page: 247 247 ** Select the option **Enter end device specifies manually** under **Input method**. ... ... @@ -252,11 +252,11 @@ 252 252 ** Select the option **Over the air activation (OTAA)** under the **Activation mode.** 253 253 ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list. 254 254 255 -[[image:lt-22222-l-manually-p1.png ||height="625" width="1000"]]278 +[[image:lt-22222-l-manually-p1.png]] 256 256 257 257 258 258 * Register end device page continued... 259 -** 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**//' 260 260 ** In the **DevEUI** field, enter the **DevEUI**. 261 261 ** In the **AppKey** field, enter the **AppKey**. 262 262 ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. ... ... @@ -263,41 +263,56 @@ 263 263 ** Under **After registration**, select the **View registered end device** option. 264 264 ** Click the **Register end device** button. 265 265 266 -[[image:lt-22222-l-manually-p2.png ||height="625" width="1000"]]289 +[[image:lt-22222-l-manually-p2.png]] 267 267 268 268 269 269 You will be navigated to the **Device overview** page. 270 270 271 271 272 -[[image:lt-22222-device-overview.png ||height="625" width="1000"]]295 +[[image:lt-22222-device-overview.png]] 273 273 274 274 275 -==== 3.2.2. 3Joining ====298 +==== 3.2.2.4 Joining ==== 276 276 277 -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. 278 278 279 -Now power on your LT-22222-L. Itwill beginjoiningThe Things Stack. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server.Once successfully joined, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**).302 +Now power on your LT-22222-L. The **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** The Things Stack network server. The **TX LED** will be on for **5 seconds** after joining the network. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server. 280 280 281 281 282 -[[image:lt-22222-join -network.png||height="625" width="1000"]]305 +[[image:lt-22222-l-joining.png]] 283 283 284 284 285 -By default, you will receive an uplink data message from the device every 10 minutes. 286 286 309 +==== 3.2.2.5 Uplinks ==== 310 + 311 + 312 +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. 313 + 287 287 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. 288 288 289 289 [[image:lt-22222-ul-payload-decoded.png]] 290 290 291 291 292 -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. 293 293 294 294 {{info}} 295 295 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. 296 296 {{/info}} 297 297 298 -[[image:lt-22222-ul-payload-fmt.png ||height="686" width="1000"]]325 +[[image:lt-22222-ul-payload-fmt.png]] 299 299 300 300 328 +We also have a payload formatter that resolves some decoding issues present in the Device Repository formatter. You can add it under the Custom JavaScript formatter. It can be found [[here>>https://github.com/dragino/dragino-end-node-decoder/blob/main/LT22222-L/v1.6_decoder_ttn%20.txt]]: 329 + 330 +(% class="wikigeneratedid" %) 331 +[[image:lt-22222-l-js-custom-payload-formatter.png]] 332 + 333 + 334 +==== 3.2.2.6 Downlinks ==== 335 + 336 +When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**. 337 + 338 + 301 301 == 3.3 Working Modes and Uplink Payload formats == 302 302 303 303 ... ... @@ -581,11 +581,11 @@ 581 581 582 582 (% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)** 583 583 584 -(% 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)** 585 585 586 -(% 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)** 587 587 588 -(% 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)** 589 589 ))) 590 590 591 591 ... ... @@ -704,9 +704,9 @@ 704 704 705 705 (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:** 706 706 707 -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** 708 708 709 -Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4 747 +**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4 710 710 711 711 AA: Type Code for this downlink Command: 712 712 ... ... @@ -735,7 +735,7 @@ 735 735 736 736 MOD6 Payload: total of 11 bytes 737 737 738 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:515px" %)776 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) 739 739 |(% 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** 740 740 |Value|((( 741 741 TRI_A FLAG ... ... @@ -749,7 +749,7 @@ 749 749 750 750 (% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below 751 751 752 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:515px" %)790 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) 753 753 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 754 754 |((( 755 755 AV1_LOW ... ... @@ -773,12 +773,12 @@ 773 773 774 774 **Example:** 775 775 776 -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. 777 777 778 778 779 779 (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below 780 780 781 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:515px" %)819 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) 782 782 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 783 783 |((( 784 784 AV1_LOW ... ... @@ -802,31 +802,31 @@ 802 802 803 803 **Example:** 804 804 805 -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. 806 806 807 807 808 808 (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below 809 809 810 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:674px" %)811 -|(% 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**812 -|(% 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 813 813 814 -* Each bit sshows which status has been triggered on this uplink.852 +* Each bit shows which status has been triggered on this uplink. 815 815 816 816 **Example:** 817 817 818 -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. 819 819 820 -00000101: Means both DI1 and DI2 trigger are enabled.858 +00000101: This means both DI1 and DI2 triggers are enabled. 821 821 822 822 823 -(% 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. 824 824 825 -Downlink command to poll MOD6 status: 863 +Downlink command to poll/request MOD6 status: 826 826 827 827 **AB 06** 828 828 829 -When device gotthis command, it will send the MOD6 payload.867 +When device receives this command, it will send the MOD6 payload. 830 830 831 831 832 832 === 3.3.7 Payload Decoder === ... ... @@ -840,6 +840,7 @@ 840 840 841 841 == 3.4 Configure LT-22222-L via AT Commands or Downlinks == 842 842 881 + 843 843 ((( 844 844 You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks. 845 845 ))) ... ... @@ -856,17 +856,22 @@ 856 856 857 857 === 3.4.1 Common commands === 858 858 898 + 859 859 ((( 860 860 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 + 861 861 ))) 862 862 863 863 === 3.4.2 Sensor-related commands === 864 864 907 + 865 865 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. 866 866 867 867 868 -==== 3.4.2.1 Set Transmit Interval ==== 911 +==== 3.4.2.1 Set Transmit/Uplink Interval ==== 869 869 913 + 870 870 Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes. 871 871 872 872 (% style="color:#037691" %)**AT command** ... ... @@ -873,12 +873,19 @@ 873 873 874 874 (% border="2" style="width:500px" %) 875 875 |**Command**|AT+TDC=<time> 876 -|**Response**| 877 -|**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 878 878 |**Example**|((( 879 879 AT+TDC=30000 880 880 881 -Sets the uplink interval to 30 ,000milliseconds (30 seconds)932 +Sets the uplink interval to **30 seconds** (30000 milliseconds) 882 882 ))) 883 883 884 884 (% style="color:#037691" %)**Downlink payload** ... ... @@ -890,27 +890,29 @@ 890 890 |**Parameters**|((( 891 891 **prefix** : 0x01 892 892 893 -**time** : uplink interval i s inmilliseconds, represented by 3 bytes in hexadecimal.944 +**time** : uplink interval in **seconds**, represented by **3 bytes** in **hexadecimal**. 894 894 ))) 895 895 |**Example**|((( 896 -01 **00 75 30**947 +01 **00 00 1E** 897 897 898 -Sets the uplink interval to 30 ,000milliseconds(30 seconds)949 +Sets the uplink interval to **30 seconds** 899 899 900 -Conversion: 30 000(dec) = 0075 30 (hex)951 +Conversion: 30 (dec) = 00 00 1E (hex) 901 901 902 -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]] 903 903 ))) 904 904 905 905 ==== 3.4.2.2 Set the Working Mode (AT+MOD) ==== 906 906 960 + 907 907 Sets the working mode. 908 908 909 909 (% style="color:#037691" %)**AT command** 910 910 911 911 (% border="2" style="width:500px" %) 912 -|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE=<working_mode> 913 -|(% style="width:97px" %)**Response**|(% style="width:413px" %) 966 +|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MOD=<working_mode> 914 914 |(% style="width:97px" %)**Parameters**|(% style="width:413px" %)((( 915 915 **working_mode** : 916 916 ... ... @@ -926,6 +926,18 @@ 926 926 927 927 6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5 928 928 ))) 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 +))) 929 929 |(% style="width:97px" %)**Example**|(% style="width:413px" %)((( 930 930 AT+MOD=2 931 931 ... ... @@ -948,13 +948,14 @@ 948 948 Sets the device to working mode 2 (Double DI Counting + DO + RO) 949 949 ))) 950 950 951 -==== 3.4.2.3 Pollan uplink ====1016 +==== 3.4.2.3 Request an uplink from the device ==== 952 952 953 -Requests an uplink from LT-22222-L. 954 954 1019 +Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode. 1020 + 955 955 (% style="color:#037691" %)**AT command** 956 956 957 -There is no AT Command torequestan uplinkfrom LT-22222-L1023 +There is no AT Command available for this feature. 958 958 959 959 (% style="color:#037691" %)**Downlink payload** 960 960 ... ... @@ -962,7 +962,7 @@ 962 962 |(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF 963 963 |(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08 964 964 |(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 965 -08 FF 1031 +08 **FF** 966 966 967 967 Requests an uplink from LT-22222-L. 968 968 ))) ... ... @@ -969,6 +969,7 @@ 969 969 970 970 ==== 3.4.2.4 Enable/Disable Trigger Mode ==== 971 971 1038 + 972 972 Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]). 973 973 974 974 (% style="color:#037691" %)**AT Command** ... ... @@ -996,7 +996,7 @@ 996 996 |(% style="width:97px" %)**Parameters**|(% style="width:401px" %)((( 997 997 **prefix** : 0x0A 06 (two bytes in hexadecimal) 998 998 999 -** working1066 +**enable/disable trigger_mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal. 1000 1000 ))) 1001 1001 |(% style="width:97px" %)**Example**|(% style="width:401px" %)((( 1002 1002 0A 06 **01** ... ... @@ -1004,13 +1004,14 @@ 1004 1004 Enable trigger mode for the current working mode 1005 1005 ))) 1006 1006 1007 -==== 3.4.2.5 Polltrigger settings ====1074 +==== 3.4.2.5 Request trigger settings ==== 1008 1008 1009 -Polls the trigger settings. 1010 1010 1077 +Requests the trigger settings. 1078 + 1011 1011 (% style="color:#037691" %)**AT Command:** 1012 1012 1013 -There is no AT Command for this feature. 1081 +There is no AT Command available for this feature. 1014 1014 1015 1015 (% style="color:#037691" %)**Downlink Payload** 1016 1016 ... ... @@ -1025,6 +1025,7 @@ 1025 1025 1026 1026 ==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ==== 1027 1027 1096 + 1028 1028 Enable or disable DI1/DI2/DI3 as a trigger. 1029 1029 1030 1030 (% style="color:#037691" %)**AT Command** ... ... @@ -1079,9 +1079,9 @@ 1079 1079 1080 1080 ==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ==== 1081 1081 1151 + 1082 1082 Sets DI1 or DI3 (for LT-33222-L) as a trigger. 1083 1083 1084 - 1085 1085 (% style="color:#037691" %)**AT Command** 1086 1086 1087 1087 (% border="2" style="width:500px" %) ... ... @@ -1118,9 +1118,9 @@ 1118 1118 1119 1119 ==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ==== 1120 1120 1190 + 1121 1121 Sets DI2 as a trigger. 1122 1122 1123 - 1124 1124 (% style="color:#037691" %)**AT Command** 1125 1125 1126 1126 (% border="2" style="width:500px" %) ... ... @@ -1150,10 +1150,9 @@ 1150 1150 ))) 1151 1151 |(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64** 1152 1152 1153 -==== ==== 1154 - 1155 1155 ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ==== 1156 1156 1224 + 1157 1157 Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1158 1158 1159 1159 (% style="color:#037691" %)**AT Command** ... ... @@ -1203,6 +1203,7 @@ 1203 1203 1204 1204 ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ==== 1205 1205 1274 + 1206 1206 Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1207 1207 1208 1208 (% style="color:#037691" %)**AT Command** ... ... @@ -1250,6 +1250,7 @@ 1250 1250 1251 1251 ==== 3.4.2.11 Trigger – Set minimum interval ==== 1252 1252 1322 + 1253 1253 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. 1254 1254 1255 1255 (% style="color:#037691" %)**AT Command** ... ... @@ -1285,6 +1285,7 @@ 1285 1285 1286 1286 ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ==== 1287 1287 1358 + 1288 1288 Controls the digital outputs DO1, DO2, and DO3 1289 1289 1290 1290 (% style="color:#037691" %)**AT Command** ... ... @@ -1315,11 +1315,11 @@ 1315 1315 ((( 1316 1316 01: Low, 00: High, 11: No action 1317 1317 1318 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:510px" %)1319 -|(% 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** 1320 -|02 01 00 11|Low|High|No Action 1321 -|02 00 11 01|High|No Action|Low 1322 -|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 1323 1323 ))) 1324 1324 1325 1325 ((( ... ... @@ -1333,32 +1333,28 @@ 1333 1333 ))) 1334 1334 ))) 1335 1335 1336 -==== ==== 1337 - 1338 1338 ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ==== 1339 1339 1340 1340 1341 1341 * (% style="color:#037691" %)**AT Command** 1342 1342 1343 -There is no AT Command to controlDigitalOutput1412 +There is no AT command to control the digital output. 1344 1344 1345 1345 1346 1346 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)** 1347 1347 1348 -(% 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 1349 1349 1350 - 1351 1351 This is to control the digital output time of DO pin. Include four bytes: 1352 1352 1353 -(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)1421 +(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9) 1354 1354 1355 -(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode1423 +(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode 1356 1356 1357 -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. 1358 1358 1359 -00: DO pins will change to an inverter state after timeout 1360 1360 1361 - 1362 1362 (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status: 1363 1363 1364 1364 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) ... ... @@ -1367,7 +1367,7 @@ 1367 1367 |0x00|DO1 set to high 1368 1368 |0x11|DO1 NO Action 1369 1369 1370 -(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:1437 +(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status: 1371 1371 1372 1372 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1373 1373 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1375,7 +1375,7 @@ 1375 1375 |0x00|DO2 set to high 1376 1376 |0x11|DO2 NO Action 1377 1377 1378 -(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:1445 +(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status: 1379 1379 1380 1380 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1381 1381 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1383,7 +1383,7 @@ 1383 1383 |0x00|DO3 set to high 1384 1384 |0x11|DO3 NO Action 1385 1385 1386 -(% 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) 1387 1387 1388 1388 1389 1389 (% style="color:red" %)**Note: ** ... ... @@ -1392,7 +1392,7 @@ 1392 1392 1393 1393 Before firmware v1.6.0, the latch time only supported 2 bytes. 1394 1394 1395 -(% 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.** 1396 1396 1397 1397 1398 1398 **Example payload:** ... ... @@ -1419,16 +1419,16 @@ 1419 1419 1420 1420 * (% style="color:#037691" %)**AT Command:** 1421 1421 1422 -There is no AT Command to control Relay Output 1489 +There is no AT Command to control the Relay Output 1423 1423 1424 1424 1425 1425 * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):** 1426 1426 1427 -(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set RO1/RO2 output 1494 +(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Sets RO1/RO2 output 1428 1428 1429 1429 1430 1430 ((( 1431 -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. 1432 1432 ))) 1433 1433 1434 1434 ((( ... ... @@ -1446,28 +1446,29 @@ 1446 1446 |03 00 01|Open|Close 1447 1447 ))) 1448 1448 1449 -(% 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.** 1450 1450 1451 1451 1452 1452 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== 1453 1453 1521 + 1454 1454 Controls the relay output time. 1455 1455 1456 1456 * (% style="color:#037691" %)**AT Command:** 1457 1457 1458 -There is no AT Command to control Relay Output 1526 +There is no AT Command to control the Relay Output 1459 1459 1460 1460 1461 1461 * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):** 1462 1462 1463 -(% 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 1464 1464 1465 1465 1466 -This is tocontrol the relay output time.Itincludesfourbytes:1534 +This controls the relay output time and includes 4 bytes: 1467 1467 1468 -(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)1536 +(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05) 1469 1469 1470 -(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode1538 +(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode 1471 1471 1472 1472 01: Relays will change back to their original state after timeout. 1473 1473 ... ... @@ -1474,12 +1474,12 @@ 1474 1474 00: Relays will change to the inverter state after timeout. 1475 1475 1476 1476 1477 -(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:1545 +(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status: 1478 1478 1479 1479 [[image:image-20221008095908-1.png||height="364" width="564"]] 1480 1480 1481 1481 1482 -(% 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 1483 1483 1484 1484 1485 1485 (% style="color:red" %)**Note:** ... ... @@ -1489,7 +1489,7 @@ 1489 1489 Before firmware v1.6.0, the latch time only supported 2 bytes. 1490 1490 1491 1491 1492 -(% 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.** 1493 1493 1494 1494 1495 1495 **Example payload:** ... ... @@ -1517,17 +1517,10 @@ 1517 1517 1518 1518 When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1519 1519 1520 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1521 - 1522 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):** 1523 - 1524 -(% style="color:blue" %)**0xA5 aa bb cc ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc 1525 - 1526 - 1527 1527 (% style="color:#037691" %)**AT Command** 1528 1528 1529 1529 (% border="2" style="width:500px" %) 1530 -|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage><logic> 1591 +|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage>,<logic> 1531 1531 |(% style="width:137px" %)**Response**|(% style="width:361px" %) 1532 1532 |(% style="width:137px" %)**Parameters**|(% style="width:361px" %)((( 1533 1533 **voltage** : voltage threshold in mV ... ... @@ -1534,9 +1534,9 @@ 1534 1534 1535 1535 **logic**: 1536 1536 1537 -0 : lower than 1598 +**0** : lower than 1538 1538 1539 -1: higher than 1600 +**1**: higher than 1540 1540 1541 1541 if you leave logic parameter blank, it is considered 0 1542 1542 ))) ... ... @@ -1565,9 +1565,9 @@ 1565 1565 1566 1566 **logic**: (1 byte in hexadecimal) 1567 1567 1568 -0 : lower than 1629 +**0** : lower than 1569 1569 1570 -1: higher than 1631 +**1**: higher than 1571 1571 1572 1572 if you leave logic parameter blank, it is considered 1 (higher than) 1573 1573 ))) ... ... @@ -1587,24 +1587,12 @@ 1587 1587 1588 1588 ==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ==== 1589 1589 1590 -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. 1591 1591 1592 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) ** 1593 - 1594 -(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count 1595 - 1596 -(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set 1597 - 1598 - 1599 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):** 1600 - 1601 -(% style="color:blue" %)**0x A8 aa bb cc dd ee ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee) 1602 - 1603 - 1604 1604 (% style="color:#037691" %)**AT Command** 1605 1605 1606 1606 (% border="2" style="width:500px" %) 1607 -|(% 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> 1608 1608 |(% style="width:134px" %)**Response**|(% style="width:364px" %) 1609 1609 |(% style="width:134px" %)**Parameters**|(% style="width:364px" %)((( 1610 1610 **counting_parameter** : ... ... @@ -1648,14 +1648,8 @@ 1648 1648 1649 1649 ==== 3.4.2.18 Counting ~-~- Clear Counting ==== 1650 1650 1651 -This featureclears the counting in counting mode.1700 +This command clears the counting in counting mode. 1652 1652 1653 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT **(%%) ~/~/ clear all counting 1654 - 1655 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):** 1656 - 1657 -(% style="color:blue" %)**0x A6 01 ** (%%)~/~/ clear all counting 1658 - 1659 1659 (% style="color:#037691" %)**AT Command** 1660 1660 1661 1661 (% border="2" style="width:500px" %) ... ... @@ -1673,122 +1673,264 @@ 1673 1673 ))) 1674 1674 |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01** 1675 1675 1676 -==== 3.4.2.19 Counting ~-~- Changecountingmodetosavetime====1719 +==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ==== 1677 1677 1678 -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. 1679 1679 1680 - *(%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. 1681 1681 1682 -(% 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** 1683 1683 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 1684 1684 1685 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):** 1733 +Sets the device to save its counting results to the memory every 60 seconds. 1734 +))) 1686 1686 1687 -(% style="color: blue" %)**0xA7aabb cc**(%%)~/~/ same as AT+COUTIME =aa bb cc,1736 +(% style="color:#037691" %)**Downlink Payload** 1688 1688 1689 -((( 1690 -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 1691 1691 ))) 1745 +|(% style="width:123px" %)**Example**|(% style="width:375px" %)((( 1746 +A7 **00 00 3C** 1692 1692 1748 +Sets the device to save its counting results to the memory every 60 seconds. 1749 +))) 1693 1693 1751 +==== 3.4.2.20 Reset saved RO and DO states ==== 1694 1694 1695 -==== 3.4.2.20 Reset save RO DO state ==== 1696 1696 1697 -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. 1698 1698 1699 - *(% style="color:#037691" %)**AT Command:**1756 +(% style="color:#037691" %)**AT Command** 1700 1700 1701 -(% 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** : 1702 1702 1703 - (% 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) 1704 1704 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 ** 1705 1705 1706 - *(% style="color:#037691"%)**DownlinkPayload(prefix 0xAD):**1771 +RODO will close when the device joins the network. (default) 1707 1707 1708 -(% style="color:blue" %)** 0xAD aa ** (%%)~/~/ same as AT+RODORETaa1773 +(% style="color:blue" %)**AT+RODORESET=0 ** 1709 1709 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 +))) 1710 1710 1778 +(% style="color:#037691" %)**Downlink Payload** 1711 1711 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 + 1712 1712 ==== 3.4.2.21 Encrypted payload ==== 1713 1713 1714 -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. 1715 1715 1716 - *(%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. 1717 1717 1718 -(% style="color: blue" %)**AT+DECRYPT=1** (%%)~/~/ The payload is uploaded without encryption1806 +(% style="color:#037691" %)**AT Command:** 1719 1719 1720 -(% 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** : 1721 1721 1814 +**1** : The payload is uploaded without encryption 1722 1722 1816 +**0** : The payload is encrypted when uploaded (default) 1817 +))) 1818 +|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1819 +AT+DECRYPT=1 1723 1723 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 + 1724 1724 ==== 3.4.2.22 Get sensor value ==== 1725 1725 1726 1726 1727 - *(%style="color:#037691"%)**ATCommand:**1834 +This command allows you to retrieve and optionally uplink sensor readings through the serial port. 1728 1728 1729 -(% style="color: blue" %)**AT+GETSENSORVALUE=0**(%%)~/~/ The serial port retrieves the reading of the current sensor.1836 +(% style="color:#037691" %)**AT Command** 1730 1730 1731 -(% 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** : 1732 1732 1844 +**0 **: Retrieves the current sensor reading via the serial port. 1733 1733 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 1734 1734 1735 - ==== 3.4.2.23Resets thedownlinkpacketcount====1851 +Retrieves the current sensor reading via the serial port. 1736 1736 1853 +AT+GETSENSORVALUE=1 1737 1737 1738 -* (% style="color:#037691" %)**AT Command:** 1855 +Retrieves and uplinks the current sensor reading via the serial port. 1856 +))) 1739 1739 1740 - (% 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. 1741 1741 1742 -(% 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. 1743 1743 1861 +==== 3.4.2.23 Resetting the downlink packet count ==== 1744 1744 1745 1745 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 + 1746 1746 ==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ==== 1747 1747 1748 1748 1749 - *(%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. 1750 1750 1751 -(% 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** 1752 1752 1753 -(% 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** : 1754 1754 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) 1755 1755 1756 -* (% 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 1757 1757 1758 - (%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) 1759 1759 1916 +AT+DISMACANS=1 1760 1760 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 +))) 1761 1761 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 + 1762 1762 ==== 3.4.2.25 Copy downlink to uplink ==== 1763 1763 1764 1764 1765 - *(%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. 1766 1766 1767 -(% 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**(%%)**:** 1768 1768 1769 - 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. 1770 1770 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. 1771 1771 1951 + 1772 1772 [[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"]] 1773 1773 1774 1774 For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77. 1775 1775 1776 - 1777 - 1778 1778 [[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"]] 1779 1779 1780 1780 For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. 1781 1781 1782 1782 1961 +(% style="color:#037691" %)**Downlink Payload**(%%)**:** 1783 1783 1784 - ==== 3.4.2.26 Query version numberandfrequency band 、TDC ====1963 +There is no downlink option available for this feature. 1785 1785 1786 1786 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 + 1787 1787 * ((( 1788 1788 (% style="color:#037691" %)**Downlink Payload**(%%)**:** 1789 1789 1790 -(% 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. 1791 1791 1976 + 1792 1792 1793 1793 ))) 1794 1794 ... ... @@ -1799,10 +1799,13 @@ 1799 1799 1800 1800 == 3.5 Integrating with ThingsEye.io == 1801 1801 1987 + 1802 1802 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. 1803 1803 1990 + 1804 1804 === 3.5.1 Configuring The Things Stack === 1805 1805 1993 + 1806 1806 We use The Things Stack Sandbox in this example: 1807 1807 1808 1808 * In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added. ... ... @@ -1814,15 +1814,19 @@ 1814 1814 The username and password (API key) you created here are required in the next section. 1815 1815 {{/info}} 1816 1816 1817 -[[image:tts-mqtt-integration.png ||height="625" width="1000"]]2005 +[[image:tts-mqtt-integration.png]] 1818 1818 2007 + 1819 1819 === 3.5.2 Configuring ThingsEye.io === 1820 1820 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 + 1821 1821 * Login to your [[ThingsEye.io >>https://thingseye.io]]account. 1822 1822 * Under the **Integrations center**, click **Integrations**. 1823 1823 * Click the **Add integration** button (the button with the **+** symbol). 1824 1824 1825 -[[image:thingseye-io-step-1.png ||height="625" width="1000"]]2017 +[[image:thingseye-io-step-1.png]] 1826 1826 1827 1827 1828 1828 On the **Add integration** window, configure the following: ... ... @@ -1837,7 +1837,7 @@ 1837 1837 ** Allow create devices or assets 1838 1838 * Click the **Next** button. you will be navigated to the **Uplink data converter** tab. 1839 1839 1840 -[[image:thingseye-io-step-2.png ||height="625" width="1000"]]2032 +[[image:thingseye-io-step-2.png]] 1841 1841 1842 1842 1843 1843 **Uplink data converter:** ... ... @@ -1848,7 +1848,7 @@ 1848 1848 * 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]]. 1849 1849 * Click the **Next** button. You will be navigated to the **Downlink data converter **tab. 1850 1850 1851 -[[image:thingseye-io-step-3.png ||height="625" width="1000"]]2043 +[[image:thingseye-io-step-3.png]] 1852 1852 1853 1853 1854 1854 **Downlink data converter (this is an optional step):** ... ... @@ -1859,7 +1859,7 @@ 1859 1859 * 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]]. 1860 1860 * Click the **Next** button. You will be navigated to the **Connection** tab. 1861 1861 1862 -[[image:thingseye-io-step-4.png ||height="625" width="1000"]]2054 +[[image:thingseye-io-step-4.png]] 1863 1863 1864 1864 1865 1865 **Connection:** ... ... @@ -1866,7 +1866,7 @@ 1866 1866 1867 1867 * Choose **Region** from the **Host type**. 1868 1868 * 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/...). 1869 -* 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**). 1870 1870 * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**. 1871 1871 1872 1872 [[image:message-1.png]] ... ... @@ -1874,54 +1874,64 @@ 1874 1874 1875 1875 * Click the **Add** button. 1876 1876 1877 -[[image:thingseye-io-step-5.png ||height="625" width="1000"]]2069 +[[image:thingseye-io-step-5.png]] 1878 1878 1879 1879 1880 -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. 1881 1881 1882 1882 1883 -[[image:thingseye.io_integrationsCenter_integrations.png ||height="686" width="1000"]]2075 +[[image:thingseye.io_integrationsCenter_integrations.png]] 1884 1884 1885 1885 1886 1886 ==== 3.5.2.1 Viewing integration details ==== 1887 1887 2080 + 1888 1888 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. 1889 1889 1890 -[[image:integration-details.png ||height="686" width="1000"]]2083 +[[image:integration-details.png]] 1891 1891 1892 1892 1893 1893 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. 1894 1894 1895 1895 {{info}} 1896 -See also ThingsEye documentation. 2089 +See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]]. 1897 1897 {{/info}} 1898 1898 1899 -==== **3.5.2.2 Viewing events** ==== 1900 1900 2093 +==== 3.5.2.2 Viewing events ==== 2094 + 2095 + 1901 1901 The **Events **tab displays all the uplink messages from the LT-22222-L. 1902 1902 1903 1903 * Select **Debug **from the **Event type** dropdown. 1904 1904 * Select the** time frame** from the **time window**. 1905 1905 1906 -[[image:thingseye-events.png ||height="686" width="1000"]]2101 +[[image:thingseye-events.png]] 1907 1907 1908 1908 1909 -* 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. 1910 1910 1911 -[[image:thingseye-json.png ||width="1000"]]2106 +[[image:thingseye-json.png]] 1912 1912 1913 1913 1914 -==== **3.5.2.3 Deleting an integration**====2109 +==== 3.5.2.3 Deleting an integration ==== 1915 1915 2111 + 1916 1916 If you want to delete an integration, click the **Delete integratio**n button on the Integrations page. 1917 1917 1918 1918 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 + 1919 1919 == 3.6 Interface Details == 1920 1920 1921 1921 === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) === 1922 1922 1923 1923 1924 -Supports 2126 +Supports** NPN-type **sensors. 1925 1925 1926 1926 [[image:1653356991268-289.png]] 1927 1927 ... ... @@ -2043,15 +2043,15 @@ 2043 2043 ))) 2044 2044 2045 2045 2046 -(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor 2248 +(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor 2047 2047 2048 -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. 2049 2049 2050 -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. 2051 2051 2052 2052 [[image:image-20230616235145-1.png]] 2053 2053 2054 -(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector 2256 +(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector 2055 2055 2056 2056 [[image:image-20240219115718-1.png]] 2057 2057 ... ... @@ -2127,8 +2127,9 @@ 2127 2127 [[image:image-20220524100215-10.png||height="382" width="723"]] 2128 2128 2129 2129 2130 -== 3.7 LED sIndicators ==2332 +== 3.7 LED Indicators == 2131 2131 2334 + 2132 2132 The table below lists the behavior of LED indicators for each port function. 2133 2133 2134 2134 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) ... ... @@ -2161,18 +2161,22 @@ 2161 2161 2162 2162 = 4. Using AT Commands = 2163 2163 2367 + 2164 2164 The LT-22222-L supports programming using AT Commands. 2165 2165 2370 + 2166 2166 == 4.1 Connecting the LT-22222-L to a PC == 2167 2167 2373 + 2168 2168 ((( 2169 -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. 2170 2170 2171 -[[image:usb-ttl-programming.png]] 2377 +[[image:usb-ttl-audio-jack-connection.jpg]] 2378 + 2379 + 2172 2172 ))) 2173 2173 2174 2174 2175 - 2176 2176 ((( 2177 2177 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: 2178 2178 ))) ... ... @@ -2183,7 +2183,10 @@ 2183 2183 ((( 2184 2184 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/]] 2185 2185 2393 + 2186 2186 == 4.2 LT-22222-L related AT commands == 2395 + 2396 + 2187 2187 ))) 2188 2188 2189 2189 ((( ... ... @@ -2202,39 +2202,39 @@ 2202 2202 * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey) 2203 2203 * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI) 2204 2204 * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON) 2205 -* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification) 2206 -* AT+DR: Get or set the Data Rate. (0-7 corresponding to DR_X) 2207 -* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing 2208 -* AT+PNM: Get or set the public network mode. (0: off, 1: on) 2209 -* AT+RX2FQ: Get or set the Rx2 window frequency 2210 -* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X) 2211 -* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms 2212 -* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms 2213 -* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms 2214 -* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms 2215 -* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA) 2216 -* AT+NWKID: Get or set the Network ID 2217 -* AT+FCU: Get or set the Frame Counter Uplink (FCntUp) 2218 -* AT+FCD: Get or set the Frame Counter Downlink (FCntDown) 2219 -* AT+CLASS: Get or set the Device Class 2220 -* AT+JOIN: Join network 2221 -* AT+NJS: Get OTAA Join Status 2222 -* AT+SENDB: Send hexadecimal data along with the application port 2223 -* AT+SEND: Send text data along with the application port 2224 -* AT+RECVB: Print last received data in binary format (with hexadecimal values) 2225 -* AT+RECV: Print last received data in raw format 2226 -* AT+VER: Get current image version and Frequency Band 2227 -* AT+CFM: Get or Set the confirmation mode (0-1) 2228 -* AT+CFS: Get confirmation status of the last AT+SEND (0-1) 2229 -* AT+SNR: Get the SNR of the last received packet 2230 -* AT+RSSI: Get the RSSI of the last received packet 2231 -* AT+TDC: Get or set the application data transmission interval in ms 2232 -* AT+PORT: Get or set the application port 2233 -* AT+DISAT: Disable AT commands 2234 -* AT+PWORD: Set password, max 9 digits 2235 -* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode 2236 -* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470 2237 -* 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 2238 2238 ))) 2239 2239 2240 2240 ... ... @@ -2380,16 +2380,19 @@ 2380 2380 2381 2381 == 5.1 Counting how many objects pass through the flow line == 2382 2382 2593 + 2383 2383 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]]? 2384 2384 2385 2385 2386 2386 = 6. FAQ = 2387 2387 2599 + 2388 2388 This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly. 2389 2389 2390 2390 2391 2391 == 6.1 How to update the firmware? == 2392 2392 2605 + 2393 2393 Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to: 2394 2394 2395 2395 * Support new features ... ... @@ -2399,7 +2399,7 @@ 2399 2399 You will need the following things before proceeding: 2400 2400 2401 2401 * 3.5mm programming cable (included with the LT-22222-L as an additional accessory) 2402 -* USB to TTL adapter 2615 +* USB to TTL adapter/converter 2403 2403 * 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) 2404 2404 * 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. 2405 2405 ... ... @@ -2409,7 +2409,7 @@ 2409 2409 2410 2410 Below is the hardware setup for uploading a firmware image to the LT-22222-L: 2411 2411 2412 -[[image:usb-ttl- programming.png]]2625 +[[image:usb-ttl-audio-jack-connection.jpg]] 2413 2413 2414 2414 2415 2415 ... ... @@ -2442,6 +2442,8 @@ 2442 2442 ((( 2443 2443 ((( 2444 2444 == 6.2 How to change the LoRaWAN frequency band/region? == 2658 + 2659 + 2445 2445 ))) 2446 2446 ))) 2447 2447 ... ... @@ -2453,6 +2453,8 @@ 2453 2453 2454 2454 2455 2455 == 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? == 2671 + 2672 + 2456 2456 ))) 2457 2457 2458 2458 ((( ... ... @@ -2526,11 +2526,13 @@ 2526 2526 2527 2527 == 6.4 How to change the uplink interval? == 2528 2528 2746 + 2529 2529 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/]] 2530 2530 2531 2531 2532 2532 == 6.5 Can I see the counting event in the serial output? == 2533 2533 2752 + 2534 2534 ((( 2535 2535 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. 2536 2536 ... ... @@ -2537,6 +2537,7 @@ 2537 2537 2538 2538 == 6.6 Can I use point-to-point communication with LT-22222-L? == 2539 2539 2759 + 2540 2540 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]]. 2541 2541 2542 2542 ... ... @@ -2545,6 +2545,7 @@ 2545 2545 ((( 2546 2546 == 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? == 2547 2547 2768 + 2548 2548 * If the device is not properly shut down and is directly powered off. 2549 2549 * It will default to a power-off state. 2550 2550 * In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory. ... ... @@ -2552,6 +2552,7 @@ 2552 2552 2553 2553 == 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? == 2554 2554 2776 + 2555 2555 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: 2556 2556 2557 2557 ... ... @@ -2560,16 +2560,19 @@ 2560 2560 2561 2561 == 6.9 Can the LT-22222-L save the RO state? == 2562 2562 2785 + 2563 2563 To enable this feature, the firmware version must be 1.6.0 or higher. 2564 2564 2565 2565 2566 2566 == 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? == 2567 2567 2791 + 2568 2568 It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose. 2569 2569 2570 2570 2571 2571 = 7. Troubleshooting = 2572 2572 2797 + 2573 2573 This section provides some known troubleshooting tips. 2574 2574 2575 2575 ... ... @@ -2578,6 +2578,8 @@ 2578 2578 ((( 2579 2579 ((( 2580 2580 == 7.1 Downlink isn't working. How can I solve this? == 2806 + 2807 + 2581 2581 ))) 2582 2582 ))) 2583 2583 ... ... @@ -2589,6 +2589,8 @@ 2589 2589 2590 2590 2591 2591 == 7.2 Having trouble uploading an image? == 2819 + 2820 + 2592 2592 ))) 2593 2593 2594 2594 ((( ... ... @@ -2599,6 +2599,8 @@ 2599 2599 2600 2600 2601 2601 == 7.3 Why can't I join TTN in the US915 /AU915 bands? == 2831 + 2832 + 2602 2602 ))) 2603 2603 2604 2604 ((( ... ... @@ -2608,6 +2608,7 @@ 2608 2608 2609 2609 == 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? == 2610 2610 2842 + 2611 2611 The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue. 2612 2612 Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]] 2613 2613 ... ... @@ -2614,6 +2614,7 @@ 2614 2614 2615 2615 = 8. Ordering information = 2616 2616 2849 + 2617 2617 (% style="color:#4f81bd" %)**LT-22222-L-XXX:** 2618 2618 2619 2619 (% style="color:#4f81bd" %)**XXX:** ... ... @@ -2628,8 +2628,10 @@ 2628 2628 * (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865 2629 2629 * (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779 2630 2630 2864 + 2631 2631 = 9. Package information = 2632 2632 2867 + 2633 2633 **Package includes**: 2634 2634 2635 2635 * 1 x LT-22222-L I/O Controller ... ... @@ -2644,8 +2644,10 @@ 2644 2644 * Package Size / pcs : 14.5 x 8 x 5 cm 2645 2645 * Weight / pcs : 170 g 2646 2646 2882 + 2647 2647 = 10. Support = 2648 2648 2885 + 2649 2649 * ((( 2650 2650 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. 2651 2651 ))) ... ... @@ -2657,6 +2657,7 @@ 2657 2657 2658 2658 = 11. Reference = 2659 2659 2897 + 2660 2660 * 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]] 2661 2661 * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]] 2662 2662 * [[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