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"]]
...	...	@@ -277,6 +277,7 @@
277	277	* **ADDMOD6**: Trigger Mode, Optional, used together with MOD1 ~~ MOD5
278	278
279	279
	279	+
280	280	=== 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
281	281
282	282	The uplink payload includes totally 9 bytes. Uplink packets use FPORT=2 and every 10 minutes send one uplink by default.
...	...	@@ -333,6 +333,7 @@
333	333	** DO1 LED is off in both case
334	334
335	335
	336	+
336	336	=== 3.3.2 AT+MOD~=2, (Double DI Counting) ===
337	337
338	338
...	...	@@ -478,7 +478,6 @@
478	478	)))
479	479
480	480
481		-
482	482	=== 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting ===
483	483
484	484
...	...	@@ -626,11 +626,14 @@
626	626	* **AT+MOD=1 ** **~-~->** The normal working mode
627	627	* **AT+ADDMOD6=1**   **~-~->** Enable trigger
628	628
	629	+
629	629	LT will keep monitoring AV1/AV2/AC1/AC2 every 5 seconds; LT will send uplink packets in two cases:
630	630
631	631	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
632	632	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.**
633	633
	635	+
	636	+
634	634	**AT Command to set Trigger Condition**:
635	635
636	636	(% style="color:#4f81bd" %)**Trigger base on voltage**:
...	...	@@ -710,6 +710,8 @@
710	710
711	711	* Each bits shows if the corresponding trigger has been configured.
712	712
	716	+
	717	+
713	713	**Example:**
714	714
715	715	10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW
...	...	@@ -721,6 +721,8 @@
721	721
722	722	* Each bits shows which status has been trigger on this uplink.
723	723
	729	+
	730	+
724	724	**Example:**
725	725
726	726	10000000: Means this packet is trigger by AC1_LOW. Means voltage too low.
...	...	@@ -732,6 +732,8 @@
732	732
733	733	* Each bits shows which status has been trigger on this uplink.
734	734
	742	+
	743	+
735	735	**Example:**
736	736
737	737	00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
...	...	@@ -773,6 +773,8 @@
773	773
774	774	* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L.  User can see these commands below:
775	775
	785	+
	786	+
776	776	=== 3.4.1 Common Commands ===
777	777
778	778	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]]