Skip to Content
Last modified by Mengting Qiu on 2025/06/04 18:42
From version 223.1
edited by Dilisi S
on 2024/11/26 05:20
Change comment: Nov 25 edits
To version 216.1
edited by Dilisi S
on 2024/11/24 22:05
Change comment: Uploaded new attachment "usb-ttl-audio-jack-connection.jpg", version {1}

Summary

Details

Page properties
Content
... ... @@ -116,13 +116,13 @@
116 116  
117 117  == 1.5 Hardware Variants ==
118 118  
119 -(% style="width:650px" %)
120 -|(% style="width:94px" %)**Model**|(% style="width:172px" %)**Photo**|(% style="width:256px" %)**Description**
121 -|(% style="width:94px" %)**LT-33222-L**|(% style="width:172px" %)(((
122 -[[image:lt33222-l.jpg]]
123 -)))|(% style="width:256px" %)(((
124 -* 3 x Digital Input (Bi-direction)
125 -* 3 x Digital Output
119 +(% style="width:524px" %)
120 +|(% style="width:94px" %)**Model**|(% style="width:98px" %)**Photo**|(% style="width:329px" %)**Description**
121 +|(% style="width:94px" %)**LT33222-L**|(% style="width:98px" %)(((
122 +
123 +)))|(% style="width:329px" %)(((
124 +* 2 x Digital Input (Bi-direction)
125 +* 2 x Digital Output
126 126  * 2 x Relay Output (5A@250VAC / 30VDC)
127 127  * 2 x 0~~20mA Analog Input (res:0.01mA)
128 128  * 2 x 0~~30V Analog Input (res:0.01v)
... ... @@ -237,7 +237,7 @@
237 237  *** **Profile (Region)**: Select the region that matches your device.
238 238  ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
239 239  
240 -[[image:lt-22222-l-dev-repo-reg-p1.png]]
240 +[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
241 241  
242 242  
243 243  * Register end device page continued...
... ... @@ -247,7 +247,7 @@
247 247  ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
248 248  ** Under **After registration**, select the **View registered end device** option.
249 249  
250 -[[image:lt-22222-l-dev-repo-reg-p2.png]]
250 +[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
251 251  
252 252  
253 253  ==== 3.2.2.3 Adding device manually ====
... ... @@ -261,7 +261,7 @@
261 261  ** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
262 262  ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
263 263  
264 -[[image:lt-22222-l-manually-p1.png]]
264 +[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
265 265  
266 266  
267 267  * Register end device page continued...
... ... @@ -272,13 +272,13 @@
272 272  ** Under **After registration**, select the **View registered end device** option.
273 273  ** Click the **Register end device** button.
274 274  
275 -[[image:lt-22222-l-manually-p2.png]]
275 +[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
276 276  
277 277  
278 278  You will be navigated to the **Device overview** page.
279 279  
280 280  
281 -[[image:lt-22222-device-overview.png]]
281 +[[image:lt-22222-device-overview.png||height="625" width="1000"]]
282 282  
283 283  
284 284  ==== 3.2.2.4 Joining ====
... ... @@ -288,10 +288,9 @@
288 288  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.
289 289  
290 290  
291 -[[image:lt-22222-l-joining.png]]
291 +[[image:lt-22222-join-network.png||height="625" width="1000"]]
292 292  
293 293  
294 -
295 295  ==== 3.2.2.5 Uplinks ====
296 296  
297 297  
... ... @@ -308,7 +308,7 @@
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.
309 309  {{/info}}
310 310  
311 -[[image:lt-22222-ul-payload-fmt.png]]
310 +[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
312 312  
313 313  
314 314  ==== 3.2.2.6 Downlinks ====
... ... @@ -599,11 +599,11 @@
599 599  
600 600  (% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)**
601 601  
602 -(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), the counter increases by 1)**
601 +(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
603 603  
604 -(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If the AVI1 voltage is lower than VOLMAX (20000mV =20V), counter increases by 1)**
603 +(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
605 605  
606 -(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), counter increases by 1)**
605 +(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
607 607  )))
608 608  
609 609  
... ... @@ -722,9 +722,9 @@
722 722  
723 723  (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
724 724  
725 -**Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
724 +Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
726 726  
727 -**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
726 +Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
728 728  
729 729   AA: Type Code for this downlink Command:
730 730  
... ... @@ -791,7 +791,7 @@
791 791  
792 792  **Example:**
793 793  
794 -10100000: This means the system is configured to use the triggers AV1_LOW and AV2_LOW.
793 +10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW
795 795  
796 796  
797 797  (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
... ... @@ -820,7 +820,7 @@
820 820  
821 821  **Example:**
822 822  
823 -10000000: The uplink is triggered by AV1_LOW, indicating that the voltage is too low.
822 +10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.
824 824  
825 825  
826 826  (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
... ... @@ -829,22 +829,22 @@
829 829  |(% style="width:64px" %)**bit 7**|(% style="width:68px" %)**bit 6**|(% style="width:63px" %)**bit 5**|(% style="width:66px" %)**bit 4**|(% style="width:109px" %)**bit 3**|(% style="width:93px" %)**bit 2**|(% style="width:109px" %)**bit 1**|(% style="width:99px" %)**bit 0**
830 830  |(% style="width:64px" %)N/A|(% style="width:68px" %)N/A|(% style="width:63px" %)N/A|(% style="width:66px" %)N/A|(% style="width:109px" %)DI2_STATUS|(% style="width:93px" %)DI2_FLAG|(% style="width:109px" %)DI1_STATUS|(% style="width:99px" %)DI1_FLAG
831 831  
832 -* Each bit shows which status has been triggered on this uplink.
831 +* Each bits shows which status has been triggered on this uplink.
833 833  
834 834  **Example:**
835 835  
836 -00000111: This means both DI1 and DI2 triggers are enabled, and this packet is trigger by DI1.
835 +00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
837 837  
838 -00000101: This means both DI1 and DI2 triggers are enabled.
837 +00000101: Means both DI1 and DI2 trigger are enabled.
839 839  
840 840  
841 -(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled.
840 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable.
842 842  
843 -Downlink command to poll/request MOD6 status:
842 +Downlink command to poll MOD6 status:
844 844  
845 845  **AB 06**
846 846  
847 -When device receives this command, it will send the MOD6 payload.
846 +When device got this command, it will send the MOD6 payload.
848 848  
849 849  
850 850  === 3.3.7 Payload Decoder ===
... ... @@ -968,7 +968,7 @@
968 968  Sets the device to working mode 2 (Double DI Counting + DO + RO)
969 969  )))
970 970  
971 -==== 3.4.2.3 Request an uplink from the device ====
970 +==== 3.4.2.3 Poll an uplink ====
972 972  
973 973  Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.
974 974  
... ... @@ -1024,9 +1024,9 @@
1024 1024  Enable trigger mode for the current working mode
1025 1025  )))
1026 1026  
1027 -==== 3.4.2.5 Request trigger settings ====
1026 +==== 3.4.2.5 Poll trigger settings ====
1028 1028  
1029 -Requests the trigger settings.
1028 +Polls the trigger settings.
1030 1030  
1031 1031  (% style="color:#037691" %)**AT Command:**
1032 1032  
... ... @@ -1356,23 +1356,25 @@
1356 1356  
1357 1357  * (% style="color:#037691" %)**AT Command**
1358 1358  
1359 -There is no AT command to control the digital output.
1358 +There is no AT Command to control Digital Output
1360 1360  
1361 1361  
1362 1362  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
1363 1363  
1364 -(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control
1363 +(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Set DO1/DO2/DO3 output with time control
1365 1365  
1365 +
1366 1366  This is to control the digital output time of DO pin. Include four bytes:
1367 1367  
1368 -(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)
1368 +(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
1369 1369  
1370 -(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode
1370 +(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode
1371 1371  
1372 -**01:** DO pins revert to their original state after the timeout.
1373 -**00:** DO pins switch to an inverted state after the timeout.
1372 +01: DO pins will change back to original state after timeout.
1374 1374  
1374 +00: DO pins will change to an inverter state after timeout 
1375 1375  
1376 +
1376 1376  (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
1377 1377  
1378 1378  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
... ... @@ -1381,7 +1381,7 @@
1381 1381  |0x00|DO1 set to high
1382 1382  |0x11|DO1 NO Action
1383 1383  
1384 -(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:
1385 +(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:
1385 1385  
1386 1386  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1387 1387  |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
... ... @@ -1389,7 +1389,7 @@
1389 1389  |0x00|DO2 set to high
1390 1390  |0x11|DO2 NO Action
1391 1391  
1392 -(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:
1393 +(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:
1393 1393  
1394 1394  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1395 1395  |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
... ... @@ -1397,7 +1397,7 @@
1397 1397  |0x00|DO3 set to high
1398 1398  |0x11|DO3 NO Action
1399 1399  
1400 -(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms)
1401 +(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)
1401 1401  
1402 1402  
1403 1403  (% style="color:red" %)**Note: **
... ... @@ -1406,7 +1406,7 @@
1406 1406  
1407 1407   Before firmware v1.6.0, the latch time only supported 2 bytes.
1408 1408  
1409 -(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1410 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1410 1410  
1411 1411  
1412 1412  **Example payload:**
... ... @@ -1433,16 +1433,16 @@
1433 1433  
1434 1434  * (% style="color:#037691" %)**AT Command:**
1435 1435  
1436 -There is no AT Command to control the Relay Output
1437 +There is no AT Command to control Relay Output
1437 1437  
1438 1438  
1439 1439  * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
1440 1440  
1441 -(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Sets RO1/RO2 output
1442 +(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Set RO1/RO2 output
1442 1442  
1443 1443  
1444 1444  (((
1445 -If the payload is 0x030100, it means setting RO1 to close and RO2 to open.
1446 +If payload is 0x030100, it means setting RO1 to close and RO2 to open.
1446 1446  )))
1447 1447  
1448 1448  (((
... ... @@ -1460,7 +1460,7 @@
1460 1460  |03  00  01|Open|Close
1461 1461  )))
1462 1462  
1463 -(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1464 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
1464 1464  
1465 1465  
1466 1466  ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
... ... @@ -1469,19 +1469,19 @@
1469 1469  
1470 1470  * (% style="color:#037691" %)**AT Command:**
1471 1471  
1472 -There is no AT Command to control the Relay Output
1473 +There is no AT Command to control Relay Output
1473 1473  
1474 1474  
1475 1475  * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1476 1476  
1477 -(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
1478 +(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Set RO1/RO2 relay with time control
1478 1478  
1479 1479  
1480 -This controls the relay output time and includes 4 bytes:
1481 +This is to control the relay output time. It includes four bytes:
1481 1481  
1482 -(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)
1483 +(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
1483 1483  
1484 -(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode
1485 +(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
1485 1485  
1486 1486  01: Relays will change back to their original state after timeout.
1487 1487  
... ... @@ -1488,12 +1488,12 @@
1488 1488  00: Relays will change to the inverter state after timeout.
1489 1489  
1490 1490  
1491 -(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status:
1492 +(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
1492 1492  
1493 1493  [[image:image-20221008095908-1.png||height="364" width="564"]]
1494 1494  
1495 1495  
1496 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes (cc)**(%%): Latching time. Unit: ms
1497 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms
1497 1497  
1498 1498  
1499 1499  (% style="color:red" %)**Note:**
... ... @@ -1503,7 +1503,7 @@
1503 1503   Before firmware v1.6.0, the latch time only supported 2 bytes.
1504 1504  
1505 1505  
1506 -(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1507 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1507 1507  
1508 1508  
1509 1509  **Example payload:**
... ... @@ -1662,7 +1662,7 @@
1662 1662  )))
1663 1663  |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
1664 1664  
1665 -==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ====
1666 +==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1666 1666  
1667 1667  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.
1668 1668  
... ... @@ -1693,7 +1693,7 @@
1693 1693  Sets the device to save its counting results to the memory every 60 seconds.
1694 1694  )))
1695 1695  
1696 -==== 3.4.2.20 Reset saved RO and DO states ====
1697 +==== 3.4.2.20 Reset save RO DO state ====
1697 1697  
1698 1698  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.
1699 1699  
... ... @@ -1719,6 +1719,7 @@
1719 1719  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.
1720 1720  )))
1721 1721  
1723 +
1722 1722  (% style="color:#037691" %)**Downlink Payload**
1723 1723  
1724 1724  (% border="2" style="width:500px" %)
... ... @@ -1950,7 +1950,7 @@
1950 1950  The username and  password (API key) you created here are required in the next section.
1951 1951  {{/info}}
1952 1952  
1953 -[[image:tts-mqtt-integration.png]]
1955 +[[image:tts-mqtt-integration.png||height="625" width="1000"]]
1954 1954  
1955 1955  === 3.5.2 Configuring ThingsEye.io ===
1956 1956  
... ... @@ -1960,7 +1960,7 @@
1960 1960  * Under the **Integrations center**, click **Integrations**.
1961 1961  * Click the **Add integration** button (the button with the **+** symbol).
1962 1962  
1963 -[[image:thingseye-io-step-1.png]]
1965 +[[image:thingseye-io-step-1.png||height="625" width="1000"]]
1964 1964  
1965 1965  
1966 1966  On the **Add integration** window, configure the following:
... ... @@ -1975,7 +1975,7 @@
1975 1975  ** Allow create devices or assets
1976 1976  * Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
1977 1977  
1978 -[[image:thingseye-io-step-2.png]]
1980 +[[image:thingseye-io-step-2.png||height="625" width="1000"]]
1979 1979  
1980 1980  
1981 1981  **Uplink data converter:**
... ... @@ -1986,7 +1986,7 @@
1986 1986  * 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]].
1987 1987  * Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
1988 1988  
1989 -[[image:thingseye-io-step-3.png]]
1991 +[[image:thingseye-io-step-3.png||height="625" width="1000"]]
1990 1990  
1991 1991  
1992 1992  **Downlink data converter (this is an optional step):**
... ... @@ -1997,7 +1997,7 @@
1997 1997  * 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]].
1998 1998  * Click the **Next** button. You will be navigated to the **Connection** tab.
1999 1999  
2000 -[[image:thingseye-io-step-4.png]]
2002 +[[image:thingseye-io-step-4.png||height="625" width="1000"]]
2001 2001  
2002 2002  
2003 2003  **Connection:**
... ... @@ -2012,13 +2012,13 @@
2012 2012  
2013 2013  * Click the **Add** button.
2014 2014  
2015 -[[image:thingseye-io-step-5.png]]
2017 +[[image:thingseye-io-step-5.png||height="625" width="1000"]]
2016 2016  
2017 2017  
2018 2018  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.
2019 2019  
2020 2020  
2021 -[[image:thingseye.io_integrationsCenter_integrations.png]]
2023 +[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
2022 2022  
2023 2023  
2024 2024  ==== 3.5.2.1 Viewing integration details ====
... ... @@ -2025,7 +2025,7 @@
2025 2025  
2026 2026  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.
2027 2027  
2028 -[[image:integration-details.png]]
2030 +[[image:integration-details.png||height="686" width="1000"]]
2029 2029  
2030 2030  
2031 2031  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.
... ... @@ -2041,12 +2041,12 @@
2041 2041  * Select **Debug **from the **Event type** dropdown.
2042 2042  * Select the** time frame** from the **time window**.
2043 2043  
2044 -[[image:thingseye-events.png]]
2046 +[[image:thingseye-events.png||height="686" width="1000"]]
2045 2045  
2046 2046  
2047 2047  * To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
2048 2048  
2049 -[[image:thingseye-json.png]]
2051 +[[image:thingseye-json.png||width="1000"]]
2050 2050  
2051 2051  
2052 2052  ==== **3.5.2.3 Deleting an integration** ====
... ... @@ -2064,7 +2064,7 @@
2064 2064  === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
2065 2065  
2066 2066  
2067 -Supports** NPN-type **sensors.
2069 +Supports NPN-type sensors.
2068 2068  
2069 2069  [[image:1653356991268-289.png]]
2070 2070  
... ... @@ -2186,15 +2186,15 @@
2186 2186  )))
2187 2187  
2188 2188  
2189 -(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor
2191 +(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
2190 2190  
2191 -From the DI port circuit above, activating the photocoupler requires a voltage difference between the DI+ and DI- ports. However, the Dry Contact sensor is a passive component and cannot provide this voltage difference on its own.
2193 +From the DI port circuit above, you can see that activating the photocoupler requires a voltage difference between the DI+ and DI- ports. However, the Dry Contact sensor is a passive component and cannot provide this voltage difference.
2192 2192  
2193 -To detect a Dry Contact, you can supply a power source to one of the pins of the Dry Contact. A reference circuit diagram is shown below.
2195 +To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram.
2194 2194  
2195 2195  [[image:image-20230616235145-1.png]]
2196 2196  
2197 -(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector
2199 +(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
2198 2198  
2199 2199  [[image:image-20240219115718-1.png]]
2200 2200  
... ... @@ -2270,7 +2270,7 @@
2270 2270  [[image:image-20220524100215-10.png||height="382" width="723"]]
2271 2271  
2272 2272  
2273 -== 3.7 LED Indicators ==
2275 +== 3.7 LEDs Indicators ==
2274 2274  
2275 2275  The table below lists the behavior of LED indicators for each port function.
2276 2276  
... ... @@ -2309,14 +2309,13 @@
2309 2309  == 4.1 Connecting the LT-22222-L to a PC ==
2310 2310  
2311 2311  (((
2312 -You can use a USB-to-TTL adapter/converter along with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below.
2314 +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.
2313 2313  
2314 -[[image:usb-ttl-audio-jack-connection.jpg]]
2315 -
2316 -
2316 +[[image:usb-ttl-programming.png]]
2317 2317  )))
2318 2318  
2319 2319  
2320 +
2320 2320  (((
2321 2321  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:
2322 2322  )))
... ... @@ -2346,39 +2346,39 @@
2346 2346  * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
2347 2347  * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
2348 2348  * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
2349 -* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2350 -* **##AT+DR##**:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
2351 -* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2352 -* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)
2353 -* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency
2354 -* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2355 -* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2356 -* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2357 -* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2358 -* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2359 -* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2360 -* ##**AT+NWKID**##: Get or set the Network ID
2361 -* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)
2362 -* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)
2363 -* ##**AT+CLASS**##: Get or set the Device Class
2364 -* ##**AT+JOIN**##: Join network
2365 -* ##**AT+NJS**##: Get OTAA Join Status
2366 -* ##**AT+SENDB**##: Send hexadecimal data along with the application port
2367 -* ##**AT+SEND**##: Send text data along with the application port
2368 -* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)
2369 -* ##**AT+RECV**##: Print last received data in raw format
2370 -* ##**AT+VER**##: Get current image version and Frequency Band
2371 -* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)
2372 -* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)
2373 -* ##**AT+SNR**##: Get the SNR of the last received packet
2374 -* ##**AT+RSSI**##: Get the RSSI of the last received packet
2375 -* ##**AT+TDC**##: Get or set the application data transmission interval in ms
2376 -* ##**AT+PORT**##: Get or set the application port
2377 -* ##**AT+DISAT**##: Disable AT commands
2378 -* ##**AT+PWORD**##: Set password, max 9 digits
2379 -* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2380 -* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN470
2381 -* ##**AT+CFG**##: Print all settings
2350 +* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2351 +* AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
2352 +* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2353 +* AT+PNM: Get or set the public network mode. (0: off, 1: on)
2354 +* AT+RX2FQ: Get or set the Rx2 window frequency
2355 +* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2356 +* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2357 +* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2358 +* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2359 +* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2360 +* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2361 +* AT+NWKID: Get or set the Network ID
2362 +* AT+FCU: Get or set the Frame Counter Uplink (FCntUp)
2363 +* AT+FCD: Get or set the Frame Counter Downlink (FCntDown)
2364 +* AT+CLASS: Get or set the Device Class
2365 +* AT+JOIN: Join network
2366 +* AT+NJS: Get OTAA Join Status
2367 +* AT+SENDB: Send hexadecimal data along with the application port
2368 +* AT+SEND: Send text data along with the application port
2369 +* AT+RECVB: Print last received data in binary format (with hexadecimal values)
2370 +* AT+RECV: Print last received data in raw format
2371 +* AT+VER: Get current image version and Frequency Band
2372 +* AT+CFM: Get or Set the confirmation mode (0-1)
2373 +* AT+CFS: Get confirmation status of the last AT+SEND (0-1)
2374 +* AT+SNR: Get the SNR of the last received packet
2375 +* AT+RSSI: Get the RSSI of the last received packet
2376 +* AT+TDC: Get or set the application data transmission interval in ms
2377 +* AT+PORT: Get or set the application port
2378 +* AT+DISAT: Disable AT commands
2379 +* AT+PWORD: Set password, max 9 digits
2380 +* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2381 +* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470
2382 +* AT+CFG: Print all settings
2382 2382  )))
2383 2383  
2384 2384  
... ... @@ -2543,7 +2543,7 @@
2543 2543  You will need the following things before proceeding:
2544 2544  
2545 2545  * 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
2546 -* USB to TTL adapter/converter
2547 +* USB to TTL adapter
2547 2547  * 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)
2548 2548  * 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.
2549 2549  
... ... @@ -2553,7 +2553,7 @@
2553 2553  
2554 2554  Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2555 2555  
2556 -[[image:usb-ttl-audio-jack-connection.jpg]]
2557 +[[image:usb-ttl-programming.png]]
2557 2557  
2558 2558  
2559 2559  
lt-22222-l-joining.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -301.9 KB
Content
lt33222-l.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -31.3 KB
Content