Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -76,8 +76,6 @@
76	76	)))
77	77
78	78	(((
79		-
80		-
81	81	**Interface for Model: LT22222-L:**
82	82	)))
83	83
...	...	@@ -101,8 +101,6 @@
101	101	)))
102	102
103	103	(((
104		-
105		-
106	106	**LoRa Spec:**
107	107	)))
108	108
...	...	@@ -162,6 +162,8 @@
162	162	)))
163	163	* (((
164	164	Packet engine up to 256 bytes with CRC.
	161	+
	162	+
165	165	)))
166	166
167	167	== 1.3 Features ==
...	...	@@ -218,9 +218,12 @@
218	218
219	219	(((
220	220	In case user can’t set the OTAA keys in the network server and has to use the existing keys from server. User can [[use AT Command>>||anchor="H4.UseATCommand"]] to set the keys in the devices.
	219	+
	220	+
221	221	)))
222	222
223	223
	224	+
224	224	== 3.2 Example to join LoRaWAN network ==
225	225
226	226	(((
...	...	@@ -229,13 +229,12 @@
229	229
230	230	[[image:image-20220523172350-1.png||height="266" width="864"]]
231	231
232		-
233	233	(((
234	234	The LG308 is already set to connect to [[TTN network >>url:https://www.thethingsnetwork.org/]]. So what we need to do now is only configure register this device to TTN:
235	235	)))
236	236
237	237	(((
238		-(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LT IO controller.
	238	+**(% style="color:blue" %)Step 1**(%%): Create a device in TTN with the OTAA keys from LT IO controller.
239	239	)))
240	240
241	241	(((
...	...	@@ -244,7 +244,6 @@
244	244
245	245	[[image:1653297924498-393.png]]
246	246
247		-
248	248	Input these keys in the LoRaWAN Server portal. Below is TTN screen shot:
249	249
250	250	Add APP EUI in the application.
...	...	@@ -258,7 +258,7 @@
258	258
259	259
260	260	(((
261		-(% style="color:blue" %)**Step 2**(%%): Power on LT and it will auto join to the TTN network. After join success, it will start to upload message to TTN and user can see in the panel.
	260	+**(% style="color:blue" %)Step 2**(%%): Power on LT and it will auto join to the TTN network. After join success, it will start to upload message to TTN and user can see in the panel.
262	262	)))
263	263
264	264	[[image:1653298044601-602.png||height="405" width="709"]]
...	...	@@ -276,6 +276,8 @@
276	276	* **MOD5**: Single DI Counting + 2 x AVI + 1 x ACI + DO + RO
277	277	* **ADDMOD6**: Trigger Mode, Optional, used together with MOD1 ~~ MOD5
278	278
	278	+
	279	+
279	279	=== 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
280	280
281	281	The uplink payload includes totally 9 bytes. Uplink packets use FPORT=2 and every 10 minutes send one uplink by default.
...	...	@@ -315,6 +315,7 @@
315	315	* [0] RO2 relay channel is open and RO2 LED is OFF;
316	316
317	317
	319	+
318	318	**LT22222-L:**
319	319
320	320	* [1] DI2 channel is high input and DI2 LED is ON;
...	...	@@ -330,6 +330,8 @@
330	330	** DO1 is high in case there is load between DO1 and V+.
331	331	** DO1 LED is off in both case
332	332
	335	+
	336	+
333	333	=== 3.3.2 AT+MOD~=2, (Double DI Counting) ===
334	334
335	335
...	...	@@ -470,10 +470,11 @@
470	470
471	471	(((
472	472	Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]].
	477	+
	478	+
473	473	)))
474	474
475	475
476		-
477	477	=== 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting ===
478	478
479	479
...	...	@@ -621,11 +621,14 @@
621	621	* **AT+MOD=1 ** **~-~->** The normal working mode
622	622	* **AT+ADDMOD6=1**   **~-~->** Enable trigger
623	623
	629	+
624	624	LT will keep monitoring AV1/AV2/AC1/AC2 every 5 seconds; LT will send uplink packets in two cases:
625	625
626	626	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
627	627	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.**
628	628
	635	+
	636	+
629	629	**AT Command to set Trigger Condition**:
630	630
631	631	(% style="color:#4f81bd" %)**Trigger base on voltage**:
...	...	@@ -705,6 +705,8 @@
705	705
706	706	* Each bits shows if the corresponding trigger has been configured.
707	707
	716	+
	717	+
708	708	**Example:**
709	709
710	710	10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW
...	...	@@ -716,6 +716,8 @@
716	716
717	717	* Each bits shows which status has been trigger on this uplink.
718	718
	729	+
	730	+
719	719	**Example:**
720	720
721	721	10000000: Means this packet is trigger by AC1_LOW. Means voltage too low.
...	...	@@ -727,6 +727,8 @@
727	727
728	728	* Each bits shows which status has been trigger on this uplink.
729	729
	742	+
	743	+
730	730	**Example:**
731	731
732	732	00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
...	...	@@ -755,6 +755,7 @@
755	755	)))
756	756
757	757
	772	+
758	758	== 3.4 ​Configure LT via AT or Downlink ==
759	759
760	760	User can configure LT I/O Controller via AT Commands or LoRaWAN Downlink Commands