Changes for page LT-22222-L -- LoRa I/O Controller User Manual
Last modified by Mengting Qiu on 2025/06/04 18:42
From version 241.1
edited by Mengting Qiu
on 2025/02/24 10:23
on 2025/02/24 10:23
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 10 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ting1 +XWiki.pradeeka - Content
-
... ... @@ -21,15 +21,10 @@ 21 21 22 22 == 1.1 What is the LT-22222-L I/O Controller? == 23 23 24 - 25 25 ((( 26 26 ((( 27 -{{info}} 28 -**This manual is also applicable to the LT-33222-L.** 29 -{{/info}} 26 +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. 30 30 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. 32 - 33 33 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. 34 34 ))) 35 35 ))) ... ... @@ -41,24 +41,23 @@ 41 41 ((( 42 42 You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways: 43 43 44 -* If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Stack CommunityNetwork), you can select a network and register the LT-22222-L I/O controller with it.39 +* 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. 45 45 * 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. 46 46 * Setup your own private LoRaWAN network. 42 + 43 +{{info}} 44 + 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. 45 +{{/info}} 47 47 ))) 48 48 49 49 ((( 50 - 49 +[[image:1653295757274-912.png]] 51 51 52 - Thenetwork diagram below illustrates how the LT-22222-L communicates with a typical LoRaWAN network.51 + 53 53 ))) 54 54 55 -(% class="wikigeneratedid" %) 56 -[[image:lorawan-nw.jpg||height="354" width="900"]] 57 - 58 - 59 59 == 1.2 Specifications == 60 60 61 - 62 62 (% style="color:#037691" %)**Hardware System:** 63 63 64 64 * STM32L072xxxx MCU ... ... @@ -100,7 +100,6 @@ 100 100 101 101 == 1.3 Features == 102 102 103 - 104 104 * LoRaWAN Class A & Class C modes 105 105 * Optional Customized LoRa Protocol 106 106 * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869 ... ... @@ -111,7 +111,6 @@ 111 111 112 112 == 1.4 Applications == 113 113 114 - 115 115 * Smart buildings & home automation 116 116 * Logistics and supply chain management 117 117 * Smart metering ... ... @@ -119,73 +119,54 @@ 119 119 * Smart cities 120 120 * Smart factory 121 121 122 -== 1.5 Hardware Variants == 123 - 124 - 125 -(% border="1" cellspacing="3" style="width:510px" %) 126 -|(% style="background-color:#4f81bd; color:white; width:94px" %)**Model**|(% style="background-color:#4f81bd; color:white; width:172px" %)**Photo**|(% style="background-color:#4f81bd; color:white; width:244px" %)**Description** 127 -|(% style="width:94px" %)**LT-33222-L**|(% style="width:172px" %)((( 128 -(% style="text-align:center" %) 129 -[[image:lt33222-l.jpg||height="110" width="95"]] 130 -)))|(% style="width:256px" %)((( 131 -* 3 x Digital Input (Bi-direction) 132 -* 3 x Digital Output 133 -* 2 x Relay Output (5A@250VAC / 30VDC) 134 -* 2 x 0~~20mA Analog Input (res:0.01mA) 135 -* 2 x 0~~30V Analog Input (res:0.01v) 136 -* 1 x Counting Port 137 -))) 138 - 139 139 = 2. Assembling the device = 140 140 141 141 == 2.1 Connecting the antenna == 142 142 143 - 144 144 Connect the LoRa antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper screw terminal block. Secure the antenna by tightening it clockwise. 145 145 146 146 {{warning}} 147 - **Warning! Do not power on the device without connecting the antenna.**121 +Warning! Do not power on the device without connecting the antenna. 148 148 {{/warning}} 149 149 150 - 151 151 == 2.2 Terminals == 152 152 126 +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. 153 153 154 - The LT-22222-L has two screw terminal blocks. The upper screw terminal blockhas 6 screw terminalsand thelower screwterminalblockhas 10 screw terminals.128 +Upper screw terminal block (from left to right): 155 155 156 -**Upper screw terminal block (from left to right):** 130 +(% style="width:634px" %) 131 +|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function 132 +|(% style="width:295px" %)GND|(% style="width:338px" %)Ground 133 +|(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage 134 +|(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2 135 +|(% style="width:295px" %)AVI1|(% style="width:338px" %)Analog Voltage Input Terminal 1 136 +|(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2 137 +|(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1 157 157 158 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:381px" %) 159 -|=(% style="width: 139px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 242px;background-color:#4f81bd;color:white" %)Function 160 -|(% style="width:139px" %)GND|(% style="width:242px" %)Ground 161 -|(% style="width:139px" %)VIN|(% style="width:242px" %)Input Voltage 162 -|(% style="width:139px" %)AVI2|(% style="width:242px" %)Analog Voltage Input Terminal 2 163 -|(% style="width:139px" %)AVI1|(% style="width:242px" %)Analog Voltage Input Terminal 1 164 -|(% style="width:139px" %)ACI2|(% style="width:242px" %)Analog Current Input Terminal 2 165 -|(% style="width:139px" %)ACI1|(% style="width:242px" %)Analog Current Input Terminal 1 139 +Lower screw terminal block (from left to right): 166 166 167 -**Lower screw terminal block (from left to right):** 141 +(% style="width:633px" %) 142 +|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function 143 +|(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1 144 +|(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1 145 +|(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2 146 +|(% style="width:296px" %)RO2-1|(% style="width:334px" %)Relay Output 2 147 +|(% style="width:296px" %)DI2+|(% style="width:334px" %)Digital Input 2 148 +|(% style="width:296px" %)DI2-|(% style="width:334px" %)Digital Input 2 149 +|(% style="width:296px" %)DI1+|(% style="width:334px" %)Digital Input 1 150 +|(% style="width:296px" %)DI1-|(% style="width:334px" %)Digital Input 1 151 +|(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2 152 +|(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1 168 168 169 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:253px" %) 170 -|=(% style="width: 125px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 128px;background-color:#4f81bd;color:white" %)Function 171 -|(% style="width:125px" %)RO1-2|(% style="width:128px" %)Relay Output 1 172 -|(% style="width:125px" %)RO1-1|(% style="width:128px" %)Relay Output 1 173 -|(% style="width:125px" %)RO2-2|(% style="width:128px" %)Relay Output 2 174 -|(% style="width:125px" %)RO2-1|(% style="width:128px" %)Relay Output 2 175 -|(% style="width:125px" %)DI2+|(% style="width:128px" %)Digital Input 2 176 -|(% style="width:125px" %)DI2-|(% style="width:128px" %)Digital Input 2 177 -|(% style="width:125px" %)DI1+|(% style="width:128px" %)Digital Input 1 178 -|(% style="width:125px" %)DI1-|(% style="width:128px" %)Digital Input 1 179 -|(% style="width:125px" %)DO2|(% style="width:128px" %)Digital Output 2 180 -|(% style="width:125px" %)DO1|(% style="width:128px" %)Digital Output 1 154 +== 2.3 Powering the device == 181 181 182 - ==2.3ConnectingLT-22222-Lto aPowerSource==156 +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. 183 183 158 +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** The Things Stack. 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. 184 184 185 -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. 186 - 187 187 {{warning}} 188 - **We recommend that you power on the LT-22222-L afteradding its registration information to theLoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.**161 +We recommend that you power on the LT-22222-L after configuring its registration information with a LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail. 189 189 {{/warning}} 190 190 191 191 ... ... @@ -192,58 +192,37 @@ 192 192 [[image:1653297104069-180.png]] 193 193 194 194 195 -= 3. Registering LT-22222-Lwith a LoRaWAN Network Server =168 += 3. Registering with a LoRaWAN Network Server = 196 196 170 +By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode. It supports OTAA (Over-the-Air Activation), the most secure method for activating a device with a LoRaWAN network server. The LT-22222-L comes with device registration information that allows you to register it with a LoRaWAN network, enabling the device to perform OTAA activation with the network server upon initial power-up and after any subsequent reboots. 197 197 198 - TheLT-22222-L supportsbothOTAA(Over-the-AirActivation)andABP (ActivationBy Personalization)methodsto activatewithaLoRaWANNetworkServer.However,OTAAisthemostsecuremethod foractivatinga device witha LoRaWAN NetworkServer.OTAA regeneratessessionysuponinitialregistrationandregeneratesnewsessionkeysafteranysubsequentreboots. Bydefault, theLT-22222-L isconfiguredtooperatein LoRaWAN ClassCmode.172 +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. 199 199 174 +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. 200 200 201 - ==3.1Prerequisites==176 +The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network. 202 202 178 +[[image:image-20220523172350-1.png||height="266" width="864"]] 203 203 204 - TheLT-22222-L comes with device registration information such as DevEUI, AppEUI, and AppKey which allows you to register it with a LoRaWAN network.Thisregistration information can befound on a sticker that can be found insidethepackage. Pleasekeep the **registration information** sticker in a safe place for future reference.180 +=== 3.2.1 Prerequisites === 205 205 182 +Make sure you have the device registration information such as DevEUI, AppEUI, and AppKey with 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. 183 + 206 206 [[image:image-20230425173427-2.png||height="246" width="530"]] 207 207 208 -{{info}} 209 -If you are unable to set the provided root key and other identifiers in the network server, you must generate new keys and identifiers with the network server and configure the device with them using AT commands. 210 -{{/info}} 211 - 212 212 The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers. 213 213 188 +=== 3.2.2 The Things Stack Sandbox (TTSS) === 214 214 215 -== 3.2 The Things Stack == 216 - 217 - 218 -This section guides you through how to register your LT-22222-L with The Things Stack Sandbox. 219 - 220 -{{info}} 221 221 The Things Stack Sandbox was formally called The Things Stack Community Edition. 222 -{{/info}} 223 223 224 - 225 -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. 226 - 227 - 228 -[[image:dragino-lorawan-nw-lt-22222-n.jpg||height="374" width="1400"]] 229 - 230 -{{info}} 231 - 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. 232 -{{/info}} 233 - 234 - 235 -=== 3.2.1 Setting up === 236 - 237 - 238 -* Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet. 239 -* Log in to your The Things Stack Sandbox account. 240 -* Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs). 241 -* Go to your application's page and click on the **End devices** in the left menu. 192 +* Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account. 193 +* Create an application with The Things Stack if you do not have one yet. 194 +* Go to your application page and click on the **End devices** in the left menu. 242 242 * On the End devices page, click on **+ Register end device**. Two registration options are available: 243 243 244 -==== 3.2. 1.1 Using the LoRaWAN Device Repository ====197 +==== 3.2.2.1 Using the LoRaWAN Device Repository ==== 245 245 246 - 247 247 * On the **Register end device** page: 248 248 ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**. 249 249 ** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists. ... ... @@ -254,7 +254,7 @@ 254 254 *** **Profile (Region)**: Select the region that matches your device. 255 255 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 256 256 257 -[[image:lt-22222-l-dev-repo-reg-p1.png]] 209 +[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]] 258 258 259 259 260 260 * Register end device page continued... ... ... @@ -261,21 +261,15 @@ 261 261 ** 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'. 262 262 ** In the **DevEUI** field, enter the **DevEUI**. 263 263 ** In the **AppKey** field, enter the **AppKey.** 264 -** In the **End device ID** field, enter a unique name for your LT-22222- Lwithin this application.216 +** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. 265 265 ** Under **After registration**, select the **View registered end device** option. 266 -** Click **Register end device** button. 267 267 268 -[[image:lt-22222-l-dev-repo-reg-p2.png]] 219 +[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]] 269 269 221 +==== ==== 270 270 271 - *Youwill benavigatedto the**Deviceoverview** page.223 +==== 3.2.2.2 Adding device manually ==== 272 272 273 -[[image:lt-22222-device-overview.png]] 274 - 275 - 276 -==== 3.2.1.2 Adding device manually ==== 277 - 278 - 279 279 * On the **Register end device** page: 280 280 ** Select the option **Enter end device specifies manually** under **Input method**. 281 281 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. ... ... @@ -285,11 +285,11 @@ 285 285 ** Select the option **Over the air activation (OTAA)** under the **Activation mode.** 286 286 ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list. 287 287 288 -[[image:lt-22222-l-manually-p1.png]] 234 +[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]] 289 289 290 290 291 291 * Register end device page continued... 292 -** 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**//'238 +** 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' 293 293 ** In the **DevEUI** field, enter the **DevEUI**. 294 294 ** In the **AppKey** field, enter the **AppKey**. 295 295 ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. ... ... @@ -296,62 +296,46 @@ 296 296 ** Under **After registration**, select the **View registered end device** option. 297 297 ** Click the **Register end device** button. 298 298 299 -[[image:lt-22222-l-manually-p2.png]] 245 +[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]] 300 300 301 301 302 302 You will be navigated to the **Device overview** page. 303 303 304 304 305 -[[image:lt-22222-device-overview.png]] 251 +[[image:lt-22222-device-overview.png||height="625" width="1000"]] 306 306 307 307 308 -=== 3.2.2 Joining === 254 +==== 3.2.2.3 Joining ==== 309 309 256 +On the Device overview page, click on **Live data** tab. The Live data panel for your device will display. 310 310 311 - Ontheenddevice'spage(inthiscase, lt-22222-l),clickon **Live data**tab.TheLive datapanelfor yourdevice will display.Initially,it isblank.258 +Now power on your LT-22222-L. It will begin joining The 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**). 312 312 313 -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. 314 314 261 +[[image:lt-22222-join-network.png||height="625" width="1000"]] 315 315 316 -[[image:lt-22222-l-joining.png]] 317 317 264 +By default, you will receive an uplink data message from the device every 10 minutes. 318 318 319 - ===3.2.3Uplinks===266 +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. 320 320 321 - 322 -After successfully joining, the device will send its first **uplink data message** to The Things Stack application it belongs to (in this example, it is **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. 323 - 324 -Click on one of the **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the **decode_payload {}** JSON object. 325 - 326 326 [[image:lt-22222-ul-payload-decoded.png]] 327 327 328 328 329 -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]**271 +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** > **Payload formatters** > **Uplink**. Then select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes. 330 330 331 331 {{info}} 332 332 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. 333 333 {{/info}} 334 334 335 -[[image:lt-22222-ul-payload-fmt.png]] 277 +[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]] 336 336 337 337 338 - Wehavewritten a payload formatterthat resolves somedecoding issuespresentinThe Things StackDevice Repository payload formatter. You can add it under the **CustomJavaScript formatter**. It can be found [[here>>https://github.com/dragino/dragino-end-node-decoder/blob/main/LT22222-L/v1.6_decoder_ttn%20.txt]]:280 +== 3.3 Work Modes and Uplink Payload formats == 339 339 340 -(% class="wikigeneratedid" %) 341 -[[image:lt-22222-l-js-custom-payload-formatter.png]] 342 342 283 +The LT-22222-L has 5 **work modes**. It also has an interrupt/trigger mode for different types of applications that can be used together with any work mode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands. 343 343 344 -=== 3.2.4 Downlinks === 345 - 346 - 347 -When the LT-22222-L receives a downlink message from the LoRaWAN Network Server, the **RX LED** turns on for **1 second**. 348 - 349 - 350 -== 3.3 Working Modes and Uplink Payload formats == 351 - 352 - 353 -The LT-22222-L has 5 **working modes**. It also has an interrupt/trigger mode for different types of applications that can be used together with any working mode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands. 354 - 355 355 * (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO 356 356 357 357 * (% style="color:blue" %)**MOD2**(%%): Double DI Counting + DO + RO ... ... @@ -364,18 +364,16 @@ 364 364 365 365 * (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5 366 366 367 -The uplink messages are sent over LoRaWAN FPort =2. By default, an uplink message is sent every 10 minutes.297 +The uplink messages are sent over LoRaWAN FPort 2. By default, an uplink message is sent every 10 minutes. 368 368 369 - 370 370 === 3.3.1 AT+MOD~=1, 2ACI+2AVI === 371 371 372 - 373 373 ((( 374 374 This is the default mode. 375 375 376 376 The uplink payload is 11 bytes long. 377 377 378 -(% style="color:red" %)**Note:The maximum count depends on the bytes number of bytes.306 +(% style="color:red" %)**Note:The maximum count depends on the bytes it is. 379 379 The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 380 380 It starts counting again when it reaches the maximum value.**(% style="display:none" wfd-invisible="true" %) 381 381 ... ... @@ -435,14 +435,9 @@ 435 435 * [1] DO2 channel output is LOW, and the DO2 LED is ON. 436 436 * [0] DO1 channel output state: 437 437 ** DO1 is FLOATING when there is no load between DO1 and V+. 438 -** DO1 is HIGH andthere is a load between DO1 and V+.366 +** DO1 is HIGH when there is a load between DO1 and V+. 439 439 ** DO1 LED is OFF in both cases. 440 440 441 -Reserve = 0 442 - 443 -MOD = 1 444 - 445 - 446 446 === 3.3.2 AT+MOD~=2, (Double DI Counting) === 447 447 448 448 ... ... @@ -521,7 +521,6 @@ 521 521 522 522 === 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI === 523 523 524 - 525 525 (% style="color:red" %)**Note: The maximum count depends on the bytes it is. 526 526 The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 527 527 It starts counting again when it reaches the maximum value.** ... ... @@ -575,7 +575,6 @@ 575 575 576 576 === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting === 577 577 578 - 579 579 (% style="color:red" %)**Note:The maximum count depends on the bytes it is. 580 580 The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 581 581 It starts counting again when it reaches the maximum value.** ... ... @@ -627,25 +627,24 @@ 627 627 ))) 628 628 629 629 ((( 630 -AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s. 551 +Other AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s. 631 631 ))) 632 632 633 633 ((( 634 634 **In addition to that, below are the commands for AVI1 Counting:** 635 635 636 -(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI 1Count to 60)**557 +(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI Count to 60)** 637 637 638 -(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If theAVI1 voltageishigher than VOLMAX (20000mV =20V),thecounter increasesby1)**559 +(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 639 639 640 -(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If theAVI1 voltageislower than VOLMAX (20000mV =20V), counter increasesby1)**561 +(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)** 641 641 642 -(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If theAVI1 voltageishigher than VOLMAX (20000mV =20V), counter increasesby1)**563 +(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 643 643 ))) 644 644 645 645 646 646 === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI === 647 647 648 - 649 649 (% style="color:red" %)**Note:The maximum count depends on the bytes it is. 650 650 The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 651 651 It starts counting again when it reaches the maximum value.** ... ... @@ -701,27 +701,24 @@ 701 701 ))) 702 702 703 703 704 -=== 3.3.6 AT+ADDMOD~=6 (Trigger Mode, Optional) === 624 +=== 3.3.6 AT+ADDMOD~=6. (Trigger Mode, Optional) === 705 705 706 706 707 -(% style="color:#4f81bd" %)**This mode is optional and intended for trigger purposes. It can operate __alongside__with other modes.**627 +(% style="color:#4f81bd" %)**This mode is optional and intended for trigger purposes. It can operate together with other modes.** 708 708 709 -For example, if you configure the following commands: 629 +For example, if you configured the following commands: 710 710 711 -* **AT+MOD=1 ** **~-~->** Sets the default workingmode712 -* **AT+ADDMOD6=1** **~-~->** Enable strigger mode631 +* **AT+MOD=1 ** **~-~->** The default work mode 632 +* **AT+ADDMOD6=1** **~-~->** Enable trigger mode 713 713 714 -The LT-22222-L will continuously monitor AV1, AV2, AC1, and AC2 every 5 seconds. Itwill send uplink packets in two cases:634 +The LT-22222-L will continuously monitor AV1, AV2, AC1, and AC2 every 5 seconds. LT will send uplink packets in two cases: 715 715 716 -1. Periodic uplink :Based on TDC time.setabove). These are (% style="color:#4f81bd" %)**unconfirmed**(%%) uplinks.636 +1. Periodically uplink (Based on TDC time). The payload is the same as in normal mode (MOD=1 for the commands above). These are (% style="color:#4f81bd" %)**unconfirmed**(%%) uplinks. 717 717 1. ((( 718 -Trigger uplink: sent when a trigger condition is met. In this case, LT will send two packets 719 - 720 -* The first uplink uses the payload specified in trigger mode (MOD=6). 721 -* The second packet uses the normal mode payload (MOD=1 as set above). Both are (% style="color:#4f81bd" %)**confirmed uplinks.** 638 +Trigger uplink when the trigger condition is met. LT will send two packets in this case. The first uplink uses the payload specified in trigger mode (MOD=6). The second packet uses the normal mode payload (MOD=1 as set above). Both are (% style="color:#4f81bd" %)**confirmed uplinks.** 722 722 ))) 723 723 724 -(% style="color:#037691" %)**AT Commands to set Trigger Condition s**:641 +(% style="color:#037691" %)**AT Commands to set Trigger Condition**: 725 725 726 726 (% style="color:#4f81bd" %)**Trigger based on voltage**: 727 727 ... ... @@ -730,9 +730,9 @@ 730 730 731 731 **Example:** 732 732 733 -AT+AVLIM=3000,6000,0,2000 (triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V) 650 +AT+AVLIM=3000,6000,0,2000 (triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V) 734 734 735 -AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage islower than 5V. Use 0 for parameters that are not in use)652 +AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage lower than 5V. Use 0 for parameters that are not in use) 736 736 737 737 738 738 (% style="color:#4f81bd" %)**Trigger based on current**: ... ... @@ -742,7 +742,7 @@ 742 742 743 743 **Example:** 744 744 745 -AT+ACLIM=10000,15000,0,0 (triggers an uplink if AC1 current is lower than 10mA or higher than 15mA)662 +AT+ACLIM=10000,15000,0,0 (triggers an uplink if ACI1 voltage is lower than 10mA or higher than 15mA) 746 746 747 747 748 748 (% style="color:#4f81bd" %)**Trigger based on DI status**: ... ... @@ -759,9 +759,9 @@ 759 759 760 760 (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:** 761 761 762 - **Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**679 +Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 763 763 764 - **Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4681 +Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4 765 765 766 766 AA: Type Code for this downlink Command: 767 767 ... ... @@ -788,9 +788,9 @@ 788 788 789 789 (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:** 790 790 791 -MOD6 Payload: atotal of 11 bytes708 +MOD6 Payload: total of 11 bytes 792 792 793 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)710 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 794 794 |(% 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** 795 795 |Value|((( 796 796 TRI_A FLAG ... ... @@ -802,9 +802,9 @@ 802 802 MOD(6) 803 803 ))) 804 804 805 -(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Total 1 byte as below .722 +(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below 806 806 807 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)724 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 808 808 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 809 809 |((( 810 810 AV1_LOW ... ... @@ -828,12 +828,12 @@ 828 828 829 829 **Example:** 830 830 831 -10100000: This means the systemis configuredto use the triggersAV1_LOW and AV2_LOW.748 +10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW 832 832 833 833 834 -(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger ed. Total 1 byte as below.751 +(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below 835 835 836 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)753 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 837 837 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 838 838 |((( 839 839 AV1_LOW ... ... @@ -857,31 +857,31 @@ 857 857 858 858 **Example:** 859 859 860 -10000000: The uplink is triggered by AV1_LOW,indicatingthatthe voltage is too low.777 +10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low. 861 861 862 862 863 -(% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger ed. Total 1.780 +(% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below 864 864 865 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)866 -| (% style="width:50px" %)**bit(% style="width:50px" %)**bit(% style="width:50px" %)**bit(% style="width:50px" %)**bit(% style="width:90px" %)**bit(% style="width:80px" %)**bit(% style="width:90px" %)**bit(% style="width:95px" %)**bit867 -| (% 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_FLAG782 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 783 +|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0** 784 +|N/A|N/A|N/A|N/A|DI2_STATUS|DI2_FLAG|DI1_STATUS|DI1_FLAG 868 868 869 -* Each bit shows which status has been triggered on this uplink. 786 +* Each bits shows which status has been triggered on this uplink. 870 870 871 871 **Example:** 872 872 873 -00000111: This means both DI1 and DI2 triggersare enabled,and this packet is triggeredby DI1.790 +00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1. 874 874 875 -00000101: This means both DI1 and DI2 triggersare enabled.792 +00000101: Means both DI1 and DI2 trigger are enabled. 876 876 877 877 878 -(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable d. 0x00: MOD6 is disabled.795 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable. 879 879 880 -Downlink command to poll /requestMOD6 status:797 +Downlink command to poll MOD6 status: 881 881 882 882 **AB 06** 883 883 884 -When thedevicereceivesthis command, it will send the MOD6 payload.801 +When device got this command, it will send the MOD6 payload. 885 885 886 886 887 887 === 3.3.7 Payload Decoder === ... ... @@ -895,7 +895,6 @@ 895 895 896 896 == 3.4 Configure LT-22222-L via AT Commands or Downlinks == 897 897 898 - 899 899 ((( 900 900 You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks. 901 901 ))) ... ... @@ -902,7 +902,7 @@ 902 902 903 903 ((( 904 904 ((( 905 -There are two ty pes of commands:821 +There are two tytes of commands: 906 906 ))) 907 907 ))) 908 908 ... ... @@ -912,683 +912,398 @@ 912 912 913 913 === 3.4.1 Common commands === 914 914 915 - 916 916 ((( 917 -These are available for each sensor 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. 918 - 919 - 832 +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. 920 920 ))) 921 921 922 922 === 3.4.2 Sensor-related commands === 923 923 924 - 925 925 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. 926 926 839 +==== 3.4.2.1 Set Transmit Interval ==== 927 927 928 -==== 3.4.2.1 Set Transmit/Uplink Interval ==== 929 - 930 - 931 931 Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes. 932 932 933 933 (% style="color:#037691" %)**AT command** 934 934 935 -(% border="2" style="width:500px" %) 936 -|**Command**|AT+TDC=<time> 937 -|**Parameters**|**time **: uplink interval in milliseconds 938 -|**Get**|AT+TDC=? 939 -|**Response**|((( 940 -current uplink interval 941 - 942 -OK 943 -))) 944 -|**Set**|AT+TDC=<time> 945 -|**Response**|OK 845 +(% style="width:500px" %) 846 +|**Command**|AT+TDC<time> 847 +|**Response**| 848 +|**Parameters**|<time> uplink interval is in milliseconds 946 946 |**Example**|((( 947 947 AT+TDC=30000 948 948 949 -Sets the uplink interval to **30 seconds**(30000milliseconds)852 +Sets the uplink interval to 30,000 milliseconds (30 seconds) 950 950 ))) 951 951 952 952 (% style="color:#037691" %)**Downlink payload** 953 953 954 -(% border="2"style="width:500px" %)857 +(% style="width:500px" %) 955 955 |**Payload**|((( 956 956 <prefix><time> 957 957 ))) 958 958 |**Parameters**|((( 959 - **prefix**:0x01862 +<prefix> 0x01 960 960 961 - **time**:uplink interval in**seconds**, represented by**3 bytes**in**hexadecimal**.864 +<time> uplink interval is in milliseconds, represented by 3 bytes in hexadecimal. 962 962 ))) 963 963 |**Example**|((( 964 -01 **00 001E**867 +01 **00 75 30** 965 965 966 -Sets the uplink interval to **30 seconds**869 +Sets the uplink interval to 30,000 milliseconds (30 seconds) 967 967 968 -Conversion: 30 (dec) = 00 0 01E(hex)871 +Conversion: 30000 (dec) = 00 75 30 (hex) 969 969 970 -See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30]] 971 - 972 -[[image:Screenshot 2024-11-23 at 18.27.11.png]] 873 +See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]] 973 973 ))) 974 974 975 -==== 3.4.2.2 Set the Work ingMode (AT+MOD) ====876 +==== 3.4.2.2 Set the Work Mode (AT+MOD) ==== 976 976 977 977 978 -Sets the work ingmode.879 +Sets the work mode. 979 979 980 -(% style="color:#037691" %)**AT command** 881 +* (% style="color:#037691" %)**AT command:**(%%) (% style="color:blue" %)**AT+MOD=N ** 981 981 982 -(% border="2" style="width:500px" %) 983 -|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MOD=<working_mode> 984 -|(% style="width:97px" %)**Parameters**|(% style="width:413px" %)((( 985 -**working_mode** : 883 +Where N is the work mode. 986 986 987 - 1=(Default mode/factoryset): 2ACI+ 2AVI +DI+DO + RO885 +**Example**: AT+MOD=2. This will set the work mode to Double DI counting mode. 988 988 989 -2 = Double DI Counting + DO + RO 990 990 991 - 3=Single DI Counting +2x ACI + DO + RO888 +* (% style="color:#037691" %)**Downlink payload (prefix 0x0A):** 992 992 993 - 4=SingleDICounting+1xVoltageCounting+DO+ RO890 +(% style="color:blue" %)**0x0A aa **(%%)** ** ~/~/ Same as AT+MOD=aa 994 994 995 -5 = Single DI Counting + 2 x AVI + 1 x ACI + DO + RO 996 996 997 -6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5 998 -))) 999 -|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=? 1000 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)((( 1001 -Current working mode 1002 1002 1003 -OK 1004 -))) 1005 -|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode> 1006 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)((( 1007 -Attention:Take effect after ATZ 894 +==== 3.4.2.3 Poll an uplink ==== 1008 1008 1009 -OK 1010 -))) 1011 -|(% style="width:97px" %)**Example**|(% style="width:413px" %)((( 1012 -AT+MOD=2 896 +Requests the device to send an uplink. 1013 1013 1014 -Sets the device to working mode 2 (Double DI Counting + DO + RO) 1015 -))) 1016 1016 1017 -(% class="wikigeneratedid" %) 1018 -(% style="color:#037691" %)**Downlink payload** 899 +* (% style="color:#037691" %)**AT command:**(%%) There is no AT Command to poll uplink 1019 1019 1020 -(% border="2" style="width:500px" %) 1021 -|(% style="width:98px" %)**Payload**|(% style="width:400px" %)<prefix><working_mode> 1022 -|(% style="width:98px" %)**Parameters**|(% style="width:400px" %)((( 1023 -**prefix** : 0x0A 901 +* (% style="color:#037691" %)**Downlink payload (prefix 0x08):** 1024 1024 1025 -**working_mode** : Working mode, represented by 1 byte in hexadecimal. 1026 -))) 1027 -|(% style="width:98px" %)**Example**|(% style="width:400px" %)((( 1028 -0A **02** 903 +(% style="color:blue" %)**0x08 FF **(%%)** **~/~/ Poll an uplink 1029 1029 1030 -Sets the device to working mode 2 (Double DI Counting + DO + RO) 1031 -))) 905 +**Example**: 0x08FF, ask device to send an Uplink 1032 1032 1033 -==== 3.4.2.3 Request an uplink from the device ==== 1034 1034 1035 1035 1036 -Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode. 1037 - 1038 -(% style="color:#037691" %)**AT command** 1039 - 1040 -There is no AT Command available for this feature. 1041 - 1042 -(% style="color:#037691" %)**Downlink payload** 1043 - 1044 -(% border="2" style="width:500px" %) 1045 -|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF 1046 -|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08 1047 -|(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 1048 -08 **FF** 1049 - 1050 -Requests an uplink from LT-22222-L. 1051 -))) 1052 - 1053 1053 ==== 3.4.2.4 Enable/Disable Trigger Mode ==== 1054 1054 911 +Enable or disable the trigger mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]). 1055 1055 1056 - Enableordisablethe trigger mode forthecurrent workingmode(seealso [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).913 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0** 1057 1057 1058 -(% style="color: #037691" %)**ATCommand**915 +(% style="color:red" %)**1:** (%%)Enable the trigger mode 1059 1059 1060 -(% border="2" style="width:500px" %) 1061 -|(% style="width:95px" %)**Command**|(% style="width:403px" %)AT+ADDMOD6=<enable/disable trigger_mode> 1062 -|(% style="width:95px" %)**Response**|(% style="width:403px" %) 1063 -|(% style="width:95px" %)**Parameters**|(% style="width:403px" %)((( 1064 -**enable/disable trigger_mode** : 917 +(% style="color:red" %)**0: **(%%)Disable the trigger mode 1065 1065 1066 -1 = enable trigger mode 1067 1067 1068 -0 = disable trigger mode 1069 -))) 1070 -|(% style="width:95px" %)**Example**|(% style="width:403px" %)((( 1071 -AT+ADDMOD6=1 920 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A 06):** 1072 1072 1073 -Enable trigger mode for the current working mode 1074 -))) 922 +(% style="color:blue" %)**0x0A 06 aa **(%%) ~/~/ Same as AT+ADDMOD6=aa 1075 1075 1076 -(% style="color:#037691" %)**Downlink payload** 1077 1077 1078 -(% border="2" style="width:500px" %) 1079 -|(% style="width:97px" %)**Payload**|(% style="width:401px" %)<prefix><enable/disable trigger_mode> 1080 -|(% style="width:97px" %)**Parameters**|(% style="width:401px" %)((( 1081 -**prefix** : 0x0A 06 (two bytes in hexadecimal) 1082 1082 1083 -**enable/disable trigger_mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal. 1084 -))) 1085 -|(% style="width:97px" %)**Example**|(% style="width:401px" %)((( 1086 -0A 06 **01** 926 +==== 3.4.2.5 Poll trigger settings ==== 1087 1087 1088 -Enable trigger mode for the current working mode 1089 -))) 928 +Polls the trigger settings. 1090 1090 1091 - ====3.4.2.5Requesttriggersettings====930 +* (% style="color:#037691" %)**AT Command:** 1092 1092 932 +There is no AT Command for this feature. 1093 1093 1094 - Requeststhetriggersettings.934 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x AB 06):** 1095 1095 1096 -(% style="color: #037691" %)**ATCommand:**936 +(% style="color:blue" %)**0xAB 06 ** (%%) ~/~/ Poll the trigger settings. Device will uplink trigger settings once receive this command 1097 1097 1098 -There is no AT Command available for this feature. 1099 1099 1100 -(% style="color:#037691" %)**Downlink Payload** 1101 1101 1102 -(% border="2" style="width:500px" %) 1103 -|(% style="width:95px" %)**Payload**|(% style="width:403px" %)<prefix> 1104 -|(% style="width:95px" %)**Parameters**|(% style="width:403px" %)**prefix **: AB 06 (two bytes in hexadecimal) 1105 -|(% style="width:95px" %)**Example**|(% style="width:403px" %)((( 1106 -AB 06 940 +==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as a trigger ==== 1107 1107 1108 -Uplink the trigger settings. 1109 -))) 942 +Enable or disable DI1/DI2/DI2 as a trigger. 1110 1110 1111 - ====3.4.2.6Enable/Disable DI1/DI2/DI3as a trigger ====944 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >** 1112 1112 946 +**Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 1113 1113 1114 -Enable or disable DI1/DI2/DI3 as a trigger. 1115 1115 1116 -(% style="color:#037691" %)** ATCommand**949 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 02):** 1117 1117 1118 -(% border="2" style="width:500px" %) 1119 -|(% style="width:98px" %)**Command**|(% style="width:400px" %)AT+DTRI=<DI1_trigger>,<DI2_trigger> 1120 -|(% style="width:98px" %)**Response**|(% style="width:400px" %) 1121 -|(% style="width:98px" %)**Parameters**|(% style="width:400px" %)((( 1122 -**DI1_trigger:** 951 +(% style="color:blue" %)**0xAA 02 aa bb ** (%%) ~/~/ Same as AT+DTRI=aa,bb 1123 1123 1124 -1 = enable DI1 trigger 1125 1125 1126 -0 = disable DI1 trigger 1127 1127 1128 - **DI2_trigger**955 +==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ==== 1129 1129 1130 -1 = enable DI2 trigger 1131 - 1132 -0 = disable DI2 trigger 1133 -))) 1134 -|(% style="width:98px" %)**Example**|(% style="width:400px" %)((( 1135 -AT+DTRI=1,0 1136 - 1137 -Enable DI1 trigger, disable DI2 trigger 1138 -))) 1139 - 1140 -(% class="wikigeneratedid" %) 1141 -(% style="color:#037691" %)**Downlink Payload** 1142 - 1143 -(% border="2" style="width:500px" %) 1144 -|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix><DI1_trigger><DI2_trigger> 1145 -|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)((( 1146 -**prefix :** AA 02 (two bytes in hexadecimal) 1147 - 1148 -**DI1_trigger:** 1149 - 1150 -1 = enable DI1 trigger, represented by 1 byte in hexadecimal. 1151 - 1152 -0 = disable DI1 trigger, represented by 1 byte in hexadecimal. 1153 - 1154 -**DI2 _trigger** 1155 - 1156 -1 = enable DI2 trigger, represented by 1 byte in hexadecimal. 1157 - 1158 -0 = disable DI2 trigger, represented by 1 byte in hexadecimal. 1159 -))) 1160 -|(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 1161 -AA 02 **01 00** 1162 - 1163 -Enable DI1 trigger, disable DI2 trigger 1164 -))) 1165 - 1166 -==== 3.4.2.7 Trigger1 – Set DI1 or DI3 as a trigger ==== 1167 - 1168 - 1169 1169 Sets DI1 or DI3 (for LT-33222-L) as a trigger. 1170 1170 1171 -(% style="color:#037691" %)**AT Command** 959 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG1=a,b** 1172 1172 1173 -(% border="2" style="width:500px" %) 1174 -|(% style="width:101px" %)**Command**|(% style="width:397px" %)AT+TRIG1=<interrupt_mode>,<minimum_signal_duration> 1175 -|(% style="width:101px" %)**Response**|(% style="width:397px" %) 1176 -|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)((( 1177 -**interrupt_mode** : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1). 961 +(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1). 1178 1178 1179 -**minimum_signal_duration** : the **minimum signal duration** required for the DI1 port to recognize a valid trigger. 1180 -))) 1181 -|(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 1182 -AT+TRIG1=1,100 963 +(% style="color:red" %)**b :** (%%)delay timing. 1183 1183 1184 -Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms. 1185 -))) 965 +**Example:** AT+TRIG1=1,100(set DI1 port to trigger on high level, valid signal is 100ms ) 1186 1186 1187 -(% class="wikigeneratedid" %) 1188 -(% style="color:#037691" %)**Downlink Payload** 1189 1189 1190 -(% border="2" style="width:500px" %) 1191 -|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix><interrupt_mode><minimum_signal_duration> 1192 -|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)((( 1193 -**prefix** : 09 01 (hexadecimal) 968 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 01 ):** 1194 1194 1195 - **interrupt_mode**:0:fallingedge;1:risingedge,2:fallingandraisingedge (for MOD=1),representedby 1bytein hexadecimal.970 +(% style="color:blue" %)**0x09 01 aa bb cc ** (%%) ~/~/ same as AT+TRIG1=aa,0x(bb cc) 1196 1196 1197 -**minimum_signal_duration** : in milliseconds, represented two bytes in hexadecimal. 1198 -))) 1199 -|(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 1200 -09 01 **01 00 64** 1201 1201 1202 -Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms. 1203 -))) 1204 - 1205 1205 ==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ==== 1206 1206 1207 - 1208 1208 Sets DI2 as a trigger. 1209 1209 1210 -(% style="color:#037691" %)**AT Command** 977 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b** 1211 1211 1212 -(% border="2" style="width:500px" %) 1213 -|(% style="width:94px" %)**Command**|(% style="width:404px" %)AT+TRIG2=<interrupt_mode>,<minimum_signal_duration> 1214 -|(% style="width:94px" %)**Response**|(% style="width:404px" %) 1215 -|(% style="width:94px" %)**Parameters**|(% style="width:404px" %)((( 1216 -**interrupt_mode **: 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1). 979 +(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1). 1217 1217 1218 -**minimum_signal_duration** : the **minimum signal duration** required for the DI1 port to recognize a valid trigger. 1219 -))) 1220 -|(% style="width:94px" %)**Example**|(% style="width:404px" %)((( 1221 -AT+TRIG2=0,100 981 +(% style="color:red" %)**b :** (%%)delay timing. 1222 1222 1223 -Set the DI1 port to trigger on a falling edge; the valid signal duration is 100 ms. 1224 -))) 983 +**Example:** AT+TRIG2=0,100 (set DI1 port to trigger on low level, valid signal is 100ms ) 1225 1225 1226 -(% style="color:#037691" %)**Downlink Payload** 1227 1227 1228 -(% border="2" style="width:500px" %) 1229 -|(% style="width:96px" %)**Payload**|(% style="width:402px" %)<prefix><interrupt_mode><minimum_signal_duration> 1230 -|(% style="width:96px" %)**Parameters**|(% style="width:402px" %)((( 1231 -**prefix** : 09 02 (hexadecimal) 986 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 02 ):** 1232 1232 1233 - **interrupt_mode **:0:fallingedge;1:risingedge,2:fallingand raisingedge (for MOD=1),representedby 1bytein hexadecimal.988 +(% style="color:blue" %)**0x09 02 aa bb cc ** (%%)~/~/ same as AT+TRIG2=aa,0x(bb cc) 1234 1234 1235 -**minimum_signal_duration** : in milliseconds, represented two bytes in hexadecimal 1236 -))) 1237 -|(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64** 1238 1238 1239 1239 ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ==== 1240 1240 993 +Sets the current trigger based on the AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1241 1241 1242 - SetstheurrenttriggerbasedontheAC port. See also[[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]995 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ACLIM** 1243 1243 1244 -(% style="color:#037691" %)** ATCommand**997 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 01 )** 1245 1245 1246 -(% border="2" style="width:500px" %) 1247 -|(% style="width:104px" %)**Command**|(% style="width:394px" %)((( 1248 -AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH> 1249 -))) 1250 -|(% style="width:104px" %)**Response**|(% style="width:394px" %) 1251 -|(% style="width:104px" %)**Parameters**|(% style="width:394px" %)((( 1252 -**AC1_LIMIT_LOW** : lower limit of the current to be checked 999 +(% style="color:blue" %)**0x AA 01 aa bb cc dd ee ff gg hh ** (%%) ~/~/ same as AT+ACLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1253 1253 1254 -**AC1_LIMIT_HIGH **: higher limit of the current to be checked 1255 1255 1256 -**AC2_LIMIT_HIGH **: lower limit of the current to be checked 1257 1257 1258 -**AC2_LIMIT_LOW** : higher limit of the current to be checked 1259 -))) 1260 -|(% style="width:104px" %)**Example**|(% style="width:394px" %)((( 1261 -AT+ACLIM=10000,15000,0,0 1262 - 1263 -Triggers an uplink if AC1 current is lower than 10mA or higher than 15mA 1264 -))) 1265 -|(% style="width:104px" %)Note|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1266 - 1267 -(% style="color:#037691" %)**Downlink Payload** 1268 - 1269 -(% border="2" style="width:500px" %) 1270 -|(% style="width:104px" %)**Payload**|(% style="width:394px" %)<prefix><AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH> 1271 -|(% style="width:104px" %)**Parameters**|(% style="width:394px" %)((( 1272 -**prefix **: AA 01 (hexadecimal) 1273 - 1274 -**AC1_LIMIT_LOW** : lower limit of the current to be checked, two bytes in hexadecimal 1275 - 1276 -**AC1_LIMIT_HIGH **: higher limit of the current to be checked, two bytes in hexadecimal 1277 - 1278 -**AC2_LIMIT_HIGH **: lower limit of the current to be checked, two bytes in hexadecimal 1279 - 1280 -**AC2_LIMIT_LOW** : higher limit of the current to be checked, two bytes in hexadecimal 1281 -))) 1282 -|(% style="width:104px" %)**Example**|(% style="width:394px" %)((( 1283 -AA 01 **27** **10 3A** **98** 00 00 00 00 1284 - 1285 -Triggers an uplink if AC1 current is lower than 10mA or higher than 15mA. Set all values to zero for AC2 limits because we are only checking AC1 limits. 1286 -))) 1287 -|(% style="width:104px" %)Note|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1288 - 1289 1289 ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ==== 1290 1290 1005 +Sets the current trigger based on the AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1291 1291 1292 - Setstheurrenttriggerasedon theAVport.Seealso[[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]1007 +* (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+AVLIM **(%%)** See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]** 1293 1293 1294 -(% style="color:#037691" %)** ATCommand**1009 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 00 )** 1295 1295 1296 -(% border="2" style="width:500px" %) 1297 -|(% style="width:104px" %)**Command**|(% style="width:387px" %)AT+AVLIM= AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH> 1298 -|(% style="width:104px" %)**Response**|(% style="width:387px" %) 1299 -|(% style="width:104px" %)**Parameters**|(% style="width:387px" %)((( 1300 -**AC1_LIMIT_LOW** : lower limit of the current to be checked 1011 +(% style="color:blue" %)**0x AA 00 aa bb cc dd ee ff gg hh ** (%%) ~/~/ same as AT+AVLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1301 1301 1302 -**AC1_LIMIT_HIGH **: higher limit of the current to be checked 1303 1303 1304 - **AC2_LIMIT_HIGH**: lowerlimitof thecurrentto bechecked1014 +==== 3.4.2.11 Trigger – Set minimum interval ==== 1305 1305 1306 -**AC2_LIMIT_LOW** : higher limit of the current to be checked 1307 -))) 1308 -|(% style="width:104px" %)**Example**|(% style="width:387px" %)((( 1309 -AT+AVLIM=3000,6000,0,2000 1016 +Sets AV and AC trigger minimum interval. Device won't response to the second trigger within this set time after the first trigger. 1310 1310 1311 -Triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V 1312 -))) 1313 -|(% style="width:104px" %)**Note**|(% style="width:387px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1018 +* (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+ATDC=5 ** ~/~/ (%%)Device won't response the second trigger within 5 minute after the first trigger. 1314 1314 1315 -(% style="color:#037691" %)**Downlink Payload** 1020 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xAC )** 1316 1316 1317 -(% border="2" style="width:500px" %) 1318 -|(% style="width:104px" %)**Payload**|(% style="width:394px" %)<prefix><AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH> 1319 -|(% style="width:104px" %)**Parameters**|(% style="width:394px" %)((( 1320 -**prefix **: AA 00 (hexadecimal) 1022 +(% style="color:blue" %)**0x AC aa bb **(%%) ~/~/ same as AT+ATDC=0x(aa bb) . Unit (min) 1321 1321 1322 -**AV1_LIMIT_LOW** : lower limit of the voltage to be checked, two bytes in hexadecimal 1323 - 1324 -**AV1_LIMIT_HIGH **: higher limit of the voltage to be checked, two bytes in hexadecimal 1325 - 1326 -**AV2_LIMIT_HIGH **: lower limit of the voltage to be checked, two bytes in hexadecimal 1327 - 1328 -**AV2_LIMIT_LOW** : higher limit of the voltage to be checked, two bytes in hexadecimal 1024 +((( 1025 +(% style="color:red" %)**Note: ATDC setting must be more than 5min** 1329 1329 ))) 1330 -|(% style="width:104px" %)**Example**|(% style="width:394px" %)((( 1331 -AA 00 **0B B8 17 70 00 00 07 D0** 1332 1332 1333 -Triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V. 1334 -))) 1335 -|(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1336 1336 1337 -==== 3.4.2.11 Trigger – Set the minimum interval ==== 1338 1338 1339 - 1340 -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. 1341 - 1342 -(% style="color:#037691" %)**AT Command** 1343 - 1344 -(% border="2" style="width:500px" %) 1345 -|(% style="width:113px" %)**Command**|(% style="width:385px" %)AT+ATDC=<time> 1346 -|(% style="width:113px" %)**Response**|(% style="width:385px" %) 1347 -|(% style="width:113px" %)**Parameters**|(% style="width:385px" %)((( 1348 -**time** : in minutes 1349 -))) 1350 -|(% style="width:113px" %)**Example**|(% style="width:385px" %)((( 1351 -AT+ATDC=5 1352 - 1353 -The device won't respond to the second trigger within 5 minutes after the first trigger. 1354 -))) 1355 -|(% style="width:113px" %)Note|(% style="width:385px" %)(% style="color:red" %)**The time must be greater than 5 minutes.** 1356 - 1357 -(% style="color:#037691" %)**Downlink Payload** 1358 - 1359 -(% border="2" style="width:500px" %) 1360 -|(% style="width:112px" %)**Payload**|(% style="width:386px" %)<prefix><time> 1361 -|(% style="width:112px" %)**Parameters**|(% style="width:386px" %)((( 1362 -**prefix** : AC (hexadecimal) 1363 - 1364 -**time **: in minutes (two bytes in hexadecimal) 1365 -))) 1366 -|(% style="width:112px" %)**Example**|(% style="width:386px" %)((( 1367 -AC **00 05** 1368 - 1369 -The device won't respond to the second trigger within 5 minutes after the first trigger. 1370 -))) 1371 -|(% style="width:112px" %)Note|(% style="width:386px" %)(% style="color:red" %)**The time must be greater than 5 minutes.** 1372 - 1373 1373 ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ==== 1374 1374 1375 - 1376 1376 Controls the digital outputs DO1, DO2, and DO3 1377 1377 1378 -(% style="color:#037691" %)**AT Command** 1034 +* (% style="color:#037691" %)**AT Command** 1379 1379 1380 -There is no AT Command to control theDigital Output.1036 +There is no AT Command to control Digital Output 1381 1381 1382 1382 1383 -(% style="color:#037691" %)**Downlink Payload** 1039 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x02)** 1384 1384 1385 -(% border="2" style="width:500px" %) 1386 -|(% style="width:115px" %)**Payload**|(% style="width:383px" %)<prefix><DO1><DO2><DO3> 1387 -|(% style="width:115px" %)**Parameters**|(% style="width:383px" %)((( 1388 -**prefix** : 02 (hexadecimal) 1041 +(% style="color:blue" %)**0x02 aa bb cc ** (%%)~/~/ Set DO1/DO2/DO3 output 1389 1389 1390 -**DOI** : 01: Low, 00: High, 11: No action (1 byte in hex) 1391 - 1392 -**DO2** : 01: Low, 00: High, 11: No action (1 byte in hex) 1393 - 1394 -**DO3 **: 01: Low, 00: High, 11: No action (1 byte in hex) 1043 +((( 1044 +If payload = 0x02010001, while there is load between V+ and DOx, it means set DO1 to low, DO2 to high and DO3 to low. 1395 1395 ))) 1396 -|(% style="width:115px" %)**Examples**|(% style="width:383px" %)((( 1397 -02 **01 00 01** 1398 1398 1399 -If there is a load between V+ and DOx, it means DO1 is set to low, DO2 is set to high, and DO3 is set to low. 1400 - 1401 -**More examples:** 1402 - 1403 1403 ((( 1404 -01: Low, 00: High, 11: No action 1048 +01: Low, 00: High , 11: No action 1405 1405 1406 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:383px" %)1407 -|(% 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**1408 -| (% style="width:126px" %)02 01 00 11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action1409 -| (% style="width:126px" %)02 00 11 01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low1410 -| (% style="width:126px" %)02 11 01 00|(% style="width:85px" %)No Action|(% style="width:86px" %)Low|(% style="width:86px" %)High1050 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 1051 +|(% 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** 1052 +|02 01 00 11|Low|High|No Action 1053 +|02 00 11 01|High|No Action|Low 1054 +|02 11 01 00|No Action|Low|High 1411 1411 ))) 1412 1412 1413 1413 ((( 1414 -((( 1415 -(% style="color:red" %)**Note: For the LT-22222-L, there is no DO3; the last byte can have any value.** 1058 +(% style="color:red" %)**Note: For LT-22222-L, there is no DO3, the last byte can use any value.** 1416 1416 ))) 1417 1417 1418 1418 ((( 1419 -(% style="color:red" %)** Thedevice will upload a packet if downlink code executes successfully.**1062 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1420 1420 ))) 1421 -))) 1422 -))) 1423 1423 1424 -==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ==== 1425 1425 1426 1426 1427 - (%style="color:#037691"%)**ATcommand**1067 +==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ==== 1428 1428 1429 -There is no AT command to control the digital output. 1430 1430 1070 +* (% style="color:#037691" %)**AT Command** 1431 1431 1432 - (%style="color:#037691"%)**Downlinkpayload**1072 +There is no AT Command to control Digital Output 1433 1433 1434 1434 1435 -(% border="2" style="width:500px" %) 1436 -|(% style="width:116px" %)**Prefix**|(% style="width:382px" %)0xA9 1437 -|(% style="width:116px" %)**Parameters**|(% style="width:382px" %)((( 1438 -**inverter_mode**: 1 byte in hex. 1075 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)** 1439 1439 1440 -**01:** DO pins revert to their original state after the timeout. 1441 -**00:** DO pins switch to an inverted state after the timeout. 1077 +(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Set DO1/DO2/DO3 output with time control 1442 1442 1443 1443 1444 - **DO1_control_method_and_port_status**- 1 byte inhex1080 +This is to control the digital output time of DO pin. Include four bytes: 1445 1445 1446 - 0x01:DO1 set tolow1082 +(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9) 1447 1447 1448 - 0x00:DO1set tohigh1084 +(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode 1449 1449 1450 -0 x11:1NOaction1086 +01: DO pins will change back to original state after timeout. 1451 1451 1088 +00: DO pins will change to an inverter state after timeout 1452 1452 1453 -**DO2_control_method_and_port_status** - 1 byte in hex 1454 1454 1455 - 0x01:DO2 set tolow1091 +(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Ports status: 1456 1456 1457 -0x00 : DO2 set to high 1093 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1094 +|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** 1095 +|0x01|DO1 set to low 1096 +|0x00|DO1 set to high 1097 +|0x11|DO1 NO Action 1458 1458 1459 - 0x11:DO2NOaction1099 +(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Ports status: 1460 1460 1101 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1102 +|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** 1103 +|0x01|DO2 set to low 1104 +|0x00|DO2 set to high 1105 +|0x11|DO2 NO Action 1461 1461 1462 -** DO3_control_method_and_port_status**- 1 byte in hex1107 +(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Ports status: 1463 1463 1464 -0x01 : DO3 set to low 1109 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1110 +|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** 1111 +|0x01|DO3 set to low 1112 +|0x00|DO3 set to high 1113 +|0x11|DO3 NO Action 1465 1465 1466 - 0x00:DO3set tohigh1115 +(% style="color:#4f81bd" %)**Sixth and Seventh and Eighth and Ninth Byte**:(%%) Latching time. Unit: ms 1467 1467 1468 -0x11 : DO3 NO action 1469 1469 1118 +(% style="color:red" %)**Note: ** 1470 1470 1471 - **latching_time**:4inhex1120 + Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes 1472 1472 1473 - (%style="color:red"%)**Note: **1122 + Before Firmwre v1.6.0 the latch time only suport 2 bytes. 1474 1474 1475 - Sincefirmware v1.6.0, the latchtime supports4bytesor2bytes1124 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1476 1476 1477 - Before firmware v1.6.0, the latch time only supported 2 bytes. 1478 1478 1479 -(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.** 1480 -))) 1481 -|(% style="width:116px" %)**Payload format**|(% style="width:382px" %)<prefix><inverter_mode><DO1_control_method_and_port_status><DO2_control_method_and_port_status><DO2_control_method_and_port_status><latching_time> 1482 -|(% style="width:116px" %)**Example**|(% style="width:382px" %)((( 1483 -**A9 01 01 01 01 07 D0** 1127 +**Example payload:** 1484 1484 1485 - DO1pin,DO2pin,andDO3pinwill be set to low, last for 2 seconds, and then revert to their original state.1129 +**~1. A9 01 01 01 01 07 D0** 1486 1486 1131 +DO1 pin & DO2 pin & DO3 pin will be set to Low, last 2 seconds, then change back to original state. 1487 1487 1488 -**A9 01 00 01 11 07 D0** 1133 +**2. A9 01 00 01 11 07 D0** 1489 1489 1490 -DO1 pin issettohigh, DO2 pinissettolow,andDO3 pintakesno action.Thislastsfor2 secondsandthenrevertstotheoriginal state.1135 +DO1 pin set high, DO2 pin set low, DO3 pin no action, last 2 seconds, then change back to original state. 1491 1491 1137 +**3. A9 00 00 00 00 07 D0** 1492 1492 1493 - **A90000000007D0**1139 +DO1 pin & DO2 pin & DO3 pin will be set to high, last 2 seconds, then both change to low. 1494 1494 1495 - DO1pin,DO2pin,andDO3pinwill be set to high, last for 2 seconds, and then all change to low.1141 +**4. A9 00 11 01 00 07 D0** 1496 1496 1143 +DO1 pin no action, DO2 pin set low, DO3 pin set high, last 2 seconds, then DO1 pin no action, DO2 pin set high, DO3 pin set low 1497 1497 1498 -**A9 00 11 01 00 07 D0** 1499 1499 1500 -DO1 pin takes no action, DO2 pin is set to low, and DO3 pin is set to high. This lasts for 2 seconds, after which the DO1 pin takes no action, the DO2 pin is set to high, and the DO3 pin is set to low. 1501 -))) 1502 1502 1503 1503 ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ==== 1504 1504 1505 1505 1506 -(% style="color:#037691" %)**AT Command:** 1150 +* (% style="color:#037691" %)**AT Command:** 1507 1507 1508 -There is no AT Command to control theRelay Output.1152 +There is no AT Command to control Relay Output 1509 1509 1510 1510 1511 -(% style="color:#037691" %)**Downlink Payload** 1155 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x03):** 1512 1512 1513 -(% border="2" style="width:500px" %) 1514 -|(% style="width:113px" %)**Prefix**|(% style="width:384px" %)0x03 1515 -|(% style="width:113px" %)**Parameters**|(% style="width:384px" %)((( 1516 -**RO1_status** : 1 byte in hex 1157 +(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set RO1/RO2 output 1517 1517 1518 -00: Close 1519 1519 1520 -01: Open 1160 +((( 1161 +If payload = 0x030100, it means set RO1 to close and RO2 to open. 1162 +))) 1521 1521 1522 -11: No action 1164 +((( 1165 +00: Closed , 01: Open , 11: No action 1523 1523 1167 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %) 1168 +|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**RO1**|(% style="background-color:#4f81bd; color:white" %)**RO2** 1169 +|03 00 11|Open|No Action 1170 +|03 01 11|Close|No Action 1171 +|03 11 00|No Action|Open 1172 +|03 11 01|No Action|Close 1173 +|03 00 00|Open|Open 1174 +|03 01 01|Close|Close 1175 +|03 01 00|Close|Open 1176 +|03 00 01|Open|Close 1177 +))) 1524 1524 1525 - **RO2_status**:1byte inhex1179 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1526 1526 1527 -00: Close 1528 1528 1529 -01: Open 1530 1530 1531 -11: No action 1532 -))) 1533 -|(% style="width:113px" %)**Payload format**|(% style="width:384px" %)<prefix><RO1_status><RO2_status> 1534 -|(% style="width:113px" %)**Example**|(% style="width:384px" %)((( 1535 -(% border="2" %) 1536 -|=Payload|=RO1|=RO2 1537 -|03 00 11|Open|No action 1538 -|03 01 11|Close|No action 1539 -|03 11 00|No action|Open 1540 -|03 11 10|No action|Close 1541 -|03 00 00|Open|Open 1542 -|03 01 01|Close|Close 1543 -|03 01 00|Close|Open 1544 -|03 00 01|Open|Close 1545 - 1546 -(% style="color:red" %)**The device will transmit an uplink packet if the downlink payload is executed successfully.** 1547 -))) 1548 - 1549 1549 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== 1550 1550 1551 1551 1552 - Controlstherelayoutputtime.1186 +* (% style="color:#037691" %)**AT Command:** 1553 1553 1188 +There is no AT Command to control Relay Output 1554 1554 1555 -(% style="color:#037691" %)**AT Command:** 1556 1556 1557 - Thereisno AT Commandtocontrolthe RelayOutput1191 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x05):** 1558 1558 1193 +(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set RO1/RO2 relay with time control 1559 1559 1560 -(% style="color:#037691" %)**Downlink Payload (prefix 0x05):** 1561 1561 1562 - (%style="color:blue"%)**0x05 aa bb cc dd ** (%%)~/~/ SetsRO1/RO2relayswithtimecontrol1196 +This is to control the relay output time of relay. Include four bytes: 1563 1563 1198 +(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05) 1564 1564 1565 - Thiscontrolstherelayoutput timendincludes 4 bytes:1200 +(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode 1566 1566 1567 - (%style="color:#4f81bd" %)**Firstbyte**(%%)**:** Typecode(0x05)1202 +01: Relays will change back to original state after timeout. 1568 1568 1569 - (%style="color:#4f81bd"%)**Secondbyte(aa)**(%%):InverterMode1204 +00: Relays will change to an inverter state after timeout 1570 1570 1571 -01: Relays will change back to their original state after a timeout. 1572 1572 1573 - 00:Relayswillchange to theinverterstate after a timeout.1207 +(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status: 1574 1574 1575 - 1576 -(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status: 1577 - 1578 1578 [[image:image-20221008095908-1.png||height="364" width="564"]] 1579 1579 1580 1580 1581 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes1212 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms 1582 1582 1583 1583 1584 1584 (% style="color:red" %)**Note:** 1585 1585 1586 - Since firmware v1.6.0, the latch time supportsboth4 bytes and 2 bytes.1217 + Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes 1587 1587 1588 - Before firmware v1.6.0,the latch time only supported2 bytes.1219 + Before Firmwre v1.6.0 the latch time only suport 2 bytes. 1589 1589 1590 1590 1591 -(% style="color:red" %)** Thedevice will uplinka packet ifthedownlink code executes successfully.**1222 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1592 1592 1593 1593 1594 1594 **Example payload:** ... ... @@ -1595,19 +1595,19 @@ 1595 1595 1596 1596 **~1. 05 01 11 07 D0** 1597 1597 1598 -Relay1 and Relay2 will be set to NC, last ing2 seconds, thenreverttotheiroriginal state1229 +Relay1 and Relay 2 will be set to NC , last 2 seconds, then change back to original state. 1599 1599 1600 1600 **2. 05 01 10 07 D0** 1601 1601 1602 -Relay1 will change to NC, Relay2 will change to NO, last ing2 seconds,andthen bothwill reverttotheiroriginal state.1233 +Relay1 will change to NC, Relay2 will change to NO, last 2 seconds, then both change back to original state. 1603 1603 1604 1604 **3. 05 00 01 07 D0** 1605 1605 1606 -Relay1 will change to NO, Relay2 will change to NC, last ing2 seconds, thenRelay1willchange to NC,andRelay2willchange to NO.1237 +Relay1 will change to NO, Relay2 will change to NC, last 2 seconds, then relay change to NC,Relay2 change to NO. 1607 1607 1608 1608 **4. 05 00 00 07 D0** 1609 1609 1610 -Relay1 andRelay2 will change to NO, lasting2 seconds, then bothwillchange to NC.1241 +Relay 1 & relay2 will change to NO, last 2 seconds, then both change to NC. 1611 1611 1612 1612 1613 1613 ... ... @@ -1614,397 +1614,158 @@ 1614 1614 ==== 3.4.2.16 Counting ~-~- Voltage threshold counting ==== 1615 1615 1616 1616 1617 -When thevoltage exceedsthe threshold, counting begins. For details,see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]1248 +When voltage exceed the threshold, count. Feature see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1618 1618 1619 -(% style="color:#037691" %)**AT Command** 1250 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1620 1620 1621 -(% border="2" style="width:500px" %) 1622 -|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage>,<logic> 1623 -|(% style="width:137px" %)**Response**|(% style="width:361px" %) 1624 -|(% style="width:137px" %)**Parameters**|(% style="width:361px" %)((( 1625 -**voltage** : voltage threshold in mV 1252 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):** 1626 1626 1627 - **logic**:1254 +(% style="color:blue" %)**0xA5 aa bb cc ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc 1628 1628 1629 -**0** : lower than 1630 1630 1631 -**1**: higher than 1632 1632 1633 -if you leave the logic parameter blank, it is considered 0 1634 -))) 1635 -|(% style="width:137px" %)**Examples**|(% style="width:361px" %)((( 1636 -AT+VOLMAX=20000 1637 - 1638 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1639 - 1640 -AT+VOLMAX=20000,0 1641 - 1642 -If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1 1643 - 1644 -AT+VOLMAX=20000,1 1645 - 1646 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1647 -))) 1648 - 1649 -(% style="color:#037691" %)**Downlink Payload** 1650 - 1651 -(% border="2" style="width:500px" %) 1652 -|(% style="width:140px" %)**Payload**|(% style="width:358px" %)<prefix><voltage><logic> 1653 -|(% style="width:140px" %)**Parameters**|(% style="width:358px" %)((( 1654 -**prefix** : A5 (hex) 1655 - 1656 -**voltage** : voltage threshold in mV (2 bytes in hex) 1657 - 1658 -**logic**: (1 byte in hexadecimal) 1659 - 1660 -**0** : lower than 1661 - 1662 -**1**: higher than 1663 - 1664 -if you leave the logic parameter blank, it is considered 1 (higher than) 1665 -))) 1666 -|(% style="width:140px" %)**Example**|(% style="width:358px" %)((( 1667 -A5 **4E 20** 1668 - 1669 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1670 - 1671 -A5 **4E 20 00** 1672 - 1673 -If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1 1674 - 1675 -A5 **4E 20 01** 1676 - 1677 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1678 -))) 1679 - 1680 1680 ==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ==== 1681 1681 1682 -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. 1683 1683 1684 -(% style="color:#037691" %)**AT Command** 1261 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) ** 1685 1685 1686 -(% border="2" style="width:500px" %) 1687 -|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter>,<number> 1688 -|(% style="width:134px" %)**Response**|(% style="width:364px" %) 1689 -|(% style="width:134px" %)**Parameters**|(% style="width:364px" %)((( 1690 -**counting_parameter** : 1263 +(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count 1691 1691 1692 - 1:COUNT11265 +(% style="color:red" %)**bb cc dd ee: **(%%)number to be set 1693 1693 1694 -2: COUNT2 1695 1695 1696 - 3:AVI1Count1268 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):** 1697 1697 1698 -**number** : Start number 1699 -))) 1700 -|(% style="width:134px" %)**Example**|(% style="width:364px" %)((( 1701 -AT+SETCNT=1,10 1270 +(% style="color:blue" %)**0x A8 aa bb cc dd ee ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee) 1702 1702 1703 -Sets the COUNT1 to 10. 1704 -))) 1705 1705 1706 -(% style="color:#037691" %)**Downlink Payload** 1707 1707 1708 -(% border="2" style="width:500px" %) 1709 -|(% style="width:135px" %)**Payload**|(% style="width:363px" %)<prefix><counting_parameter><number> 1710 -|(% style="width:135px" %)**Parameters**|(% style="width:363px" %)((( 1711 -prefix : A8 (hex) 1712 - 1713 -**counting_parameter** : (1 byte in hexadecimal) 1714 - 1715 -1: COUNT1 1716 - 1717 -2: COUNT2 1718 - 1719 -3: AVI1 Count 1720 - 1721 -**number** : Start number, 4 bytes in hexadecimal 1722 -))) 1723 -|(% style="width:135px" %)**Example**|(% style="width:363px" %)((( 1724 -A8 **01 00 00 00 0A** 1725 - 1726 -Sets the COUNT1 to 10. 1727 -))) 1728 - 1729 1729 ==== 3.4.2.18 Counting ~-~- Clear Counting ==== 1730 1730 1731 -This command clears the counting in counting mode. 1732 1732 1733 - (% style="color:#037691"%)**AT Command**1277 +Clear counting for counting mode 1734 1734 1735 -(% border="2" style="width:500px" %) 1736 -|(% style="width:142px" %)**Command**|(% style="width:356px" %)AT+CLRCOUNT 1737 -|(% style="width:142px" %)**Response**|(% style="width:356px" %)- 1279 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT **(%%) ~/~/ clear all counting 1738 1738 1739 -(% style="color:#037691" %)**Downlink Payload** 1281 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):** 1740 1740 1741 -(% border="2" style="width:500px" %) 1742 -|(% style="width:141px" %)**Payload**|(% style="width:357px" %)<prefix><clear?> 1743 -|(% style="width:141px" %)**Parameters**|(% style="width:357px" %)((( 1744 -prefix : A6 (hex) 1283 +(% style="color:blue" %)**0x A6 01 ** (%%)~/~/ clear all counting 1745 1745 1746 -clear? : 01 (hex) 1747 -))) 1748 -|(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01** 1749 1749 1750 -==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ==== 1751 1751 1287 +==== 3.4.2.19 Counting ~-~- Change counting mode to save time ==== 1752 1752 1753 -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. 1754 1754 1755 -(% style="color:#037691" %)**AT Command** 1290 +* (% style="color:#037691" %)**AT Command:** 1756 1756 1757 -(% border="2" style="width:500px" %) 1758 -|(% style="width:124px" %)**Command**|(% style="width:374px" %)AT+COUTIME=<time> 1759 -|(% style="width:124px" %)**Response**|(% style="width:374px" %) 1760 -|(% style="width:124px" %)**Parameters**|(% style="width:374px" %)time : seconds (0 to 16777215) 1761 -|(% style="width:124px" %)**Example**|(% style="width:374px" %)((( 1762 -AT+COUTIME=60 1292 +(% style="color:blue" %)**AT+COUTIME=60 **(%%)~/~/ Set save time to 60 seconds. Device will save the counting result in internal flash every 60 seconds. (min value: 30) 1763 1763 1764 -Sets the device to save its counting results to the memory every 60 seconds. 1765 -))) 1766 1766 1767 -(% style="color:#037691" %)**Downlink Payload** 1295 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):** 1768 1768 1769 -(% border="2" style="width:500px" %) 1770 -|(% style="width:123px" %)**Payload**|(% style="width:375px" %)<prefix><time> 1771 -|(% style="width:123px" %)**Parameters**|(% style="width:375px" %)((( 1772 -prefix : A7 1297 +(% style="color:blue" %)**0x A7 aa bb cc ** (%%)~/~/ same as AT+COUTIME =aa bb cc, 1773 1773 1774 -time : seconds, 3 bytes in hexadecimal 1299 +((( 1300 +range: aa bb cc:0 to 16777215, (unit:second) 1775 1775 ))) 1776 -|(% style="width:123px" %)**Example**|(% style="width:375px" %)((( 1777 -A7 **00 00 3C** 1778 1778 1779 -Sets the device to save its counting results to the memory every 60 seconds. 1780 -))) 1781 1781 1782 -==== 3.4.2.20 Reset saved RO and DO states ==== 1783 1783 1305 +==== 3.4.2.20 Reset save RO DO state ==== 1784 1784 1785 -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. 1786 1786 1787 -(% style="color:#037691" %)**AT Command** 1308 +* (% style="color:#037691" %)**AT Command:** 1788 1788 1789 -(% border="2" style="width:500px" %) 1790 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state> 1791 -|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1792 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1793 -**state** : 1310 +(% style="color:blue" %)**AT+RODORESET=1 **(%%)~/~/ RODO will close when the device joining the network. (default) 1794 1794 1795 -**0** :RODOwillclosewhen the devicejoinsthe network.(default)1312 +(% style="color:blue" %)**AT+RODORESET=0 **(%%)~/~/ After the device is reset, the previously saved RODO state (only MOD2 to MOD5) is read, and its state is not changed when it is reconnected to the network. 1796 1796 1797 -**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. 1798 -))) 1799 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1800 -(% style="color:blue" %)**AT+RODORESET=1 ** 1801 1801 1802 - RODOwillclosewhenthe device joinsthe network.(default)1315 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):** 1803 1803 1804 -(% style="color:blue" %)**AT+RODORE SET=0**1317 +(% style="color:blue" %)**0x AD aa ** (%%)~/~/ same as AT+RODORET =aa 1805 1805 1806 -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. 1807 -))) 1808 1808 1809 -(% style="color:#037691" %)**Downlink Payload** 1810 1810 1811 -(% border="2" style="width:500px" %) 1812 -|(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state> 1813 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1814 -**prefix** : AD 1815 - 1816 -**state** : 1817 - 1818 -**0** : RODO will close when the device joins the network. (default), represents as 1 byte in hexadecimal. 1819 - 1820 -**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 1821 -))) 1822 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1823 -AD **01** 1824 - 1825 -RODO will close when the device joins the network. (default) 1826 - 1827 -AD **00** 1828 - 1829 -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. 1830 -))) 1831 - 1832 1832 ==== 3.4.2.21 Encrypted payload ==== 1833 1833 1834 1834 1835 - Thiscommandallowsyouto 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 eitheruploadencrypted dataor transmit it without encryption.1324 +* (% style="color:#037691" %)**AT Command:** 1836 1836 1837 -(% style="color: #037691" %)**ATmmand:**1326 +(% style="color:blue" %)**AT+DECRYPT=1 ** (%%)~/~/ The payload is uploaded without encryption 1838 1838 1839 -(% border="2" style="width:500px" %) 1840 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state> 1841 -|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1842 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1843 -**state** : 1328 +(% style="color:blue" %)**AT+DECRYPT=0 **(%%)~/~/ Encrypt when uploading payload (default) 1844 1844 1845 -**1** : The payload is uploaded without encryption 1846 1846 1847 -**0** : The payload is encrypted when uploaded (default) 1848 -))) 1849 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1850 -AT+DECRYPT=1 1851 1851 1852 -The payload is uploaded without encryption 1853 - 1854 -AT+DECRYPT=0 1855 - 1856 -The payload is encrypted when uploaded (default) 1857 -))) 1858 - 1859 -There is no downlink payload for this configuration. 1860 - 1861 - 1862 1862 ==== 3.4.2.22 Get sensor value ==== 1863 1863 1864 1864 1865 - Thiscommandallowsyouto retrieve and optionallyuplink sensorreadingsthrough the serial port.1335 +* (% style="color:#037691" %)**AT Command:** 1866 1866 1867 -(% style="color: #037691" %)**ATCommand**1337 +(% style="color:blue" %)**AT+GETSENSORVALUE=0 **(%%)~/~/ The serial port gets the reading of the current sensor 1868 1868 1869 -(% border="2" style="width:500px" %) 1870 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state> 1871 -|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1872 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1873 -**state** : 1339 +(% style="color:blue" %)**AT+GETSENSORVALUE=1 **(%%)~/~/ The serial port gets the current sensor reading and uploads it. 1874 1874 1875 -**0 **: Retrieves the current sensor reading via the serial port. 1876 1876 1877 -**1 **: Retrieves and uploads the current sensor reading via the serial port. 1878 -))) 1879 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1880 -AT+GETSENSORVALUE=0 1881 1881 1882 -Re trieves thecurrent sensor readingviatheserial port.1343 +==== 3.4.2.23 Resets the downlink packet count ==== 1883 1883 1884 -AT+GETSENSORVALUE=1 1885 1885 1886 -Retrieves and uplinks the current sensor reading via the serial port. 1887 -))) 1346 +* (% style="color:#037691" %)**AT Command:** 1888 1888 1889 -There is no downlink pa yloadfor thisconfiguration.1348 +(% style="color:blue" %)**AT+DISFCNTCHECK=0 **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node will no longer receive downlink packets (default) 1890 1890 1350 +(% 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. 1891 1891 1892 -==== 3.4.2.23 Resetting the downlink packet count ==== 1893 1893 1894 1894 1895 -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. 1896 - 1897 -(% style="color:#037691" %)**AT Command** 1898 - 1899 -(% border="2" style="width:500px" %) 1900 -|(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state> 1901 -|(% style="width:130px" %)**Response**|(% style="width:368px" %)((( 1902 - 1903 -))) 1904 -|(% style="width:130px" %)**Parameters**|(% style="width:368px" %)((( 1905 -**state **: 1906 - 1907 -**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). 1908 - 1909 - 1910 -**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. 1911 -))) 1912 -|(% style="width:130px" %)**Example**|(% style="width:368px" %)((( 1913 -AT+DISFCNTCHECK=0 1914 - 1915 -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). 1916 - 1917 -AT+DISFCNTCHECK=1 1918 - 1919 -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. 1920 -))) 1921 - 1922 -There is no downlink payload for this configuration. 1923 - 1924 - 1925 1925 ==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ==== 1926 1926 1927 1927 1928 - Thiscommand controls the behavior of the node when the combined size of the MAC commands(MACANS)from theserver andthe payloadexceed the allowed bytelimit forthe current data rate (DR).Thecommandprovides 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.1357 +* (% style="color:#037691" %)**AT Command:** 1929 1929 1930 -(% style="color: #037691" %)**AT Command**1359 +(% style="color:blue" %)**AT+DISMACANS=0** (%%) ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of 11 bytes (DR0 of US915, DR2 of AS923, DR2 of AU195), the node will send a packet with a payload of 00 and a port of 4. (default) 1931 1931 1932 -(% border="2" style="width:500px" %) 1933 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DISMACANS=<state> 1934 -|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1935 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1936 -**state** : 1361 +(% 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. 1937 1937 1938 -**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) 1939 1939 1940 -**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. 1941 -))) 1942 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1943 -AT+DISMACANS=0 1364 +* (% style="color:#037691" %)**Downlink Payload **(%%)**:** 1944 1944 1945 - Whenthembined sizeof the MACANS from the server and the payloadexceedsthe byte limit (11bytes for DR0of US915,DR2ofAS923,DR2ofAU915),thenodesendsapacketwith a payload of00 anda portof 4. (default)1366 +(% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set the DISMACANS=1 1946 1946 1947 -AT+DISMACANS=1 1948 1948 1949 -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. 1950 -))) 1951 1951 1952 -(% style="color:#037691" %)**Downlink Payload** 1953 - 1954 -(% border="2" style="width:500px" %) 1955 -|(% style="width:126px" %)**Payload**|(% style="width:372px" %)<prefix><state> 1956 -|(% style="width:126px" %)**Parameters**|(% style="width:372px" %)((( 1957 -**prefix** : 21 1958 - 1959 -**state** : (2 bytes in hexadecimal) 1960 - 1961 -**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) 1962 - 1963 -**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. 1964 -))) 1965 -|(% style="width:126px" %)**Example**|(% style="width:372px" %)((( 1966 -21 **00 01** 1967 - 1968 -Set DISMACANS=1 1969 -))) 1970 - 1971 1971 ==== 3.4.2.25 Copy downlink to uplink ==== 1972 1972 1973 1973 1974 - Thiscommandenableshe device to immediatelyuplink thepayload of a received downlink packet back tothe server.Thecommandallows for quick data replication from downlink to uplink, with a fixed port number of 100.1373 +* (% style="color:#037691" %)**AT Command**(%%)**:** 1975 1975 1976 -(% style="color: #037691" %)**ATCommand**(%%)**:**1375 +(% style="color:blue" %)**AT+RPL=5** (%%) ~/~/ After receiving the package from the server, it will immediately upload the content of the package to the server, the port number is 100. 1977 1977 1978 - (% style="color:blue" %)**AT+RPL=5**(%%)~/~/Afterreceivingadownlink payloadfromtherver,thedevice will immediately uplinkthe payloadback to the serverusingportnumber100.1377 +Example:**aa xx xx xx xx** ~/~/ aa indicates whether the configuration has changed, 00 is yes, 01 is no; xx xx xx xx are the bytes sent. 1979 1979 1980 -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. 1981 1981 1982 - 1983 1983 [[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"]] 1984 1984 1985 1985 For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77. 1986 1986 1384 + 1385 + 1987 1987 [[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"]] 1988 1988 1989 1989 For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. 1990 1990 1991 1991 1992 -(% style="color:#037691" %)**Downlink Payload**(%%)**:** 1993 1993 1994 - Thereisno downlinkoptionavailableforthisfeature.1392 +==== 3.4.2.26 Query version number and frequency band 、TDC ==== 1995 1995 1996 1996 1997 -==== 3.4.2.26 Query firmware version, frequency band, subband, and TDC time ==== 1998 - 1999 - 2000 -This command is used to query key information about the device, including its firmware version, frequency band, subband, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device. 2001 - 2002 2002 * ((( 2003 2003 (% style="color:#037691" %)**Downlink Payload**(%%)**:** 2004 2004 2005 -(% style="color:blue" %)**26 01 ** (%%) ~/~/ The downlinkpayload26 01isusedtoquerythedevice'sfirmwareversion, frequency band, subband,andTDC time.1398 +(% style="color:blue" %)**26 01 ** (%%) ~/~/ Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time. 2006 2006 2007 - 2008 2008 2009 2009 ))) 2010 2010 ... ... @@ -2015,13 +2015,10 @@ 2015 2015 2016 2016 == 3.5 Integrating with ThingsEye.io == 2017 2017 2018 - 2019 2019 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. 2020 2020 2021 - 2022 2022 === 3.5.1 Configuring The Things Stack === 2023 2023 2024 - 2025 2025 We use The Things Stack Sandbox in this example: 2026 2026 2027 2027 * In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added. ... ... @@ -2033,19 +2033,15 @@ 2033 2033 The username and password (API key) you created here are required in the next section. 2034 2034 {{/info}} 2035 2035 2036 -[[image:tts-mqtt-integration.png]] 1425 +[[image:tts-mqtt-integration.png||height="625" width="1000"]] 2037 2037 2038 - 2039 2039 === 3.5.2 Configuring ThingsEye.io === 2040 2040 2041 - 2042 -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. 2043 - 2044 2044 * Login to your [[ThingsEye.io >>https://thingseye.io]]account. 2045 2045 * Under the **Integrations center**, click **Integrations**. 2046 2046 * Click the **Add integration** button (the button with the **+** symbol). 2047 2047 2048 -[[image:thingseye-io-step-1.png]] 1433 +[[image:thingseye-io-step-1.png||height="625" width="1000"]] 2049 2049 2050 2050 2051 2051 On the **Add integration** window, configure the following: ... ... @@ -2057,10 +2057,10 @@ 2057 2057 * Ensure the following options are turned on. 2058 2058 ** Enable integration 2059 2059 ** Debug mode 2060 -** Allow creat ingdevices or assets1445 +** Allow create devices or assets 2061 2061 * Click the **Next** button. you will be navigated to the **Uplink data converter** tab. 2062 2062 2063 -[[image:thingseye-io-step-2.png]] 1448 +[[image:thingseye-io-step-2.png||height="625" width="1000"]] 2064 2064 2065 2065 2066 2066 **Uplink data converter:** ... ... @@ -2071,7 +2071,7 @@ 2071 2071 * 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]]. 2072 2072 * Click the **Next** button. You will be navigated to the **Downlink data converter **tab. 2073 2073 2074 -[[image:thingseye-io-step-3.png]] 1459 +[[image:thingseye-io-step-3.png||height="625" width="1000"]] 2075 2075 2076 2076 2077 2077 **Downlink data converter (this is an optional step):** ... ... @@ -2082,7 +2082,7 @@ 2082 2082 * 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]]. 2083 2083 * Click the **Next** button. You will be navigated to the **Connection** tab. 2084 2084 2085 -[[image:thingseye-io-step-4.png]] 1470 +[[image:thingseye-io-step-4.png||height="625" width="1000"]] 2086 2086 2087 2087 2088 2088 **Connection:** ... ... @@ -2089,7 +2089,7 @@ 2089 2089 2090 2090 * Choose **Region** from the **Host type**. 2091 2091 * 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/...). 2092 -* 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.1Configuring The Things Stack**).1477 +* 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). 2093 2093 * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**. 2094 2094 2095 2095 [[image:message-1.png]] ... ... @@ -2097,73 +2097,59 @@ 2097 2097 2098 2098 * Click the **Add** button. 2099 2099 2100 -[[image:thingseye-io-step-5.png]] 1485 +[[image:thingseye-io-step-5.png||height="625" width="1000"]] 2101 2101 2102 2102 2103 -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.1488 +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. 2104 2104 2105 2105 2106 -[[image:thingseye.io_integrationsCenter_integrations.png]] 1491 +[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]] 2107 2107 2108 2108 2109 - ==== 3.5.2.1Viewing integration details====1494 +**Viewing integration details**: 2110 2110 2111 - 2112 2112 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. 2113 2113 2114 -[[image:integration-details.png]] 1498 +[[image:integration-details.png||height="686" width="1000"]] 2115 2115 2116 2116 2117 2117 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. 2118 2118 2119 2119 {{info}} 2120 -See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].1504 +See also ThingsEye documentation. 2121 2121 {{/info}} 2122 2122 1507 +**Viewing events:** 2123 2123 2124 -==== 3.5.2.2 Viewing events ==== 2125 - 2126 - 2127 2127 The **Events **tab displays all the uplink messages from the LT-22222-L. 2128 2128 2129 2129 * Select **Debug **from the **Event type** dropdown. 2130 2130 * Select the** time frame** from the **time window**. 2131 2131 2132 -[[image:thingseye-events.png]] 1514 +[[image:thingseye-events.png||height="686" width="1000"]] 2133 2133 2134 2134 2135 -* To view the **JSON payload**of a message, click on the**three dots (...)**in the**Message**column of the desired message.1517 +* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message. 2136 2136 2137 -[[image:thingseye-json.png]] 1519 +[[image:thingseye-json.png||width="1000"]] 2138 2138 2139 2139 2140 - ==== 3.5.2.3Deletinganintegration====1522 +**Deleting the integration**: 2141 2141 1524 +If you want to delete this integration, click the **Delete integratio**n button. 2142 2142 2143 -If you want to delete an integration, click the **Delete integratio**n button on the Integrations page. 2144 2144 2145 - 2146 -==== 3.5.2.4 Viewing sensor data on a dashboard ==== 2147 - 2148 - 2149 -You can create a dashboard with ThingsEye to visualize the sensor data coming from the LT-22222-L. The following image shows a dashboard created for the LT-22222-L. See **Creating a dashboard** in ThingsEye documentation for more information. 2150 - 2151 - 2152 - 2153 -[[image:lt-22222-l-dashboard.png]] 2154 - 2155 - 2156 2156 == 3.6 Interface Details == 2157 2157 2158 -=== 3.6.1 Digital Input Port s: DI1/DI2/DI3 (For LT-33222-L,LowActive) ===1529 +=== 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) === 2159 2159 2160 2160 2161 -Support s**NPN-type**sensors.1532 +Support NPN-type sensor 2162 2162 2163 2163 [[image:1653356991268-289.png]] 2164 2164 2165 2165 2166 -=== 3.6.2 Digital Input Ports: DI1/DI2 === 1537 +=== 3.6.2 Digital Input Ports: DI1/DI2 ( For LT-22222-L) === 2167 2167 2168 2168 2169 2169 ((( ... ... @@ -2280,20 +2280,20 @@ 2280 2280 ))) 2281 2281 2282 2282 2283 -(% style="color:blue" %)**Example aDry Contact sensor1654 +(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor 2284 2284 2285 -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.1656 +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. 2286 2286 2287 -To detect a Dry Contact, you can supply a power source to one of thepinsof the Dry Contact.Areference circuit diagramis shown below.1658 +To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram. 2288 2288 2289 2289 [[image:image-20230616235145-1.png]] 2290 2290 2291 -(% style="color:blue" %)**Example 1662 +(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector 2292 2292 2293 2293 [[image:image-20240219115718-1.png]] 2294 2294 2295 2295 2296 -=== 3.6.3 Digital Output Ports: DO1/DO2 === 1667 +=== 3.6.3 Digital Output Ports: DO1/DO2 /DO3 === 2297 2297 2298 2298 2299 2299 (% style="color:blue" %)**NPN output**(%%): GND or Float. The maximum voltage that can be applied to the output pin is 36V. ... ... @@ -2364,21 +2364,20 @@ 2364 2364 [[image:image-20220524100215-10.png||height="382" width="723"]] 2365 2365 2366 2366 2367 -== 3.7 LED Indicators == 1738 +== 3.7 LEDs Indicators == 2368 2368 1740 +The table below lists the behavior of LED indicators for each port function. 2369 2369 2370 -The table below lists the behaviour of LED indicators for each port function. 2371 - 2372 2372 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) 2373 2373 |(% style="background-color:#4f81bd; color:white; width:50px" %)**LEDs**|(% style="background-color:#4f81bd; color:white; width:460px" %)**Feature** 2374 2374 |**PWR**|Always on when there is power 2375 2375 |**TX**|((( 2376 2376 ((( 2377 -Device boot ing: TX blinks 5 times.1747 +Device boot: TX blinks 5 times. 2378 2378 ))) 2379 2379 2380 2380 ((( 2381 -Successful network join s: TX remains ON for 5 seconds.1751 +Successful network join: TX remains ON for 5 seconds. 2382 2382 ))) 2383 2383 2384 2384 ((( ... ... @@ -2399,22 +2399,17 @@ 2399 2399 2400 2400 = 4. Using AT Commands = 2401 2401 2402 - 2403 2403 The LT-22222-L supports programming using AT Commands. 2404 2404 2405 - 2406 2406 == 4.1 Connecting the LT-22222-L to a PC == 2407 2407 2408 - 2409 2409 ((( 2410 -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. 2411 - 2412 -[[image:usb-ttl-audio-jack-connection.jpg]] 2413 - 2414 - 1777 +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. 2415 2415 ))) 2416 2416 1780 +[[image:1653358238933-385.png]] 2417 2417 1782 + 2418 2418 ((( 2419 2419 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: 2420 2420 ))) ... ... @@ -2425,61 +2425,58 @@ 2425 2425 ((( 2426 2426 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/]] 2427 2427 2428 - 2429 2429 == 4.2 LT-22222-L related AT commands == 2430 - 2431 - 2432 2432 ))) 2433 2433 2434 2434 ((( 2435 2435 The following is the list of all the AT commands related to the LT-22222-L, except for those used for switching between working modes. 2436 2436 2437 -* **##AT##+<CMD>?**: Help on <CMD>2438 -* **##AT##+<CMD>**: Run <CMD>2439 -* **##AT##+<CMD>=<value>**: Set the value2440 -* **##AT##+<CMD>=?**: Get the value2441 -* ##**ATZ**##: Trigger a reset of the MCU1799 +* AT+<CMD>? : Help on <CMD> 1800 +* AT+<CMD> : Run <CMD> 1801 +* AT+<CMD>=<value> : Set the value 1802 +* AT+<CMD>=? : Get the value 1803 +* ATZ: Trigger a reset of the MCU 2442 2442 * ##**AT+FDR**##: Reset Parameters to factory default, reserve keys 2443 2443 * **##AT+DEUI##**: Get or set the Device EUI (DevEUI) 2444 2444 * **##AT+DADDR##**: Get or set the Device Address (DevAddr) 2445 2445 * **##AT+APPKEY##**: Get or set the Application Key (AppKey) 2446 -* ##**AT+NWKSKEY**##: Get or set the Network Session Key (NwkSKey)2447 -* **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)2448 -* **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)2449 -* **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)2450 -* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)2451 -* **##AT+DR##**: Get or set the Data Rate. (0-7 corresponding to DR_X)2452 -* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing2453 -* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)2454 -* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency2455 -* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)2456 -* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms2457 -* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms2458 -* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms2459 -* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms2460 -* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)2461 -* ##**AT+NWKID**##: Get or set the Network ID2462 -* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)2463 -* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)2464 -* ##**AT+CLASS**##: Get or set the Device Class2465 -* ##**AT+JOIN**##: JoinNetwork2466 -* ##**AT+NJS**##: Get OTAA Join Status2467 -* ##**AT+SENDB**##: Send hexadecimal data along with the application port2468 -* ##**AT+SEND**##: Send text data along with the application port2469 -* ##**AT+RECVB**##: Printthelast received data in binary format (with hexadecimal values)2470 -* ##**AT+RECV**##: Printthelast received data in raw format2471 -* ##**AT+VER**##: Getthecurrent image version and Frequency Band2472 -* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)2473 -* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)2474 -* ##**AT+SNR**##: Get the SNR of the last received packet2475 -* ##**AT+RSSI**##: Get the RSSI of the last received packet2476 -* ##**AT+TDC**##: Get or set the application data transmission interval in ms2477 -* ##**AT+PORT**##: Get or set the application port2478 -* ##**AT+DISAT**##: Disable AT commands2479 -* ##**AT+PWORD**##: Set password, max 9 digits2480 -* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode2481 -* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN4702482 -* ##**AT+CFG**##: Print all settings1808 +* AT+NWKSKEY: Get or set the Network Session Key (NwkSKey) 1809 +* AT+APPSKEY: Get or set the Application Session Key (AppSKey) 1810 +* AT+APPEUI: Get or set the Application EUI (AppEUI) 1811 +* AT+ADR: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON) 1812 +* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification) 1813 +* AT+DR: Get or set the Data Rate. (0-7 corresponding to DR_X) 1814 +* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing 1815 +* AT+PNM: Get or set the public network mode. (0: off, 1: on) 1816 +* AT+RX2FQ: Get or set the Rx2 window frequency 1817 +* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X) 1818 +* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms 1819 +* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms 1820 +* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms 1821 +* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms 1822 +* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA) 1823 +* AT+NWKID: Get or set the Network ID 1824 +* AT+FCU: Get or set the Frame Counter Uplink (FCntUp) 1825 +* AT+FCD: Get or set the Frame Counter Downlink (FCntDown) 1826 +* AT+CLASS: Get or set the Device Class 1827 +* AT+JOIN: Join network 1828 +* AT+NJS: Get OTAA Join Status 1829 +* AT+SENDB: Send hexadecimal data along with the application port 1830 +* AT+SEND: Send text data along with the application port 1831 +* AT+RECVB: Print last received data in binary format (with hexadecimal values) 1832 +* AT+RECV: Print last received data in raw format 1833 +* AT+VER: Get current image version and Frequency Band 1834 +* AT+CFM: Get or Set the confirmation mode (0-1) 1835 +* AT+CFS: Get confirmation status of the last AT+SEND (0-1) 1836 +* AT+SNR: Get the SNR of the last received packet 1837 +* AT+RSSI: Get the RSSI of the last received packet 1838 +* AT+TDC: Get or set the application data transmission interval in ms 1839 +* AT+PORT: Get or set the application port 1840 +* AT+DISAT: Disable AT commands 1841 +* AT+PWORD: Set password, max 9 digits 1842 +* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode 1843 +* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470 1844 +* AT+CFG: Print all settings 2483 2483 ))) 2484 2484 2485 2485 ... ... @@ -2496,7 +2496,7 @@ 2496 2496 ))) 2497 2497 2498 2498 ((( 2499 -(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT command access**## 1861 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**## 2500 2500 ))) 2501 2501 2502 2502 ((( ... ... @@ -2504,7 +2504,7 @@ 2504 2504 ))) 2505 2505 2506 2506 ((( 2507 -(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT command access**## 1869 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**## 2508 2508 ))) 2509 2509 2510 2510 ((( ... ... @@ -2535,7 +2535,7 @@ 2535 2535 2536 2536 2537 2537 ((( 2538 -(% style="background-color:#dcdcdc" %)**123456**(%%) ~/~/ Enter thepassword to enable AT commands access1900 +(% style="background-color:#dcdcdc" %)**123456**(%%) ~/~/ Enter password to enable AT commands access 2539 2539 ))) 2540 2540 ))) 2541 2541 ... ... @@ -2544,7 +2544,7 @@ 2544 2544 ))) 2545 2545 2546 2546 ((( 2547 -(% style="background-color:#dcdcdc" %)** 123456**(%%) ~/~/ Enter thepassword to enable AT command access1909 +(% style="background-color:#dcdcdc" %)** 123456**(%%) ~/~/ Enter password to enable AT commands access 2548 2548 ))) 2549 2549 2550 2550 ((( ... ... @@ -2613,7 +2613,7 @@ 2613 2613 2614 2614 2615 2615 ((( 2616 -(% style="color:blue" %)**If thesensorhasJOINED:**1978 +(% style="color:blue" %)**If sensor JOINED:** 2617 2617 2618 2618 (% style="background-color:#dcdcdc" %)**AT+CLASS=A** 2619 2619 ... ... @@ -2623,21 +2623,18 @@ 2623 2623 2624 2624 = 5. Case Study = 2625 2625 2626 -== 5.1 Counting how many objects pass through the flow line ==1988 +== 5.1 Counting how many objects pass through the flow Line == 2627 2627 1990 +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]]? 2628 2628 2629 -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]]. 2630 2630 2631 - 2632 2632 = 6. FAQ = 2633 2633 2634 - 2635 2635 This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly. 2636 2636 2637 2637 2638 2638 == 6.1 How to update the firmware? == 2639 2639 2640 - 2641 2641 Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to: 2642 2642 2643 2643 * Support new features ... ... @@ -2647,7 +2647,7 @@ 2647 2647 You will need the following things before proceeding: 2648 2648 2649 2649 * 3.5mm programming cable (included with the LT-22222-L as an additional accessory) 2650 -* USB to TTL adapter /converter2009 +* USB to TTL adapter 2651 2651 * 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) 2652 2652 * 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. 2653 2653 ... ... @@ -2657,7 +2657,7 @@ 2657 2657 2658 2658 Below is the hardware setup for uploading a firmware image to the LT-22222-L: 2659 2659 2660 -[[image:usb-ttl- audio-jack-connection.jpg]]2019 +[[image:usb-ttl-programming.png]] 2661 2661 2662 2662 2663 2663 ... ... @@ -2690,21 +2690,17 @@ 2690 2690 ((( 2691 2691 ((( 2692 2692 == 6.2 How to change the LoRaWAN frequency band/region? == 2693 - 2694 - 2695 2695 ))) 2696 2696 ))) 2697 2697 2698 2698 ((( 2699 -You can follow the introductions on [[how to upgrade theimage>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloading, select the required image file.2056 +You can follow the introductions on [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloading, select the required image file. 2700 2700 ))) 2701 2701 2702 2702 ((( 2703 2703 2704 2704 2705 -== 6.3 How to set up LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? == 2706 - 2707 - 2062 +== 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? == 2708 2708 ))) 2709 2709 2710 2710 ((( ... ... @@ -2778,13 +2778,11 @@ 2778 2778 2779 2779 == 6.4 How to change the uplink interval? == 2780 2780 2781 - 2782 2782 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/]] 2783 2783 2784 2784 2785 2785 == 6.5 Can I see the counting event in the serial output? == 2786 2786 2787 - 2788 2788 ((( 2789 2789 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. 2790 2790 ... ... @@ -2791,7 +2791,6 @@ 2791 2791 2792 2792 == 6.6 Can I use point-to-point communication with LT-22222-L? == 2793 2793 2794 - 2795 2795 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]]. 2796 2796 2797 2797 ... ... @@ -2800,14 +2800,13 @@ 2800 2800 ((( 2801 2801 == 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? == 2802 2802 2803 - 2804 2804 * If the device is not properly shut down and is directly powered off. 2805 2805 * It will default to a power-off state. 2806 2806 * In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory. 2807 -* After a restart, the status before the power failure will be read from Flash.2158 +* After a restart, the status before the power failure will be read from flash. 2808 2808 2809 -== 6.8 Can I set up LT-22222-L as an NC (Normally Closed) relay? == 2810 2810 2161 +== 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? == 2811 2811 2812 2812 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: 2813 2813 ... ... @@ -2817,19 +2817,16 @@ 2817 2817 2818 2818 == 6.9 Can the LT-22222-L save the RO state? == 2819 2819 2820 - 2821 2821 To enable this feature, the firmware version must be 1.6.0 or higher. 2822 2822 2823 2823 2824 2824 == 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? == 2825 2825 2826 - 2827 2827 It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose. 2828 2828 2829 2829 2830 2830 = 7. Troubleshooting = 2831 2831 2832 - 2833 2833 This section provides some known troubleshooting tips. 2834 2834 2835 2835 ... ... @@ -2838,8 +2838,6 @@ 2838 2838 ((( 2839 2839 ((( 2840 2840 == 7.1 Downlink isn't working. How can I solve this? == 2841 - 2842 - 2843 2843 ))) 2844 2844 ))) 2845 2845 ... ... @@ -2851,8 +2851,6 @@ 2851 2851 2852 2852 2853 2853 == 7.2 Having trouble uploading an image? == 2854 - 2855 - 2856 2856 ))) 2857 2857 2858 2858 ((( ... ... @@ -2863,8 +2863,6 @@ 2863 2863 2864 2864 2865 2865 == 7.3 Why can't I join TTN in the US915 /AU915 bands? == 2866 - 2867 - 2868 2868 ))) 2869 2869 2870 2870 ((( ... ... @@ -2874,7 +2874,6 @@ 2874 2874 2875 2875 == 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? == 2876 2876 2877 - 2878 2878 The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue. 2879 2879 Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]] 2880 2880 ... ... @@ -2881,7 +2881,6 @@ 2881 2881 2882 2882 = 8. Ordering information = 2883 2883 2884 - 2885 2885 (% style="color:#4f81bd" %)**LT-22222-L-XXX:** 2886 2886 2887 2887 (% style="color:#4f81bd" %)**XXX:** ... ... @@ -2896,9 +2896,9 @@ 2896 2896 * (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865 2897 2897 * (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779 2898 2898 2239 + 2899 2899 = 9. Package information = 2900 2900 2901 - 2902 2902 **Package includes**: 2903 2903 2904 2904 * 1 x LT-22222-L I/O Controller ... ... @@ -2913,9 +2913,9 @@ 2913 2913 * Package Size / pcs : 14.5 x 8 x 5 cm 2914 2914 * Weight / pcs : 170 g 2915 2915 2256 + 2916 2916 = 10. Support = 2917 2917 2918 - 2919 2919 * ((( 2920 2920 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. 2921 2921 ))) ... ... @@ -2927,7 +2927,6 @@ 2927 2927 2928 2928 = 11. Reference = 2929 2929 2930 - 2931 2931 * 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]] 2932 2932 * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]] 2933 2933 * [[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,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -143.4 KB - Content
- Screenshot 2024-12-08 193946.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -32.4 KB - Content
- dragino-lorawan-nw-lt-22222-n.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -267.3 KB - Content
- dragino-ttn-te.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -273.8 KB - Content
- lorawan-nw.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -250.6 KB - Content
- lt-22222-l-dashboard.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -352.8 KB - Content
- lt-22222-l-joining.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -301.9 KB - Content
- lt-22222-l-js-custom-payload-formatter.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -453.9 KB - Content
- lt33222-l.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.3 KB - Content
- usb-ttl-audio-jack-connection.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -394.4 KB - Content