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

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 6 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
  • usb-ttl-audio-jack-connection.jpg

Details

Page properties

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,13 +121,11 @@
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-22222-L**|(% style="width:172px" %)(((
128		-(% style="text-align:center" %)
129		-[[image:lt33222-l.jpg||height="110" width="95"]]
130		-)))|(% style="width:256px" %)(((
	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" %)(((
131	131	* 2 x Digital Input (Bi-direction)
132	132	* 2 x Digital Output
133	133	* 2 x Relay Output (5A@250VAC / 30VDC)
...	...	@@ -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
153		-
154	154	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.
155	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
203		-
204	204	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.
205	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...
...	...	@@ -264,12 +264,11 @@
264	264	** 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	266
267		-[[image:lt-22222-l-dev-repo-reg-p2.png]]
	250	+[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
268	268
269	269
270		-==== 3.2.1.2 Adding device manually ====
	253	+==== 3.2.2.3 Adding device manually ====
271	271
272		-
273	273	* On the **Register end device** page:
274	274	** Select the option **Enter end device specifies manually** under **Input method**.
275	275	** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
...	...	@@ -279,7 +279,7 @@
279	279	** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
280	280	** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
281	281
282		-[[image:lt-22222-l-manually-p1.png]]
	264	+[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
283	283
284	284
285	285	* Register end device page continued...
...	...	@@ -290,27 +290,26 @@
290	290	** Under **After registration**, select the **View registered end device** option.
291	291	** Click the **Register end device** button.
292	292
293		-[[image:lt-22222-l-manually-p2.png]]
	275	+[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
294	294
295	295
296	296	You will be navigated to the **Device overview** page.
297	297
298	298
299		-[[image:lt-22222-device-overview.png]]
	281	+[[image:lt-22222-device-overview.png||height="625" width="1000"]]
300	300
301	301
302		-=== 3.2.2 Joining ===
	284	+==== 3.2.2.4 Joining ====
303	303
304		-
305	305	On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
306	306
307	307	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.
308	308
309	309
310		-[[image:lt-22222-l-joining.png]]
	291	+[[image:lt-22222-join-network.png||height="625" width="1000"]]
311	311
312	312
313		-=== 3.2.3 Uplinks ===
	294	+==== 3.2.2.5 Uplinks ====
314	314
315	315
316	316	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.
...	...	@@ -326,18 +326,11 @@
326	326	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.
327	327	{{/info}}
328	328
329		-[[image:lt-22222-ul-payload-fmt.png]]
	310	+[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
330	330
331	331
332		-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]]:
	313	+==== 3.2.2.6 Downlinks ====
333	333
334		-(% class="wikigeneratedid" %)
335		-[[image:lt-22222-l-js-custom-payload-formatter.png]]
336		-
337		-
338		-=== 3.2.4 Downlinks ===
339		-
340		-
341	341	When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
342	342
343	343
...	...	@@ -360,10 +360,8 @@
360	360
361	361	The uplink messages are sent over LoRaWAN FPort=2. By default, an uplink message is sent every 10 minutes.
362	362
363		-
364	364	=== 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
365	365
366		-
367	367	(((
368	368	This is the default mode.
369	369
...	...	@@ -436,7 +436,6 @@
436	436
437	437	MOD = 1
438	438
439		-
440	440	=== 3.3.2 AT+MOD~=2, (Double DI Counting) ===
441	441
442	442
...	...	@@ -515,7 +515,6 @@
515	515
516	516	=== 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI ===
517	517
518		-
519	519	(% style="color:red" %)**Note: The maximum count depends on the bytes it is.
520	520	The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
521	521	It starts counting again when it reaches the maximum value.**
...	...	@@ -569,7 +569,6 @@
569	569
570	570	=== 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting ===
571	571
572		-
573	573	(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
574	574	The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
575	575	It starts counting again when it reaches the maximum value.**
...	...	@@ -629,17 +629,16 @@
629	629
630	630	(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)**
631	631
632		-(% 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)**
633	633
634		-(% 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)**
635	635
636		-(% 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)**
637	637	)))
638	638
639	639
640	640	=== 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI ===
641	641
642		-
643	643	(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
644	644	The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
645	645	It starts counting again when it reaches the maximum value.**
...	...	@@ -753,9 +753,9 @@
753	753
754	754	(% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
755	755
756		-**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**
757	757
758		-**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
	726	+Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
759	759
760	760	AA: Type Code for this downlink Command:
761	761
...	...	@@ -784,7 +784,7 @@
784	784
785	785	MOD6 Payload: total of 11 bytes
786	786
787		-(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
	755	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
788	788	|(% 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**
789	789	|Value|(((
790	790	TRI_A FLAG
...	...	@@ -798,7 +798,7 @@
798	798
799	799	(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
800	800
801		-(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
	769	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
802	802	|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
803	803	|(((
804	804	AV1_LOW
...	...	@@ -822,12 +822,12 @@
822	822
823	823	**Example:**
824	824
825		-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
826	826
827	827
828	828	(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
829	829
830		-(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
	798	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
831	831	|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
832	832	|(((
833	833	AV1_LOW
...	...	@@ -851,31 +851,31 @@
851	851
852	852	**Example:**
853	853
854		-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.
855	855
856	856
857	857	(% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
858	858
859		-(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
860		-|(% 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**
861		-|(% 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
862	862
863		-* Each bit shows which status has been triggered on this uplink.
	831	+* Each bits shows which status has been triggered on this uplink.
864	864
865	865	**Example:**
866	866
867		-00000111: This means both DI1 and DI2 triggers are enabled, and this packet is trigger by DI1.
	835	+00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
868	868
869		-00000101: This means both DI1 and DI2 triggers are enabled.
	837	+00000101: Means both DI1 and DI2 trigger are enabled.
870	870
871	871
872		-(% 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.
873	873
874		-Downlink command to poll/request MOD6 status:
	842	+Downlink command to poll MOD6 status:
875	875
876	876	**AB 06**
877	877
878		-When device receives this command, it will send the MOD6 payload.
	846	+When device got this command, it will send the MOD6 payload.
879	879
880	880
881	881	=== 3.3.7 Payload Decoder ===
...	...	@@ -889,7 +889,6 @@
889	889
890	890	== 3.4 ​Configure LT-22222-L via AT Commands or Downlinks ==
891	891
892		-
893	893	(((
894	894	You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks.
895	895	)))
...	...	@@ -906,22 +906,17 @@
906	906
907	907	=== 3.4.1 Common commands ===
908	908
909		-
910	910	(((
911	911	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.
912		-
913		-
914	914	)))
915	915
916	916	=== 3.4.2 Sensor-related commands ===
917	917
918		-
919	919	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.
920	920
921	921
922	922	==== 3.4.2.1 Set Transmit/Uplink Interval ====
923	923
924		-
925	925	Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
926	926
927	927	(% style="color:#037691" %)**AT command**
...	...	@@ -928,15 +928,8 @@
928	928
929	929	(% border="2" style="width:500px" %)
930	930	|**Command**|AT+TDC=<time>
931		-|**Parameters**|**time **: uplink interval in milliseconds
932		-|**Get**|AT+TDC=?
933		-|**Response**|(((
934		-current uplink interval
935		-
936		-OK
937		-)))
938		-|**Set**|AT+TDC=<time>
939		-|**Response**|OK
	893	+|**Response**|
	894	+|**Parameters**|**time** : uplink interval is in **milliseconds**
940	940	|**Example**|(((
941	941	AT+TDC=30000
942	942
...	...	@@ -952,7 +952,7 @@
952	952	|**Parameters**|(((
953	953	**prefix** : 0x01
954	954
955		-**time** : uplink interval in **seconds**, represented by **3  bytes** in **hexadecimal**.
	910	+**time** : uplink interval is in **seconds**, represented by **3  bytes** in **hexadecimal**.
956	956	)))
957	957	|**Example**|(((
958	958	01 **00 00 1E**
...	...	@@ -968,13 +968,13 @@
968	968
969	969	==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
970	970
971		-
972	972	Sets the working mode.
973	973
974	974	(% style="color:#037691" %)**AT command**
975	975
976	976	(% border="2" style="width:500px" %)
977		-|(% 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" %)
978	978	|(% style="width:97px" %)**Parameters**|(% style="width:413px" %)(((
979	979	**working_mode** :
980	980
...	...	@@ -990,18 +990,6 @@
990	990
991	991	6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5
992	992	)))
993		-|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=?
994		-|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
995		-Current working mode
996		-
997		-OK
998		-)))
999		-|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode>
1000		-|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
1001		-Attention:Take effect after ATZ
1002		-
1003		-OK
1004		-)))
1005	1005	|(% style="width:97px" %)**Example**|(% style="width:413px" %)(((
1006	1006	AT+MOD=2
1007	1007
...	...	@@ -1024,14 +1024,13 @@
1024	1024	Sets the device to working mode 2 (Double DI Counting + DO + RO)
1025	1025	)))
1026	1026
1027		-==== 3.4.2.3 Request an uplink from the device ====
	970	+==== 3.4.2.3 Poll an uplink ====
1028	1028
	972	+Requests an uplink from LT-22222-L.
1029	1029
1030		-Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.
1031		-
1032	1032	(% style="color:#037691" %)**AT command**
1033	1033
1034		-There is no AT Command available for this feature.
	976	+There is no AT Command to request an uplink from LT-22222-L
1035	1035
1036	1036	(% style="color:#037691" %)**Downlink payload**
1037	1037
...	...	@@ -1039,7 +1039,7 @@
1039	1039	|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF
1040	1040	|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08
1041	1041	|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
1042		-08 **FF**
	984	+08 FF
1043	1043
1044	1044	Requests an uplink from LT-22222-L.
1045	1045	)))
...	...	@@ -1046,7 +1046,6 @@
1046	1046
1047	1047	==== 3.4.2.4 Enable/Disable Trigger Mode ====
1048	1048
1049		-
1050	1050	Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
1051	1051
1052	1052	(% style="color:#037691" %)**AT Command**
...	...	@@ -1074,7 +1074,7 @@
1074	1074	|(% style="width:97px" %)**Parameters**|(% style="width:401px" %)(((
1075	1075	**prefix** : 0x0A 06 (two bytes in hexadecimal)
1076	1076
1077		-**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.
1078	1078	)))
1079	1079	|(% style="width:97px" %)**Example**|(% style="width:401px" %)(((
1080	1080	0A 06 **01**
...	...	@@ -1082,14 +1082,13 @@
1082	1082	Enable trigger mode for the current working mode
1083	1083	)))
1084	1084
1085		-==== 3.4.2.5 Request trigger settings ====
	1026	+==== 3.4.2.5 Poll trigger settings ====
1086	1086
	1028	+Polls the trigger settings.
1087	1087
1088		-Requests the trigger settings.
1089		-
1090	1090	(% style="color:#037691" %)**AT Command:**
1091	1091
1092		-There is no AT Command available for this feature.
	1032	+There is no AT Command for this feature.
1093	1093
1094	1094	(% style="color:#037691" %)**Downlink Payload**
1095	1095
...	...	@@ -1104,7 +1104,6 @@
1104	1104
1105	1105	==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ====
1106	1106
1107		-
1108	1108	Enable or disable DI1/DI2/DI3 as a trigger.
1109	1109
1110	1110	(% style="color:#037691" %)**AT Command**
...	...	@@ -1159,9 +1159,9 @@
1159	1159
1160	1160	==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ====
1161	1161
1162		-
1163	1163	Sets DI1 or DI3 (for LT-33222-L) as a trigger.
1164	1164
	1103	+
1165	1165	(% style="color:#037691" %)**AT Command**
1166	1166
1167	1167	(% border="2" style="width:500px" %)
...	...	@@ -1198,9 +1198,9 @@
1198	1198
1199	1199	==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
1200	1200
1201		-
1202	1202	Sets DI2 as a trigger.
1203	1203
	1142	+
1204	1204	(% style="color:#037691" %)**AT Command**
1205	1205
1206	1206	(% border="2" style="width:500px" %)
...	...	@@ -1230,9 +1230,9 @@
1230	1230	)))
1231	1231	|(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64**
1232	1232
	1172	+
1233	1233	==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
1234	1234
1235		-
1236	1236	Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1237	1237
1238	1238	(% style="color:#037691" %)**AT Command**
...	...	@@ -1282,7 +1282,6 @@
1282	1282
1283	1283	==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
1284	1284
1285		-
1286	1286	Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1287	1287
1288	1288	(% style="color:#037691" %)**AT Command**
...	...	@@ -1330,7 +1330,6 @@
1330	1330
1331	1331	==== 3.4.2.11 Trigger – Set minimum interval ====
1332	1332
1333		-
1334	1334	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.
1335	1335
1336	1336	(% style="color:#037691" %)**AT Command**
...	...	@@ -1366,7 +1366,6 @@
1366	1366
1367	1367	==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
1368	1368
1369		-
1370	1370	Controls the digital outputs DO1, DO2, and DO3
1371	1371
1372	1372	(% style="color:#037691" %)**AT Command**
...	...	@@ -1397,11 +1397,11 @@
1397	1397	(((
1398	1398	01: Low,  00: High,  11: No action
1399	1399
1400		-(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:383px" %)
1401		-|(% 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**
1402		-|(% style="width:126px" %)02  01  00  11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action
1403		-|(% style="width:126px" %)02  00  11  01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low
1404		-|(% style="width:126px" %)02  11  01  00|(% style="width:85px" %)No Action|(% style="width:86px" %)Low|(% style="width:86px" %)High
	1336	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
	1337	+|(% 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**
	1338	+|02  01  00  11|Low|High|No Action
	1339	+|02  00  11  01|High|No Action|Low
	1340	+|02  11  01  00|No Action|Low|High
1405	1405	)))
1406	1406
1407	1407	(((
...	...	@@ -1415,165 +1415,152 @@
1415	1415	)))
1416	1416	)))
1417	1417
	1354	+
1418	1418	==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
1419	1419
1420	1420
1421		-(% style="color:#037691" %)**AT command**
	1358	+* (% style="color:#037691" %)**AT Command**
1422	1422
1423		-There is no AT command to control the digital output.
	1360	+There is no AT Command to control Digital Output
1424	1424
1425	1425
1426		-(% style="color:#037691" %)**Downlink payload**
	1363	+* (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
1427	1427
	1365	+(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Set DO1/DO2/DO3 output with time control
1428	1428
1429		-(% border="2" style="width:500px" %)
1430		-|(% style="width:116px" %)**Prefix**|(% style="width:382px" %)0xA9
1431		-|(% style="width:116px" %)**Parameters**|(% style="width:382px" %)(((
1432		-**inverter_mode**: 1 byte in hex.
1433	1433
1434		-**01:** DO pins revert to their original state after the timeout.
1435		-**00:** DO pins switch to an inverted state after the timeout.
	1368	+This is to control the digital output time of DO pin. Include four bytes:
1436	1436
	1370	+(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
1437	1437
1438		-**DO1_control_method_and_port_status **- 1 byte in hex
	1372	+(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode
1439	1439
1440		-0x01 : DO1 set to low
	1374	+01: DO pins will change back to original state after timeout.
1441	1441
1442		-0x00 : DO1 set to high
	1376	+00: DO pins will change to an inverter state after timeout
1443	1443
1444		-0x11 : DO1 NO action
1445	1445
	1379	+(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
1446	1446
1447		-**DO2_control_method_and_port_status** - 1 byte in hex
	1381	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
	1382	+|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
	1383	+|0x01|DO1 set to low
	1384	+|0x00|DO1 set to high
	1385	+|0x11|DO1 NO Action
1448	1448
1449		-0x01 : DO2 set to low
	1387	+(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:
1450	1450
1451		-0x00 : DO2 set to high
	1389	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
	1390	+|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
	1391	+|0x01|DO2 set to low
	1392	+|0x00|DO2 set to high
	1393	+|0x11|DO2 NO Action
1452	1452
1453		-0x11 : DO2 NO action
	1395	+(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:
1454	1454
	1397	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
	1398	+|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
	1399	+|0x01|DO3 set to low
	1400	+|0x00|DO3 set to high
	1401	+|0x11|DO3 NO Action
1455	1455
1456		-**DO3_control_method_and_port_status **- 1 byte in hex
	1403	+(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)
1457	1457
1458		-0x01 : DO3 set to low
1459	1459
1460		-0x00 : DO3 set to high
	1406	+(% style="color:red" %)**Note: **
1461	1461
1462		-0x11 : DO3 NO action
	1408	+ Since firmware v1.6.0, the latch time support 4 bytes and 2 bytes
1463	1463
	1410	+ Before firmware v1.6.0, the latch time only supported 2 bytes.
1464	1464
1465		-**latching_time** : 4 bytes in hex
	1412	+(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1466	1466
1467		-(% style="color:red" %)**Note: **
1468	1468
1469		- Since firmware v1.6.0, the latch time support 4 bytes or 2 bytes
	1415	+**Example payload:**
1470	1470
1471		- Before firmware v1.6.0, the latch time only supported 2 bytes.
	1417	+**~1. A9 01 01 01 01 07 D0**
1472	1472
1473		-(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1474		-)))
1475		-|(% 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>
1476		-|(% style="width:116px" %)**Example**|(% style="width:382px" %)(((
1477		-**A9 01 01 01 01 07 D0**
1478		-
1479	1479	DO1 pin, DO2 pin, and DO3 pin will be set to low, last for 2 seconds, and then revert to their original state.
1480	1480
	1421	+**2. A9 01 00 01 11 07 D0**
1481	1481
1482		-**A9 01 00 01 11 07 D0**
1483		-
1484	1484	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.
1485	1485
	1425	+**3. A9 00 00 00 00 07 D0**
1486	1486
1487		-**A9 00 00 00 00 07 D0**
1488		-
1489	1489	DO1 pin, DO2 pin, and DO3 pin will be set to high, last for 2 seconds, and then all change to low.
1490	1490
	1429	+**4. A9 00 11 01 00 07 D0**
1491	1491
1492		-**A9 00 11 01 00 07 D0**
1493		-
1494	1494	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.
1495		-)))
1496	1496
	1433	+
1497	1497	==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
1498	1498
1499	1499
1500		-(% style="color:#037691" %)**AT Command:**
	1437	+* (% style="color:#037691" %)**AT Command:**
1501	1501
1502		-There is no AT Command to control the Relay Output.
	1439	+There is no AT Command to control Relay Output
1503	1503
1504	1504
1505		-(% style="color:#037691" %)**Downlink Payload**
	1442	+* (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
1506	1506
1507		-(% border="2" style="width:500px" %)
1508		-|(% style="width:113px" %)**Prefix**|(% style="width:384px" %)0x03
1509		-|(% style="width:113px" %)**Parameters**|(% style="width:384px" %)(((
1510		-**RO1_status** : 1 byte in hex
	1444	+(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Set RO1/RO2 output
1511	1511
1512		-00: Close
1513	1513
1514		-01: Open
	1447	+(((
	1448	+If payload is 0x030100, it means setting RO1 to close and RO2 to open.
	1449	+)))
1515	1515
1516		-11: No action
	1451	+(((
	1452	+00: Close ,  01: Open , 11: No action
1517	1517
1518		-
1519		-**RO2_status** : 1 byte in hex
1520		-
1521		-00: Close
1522		-
1523		-01: Open
1524		-
1525		-11: No action
	1454	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %)
	1455	+|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**RO1**|(% style="background-color:#4f81bd; color:white" %)**RO2**
	1456	+|03  00  11|Open|No Action
	1457	+|03  01  11|Close|No Action
	1458	+|03  11  00|No Action|Open
	1459	+|03  11  01|No Action|Close
	1460	+|03  00  00|Open|Open
	1461	+|03  01  01|Close|Close
	1462	+|03  01  00|Close|Open
	1463	+|03  00  01|Open|Close
1526	1526	)))
1527		-|(% style="width:113px" %)**Payload format**|(% style="width:384px" %)<prefix><RO1_status><RO2_status>
1528		-|(% style="width:113px" %)**Example**|(% style="width:384px" %)(((
1529		-(% border="2" %)
1530		-|=Payload|=RO1|=RO2
1531		-|03  00  11|Open|No action
1532		-|03  01  11|Close|No action
1533		-|03 11  00|No action|Open
1534		-|03 11 10|No action|Close
1535		-|03 00 00|Open|Open
1536		-|03 01 01|Close|Close
1537		-|03 01 00|Close|Open
1538		-|03 00 01|Open|Close
1539	1539
1540		-(% style="color:red" %)**The device will transmit an uplink packet if the downlink payload is executed successfully.**
1541		-)))
	1466	+(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
1542	1542
1543	1543
1544	1544	==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
1545	1545
1546		-
1547	1547	Controls the relay output time.
1548	1548
	1473	+* (% style="color:#037691" %)**AT Command:**
1549	1549
1550		-(% style="color:#037691" %)**AT Command:**
	1475	+There is no AT Command to control Relay Output
1551	1551
1552		-There is no AT Command to control the Relay Output
1553	1553
	1478	+* (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1554	1554
1555		-(% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
	1480	+(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Set RO1/RO2 relay with time control
1556	1556
1557		-(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
1558	1558
	1483	+This is to control the relay output time. It includes four bytes:
1559	1559
1560		-This controls the relay output time and includes 4 bytes:
	1485	+(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
1561	1561
1562		-(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)
	1487	+(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
1563	1563
1564		-(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode
1565		-
1566	1566	01: Relays will change back to their original state after timeout.
1567	1567
1568	1568	00: Relays will change to the inverter state after timeout.
1569	1569
1570	1570
1571		-(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status:
	1494	+(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
1572	1572
1573	1573	[[image:image-20221008095908-1.png||height="364" width="564"]]
1574	1574
1575	1575
1576		-(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes (cc)**(%%): Latching time. Unit: ms
	1499	+(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms
1577	1577
1578	1578
1579	1579	(% style="color:red" %)**Note:**
...	...	@@ -1583,7 +1583,7 @@
1583	1583	Before firmware v1.6.0, the latch time only supported 2 bytes.
1584	1584
1585	1585
1586		-(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
	1509	+(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1587	1587
1588	1588
1589	1589	**Example payload:**
...	...	@@ -1611,10 +1611,17 @@
1611	1611
1612	1612	When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
1613	1613
	1537	+* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX   ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
	1538	+
	1539	+* (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):**
	1540	+
	1541	+(% style="color:blue" %)**0xA5 aa bb cc   ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc
	1542	+
	1543	+
1614	1614	(% style="color:#037691" %)**AT Command**
1615	1615
1616	1616	(% border="2" style="width:500px" %)
1617		-|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage>,<logic>
	1547	+|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage><logic>
1618	1618	|(% style="width:137px" %)**Response**|(% style="width:361px" %)
1619	1619	|(% style="width:137px" %)**Parameters**|(% style="width:361px" %)(((
1620	1620	**voltage** : voltage threshold in mV
...	...	@@ -1621,9 +1621,9 @@
1621	1621
1622	1622	**logic**:
1623	1623
1624		-**0** : lower than
	1554	+0 : lower than
1625	1625
1626		-**1**: higher than
	1556	+1: higher than
1627	1627
1628	1628	if you leave logic parameter blank, it is considered 0
1629	1629	)))
...	...	@@ -1652,9 +1652,9 @@
1652	1652
1653	1653	**logic**: (1 byte in hexadecimal)
1654	1654
1655		-**0** : lower than
	1585	+0 : lower than
1656	1656
1657		-**1**: higher than
	1587	+1: higher than
1658	1658
1659	1659	if you leave logic parameter blank, it is considered 1 (higher than)
1660	1660	)))
...	...	@@ -1676,10 +1676,22 @@
1676	1676
1677	1677	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.
1678	1678
	1609	+* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) **
	1610	+
	1611	+(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count
	1612	+
	1613	+(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set
	1614	+
	1615	+
	1616	+* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):**
	1617	+
	1618	+(% style="color:blue" %)**0x A8 aa bb cc dd ee     ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee)
	1619	+
	1620	+
1679	1679	(% style="color:#037691" %)**AT Command**
1680	1680
1681	1681	(% border="2" style="width:500px" %)
1682		-|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter>,<number>
	1624	+|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter><number>
1683	1683	|(% style="width:134px" %)**Response**|(% style="width:364px" %)
1684	1684	|(% style="width:134px" %)**Parameters**|(% style="width:364px" %)(((
1685	1685	**counting_parameter** :
...	...	@@ -1725,6 +1725,12 @@
1725	1725
1726	1726	This command clears the counting in counting mode.
1727	1727
	1670	+* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT         **(%%) ~/~/ clear all counting
	1671	+
	1672	+* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):**
	1673	+
	1674	+(% style="color:blue" %)**0x A6 01    ** (%%)~/~/ clear all counting
	1675	+
1728	1728	(% style="color:#037691" %)**AT Command**
1729	1729
1730	1730	(% border="2" style="width:500px" %)
...	...	@@ -1742,11 +1742,24 @@
1742	1742	)))
1743	1743	|(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
1744	1744
1745		-==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ====
	1693	+==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1746	1746
1747		-
1748	1748	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.
1749	1749
	1697	+* (% style="color:#037691" %)**AT Command:**
	1698	+
	1699	+(% 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)
	1700	+
	1701	+
	1702	+* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):**
	1703	+
	1704	+(% style="color:blue" %)**0x A7 aa bb cc     ** (%%)~/~/ same as AT+COUTIME =aa bb cc,
	1705	+
	1706	+(((
	1707	+Range: aa bb cc:0 to 16777215,  (unit: seconds)
	1708	+)))
	1709	+
	1710	+
1750	1750	(% style="color:#037691" %)**AT Command**
1751	1751
1752	1752	(% border="2" style="width:500px" %)
...	...	@@ -1774,13 +1774,22 @@
1774	1774	Sets the device to save its counting results to the memory every 60 seconds.
1775	1775	)))
1776	1776
1777		-==== 3.4.2.20 Reset saved RO and DO states ====
	1738	+==== 3.4.2.20 Reset save RO DO state ====
1778	1778
1779		-
1780	1780	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.
1781	1781
1782		-(% style="color:#037691" %)**AT Command**
	1742	+* (% style="color:#037691" %)**AT Command:**
1783	1783
	1744	+(% style="color:blue" %)**AT+RODORESET=1    **(%%)~/~/ RODO will close when the device joining the network. (default)
	1745	+
	1746	+(% 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.
	1747	+
	1748	+
	1749	+* (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):**
	1750	+
	1751	+(% style="color:blue" %)**0x AD aa      ** (%%)~/~/ same as AT+RODORET =aa
	1752	+
	1753	+
1784	1784	(% border="2" style="width:500px" %)
1785	1785	|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state>
1786	1786	|(% style="width:127px" %)**Response**|(% style="width:371px" %)
...	...	@@ -1801,8 +1801,6 @@
1801	1801	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.
1802	1802	)))
1803	1803
1804		-(% style="color:#037691" %)**Downlink Payload**
1805		-
1806	1806	(% border="2" style="width:500px" %)
1807	1807	|(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state>
1808	1808	|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
...	...	@@ -1826,20 +1826,24 @@
1826	1826
1827	1827	==== 3.4.2.21 Encrypted payload ====
1828	1828
1829		-
1830	1830	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.
1831	1831
1832		-(% style="color:#037691" %)**AT Command:**
	1799	+* (% style="color:#037691" %)**AT Command:**
1833	1833
	1801	+(% style="color:blue" %)**AT+DECRYPT=1  ** (%%)~/~/ The payload is uploaded without encryption
	1802	+
	1803	+(% style="color:blue" %)**AT+DECRYPT=0    **(%%)~/~/  Encrypt when uploading payload (default)
	1804	+
	1805	+
1834	1834	(% border="2" style="width:500px" %)
1835	1835	|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state>
1836	1836	|(% style="width:127px" %)**Response**|(% style="width:371px" %)
1837	1837	|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1838		-**state** :
	1810	+state :
1839	1839
1840		-**1** : The payload is uploaded without encryption
	1812	+1 : The payload is uploaded without encryption
1841	1841
1842		-**0** : The payload is encrypted when uploaded (default)
	1814	+0 : The payload is encrypted when uploaded (default)
1843	1843	)))
1844	1844	|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1845	1845	AT+DECRYPT=1
...	...	@@ -1856,11 +1856,15 @@
1856	1856
1857	1857	==== 3.4.2.22 Get sensor value ====
1858	1858
1859		-
1860	1860	This command allows you to retrieve and optionally uplink sensor readings through the serial port.
1861	1861
1862		-(% style="color:#037691" %)**AT Command**
	1833	+* (% style="color:#037691" %)**AT Command:**
1863	1863
	1835	+(% style="color:blue" %)**AT+GETSENSORVALUE=0    **(%%)~/~/ The serial port retrieves the reading of the current sensor.
	1836	+
	1837	+(% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it.
	1838	+
	1839	+
1864	1864	(% border="2" style="width:500px" %)
1865	1865	|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state>
1866	1866	|(% style="width:127px" %)**Response**|(% style="width:371px" %)
...	...	@@ -1886,11 +1886,15 @@
1886	1886
1887	1887	==== 3.4.2.23 Resetting the downlink packet count ====
1888	1888
1889		-
1890	1890	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.
1891	1891
1892		-(% style="color:#037691" %)**AT Command**
	1867	+* (% style="color:#037691" %)**AT Command:**
1893	1893
	1869	+(% 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)
	1870	+
	1871	+(% 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.
	1872	+
	1873	+
1894	1894	(% border="2" style="width:500px" %)
1895	1895	|(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state>
1896	1896	|(% style="width:130px" %)**Response**|(% style="width:368px" %)(((
...	...	@@ -1922,6 +1922,17 @@
1922	1922
1923	1923	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.
1924	1924
	1905	+* (% style="color:#037691" %)**AT Command:**
	1906	+
	1907	+(% 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)
	1908	+
	1909	+(% 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.
	1910	+
	1911	+
	1912	+* (% style="color:#037691" %)**Downlink Payload **(%%)**:**
	1913	+
	1914	+(% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set  the DISMACANS=1
	1915	+
1925	1925	(% style="color:#037691" %)**AT Command**
1926	1926
1927	1927	(% border="2" style="width:500px" %)
...	...	@@ -1965,33 +1965,43 @@
1965	1965
1966	1966	==== 3.4.2.25 Copy downlink to uplink ====
1967	1967
	1959	+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.
1968	1968
1969		-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.
	1961	+* (% style="color:#037691" %)**AT Command**(%%)**:**
1970	1970
1971		-(% style="color:#037691" %)**AT Command**(%%)**:**
	1963	+(% 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.
1972	1972
1973		-(% 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.
	1965	+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.
1974	1974
1975		-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.
1976	1976
1977		-
1978	1978	[[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"]]
1979	1979
1980	1980	For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
1981	1981
1982		-[[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	+(% border="2" style="width:500px" %)
	1973	+|(% style="width:122px" %)**Command**|(% style="width:376px" %)(((
	1974	+AT+RPL=5
1983	1983
1984		-For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
	1976	+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.
	1977	+)))
	1978	+|(% style="width:122px" %)**Example**|(% style="width:376px" %)(((
	1979	+Downlink:
1985	1985
	1981	+01 00 02 58
1986	1986
1987		-(% style="color:#037691" %)**Downlink Payload**(%%)**:**
	1983	+Uplink:
1988	1988
1989		-There is no downlink option available for this feature.
	1985	+01 01 00 02 58
	1986	+)))
1990	1990
	1988	+[[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"]]
1991	1991
1992		-==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
	1990	+For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
1993	1993
1994	1994
	1993	+
	1994	+==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
	1995	+
1995	1995	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.
1996	1996
1997	1997	* (((
...	...	@@ -2010,13 +2010,10 @@
2010	2010
2011	2011	== 3.5 Integrating with ThingsEye.io ==
2012	2012
2013		-
2014	2014	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.
2015	2015
2016		-
2017	2017	=== 3.5.1 Configuring The Things Stack ===
2018	2018
2019		-
2020	2020	We use The Things Stack Sandbox in this example:
2021	2021
2022	2022	* In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
...	...	@@ -2028,12 +2028,10 @@
2028	2028	The username and  password (API key) you created here are required in the next section.
2029	2029	{{/info}}
2030	2030
2031		-[[image:tts-mqtt-integration.png]]
	2029	+[[image:tts-mqtt-integration.png||height="625" width="1000"]]
2032	2032
2033		-
2034	2034	=== 3.5.2 Configuring ThingsEye.io ===
2035	2035
2036		-
2037	2037	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.
2038	2038
2039	2039	* Login to your [[ThingsEye.io >>https://thingseye.io]]account.
...	...	@@ -2040,7 +2040,7 @@
2040	2040	* Under the **Integrations center**, click **Integrations**.
2041	2041	* Click the **Add integration** button (the button with the **+** symbol).
2042	2042
2043		-[[image:thingseye-io-step-1.png]]
	2039	+[[image:thingseye-io-step-1.png||height="625" width="1000"]]
2044	2044
2045	2045
2046	2046	On the **Add integration** window, configure the following:
...	...	@@ -2055,7 +2055,7 @@
2055	2055	** Allow create devices or assets
2056	2056	* Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
2057	2057
2058		-[[image:thingseye-io-step-2.png]]
	2054	+[[image:thingseye-io-step-2.png||height="625" width="1000"]]
2059	2059
2060	2060
2061	2061	**Uplink data converter:**
...	...	@@ -2066,7 +2066,7 @@
2066	2066	* 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]].
2067	2067	* Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
2068	2068
2069		-[[image:thingseye-io-step-3.png]]
	2065	+[[image:thingseye-io-step-3.png||height="625" width="1000"]]
2070	2070
2071	2071
2072	2072	**Downlink data converter (this is an optional step):**
...	...	@@ -2077,7 +2077,7 @@
2077	2077	* 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]].
2078	2078	* Click the **Next** button. You will be navigated to the **Connection** tab.
2079	2079
2080		-[[image:thingseye-io-step-4.png]]
	2076	+[[image:thingseye-io-step-4.png||height="625" width="1000"]]
2081	2081
2082	2082
2083	2083	**Connection:**
...	...	@@ -2092,21 +2092,20 @@
2092	2092
2093	2093	* Click the **Add** button.
2094	2094
2095		-[[image:thingseye-io-step-5.png]]
	2091	+[[image:thingseye-io-step-5.png||height="625" width="1000"]]
2096	2096
2097	2097
2098	2098	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.
2099	2099
2100	2100
2101		-[[image:thingseye.io_integrationsCenter_integrations.png]]
	2097	+[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
2102	2102
2103	2103
2104	2104	==== 3.5.2.1 Viewing integration details ====
2105	2105
2106		-
2107	2107	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.
2108	2108
2109		-[[image:integration-details.png]]
	2104	+[[image:integration-details.png||height="686" width="1000"]]
2110	2110
2111	2111
2112	2112	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.
...	...	@@ -2115,45 +2115,37 @@
2115	2115	See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
2116	2116	{{/info}}
2117	2117
	2113	+==== **3.5.2.2 Viewing events** ====
2118	2118
2119		-==== 3.5.2.2 Viewing events ====
2120		-
2121		-
2122	2122	The **Events **tab displays all the uplink messages from the LT-22222-L.
2123	2123
2124	2124	* Select **Debug **from the **Event type** dropdown.
2125	2125	* Select the** time frame** from the **time window**.
2126	2126
2127		-[[image:thingseye-events.png]]
	2120	+[[image:thingseye-events.png||height="686" width="1000"]]
2128	2128
2129	2129
2130		-* To view the **JSON payload** of a message, click on the **three dots (...)** in the **Message** column of the desired message.
	2123	+* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
2131	2131
2132		-[[image:thingseye-json.png]]
	2125	+[[image:thingseye-json.png||width="1000"]]
2133	2133
2134	2134
2135		-==== 3.5.2.3 Deleting an integration ====
	2128	+==== **3.5.2.3 Deleting an integration** ====
2136	2136
2137		-
2138	2138	If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
2139	2139
2140	2140
2141		-==== 3.5.2.4 Viewing sensor data on a dashboard ====
	2133	+==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
2142	2142
	2135	+This will be added soon.
2143	2143
2144		-You can create a dashboard with ThingsEye to visualize the sensor data coming from the LHT65N-VIB. The following image shows a dashboard created for the LT-22222-L. See **Creating a dashboard** in ThingsEye documentation for more information.
2145	2145
2146		-
2147		-
2148		-[[image:lt-22222-l-dashboard.png]]
2149		-
2150		-
2151	2151	== 3.6 Interface Details ==
2152	2152
2153	2153	=== 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
2154	2154
2155	2155
2156		-Supports** NPN-type **sensors.
	2143	+Supports NPN-type sensors.
2157	2157
2158	2158	[[image:1653356991268-289.png]]
2159	2159
...	...	@@ -2275,15 +2275,15 @@
2275	2275	)))
2276	2276
2277	2277
2278		-(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor
	2265	+(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
2279	2279
2280		-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.
	2267	+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.
2281	2281
2282		-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.
	2269	+To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram.
2283	2283
2284	2284	[[image:image-20230616235145-1.png]]
2285	2285
2286		-(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector
	2273	+(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
2287	2287
2288	2288	[[image:image-20240219115718-1.png]]
2289	2289
...	...	@@ -2359,9 +2359,8 @@
2359	2359	[[image:image-20220524100215-10.png||height="382" width="723"]]
2360	2360
2361	2361
2362		-== 3.7 LED Indicators ==
	2349	+== 3.7 LEDs Indicators ==
2363	2363
2364		-
2365	2365	The table below lists the behavior of LED indicators for each port function.
2366	2366
2367	2367	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
...	...	@@ -2394,22 +2394,18 @@
2394	2394
2395	2395	= 4. Using AT Commands =
2396	2396
2397		-
2398	2398	The LT-22222-L supports programming using AT Commands.
2399	2399
2400		-
2401	2401	== 4.1 Connecting the LT-22222-L to a PC ==
2402	2402
2403		-
2404	2404	(((
2405		-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.
	2388	+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.
2406	2406
2407		-[[image:usb-ttl-audio-jack-connection.jpg]]
2408		-
2409		-
	2390	+[[image:usb-ttl-programming.png]]
2410	2410	)))
2411	2411
2412	2412
	2394	+
2413	2413	(((
2414	2414	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:
2415	2415	)))
...	...	@@ -2420,10 +2420,7 @@
2420	2420	(((
2421	2421	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/]]
2422	2422
2423		-
2424	2424	== 4.2 LT-22222-L related AT commands ==
2425		-
2426		-
2427	2427	)))
2428	2428
2429	2429	(((
...	...	@@ -2442,39 +2442,39 @@
2442	2442	* **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
2443	2443	* **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
2444	2444	* **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
2445		-* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2446		-* **##AT+DR##**:  Get or set the Data Rate. (0-7 corresponding to DR_X)
2447		-* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2448		-* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)
2449		-* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency
2450		-* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2451		-* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2452		-* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2453		-* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2454		-* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2455		-* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2456		-* ##**AT+NWKID**##: Get or set the Network ID
2457		-* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)
2458		-* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)
2459		-* ##**AT+CLASS**##: Get or set the Device Class
2460		-* ##**AT+JOIN**##: Join network
2461		-* ##**AT+NJS**##: Get OTAA Join Status
2462		-* ##**AT+SENDB**##: Send hexadecimal data along with the application port
2463		-* ##**AT+SEND**##: Send text data along with the application port
2464		-* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)
2465		-* ##**AT+RECV**##: Print last received data in raw format
2466		-* ##**AT+VER**##: Get current image version and Frequency Band
2467		-* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)
2468		-* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)
2469		-* ##**AT+SNR**##: Get the SNR of the last received packet
2470		-* ##**AT+RSSI**##: Get the RSSI of the last received packet
2471		-* ##**AT+TDC**##: Get or set the application data transmission interval in ms
2472		-* ##**AT+PORT**##: Get or set the application port
2473		-* ##**AT+DISAT**##: Disable AT commands
2474		-* ##**AT+PWORD**##: Set password, max 9 digits
2475		-* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2476		-* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN470
2477		-* ##**AT+CFG**##: Print all settings
	2424	+* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
	2425	+* AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)
	2426	+* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
	2427	+* AT+PNM: Get or set the public network mode. (0: off, 1: on)
	2428	+* AT+RX2FQ: Get or set the Rx2 window frequency
	2429	+* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
	2430	+* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
	2431	+* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
	2432	+* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
	2433	+* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
	2434	+* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
	2435	+* AT+NWKID: Get or set the Network ID
	2436	+* AT+FCU: Get or set the Frame Counter Uplink (FCntUp)
	2437	+* AT+FCD: Get or set the Frame Counter Downlink (FCntDown)
	2438	+* AT+CLASS: Get or set the Device Class
	2439	+* AT+JOIN: Join network
	2440	+* AT+NJS: Get OTAA Join Status
	2441	+* AT+SENDB: Send hexadecimal data along with the application port
	2442	+* AT+SEND: Send text data along with the application port
	2443	+* AT+RECVB: Print last received data in binary format (with hexadecimal values)
	2444	+* AT+RECV: Print last received data in raw format
	2445	+* AT+VER: Get current image version and Frequency Band
	2446	+* AT+CFM: Get or Set the confirmation mode (0-1)
	2447	+* AT+CFS: Get confirmation status of the last AT+SEND (0-1)
	2448	+* AT+SNR: Get the SNR of the last received packet
	2449	+* AT+RSSI: Get the RSSI of the last received packet
	2450	+* AT+TDC: Get or set the application data transmission interval in ms
	2451	+* AT+PORT: Get or set the application port
	2452	+* AT+DISAT: Disable AT commands
	2453	+* AT+PWORD: Set password, max 9 digits
	2454	+* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode
	2455	+* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470
	2456	+* AT+CFG: Print all settings
2478	2478	)))
2479	2479
2480	2480
...	...	@@ -2620,19 +2620,16 @@
2620	2620
2621	2621	== 5.1 Counting how many objects pass through the flow line ==
2622	2622
2623		-
2624	2624	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]]?
2625	2625
2626	2626
2627	2627	= 6. FAQ =
2628	2628
2629		-
2630	2630	This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
2631	2631
2632	2632
2633	2633	== 6.1 How to update the firmware? ==
2634	2634
2635		-
2636	2636	Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to:
2637	2637
2638	2638	* Support new features
...	...	@@ -2642,7 +2642,7 @@
2642	2642	You will need the following things before proceeding:
2643	2643
2644	2644	* 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
2645		-* USB to TTL adapter/converter
	2621	+* USB to TTL adapter
2646	2646	* 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)
2647	2647	* 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.
2648	2648
...	...	@@ -2652,7 +2652,7 @@
2652	2652
2653	2653	Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2654	2654
2655		-[[image:usb-ttl-audio-jack-connection.jpg]]
	2631	+[[image:usb-ttl-programming.png]]
2656	2656
2657	2657
2658	2658
...	...	@@ -2685,8 +2685,6 @@
2685	2685	(((
2686	2686	(((
2687	2687	== 6.2 How to change the LoRaWAN frequency band/region? ==
2688		-
2689		-
2690	2690	)))
2691	2691	)))
2692	2692
...	...	@@ -2698,8 +2698,6 @@
2698	2698
2699	2699
2700	2700	== 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
2701		-
2702		-
2703	2703	)))
2704	2704
2705	2705	(((
...	...	@@ -2773,13 +2773,11 @@
2773	2773
2774	2774	== 6.4 How to change the uplink interval? ==
2775	2775
2776		-
2777	2777	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/]]
2778	2778
2779	2779
2780	2780	== 6.5 Can I see the counting event in the serial output? ==
2781	2781
2782		-
2783	2783	(((
2784	2784	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.
2785	2785
...	...	@@ -2786,7 +2786,6 @@
2786	2786
2787	2787	== 6.6 Can I use point-to-point communication with LT-22222-L? ==
2788	2788
2789		-
2790	2790	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]].
2791	2791
2792	2792
...	...	@@ -2795,7 +2795,6 @@
2795	2795	(((
2796	2796	== 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
2797	2797
2798		-
2799	2799	* If the device is not properly shut down and is directly powered off.
2800	2800	* It will default to a power-off state.
2801	2801	* In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
...	...	@@ -2803,7 +2803,6 @@
2803	2803
2804	2804	== 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
2805	2805
2806		-
2807	2807	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:
2808	2808
2809	2809
...	...	@@ -2812,19 +2812,16 @@
2812	2812
2813	2813	== 6.9 Can the LT-22222-L save the RO state? ==
2814	2814
2815		-
2816	2816	To enable this feature, the firmware version must be 1.6.0 or higher.
2817	2817
2818	2818
2819	2819	== 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
2820	2820
2821		-
2822	2822	It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
2823	2823
2824	2824
2825	2825	= 7. Troubleshooting =
2826	2826
2827		-
2828	2828	This section provides some known troubleshooting tips.
2829	2829
2830	2830
...	...	@@ -2833,8 +2833,6 @@
2833	2833	(((
2834	2834	(((
2835	2835	== 7.1 Downlink isn't working. How can I solve this? ==
2836		-
2837		-
2838	2838	)))
2839	2839	)))
2840	2840
...	...	@@ -2846,8 +2846,6 @@
2846	2846
2847	2847
2848	2848	== 7.2 Having trouble uploading an image? ==
2849		-
2850		-
2851	2851	)))
2852	2852
2853	2853	(((
...	...	@@ -2858,8 +2858,6 @@
2858	2858
2859	2859
2860	2860	== 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
2861		-
2862		-
2863	2863	)))
2864	2864
2865	2865	(((
...	...	@@ -2869,7 +2869,6 @@
2869	2869
2870	2870	== 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? ==
2871	2871
2872		-
2873	2873	The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
2874	2874	Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2875	2875
...	...	@@ -2876,7 +2876,6 @@
2876	2876
2877	2877	= 8. Ordering information =
2878	2878
2879		-
2880	2880	(% style="color:#4f81bd" %)**LT-22222-L-XXX:**
2881	2881
2882	2882	(% style="color:#4f81bd" %)**XXX:**
...	...	@@ -2893,7 +2893,6 @@
2893	2893
2894	2894	= 9. Package information =
2895	2895
2896		-
2897	2897	**Package includes**:
2898	2898
2899	2899	* 1 x LT-22222-L I/O Controller
...	...	@@ -2910,7 +2910,6 @@
2910	2910
2911	2911	= 10. Support =
2912	2912
2913		-
2914	2914	* (((
2915	2915	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.
2916	2916	)))
...	...	@@ -2922,7 +2922,6 @@
2922	2922
2923	2923	= 11. Reference​​​​​ =
2924	2924
2925		-
2926	2926	* 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]]
2927	2927	* [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]]
2928	2928	* [[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

usb-ttl-audio-jack-connection.jpg

Author

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

Size

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

Content