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)
Details
- Page properties
-
- Content
-
... ... @@ -45,7 +45,7 @@ 45 45 * Setup your own private LoRaWAN network. 46 46 47 47 {{info}} 48 - You can use a LoRaWAN gateway, such as the Dragino L PS8N, to expand or create LoRaWAN coverage in your area.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 49 {{/info}} 50 50 ))) 51 51 ... ... @@ -213,12 +213,10 @@ 213 213 214 214 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. 215 215 216 +[[image:dragino-ttn-te.jpg]] 216 216 217 -[[image:dragino-lorawan-nw-lt-22222-n.jpg]] 218 218 219 219 220 - 221 - 222 222 ==== 3.2.2.1 Setting up ==== 223 223 224 224 * Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet. ... ... @@ -227,6 +227,7 @@ 227 227 * Go to your application's page and click on the **End devices** in the left menu. 228 228 * On the End devices page, click on **+ Register end device**. Two registration options are available: 229 229 228 + 230 230 ==== 3.2.2.2 Using the LoRaWAN Device Repository ==== 231 231 232 232 * On the **Register end device** page: ... ... @@ -1607,7 +1607,7 @@ 1607 1607 1608 1608 ==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ==== 1609 1609 1610 -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. 1611 1611 1612 1612 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) ** 1613 1613 ... ... @@ -1668,7 +1668,7 @@ 1668 1668 1669 1669 ==== 3.4.2.18 Counting ~-~- Clear Counting ==== 1670 1670 1671 -This commandclears the counting in counting mode.1670 +This feature clears the counting in counting mode. 1672 1672 1673 1673 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT **(%%) ~/~/ clear all counting 1674 1674 ... ... @@ -1695,7 +1695,7 @@ 1695 1695 1696 1696 ==== 3.4.2.19 Counting ~-~- Change counting mode to save time ==== 1697 1697 1698 -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. 1699 1699 1700 1700 * (% style="color:#037691" %)**AT Command:** 1701 1701 ... ... @@ -1738,9 +1738,10 @@ 1738 1738 Sets the device to save its counting results to the memory every 60 seconds. 1739 1739 ))) 1740 1740 1740 + 1741 1741 ==== 3.4.2.20 Reset save RO DO state ==== 1742 1742 1743 -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. 1744 1744 1745 1745 * (% style="color:#037691" %)**AT Command:** 1746 1746 ... ... @@ -1758,11 +1758,11 @@ 1758 1758 |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state> 1759 1759 |(% style="width:127px" %)**Response**|(% style="width:371px" %) 1760 1760 |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1761 - **state**:1761 +state : 1762 1762 1763 - **0**: RODO will close when the device joins the network. (default)1763 +0 : RODO will close when the device joins the network. (default) 1764 1764 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.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. 1766 1766 ))) 1767 1767 |(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1768 1768 (% style="color:blue" %)**AT+RODORESET=1 ** ... ... @@ -1774,16 +1774,17 @@ 1774 1774 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. 1775 1775 ))) 1776 1776 1777 + 1777 1777 (% border="2" style="width:500px" %) 1778 1778 |(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state> 1779 1779 |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1780 - **prefix**: AD1781 +prefix : AD 1781 1781 1782 - **state**:1783 +state : 1783 1783 1784 - **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. 1785 1785 1786 - **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 1787 1787 ))) 1788 1788 |(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1789 1789 AD **01** ... ... @@ -1795,9 +1795,10 @@ 1795 1795 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. 1796 1796 ))) 1797 1797 1799 + 1798 1798 ==== 3.4.2.21 Encrypted payload ==== 1799 1799 1800 -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. 1801 1801 1802 1802 * (% style="color:#037691" %)**AT Command:** 1803 1803 ... ... @@ -1806,32 +1806,9 @@ 1806 1806 (% style="color:blue" %)**AT+DECRYPT=0 **(%%)~/~/ Encrypt when uploading payload (default) 1807 1807 1808 1808 1809 -(% border="2" style="width:500px" %) 1810 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state> 1811 -|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1812 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1813 -state : 1814 1814 1815 -1 : The payload is uploaded without encryption 1816 - 1817 -0 : The payload is encrypted when uploaded (default) 1818 -))) 1819 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1820 -AT+DECRYPT=1 1821 - 1822 -The payload is uploaded without encryption 1823 - 1824 -AT+DECRYPT=0 1825 - 1826 -The payload is encrypted when uploaded (default) 1827 -))) 1828 - 1829 -There is no downlink payload for this configuration. 1830 - 1831 - 1832 1832 ==== 3.4.2.22 Get sensor value ==== 1833 1833 1834 -This command allows you to retrieve and optionally uplink sensor readings through the serial port. 1835 1835 1836 1836 * (% style="color:#037691" %)**AT Command:** 1837 1837 ... ... @@ -1840,33 +1840,10 @@ 1840 1840 (% style="color:blue" %)**AT+GETSENSORVALUE=1 **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it. 1841 1841 1842 1842 1843 -(% border="2" style="width:500px" %) 1844 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state> 1845 -|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1846 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1847 -**state** : 1848 1848 1849 - **0**:Retrieves thecurrent sensor readingviatheserial port.1823 +==== 3.4.2.23 Resets the downlink packet count ==== 1850 1850 1851 -**1 **: Retrieves and uploads the current sensor reading via the serial port. 1852 -))) 1853 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1854 -AT+GETSENSORVALUE=0 1855 1855 1856 -Retrieves the current sensor reading via the serial port. 1857 - 1858 -AT+GETSENSORVALUE=1 1859 - 1860 -Retrieves and uplinks the current sensor reading via the serial port. 1861 -))) 1862 - 1863 -There is no downlink payload for this configuration. 1864 - 1865 - 1866 -==== 3.4.2.23 Resetting the downlink packet count ==== 1867 - 1868 -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. 1869 - 1870 1870 * (% style="color:#037691" %)**AT Command:** 1871 1871 1872 1872 (% 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) ... ... @@ -1874,37 +1874,10 @@ 1874 1874 (% 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. 1875 1875 1876 1876 1877 -(% border="2" style="width:500px" %) 1878 -|(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state> 1879 -|(% style="width:130px" %)**Response**|(% style="width:368px" %)((( 1880 - 1881 -))) 1882 -|(% style="width:130px" %)**Parameters**|(% style="width:368px" %)((( 1883 -**state **: 1884 1884 1885 -**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). 1886 - 1887 - 1888 -**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. 1889 -))) 1890 -|(% style="width:130px" %)**Example**|(% style="width:368px" %)((( 1891 -AT+DISFCNTCHECK=0 1892 - 1893 -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). 1894 - 1895 -AT+DISFCNTCHECK=1 1896 - 1897 -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. 1898 -))) 1899 - 1900 -There is no downlink payload for this configuration. 1901 - 1902 - 1903 1903 ==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ==== 1904 1904 1905 1905 1906 -This command controls the behavior of the node when the combined size of the MAC commands (MACANS) from the server and the payload exceeds the allowed byte limit for the current data rate (DR). The command provides 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. 1907 - 1908 1908 * (% style="color:#037691" %)**AT Command:** 1909 1909 1910 1910 (% 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) ... ... @@ -1916,51 +1916,10 @@ 1916 1916 1917 1917 (% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set the DISMACANS=1 1918 1918 1919 -(% style="color:#037691" %)**AT Command** 1920 1920 1921 -(% border="2" style="width:500px" %) 1922 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DISMACANS=<state> 1923 -|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1924 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1925 -**state** : 1926 1926 1927 -**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) 1928 - 1929 -**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. 1930 -))) 1931 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1932 -AT+DISMACANS=0 1933 - 1934 -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) 1935 - 1936 -AT+DISMACANS=1 1937 - 1938 -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. 1939 -))) 1940 - 1941 -(% style="color:#037691" %)**Downlink Payload** 1942 - 1943 -(% border="2" style="width:500px" %) 1944 -|(% style="width:126px" %)**Payload**|(% style="width:372px" %)<prefix><state> 1945 -|(% style="width:126px" %)**Parameters**|(% style="width:372px" %)((( 1946 -**prefix** : 21 1947 - 1948 -**state** : (2 bytes in hexadecimal) 1949 - 1950 -**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) 1951 - 1952 -**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. 1953 -))) 1954 -|(% style="width:126px" %)**Example**|(% style="width:372px" %)((( 1955 -21 **00 01** 1956 - 1957 -Set DISMACANS=1 1958 -))) 1959 - 1960 - 1961 1961 ==== 3.4.2.25 Copy downlink to uplink ==== 1962 1962 1963 -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. 1964 1964 1965 1965 * (% style="color:#037691" %)**AT Command**(%%)**:** 1966 1966 ... ... @@ -1973,32 +1973,8 @@ 1973 1973 1974 1974 For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77. 1975 1975 1976 -(% border="2" style="width:500px" %) 1977 -|(% style="width:122px" %)Command|(% style="width:376px" %)((( 1978 -AT+RPL=5 1979 1979 1980 -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. 1981 -))) 1982 -|(% style="width:122px" %)Uplink payload|(% style="width:376px" %)((( 1983 -aa xx xx xx xx 1984 1984 1985 -aa : indicates whether the configuration has changed. 1986 - 1987 -00 : YES 1988 - 1989 -01 : NO 1990 -))) 1991 -|(% style="width:122px" %)Example|(% style="width:376px" %)((( 1992 -Downlink: 1993 - 1994 -11 22 33 44 55 66 77 1995 - 1996 -Uplink: 1997 - 1998 -00 11 22 33 44 55 66 77 1999 -))) 2000 - 2001 - 2002 2002 [[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"]] 2003 2003 2004 2004 For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.