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, 8 removed)
  • integration-details.png
  • lt-22222-device-overview.png
  • lt-22222-join-network.png
  • lt-22222-ul-payload-decoded.png
  • lt-22222-ul-payload-fmt.png
  • message-1.png
  • thingseye.io_integrationsCenter_integrations-2.png
  • thingseye.io_integrationsCenter_integrations.png

Details

Page properties

Content

...	...	@@ -17,7 +17,7 @@
17	17
18	18
19	19
20		-= 1. Introduction =
	20	+= 1.Introduction =
21	21
22	22	== 1.1 What is the LT-22222-L I/O Controller? ==
23	23
...	...	@@ -33,6 +33,8 @@
33	33	With the LT-22222-L I/O Controller, users can transmit data over ultra-long distances with low power consumption using LoRa, a spread-spectrum modulation technique derived from chirp spread spectrum (CSS) technology that operates on license-free ISM bands.
34	34	)))
35	35
	36	+> The LT Series I/O Controllers are designed for easy, low-cost installation on LoRaWAN networks.
	37	+
36	36	(((
37	37	You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways:
38	38
...	...	@@ -40,7 +40,7 @@
40	40	* 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.
41	41	* Setup your own private LoRaWAN network.
42	42
43		-> You can use a LoRaWAN gateway, such as the Dragino LG308, to expand or create LoRaWAN coverage in your area.
	45	+> You can use the Dragino LG308 gateway to expand or create LoRaWAN coverage in your area.
44	44	)))
45	45
46	46	(((
...	...	@@ -57,16 +57,16 @@
57	57	* SX1276/78 Wireless Chip
58	58	* Power Consumption:
59	59	** Idle: 4mA@12v
60		-** 20dB Transmit: 34mA@12V
61		-* Operating Temperature: -40 ~~ 85 Degrees, No Dew
	62	+** 20dB Transmit: 34mA@12v
	63	+* Operating Temperature: -40 ~~ 85 Degree, No Dew
62	62
63	63	(% style="color:#037691" %)**Interface for Model: LT22222-L:**
64	64
65	65	* 2 x Digital dual direction Input (Detect High/Low signal, Max: 50v, or 220v with optional external resistor)
66		-* 2 x Digital Output (NPN output. Max pull-up voltage 36V,450mA)
	68	+* 2 x Digital Output (NPN output. Max pull up voltage 36V,450mA)
67	67	* 2 x Relay Output (5A@250VAC / 30VDC)
68	68	* 2 x 0~~20mA Analog Input (res:0.01mA)
69		-* 2 x 0~~30V Analog Input (res:0.01V)
	71	+* 2 x 0~~30V Analog Input (res:0.01v)
70	70	* Power Input 7~~ 24V DC.
71	71
72	72	(% style="color:#037691" %)**LoRa Spec:**
...	...	@@ -76,7 +76,7 @@
76	76	** Band 2 (LF): 410 ~~ 528 Mhz
77	77	* 168 dB maximum link budget.
78	78	* +20 dBm - 100 mW constant RF output vs.
79		-* +14 dBm high-efficiency PA.
	81	+* +14 dBm high efficiency PA.
80	80	* Programmable bit rate up to 300 kbps.
81	81	* High sensitivity: down to -148 dBm.
82	82	* Bullet-proof front end: IIP3 = -12.5 dBm.
...	...	@@ -96,7 +96,7 @@
96	96	* Optional Customized LoRa Protocol
97	97	* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
98	98	* AT Commands to change parameters
99		-* Remotely configure parameters via LoRaWAN Downlink
	101	+* Remote configure parameters via LoRa Downlink
100	100	* Firmware upgradable via program port
101	101	* Counting
102	102
...	...	@@ -134,10 +134,10 @@
134	134
135	135	* 1 x LT-22222-L I/O Controller
136	136	* 1 x LoRaWAN antenna matched to the frequency of the LT-22222-L
137		-* 1 x bracket for DIN rail mounting
	139	+* 1 x bracket for wall mounting
138	138	* 1 x programming cable
139	139
140		-Attach the LoRaWAN antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper terminal block. Secure the antenna by tightening it clockwise.
	142	+Attach the LoRaWAN antenna to the connector labeled **ANT** (located on the top right side of the device, next to the upper terminal block). Secure the antenna by tightening it clockwise.
141	141
142	142	== 2.2 Terminals ==
143	143
...	...	@@ -167,9 +167,9 @@
167	167	|(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
168	168	|(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
169	169
170		-== 2.3 Powering the LT-22222-L ==
	172	+== 2.3 Powering ==
171	171
172		-The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect the 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 the power supply’s positive wire to the VIN screw terminal and the negative wire to the GND screw terminal. The power indicator (PWR) LED will turn on when the device is properly powered.
173	173
174	174
175	175	[[image:1653297104069-180.png]]
...	...	@@ -179,15 +179,15 @@
179	179
180	180	== 3.1 How does it work? ==
181	181
182		-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.
	184	+The LT-22222-L is configured to operate in LoRaWAN Class C mode by default. It supports OTAA (Over-the-Air Activation), which is 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.
183	183
184		-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 LE**D 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.
	186	+For LT-22222-L, the LED will show the Join status: After power on (% style="color:green" %)**TX LED**(%%) will fast blink 5 times, LT-22222-L will enter working mode and start to JOIN LoRaWAN network. (% style="color:green" %)**TX LED**(%%) will be on for 5 seconds after joined in network. When there is message from server, the RX LED will be on for 1 second.
185	185
186	186	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.
187	187
188	188	== 3.2 Registering with a LoRaWAN network server ==
189	189
190		-The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
	192	+The diagram below shows how the LT-22222-L connects to a typical LoRaWAN network.
191	191
192	192	[[image:image-20220523172350-1.png||height="266" width="864"]]
193	193
...	...	@@ -203,24 +203,20 @@
203	203
204	204	* Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account.
205	205	* Create an application if you do not have one yet.
206		-* Register LT-22222-L with that application. Two registration options are available:
	208	+* Register LT-22222-L with that application. Two registration options available:
207	207
208		-(% class="wikigeneratedid" %)
209		-==== ====
	210	+==== Using the LoRaWAN Device Repository: ====
210	210
211		-==== 3.2.2.1 Using the LoRaWAN Device Repository ====
212		-
213	213	* Go to your application and click on the **Register end device** button.
214	214	* On the **Register end device** page:
215	215	** Select the option **Select the end device in the LoRaWAN Device Repository**.
216	216	** Choose the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)**.
217		-** Select the **Frequency plan** that matches your device.
	216	+** Select the **Frequency plan** that matches with your device.
218	218
219	219	[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
220	220
221		-
222		-* Page continued...
223		-** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
	220	+*
	221	+** Enter the **AppEUI** in the **JoinEUI** field and click **Confirm** button.
224	224	** Enter the **DevEUI** in the **DevEUI** field.
225	225	** Enter the **AppKey** in the **AppKey** field.
226	226	** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
...	...	@@ -228,69 +228,43 @@
228	228
229	229	[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
230	230
231		-(% class="wikigeneratedid" %)
232		-==== ====
	229	+==== Entering device information manually: ====
233	233
234		-==== 3.2.2.2 Entering device information manually ====
235		-
236	236	* On the **Register end device** page:
237	237	** Select the **Enter end device specifies manually** option as the input method.
238		-** Select the **Frequency plan** that matches your device.
	233	+** Select the **Frequency plan** that matches with your device.
239	239	** Select the **LoRaWAN version**.
240	240	** Select the **Regional Parameters version**.
241	241	** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the section.
242		-** Select **Over the air activation (OTAA)** option under the **Activation mode**
	237	+** Select **Over the air activation (OTAA)** option under **Activation mode**
243	243	** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities**.
244	244
245	245	[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
246	246
247	247
248		-* Page continued...
249		-** Enter **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
250		-** Enter **DevEUI** in the **DevEUI** field.
251		-** Enter **AppKey** in the **AppKey** field.
252		-** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
253		-** Under **After registration**, select the **View registered end device** option.
254		-** Click the **Register end device** button.
	243	+* Enter **AppEUI** in the **JoinEUI** field and click **Confirm** button.
	244	+* Enter **DevEUI** in the **DevEUI** field.
	245	+* Enter **AppKey** in the **AppKey** field.
	246	+* In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
	247	+* Under **After registration**, select the **View registered end device** option.
255	255
256	256	[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
257	257
258	258
259		-You will be navigated to the **Device overview** page.
	252	+==== Joining ====
260	260
	254	+Click on **Live Data** in the left navigation. Then, power on the device, and it will join The Things Stack Sandbox. You can see the join request, join accept, followed by uplink messages form the device showing in the Live Data panel.
261	261
262		-[[image:lt-22222-device-overview.png||height="625" width="1000"]]
	256	+[[image:1653298044601-602.png||height="405" width="709"]]
263	263
264	264
265		-==== 3.2.2.3 Joining ====
	259	+== 3.3 Uplink Payload formats ==
266	266
267		-Click on **Live data** in the left navigation. The Live data panel for your application will display.
268	268
269		-Power on your LT-22222-L. It will begin joining The Things Stack LoRaWAN network server. 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**).
	262	+The LT-22222-L has 5 working modes. It also has an interrupt/trigger mode for different type applications that can be used together with all the working modes as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands.
270	270
	264	+* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2 x ACI + 2AVI + DI + DO + RO
271	271
272		-[[image:lt-22222-join-network.png||height="625" width="1000"]]
273		-
274		-
275		-By default, you will receive an uplink data message every 10 minutes.
276		-
277		-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.
278		-
279		-[[image:lt-22222-ul-payload-decoded.png]]
280		-
281		-
282		-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.
283		-
284		-[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
285		-
286		-
287		-== 3.3 Work Modes and their Uplink Payload formats ==
288		-
289		-
290		-The LT-22222-L has 5 **work modes**. It also has an interrupt/trigger mode for different types of applications that can be used together with any work mode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands.
291		-
292		-* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO
293		-
294	294	* (% style="color:blue" %)**MOD2**(%%): Double DI Counting + DO + RO
295	295
296	296	* (% style="color:blue" %)**MOD3**(%%): Single DI Counting + 2 x ACI + DO + RO
...	...	@@ -301,16 +301,12 @@
301	301
302	302	* (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5
303	303
304		-
305		-The uplink messages are sent over LoRaWAN FPort 2. By default, an uplink message is sent every 10 minutes.
306		-
307	307	=== 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
308	308
	278	+
309	309	(((
310		-This is the default mode.
	280	+The uplink payload is 11 bytes long. Uplink packets are sent over LoRaWAN FPort=2. By default, one uplink is sent every 10 minutes. (% style="display:none" %)
311	311
312		-The uplink payload is 11 bytes long. (% style="display:none" wfd-invisible="true" %)
313		-
314	314	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
315	315	|(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**
316	316	|Value|(((
...	...	@@ -321,13 +321,13 @@
321	321	ACI1 Current
322	322	)))|(((
323	323	ACI2 Current
324		-)))|**DIDORO***|(((
	292	+)))|DIDORO*|(((
325	325	Reserve
326	326	)))|MOD
327	327	)))
328	328
329	329	(((
330		-(% style="color:#4f81bd" %)*** DIDORO**(%%) is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, and its size is1 byte long as shown below.
	298	+(% style="color:#4f81bd" %)*** DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below.
331	331
332	332	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
333	333	|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
...	...	@@ -334,9 +334,9 @@
334	334	|RO1|RO2|--DI3--|DI2|DI1|--DO3--|DO2|DO1
335	335	)))
336	336
337		-* RO is for the relay. ROx=1: CLOSED, ROx=0 always OPEN.
338		-* DI is for digital input. DIx=1: HIGH or FLOATING, DIx=0: LOW.
339		-* DO is for reverse digital output. DOx=1: LOW, DOx=0: HIGH or FLOATING.
	305	+* RO is for relay. ROx=1 : closed, ROx=0 always open.
	306	+* DI is for digital input. DIx=1: high or floating, DIx=0: low.
	307	+* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.
340	340
341	341	(% style="color:red" %)**Note: DI3 and DO3 bits are not valid for LT-22222-L**
342	342
...	...	@@ -353,28 +353,31 @@
353	353
354	354	ACI2 channel current is 0x1300/1000=4.864mA
355	355
356		-The last byte 0xAA= **10101010**(b) means,
	324	+The last byte 0xAA= 10101010(b) means,
357	357
358		-* [1] The RO1 relay channel is CLOSED, and the RO1 LED is ON.
359		-* [0] The RO2 relay channel is OPEN, and the RO2 LED is OFF.
360		-* **[1] DI3 - not used for LT-22222-L.**
361		-* [0] DI2 channel input is LOW, and the DI2 LED is OFF.
	326	+* [1] RO1 relay channel is closed, and the RO1 LED is ON.
	327	+* [0] RO2 relay channel is open, and RO2 LED is OFF.
	328	+* [1] DI3 - not used for LT-22222-L.
	329	+* [0] DI2 channel input is low, and the DI2 LED is OFF.
362	362	* [1] DI1 channel input state:
363		-** DI1 is FLOATING when no sensor is connected between DI1+ and DI1-.
364		-** DI1 is HIGH when a sensor is connected between DI1- and DI1+ and the sensor is ACTIVE.
	331	+** DI1 is floating when there is no load between DI1 and V+.
	332	+** DI1 is high when there is load between DI1 and V+.
365	365	** DI1 LED is ON in both cases.
366		-* **[0] DO3 - not used for LT-22222-L.**
367		-* [1] DO2 channel output is LOW, and the DO2 LED is ON.
	334	+* [0] DO3 channel output state:
	335	+** DO3 is float in case no load between DO3 and V+.
	336	+** DO3 is high in case there is load between DO3 and V+.
	337	+** DO3 LED is OFF in both case
	338	+* [1] DO2 channel output is low, and the DO2 LED is ON.
368	368	* [0] DO1 channel output state:
369		-** DO1 is FLOATING when there is no load between DO1 and V+.
370		-** DO1 is HIGH when there is a load between DO1 and V+.
371		-** DO1 LED is OFF in both cases.
	340	+** DO1 is floating when there is no load between DO1 and V+.
	341	+** DO1 is high when there is load between DO1 and V+.
	342	+** DO1 LED is OFF in both case.
372	372
373	373	=== 3.3.2 AT+MOD~=2, (Double DI Counting) ===
374	374
375	375
376	376	(((
377		-**For LT-22222-L**: In this mode, **DI1 and DI2** are used as counting pins.
	348	+**For LT-22222-L**: In this mode, the **DI1 and DI2** are used as counting pins.
378	378	)))
379	379
380	380	(((
...	...	@@ -388,17 +388,17 @@
388	388	)))
389	389
390	390	(((
391		-(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, FIRST, Reserve, Reserve, DO3, DO2 and DO1, and its size is 1 byte long as shown below.
	362	+(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination for RO1, RO2, DO3, DO2 and DO1, for a total of 1 byte, as shown below.
392	392
393	393	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
394	394	|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
395	395	|RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1
396	396
397		-* RO is for the relay. ROx=1: CLOSED, ROx=0 always OPEN.
	368	+* RO is for relay. ROx=1 : closed, ROx=0 always open.
398	398	)))
399	399
400	400	* FIRST: Indicates that this is the first packet after joining the network.
401		-* DO is for reverse digital output. DOx=1: LOW, DOx=0: HIGH or FLOATING.
	372	+* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.
402	402
403	403	(((
404	404	(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L**
...	...	@@ -407,7 +407,7 @@
407	407	)))
408	408
409	409	(((
410		-**To activate this mode, run the following AT commands:**
	381	+**To activate this mode, please run the following AT command:**
411	411	)))
412	412
413	413	(((
...	...	@@ -428,17 +428,17 @@
428	428	(((
429	429	**For LT22222-L:**
430	430
431		-(% style="color:blue" %)**AT+TRIG1=0,100**(%%)** (sets the DI1 port to trigger on a LOW level. The valid signal duration is 100ms) **
	402	+(% style="color:blue" %)**AT+TRIG1=0,100**(%%)**  (set the DI1 port to trigger on a low level, the valid signal duration is 100ms) **
432	432
433		-(% style="color:blue" %)**AT+TRIG1=1,100**(%%)** (sets the DI1 port to trigger on a HIGH level. The valid signal duration is 100ms) **
	404	+(% style="color:blue" %)**AT+TRIG1=1,100**(%%)**  (set the DI1 port to trigger on a high level, the valid signal duration is 100ms) **
434	434
435		-(% style="color:blue" %)**AT+TRIG2=0,100**(%%)** (sets the DI2 port to trigger on a LOW level. The valid signal duration is 100ms) **
	406	+(% style="color:blue" %)**AT+TRIG2=0,100**(%%)**  (set the DI2 port to trigger on a low level, the valid signal duration is 100ms) **
436	436
437		-(% style="color:blue" %)**AT+TRIG2=1,100**(%%)** (sets the DI2 port to trigger on a HIGH level. The valid signal duration is 100ms) **
	408	+(% style="color:blue" %)**AT+TRIG2=1,100**(%%)**  (set the DI2 port to trigger on a high level, the valid signal duration is 100ms) **
438	438
439		-(% style="color:blue" %)**AT+SETCNT=1,60**(%%)** (sets the COUNT1 value to 60)**
	410	+(% style="color:blue" %)**AT+SETCNT=1,60**(%%)**   (Set the COUNT1 value to 60)**
440	440
441		-(% style="color:blue" %)**AT+SETCNT=2,60 **(%%)**(sets the COUNT2 value to 60)**
	412	+(% style="color:blue" %)**AT+SETCNT=2,60**(%%)**   (Set the COUNT2 value to 60)**
442	442	)))
443	443
444	444
...	...	@@ -456,7 +456,7 @@
456	456	)))|DIDORO*|Reserve|MOD
457	457
458	458	(((
459		-(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below.
	430	+(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below.
460	460
461	461	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
462	462	|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
...	...	@@ -463,17 +463,17 @@
463	463	|RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1
464	464	)))
465	465
466		-* RO is for the relay. ROx=1: closed, ROx=0 always open.
	437	+* RO is for relay. ROx=1 : closed, ROx=0 always open.
467	467	* FIRST: Indicates that this is the first packet after joining the network.
468	468	* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.
469	469
470	470	(((
471		-(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L.**
	442	+(% style="color:red" %)**Note: DO3 is not valid for LT-22222-L.**
472	472	)))
473	473
474	474
475	475	(((
476		-**To activate this mode, run the following AT commands:**
	447	+**To activate this mode, please run the following AT command:**
477	477	)))
478	478
479	479	(((
...	...	@@ -488,7 +488,7 @@
488	488	(((
489	489	AT Commands for counting:
490	490
491		-The AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
	462	+The AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]. Use only the commands that match 'DI'.
492	492	)))
493	493
494	494
...	...	@@ -510,7 +510,7 @@
510	510	)))
511	511
512	512	(((
513		-(% style="color:#4f81bd" %)**DIDORO **(%%)is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below.
	484	+(% style="color:#4f81bd" %)**DIDORO **(%%)is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below.
514	514
515	515	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
516	516	|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
...	...	@@ -517,18 +517,18 @@
517	517	|RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1
518	518	)))
519	519
520		-* RO is for the relay. ROx=1: closed, ROx=0 always open.
	491	+* RO is for relay. ROx=1 : closed, ROx=0 always open.
521	521	* FIRST: Indicates that this is the first packet after joining the network.
522	522	* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.
523	523
524	524	(((
525		-(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L.**
	496	+(% style="color:red" %)**Note: DO3 is not valid for LT-22222-L.**
526	526
527	527
528	528	)))
529	529
530	530	(((
531		-**To activate this mode, run the following AT commands:**
	502	+**To activate this mode, please run the following AT command:**
532	532	)))
533	533
534	534	(((
...	...	@@ -541,19 +541,19 @@
541	541	)))
542	542
543	543	(((
544		-Other AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
	515	+Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]].
545	545	)))
546	546
547	547	(((
548	548	**In addition to that, below are the commands for AVI1 Counting:**
549	549
550		-(% style="color:blue" %)**AT+SETCNT=3,60**(%%)**  (Sets AVI Count to 60)**
	521	+(% style="color:blue" %)**AT+SETCNT=3,60**(%%)**  (set AVI Count to 60)**
551	551
552	552	(% style="color:blue" %)**AT+VOLMAX=20000**(%%)**  (If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
553	553
554	554	(% style="color:blue" %)**AT+VOLMAX=20000,0**(%%)**  (If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
555	555
556		-(% style="color:blue" %)**AT+VOLMAX=20000,1**(%%)**  (If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
	527	+(% style="color:blue" %)**AT+VOLMAX=20000,1**(%%)**  (If AVI1 voltage higer than VOLMAX (20000mV =20v), counter increase 1)**
557	557	)))
558	558
559	559
...	...	@@ -560,7 +560,7 @@
560	560	=== 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI ===
561	561
562	562
563		-**LT22222-L**: In this mode, the DI1 is used as a counting pin.
	534	+**LT22222-L**: This mode the DI1 is used as a counting pin.
564	564
565	565	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
566	566	|(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**
...	...	@@ -575,25 +575,25 @@
575	575	)))|MOD
576	576
577	577	(((
578		-(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below.
	549	+(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below
579	579
580	580	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
581		-|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
	552	+|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
582	582	|RO1|RO2|FIRST|Reserve|Reserve|DO3|DO2|DO1
583	583	)))
584	584
585		-* RO is for the relay. ROx=1: closed, ROx=0 always open.
586		-* FIRST: Indicates that this is the first packet after joining the network.
	556	+* RO is for relay. ROx=1 : close, ROx=0 always open.
	557	+* FIRST: Indicate this is the first packet after join network.
587	587	* (((
588		-DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.
	559	+DO is for reverse digital output. DOx=1: output low, DOx=0: high or float.
589	589	)))
590	590
591	591	(((
592		-(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L.**
	563	+(% style="color:red" %)**Note: DO3 is not valid for LT-22222-L.**
593	593	)))
594	594
595	595	(((
596		-**To activate this mode, run the following AT commands:**
	567	+**To use this mode, please run:**
597	597	)))
598	598
599	599	(((
...	...	@@ -606,7 +606,7 @@
606	606	)))
607	607
608	608	(((
609		-Other AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
	580	+Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]].
610	610	)))
611	611
612	612
...	...	@@ -613,46 +613,49 @@
613	613	=== 3.3.6 AT+ADDMOD~=6. (Trigger Mode, Optional) ===
614	614
615	615
616		-(% style="color:#4f81bd" %)**This mode is optional and intended for trigger purposes. It can operate together with other modes.**
	587	+(% style="color:#4f81bd" %)**This mode is an optional mode for trigger purpose. It can run together with other mode.**
617	617
618		-For example, if you configured the following commands:
	589	+For example, if user has configured below commands:
619	619
620	620	* **AT+MOD=1 ** **~-~->**  The normal working mode
621		-* **AT+ADDMOD6=1**   **~-~->**  Enable trigger mode
	592	+* **AT+ADDMOD6=1**   **~-~->**  Enable trigger
622	622
623		-The LT-22222-L will continuously monitor AV1, AV2, AC1, and AC2 every 5 seconds. LT will send uplink packets in two cases:
	594	+LT will keep monitoring AV1/AV2/AC1/AC2 every 5 seconds; LT will send uplink packets in two cases:
624	624
625		-1. Periodically uplink (Based on TDC time). The payload is the same as in normal mode (MOD=1 for the commands above). These are (% style="color:#4f81bd" %)**unconfirmed**(%%) uplinks.
626		-1. Trigger uplink when the trigger condition is met. LT will send two packets in this case. The first uplink uses the payload specified in trigger mode (MOD=6). The second packet uses the normal mode payload (MOD=1 as set above). Both are (% style="color:#4f81bd" %)**CONFIRMED uplinks.**
	596	+1. Periodically uplink (Base on TDC time). Payload is same as the normal MOD (MOD 1 for above command). This uplink uses LoRaWAN (% style="color:#4f81bd" %)**unconfirmed**(%%) data type
	597	+1. Trigger uplink when meet the trigger condition. LT will sent two packets in this case, the first uplink use payload specify in this mod (mod=6), the second packets use the normal mod payload(MOD=1 for above settings). Both Uplinks use LoRaWAN (% style="color:#4f81bd" %)**CONFIRMED data type.**
627	627
628	628	(% style="color:#037691" %)**AT Command to set Trigger Condition**:
629	629
630		-(% style="color:#4f81bd" %)**Trigger based on voltage**:
631	631
	602	+(% style="color:#4f81bd" %)**Trigger base on voltage**:
	603	+
632	632	Format: AT+AVLIM=<AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH>
633	633
634	634
635	635	**Example:**
636	636
637		-AT+AVLIM=3000,6000,0,2000   (triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V)
	609	+AT+AVLIM=3000,6000,0,2000   (If AVI1 voltage lower than 3v or higher than 6v. or AV2 voltage is higher than 2v, LT will trigger Uplink)
638	638
639		-AT+AVLIM=5000,0,0,0   (triggers an uplink if AVI1 voltage lower than 5V. Use 0 for parameters that are not in use)
	611	+AT+AVLIM=5000,0,0,0   (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore)
640	640
641	641
642		-(% style="color:#4f81bd" %)**Trigger based on current**:
643	643
	615	+(% style="color:#4f81bd" %)**Trigger base on current**:
	616	+
644	644	Format: AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH>
645	645
646	646
647	647	**Example:**
648	648
649		-AT+ACLIM=10000,15000,0,0   (triggers an uplink if ACI1 voltage is lower than 10mA or higher than 15mA)
	622	+AT+ACLIM=10000,15000,0,0   (If ACI1 voltage lower than 10mA or higher than 15mA, trigger an uplink)
650	650
651	651
652		-(% style="color:#4f81bd" %)**Trigger based on DI status**:
653	653
654		-DI status triggers Flag.
	626	+(% style="color:#4f81bd" %)**Trigger base on DI status**:
655	655
	628	+DI status trigger Flag.
	629	+
656	656	Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >
657	657
658	658
...	...	@@ -661,38 +661,39 @@
661	661	AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
662	662
663	663
664		-(% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
	638	+(% style="color:#037691" %)**Downlink Command to set Trigger Condition:**
665	665
666	666	Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
667	667
668	668	Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
669	669
670		- AA: Type Code for this downlink Command:
	644	+ AA: Code for this downlink Command:
671	671
672		- xx: **0**: Limit for AV1 and AV2; **1**: limit for AC1 and AC2; **2**: DI1and DI2 trigger enable/disable.
	646	+ xx: 0: Limit for AV1 and AV2;  1: limit for AC1 and AC2 ; 2 DI1, DI2 trigger enable/disable
673	673
674		- yy1 yy1: AC1 or AV1 LOW limit or DI1/DI2 trigger status.
	648	+ yy1 yy1: AC1 or AV1 low limit or DI1/DI2 trigger status.
675	675
676		- yy2 yy2: AC1 or AV1 HIGH limit.
	650	+ yy2 yy2: AC1 or AV1 high limit.
677	677
678		- yy3 yy3: AC2 or AV2 LOW limit.
	652	+ yy3 yy3: AC2 or AV2 low limit.
679	679
680		- Yy4 yy4: AC2 or AV2 HIGH limit.
	654	+ Yy4 yy4: AC2 or AV2 high limit.
681	681
682	682
683		-**Example 1**: AA 00 13 88 00 00 00 00 00 00
	657	+**Example1**: AA 00 13 88 00 00 00 00 00 00
684	684
685		-Same as AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage is lower than 5V. Use 0s for parameters that are not in use)
	659	+Same as AT+AVLIM=5000,0,0,0   (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore)
686	686
687	687
688		-**Example 2**: AA 02 01 00
	662	+**Example2**: AA 02 01 00
689	689
690		-Same as AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
	664	+Same as AT+ DTRI =1,0  (Enable DI1 trigger / disable DI2 trigger)
691	691
692	692
	667	+
693	693	(% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:**
694	694
695		-MOD6 Payload: total of 11 bytes
	670	+MOD6 Payload : total 11 bytes payload
696	696
697	697	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
698	698	|(% 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**
...	...	@@ -706,10 +706,10 @@
706	706	MOD(6)
707	707	)))
708	708
709		-(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
	684	+(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if trigger is set for this part. Totally 1byte as below
710	710
711	711	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
712		-|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
	687	+|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
713	713	|(((
714	714	AV1_LOW
715	715	)))|(((
...	...	@@ -728,17 +728,17 @@
728	728	AC2_HIGH
729	729	)))
730	730
731		-* Each bit shows if the corresponding trigger has been configured.
	706	+* Each bits shows if the corresponding trigger has been configured.
732	732
733	733	**Example:**
734	734
735		-10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW
	710	+10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW
736	736
737	737
738		-(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
	713	+(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1byte as below
739	739
740	740	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
741		-|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
	716	+|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
742	742	|(((
743	743	AV1_LOW
744	744	)))|(((
...	...	@@ -757,11 +757,11 @@
757	757	AC2_HIGH
758	758	)))
759	759
760		-* Each bit shows which status has been triggered on this uplink.
	735	+* Each bits shows which status has been trigger on this uplink.
761	761
762	762	**Example:**
763	763
764		-10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.
	739	+10000000: Means this packet is trigger by AC1_LOW. Means voltage too low.
765	765
766	766
767	767	(% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
...	...	@@ -770,7 +770,7 @@
770	770	|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
771	771	|N/A|N/A|N/A|N/A|DI2_STATUS|DI2_FLAG|DI1_STATUS|DI1_FLAG
772	772
773		-* Each bits shows which status has been triggered on this uplink.
	748	+* Each bits shows which status has been trigger on this uplink.
774	774
775	775	**Example:**
776	776
...	...	@@ -797,11 +797,11 @@
797	797	)))
798	798
799	799
800		-== 3.4 ​Configure LT via AT Commands or Downlinks ==
	775	+== 3.4 ​Configure LT via AT or Downlink ==
801	801
802	802
803	803	(((
804		-User can configure LT I/O Controller via AT Commands or LoRaWAN Downlinks.
	779	+User can configure LT I/O Controller via AT Commands or LoRaWAN Downlink Commands
805	805	)))
806	806
807	807	(((
...	...	@@ -816,8 +816,9 @@
816	816
817	817	=== 3.4.1 Common Commands ===
818	818
	794	+
819	819	(((
820		-These commands should be available for all Dragino sensors, 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]].
	796	+They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.5.4, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
821	821	)))
822	822
823	823
...	...	@@ -825,37 +825,34 @@
825	825
826	826	==== 3.4.2.1 Set Transmit Interval ====
827	827
828		-Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
829	829
830		-* (% style="color:#037691" %)**AT command:**
	805	+Set device uplink interval.
831	831
832		-(% style="color:blue" %)**AT+TDC=N**
	807	+* (% style="color:#037691" %)**AT Command:**
833	833
834		-where N is the time in milliseconds.
	809	+(% style="color:blue" %)**AT+TDC=N **
835	835
836		-**Example: **AT+TDC=30000. This will set the uplink interval to 30 seconds
837	837
	812	+**Example: **AT+TDC=30000. Means set interval to 30 seconds
838	838
839		-* (% style="color:#037691" %)**Downlink payload (prefix 0x01):**
840	840
	815	+* (% style="color:#037691" %)**Downlink Payload (prefix 0x01):**
	816	+
841	841	(% style="color:blue" %)**0x01 aa bb cc  **(%%)** ~/~/ Same as AT+TDC=0x(aa bb cc)**
842	842
843	843
844	844
845		-==== 3.4.2.2 Set the Work Mode (AT+MOD) ====
	821	+==== 3.4.2.2 Set Work Mode (AT+MOD) ====
846	846
847	847
848		-Sets the work mode.
	824	+Set work mode.
849	849
850		-* (% style="color:#037691" %)**AT command:**(%%) (% style="color:blue" %)**AT+MOD=N  **
	826	+* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+MOD=N  **
851	851
852		-Where N is the work mode.
	828	+**Example**: AT+MOD=2. Set work mode to Double DI counting mode
853	853
854		-**Example**: AT+MOD=2. This will set the work mode to Double DI counting mode.
	830	+* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A):**
855	855
856		-
857		-* (% style="color:#037691" %)**Downlink payload (prefix 0x0A):**
858		-
859	859	(% style="color:blue" %)**0x0A aa  **(%%)** ** ~/~/ Same as AT+MOD=aa
860	860
861	861
...	...	@@ -863,12 +863,10 @@
863	863	==== 3.4.2.3 Poll an uplink ====
864	864
865	865
866		-Asks the device to send an uplink.
	839	+* (% style="color:#037691" %)**AT Command:**(%%) There is no AT Command to poll uplink
867	867
868		-* (% style="color:#037691" %)**AT command:**(%%) There is no AT Command to poll uplink
	841	+* (% style="color:#037691" %)**Downlink Payload (prefix 0x08):**
869	869
870		-* (% style="color:#037691" %)**Downlink payload (prefix 0x08):**
871		-
872	872	(% style="color:blue" %)**0x08 FF  **(%%)** **~/~/ Poll an uplink
873	873
874	874	**Example**: 0x08FF, ask device to send an Uplink
...	...	@@ -875,16 +875,16 @@
875	875
876	876
877	877
878		-==== 3.4.2.4 Enable/Disable Trigger Mode ====
	849	+==== 3.4.2.4 Enable Trigger Mode ====
879	879
880	880
881		-Enable or disable the trigger mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
	852	+Use of trigger mode, please check [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
882	882
883	883	* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0**
884	884
885		-(% style="color:red" %)**1:** (%%)Enable the trigger mode
	856	+(% style="color:red" %)**1:** (%%)Enable Trigger Mode
886	886
887		-(% style="color:red" %)**0: **(%%)Disable the trigger mode
	858	+(% style="color:red" %)**0: **(%%)Disable Trigger Mode
888	888
889	889
890	890	* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A 06):**
...	...	@@ -896,7 +896,7 @@
896	896	==== 3.4.2.5 Poll trigger settings ====
897	897
898	898
899		-Polls the trigger settings
	870	+Poll trigger settings
900	900
901	901	* (% style="color:#037691" %)**AT Command:**
902	902
...	...	@@ -904,7 +904,7 @@
904	904
905	905	* (% style="color:#037691" %)**Downlink Payload (prefix 0x AB 06):**
906	906
907		-(% style="color:blue" %)**0xAB 06  ** (%%) ~/~/ Poll the trigger settings. Device will uplink trigger settings once receive this command
	878	+(% style="color:blue" %)**0xAB 06  ** (%%) ~/~/ Poll trigger settings, device will uplink trigger settings once receive this command
908	908
909	909
910	910
...	...	@@ -911,11 +911,11 @@
911	911	==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ====
912	912
913	913
914		-Enable or Disable DI1/DI2/DI2 as trigger,
	885	+Enable Disable DI1/DI2/DI2 as trigger,
915	915
916	916	* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
917	917
918		-**Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
	889	+**Example:** AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
919	919
920	920
921	921	* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 02):**
...	...	@@ -947,15 +947,15 @@
947	947	==== 3.4.2.8 Trigger2 – Set DI2 as trigger ====
948	948
949	949
950		-Sets DI2 trigger.
	921	+Set DI2 trigger.
951	951
952	952	* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b**
953	953
954		-(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
	925	+(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
955	955
956	956	(% style="color:red" %)**b :** (%%)delay timing.
957	957
958		-**Example:** AT+TRIG2=0,100 (set DI1 port to trigger on low level, valid signal is 100ms )
	929	+**Example:** AT+TRIG2=0,100(set DI1 port to trigger on low level, valid signal is 100ms )
959	959
960	960
961	961	* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 02 ):**
...	...	@@ -993,7 +993,7 @@
993	993	==== 3.4.2.11 Trigger – Set minimum interval ====
994	994
995	995
996		-Sets AV and AC trigger minimum interval. Device won't response to the second trigger within this set time after the first trigger.
	967	+Set AV and AC trigger minimum interval, system won't response to the second trigger within this set time after the first trigger.
997	997
998	998	* (% 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.
999	999
...	...	@@ -1141,7 +1141,7 @@
1141	1141	)))
1142	1142
1143	1143	(((
1144		-00: Closed ,  01: Open , 11: No action
	1115	+00: Close ,  01: Open , 11: No action
1145	1145
1146	1146	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %)
1147	1147	|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**RO1**|(% style="background-color:#4f81bd; color:white" %)**RO2**
...	...	@@ -1263,7 +1263,7 @@
1263	1263
1264	1264
1265	1265
1266		-==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
	1237	+==== 3.4.2.19 Counting ~-~- Change counting mode save time ====
1267	1267
1268	1268
1269	1269	* (% style="color:#037691" %)**AT Command:**
...	...	@@ -1386,142 +1386,89 @@
1386	1386
1387	1387	== 3.5 Integrating with ThingsEye.io ==
1388	1388
1389		-The Things Stack applications can be integrated with ThingsEye.io. Once integrated, ThingsEye.io works as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
	1360	+If you are using one of The Things Stack plans, you can integrate ThingsEye.io with your application. Once integrated, ThingsEye.io works as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
1390	1390
1391		-=== 3.5.1 Configuring MQTT Connection Information with The Things Stack Sandbox ===
	1362	+=== 3.5.1 Configuring The Things Stack Sandbox ===
1392	1392
1393		-We use The Things Stack Sandbox for demonstating the configuration but  other
	1364	+* Go to your Application and select MQTT under Integrations.
	1365	+* In the Connection credentials section, under Username, The Thins Stack displays an auto-generated username. You can use it or provide a new one.
	1366	+* For the Password, click the Generate new API key button to generate a password. You can see it by clicking on the eye button.
1394	1394
1395		-* In **The Things Stack Sandbox**, select your application under **Applications**.
1396		-* Select **MQTT** under **Integrations**.
1397		-* In the **Connection information **section, for **Username**, The Things Stack displays an auto-generated username. You can use it or provide a new one.
1398		-* For the **Password**, click the **Generate new API key** button to generate a password. You can see it by clicking on the **eye** button. The API key works as the password.
1399		-
1400		-NOTE. The username and  password (API key) you created here are required in the next section.
1401		-
1402	1402	[[image:tts-mqtt-integration.png||height="625" width="1000"]]
1403	1403
1404	1404	=== 3.5.2 Configuring ThingsEye.io ===
1405	1405
1406		-This section guides you on how to create an integration in ThingsEye to connect with The Things Stack MQTT server.
	1372	+* Login to your thingsEye.io account.
	1373	+* Under the Integrations center, click Integrations.
	1374	+* Click the Add integration button (the button with the + symbol).
1407	1407
1408		-* Login to your [[ThingsEye.io >>https://thingseye.io]]account.
1409		-* Under the **Integrations center**, click **Integrations**.
1410		-* Click the **Add integration** button (the button with the **+** symbol).
1411		-
1412	1412	[[image:thingseye-io-step-1.png||height="625" width="1000"]]
1413	1413
1414	1414
1415		-On the **Add integration** window, configure the following:
	1379	+On the Add integration page configure the following:
1416	1416
1417		-**Basic settings:**
	1381	+Basic settings:
1418	1418
1419		-* Select **The Things Stack Community** from the **Integration type** list.
1420		-* Enter a suitable name for your integration in the **Name **text** **box or keep the default name.
1421		-* Ensure the following options are turned on.
1422		-** Enable integration
1423		-** Debug mode
1424		-** Allow create devices or assets
1425		-* Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
	1383	+* Select The Things Stack Community from the Integration type list.
	1384	+* Enter a suitable name for your integration in the Name box or keep the default name.
	1385	+* Click the Next button.
1426	1426
1427	1427	[[image:thingseye-io-step-2.png||height="625" width="1000"]]
1428	1428
	1389	+Uplink Data converter:
1429	1429
1430		-**Uplink data converter:**
	1391	+* Click the Create New button if it is not selected by default.
	1392	+* Click the JavaScript button.
	1393	+* Paste the uplink decoder function into the text area (first, delete the default code). The demo decoder function can be found here.
	1394	+* Click the Next button.
1431	1431
1432		-* Click the **Create new** button if it is not selected by default.
1433		-* Enter a suitable name for the uplink data converter in the **Name **text** **box or keep the default name.
1434		-* Click the **JavaScript** button.
1435		-* 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]].
1436		-* Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
1437		-
1438	1438	[[image:thingseye-io-step-3.png||height="625" width="1000"]]
1439	1439
	1398	+Downlink Data converter (this is an optional step):
1440	1440
1441		-**Downlink data converter (this is an optional step):**
	1400	+* Click the Create new button if it is not selected by default.
	1401	+* Click the JavaScript button.
	1402	+* Paste the downlink decoder function into the text area (first, delete the default code). The demo decoder function can be found here.
	1403	+* Click the Next button.
1442	1442
1443		-* Click the **Create new** button if it is not selected by default.
1444		-* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name
1445		-* Click the **JavaScript** button.
1446		-* Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found here.
1447		-* Click the **Next** button. You will be navigated to the **Connection** tab.
1448		-
1449	1449	[[image:thingseye-io-step-4.png||height="625" width="1000"]]
1450	1450
	1407	+Connection:
1451	1451
1452		-**Connection:**
	1409	+* Choose Region from the Host type.
	1410	+* Enter the cluster of your The Things Stack in the Region textbox.
	1411	+* Enter the Username and Password in the Credentials section. Use the same username and password you created with the MQTT page of The Things Stack.
	1412	+* Click Check connection to test the connection. If the connection is successful, you can see the message saying Connected.
	1413	+* Click the Add button.
1453	1453
1454		-* Choose **Region** from the **Host type**.
1455		-* 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/...).
1456		-* 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 MQTT Connection information with The Things Stack Sandbox).
1457		-* Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
1458		-
1459		-[[image:message-1.png]]
1460		-
1461		-
1462		-* Click the **Add** button.
1463		-
1464	1464	[[image:thingseye-io-step-5.png||height="625" width="1000"]]
1465	1465
1466	1466
1467		-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.
	1418	+Your integration is added to the integrations list and it will display on the Integrations page.
1468	1468
	1420	+[[image:thingseye-io-step-6.png||height="625" width="1000"]]
1469	1469
1470		-[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
1471	1471
	1423	+== 3.6 Interface Detail ==
1472	1472
1473		-**Viewing integration details**:
1474		-
1475		-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.
1476		-
1477		-[[image:integration-details.png||height="686" width="1000"]]
1478		-
1479		-
1480		-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.
1481		-
1482		-Note: See also ThingsEye documentation.
1483		-
1484		-
1485		-**Viewing events:**
1486		-
1487		-This tab  displays all the uplink messages from the LT-22222-L.
1488		-
1489		-* Click on the **Events **tab.
1490		-* Select **Debug **from the **Event type** dropdown.
1491		-* Select the** time frame** from the **time window**.
1492		-
1493		-[insert image]
1494		-
1495		-- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
1496		-
1497		-[insert image]
1498		-
1499		-
1500		-**Deleting the integration**:
1501		-
1502		-If you want to delete this integration, click the **Delete integratio**n button.
1503		-
1504		-
1505		-== 3.6 Interface Details ==
1506		-
1507	1507	=== 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) ===
1508	1508
1509	1509
1510		-Support NPN-type sensor
	1428	+Support NPN Type sensor
1511	1511
1512	1512	[[image:1653356991268-289.png]]
1513	1513
1514	1514
1515		-=== 3.6.2 Digital Input Ports: DI1/DI2 ( For LT-22222-L) ===
	1433	+=== 3.6.2 Digital Input Port: DI1/DI2 ( For LT-22222-L) ===
1516	1516
1517	1517
1518	1518	(((
1519		-The DI ports of the LT-22222-L can support **NPN**, **PNP**, or **dry contact** output sensors.
	1437	+The DI port of LT-22222-L can support **NPN** or **PNP** or **Dry Contact** output sensor.
1520	1520	)))
1521	1521
1522	1522	(((
1523	1523	(((
1524		-The part of the internal circuit of the LT-22222-L shown below includes the NEC2501 photocoupler. The active current from NEC2501 pin 1 to pin 2 is 1 mA, with a maximum allowable current of 50 mA. When active current flows from NEC2501 pin 1 to pin 2, the DI becomes active HIGH and the DI LED status changes.
	1442	+Internal circuit as below, the NEC2501 is a photocoupler, the Active current (from NEC2501 pin 1 to pin 2 is 1ma and the max current is 50mA). (% class="mark" %)When there is active current pass NEC2501 pin1 to pin2. The DI will be active high and DI LED status will change.
1525	1525
1526	1526
1527	1527	)))
...	...	@@ -1531,7 +1531,7 @@
1531	1531
1532	1532	(((
1533	1533	(((
1534		-(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)When connecting a device to the DI port, both DI1+ and DI1- must be connected.
	1452	+When use need to connect a device to the DI port, both DI1+ and DI1- must be connected.
1535	1535	)))
1536	1536	)))
1537	1537
...	...	@@ -1540,22 +1540,22 @@
1540	1540	)))
1541	1541
1542	1542	(((
1543		-(% style="color:#0000ff" %)**Example 1**(%%): Connecting to a low-active sensor.
	1461	+(% style="color:blue" %)**Example1**(%%): Connect to a Low active sensor.
1544	1544	)))
1545	1545
1546	1546	(((
1547		-This type of sensor outputs a low (GND) signal when active.
	1465	+This type of sensor will output a low signal GND when active.
1548	1548	)))
1549	1549
1550	1550	* (((
1551		-Connect the sensor's output to DI1-
	1469	+Connect sensor's output to DI1-
1552	1552	)))
1553	1553	* (((
1554		-Connect the sensor's VCC to DI1+.
	1472	+Connect sensor's VCC to DI1+.
1555	1555	)))
1556	1556
1557	1557	(((
1558		-When the sensor is active, the current between NEC2501 pin 1 and pin 2 will be：
	1476	+So when sensor active, the current between NEC2501 pin1 and pin2 is：
1559	1559	)))
1560	1560
1561	1561	(((
...	...	@@ -1563,7 +1563,7 @@
1563	1563	)))
1564	1564
1565	1565	(((
1566		-For example, if** DI1+ **= **12V**, the resulting current is [[image:1653968155772-850.png||height="23" width="19"]]= 12mA. Therefore, the LT-22222-L will be able to detect this active signal.
	1484	+If** DI1+ **= **12v**, the [[image:1653968155772-850.png||height="23" width="19"]]= 12mA , So the LT-22222-L will be able to detect this active signal.
1567	1567	)))
1568	1568
1569	1569	(((
...	...	@@ -1571,22 +1571,22 @@
1571	1571	)))
1572	1572
1573	1573	(((
1574		-(% style="color:#0000ff" %)**Example 2**(%%): Connecting to a high-active sensor.
	1492	+(% style="color:blue" %)**Example2**(%%): Connect to a High active sensor.
1575	1575	)))
1576	1576
1577	1577	(((
1578		-This type of sensor outputs a high signal (e.g., 24V) when active.
	1496	+This type of sensor will output a high signal (example 24v) when active.
1579	1579	)))
1580	1580
1581	1581	* (((
1582		-Connect the sensor's output to DI1+
	1500	+Connect sensor's output to DI1+
1583	1583	)))
1584	1584	* (((
1585		-Connect the sensor's GND DI1-.
	1503	+Connect sensor's GND DI1-.
1586	1586	)))
1587	1587
1588	1588	(((
1589		-When the sensor is active, the current between NEC2501 pin1 and pin2 will be:
	1507	+So when sensor active, the current between NEC2501 pin1 and pin2 is:
1590	1590	)))
1591	1591
1592	1592	(((
...	...	@@ -1594,7 +1594,7 @@
1594	1594	)))
1595	1595
1596	1596	(((
1597		-If **DI1+ = 24V**, the resulting current[[image:1653968155772-850.png||height="23" width="19"]] is 24mA, Therefore, the LT-22222-L will detect this high-active signal.
	1515	+If **DI1+ = 24v**, the[[image:1653968155772-850.png||height="23" width="19"]] 24mA , So the LT-22222-L will be able to detect this high active signal.
1598	1598	)))
1599	1599
1600	1600	(((
...	...	@@ -1602,22 +1602,22 @@
1602	1602	)))
1603	1603
1604	1604	(((
1605		-(% style="color:#0000ff" %)**Example 3**(%%): Connecting to a 220V high-active sensor.
	1523	+(% style="color:blue" %)**Example3**(%%): Connect to a 220v high active sensor.
1606	1606	)))
1607	1607
1608	1608	(((
1609		-Assume that you want to monitor an active signal higher than 220V without damaging the photocoupler
	1527	+Assume user want to monitor an active signal higher than 220v, to make sure not burn the photocoupler
1610	1610	)))
1611	1611
1612	1612	* (((
1613		-Connect the sensor's output to DI1+ with a 50K resistor in series.
	1531	+Connect sensor's output to DI1+ with a serial 50K resistor
1614	1614	)))
1615	1615	* (((
1616		-Connect the sensor's GND DI1-.
	1534	+Connect sensor's GND DI1-.
1617	1617	)))
1618	1618
1619	1619	(((
1620		-When the sensor is active, the current between NEC2501 pin1 and pin2 will be:
	1538	+So when sensor active, the current between NEC2501 pin1 and pin2 is:
1621	1621	)))
1622	1622
1623	1623	(((
...	...	@@ -1625,37 +1625,37 @@
1625	1625	)))
1626	1626
1627	1627	(((
1628		-If the sensor output is 220V, then [[image:1653968155772-850.png||height="23" width="19"]](% id="cke_bm_243359S" style="display:none" wfd-invisible="true" %)[[image:image-20220524095628-8.png]](%%) = DI1+ / 51K  = 4.3mA. Therefore, the LT-22222-L will be able to safely detect this high-active signal.
	1546	+If sensor output is 220v, the [[image:1653968155772-850.png||height="23" width="19"]](% id="cke_bm_243359S" style="display:none" %)[[image:image-20220524095628-8.png]](%%) = DI1+ / 51K.  = 4.3mA , So the LT-22222-L will be able to detect this high active signal safely.
1629	1629	)))
1630	1630
1631	1631
1632		-(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
	1550	+(% style="color:blue" %)**Example4**(%%): Connect to Dry Contact sensor
1633	1633
1634		-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.
	1552	+From above DI ports circuit, we can see that active the photocoupler will need to have a voltage difference between DI+ and DI- port. While the Dry Contact sensor is a passive component which can't provide this voltage difference.
1635	1635
1636		-To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram.
	1554	+To detect a Dry Contact, we can provide a power source to one pin of the Dry Contact. Below is a reference connection.
1637	1637
1638	1638	[[image:image-20230616235145-1.png]]
1639	1639
1640		-(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
	1558	+(% style="color:blue" %)**Example5**(%%): Connect to Open Colleactor
1641	1641
1642	1642	[[image:image-20240219115718-1.png]]
1643	1643
1644	1644
1645		-=== 3.6.3 Digital Output Ports: DO1/DO2 /DO3 ===
	1563	+=== 3.6.3 Digital Output Port: DO1/DO2 /DO3 ===
1646	1646
1647	1647
1648		-(% style="color:blue" %)**NPN output**(%%): GND or Float. The maximum voltage that can be applied to the output pin is 36V.
	1566	+(% style="color:blue" %)**NPN output**(%%): GND or Float. Max voltage can apply to output pin is 36v.
1649	1649
1650		-(% style="color:red" %)**Note: The DO pins will float when the device is powered off.**
	1568	+(% style="color:red" %)**Note: DO pins go to float when device is power off.**
1651	1651
1652	1652	[[image:1653357531600-905.png]]
1653	1653
1654	1654
1655		-=== 3.6.4 Analog Input Interfaces ===
	1573	+=== 3.6.4 Analog Input Interface ===
1656	1656
1657	1657
1658		-The analog input interface is shown below. The LT-22222-L will measure the IN2 voltage to calculate the current passing through the load. The formula is:
	1576	+The analog input interface is as below. The LT will measure the IN2 voltage so to calculate the current pass the Load. The formula is:
1659	1659
1660	1660
1661	1661	(% style="color:blue" %)**AC2 = (IN2 voltage )/12**
...	...	@@ -1662,14 +1662,14 @@
1662	1662
1663	1663	[[image:1653357592296-182.png]]
1664	1664
1665		-Example: Connecting a 4~~20mA sensor
	1583	+Example to connect a 4~~20mA sensor
1666	1666
1667		-We will use the wind speed sensor as an example for reference only.
	1585	+We take the wind speed sensor as an example for reference only.
1668	1668
1669	1669
1670	1670	(% style="color:blue" %)**Specifications of the wind speed sensor:**
1671	1671
1672		-(% style="color:red" %)**Red:  12~~24V**
	1590	+(% style="color:red" %)**Red:  12~~24v**
1673	1673
1674	1674	(% style="color:#ffc000" %)**Yellow:  4~~20mA**
1675	1675
...	...	@@ -1682,7 +1682,7 @@
1682	1682	[[image:1653357648330-671.png||height="155" width="733"]]
1683	1683
1684	1684
1685		-Example: Connecting to a regulated power supply to measure voltage
	1603	+Example connected to a regulated power supply to measure voltage
1686	1686
1687	1687	[[image:image-20230608101532-1.png||height="606" width="447"]]
1688	1688
...	...	@@ -1691,7 +1691,7 @@
1691	1691	[[image:image-20230608101722-3.png||height="102" width="1139"]]
1692	1692
1693	1693
1694		-(% style="color:blue; font-weight:bold" %)**Specifications of the regulated power supply**(% style="color:blue" %)**:**
	1612	+(% style="color:blue; font-weight:bold" %)**Specifications of the regulated power**(%%) (% style="color:blue" %)**:**
1695	1695
1696	1696	(% style="color:red" %)**Red:  12~~24v**
1697	1697
...	...	@@ -1702,9 +1702,9 @@
1702	1702
1703	1703
1704	1704	(((
1705		-The LT-22222-L has two relay interfaces, RO1 and RO2, each using two pins of the screw terminal (ROx-1 and ROx-2 where x is the port number, 1 or 2). You can connect a device's power line in series with one of the relay interfaces (e.g., RO1-1 and RO1-2 screw terminals). See the example below:
	1623	+The LT serial controller has two relay interfaces; each interface uses two pins of the screw terminal. User can connect other device's Power Line to in serial of RO1_1 and RO_2. Such as below:
1706	1706
1707		-**Note**: The ROx pins will be in the Open (NO) state when the LT-22222-L is powered off.
	1625	+**Note**: RO pins go to Open(NO) when device is power off.
1708	1708	)))
1709	1709
1710	1710	[[image:image-20220524100215-9.png]]
...	...	@@ -1732,25 +1732,25 @@
1732	1732	Transmit a LoRa packet: TX blinks once
1733	1733	)))
1734	1734	)))
1735		-|**RX**|RX blinks once when receiving a packet.
1736		-|**DO1**|For LT-22222-L: ON when DO1 is low, OFF when DO1 is high
1737		-|**DO2**|For LT-22222-L: ON when DO2 is low, OFF when DO2 is high
	1653	+|**RX**|RX blinks once when receive a packet.
	1654	+|**DO1**|For LT-22222-L: ON when DO1 is low, LOW when DO1 is high
	1655	+|**DO2**|For LT-22222-L: ON when DO2 is low, LOW when DO2 is high
1738	1738	|**DI1**|(((
1739		-For LT-22222-L: ON when DI1 is high, OFF when DI1 is low
	1657	+For LT-22222-L: ON when DI1 is high, LOW when DI1 is low
1740	1740	)))
1741	1741	|**DI2**|(((
1742		-For LT-22222-L: ON when DI2 is high, OFF when DI2 is low
	1660	+For LT-22222-L: ON when DI2 is high, LOW when DI2 is low
1743	1743	)))
1744		-|**RO1**|For LT-22222-L: ON when RO1 is closed, OFF when RO1 is open
1745		-|**RO2**|For LT-22222-L: ON when RO2 is closed, OFF when RO2 is open
	1662	+|**RO1**|For LT-22222-L: ON when RO1 is closed, LOW when RO1 is open
	1663	+|**RO2**|For LT-22222-L: ON when RO2 is closed, LOW when RO2 is open
1746	1746
1747		-= 4. Using AT Command =
	1665	+= 4. Use AT Command =
1748	1748
1749		-== 4.1 Connecting the LT-22222-L to a computer ==
	1667	+== 4.1 Access AT Command ==
1750	1750
1751	1751
1752	1752	(((
1753		-The LT-22222-L supports programming using AT Commands. You can use a USB-to-TTL adapter along with a 3.5mm Program Cable to connect the LT-22222-L to a computer, as shown below.
	1671	+LT supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to LT for using AT command, as below.
1754	1754	)))
1755	1755
1756	1756	[[image:1653358238933-385.png]]
...	...	@@ -1757,7 +1757,7 @@
1757	1757
1758	1758
1759	1759	(((
1760		-On the PC, the user needs 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. The AT commands are disabled by default, and a password (default:(% style="color:green" %)**123456**)(%%) must be entered to active them, as shown below:
	1678	+In PC, User needs to set (% style="color:#4f81bd" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600**(%%) to access to access serial console for LT. The AT commands are disable by default and need to enter password (default:(% style="color:green" %)**123456**)(%%) to active it. As shown below:
1761	1761	)))
1762	1762
1763	1763	[[image:1653358355238-883.png]]
...	...	@@ -1764,12 +1764,10 @@
1764	1764
1765	1765
1766	1766	(((
1767		-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/]]
	1685	+More detail AT Command manual can be found at [[AT Command Manual>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
1768	1768	)))
1769	1769
1770	1770	(((
1771		-The following table lists all the AT commands related to the LT-22222-L, except for those used for switching between modes.
1772		-
1773	1773	AT+<CMD>?        : Help on <CMD>
1774	1774	)))
1775	1775
...	...	@@ -2094,42 +2094,37 @@
2094	2094
2095	2095	= 5. Case Study =
2096	2096
2097		-== 5.1 Counting how many objects pass through the flow Line ==
	2013	+== 5.1 Counting how many objects pass in Flow Line ==
2098	2098
2099	2099
2100		-Reference Link: [[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]]?
	2016	+Reference Link: [[How to set up to count objects pass in flow line>>How to set up to count objects pass in flow line]]?
2101	2101
2102	2102
2103	2103	= 6. FAQ =
2104	2104
2105		-== 6.1 How to upgrade the firmware image? ==
	2021	+== 6.1 How to upgrade the image? ==
2106	2106
2107	2107
2108		-The LT-22222-L I/O Controller is shipped with a 3.5mm cable, which is used to upload an image to LT in order to:
	2024	+The LT LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to LT to:
2109	2109
2110		-* Support new features.
2111		-* Fix bugs.
	2026	+* Support new features
	2027	+* For bug fix
2112	2112	* Change LoRaWAN bands.
2113	2113
2114		-Below is the hardware connection setup for uploading an firmware image to the LT-22222-L:
	2030	+Below shows the hardware connection for how to upload an image to the LT:
2115	2115
2116		-(% class="box infomessage" %)
2117		-(((
2118		-The latest firmware version available for the LT-22222-L is v1.6.1 at the time of this writing.
2119		-)))
2120		-
2121	2121	[[image:1653359603330-121.png]]
2122	2122
2123	2123
2124	2124	(((
2125		-(% style="color:#0000ff" %)**Step 1**(%%)**:** Download the F[[lash 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)
2126		-(% style="color:#0000ff" %)**Step 2**(%%)**:** Download the [[LT Image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]].
2127		-(% style="color:#0000ff" %)**Step 3**(%%)**:** Open the Flash Loader and choose the correct COM port to update.
	2036	+(% style="color:blue" %)**Step1**(%%)**:** Download [[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]].
	2037	+(% style="color:blue" %)**Step2**(%%)**:** Download the [[LT Image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]].
	2038	+(% style="color:blue" %)**Step3**(%%)**:** Open flashloader; choose the correct COM port to update.
	2039	+
2128	2128
2129	2129	(((
2130	2130	(% style="color:blue" %)**For LT-22222-L**(%%):
2131		-
2132		-Hold down the **PRO** button, then briefly press the **RST** button. The **DO1** LED will change from OFF to ON. When the **DO1** LED is ON, it indicates that the device is in firmware download mode.
	2043	+Hold down the PRO button and then momentarily press the RST reset button and the (% style="color:red" %)**DO1 led**(%%) will change from OFF to ON. When (% style="color:red" %)**DO1 LED**(%%) is on, it means the device is in download mode.
2133	2133	)))
2134	2134
2135	2135
...	...	@@ -2144,7 +2144,7 @@
2144	2144	[[image:image-20220524104033-15.png]]
2145	2145
2146	2146
2147		-(% style="color:red" %)**Note**(%%): If you have lost the programming cable, you can make one from a 3.5mm cable. The pin mapping is as follows:
	2058	+(% style="color:red" %)**Notice**(%%): In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
2148	2148
2149	2149	[[image:1653360054704-518.png||height="186" width="745"]]
2150	2150
...	...	@@ -2158,13 +2158,13 @@
2158	2158	)))
2159	2159
2160	2160	(((
2161		-You can follow the introductions on [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloading, select the required image file.
	2072	+User can follow the introduction for [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
2162	2162	)))
2163	2163
2164	2164	(((
2165	2165
2166	2166
2167		-== 6.3 How to set up LT to work with a Single Channel Gateway, such as LG01/LG02? ==
	2078	+== 6.3 How to set up LT to work with Single Channel Gateway such as LG01/LG02? ==
2168	2168
2169	2169
2170	2170	)))
...	...	@@ -2171,13 +2171,13 @@
2171	2171
2172	2172	(((
2173	2173	(((
2174		-In this case, you need to set the LT-33222-L to work in ABP mode and transmit on only one frequency.
	2085	+In this case, users need to set LT-33222-L to work in ABP mode & transmit in only one frequency.
2175	2175	)))
2176	2176	)))
2177	2177
2178	2178	(((
2179	2179	(((
2180		-Assume you have an LG02 working on the frequency 868400000. Below are the steps.
	2091	+Assume we have a LG02 working in the frequency 868400000 now , below is the step.
2181	2181
2182	2182
2183	2183	)))
...	...	@@ -2184,7 +2184,7 @@
2184	2184	)))
2185	2185
2186	2186	(((
2187		-(% style="color:#0000ff" %)**Step 1**(%%):  Log in to The Things Stack SANDBOX, create an ABP device in the application, and input the Network Session key (NwkSKey), App session key (AppSKey) of the device.
	2098	+(% style="color:blue" %)**Step1**(%%):  Log in TTN, Create an ABP device in the application and input the network session key (NETSKEY), app session key (APPSKEY) from the device.
2188	2188
2189	2189
2190	2190	)))
...	...	@@ -2241,7 +2241,7 @@
2241	2241	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/]]
2242	2242
2243	2243
2244		-== 6.5 Can I see the counting event in Serial? ==
	2155	+== 6.5 Can I see counting event in Serial? ==
2245	2245
2246	2246
2247	2247	(((
...	...	@@ -2248,10 +2248,10 @@
2248	2248	User can run AT+DEBUG command to see the counting event in serial. If firmware too old and doesn't support AT+DEBUG. User can update to latest firmware first.
2249	2249
2250	2250
2251		-== 6.6 Can I use point-to-point communication with LT-22222-L? ==
	2162	+== 6.6 Can i use point to point communication for LT-22222-L? ==
2252	2252
2253	2253
2254		-Yes, please refer [[Point to Point Communication>>doc:Main. Point to Point Communication of LT-22222-L.WebHome]]. this is [[firmware>>https://github.com/dragino/LT-22222-L/releases]].
	2165	+Yes, please refer [[Point to Point Communication>>doc:Main. Point to Point Communication of LT-22222-L.WebHome]]  ，this is [[firmware>>https://github.com/dragino/LT-22222-L/releases]].
2255	2255
2256	2256
2257	2257	)))

integration-details.png

Author

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

Size

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

Content

lt-22222-device-overview.png

Author

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

Size

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

Content

lt-22222-join-network.png

Author

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

Size

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

Content

lt-22222-ul-payload-decoded.png

Author

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

Size

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

Content

lt-22222-ul-payload-fmt.png

Author

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

Size

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

Content

message-1.png

Author

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

Size

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

Content

thingseye.io_integrationsCenter_integrations-2.png

Author

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

Size

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

Content

thingseye.io_integrationsCenter_integrations.png

Author

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

Size

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

Content