Last modified by Mengting Qiu on 2025/06/04 18:42

From version 217.1
edited by Dilisi S
on 2024/11/24 22:28
Change comment: Nov 24 Fix images and few edits
To version 208.1
edited by Dilisi S
on 2024/11/22 05:35
Change comment: Nov 21 edits

Summary

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 LPS8N, 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 communicates with a 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 screw terminals and the lower screw terminal block has 10 screw terminals.
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;" %)Screw Terminal|=(% style="width: 338px;" %)Function
153 +|=(% 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;" %)Screw Terminal|=(% style="width: 334px;" %)Function
164 +|=(% 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
... ... @@ -212,11 +212,9 @@
212 212  
213 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 219  
221 +
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.
... ... @@ -249,6 +249,7 @@
249 249  
250 250  [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
251 251  
254 +==== ====
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's page, click on **Live data** tab. The Live data panel for your device will display.
289 +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** > **Payload formatters** > **Uplink**. Then  select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
307 +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/Uplink Interval ====
888 +==== 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**
897 +|**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** (30000 milliseconds)
901 +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**.
913 +**time** : uplink interval is in milliseconds, represented by 3  bytes in hexadecimal.
911 911  )))
912 912  |**Example**|(((
913 -01 **00 00 1E**
916 +01 **00 75 30**
914 914  
915 -Sets the uplink interval to **30 seconds**
918 +Sets the uplink interval to 30,000 milliseconds (30 seconds)
916 916  
917 -Conversion: 30 (dec) = 00 00 1E (hex)
920 +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]]
922 +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.
973 +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 for this feature.
977 +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**
985 +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.
1019 +**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 available for this feature.
1033 +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  
1173 +==== ====
1174 +
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  
1356 +==== ====
1357 +
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  
1540 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX   ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
1541 +
1542 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):**
1543 +
1544 +(% style="color:blue" %)**0xA5 aa bb cc   ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc
1545 +
1546 +
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>
1550 +|(% 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 than
1557 +0 : lower than
1546 1546  
1547 -**1**: higher than
1559 +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 than
1588 +0 : lower than
1577 1577  
1578 -**1**: higher than
1590 +1: higher than
1579 1579  
1580 1580  if you leave logic parameter blank, it is considered 1 (higher than)
1581 1581  )))
... ... @@ -1597,10 +1597,22 @@
1597 1597  
1598 1598  This command 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  
1612 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) **
1613 +
1614 +(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count
1615 +
1616 +(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set
1617 +
1618 +
1619 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):**
1620 +
1621 +(% style="color:blue" %)**0x A8 aa bb cc dd ee     ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee)
1622 +
1623 +
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>
1627 +|(% 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** :
... ... @@ -1646,6 +1646,12 @@
1646 1646  
1647 1647  This command clears the counting in counting mode.
1648 1648  
1673 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT         **(%%) ~/~/ clear all counting
1674 +
1675 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):**
1676 +
1677 +(% style="color:blue" %)**0x A6 01    ** (%%)~/~/ clear all counting
1678 +
1649 1649  (% style="color:#037691" %)**AT Command**
1650 1650  
1651 1651  (% border="2" style="width:500px" %)
... ... @@ -1667,6 +1667,20 @@
1667 1667  
1668 1668  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.
1669 1669  
1700 +* (% style="color:#037691" %)**AT Command:**
1701 +
1702 +(% 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)
1703 +
1704 +
1705 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):**
1706 +
1707 +(% style="color:blue" %)**0x A7 aa bb cc     ** (%%)~/~/ same as AT+COUTIME =aa bb cc,
1708 +
1709 +(((
1710 +Range: aa bb cc:0 to 16777215,  (unit: seconds)
1711 +)))
1712 +
1713 +
1670 1670  (% style="color:#037691" %)**AT Command**
1671 1671  
1672 1672  (% border="2" style="width:500px" %)
... ... @@ -1698,8 +1698,18 @@
1698 1698  
1699 1699  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.
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" %)
... ... @@ -1720,8 +1720,6 @@
1720 1720  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.
1721 1721  )))
1722 1722  
1723 -(% style="color:#037691" %)**Downlink Payload**
1724 -
1725 1725  (% border="2" style="width:500px" %)
1726 1726  |(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state>
1727 1727  |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
... ... @@ -1747,17 +1747,22 @@
1747 1747  
1748 1748  This command 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.
1749 1749  
1750 -(% style="color:#037691" %)**AT Command:**
1802 +* (% style="color:#037691" %)**AT Command:**
1751 1751  
1804 +(% style="color:blue" %)**AT+DECRYPT=1  ** (%%)~/~/ The payload is uploaded without encryption
1805 +
1806 +(% style="color:blue" %)**AT+DECRYPT=0    **(%%)~/~/  Encrypt when uploading payload (default)
1807 +
1808 +
1752 1752  (% border="2" style="width:500px" %)
1753 1753  |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state>
1754 1754  |(% style="width:127px" %)**Response**|(% style="width:371px" %)
1755 1755  |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1756 -**state** :
1813 +state :
1757 1757  
1758 -**1** : The payload is uploaded without encryption
1815 +1 : The payload is uploaded without encryption
1759 1759  
1760 -**0** : The payload is encrypted when uploaded (default)
1817 +0 : The payload is encrypted when uploaded (default)
1761 1761  )))
1762 1762  |(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1763 1763  AT+DECRYPT=1
... ... @@ -1776,8 +1776,13 @@
1776 1776  
1777 1777  This command allows you to retrieve and optionally uplink sensor readings through the serial port.
1778 1778  
1779 -(% style="color:#037691" %)**AT Command**
1836 +* (% style="color:#037691" %)**AT Command:**
1780 1780  
1838 +(% style="color:blue" %)**AT+GETSENSORVALUE=0    **(%%)~/~/ The serial port retrieves the reading of the current sensor.
1839 +
1840 +(% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it.
1841 +
1842 +
1781 1781  (% border="2" style="width:500px" %)
1782 1782  |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state>
1783 1783  |(% style="width:127px" %)**Response**|(% style="width:371px" %)
... ... @@ -1805,8 +1805,13 @@
1805 1805  
1806 1806  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.
1807 1807  
1808 -(% style="color:#037691" %)**AT Command**
1870 +* (% style="color:#037691" %)**AT Command:**
1809 1809  
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)
1873 +
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 +
1876 +
1810 1810  (% border="2" style="width:500px" %)
1811 1811  |(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state>
1812 1812  |(% style="width:130px" %)**Response**|(% style="width:368px" %)(((
... ... @@ -1838,6 +1838,17 @@
1838 1838  
1839 1839  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.
1840 1840  
1908 +* (% style="color:#037691" %)**AT Command:**
1909 +
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)
1911 +
1912 +(% 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.
1913 +
1914 +
1915 +* (% style="color:#037691" %)**Downlink Payload **(%%)**:**
1916 +
1917 +(% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set  the DISMACANS=1
1918 +
1841 1841  (% style="color:#037691" %)**AT Command**
1842 1842  
1843 1843  (% border="2" style="width:500px" %)
... ... @@ -1879,6 +1879,7 @@
1879 1879  Set DISMACANS=1
1880 1880  )))
1881 1881  
1960 +
1882 1882  ==== 3.4.2.25 Copy downlink to uplink ====
1883 1883  
1884 1884  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.
... ... @@ -1895,21 +1895,31 @@
1895 1895  For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
1896 1896  
1897 1897  (% border="2" style="width:500px" %)
1898 -|(% style="width:122px" %)**Command**|(% style="width:376px" %)(((
1977 +|(% style="width:122px" %)Command|(% style="width:376px" %)(((
1899 1899  AT+RPL=5
1900 1900  
1901 1901  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.
1902 1902  )))
1903 -|(% style="width:122px" %)**Example**|(% style="width:376px" %)(((
1982 +|(% style="width:122px" %)Uplink payload|(% style="width:376px" %)(((
1983 +aa xx xx xx xx
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" %)(((
1904 1904  Downlink:
1905 1905  
1906 -01 00 02 58
1994 +11 22 33 44 55 66 77
1907 1907  
1908 1908  Uplink:
1909 1909  
1910 -01 01 00 02 58
1998 +00 11 22 33 44 55 66 77
1911 1911  )))
1912 1912  
2001 +
1913 1913  [[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"]]
1914 1914  
1915 1915  For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
... ... @@ -1916,16 +1916,14 @@
1916 1916  
1917 1917  
1918 1918  
1919 -==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
2008 +==== 3.4.2.26 Query version number and frequency band TDC ====
1920 1920  
1921 -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.
1922 1922  
1923 1923  * (((
1924 1924  (% style="color:#037691" %)**Downlink Payload**(%%)**:**
1925 1925  
1926 -(% style="color:blue" %)**26 01  ** (%%) ~/~/  The downlink payload 26 01 is used to query the device's firmware version, frequency band, sub band, and TDC time.
2014 +(% style="color:blue" %)**26 01  ** (%%) ~/~/  Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.
1927 1927  
1928 -
1929 1929  
1930 1930  )))
1931 1931  
... ... @@ -1955,8 +1955,6 @@
1955 1955  
1956 1956  === 3.5.2 Configuring ThingsEye.io ===
1957 1957  
1958 -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.
1959 -
1960 1960  * Login to your [[ThingsEye.io >>https://thingseye.io]]account.
1961 1961  * Under the **Integrations center**, click **Integrations**.
1962 1962  * Click the **Add integration** button (the button with the **+** symbol).
... ... @@ -2005,7 +2005,7 @@
2005 2005  
2006 2006  * Choose **Region** from the **Host type**.
2007 2007  * 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/...).
2008 -* 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.1 Configuring The Things Stack**).
2093 +* 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).
2009 2009  * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
2010 2010  
2011 2011  [[image:message-1.png]]
... ... @@ -2016,7 +2016,7 @@
2016 2016  [[image:thingseye-io-step-5.png||height="625" width="1000"]]
2017 2017  
2018 2018  
2019 -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.
2104 +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.
2020 2020  
2021 2021  
2022 2022  [[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
... ... @@ -2032,7 +2032,7 @@
2032 2032  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.
2033 2033  
2034 2034  {{info}}
2035 -See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
2120 +See also ThingsEye documentation.
2036 2036  {{/info}}
2037 2037  
2038 2038  ==== **3.5.2.2 Viewing events** ====
... ... @@ -2045,7 +2045,7 @@
2045 2045  [[image:thingseye-events.png||height="686" width="1000"]]
2046 2046  
2047 2047  
2048 -* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
2133 +* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
2049 2049  
2050 2050  [[image:thingseye-json.png||width="1000"]]
2051 2051  
... ... @@ -2055,17 +2055,12 @@
2055 2055  If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
2056 2056  
2057 2057  
2058 -==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
2059 -
2060 -This will be added soon.
2061 -
2062 -
2063 2063  == 3.6 Interface Details ==
2064 2064  
2065 2065  === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
2066 2066  
2067 2067  
2068 -Supports** NPN-type **sensors.
2148 +Supports NPN-type sensors.
2069 2069  
2070 2070  [[image:1653356991268-289.png]]
2071 2071  
... ... @@ -2187,15 +2187,15 @@
2187 2187  )))
2188 2188  
2189 2189  
2190 -(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor
2270 +(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
2191 2191  
2192 -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.
2272 +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.
2193 2193  
2194 -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.
2274 +To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram.
2195 2195  
2196 2196  [[image:image-20230616235145-1.png]]
2197 2197  
2198 -(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector
2278 +(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
2199 2199  
2200 2200  [[image:image-20240219115718-1.png]]
2201 2201  
... ... @@ -2271,7 +2271,7 @@
2271 2271  [[image:image-20220524100215-10.png||height="382" width="723"]]
2272 2272  
2273 2273  
2274 -== 3.7 LED Indicators ==
2354 +== 3.7 LEDs Indicators ==
2275 2275  
2276 2276  The table below lists the behavior of LED indicators for each port function.
2277 2277  
... ... @@ -2310,14 +2310,13 @@
2310 2310  == 4.1 Connecting the LT-22222-L to a PC ==
2311 2311  
2312 2312  (((
2313 -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.
2393 +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.
2314 2314  
2315 -[[image:usb-ttl-audio-jack-connection.jpg]]
2316 -
2317 -
2395 +[[image:usb-ttl-programming.png]]
2318 2318  )))
2319 2319  
2320 2320  
2399 +
2321 2321  (((
2322 2322  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:
2323 2323  )))
... ... @@ -2347,39 +2347,39 @@
2347 2347  * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
2348 2348  * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
2349 2349  * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
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
2429 +* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2430 +* AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
2431 +* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2432 +* AT+PNM: Get or set the public network mode. (0: off, 1: on)
2433 +* AT+RX2FQ: Get or set the Rx2 window frequency
2434 +* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2435 +* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2436 +* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2437 +* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2438 +* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2439 +* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2440 +* AT+NWKID: Get or set the Network ID
2441 +* AT+FCU: Get or set the Frame Counter Uplink (FCntUp)
2442 +* AT+FCD: Get or set the Frame Counter Downlink (FCntDown)
2443 +* AT+CLASS: Get or set the Device Class
2444 +* AT+JOIN: Join network
2445 +* AT+NJS: Get OTAA Join Status
2446 +* AT+SENDB: Send hexadecimal data along with the application port
2447 +* AT+SEND: Send text data along with the application port
2448 +* AT+RECVB: Print last received data in binary format (with hexadecimal values)
2449 +* AT+RECV: Print last received data in raw format
2450 +* AT+VER: Get current image version and Frequency Band
2451 +* AT+CFM: Get or Set the confirmation mode (0-1)
2452 +* AT+CFS: Get confirmation status of the last AT+SEND (0-1)
2453 +* AT+SNR: Get the SNR of the last received packet
2454 +* AT+RSSI: Get the RSSI of the last received packet
2455 +* AT+TDC: Get or set the application data transmission interval in ms
2456 +* AT+PORT: Get or set the application port
2457 +* AT+DISAT: Disable AT commands
2458 +* AT+PWORD: Set password, max 9 digits
2459 +* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2460 +* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470
2461 +* AT+CFG: Print all settings
2383 2383  )))
2384 2384  
2385 2385  
... ... @@ -2544,7 +2544,7 @@
2544 2544  You will need the following things before proceeding:
2545 2545  
2546 2546  * 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
2547 -* USB to TTL adapter/converter
2626 +* USB to TTL adapter
2548 2548  * 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)
2549 2549  * 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.
2550 2550  
... ... @@ -2554,7 +2554,7 @@
2554 2554  
2555 2555  Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2556 2556  
2557 -[[image:usb-ttl-audio-jack-connection.jpg]]
2636 +[[image:usb-ttl-programming.png]]
2558 2558  
2559 2559  
2560 2560  
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
usb-ttl-audio-jack-connection.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -394.4 KB
Content