Last modified by Saxer Lin on 2025/04/15 17:24
<
From version < 209.1 >
edited by Dilisi S
on 2024/11/22 19:34
To version < 203.1 >
edited by Dilisi S
on 2024/11/19 19:12
>
Change comment: Uploaded new attachment "dragino-ttn-te.jpg", version {1}

Summary

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 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.
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,20 +40,21 @@
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 Community Network), 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 -The network 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 57  == 1.2 Specifications ==
58 58  
59 59  (% style="color:#037691" %)**Hardware System:**
... ... @@ -119,7 +119,7 @@
119 119  (% style="width:524px" %)
120 120  |(% style="width:94px" %)**Model**|(% style="width:98px" %)**Photo**|(% style="width:329px" %)**Description**
121 121  |(% style="width:94px" %)**LT33222-L**|(% style="width:98px" %)(((
122 -
123 +[[image:/xwiki/bin/downloadrev/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LT-22222-L/WebHome/image-20230424115112-1.png?rev=1.1&width=58&height=106||alt="image-20230424115112-1.png" height="106" width="58"]]
123 123  )))|(% style="width:329px" %)(((
124 124  * 2 x Digital Input (Bi-direction)
125 125  * 2 x Digital Output
... ... @@ -129,6 +129,8 @@
129 129  * 1 x Counting Port
130 130  )))
131 131  
133 +
134 +
132 132  == 2. Assembling the device ==
133 133  
134 134  == 2.1 Connecting the antenna ==
... ... @@ -136,17 +136,17 @@
136 136  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.
137 137  
138 138  {{warning}}
139 -**Warning! Do not power on the device without connecting the antenna.**
142 +Warning! Do not power on the device without connecting the antenna.
140 140  {{/warning}}
141 141  
142 142  == 2.2 Terminals ==
143 143  
144 -The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals.
147 +The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 terminals and the lower screw terminal block has 10 terminals.
145 145  
146 -**Upper screw terminal block (from left to right):**
149 +Upper screw terminal block (from left to right):
147 147  
148 148  (% style="width:634px" %)
149 -|=(% style="width: 295px;" %)Screw Terminal|=(% style="width: 338px;" %)Function
152 +|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function
150 150  |(% style="width:295px" %)GND|(% style="width:338px" %)Ground
151 151  |(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage
152 152  |(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2
... ... @@ -154,10 +154,10 @@
154 154  |(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2
155 155  |(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1
156 156  
157 -**Lower screw terminal block (from left to right):**
160 +Lower screw terminal block (from left to right):
158 158  
159 159  (% style="width:633px" %)
160 -|=(% style="width: 296px;" %)Screw Terminal|=(% style="width: 334px;" %)Function
163 +|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function
161 161  |(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1
162 162  |(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1
163 163  |(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2
... ... @@ -169,12 +169,14 @@
169 169  |(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
170 170  |(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
171 171  
172 -== 2.3 Connecting LT-22222-L to a Power Source ==
175 +== 2.3 Powering the device ==
173 173  
174 -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.
177 +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.
175 175  
179 +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.
180 +
176 176  {{warning}}
177 -**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 +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.
178 178  {{/warning}}
179 179  
180 180  
... ... @@ -181,51 +181,36 @@
181 181  [[image:1653297104069-180.png]]
182 182  
183 183  
184 -= 3. Registering LT-22222-L with a LoRaWAN Network Server =
189 += 3. Registering with a LoRaWAN Network Server =
185 185  
186 -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.
191 +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.
187 187  
193 +After powering on, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** the LoRaWAN network. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LED** will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status.
188 188  
195 +In case you can't set the root key and other identifiers in the network server and must use them from the server, you can use [[AT Commands>>||anchor="H4.UseATCommand"]] to configure them on the device.
196 +
197 +The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
198 +
199 +[[image:image-20220523172350-1.png||height="266" width="864"]]
200 +
189 189  === 3.2.1 Prerequisites ===
190 190  
191 -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.
203 +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.
192 192  
193 193  [[image:image-20230425173427-2.png||height="246" width="530"]]
194 194  
195 -{{info}}
196 -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.
197 -{{/info}}
198 -
199 199  The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
200 200  
201 -=== 3.2.2 The Things Stack ===
209 +=== 3.2.2 The Things Stack Sandbox (TTSS) ===
202 202  
203 -This section guides you through how to register your LT-22222-L with The Things Stack Sandbox.
204 -
205 -{{info}}
206 206  The Things Stack Sandbox was formally called The Things Stack Community Edition.
207 -{{/info}}
208 208  
209 -
210 -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.
211 -
212 -
213 -[[image:dragino-lorawan-nw-lt-22222-n.jpg]]
214 -
215 -{{info}}
216 - 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.
217 -{{/info}}
218 -
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.
223 -* Log in to your The Things Stack Sandbox account.
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.
213 +* Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account.
214 +* Create an application with The Things Stack if you do not have one yet.
215 +* Go to your application page and click on the **End devices** in the left menu.
226 226  * On the End devices page, click on **+ Register end device**. Two registration options are available:
227 227  
228 -==== 3.2.2.2 Using the LoRaWAN Device Repository ====
218 +==== 3.2.2.1 Using the LoRaWAN Device Repository ====
229 229  
230 230  * On the **Register end device** page:
231 231  ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
... ... @@ -251,7 +251,7 @@
251 251  
252 252  ==== ====
253 253  
254 -==== 3.2.2.3 Adding device manually ====
244 +==== 3.2.2.2 Adding device manually ====
255 255  
256 256  * On the **Register end device** page:
257 257  ** Select the option **Enter end device specifies manually** under **Input method**.
... ... @@ -266,7 +266,7 @@
266 266  
267 267  
268 268  * Register end device page continued...
269 -** 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**//'
259 +** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network'
270 270  ** In the **DevEUI** field, enter the **DevEUI**.
271 271  ** In the **AppKey** field, enter the **AppKey**.
272 272  ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
... ... @@ -282,27 +282,24 @@
282 282  [[image:lt-22222-device-overview.png||height="625" width="1000"]]
283 283  
284 284  
285 -==== 3.2.2.4 Joining ====
275 +==== 3.2.2.3 Joining ====
286 286  
287 -On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
277 +On the Device overview page, click on **Live data** tab. The Live data panel for your device will display.
288 288  
289 -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.
279 +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**).
290 290  
291 291  
292 292  [[image:lt-22222-join-network.png||height="625" width="1000"]]
293 293  
294 294  
295 -==== 3.2.2.5 Uplinks ====
285 +By default, you will receive an uplink data message from the device every 10 minutes.
296 296  
297 -
298 -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.
299 -
300 300  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.
301 301  
302 302  [[image:lt-22222-ul-payload-decoded.png]]
303 303  
304 304  
305 -If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **Applications > your application > End devices** > **your end device** > **Payload formatters** > **Uplink**. Then  select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
292 +If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **End devices** > **LT-22222-L** > **Payload formatters** > **Uplink**. Then  select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
306 306  
307 307  {{info}}
308 308  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.
... ... @@ -311,11 +311,6 @@
311 311  [[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
312 312  
313 313  
314 -==== 3.2.2.6 Downlinks ====
315 -
316 -When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
317 -
318 -
319 319  == 3.3 Working Modes and Uplink Payload formats ==
320 320  
321 321  
... ... @@ -1605,7 +1605,7 @@
1605 1605  
1606 1606  ==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ====
1607 1607  
1608 -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.
1590 +This feature 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.
1609 1609  
1610 1610  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) **
1611 1611  
... ... @@ -1666,7 +1666,7 @@
1666 1666  
1667 1667  ==== 3.4.2.18 Counting ~-~- Clear Counting ====
1668 1668  
1669 -This command clears the counting in counting mode.
1651 +This feature clears the counting in counting mode.
1670 1670  
1671 1671  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT         **(%%) ~/~/ clear all counting
1672 1672  
... ... @@ -1693,7 +1693,7 @@
1693 1693  
1694 1694  ==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1695 1695  
1696 -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.
1678 +This feature allows you to configure the device to save its counting result to internal flash memory at specified intervals. By setting a save time, the device will periodically store the counting data to prevent loss in case of power failure. The save interval can be adjusted to suit your requirements, with a minimum value of 30 seconds.
1697 1697  
1698 1698  * (% style="color:#037691" %)**AT Command:**
1699 1699  
... ... @@ -1709,36 +1709,10 @@
1709 1709  )))
1710 1710  
1711 1711  
1712 -(% style="color:#037691" %)**AT Command**
1713 1713  
1714 -(% border="2" style="width:500px" %)
1715 -|(% style="width:124px" %)**Command**|(% style="width:374px" %)AT+COUTIME=<time>
1716 -|(% style="width:124px" %)**Response**|(% style="width:374px" %)
1717 -|(% style="width:124px" %)**Parameters**|(% style="width:374px" %)time : seconds (0 to 16777215)
1718 -|(% style="width:124px" %)**Example**|(% style="width:374px" %)(((
1719 -AT+COUTIME=60
1720 -
1721 -Sets the device to save its counting results to the memory every 60 seconds.
1722 -)))
1723 -
1724 -(% style="color:#037691" %)**Downlink Payload**
1725 -
1726 -(% border="2" style="width:500px" %)
1727 -|(% style="width:123px" %)**Payload**|(% style="width:375px" %)<prefix><time>
1728 -|(% style="width:123px" %)**Parameters**|(% style="width:375px" %)(((
1729 -prefix : A7
1730 -
1731 -time : seconds, 3 bytes in hexadecimal
1732 -)))
1733 -|(% style="width:123px" %)**Example**|(% style="width:375px" %)(((
1734 -A7 **00 00 3C**
1735 -
1736 -Sets the device to save its counting results to the memory every 60 seconds.
1737 -)))
1738 -
1739 1739  ==== 3.4.2.20 Reset save RO DO state ====
1740 1740  
1741 -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.
1697 +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.
1742 1742  
1743 1743  * (% style="color:#037691" %)**AT Command:**
1744 1744  
... ... @@ -1752,50 +1752,10 @@
1752 1752  (% style="color:blue" %)**0x AD aa      ** (%%)~/~/ same as AT+RODORET =aa
1753 1753  
1754 1754  
1755 -(% border="2" style="width:500px" %)
1756 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state>
1757 -|(% style="width:127px" %)**Response**|(% style="width:371px" %)
1758 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1759 -**state** :
1760 1760  
1761 -**0** : RODO will close when the device joins the network. (default)
1762 -
1763 -**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.
1764 -)))
1765 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1766 -(% style="color:blue" %)**AT+RODORESET=1 **
1767 -
1768 -RODO will close when the device joins the network. (default)
1769 -
1770 -(% style="color:blue" %)**AT+RODORESET=0 **
1771 -
1772 -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.
1773 -)))
1774 -
1775 -(% border="2" style="width:500px" %)
1776 -|(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state>
1777 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1778 -**prefix** : AD
1779 -
1780 -**state** :
1781 -
1782 -**0** : RODO will close when the device joins the network. (default), represents as 1 byte in hexadecimal.
1783 -
1784 -**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
1785 -)))
1786 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1787 -AD **01**
1788 -
1789 -RODO will close when the device joins the network. (default)
1790 -
1791 -AD **00**
1792 -
1793 -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.
1794 -)))
1795 -
1796 1796  ==== 3.4.2.21 Encrypted payload ====
1797 1797  
1798 -This command allows you to configure whether the device should upload data in an encrypted format or in plaintext. By default, the device encrypts the payload before uploading. You can toggle this setting to either upload encrypted data or transmit it without encryption.
1714 +This feature allows you to configure whether the device should upload data in an encrypted format or in plaintext. By default, the device encrypts the payload before uploading. You can toggle this setting to either upload encrypted data or transmit it without encryption.
1799 1799  
1800 1800  * (% style="color:#037691" %)**AT Command:**
1801 1801  
... ... @@ -1804,32 +1804,9 @@
1804 1804  (% style="color:blue" %)**AT+DECRYPT=0    **(%%)~/~/  Encrypt when uploading payload (default)
1805 1805  
1806 1806  
1807 -(% border="2" style="width:500px" %)
1808 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state>
1809 -|(% style="width:127px" %)**Response**|(% style="width:371px" %)
1810 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1811 -state :
1812 1812  
1813 -1 : The payload is uploaded without encryption
1814 -
1815 -0 : The payload is encrypted when uploaded (default)
1816 -)))
1817 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1818 -AT+DECRYPT=1
1819 -
1820 -The payload is uploaded without encryption
1821 -
1822 -AT+DECRYPT=0
1823 -
1824 -The payload is encrypted when uploaded (default)
1825 -)))
1826 -
1827 -There is no downlink payload for this configuration.
1828 -
1829 -
1830 1830  ==== 3.4.2.22 Get sensor value ====
1831 1831  
1832 -This command allows you to retrieve and optionally uplink sensor readings through the serial port.
1833 1833  
1834 1834  * (% style="color:#037691" %)**AT Command:**
1835 1835  
... ... @@ -1838,33 +1838,10 @@
1838 1838  (% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it.
1839 1839  
1840 1840  
1841 -(% border="2" style="width:500px" %)
1842 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state>
1843 -|(% style="width:127px" %)**Response**|(% style="width:371px" %)
1844 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1845 -**state** :
1846 1846  
1847 -**0 **: Retrieves the current sensor reading via the serial port.
1735 +==== 3.4.2.23 Resets the downlink packet count ====
1848 1848  
1849 -**1 **: Retrieves and uploads the current sensor reading via the serial port.
1850 -)))
1851 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1852 -AT+GETSENSORVALUE=0
1853 1853  
1854 -Retrieves the current sensor reading via the serial port.
1855 -
1856 -AT+GETSENSORVALUE=1
1857 -
1858 -Retrieves and uplinks the current sensor reading via the serial port.
1859 -)))
1860 -
1861 -There is no downlink payload for this configuration.
1862 -
1863 -
1864 -==== 3.4.2.23 Resetting the downlink packet count ====
1865 -
1866 -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.
1867 -
1868 1868  * (% style="color:#037691" %)**AT Command:**
1869 1869  
1870 1870  (% 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)
... ... @@ -1872,37 +1872,10 @@
1872 1872  (% 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.
1873 1873  
1874 1874  
1875 -(% border="2" style="width:500px" %)
1876 -|(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state>
1877 -|(% style="width:130px" %)**Response**|(% style="width:368px" %)(((
1878 -
1879 -)))
1880 -|(% style="width:130px" %)**Parameters**|(% style="width:368px" %)(((
1881 -**state **:
1882 1882  
1883 -**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).
1884 -
1885 -
1886 -**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.
1887 -)))
1888 -|(% style="width:130px" %)**Example**|(% style="width:368px" %)(((
1889 -AT+DISFCNTCHECK=0
1890 -
1891 -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).
1892 -
1893 -AT+DISFCNTCHECK=1
1894 -
1895 -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.
1896 -)))
1897 -
1898 -There is no downlink payload for this configuration.
1899 -
1900 -
1901 1901  ==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ====
1902 1902  
1903 1903  
1904 -This command controls the behavior of the node when the combined size of the MAC commands (MACANS) from the server and the payload exceeds the allowed byte limit for the current data rate (DR). The command provides two modes: one enables splitting the data into batches to ensure compliance with the byte limit, while the other prioritizes the payload and ignores the MACANS in cases of overflow.
1905 -
1906 1906  * (% style="color:#037691" %)**AT Command:**
1907 1907  
1908 1908  (% 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)
... ... @@ -1914,50 +1914,10 @@
1914 1914  
1915 1915  (% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set  the DISMACANS=1
1916 1916  
1917 -(% style="color:#037691" %)**AT Command**
1918 1918  
1919 -(% border="2" style="width:500px" %)
1920 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DISMACANS=<state>
1921 -|(% style="width:127px" %)**Response**|(% style="width:371px" %)
1922 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1923 -**state** :
1924 1924  
1925 -**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)
1926 -
1927 -**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.
1928 -)))
1929 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1930 -AT+DISMACANS=0
1931 -
1932 -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)
1933 -
1934 -AT+DISMACANS=1
1935 -
1936 -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.
1937 -)))
1938 -
1939 -(% style="color:#037691" %)**Downlink Payload**
1940 -
1941 -(% border="2" style="width:500px" %)
1942 -|(% style="width:126px" %)**Payload**|(% style="width:372px" %)<prefix><state>
1943 -|(% style="width:126px" %)**Parameters**|(% style="width:372px" %)(((
1944 -**prefix** : 21
1945 -
1946 -**state** : (2 bytes in hexadecimal)
1947 -
1948 -**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)
1949 -
1950 -**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.
1951 -)))
1952 -|(% style="width:126px" %)**Example**|(% style="width:372px" %)(((
1953 -21 **00 01**
1954 -
1955 -Set DISMACANS=1
1956 -)))
1957 -
1958 1958  ==== 3.4.2.25 Copy downlink to uplink ====
1959 1959  
1960 -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.
1961 1961  
1962 1962  * (% style="color:#037691" %)**AT Command**(%%)**:**
1963 1963  
... ... @@ -1970,22 +1970,8 @@
1970 1970  
1971 1971  For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
1972 1972  
1973 -(% border="2" style="width:500px" %)
1974 -|(% style="width:122px" %)**Command**|(% style="width:376px" %)(((
1975 -AT+RPL=5
1976 1976  
1977 -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.
1978 -)))
1979 -|(% style="width:122px" %)**Example**|(% style="width:376px" %)(((
1980 -Downlink:
1981 1981  
1982 -01 00 02 58
1983 -
1984 -Uplink:
1985 -
1986 -01 01 00 02 58
1987 -)))
1988 -
1989 1989  [[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"]]
1990 1990  
1991 1991  For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
... ... @@ -1992,16 +1992,14 @@
1992 1992  
1993 1993  
1994 1994  
1995 -==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
1784 +==== 3.4.2.26 Query version number and frequency band 、TDC ====
1996 1996  
1997 -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.
1998 1998  
1999 1999  * (((
2000 2000  (% style="color:#037691" %)**Downlink Payload**(%%)**:**
2001 2001  
2002 -(% style="color:blue" %)**26 01  ** (%%) ~/~/  The downlink payload 26 01 is used to query the device's firmware version, frequency band, sub band, and TDC time.
1790 +(% style="color:blue" %)**26 01  ** (%%) ~/~/  Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.
2003 2003  
2004 -
2005 2005  
2006 2006  )))
2007 2007  
... ... @@ -2031,8 +2031,6 @@
2031 2031  
2032 2032  === 3.5.2 Configuring ThingsEye.io ===
2033 2033  
2034 -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.
2035 -
2036 2036  * Login to your [[ThingsEye.io >>https://thingseye.io]]account.
2037 2037  * Under the **Integrations center**, click **Integrations**.
2038 2038  * Click the **Add integration** button (the button with the **+** symbol).
... ... @@ -2081,7 +2081,7 @@
2081 2081  
2082 2082  * Choose **Region** from the **Host type**.
2083 2083  * 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/...).
2084 -* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The **username **and **password **can be found on the MQTT integration page of your The Things Stack account (see **3.5.1 Configuring The Things Stack**).
1869 +* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The **username **and **password **can be found on the MQTT integration page of your The Things Stack account (see Configuring The Things Stack).
2085 2085  * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
2086 2086  
2087 2087  [[image:message-1.png]]
... ... @@ -2092,7 +2092,7 @@
2092 2092  [[image:thingseye-io-step-5.png||height="625" width="1000"]]
2093 2093  
2094 2094  
2095 -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.
1880 +Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings.
2096 2096  
2097 2097  
2098 2098  [[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
... ... @@ -2108,7 +2108,7 @@
2108 2108  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.
2109 2109  
2110 2110  {{info}}
2111 -See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
1896 +See also ThingsEye documentation.
2112 2112  {{/info}}
2113 2113  
2114 2114  ==== **3.5.2.2 Viewing events** ====
... ... @@ -2121,7 +2121,7 @@
2121 2121  [[image:thingseye-events.png||height="686" width="1000"]]
2122 2122  
2123 2123  
2124 -* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
1909 +* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
2125 2125  
2126 2126  [[image:thingseye-json.png||width="1000"]]
2127 2127  
... ... @@ -2131,11 +2131,6 @@
2131 2131  If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
2132 2132  
2133 2133  
2134 -==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
2135 -
2136 -This will be added soon.
2137 -
2138 -
2139 2139  == 3.6 Interface Details ==
2140 2140  
2141 2141  === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
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
lorawan-nw.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -250.6 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0