Changes for page LT-22222-L -- LoRa I/O Controller User Manual
Last modified by Saxer Lin on 2025/04/15 17:24
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- 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 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 +The Dragino (% style="color:blue" %)**LT-22222-L I/O Controller**(%%) is an advanced LoRaWAN end device designed to provide seamless wireless long-range connectivity with various I/O options, including analog current and voltage inputs, digital inputs and outputs, and relay outputs. 31 31 32 32 The LT-22222-L I/O Controller simplifies and enhances I/O monitoring and controlling. It is ideal for professional applications in wireless sensor networks, including irrigation systems, smart metering, smart cities, building automation, and more. These controllers are designed for easy, cost-effective deployment using LoRa wireless technology. 33 33 ))) ... ... @@ -133,7 +133,6 @@ 133 133 * 1 x Counting Port 134 134 ))) 135 135 136 - 137 137 == 2. Assembling the device == 138 138 139 139 == 2.1 Connecting the antenna == ... ... @@ -178,10 +178,8 @@ 178 178 179 179 The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s **positive wire** to the **VIN** and the **negative wire** to the **GND** screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered. 180 180 181 -Once powered, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** with the Network Server. 182 - 183 183 {{warning}} 184 -We recommend that you power on the LT-22222-L after configuring its registration 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. 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.** 185 185 {{/warning}} 186 186 187 187 ... ... @@ -190,16 +190,13 @@ 190 190 191 191 = 3. Registering LT-22222-L with a LoRaWAN Network Server = 192 192 193 - By default, the LT-22222-Lisconfigured to operate in LoRaWAN Class C mode. It supports both OTAA (Over-the-Air Activation) and ABP (Activation By Personalization) methods to activate with a LoRaWAN Network Server. However, OTAA is the most secure method for activating a device with a LoRaWAN Network Server.190 +The LT-22222-L supports both OTAA (Over-the-Air Activation) and ABP (Activation By Personalization) methods to activate with a LoRaWAN Network Server. However, OTAA is the most secure method for activating a device with a LoRaWAN Network Server. OTAA regenerates session keys upon initial registration and regenerates new session keys after any subsequent reboots. By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode. 194 194 195 195 196 - 197 197 === 3.2.1 Prerequisites === 198 198 199 -The LT-22222-L comes with device registration information that allows you to register it with a LoRaWAN network ,enabling thedevicetoperformOTAAactivationwiththe network serverupon initial power-upandafteranysubsequentreboots.195 +The LT-22222-L comes with device registration information such as DevEUI, AppEUI, and AppKey that allows you to register it with a LoRaWAN network. These registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference. 200 200 201 -Make sure you have the device registration information such as DevEUI, AppEUI, and AppKey with you. These registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference. 202 - 203 203 [[image:image-20230425173427-2.png||height="246" width="530"]] 204 204 205 205 {{info}} ... ... @@ -208,26 +208,31 @@ 208 208 209 209 The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers. 210 210 211 -=== 3.2.2 Registering withThe Things Stack ===205 +=== 3.2.2 The Things Stack === 212 212 207 +This section guides you through how to register your LT-22222-L with The Things Stack Sandbox. 208 + 213 213 {{info}} 214 214 The Things Stack Sandbox was formally called The Things Stack Community Edition. 215 215 {{/info}} 216 216 217 217 218 -The network diagram below s hows how the LT-22222-Lis connectedtoThe Things Stack and integrates itsdatawith the ThingsEye IoT platform.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. 219 219 220 220 [[image:dragino-ttn-te.jpg]] 221 221 222 222 223 -* Create a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have a one yet. 219 + 220 +==== 3.2.2.1 Setting up ==== 221 + 222 +* Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet. 224 224 * Log in to your The Things Stack Sandbox account. 225 -* Create an application with The Things Stack if you do not have one yet. 226 -* Go to your application page and click on the **End devices** in the left menu. 224 +* Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs). 225 +* Go to your application's page and click on the **End devices** in the left menu. 227 227 * On the End devices page, click on **+ Register end device**. Two registration options are available: 228 228 229 229 230 -==== 3.2.2. 1Using the LoRaWAN Device Repository ====229 +==== 3.2.2.2 Using the LoRaWAN Device Repository ==== 231 231 232 232 * On the **Register end device** page: 233 233 ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**. ... ... @@ -239,7 +239,6 @@ 239 239 *** **Profile (Region)**: Select the region that matches your device. 240 240 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 241 241 242 - 243 243 [[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]] 244 244 245 245 ... ... @@ -254,7 +254,7 @@ 254 254 255 255 ==== ==== 256 256 257 -==== 3.2.2. 2Adding device manually ====255 +==== 3.2.2.3 Adding device manually ==== 258 258 259 259 * On the **Register end device** page: 260 260 ** Select the option **Enter end device specifies manually** under **Input method**. ... ... @@ -269,7 +269,7 @@ 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' 270 +** 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. ... ... @@ -285,7 +285,7 @@ 285 285 [[image:lt-22222-device-overview.png||height="625" width="1000"]] 286 286 287 287 288 -==== 3.2.2. 3Joining ====286 +==== 3.2.2.4 Joining ==== 289 289 290 290 On the Device overview page, click on **Live data** tab. The Live data panel for your device will display. 291 291 ... ... @@ -295,7 +295,7 @@ 295 295 [[image:lt-22222-join-network.png||height="625" width="1000"]] 296 296 297 297 298 -==== 3.2.2. 4Uplinks ====296 +==== 3.2.2.5 Uplinks ==== 299 299 300 300 301 301 After successfully joining, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**). When the LT-22222-L sends an uplink message to the server, the **TX LED** turns on for **1 second**. By default, you will receive an uplink data message from the device every 10 minutes. ... ... @@ -314,7 +314,7 @@ 314 314 [[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]] 315 315 316 316 317 -==== 3.2.2. 4Uplinks ====315 +==== 3.2.2.6 Downlinks ==== 318 318 319 319 When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**. 320 320 ... ... @@ -1712,7 +1712,34 @@ 1712 1712 ))) 1713 1713 1714 1714 1713 +(% style="color:#037691" %)**AT Command** 1715 1715 1715 +(% border="2" style="width:500px" %) 1716 +|(% style="width:124px" %)**Command**|(% style="width:374px" %)AT+COUTIME=<time> 1717 +|(% style="width:124px" %)**Response**|(% style="width:374px" %) 1718 +|(% style="width:124px" %)**Parameters**|(% style="width:374px" %)time : seconds (0 to 16777215) 1719 +|(% style="width:124px" %)**Example**|(% style="width:374px" %)((( 1720 +AT+COUTIME=60 1721 + 1722 +Sets the device to save its counting results to the memory every 60 seconds. 1723 +))) 1724 + 1725 +(% style="color:#037691" %)**Downlink Payload** 1726 + 1727 +(% border="2" style="width:500px" %) 1728 +|(% style="width:123px" %)**Payload**|(% style="width:375px" %)<prefix><time> 1729 +|(% style="width:123px" %)**Parameters**|(% style="width:375px" %)((( 1730 +prefix : A7 1731 + 1732 +time : seconds, 3 bytes in hexadecimal 1733 +))) 1734 +|(% style="width:123px" %)**Example**|(% style="width:375px" %)((( 1735 +A7 **00 00 3C** 1736 + 1737 +Sets the device to save its counting results to the memory every 60 seconds. 1738 +))) 1739 + 1740 + 1716 1716 ==== 3.4.2.20 Reset save RO DO state ==== 1717 1717 1718 1718 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. ... ... @@ -1729,7 +1729,49 @@ 1729 1729 (% style="color:blue" %)**0x AD aa ** (%%)~/~/ same as AT+RODORET =aa 1730 1730 1731 1731 1757 +(% border="2" style="width:500px" %) 1758 +|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state> 1759 +|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1760 +|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1761 +state : 1732 1732 1763 +0 : RODO will close when the device joins the network. (default) 1764 + 1765 +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. 1766 +))) 1767 +|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1768 +(% style="color:blue" %)**AT+RODORESET=1 ** 1769 + 1770 +RODO will close when the device joins the network. (default) 1771 + 1772 +(% style="color:blue" %)**AT+RODORESET=0 ** 1773 + 1774 +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. 1775 +))) 1776 + 1777 + 1778 +(% border="2" style="width:500px" %) 1779 +|(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state> 1780 +|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1781 +prefix : AD 1782 + 1783 +state : 1784 + 1785 +0 : RODO will close when the device joins the network. (default), represents as 1 byte in hexadecimal. 1786 + 1787 +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 1788 +))) 1789 +|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1790 +AD **01** 1791 + 1792 +RODO will close when the device joins the network. (default) 1793 + 1794 +AD **00** 1795 + 1796 +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. 1797 +))) 1798 + 1799 + 1733 1733 ==== 3.4.2.21 Encrypted payload ==== 1734 1734 1735 1735 This feature allows you to configure whether the device should upload data in an encrypted format or in plaintext. By default, the device encrypts the payload before uploading. You can toggle this setting to either upload encrypted data or transmit it without encryption.
- dragino-lorawan-nw-lt-22222-n.jpg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +267.3 KB - Content