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

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 3 added, 0 removed)
  • dragino-lorawan-nw-lt-22222-n.jpg
  • dragino-ttn-te.jpg
  • lorawan-nw.jpg

Details

Page properties

Content

...	...	@@ -27,7 +27,7 @@
27	27	**This manual is also applicable to the LT-33222-L.**
28	28	{{/info}}
29	29
30		-The Dragino (% style="color:blue" %)**LT-22222-L I/O Controller**(%%) is an advanced LoRaWAN device designed to provide seamless wireless long-range connectivity with various I/O options, including analog current and voltage inputs, digital inputs and outputs, and relay outputs.
	30	+The Dragino (% style="color:blue" %)**LT-22222-L I/O Controller**(%%) is an advanced LoRaWAN end device designed to provide seamless wireless long-range connectivity with various I/O options, including analog current and voltage inputs, digital inputs and outputs, and relay outputs.
31	31
32	32	The LT-22222-L I/O Controller simplifies and enhances I/O monitoring and controlling. It is ideal for professional applications in wireless sensor networks, including irrigation systems, smart metering, smart cities, building automation, and more. These controllers are designed for easy, cost-effective deployment using LoRa wireless technology.
33	33	)))
...	...	@@ -40,21 +40,20 @@
40	40	(((
41	41	You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways:
42	42
43		-* If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Network), you can select a network and register the LT-22222-L I/O controller with it.
	43	+* If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Stack Community Network), you can select a network and register the LT-22222-L I/O controller with it.
44	44	* If there is no public LoRaWAN coverage in your area, you can set up a LoRaWAN gateway, or multiple gateways, and connect them to a LoRaWAN network server to create adequate coverage. Then, register the LT-22222-L I/O controller with this network.
45	45	* Setup your own private LoRaWAN network.
46		-
47		-{{info}}
48		- You can use a LoRaWAN gateway, such as the [[Dragino LG308>>https://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], to expand or create LoRaWAN coverage in your area.
49		-{{/info}}
50	50	)))
51	51
52	52	(((
53		-[[image:1653295757274-912.png]]
54		-
55	55
	50	+
	51	+The network diagram below illustrates how the LT-22222-L communicates with a typical LoRaWAN network.
56	56	)))
57	57
	54	+(% class="wikigeneratedid" %)
	55	+[[image:lorawan-nw.jpg||height="354" width="900"]]
	56	+
58	58	== 1.2 Specifications ==
59	59
60	60	(% style="color:#037691" %)**Hardware System:**
...	...	@@ -115,7 +115,21 @@
115	115	* Smart cities
116	116	* Smart factory
117	117
	117	+== 1.5 Hardware Variants ==
118	118
	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
	126	+* 2 x Relay Output (5A@250VAC / 30VDC)
	127	+* 2 x 0~~20mA Analog Input (res:0.01mA)
	128	+* 2 x 0~~30V Analog Input (res:0.01v)
	129	+* 1 x Counting Port
	130	+)))
	131	+
119	119	== 2. Assembling the device ==
120	120
121	121	== 2.1 Connecting the antenna ==
...	...	@@ -123,17 +123,17 @@
123	123	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.
124	124
125	125	{{warning}}
126		-Warning! Do not power on the device without connecting the antenna.
	139	+**Warning! Do not power on the device without connecting the antenna.**
127	127	{{/warning}}
128	128
129	129	== 2.2 Terminals ==
130	130
131		-The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 terminals and the lower screw terminal block has 10 terminals.
	144	+The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals.
132	132
133		-Upper screw terminal block (from left to right):
	146	+**Upper screw terminal block (from left to right):**
134	134
135	135	(% style="width:634px" %)
136		-|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function
	149	+|=(% style="width: 295px;" %)Screw Terminal|=(% style="width: 338px;" %)Function
137	137	|(% style="width:295px" %)GND|(% style="width:338px" %)Ground
138	138	|(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage
139	139	|(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2
...	...	@@ -141,10 +141,10 @@
141	141	|(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2
142	142	|(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1
143	143
144		-Lower screw terminal block (from left to right):
	157	+**Lower screw terminal block (from left to right):**
145	145
146	146	(% style="width:633px" %)
147		-|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function
	160	+|=(% style="width: 296px;" %)Screw Terminal|=(% style="width: 334px;" %)Function
148	148	|(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1
149	149	|(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1
150	150	|(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2
...	...	@@ -156,14 +156,12 @@
156	156	|(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
157	157	|(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
158	158
159		-== 2.3 Powering the device ==
	172	+== 2.3 Connecting LT-22222-L to a Power Source ==
160	160
161		-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.
	174	+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.
162	162
163		-Once powered, 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. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LED** will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status.
164		-
165	165	{{warning}}
166		-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.
	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.**
167	167	{{/warning}}
168	168
169	169
...	...	@@ -170,36 +170,51 @@
170	170	[[image:1653297104069-180.png]]
171	171
172	172
173		-= 3. Registering with a LoRaWAN Network Server =
	184	+= 3. Registering LT-22222-L with a LoRaWAN Network Server =
174	174
175		-By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode. It supports OTAA (Over-the-Air Activation), the most secure method for activating a device with a LoRaWAN network server. The LT-22222-L comes with device registration information that allows you to register it with a LoRaWAN network, enabling the device to perform OTAA activation with the network server upon initial power-up and after any subsequent reboots.
	186	+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.
176	176
177		-After powering on, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** the LoRaWAN network. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LED** will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status.
178	178
179		-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.
180		-
181		-The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
182		-
183		-[[image:image-20220523172350-1.png||height="266" width="864"]]
184		-
185	185	=== 3.2.1 Prerequisites ===
186	186
187		-Make sure you have the device registration information such as DevEUI, AppEUI, and AppKey with you. The 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.
	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.
188	188
189	189	[[image:image-20230425173427-2.png||height="246" width="530"]]
190	190
	195	+{{info}}
	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.
	197	+{{/info}}
	198	+
191	191	The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
192	192
193		-=== 3.2.2 The Things Stack Sandbox (TTSS) ===
	201	+=== 3.2.2 The Things Stack ===
194	194
	203	+This section guides you through how to register your LT-22222-L with The Things Stack Sandbox.
	204	+
	205	+{{info}}
195	195	The Things Stack Sandbox was formally called The Things Stack Community Edition.
	207	+{{/info}}
196	196
197		-* Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account.
198		-* Create an application with The Things Stack if you do not have one yet.
199		-* Go to your application page and click on the **End devices** in the left menu.
	209	+
	210	+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.
	211	+
	212	+
	213	+[[image:dragino-lorawan-nw-lt-22222-n.jpg]]
	214	+
	215	+{{info}}
	216	+ You can use a LoRaWAN gateway, such as the [[Dragino LPS8N>>https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]], to expand or create LoRaWAN coverage in your area.
	217	+{{/info}}
	218	+
	219	+
	220	+==== 3.2.2.1 Setting up ====
	221	+
	222	+* Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet.
	223	+* Log in to your The Things Stack Sandbox account.
	224	+* Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs).
	225	+* Go to your application's page and click on the **End devices** in the left menu.
200	200	* On the End devices page, click on **+ Register end device**. Two registration options are available:
201	201
202		-==== 3.2.2.1 Using the LoRaWAN Device Repository ====
	228	+==== 3.2.2.2 Using the LoRaWAN Device Repository ====
203	203
204	204	* On the **Register end device** page:
205	205	** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
...	...	@@ -225,7 +225,7 @@
225	225
226	226	==== ====
227	227
228		-==== 3.2.2.2 Adding device manually ====
	254	+==== 3.2.2.3 Adding device manually ====
229	229
230	230	* On the **Register end device** page:
231	231	** Select the option **Enter end device specifies manually** under **Input method**.
...	...	@@ -240,7 +240,7 @@
240	240
241	241
242	242	* Register end device page continued...
243		-** 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'
	269	+** 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**//'
244	244	** In the **DevEUI** field, enter the **DevEUI**.
245	245	** In the **AppKey** field, enter the **AppKey**.
246	246	** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
...	...	@@ -256,24 +256,27 @@
256	256	[[image:lt-22222-device-overview.png||height="625" width="1000"]]
257	257
258	258
259		-==== 3.2.2.3 Joining ====
	285	+==== 3.2.2.4 Joining ====
260	260
261		-On the Device overview page, click on **Live data** tab. The Live data panel for your device will display.
	287	+On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
262	262
263		-Now power on your LT-22222-L. It will begin joining The Things Stack. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server. Once successfully joined, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**).
	289	+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.
264	264
265	265
266	266	[[image:lt-22222-join-network.png||height="625" width="1000"]]
267	267
268	268
269		-By default, you will receive an uplink data message from the device every 10 minutes.
	295	+==== 3.2.2.5 Uplinks ====
270	270
	297	+
	298	+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.
	299	+
271	271	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.
272	272
273	273	[[image:lt-22222-ul-payload-decoded.png]]
274	274
275	275
276		-If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **End devices** > **LT-22222-L** > **Payload formatters** > **Uplink**. Then  select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
	305	+If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **Applications > your application > End devices** > **your end device** > **Payload formatters** > **Uplink**. Then  select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
277	277
278	278	{{info}}
279	279	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.
...	...	@@ -282,6 +282,11 @@
282	282	[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
283	283
284	284
	314	+==== 3.2.2.6 Downlinks ====
	315	+
	316	+When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
	317	+
	318	+
285	285	== 3.3 Working Modes and Uplink Payload formats ==
286	286
287	287
...	...	@@ -557,13 +557,13 @@
557	557	)))
558	558
559	559	(((
560		-Other AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
	594	+AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
561	561	)))
562	562
563	563	(((
564	564	**In addition to that, below are the commands for AVI1 Counting:**
565	565
566		-(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI Count to 60)**
	600	+(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)**
567	567
568	568	(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
569	569
...	...	@@ -791,9 +791,9 @@
791	791
792	792	(% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
793	793
794		-(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
795		-|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
796		-|N/A|N/A|N/A|N/A|DI2_STATUS|DI2_FLAG|DI1_STATUS|DI1_FLAG
	828	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:674px" %)
	829	+|(% 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**
	830	+|(% 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
797	797
798	798	* Each bits shows which status has been triggered on this uplink.
799	799
...	...	@@ -855,10 +855,10 @@
855	855
856	856	(% style="color:#037691" %)**AT command**
857	857
858		-(% style="width:500px" %)
859		-|**Command**|AT+TDC<time>
	892	+(% border="2" style="width:500px" %)
	893	+|**Command**|AT+TDC=<time>
860	860	|**Response**|
861		-|**Parameters**|time : uplink interval is in milliseconds
	895	+|**Parameters**|**time** : uplink interval is in milliseconds
862	862	|**Example**|(((
863	863	AT+TDC=30000
864	864
...	...	@@ -867,14 +867,14 @@
867	867
868	868	(% style="color:#037691" %)**Downlink payload**
869	869
870		-(% style="width:500px" %)
	904	+(% border="2" style="width:500px" %)
871	871	|**Payload**|(((
872	872	<prefix><time>
873	873	)))
874	874	|**Parameters**|(((
875		-prefix : 0x01
	909	+**prefix** : 0x01
876	876
877		-time : uplink interval is in milliseconds, represented by 3  bytes in hexadecimal.
	911	+**time** : uplink interval is in milliseconds, represented by 3  bytes in hexadecimal.
878	878	)))
879	879	|**Example**|(((
880	880	01 **00 75 30**
...	...	@@ -892,11 +892,11 @@
892	892
893	893	(% style="color:#037691" %)**AT command**
894	894
895		-(% style="width:500px" %)
896		-|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE<working_mode>
	929	+(% border="2" style="width:500px" %)
	930	+|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE=<working_mode>
897	897	|(% style="width:97px" %)**Response**|(% style="width:413px" %)
898	898	|(% style="width:97px" %)**Parameters**|(% style="width:413px" %)(((
899		-working_mode :
	933	+**working_mode** :
900	900
901	901	1 = (Default mode/factory set):  2ACI + 2AVI + DI + DO + RO
902	902
...	...	@@ -919,12 +919,12 @@
919	919	(% class="wikigeneratedid" %)
920	920	(% style="color:#037691" %)**Downlink payload**
921	921
922		-(% style="width:500px" %)
	956	+(% border="2" style="width:500px" %)
923	923	|(% style="width:98px" %)**Payload**|(% style="width:400px" %)<prefix><working_mode>
924	924	|(% style="width:98px" %)**Parameters**|(% style="width:400px" %)(((
925		-prefix : 0x0A
	959	+**prefix** : 0x0A
926	926
927		-working_mode : Working mode, represented by 1 byte in hexadecimal.
	961	+**working_mode** : Working mode, represented by 1 byte in hexadecimal.
928	928	)))
929	929	|(% style="width:98px" %)**Example**|(% style="width:400px" %)(((
930	930	0A **02**
...	...	@@ -942,9 +942,9 @@
942	942
943	943	(% style="color:#037691" %)**Downlink payload**
944	944
945		-(% style="width:500px" %)
	979	+(% border="2" style="width:500px" %)
946	946	|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF
947		-|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)prefix : 0x08
	981	+|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08
948	948	|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
949	949	08 FF
950	950
...	...	@@ -957,11 +957,11 @@
957	957
958	958	(% style="color:#037691" %)**AT Command**
959	959
960		-(% style="width:500px" %)
	994	+(% border="2" style="width:500px" %)
961	961	|(% style="width:95px" %)**Command**|(% style="width:403px" %)AT+ADDMOD6=<enable/disable trigger_mode>
962	962	|(% style="width:95px" %)**Response**|(% style="width:403px" %)
963	963	|(% style="width:95px" %)**Parameters**|(% style="width:403px" %)(((
964		-enable/disable trigger_mode :
	998	+**enable/disable trigger_mode** :
965	965
966	966	1 = enable trigger mode
967	967
...	...	@@ -975,12 +975,12 @@
975	975
976	976	(% style="color:#037691" %)**Downlink payload**
977	977
978		-(% style="width:500px" %)
	1012	+(% border="2" style="width:500px" %)
979	979	|(% style="width:97px" %)**Payload**|(% style="width:401px" %)<prefix><enable/disable trigger_mode>
980	980	|(% style="width:97px" %)**Parameters**|(% style="width:401px" %)(((
981		-prefix : 0x0A 06
	1015	+**prefix** : 0x0A 06 (two bytes in hexadecimal)
982	982
983		-working mode : enable (1) or disable (0), represented by 1 byte in hexadecimal.
	1017	+**working mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
984	984	)))
985	985	|(% style="width:97px" %)**Example**|(% style="width:401px" %)(((
986	986	0A 06 **01**
...	...	@@ -998,9 +998,9 @@
998	998
999	999	(% style="color:#037691" %)**Downlink Payload**
1000	1000
1001		-(% style="width:500px" %)
	1035	+(% border="2" style="width:500px" %)
1002	1002	|(% style="width:95px" %)**Payload**|(% style="width:403px" %)<prefix>
1003		-|(% style="width:95px" %)**Parameters**|(% style="width:403px" %)prefix : AB 06
	1037	+|(% style="width:95px" %)**Parameters**|(% style="width:403px" %)**prefix **: AB 06 (two bytes in hexadecimal)
1004	1004	|(% style="width:95px" %)**Example**|(% style="width:403px" %)(((
1005	1005	AB 06
1006	1006
...	...	@@ -1007,29 +1007,29 @@
1007	1007	Uplinks the trigger settings.
1008	1008	)))
1009	1009
1010		-==== 3.4.2.6 Enable/Disable DI1/DI2 as a trigger ====
	1044	+==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ====
1011	1011
1012		-Enable or disable DI1/DI2 as a trigger.
	1046	+Enable or disable DI1/DI2/DI3 as a trigger.
1013	1013
1014	1014	(% style="color:#037691" %)**AT Command**
1015	1015
1016		-(% style="width:500px" %)
1017		-|(% style="width:98px" %)Command|(% style="width:400px" %)AT+DTRI=<DI1_trigger><DI2_trigger>
1018		-|(% style="width:98px" %)Response|(% style="width:400px" %)
1019		-|(% style="width:98px" %)Parameters|(% style="width:400px" %)(((
1020		-DI1_trigger:
	1050	+(% border="2" style="width:500px" %)
	1051	+|(% style="width:98px" %)**Command**|(% style="width:400px" %)AT+DTRI=<DI1_trigger>,<DI2_trigger>
	1052	+|(% style="width:98px" %)**Response**|(% style="width:400px" %)
	1053	+|(% style="width:98px" %)**Parameters**|(% style="width:400px" %)(((
	1054	+**DI1_trigger:**
1021	1021
1022	1022	1 = enable DI1 trigger
1023	1023
1024	1024	0 = disable DI1 trigger
1025	1025
1026		-DI2 _trigger
	1060	+**DI2 _trigger**
1027	1027
1028	1028	1 = enable DI2 trigger
1029	1029
1030	1030	0 = disable DI2 trigger
1031	1031	)))
1032		-|(% style="width:98px" %)Example|(% style="width:400px" %)(((
	1066	+|(% style="width:98px" %)**Example**|(% style="width:400px" %)(((
1033	1033	AT+DTRI=1,0
1034	1034
1035	1035	Enable DI1 trigger, disable DI2 trigger
...	...	@@ -1038,24 +1038,24 @@
1038	1038	(% class="wikigeneratedid" %)
1039	1039	(% style="color:#037691" %)**Downlink Payload**
1040	1040
1041		-(% style="width:500px" %)
1042		-|(% style="width:101px" %)Payload|(% style="width:397px" %)<prefix><DI1_trigger><DI2_trigger>
1043		-|(% style="width:101px" %)Parameters|(% style="width:397px" %)(((
1044		-prefix : AA 02
	1075	+(% border="2" style="width:500px" %)
	1076	+|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix><DI1_trigger><DI2_trigger>
	1077	+|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)(((
	1078	+**prefix :** AA 02 (two bytes in hexadecimal)
1045	1045
1046		-DI1_trigger:
	1080	+**DI1_trigger:**
1047	1047
1048	1048	1 = enable DI1 trigger, represented by 1 byte in hexadecimal.
1049	1049
1050	1050	0 = disable DI1 trigger, represented by 1 byte in hexadecimal.
1051	1051
1052		-DI2 _trigger
	1086	+**DI2 _trigger**
1053	1053
1054	1054	1 = enable DI2 trigger, represented by 1 byte in hexadecimal.
1055	1055
1056	1056	0 = disable DI2 trigger, represented by 1 byte in hexadecimal.
1057	1057	)))
1058		-|(% style="width:101px" %)Example|(% style="width:397px" %)(((
	1092	+|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
1059	1059	AA 02 **01 00**
1060	1060
1061	1061	Enable DI1 trigger, disable DI2 trigger
...	...	@@ -1065,142 +1065,239 @@
1065	1065
1066	1066	Sets DI1 or DI3 (for LT-33222-L) as a trigger.
1067	1067
1068		-* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG1=a,b**
1069	1069
1070		-(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
	1103	+(% style="color:#037691" %)**AT Command**
1071	1071
1072		-(% style="color:red" %)**b :** (%%)delay timing.
	1105	+(% border="2" style="width:500px" %)
	1106	+|(% style="width:101px" %)**Command**|(% style="width:397px" %)AT+TRIG1=<interrupt_mode>,<minimum_signal_duration>
	1107	+|(% style="width:101px" %)**Response**|(% style="width:397px" %)
	1108	+|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)(((
	1109	+**interrupt_mode** :  0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
1073	1073
1074		-**Example:** AT+TRIG1=1,100(set DI1 port to trigger on high level, valid signal is 100ms )
	1111	+**minimum_signal_duration** : the **minimum signal duration** required for the DI1 port to recognize a valid trigger.
	1112	+)))
	1113	+|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
	1114	+AT+TRIG1=1,100
1075	1075
	1116	+Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms.
	1117	+)))
1076	1076
1077		-* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 01 ):**
	1119	+(% class="wikigeneratedid" %)
	1120	+(% style="color:#037691" %)**Downlink Payload**
1078	1078
1079		-(% style="color:blue" %)**0x09 01 aa bb cc    ** (%%) ~/~/ same as AT+TRIG1=aa,0x(bb cc)
	1122	+(% border="2" style="width:500px" %)
	1123	+|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix><interrupt_mode><minimum_signal_duration>
	1124	+|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)(((
	1125	+**prefix** : 09 01 (hexadecimal)
1080	1080
	1127	+**interrupt_mode** : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal.
1081	1081
1082		-(% style="width:500px" %)
1083		-|(% style="width:101px" %)Command|(% style="width:397px" %)
1084		-|(% style="width:101px" %)Response|(% style="width:397px" %)
1085		-|(% style="width:101px" %)Parameters|(% style="width:397px" %)
1086		-|(% style="width:101px" %)Example|(% style="width:397px" %)
	1129	+**minimum_signal_duration** : in milliseconds, represented two bytes in hexadecimal.
	1130	+)))
	1131	+|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
	1132	+09 01 **01 00 64**
1087	1087
	1134	+Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms.
	1135	+)))
	1136	+
1088	1088	==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
1089	1089
1090	1090	Sets DI2 as a trigger.
1091	1091
1092		-* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b**
1093	1093
1094		-(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
	1142	+(% style="color:#037691" %)**AT Command**
1095	1095
1096		-(% style="color:red" %)**b :** (%%)delay timing.
	1144	+(% border="2" style="width:500px" %)
	1145	+|(% style="width:94px" %)**Command**|(% style="width:404px" %)AT+TRIG2=<interrupt_mode>,<minimum_signal_duration>
	1146	+|(% style="width:94px" %)**Response**|(% style="width:404px" %)
	1147	+|(% style="width:94px" %)**Parameters**|(% style="width:404px" %)(((
	1148	+**interrupt_mode **:  0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
1097	1097
1098		-**Example:** AT+TRIG2=0,100 (Set the DI1 port to trigger on a falling edge; the valid signal duration is 100 ms)
	1150	+**minimum_signal_duration** : the **minimum signal duration** required for the DI1 port to recognize a valid trigger.
	1151	+)))
	1152	+|(% style="width:94px" %)**Example**|(% style="width:404px" %)(((
	1153	+AT+TRIG2=0,100
1099	1099
	1155	+Set the DI1 port to trigger on a falling edge; the valid signal duration is 100 ms.
	1156	+)))
1100	1100
1101		-* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 02 ):**
	1158	+(% style="color:#037691" %)**Downlink Payload**
1102	1102
1103		-(% style="color:blue" %)**0x09 02 aa bb cc   ** (%%)~/~/ same as AT+TRIG2=aa,0x(bb cc)
	1160	+(% border="2" style="width:500px" %)
	1161	+|(% style="width:96px" %)**Payload**|(% style="width:402px" %)<prefix><interrupt_mode><minimum_signal_duration>
	1162	+|(% style="width:96px" %)**Parameters**|(% style="width:402px" %)(((
	1163	+**prefix** : 09 02 (hexadecimal)
1104	1104
	1165	+**interrupt_mode **: 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal.
1105	1105
	1167	+**minimum_signal_duration** : in milliseconds, represented two bytes in hexadecimal
	1168	+)))
	1169	+|(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64**
	1170	+
	1171	+==== ====
	1172	+
	1173	+==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
	1174	+
	1175	+Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
	1176	+
1106	1106	(% style="color:#037691" %)**AT Command**
1107	1107
1108		-(% style="width:500px" %)
1109		-|(% style="width:94px" %)Command|(% style="width:404px" %)AT+TRIG=<interrupt_mode><minimum_signal_duration>
1110		-|(% style="width:94px" %)Response|(% style="width:404px" %)
1111		-|(% style="width:94px" %)Parameters|(% style="width:404px" %)(((
1112		-interrupt_mode :  0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
	1179	+(% border="2" style="width:500px" %)
	1180	+|(% style="width:104px" %)**Command**|(% style="width:394px" %)(((
	1181	+AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH>
	1182	+)))
	1183	+|(% style="width:104px" %)**Response**|(% style="width:394px" %)
	1184	+|(% style="width:104px" %)**Parameters**|(% style="width:394px" %)(((
	1185	+**AC1_LIMIT_LOW** : lower limit of the current to be checked
1113	1113
1114		-minimum_signal_duration : the **minimum signal duration** required for the DI1 port to recognize a valid trigger.
	1187	+**AC1_LIMIT_HIGH **: higher limit of the current to be checked
	1188	+
	1189	+**AC2_LIMIT_HIGH **: lower limit of the current to be checked
	1190	+
	1191	+**AC2_LIMIT_LOW** : higher limit of the current to be checked
1115	1115	)))
1116		-|(% style="width:94px" %)Example|(% style="width:404px" %)(((
1117		-AT+TRIG2=0,100
	1193	+|(% style="width:104px" %)**Example**|(% style="width:394px" %)(((
	1194	+AT+ACLIM=10000,15000,0,0
1118	1118
1119		-Set the DI1 port to trigger on a falling edge; the valid signal duration is 100 ms.
	1196	+Triggers an uplink if AC1 current is lower than 10mA or higher than 15mA
1120	1120	)))
	1198	+|(% style="width:104px" %)Note|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1121	1121
1122	1122	(% style="color:#037691" %)**Downlink Payload**
1123	1123
1124		-(% style="width:500px" %)
1125		-|(% style="width:96px" %)Payload|(% style="width:402px" %)<prefix><interrupt_mode><minimum_signal_duration>
1126		-|(% style="width:96px" %)Parameters|(% style="width:402px" %)(((
1127		-prefix : 09 02
	1202	+(% border="2" style="width:500px" %)
	1203	+|(% style="width:104px" %)**Payload**|(% style="width:394px" %)<prefix><AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH>
	1204	+|(% style="width:104px" %)**Parameters**|(% style="width:394px" %)(((
	1205	+**prefix **: AA 01 (hexadecimal)
1128	1128
1129		-interrupt_mode : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal.
	1207	+**AC1_LIMIT_LOW** : lower limit of the current to be checked, two bytes in hexadecimal
1130	1130
1131		-<minimum_signal_duration>, represented two bytes in hexadecimal
	1209	+**AC1_LIMIT_HIGH **: higher limit of the current to be checked, two bytes in hexadecimal
	1210	+
	1211	+**AC2_LIMIT_HIGH **: lower limit of the current to be checked, two bytes in hexadecimal
	1212	+
	1213	+**AC2_LIMIT_LOW** : higher limit of the current to be checked, two bytes in hexadecimal
1132	1132	)))
1133		-|(% style="width:96px" %)Example|(% style="width:402px" %)09 02 **00 00 64**
	1215	+|(% style="width:104px" %)**Example**|(% style="width:394px" %)(((
	1216	+AA 01 **27** **10 3A** **98** 00 00 00 00
1134	1134
1135		-==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
	1218	+Triggers an uplink if AC1 current is lower than 10mA or higher than 15mA. Set all values to zero for AC2 limits because we are only checking AC1 limits.
	1219	+)))
	1220	+|(% style="width:104px" %)Note|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1136	1136
1137		-Sets the current trigger based on the AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
	1222	+==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
1138	1138
1139		-* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ACLIM**
	1224	+Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1140	1140
1141		-* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 01 )**
	1226	+(% style="color:#037691" %)**AT Command**
1142	1142
1143		-(% style="color:blue" %)**0x AA 01 aa bb cc dd ee ff gg hh        ** (%%) ~/~/ same as AT+ACLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
	1228	+(% border="2" style="width:500px" %)
	1229	+|(% style="width:104px" %)**Command**|(% style="width:387px" %)AT+AVLIM= AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH>
	1230	+|(% style="width:104px" %)**Response**|(% style="width:387px" %)
	1231	+|(% style="width:104px" %)**Parameters**|(% style="width:387px" %)(((
	1232	+**AC1_LIMIT_LOW** : lower limit of the current to be checked
1144	1144
	1234	+**AC1_LIMIT_HIGH **: higher limit of the current to be checked
1145	1145
1146		-(% style="width:500px" %)
1147		-|(% style="width:104px" %)Command|(% style="width:394px" %)AT+ACLIM
1148		-|(% style="width:104px" %)Response|(% style="width:394px" %)
1149		-|(% style="width:104px" %)Parameters|(% style="width:394px" %)-
1150		-|(% style="width:104px" %)Example|(% style="width:394px" %)AT+ACLIM
	1236	+**AC2_LIMIT_HIGH **: lower limit of the current to be checked
1151	1151
	1238	+**AC2_LIMIT_LOW** : higher limit of the current to be checked
	1239	+)))
	1240	+|(% style="width:104px" %)**Example**|(% style="width:387px" %)(((
	1241	+AT+AVLIM=3000,6000,0,2000
1152	1152
1153		-(% style="width:500px" %)
1154		-|(% style="width:104px" %)Payload|(% style="width:394px" %)<prefix>
1155		-|(% style="width:104px" %)Parameters|(% style="width:394px" %)prefix : AA 01
1156		-|(% style="width:104px" %)Example|(% style="width:394px" %)AA 01 aa bb cc dd ee ff gg hh
	1243	+Triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V
	1244	+)))
	1245	+|(% style="width:104px" %)**Note**|(% style="width:387px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1157	1157
1158		-==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
	1247	+(% style="color:#037691" %)**Downlink Payload**
1159	1159
1160		-Sets the current trigger based on the AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
	1249	+(% border="2" style="width:500px" %)
	1250	+|(% style="width:104px" %)**Payload**|(% style="width:394px" %)<prefix><AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH>
	1251	+|(% style="width:104px" %)**Parameters**|(% style="width:394px" %)(((
	1252	+**prefix **: AA 00 (hexadecimal)
1161	1161
1162		-* (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+AVLIM    **(%%)** See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]**
	1254	+**AV1_LIMIT_LOW** : lower limit of the voltage to be checked, two bytes in hexadecimal
1163	1163
1164		-* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 00 )**
	1256	+**AV1_LIMIT_HIGH **: higher limit of the voltage to be checked, two bytes in hexadecimal
1165	1165
1166		-(% style="color:blue" %)**0x AA 00 aa bb cc dd ee ff gg hh    ** (%%) ~/~/ same as AT+AVLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
	1258	+**AV2_LIMIT_HIGH **: lower limit of the voltage to be checked, two bytes in hexadecimal
1167	1167
	1260	+**AV2_LIMIT_LOW** : higher limit of the voltage to be checked, two bytes in hexadecimal
	1261	+)))
	1262	+|(% style="width:104px" %)**Example**|(% style="width:394px" %)(((
	1263	+AA 00 **0B B8 17 70 00 00 07 D0**
1168	1168
	1265	+Triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V.
	1266	+)))
	1267	+|(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
	1268	+
1169	1169	==== 3.4.2.11 Trigger – Set minimum interval ====
1170	1170
1171		-Sets AV and AC trigger minimum interval. Device won't response to the second trigger within this set time after the first trigger.
	1271	+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.
1172	1172
1173		-* (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+ATDC=5        ** ~/~/ (%%)Device won't response the second trigger within 5 minute after the first trigger.
	1273	+(% style="color:#037691" %)**AT Command**
1174	1174
1175		-* (% style="color:#037691" %)**Downlink Payload (prefix 0xAC )**
	1275	+(% border="2" style="width:500px" %)
	1276	+|(% style="width:113px" %)**Command**|(% style="width:385px" %)AT+ATDC=<time>
	1277	+|(% style="width:113px" %)**Response**|(% style="width:385px" %)
	1278	+|(% style="width:113px" %)**Parameters**|(% style="width:385px" %)(((
	1279	+**time** : in minutes
	1280	+)))
	1281	+|(% style="width:113px" %)**Example**|(% style="width:385px" %)(((
	1282	+AT+ATDC=5
1176	1176
1177		-(% style="color:blue" %)**0x AC aa bb   **(%%) ~/~/ same as AT+ATDC=0x(aa bb)   . Unit (min)
1178		-
1179		-(((
1180		-(% style="color:red" %)**Note: ATDC setting must be more than 5min**
	1284	+The device won't respond to the second trigger within 5 minutes after the first trigger.
1181	1181	)))
	1286	+|(% style="width:113px" %)Note|(% style="width:385px" %)(% style="color:red" %)**The time must be greater than 5 minutes.**
1182	1182
	1288	+(% style="color:#037691" %)**Downlink Payload**
1183	1183
	1290	+(% border="2" style="width:500px" %)
	1291	+|(% style="width:112px" %)**Payload**|(% style="width:386px" %)<prefix><time>
	1292	+|(% style="width:112px" %)**Parameters**|(% style="width:386px" %)(((
	1293	+**prefix** : AC (hexadecimal)
1184	1184
	1295	+**time **: in minutes (two bytes in hexadecimal)
	1296	+)))
	1297	+|(% style="width:112px" %)**Example**|(% style="width:386px" %)(((
	1298	+AC **00 05**
	1299	+
	1300	+The device won't respond to the second trigger within 5 minutes after the first trigger.
	1301	+)))
	1302	+|(% style="width:112px" %)Note|(% style="width:386px" %)(% style="color:red" %)**The time must be greater than 5 minutes.**
	1303	+
1185	1185	==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
1186	1186
1187	1187	Controls the digital outputs DO1, DO2, and DO3
1188	1188
1189		-* (% style="color:#037691" %)**AT Command**
	1308	+(% style="color:#037691" %)**AT Command**
1190	1190
1191		-There is no AT Command to control Digital Output
	1310	+There is no AT Command to control the Digital Output.
1192	1192
1193	1193
1194		-* (% style="color:#037691" %)**Downlink Payload (prefix 0x02)**
	1313	+(% style="color:#037691" %)**Downlink Payload**
1195	1195
1196		-(% style="color:blue" %)**0x02 aa bb cc     ** (%%)~/~/ Set DO1/DO2/DO3 output
	1315	+(% border="2" style="width:500px" %)
	1316	+|(% style="width:115px" %)**Payload**|(% style="width:383px" %)<prefix><DO1><DO2><DO3>
	1317	+|(% style="width:115px" %)**Parameters**|(% style="width:383px" %)(((
	1318	+**prefix** : 02 (hexadecimal)
1197	1197
1198		-(((
1199		-If payload = 0x02010001, while there is load between V+ and DOx, it means set DO1 to low, DO2 to high and DO3 to low.
	1320	+**DOI** : 01: Low,  00: High, 11: No action (1 byte in hex)
	1321	+
	1322	+**DO2** : 01: Low,  00: High, 11: No action (1 byte in hex)
	1323	+
	1324	+**DO3 **: 01: Low,  00: High, 11: No action (1 byte in hex)
1200	1200	)))
	1326	+|(% style="width:115px" %)**Examples**|(% style="width:383px" %)(((
	1327	+02 **01 00 01**
1201	1201
	1329	+If there is a load between V+ and DOx, it means DO1 is set to low, DO2 is set to high, and DO3 is set to low.
	1330	+
	1331	+**More examples:**
	1332	+
1202	1202	(((
1203		-01: Low,  00: High ,  11: No action
	1334	+01: Low,  00: High,  11: No action
1204	1204
1205	1205	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
1206	1206	|(% 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**
...	...	@@ -1210,15 +1210,18 @@
1210	1210	)))
1211	1211
1212	1212	(((
1213		-(% style="color:red" %)**Note: For LT-22222-L, there is no DO3, the last byte can use any value.**
	1344	+(((
	1345	+(% style="color:red" %)**Note: For the LT-22222-L, there is no DO3; the last byte can have any value.**
1214	1214	)))
1215	1215
1216	1216	(((
1217		-(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
	1349	+(% style="color:red" %)**The device will upload a packet if downlink code executes successfully.**
1218	1218	)))
	1351	+)))
	1352	+)))
1219	1219
	1354	+==== ====
1220	1220
1221		-
1222	1222	==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
1223	1223
1224	1224
...	...	@@ -1243,7 +1243,7 @@
1243	1243	00: DO pins will change to an inverter state after timeout
1244	1244
1245	1245
1246		-(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Ports status:
	1380	+(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
1247	1247
1248	1248	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1249	1249	|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
...	...	@@ -1251,7 +1251,7 @@
1251	1251	|0x00|DO1 set to high
1252	1252	|0x11|DO1 NO Action
1253	1253
1254		-(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Ports status:
	1388	+(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:
1255	1255
1256	1256	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1257	1257	|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
...	...	@@ -1259,7 +1259,7 @@
1259	1259	|0x00|DO2 set to high
1260	1260	|0x11|DO2 NO Action
1261	1261
1262		-(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Ports status:
	1396	+(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:
1263	1263
1264	1264	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1265	1265	|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
...	...	@@ -1267,16 +1267,16 @@
1267	1267	|0x00|DO3 set to high
1268	1268	|0x11|DO3 NO Action
1269	1269
1270		-(% style="color:#4f81bd" %)**Sixth and Seventh and Eighth and Ninth Byte**:(%%) Latching time. Unit: ms
	1404	+(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)
1271	1271
1272	1272
1273	1273	(% style="color:red" %)**Note: **
1274	1274
1275		- Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes
	1409	+ Since firmware v1.6.0, the latch time support 4 bytes and 2 bytes
1276	1276
1277		- Before Firmwre v1.6.0 the latch time only suport 2 bytes.
	1411	+ Before firmware v1.6.0, the latch time only supported 2 bytes.
1278	1278
1279		-(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
	1413	+(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1280	1280
1281	1281
1282	1282	**Example payload:**
...	...	@@ -1283,22 +1283,21 @@
1283	1283
1284	1284	**~1. A9 01 01 01 01 07 D0**
1285	1285
1286		-DO1 pin & DO2 pin & DO3 pin will be set to Low, last 2 seconds, then change back to original state.
	1420	+DO1 pin, DO2 pin, and DO3 pin will be set to low, last for 2 seconds, and then revert to their original state.
1287	1287
1288	1288	**2. A9 01 00 01 11 07 D0**
1289	1289
1290		-DO1 pin set high, DO2 pin set low, DO3 pin no action, last 2 seconds, then change back to original state.
	1424	+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.
1291	1291
1292	1292	**3. A9 00 00 00 00 07 D0**
1293	1293
1294		-DO1 pin & DO2 pin & DO3 pin will be set to high, last 2 seconds, then both change to low.
	1428	+DO1 pin, DO2 pin, and DO3 pin will be set to high, last for 2 seconds, and then all change to low.
1295	1295
1296	1296	**4. A9 00 11 01 00 07 D0**
1297	1297
1298		-DO1 pin no action, DO2 pin set low, DO3 pin set high, last 2 seconds, then DO1 pin no action, DO2 pin set high, DO3 pin set low
	1432	+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.
1299	1299
1300	1300
1301		-
1302	1302	==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
1303	1303
1304	1304
...	...	@@ -1313,11 +1313,11 @@
1313	1313
1314	1314
1315	1315	(((
1316		-If payload = 0x030100, it means set RO1 to close and RO2 to open.
	1449	+If payload is 0x030100, it means setting RO1 to close and RO2 to open.
1317	1317	)))
1318	1318
1319	1319	(((
1320		-00: Closed ,  01: Open , 11: No action
	1453	+00: Close ,  01: Open , 11: No action
1321	1321
1322	1322	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %)
1323	1323	|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**RO1**|(% style="background-color:#4f81bd; color:white" %)**RO2**
...	...	@@ -1334,9 +1334,9 @@
1334	1334	(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
1335	1335
1336	1336
1337		-
1338	1338	==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
1339	1339
	1472	+Controls the relay output time.
1340	1340
1341	1341	* (% style="color:#037691" %)**AT Command:**
1342	1342
...	...	@@ -1348,15 +1348,15 @@
1348	1348	(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Set RO1/RO2 relay with time control
1349	1349
1350	1350
1351		-This is to control the relay output time of relay. Include four bytes:
	1484	+This is to control the relay output time. It includes four bytes:
1352	1352
1353	1353	(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
1354	1354
1355	1355	(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
1356	1356
1357		-01: Relays will change back to original state after timeout.
	1490	+01: Relays will change back to their original state after timeout.
1358	1358
1359		-00: Relays will change to an inverter state after timeout
	1492	+00: Relays will change to the inverter state after timeout.
1360	1360
1361	1361
1362	1362	(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
...	...	@@ -1369,12 +1369,12 @@
1369	1369
1370	1370	(% style="color:red" %)**Note:**
1371	1371
1372		- Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes
	1505	+ Since firmware v1.6.0, the latch time supports both 4 bytes and 2 bytes.
1373	1373
1374		- Before Firmwre v1.6.0 the latch time only suport 2 bytes.
	1507	+ Before firmware v1.6.0, the latch time only supported 2 bytes.
1375	1375
1376	1376
1377		-(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
	1510	+(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1378	1378
1379	1379
1380	1380	**Example payload:**
...	...	@@ -1381,19 +1381,19 @@
1381	1381
1382	1382	**~1. 05 01 11 07 D0**
1383	1383
1384		-Relay1 and Relay 2 will be set to NC , last 2 seconds, then change back to original state.
	1517	+Relay1 and Relay2 will be set to NC, lasting 2 seconds, then revert to their original state
1385	1385
1386	1386	**2. 05 01 10 07 D0**
1387	1387
1388		-Relay1 will change to NC, Relay2 will change to NO, last 2 seconds, then both change back to original state.
	1521	+Relay1 will change to NC, Relay2 will change to NO, lasting 2 seconds, then both will revert to their original state.
1389	1389
1390	1390	**3. 05 00 01 07 D0**
1391	1391
1392		-Relay1 will change to NO, Relay2 will change to NC, last 2 seconds, then relay change to NC,Relay2 change to NO.
	1525	+Relay1 will change to NO, Relay2 will change to NC, lasting 2 seconds, then Relay1 will change to NC, and Relay2 will change to NO.
1393	1393
1394	1394	**4. 05 00 00 07 D0**
1395	1395
1396		-Relay 1 & relay2 will change to NO, last 2 seconds, then both change to NC.
	1529	+Relay1 and Relay2 will change to NO, lasting 2 seconds, then both will change to NC.
1397	1397
1398	1398
1399	1399
...	...	@@ -1400,7 +1400,7 @@
1400	1400	==== 3.4.2.16 Counting ~-~- Voltage threshold counting ====
1401	1401
1402	1402
1403		-When voltage exceed the threshold, count. Feature see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
	1536	+When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
1404	1404
1405	1405	* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX   ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
1406	1406
...	...	@@ -1409,15 +1409,76 @@
1409	1409	(% style="color:blue" %)**0xA5 aa bb cc   ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc
1410	1410
1411	1411
	1545	+(% style="color:#037691" %)**AT Command**
1412	1412
	1547	+(% border="2" style="width:500px" %)
	1548	+|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage><logic>
	1549	+|(% style="width:137px" %)**Response**|(% style="width:361px" %)
	1550	+|(% style="width:137px" %)**Parameters**|(% style="width:361px" %)(((
	1551	+**voltage** : voltage threshold in mV
	1552	+
	1553	+**logic**:
	1554	+
	1555	+0 : lower than
	1556	+
	1557	+1: higher than
	1558	+
	1559	+if you leave logic parameter blank, it is considered 0
	1560	+)))
	1561	+|(% style="width:137px" %)**Examples**|(% style="width:361px" %)(((
	1562	+AT+VOLMAX=20000
	1563	+
	1564	+If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
	1565	+
	1566	+AT+VOLMAX=20000,0
	1567	+
	1568	+If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1
	1569	+
	1570	+AT+VOLMAX=20000,1
	1571	+
	1572	+If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
	1573	+)))
	1574	+
	1575	+(% style="color:#037691" %)**Downlink Payload**
	1576	+
	1577	+(% border="2" style="width:500px" %)
	1578	+|(% style="width:140px" %)**Payload**|(% style="width:358px" %)<prefix><voltage><logic>
	1579	+|(% style="width:140px" %)**Parameters**|(% style="width:358px" %)(((
	1580	+**prefix** : A5 (hex)
	1581	+
	1582	+**voltage** : voltage threshold in mV (2 bytes in hex)
	1583	+
	1584	+**logic**: (1 byte in hexadecimal)
	1585	+
	1586	+0 : lower than
	1587	+
	1588	+1: higher than
	1589	+
	1590	+if you leave logic parameter blank, it is considered 1 (higher than)
	1591	+)))
	1592	+|(% style="width:140px" %)**Example**|(% style="width:358px" %)(((
	1593	+A5 **4E 20**
	1594	+
	1595	+If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
	1596	+
	1597	+A5 **4E 20 00**
	1598	+
	1599	+If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1
	1600	+
	1601	+A5 **4E 20 01**
	1602	+
	1603	+If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
	1604	+)))
	1605	+
1413	1413	==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ====
1414	1414
	1608	+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.
1415	1415
1416	1416	* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) **
1417	1417
1418	1418	(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count
1419	1419
1420		-(% style="color:red" %)**bb cc dd ee: **(%%)number to be set
	1614	+(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set
1421	1421
1422	1422
1423	1423	* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):**
...	...	@@ -1425,12 +1425,55 @@
1425	1425	(% style="color:blue" %)**0x A8 aa bb cc dd ee     ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee)
1426	1426
1427	1427
	1622	+(% style="color:#037691" %)**AT Command**
1428	1428
1429		-==== 3.4.2.18 Counting ~-~- Clear Counting ====
	1624	+(% border="2" style="width:500px" %)
	1625	+|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter><number>
	1626	+|(% style="width:134px" %)**Response**|(% style="width:364px" %)
	1627	+|(% style="width:134px" %)**Parameters**|(% style="width:364px" %)(((
	1628	+**counting_parameter** :
1430	1430
	1630	+1: COUNT1
1431	1431
1432		-Clear counting for counting mode
	1632	+2: COUNT2
1433	1433
	1634	+3: AVI1 Count
	1635	+
	1636	+**number** : Start number
	1637	+)))
	1638	+|(% style="width:134px" %)**Example**|(% style="width:364px" %)(((
	1639	+AT+SETCNT=1,10
	1640	+
	1641	+Sets the COUNT1 to 10.
	1642	+)))
	1643	+
	1644	+(% style="color:#037691" %)**Downlink Payload**
	1645	+
	1646	+(% border="2" style="width:500px" %)
	1647	+|(% style="width:135px" %)**Payload**|(% style="width:363px" %)<prefix><counting_parameter><number>
	1648	+|(% style="width:135px" %)**Parameters**|(% style="width:363px" %)(((
	1649	+prefix : A8 (hex)
	1650	+
	1651	+**counting_parameter** : (1 byte in hexadecimal)
	1652	+
	1653	+1: COUNT1
	1654	+
	1655	+2: COUNT2
	1656	+
	1657	+3: AVI1 Count
	1658	+
	1659	+**number** : Start number, 4 bytes in hexadecimal
	1660	+)))
	1661	+|(% style="width:135px" %)**Example**|(% style="width:363px" %)(((
	1662	+A8 **01 00 00 00 0A**
	1663	+
	1664	+Sets the COUNT1 to 10.
	1665	+)))
	1666	+
	1667	+==== 3.4.2.18 Counting ~-~- Clear Counting ====
	1668	+
	1669	+This command clears the counting in counting mode.
	1670	+
1434	1434	* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT         **(%%) ~/~/ clear all counting
1435	1435
1436	1436	* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):**
...	...	@@ -1437,14 +1437,30 @@
1437	1437
1438	1438	(% style="color:blue" %)**0x A6 01    ** (%%)~/~/ clear all counting
1439	1439
	1677	+(% style="color:#037691" %)**AT Command**
1440	1440
	1679	+(% border="2" style="width:500px" %)
	1680	+|(% style="width:142px" %)**Command**|(% style="width:356px" %)AT+CLRCOUNT
	1681	+|(% style="width:142px" %)**Response**|(% style="width:356px" %)-
1441	1441
	1683	+(% style="color:#037691" %)**Downlink Payload**
	1684	+
	1685	+(% border="2" style="width:500px" %)
	1686	+|(% style="width:141px" %)**Payload**|(% style="width:357px" %)<prefix><clear?>
	1687	+|(% style="width:141px" %)**Parameters**|(% style="width:357px" %)(((
	1688	+prefix : A6 (hex)
	1689	+
	1690	+clear? : 01 (hex)
	1691	+)))
	1692	+|(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
	1693	+
1442	1442	==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1443	1443
	1696	+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.
1444	1444
1445	1445	* (% style="color:#037691" %)**AT Command:**
1446	1446
1447		-(% style="color:blue" %)**AT+COUTIME=60  **(%%)~/~/ Set save time to 60 seconds. Device will save the counting result in internal flash every 60 seconds. (min value: 30)
	1700	+(% 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)
1448	1448
1449	1449
1450	1450	* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):**
...	...	@@ -1452,19 +1452,46 @@
1452	1452	(% style="color:blue" %)**0x A7 aa bb cc     ** (%%)~/~/ same as AT+COUTIME =aa bb cc,
1453	1453
1454	1454	(((
1455		-range: aa bb cc:0 to 16777215,  (unit:second)
	1708	+Range: aa bb cc:0 to 16777215,  (unit: seconds)
1456	1456	)))
1457	1457
1458	1458
	1712	+(% style="color:#037691" %)**AT Command**
1459	1459
	1714	+(% border="2" style="width:500px" %)
	1715	+|(% style="width:124px" %)**Command**|(% style="width:374px" %)AT+COUTIME=<time>
	1716	+|(% style="width:124px" %)**Response**|(% style="width:374px" %)
	1717	+|(% style="width:124px" %)**Parameters**|(% style="width:374px" %)time : seconds (0 to 16777215)
	1718	+|(% style="width:124px" %)**Example**|(% style="width:374px" %)(((
	1719	+AT+COUTIME=60
	1720	+
	1721	+Sets the device to save its counting results to the memory every 60 seconds.
	1722	+)))
	1723	+
	1724	+(% style="color:#037691" %)**Downlink Payload**
	1725	+
	1726	+(% border="2" style="width:500px" %)
	1727	+|(% style="width:123px" %)**Payload**|(% style="width:375px" %)<prefix><time>
	1728	+|(% style="width:123px" %)**Parameters**|(% style="width:375px" %)(((
	1729	+prefix : A7
	1730	+
	1731	+time : seconds, 3 bytes in hexadecimal
	1732	+)))
	1733	+|(% style="width:123px" %)**Example**|(% style="width:375px" %)(((
	1734	+A7 **00 00 3C**
	1735	+
	1736	+Sets the device to save its counting results to the memory every 60 seconds.
	1737	+)))
	1738	+
1460	1460	==== 3.4.2.20 Reset save RO DO state ====
1461	1461
	1741	+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.
1462	1462
1463	1463	* (% style="color:#037691" %)**AT Command:**
1464	1464
1465	1465	(% style="color:blue" %)**AT+RODORESET=1    **(%%)~/~/ RODO will close when the device joining the network. (default)
1466	1466
1467		-(% 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 is not changed when it is reconnected to the network.
	1747	+(% 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.
1468	1468
1469	1469
1470	1470	* (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):**
...	...	@@ -1472,9 +1472,50 @@
1472	1472	(% style="color:blue" %)**0x AD aa      ** (%%)~/~/ same as AT+RODORET =aa
1473	1473
1474	1474
	1755	+(% border="2" style="width:500px" %)
	1756	+|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state>
	1757	+|(% style="width:127px" %)**Response**|(% style="width:371px" %)
	1758	+|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
	1759	+**state** :
1475	1475
	1761	+**0** : RODO will close when the device joins the network. (default)
	1762	+
	1763	+**1**: After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network.
	1764	+)))
	1765	+|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
	1766	+(% style="color:blue" %)**AT+RODORESET=1 **
	1767	+
	1768	+RODO will close when the device joins the network. (default)
	1769	+
	1770	+(% style="color:blue" %)**AT+RODORESET=0 **
	1771	+
	1772	+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.
	1773	+)))
	1774	+
	1775	+(% border="2" style="width:500px" %)
	1776	+|(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state>
	1777	+|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
	1778	+**prefix** : AD
	1779	+
	1780	+**state** :
	1781	+
	1782	+**0** : RODO will close when the device joins the network. (default), represents as 1 byte in hexadecimal.
	1783	+
	1784	+**1**: After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network. - represents as 1 byte in hexadecimal
	1785	+)))
	1786	+|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
	1787	+AD **01**
	1788	+
	1789	+RODO will close when the device joins the network. (default)
	1790	+
	1791	+AD **00**
	1792	+
	1793	+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.
	1794	+)))
	1795	+
1476	1476	==== 3.4.2.21 Encrypted payload ====
1477	1477
	1798	+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.
1478	1478
1479	1479	* (% style="color:#037691" %)**AT Command:**
1480	1480
...	...	@@ -1483,21 +1483,67 @@
1483	1483	(% style="color:blue" %)**AT+DECRYPT=0    **(%%)~/~/  Encrypt when uploading payload (default)
1484	1484
1485	1485
	1807	+(% border="2" style="width:500px" %)
	1808	+|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state>
	1809	+|(% style="width:127px" %)**Response**|(% style="width:371px" %)
	1810	+|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
	1811	+state :
1486	1486
	1813	+1 : The payload is uploaded without encryption
	1814	+
	1815	+0 : The payload is encrypted when uploaded (default)
	1816	+)))
	1817	+|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
	1818	+AT+DECRYPT=1
	1819	+
	1820	+The payload is uploaded without encryption
	1821	+
	1822	+AT+DECRYPT=0
	1823	+
	1824	+The payload is encrypted when uploaded (default)
	1825	+)))
	1826	+
	1827	+There is no downlink payload for this configuration.
	1828	+
	1829	+
1487	1487	==== 3.4.2.22 Get sensor value ====
1488	1488
	1832	+This command allows you to retrieve and optionally uplink sensor readings through the serial port.
1489	1489
1490	1490	* (% style="color:#037691" %)**AT Command:**
1491	1491
1492		-(% style="color:blue" %)**AT+GETSENSORVALUE=0    **(%%)~/~/ The serial port gets the reading of the current sensor
	1836	+(% style="color:blue" %)**AT+GETSENSORVALUE=0    **(%%)~/~/ The serial port retrieves the reading of the current sensor.
1493	1493
1494		-(% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port gets the current sensor reading and uploads it.
	1838	+(% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it.
1495	1495
1496	1496
	1841	+(% border="2" style="width:500px" %)
	1842	+|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state>
	1843	+|(% style="width:127px" %)**Response**|(% style="width:371px" %)
	1844	+|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
	1845	+**state** :
1497	1497
1498		-==== 3.4.2.23 Resets the downlink packet count ====
	1847	+**0 **: Retrieves the current sensor reading via the serial port.
1499	1499
	1849	+**1 **: Retrieves and uploads the current sensor reading via the serial port.
	1850	+)))
	1851	+|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
	1852	+AT+GETSENSORVALUE=0
1500	1500
	1854	+Retrieves the current sensor reading via the serial port.
	1855	+
	1856	+AT+GETSENSORVALUE=1
	1857	+
	1858	+Retrieves and uplinks the current sensor reading via the serial port.
	1859	+)))
	1860	+
	1861	+There is no downlink payload for this configuration.
	1862	+
	1863	+
	1864	+==== 3.4.2.23 Resetting the downlink packet count ====
	1865	+
	1866	+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.
	1867	+
1501	1501	* (% style="color:#037691" %)**AT Command:**
1502	1502
1503	1503	(% 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)
...	...	@@ -1505,10 +1505,37 @@
1505	1505	(% 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.
1506	1506
1507	1507
	1875	+(% border="2" style="width:500px" %)
	1876	+|(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state>
	1877	+|(% style="width:130px" %)**Response**|(% style="width:368px" %)(((
	1878	+
	1879	+)))
	1880	+|(% style="width:130px" %)**Parameters**|(% style="width:368px" %)(((
	1881	+**state **:
1508	1508
	1883	+**0** : When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node stops receiving further downlink packets (default).
	1884	+
	1885	+
	1886	+**1** : When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node resets its downlink packet count to match the server's, ensuring consistency.
	1887	+)))
	1888	+|(% style="width:130px" %)**Example**|(% style="width:368px" %)(((
	1889	+AT+DISFCNTCHECK=0
	1890	+
	1891	+When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node stops receiving further downlink packets (default).
	1892	+
	1893	+AT+DISFCNTCHECK=1
	1894	+
	1895	+When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node resets its downlink packet count to match the server's, ensuring consistency.
	1896	+)))
	1897	+
	1898	+There is no downlink payload for this configuration.
	1899	+
	1900	+
1509	1509	==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ====
1510	1510
1511	1511
	1904	+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.
	1905	+
1512	1512	* (% style="color:#037691" %)**AT Command:**
1513	1513
1514	1514	(% 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)
...	...	@@ -1520,10 +1520,50 @@
1520	1520
1521	1521	(% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set  the DISMACANS=1
1522	1522
	1917	+(% style="color:#037691" %)**AT Command**
1523	1523
	1919	+(% border="2" style="width:500px" %)
	1920	+|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DISMACANS=<state>
	1921	+|(% style="width:127px" %)**Response**|(% style="width:371px" %)
	1922	+|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
	1923	+**state** :
1524	1524
	1925	+**0** : When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default)
	1926	+
	1927	+**1** : When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload.
	1928	+)))
	1929	+|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
	1930	+AT+DISMACANS=0
	1931	+
	1932	+When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default)
	1933	+
	1934	+AT+DISMACANS=1
	1935	+
	1936	+When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload.
	1937	+)))
	1938	+
	1939	+(% style="color:#037691" %)**Downlink Payload**
	1940	+
	1941	+(% border="2" style="width:500px" %)
	1942	+|(% style="width:126px" %)**Payload**|(% style="width:372px" %)<prefix><state>
	1943	+|(% style="width:126px" %)**Parameters**|(% style="width:372px" %)(((
	1944	+**prefix** : 21
	1945	+
	1946	+**state** : (2 bytes in hexadecimal)
	1947	+
	1948	+**0** : When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default)
	1949	+
	1950	+**1 **: When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload.
	1951	+)))
	1952	+|(% style="width:126px" %)**Example**|(% style="width:372px" %)(((
	1953	+21 **00 01**
	1954	+
	1955	+Set DISMACANS=1
	1956	+)))
	1957	+
1525	1525	==== 3.4.2.25 Copy downlink to uplink ====
1526	1526
	1960	+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.
1527	1527
1528	1528	* (% style="color:#037691" %)**AT Command**(%%)**:**
1529	1529
...	...	@@ -1536,8 +1536,22 @@
1536	1536
1537	1537	For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
1538	1538
	1973	+(% border="2" style="width:500px" %)
	1974	+|(% style="width:122px" %)**Command**|(% style="width:376px" %)(((
	1975	+AT+RPL=5
1539	1539
	1977	+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.
	1978	+)))
	1979	+|(% style="width:122px" %)**Example**|(% style="width:376px" %)(((
	1980	+Downlink:
1540	1540
	1982	+01 00 02 58
	1983	+
	1984	+Uplink:
	1985	+
	1986	+01 01 00 02 58
	1987	+)))
	1988	+
1541	1541	[[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"]]
1542	1542
1543	1543	For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
...	...	@@ -1544,14 +1544,16 @@
1544	1544
1545	1545
1546	1546
1547		-==== 3.4.2.26 Query version number and frequency band 、TDC ====
	1995	+==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
1548	1548
	1997	+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.
1549	1549
1550	1550	* (((
1551	1551	(% style="color:#037691" %)**Downlink Payload**(%%)**:**
1552	1552
1553		-(% style="color:blue" %)**26 01  ** (%%) ~/~/  Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.
	2002	+(% 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.
1554	1554
	2004	+
1555	1555
1556	1556	)))
1557	1557
...	...	@@ -1581,6 +1581,8 @@
1581	1581
1582	1582	=== 3.5.2 Configuring ThingsEye.io ===
1583	1583
	2034	+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.
	2035	+
1584	1584	* Login to your [[ThingsEye.io >>https://thingseye.io]]account.
1585	1585	* Under the **Integrations center**, click **Integrations**.
1586	1586	* Click the **Add integration** button (the button with the **+** symbol).
...	...	@@ -1629,7 +1629,7 @@
1629	1629
1630	1630	* Choose **Region** from the **Host type**.
1631	1631	* Enter the **cluster** of your **The Things Stack** in the **Region** textbox. You can find the cluster in the url (e.g., https:~/~/**eu1**.cloud.thethings.network/...).
1632		-* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The **username **and **password **can be found on the MQTT integration page of your The Things Stack account (see Configuring The Things Stack).
	2084	+* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The **username **and **password **can be found on the MQTT integration page of your The Things Stack account (see **3.5.1 Configuring The Things Stack**).
1633	1633	* Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
1634	1634
1635	1635	[[image:message-1.png]]
...	...	@@ -1640,7 +1640,7 @@
1640	1640	[[image:thingseye-io-step-5.png||height="625" width="1000"]]
1641	1641
1642	1642
1643		-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.
	2095	+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.
1644	1644
1645	1645
1646	1646	[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
...	...	@@ -1656,7 +1656,7 @@
1656	1656	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.
1657	1657
1658	1658	{{info}}
1659		-See also ThingsEye documentation.
	2111	+See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
1660	1660	{{/info}}
1661	1661
1662	1662	==== **3.5.2.2 Viewing events** ====
...	...	@@ -1669,7 +1669,7 @@
1669	1669	[[image:thingseye-events.png||height="686" width="1000"]]
1670	1670
1671	1671
1672		-* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
	2124	+* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
1673	1673
1674	1674	[[image:thingseye-json.png||width="1000"]]
1675	1675
...	...	@@ -1679,9 +1679,14 @@
1679	1679	If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
1680	1680
1681	1681
	2134	+==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
	2135	+
	2136	+This will be added soon.
	2137	+
	2138	+
1682	1682	== 3.6 Interface Details ==
1683	1683
1684		-=== 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active ) ===
	2141	+=== 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
1685	1685
1686	1686
1687	1687	Supports NPN-type sensors.

dragino-lorawan-nw-lt-22222-n.jpg

Author

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

Size

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

Content

dragino-ttn-te.jpg

Author

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

Size

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

Content

lorawan-nw.jpg

Author

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

Size

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

Content