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, 5 removed)
  • Screenshot 2024-12-08 193946.png
  • lt-22222-l-dashboard.png
  • lt-22222-l-joining.png
  • lt-22222-l-js-custom-payload-formatter.png
  • lt33222-l.jpg

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ting
	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}}
...	...	@@ -55,10 +55,8 @@
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
...	...	@@ -100,7 +100,6 @@
100	100
101	101	== 1.3 Features ==
102	102
103		-
104	104	* LoRaWAN Class A & Class C modes
105	105	* Optional Customized LoRa Protocol
106	106	* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
...	...	@@ -111,7 +111,6 @@
111	111
112	112	== 1.4 Applications ==
113	113
114		-
115	115	* Smart buildings & home automation
116	116	* Logistics and supply chain management
117	117	* Smart metering
...	...	@@ -121,15 +121,13 @@
121	121
122	122	== 1.5 Hardware Variants ==
123	123
124		-
125		-(% border="1" cellspacing="3" style="width:510px" %)
126		-|(% 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**
127		-|(% style="width:94px" %)**LT-33222-L**|(% style="width:172px" %)(((
128		-(% style="text-align:center" %)
129		-[[image:lt33222-l.jpg||height="110" width="95"]]
130		-)))|(% style="width:256px" %)(((
131		-* 3 x Digital Input (Bi-direction)
132		-* 3 x Digital Output
	119	+(% style="width:524px" %)
	120	+|(% style="width:94px" %)**Model**|(% style="width:98px" %)**Photo**|(% style="width:329px" %)**Description**
	121	+|(% style="width:94px" %)**LT33222-L**|(% style="width:98px" %)(((
	122	+
	123	+)))|(% style="width:329px" %)(((
	124	+* 2 x Digital Input (Bi-direction)
	125	+* 2 x Digital Output
133	133	* 2 x Relay Output (5A@250VAC / 30VDC)
134	134	* 2 x 0~~20mA Analog Input (res:0.01mA)
135	135	* 2 x 0~~30V Analog Input (res:0.01v)
...	...	@@ -140,7 +140,6 @@
140	140
141	141	== 2.1 Connecting the antenna ==
142	142
143		-
144	144	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.
145	145
146	146	{{warning}}
...	...	@@ -147,45 +147,42 @@
147	147	**Warning! Do not power on the device without connecting the antenna.**
148	148	{{/warning}}
149	149
150		-
151	151	== 2.2 Terminals ==
152	152
	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.
153	153
154		-The  LT-22222-L has two screw terminal blocks. The upper screw terminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals.
155		-
156	156	**Upper screw terminal block (from left to right):**
157	157
158		-(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:381px" %)
159		-|=(% style="width: 139px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 242px;background-color:#4f81bd;color:white" %)Function
160		-|(% style="width:139px" %)GND|(% style="width:242px" %)Ground
161		-|(% style="width:139px" %)VIN|(% style="width:242px" %)Input Voltage
162		-|(% style="width:139px" %)AVI2|(% style="width:242px" %)Analog Voltage Input Terminal 2
163		-|(% style="width:139px" %)AVI1|(% style="width:242px" %)Analog Voltage Input Terminal 1
164		-|(% style="width:139px" %)ACI2|(% style="width:242px" %)Analog Current Input Terminal 2
165		-|(% style="width:139px" %)ACI1|(% style="width:242px" %)Analog Current Input Terminal 1
	148	+(% style="width:634px" %)
	149	+|=(% style="width: 295px;" %)Screw Terminal|=(% style="width: 338px;" %)Function
	150	+|(% style="width:295px" %)GND|(% style="width:338px" %)Ground
	151	+|(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage
	152	+|(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2
	153	+|(% style="width:295px" %)AVI1|(% style="width:338px" %)Analog Voltage Input Terminal 1
	154	+|(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2
	155	+|(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1
166	166
167	167	**Lower screw terminal block (from left to right):**
168	168
169		-(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:253px" %)
170		-|=(% style="width: 125px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 128px;background-color:#4f81bd;color:white" %)Function
171		-|(% style="width:125px" %)RO1-2|(% style="width:128px" %)Relay Output 1
172		-|(% style="width:125px" %)RO1-1|(% style="width:128px" %)Relay Output 1
173		-|(% style="width:125px" %)RO2-2|(% style="width:128px" %)Relay Output 2
174		-|(% style="width:125px" %)RO2-1|(% style="width:128px" %)Relay Output 2
175		-|(% style="width:125px" %)DI2+|(% style="width:128px" %)Digital Input 2
176		-|(% style="width:125px" %)DI2-|(% style="width:128px" %)Digital Input 2
177		-|(% style="width:125px" %)DI1+|(% style="width:128px" %)Digital Input 1
178		-|(% style="width:125px" %)DI1-|(% style="width:128px" %)Digital Input 1
179		-|(% style="width:125px" %)DO2|(% style="width:128px" %)Digital Output 2
180		-|(% style="width:125px" %)DO1|(% style="width:128px" %)Digital Output 1
	159	+(% style="width:633px" %)
	160	+|=(% style="width: 296px;" %)Screw Terminal|=(% style="width: 334px;" %)Function
	161	+|(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1
	162	+|(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1
	163	+|(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2
	164	+|(% style="width:296px" %)RO2-1|(% style="width:334px" %)Relay Output 2
	165	+|(% style="width:296px" %)DI2+|(% style="width:334px" %)Digital Input 2
	166	+|(% style="width:296px" %)DI2-|(% style="width:334px" %)Digital Input 2
	167	+|(% style="width:296px" %)DI1+|(% style="width:334px" %)Digital Input 1
	168	+|(% style="width:296px" %)DI1-|(% style="width:334px" %)Digital Input 1
	169	+|(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
	170	+|(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
181	181
182	182	== 2.3 Connecting LT-22222-L to a Power Source ==
183	183
184		-
185	185	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.
186	186
187	187	{{warning}}
188		-**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.**
	177	+**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.**
189	189	{{/warning}}
190	190
191	191
...	...	@@ -194,27 +194,23 @@
194	194
195	195	= 3. Registering LT-22222-L with a LoRaWAN Network Server =
196	196
197		-
198	198	The LT-22222-L supports both OTAA (Over-the-Air Activation) and ABP (Activation By Personalization) methods to activate with a LoRaWAN Network Server. However, OTAA is the most secure method for activating a device with a LoRaWAN Network Server. OTAA regenerates session keys upon initial registration and regenerates new session keys after any subsequent reboots. By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode.
199	199
200	200
201		-== 3.1 Prerequisites ==
	189	+=== 3.2.1 Prerequisites ===
202	202
	191	+The LT-22222-L comes with device registration information such as DevEUI, AppEUI, and AppKey that allows you to register it with a LoRaWAN network. These registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference.
203	203
204		-The LT-22222-L comes with device registration information such as DevEUI, AppEUI, and AppKey which allows you to register it with a LoRaWAN network. This registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference.
205		-
206	206	[[image:image-20230425173427-2.png||height="246" width="530"]]
207	207
208	208	{{info}}
209		-If you are unable to set the provided root key and other identifiers in the network server, you must generate new keys and identifiers with the network server and configure the device with them using AT commands.
	196	+In case you can't set the root key and other identifiers in the network server and must use them from the server, you can use [[AT Commands>>||anchor="H4.UseATCommand"]] to configure them on the device.
210	210	{{/info}}
211	211
212	212	The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
213	213
	201	+=== 3.2.2 The Things Stack ===
214	214
215		-== 3.2 The Things Stack ==
216		-
217		-
218	218	This section guides you through how to register your LT-22222-L with The Things Stack Sandbox.
219	219
220	220	{{info}}
...	...	@@ -225,7 +225,7 @@
225	225	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.
226	226
227	227
228		-[[image:dragino-lorawan-nw-lt-22222-n.jpg||height="374" width="1400"]]
	213	+[[image:dragino-lorawan-nw-lt-22222-n.jpg]]
229	229
230	230	{{info}}
231	231	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.
...	...	@@ -232,9 +232,8 @@
232	232	{{/info}}
233	233
234	234
235		-=== 3.2.1 Setting up ===
	220	+==== 3.2.2.1 Setting up ====
236	236
237		-
238	238	* Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet.
239	239	* Log in to your The Things Stack Sandbox account.
240	240	* Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs).
...	...	@@ -241,9 +241,8 @@
241	241	* Go to your application's page and click on the **End devices** in the left menu.
242	242	* On the End devices page, click on **+ Register end device**. Two registration options are available:
243	243
244		-==== 3.2.1.1 Using the LoRaWAN Device Repository ====
	228	+==== 3.2.2.2 Using the LoRaWAN Device Repository ====
245	245
246		-
247	247	* On the **Register end device** page:
248	248	** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
249	249	** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists.
...	...	@@ -254,7 +254,7 @@
254	254	*** **Profile (Region)**: Select the region that matches your device.
255	255	** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
256	256
257		-[[image:lt-22222-l-dev-repo-reg-p1.png]]
	240	+[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
258	258
259	259
260	260	* Register end device page continued...
...	...	@@ -261,21 +261,14 @@
261	261	** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network'.
262	262	** In the **DevEUI** field, enter the **DevEUI**.
263	263	** In the **AppKey** field, enter the **AppKey.**
264		-** In the **End device ID** field, enter a unique name for your LT-22222-L within this application.
	247	+** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
265	265	** Under **After registration**, select the **View registered end device** option.
266		-** Click **Register end device** button.
267	267
268		-[[image:lt-22222-l-dev-repo-reg-p2.png]]
	250	+[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
269	269
270	270
271		-* You will be navigated to the **Device overview** page.
	253	+==== 3.2.2.3 Adding device manually ====
272	272
273		-[[image:lt-22222-device-overview.png]]
274		-
275		-
276		-==== 3.2.1.2 Adding device manually ====
277		-
278		-
279	279	* On the **Register end device** page:
280	280	** Select the option **Enter end device specifies manually** under **Input method**.
281	281	** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
...	...	@@ -285,7 +285,7 @@
285	285	** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
286	286	** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
287	287
288		-[[image:lt-22222-l-manually-p1.png]]
	264	+[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
289	289
290	290
291	291	* Register end device page continued...
...	...	@@ -296,57 +296,49 @@
296	296	** Under **After registration**, select the **View registered end device** option.
297	297	** Click the **Register end device** button.
298	298
299		-[[image:lt-22222-l-manually-p2.png]]
	275	+[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
300	300
301	301
302	302	You will be navigated to the **Device overview** page.
303	303
304	304
305		-[[image:lt-22222-device-overview.png]]
	281	+[[image:lt-22222-device-overview.png||height="625" width="1000"]]
306	306
307	307
308		-=== 3.2.2 Joining ===
	284	+==== 3.2.2.4 Joining ====
309	309
	286	+On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
310	310
311		-On the end device's page (in this case, lt-22222-l), click on **Live data** tab. The Live data panel for your device will display. Initially, it is blank.
312		-
313	313	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.
314	314
315	315
316		-[[image:lt-22222-l-joining.png]]
	291	+[[image:lt-22222-join-network.png||height="625" width="1000"]]
317	317
318	318
319		-=== 3.2.3 Uplinks ===
	294	+==== 3.2.2.5 Uplinks ====
320	320
321	321
322		-After successfully joining, the device will send its first **uplink data message** to The Things Stack application it belongs to (in this example, it is **dragino-docs**). When the LT-22222-L sends an uplink message to the server, the **TX LED** turns on for **1 second**. By default, you will receive an uplink data message from the device every 10 minutes.
	297	+After successfully joining, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**). When the LT-22222-L sends an uplink message to the server, the **TX LED** turns on for **1 second**. By default, you will receive an uplink data message from the device every 10 minutes.
323	323
324		-Click on one of the **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the **decode_payload {}** JSON object.
	299	+Click on one of a **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the decode_payload {} JSON object.
325	325
326	326	[[image:lt-22222-ul-payload-decoded.png]]
327	327
328	328
329		-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.
	304	+If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **Applications > your application > End devices** > **your end device** > **Payload formatters** > **Uplink**. Then  select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
330	330
331	331	{{info}}
332	332	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.
333	333	{{/info}}
334	334
335		-[[image:lt-22222-ul-payload-fmt.png]]
	310	+[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
336	336
337	337
338		-We have written a payload formatter that resolves some decoding issues present in The Things Stack Device Repository payload 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]]:
	313	+==== 3.2.2.6 Downlinks ====
339	339
340		-(% class="wikigeneratedid" %)
341		-[[image:lt-22222-l-js-custom-payload-formatter.png]]
	315	+When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
342	342
343	343
344		-=== 3.2.4 Downlinks ===
345		-
346		-
347		-When the LT-22222-L receives a downlink message from the LoRaWAN Network Server, the **RX LED** turns on for **1 second**.
348		-
349		-
350	350	== 3.3 Working Modes and Uplink Payload formats ==
351	351
352	352
...	...	@@ -366,10 +366,8 @@
366	366
367	367	The uplink messages are sent over LoRaWAN FPort=2. By default, an uplink message is sent every 10 minutes.
368	368
369		-
370	370	=== 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
371	371
372		-
373	373	(((
374	374	This is the default mode.
375	375
...	...	@@ -442,7 +442,6 @@
442	442
443	443	MOD = 1
444	444
445		-
446	446	=== 3.3.2 AT+MOD~=2, (Double DI Counting) ===
447	447
448	448
...	...	@@ -521,7 +521,6 @@
521	521
522	522	=== 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI ===
523	523
524		-
525	525	(% style="color:red" %)**Note: The maximum count depends on the bytes it is.
526	526	The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
527	527	It starts counting again when it reaches the maximum value.**
...	...	@@ -575,7 +575,6 @@
575	575
576	576	=== 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting ===
577	577
578		-
579	579	(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
580	580	The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
581	581	It starts counting again when it reaches the maximum value.**
...	...	@@ -635,17 +635,16 @@
635	635
636	636	(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)**
637	637
638		-(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), the counter increases by 1)**
	601	+(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
639	639
640		-(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If the AVI1 voltage is lower than VOLMAX (20000mV =20V), counter increases by 1)**
	603	+(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
641	641
642		-(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), counter increases by 1)**
	605	+(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
643	643	)))
644	644
645	645
646	646	=== 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI ===
647	647
648		-
649	649	(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
650	650	The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
651	651	It starts counting again when it reaches the maximum value.**
...	...	@@ -732,7 +732,7 @@
732	732
733	733	AT+AVLIM=3000,6000,0,2000 (triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V)
734	734
735		-AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage is lower than 5V. Use 0 for parameters that are not in use)
	697	+AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage lower than 5V. Use 0 for parameters that are not in use)
736	736
737	737
738	738	(% style="color:#4f81bd" %)**Trigger based on current**:
...	...	@@ -759,9 +759,9 @@
759	759
760	760	(% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
761	761
762		-**Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
	724	+Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
763	763
764		-**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
	726	+Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
765	765
766	766	AA: Type Code for this downlink Command:
767	767
...	...	@@ -788,9 +788,9 @@
788	788
789	789	(% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:**
790	790
791		-MOD6 Payload: a total of 11 bytes
	753	+MOD6 Payload: total of 11 bytes
792	792
793		-(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
	755	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
794	794	|(% 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**
795	795	|Value|(((
796	796	TRI_A FLAG
...	...	@@ -802,9 +802,9 @@
802	802	MOD(6)
803	803	)))
804	804
805		-(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Total 1 byte as below.
	767	+(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
806	806
807		-(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
	769	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
808	808	|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
809	809	|(((
810	810	AV1_LOW
...	...	@@ -828,12 +828,12 @@
828	828
829	829	**Example:**
830	830
831		-10100000: This means the system is configured to use the triggers AV1_LOW and AV2_LOW.
	793	+10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW
832	832
833	833
834		-(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is triggered. Total 1 byte as below.
	796	+(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
835	835
836		-(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
	798	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
837	837	|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
838	838	|(((
839	839	AV1_LOW
...	...	@@ -857,31 +857,31 @@
857	857
858	858	**Example:**
859	859
860		-10000000: The uplink is triggered by AV1_LOW, indicating that the voltage is too low.
	822	+10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.
861	861
862	862
863		-(% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is triggered. Total 1 byte as below.
	825	+(% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
864	864
865		-(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
866		-|(% 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**
867		-|(% 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
	827	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:674px" %)
	828	+|(% 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**
	829	+|(% 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
868	868
869		-* Each bit shows which status has been triggered on this uplink.
	831	+* Each bits shows which status has been triggered on this uplink.
870	870
871	871	**Example:**
872	872
873		-00000111: This means both DI1 and DI2 triggers are enabled, and this packet is triggered by DI1.
	835	+00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
874	874
875		-00000101: This means both DI1 and DI2 triggers are enabled.
	837	+00000101: Means both DI1 and DI2 trigger are enabled.
876	876
877	877
878		-(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled.
	840	+(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable.
879	879
880		-Downlink command to poll/request MOD6 status:
	842	+Downlink command to poll MOD6 status:
881	881
882	882	**AB 06**
883	883
884		-When the device receives this command, it will send the MOD6 payload.
	846	+When device got this command, it will send the MOD6 payload.
885	885
886	886
887	887	=== 3.3.7 Payload Decoder ===
...	...	@@ -895,7 +895,6 @@
895	895
896	896	== 3.4 ​Configure LT-22222-L via AT Commands or Downlinks ==
897	897
898		-
899	899	(((
900	900	You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks.
901	901	)))
...	...	@@ -902,7 +902,7 @@
902	902
903	903	(((
904	904	(((
905		-There are two types of commands:
	866	+There are two tytes of commands:
906	906	)))
907	907	)))
908	908
...	...	@@ -912,22 +912,17 @@
912	912
913	913	=== 3.4.1 Common commands ===
914	914
915		-
916	916	(((
917		-These are available for each sensor 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.
918		-
919		-
	877	+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.
920	920	)))
921	921
922	922	=== 3.4.2 Sensor-related commands ===
923	923
924		-
925	925	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.
926	926
927	927
928	928	==== 3.4.2.1 Set Transmit/Uplink Interval ====
929	929
930		-
931	931	Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
932	932
933	933	(% style="color:#037691" %)**AT command**
...	...	@@ -934,15 +934,8 @@
934	934
935	935	(% border="2" style="width:500px" %)
936	936	|**Command**|AT+TDC=<time>
937		-|**Parameters**|**time **: uplink interval in milliseconds
938		-|**Get**|AT+TDC=?
939		-|**Response**|(((
940		-current uplink interval
941		-
942		-OK
943		-)))
944		-|**Set**|AT+TDC=<time>
945		-|**Response**|OK
	893	+|**Response**|
	894	+|**Parameters**|**time** : uplink interval is in **milliseconds**
946	946	|**Example**|(((
947	947	AT+TDC=30000
948	948
...	...	@@ -958,7 +958,7 @@
958	958	|**Parameters**|(((
959	959	**prefix** : 0x01
960	960
961		-**time** : uplink interval in **seconds**, represented by **3  bytes** in **hexadecimal**.
	910	+**time** : uplink interval is in **seconds**, represented by **3  bytes** in **hexadecimal**.
962	962	)))
963	963	|**Example**|(((
964	964	01 **00 00 1E**
...	...	@@ -974,13 +974,13 @@
974	974
975	975	==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
976	976
977		-
978	978	Sets the working mode.
979	979
980	980	(% style="color:#037691" %)**AT command**
981	981
982	982	(% border="2" style="width:500px" %)
983		-|(% 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" %)
984	984	|(% style="width:97px" %)**Parameters**|(% style="width:413px" %)(((
985	985	**working_mode** :
986	986
...	...	@@ -996,18 +996,6 @@
996	996
997	997	6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5
998	998	)))
999		-|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=?
1000		-|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
1001		-Current working mode
1002		-
1003		-OK
1004		-)))
1005		-|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode>
1006		-|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
1007		-Attention:Take effect after ATZ
1008		-
1009		-OK
1010		-)))
1011	1011	|(% style="width:97px" %)**Example**|(% style="width:413px" %)(((
1012	1012	AT+MOD=2
1013	1013
...	...	@@ -1030,9 +1030,8 @@
1030	1030	Sets the device to working mode 2 (Double DI Counting + DO + RO)
1031	1031	)))
1032	1032
1033		-==== 3.4.2.3 Request an uplink from the device ====
	970	+==== 3.4.2.3 Poll an uplink ====
1034	1034
1035		-
1036	1036	Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.
1037	1037
1038	1038	(% style="color:#037691" %)**AT command**
...	...	@@ -1052,7 +1052,6 @@
1052	1052
1053	1053	==== 3.4.2.4 Enable/Disable Trigger Mode ====
1054	1054
1055		-
1056	1056	Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
1057	1057
1058	1058	(% style="color:#037691" %)**AT Command**
...	...	@@ -1088,11 +1088,10 @@
1088	1088	Enable trigger mode for the current working mode
1089	1089	)))
1090	1090
1091		-==== 3.4.2.5 Request trigger settings ====
	1026	+==== 3.4.2.5 Poll trigger settings ====
1092	1092
	1028	+Polls the trigger settings.
1093	1093
1094		-Requests the trigger settings.
1095		-
1096	1096	(% style="color:#037691" %)**AT Command:**
1097	1097
1098	1098	There is no AT Command available for this feature.
...	...	@@ -1105,12 +1105,11 @@
1105	1105	|(% style="width:95px" %)**Example**|(% style="width:403px" %)(((
1106	1106	AB 06
1107	1107
1108		-Uplink the trigger settings.
	1042	+Uplinks the trigger settings.
1109	1109	)))
1110	1110
1111	1111	==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ====
1112	1112
1113		-
1114	1114	Enable or disable DI1/DI2/DI3 as a trigger.
1115	1115
1116	1116	(% style="color:#037691" %)**AT Command**
...	...	@@ -1163,11 +1163,11 @@
1163	1163	Enable DI1 trigger, disable DI2 trigger
1164	1164	)))
1165	1165
1166		-==== 3.4.2.7 Trigger1 – Set DI1 or DI3 as a trigger ====
	1099	+==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ====
1167	1167
1168		-
1169	1169	Sets DI1 or DI3 (for LT-33222-L) as a trigger.
1170	1170
	1103	+
1171	1171	(% style="color:#037691" %)**AT Command**
1172	1172
1173	1173	(% border="2" style="width:500px" %)
...	...	@@ -1204,9 +1204,9 @@
1204	1204
1205	1205	==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
1206	1206
1207		-
1208	1208	Sets DI2 as a trigger.
1209	1209
	1142	+
1210	1210	(% style="color:#037691" %)**AT Command**
1211	1211
1212	1212	(% border="2" style="width:500px" %)
...	...	@@ -1238,7 +1238,6 @@
1238	1238
1239	1239	==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
1240	1240
1241		-
1242	1242	Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1243	1243
1244	1244	(% style="color:#037691" %)**AT Command**
...	...	@@ -1288,7 +1288,6 @@
1288	1288
1289	1289	==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
1290	1290
1291		-
1292	1292	Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1293	1293
1294	1294	(% style="color:#037691" %)**AT Command**
...	...	@@ -1334,9 +1334,8 @@
1334	1334	)))
1335	1335	|(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1336	1336
1337		-==== 3.4.2.11 Trigger – Set the minimum interval ====
	1268	+==== 3.4.2.11 Trigger – Set minimum interval ====
1338	1338
1339		-
1340	1340	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.
1341	1341
1342	1342	(% style="color:#037691" %)**AT Command**
...	...	@@ -1372,7 +1372,6 @@
1372	1372
1373	1373	==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
1374	1374
1375		-
1376	1376	Controls the digital outputs DO1, DO2, and DO3
1377	1377
1378	1378	(% style="color:#037691" %)**AT Command**
...	...	@@ -1403,11 +1403,11 @@
1403	1403	(((
1404	1404	01: Low,  00: High,  11: No action
1405	1405
1406		-(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:383px" %)
1407		-|(% 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**
1408		-|(% style="width:126px" %)02  01  00  11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action
1409		-|(% style="width:126px" %)02  00  11  01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low
1410		-|(% style="width:126px" %)02  11  01  00|(% style="width:85px" %)No Action|(% style="width:86px" %)Low|(% style="width:86px" %)High
	1335	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
	1336	+|(% 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**
	1337	+|02  01  00  11|Low|High|No Action
	1338	+|02  00  11  01|High|No Action|Low
	1339	+|02  11  01  00|No Action|Low|High
1411	1411	)))
1412	1412
1413	1413	(((
...	...	@@ -1424,161 +1424,148 @@
1424	1424	==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
1425	1425
1426	1426
1427		-(% style="color:#037691" %)**AT command**
	1356	+* (% style="color:#037691" %)**AT Command**
1428	1428
1429		-There is no AT command to control the digital output.
	1358	+There is no AT Command to control Digital Output
1430	1430
1431	1431
1432		-(% style="color:#037691" %)**Downlink payload**
	1361	+* (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
1433	1433
	1363	+(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Set DO1/DO2/DO3 output with time control
1434	1434
1435		-(% border="2" style="width:500px" %)
1436		-|(% style="width:116px" %)**Prefix**|(% style="width:382px" %)0xA9
1437		-|(% style="width:116px" %)**Parameters**|(% style="width:382px" %)(((
1438		-**inverter_mode**: 1 byte in hex.
1439	1439
1440		-**01:** DO pins revert to their original state after the timeout.
1441		-**00:** DO pins switch to an inverted state after the timeout.
	1366	+This is to control the digital output time of DO pin. Include four bytes:
1442	1442
	1368	+(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
1443	1443
1444		-**DO1_control_method_and_port_status **- 1 byte in hex
	1370	+(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode
1445	1445
1446		-0x01 : DO1 set to low
	1372	+01: DO pins will change back to original state after timeout.
1447	1447
1448		-0x00 : DO1 set to high
	1374	+00: DO pins will change to an inverter state after timeout
1449	1449
1450		-0x11 : DO1 NO action
1451	1451
	1377	+(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
1452	1452
1453		-**DO2_control_method_and_port_status** - 1 byte in hex
	1379	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
	1380	+|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
	1381	+|0x01|DO1 set to low
	1382	+|0x00|DO1 set to high
	1383	+|0x11|DO1 NO Action
1454	1454
1455		-0x01 : DO2 set to low
	1385	+(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:
1456	1456
1457		-0x00 : DO2 set to high
	1387	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
	1388	+|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
	1389	+|0x01|DO2 set to low
	1390	+|0x00|DO2 set to high
	1391	+|0x11|DO2 NO Action
1458	1458
1459		-0x11 : DO2 NO action
	1393	+(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:
1460	1460
	1395	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
	1396	+|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
	1397	+|0x01|DO3 set to low
	1398	+|0x00|DO3 set to high
	1399	+|0x11|DO3 NO Action
1461	1461
1462		-**DO3_control_method_and_port_status **- 1 byte in hex
	1401	+(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)
1463	1463
1464		-0x01 : DO3 set to low
1465	1465
1466		-0x00 : DO3 set to high
	1404	+(% style="color:red" %)**Note: **
1467	1467
1468		-0x11 : DO3 NO action
	1406	+ Since firmware v1.6.0, the latch time support 4 bytes and 2 bytes
1469	1469
	1408	+ Before firmware v1.6.0, the latch time only supported 2 bytes.
1470	1470
1471		-**latching_time** : 4 bytes in hex
	1410	+(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1472	1472
1473		-(% style="color:red" %)**Note: **
1474	1474
1475		- Since firmware v1.6.0, the latch time supports 4 bytes or 2 bytes
	1413	+**Example payload:**
1476	1476
1477		- Before firmware v1.6.0, the latch time only supported 2 bytes.
	1415	+**~1. A9 01 01 01 01 07 D0**
1478	1478
1479		-(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1480		-)))
1481		-|(% style="width:116px" %)**Payload format**|(% style="width:382px" %)<prefix><inverter_mode><DO1_control_method_and_port_status><DO2_control_method_and_port_status><DO2_control_method_and_port_status><latching_time>
1482		-|(% style="width:116px" %)**Example**|(% style="width:382px" %)(((
1483		-**A9 01 01 01 01 07 D0**
1484		-
1485	1485	DO1 pin, DO2 pin, and DO3 pin will be set to low, last for 2 seconds, and then revert to their original state.
1486	1486
	1419	+**2. A9 01 00 01 11 07 D0**
1487	1487
1488		-**A9 01 00 01 11 07 D0**
1489		-
1490	1490	DO1 pin is set to high, DO2 pin is set to low, and DO3 pin takes no action. This lasts for 2 seconds and then reverts to the original state.
1491	1491
	1423	+**3. A9 00 00 00 00 07 D0**
1492	1492
1493		-**A9 00 00 00 00 07 D0**
1494		-
1495	1495	DO1 pin, DO2 pin, and DO3 pin will be set to high, last for 2 seconds, and then all change to low.
1496	1496
	1427	+**4. A9 00 11 01 00 07 D0**
1497	1497
1498		-**A9 00 11 01 00 07 D0**
	1429	+DO1 pin takes no action, DO2 pin is set to low, and DO3 pin is set to high. This lasts for 2 seconds, after which DO1 pin takes no action, DO2 pin is set to high, and DO3 pin is set to low.
1499	1499
1500		-DO1 pin takes no action, DO2 pin is set to low, and DO3 pin is set to high. This lasts for 2 seconds, after which the DO1 pin takes no action, the DO2 pin is set to high, and the DO3 pin is set to low.
1501		-)))
1502	1502
1503	1503	==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
1504	1504
1505	1505
1506		-(% style="color:#037691" %)**AT Command:**
	1435	+* (% style="color:#037691" %)**AT Command:**
1507	1507
1508		-There is no AT Command to control the Relay Output.
	1437	+There is no AT Command to control Relay Output
1509	1509
1510	1510
1511		-(% style="color:#037691" %)**Downlink Payload**
	1440	+* (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
1512	1512
1513		-(% border="2" style="width:500px" %)
1514		-|(% style="width:113px" %)**Prefix**|(% style="width:384px" %)0x03
1515		-|(% style="width:113px" %)**Parameters**|(% style="width:384px" %)(((
1516		-**RO1_status** : 1 byte in hex
	1442	+(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Set RO1/RO2 output
1517	1517
1518		-00: Close
1519	1519
1520		-01: Open
	1445	+(((
	1446	+If payload is 0x030100, it means setting RO1 to close and RO2 to open.
	1447	+)))
1521	1521
1522		-11: No action
	1449	+(((
	1450	+00: Close ,  01: Open , 11: No action
1523	1523
1524		-
1525		-**RO2_status** : 1 byte in hex
1526		-
1527		-00: Close
1528		-
1529		-01: Open
1530		-
1531		-11: No action
	1452	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %)
	1453	+|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**RO1**|(% style="background-color:#4f81bd; color:white" %)**RO2**
	1454	+|03  00  11|Open|No Action
	1455	+|03  01  11|Close|No Action
	1456	+|03  11  00|No Action|Open
	1457	+|03  11  01|No Action|Close
	1458	+|03  00  00|Open|Open
	1459	+|03  01  01|Close|Close
	1460	+|03  01  00|Close|Open
	1461	+|03  00  01|Open|Close
1532	1532	)))
1533		-|(% style="width:113px" %)**Payload format**|(% style="width:384px" %)<prefix><RO1_status><RO2_status>
1534		-|(% style="width:113px" %)**Example**|(% style="width:384px" %)(((
1535		-(% border="2" %)
1536		-|=Payload|=RO1|=RO2
1537		-|03  00  11|Open|No action
1538		-|03  01  11|Close|No action
1539		-|03 11  00|No action|Open
1540		-|03 11 10|No action|Close
1541		-|03 00 00|Open|Open
1542		-|03 01 01|Close|Close
1543		-|03 01 00|Close|Open
1544		-|03 00 01|Open|Close
1545	1545
1546		-(% style="color:red" %)**The device will transmit an uplink packet if the downlink payload is executed successfully.**
1547		-)))
	1464	+(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
1548	1548
	1466	+
1549	1549	==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
1550	1550
1551		-
1552	1552	Controls the relay output time.
1553	1553
	1471	+* (% style="color:#037691" %)**AT Command:**
1554	1554
1555		-(% style="color:#037691" %)**AT Command:**
	1473	+There is no AT Command to control Relay Output
1556	1556
1557		-There is no AT Command to control the Relay Output
1558	1558
	1476	+* (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1559	1559
1560		-(% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
	1478	+(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Set RO1/RO2 relay with time control
1561	1561
1562		-(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
1563	1563
	1481	+This is to control the relay output time. It includes four bytes:
1564	1564
1565		-This controls the relay output time and includes 4 bytes:
	1483	+(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
1566	1566
1567		-(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)
	1485	+(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
1568	1568
1569		-(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode
	1487	+01: Relays will change back to their original state after timeout.
1570	1570
1571		-01: Relays will change back to their original state after a timeout.
	1489	+00: Relays will change to the inverter state after timeout.
1572	1572
1573		-00: Relays will change to the inverter state after a timeout.
1574	1574
	1492	+(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
1575	1575
1576		-(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status:
1577		-
1578	1578	[[image:image-20221008095908-1.png||height="364" width="564"]]
1579	1579
1580	1580
1581		-(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes (cc)**(%%): Latching time. Unit: ms
	1497	+(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms
1582	1582
1583	1583
1584	1584	(% style="color:red" %)**Note:**
...	...	@@ -1588,7 +1588,7 @@
1588	1588	Before firmware v1.6.0, the latch time only supported 2 bytes.
1589	1589
1590	1590
1591		-(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
	1507	+(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1592	1592
1593	1593
1594	1594	**Example payload:**
...	...	@@ -1599,7 +1599,7 @@
1599	1599
1600	1600	**2. 05 01 10 07 D0**
1601	1601
1602		-Relay1 will change to NC, Relay2 will change to NO, lasting 2 seconds, and then both will revert to their original state.
	1518	+Relay1 will change to NC, Relay2 will change to NO, lasting 2 seconds, then both will revert to their original state.
1603	1603
1604	1604	**3. 05 00 01 07 D0**
1605	1605
...	...	@@ -1630,7 +1630,7 @@
1630	1630
1631	1631	**1**: higher than
1632	1632
1633		-if you leave the logic parameter blank, it is considered 0
	1549	+if you leave logic parameter blank, it is considered 0
1634	1634	)))
1635	1635	|(% style="width:137px" %)**Examples**|(% style="width:361px" %)(((
1636	1636	AT+VOLMAX=20000
...	...	@@ -1661,7 +1661,7 @@
1661	1661
1662	1662	**1**: higher than
1663	1663
1664		-if you leave the logic parameter blank, it is considered 1 (higher than)
	1580	+if you leave logic parameter blank, it is considered 1 (higher than)
1665	1665	)))
1666	1666	|(% style="width:140px" %)**Example**|(% style="width:358px" %)(((
1667	1667	A5 **4E 20**
...	...	@@ -1747,9 +1747,8 @@
1747	1747	)))
1748	1748	|(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
1749	1749
1750		-==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ====
	1666	+==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1751	1751
1752		-
1753	1753	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.
1754	1754
1755	1755	(% style="color:#037691" %)**AT Command**
...	...	@@ -1779,9 +1779,8 @@
1779	1779	Sets the device to save its counting results to the memory every 60 seconds.
1780	1780	)))
1781	1781
1782		-==== 3.4.2.20 Reset saved RO and DO states ====
	1697	+==== 3.4.2.20 Reset save RO DO state ====
1783	1783
1784		-
1785	1785	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.
1786	1786
1787	1787	(% style="color:#037691" %)**AT Command**
...	...	@@ -1806,6 +1806,7 @@
1806	1806	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.
1807	1807	)))
1808	1808
	1723	+
1809	1809	(% style="color:#037691" %)**Downlink Payload**
1810	1810
1811	1811	(% border="2" style="width:500px" %)
...	...	@@ -1831,7 +1831,6 @@
1831	1831
1832	1832	==== 3.4.2.21 Encrypted payload ====
1833	1833
1834		-
1835	1835	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.
1836	1836
1837	1837	(% style="color:#037691" %)**AT Command:**
...	...	@@ -1861,7 +1861,6 @@
1861	1861
1862	1862	==== 3.4.2.22 Get sensor value ====
1863	1863
1864		-
1865	1865	This command allows you to retrieve and optionally uplink sensor readings through the serial port.
1866	1866
1867	1867	(% style="color:#037691" %)**AT Command**
...	...	@@ -1891,7 +1891,6 @@
1891	1891
1892	1892	==== 3.4.2.23 Resetting the downlink packet count ====
1893	1893
1894		-
1895	1895	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.
1896	1896
1897	1897	(% style="color:#037691" %)**AT Command**
...	...	@@ -1925,7 +1925,7 @@
1925	1925	==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ====
1926	1926
1927	1927
1928		-This command controls the behavior of the node when the combined size of the MAC commands (MACANS) from the server and the payload exceed the allowed byte limit for the current data rate (DR). The command provides two modes: one enables splitting the data into batches to ensure compliance with the byte limit, while the other prioritizes the payload and ignores the MACANS in cases of overflow.
	1840	+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.
1929	1929
1930	1930	(% style="color:#037691" %)**AT Command**
1931	1931
...	...	@@ -1970,39 +1970,49 @@
1970	1970
1971	1971	==== 3.4.2.25 Copy downlink to uplink ====
1972	1972
	1885	+This command enables the device to immediately uplink the content of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100.
1973	1973
1974		-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.
	1887	+* (% style="color:#037691" %)**AT Command**(%%)**:**
1975	1975
1976		-(% style="color:#037691" %)**AT Command**(%%)**:**
	1889	+(% 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.
1977	1977
1978		-(% 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.
	1891	+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.
1979	1979
1980		-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.
1981	1981
1982		-
1983	1983	[[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"]]
1984	1984
1985	1985	For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
1986	1986
1987		-[[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"]]
	1898	+(% border="2" style="width:500px" %)
	1899	+|(% style="width:122px" %)**Command**|(% style="width:376px" %)(((
	1900	+AT+RPL=5
1988	1988
1989		-For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
	1902	+After receiving a downlink packet from the server, the node immediately uplinks the content of the packet back to the server using port number 100.
	1903	+)))
	1904	+|(% style="width:122px" %)**Example**|(% style="width:376px" %)(((
	1905	+Downlink:
1990	1990
	1907	+01 00 02 58
1991	1991
1992		-(% style="color:#037691" %)**Downlink Payload**(%%)**:**
	1909	+Uplink:
1993	1993
1994		-There is no downlink option available for this feature.
	1911	+01 01 00 02 58
	1912	+)))
1995	1995
	1914	+[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]]
1996	1996
1997		-==== 3.4.2.26 Query firmware version, frequency band, subband, and TDC time ====
	1916	+For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
1998	1998
1999	1999
2000		-This command is used to query key information about the device, including its firmware version, frequency band, subband, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device.
2001	2001
	1920	+==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
	1921	+
	1922	+This command is used to query key information about the device, including its firmware version, frequency band, sub band, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device.
	1923	+
2002	2002	* (((
2003	2003	(% style="color:#037691" %)**Downlink Payload**(%%)**:**
2004	2004
2005		-(% style="color:blue" %)**26 01  ** (%%) ~/~/  The downlink payload 26 01 is used to query the device's firmware version, frequency band, subband, and TDC time.
	1927	+(% 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.
2006	2006
2007	2007
2008	2008
...	...	@@ -2015,13 +2015,10 @@
2015	2015
2016	2016	== 3.5 Integrating with ThingsEye.io ==
2017	2017
2018		-
2019	2019	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.
2020	2020
2021		-
2022	2022	=== 3.5.1 Configuring The Things Stack ===
2023	2023
2024		-
2025	2025	We use The Things Stack Sandbox in this example:
2026	2026
2027	2027	* In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
...	...	@@ -2033,12 +2033,10 @@
2033	2033	The username and  password (API key) you created here are required in the next section.
2034	2034	{{/info}}
2035	2035
2036		-[[image:tts-mqtt-integration.png]]
	1955	+[[image:tts-mqtt-integration.png||height="625" width="1000"]]
2037	2037
2038		-
2039	2039	=== 3.5.2 Configuring ThingsEye.io ===
2040	2040
2041		-
2042	2042	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.
2043	2043
2044	2044	* Login to your [[ThingsEye.io >>https://thingseye.io]]account.
...	...	@@ -2045,7 +2045,7 @@
2045	2045	* Under the **Integrations center**, click **Integrations**.
2046	2046	* Click the **Add integration** button (the button with the **+** symbol).
2047	2047
2048		-[[image:thingseye-io-step-1.png]]
	1965	+[[image:thingseye-io-step-1.png||height="625" width="1000"]]
2049	2049
2050	2050
2051	2051	On the **Add integration** window, configure the following:
...	...	@@ -2057,10 +2057,10 @@
2057	2057	* Ensure the following options are turned on.
2058	2058	** Enable integration
2059	2059	** Debug mode
2060		-** Allow creating devices or assets
	1977	+** Allow create devices or assets
2061	2061	* Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
2062	2062
2063		-[[image:thingseye-io-step-2.png]]
	1980	+[[image:thingseye-io-step-2.png||height="625" width="1000"]]
2064	2064
2065	2065
2066	2066	**Uplink data converter:**
...	...	@@ -2071,7 +2071,7 @@
2071	2071	* 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]].
2072	2072	* Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
2073	2073
2074		-[[image:thingseye-io-step-3.png]]
	1991	+[[image:thingseye-io-step-3.png||height="625" width="1000"]]
2075	2075
2076	2076
2077	2077	**Downlink data converter (this is an optional step):**
...	...	@@ -2082,7 +2082,7 @@
2082	2082	* 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]].
2083	2083	* Click the **Next** button. You will be navigated to the **Connection** tab.
2084	2084
2085		-[[image:thingseye-io-step-4.png]]
	2002	+[[image:thingseye-io-step-4.png||height="625" width="1000"]]
2086	2086
2087	2087
2088	2088	**Connection:**
...	...	@@ -2097,21 +2097,20 @@
2097	2097
2098	2098	* Click the **Add** button.
2099	2099
2100		-[[image:thingseye-io-step-5.png]]
	2017	+[[image:thingseye-io-step-5.png||height="625" width="1000"]]
2101	2101
2102	2102
2103	2103	Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings and correct any errors.
2104	2104
2105	2105
2106		-[[image:thingseye.io_integrationsCenter_integrations.png]]
	2023	+[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
2107	2107
2108	2108
2109	2109	==== 3.5.2.1 Viewing integration details ====
2110	2110
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]]
	2030	+[[image:integration-details.png||height="686" width="1000"]]
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.
...	...	@@ -2120,45 +2120,37 @@
2120	2120	See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
2121	2121	{{/info}}
2122	2122
	2039	+==== **3.5.2.2 Viewing events** ====
2123	2123
2124		-==== 3.5.2.2 Viewing events ====
2125		-
2126		-
2127	2127	The **Events **tab displays all the uplink messages from the LT-22222-L.
2128	2128
2129	2129	* Select **Debug **from the **Event type** dropdown.
2130	2130	* Select the** time frame** from the **time window**.
2131	2131
2132		-[[image:thingseye-events.png]]
	2046	+[[image:thingseye-events.png||height="686" width="1000"]]
2133	2133
2134	2134
2135		-* To view the **JSON payload** of a message, click on the **three dots (...)** in the **Message** column of the desired message.
	2049	+* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
2136	2136
2137		-[[image:thingseye-json.png]]
	2051	+[[image:thingseye-json.png||width="1000"]]
2138	2138
2139	2139
2140		-==== 3.5.2.3 Deleting an integration ====
	2054	+==== **3.5.2.3 Deleting an integration** ====
2141	2141
2142		-
2143	2143	If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
2144	2144
2145	2145
2146		-==== 3.5.2.4 Viewing sensor data on a dashboard ====
	2059	+==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
2147	2147
	2061	+This will be added soon.
2148	2148
2149		-You can create a dashboard with ThingsEye to visualize the sensor data coming from the LT-22222-L. The following image shows a dashboard created for the LT-22222-L. See **Creating a dashboard** in ThingsEye documentation for more information.
2150	2150
2151		-
2152		-
2153		-[[image:lt-22222-l-dashboard.png]]
2154		-
2155		-
2156	2156	== 3.6 Interface Details ==
2157	2157
2158	2158	=== 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
2159	2159
2160	2160
2161		-Supports** NPN-type **sensors.
	2069	+Supports NPN-type sensors.
2162	2162
2163	2163	[[image:1653356991268-289.png]]
2164	2164
...	...	@@ -2280,15 +2280,15 @@
2280	2280	)))
2281	2281
2282	2282
2283		-(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor
	2191	+(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
2284	2284
2285		-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.
	2193	+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.
2286	2286
2287		-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.
	2195	+To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram.
2288	2288
2289	2289	[[image:image-20230616235145-1.png]]
2290	2290
2291		-(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector
	2199	+(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
2292	2292
2293	2293	[[image:image-20240219115718-1.png]]
2294	2294
...	...	@@ -2364,21 +2364,20 @@
2364	2364	[[image:image-20220524100215-10.png||height="382" width="723"]]
2365	2365
2366	2366
2367		-== 3.7 LED Indicators ==
	2275	+== 3.7 LEDs Indicators ==
2368	2368
	2277	+The table below lists the behavior of LED indicators for each port function.
2369	2369
2370		-The table below lists the behaviour of LED indicators for each port function.
2371		-
2372	2372	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
2373	2373	|(% style="background-color:#4f81bd; color:white; width:50px" %)**LEDs**|(% style="background-color:#4f81bd; color:white; width:460px" %)**Feature**
2374	2374	|**PWR**|Always on when there is power
2375	2375	|**TX**|(((
2376	2376	(((
2377		-Device booting: TX blinks 5 times.
	2284	+Device boot: TX blinks 5 times.
2378	2378	)))
2379	2379
2380	2380	(((
2381		-Successful network joins: TX remains ON for 5 seconds.
	2288	+Successful network join: TX remains ON for 5 seconds.
2382	2382	)))
2383	2383
2384	2384	(((
...	...	@@ -2399,22 +2399,18 @@
2399	2399
2400	2400	= 4. Using AT Commands =
2401	2401
2402		-
2403	2403	The LT-22222-L supports programming using AT Commands.
2404	2404
2405		-
2406	2406	== 4.1 Connecting the LT-22222-L to a PC ==
2407	2407
2408		-
2409	2409	(((
2410		-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.
	2314	+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.
2411	2411
2412		-[[image:usb-ttl-audio-jack-connection.jpg]]
2413		-
2414		-
	2316	+[[image:usb-ttl-programming.png]]
2415	2415	)))
2416	2416
2417	2417
	2320	+
2418	2418	(((
2419	2419	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:
2420	2420	)))
...	...	@@ -2425,10 +2425,7 @@
2425	2425	(((
2426	2426	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/]]
2427	2427
2428		-
2429	2429	== 4.2 LT-22222-L related AT commands ==
2430		-
2431		-
2432	2432	)))
2433	2433
2434	2434	(((
...	...	@@ -2447,39 +2447,39 @@
2447	2447	* **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
2448	2448	* **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
2449	2449	* **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
2450		-* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2451		-* **##AT+DR##**:  Get or set the Data Rate. (0-7 corresponding to DR_X)
2452		-* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2453		-* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)
2454		-* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency
2455		-* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2456		-* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2457		-* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2458		-* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2459		-* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2460		-* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2461		-* ##**AT+NWKID**##: Get or set the Network ID
2462		-* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)
2463		-* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)
2464		-* ##**AT+CLASS**##: Get or set the Device Class
2465		-* ##**AT+JOIN**##: Join Network
2466		-* ##**AT+NJS**##: Get OTAA Join Status
2467		-* ##**AT+SENDB**##: Send hexadecimal data along with the application port
2468		-* ##**AT+SEND**##: Send text data along with the application port
2469		-* ##**AT+RECVB**##: Print the last received data in binary format (with hexadecimal values)
2470		-* ##**AT+RECV**##: Print the last received data in raw format
2471		-* ##**AT+VER**##: Get the current image version and Frequency Band
2472		-* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)
2473		-* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)
2474		-* ##**AT+SNR**##: Get the SNR of the last received packet
2475		-* ##**AT+RSSI**##: Get the RSSI of the last received packet
2476		-* ##**AT+TDC**##: Get or set the application data transmission interval in ms
2477		-* ##**AT+PORT**##: Get or set the application port
2478		-* ##**AT+DISAT**##: Disable AT commands
2479		-* ##**AT+PWORD**##: Set password, max 9 digits
2480		-* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2481		-* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN470
2482		-* ##**AT+CFG**##: Print all settings
	2350	+* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
	2351	+* AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)
	2352	+* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
	2353	+* AT+PNM: Get or set the public network mode. (0: off, 1: on)
	2354	+* AT+RX2FQ: Get or set the Rx2 window frequency
	2355	+* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
	2356	+* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
	2357	+* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
	2358	+* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
	2359	+* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
	2360	+* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
	2361	+* AT+NWKID: Get or set the Network ID
	2362	+* AT+FCU: Get or set the Frame Counter Uplink (FCntUp)
	2363	+* AT+FCD: Get or set the Frame Counter Downlink (FCntDown)
	2364	+* AT+CLASS: Get or set the Device Class
	2365	+* AT+JOIN: Join network
	2366	+* AT+NJS: Get OTAA Join Status
	2367	+* AT+SENDB: Send hexadecimal data along with the application port
	2368	+* AT+SEND: Send text data along with the application port
	2369	+* AT+RECVB: Print last received data in binary format (with hexadecimal values)
	2370	+* AT+RECV: Print last received data in raw format
	2371	+* AT+VER: Get current image version and Frequency Band
	2372	+* AT+CFM: Get or Set the confirmation mode (0-1)
	2373	+* AT+CFS: Get confirmation status of the last AT+SEND (0-1)
	2374	+* AT+SNR: Get the SNR of the last received packet
	2375	+* AT+RSSI: Get the RSSI of the last received packet
	2376	+* AT+TDC: Get or set the application data transmission interval in ms
	2377	+* AT+PORT: Get or set the application port
	2378	+* AT+DISAT: Disable AT commands
	2379	+* AT+PWORD: Set password, max 9 digits
	2380	+* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode
	2381	+* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470
	2382	+* AT+CFG: Print all settings
2483	2483	)))
2484	2484
2485	2485
...	...	@@ -2496,7 +2496,7 @@
2496	2496	)))
2497	2497
2498	2498	(((
2499		-(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT command access**##
	2399	+(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**##
2500	2500	)))
2501	2501
2502	2502	(((
...	...	@@ -2504,7 +2504,7 @@
2504	2504	)))
2505	2505
2506	2506	(((
2507		-(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT command access**##
	2407	+(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**##
2508	2508	)))
2509	2509
2510	2510	(((
...	...	@@ -2535,7 +2535,7 @@
2535	2535
2536	2536
2537	2537	(((
2538		-(% style="background-color:#dcdcdc" %)**123456**(%%)  ~/~/ Enter the password to enable AT commands access
	2438	+(% style="background-color:#dcdcdc" %)**123456**(%%)  ~/~/ Enter password to enable AT commands access
2539	2539	)))
2540	2540	)))
2541	2541
...	...	@@ -2544,7 +2544,7 @@
2544	2544	)))
2545	2545
2546	2546	(((
2547		-(% style="background-color:#dcdcdc" %)** 123456**(%%)  ~/~/ Enter the password to enable AT command access
	2447	+(% style="background-color:#dcdcdc" %)** 123456**(%%)  ~/~/ Enter password to enable AT commands access
2548	2548	)))
2549	2549
2550	2550	(((
...	...	@@ -2625,19 +2625,16 @@
2625	2625
2626	2626	== 5.1 Counting how many objects pass through the flow line ==
2627	2627
	2528	+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]]?
2628	2628
2629		-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]].
2630	2630
2631		-
2632	2632	= 6. FAQ =
2633	2633
2634		-
2635	2635	This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
2636	2636
2637	2637
2638	2638	== 6.1 How to update the firmware? ==
2639	2639
2640		-
2641	2641	Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to:
2642	2642
2643	2643	* Support new features
...	...	@@ -2647,7 +2647,7 @@
2647	2647	You will need the following things before proceeding:
2648	2648
2649	2649	* 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
2650		-* USB to TTL adapter/converter
	2547	+* USB to TTL adapter
2651	2651	* 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)
2652	2652	* 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.
2653	2653
...	...	@@ -2657,7 +2657,7 @@
2657	2657
2658	2658	Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2659	2659
2660		-[[image:usb-ttl-audio-jack-connection.jpg]]
	2557	+[[image:usb-ttl-programming.png]]
2661	2661
2662	2662
2663	2663
...	...	@@ -2690,21 +2690,17 @@
2690	2690	(((
2691	2691	(((
2692	2692	== 6.2 How to change the LoRaWAN frequency band/region? ==
2693		-
2694		-
2695	2695	)))
2696	2696	)))
2697	2697
2698	2698	(((
2699		-You can follow the introductions on [[how to upgrade the image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloading, select the required image file.
	2594	+You can follow the introductions on [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloading, select the required image file.
2700	2700	)))
2701	2701
2702	2702	(((
2703	2703
2704	2704
2705		-== 6.3 How to set up LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
2706		-
2707		-
	2600	+== 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
2708	2708	)))
2709	2709
2710	2710	(((
...	...	@@ -2778,13 +2778,11 @@
2778	2778
2779	2779	== 6.4 How to change the uplink interval? ==
2780	2780
2781		-
2782	2782	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/]]
2783	2783
2784	2784
2785	2785	== 6.5 Can I see the counting event in the serial output? ==
2786	2786
2787		-
2788	2788	(((
2789	2789	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.
2790	2790
...	...	@@ -2791,7 +2791,6 @@
2791	2791
2792	2792	== 6.6 Can I use point-to-point communication with LT-22222-L? ==
2793	2793
2794		-
2795	2795	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]].
2796	2796
2797	2797
...	...	@@ -2800,15 +2800,13 @@
2800	2800	(((
2801	2801	== 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
2802	2802
2803		-
2804	2804	* If the device is not properly shut down and is directly powered off.
2805	2805	* It will default to a power-off state.
2806	2806	* In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
2807		-* After a restart, the status before the power failure will be read from Flash.
	2696	+* After a restart, the status before the power failure will be read from flash.
2808	2808
2809		-== 6.8 Can I set up LT-22222-L as an NC (Normally Closed) relay? ==
	2698	+== 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
2810	2810
2811		-
2812	2812	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:
2813	2813
2814	2814
...	...	@@ -2817,19 +2817,16 @@
2817	2817
2818	2818	== 6.9 Can the LT-22222-L save the RO state? ==
2819	2819
2820		-
2821	2821	To enable this feature, the firmware version must be 1.6.0 or higher.
2822	2822
2823	2823
2824	2824	== 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
2825	2825
2826		-
2827	2827	It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
2828	2828
2829	2829
2830	2830	= 7. Troubleshooting =
2831	2831
2832		-
2833	2833	This section provides some known troubleshooting tips.
2834	2834
2835	2835
...	...	@@ -2838,8 +2838,6 @@
2838	2838	(((
2839	2839	(((
2840	2840	== 7.1 Downlink isn't working. How can I solve this? ==
2841		-
2842		-
2843	2843	)))
2844	2844	)))
2845	2845
...	...	@@ -2851,8 +2851,6 @@
2851	2851
2852	2852
2853	2853	== 7.2 Having trouble uploading an image? ==
2854		-
2855		-
2856	2856	)))
2857	2857
2858	2858	(((
...	...	@@ -2863,8 +2863,6 @@
2863	2863
2864	2864
2865	2865	== 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
2866		-
2867		-
2868	2868	)))
2869	2869
2870	2870	(((
...	...	@@ -2874,7 +2874,6 @@
2874	2874
2875	2875	== 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? ==
2876	2876
2877		-
2878	2878	The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
2879	2879	Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2880	2880
...	...	@@ -2881,7 +2881,6 @@
2881	2881
2882	2882	= 8. Ordering information =
2883	2883
2884		-
2885	2885	(% style="color:#4f81bd" %)**LT-22222-L-XXX:**
2886	2886
2887	2887	(% style="color:#4f81bd" %)**XXX:**
...	...	@@ -2898,7 +2898,6 @@
2898	2898
2899	2899	= 9. Package information =
2900	2900
2901		-
2902	2902	**Package includes**:
2903	2903
2904	2904	* 1 x LT-22222-L I/O Controller
...	...	@@ -2915,7 +2915,6 @@
2915	2915
2916	2916	= 10. Support =
2917	2917
2918		-
2919	2919	* (((
2920	2920	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.
2921	2921	)))
...	...	@@ -2927,7 +2927,6 @@
2927	2927
2928	2928	= 11. Reference​​​​​ =
2929	2929
2930		-
2931	2931	* 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]]
2932	2932	* [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]]
2933	2933	* [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]

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-dashboard.png

Author

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

Size

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