<
From version < 178.1 >
edited by Dilisi S
on 2024/11/09 02:59
To version < 185.1 >
edited by Dilisi S
on 2024/11/10 05:32
>
Change comment: Nov 9 edits (saturday)

Summary

Details

Page properties
Content
... ... @@ -126,21 +126,14 @@
126 126  * 1 x Counting Port
127 127  )))
128 128  
129 -= 2. Assembling the Device =
129 += 2. Assembling =
130 130  
131 -== 2.1 What is included in the package? ==
131 +Attach 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.
132 132  
133 -The package includes the following items:
134 -
135 -* 1 x LT-22222-L I/O Controller
136 -* 1 x LoRaWAN antenna matched to the frequency of the LT-22222-L
137 -* 1 x bracket for DIN rail mounting
138 -* 1 x programming cable
139 -
140 -Attach the LoRaWAN antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper terminal block. Secure the antenna by tightening it clockwise.
141 -
142 142  == 2.2 Terminals ==
143 143  
135 +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.
136 +
144 144  Upper screw terminal block (from left to right):
145 145  
146 146  (% style="width:634px" %)
... ... @@ -167,26 +167,30 @@
167 167  |(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
168 168  |(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
169 169  
170 -== 2.3 Powering the LT-22222-L ==
163 +== 2.3 Powering the device ==
171 171  
172 -The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect the 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.
165 +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.
173 173  
167 +Powering on the device
174 174  
175 -[[image:1653297104069-180.png]]
169 +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.
176 176  
171 +{{warning}}
172 +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.
173 +{{/warning}}
177 177  
178 -= 3. Operation Mode =
179 179  
180 -== 3.1 How does it work? ==
176 +[[image:1653297104069-180.png]]
181 181  
178 +
179 += 3. Registering with a LoRaWAN Network Server =
180 +
182 182  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.
183 183  
184 -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 LE**D 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.
183 +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.
185 185  
186 186  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.
187 187  
188 -== 3.2 Registering with a LoRaWAN network server ==
189 -
190 190  The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
191 191  
192 192  [[image:image-20220523172350-1.png||height="266" width="864"]]
... ... @@ -201,55 +201,59 @@
201 201  
202 202  === 3.2.2 The Things Stack Sandbox (TTSS) ===
203 203  
201 +The Things Stack Sandbox was formally called The Things Stack Community Edition.
202 +
204 204  * Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account.
205 -* Create an application if you do not have one yet.
206 -* Register LT-22222-L with that application. Two registration options are available:
204 +* Create an application with The Things Stack if you do not have one yet.
205 +* Go to your application page and click on the **End devices** in the left menu.
206 +* On the End devices page, click on **+ Register end device**. Two registration options are available:
207 207  
208 -(% class="wikigeneratedid" %)
209 -==== ====
210 210  
211 211  ==== 3.2.2.1 Using the LoRaWAN Device Repository ====
212 212  
213 -* Go to your application and click on the **Register end device** button.
214 214  * On the **Register end device** page:
215 -** Select the option **Select the end device in the LoRaWAN Device Repository**.
216 -** Choose the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)**.
217 -** Select the **Frequency plan** that matches your device.
212 +** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
213 +** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists.
214 +*** **End device brand**: Dragino Technology Co., Limited
215 +*** **Model**: LT22222-L I/O Controller
216 +*** **Hardware ver**: Unknown
217 +*** **Firmware ver**: 1.6.0
218 +*** **Profile (Region)**: Select the region that matches your device.
219 +** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
218 218  
219 219  [[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
220 220  
221 221  
222 -* Page continued...
223 -** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
224 -** Enter the **DevEUI** in the **DevEUI** field.
225 -** Enter the **AppKey** in the **AppKey** field.
226 -** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
224 +* Register end device page continued...
225 +** 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'.
226 +** In the **DevEUI** field, enter the **DevEUI**.
227 +** In the **AppKey** field, enter the **AppKey.**
228 +** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
227 227  ** Under **After registration**, select the **View registered end device** option.
228 228  
229 229  [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
230 230  
231 -(% class="wikigeneratedid" %)
232 232  ==== ====
233 233  
234 -==== 3.2.2.2 Entering device information manually ====
235 +==== 3.2.2.2 Adding device manually ====
235 235  
236 236  * On the **Register end device** page:
237 -** Select the **Enter end device specifies manually** option as the input method.
238 -** Select the **Frequency plan** that matches your device.
239 -** Select the **LoRaWAN version**.
240 -** Select the **Regional Parameters version**.
241 -** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the section.
242 -** Select **Over the air activation (OTAA)** option under the **Activation mode**
243 -** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities**.
238 +** Select the option **Enter end device specifies manually** under **Input method**.
239 +** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
240 +** Select the **LoRaWAN version** as **LoRaWAN Specification 1.0.3**
241 +** Select the **Regional Parameters version** as** RP001 Regional Parameters 1.0.3 revision A**
242 +** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the hidden section.
243 +** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
244 +** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
244 244  
245 245  [[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
246 246  
247 247  
248 -* Page continued...
249 -** Enter **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
250 -** Enter **DevEUI** in the **DevEUI** field.
251 -** Enter **AppKey** in the **AppKey** field.
252 -** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
249 +* Register end device page continued...
250 +** 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'
251 +** In the **DevEUI** field, enter the **DevEUI**.
252 +** In the **AppKey** field, enter the **AppKey**.
253 +** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
253 253  ** Under **After registration**, select the **View registered end device** option.
254 254  ** Click the **Register end device** button.
255 255  
... ... @@ -264,15 +264,15 @@
264 264  
265 265  ==== 3.2.2.3 Joining ====
266 266  
267 -Click on **Live data** in the left navigation. The Live data panel for your application will display.
268 +On the Device overview page, click on **Live data** tab. The Live data panel for your device will display.
268 268  
269 -Power on your LT-22222-L. It will begin joining The Things Stack LoRaWAN network server. 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**).
270 +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**).
270 270  
271 271  
272 272  [[image:lt-22222-join-network.png||height="625" width="1000"]]
273 273  
274 274  
275 -By default, you will receive an uplink data message every 10 minutes.
276 +By default, you will receive an uplink data message from the device every 10 minutes.
276 276  
277 277  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.
278 278  
... ... @@ -281,6 +281,10 @@
281 281  
282 282  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.
283 283  
285 +{{info}}
286 +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.
287 +{{/info}}
288 +
284 284  [[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
285 285  
286 286  
... ... @@ -301,7 +301,6 @@
301 301  
302 302  * (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5
303 303  
304 -
305 305  The uplink messages are sent over LoRaWAN FPort 2. By default, an uplink message is sent every 10 minutes.
306 306  
307 307  === 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
... ... @@ -1386,25 +1386,25 @@
1386 1386  
1387 1387  == 3.5 Integrating with ThingsEye.io ==
1388 1388  
1389 -The Things Stack applications can be integrated with ThingsEye.io. Once integrated, ThingsEye.io works as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
1393 +The Things Stack application supports integration with ThingsEye.io. Once integrated, ThingsEye.io acts as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
1390 1390  
1391 -=== 3.5.1 Configuring MQTT Connection Information with The Things Stack Sandbox ===
1395 +=== 3.5.1 Configuring The Things Stack ===
1392 1392  
1393 -We use The Things Stack Sandbox for demonstating the configuration but  other
1397 +We use The Things Stack Sandbox in this example:
1394 1394  
1395 -* In **The Things Stack Sandbox**, select your application under **Applications**.
1396 -* Select **MQTT** under **Integrations**.
1397 -* In the **Connection information **section, for **Username**, The Things Stack displays an auto-generated username. You can use it or provide a new one.
1398 -* For the **Password**, click the **Generate new API key** button to generate a password. You can see it by clicking on the **eye** button. The API key works as the password.
1399 +* In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
1400 +* Select **MQTT** under **Integrations** in the left menu.
1401 +* In the **Connection information **section, under **Connection credentials**, The Things Stack displays an auto-generated **username**. You can use it or provide a new one.
1402 +* Click the **Generate new API key** button to generate a password. You can view it by clicking on the **visibility toggle/eye** icon. The API key works as the password.
1399 1399  
1400 -NOTE. The username and  password (API key) you created here are required in the next section.
1404 +{{info}}
1405 +The username and  password (API key) you created here are required in the next section.
1406 +{{/info}}
1401 1401  
1402 1402  [[image:tts-mqtt-integration.png||height="625" width="1000"]]
1403 1403  
1404 1404  === 3.5.2 Configuring ThingsEye.io ===
1405 1405  
1406 -This section guides you on how to create an integration in ThingsEye to connect with The Things Stack MQTT server.
1407 -
1408 1408  * Login to your [[ThingsEye.io >>https://thingseye.io]]account.
1409 1409  * Under the **Integrations center**, click **Integrations**.
1410 1410  * Click the **Add integration** button (the button with the **+** symbol).
... ... @@ -1443,7 +1443,7 @@
1443 1443  * Click the **Create new** button if it is not selected by default.
1444 1444  * Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name
1445 1445  * Click the **JavaScript** button.
1446 -* Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found here.
1450 +* 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]].
1447 1447  * Click the **Next** button. You will be navigated to the **Connection** tab.
1448 1448  
1449 1449  [[image:thingseye-io-step-4.png||height="625" width="1000"]]
... ... @@ -1472,7 +1472,7 @@
1472 1472  
1473 1473  **Viewing integration details**:
1474 1474  
1475 -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.
1479 +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.
1476 1476  
1477 1477  [[image:integration-details.png||height="686" width="1000"]]
1478 1478  
... ... @@ -1479,24 +1479,25 @@
1479 1479  
1480 1480  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.
1481 1481  
1482 -Note: See also ThingsEye documentation.
1486 +{{info}}
1487 +See also ThingsEye documentation.
1488 +{{/info}}
1483 1483  
1484 -
1485 1485  **Viewing events:**
1486 1486  
1487 -This tab  displays all the uplink messages from the LT-22222-L.
1492 +The **Events **tab displays all the uplink messages from the LT-22222-L.
1488 1488  
1489 -* Click on the **Events **tab.
1490 1490  * Select **Debug **from the **Event type** dropdown.
1491 1491  * Select the** time frame** from the **time window**.
1492 1492  
1493 -[insert image]
1497 +[[image:thingseye-events.png||height="686" width="1000"]]
1494 1494  
1495 -- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
1496 1496  
1497 -[insert image]
1500 +* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
1498 1498  
1502 +[[image:thingseye-json.png||width="1000"]]
1499 1499  
1504 +
1500 1500  **Deleting the integration**:
1501 1501  
1502 1502  If you want to delete this integration, click the **Delete integratio**n button.
... ... @@ -1744,13 +1744,14 @@
1744 1744  |**RO1**|For LT-22222-L: ON when RO1 is closed, OFF when RO1 is open
1745 1745  |**RO2**|For LT-22222-L: ON when RO2 is closed, OFF when RO2 is open
1746 1746  
1747 -= 4. Using AT Command =
1752 += 4. Using AT Commands =
1748 1748  
1749 -== 4.1 Connecting the LT-22222-L to a computer ==
1754 +The LT-22222-L supports programming using AT Commands.
1750 1750  
1756 +== 4.1 Connecting the LT-22222-L to a PC ==
1751 1751  
1752 1752  (((
1753 -The LT-22222-L supports programming using AT Commands. You can use a USB-to-TTL adapter along with a 3.5mm Program Cable to connect the LT-22222-L to a computer, as shown below.
1759 +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.
1754 1754  )))
1755 1755  
1756 1756  [[image:1653358238933-385.png]]
... ... @@ -1757,7 +1757,7 @@
1757 1757  
1758 1758  
1759 1759  (((
1760 -On the PC, the user needs 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. The AT commands are disabled by default, and a password (default:(% style="color:green" %)**123456**)(%%) must be entered to active them, as shown below:
1766 +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:
1761 1761  )))
1762 1762  
1763 1763  [[image:1653358355238-883.png]]
... ... @@ -1765,195 +1765,62 @@
1765 1765  
1766 1766  (((
1767 1767  You can find more details in the [[AT Command Manual>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
1768 -)))
1769 1769  
1770 -(((
1771 -The following table lists all the AT commands related to the LT-22222-L, except for those used for switching between modes.
1772 -
1773 -AT+<CMD>?        : Help on <CMD>
1775 +== 4.2 LT-22222-L related AT commands ==
1774 1774  )))
1775 1775  
1776 1776  (((
1777 -AT+<CMD>         : Run <CMD>
1778 -)))
1779 +The following is the list of all the AT commands related to the LT-22222-L, except for those used for switching between work modes.
1779 1779  
1780 -(((
1781 -AT+<CMD>=<value> : Set the value
1781 +* AT+<CMD>? : Help on <CMD>
1782 +* AT+<CMD> : Run <CMD>
1783 +* AT+<CMD>=<value> : Set the value
1784 +* AT+<CMD>=? : Get the value
1785 +* ATZ: Trigger a reset of the MCU
1786 +* ##**AT+FDR**##: Reset Parameters to factory default, reserve keys 
1787 +* **##AT+DEUI##**: Get or set the Device EUI (DevEUI)
1788 +* **##AT+DADDR##**: Get or set the Device Address (DevAddr)
1789 +* **##AT+APPKEY##**: Get or set the Application Key (AppKey)
1790 +* AT+NWKSKEY: Get or set the Network Session Key (NwkSKey)
1791 +* AT+APPSKEY: Get or set the Application Session Key (AppSKey)
1792 +* AT+APPEUI: Get or set the Application EUI (AppEUI)
1793 +* AT+ADR: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
1794 +* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
1795 +* AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
1796 +* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
1797 +* AT+PNM: Get or set the public network mode. (0: off, 1: on)
1798 +* AT+RX2FQ: Get or set the Rx2 window frequency
1799 +* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
1800 +* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
1801 +* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
1802 +* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
1803 +* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
1804 +* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
1805 +* AT+NWKID: Get or set the Network ID
1806 +* AT+FCU: Get or set the Frame Counter Uplink (FCntUp)
1807 +* AT+FCD: Get or set the Frame Counter Downlink (FCntDown)
1808 +* AT+CLASS: Get or set the Device Class
1809 +* AT+JOIN: Join network
1810 +* AT+NJS: Get OTAA Join Status
1811 +* AT+SENDB: Send hexadecimal data along with the application port
1812 +* AT+SEND: Send text data along with the application port
1813 +* AT+RECVB: Print last received data in binary format (with hexadecimal values)
1814 +* AT+RECV: Print last received data in raw format
1815 +* AT+VER: Get current image version and Frequency Band
1816 +* AT+CFM: Get or Set the confirmation mode (0-1)
1817 +* AT+CFS: Get confirmation status of the last AT+SEND (0-1)
1818 +* AT+SNR: Get the SNR of the last received packet
1819 +* AT+RSSI: Get the RSSI of the last received packet
1820 +* AT+TDC: Get or set the application data transmission interval in ms
1821 +* AT+PORT: Get or set the application port
1822 +* AT+DISAT: Disable AT commands
1823 +* AT+PWORD: Set password, max 9 digits
1824 +* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode
1825 +* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470
1826 +* AT+CFG: Print all settings
1782 1782  )))
1783 1783  
1784 -(((
1785 -AT+<CMD>=?       :  Get the value
1786 -)))
1787 1787  
1788 -(((
1789 -ATZ: Trig a reset of the MCU
1790 -)))
1791 -
1792 -(((
1793 -AT+FDR: Reset Parameters to Factory Default, Keys Reserve 
1794 -)))
1795 -
1796 -(((
1797 -AT+DEUI: Get or Set the Device EUI
1798 -)))
1799 -
1800 -(((
1801 -AT+DADDR: Get or Set the Device Address
1802 -)))
1803 -
1804 -(((
1805 -AT+APPKEY: Get or Set the Application Key
1806 -)))
1807 -
1808 -(((
1809 -AT+NWKSKEY: Get or Set the Network Session Key
1810 -)))
1811 -
1812 -(((
1813 -AT+APPSKEY:  Get or Set the Application Session Key
1814 -)))
1815 -
1816 -(((
1817 -AT+APPEUI:  Get or Set the Application EUI
1818 -)))
1819 -
1820 -(((
1821 -AT+ADR: Get or Set the Adaptive Data Rate setting. (0: off, 1: on)
1822 -)))
1823 -
1824 -(((
1825 -AT+TXP: Get or Set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Spec)
1826 -)))
1827 -
1828 -(((
1829 -AT+DR:  Get or Set the Data Rate. (0-7 corresponding to DR_X)  
1830 -)))
1831 -
1832 -(((
1833 -AT+DCS: Get or Set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
1834 -)))
1835 -
1836 -(((
1837 -AT+PNM: Get or Set the public network mode. (0: off, 1: on)
1838 -)))
1839 -
1840 -(((
1841 -AT+RX2FQ: Get or Set the Rx2 window frequency
1842 -)))
1843 -
1844 -(((
1845 -AT+RX2DR: Get or Set the Rx2 window data rate (0-7 corresponding to DR_X)
1846 -)))
1847 -
1848 -(((
1849 -AT+RX1DL: Get or Set the delay between the end of the Tx and the Rx Window 1 in ms
1850 -)))
1851 -
1852 -(((
1853 -AT+RX2DL: Get or Set the delay between the end of the Tx and the Rx Window 2 in ms
1854 -)))
1855 -
1856 -(((
1857 -AT+JN1DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
1858 -)))
1859 -
1860 -(((
1861 -AT+JN2DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
1862 -)))
1863 -
1864 -(((
1865 -AT+NJM:  Get or Set the Network Join Mode. (0: ABP, 1: OTAA)
1866 -)))
1867 -
1868 -(((
1869 -AT+NWKID: Get or Set the Network ID
1870 -)))
1871 -
1872 -(((
1873 -AT+FCU: Get or Set the Frame Counter Uplink
1874 -)))
1875 -
1876 -(((
1877 -AT+FCD: Get or Set the Frame Counter Downlink
1878 -)))
1879 -
1880 -(((
1881 -AT+CLASS: Get or Set the Device Class
1882 -)))
1883 -
1884 -(((
1885 -AT+JOIN: Join network
1886 -)))
1887 -
1888 -(((
1889 -AT+NJS: Get OTAA Join Status
1890 -)))
1891 -
1892 -(((
1893 -AT+SENDB: Send hexadecimal data along with the application port
1894 -)))
1895 -
1896 -(((
1897 -AT+SEND: Send text data along with the application port
1898 -)))
1899 -
1900 -(((
1901 -AT+RECVB: Print last received data in binary format (with hexadecimal values)
1902 -)))
1903 -
1904 -(((
1905 -AT+RECV: Print last received data in raw format
1906 -)))
1907 -
1908 -(((
1909 -AT+VER:  Get current image version and Frequency Band
1910 -)))
1911 -
1912 -(((
1913 -AT+CFM: Get or Set the confirmation mode (0-1)
1914 -)))
1915 -
1916 -(((
1917 -AT+CFS:  Get confirmation status of the last AT+SEND (0-1)
1918 -)))
1919 -
1920 -(((
1921 -AT+SNR: Get the SNR of the last received packet
1922 -)))
1923 -
1924 -(((
1925 -AT+RSSI: Get the RSSI of the last received packet
1926 -)))
1927 -
1928 -(((
1929 -AT+TDC: Get or set the application data transmission interval in ms
1930 -)))
1931 -
1932 -(((
1933 -AT+PORT: Get or set the application port
1934 -)))
1935 -
1936 -(((
1937 -AT+DISAT: Disable AT commands
1938 -)))
1939 -
1940 -(((
1941 -AT+PWORD: Set password, max 9 digits
1942 -)))
1943 -
1944 -(((
1945 -AT+CHS: Get or Set Frequency (Unit: Hz) for Single Channel Mode
1946 -)))
1947 -
1948 -(((
1949 -AT+CHE: Get or Set eight channels mode, Only for US915, AU915, CN470
1950 -)))
1951 -
1952 -(((
1953 -AT+CFG: Print all settings
1954 -)))
1955 -
1956 -
1957 1957  == 4.2 Common AT Command Sequence ==
1958 1958  
1959 1959  === 4.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
... ... @@ -1962,41 +1962,41 @@
1962 1962  
1963 1963  
1964 1964  (((
1965 -(% style="color:blue" %)**If device has not joined network yet:**
1838 +(% style="color:blue" %)**If the device has not joined the network yet:**
1966 1966  )))
1967 1967  )))
1968 1968  
1969 1969  (((
1970 -(% style="background-color:#dcdcdc" %)**123456**
1843 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**##
1971 1971  )))
1972 1972  
1973 1973  (((
1974 -(% style="background-color:#dcdcdc" %)**AT+FDR**
1847 +(% style="background-color:#dcdcdc" %)##**AT+FDR ~/~/reset parameters to factory default, reserve keys**##
1975 1975  )))
1976 1976  
1977 1977  (((
1978 -(% style="background-color:#dcdcdc" %)**123456**
1851 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**##
1979 1979  )))
1980 1980  
1981 1981  (((
1982 -(% style="background-color:#dcdcdc" %)**AT+NJM=0**
1855 +(% style="background-color:#dcdcdc" %)##**AT+NJM=0 ~/~/set to ABP mode**##
1983 1983  )))
1984 1984  
1985 1985  (((
1986 -(% style="background-color:#dcdcdc" %)**ATZ**
1859 +(% style="background-color:#dcdcdc" %)##**ATZ ~/~/reset MCU**##
1987 1987  )))
1988 1988  
1989 1989  
1990 1990  (((
1991 -(% style="color:blue" %)**If device already joined network:**
1864 +(% style="color:blue" %)**If the device has already joined the network:**
1992 1992  )))
1993 1993  
1994 1994  (((
1995 -(% style="background-color:#dcdcdc" %)**AT+NJM=0**
1868 +(% style="background-color:#dcdcdc" %)##**AT+NJM=0**##
1996 1996  )))
1997 1997  
1998 1998  (((
1999 -(% style="background-color:#dcdcdc" %)**ATZ**
1872 +(% style="background-color:#dcdcdc" %)##**ATZ**##
2000 2000  )))
2001 2001  
2002 2002  
... ... @@ -2102,31 +2102,39 @@
2102 2102  
2103 2103  = 6. FAQ =
2104 2104  
2105 -== 6.1 How to upgrade the firmware image? ==
1978 +This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
2106 2106  
1980 +== 6.1 How to update the firmware? ==
2107 2107  
2108 -The LT-22222-L I/O Controller is shipped with a 3.5mm cable, which is used to upload an image to LT in order to:
1982 +Dragino frequently releases firmware updates for the LT-22222-L.
2109 2109  
2110 -* Support new features.
2111 -* Fix bugs.
2112 -* Change LoRaWAN bands.
1984 +Updating your LT-22222-L with the latest firmware version helps to:
2113 2113  
2114 -Below is the hardware connection setup for uploading an firmware image to the LT-22222-L:
1986 +* Support new features
1987 +* Fix bugs
1988 +* Change LoRaWAN frequency bands
2115 2115  
2116 -(% class="box infomessage" %)
2117 -(((
2118 -The latest firmware version available for the LT-22222-L is v1.6.1 at the time of this writing.
2119 -)))
1990 +You will need the following things before proceeding:
2120 2120  
1992 +* 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
1993 +* USB to TTL adapter
1994 +* 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)
1995 +* 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.
1996 +
1997 +{{info}}
1998 +As of this writing, the latest firmware version available for the LT-22222-L is v1.6.1.
1999 +{{/info}}
2000 +
2001 +Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2002 +
2003 +
2121 2121  [[image:1653359603330-121.png]]
2122 2122  
2123 2123  
2124 -(((
2125 -(% style="color:#0000ff" %)**Step 1**(%%)**:** Download the F[[lash 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)
2126 -(% style="color:#0000ff" %)**Step 2**(%%)**:** Download the [[LT Image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]].
2127 -(% style="color:#0000ff" %)**Step 3**(%%)**:** Open the Flash Loader and choose the correct COM port to update.
2007 +Start the STM32 Flash Loader and choose the correct COM port to update.
2128 2128  
2129 2129  (((
2010 +(((
2130 2130  (% style="color:blue" %)**For LT-22222-L**(%%):
2131 2131  
2132 2132  Hold down the **PRO** button, then briefly press the **RST** button. The **DO1** LED will change from OFF to ON. When the **DO1** LED is ON, it indicates that the device is in firmware download mode.
... ... @@ -2151,7 +2151,7 @@
2151 2151  
2152 2152  (((
2153 2153  (((
2154 -== 6.2 How to change the LoRa Frequency Bands/Region? ==
2035 +== 6.2 How to change the LoRaWAN frequency band/region? ==
2155 2155  
2156 2156  
2157 2157  )))
... ... @@ -2164,7 +2164,7 @@
2164 2164  (((
2165 2165  
2166 2166  
2167 -== 6.3 How to set up LT to work with a Single Channel Gateway, such as LG01/LG02? ==
2048 +== 6.3 How to setup LT to work with a Single Channel Gateway, such as LG01/LG02? ==
2168 2168  
2169 2169  
2170 2170  )))
... ... @@ -2241,61 +2241,55 @@
2241 2241  Please see this link: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/]]
2242 2242  
2243 2243  
2244 -== 6.5 Can I see the counting event in Serial? ==
2125 +== 6.5 Can I see the counting event in the serial output? ==
2245 2245  
2246 2246  
2247 2247  (((
2248 -User can run AT+DEBUG command to see the counting event in serial. If firmware too old and doesn't support AT+DEBUG. User can update to latest firmware first.
2129 +You can run the AT command AT+DEBUG to view the counting event in the serial output. If the firmware is too old and doesnt support AT+DEBUG, update to the latest firmware first.
2249 2249  
2250 2250  
2251 2251  == 6.6 Can I use point-to-point communication with LT-22222-L? ==
2252 2252  
2253 2253  
2254 -Yes, please refer [[Point to Point Communication>>doc:Main. Point to Point Communication of LT-22222-L.WebHome]]. this is [[firmware>>https://github.com/dragino/LT-22222-L/releases]].
2255 -
2256 -
2135 +Yes, you can. Please refer to the [[Point-to-Point Communication of LT-22222-L>>https://wiki.dragino.com/xwiki/bin/view/Main/%20Point%20to%20Point%20Communication%20of%20LT-22222-L/]] page. The firmware that supports point-to-point communication can be found [[here>>https://github.com/dragino/LT-22222-L/releases]].
2257 2257  )))
2258 2258  
2259 2259  (((
2260 -== 6.7 Why does the relay output become the default and open relay after the lt22222 is powered off? ==
2139 +== 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
2261 2261  
2262 2262  
2263 -If the device is not shut down, but directly powered off.
2142 +* If the device is not properly shut down and is directly powered off.
2143 +* It will default to a power-off state.
2144 +* In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
2145 +* After a restart, the status before the power failure will be read from flash.
2264 2264  
2265 -It will default that this is a power-off state.
2147 +== 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
2266 2266  
2267 -In modes 2 to 5, DO RO status and pulse count are saved in flash.
2268 2268  
2269 -After restart, the status before power failure will be read from flash.
2150 +The LT-22222-L's built-in relay is Normally Open (NO). You can use an external relay to achieve a Normally Closed (NC) configuration. The circuit diagram is shown below:
2270 2270  
2271 2271  
2272 -== 6.8 Can i set up LT-22222-L as a NC(Normal Close) Relay? ==
2273 -
2274 -
2275 -LT-22222-L built-in relay is NO (Normal Open). User can use an external relay to achieve Normal Close purpose. Diagram as below:
2276 -
2277 -
2278 2278  [[image:image-20221006170630-1.png||height="610" width="945"]]
2279 2279  
2280 2280  
2281 -== 6.9 Can LT22222-L save RO state? ==
2156 +== 6.9 Can the LT-22222-L save the RO state? ==
2282 2282  
2283 2283  
2284 -Firmware version needs to be no less than 1.6.0.
2159 +The firmware version must be at least 1.6.0.
2285 2285  
2286 2286  
2287 -== 6.10 Why does the LT22222 always report 15.585V when measuring AVI? ==
2162 +== 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
2288 2288  
2289 2289  
2290 -It is likely that the GND is not connected during the measurement, or the wire connected to the GND is loose.
2165 +It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
2291 2291  
2292 2292  
2293 -= 7. Trouble Shooting =
2168 += 7. Troubleshooting =
2294 2294  )))
2295 2295  
2296 2296  (((
2297 2297  (((
2298 -== 7.1 Downlink doesn't work, how to solve it? ==
2173 +== 7.1 Downlink isn't working. How can I solve this? ==
2299 2299  
2300 2300  
2301 2301  )))
... ... @@ -2302,42 +2302,42 @@
2302 2302  )))
2303 2303  
2304 2304  (((
2305 -Please see this link for how to debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]]
2180 +Please refer to this link for debugging instructions: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]]
2306 2306  )))
2307 2307  
2308 2308  (((
2309 2309  
2310 2310  
2311 -== 7.2 Have trouble to upload image. ==
2186 +== 7.2 Having trouble uploading an image? ==
2312 2312  
2313 2313  
2314 2314  )))
2315 2315  
2316 2316  (((
2317 -See this link for trouble shooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
2192 +Please refer to this link for troubleshooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
2318 2318  )))
2319 2319  
2320 2320  (((
2321 2321  
2322 2322  
2323 -== 7.3 Why I can't join TTN in US915 /AU915 bands? ==
2198 +== 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
2324 2324  
2325 2325  
2326 2326  )))
2327 2327  
2328 2328  (((
2329 -It might be about the channels mapping. [[Please see this link for detail>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
2204 +It might be related to the channel mapping. [[Please refer to this link for details.>>https://github.com/dragino/LT-22222-L/releases]]
2330 2330  )))
2331 2331  
2332 2332  
2333 -== 7.4 Why can LT22222 perform Uplink normally, but cannot receive Downlink? ==
2208 +== 7.4 Why can the LT-22222-L perform Uplink normally, but cannot receive Downlink? ==
2334 2334  
2335 2335  
2336 -The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue state.
2337 -Use this command to bring their counts back together: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2211 +The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
2212 +Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2338 2338  
2339 2339  
2340 -= 8. Order Info =
2215 += 8. Ordering information =
2341 2341  
2342 2342  
2343 2343  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
... ... @@ -2344,43 +2344,42 @@
2344 2344  
2345 2345  (% style="color:#4f81bd" %)**XXX:**
2346 2346  
2347 -* (% style="color:red" %)**EU433**(%%):  LT with frequency bands EU433
2348 -* (% style="color:red" %)**EU868**(%%):  LT with frequency bands EU868
2349 -* (% style="color:red" %)**KR920**(%%):  LT with frequency bands KR920
2350 -* (% style="color:red" %)**CN470**(%%):  LT with frequency bands CN470
2351 -* (% style="color:red" %)**AS923**(%%):  LT with frequency bands AS923
2352 -* (% style="color:red" %)**AU915**(%%):  LT with frequency bands AU915
2353 -* (% style="color:red" %)**US915**(%%):  LT with frequency bands US915
2354 -* (% style="color:red" %)**IN865**(%%):  LT with frequency bands IN865
2355 -* (% style="color:red" %)**CN779**(%%):  LT with frequency bands CN779
2222 +* (% style="color:red" %)**EU433**(%%): LT with frequency bands EU433
2223 +* (% style="color:red" %)**EU868**(%%): LT with frequency bands EU868
2224 +* (% style="color:red" %)**KR920**(%%): LT with frequency bands KR920
2225 +* (% style="color:red" %)**CN470**(%%): LT with frequency bands CN470
2226 +* (% style="color:red" %)**AS923**(%%): LT with frequency bands AS923
2227 +* (% style="color:red" %)**AU915**(%%): LT with frequency bands AU915
2228 +* (% style="color:red" %)**US915**(%%): LT with frequency bands US915
2229 +* (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865
2230 +* (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779
2356 2356  
2357 -= 9. Packing Info =
2232 += 9. Packing information =
2358 2358  
2359 2359  
2360 -**Package Includes**:
2235 +**Package includes**:
2361 2361  
2362 -* LT-22222-L I/O Controller x 1
2363 -* Stick Antenna for LoRa RF part x 1
2364 -* Bracket for controller x1
2365 -* Program cable x 1
2237 +* 1 x LT-22222-L I/O Controller
2238 +* 1 x LoRa antenna matched to the frequency of the LT-22222-L
2239 +* 1 x bracket for DIN rail mounting
2240 +* 1 x 3.5mm programming cable
2366 2366  
2367 2367  **Dimension and weight**:
2368 2368  
2369 2369  * Device Size: 13.5 x 7 x 3 cm
2370 -* Device Weight: 105g
2245 +* Device Weight: 105 g
2371 2371  * Package Size / pcs : 14.5 x 8 x 5 cm
2372 -* Weight / pcs : 170g
2247 +* Weight / pcs : 170 g
2373 2373  
2374 2374  = 10. Support =
2375 2375  
2376 2376  
2377 2377  * (((
2378 -Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
2253 +Support is available Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different time zones, we cannot offer live support. However, your questions will be answered as soon as possible within the aforementioned schedule.
2379 2379  )))
2380 2380  * (((
2381 -Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[Support@dragino.cc>>mailto:Support@dragino.cc]]
2256 +Please provide as much information as possible regarding your inquiry (e.g., product models, a detailed description of the problem, steps to replicate it, etc.) and send an email to [[support@dragino.cc>>mailto:support@dragino.cc]]
2382 2382  
2383 -
2384 2384  
2385 2385  )))
2386 2386  
thingseye-events.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +530.6 KB
Content
thingseye-json.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +554.8 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0