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"]]
...	...	@@ -285,8 +285,6 @@
285	285	* **MOD5**: Single DI Counting + 2 x AVI + 1 x ACI + DO + RO
286	286	* **ADDMOD6**: Trigger Mode, Optional, used together with MOD1 ~~ MOD5
287	287
288		-
289		-
290	290	=== 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
291	291
292	292	The uplink payload includes totally 9 bytes. Uplink packets use FPORT=2 and every 10 minutes send one uplink by default.
...	...	@@ -294,8 +294,6 @@
294	294	[[image:image-20220523174024-3.png]]
295	295
296	296	(((
297		-
298		-
299	299	(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below
300	300	)))
301	301
...	...	@@ -309,7 +309,6 @@
309	309
310	310	For example if payload is: [[image:image-20220523175847-2.png]]
311	311
312		-
313	313	**The value for the interface is:  **
314	314
315	315	AVI1 channel voltage is 0x04AB/1000=1195（DEC）/1000=1.195V
...	...	@@ -325,7 +325,6 @@
325	325	* [1] RO1 relay channel is close and the RO1 LED is ON.
326	326	* [0] RO2 relay channel is open and RO2 LED is OFF;
327	327
328		-
329	329	**LT22222-L:**
330	330
331	331	* [1] DI2 channel is high input and DI2 LED is ON;
...	...	@@ -341,11 +341,8 @@
341	341	** DO1 is high in case there is load between DO1 and V+.
342	342	** DO1 LED is off in both case
343	343
344		-
345		-
346	346	=== 3.3.2 AT+MOD~=2, (Double DI Counting) ===
347	347
348		-
349	349	**For LT-22222-L**: this mode the **DI1 and DI2** are used as counting pins.
350	350
351	351	(((
...	...	@@ -354,7 +354,6 @@
354	354
355	355	[[image:image-20220523180452-3.png]]
356	356
357		-
358	358	(((
359	359	(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DO3, DO2 and DO1. Totally 1bytes as below
360	360	)))
...	...	@@ -370,8 +370,6 @@
370	370	)))
371	371
372	372	(((
373		-
374		-
375	375	**To use counting mode, please run:**
376	376	)))
377	377
...	...	@@ -390,8 +390,6 @@
390	390	)))
391	391
392	392	(((
393		-
394		-
395	395	(% style="color:#4f81bd" %)**AT Commands for counting:**
396	396	)))
397	397
...	...	@@ -488,6 +488,7 @@
488	488	)))
489	489
490	490
	467	+
491	491	=== 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting ===
492	492
493	493
...	...	@@ -627,7 +627,6 @@
627	627
628	628	=== 3.3.6 AT+ADDMOD~=6. (Trigger Mode, Optional) ===
629	629
630		-
631	631	(% style="color:#4f81bd" %)**This mode is an optional mode for trigger purpose. It can run together with other mode.**
632	632
633	633	For example, if user has configured below commands:
...	...	@@ -635,6 +635,7 @@
635	635	* **AT+MOD=1 ** **~-~->** The normal working mode
636	636	* **AT+ADDMOD6=1**   **~-~->** Enable trigger
637	637
	614	+
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
...	...	@@ -654,7 +654,6 @@
654	654	AT+AVLIM=5000,0,0,0   (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore)
655	655
656	656
657		-
658	658	(% style="color:#4f81bd" %)**Trigger base on current**:
659	659
660	660	Format: AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH>
...	...	@@ -664,7 +664,6 @@
664	664	AT+ACLIM=10000,15000,0,0   (If ACI1 voltage lower than 10mA or higher than 15mA, trigger an uplink)
665	665
666	666
667		-
668	668	(% style="color:#4f81bd" %)**Trigger base on DI status**:
669	669
670	670	DI status trigger Flag.
...	...	@@ -671,13 +671,12 @@
671	671
672	672	Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >
673	673
674		-
675	675	**Example:**
676	676
677	677	AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
678	678
679	679
680		-**Downlink Command to set Trigger Condition:**
	654	+**Downlink Command to set Trigger Condition**
681	681
682	682	Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
683	683
...	...	@@ -706,7 +706,6 @@
706	706	Same as AT+ DTRI =1,0  (Enable DI1 trigger / disable DI2 trigger)
707	707
708	708
709		-
710	710	(% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:**
711	711
712	712	MOD6 Payload : total 11 bytes payload
...	...	@@ -765,8 +765,6 @@
765	765	=== 3.3.7 Payload Decoder ===
766	766
767	767	(((
768		-
769		-
770	770	**Decoder for TTN/loraserver/ChirpStack**: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/Payload_decoder/>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/Payload_decoder/]]
771	771
772	772
...	...	@@ -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
	761	+
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]]