Skip to Content
Last modified by Mengting Qiu on 2025/06/04 18:42
From version 166.1
edited by Dilisi S
on 2024/11/07 05:43
Change comment: more edits
To version 178.1
edited by Dilisi S
on 2024/11/09 02:59
Change comment: Nov 8 edits - part 1

Summary

Details

Page properties
Content
... ... @@ -33,8 +33,6 @@
33 33  With the LT-22222-L I/O Controller, users can transmit data over ultra-long distances with low power consumption using LoRa, a spread-spectrum modulation technique derived from chirp spread spectrum (CSS) technology that operates on license-free ISM bands.
34 34  )))
35 35  
36 -> The LT Series I/O Controllers are designed for easy, low-cost installation on LoRaWAN networks.
37 -
38 38  (((
39 39  You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways:
40 40  
... ... @@ -59,7 +59,7 @@
59 59  * SX1276/78 Wireless Chip 
60 60  * Power Consumption:
61 61  ** Idle: 4mA@12v
62 -** 20dB Transmit: 34mA@12v
60 +** 20dB Transmit: 34mA@12V
63 63  * Operating Temperature: -40 ~~ 85 Degrees, No Dew
64 64  
65 65  (% style="color:#037691" %)**Interface for Model: LT22222-L:**
... ... @@ -68,7 +68,7 @@
68 68  * 2 x Digital Output (NPN output. Max pull-up voltage 36V,450mA)
69 69  * 2 x Relay Output (5A@250VAC / 30VDC)
70 70  * 2 x 0~~20mA Analog Input (res:0.01mA)
71 -* 2 x 0~~30V Analog Input (res:0.01v)
69 +* 2 x 0~~30V Analog Input (res:0.01V)
72 72  * Power Input 7~~ 24V DC. 
73 73  
74 74  (% style="color:#037691" %)**LoRa Spec:**
... ... @@ -136,10 +136,10 @@
136 136  
137 137  * 1 x LT-22222-L I/O Controller
138 138  * 1 x LoRaWAN antenna matched to the frequency of the LT-22222-L
139 -* 1 x bracket for wall mounting
137 +* 1 x bracket for DIN rail mounting
140 140  * 1 x programming cable
141 141  
142 -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.
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.
143 143  
144 144  == 2.2 Terminals ==
145 145  
... ... @@ -171,7 +171,7 @@
171 171  
172 172  == 2.3 Powering the LT-22222-L ==
173 173  
174 -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.
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.
175 175  
176 176  
177 177  [[image:1653297104069-180.png]]
... ... @@ -183,13 +183,13 @@
183 183  
184 184  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.
185 185  
186 -For LT-22222-L, the LED will show the Join status: After powering on, the TX LED will fast-blink 5 times which means the LT-22222-L will enter the working 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 message from the server, the RX LED will be on for 1 second. 
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.
187 187  
188 188  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.
189 189  
190 190  == 3.2 Registering with a LoRaWAN network server ==
191 191  
192 -The diagram below shows how the LT-22222-L connects to a typical LoRaWAN network.
190 +The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
193 193  
194 194  [[image:image-20220523172350-1.png||height="266" width="864"]]
195 195  
... ... @@ -207,8 +207,11 @@
207 207  * Create an application if you do not have one yet.
208 208  * Register LT-22222-L with that application. Two registration options are available:
209 209  
210 -==== Using the LoRaWAN Device Repository: ====
208 +(% class="wikigeneratedid" %)
209 +==== ====
211 211  
211 +==== 3.2.2.1 Using the LoRaWAN Device Repository ====
212 +
212 212  * Go to your application and click on the **Register end device** button.
213 213  * On the **Register end device** page:
214 214  ** Select the option **Select the end device in the LoRaWAN Device Repository**.
... ... @@ -217,7 +217,8 @@
217 217  
218 218  [[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
219 219  
220 -*
221 +
222 +* Page continued...
221 221  ** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
222 222  ** Enter the **DevEUI** in the **DevEUI** field.
223 223  ** Enter the **AppKey** in the **AppKey** field.
... ... @@ -226,8 +226,11 @@
226 226  
227 227  [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
228 228  
229 -==== Entering device information manually: ====
231 +(% class="wikigeneratedid" %)
232 +==== ====
230 230  
234 +==== 3.2.2.2 Entering device information manually ====
235 +
231 231  * On the **Register end device** page:
232 232  ** Select the **Enter end device specifies manually** option as the input method.
233 233  ** Select the **Frequency plan** that matches your device.
... ... @@ -240,26 +240,49 @@
240 240  [[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
241 241  
242 242  
243 -* Enter **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
244 -* Enter **DevEUI** in the **DevEUI** field.
245 -* Enter **AppKey** in the **AppKey** field.
246 -* In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
247 -* Under **After registration**, select the **View registered end device** option.
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.
253 +** Under **After registration**, select the **View registered end device** option.
254 +** Click the **Register end device** button.
248 248  
249 249  [[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
250 250  
251 251  
252 -==== Joining ====
259 +You will be navigated to the **Device overview** page.
253 253  
254 -Click on **Live Data** in the left navigation. Then, power on the device, and it will join The Things Stack Sandbox. You can see the join request, join accept, followed by uplink messages form the device showing in the Live Data panel.
255 255  
256 -[[image:1653298044601-602.png||height="405" width="709"]]
262 +[[image:lt-22222-device-overview.png||height="625" width="1000"]]
257 257  
258 258  
265 +==== 3.2.2.3 Joining ====
266 +
267 +Click on **Live data** in the left navigation. The Live data panel for your application will display.
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 +
271 +
272 +[[image:lt-22222-join-network.png||height="625" width="1000"]]
273 +
274 +
275 +By default, you will receive an uplink data message every 10 minutes.
276 +
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 +
279 +[[image:lt-22222-ul-payload-decoded.png]]
280 +
281 +
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 +
284 +[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
285 +
286 +
259 259  == 3.3 Work Modes and their Uplink Payload formats ==
260 260  
261 261  
262 -The LT-22222-L has 5 **work modes**. It also has an interrupt/trigger mode for different types of applications that can be used together with any working mode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands.
290 +The LT-22222-L has 5 **work modes**. It also has an interrupt/trigger mode for different types of applications that can be used together with any work mode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands.
263 263  
264 264  * (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO
265 265  
... ... @@ -273,11 +273,16 @@
273 273  
274 274  * (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5
275 275  
304 +
305 +The uplink messages are sent over LoRaWAN FPort 2. By default, an uplink message is sent every 10 minutes.
306 +
276 276  === 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
277 277  
278 278  (((
279 -The uplink payload is 11 bytes long. Uplink messages are sent over LoRaWAN FPort 2. By default, one uplink is sent every 10 minutes. (% style="display:none" wfd-invisible="true" %)
310 +This is the default mode.
280 280  
312 +The uplink payload is 11 bytes long. (% style="display:none" wfd-invisible="true" %)
313 +
281 281  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
282 282  |(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**
283 283  |Value|(((
... ... @@ -324,13 +324,13 @@
324 324  
325 325  * [1] The RO1 relay channel is CLOSED, and the RO1 LED is ON.
326 326  * [0] The RO2 relay channel is OPEN, and the RO2 LED is OFF.
327 -* [1] DI3 - not used for LT-22222-L.
360 +* **[1] DI3 - not used for LT-22222-L.**
328 328  * [0] DI2 channel input is LOW, and the DI2 LED is OFF.
329 329  * [1] DI1 channel input state:
330 330  ** DI1 is FLOATING when no sensor is connected between DI1+ and DI1-.
331 331  ** DI1 is HIGH when a sensor is connected between DI1- and DI1+ and the sensor is ACTIVE.
332 332  ** DI1 LED is ON in both cases.
333 -* [0] DO3 - not used for LT-22222-L.
366 +* **[0] DO3 - not used for LT-22222-L.**
334 334  * [1] DO2 channel output is LOW, and the DO2 LED is ON.
335 335  * [0] DO1 channel output state:
336 336  ** DO1 is FLOATING when there is no load between DO1 and V+.
... ... @@ -355,7 +355,7 @@
355 355  )))
356 356  
357 357  (((
358 -(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, DO3, DO2 and DO1, and its size is 1 byte long as shown below.
391 +(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, FIRST, Reserve, Reserve, DO3, DO2 and DO1, and its size is 1 byte long as shown below.
359 359  
360 360  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
361 361  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
... ... @@ -783,9 +783,8 @@
783 783  
784 784  === 3.4.1 Common Commands ===
785 785  
786 -
787 787  (((
788 -They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.5.4, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
820 +These commands should be available for all Dragino sensors, such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]].
789 789  )))
790 790  
791 791  
... ... @@ -793,7 +793,6 @@
793 793  
794 794  ==== 3.4.2.1 Set Transmit Interval ====
795 795  
796 -
797 797  Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
798 798  
799 799  * (% style="color:#037691" %)**AT command:**
... ... @@ -1355,69 +1355,122 @@
1355 1355  
1356 1356  == 3.5 Integrating with ThingsEye.io ==
1357 1357  
1358 -If you are using one of The Things Stack plans, you can integrate ThingsEye.io with your application. 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.
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.
1359 1359  
1360 -=== 3.5.1 Configuring The Things Stack Sandbox ===
1391 +=== 3.5.1 Configuring MQTT Connection Information with The Things Stack Sandbox ===
1361 1361  
1362 -* Go to your Application and select MQTT under Integrations.
1363 -* In the Connection credentials section, under Username, The Thins Stack displays an auto-generated username. You can use it or provide a new one.
1364 -* For the Password, click the Generate new API key button to generate a password. You can see it by clicking on the eye button.
1393 +We use The Things Stack Sandbox for demonstating the configuration but  other
1365 1365  
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 +
1400 +NOTE. The username and  password (API key) you created here are required in the next section.
1401 +
1366 1366  [[image:tts-mqtt-integration.png||height="625" width="1000"]]
1367 1367  
1368 1368  === 3.5.2 Configuring ThingsEye.io ===
1369 1369  
1370 -* Login to your thingsEye.io account.
1371 -* Under the Integrations center, click Integrations.
1372 -* Click the Add integration button (the button with the + symbol).
1406 +This section guides you on how to create an integration in ThingsEye to connect with The Things Stack MQTT server.
1373 1373  
1408 +* Login to your [[ThingsEye.io >>https://thingseye.io]]account.
1409 +* Under the **Integrations center**, click **Integrations**.
1410 +* Click the **Add integration** button (the button with the **+** symbol).
1411 +
1374 1374  [[image:thingseye-io-step-1.png||height="625" width="1000"]]
1375 1375  
1376 1376  
1377 -On the Add integration page configure the following:
1415 +On the **Add integration** window, configure the following:
1378 1378  
1379 -Basic settings:
1417 +**Basic settings:**
1380 1380  
1381 -* Select The Things Stack Community from the Integration type list.
1382 -* Enter a suitable name for your integration in the Name box or keep the default name.
1383 -* Click the Next button.
1419 +* Select **The Things Stack Community** from the **Integration type** list.
1420 +* Enter a suitable name for your integration in the **Name **text** **box or keep the default name.
1421 +* Ensure the following options are turned on.
1422 +** Enable integration
1423 +** Debug mode
1424 +** Allow create devices or assets
1425 +* Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
1384 1384  
1385 1385  [[image:thingseye-io-step-2.png||height="625" width="1000"]]
1386 1386  
1387 -Uplink Data converter:
1388 1388  
1389 -* Click the Create New button if it is not selected by default.
1390 -* Click the JavaScript button.
1391 -* Paste the uplink decoder function into the text area (first, delete the default code). The demo decoder function can be found here.
1392 -* Click the Next button.
1430 +**Uplink data converter:**
1393 1393  
1432 +* Click the **Create new** button if it is not selected by default.
1433 +* Enter a suitable name for the uplink data converter in the **Name **text** **box or keep the default name.
1434 +* Click the **JavaScript** button.
1435 +* Paste the uplink decoder function into the text area (first, delete the default code). The demo uplink decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Uplink_Converter.js]].
1436 +* Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
1437 +
1394 1394  [[image:thingseye-io-step-3.png||height="625" width="1000"]]
1395 1395  
1396 -Downlink Data converter (this is an optional step):
1397 1397  
1398 -* Click the Create new button if it is not selected by default.
1399 -* Click the JavaScript button.
1400 -* Paste the downlink decoder function into the text area (first, delete the default code). The demo decoder function can be found here.
1401 -* Click the Next button.
1441 +**Downlink data converter (this is an optional step):**
1402 1402  
1443 +* Click the **Create new** button if it is not selected by default.
1444 +* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name
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.
1447 +* Click the **Next** button. You will be navigated to the **Connection** tab.
1448 +
1403 1403  [[image:thingseye-io-step-4.png||height="625" width="1000"]]
1404 1404  
1405 -Connection:
1406 1406  
1407 -* Choose Region from the Host type.
1408 -* Enter the cluster of your The Things Stack in the Region textbox.
1409 -* Enter the Username and Password in the Credentials section. Use the same username and password you created with the MQTT page of The Things Stack.
1410 -* Click Check connection to test the connection. If the connection is successful, you can see the message saying Connected.
1411 -* Click the Add button.
1452 +**Connection:**
1412 1412  
1454 +* Choose **Region** from the **Host type**.
1455 +* 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/...).
1456 +* 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 MQTT Connection information with The Things Stack Sandbox).
1457 +* Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
1458 +
1459 +[[image:message-1.png]]
1460 +
1461 +
1462 +* Click the **Add** button.
1463 +
1413 1413  [[image:thingseye-io-step-5.png||height="625" width="1000"]]
1414 1414  
1415 1415  
1416 -Your integration is added to the integrations list and it will display on the Integrations page.
1467 +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.
1417 1417  
1418 -[[image:thingseye-io-step-6.png||height="625" width="1000"]]
1419 1419  
1470 +[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
1420 1420  
1472 +
1473 +**Viewing integration details**:
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.
1476 +
1477 +[[image:integration-details.png||height="686" width="1000"]]
1478 +
1479 +
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 +
1482 +Note: See also ThingsEye documentation.
1483 +
1484 +
1485 +**Viewing events:**
1486 +
1487 +This tab  displays all the uplink messages from the LT-22222-L.
1488 +
1489 +* Click on the **Events **tab.
1490 +* Select **Debug **from the **Event type** dropdown.
1491 +* Select the** time frame** from the **time window**.
1492 +
1493 +[insert image]
1494 +
1495 +- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
1496 +
1497 +[insert image]
1498 +
1499 +
1500 +**Deleting the integration**:
1501 +
1502 +If you want to delete this integration, click the **Delete integratio**n button.
1503 +
1504 +
1421 1421  == 3.6 Interface Details ==
1422 1422  
1423 1423  === 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) ===
... ... @@ -1673,7 +1673,7 @@
1673 1673  
1674 1674  
1675 1675  (((
1676 -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]], SecureCRT) to a baud rate of (% style="color:green" %)**9600**(%%) to access to access 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:
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:
1677 1677  )))
1678 1678  
1679 1679  [[image:1653358355238-883.png]]
... ... @@ -2018,7 +2018,7 @@
2018 2018  
2019 2019  = 6. FAQ =
2020 2020  
2021 -== 6.1 How to upgrade the image? ==
2105 +== 6.1 How to upgrade the firmware image? ==
2022 2022  
2023 2023  
2024 2024  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:
... ... @@ -2027,20 +2027,25 @@
2027 2027  * Fix bugs.
2028 2028  * Change LoRaWAN bands.
2029 2029  
2030 -Below is the hardware connection setup for uploading an image to the LT:
2114 +Below is the hardware connection setup for uploading an firmware image to the LT-22222-L:
2031 2031  
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 +)))
2120 +
2032 2032  [[image:1653359603330-121.png]]
2033 2033  
2034 2034  
2035 2035  (((
2036 -(% 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]].
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)
2037 2037  (% 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]].
2038 2038  (% style="color:#0000ff" %)**Step 3**(%%)**:** Open the Flash Loader and choose the correct COM port to update.
2039 -
2040 2040  
2041 2041  (((
2042 2042  (% style="color:blue" %)**For LT-22222-L**(%%):
2043 -Hold down the PRO button, then momentarily press the RST reset button. The (% style="color:red" %)**DO1 LED**(%%) will change from OFF to ON. When the (% style="color:red" %)**DO1 LED**(%%) is ON, it indicates that the device is in download mode.
2131 +
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.
2044 2044  )))
2045 2045  
2046 2046  
integration-details.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +463.9 KB
Content
lt-22222-device-overview.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +497.2 KB
Content
lt-22222-join-network.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +340.6 KB
Content
lt-22222-ul-payload-decoded.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +48.7 KB
Content
lt-22222-ul-payload-fmt.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +438.6 KB
Content
message-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +20.1 KB
Content
thingseye.io_integrationsCenter_integrations-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +469.3 KB
Content
thingseye.io_integrationsCenter_integrations.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +302.3 KB
Content