Summary

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

Details

Page properties

Content

...	...	@@ -162,9 +162,6 @@
162	162
163	163	)))
164	164
165		-
166		-
167		-
168	168	== 1.3 Features ==
169	169
170	170	* LoRaWAN Class A & Class C protocol
...	...	@@ -175,9 +175,6 @@
175	175	* Firmware upgradable via program port
176	176	* Counting
177	177
178		-
179		-
180		-
181	181	== 1.4  Applications ==
182	182
183	183	* Smart Buildings & Home Automation
...	...	@@ -187,9 +187,6 @@
187	187	* Smart Cities
188	188	* Smart Factory
189	189
190		-
191		-
192		-
193	193	== 1.5 Hardware Variants ==
194	194
195	195	(% border="1" style="background-color:#f7faff; width:500px" %)
...	...	@@ -203,8 +203,6 @@
203	203	* 1 x Counting Port
204	204	)))
205	205
206		-
207		-
208	208	= 2. Power ON Device =
209	209
210	210	The LT controller can be powered by 7 ~~ 24V DC power source. Connect VIN to Power Input V+ and GND to power input V- to power the LT controller.
...	...	@@ -227,9 +227,12 @@
227	227
228	228	(((
229	229	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	+
230	230	)))
231	231
232	232
	224	+
233	233	== 3.2 Example to join LoRaWAN network ==
234	234
235	235	(((
...	...	@@ -238,13 +238,12 @@
238	238
239	239	[[image:image-20220523172350-1.png||height="266" width="864"]]
240	240
241		-
242	242	(((
243	243	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:
244	244	)))
245	245
246	246	(((
247		-(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LT IO controller.
	238	+**Step 1**: Create a device in TTN with the OTAA keys from LT IO controller.
248	248	)))
249	249
250	250	(((
...	...	@@ -253,7 +253,6 @@
253	253
254	254	[[image:1653297924498-393.png]]
255	255
256		-
257	257	Input these keys in the LoRaWAN Server portal. Below is TTN screen shot:
258	258
259	259	Add APP EUI in the application.
...	...	@@ -267,7 +267,7 @@
267	267
268	268
269	269	(((
270		-(% 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	+**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.
271	271	)))
272	272
273	273	[[image:1653298044601-602.png||height="405" width="709"]]
...	...	@@ -326,6 +326,7 @@
326	326	* [0] RO2 relay channel is open and RO2 LED is OFF;
327	327
328	328
	319	+
329	329	**LT22222-L:**
330	330
331	331	* [1] DI2 channel is high input and DI2 LED is ON;
...	...	@@ -635,6 +635,7 @@
635	635	* **AT+MOD=1 ** **~-~->** The normal working mode
636	636	* **AT+ADDMOD6=1**   **~-~->** Enable trigger
637	637
	629	+
638	638	LT will keep monitoring AV1/AV2/AC1/AC2 every 5 seconds; LT will send uplink packets in two cases:
639	639
640	640	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
...	...	@@ -641,6 +641,7 @@
641	641	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.**
642	642
643	643
	636	+
644	644	**AT Command to set Trigger Condition**:
645	645
646	646	(% style="color:#4f81bd" %)**Trigger base on voltage**:
...	...	@@ -721,6 +721,7 @@
721	721	* Each bits shows if the corresponding trigger has been configured.
722	722
723	723
	717	+
724	724	**Example:**
725	725
726	726	10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW
...	...	@@ -733,6 +733,7 @@
733	733	* Each bits shows which status has been trigger on this uplink.
734	734
735	735
	730	+
736	736	**Example:**
737	737
738	738	10000000: Means this packet is trigger by AC1_LOW. Means voltage too low.
...	...	@@ -745,6 +745,7 @@
745	745	* Each bits shows which status has been trigger on this uplink.
746	746
747	747
	743	+
748	748	**Example:**
749	749
750	750	00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
...	...	@@ -787,6 +787,7 @@
787	787	* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L.  User can see these commands below:
788	788
789	789
	786	+
790	790	=== 3.4.1 Common Commands ===
791	791
792	792	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]]