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 (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Content
-
... ... @@ -43,12 +43,16 @@ 43 43 * If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Stack Community Network), you can select a network and register the LT-22222-L I/O controller with it. 44 44 * If there is no public LoRaWAN coverage in your area, you can set up a LoRaWAN gateway, or multiple gateways, and connect them to a LoRaWAN network server to create adequate coverage. Then, register the LT-22222-L I/O controller with this network. 45 45 * Setup your own private LoRaWAN network. 46 + 47 +{{info}} 48 + You can use a LoRaWAN gateway, such as the [[Dragino LG308>>https://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], to expand or create LoRaWAN coverage in your area. 49 +{{/info}} 46 46 ))) 47 47 48 48 ((( 49 49 50 50 51 -The network diagram below illustrates how the LT-22222-L communicateswitha typical LoRaWAN network.55 +The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network. 52 52 ))) 53 53 54 54 (% class="wikigeneratedid" %) ... ... @@ -129,7 +129,7 @@ 129 129 * 1 x Counting Port 130 130 ))) 131 131 132 -= 2. Assembling the device = 136 +== 2. Assembling the device == 133 133 134 134 == 2.1 Connecting the antenna == 135 135 ... ... @@ -136,17 +136,17 @@ 136 136 Connect the LoRa antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper screw terminal block. Secure the antenna by tightening it clockwise. 137 137 138 138 {{warning}} 139 - **Warning! Do not power on the device without connecting the antenna.**143 +Warning! Do not power on the device without connecting the antenna. 140 140 {{/warning}} 141 141 142 142 == 2.2 Terminals == 143 143 144 -The LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 screwterminals and the lower screw terminal block has 10screwterminals.148 +The LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 terminals and the lower screw terminal block has 10 terminals. 145 145 146 - **Upper screw terminal block (from left to right):**150 +Upper screw terminal block (from left to right): 147 147 148 148 (% style="width:634px" %) 149 -|=(% style="width: 295px;" %) ScrewTerminal|=(% style="width: 338px;" %)Function153 +|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function 150 150 |(% style="width:295px" %)GND|(% style="width:338px" %)Ground 151 151 |(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage 152 152 |(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2 ... ... @@ -154,10 +154,10 @@ 154 154 |(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2 155 155 |(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1 156 156 157 - **Lower screw terminal block (from left to right):**161 +Lower screw terminal block (from left to right): 158 158 159 159 (% style="width:633px" %) 160 -|=(% style="width: 296px;" %) ScrewTerminal|=(% style="width: 334px;" %)Function164 +|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function 161 161 |(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1 162 162 |(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1 163 163 |(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2 ... ... @@ -209,14 +209,10 @@ 209 209 210 210 The network diagram below illustrates the connection between the LT-22222-L and The Things Stack, as well as how the data can be integrated with the ThingsEye IoT platform. 211 211 216 +[[image:dragino-ttn-te.jpg]] 212 212 213 -[[image:dragino-lorawan-nw-lt-22222-n.jpg]] 214 214 215 -{{info}} 216 - You can use a LoRaWAN gateway, such as the [[Dragino LPS8N>>https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]], to expand or create LoRaWAN coverage in your area. 217 -{{/info}} 218 218 219 - 220 220 ==== 3.2.2.1 Setting up ==== 221 221 222 222 * Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet. ... ... @@ -225,6 +225,7 @@ 225 225 * Go to your application's page and click on the **End devices** in the left menu. 226 226 * On the End devices page, click on **+ Register end device**. Two registration options are available: 227 227 228 + 228 228 ==== 3.2.2.2 Using the LoRaWAN Device Repository ==== 229 229 230 230 * On the **Register end device** page: ... ... @@ -249,6 +249,7 @@ 249 249 250 250 [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]] 251 251 253 +==== ==== 252 252 253 253 ==== 3.2.2.3 Adding device manually ==== 254 254 ... ... @@ -283,7 +283,7 @@ 283 283 284 284 ==== 3.2.2.4 Joining ==== 285 285 286 -On the Device 'spage, click on **Live data** tab. The Live data panel for your device will display.288 +On the Device overview page, click on **Live data** tab. The Live data panel for your device will display. 287 287 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 ... ... @@ -301,7 +301,7 @@ 301 301 [[image:lt-22222-ul-payload-decoded.png]] 302 302 303 303 304 -If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select ** Applications > your application >End devices** > **your end device**306 +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. 305 305 306 306 {{info}} 307 307 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. ... ... @@ -882,7 +882,7 @@ 882 882 These commands are specially designed for the LT-22222-L. Commands can be sent to the device using options such as an AT command or a LoRaWAN downlink payload. 883 883 884 884 885 -==== 3.4.2.1 Set Transmit /UplinkInterval ====887 +==== 3.4.2.1 Set Transmit Interval ==== 886 886 887 887 Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes. 888 888 ... ... @@ -891,11 +891,11 @@ 891 891 (% border="2" style="width:500px" %) 892 892 |**Command**|AT+TDC=<time> 893 893 |**Response**| 894 -|**Parameters**|**time** : uplink interval is in **milliseconds**896 +|**Parameters**|**time** : uplink interval is in milliseconds 895 895 |**Example**|((( 896 896 AT+TDC=30000 897 897 898 -Sets the uplink interval to **30 seconds**(30000milliseconds)900 +Sets the uplink interval to 30,000 milliseconds (30 seconds) 899 899 ))) 900 900 901 901 (% style="color:#037691" %)**Downlink payload** ... ... @@ -907,18 +907,16 @@ 907 907 |**Parameters**|((( 908 908 **prefix** : 0x01 909 909 910 -**time** : uplink interval is in **seconds**, represented by**3 bytes**in**hexadecimal**.912 +**time** : uplink interval is in milliseconds, represented by 3 bytes in hexadecimal. 911 911 ))) 912 912 |**Example**|((( 913 -01 **00 001E**915 +01 **00 75 30** 914 914 915 -Sets the uplink interval to **30 seconds**917 +Sets the uplink interval to 30,000 milliseconds (30 seconds) 916 916 917 -Conversion: 30 (dec) = 00 0 01E(hex)919 +Conversion: 30000 (dec) = 00 75 30 (hex) 918 918 919 -See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30]] 920 - 921 -[[image:Screenshot 2024-11-23 at 18.27.11.png]] 921 +See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]] 922 922 ))) 923 923 924 924 ==== 3.4.2.2 Set the Working Mode (AT+MOD) ==== ... ... @@ -969,11 +969,11 @@ 969 969 970 970 ==== 3.4.2.3 Poll an uplink ==== 971 971 972 -Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.972 +Requests an uplink from LT-22222-L. 973 973 974 974 (% style="color:#037691" %)**AT command** 975 975 976 -There is no AT Command available forthisfeature.976 +There is no AT Command to request an uplink from LT-22222-L 977 977 978 978 (% style="color:#037691" %)**Downlink payload** 979 979 ... ... @@ -981,7 +981,7 @@ 981 981 |(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF 982 982 |(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08 983 983 |(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 984 -08 **FF**984 +08 FF 985 985 986 986 Requests an uplink from LT-22222-L. 987 987 ))) ... ... @@ -1015,7 +1015,7 @@ 1015 1015 |(% style="width:97px" %)**Parameters**|(% style="width:401px" %)((( 1016 1016 **prefix** : 0x0A 06 (two bytes in hexadecimal) 1017 1017 1018 -** enable/disable trigger_mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.1018 +**working mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal. 1019 1019 ))) 1020 1020 |(% style="width:97px" %)**Example**|(% style="width:401px" %)((( 1021 1021 0A 06 **01** ... ... @@ -1029,7 +1029,7 @@ 1029 1029 1030 1030 (% style="color:#037691" %)**AT Command:** 1031 1031 1032 -There is no AT Command availablefor this feature.1032 +There is no AT Command for this feature. 1033 1033 1034 1034 (% style="color:#037691" %)**Downlink Payload** 1035 1035 ... ... @@ -1169,6 +1169,8 @@ 1169 1169 ))) 1170 1170 |(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64** 1171 1171 1172 +==== ==== 1173 + 1172 1172 ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ==== 1173 1173 1174 1174 Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] ... ... @@ -1350,6 +1350,8 @@ 1350 1350 ))) 1351 1351 ))) 1352 1352 1355 +==== ==== 1356 + 1353 1353 ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ==== 1354 1354 1355 1355 ... ... @@ -1532,10 +1532,17 @@ 1532 1532 1533 1533 When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1534 1534 1539 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1540 + 1541 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):** 1542 + 1543 +(% style="color:blue" %)**0xA5 aa bb cc ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc 1544 + 1545 + 1535 1535 (% style="color:#037691" %)**AT Command** 1536 1536 1537 1537 (% border="2" style="width:500px" %) 1538 -|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage> ,<logic>1549 +|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage><logic> 1539 1539 |(% style="width:137px" %)**Response**|(% style="width:361px" %) 1540 1540 |(% style="width:137px" %)**Parameters**|(% style="width:361px" %)((( 1541 1541 **voltage** : voltage threshold in mV ... ... @@ -1542,9 +1542,9 @@ 1542 1542 1543 1543 **logic**: 1544 1544 1545 - **0**: lower than1556 +0 : lower than 1546 1546 1547 - **1**: higher than1558 +1: higher than 1548 1548 1549 1549 if you leave logic parameter blank, it is considered 0 1550 1550 ))) ... ... @@ -1573,9 +1573,9 @@ 1573 1573 1574 1574 **logic**: (1 byte in hexadecimal) 1575 1575 1576 - **0**: lower than1587 +0 : lower than 1577 1577 1578 - **1**: higher than1589 +1: higher than 1579 1579 1580 1580 if you leave logic parameter blank, it is considered 1 (higher than) 1581 1581 ))) ... ... @@ -1595,12 +1595,24 @@ 1595 1595 1596 1596 ==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ==== 1597 1597 1598 -This commandallows users to pre-configure specific count numbers for various counting parameters such as Count1, Count2, or AVI1 Count. Use the AT command to set the desired count number for each configuration.1609 +This feature allows users to pre-configure specific count numbers for various counting parameters such as Count1, Count2, or AVI1 Count. Use the AT command to set the desired count number for each configuration. 1599 1599 1611 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) ** 1612 + 1613 +(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count 1614 + 1615 +(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set 1616 + 1617 + 1618 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):** 1619 + 1620 +(% style="color:blue" %)**0x A8 aa bb cc dd ee ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee) 1621 + 1622 + 1600 1600 (% style="color:#037691" %)**AT Command** 1601 1601 1602 1602 (% border="2" style="width:500px" %) 1603 -|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter> ,<number>1626 +|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter><number> 1604 1604 |(% style="width:134px" %)**Response**|(% style="width:364px" %) 1605 1605 |(% style="width:134px" %)**Parameters**|(% style="width:364px" %)((( 1606 1606 **counting_parameter** : ... ... @@ -1644,8 +1644,14 @@ 1644 1644 1645 1645 ==== 3.4.2.18 Counting ~-~- Clear Counting ==== 1646 1646 1647 -This commandclears the counting in counting mode.1670 +This feature clears the counting in counting mode. 1648 1648 1672 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT **(%%) ~/~/ clear all counting 1673 + 1674 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):** 1675 + 1676 +(% style="color:blue" %)**0x A6 01 ** (%%)~/~/ clear all counting 1677 + 1649 1649 (% style="color:#037691" %)**AT Command** 1650 1650 1651 1651 (% border="2" style="width:500px" %) ... ... @@ -1665,8 +1665,22 @@ 1665 1665 1666 1666 ==== 3.4.2.19 Counting ~-~- Change counting mode to save time ==== 1667 1667 1668 -This commandallows you to configure the device to save its counting result to internal flash memory at specified intervals. By setting a save time, the device will periodically store the counting data to prevent loss in case of power failure. The save interval can be adjusted to suit your requirements, with a minimum value of 30 seconds.1697 +This feature allows you to configure the device to save its counting result to internal flash memory at specified intervals. By setting a save time, the device will periodically store the counting data to prevent loss in case of power failure. The save interval can be adjusted to suit your requirements, with a minimum value of 30 seconds. 1669 1669 1699 +* (% style="color:#037691" %)**AT Command:** 1700 + 1701 +(% style="color:blue" %)**AT+COUTIME=60 **(%%)~/~/ Sets the save time to 60 seconds. The device will save the counting result in internal flash every 60 seconds. (Min value: 30 seconds) 1702 + 1703 + 1704 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):** 1705 + 1706 +(% style="color:blue" %)**0x A7 aa bb cc ** (%%)~/~/ same as AT+COUTIME =aa bb cc, 1707 + 1708 +((( 1709 +Range: aa bb cc:0 to 16777215, (unit: seconds) 1710 +))) 1711 + 1712 + 1670 1670 (% style="color:#037691" %)**AT Command** 1671 1671 1672 1672 (% border="2" style="width:500px" %) ... ... @@ -1694,21 +1694,32 @@ 1694 1694 Sets the device to save its counting results to the memory every 60 seconds. 1695 1695 ))) 1696 1696 1740 + 1697 1697 ==== 3.4.2.20 Reset save RO DO state ==== 1698 1698 1699 -This commandallows 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.1743 +This feature allows you to reset the saved relay output (RO) and digital output (DO) states when the device joins the network. By configuring this setting, you can control whether the device should retain or reset the relay states after a reset and rejoin to the network. 1700 1700 1701 -(% style="color:#037691" %)**AT Command** 1745 +* (% style="color:#037691" %)**AT Command:** 1702 1702 1747 +(% style="color:blue" %)**AT+RODORESET=1 **(%%)~/~/ RODO will close when the device joining the network. (default) 1748 + 1749 +(% style="color:blue" %)**AT+RODORESET=0 **(%%)~/~/ After the device is reset, the previously saved RODO state (only MOD2 to MOD5) is read, and its state will not change when the device reconnects to the network. 1750 + 1751 + 1752 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):** 1753 + 1754 +(% style="color:blue" %)**0x AD aa ** (%%)~/~/ same as AT+RODORET =aa 1755 + 1756 + 1703 1703 (% border="2" style="width:500px" %) 1704 1704 |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state> 1705 1705 |(% style="width:127px" %)**Response**|(% style="width:371px" %) 1706 1706 |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1707 - **state**:1761 +state : 1708 1708 1709 - **0**: RODO will close when the device joins the network. (default)1763 +0 : RODO will close when the device joins the network. (default) 1710 1710 1711 - **1**: After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network.1765 +1: After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network. 1712 1712 ))) 1713 1713 |(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1714 1714 (% style="color:blue" %)**AT+RODORESET=1 ** ... ... @@ -1721,18 +1721,16 @@ 1721 1721 ))) 1722 1722 1723 1723 1724 -(% style="color:#037691" %)**Downlink Payload** 1725 - 1726 1726 (% border="2" style="width:500px" %) 1727 1727 |(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state> 1728 1728 |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1729 - **prefix**: AD1781 +prefix : AD 1730 1730 1731 - **state**:1783 +state : 1732 1732 1733 - **0**: RODO will close when the device joins the network. (default), represents as 1 byte in hexadecimal.1785 +0 : RODO will close when the device joins the network. (default), represents as 1 byte in hexadecimal. 1734 1734 1735 - **1**: After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network. - represents as 1 byte in hexadecimal1787 +1: After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network. - represents as 1 byte in hexadecimal 1736 1736 ))) 1737 1737 |(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1738 1738 AD **01** ... ... @@ -1744,145 +1744,59 @@ 1744 1744 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. 1745 1745 ))) 1746 1746 1799 + 1747 1747 ==== 3.4.2.21 Encrypted payload ==== 1748 1748 1749 -This commandallows you to configure whether the device should upload data in an encrypted format or in plaintext. By default, the device encrypts the payload before uploading. You can toggle this setting to either upload encrypted data or transmit it without encryption.1802 +This feature allows you to configure whether the device should upload data in an encrypted format or in plaintext. By default, the device encrypts the payload before uploading. You can toggle this setting to either upload encrypted data or transmit it without encryption. 1750 1750 1751 -(% style="color:#037691" %)**AT Command:** 1804 +* (% style="color:#037691" %)**AT Command:** 1752 1752 1753 -(% border="2" style="width:500px" %) 1754 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state> 1755 -|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1756 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1757 -**state** : 1806 +(% style="color:blue" %)**AT+DECRYPT=1 ** (%%)~/~/ The payload is uploaded without encryption 1758 1758 1759 -** 1**:The payloadsuploadedwithoutencryption1808 +(% style="color:blue" %)**AT+DECRYPT=0 **(%%)~/~/ Encrypt when uploading payload (default) 1760 1760 1761 -**0** : The payload is encrypted when uploaded (default) 1762 -))) 1763 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1764 -AT+DECRYPT=1 1765 1765 1766 -The payload is uploaded without encryption 1767 1767 1768 -AT+DECRYPT=0 1769 - 1770 -The payload is encrypted when uploaded (default) 1771 -))) 1772 - 1773 -There is no downlink payload for this configuration. 1774 - 1775 - 1776 1776 ==== 3.4.2.22 Get sensor value ==== 1777 1777 1778 -This command allows you to retrieve and optionally uplink sensor readings through the serial port. 1779 1779 1780 -(% style="color:#037691" %)**AT Command** 1815 +* (% style="color:#037691" %)**AT Command:** 1781 1781 1782 -(% border="2" style="width:500px" %) 1783 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state> 1784 -|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1785 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1786 -**state** : 1817 +(% style="color:blue" %)**AT+GETSENSORVALUE=0 **(%%)~/~/ The serial port retrieves the reading of the current sensor. 1787 1787 1788 -** 0**: Retrieves the current sensor readingviathe serialport.1819 +(% style="color:blue" %)**AT+GETSENSORVALUE=1 **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it. 1789 1789 1790 -**1 **: Retrieves and uploads the current sensor reading via the serial port. 1791 -))) 1792 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1793 -AT+GETSENSORVALUE=0 1794 1794 1795 -Retrieves the current sensor reading via the serial port. 1796 1796 1797 - AT+GETSENSORVALUE=11823 +==== 3.4.2.23 Resets the downlink packet count ==== 1798 1798 1799 -Retrieves and uplinks the current sensor reading via the serial port. 1800 -))) 1801 1801 1802 - Thereisno downlink payload forthisconfiguration.1826 +* (% style="color:#037691" %)**AT Command:** 1803 1803 1828 +(% style="color:blue" %)**AT+DISFCNTCHECK=0 **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node will no longer receive downlink packets (default) 1804 1804 1805 -== ==3.4.2.23Resettingthe downlink packet count====1830 +(% style="color:blue" %)**AT+DISFCNTCHECK=1 **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node resets the downlink packet count and keeps it consistent with the server downlink packet count. 1806 1806 1807 -This command manages how the node handles mismatched downlink packet counts. It offers two modes: one disables the reception of further downlink packets if discrepancies occur, while the other resets the downlink packet count to align with the server, ensuring continued communication. 1808 1808 1809 -(% style="color:#037691" %)**AT Command** 1810 1810 1811 -(% border="2" style="width:500px" %) 1812 -|(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state> 1813 -|(% style="width:130px" %)**Response**|(% style="width:368px" %)((( 1814 - 1815 -))) 1816 -|(% style="width:130px" %)**Parameters**|(% style="width:368px" %)((( 1817 -**state **: 1818 - 1819 -**0** : When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node stops receiving further downlink packets (default). 1820 - 1821 - 1822 -**1** : When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node resets its downlink packet count to match the server's, ensuring consistency. 1823 -))) 1824 -|(% style="width:130px" %)**Example**|(% style="width:368px" %)((( 1825 -AT+DISFCNTCHECK=0 1826 - 1827 -When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node stops receiving further downlink packets (default). 1828 - 1829 -AT+DISFCNTCHECK=1 1830 - 1831 -When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node resets its downlink packet count to match the server's, ensuring consistency. 1832 -))) 1833 - 1834 -There is no downlink payload for this configuration. 1835 - 1836 - 1837 1837 ==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ==== 1838 1838 1839 1839 1840 - Thiscommand controls the behavior of the node when the combined size of the MAC commands(MACANS)from theserver andthe payloadexceeds the allowed bytelimit forthe current data rate (DR).Thecommandprovides two modes:one enables splitting the data into batches to ensure compliance with the byte limit, while the other prioritizes the payload and ignores the MACANS in cases of overflow.1837 +* (% style="color:#037691" %)**AT Command:** 1841 1841 1842 -(% style="color: #037691" %)**AT Command**1839 +(% style="color:blue" %)**AT+DISMACANS=0** (%%) ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of 11 bytes (DR0 of US915, DR2 of AS923, DR2 of AU195), the node will send a packet with a payload of 00 and a port of 4. (default) 1843 1843 1844 -(% border="2" style="width:500px" %) 1845 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DISMACANS=<state> 1846 -|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1847 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1848 -**state** : 1841 +(% style="color:blue" %)**AT+DISMACANS=1** (%%) ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of the DR, the node will ignore the MACANS and not reply, and only upload the payload part. 1849 1849 1850 -**0** : When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default) 1851 1851 1852 -**1** : When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload. 1853 -))) 1854 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1855 -AT+DISMACANS=0 1844 +* (% style="color:#037691" %)**Downlink Payload **(%%)**:** 1856 1856 1857 - Whenthembined sizeof the MACANS from the server and the payloadexceedsthe byte limit (11bytes for DR0of US915,DR2ofAS923,DR2ofAU915),thenodesendsapacketwith a payload of00 anda portof 4. (default)1846 +(% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set the DISMACANS=1 1858 1858 1859 -AT+DISMACANS=1 1860 1860 1861 -When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload. 1862 -))) 1863 1863 1864 -(% style="color:#037691" %)**Downlink Payload** 1865 - 1866 -(% border="2" style="width:500px" %) 1867 -|(% style="width:126px" %)**Payload**|(% style="width:372px" %)<prefix><state> 1868 -|(% style="width:126px" %)**Parameters**|(% style="width:372px" %)((( 1869 -**prefix** : 21 1870 - 1871 -**state** : (2 bytes in hexadecimal) 1872 - 1873 -**0** : When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default) 1874 - 1875 -**1 **: When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload. 1876 -))) 1877 -|(% style="width:126px" %)**Example**|(% style="width:372px" %)((( 1878 -21 **00 01** 1879 - 1880 -Set DISMACANS=1 1881 -))) 1882 - 1883 1883 ==== 3.4.2.25 Copy downlink to uplink ==== 1884 1884 1885 -This command enables the device to immediately uplink the content of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100. 1886 1886 1887 1887 * (% style="color:#037691" %)**AT Command**(%%)**:** 1888 1888 ... ... @@ -1895,22 +1895,8 @@ 1895 1895 1896 1896 For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77. 1897 1897 1898 -(% border="2" style="width:500px" %) 1899 -|(% style="width:122px" %)**Command**|(% style="width:376px" %)((( 1900 -AT+RPL=5 1901 1901 1902 -After receiving a downlink packet from the server, the node immediately uplinks the content of the packet back to the server using port number 100. 1903 -))) 1904 -|(% style="width:122px" %)**Example**|(% style="width:376px" %)((( 1905 -Downlink: 1906 1906 1907 -01 00 02 58 1908 - 1909 -Uplink: 1910 - 1911 -01 01 00 02 58 1912 -))) 1913 - 1914 1914 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]] 1915 1915 1916 1916 For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. ... ... @@ -1917,16 +1917,14 @@ 1917 1917 1918 1918 1919 1919 1920 -==== 3.4.2.26 Query firmwareversion,frequency band,sub band, andTDCtime====1872 +==== 3.4.2.26 Query version number and frequency band 、TDC ==== 1921 1921 1922 -This command is used to query key information about the device, including its firmware version, frequency band, sub band, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device. 1923 1923 1924 1924 * ((( 1925 1925 (% style="color:#037691" %)**Downlink Payload**(%%)**:** 1926 1926 1927 -(% style="color:blue" %)**26 01 ** (%%) ~/~/ The downlinkpayload26 01isusedtoquerythedevice'sfirmwareversion, frequency band, sub band,andTDC time.1878 +(% style="color:blue" %)**26 01 ** (%%) ~/~/ Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time. 1928 1928 1929 - 1930 1930 1931 1931 ))) 1932 1932 ... ... @@ -1956,8 +1956,6 @@ 1956 1956 1957 1957 === 3.5.2 Configuring ThingsEye.io === 1958 1958 1959 -The ThingsEye.io IoT platform is not open for self-registration at the moment. If you are interested in testing the platform, please send your project information to admin@thingseye.io, and we will create an account for you. 1960 - 1961 1961 * Login to your [[ThingsEye.io >>https://thingseye.io]]account. 1962 1962 * Under the **Integrations center**, click **Integrations**. 1963 1963 * Click the **Add integration** button (the button with the **+** symbol). ... ... @@ -2006,7 +2006,7 @@ 2006 2006 2007 2007 * Choose **Region** from the **Host type**. 2008 2008 * 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/...). 2009 -* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The **username **and **password **can be found on the MQTT integration page of your The Things Stack account (see **3.5.1Configuring The Things Stack**).1957 +* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The **username **and **password **can be found on the MQTT integration page of your The Things Stack account (see Configuring The Things Stack). 2010 2010 * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**. 2011 2011 2012 2012 [[image:message-1.png]] ... ... @@ -2017,7 +2017,7 @@ 2017 2017 [[image:thingseye-io-step-5.png||height="625" width="1000"]] 2018 2018 2019 2019 2020 -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.1968 +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. 2021 2021 2022 2022 2023 2023 [[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]] ... ... @@ -2033,7 +2033,7 @@ 2033 2033 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. 2034 2034 2035 2035 {{info}} 2036 -See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].1984 +See also ThingsEye documentation. 2037 2037 {{/info}} 2038 2038 2039 2039 ==== **3.5.2.2 Viewing events** ==== ... ... @@ -2046,7 +2046,7 @@ 2046 2046 [[image:thingseye-events.png||height="686" width="1000"]] 2047 2047 2048 2048 2049 -* To view the **JSON payload**of a message, click on the**three dots (...)**in the Message column of the desired message.1997 +* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message. 2050 2050 2051 2051 [[image:thingseye-json.png||width="1000"]] 2052 2052 ... ... @@ -2056,11 +2056,6 @@ 2056 2056 If you want to delete an integration, click the **Delete integratio**n button on the Integrations page. 2057 2057 2058 2058 2059 -==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ==== 2060 - 2061 -This will be added soon. 2062 - 2063 - 2064 2064 == 3.6 Interface Details == 2065 2065 2066 2066 === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
- Screenshot 2024-11-23 at 18.27.11.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -143.4 KB - Content
- dragino-lorawan-nw-lt-22222-n.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -267.3 KB - Content