Changes for page LT-22222-L -- LoRa I/O Controller User Manual
Last modified by Mengting Qiu on 2025/06/04 18:42
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.pradeeka - Content
-
... ... @@ -54,10 +54,8 @@ 54 54 (% class="wikigeneratedid" %) 55 55 [[image:lorawan-nw.jpg||height="354" width="900"]] 56 56 57 - 58 58 == 1.2 Specifications == 59 59 60 - 61 61 (% style="color:#037691" %)**Hardware System:** 62 62 63 63 * STM32L072xxxx MCU ... ... @@ -118,15 +118,13 @@ 118 118 119 119 == 1.5 Hardware Variants == 120 120 121 - 122 -(% border="1" cellspacing="3" style="width:510px" %) 123 -|(% style="width:94px" %)**Model**|(% style="width:172px" %)**Photo**|(% style="width:244px" %)**Description** 124 -|(% style="width:94px" %)**LT-33222-L**|(% style="width:172px" %)((( 125 -(% style="text-align:center" %) 126 -[[image:lt33222-l.jpg||height="139" width="120"]] 127 -)))|(% style="width:256px" %)((( 128 -* 3 x Digital Input (Bi-direction) 129 -* 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 130 130 * 2 x Relay Output (5A@250VAC / 30VDC) 131 131 * 2 x 0~~20mA Analog Input (res:0.01mA) 132 132 * 2 x 0~~30V Analog Input (res:0.01v) ... ... @@ -241,7 +241,7 @@ 241 241 *** **Profile (Region)**: Select the region that matches your device. 242 242 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 243 243 244 -[[image:lt-22222-l-dev-repo-reg-p1.png]] 240 +[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]] 245 245 246 246 247 247 * Register end device page continued... ... ... @@ -251,7 +251,7 @@ 251 251 ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. 252 252 ** Under **After registration**, select the **View registered end device** option. 253 253 254 -[[image:lt-22222-l-dev-repo-reg-p2.png]] 250 +[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]] 255 255 256 256 257 257 ==== 3.2.2.3 Adding device manually ==== ... ... @@ -265,7 +265,7 @@ 265 265 ** Select the option **Over the air activation (OTAA)** under the **Activation mode.** 266 266 ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list. 267 267 268 -[[image:lt-22222-l-manually-p1.png]] 264 +[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]] 269 269 270 270 271 271 * Register end device page continued... ... ... @@ -276,13 +276,13 @@ 276 276 ** Under **After registration**, select the **View registered end device** option. 277 277 ** Click the **Register end device** button. 278 278 279 -[[image:lt-22222-l-manually-p2.png]] 275 +[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]] 280 280 281 281 282 282 You will be navigated to the **Device overview** page. 283 283 284 284 285 -[[image:lt-22222-device-overview.png]] 281 +[[image:lt-22222-device-overview.png||height="625" width="1000"]] 286 286 287 287 288 288 ==== 3.2.2.4 Joining ==== ... ... @@ -292,10 +292,9 @@ 292 292 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. 293 293 294 294 295 -[[image:lt-22222- l-joining.png]]291 +[[image:lt-22222-join-network.png||height="625" width="1000"]] 296 296 297 297 298 - 299 299 ==== 3.2.2.5 Uplinks ==== 300 300 301 301 ... ... @@ -312,7 +312,7 @@ 312 312 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. 313 313 {{/info}} 314 314 315 -[[image:lt-22222-ul-payload-fmt.png]] 310 +[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]] 316 316 317 317 318 318 ==== 3.2.2.6 Downlinks ==== ... ... @@ -603,11 +603,11 @@ 603 603 604 604 (% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)** 605 605 606 -(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If theAVI1 voltageishigher than VOLMAX (20000mV =20V),thecounter increasesby1)**601 +(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 607 607 608 -(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If theAVI1 voltageislower than VOLMAX (20000mV =20V), counter increasesby1)**603 +(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)** 609 609 610 -(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If theAVI1 voltageishigher than VOLMAX (20000mV =20V), counter increasesby1)**605 +(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 611 611 ))) 612 612 613 613 ... ... @@ -726,9 +726,9 @@ 726 726 727 727 (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:** 728 728 729 - **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** 730 730 731 - **Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4726 +Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4 732 732 733 733 AA: Type Code for this downlink Command: 734 734 ... ... @@ -795,7 +795,7 @@ 795 795 796 796 **Example:** 797 797 798 -10100000: This means the systemis configuredto use the triggersAV1_LOW and AV2_LOW.793 +10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW 799 799 800 800 801 801 (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below ... ... @@ -824,7 +824,7 @@ 824 824 825 825 **Example:** 826 826 827 -10000000: The uplink is triggered by AV1_LOW,indicatingthatthe voltage is too low.822 +10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low. 828 828 829 829 830 830 (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below ... ... @@ -833,22 +833,22 @@ 833 833 |(% 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** 834 834 |(% 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 835 835 836 -* Each bit shows which status has been triggered on this uplink. 831 +* Each bits shows which status has been triggered on this uplink. 837 837 838 838 **Example:** 839 839 840 -00000111: This means both DI1 and DI2 triggersare 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. 841 841 842 -00000101: This means both DI1 and DI2 triggersare enabled.837 +00000101: Means both DI1 and DI2 trigger are enabled. 843 843 844 844 845 -(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable d. 0x00: MOD6 is disabled.840 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable. 846 846 847 -Downlink command to poll /requestMOD6 status:842 +Downlink command to poll MOD6 status: 848 848 849 849 **AB 06** 850 850 851 -When device receivesthis command, it will send the MOD6 payload.846 +When device got this command, it will send the MOD6 payload. 852 852 853 853 854 854 === 3.3.7 Payload Decoder === ... ... @@ -972,7 +972,7 @@ 972 972 Sets the device to working mode 2 (Double DI Counting + DO + RO) 973 973 ))) 974 974 975 -==== 3.4.2.3 Requestan uplinkfrom the device====970 +==== 3.4.2.3 Poll an uplink ==== 976 976 977 977 Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode. 978 978 ... ... @@ -1028,9 +1028,9 @@ 1028 1028 Enable trigger mode for the current working mode 1029 1029 ))) 1030 1030 1031 -==== 3.4.2.5 Requesttrigger settings ====1026 +==== 3.4.2.5 Poll trigger settings ==== 1032 1032 1033 - Requeststhe trigger settings.1028 +Polls the trigger settings. 1034 1034 1035 1035 (% style="color:#037691" %)**AT Command:** 1036 1036 ... ... @@ -1360,23 +1360,25 @@ 1360 1360 1361 1361 * (% style="color:#037691" %)**AT Command** 1362 1362 1363 -There is no AT command to controlthe digitaloutput.1358 +There is no AT Command to control Digital Output 1364 1364 1365 1365 1366 1366 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)** 1367 1367 1368 -(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Set sDO1/DO2/DO3 outputswith time control1363 +(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Set DO1/DO2/DO3 output with time control 1369 1369 1365 + 1370 1370 This is to control the digital output time of DO pin. Include four bytes: 1371 1371 1372 -(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)1368 +(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9) 1373 1373 1374 -(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode1370 +(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode 1375 1375 1376 -**01:** DO pins revert to their original state after the timeout. 1377 -**00:** DO pins switch to an inverted state after the timeout. 1372 +01: DO pins will change back to original state after timeout. 1378 1378 1374 +00: DO pins will change to an inverter state after timeout 1379 1379 1376 + 1380 1380 (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status: 1381 1381 1382 1382 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) ... ... @@ -1385,7 +1385,7 @@ 1385 1385 |0x00|DO1 set to high 1386 1386 |0x11|DO1 NO Action 1387 1387 1388 -(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:1385 +(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status: 1389 1389 1390 1390 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1391 1391 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1393,7 +1393,7 @@ 1393 1393 |0x00|DO2 set to high 1394 1394 |0x11|DO2 NO Action 1395 1395 1396 -(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:1393 +(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status: 1397 1397 1398 1398 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1399 1399 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1401,7 +1401,7 @@ 1401 1401 |0x00|DO3 set to high 1402 1402 |0x11|DO3 NO Action 1403 1403 1404 -(% 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) 1405 1405 1406 1406 1407 1407 (% style="color:red" %)**Note: ** ... ... @@ -1410,7 +1410,7 @@ 1410 1410 1411 1411 Before firmware v1.6.0, the latch time only supported 2 bytes. 1412 1412 1413 -(% style="color:red" %)** Thedevice will uplinka packet if the downlink code executes successfully.**1410 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.** 1414 1414 1415 1415 1416 1416 **Example payload:** ... ... @@ -1437,16 +1437,16 @@ 1437 1437 1438 1438 * (% style="color:#037691" %)**AT Command:** 1439 1439 1440 -There is no AT Command to control theRelay Output1437 +There is no AT Command to control Relay Output 1441 1441 1442 1442 1443 1443 * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):** 1444 1444 1445 -(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set sRO1/RO2 output1442 +(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set RO1/RO2 output 1446 1446 1447 1447 1448 1448 ((( 1449 -If thepayload 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. 1450 1450 ))) 1451 1451 1452 1452 ((( ... ... @@ -1464,7 +1464,7 @@ 1464 1464 |03 00 01|Open|Close 1465 1465 ))) 1466 1466 1467 -(% style="color:red" %)** Thedevice will uplinka packet ifthedownlink code executes successfully.**1464 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1468 1468 1469 1469 1470 1470 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== ... ... @@ -1473,19 +1473,19 @@ 1473 1473 1474 1474 * (% style="color:#037691" %)**AT Command:** 1475 1475 1476 -There is no AT Command to control theRelay Output1473 +There is no AT Command to control Relay Output 1477 1477 1478 1478 1479 1479 * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):** 1480 1480 1481 -(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set sRO1/RO2 relayswith time control1478 +(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set RO1/RO2 relay with time control 1482 1482 1483 1483 1484 -This control sthe relay output timeandincludes4bytes:1481 +This is to control the relay output time. It includes four bytes: 1485 1485 1486 -(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)1483 +(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05) 1487 1487 1488 -(% style="color:#4f81bd" %)**Second byte1485 +(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode 1489 1489 1490 1490 01: Relays will change back to their original state after timeout. 1491 1491 ... ... @@ -1492,12 +1492,12 @@ 1492 1492 00: Relays will change to the inverter state after timeout. 1493 1493 1494 1494 1495 -(% style="color:#4f81bd" %)**Third byte1492 +(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status: 1496 1496 1497 1497 [[image:image-20221008095908-1.png||height="364" width="564"]] 1498 1498 1499 1499 1500 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes1497 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms 1501 1501 1502 1502 1503 1503 (% style="color:red" %)**Note:** ... ... @@ -1507,7 +1507,7 @@ 1507 1507 Before firmware v1.6.0, the latch time only supported 2 bytes. 1508 1508 1509 1509 1510 -(% style="color:red" %)** Thedevice will uplinka packet if the downlink code executes successfully.**1507 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.** 1511 1511 1512 1512 1513 1513 **Example payload:** ... ... @@ -1666,7 +1666,7 @@ 1666 1666 ))) 1667 1667 |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01** 1668 1668 1669 -==== 3.4.2.19 Counting ~-~- Set SavingIntervalfor 'CountingResult'====1666 +==== 3.4.2.19 Counting ~-~- Change counting mode to save time ==== 1670 1670 1671 1671 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. 1672 1672 ... ... @@ -1697,7 +1697,7 @@ 1697 1697 Sets the device to save its counting results to the memory every 60 seconds. 1698 1698 ))) 1699 1699 1700 -==== 3.4.2.20 Reset save dROandDO states====1697 +==== 3.4.2.20 Reset save RO DO state ==== 1701 1701 1702 1702 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. 1703 1703 ... ... @@ -1723,6 +1723,7 @@ 1723 1723 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. 1724 1724 ))) 1725 1725 1723 + 1726 1726 (% style="color:#037691" %)**Downlink Payload** 1727 1727 1728 1728 (% border="2" style="width:500px" %) ... ... @@ -1954,7 +1954,7 @@ 1954 1954 The username and password (API key) you created here are required in the next section. 1955 1955 {{/info}} 1956 1956 1957 -[[image:tts-mqtt-integration.png]] 1955 +[[image:tts-mqtt-integration.png||height="625" width="1000"]] 1958 1958 1959 1959 === 3.5.2 Configuring ThingsEye.io === 1960 1960 ... ... @@ -1964,7 +1964,7 @@ 1964 1964 * Under the **Integrations center**, click **Integrations**. 1965 1965 * Click the **Add integration** button (the button with the **+** symbol). 1966 1966 1967 -[[image:thingseye-io-step-1.png]] 1965 +[[image:thingseye-io-step-1.png||height="625" width="1000"]] 1968 1968 1969 1969 1970 1970 On the **Add integration** window, configure the following: ... ... @@ -1979,7 +1979,7 @@ 1979 1979 ** Allow create devices or assets 1980 1980 * Click the **Next** button. you will be navigated to the **Uplink data converter** tab. 1981 1981 1982 -[[image:thingseye-io-step-2.png]] 1980 +[[image:thingseye-io-step-2.png||height="625" width="1000"]] 1983 1983 1984 1984 1985 1985 **Uplink data converter:** ... ... @@ -1990,7 +1990,7 @@ 1990 1990 * 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]]. 1991 1991 * Click the **Next** button. You will be navigated to the **Downlink data converter **tab. 1992 1992 1993 -[[image:thingseye-io-step-3.png]] 1991 +[[image:thingseye-io-step-3.png||height="625" width="1000"]] 1994 1994 1995 1995 1996 1996 **Downlink data converter (this is an optional step):** ... ... @@ -2001,7 +2001,7 @@ 2001 2001 * 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]]. 2002 2002 * Click the **Next** button. You will be navigated to the **Connection** tab. 2003 2003 2004 -[[image:thingseye-io-step-4.png]] 2002 +[[image:thingseye-io-step-4.png||height="625" width="1000"]] 2005 2005 2006 2006 2007 2007 **Connection:** ... ... @@ -2016,13 +2016,13 @@ 2016 2016 2017 2017 * Click the **Add** button. 2018 2018 2019 -[[image:thingseye-io-step-5.png]] 2017 +[[image:thingseye-io-step-5.png||height="625" width="1000"]] 2020 2020 2021 2021 2022 2022 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. 2023 2023 2024 2024 2025 -[[image:thingseye.io_integrationsCenter_integrations.png]] 2023 +[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]] 2026 2026 2027 2027 2028 2028 ==== 3.5.2.1 Viewing integration details ==== ... ... @@ -2029,7 +2029,7 @@ 2029 2029 2030 2030 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. 2031 2031 2032 -[[image:integration-details.png]] 2030 +[[image:integration-details.png||height="686" width="1000"]] 2033 2033 2034 2034 2035 2035 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. ... ... @@ -2045,12 +2045,12 @@ 2045 2045 * Select **Debug **from the **Event type** dropdown. 2046 2046 * Select the** time frame** from the **time window**. 2047 2047 2048 -[[image:thingseye-events.png]] 2046 +[[image:thingseye-events.png||height="686" width="1000"]] 2049 2049 2050 2050 2051 2051 * To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message. 2052 2052 2053 -[[image:thingseye-json.png]] 2051 +[[image:thingseye-json.png||width="1000"]] 2054 2054 2055 2055 2056 2056 ==== **3.5.2.3 Deleting an integration** ==== ... ... @@ -2068,7 +2068,7 @@ 2068 2068 === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) === 2069 2069 2070 2070 2071 -Supports **NPN-type**sensors.2069 +Supports NPN-type sensors. 2072 2072 2073 2073 [[image:1653356991268-289.png]] 2074 2074 ... ... @@ -2190,15 +2190,15 @@ 2190 2190 ))) 2191 2191 2192 2192 2193 -(% style="color:blue" %)**Example aDry Contact sensor2191 +(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor 2194 2194 2195 -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. 2196 2196 2197 -To detect a Dry Contact, you can supply a power source to one of thepinsof the Dry Contact.Areference circuit diagramis 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. 2198 2198 2199 2199 [[image:image-20230616235145-1.png]] 2200 2200 2201 -(% style="color:blue" %)**Example 2199 +(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector 2202 2202 2203 2203 [[image:image-20240219115718-1.png]] 2204 2204 ... ... @@ -2274,7 +2274,7 @@ 2274 2274 [[image:image-20220524100215-10.png||height="382" width="723"]] 2275 2275 2276 2276 2277 -== 3.7 LED Indicators == 2275 +== 3.7 LEDs Indicators == 2278 2278 2279 2279 The table below lists the behavior of LED indicators for each port function. 2280 2280 ... ... @@ -2313,14 +2313,13 @@ 2313 2313 == 4.1 Connecting the LT-22222-L to a PC == 2314 2314 2315 2315 ((( 2316 -You can use a USB-to-TTL adapter /converteralong 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. 2317 2317 2318 -[[image:usb-ttl-audio-jack-connection.jpg]] 2319 - 2320 - 2316 +[[image:usb-ttl-programming.png]] 2321 2321 ))) 2322 2322 2323 2323 2320 + 2324 2324 ((( 2325 2325 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: 2326 2326 ))) ... ... @@ -2350,39 +2350,39 @@ 2350 2350 * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey) 2351 2351 * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI) 2352 2352 * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON) 2353 -* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)2354 -* **##AT+DR##**: Get or set the Data Rate. (0-7 corresponding to DR_X)2355 -* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing2356 -* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)2357 -* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency2358 -* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)2359 -* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms2360 -* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms2361 -* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms2362 -* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms2363 -* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)2364 -* ##**AT+NWKID**##: Get or set the Network ID2365 -* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)2366 -* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)2367 -* ##**AT+CLASS**##: Get or set the Device Class2368 -* ##**AT+JOIN**##: Join network2369 -* ##**AT+NJS**##: Get OTAA Join Status2370 -* ##**AT+SENDB**##: Send hexadecimal data along with the application port2371 -* ##**AT+SEND**##: Send text data along with the application port2372 -* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)2373 -* ##**AT+RECV**##: Print last received data in raw format2374 -* ##**AT+VER**##: Get current image version and Frequency Band2375 -* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)2376 -* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)2377 -* ##**AT+SNR**##: Get the SNR of the last received packet2378 -* ##**AT+RSSI**##: Get the RSSI of the last received packet2379 -* ##**AT+TDC**##: Get or set the application data transmission interval in ms2380 -* ##**AT+PORT**##: Get or set the application port2381 -* ##**AT+DISAT**##: Disable AT commands2382 -* ##**AT+PWORD**##: Set password, max 9 digits2383 -* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode2384 -* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN4702385 -* ##**AT+CFG**##: Print all settings2350 +* 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 2386 2386 ))) 2387 2387 2388 2388 ... ... @@ -2547,7 +2547,7 @@ 2547 2547 You will need the following things before proceeding: 2548 2548 2549 2549 * 3.5mm programming cable (included with the LT-22222-L as an additional accessory) 2550 -* USB to TTL adapter /converter2547 +* USB to TTL adapter 2551 2551 * 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) 2552 2552 * 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. 2553 2553 ... ... @@ -2557,7 +2557,7 @@ 2557 2557 2558 2558 Below is the hardware setup for uploading a firmware image to the LT-22222-L: 2559 2559 2560 -[[image:usb-ttl- audio-jack-connection.jpg]]2557 +[[image:usb-ttl-programming.png]] 2561 2561 2562 2562 2563 2563
- 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