Changes for page LT-22222-L -- LoRa I/O Controller User Manual

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 6 removed)
  • Screenshot 2024-11-23 at 18.27.11.png
  • Screenshot 2024-12-08 193946.png
  • lt-22222-l-joining.png
  • lt-22222-l-js-custom-payload-formatter.png
  • lt33222-l.jpg
  • usb-ttl-audio-jack-connection.jpg

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Xiaoling
	1	+XWiki.pradeeka

Content

...	...	@@ -21,7 +21,6 @@
21	21
22	22	== 1.1 What is the LT-22222-L I/O Controller? ==
23	23
24		-
25	25	(((
26	26	(((
27	27	{{info}}
...	...	@@ -44,21 +44,23 @@
44	44	* 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.
45	45	* 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.
46	46	* Setup your own private LoRaWAN network.
	46	+
	47	+{{info}}
	48	+ You can use a LoRaWAN gateway, such as the [[Dragino LG308>>https://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], to expand or create LoRaWAN coverage in your area.
	49	+{{/info}}
47	47	)))
48	48
49	49	(((
50	50
51	51
52		-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.
53	53	)))
54	54
55	55	(% class="wikigeneratedid" %)
56	56	[[image:lorawan-nw.jpg||height="354" width="900"]]
57	57
58		-
59	59	== 1.2 Specifications ==
60	60
61		-
62	62	(% style="color:#037691" %)**Hardware System:**
63	63
64	64	* STM32L072xxxx MCU
...	...	@@ -98,11 +98,8 @@
98	98	* Automatic RF Sense and CAD with ultra-fast AFC.
99	99	* Packet engine up to 256 bytes with CRC.
100	100
101		-
102		-
103	103	== 1.3 Features ==
104	104
105		-
106	106	* LoRaWAN Class A & Class C modes
107	107	* Optional Customized LoRa Protocol
108	108	* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
...	...	@@ -111,11 +111,8 @@
111	111	* Firmware upgradable via program port
112	112	* Counting
113	113
114		-
115		-
116	116	== 1.4 Applications ==
117	117
118		-
119	119	* Smart buildings & home automation
120	120	* Logistics and supply chain management
121	121	* Smart metering
...	...	@@ -123,17 +123,13 @@
123	123	* Smart cities
124	124	* Smart factory
125	125
126		-
127		-
128	128	== 1.5 Hardware Variants ==
129	129
130		-
131		-(% border="1" cellspacing="3" style="width:510px" %)
132		-|(% style="background-color:#4f81bd; color:white; width:94px" %)**Model**|(% style="background-color:#4f81bd; color:white; width:172px" %)**Photo**|(% style="background-color:#4f81bd; color:white; width:244px" %)**Description**
133		-|(% style="width:94px" %)**LT-22222-L**|(% style="width:172px" %)(((
134		-(% style="text-align:center" %)
135		-[[image:lt33222-l.jpg||height="116" width="100"]]
136		-)))|(% style="width:256px" %)(((
	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" %)(((
137	137	* 2 x Digital Input (Bi-direction)
138	138	* 2 x Digital Output
139	139	* 2 x Relay Output (5A@250VAC / 30VDC)
...	...	@@ -142,7 +142,7 @@
142	142	* 1 x Counting Port
143	143	)))
144	144
145		-= 2. Assembling the device =
	136	+== 2. Assembling the device ==
146	146
147	147	== 2.1 Connecting the antenna ==
148	148
...	...	@@ -149,17 +149,17 @@
149	149	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.
150	150
151	151	{{warning}}
152		-**Warning! Do not power on the device without connecting the antenna.**
	143	+Warning! Do not power on the device without connecting the antenna.
153	153	{{/warning}}
154	154
155	155	== 2.2 Terminals ==
156	156
157		-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.
158	158
159		-**Upper screw terminal block (from left to right):**
	150	+Upper screw terminal block (from left to right):
160	160
161	161	(% style="width:634px" %)
162		-|=(% style="width: 295px;" %)Screw Terminal|=(% style="width: 338px;" %)Function
	153	+|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function
163	163	|(% style="width:295px" %)GND|(% style="width:338px" %)Ground
164	164	|(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage
165	165	|(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2
...	...	@@ -167,10 +167,10 @@
167	167	|(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2
168	168	|(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1
169	169
170		-**Lower screw terminal block (from left to right):**
	161	+Lower screw terminal block (from left to right):
171	171
172	172	(% style="width:633px" %)
173		-|=(% style="width: 296px;" %)Screw Terminal|=(% style="width: 334px;" %)Function
	164	+|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function
174	174	|(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1
175	175	|(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1
176	176	|(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2
...	...	@@ -187,7 +187,7 @@
187	187	The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s **positive wire** to the **VIN** and the **negative wire** to the **GND** screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered.
188	188
189	189	{{warning}}
190		-**We recommend that you power on the LT-22222-L after adding its registration information to the LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.**
	181	+**We recommend that you power on the LT-22222-L after configuring its registration information with a LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.**
191	191	{{/warning}}
192	192
193	193
...	...	@@ -222,14 +222,10 @@
222	222
223	223	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.
224	224
	216	+[[image:dragino-ttn-te.jpg]]
225	225
226		-[[image:dragino-lorawan-nw-lt-22222-n.jpg]]
227	227
228		-{{info}}
229		- 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.
230		-{{/info}}
231	231
232		-
233	233	==== 3.2.2.1 Setting up ====
234	234
235	235	* Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet.
...	...	@@ -238,6 +238,7 @@
238	238	* Go to your application's page and click on the **End devices** in the left menu.
239	239	* On the End devices page, click on **+ Register end device**. Two registration options are available:
240	240
	228	+
241	241	==== 3.2.2.2 Using the LoRaWAN Device Repository ====
242	242
243	243	* On the **Register end device** page:
...	...	@@ -250,7 +250,7 @@
250	250	*** **Profile (Region)**: Select the region that matches your device.
251	251	** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
252	252
253		-[[image:lt-22222-l-dev-repo-reg-p1.png]]
	241	+[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
254	254
255	255
256	256	* Register end device page continued...
...	...	@@ -260,8 +260,9 @@
260	260	** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
261	261	** Under **After registration**, select the **View registered end device** option.
262	262
263		-[[image:lt-22222-l-dev-repo-reg-p2.png]]
	251	+[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
264	264
	253	+==== ====
265	265
266	266	==== 3.2.2.3 Adding device manually ====
267	267
...	...	@@ -274,7 +274,7 @@
274	274	** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
275	275	** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
276	276
277		-[[image:lt-22222-l-manually-p1.png]]
	266	+[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
278	278
279	279
280	280	* Register end device page continued...
...	...	@@ -285,26 +285,25 @@
285	285	** Under **After registration**, select the **View registered end device** option.
286	286	** Click the **Register end device** button.
287	287
288		-[[image:lt-22222-l-manually-p2.png]]
	277	+[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
289	289
290	290
291	291	You will be navigated to the **Device overview** page.
292	292
293	293
294		-[[image:lt-22222-device-overview.png]]
	283	+[[image:lt-22222-device-overview.png||height="625" width="1000"]]
295	295
296	296
297	297	==== 3.2.2.4 Joining ====
298	298
299		-On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
	288	+On the Device overview page, click on **Live data** tab. The Live data panel for your device will display.
300	300
301	301	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.
302	302
303	303
304		-[[image:lt-22222-l-joining.png]]
	293	+[[image:lt-22222-join-network.png||height="625" width="1000"]]
305	305
306	306
307		-
308	308	==== 3.2.2.5 Uplinks ====
309	309
310	310
...	...	@@ -315,21 +315,15 @@
315	315	[[image:lt-22222-ul-payload-decoded.png]]
316	316
317	317
318		-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.
	306	+If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **End devices** > **LT-22222-L** > **Payload formatters** > **Uplink**. Then  select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
319	319
320	320	{{info}}
321	321	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.
322	322	{{/info}}
323	323
324		-[[image:lt-22222-ul-payload-fmt.png]]
	312	+[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
325	325
326	326
327		-We also have a payload formatter that resolves some decoding issues present in the Device Repository formatter. You can add it under the Custom JavaScript formatter. It can be found [[here>>https://github.com/dragino/dragino-end-node-decoder/blob/main/LT22222-L/v1.6_decoder_ttn%20.txt]]:
328		-
329		-(% class="wikigeneratedid" %)
330		-[[image:lt-22222-l-js-custom-payload-formatter.png]]
331		-
332		-
333	333	==== 3.2.2.6 Downlinks ====
334	334
335	335	When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
...	...	@@ -618,11 +618,11 @@
618	618
619	619	(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)**
620	620
621		-(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), the counter increases by 1)**
	603	+(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
622	622
623		-(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If the AVI1 voltage is lower than VOLMAX (20000mV =20V), counter increases by 1)**
	605	+(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
624	624
625		-(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), counter increases by 1)**
	607	+(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
626	626	)))
627	627
628	628
...	...	@@ -741,9 +741,9 @@
741	741
742	742	(% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
743	743
744		-**Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
	726	+Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
745	745
746		-**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
	728	+Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
747	747
748	748	AA: Type Code for this downlink Command:
749	749
...	...	@@ -772,7 +772,7 @@
772	772
773	773	MOD6 Payload: total of 11 bytes
774	774
775		-(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
	757	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
776	776	|(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:69px" %)**1**|(% style="background-color:#4f81bd; color:white; width:69px" %)**1**|(% style="background-color:#4f81bd; color:white; width:109px" %)**1**|(% style="background-color:#4f81bd; color:white; width:49px" %)**6**|(% style="background-color:#4f81bd; color:white; width:109px" %)**1**|(% style="background-color:#4f81bd; color:white; width:50px" %)**1**
777	777	|Value|(((
778	778	TRI_A FLAG
...	...	@@ -786,7 +786,7 @@
786	786
787	787	(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
788	788
789		-(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
	771	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
790	790	|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
791	791	|(((
792	792	AV1_LOW
...	...	@@ -810,12 +810,12 @@
810	810
811	811	**Example:**
812	812
813		-10100000: This means the system is configured to use the triggers AV1_LOW and AV2_LOW.
	795	+10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW
814	814
815	815
816	816	(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
817	817
818		-(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
	800	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
819	819	|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
820	820	|(((
821	821	AV1_LOW
...	...	@@ -839,31 +839,31 @@
839	839
840	840	**Example:**
841	841
842		-10000000: The uplink is triggered by AV1_LOW, indicating that the voltage is too low.
	824	+10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.
843	843
844	844
845	845	(% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
846	846
847		-(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
848		-|(% style="width:50px" %)**bit 7**|(% style="width:50px" %)**bit 6**|(% style="width:50px" %)**bit 5**|(% style="width:50px" %)**bit 4**|(% style="width:90px" %)**bit 3**|(% style="width:80px" %)**bit 2**|(% style="width:90px" %)**bit 1**|(% style="width:95px" %)**bit 0**
849		-|(% style="width:49px" %)N/A|(% style="width:53px" %)N/A|(% style="width:53px" %)N/A|(% style="width:55px" %)N/A|(% style="width:99px" %)DI2_STATUS|(% style="width:83px" %)DI2_FLAG|(% style="width:98px" %)DI1_STATUS|(% style="width:85px" %)DI1_FLAG
	829	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:674px" %)
	830	+|(% 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**
	831	+|(% 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
850	850
851		-* Each bit shows which status has been triggered on this uplink.
	833	+* Each bits shows which status has been triggered on this uplink.
852	852
853	853	**Example:**
854	854
855		-00000111: This means both DI1 and DI2 triggers are enabled, and this packet is trigger by DI1.
	837	+00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
856	856
857		-00000101: This means both DI1 and DI2 triggers are enabled.
	839	+00000101: Means both DI1 and DI2 trigger are enabled.
858	858
859	859
860		-(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled.
	842	+(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable.
861	861
862		-Downlink command to poll/request MOD6 status:
	844	+Downlink command to poll MOD6 status:
863	863
864	864	**AB 06**
865	865
866		-When device receives this command, it will send the MOD6 payload.
	848	+When device got this command, it will send the MOD6 payload.
867	867
868	868
869	869	=== 3.3.7 Payload Decoder ===
...	...	@@ -877,7 +877,6 @@
877	877
878	878	== 3.4 ​Configure LT-22222-L via AT Commands or Downlinks ==
879	879
880		-
881	881	(((
882	882	You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks.
883	883	)))
...	...	@@ -892,25 +892,19 @@
892	892
893	893	* (% style="color:blue" %)**Sensor-related commands**(%%):
894	894
895		-
896	896	=== 3.4.1 Common commands ===
897	897
898		-
899	899	(((
900	900	These are available for each sensors and include actions such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]s.
901		-
902		-
903	903	)))
904	904
905	905	=== 3.4.2 Sensor-related commands ===
906	906
907		-
908	908	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.
909	909
910	910
911		-==== 3.4.2.1 Set Transmit/Uplink Interval ====
	887	+==== 3.4.2.1 Set Transmit Interval ====
912	912
913		-
914	914	Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
915	915
916	916	(% style="color:#037691" %)**AT command**
...	...	@@ -917,19 +917,12 @@
917	917
918	918	(% border="2" style="width:500px" %)
919	919	|**Command**|AT+TDC=<time>
920		-|**Parameters**|**time **: uplink interval in milliseconds
921		-|**Get**|AT+TDC=?
922		-|**Response**|(((
923		-current uplink interval
924		-
925		-OK
926		-)))
927		-|**Set**|AT+TDC=<time>
928		-|**Response**|OK
	895	+|**Response**|
	896	+|**Parameters**|**time** : uplink interval is in milliseconds
929	929	|**Example**|(((
930	930	AT+TDC=30000
931	931
932		-Sets the uplink interval to **30 seconds** (30000 milliseconds)
	900	+Sets the uplink interval to 30,000 milliseconds (30 seconds)
933	933	)))
934	934
935	935	(% style="color:#037691" %)**Downlink payload**
...	...	@@ -941,29 +941,27 @@
941	941	|**Parameters**|(((
942	942	**prefix** : 0x01
943	943
944		-**time** : uplink interval in **seconds**, represented by **3  bytes** in **hexadecimal**.
	912	+**time** : uplink interval is in milliseconds, represented by 3  bytes in hexadecimal.
945	945	)))
946	946	|**Example**|(((
947		-01 **00 00 1E**
	915	+01 **00 75 30**
948	948
949		-Sets the uplink interval to **30 seconds**
	917	+Sets the uplink interval to 30,000 milliseconds (30 seconds)
950	950
951		-Conversion: 30 (dec) = 00 00 1E (hex)
	919	+Conversion: 30000 (dec) = 00 75 30 (hex)
952	952
953		-See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30]]
954		-
955		-[[image:Screenshot 2024-11-23 at 18.27.11.png]]
	921	+See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]]
956	956	)))
957	957
958	958	==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
959	959
960		-
961	961	Sets the working mode.
962	962
963	963	(% style="color:#037691" %)**AT command**
964	964
965	965	(% border="2" style="width:500px" %)
966		-|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MOD=<working_mode>
	931	+|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE=<working_mode>
	932	+|(% style="width:97px" %)**Response**|(% style="width:413px" %)
967	967	|(% style="width:97px" %)**Parameters**|(% style="width:413px" %)(((
968	968	**working_mode** :
969	969
...	...	@@ -979,18 +979,6 @@
979	979
980	980	6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5
981	981	)))
982		-|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=?
983		-|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
984		-Current working mode
985		-
986		-OK
987		-)))
988		-|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode>
989		-|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
990		-Attention:Take effect after ATZ
991		-
992		-OK
993		-)))
994	994	|(% style="width:97px" %)**Example**|(% style="width:413px" %)(((
995	995	AT+MOD=2
996	996
...	...	@@ -1013,15 +1013,13 @@
1013	1013	Sets the device to working mode 2 (Double DI Counting + DO + RO)
1014	1014	)))
1015	1015
	970	+==== 3.4.2.3 Poll an uplink ====
1016	1016
1017		-==== 3.4.2.3 Request an uplink from the device ====
	972	+Requests an uplink from LT-22222-L.
1018	1018
1019		-
1020		-Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.
1021		-
1022	1022	(% style="color:#037691" %)**AT command**
1023	1023
1024		-There is no AT Command available for this feature.
	976	+There is no AT Command to request an uplink from LT-22222-L
1025	1025
1026	1026	(% style="color:#037691" %)**Downlink payload**
1027	1027
...	...	@@ -1029,15 +1029,13 @@
1029	1029	|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF
1030	1030	|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08
1031	1031	|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
1032		-08 **FF**
	984	+08 FF
1033	1033
1034	1034	Requests an uplink from LT-22222-L.
1035	1035	)))
1036	1036
1037		-
1038	1038	==== 3.4.2.4 Enable/Disable Trigger Mode ====
1039	1039
1040		-
1041	1041	Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
1042	1042
1043	1043	(% style="color:#037691" %)**AT Command**
...	...	@@ -1065,7 +1065,7 @@
1065	1065	|(% style="width:97px" %)**Parameters**|(% style="width:401px" %)(((
1066	1066	**prefix** : 0x0A 06 (two bytes in hexadecimal)
1067	1067
1068		-**enable/disable trigger_mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
	1018	+**working mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
1069	1069	)))
1070	1070	|(% style="width:97px" %)**Example**|(% style="width:401px" %)(((
1071	1071	0A 06 **01**
...	...	@@ -1073,15 +1073,13 @@
1073	1073	Enable trigger mode for the current working mode
1074	1074	)))
1075	1075
	1026	+==== 3.4.2.5 Poll trigger settings ====
1076	1076
1077		-==== 3.4.2.5 Request trigger settings ====
	1028	+Polls the trigger settings.
1078	1078
1079		-
1080		-Requests the trigger settings.
1081		-
1082	1082	(% style="color:#037691" %)**AT Command:**
1083	1083
1084		-There is no AT Command available for this feature.
	1032	+There is no AT Command for this feature.
1085	1085
1086	1086	(% style="color:#037691" %)**Downlink Payload**
1087	1087
...	...	@@ -1094,10 +1094,8 @@
1094	1094	Uplinks the trigger settings.
1095	1095	)))
1096	1096
1097		-
1098	1098	==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ====
1099	1099
1100		-
1101	1101	Enable or disable DI1/DI2/DI3 as a trigger.
1102	1102
1103	1103	(% style="color:#037691" %)**AT Command**
...	...	@@ -1150,12 +1150,11 @@
1150	1150	Enable DI1 trigger, disable DI2 trigger
1151	1151	)))
1152	1152
1153		-
1154	1154	==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ====
1155	1155
1156		-
1157	1157	Sets DI1 or DI3 (for LT-33222-L) as a trigger.
1158	1158
	1103	+
1159	1159	(% style="color:#037691" %)**AT Command**
1160	1160
1161	1161	(% border="2" style="width:500px" %)
...	...	@@ -1190,12 +1190,11 @@
1190	1190	Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms.
1191	1191	)))
1192	1192
1193		-
1194	1194	==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
1195	1195
1196		-
1197	1197	Sets DI2 as a trigger.
1198	1198
	1142	+
1199	1199	(% style="color:#037691" %)**AT Command**
1200	1200
1201	1201	(% border="2" style="width:500px" %)
...	...	@@ -1225,10 +1225,10 @@
1225	1225	)))
1226	1226	|(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64**
1227	1227
	1172	+==== ====
1228	1228
1229	1229	==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
1230	1230
1231		-
1232	1232	Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1233	1233
1234	1234	(% style="color:#037691" %)**AT Command**
...	...	@@ -1276,10 +1276,8 @@
1276	1276	)))
1277	1277	|(% style="width:104px" %)Note|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1278	1278
1279		-
1280	1280	==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
1281	1281
1282		-
1283	1283	Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1284	1284
1285	1285	(% style="color:#037691" %)**AT Command**
...	...	@@ -1325,10 +1325,8 @@
1325	1325	)))
1326	1326	|(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1327	1327
1328		-
1329	1329	==== 3.4.2.11 Trigger – Set minimum interval ====
1330	1330
1331		-
1332	1332	Sets the AV and AC trigger minimum interval. The device won't respond to a second trigger within this set time after the first trigger.
1333	1333
1334	1334	(% style="color:#037691" %)**AT Command**
...	...	@@ -1362,10 +1362,8 @@
1362	1362	)))
1363	1363	|(% style="width:112px" %)Note|(% style="width:386px" %)(% style="color:red" %)**The time must be greater than 5 minutes.**
1364	1364
1365		-
1366	1366	==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
1367	1367
1368		-
1369	1369	Controls the digital outputs DO1, DO2, and DO3
1370	1370
1371	1371	(% style="color:#037691" %)**AT Command**
...	...	@@ -1396,11 +1396,11 @@
1396	1396	(((
1397	1397	01: Low,  00: High,  11: No action
1398	1398
1399		-(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:383px" %)
1400		-|(% style="background-color:#4f81bd; color:white; width:126px" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white; width:85px" %)**DO1**|(% style="background-color:#4f81bd; color:white; width:86px" %)**DO2**|(% style="background-color:#4f81bd; color:white; width:86px" %)**DO3**
1401		-|(% style="width:126px" %)02  01  00  11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action
1402		-|(% style="width:126px" %)02  00  11  01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low
1403		-|(% style="width:126px" %)02  11  01  00|(% style="width:85px" %)No Action|(% style="width:86px" %)Low|(% style="width:86px" %)High
	1337	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
	1338	+|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**DO1**|(% style="background-color:#4f81bd; color:white" %)**DO2**|(% style="background-color:#4f81bd; color:white" %)**DO3**
	1339	+|02  01  00  11|Low|High|No Action
	1340	+|02  00  11  01|High|No Action|Low
	1341	+|02  11  01  00|No Action|Low|High
1404	1404	)))
1405	1405
1406	1406	(((
...	...	@@ -1414,6 +1414,7 @@
1414	1414	)))
1415	1415	)))
1416	1416
	1355	+==== ====
1417	1417
1418	1418	==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
1419	1419
...	...	@@ -1420,23 +1420,25 @@
1420	1420
1421	1421	* (% style="color:#037691" %)**AT Command**
1422	1422
1423		-There is no AT command to control the digital output.
	1362	+There is no AT Command to control Digital Output
1424	1424
1425	1425
1426	1426	* (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
1427	1427
1428		-(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control
	1367	+(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Set DO1/DO2/DO3 output with time control
1429	1429
	1369	+
1430	1430	This is to control the digital output time of DO pin. Include four bytes:
1431	1431
1432		-(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)
	1372	+(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
1433	1433
1434		-(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode
	1374	+(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode
1435	1435
1436		-**01:** DO pins revert to their original state after the timeout.
1437		-**00:** DO pins switch to an inverted state after the timeout.
	1376	+01: DO pins will change back to original state after timeout.
1438	1438
	1378	+00: DO pins will change to an inverter state after timeout
1439	1439
	1380	+
1440	1440	(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
1441	1441
1442	1442	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
...	...	@@ -1445,7 +1445,7 @@
1445	1445	|0x00|DO1 set to high
1446	1446	|0x11|DO1 NO Action
1447	1447
1448		-(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:
	1389	+(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:
1449	1449
1450	1450	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1451	1451	|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
...	...	@@ -1453,7 +1453,7 @@
1453	1453	|0x00|DO2 set to high
1454	1454	|0x11|DO2 NO Action
1455	1455
1456		-(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:
	1397	+(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:
1457	1457
1458	1458	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1459	1459	|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
...	...	@@ -1461,7 +1461,7 @@
1461	1461	|0x00|DO3 set to high
1462	1462	|0x11|DO3 NO Action
1463	1463
1464		-(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms)
	1405	+(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)
1465	1465
1466	1466
1467	1467	(% style="color:red" %)**Note: **
...	...	@@ -1470,7 +1470,7 @@
1470	1470
1471	1471	Before firmware v1.6.0, the latch time only supported 2 bytes.
1472	1472
1473		-(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
	1414	+(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1474	1474
1475	1475
1476	1476	**Example payload:**
...	...	@@ -1497,16 +1497,16 @@
1497	1497
1498	1498	* (% style="color:#037691" %)**AT Command:**
1499	1499
1500		-There is no AT Command to control the Relay Output
	1441	+There is no AT Command to control Relay Output
1501	1501
1502	1502
1503	1503	* (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
1504	1504
1505		-(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Sets RO1/RO2 output
	1446	+(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Set RO1/RO2 output
1506	1506
1507	1507
1508	1508	(((
1509		-If the payload is 0x030100, it means setting RO1 to close and RO2 to open.
	1450	+If payload is 0x030100, it means setting RO1 to close and RO2 to open.
1510	1510	)))
1511	1511
1512	1512	(((
...	...	@@ -1524,29 +1524,28 @@
1524	1524	|03  00  01|Open|Close
1525	1525	)))
1526	1526
1527		-(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
	1468	+(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
1528	1528
1529	1529
1530	1530	==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
1531	1531
1532		-
1533	1533	Controls the relay output time.
1534	1534
1535	1535	* (% style="color:#037691" %)**AT Command:**
1536	1536
1537		-There is no AT Command to control the Relay Output
	1477	+There is no AT Command to control Relay Output
1538	1538
1539	1539
1540	1540	* (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1541	1541
1542		-(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
	1482	+(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Set RO1/RO2 relay with time control
1543	1543
1544	1544
1545		-This controls the relay output time and includes 4 bytes:
	1485	+This is to control the relay output time. It includes four bytes:
1546	1546
1547		-(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)
	1487	+(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
1548	1548
1549		-(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode
	1489	+(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
1550	1550
1551	1551	01: Relays will change back to their original state after timeout.
1552	1552
...	...	@@ -1553,12 +1553,12 @@
1553	1553	00: Relays will change to the inverter state after timeout.
1554	1554
1555	1555
1556		-(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status:
	1496	+(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
1557	1557
1558	1558	[[image:image-20221008095908-1.png||height="364" width="564"]]
1559	1559
1560	1560
1561		-(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes (cc)**(%%): Latching time. Unit: ms
	1501	+(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms
1562	1562
1563	1563
1564	1564	(% style="color:red" %)**Note:**
...	...	@@ -1568,7 +1568,7 @@
1568	1568	Before firmware v1.6.0, the latch time only supported 2 bytes.
1569	1569
1570	1570
1571		-(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
	1511	+(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1572	1572
1573	1573
1574	1574	**Example payload:**
...	...	@@ -1596,10 +1596,17 @@
1596	1596
1597	1597	When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
1598	1598
	1539	+* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX   ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
	1540	+
	1541	+* (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):**
	1542	+
	1543	+(% style="color:blue" %)**0xA5 aa bb cc   ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc
	1544	+
	1545	+
1599	1599	(% style="color:#037691" %)**AT Command**
1600	1600
1601	1601	(% border="2" style="width:500px" %)
1602		-|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage>,<logic>
	1549	+|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage><logic>
1603	1603	|(% style="width:137px" %)**Response**|(% style="width:361px" %)
1604	1604	|(% style="width:137px" %)**Parameters**|(% style="width:361px" %)(((
1605	1605	**voltage** : voltage threshold in mV
...	...	@@ -1606,9 +1606,9 @@
1606	1606
1607	1607	**logic**:
1608	1608
1609		-**0** : lower than
	1556	+0 : lower than
1610	1610
1611		-**1**: higher than
	1558	+1: higher than
1612	1612
1613	1613	if you leave logic parameter blank, it is considered 0
1614	1614	)))
...	...	@@ -1637,9 +1637,9 @@
1637	1637
1638	1638	**logic**: (1 byte in hexadecimal)
1639	1639
1640		-**0** : lower than
	1587	+0 : lower than
1641	1641
1642		-**1**: higher than
	1589	+1: higher than
1643	1643
1644	1644	if you leave logic parameter blank, it is considered 1 (higher than)
1645	1645	)))
...	...	@@ -1659,12 +1659,24 @@
1659	1659
1660	1660	==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ====
1661	1661
1662		-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.
	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.
1663	1663
	1611	+* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) **
	1612	+
	1613	+(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count
	1614	+
	1615	+(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set
	1616	+
	1617	+
	1618	+* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):**
	1619	+
	1620	+(% style="color:blue" %)**0x A8 aa bb cc dd ee     ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee)
	1621	+
	1622	+
1664	1664	(% style="color:#037691" %)**AT Command**
1665	1665
1666	1666	(% border="2" style="width:500px" %)
1667		-|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter>,<number>
	1626	+|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter><number>
1668	1668	|(% style="width:134px" %)**Response**|(% style="width:364px" %)
1669	1669	|(% style="width:134px" %)**Parameters**|(% style="width:364px" %)(((
1670	1670	**counting_parameter** :
...	...	@@ -1708,8 +1708,14 @@
1708	1708
1709	1709	==== 3.4.2.18 Counting ~-~- Clear Counting ====
1710	1710
1711		-This command clears the counting in counting mode.
	1670	+This feature clears the counting in counting mode.
1712	1712
	1672	+* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT         **(%%) ~/~/ clear all counting
	1673	+
	1674	+* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):**
	1675	+
	1676	+(% style="color:blue" %)**0x A6 01    ** (%%)~/~/ clear all counting
	1677	+
1713	1713	(% style="color:#037691" %)**AT Command**
1714	1714
1715	1715	(% border="2" style="width:500px" %)
...	...	@@ -1727,12 +1727,24 @@
1727	1727	)))
1728	1728	|(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
1729	1729
	1695	+==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1730	1730
1731		-==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ====
	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.
1732	1732
	1699	+* (% style="color:#037691" %)**AT Command:**
1733	1733
1734		-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.
	1701	+(% style="color:blue" %)**AT+COUTIME=60  **(%%)~/~/ Sets the save time to 60 seconds. The device will save the counting result in internal flash every 60 seconds. (Min value: 30 seconds)
1735	1735
	1703	+
	1704	+* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):**
	1705	+
	1706	+(% style="color:blue" %)**0x A7 aa bb cc     ** (%%)~/~/ same as AT+COUTIME =aa bb cc,
	1707	+
	1708	+(((
	1709	+Range: aa bb cc:0 to 16777215,  (unit: seconds)
	1710	+)))
	1711	+
	1712	+
1736	1736	(% style="color:#037691" %)**AT Command**
1737	1737
1738	1738	(% border="2" style="width:500px" %)
...	...	@@ -1761,22 +1761,31 @@
1761	1761	)))
1762	1762
1763	1763
1764		-==== 3.4.2.20 Reset saved RO and DO states ====
	1741	+==== 3.4.2.20 Reset save RO DO state ====
1765	1765
	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.
1766	1766
1767		-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.
	1745	+* (% style="color:#037691" %)**AT Command:**
1768	1768
1769		-(% style="color:#037691" %)**AT Command**
	1747	+(% style="color:blue" %)**AT+RODORESET=1    **(%%)~/~/ RODO will close when the device joining the network. (default)
1770	1770
	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	+
1771	1771	(% border="2" style="width:500px" %)
1772	1772	|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state>
1773	1773	|(% style="width:127px" %)**Response**|(% style="width:371px" %)
1774	1774	|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1775		-**state** :
	1761	+state :
1776	1776
1777		-**0** : RODO will close when the device joins the network. (default)
	1763	+0 : RODO will close when the device joins the network. (default)
1778	1778
1779		-**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.
1780	1780	)))
1781	1781	|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1782	1782	(% style="color:blue" %)**AT+RODORESET=1 **
...	...	@@ -1788,18 +1788,17 @@
1788	1788	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.
1789	1789	)))
1790	1790
1791		-(% style="color:#037691" %)**Downlink Payload**
1792	1792
1793	1793	(% border="2" style="width:500px" %)
1794	1794	|(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state>
1795	1795	|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1796		-**prefix** : AD
	1781	+prefix : AD
1797	1797
1798		-**state** :
	1783	+state :
1799	1799
1800		-**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.
1801	1801
1802		-**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	+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
1803	1803	)))
1804	1804	|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1805	1805	AD **01**
...	...	@@ -1814,181 +1814,84 @@
1814	1814
1815	1815	==== 3.4.2.21 Encrypted payload ====
1816	1816
	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.
1817	1817
1818		-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.
	1804	+* (% style="color:#037691" %)**AT Command:**
1819	1819
1820		-(% style="color:#037691" %)**AT Command:**
	1806	+(% style="color:blue" %)**AT+DECRYPT=1  ** (%%)~/~/ The payload is uploaded without encryption
1821	1821
1822		-(% border="2" style="width:500px" %)
1823		-|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state>
1824		-|(% style="width:127px" %)**Response**|(% style="width:371px" %)
1825		-|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1826		-**state** :
	1808	+(% style="color:blue" %)**AT+DECRYPT=0    **(%%)~/~/  Encrypt when uploading payload (default)
1827	1827
1828		-**1** : The payload is uploaded without encryption
1829	1829
1830		-**0** : The payload is encrypted when uploaded (default)
1831		-)))
1832		-|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1833		-AT+DECRYPT=1
1834	1834
1835		-The payload is uploaded without encryption
1836		-
1837		-AT+DECRYPT=0
1838		-
1839		-The payload is encrypted when uploaded (default)
1840		-)))
1841		-
1842		-There is no downlink payload for this configuration.
1843		-
1844		-
1845	1845	==== 3.4.2.22 Get sensor value ====
1846	1846
1847	1847
1848		-This command allows you to retrieve and optionally uplink sensor readings through the serial port.
	1815	+* (% style="color:#037691" %)**AT Command:**
1849	1849
1850		-(% style="color:#037691" %)**AT Command**
	1817	+(% style="color:blue" %)**AT+GETSENSORVALUE=0    **(%%)~/~/ The serial port retrieves the reading of the current sensor.
1851	1851
1852		-(% border="2" style="width:500px" %)
1853		-|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state>
1854		-|(% style="width:127px" %)**Response**|(% style="width:371px" %)
1855		-|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1856		-**state** :
	1819	+(% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it.
1857	1857
1858		-**0 **: Retrieves the current sensor reading via the serial port.
1859	1859
1860		-**1 **: Retrieves and uploads the current sensor reading via the serial port.
1861		-)))
1862		-|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1863		-AT+GETSENSORVALUE=0
1864	1864
1865		-Retrieves the current sensor reading via the serial port.
	1823	+==== 3.4.2.23 Resets the downlink packet count ====
1866	1866
1867		-AT+GETSENSORVALUE=1
1868	1868
1869		-Retrieves and uplinks the current sensor reading via the serial port.
1870		-)))
	1826	+* (% style="color:#037691" %)**AT Command:**
1871	1871
1872		-There is no downlink payload for this configuration.
	1828	+(% style="color:blue" %)**AT+DISFCNTCHECK=0   **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node will no longer receive downlink packets (default)
1873	1873
	1830	+(% style="color:blue" %)**AT+DISFCNTCHECK=1   **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node resets the downlink packet count and keeps it consistent with the server downlink packet count.
1874	1874
1875		-==== 3.4.2.23 Resetting the downlink packet count ====
1876	1876
1877	1877
1878		-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.
1879		-
1880		-(% style="color:#037691" %)**AT Command**
1881		-
1882		-(% border="2" style="width:500px" %)
1883		-|(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state>
1884		-|(% style="width:130px" %)**Response**|(% style="width:368px" %)(((
1885		-
1886		-)))
1887		-|(% style="width:130px" %)**Parameters**|(% style="width:368px" %)(((
1888		-**state **:
1889		-
1890		-**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).
1891		-
1892		-
1893		-**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.
1894		-)))
1895		-|(% style="width:130px" %)**Example**|(% style="width:368px" %)(((
1896		-AT+DISFCNTCHECK=0
1897		-
1898		-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).
1899		-
1900		-AT+DISFCNTCHECK=1
1901		-
1902		-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.
1903		-)))
1904		-
1905		-There is no downlink payload for this configuration.
1906		-
1907		-
1908	1908	==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ====
1909	1909
1910	1910
1911		-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.
	1837	+* (% style="color:#037691" %)**AT Command:**
1912	1912
1913		-(% style="color:#037691" %)**AT Command**
	1839	+(% style="color:blue" %)**AT+DISMACANS=0**   (%%) ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of 11 bytes (DR0 of US915, DR2 of AS923, DR2 of AU195), the node will send a packet with a payload of 00 and a port of 4. (default)
1914	1914
1915		-(% border="2" style="width:500px" %)
1916		-|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DISMACANS=<state>
1917		-|(% style="width:127px" %)**Response**|(% style="width:371px" %)
1918		-|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1919		-**state** :
	1841	+(% style="color:blue" %)**AT+DISMACANS=1**  (%%) ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of the DR, the node will ignore the MACANS and not reply, and only upload the payload part.
1920	1920
1921		-**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)
1922	1922
1923		-**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.
1924		-)))
1925		-|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1926		-AT+DISMACANS=0
	1844	+* (% style="color:#037691" %)**Downlink Payload **(%%)**:**
1927	1927
1928		-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)
	1846	+(% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set  the DISMACANS=1
1929	1929
1930		-AT+DISMACANS=1
1931	1931
1932		-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.
1933		-)))
1934	1934
1935		-(% style="color:#037691" %)**Downlink Payload**
1936		-
1937		-(% border="2" style="width:500px" %)
1938		-|(% style="width:126px" %)**Payload**|(% style="width:372px" %)<prefix><state>
1939		-|(% style="width:126px" %)**Parameters**|(% style="width:372px" %)(((
1940		-**prefix** : 21
1941		-
1942		-**state** : (2 bytes in hexadecimal)
1943		-
1944		-**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)
1945		-
1946		-**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.
1947		-)))
1948		-|(% style="width:126px" %)**Example**|(% style="width:372px" %)(((
1949		-21 **00 01**
1950		-
1951		-Set DISMACANS=1
1952		-)))
1953		-
1954		-
1955	1955	==== 3.4.2.25 Copy downlink to uplink ====
1956	1956
1957	1957
1958		-This command enables the device to immediately uplink the payload 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.
	1853	+* (% style="color:#037691" %)**AT Command**(%%)**:**
1959	1959
1960		-(% style="color:#037691" %)**AT Command**(%%)**:**
	1855	+(% style="color:blue" %)**AT+RPL=5**   (%%) ~/~/ After receiving the package from the server, it will immediately upload the content of the package to the server, the port number is 100.
1961	1961
1962		-(% style="color:blue" %)**AT+RPL=5**   (%%) ~/~/ After receiving a downlink payload from the server, the device will immediately uplink the payload back to the server using port number 100.
	1857	+Example：**aa xx xx xx xx**         ~/~/ aa indicates whether the configuration has changed, 00 is yes, 01 is no; xx xx xx xx are the bytes sent.
1963	1963
1964		-Example：**aa xx xx xx xx**         ~/~/ **aa** indicates whether the configuration has changed: **00** means YES, and **01** means NO. **xx xx xx xx** are the bytes uplinked back.
1965	1965
1966		-
1967	1967	[[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-20220823173747-6.png?width=1124&height=165&rev=1.1||alt="image-20220823173747-6.png"]]
1968	1968
1969	1969	For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
1970	1970
	1864	+
	1865	+
1971	1971	[[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"]]
1972	1972
1973	1973	For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
1974	1974
1975	1975
1976		-(% style="color:#037691" %)**Downlink Payload**(%%)**:**
1977	1977
1978		-There is no downlink option available for this feature.
	1872	+==== 3.4.2.26 Query version number and frequency band 、TDC ====
1979	1979
1980	1980
1981		-==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
1982		-
1983		-
1984		-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.
1985		-
1986	1986	* (((
1987	1987	(% style="color:#037691" %)**Downlink Payload**(%%)**:**
1988	1988
1989		-(% 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.
	1878	+(% style="color:blue" %)**26 01  ** (%%) ~/~/  Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.
1990	1990
1991		-
1992	1992
1993	1993	)))
1994	1994
...	...	@@ -1999,13 +1999,10 @@
1999	1999
2000	2000	== 3.5 Integrating with ThingsEye.io ==
2001	2001
2002		-
2003	2003	The Things Stack application supports integration with ThingsEye.io. Once integrated, ThingsEye.io acts as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
2004	2004
2005		-
2006	2006	=== 3.5.1 Configuring The Things Stack ===
2007	2007
2008		-
2009	2009	We use The Things Stack Sandbox in this example:
2010	2010
2011	2011	* In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
...	...	@@ -2017,19 +2017,15 @@
2017	2017	The username and  password (API key) you created here are required in the next section.
2018	2018	{{/info}}
2019	2019
2020		-[[image:tts-mqtt-integration.png]]
	1905	+[[image:tts-mqtt-integration.png||height="625" width="1000"]]
2021	2021
2022		-
2023	2023	=== 3.5.2 Configuring ThingsEye.io ===
2024	2024
2025		-
2026		-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.
2027		-
2028	2028	* Login to your [[ThingsEye.io >>https://thingseye.io]]account.
2029	2029	* Under the **Integrations center**, click **Integrations**.
2030	2030	* Click the **Add integration** button (the button with the **+** symbol).
2031	2031
2032		-[[image:thingseye-io-step-1.png]]
	1913	+[[image:thingseye-io-step-1.png||height="625" width="1000"]]
2033	2033
2034	2034
2035	2035	On the **Add integration** window, configure the following:
...	...	@@ -2044,7 +2044,7 @@
2044	2044	** Allow create devices or assets
2045	2045	* Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
2046	2046
2047		-[[image:thingseye-io-step-2.png]]
	1928	+[[image:thingseye-io-step-2.png||height="625" width="1000"]]
2048	2048
2049	2049
2050	2050	**Uplink data converter:**
...	...	@@ -2055,7 +2055,7 @@
2055	2055	* 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]].
2056	2056	* Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
2057	2057
2058		-[[image:thingseye-io-step-3.png]]
	1939	+[[image:thingseye-io-step-3.png||height="625" width="1000"]]
2059	2059
2060	2060
2061	2061	**Downlink data converter (this is an optional step):**
...	...	@@ -2066,7 +2066,7 @@
2066	2066	* 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]].
2067	2067	* Click the **Next** button. You will be navigated to the **Connection** tab.
2068	2068
2069		-[[image:thingseye-io-step-4.png]]
	1950	+[[image:thingseye-io-step-4.png||height="625" width="1000"]]
2070	2070
2071	2071
2072	2072	**Connection:**
...	...	@@ -2073,7 +2073,7 @@
2073	2073
2074	2074	* Choose **Region** from the **Host type**.
2075	2075	* 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/...).
2076		-* 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**).
	1957	+* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The **username **and **password **can be found on the MQTT integration page of your The Things Stack account (see Configuring The Things Stack).
2077	2077	* Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
2078	2078
2079	2079	[[image:message-1.png]]
...	...	@@ -2081,64 +2081,54 @@
2081	2081
2082	2082	* Click the **Add** button.
2083	2083
2084		-[[image:thingseye-io-step-5.png]]
	1965	+[[image:thingseye-io-step-5.png||height="625" width="1000"]]
2085	2085
2086	2086
2087		-Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings and correct any errors.
	1968	+Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings.
2088	2088
2089	2089
2090		-[[image:thingseye.io_integrationsCenter_integrations.png]]
	1971	+[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
2091	2091
2092	2092
2093	2093	==== 3.5.2.1 Viewing integration details ====
2094	2094
2095		-
2096	2096	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.
2097	2097
2098		-[[image:integration-details.png]]
	1978	+[[image:integration-details.png||height="686" width="1000"]]
2099	2099
2100	2100
2101	2101	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.
2102	2102
2103	2103	{{info}}
2104		-See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
	1984	+See also ThingsEye documentation.
2105	2105	{{/info}}
2106	2106
	1987	+==== **3.5.2.2 Viewing events** ====
2107	2107
2108		-==== 3.5.2.2 Viewing events ====
2109		-
2110		-
2111	2111	The **Events **tab displays all the uplink messages from the LT-22222-L.
2112	2112
2113	2113	* Select **Debug **from the **Event type** dropdown.
2114	2114	* Select the** time frame** from the **time window**.
2115	2115
2116		-[[image:thingseye-events.png]]
	1994	+[[image:thingseye-events.png||height="686" width="1000"]]
2117	2117
2118	2118
2119		-* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
	1997	+* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
2120	2120
2121		-[[image:thingseye-json.png]]
	1999	+[[image:thingseye-json.png||width="1000"]]
2122	2122
2123	2123
2124		-==== 3.5.2.3 Deleting an integration ====
	2002	+==== **3.5.2.3 Deleting an integration** ====
2125	2125
2126		-
2127	2127	If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
2128	2128
2129	2129
2130		-==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
2131		-
2132		-
2133		-This will be added soon.
2134		-
2135		-
2136	2136	== 3.6 Interface Details ==
2137	2137
2138	2138	=== 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
2139	2139
2140	2140
2141		-Supports** NPN-type **sensors.
	2012	+Supports NPN-type sensors.
2142	2142
2143	2143	[[image:1653356991268-289.png]]
2144	2144
...	...	@@ -2260,15 +2260,15 @@
2260	2260	)))
2261	2261
2262	2262
2263		-(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor
	2134	+(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
2264	2264
2265		-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.
	2136	+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.
2266	2266
2267		-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.
	2138	+To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram.
2268	2268
2269	2269	[[image:image-20230616235145-1.png]]
2270	2270
2271		-(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector
	2142	+(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
2272	2272
2273	2273	[[image:image-20240219115718-1.png]]
2274	2274
...	...	@@ -2344,9 +2344,8 @@
2344	2344	[[image:image-20220524100215-10.png||height="382" width="723"]]
2345	2345
2346	2346
2347		-== 3.7 LED Indicators ==
	2218	+== 3.7 LEDs Indicators ==
2348	2348
2349		-
2350	2350	The table below lists the behavior of LED indicators for each port function.
2351	2351
2352	2352	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
...	...	@@ -2377,25 +2377,20 @@
2377	2377	|**RO1**|For LT-22222-L: ON when RO1 is closed, OFF when RO1 is open
2378	2378	|**RO2**|For LT-22222-L: ON when RO2 is closed, OFF when RO2 is open
2379	2379
2380		-
2381	2381	= 4. Using AT Commands =
2382	2382
2383		-
2384	2384	The LT-22222-L supports programming using AT Commands.
2385	2385
2386		-
2387	2387	== 4.1 Connecting the LT-22222-L to a PC ==
2388	2388
2389		-
2390	2390	(((
2391		-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.
	2257	+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.
2392	2392
2393		-[[image:usb-ttl-audio-jack-connection.jpg]]
2394		-
2395		-
	2259	+[[image:usb-ttl-programming.png]]
2396	2396	)))
2397	2397
2398	2398
	2263	+
2399	2399	(((
2400	2400	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:
2401	2401	)))
...	...	@@ -2406,10 +2406,7 @@
2406	2406	(((
2407	2407	You can find more details in the [[AT Command Manual>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
2408	2408
2409		-
2410	2410	== 4.2 LT-22222-L related AT commands ==
2411		-
2412		-
2413	2413	)))
2414	2414
2415	2415	(((
...	...	@@ -2428,39 +2428,39 @@
2428	2428	* **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
2429	2429	* **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
2430	2430	* **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
2431		-* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2432		-* **##AT+DR##**:  Get or set the Data Rate. (0-7 corresponding to DR_X)
2433		-* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2434		-* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)
2435		-* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency
2436		-* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2437		-* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2438		-* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2439		-* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2440		-* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2441		-* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2442		-* ##**AT+NWKID**##: Get or set the Network ID
2443		-* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)
2444		-* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)
2445		-* ##**AT+CLASS**##: Get or set the Device Class
2446		-* ##**AT+JOIN**##: Join network
2447		-* ##**AT+NJS**##: Get OTAA Join Status
2448		-* ##**AT+SENDB**##: Send hexadecimal data along with the application port
2449		-* ##**AT+SEND**##: Send text data along with the application port
2450		-* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)
2451		-* ##**AT+RECV**##: Print last received data in raw format
2452		-* ##**AT+VER**##: Get current image version and Frequency Band
2453		-* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)
2454		-* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)
2455		-* ##**AT+SNR**##: Get the SNR of the last received packet
2456		-* ##**AT+RSSI**##: Get the RSSI of the last received packet
2457		-* ##**AT+TDC**##: Get or set the application data transmission interval in ms
2458		-* ##**AT+PORT**##: Get or set the application port
2459		-* ##**AT+DISAT**##: Disable AT commands
2460		-* ##**AT+PWORD**##: Set password, max 9 digits
2461		-* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2462		-* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN470
2463		-* ##**AT+CFG**##: Print all settings
	2293	+* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
	2294	+* AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)
	2295	+* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
	2296	+* AT+PNM: Get or set the public network mode. (0: off, 1: on)
	2297	+* AT+RX2FQ: Get or set the Rx2 window frequency
	2298	+* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
	2299	+* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
	2300	+* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
	2301	+* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
	2302	+* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
	2303	+* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
	2304	+* AT+NWKID: Get or set the Network ID
	2305	+* AT+FCU: Get or set the Frame Counter Uplink (FCntUp)
	2306	+* AT+FCD: Get or set the Frame Counter Downlink (FCntDown)
	2307	+* AT+CLASS: Get or set the Device Class
	2308	+* AT+JOIN: Join network
	2309	+* AT+NJS: Get OTAA Join Status
	2310	+* AT+SENDB: Send hexadecimal data along with the application port
	2311	+* AT+SEND: Send text data along with the application port
	2312	+* AT+RECVB: Print last received data in binary format (with hexadecimal values)
	2313	+* AT+RECV: Print last received data in raw format
	2314	+* AT+VER: Get current image version and Frequency Band
	2315	+* AT+CFM: Get or Set the confirmation mode (0-1)
	2316	+* AT+CFS: Get confirmation status of the last AT+SEND (0-1)
	2317	+* AT+SNR: Get the SNR of the last received packet
	2318	+* AT+RSSI: Get the RSSI of the last received packet
	2319	+* AT+TDC: Get or set the application data transmission interval in ms
	2320	+* AT+PORT: Get or set the application port
	2321	+* AT+DISAT: Disable AT commands
	2322	+* AT+PWORD: Set password, max 9 digits
	2323	+* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode
	2324	+* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470
	2325	+* AT+CFG: Print all settings
2464	2464	)))
2465	2465
2466	2466
...	...	@@ -2606,19 +2606,16 @@
2606	2606
2607	2607	== 5.1 Counting how many objects pass through the flow line ==
2608	2608
2609		-
2610	2610	See [[How to set up to setup counting for objects passing through the flow line>>How to set up to count objects pass in flow line]]?
2611	2611
2612	2612
2613	2613	= 6. FAQ =
2614	2614
2615		-
2616	2616	This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
2617	2617
2618	2618
2619	2619	== 6.1 How to update the firmware? ==
2620	2620
2621		-
2622	2622	Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to:
2623	2623
2624	2624	* Support new features
...	...	@@ -2628,7 +2628,7 @@
2628	2628	You will need the following things before proceeding:
2629	2629
2630	2630	* 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
2631		-* USB to TTL adapter/converter
	2490	+* USB to TTL adapter
2632	2632	* 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)
2633	2633	* 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.
2634	2634
...	...	@@ -2638,7 +2638,7 @@
2638	2638
2639	2639	Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2640	2640
2641		-[[image:usb-ttl-audio-jack-connection.jpg]]
	2500	+[[image:usb-ttl-programming.png]]
2642	2642
2643	2643
2644	2644
...	...	@@ -2671,8 +2671,6 @@
2671	2671	(((
2672	2672	(((
2673	2673	== 6.2 How to change the LoRaWAN frequency band/region? ==
2674		-
2675		-
2676	2676	)))
2677	2677	)))
2678	2678
...	...	@@ -2684,8 +2684,6 @@
2684	2684
2685	2685
2686	2686	== 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
2687		-
2688		-
2689	2689	)))
2690	2690
2691	2691	(((
...	...	@@ -2759,13 +2759,11 @@
2759	2759
2760	2760	== 6.4 How to change the uplink interval? ==
2761	2761
2762		-
2763	2763	Please see this link: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/]]
2764	2764
2765	2765
2766	2766	== 6.5 Can I see the counting event in the serial output? ==
2767	2767
2768		-
2769	2769	(((
2770	2770	You can run the AT command **AT+DEBUG** to view the counting event in the serial output. If the firmware is too old and doesn’t support AT+DEBUG, update to the latest firmware first.
2771	2771
...	...	@@ -2772,7 +2772,6 @@
2772	2772
2773	2773	== 6.6 Can I use point-to-point communication with LT-22222-L? ==
2774	2774
2775		-
2776	2776	Yes, you can. Please refer to the [[Point-to-Point Communication of LT-22222-L>>https://wiki.dragino.com/xwiki/bin/view/Main/%20Point%20to%20Point%20Communication%20of%20LT-22222-L/]] page. The firmware that supports point-to-point communication can be found [[here>>https://github.com/dragino/LT-22222-L/releases]].
2777	2777
2778	2778
...	...	@@ -2781,16 +2781,13 @@
2781	2781	(((
2782	2782	== 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
2783	2783
2784		-
2785	2785	* If the device is not properly shut down and is directly powered off.
2786	2786	* It will default to a power-off state.
2787	2787	* In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
2788	2788	* After a restart, the status before the power failure will be read from flash.
2789	2789
2790		-
2791	2791	== 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
2792	2792
2793		-
2794	2794	The LT-22222-L's built-in relay is Normally Open (NO). You can use an external relay to achieve a Normally Closed (NC) configuration. The circuit diagram is shown below:
2795	2795
2796	2796
...	...	@@ -2799,19 +2799,16 @@
2799	2799
2800	2800	== 6.9 Can the LT-22222-L save the RO state? ==
2801	2801
2802		-
2803	2803	To enable this feature, the firmware version must be 1.6.0 or higher.
2804	2804
2805	2805
2806	2806	== 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
2807	2807
2808		-
2809	2809	It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
2810	2810
2811	2811
2812	2812	= 7. Troubleshooting =
2813	2813
2814		-
2815	2815	This section provides some known troubleshooting tips.
2816	2816
2817	2817
...	...	@@ -2820,8 +2820,6 @@
2820	2820	(((
2821	2821	(((
2822	2822	== 7.1 Downlink isn't working. How can I solve this? ==
2823		-
2824		-
2825	2825	)))
2826	2826	)))
2827	2827
...	...	@@ -2833,8 +2833,6 @@
2833	2833
2834	2834
2835	2835	== 7.2 Having trouble uploading an image? ==
2836		-
2837		-
2838	2838	)))
2839	2839
2840	2840	(((
...	...	@@ -2845,8 +2845,6 @@
2845	2845
2846	2846
2847	2847	== 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
2848		-
2849		-
2850	2850	)))
2851	2851
2852	2852	(((
...	...	@@ -2856,7 +2856,6 @@
2856	2856
2857	2857	== 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? ==
2858	2858
2859		-
2860	2860	The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
2861	2861	Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2862	2862
...	...	@@ -2863,7 +2863,6 @@
2863	2863
2864	2864	= 8. Ordering information =
2865	2865
2866		-
2867	2867	(% style="color:#4f81bd" %)**LT-22222-L-XXX:**
2868	2868
2869	2869	(% style="color:#4f81bd" %)**XXX:**
...	...	@@ -2878,11 +2878,8 @@
2878	2878	* (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865
2879	2879	* (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779
2880	2880
2881		-
2882		-
2883	2883	= 9. Package information =
2884	2884
2885		-
2886	2886	**Package includes**:
2887	2887
2888	2888	* 1 x LT-22222-L I/O Controller
...	...	@@ -2897,11 +2897,8 @@
2897	2897	* Package Size / pcs : 14.5 x 8 x 5 cm
2898	2898	* Weight / pcs : 170 g
2899	2899
2900		-
2901		-
2902	2902	= 10. Support =
2903	2903
2904		-
2905	2905	* (((
2906	2906	Support is available Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different time zones, we cannot offer live support. However, your questions will be answered as soon as possible within the aforementioned schedule.
2907	2907	)))
...	...	@@ -2913,7 +2913,6 @@
2913	2913
2914	2914	= 11. Reference​​​​​ =
2915	2915
2916		-
2917	2917	* LT-22222-L: [[http:~~/~~/www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html>>url:http://www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html]]
2918	2918	* [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]]
2919	2919	* [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]

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

Screenshot 2024-12-08 193946.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.pradeeka

Size

...	...	@@ -1,1 +1,0 @@
1		-32.4 KB

Content

lt-22222-l-joining.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.pradeeka

Size

...	...	@@ -1,1 +1,0 @@
1		-301.9 KB

Content

lt-22222-l-js-custom-payload-formatter.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.pradeeka

Size

...	...	@@ -1,1 +1,0 @@
1		-453.9 KB

Content

lt33222-l.jpg

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.pradeeka

Size

...	...	@@ -1,1 +1,0 @@
1		-31.3 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