Skip to Content
Last modified by Mengting Qiu on 2025/06/04 18:42
From version 208.1
edited by Dilisi S
on 2024/11/22 05:35
Change comment: Nov 21 edits
To version 223.1
edited by Dilisi S
on 2024/11/26 05:20
Change comment: Nov 25 edits

Summary

Details

Page properties
Content
... ... @@ -43,16 +43,12 @@
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}}
50 50  )))
51 51  
52 52  (((
53 53  
54 54  
55 -The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
51 +The network diagram below illustrates how the LT-22222-L communicates with a typical LoRaWAN network.
56 56  )))
57 57  
58 58  (% class="wikigeneratedid" %)
... ... @@ -120,13 +120,13 @@
120 120  
121 121  == 1.5 Hardware Variants ==
122 122  
123 -(% style="width:524px" %)
124 -|(% style="width:94px" %)**Model**|(% style="width:98px" %)**Photo**|(% style="width:329px" %)**Description**
125 -|(% style="width:94px" %)**LT33222-L**|(% style="width:98px" %)(((
126 -
127 -)))|(% style="width:329px" %)(((
128 -* 2 x Digital Input (Bi-direction)
129 -* 2 x Digital Output
119 +(% style="width:650px" %)
120 +|(% style="width:94px" %)**Model**|(% style="width:172px" %)**Photo**|(% style="width:256px" %)**Description**
121 +|(% style="width:94px" %)**LT-33222-L**|(% style="width:172px" %)(((
122 +[[image:lt33222-l.jpg]]
123 +)))|(% style="width:256px" %)(((
124 +* 3 x Digital Input (Bi-direction)
125 +* 3 x Digital Output
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)
... ... @@ -133,7 +133,7 @@
133 133  * 1 x Counting Port
134 134  )))
135 135  
136 -== 2. Assembling the device ==
132 += 2. Assembling the device =
137 137  
138 138  == 2.1 Connecting the antenna ==
139 139  
... ... @@ -140,17 +140,17 @@
140 140  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.
141 141  
142 142  {{warning}}
143 -Warning! Do not power on the device without connecting the antenna.
139 +**Warning! Do not power on the device without connecting the antenna.**
144 144  {{/warning}}
145 145  
146 146  == 2.2 Terminals ==
147 147  
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.
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.
149 149  
150 -Upper screw terminal block (from left to right):
146 +**Upper screw terminal block (from left to right):**
151 151  
152 152  (% style="width:634px" %)
153 -|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function
149 +|=(% style="width: 295px;" %)Screw Terminal|=(% style="width: 338px;" %)Function
154 154  |(% style="width:295px" %)GND|(% style="width:338px" %)Ground
155 155  |(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage
156 156  |(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2
... ... @@ -158,10 +158,10 @@
158 158  |(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2
159 159  |(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1
160 160  
161 -Lower screw terminal block (from left to right):
157 +**Lower screw terminal block (from left to right):**
162 162  
163 163  (% style="width:633px" %)
164 -|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function
160 +|=(% style="width: 296px;" %)Screw Terminal|=(% style="width: 334px;" %)Function
165 165  |(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1
166 166  |(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1
167 167  |(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2
... ... @@ -216,9 +216,11 @@
216 216  
217 217  [[image:dragino-lorawan-nw-lt-22222-n.jpg]]
218 218  
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}}
219 219  
220 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.
... ... @@ -239,7 +239,7 @@
239 239  *** **Profile (Region)**: Select the region that matches your device.
240 240  ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
241 241  
242 -[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
240 +[[image:lt-22222-l-dev-repo-reg-p1.png]]
243 243  
244 244  
245 245  * Register end device page continued...
... ... @@ -249,9 +249,8 @@
249 249  ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
250 250  ** Under **After registration**, select the **View registered end device** option.
251 251  
252 -[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
250 +[[image:lt-22222-l-dev-repo-reg-p2.png]]
253 253  
254 -==== ====
255 255  
256 256  ==== 3.2.2.3 Adding device manually ====
257 257  
... ... @@ -264,7 +264,7 @@
264 264  ** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
265 265  ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
266 266  
267 -[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
264 +[[image:lt-22222-l-manually-p1.png]]
268 268  
269 269  
270 270  * Register end device page continued...
... ... @@ -275,25 +275,26 @@
275 275  ** Under **After registration**, select the **View registered end device** option.
276 276  ** Click the **Register end device** button.
277 277  
278 -[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
275 +[[image:lt-22222-l-manually-p2.png]]
279 279  
280 280  
281 281  You will be navigated to the **Device overview** page.
282 282  
283 283  
284 -[[image:lt-22222-device-overview.png||height="625" width="1000"]]
281 +[[image:lt-22222-device-overview.png]]
285 285  
286 286  
287 287  ==== 3.2.2.4 Joining ====
288 288  
289 -On the Device overview page, click on **Live data** tab. The Live data panel for your device will display.
286 +On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
290 290  
291 291  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.
292 292  
293 293  
294 -[[image:lt-22222-join-network.png||height="625" width="1000"]]
291 +[[image:lt-22222-l-joining.png]]
295 295  
296 296  
294 +
297 297  ==== 3.2.2.5 Uplinks ====
298 298  
299 299  
... ... @@ -304,13 +304,13 @@
304 304  [[image:lt-22222-ul-payload-decoded.png]]
305 305  
306 306  
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 +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.
308 308  
309 309  {{info}}
310 310  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.
311 311  {{/info}}
312 312  
313 -[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
311 +[[image:lt-22222-ul-payload-fmt.png]]
314 314  
315 315  
316 316  ==== 3.2.2.6 Downlinks ====
... ... @@ -601,11 +601,11 @@
601 601  
602 602  (% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)**
603 603  
604 -(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
602 +(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), the counter increases by 1)**
605 605  
606 -(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
604 +(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If the AVI1 voltage is lower than VOLMAX (20000mV =20V), counter increases by 1)**
607 607  
608 -(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
606 +(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), counter increases by 1)**
609 609  )))
610 610  
611 611  
... ... @@ -724,9 +724,9 @@
724 724  
725 725  (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
726 726  
727 -Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
725 +**Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
728 728  
729 -Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
727 +**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
730 730  
731 731   AA: Type Code for this downlink Command:
732 732  
... ... @@ -793,7 +793,7 @@
793 793  
794 794  **Example:**
795 795  
796 -10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW
794 +10100000: This means the system is configured to use the triggers AV1_LOW and AV2_LOW.
797 797  
798 798  
799 799  (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
... ... @@ -822,7 +822,7 @@
822 822  
823 823  **Example:**
824 824  
825 -10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.
823 +10000000: The uplink is triggered by AV1_LOW, indicating that the voltage is too low.
826 826  
827 827  
828 828  (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
... ... @@ -831,22 +831,22 @@
831 831  |(% 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**
832 832  |(% 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
833 833  
834 -* Each bits shows which status has been triggered on this uplink.
832 +* Each bit shows which status has been triggered on this uplink.
835 835  
836 836  **Example:**
837 837  
838 -00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
836 +00000111: This means both DI1 and DI2 triggers are enabled, and this packet is trigger by DI1.
839 839  
840 -00000101: Means both DI1 and DI2 trigger are enabled.
838 +00000101: This means both DI1 and DI2 triggers are enabled.
841 841  
842 842  
843 -(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable.
841 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled.
844 844  
845 -Downlink command to poll MOD6 status:
843 +Downlink command to poll/request MOD6 status:
846 846  
847 847  **AB 06**
848 848  
849 -When device got this command, it will send the MOD6 payload.
847 +When device receives this command, it will send the MOD6 payload.
850 850  
851 851  
852 852  === 3.3.7 Payload Decoder ===
... ... @@ -885,7 +885,7 @@
885 885  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.
886 886  
887 887  
888 -==== 3.4.2.1 Set Transmit Interval ====
886 +==== 3.4.2.1 Set Transmit/Uplink Interval ====
889 889  
890 890  Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
891 891  
... ... @@ -894,11 +894,11 @@
894 894  (% border="2" style="width:500px" %)
895 895  |**Command**|AT+TDC=<time>
896 896  |**Response**|
897 -|**Parameters**|**time** : uplink interval is in milliseconds
895 +|**Parameters**|**time** : uplink interval is in **milliseconds**
898 898  |**Example**|(((
899 899  AT+TDC=30000
900 900  
901 -Sets the uplink interval to 30,000 milliseconds (30 seconds)
899 +Sets the uplink interval to **30 seconds** (30000 milliseconds)
902 902  )))
903 903  
904 904  (% style="color:#037691" %)**Downlink payload**
... ... @@ -910,16 +910,18 @@
910 910  |**Parameters**|(((
911 911  **prefix** : 0x01
912 912  
913 -**time** : uplink interval is in milliseconds, represented by 3  bytes in hexadecimal.
911 +**time** : uplink interval is in **seconds**, represented by **3  bytes** in **hexadecimal**.
914 914  )))
915 915  |**Example**|(((
916 -01 **00 75 30**
914 +01 **00 00 1E**
917 917  
918 -Sets the uplink interval to 30,000 milliseconds (30 seconds)
916 +Sets the uplink interval to **30 seconds**
919 919  
920 -Conversion: 30000 (dec) = 00 75 30 (hex)
918 +Conversion: 30 (dec) = 00 00 1E (hex)
921 921  
922 -See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]]
920 +See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30]]
921 +
922 +[[image:Screenshot 2024-11-23 at 18.27.11.png]]
923 923  )))
924 924  
925 925  ==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
... ... @@ -968,13 +968,13 @@
968 968  Sets the device to working mode 2 (Double DI Counting + DO + RO)
969 969  )))
970 970  
971 -==== 3.4.2.3 Poll an uplink ====
971 +==== 3.4.2.3 Request an uplink from the device ====
972 972  
973 -Requests an uplink from LT-22222-L.
973 +Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.
974 974  
975 975  (% style="color:#037691" %)**AT command**
976 976  
977 -There is no AT Command to request an uplink from LT-22222-L
977 +There is no AT Command available for this feature.
978 978  
979 979  (% style="color:#037691" %)**Downlink payload**
980 980  
... ... @@ -982,7 +982,7 @@
982 982  |(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF
983 983  |(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08
984 984  |(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
985 -08 FF
985 +08 **FF**
986 986  
987 987  Requests an uplink from LT-22222-L.
988 988  )))
... ... @@ -1016,7 +1016,7 @@
1016 1016  |(% style="width:97px" %)**Parameters**|(% style="width:401px" %)(((
1017 1017  **prefix** : 0x0A 06 (two bytes in hexadecimal)
1018 1018  
1019 -**working mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
1019 +**enable/disable trigger_mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
1020 1020  )))
1021 1021  |(% style="width:97px" %)**Example**|(% style="width:401px" %)(((
1022 1022  0A 06 **01**
... ... @@ -1024,13 +1024,13 @@
1024 1024  Enable trigger mode for the current working mode
1025 1025  )))
1026 1026  
1027 -==== 3.4.2.5 Poll trigger settings ====
1027 +==== 3.4.2.5 Request trigger settings ====
1028 1028  
1029 -Polls the trigger settings.
1029 +Requests the trigger settings.
1030 1030  
1031 1031  (% style="color:#037691" %)**AT Command:**
1032 1032  
1033 -There is no AT Command for this feature.
1033 +There is no AT Command available for this feature.
1034 1034  
1035 1035  (% style="color:#037691" %)**Downlink Payload**
1036 1036  
... ... @@ -1170,8 +1170,6 @@
1170 1170  )))
1171 1171  |(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64**
1172 1172  
1173 -==== ====
1174 -
1175 1175  ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
1176 1176  
1177 1177  Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
... ... @@ -1353,32 +1353,28 @@
1353 1353  )))
1354 1354  )))
1355 1355  
1356 -==== ====
1357 -
1358 1358  ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
1359 1359  
1360 1360  
1361 1361  * (% style="color:#037691" %)**AT Command**
1362 1362  
1363 -There is no AT Command to control Digital Output
1359 +There is no AT command to control the 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 DO1/DO2/DO3 output with time control
1364 +(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control
1369 1369  
1370 -
1371 1371  This is to control the digital output time of DO pin. Include four bytes:
1372 1372  
1373 -(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
1368 +(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)
1374 1374  
1375 -(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode
1370 +(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode
1376 1376  
1377 -01: DO pins will change back to original state after timeout.
1372 +**01:** DO pins revert to their original state after the timeout.
1373 +**00:** DO pins switch to an inverted state after the timeout.
1378 1378  
1379 -00: DO pins will change to an inverter state after timeout 
1380 1380  
1381 -
1382 1382  (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
1383 1383  
1384 1384  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
... ... @@ -1387,7 +1387,7 @@
1387 1387  |0x00|DO1 set to high
1388 1388  |0x11|DO1 NO Action
1389 1389  
1390 -(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:
1384 +(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:
1391 1391  
1392 1392  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1393 1393  |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
... ... @@ -1395,7 +1395,7 @@
1395 1395  |0x00|DO2 set to high
1396 1396  |0x11|DO2 NO Action
1397 1397  
1398 -(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:
1392 +(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:
1399 1399  
1400 1400  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1401 1401  |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
... ... @@ -1403,7 +1403,7 @@
1403 1403  |0x00|DO3 set to high
1404 1404  |0x11|DO3 NO Action
1405 1405  
1406 -(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)
1400 +(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms)
1407 1407  
1408 1408  
1409 1409  (% style="color:red" %)**Note: **
... ... @@ -1412,7 +1412,7 @@
1412 1412  
1413 1413   Before firmware v1.6.0, the latch time only supported 2 bytes.
1414 1414  
1415 -(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1409 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1416 1416  
1417 1417  
1418 1418  **Example payload:**
... ... @@ -1439,16 +1439,16 @@
1439 1439  
1440 1440  * (% style="color:#037691" %)**AT Command:**
1441 1441  
1442 -There is no AT Command to control Relay Output
1436 +There is no AT Command to control the Relay Output
1443 1443  
1444 1444  
1445 1445  * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
1446 1446  
1447 -(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Set RO1/RO2 output
1441 +(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Sets RO1/RO2 output
1448 1448  
1449 1449  
1450 1450  (((
1451 -If payload is 0x030100, it means setting RO1 to close and RO2 to open.
1445 +If the payload is 0x030100, it means setting RO1 to close and RO2 to open.
1452 1452  )))
1453 1453  
1454 1454  (((
... ... @@ -1466,7 +1466,7 @@
1466 1466  |03  00  01|Open|Close
1467 1467  )))
1468 1468  
1469 -(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
1463 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1470 1470  
1471 1471  
1472 1472  ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
... ... @@ -1475,19 +1475,19 @@
1475 1475  
1476 1476  * (% style="color:#037691" %)**AT Command:**
1477 1477  
1478 -There is no AT Command to control Relay Output
1472 +There is no AT Command to control the Relay Output
1479 1479  
1480 1480  
1481 1481  * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1482 1482  
1483 -(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Set RO1/RO2 relay with time control
1477 +(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
1484 1484  
1485 1485  
1486 -This is to control the relay output time. It includes four bytes:
1480 +This controls the relay output time and includes 4 bytes:
1487 1487  
1488 -(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
1482 +(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)
1489 1489  
1490 -(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
1484 +(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode
1491 1491  
1492 1492  01: Relays will change back to their original state after timeout.
1493 1493  
... ... @@ -1494,12 +1494,12 @@
1494 1494  00: Relays will change to the inverter state after timeout.
1495 1495  
1496 1496  
1497 -(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
1491 +(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status:
1498 1498  
1499 1499  [[image:image-20221008095908-1.png||height="364" width="564"]]
1500 1500  
1501 1501  
1502 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms
1496 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes (cc)**(%%): Latching time. Unit: ms
1503 1503  
1504 1504  
1505 1505  (% style="color:red" %)**Note:**
... ... @@ -1509,7 +1509,7 @@
1509 1509   Before firmware v1.6.0, the latch time only supported 2 bytes.
1510 1510  
1511 1511  
1512 -(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1506 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1513 1513  
1514 1514  
1515 1515  **Example payload:**
... ... @@ -1537,17 +1537,10 @@
1537 1537  
1538 1538  When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
1539 1539  
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 -
1547 1547  (% style="color:#037691" %)**AT Command**
1548 1548  
1549 1549  (% border="2" style="width:500px" %)
1550 -|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage><logic>
1537 +|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage>,<logic>
1551 1551  |(% style="width:137px" %)**Response**|(% style="width:361px" %)
1552 1552  |(% style="width:137px" %)**Parameters**|(% style="width:361px" %)(((
1553 1553  **voltage** : voltage threshold in mV
... ... @@ -1554,9 +1554,9 @@
1554 1554  
1555 1555  **logic**:
1556 1556  
1557 -0 : lower than
1544 +**0** : lower than
1558 1558  
1559 -1: higher than
1546 +**1**: higher than
1560 1560  
1561 1561  if you leave logic parameter blank, it is considered 0
1562 1562  )))
... ... @@ -1585,9 +1585,9 @@
1585 1585  
1586 1586  **logic**: (1 byte in hexadecimal)
1587 1587  
1588 -0 : lower than
1575 +**0** : lower than
1589 1589  
1590 -1: higher than
1577 +**1**: higher than
1591 1591  
1592 1592  if you leave logic parameter blank, it is considered 1 (higher than)
1593 1593  )))
... ... @@ -1609,22 +1609,10 @@
1609 1609  
1610 1610  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.
1611 1611  
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 -
1624 1624  (% style="color:#037691" %)**AT Command**
1625 1625  
1626 1626  (% border="2" style="width:500px" %)
1627 -|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter><number>
1602 +|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter>,<number>
1628 1628  |(% style="width:134px" %)**Response**|(% style="width:364px" %)
1629 1629  |(% style="width:134px" %)**Parameters**|(% style="width:364px" %)(((
1630 1630  **counting_parameter** :
... ... @@ -1670,12 +1670,6 @@
1670 1670  
1671 1671  This command clears the counting in counting mode.
1672 1672  
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 -
1679 1679  (% style="color:#037691" %)**AT Command**
1680 1680  
1681 1681  (% border="2" style="width:500px" %)
... ... @@ -1693,24 +1693,10 @@
1693 1693  )))
1694 1694  |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
1695 1695  
1696 -==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1665 +==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ====
1697 1697  
1698 1698  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.
1699 1699  
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 -
1714 1714  (% style="color:#037691" %)**AT Command**
1715 1715  
1716 1716  (% border="2" style="width:500px" %)
... ... @@ -1738,22 +1738,12 @@
1738 1738  Sets the device to save its counting results to the memory every 60 seconds.
1739 1739  )))
1740 1740  
1741 -==== 3.4.2.20 Reset save RO DO state ====
1696 +==== 3.4.2.20 Reset saved RO and DO states ====
1742 1742  
1743 1743  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.
1744 1744  
1745 -* (% style="color:#037691" %)**AT Command:**
1700 +(% style="color:#037691" %)**AT Command**
1746 1746  
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 -
1757 1757  (% border="2" style="width:500px" %)
1758 1758  |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state>
1759 1759  |(% style="width:127px" %)**Response**|(% style="width:371px" %)
... ... @@ -1774,6 +1774,8 @@
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  
1722 +(% style="color:#037691" %)**Downlink Payload**
1723 +
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" %)(((
... ... @@ -1799,22 +1799,17 @@
1799 1799  
1800 1800  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.
1801 1801  
1802 -* (% style="color:#037691" %)**AT Command:**
1749 +(% style="color:#037691" %)**AT Command:**
1803 1803  
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 -
1809 1809  (% border="2" style="width:500px" %)
1810 1810  |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state>
1811 1811  |(% style="width:127px" %)**Response**|(% style="width:371px" %)
1812 1812  |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1813 -state :
1755 +**state** :
1814 1814  
1815 -1 : The payload is uploaded without encryption
1757 +**1** : The payload is uploaded without encryption
1816 1816  
1817 -0 : The payload is encrypted when uploaded (default)
1759 +**0** : The payload is encrypted when uploaded (default)
1818 1818  )))
1819 1819  |(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1820 1820  AT+DECRYPT=1
... ... @@ -1833,13 +1833,8 @@
1833 1833  
1834 1834  This command allows you to retrieve and optionally uplink sensor readings through the serial port.
1835 1835  
1836 -* (% style="color:#037691" %)**AT Command:**
1778 +(% style="color:#037691" %)**AT Command**
1837 1837  
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 -
1843 1843  (% border="2" style="width:500px" %)
1844 1844  |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state>
1845 1845  |(% style="width:127px" %)**Response**|(% style="width:371px" %)
... ... @@ -1867,13 +1867,8 @@
1867 1867  
1868 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 1869  
1870 -* (% style="color:#037691" %)**AT Command:**
1807 +(% style="color:#037691" %)**AT Command**
1871 1871  
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 -
1877 1877  (% border="2" style="width:500px" %)
1878 1878  |(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state>
1879 1879  |(% style="width:130px" %)**Response**|(% style="width:368px" %)(((
... ... @@ -1905,17 +1905,6 @@
1905 1905  
1906 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 1907  
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 -
1919 1919  (% style="color:#037691" %)**AT Command**
1920 1920  
1921 1921  (% border="2" style="width:500px" %)
... ... @@ -1957,7 +1957,6 @@
1957 1957  Set DISMACANS=1
1958 1958  )))
1959 1959  
1960 -
1961 1961  ==== 3.4.2.25 Copy downlink to uplink ====
1962 1962  
1963 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.
... ... @@ -1974,31 +1974,21 @@
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 1976  (% border="2" style="width:500px" %)
1977 -|(% style="width:122px" %)Command|(% style="width:376px" %)(((
1897 +|(% style="width:122px" %)**Command**|(% style="width:376px" %)(((
1978 1978  AT+RPL=5
1979 1979  
1980 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 1981  )))
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" %)(((
1902 +|(% style="width:122px" %)**Example**|(% style="width:376px" %)(((
1992 1992  Downlink:
1993 1993  
1994 -11 22 33 44 55 66 77
1905 +01 00 02 58
1995 1995  
1996 1996  Uplink:
1997 1997  
1998 -00 11 22 33 44 55 66 77
1909 +01 01 00 02 58
1999 1999  )))
2000 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.
... ... @@ -2005,14 +2005,16 @@
2005 2005  
2006 2006  
2007 2007  
2008 -==== 3.4.2.26 Query version number and frequency band 、TDC ====
1918 +==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
2009 2009  
1920 +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.
2010 2010  
2011 2011  * (((
2012 2012  (% style="color:#037691" %)**Downlink Payload**(%%)**:**
2013 2013  
2014 -(% style="color:blue" %)**26 01  ** (%%) ~/~/  Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.
1925 +(% 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.
2015 2015  
1927 +
2016 2016  
2017 2017  )))
2018 2018  
... ... @@ -2038,15 +2038,17 @@
2038 2038  The username and  password (API key) you created here are required in the next section.
2039 2039  {{/info}}
2040 2040  
2041 -[[image:tts-mqtt-integration.png||height="625" width="1000"]]
1953 +[[image:tts-mqtt-integration.png]]
2042 2042  
2043 2043  === 3.5.2 Configuring ThingsEye.io ===
2044 2044  
1957 +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.
1958 +
2045 2045  * Login to your [[ThingsEye.io >>https://thingseye.io]]account.
2046 2046  * Under the **Integrations center**, click **Integrations**.
2047 2047  * Click the **Add integration** button (the button with the **+** symbol).
2048 2048  
2049 -[[image:thingseye-io-step-1.png||height="625" width="1000"]]
1963 +[[image:thingseye-io-step-1.png]]
2050 2050  
2051 2051  
2052 2052  On the **Add integration** window, configure the following:
... ... @@ -2061,7 +2061,7 @@
2061 2061  ** Allow create devices or assets
2062 2062  * Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
2063 2063  
2064 -[[image:thingseye-io-step-2.png||height="625" width="1000"]]
1978 +[[image:thingseye-io-step-2.png]]
2065 2065  
2066 2066  
2067 2067  **Uplink data converter:**
... ... @@ -2072,7 +2072,7 @@
2072 2072  * 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]].
2073 2073  * Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
2074 2074  
2075 -[[image:thingseye-io-step-3.png||height="625" width="1000"]]
1989 +[[image:thingseye-io-step-3.png]]
2076 2076  
2077 2077  
2078 2078  **Downlink data converter (this is an optional step):**
... ... @@ -2083,7 +2083,7 @@
2083 2083  * 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]].
2084 2084  * Click the **Next** button. You will be navigated to the **Connection** tab.
2085 2085  
2086 -[[image:thingseye-io-step-4.png||height="625" width="1000"]]
2000 +[[image:thingseye-io-step-4.png]]
2087 2087  
2088 2088  
2089 2089  **Connection:**
... ... @@ -2090,7 +2090,7 @@
2090 2090  
2091 2091  * Choose **Region** from the **Host type**.
2092 2092  * 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/...).
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).
2007 +* 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**).
2094 2094  * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
2095 2095  
2096 2096  [[image:message-1.png]]
... ... @@ -2098,13 +2098,13 @@
2098 2098  
2099 2099  * Click the **Add** button.
2100 2100  
2101 -[[image:thingseye-io-step-5.png||height="625" width="1000"]]
2015 +[[image:thingseye-io-step-5.png]]
2102 2102  
2103 2103  
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.
2018 +Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings and correct any errors.
2105 2105  
2106 2106  
2107 -[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
2021 +[[image:thingseye.io_integrationsCenter_integrations.png]]
2108 2108  
2109 2109  
2110 2110  ==== 3.5.2.1 Viewing integration details ====
... ... @@ -2111,13 +2111,13 @@
2111 2111  
2112 2112  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.
2113 2113  
2114 -[[image:integration-details.png||height="686" width="1000"]]
2028 +[[image:integration-details.png]]
2115 2115  
2116 2116  
2117 2117  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.
2118 2118  
2119 2119  {{info}}
2120 -See also ThingsEye documentation.
2034 +See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
2121 2121  {{/info}}
2122 2122  
2123 2123  ==== **3.5.2.2 Viewing events** ====
... ... @@ -2127,12 +2127,12 @@
2127 2127  * Select **Debug **from the **Event type** dropdown.
2128 2128  * Select the** time frame** from the **time window**.
2129 2129  
2130 -[[image:thingseye-events.png||height="686" width="1000"]]
2044 +[[image:thingseye-events.png]]
2131 2131  
2132 2132  
2133 -* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
2047 +* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
2134 2134  
2135 -[[image:thingseye-json.png||width="1000"]]
2049 +[[image:thingseye-json.png]]
2136 2136  
2137 2137  
2138 2138  ==== **3.5.2.3 Deleting an integration** ====
... ... @@ -2140,12 +2140,17 @@
2140 2140  If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
2141 2141  
2142 2142  
2057 +==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
2058 +
2059 +This will be added soon.
2060 +
2061 +
2143 2143  == 3.6 Interface Details ==
2144 2144  
2145 2145  === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
2146 2146  
2147 2147  
2148 -Supports NPN-type sensors.
2067 +Supports** NPN-type **sensors.
2149 2149  
2150 2150  [[image:1653356991268-289.png]]
2151 2151  
... ... @@ -2267,15 +2267,15 @@
2267 2267  )))
2268 2268  
2269 2269  
2270 -(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
2189 +(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor
2271 2271  
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.
2191 +From the DI port circuit above, activating the photocoupler requires a voltage difference between the DI+ and DI- ports. However, the Dry Contact sensor is a passive component and cannot provide this voltage difference on its own.
2273 2273  
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.
2193 +To detect a Dry Contact, you can supply a power source to one of the pins of the Dry Contact. A reference circuit diagram is shown below.
2275 2275  
2276 2276  [[image:image-20230616235145-1.png]]
2277 2277  
2278 -(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
2197 +(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector
2279 2279  
2280 2280  [[image:image-20240219115718-1.png]]
2281 2281  
... ... @@ -2351,7 +2351,7 @@
2351 2351  [[image:image-20220524100215-10.png||height="382" width="723"]]
2352 2352  
2353 2353  
2354 -== 3.7 LEDs Indicators ==
2273 +== 3.7 LED Indicators ==
2355 2355  
2356 2356  The table below lists the behavior of LED indicators for each port function.
2357 2357  
... ... @@ -2390,13 +2390,14 @@
2390 2390  == 4.1 Connecting the LT-22222-L to a PC ==
2391 2391  
2392 2392  (((
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.
2312 +You can use a USB-to-TTL adapter/converter along with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below.
2394 2394  
2395 -[[image:usb-ttl-programming.png]]
2314 +[[image:usb-ttl-audio-jack-connection.jpg]]
2315 +
2316 +
2396 2396  )))
2397 2397  
2398 2398  
2399 -
2400 2400  (((
2401 2401  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:
2402 2402  )))
... ... @@ -2426,39 +2426,39 @@
2426 2426  * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
2427 2427  * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
2428 2428  * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
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
2349 +* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2350 +* **##AT+DR##**:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
2351 +* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2352 +* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)
2353 +* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency
2354 +* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2355 +* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2356 +* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2357 +* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2358 +* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2359 +* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2360 +* ##**AT+NWKID**##: Get or set the Network ID
2361 +* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)
2362 +* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)
2363 +* ##**AT+CLASS**##: Get or set the Device Class
2364 +* ##**AT+JOIN**##: Join network
2365 +* ##**AT+NJS**##: Get OTAA Join Status
2366 +* ##**AT+SENDB**##: Send hexadecimal data along with the application port
2367 +* ##**AT+SEND**##: Send text data along with the application port
2368 +* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)
2369 +* ##**AT+RECV**##: Print last received data in raw format
2370 +* ##**AT+VER**##: Get current image version and Frequency Band
2371 +* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)
2372 +* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)
2373 +* ##**AT+SNR**##: Get the SNR of the last received packet
2374 +* ##**AT+RSSI**##: Get the RSSI of the last received packet
2375 +* ##**AT+TDC**##: Get or set the application data transmission interval in ms
2376 +* ##**AT+PORT**##: Get or set the application port
2377 +* ##**AT+DISAT**##: Disable AT commands
2378 +* ##**AT+PWORD**##: Set password, max 9 digits
2379 +* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2380 +* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN470
2381 +* ##**AT+CFG**##: Print all settings
2462 2462  )))
2463 2463  
2464 2464  
... ... @@ -2623,7 +2623,7 @@
2623 2623  You will need the following things before proceeding:
2624 2624  
2625 2625  * 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
2626 -* USB to TTL adapter
2546 +* USB to TTL adapter/converter
2627 2627  * 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)
2628 2628  * 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.
2629 2629  
... ... @@ -2633,7 +2633,7 @@
2633 2633  
2634 2634  Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2635 2635  
2636 -[[image:usb-ttl-programming.png]]
2556 +[[image:usb-ttl-audio-jack-connection.jpg]]
2637 2637  
2638 2638  
2639 2639  
Screenshot 2024-11-23 at 18.27.11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +143.4 KB
Content
lt-22222-l-joining.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +301.9 KB
Content
lt33222-l.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +31.3 KB
Content
usb-ttl-audio-jack-connection.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +394.4 KB
Content