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
...	...	@@ -42,7 +42,7 @@
42	42	* 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.
43	43	* Setup your own private LoRaWAN network.
44	44
45		-> 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.
46	46	)))
47	47
48	48	(((
...	...	@@ -60,12 +60,12 @@
60	60	* Power Consumption:
61	61	** Idle: 4mA@12v
62	62	** 20dB Transmit: 34mA@12v
63		-* Operating Temperature: -40 ~~ 85 Degrees, No Dew
	63	+* Operating Temperature: -40 ~~ 85 Degree, No Dew
64	64
65	65	(% style="color:#037691" %)**Interface for Model: LT22222-L:**
66	66
67	67	* 2 x Digital dual direction Input (Detect High/Low signal, Max: 50v, or 220v with optional external resistor)
68		-* 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)
69	69	* 2 x Relay Output (5A@250VAC / 30VDC)
70	70	* 2 x 0~~20mA Analog Input (res:0.01mA)
71	71	* 2 x 0~~30V Analog Input (res:0.01v)
...	...	@@ -78,7 +78,7 @@
78	78	** Band 2 (LF): 410 ~~ 528 Mhz
79	79	* 168 dB maximum link budget.
80	80	* +20 dBm - 100 mW constant RF output vs.
81		-* +14 dBm high-efficiency PA.
	81	+* +14 dBm high efficiency PA.
82	82	* Programmable bit rate up to 300 kbps.
83	83	* High sensitivity: down to -148 dBm.
84	84	* Bullet-proof front end: IIP3 = -12.5 dBm.
...	...	@@ -98,7 +98,7 @@
98	98	* Optional Customized LoRa Protocol
99	99	* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
100	100	* AT Commands to change parameters
101		-* Remotely configure parameters via LoRaWAN Downlink
	101	+* Remote configure parameters via LoRa Downlink
102	102	* Firmware upgradable via program port
103	103	* Counting
104	104
...	...	@@ -139,7 +139,7 @@
139	139	* 1 x bracket for wall mounting
140	140	* 1 x programming cable
141	141
142		-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.
143	143
144	144	== 2.2 Terminals ==
145	145
...	...	@@ -169,9 +169,9 @@
169	169	|(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
170	170	|(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
171	171
172		-== 2.3 Powering the LT-22222-L ==
	172	+== 2.3 Powering ==
173	173
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 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.
175	175
176	176
177	177	[[image:1653297104069-180.png]]
...	...	@@ -181,9 +181,9 @@
181	181
182	182	== 3.1 How does it work? ==
183	183
184		-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.
185	185
186		-For LT-22222-L, the LED will show the Join status: After powering on, the TX LED will fast-blink 5 times which means the LT-22222-L will enter the working 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 message from the server, the RX LED will be on for 1 second.
	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.
187	187
188	188	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.
189	189
...	...	@@ -205,7 +205,7 @@
205	205
206	206	* Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account.
207	207	* Create an application if you do not have one yet.
208		-* Register LT-22222-L with that application. Two registration options are available:
	208	+* Register LT-22222-L with that application. Two registration options available:
209	209
210	210	==== Using the LoRaWAN Device Repository: ====
211	211
...	...	@@ -213,12 +213,12 @@
213	213	* On the **Register end device** page:
214	214	** Select the option **Select the end device in the LoRaWAN Device Repository**.
215	215	** Choose the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)**.
216		-** Select the **Frequency plan** that matches your device.
	216	+** Select the **Frequency plan** that matches with your device.
217	217
218	218	[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
219	219
220	220	*
221		-** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
	221	+** Enter the **AppEUI** in the **JoinEUI** field and click **Confirm** button.
222	222	** Enter the **DevEUI** in the **DevEUI** field.
223	223	** Enter the **AppKey** in the **AppKey** field.
224	224	** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
...	...	@@ -230,55 +230,39 @@
230	230
231	231	* On the **Register end device** page:
232	232	** Select the **Enter end device specifies manually** option as the input method.
233		-** Select the **Frequency plan** that matches your device.
	233	+** Select the **Frequency plan** that matches with your device.
234	234	** Select the **LoRaWAN version**.
235	235	** Select the **Regional Parameters version**.
236	236	** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the section.
237		-** Select **Over the air activation (OTAA)** option under the **Activation mode**
	237	+** Select **Over the air activation (OTAA)** option under **Activation mode**
238	238	** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities**.
239	239
240	240	[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
241	241
242	242
243		-* Enter **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
	243	+* Enter **AppEUI** in the **JoinEUI** field and click **Confirm** button.
244	244	* Enter **DevEUI** in the **DevEUI** field.
245	245	* Enter **AppKey** in the **AppKey** field.
246	246	* In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
247	247	* Under **After registration**, select the **View registered end device** option.
248		-* Click the **Register end device** button.
249	249
250	250	[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
251	251
252	252
253		-You will be navigated to the **Device overview** page.
254		-
255		-[[image:lt-22222-device-overview.png||height="625" width="1000"]]
256		-
257		-
258	258	==== Joining ====
259	259
260		-Click on **Live data** in the left navigation. Then, power on LT-22222-L. It will join The Things Stack LoRaWAN network server. You can see the **join request**, **join accept**, followed by **uplink data messages** form the device showing in the **Live data** panel.
	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-join-network.png||height="625" width="1000"]]
	256	+[[image:1653298044601-602.png||height="405" width="709"]]
263	263
264	264
265		-Click on a message with the messge type, **Forward uplink data message**. You can see the  decoded uplink payload as shown below.
	259	+== 3.3 Uplink Payload formats ==
266	266
267		-[[image:lt-22222-ul-payload-decoded.png]]
268	268
	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.
269	269
270		-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.
	264	+* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2 x ACI + 2AVI + DI + DO + RO
271	271
272		-[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
273		-
274		-
275		-== 3.3 Work Modes and their Uplink Payload formats ==
276		-
277		-
278		-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 working mode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands.
279		-
280		-* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO
281		-
282	282	* (% style="color:blue" %)**MOD2**(%%): Double DI Counting + DO + RO
283	283
284	284	* (% style="color:blue" %)**MOD3**(%%): Single DI Counting + 2 x ACI + DO + RO
...	...	@@ -291,8 +291,9 @@
291	291
292	292	=== 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
293	293
	278	+
294	294	(((
295		-The uplink payload is 11 bytes long. Uplink messages are sent over LoRaWAN FPort 2. By default, one uplink is sent every 10 minutes. (% style="display:none" wfd-invisible="true" %)
	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" %)
296	296
297	297	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
298	298	|(% 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**
...	...	@@ -304,13 +304,13 @@
304	304	ACI1 Current
305	305	)))|(((
306	306	ACI2 Current
307		-)))|**DIDORO***|(((
	292	+)))|DIDORO*|(((
308	308	Reserve
309	309	)))|MOD
310	310	)))
311	311
312	312	(((
313		-(% 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.
314	314
315	315	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
316	316	|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
...	...	@@ -317,9 +317,9 @@
317	317	|RO1|RO2|--DI3--|DI2|DI1|--DO3--|DO2|DO1
318	318	)))
319	319
320		-* RO is for the relay. ROx=1: CLOSED, ROx=0 always OPEN.
321		-* DI is for digital input. DIx=1: HIGH or FLOATING, DIx=0: LOW.
322		-* 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.
323	323
324	324	(% style="color:red" %)**Note: DI3 and DO3 bits are not valid for LT-22222-L**
325	325
...	...	@@ -336,28 +336,31 @@
336	336
337	337	ACI2 channel current is 0x1300/1000=4.864mA
338	338
339		-The last byte 0xAA= **10101010**(b) means,
	324	+The last byte 0xAA= 10101010(b) means,
340	340
341		-* [1] The RO1 relay channel is CLOSED, and the RO1 LED is ON.
342		-* [0] The RO2 relay channel is OPEN, and the RO2 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.
343	343	* [1] DI3 - not used for LT-22222-L.
344		-* [0] DI2 channel input is LOW, and the DI2 LED is OFF.
	329	+* [0] DI2 channel input is low, and the DI2 LED is OFF.
345	345	* [1] DI1 channel input state:
346		-** DI1 is FLOATING when no sensor is connected between DI1+ and DI1-.
347		-** 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+.
348	348	** DI1 LED is ON in both cases.
349		-* [0] DO3 - not used for LT-22222-L.
350		-* [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.
351	351	* [0] DO1 channel output state:
352		-** DO1 is FLOATING when there is no load between DO1 and V+.
353		-** DO1 is HIGH when there is a load between DO1 and V+.
354		-** 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.
355	355
356	356	=== 3.3.2 AT+MOD~=2, (Double DI Counting) ===
357	357
358	358
359	359	(((
360		-**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.
361	361	)))
362	362
363	363	(((
...	...	@@ -371,17 +371,17 @@
371	371	)))
372	372
373	373	(((
374		-(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, 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.
375	375
376	376	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
377	377	|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
378	378	|RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1
379	379
380		-* RO is for the relay. ROx=1: CLOSED, ROx=0 always OPEN.
	368	+* RO is for relay. ROx=1 : closed, ROx=0 always open.
381	381	)))
382	382
383	383	* FIRST: Indicates that this is the first packet after joining the network.
384		-* 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.
385	385
386	386	(((
387	387	(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L**
...	...	@@ -390,7 +390,7 @@
390	390	)))
391	391
392	392	(((
393		-**To activate this mode, run the following AT commands:**
	381	+**To activate this mode, please run the following AT command:**
394	394	)))
395	395
396	396	(((
...	...	@@ -411,17 +411,17 @@
411	411	(((
412	412	**For LT22222-L:**
413	413
414		-(% 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) **
415	415
416		-(% 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) **
417	417
418		-(% 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) **
419	419
420		-(% 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) **
421	421
422		-(% 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)**
423	423
424		-(% 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)**
425	425	)))
426	426
427	427
...	...	@@ -439,7 +439,7 @@
439	439	)))|DIDORO*|Reserve|MOD
440	440
441	441	(((
442		-(% 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.
443	443
444	444	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
445	445	|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
...	...	@@ -446,17 +446,17 @@
446	446	|RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1
447	447	)))
448	448
449		-* RO is for the relay. ROx=1: closed, ROx=0 always open.
	437	+* RO is for relay. ROx=1 : closed, ROx=0 always open.
450	450	* FIRST: Indicates that this is the first packet after joining the network.
451	451	* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.
452	452
453	453	(((
454		-(% 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.**
455	455	)))
456	456
457	457
458	458	(((
459		-**To activate this mode, run the following AT commands:**
	447	+**To activate this mode, please run the following AT command:**
460	460	)))
461	461
462	462	(((
...	...	@@ -471,7 +471,7 @@
471	471	(((
472	472	AT Commands for counting:
473	473
474		-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'.
475	475	)))
476	476
477	477
...	...	@@ -493,7 +493,7 @@
493	493	)))
494	494
495	495	(((
496		-(% 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.
497	497
498	498	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
499	499	|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
...	...	@@ -500,18 +500,18 @@
500	500	|RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1
501	501	)))
502	502
503		-* RO is for the relay. ROx=1: closed, ROx=0 always open.
	491	+* RO is for relay. ROx=1 : closed, ROx=0 always open.
504	504	* FIRST: Indicates that this is the first packet after joining the network.
505	505	* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.
506	506
507	507	(((
508		-(% 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.**
509	509
510	510
511	511	)))
512	512
513	513	(((
514		-**To activate this mode, run the following AT commands:**
	502	+**To activate this mode, please run the following AT command:**
515	515	)))
516	516
517	517	(((
...	...	@@ -524,19 +524,19 @@
524	524	)))
525	525
526	526	(((
527		-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"]].
528	528	)))
529	529
530	530	(((
531	531	**In addition to that, below are the commands for AVI1 Counting:**
532	532
533		-(% 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)**
534	534
535	535	(% style="color:blue" %)**AT+VOLMAX=20000**(%%)**  (If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
536	536
537	537	(% style="color:blue" %)**AT+VOLMAX=20000,0**(%%)**  (If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
538	538
539		-(% 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)**
540	540	)))
541	541
542	542
...	...	@@ -543,7 +543,7 @@
543	543	=== 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI ===
544	544
545	545
546		-**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.
547	547
548	548	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
549	549	|(% 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**
...	...	@@ -558,25 +558,25 @@
558	558	)))|MOD
559	559
560	560	(((
561		-(% 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
562	562
563	563	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
564		-|**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**
565	565	|RO1|RO2|FIRST|Reserve|Reserve|DO3|DO2|DO1
566	566	)))
567	567
568		-* RO is for the relay. ROx=1: closed, ROx=0 always open.
569		-* 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.
570	570	* (((
571		-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.
572	572	)))
573	573
574	574	(((
575		-(% 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.**
576	576	)))
577	577
578	578	(((
579		-**To activate this mode, run the following AT commands:**
	567	+**To use this mode, please run:**
580	580	)))
581	581
582	582	(((
...	...	@@ -589,7 +589,7 @@
589	589	)))
590	590
591	591	(((
592		-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"]].
593	593	)))
594	594
595	595
...	...	@@ -596,46 +596,49 @@
596	596	=== 3.3.6 AT+ADDMOD~=6. (Trigger Mode, Optional) ===
597	597
598	598
599		-(% 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.**
600	600
601		-For example, if you configured the following commands:
	589	+For example, if user has configured below commands:
602	602
603	603	* **AT+MOD=1 ** **~-~->**  The normal working mode
604		-* **AT+ADDMOD6=1**   **~-~->**  Enable trigger mode
	592	+* **AT+ADDMOD6=1**   **~-~->**  Enable trigger
605	605
606		-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:
607	607
608		-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.
609		-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.**
610	610
611	611	(% style="color:#037691" %)**AT Command to set Trigger Condition**:
612	612
613		-(% style="color:#4f81bd" %)**Trigger based on voltage**:
614	614
	602	+(% style="color:#4f81bd" %)**Trigger base on voltage**:
	603	+
615	615	Format: AT+AVLIM=<AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH>
616	616
617	617
618	618	**Example:**
619	619
620		-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)
621	621
622		-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)
623	623
624	624
625		-(% style="color:#4f81bd" %)**Trigger based on current**:
626	626
	615	+(% style="color:#4f81bd" %)**Trigger base on current**:
	616	+
627	627	Format: AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH>
628	628
629	629
630	630	**Example:**
631	631
632		-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)
633	633
634	634
635		-(% style="color:#4f81bd" %)**Trigger based on DI status**:
636	636
637		-DI status triggers Flag.
	626	+(% style="color:#4f81bd" %)**Trigger base on DI status**:
638	638
	628	+DI status trigger Flag.
	629	+
639	639	Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >
640	640
641	641
...	...	@@ -644,38 +644,39 @@
644	644	AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
645	645
646	646
647		-(% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
	638	+(% style="color:#037691" %)**Downlink Command to set Trigger Condition:**
648	648
649	649	Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
650	650
651	651	Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
652	652
653		- AA: Type Code for this downlink Command:
	644	+ AA: Code for this downlink Command:
654	654
655		- 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
656	656
657		- 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.
658	658
659		- yy2 yy2: AC1 or AV1 HIGH limit.
	650	+ yy2 yy2: AC1 or AV1 high limit.
660	660
661		- yy3 yy3: AC2 or AV2 LOW limit.
	652	+ yy3 yy3: AC2 or AV2 low limit.
662	662
663		- Yy4 yy4: AC2 or AV2 HIGH limit.
	654	+ Yy4 yy4: AC2 or AV2 high limit.
664	664
665	665
666		-**Example 1**: AA 00 13 88 00 00 00 00 00 00
	657	+**Example1**: AA 00 13 88 00 00 00 00 00 00
667	667
668		-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)
669	669
670	670
671		-**Example 2**: AA 02 01 00
	662	+**Example2**: AA 02 01 00
672	672
673		-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)
674	674
675	675
	667	+
676	676	(% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:**
677	677
678		-MOD6 Payload: total of 11 bytes
	670	+MOD6 Payload : total 11 bytes payload
679	679
680	680	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
681	681	|(% 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**
...	...	@@ -689,10 +689,10 @@
689	689	MOD(6)
690	690	)))
691	691
692		-(% 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
693	693
694	694	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
695		-|**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**
696	696	|(((
697	697	AV1_LOW
698	698	)))|(((
...	...	@@ -711,17 +711,17 @@
711	711	AC2_HIGH
712	712	)))
713	713
714		-* Each bit shows if the corresponding trigger has been configured.
	706	+* Each bits shows if the corresponding trigger has been configured.
715	715
716	716	**Example:**
717	717
718		-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
719	719
720	720
721		-(% 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
722	722
723	723	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
724		-|**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**
725	725	|(((
726	726	AV1_LOW
727	727	)))|(((
...	...	@@ -740,11 +740,11 @@
740	740	AC2_HIGH
741	741	)))
742	742
743		-* Each bit shows which status has been triggered on this uplink.
	735	+* Each bits shows which status has been trigger on this uplink.
744	744
745	745	**Example:**
746	746
747		-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.
748	748
749	749
750	750	(% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
...	...	@@ -753,7 +753,7 @@
753	753	|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
754	754	|N/A|N/A|N/A|N/A|DI2_STATUS|DI2_FLAG|DI1_STATUS|DI1_FLAG
755	755
756		-* Each bits shows which status has been triggered on this uplink.
	748	+* Each bits shows which status has been trigger on this uplink.
757	757
758	758	**Example:**
759	759
...	...	@@ -780,11 +780,11 @@
780	780	)))
781	781
782	782
783		-== 3.4 ​Configure LT via AT Commands or Downlinks ==
	775	+== 3.4 ​Configure LT via AT or Downlink ==
784	784
785	785
786	786	(((
787		-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
788	788	)))
789	789
790	790	(((
...	...	@@ -799,8 +799,9 @@
799	799
800	800	=== 3.4.1 Common Commands ===
801	801
	794	+
802	802	(((
803		-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]]
804	804	)))
805	805
806	806
...	...	@@ -808,37 +808,34 @@
808	808
809	809	==== 3.4.2.1 Set Transmit Interval ====
810	810
811		-Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
812	812
813		-* (% style="color:#037691" %)**AT command:**
	805	+Set device uplink interval.
814	814
815		-(% style="color:blue" %)**AT+TDC=N**
	807	+* (% style="color:#037691" %)**AT Command:**
816	816
817		-where N is the time in milliseconds.
	809	+(% style="color:blue" %)**AT+TDC=N **
818	818
819		-**Example: **AT+TDC=30000. This will set the uplink interval to 30 seconds
820	820
	812	+**Example: **AT+TDC=30000. Means set interval to 30 seconds
821	821
822		-* (% style="color:#037691" %)**Downlink payload (prefix 0x01):**
823	823
	815	+* (% style="color:#037691" %)**Downlink Payload (prefix 0x01):**
	816	+
824	824	(% style="color:blue" %)**0x01 aa bb cc  **(%%)** ~/~/ Same as AT+TDC=0x(aa bb cc)**
825	825
826	826
827	827
828		-==== 3.4.2.2 Set the Work Mode (AT+MOD) ====
	821	+==== 3.4.2.2 Set Work Mode (AT+MOD) ====
829	829
830	830
831		-Sets the work mode.
	824	+Set work mode.
832	832
833		-* (% style="color:#037691" %)**AT command:**(%%) (% style="color:blue" %)**AT+MOD=N  **
	826	+* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+MOD=N  **
834	834
835		-Where N is the work mode.
	828	+**Example**: AT+MOD=2. Set work mode to Double DI counting mode
836	836
837		-**Example**: AT+MOD=2. This will set the work mode to Double DI counting mode.
	830	+* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A):**
838	838
839		-
840		-* (% style="color:#037691" %)**Downlink payload (prefix 0x0A):**
841		-
842	842	(% style="color:blue" %)**0x0A aa  **(%%)** ** ~/~/ Same as AT+MOD=aa
843	843
844	844
...	...	@@ -846,12 +846,10 @@
846	846	==== 3.4.2.3 Poll an uplink ====
847	847
848	848
849		-Asks the device to send an uplink.
	839	+* (% style="color:#037691" %)**AT Command:**(%%) There is no AT Command to poll uplink
850	850
851		-* (% style="color:#037691" %)**AT command:**(%%) There is no AT Command to poll uplink
	841	+* (% style="color:#037691" %)**Downlink Payload (prefix 0x08):**
852	852
853		-* (% style="color:#037691" %)**Downlink payload (prefix 0x08):**
854		-
855	855	(% style="color:blue" %)**0x08 FF  **(%%)** **~/~/ Poll an uplink
856	856
857	857	**Example**: 0x08FF, ask device to send an Uplink
...	...	@@ -858,16 +858,16 @@
858	858
859	859
860	860
861		-==== 3.4.2.4 Enable/Disable Trigger Mode ====
	849	+==== 3.4.2.4 Enable Trigger Mode ====
862	862
863	863
864		-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"]]
865	865
866	866	* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0**
867	867
868		-(% style="color:red" %)**1:** (%%)Enable the trigger mode
	856	+(% style="color:red" %)**1:** (%%)Enable Trigger Mode
869	869
870		-(% style="color:red" %)**0: **(%%)Disable the trigger mode
	858	+(% style="color:red" %)**0: **(%%)Disable Trigger Mode
871	871
872	872
873	873	* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A 06):**
...	...	@@ -879,7 +879,7 @@
879	879	==== 3.4.2.5 Poll trigger settings ====
880	880
881	881
882		-Polls the trigger settings
	870	+Poll trigger settings
883	883
884	884	* (% style="color:#037691" %)**AT Command:**
885	885
...	...	@@ -887,7 +887,7 @@
887	887
888	888	* (% style="color:#037691" %)**Downlink Payload (prefix 0x AB 06):**
889	889
890		-(% 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
891	891
892	892
893	893
...	...	@@ -894,11 +894,11 @@
894	894	==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ====
895	895
896	896
897		-Enable or Disable DI1/DI2/DI2 as trigger,
	885	+Enable Disable DI1/DI2/DI2 as trigger,
898	898
899	899	* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
900	900
901		-**Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
	889	+**Example:** AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
902	902
903	903
904	904	* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 02):**
...	...	@@ -930,15 +930,15 @@
930	930	==== 3.4.2.8 Trigger2 – Set DI2 as trigger ====
931	931
932	932
933		-Sets DI2 trigger.
	921	+Set DI2 trigger.
934	934
935	935	* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b**
936	936
937		-(% 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).
938	938
939	939	(% style="color:red" %)**b :** (%%)delay timing.
940	940
941		-**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 )
942	942
943	943
944	944	* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 02 ):**
...	...	@@ -976,7 +976,7 @@
976	976	==== 3.4.2.11 Trigger – Set minimum interval ====
977	977
978	978
979		-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.
980	980
981	981	* (% 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.
982	982
...	...	@@ -1124,7 +1124,7 @@
1124	1124	)))
1125	1125
1126	1126	(((
1127		-00: Closed ,  01: Open , 11: No action
	1115	+00: Close ,  01: Open , 11: No action
1128	1128
1129	1129	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %)
1130	1130	|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**RO1**|(% style="background-color:#4f81bd; color:white" %)**RO2**
...	...	@@ -1246,7 +1246,7 @@
1246	1246
1247	1247
1248	1248
1249		-==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
	1237	+==== 3.4.2.19 Counting ~-~- Change counting mode save time ====
1250	1250
1251	1251
1252	1252	* (% style="color:#037691" %)**AT Command:**
...	...	@@ -1369,128 +1369,75 @@
1369	1369
1370	1370	== 3.5 Integrating with ThingsEye.io ==
1371	1371
1372		-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.
1373	1373
1374		-=== 3.5.1 Configuring MQTT Connection Information with The Things Stack Sandbox ===
	1362	+=== 3.5.1 Configuring The Things Stack Sandbox ===
1375	1375
1376		-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.
1377	1377
1378		-* In **The Things Stack Sandbox**, select your application under **Applications**.
1379		-* Select **MQTT** under **Integrations**.
1380		-* In the **Connection information **section, for **Username**, The Things Stack displays an auto-generated username. You can use it or provide a new one.
1381		-* 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.
1382		-
1383		-NOTE. The username and  password (API key) you created here are required in the next section.
1384		-
1385	1385	[[image:tts-mqtt-integration.png||height="625" width="1000"]]
1386	1386
1387	1387	=== 3.5.2 Configuring ThingsEye.io ===
1388	1388
1389		-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).
1390	1390
1391		-* Login to your [[ThingsEye.io >>https://thingseye.io]]account.
1392		-* Under the **Integrations center**, click **Integrations**.
1393		-* Click the **Add integration** button (the button with the **+** symbol).
1394		-
1395	1395	[[image:thingseye-io-step-1.png||height="625" width="1000"]]
1396	1396
1397	1397
1398		-On the **Add integration** window, configure the following:
	1379	+On the Add integration page configure the following:
1399	1399
1400		-**Basic settings:**
	1381	+Basic settings:
1401	1401
1402		-* Select **The Things Stack Community** from the **Integration type** list.
1403		-* Enter a suitable name for your integration in the **Name **text** **box or keep the default name.
1404		-* Ensure the following options are turned on.
1405		-** Enable integration
1406		-** Debug mode
1407		-** Allow create devices or assets
1408		-* 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.
1409	1409
1410	1410	[[image:thingseye-io-step-2.png||height="625" width="1000"]]
1411	1411
	1389	+Uplink Data converter:
1412	1412
1413		-**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.
1414	1414
1415		-* Click the **Create new** button if it is not selected by default.
1416		-* Enter a suitable name for the uplink data converter in the **Name **text** **box or keep the default name.
1417		-* Click the **JavaScript** button.
1418		-* 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]].
1419		-* Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
1420		-
1421	1421	[[image:thingseye-io-step-3.png||height="625" width="1000"]]
1422	1422
	1398	+Downlink Data converter (this is an optional step):
1423	1423
1424		-**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.
1425	1425
1426		-* Click the **Create new** button if it is not selected by default.
1427		-* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name
1428		-* Click the **JavaScript** button.
1429		-* Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found here.
1430		-* Click the **Next** button. You will be navigated to the **Connection** tab.
1431		-
1432	1432	[[image:thingseye-io-step-4.png||height="625" width="1000"]]
1433	1433
	1407	+Connection:
1434	1434
1435		-**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.
1436	1436
1437		-* Choose **Region** from the **Host type**.
1438		-* 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/...).
1439		-* 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).
1440		-* Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
1441		-
1442		-[[image:message-1.png]]
1443		-
1444		-
1445		-* Click the **Add** button.
1446		-
1447	1447	[[image:thingseye-io-step-5.png||height="625" width="1000"]]
1448	1448
1449	1449
1450		-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.
1451	1451
	1420	+[[image:thingseye-io-step-6.png||height="625" width="1000"]]
1452	1452
1453		-[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
1454	1454
1455		-
1456		-**Viewing integration details**:
1457		-
1458		-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.
1459		-
1460		-[[image:integration-details.png||height="686" width="1000"]]
1461		-
1462		-
1463		-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.
1464		-
1465		-Note: See also ThingsEye documentation.
1466		-
1467		-
1468		-**Viewing events:**
1469		-
1470		-This tab  displays all the uplink messages from the LT-22222-L.
1471		-
1472		-* Click on the **Events **tab.
1473		-* Select **Debug **from the **Event type** dropdown.
1474		-* Select the** time frame** from the **time window**.
1475		-
1476		-[insert image]
1477		-
1478		-- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
1479		-
1480		-[insert image]
1481		-
1482		-
1483		-**Deleting the integration**:
1484		-
1485		-If you want to delete this integration, click the **Delete integratio**n button.
1486		-
1487		-
1488	1488	== 3.6 Interface Details ==
1489	1489
1490	1490	=== 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) ===
1491	1491
1492	1492
1493		-Support NPN-type sensor
	1428	+Support NPN Type sensor
1494	1494
1495	1495	[[image:1653356991268-289.png]]
1496	1496
...	...	@@ -1504,7 +1504,7 @@
1504	1504
1505	1505	(((
1506	1506	(((
1507		-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	+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.
1508	1508
1509	1509
1510	1510	)))
...	...	@@ -1523,11 +1523,11 @@
1523	1523	)))
1524	1524
1525	1525	(((
1526		-(% style="color:#0000ff" %)**Example 1**(%%): Connecting to a low-active sensor.
	1461	+(% style="color:blue" %)**Example1**(%%): Connecting to a low-active sensor.
1527	1527	)))
1528	1528
1529	1529	(((
1530		-This type of sensor outputs a low (GND) signal when active.
	1465	+This type of sensors outputs a low (GND) signal when active.
1531	1531	)))
1532	1532
1533	1533	* (((
...	...	@@ -1554,11 +1554,11 @@
1554	1554	)))
1555	1555
1556	1556	(((
1557		-(% style="color:#0000ff" %)**Example 2**(%%): Connecting to a high-active sensor.
	1492	+(% style="color:blue" %)**Example2**(%%): Connecting to a high-active sensor.
1558	1558	)))
1559	1559
1560	1560	(((
1561		-This type of sensor outputs a high signal (e.g., 24V) when active.
	1496	+This type of sensors outputs a high signal (e.g., 24V) when active.
1562	1562	)))
1563	1563
1564	1564	* (((
...	...	@@ -1577,7 +1577,7 @@
1577	1577	)))
1578	1578
1579	1579	(((
1580		-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 resulting current[[image:1653968155772-850.png||height="23" width="19"]] 24mA , Therefore, the LT-22222-L will detect this high-active signal.
1581	1581	)))
1582	1582
1583	1583	(((
...	...	@@ -1585,7 +1585,7 @@
1585	1585	)))
1586	1586
1587	1587	(((
1588		-(% style="color:#0000ff" %)**Example 3**(%%): Connecting to a 220V high-active sensor.
	1523	+(% style="color:blue" %)**Example3**(%%): Connecting to a 220V high-active sensor.
1589	1589	)))
1590	1590
1591	1591	(((
...	...	@@ -1608,13 +1608,13 @@
1608	1608	)))
1609	1609
1610	1610	(((
1611		-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 the sensor output is 220V, then [[image:1653968155772-850.png||height="23" width="19"]](% id="cke_bm_243359S" style="display:none" %)[[image:image-20220524095628-8.png]](%%) = DI1+ / 51K.  = 4.3mA. Therefore, the LT-22222-L will be able to safely detect this high-active signal.
1612	1612	)))
1613	1613
1614	1614
1615	1615	(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
1616	1616
1617		-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 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.
1618	1618
1619	1619	To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram.
1620	1620
...	...	@@ -1630,7 +1630,7 @@
1630	1630
1631	1631	(% style="color:blue" %)**NPN output**(%%): GND or Float. The maximum voltage that can be applied to the output pin is 36V.
1632	1632
1633		-(% style="color:red" %)**Note: The DO pins will float when the device is powered off.**
	1568	+(% style="color:red" %)**Note: The DO pins will float when device is powered off.**
1634	1634
1635	1635	[[image:1653357531600-905.png]]
1636	1636
...	...	@@ -1715,17 +1715,17 @@
1715	1715	Transmit a LoRa packet: TX blinks once
1716	1716	)))
1717	1717	)))
1718		-|**RX**|RX blinks once when receiving a packet.
1719		-|**DO1**|For LT-22222-L: ON when DO1 is low, OFF when DO1 is high
1720		-|**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
1721	1721	|**DI1**|(((
1722		-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
1723	1723	)))
1724	1724	|**DI2**|(((
1725		-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
1726	1726	)))
1727		-|**RO1**|For LT-22222-L: ON when RO1 is closed, OFF when RO1 is open
1728		-|**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
1729	1729
1730	1730	= 4. Using AT Command =
1731	1731
...	...	@@ -2077,10 +2077,10 @@
2077	2077
2078	2078	= 5. Case Study =
2079	2079
2080		-== 5.1 Counting how many objects pass through the flow Line ==
	2015	+== 5.1 Counting how many objects pass in Flow Line ==
2081	2081
2082	2082
2083		-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]]?
	2018	+Reference Link: [[How to set up to count objects pass in flow line>>How to set up to count objects pass in flow line]]?
2084	2084
2085	2085
2086	2086	= 6. FAQ =
...	...	@@ -2088,26 +2088,26 @@
2088	2088	== 6.1 How to upgrade the image? ==
2089	2089
2090	2090
2091		-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:
	2026	+The LT LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to LT to:
2092	2092
2093		-* Support new features.
2094		-* Fix bugs.
	2028	+* Support new features
	2029	+* For bug fix
2095	2095	* Change LoRaWAN bands.
2096	2096
2097		-Below is the hardware connection setup for uploading an image to the LT:
	2032	+Below shows the hardware connection for how to upload an image to the LT:
2098	2098
2099	2099	[[image:1653359603330-121.png]]
2100	2100
2101	2101
2102	2102	(((
2103		-(% 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]].
2104		-(% 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]].
2105		-(% style="color:#0000ff" %)**Step 3**(%%)**:** Open the Flash Loader and choose the correct COM port to update.
	2038	+(% 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]].
	2039	+(% 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]].
	2040	+(% style="color:blue" %)**Step3**(%%)**:** Open flashloader; choose the correct COM port to update.
2106	2106
2107	2107
2108	2108	(((
2109	2109	(% style="color:blue" %)**For LT-22222-L**(%%):
2110		-Hold down the PRO button, then momentarily press the RST reset button. The (% style="color:red" %)**DO1 LED**(%%) will change from OFF to ON. When the (% style="color:red" %)**DO1 LED**(%%) is ON, it indicates that the device is in download mode.
	2045	+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.
2111	2111	)))
2112	2112
2113	2113
...	...	@@ -2122,7 +2122,7 @@
2122	2122	[[image:image-20220524104033-15.png]]
2123	2123
2124	2124
2125		-(% 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:
	2060	+(% 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:
2126	2126
2127	2127	[[image:1653360054704-518.png||height="186" width="745"]]
2128	2128
...	...	@@ -2136,13 +2136,13 @@
2136	2136	)))
2137	2137
2138	2138	(((
2139		-You can follow the introductions on [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloading, select the required image file.
	2074	+User can follow the introduction for [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
2140	2140	)))
2141	2141
2142	2142	(((
2143	2143
2144	2144
2145		-== 6.3 How to set up LT to work with a Single Channel Gateway, such as LG01/LG02? ==
	2080	+== 6.3 How to set up LT to work with Single Channel Gateway such as LG01/LG02? ==
2146	2146
2147	2147
2148	2148	)))
...	...	@@ -2149,13 +2149,13 @@
2149	2149
2150	2150	(((
2151	2151	(((
2152		-In this case, you need to set the LT-33222-L to work in ABP mode and transmit on only one frequency.
	2087	+In this case, users need to set LT-33222-L to work in ABP mode & transmit in only one frequency.
2153	2153	)))
2154	2154	)))
2155	2155
2156	2156	(((
2157	2157	(((
2158		-Assume you have an LG02 working on the frequency 868400000. Below are the steps.
	2093	+Assume we have a LG02 working in the frequency 868400000 now , below is the step.
2159	2159
2160	2160
2161	2161	)))
...	...	@@ -2162,7 +2162,7 @@
2162	2162	)))
2163	2163
2164	2164	(((
2165		-(% 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.
	2100	+(% 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.
2166	2166
2167	2167
2168	2168	)))
...	...	@@ -2219,7 +2219,7 @@
2219	2219	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/]]
2220	2220
2221	2221
2222		-== 6.5 Can I see the counting event in Serial? ==
	2157	+== 6.5 Can I see counting event in Serial? ==
2223	2223
2224	2224
2225	2225	(((
...	...	@@ -2226,10 +2226,10 @@
2226	2226	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.
2227	2227
2228	2228
2229		-== 6.6 Can I use point-to-point communication with LT-22222-L? ==
	2164	+== 6.6 Can i use point to point communication for LT-22222-L? ==
2230	2230
2231	2231
2232		-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]].
	2167	+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]].
2233	2233
2234	2234
2235	2235	)))

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