Changes for page LT-22222-L -- LoRa I/O Controller User Manual
Last modified by Mengting Qiu on 2025/06/04 18:42
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 7 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.pradeeka - Content
-
... ... @@ -27,7 +27,7 @@ 27 27 **This manual is also applicable to the LT-33222-L.** 28 28 {{/info}} 29 29 30 -The Dragino (% style="color:blue" %)**LT-22222-L I/O Controller**(%%) is an advanced LoRaWAN enddevice 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 +The Dragino (% style="color:blue" %)**LT-22222-L I/O Controller**(%%) is an advanced LoRaWAN device designed to provide seamless wireless long-range connectivity with various I/O options, including analog current and voltage inputs, digital inputs and outputs, and relay outputs. 31 31 32 32 The LT-22222-L I/O Controller simplifies and enhances I/O monitoring and controlling. It is ideal for professional applications in wireless sensor networks, including irrigation systems, smart metering, smart cities, building automation, and more. These controllers are designed for easy, cost-effective deployment using LoRa wireless technology. 33 33 ))) ... ... @@ -40,24 +40,23 @@ 40 40 ((( 41 41 You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways: 42 42 43 -* If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Stack CommunityNetwork), you can select a network and register the LT-22222-L I/O controller with it.43 +* If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Network), you can select a network and register the LT-22222-L I/O controller with it. 44 44 * If there is no public LoRaWAN coverage in your area, you can set up a LoRaWAN gateway, or multiple gateways, and connect them to a LoRaWAN network server to create adequate coverage. Then, register the LT-22222-L I/O controller with this network. 45 45 * Setup your own private LoRaWAN network. 46 + 47 +{{info}} 48 + You can use a LoRaWAN gateway, such as the [[Dragino LG308>>https://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], to expand or create LoRaWAN coverage in your area. 49 +{{/info}} 46 46 ))) 47 47 48 48 ((( 49 - 53 +[[image:1653295757274-912.png]] 50 50 51 - Thenetwork diagram below illustrates how the LT-22222-L communicates with a typical LoRaWAN network.55 + 52 52 ))) 53 53 54 -(% class="wikigeneratedid" %) 55 -[[image:lorawan-nw.jpg||height="354" width="900"]] 56 - 57 - 58 58 == 1.2 Specifications == 59 59 60 - 61 61 (% style="color:#037691" %)**Hardware System:** 62 62 63 63 * STM32L072xxxx MCU ... ... @@ -116,41 +116,24 @@ 116 116 * Smart cities 117 117 * Smart factory 118 118 119 -== 1.5HardwareVariants==118 +== 2. Assembling the device == 120 120 121 - 122 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) 123 -|(% 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** 124 -|(% style="width:94px" %)**LT-22222-L**|(% style="width:172px" %)((( 125 -(% style="text-align:center" %) 126 -[[image:lt33222-l.jpg||height="116" width="100"]] 127 -)))|(% style="width:256px" %)((( 128 -* 3 x Digital Input (Bi-direction) 129 -* 3 x Digital Output 130 -* 2 x Relay Output (5A@250VAC / 30VDC) 131 -* 2 x 0~~20mA Analog Input (res:0.01mA) 132 -* 2 x 0~~30V Analog Input (res:0.01v) 133 -* 1 x Counting Port 134 -))) 135 - 136 -= 2. Assembling the device = 137 - 138 138 == 2.1 Connecting the antenna == 139 139 140 140 Connect the LoRa antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper screw terminal block. Secure the antenna by tightening it clockwise. 141 141 142 142 {{warning}} 143 - **Warning! Do not power on the device without connecting the antenna.**125 +Warning! Do not power on the device without connecting the antenna. 144 144 {{/warning}} 145 145 146 146 == 2.2 Terminals == 147 147 148 -The LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 screwterminals and the lower screw terminal block has 10screwterminals.130 +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. 149 149 150 - **Upper screw terminal block (from left to right):**132 +Upper screw terminal block (from left to right): 151 151 152 152 (% style="width:634px" %) 153 -|=(% style="width: 295px;" %) ScrewTerminal|=(% style="width: 338px;" %)Function135 +|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function 154 154 |(% style="width:295px" %)GND|(% style="width:338px" %)Ground 155 155 |(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage 156 156 |(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2 ... ... @@ -158,10 +158,10 @@ 158 158 |(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2 159 159 |(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1 160 160 161 - **Lower screw terminal block (from left to right):**143 +Lower screw terminal block (from left to right): 162 162 163 163 (% style="width:633px" %) 164 -|=(% style="width: 296px;" %) ScrewTerminal|=(% style="width: 334px;" %)Function146 +|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function 165 165 |(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1 166 166 |(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1 167 167 |(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2 ... ... @@ -173,12 +173,14 @@ 173 173 |(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2 174 174 |(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1 175 175 176 -== 2.3 ConnectingLT-22222-Lto a PowerSource ==158 +== 2.3 Powering the device == 177 177 178 -The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s **positive wire**to the**VIN**and the**negative wire**to the**GND**screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered.160 +The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s positive wire to the VIN and the negative wire to the GND screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered. 179 179 162 +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. 163 + 180 180 {{warning}} 181 - **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.**165 +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. 182 182 {{/warning}} 183 183 184 184 ... ... @@ -185,51 +185,36 @@ 185 185 [[image:1653297104069-180.png]] 186 186 187 187 188 -= 3. Registering LT-22222-Lwith a LoRaWAN Network Server =172 += 3. Registering with a LoRaWAN Network Server = 189 189 190 - The LT-22222-L supportsbothOTAA (Over-the-Air Activation)and ABP (ActivationBy Personalization)methodsto activate with a LoRaWANNetworkServer.However,OTAAis themost securemethodforctivatingadevice with a LoRaWANNetworkServer.OTAAregenerates sessionkeys upon initialregistrationandregenerates new session keys after any subsequent reboots.By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode.174 +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. 191 191 176 +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. 192 192 178 +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. 179 + 180 +The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network. 181 + 182 +[[image:image-20220523172350-1.png||height="266" width="864"]] 183 + 193 193 === 3.2.1 Prerequisites === 194 194 195 - TheLT-22222-Lcomeswith device registration information such as DevEUI, AppEUI, and AppKeythat allows you to register it witha LoRaWAN network. Theseregistration 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.186 +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. 196 196 197 197 [[image:image-20230425173427-2.png||height="246" width="530"]] 198 198 199 -{{info}} 200 -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. 201 -{{/info}} 202 - 203 203 The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers. 204 204 205 -=== 3.2.2 The Things Stack === 192 +=== 3.2.2 The Things Stack Sandbox (TTSS) === 206 206 207 -This section guides you through how to register your LT-22222-L with The Things Stack Sandbox. 208 - 209 -{{info}} 210 210 The Things Stack Sandbox was formally called The Things Stack Community Edition. 211 -{{/info}} 212 212 213 - 214 -The network diagram below illustrates the connection between the LT-22222-L and The Things Stack, as well as how the data can be integrated with the ThingsEye IoT platform. 215 - 216 - 217 -[[image:dragino-lorawan-nw-lt-22222-n.jpg]] 218 - 219 -{{info}} 220 - You can use a LoRaWAN gateway, such as the [[Dragino LPS8N>>https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]], to expand or create LoRaWAN coverage in your area. 221 -{{/info}} 222 - 223 - 224 -==== 3.2.2.1 Setting up ==== 225 - 226 -* Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet. 227 -* Log in to your The Things Stack Sandbox account. 228 -* Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs). 229 -* Go to your application's page and click on the **End devices** in the left menu. 196 +* Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account. 197 +* Create an application with The Things Stack if you do not have one yet. 198 +* Go to your application page and click on the **End devices** in the left menu. 230 230 * On the End devices page, click on **+ Register end device**. Two registration options are available: 231 231 232 -==== 3.2.2. 2Using the LoRaWAN Device Repository ====201 +==== 3.2.2.1 Using the LoRaWAN Device Repository ==== 233 233 234 234 * On the **Register end device** page: 235 235 ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**. ... ... @@ -241,7 +241,7 @@ 241 241 *** **Profile (Region)**: Select the region that matches your device. 242 242 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 243 243 244 -[[image:lt-22222-l-dev-repo-reg-p1.png]] 213 +[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]] 245 245 246 246 247 247 * Register end device page continued... ... ... @@ -251,10 +251,11 @@ 251 251 ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. 252 252 ** Under **After registration**, select the **View registered end device** option. 253 253 254 -[[image:lt-22222-l-dev-repo-reg-p2.png]] 223 +[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]] 255 255 225 +==== ==== 256 256 257 -==== 3.2.2. 3Adding device manually ====227 +==== 3.2.2.2 Adding device manually ==== 258 258 259 259 * On the **Register end device** page: 260 260 ** Select the option **Enter end device specifies manually** under **Input method**. ... ... @@ -265,11 +265,11 @@ 265 265 ** Select the option **Over the air activation (OTAA)** under the **Activation mode.** 266 266 ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list. 267 267 268 -[[image:lt-22222-l-manually-p1.png]] 238 +[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]] 269 269 270 270 271 271 * Register end device page continued... 272 -** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message ' //**This end device can be registered on the network**//'242 +** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network' 273 273 ** In the **DevEUI** field, enter the **DevEUI**. 274 274 ** In the **AppKey** field, enter the **AppKey**. 275 275 ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. ... ... @@ -276,50 +276,41 @@ 276 276 ** Under **After registration**, select the **View registered end device** option. 277 277 ** Click the **Register end device** button. 278 278 279 -[[image:lt-22222-l-manually-p2.png]] 249 +[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]] 280 280 281 281 282 282 You will be navigated to the **Device overview** page. 283 283 284 284 285 -[[image:lt-22222-device-overview.png]] 255 +[[image:lt-22222-device-overview.png||height="625" width="1000"]] 286 286 287 287 288 -==== 3.2.2. 4Joining ====258 +==== 3.2.2.3 Joining ==== 289 289 290 -On the Device 'spage, click on **Live data** tab. The Live data panel for your device will display.260 +On the Device overview page, click on **Live data** tab. The Live data panel for your device will display. 291 291 292 -Now power on your LT-22222-L. The**TX LED**will**fast-blink 5 times** which meansthe LT-22222-L will enter the **work mode** and start to **join**The Things Stacknetwork 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.262 +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**). 293 293 294 294 295 -[[image:lt-22222- l-joining.png]]265 +[[image:lt-22222-join-network.png||height="625" width="1000"]] 296 296 297 297 268 +By default, you will receive an uplink data message from the device every 10 minutes. 298 298 299 -==== 3.2.2.5 Uplinks ==== 300 - 301 - 302 -After successfully joining, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**). When the LT-22222-L sends an uplink message to the server, the **TX LED** turns on for **1 second**. By default, you will receive an uplink data message from the device every 10 minutes. 303 - 304 304 Click on one of a **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the decode_payload {} JSON object. 305 305 306 306 [[image:lt-22222-ul-payload-decoded.png]] 307 307 308 308 309 -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**275 +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. 310 310 311 311 {{info}} 312 312 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. 313 313 {{/info}} 314 314 315 -[[image:lt-22222-ul-payload-fmt.png]] 281 +[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]] 316 316 317 317 318 -==== 3.2.2.6 Downlinks ==== 319 - 320 -When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**. 321 - 322 - 323 323 == 3.3 Working Modes and Uplink Payload formats == 324 324 325 325 ... ... @@ -595,19 +595,19 @@ 595 595 ))) 596 596 597 597 ((( 598 -AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s. 559 +Other AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s. 599 599 ))) 600 600 601 601 ((( 602 602 **In addition to that, below are the commands for AVI1 Counting:** 603 603 604 -(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI 1Count to 60)**565 +(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI Count to 60)** 605 605 606 -(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If theAVI1 voltageishigher than VOLMAX (20000mV =20V),thecounter increasesby1)**567 +(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 607 607 608 -(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If theAVI1 voltageislower than VOLMAX (20000mV =20V), counter increasesby1)**569 +(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)** 609 609 610 -(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If theAVI1 voltageishigher than VOLMAX (20000mV =20V), counter increasesby1)**571 +(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 611 611 ))) 612 612 613 613 ... ... @@ -726,9 +726,9 @@ 726 726 727 727 (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:** 728 728 729 - **Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**690 +Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 730 730 731 - **Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4692 +Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4 732 732 733 733 AA: Type Code for this downlink Command: 734 734 ... ... @@ -795,7 +795,7 @@ 795 795 796 796 **Example:** 797 797 798 -10100000: This means the systemis configuredto use the triggersAV1_LOW and AV2_LOW.759 +10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW 799 799 800 800 801 801 (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below ... ... @@ -824,7 +824,7 @@ 824 824 825 825 **Example:** 826 826 827 -10000000: The uplink is triggered by AV1_LOW,indicatingthatthe voltage is too low.788 +10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low. 828 828 829 829 830 830 (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below ... ... @@ -833,22 +833,22 @@ 833 833 |(% style="width:64px" %)**bit 7**|(% style="width:68px" %)**bit 6**|(% style="width:63px" %)**bit 5**|(% style="width:66px" %)**bit 4**|(% style="width:109px" %)**bit 3**|(% style="width:93px" %)**bit 2**|(% style="width:109px" %)**bit 1**|(% style="width:99px" %)**bit 0** 834 834 |(% style="width:64px" %)N/A|(% style="width:68px" %)N/A|(% style="width:63px" %)N/A|(% style="width:66px" %)N/A|(% style="width:109px" %)DI2_STATUS|(% style="width:93px" %)DI2_FLAG|(% style="width:109px" %)DI1_STATUS|(% style="width:99px" %)DI1_FLAG 835 835 836 -* Each bit shows which status has been triggered on this uplink. 797 +* Each bits shows which status has been triggered on this uplink. 837 837 838 838 **Example:** 839 839 840 -00000111: This means both DI1 and DI2 triggersare enabled,and this packet is trigger by DI1.801 +00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1. 841 841 842 -00000101: This means both DI1 and DI2 triggersare enabled.803 +00000101: Means both DI1 and DI2 trigger are enabled. 843 843 844 844 845 -(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable d. 0x00: MOD6 is disabled.806 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable. 846 846 847 -Downlink command to poll /requestMOD6 status:808 +Downlink command to poll MOD6 status: 848 848 849 849 **AB 06** 850 850 851 -When device receivesthis command, it will send the MOD6 payload.812 +When device got this command, it will send the MOD6 payload. 852 852 853 853 854 854 === 3.3.7 Payload Decoder === ... ... @@ -887,7 +887,7 @@ 887 887 These commands are specially designed for the LT-22222-L. Commands can be sent to the device using options such as an AT command or a LoRaWAN downlink payload. 888 888 889 889 890 -==== 3.4.2.1 Set Transmit /UplinkInterval ====851 +==== 3.4.2.1 Set Transmit Interval ==== 891 891 892 892 Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes. 893 893 ... ... @@ -896,11 +896,11 @@ 896 896 (% border="2" style="width:500px" %) 897 897 |**Command**|AT+TDC=<time> 898 898 |**Response**| 899 -|**Parameters**|**time** : uplink interval is in **milliseconds**860 +|**Parameters**|**time** : uplink interval is in milliseconds 900 900 |**Example**|((( 901 901 AT+TDC=30000 902 902 903 -Sets the uplink interval to **30 seconds**(30000milliseconds)864 +Sets the uplink interval to 30,000 milliseconds (30 seconds) 904 904 ))) 905 905 906 906 (% style="color:#037691" %)**Downlink payload** ... ... @@ -912,18 +912,16 @@ 912 912 |**Parameters**|((( 913 913 **prefix** : 0x01 914 914 915 -**time** : uplink interval is in **seconds**, represented by**3 bytes**in**hexadecimal**.876 +**time** : uplink interval is in milliseconds, represented by 3 bytes in hexadecimal. 916 916 ))) 917 917 |**Example**|((( 918 -01 **00 001E**879 +01 **00 75 30** 919 919 920 -Sets the uplink interval to **30 seconds**881 +Sets the uplink interval to 30,000 milliseconds (30 seconds) 921 921 922 -Conversion: 30 (dec) = 00 0 01E(hex)883 +Conversion: 30000 (dec) = 00 75 30 (hex) 923 923 924 -See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30]] 925 - 926 -[[image:Screenshot 2024-11-23 at 18.27.11.png]] 885 +See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]] 927 927 ))) 928 928 929 929 ==== 3.4.2.2 Set the Working Mode (AT+MOD) ==== ... ... @@ -972,13 +972,13 @@ 972 972 Sets the device to working mode 2 (Double DI Counting + DO + RO) 973 973 ))) 974 974 975 -==== 3.4.2.3 Requestan uplinkfrom the device====934 +==== 3.4.2.3 Poll an uplink ==== 976 976 977 -Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.936 +Requests an uplink from LT-22222-L. 978 978 979 979 (% style="color:#037691" %)**AT command** 980 980 981 -There is no AT Command available forthisfeature.940 +There is no AT Command to request an uplink from LT-22222-L 982 982 983 983 (% style="color:#037691" %)**Downlink payload** 984 984 ... ... @@ -986,7 +986,7 @@ 986 986 |(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF 987 987 |(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08 988 988 |(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 989 -08 **FF**948 +08 FF 990 990 991 991 Requests an uplink from LT-22222-L. 992 992 ))) ... ... @@ -1020,7 +1020,7 @@ 1020 1020 |(% style="width:97px" %)**Parameters**|(% style="width:401px" %)((( 1021 1021 **prefix** : 0x0A 06 (two bytes in hexadecimal) 1022 1022 1023 -** enable/disable trigger_mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.982 +**working mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal. 1024 1024 ))) 1025 1025 |(% style="width:97px" %)**Example**|(% style="width:401px" %)((( 1026 1026 0A 06 **01** ... ... @@ -1028,13 +1028,13 @@ 1028 1028 Enable trigger mode for the current working mode 1029 1029 ))) 1030 1030 1031 -==== 3.4.2.5 Requesttrigger settings ====990 +==== 3.4.2.5 Poll trigger settings ==== 1032 1032 1033 - Requeststhe trigger settings.992 +Polls the trigger settings. 1034 1034 1035 1035 (% style="color:#037691" %)**AT Command:** 1036 1036 1037 -There is no AT Command availablefor this feature.996 +There is no AT Command for this feature. 1038 1038 1039 1039 (% style="color:#037691" %)**Downlink Payload** 1040 1040 ... ... @@ -1174,6 +1174,9 @@ 1174 1174 ))) 1175 1175 |(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64** 1176 1176 1136 +(% class="wikigeneratedid" %) 1137 +==== ==== 1138 + 1177 1177 ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ==== 1178 1178 1179 1179 Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] ... ... @@ -1248,6 +1248,7 @@ 1248 1248 ))) 1249 1249 |(% style="width:104px" %)**Note**|(% style="width:387px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1250 1250 1213 + 1251 1251 (% style="color:#037691" %)**Downlink Payload** 1252 1252 1253 1253 (% border="2" style="width:500px" %) ... ... @@ -1270,6 +1270,7 @@ 1270 1270 ))) 1271 1271 |(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1272 1272 1236 + 1273 1273 ==== 3.4.2.11 Trigger – Set minimum interval ==== 1274 1274 1275 1275 Sets the AV and AC trigger minimum interval. The device won't respond to a second trigger within this set time after the first trigger. ... ... @@ -1305,6 +1305,7 @@ 1305 1305 ))) 1306 1306 |(% style="width:112px" %)Note|(% style="width:386px" %)(% style="color:red" %)**The time must be greater than 5 minutes.** 1307 1307 1272 + 1308 1308 ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ==== 1309 1309 1310 1310 Controls the digital outputs DO1, DO2, and DO3 ... ... @@ -1355,28 +1355,33 @@ 1355 1355 ))) 1356 1356 ))) 1357 1357 1323 +(% class="wikigeneratedid" %) 1324 +==== ==== 1325 + 1358 1358 ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ==== 1359 1359 1360 1360 1361 1361 * (% style="color:#037691" %)**AT Command** 1362 1362 1363 -There is no AT command to controlthe digitaloutput.1331 +There is no AT Command to control Digital Output 1364 1364 1365 1365 1366 1366 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)** 1367 1367 1368 -(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Set sDO1/DO2/DO3 outputswith time control1336 +(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Set DO1/DO2/DO3 output with time control 1369 1369 1338 + 1370 1370 This is to control the digital output time of DO pin. Include four bytes: 1371 1371 1372 -(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)1341 +(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9) 1373 1373 1374 -(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode1343 +(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode 1375 1375 1376 -**01:** DO pins revert to their original state after the timeout. 1377 -**00:** DO pins switch to an inverted state after the timeout. 1345 +01: DO pins will change back to original state after timeout. 1378 1378 1347 +00: DO pins will change to an inverter state after timeout 1379 1379 1349 + 1380 1380 (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status: 1381 1381 1382 1382 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) ... ... @@ -1385,7 +1385,7 @@ 1385 1385 |0x00|DO1 set to high 1386 1386 |0x11|DO1 NO Action 1387 1387 1388 -(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:1358 +(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status: 1389 1389 1390 1390 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1391 1391 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1393,7 +1393,7 @@ 1393 1393 |0x00|DO2 set to high 1394 1394 |0x11|DO2 NO Action 1395 1395 1396 -(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:1366 +(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status: 1397 1397 1398 1398 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1399 1399 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1401,7 +1401,7 @@ 1401 1401 |0x00|DO3 set to high 1402 1402 |0x11|DO3 NO Action 1403 1403 1404 -(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms)1374 +(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms) 1405 1405 1406 1406 1407 1407 (% style="color:red" %)**Note: ** ... ... @@ -1410,7 +1410,7 @@ 1410 1410 1411 1411 Before firmware v1.6.0, the latch time only supported 2 bytes. 1412 1412 1413 -(% style="color:red" %)** Thedevice will uplinka packet if the downlink code executes successfully.**1383 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.** 1414 1414 1415 1415 1416 1416 **Example payload:** ... ... @@ -1437,16 +1437,16 @@ 1437 1437 1438 1438 * (% style="color:#037691" %)**AT Command:** 1439 1439 1440 -There is no AT Command to control theRelay Output1410 +There is no AT Command to control Relay Output 1441 1441 1442 1442 1443 1443 * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):** 1444 1444 1445 -(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set sRO1/RO2 output1415 +(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set RO1/RO2 output 1446 1446 1447 1447 1448 1448 ((( 1449 -If thepayload is 0x030100, it means setting RO1 to close and RO2 to open.1419 +If payload is 0x030100, it means setting RO1 to close and RO2 to open. 1450 1450 ))) 1451 1451 1452 1452 ((( ... ... @@ -1464,7 +1464,7 @@ 1464 1464 |03 00 01|Open|Close 1465 1465 ))) 1466 1466 1467 -(% style="color:red" %)** Thedevice will uplinka packet ifthedownlink code executes successfully.**1437 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1468 1468 1469 1469 1470 1470 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== ... ... @@ -1473,19 +1473,19 @@ 1473 1473 1474 1474 * (% style="color:#037691" %)**AT Command:** 1475 1475 1476 -There is no AT Command to control theRelay Output1446 +There is no AT Command to control Relay Output 1477 1477 1478 1478 1479 1479 * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):** 1480 1480 1481 -(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set sRO1/RO2 relayswith time control1451 +(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set RO1/RO2 relay with time control 1482 1482 1483 1483 1484 -This control sthe relay output timeandincludes4bytes:1454 +This is to control the relay output time. It includes four bytes: 1485 1485 1486 -(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)1456 +(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05) 1487 1487 1488 -(% style="color:#4f81bd" %)**Second byte1458 +(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode 1489 1489 1490 1490 01: Relays will change back to their original state after timeout. 1491 1491 ... ... @@ -1492,12 +1492,12 @@ 1492 1492 00: Relays will change to the inverter state after timeout. 1493 1493 1494 1494 1495 -(% style="color:#4f81bd" %)**Third byte1465 +(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status: 1496 1496 1497 1497 [[image:image-20221008095908-1.png||height="364" width="564"]] 1498 1498 1499 1499 1500 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes1470 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms 1501 1501 1502 1502 1503 1503 (% style="color:red" %)**Note:** ... ... @@ -1507,7 +1507,7 @@ 1507 1507 Before firmware v1.6.0, the latch time only supported 2 bytes. 1508 1508 1509 1509 1510 -(% style="color:red" %)** Thedevice will uplinka packet if the downlink code executes successfully.**1480 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.** 1511 1511 1512 1512 1513 1513 **Example payload:** ... ... @@ -1535,356 +1535,131 @@ 1535 1535 1536 1536 When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1537 1537 1538 -(% style="color:#037691" %)**AT Command** 1508 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1539 1539 1540 -(% border="2" style="width:500px" %) 1541 -|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage>,<logic> 1542 -|(% style="width:137px" %)**Response**|(% style="width:361px" %) 1543 -|(% style="width:137px" %)**Parameters**|(% style="width:361px" %)((( 1544 -**voltage** : voltage threshold in mV 1510 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):** 1545 1545 1546 - **logic**:1512 +(% style="color:blue" %)**0xA5 aa bb cc ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc 1547 1547 1548 -**0** : lower than 1549 1549 1550 -**1**: higher than 1551 1551 1552 -if you leave logic parameter blank, it is considered 0 1553 -))) 1554 -|(% style="width:137px" %)**Examples**|(% style="width:361px" %)((( 1555 -AT+VOLMAX=20000 1556 - 1557 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1558 - 1559 -AT+VOLMAX=20000,0 1560 - 1561 -If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1 1562 - 1563 -AT+VOLMAX=20000,1 1564 - 1565 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1566 -))) 1567 - 1568 -(% style="color:#037691" %)**Downlink Payload** 1569 - 1570 -(% border="2" style="width:500px" %) 1571 -|(% style="width:140px" %)**Payload**|(% style="width:358px" %)<prefix><voltage><logic> 1572 -|(% style="width:140px" %)**Parameters**|(% style="width:358px" %)((( 1573 -**prefix** : A5 (hex) 1574 - 1575 -**voltage** : voltage threshold in mV (2 bytes in hex) 1576 - 1577 -**logic**: (1 byte in hexadecimal) 1578 - 1579 -**0** : lower than 1580 - 1581 -**1**: higher than 1582 - 1583 -if you leave logic parameter blank, it is considered 1 (higher than) 1584 -))) 1585 -|(% style="width:140px" %)**Example**|(% style="width:358px" %)((( 1586 -A5 **4E 20** 1587 - 1588 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1589 - 1590 -A5 **4E 20 00** 1591 - 1592 -If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1 1593 - 1594 -A5 **4E 20 01** 1595 - 1596 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1597 -))) 1598 - 1599 1599 ==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ==== 1600 1600 1601 -This commandallows users to pre-configure specific count numbers for various counting parameters such asCount1,Count2, or AVI1Count. Use the AT command to set the desired count number for each configuration.1518 +This feature allows users to pre-configure specific count numbers for various counting parameters such as count1, count2, or AV1 count. Use the AT command to set the desired count number for each configuration. 1602 1602 1603 -(% style="color:#037691" %)**AT Command** 1520 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) ** 1604 1604 1605 -(% border="2" style="width:500px" %) 1606 -|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter>,<number> 1607 -|(% style="width:134px" %)**Response**|(% style="width:364px" %) 1608 -|(% style="width:134px" %)**Parameters**|(% style="width:364px" %)((( 1609 -**counting_parameter** : 1522 +(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count 1610 1610 1611 - 1:COUNT11524 +(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set 1612 1612 1613 -2: COUNT2 1614 1614 1615 - 3:AVI1Count1527 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):** 1616 1616 1617 -**number** : Start number 1618 -))) 1619 -|(% style="width:134px" %)**Example**|(% style="width:364px" %)((( 1620 -AT+SETCNT=1,10 1529 +(% style="color:blue" %)**0x A8 aa bb cc dd ee ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee) 1621 1621 1622 -Sets the COUNT1 to 10. 1623 -))) 1624 1624 1625 -(% style="color:#037691" %)**Downlink Payload** 1626 1626 1627 -(% border="2" style="width:500px" %) 1628 -|(% style="width:135px" %)**Payload**|(% style="width:363px" %)<prefix><counting_parameter><number> 1629 -|(% style="width:135px" %)**Parameters**|(% style="width:363px" %)((( 1630 -prefix : A8 (hex) 1631 - 1632 -**counting_parameter** : (1 byte in hexadecimal) 1633 - 1634 -1: COUNT1 1635 - 1636 -2: COUNT2 1637 - 1638 -3: AVI1 Count 1639 - 1640 -**number** : Start number, 4 bytes in hexadecimal 1641 -))) 1642 -|(% style="width:135px" %)**Example**|(% style="width:363px" %)((( 1643 -A8 **01 00 00 00 0A** 1644 - 1645 -Sets the COUNT1 to 10. 1646 -))) 1647 - 1648 1648 ==== 3.4.2.18 Counting ~-~- Clear Counting ==== 1649 1649 1650 -This commandclears the counting in counting mode.1535 +This feature clears the counting in counting mode. 1651 1651 1652 -(% style="color:#037691" %)**AT Command** 1537 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT **(%%) ~/~/ clear all counting 1653 1653 1654 -(% border="2" style="width:500px" %) 1655 -|(% style="width:142px" %)**Command**|(% style="width:356px" %)AT+CLRCOUNT 1656 -|(% style="width:142px" %)**Response**|(% style="width:356px" %)- 1539 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):** 1657 1657 1658 -(% style="color: #037691" %)**DownlinkPayload**1541 +(% style="color:blue" %)**0x A6 01 ** (%%)~/~/ clear all counting 1659 1659 1660 -(% border="2" style="width:500px" %) 1661 -|(% style="width:141px" %)**Payload**|(% style="width:357px" %)<prefix><clear?> 1662 -|(% style="width:141px" %)**Parameters**|(% style="width:357px" %)((( 1663 -prefix : A6 (hex) 1664 1664 1665 -clear? : 01 (hex) 1666 -))) 1667 -|(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01** 1668 1668 1669 -==== 3.4.2.19 Counting ~-~- Set SavingIntervalfor 'CountingResult'====1545 +==== 3.4.2.19 Counting ~-~- Change counting mode to save time ==== 1670 1670 1671 -This commandallows 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.1547 +This feature allows you to configure the device to save its counting result to internal flash memory at specified intervals. By setting a save time, the device will periodically store the counting data to prevent loss in case of power failure. The save interval can be adjusted to suit your requirements, with a minimum value of 30 seconds. 1672 1672 1673 -(% style="color:#037691" %)**AT Command** 1549 +* (% style="color:#037691" %)**AT Command:** 1674 1674 1675 -(% border="2" style="width:500px" %) 1676 -|(% style="width:124px" %)**Command**|(% style="width:374px" %)AT+COUTIME=<time> 1677 -|(% style="width:124px" %)**Response**|(% style="width:374px" %) 1678 -|(% style="width:124px" %)**Parameters**|(% style="width:374px" %)time : seconds (0 to 16777215) 1679 -|(% style="width:124px" %)**Example**|(% style="width:374px" %)((( 1680 -AT+COUTIME=60 1551 +(% style="color:blue" %)**AT+COUTIME=60 **(%%)~/~/ Sets the save time to 60 seconds. The device will save the counting result in internal flash every 60 seconds. (Min value: 30 seconds) 1681 1681 1682 -Sets the device to save its counting results to the memory every 60 seconds. 1683 -))) 1684 1684 1685 -(% style="color:#037691" %)**Downlink Payload** 1554 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):** 1686 1686 1687 -(% border="2" style="width:500px" %) 1688 -|(% style="width:123px" %)**Payload**|(% style="width:375px" %)<prefix><time> 1689 -|(% style="width:123px" %)**Parameters**|(% style="width:375px" %)((( 1690 -prefix : A7 1556 +(% style="color:blue" %)**0x A7 aa bb cc ** (%%)~/~/ same as AT+COUTIME =aa bb cc, 1691 1691 1692 -time : seconds, 3 bytes in hexadecimal 1558 +((( 1559 +Range: aa bb cc:0 to 16777215, (unit: seconds) 1693 1693 ))) 1694 -|(% style="width:123px" %)**Example**|(% style="width:375px" %)((( 1695 -A7 **00 00 3C** 1696 1696 1697 -Sets the device to save its counting results to the memory every 60 seconds. 1698 -))) 1699 1699 1700 -==== 3.4.2.20 Reset saved RO and DO states ==== 1701 1701 1702 - Thiscommand allows you to resetthesavedrelay output (RO)and digital output (DO)stateswhen 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.1564 +==== 3.4.2.20 Reset save RO DO state ==== 1703 1703 1704 -( %style="color:#037691"%)**ATCommand**1566 +This feature 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. 1705 1705 1706 -(% border="2" style="width:500px" %) 1707 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state> 1708 -|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1709 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1710 -**state** : 1568 +* (% style="color:#037691" %)**AT Command:** 1711 1711 1712 -** 0**:RODO will close when the device joinsthe network. (default)1570 +(% style="color:blue" %)**AT+RODORESET=1 **(%%)~/~/ RODO will close when the device joining the network. (default) 1713 1713 1714 -**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. 1715 -))) 1716 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1717 -(% style="color:blue" %)**AT+RODORESET=1 ** 1572 +(% 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 will not change when the device reconnects to the network. 1718 1718 1719 -RODO will close when the device joins the network. (default) 1720 1720 1721 -(% style="color: blue" %)**AT+RODORESET=0**1575 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):** 1722 1722 1723 -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. 1724 -))) 1577 +(% style="color:blue" %)**0x AD aa ** (%%)~/~/ same as AT+RODORET =aa 1725 1725 1726 -(% style="color:#037691" %)**Downlink Payload** 1727 1727 1728 -(% border="2" style="width:500px" %) 1729 -|(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state> 1730 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1731 -**prefix** : AD 1732 1732 1733 -**state** : 1734 - 1735 -**0** : RODO will close when the device joins the network. (default), represents as 1 byte in hexadecimal. 1736 - 1737 -**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 1738 -))) 1739 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1740 -AD **01** 1741 - 1742 -RODO will close when the device joins the network. (default) 1743 - 1744 -AD **00** 1745 - 1746 -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. 1747 -))) 1748 - 1749 1749 ==== 3.4.2.21 Encrypted payload ==== 1750 1750 1751 -This commandallows you to configure whether the device should upload data in an encrypted format or in plaintext. By default, the device encrypts the payload before uploading. You can toggle this setting to either upload encrypted data or transmit it without encryption.1583 +This feature allows you to configure whether the device should upload data in an encrypted format or in plaintext. By default, the device encrypts the payload before uploading. You can toggle this setting to either upload encrypted data or transmit it without encryption. 1752 1752 1753 -(% style="color:#037691" %)**AT Command:** 1585 +* (% style="color:#037691" %)**AT Command:** 1754 1754 1755 -(% border="2" style="width:500px" %) 1756 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state> 1757 -|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1758 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1759 -**state** : 1587 +(% style="color:blue" %)**AT+DECRYPT=1 ** (%%)~/~/ The payload is uploaded without encryption 1760 1760 1761 -** 1**:The payloadsuploadedwithoutencryption1589 +(% style="color:blue" %)**AT+DECRYPT=0 **(%%)~/~/ Encrypt when uploading payload (default) 1762 1762 1763 -**0** : The payload is encrypted when uploaded (default) 1764 -))) 1765 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1766 -AT+DECRYPT=1 1767 1767 1768 -The payload is uploaded without encryption 1769 1769 1770 -AT+DECRYPT=0 1771 - 1772 -The payload is encrypted when uploaded (default) 1773 -))) 1774 - 1775 -There is no downlink payload for this configuration. 1776 - 1777 - 1778 1778 ==== 3.4.2.22 Get sensor value ==== 1779 1779 1780 -This command allows you to retrieve and optionally uplink sensor readings through the serial port. 1781 1781 1782 -(% style="color:#037691" %)**AT Command** 1596 +* (% style="color:#037691" %)**AT Command:** 1783 1783 1784 -(% border="2" style="width:500px" %) 1785 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state> 1786 -|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1787 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1788 -**state** : 1598 +(% style="color:blue" %)**AT+GETSENSORVALUE=0 **(%%)~/~/ The serial port retrieves the reading of the current sensor. 1789 1789 1790 -** 0**: Retrieves the current sensor readingviathe serialport.1600 +(% style="color:blue" %)**AT+GETSENSORVALUE=1 **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it. 1791 1791 1792 -**1 **: Retrieves and uploads the current sensor reading via the serial port. 1793 -))) 1794 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1795 -AT+GETSENSORVALUE=0 1796 1796 1797 -Retrieves the current sensor reading via the serial port. 1798 1798 1799 - AT+GETSENSORVALUE=11604 +==== 3.4.2.23 Resets the downlink packet count ==== 1800 1800 1801 -Retrieves and uplinks the current sensor reading via the serial port. 1802 -))) 1803 1803 1804 - Thereisno downlink payload forthisconfiguration.1607 +* (% style="color:#037691" %)**AT Command:** 1805 1805 1609 +(% 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) 1806 1806 1807 -== ==3.4.2.23Resettingthe downlink packet count====1611 +(% 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. 1808 1808 1809 -This command manages how the node handles mismatched downlink packet counts. It offers two modes: one disables the reception of further downlink packets if discrepancies occur, while the other resets the downlink packet count to align with the server, ensuring continued communication. 1810 1810 1811 -(% style="color:#037691" %)**AT Command** 1812 1812 1813 -(% border="2" style="width:500px" %) 1814 -|(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state> 1815 -|(% style="width:130px" %)**Response**|(% style="width:368px" %)((( 1816 - 1817 -))) 1818 -|(% style="width:130px" %)**Parameters**|(% style="width:368px" %)((( 1819 -**state **: 1820 - 1821 -**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). 1822 - 1823 - 1824 -**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. 1825 -))) 1826 -|(% style="width:130px" %)**Example**|(% style="width:368px" %)((( 1827 -AT+DISFCNTCHECK=0 1828 - 1829 -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). 1830 - 1831 -AT+DISFCNTCHECK=1 1832 - 1833 -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. 1834 -))) 1835 - 1836 -There is no downlink payload for this configuration. 1837 - 1838 - 1839 1839 ==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ==== 1840 1840 1841 1841 1842 - Thiscommand controls the behavior of the node when the combined size of the MAC commands(MACANS)from theserver andthe payloadexceeds 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.1618 +* (% style="color:#037691" %)**AT Command:** 1843 1843 1844 -(% style="color: #037691" %)**AT Command**1620 +(% 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) 1845 1845 1846 -(% border="2" style="width:500px" %) 1847 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DISMACANS=<state> 1848 -|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1849 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1850 -**state** : 1622 +(% 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. 1851 1851 1852 -**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) 1853 1853 1854 -**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. 1855 -))) 1856 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1857 -AT+DISMACANS=0 1625 +* (% style="color:#037691" %)**Downlink Payload **(%%)**:** 1858 1858 1859 - 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)1627 +(% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set the DISMACANS=1 1860 1860 1861 -AT+DISMACANS=1 1862 1862 1863 -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. 1864 -))) 1865 1865 1866 -(% style="color:#037691" %)**Downlink Payload** 1867 - 1868 -(% border="2" style="width:500px" %) 1869 -|(% style="width:126px" %)**Payload**|(% style="width:372px" %)<prefix><state> 1870 -|(% style="width:126px" %)**Parameters**|(% style="width:372px" %)((( 1871 -**prefix** : 21 1872 - 1873 -**state** : (2 bytes in hexadecimal) 1874 - 1875 -**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) 1876 - 1877 -**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. 1878 -))) 1879 -|(% style="width:126px" %)**Example**|(% style="width:372px" %)((( 1880 -21 **00 01** 1881 - 1882 -Set DISMACANS=1 1883 -))) 1884 - 1885 1885 ==== 3.4.2.25 Copy downlink to uplink ==== 1886 1886 1887 -This command enables the device to immediately uplink the content of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100. 1888 1888 1889 1889 * (% style="color:#037691" %)**AT Command**(%%)**:** 1890 1890 ... ... @@ -1897,22 +1897,8 @@ 1897 1897 1898 1898 For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77. 1899 1899 1900 -(% border="2" style="width:500px" %) 1901 -|(% style="width:122px" %)**Command**|(% style="width:376px" %)((( 1902 -AT+RPL=5 1903 1903 1904 -After receiving a downlink packet from the server, the node immediately uplinks the content of the packet back to the server using port number 100. 1905 -))) 1906 -|(% style="width:122px" %)**Example**|(% style="width:376px" %)((( 1907 -Downlink: 1908 1908 1909 -01 00 02 58 1910 - 1911 -Uplink: 1912 - 1913 -01 01 00 02 58 1914 -))) 1915 - 1916 1916 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]] 1917 1917 1918 1918 For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. ... ... @@ -1919,16 +1919,14 @@ 1919 1919 1920 1920 1921 1921 1922 -==== 3.4.2.26 Query firmwareversion,frequency band,sub band, andTDCtime====1653 +==== 3.4.2.26 Query version number and frequency band 、TDC ==== 1923 1923 1924 -This command is used to query key information about the device, including its firmware version, frequency band, sub band, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device. 1925 1925 1926 1926 * ((( 1927 1927 (% style="color:#037691" %)**Downlink Payload**(%%)**:** 1928 1928 1929 -(% style="color:blue" %)**26 01 ** (%%) ~/~/ The downlinkpayload26 01isusedtoquerythedevice'sfirmwareversion, frequency band, sub band,andTDC time.1659 +(% style="color:blue" %)**26 01 ** (%%) ~/~/ Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time. 1930 1930 1931 - 1932 1932 1933 1933 ))) 1934 1934 ... ... @@ -1954,17 +1954,15 @@ 1954 1954 The username and password (API key) you created here are required in the next section. 1955 1955 {{/info}} 1956 1956 1957 -[[image:tts-mqtt-integration.png]] 1686 +[[image:tts-mqtt-integration.png||height="625" width="1000"]] 1958 1958 1959 1959 === 3.5.2 Configuring ThingsEye.io === 1960 1960 1961 -The ThingsEye.io IoT platform is not open for self-registration at the moment. If you are interested in testing the platform, please send your project information to admin@thingseye.io, and we will create an account for you. 1962 - 1963 1963 * Login to your [[ThingsEye.io >>https://thingseye.io]]account. 1964 1964 * Under the **Integrations center**, click **Integrations**. 1965 1965 * Click the **Add integration** button (the button with the **+** symbol). 1966 1966 1967 -[[image:thingseye-io-step-1.png]] 1694 +[[image:thingseye-io-step-1.png||height="625" width="1000"]] 1968 1968 1969 1969 1970 1970 On the **Add integration** window, configure the following: ... ... @@ -1979,7 +1979,7 @@ 1979 1979 ** Allow create devices or assets 1980 1980 * Click the **Next** button. you will be navigated to the **Uplink data converter** tab. 1981 1981 1982 -[[image:thingseye-io-step-2.png]] 1709 +[[image:thingseye-io-step-2.png||height="625" width="1000"]] 1983 1983 1984 1984 1985 1985 **Uplink data converter:** ... ... @@ -1990,7 +1990,7 @@ 1990 1990 * 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]]. 1991 1991 * Click the **Next** button. You will be navigated to the **Downlink data converter **tab. 1992 1992 1993 -[[image:thingseye-io-step-3.png]] 1720 +[[image:thingseye-io-step-3.png||height="625" width="1000"]] 1994 1994 1995 1995 1996 1996 **Downlink data converter (this is an optional step):** ... ... @@ -2001,7 +2001,7 @@ 2001 2001 * 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]]. 2002 2002 * Click the **Next** button. You will be navigated to the **Connection** tab. 2003 2003 2004 -[[image:thingseye-io-step-4.png]] 1731 +[[image:thingseye-io-step-4.png||height="625" width="1000"]] 2005 2005 2006 2006 2007 2007 **Connection:** ... ... @@ -2008,7 +2008,7 @@ 2008 2008 2009 2009 * Choose **Region** from the **Host type**. 2010 2010 * 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/...). 2011 -* 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**).1738 +* 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). 2012 2012 * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**. 2013 2013 2014 2014 [[image:message-1.png]] ... ... @@ -2016,13 +2016,13 @@ 2016 2016 2017 2017 * Click the **Add** button. 2018 2018 2019 -[[image:thingseye-io-step-5.png]] 1746 +[[image:thingseye-io-step-5.png||height="625" width="1000"]] 2020 2020 2021 2021 2022 -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.1749 +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. 2023 2023 2024 2024 2025 -[[image:thingseye.io_integrationsCenter_integrations.png]] 1752 +[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]] 2026 2026 2027 2027 2028 2028 ==== 3.5.2.1 Viewing integration details ==== ... ... @@ -2029,13 +2029,13 @@ 2029 2029 2030 2030 Click on your integration from the list. The **Integration details** window will appear with the **Details **tab selected. The **Details **tab shows all the settings you have provided for this integration. 2031 2031 2032 -[[image:integration-details.png]] 1759 +[[image:integration-details.png||height="686" width="1000"]] 2033 2033 2034 2034 2035 2035 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. 2036 2036 2037 2037 {{info}} 2038 -See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].1765 +See also ThingsEye documentation. 2039 2039 {{/info}} 2040 2040 2041 2041 ==== **3.5.2.2 Viewing events** ==== ... ... @@ -2045,12 +2045,12 @@ 2045 2045 * Select **Debug **from the **Event type** dropdown. 2046 2046 * Select the** time frame** from the **time window**. 2047 2047 2048 -[[image:thingseye-events.png]] 1775 +[[image:thingseye-events.png||height="686" width="1000"]] 2049 2049 2050 2050 2051 -* To view the **JSON payload**of a message, click on the**three dots (...)**in the Message column of the desired message.1778 +* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message. 2052 2052 2053 -[[image:thingseye-json.png]] 1780 +[[image:thingseye-json.png||width="1000"]] 2054 2054 2055 2055 2056 2056 ==== **3.5.2.3 Deleting an integration** ==== ... ... @@ -2058,17 +2058,12 @@ 2058 2058 If you want to delete an integration, click the **Delete integratio**n button on the Integrations page. 2059 2059 2060 2060 2061 -==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ==== 2062 - 2063 -This will be added soon. 2064 - 2065 - 2066 2066 == 3.6 Interface Details == 2067 2067 2068 2068 === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) === 2069 2069 2070 2070 2071 -Supports **NPN-type**sensors.1793 +Supports NPN-type sensors. 2072 2072 2073 2073 [[image:1653356991268-289.png]] 2074 2074 ... ... @@ -2190,15 +2190,15 @@ 2190 2190 ))) 2191 2191 2192 2192 2193 -(% style="color:blue" %)**Example aDry Contact sensor1915 +(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor 2194 2194 2195 -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.1917 +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. 2196 2196 2197 -To detect a Dry Contact, you can supply a power source to one of thepinsof the Dry Contact.Areference circuit diagramis shown below.1919 +To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram. 2198 2198 2199 2199 [[image:image-20230616235145-1.png]] 2200 2200 2201 -(% style="color:blue" %)**Example 1923 +(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector 2202 2202 2203 2203 [[image:image-20240219115718-1.png]] 2204 2204 ... ... @@ -2274,7 +2274,7 @@ 2274 2274 [[image:image-20220524100215-10.png||height="382" width="723"]] 2275 2275 2276 2276 2277 -== 3.7 LED Indicators == 1999 +== 3.7 LEDs Indicators == 2278 2278 2279 2279 The table below lists the behavior of LED indicators for each port function. 2280 2280 ... ... @@ -2313,14 +2313,13 @@ 2313 2313 == 4.1 Connecting the LT-22222-L to a PC == 2314 2314 2315 2315 ((( 2316 -You can use a USB-to-TTL adapter /converteralong with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below.2038 +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. 2317 2317 2318 -[[image:usb-ttl-audio-jack-connection.jpg]] 2319 - 2320 - 2040 +[[image:usb-ttl-programming.png]] 2321 2321 ))) 2322 2322 2323 2323 2044 + 2324 2324 ((( 2325 2325 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: 2326 2326 ))) ... ... @@ -2350,39 +2350,39 @@ 2350 2350 * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey) 2351 2351 * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI) 2352 2352 * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON) 2353 -* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)2354 -* **##AT+DR##**: Get or set the Data Rate. (0-7 corresponding to DR_X)2355 -* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing2356 -* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)2357 -* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency2358 -* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)2359 -* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms2360 -* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms2361 -* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms2362 -* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms2363 -* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)2364 -* ##**AT+NWKID**##: Get or set the Network ID2365 -* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)2366 -* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)2367 -* ##**AT+CLASS**##: Get or set the Device Class2368 -* ##**AT+JOIN**##: Join network2369 -* ##**AT+NJS**##: Get OTAA Join Status2370 -* ##**AT+SENDB**##: Send hexadecimal data along with the application port2371 -* ##**AT+SEND**##: Send text data along with the application port2372 -* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)2373 -* ##**AT+RECV**##: Print last received data in raw format2374 -* ##**AT+VER**##: Get current image version and Frequency Band2375 -* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)2376 -* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)2377 -* ##**AT+SNR**##: Get the SNR of the last received packet2378 -* ##**AT+RSSI**##: Get the RSSI of the last received packet2379 -* ##**AT+TDC**##: Get or set the application data transmission interval in ms2380 -* ##**AT+PORT**##: Get or set the application port2381 -* ##**AT+DISAT**##: Disable AT commands2382 -* ##**AT+PWORD**##: Set password, max 9 digits2383 -* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode2384 -* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN4702385 -* ##**AT+CFG**##: Print all settings2074 +* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification) 2075 +* AT+DR: Get or set the Data Rate. (0-7 corresponding to DR_X) 2076 +* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing 2077 +* AT+PNM: Get or set the public network mode. (0: off, 1: on) 2078 +* AT+RX2FQ: Get or set the Rx2 window frequency 2079 +* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X) 2080 +* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms 2081 +* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms 2082 +* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms 2083 +* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms 2084 +* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA) 2085 +* AT+NWKID: Get or set the Network ID 2086 +* AT+FCU: Get or set the Frame Counter Uplink (FCntUp) 2087 +* AT+FCD: Get or set the Frame Counter Downlink (FCntDown) 2088 +* AT+CLASS: Get or set the Device Class 2089 +* AT+JOIN: Join network 2090 +* AT+NJS: Get OTAA Join Status 2091 +* AT+SENDB: Send hexadecimal data along with the application port 2092 +* AT+SEND: Send text data along with the application port 2093 +* AT+RECVB: Print last received data in binary format (with hexadecimal values) 2094 +* AT+RECV: Print last received data in raw format 2095 +* AT+VER: Get current image version and Frequency Band 2096 +* AT+CFM: Get or Set the confirmation mode (0-1) 2097 +* AT+CFS: Get confirmation status of the last AT+SEND (0-1) 2098 +* AT+SNR: Get the SNR of the last received packet 2099 +* AT+RSSI: Get the RSSI of the last received packet 2100 +* AT+TDC: Get or set the application data transmission interval in ms 2101 +* AT+PORT: Get or set the application port 2102 +* AT+DISAT: Disable AT commands 2103 +* AT+PWORD: Set password, max 9 digits 2104 +* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode 2105 +* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470 2106 +* AT+CFG: Print all settings 2386 2386 ))) 2387 2387 2388 2388 ... ... @@ -2547,7 +2547,7 @@ 2547 2547 You will need the following things before proceeding: 2548 2548 2549 2549 * 3.5mm programming cable (included with the LT-22222-L as an additional accessory) 2550 -* USB to TTL adapter /converter2271 +* USB to TTL adapter 2551 2551 * 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) 2552 2552 * 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. 2553 2553 ... ... @@ -2557,7 +2557,7 @@ 2557 2557 2558 2558 Below is the hardware setup for uploading a firmware image to the LT-22222-L: 2559 2559 2560 -[[image:usb-ttl- audio-jack-connection.jpg]]2281 +[[image:usb-ttl-programming.png]] 2561 2561 2562 2562 2563 2563
- 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
- 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-joining.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -301.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