Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 13 added, 0 removed)
  • image-20220527161119-1.png
  • image-20220527161149-2.png
  • image-20220527162450-3.png
  • image-20220527162518-4.png
  • image-20220527162552-5.png
  • image-20220527162619-6.png
  • image-20220527162648-7.png
  • image-20220527162852-8.png
  • image-20220527163028-9.png
  • image-20220527163106-10.png
  • image-20220527163144-11.png
  • image-20220722115133-1.png
  • image-20220722115213-2.png

Details

Page properties

Content

...	...	@@ -1,105 +1,146 @@
1		- **Contents:**
	1	+**Table of Contents:**
2	2
3	3	{{toc/}}
4	4
5	5
	6	+
6	6	= 1. Introduction =
7	7
	9	+
8	8	The Dragino LoRaWAN gateway can commuicate with LoRaWAN ABP End Node without the need of LoRaWAN server. It can be used in some cases such as:
9	9
10	10	* No internet connection.
11		-* User wants to get data forward in gateway and forward to their server base on MQTT/HTTP, etc. (Combine ABP communication method and [[MQTT forward together>>url:https://wiki.dragino.com/index.php/MQTT_Forward_Instruction]]).
12	12
	14	+* User wants to get data forward in gateway and forward to their server base on MQTT/HTTP, etc. (Combine ABP communication method and [[MQTT forward together>>MQTT Forward Instruction]]).
13	13
14		-The basic of this feature is the decoding of LoRaWAN ABP End Node. Requirements:
	16	+(((
	17	+The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements:
	18	+)))
15	15
16		-1. LoRaWAN End Node in ABP mode. Make sure your end node works in this mode. End node most are default set to OTAA mode
17		-1. LoRaWAN Gateway model: [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] ,[[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]]
18		-1. Firmware version for below instruction:[[Since LG02_LG08~~-~~-build-v5.4.1593400722-20200629-1120>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
	20	+* LoRaWAN End Node in ABP mode. Make sure your end node works in this mode. End node most are default set to OTAA mode
19	19
	22	+* LoRaWAN Gateway model: [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] ,[[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]]
20	20
	24	+* Firmware version for below instruction:  **[[(% style="color:purple" %)Since LG02_LG08~~-~~-build-v5.4.1593400722-20200629-1120>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]](%%)**
	25	+
	26	+
	27	+
21	21	= 2. How it works =
22	22
23	23
24		-Video Instruction: [[https:~~/~~/youtu.be/ZBjXwmp7rwM>>url:https://youtu.be/ZBjXwmp7rwM]]
	31	+(% style="color:#037691" %)**Video Instruction**(%%): **[[https:~~/~~/youtu.be/ZBjXwmp7rwM>>url:https://youtu.be/ZBjXwmp7rwM]]**
25	25
	33	+
26	26	Assume we have the LoRaWAN tracker LGT92 which works in ABP mode and US915 band. It has below keys:
27	27
28		-{{{AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df
	36	+(% class="box infomessage" %)
	37	+(((
	38	+**AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df
29	29	AT+APPSKEY=b3 17 f8 14 7a 43 27 8a 6a 31 c4 47 3d 55 5d 33
30		-AT+DADDR=2602111D
31		-}}}
	40	+AT+DADDR=2602111D**
	41	+)))
32	32
	43	+(((
33	33	and we have the LG308 works and US915 band and support ABP decryption. User can input these keys in LG308 so the LG308 can communicate with LGT92.
34	34
	46	+
	47	+)))
	48	+
35	35	We need to input above keys in LG308 and enable ABP decryption.
36	36
37		-[[image:https://wiki.dragino.com/images/thumb/5/55/LG308_MQTT_1.png/600px-LG308_MQTT_1.png||height="329" width="600"]]
38	38
	52	+[[image:image-20220527161119-1.png]]
	53	+
	54	+
39	39	Input the ABP keys in LG308
40	40
41	41
42	42	== 2.1 Upstream ==
43	43
	60	+
44	44	Now when this End Node (Dev Addr=2602111D) send a uplink packet. When this packet arrive LG308, LG308 will decode it and put the decode data on the file /var/iot/channels/2602111D . So we have this data for further process with other applications in LG308.
45	45
46		-We can see the log of LG308 to know this packet arrive
	63	+(((
	64	+We can see the log of LG308 to know this packet arrive.
47	47
48		-[[image:https://wiki.dragino.com/images/thumb/1/16/ABP_DECODE_2.png/600px-ABP_DECODE_2.png||height="205" width="600"]]
	66	+
	67	+)))
49	49
50		-LG308 log by "logread -f" command
	69	+[[image:image-20220527161149-2.png]]
51	51
52	52
	72	+LG308 log by "(% style="color:red" %)**logread -f**" (%%)command
	73	+
	74	+
	75	+
53	53	The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it.
54	54
55		-{{{root@dragino-1d25dc:~# hexdump /var/iot/channels/2602111D
56		-0000000 4646 4646 4646 3946 3030 3030 3030 3546 --> Got RSSI and SNR
57		-0000010 cc0c 0b63 0266 017f ff7f ff00 --> Payload
	78	+(% class="box" %)
	79	+(((
	80	+root@dragino-1d25dc:~~# hexdump /var/iot/channels/2602111D
	81	+0000000 (% style="color:#037691" %)**4646 4646 4646 3946 3030 3030 3030 3546**(%%)      ~-~-> Got RSSI and SNR
	82	+0000010 (% style="color:#037691" %)**cc0c 0b63 0266 017f ff7f ff00 **(%%) ~-~-> Payload
58	58	000001c
59		-}}}
	84	+)))
60	60
61		-* RSSI: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97
62		-* SNR: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
63		-* Payload: 0xcc0c 0b63 0266 017f ff7f ff00
	86	+* **RSSI**: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97
64	64
	88	+* **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
65	65
66		-{{{Notice 1: The data file stored in LG308 for the end node is bin file. If the end node sends ASCII string to gateway, the output will as below:
67		-in LGT92, use AT+SEND=12:hello world to send ASCII string
68		-root@dragino-1d25dc:~# hexdump /var/iot/channels/2602111D
	90	+* **Payload**: 0xcc0c 0b63 0266 017f ff7f ff00
	91	+
	92	+(% class="box" %)
	93	+(((
	94	+(% style="color:red" %)**Notice 1**(%%): The data file stored in LG308 for the end node is bin file. If the end node sends ASCII string to gateway, the output will as below:
	95	+in LGT92, use (% style="color:#037691" %)**AT+SEND=12:hello world** (%%)to send ASCII string
	96	+root@dragino-1d25dc:~~# hexdump /var/iot/channels/2602111D
69	69	0000000 4646 4646 4646 3946 3030 3030 3030 3546
70		-0000010 6865 6c6c 6f20 776f 726c 6400 --> Got ASCII code "hello world"
	98	+0000010 6865 6c6c 6f20 776f 726c 6400      ~-~-> Got ASCII code "hello world"
71	71	000001c
72		-}}}
	100	+)))
73	73
74		-{{{Notice 2: The upstream payload length should match the LoRaWAN length requirement (max length depends on Frequency and DR), otherwise the gateway can't decode the payload.
75		-}}}
76	76
	103	+(% class="box" %)
	104	+(((
	105	+(% style="color:red" %)**Notice 2**(%%): The upstream payload length should match the LoRaWAN length requirement (max length depends on Frequency and DR), otherwise the gateway can't decode the payload.
	106	+)))
	107	+
	108	+
77	77	=== 2.2.1 Decode Method ===
78	78
79		-The decode methods: ASCII String, Decode_LHT65 doesn't affect how the sensor data is stored, they are to define how should the sensor data to be sent.
80	80
	112	+The decode methods: (% style="color:#037691" %)**ASCII String, Decode_LHT65**(%%) doesn't affect how the sensor data is stored, they are to define how should the sensor data to be sent.
	113	+
81	81	For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
82	82
83		-{{{root@dragino-1baf44:~# hexdump /var/iot/channels/01826108
	116	+(% class="box" %)
	117	+(((
	118	+root@dragino-1baf44:~~# hexdump /var/iot/channels/01826108
84	84	0000000 4646 4646 4646 4537 3030 3030 3030 3438
85		-0000010 ccd1 7fff 7fff 017f ff7f ff00
	120	+0000010 ccd1 7fff 7fff 017f ff7f ff00
86	86	000001c
87		-}}}
	122	+)))
88	88
	124	+
89	89	If we choose ASCII decoder, the MQTT process will send out with mqtt-data:
90	90
91		-{{{Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data
	127	+(% class="box" %)
	128	+(((
	129	+Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data
92	92	Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:decoder: ASCII
93		-Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: ffffffe700000048ccd17fff7fff017fff7fff00
94		-}}}
	131	+Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00**
	132	+)))
95	95
	134	+
96	96	If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
97	97
98		-{{{Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data
	137	+(% class="box" %)
	138	+(((
	139	+Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data
99	99	Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:decoder: Dragino_LHT65
100		-Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: {"Hum_SHT":32.7,"BatV":3.281,"TempC_DS":32.9,
101		-"EXT":"Temperature Sensor","RSSI":-24,"TempC_SHT":85.0,"SNR":8.2,"ext_sensor":0}
102		-}}}
	141	+Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]:** (% style="color:#037691" %){"Hum_SHT":32.7,"BatV":3.281,"TempC_DS":32.9,
	142	+"EXT":"Temperature Sensor","RSSI":-24,"TempC_SHT":85.0,"SNR":8.2,"ext_sensor":0}(%%)**
	143	+)))
103	103
104	104	Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI.
105	105
...	...	@@ -106,94 +106,130 @@
106	106
107	107	=== 2.2.2 How to Decode My End Node ===
108	108
109		-1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
110	110
111		-2/ Don't choose MQTT service, use LoRaWAN.
	151	+**1.** Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
112	112
113		-3/ When your end node send a message to the gateway, there will be a file store in /var/iot/channels. full path should be /var/iot/channels/END_NODE_DEV_ADDR
	153	+**2. **Don't choose MQTT service, use LoRaWAN.
114	114
115		-4/ Use the /etc/lora/decoder/Dragino_LHT65 as template to decode your payload. This script is written in Lua language. User can manually call this script when you see the data file in /var/iot/channels by running:
	155	+**3.** When your end node send a message to the gateway, there will be a file store in /var/iot/channels. full path should be /var/iot/channels/END_NODE_DEV_ADDR
116	116
	157	+**4.** Use the /etc/lora/decoder/Dragino_LHT65 as template to decode your payload. This script is written in Lua language. User can manually call this script when you see the data file in /var/iot/channels by running:
	158	+
117	117	{{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
118	118	}}}
119	119
120		-5/ What you see as output is the MQTT data device will upload, user's end node has different payload compare with LHT65, most properly this file will report with error. User need to modify to match the actual payload. Some notice:
	162	+**5.** What you see as output is the MQTT data device will upload, user's end node has different payload compare with LHT65, most properly this file will report with error. User need to modify to match the actual payload.
121	121
	164	+
	165	+(% style="color:red" %)
	166	+**Some notice:**
	167	+
122	122	* RSSI and SNR are added when gateway receive the packet, so there is always this field.
	169	+
123	123	* If you rename the file, please make it executable.
	171	+
124	124	* See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
	173	+
125	125	* Lua json module: [[http:~~/~~/json.luaforge.net/>>url:http://json.luaforge.net/]]
	175	+
126	126	* the last line return is what will be used for MQTT
	177	+
127	127	* User can use other language ,not limited to Lua, just make sure the return is what you want to send.
128	128
	180	+
	181	+
129	129	== 2.2 Downstream ==
130	130
	184	+
131	131	In LG308, we can create a file in the directory /var/iot/push for downstream purpose. We recommend using each command to generate this file. This file will be used for transmission and auto-deleted after used
132	132
133	133	The file should use below format:
134	134
	189	+(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload**
135	135
136		-dev_addr,imme/time,txt/hex,payload
137	137
138		-Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option
	192	+Since fimware > [[Dragino lgw~~-~~-build-v5.4.1668567157>>https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LG308-LG301/Firmware/Release/]] . Support more option
139	139
140		-dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow
	194	+(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow,Fport**
141	141
142		-* dev_addr: Inptu the device address
143		-* imme/time:
	196	+* **dev_addr:** Inptu the device address
	197	+
	198	+* **imme/time:**
144	144	** imme: send downstream immediately,For Class C end node.
145	145	** time: send downstream after receive device's uplink. For Class A end node
146		-* txt/hex:
	201	+
	202	+* **txt/hex:**
147	147	** txt: send payload in ASCII
148	148	** hex: send payload in HEX
149		-* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
150		-* txpw: Transmit Power. example: 20
151		-* txbw: bandwidth:
	205	+
	206	+* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
	207	+
	208	+* **txpw:** Transmit Power. example: 20
	209	+
	210	+* **txbw:** bandwidth:
152	152	** 1: 500 kHz
153	153	** 2: 250 kHz
154	154	** 3: 125 kHz
155	155	** 4: 62.5 kHz
156		-* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
157		-* Frequency: Transmit Frequency: example: 923300000
158		-* rxwindow: transmit on Rx1Window or Rx2Window.
	215	+* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
159	159
	217	+* **Frequency:** Transmit Frequency: example: 923300000
160	160
161		-Completely exmaple:
	219	+* **rxwindow:** transmit on Rx1Window or Rx2Window.
162	162
163		-* Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test
164		-* New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
	221	+* **Fport: **Transmit port,example:8
165	165
166	166
167		-Downstream Frequency
	224	+(% style="color:blue" %)**Completely exmaple:**
168	168
	226	+* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
	227	+
	228	+* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2,8 > /var/iot/push/test
	229	+
	230	+
	231	+Downstream(% style="color:#037691" %)** Frequency:**
	232	+
169	169	The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
170	170
171	171	* EU868: 869.525Mhz, DR0(SF12BW125)
	236	+
172	172	* US915: 923.3Mhz, SF12 BW500
	238	+
173	173	* CN470: 505.3Mhz, SF12 BW125
	240	+
174	174	* AU915: 923.3Mhz, SF12 BW500
	242	+
175	175	* AS923: 923.2Mhz, SF10 BW125
	244	+
176	176	* KR920: 921.9Mhz, SF12 BW125
	246	+
177	177	* IN865: 866.55Mhz, SF10 BW125
	248	+
178	178	* RU864: 869.1Mhz, SF12 BW125
179	179
180	180
181		-Examples:
182	182
183		-{{{we can use echo command to create files in LG308 for downstream.
184		-root@dragino-1d25dc:~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
	253	+(% style="color:#037691" %)**Examples:**
185	185
186		-1) From logread -f of gateway, we can see it has been added as pedning.
187		-lora_pkt_fwd[4286]: INFO~ [DNLK]Looking file : test
188		-lora_pkt_fwd[4286]: INFO~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
189		-lora_pkt_fwd[4286]: INFO~ [DNLK] DNLINK PENDING!(1 elems).
	255	+(% class="box" %)
	256	+(((
	257	+we can use echo command to create files in LG308 for downstream.
	258	+root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
190	190
191		-2) When there is an upstrea from end node, this downstream will be sent and shows:
	260	+
	261	+**1)** From logread -f of gateway, we can see it has been added as pedning.
	262	+lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
	263	+lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
	264	+lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
	265	+
	266	+
	267	+**2)** When there is an upstrea from end node, this downstream will be sent and shows:
192	192	lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
193	193	lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
194	194
195		-3) and the end node will got:
196		-[5764825]***** UpLinkCounter= 98 *****
	271	+
	272	+**3)** and the end node will got:
	273	+[5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
197	197	[5764827]TX on freq 905300000 Hz at DR 0
198	198	Update Interval: 60000 ms
199	199	[5765202]txDone
...	...	@@ -203,11 +203,11 @@
203	203	[5767501]rxDone
204	204	Rssi= -41
205	205	Receive data
206		-2:12345678 --> Hex
207		-}}}
	283	+(% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
208	208
209		-{{{4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
210		-[5955877]***** UpLinkCounter= 102 *****
	285	+
	286	+**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
	287	+[5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
211	211	[5955879]TX on freq 904100000 Hz at DR 0
212	212	Update Interval: 60000 ms
213	213	[5956254]txDone
...	...	@@ -217,114 +217,142 @@
217	217	[5958595]rxDone
218	218	Rssi= -37
219	219	Receive data
220		-2:3132333435363738 --> ASCII string "12345678"
221		-}}}
	297	+(% style="color:#037691" %)**2:3132333435363738**(%%) ~-~-> ASCII string "12345678"
	298	+)))
222	222
	300	+
223	223	= 3. Example 1: Communicate with LT-22222-L =
224	224
	303	+
225	225	Script can be download from: [[Example Script 1>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/customized_script/&file=talk_to_lt-22222-l_v0.1.sh]]
226	226
227		-{{{#!/bin/sh
	306	+(% class="box" %)
	307	+(((
	308	+//#!/bin/sh
228	228	# This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
229	229	#
230		-# Hardware Prepare:
231		-# 1. LT-22222-L x 2, both are configured to work in
232		-# a) Class C ;
233		-# b) ABP Mode ;
	311	+# Hardware Prepare:
	312	+# 1. LT-22222-L x 2, both are configured to work in
	313	+#   a) Class C ;
	314	+# b) ABP Mode ;
234	234	# c) AT+Mod=1
235		-# 2. LPS8,
236		-# a) Firmware version >
237		-# b) Input the LT-22222-L keys in LPS so LPS8 can talk with them.
238		-# c) Lorawan server choose built-in
239		-# d) in Custom page, select custom script to point to this script. (put this script in /etc/iot/scripts directory)
240		-#
241		-# How it works?
242		-# a) Devices 1 sends a uplink payload to LPS8. LPS8 will get the DI1 and DI2 info from the payload
243		-# b) LPS8 will send a message to Device 2 to set the Device2 DO1 = Device1 DI1, and Device DO2 = Device DI2.
244		-# c) Device2 will change DO1 and DO2 to according to the message from LPS8, and send back a message to LPS8 with the its DO1
245		-# and DO2 value. LPS8 will ask Device1 to change its DO1 to same as Device 2, and change the DO2 to the same as Device 2.
246		-# ( The purpose of this step is to show that the Device2 has already do the change there).
247		-#
248		-# For example: If current status of Device1 and Device2 leds shows:
249		-# Device1: DI1: ON, DI2: ON , DO1: OFF, DO2: OFF
250		-# Device2: DI1: OFF, DI2: OFF , DO1: OFF, DO2: OFF
	316	+# 2. LPS8,
	317	+#   a) Firmware version >
	318	+#   b) Input the LT-22222-L keys in LPS so LPS8 can talk with them.
	319	+#   c) Lorawan server choose built-in
	320	+#   d) in Custom page, select custom script to point to this script. (put this script in /etc/iot/scripts directory)
251	251	#
252		-# Step2 will cause below change:
253		-# Device1: DI1: ON, DI2: ON , DO1: OFF, DO2: OFF
254		-# Device2: DI1: OFF, DI2: OFF , DO1: ON, DO2: ON
255		-#
256		-# Step3 will cause below change:
257		-# Device1: DI1: ON, DI2: ON , DO1: ON, DO2: ON
258		-# Device2: DI1: OFF, DI2: OFF , DO1: ON, DO2: ON
259		-# So if a person is in the Device 1 location, he can check if the DO LED match DI LEDs on Device 1 to confirm
260		-# whether the Device 2 has been changed.}}}
	322	+# How it works?
	323	+#   a) Devices 1 sends a uplink payload to LPS8. LPS8 will get the DI1 and DI2 info from the payload
	324	+#   b) LPS8 will send a message to Device 2 to set the Device2 DO1 = Device1 DI1, and Device DO2 = Device DI2.
	325	+#   c) Device2 will change DO1 and DO2 to according to the message from LPS8, and send back a message to LPS8 with the its DO1
	326	+#   and DO2 value. LPS8 will ask Device1 to change its DO1 to same as Device 2, and change the DO2 to the same as Device 2.
	327	+#   ( The purpose of this step is to show that the Device2 has already do the change there).
	328	+#
	329	+#  For example: If current status of Device1 and Device2 leds shows:
	330	+#  Device1: DI1: ON, DI2: ON , DO1: OFF,  DO2: OFF
	331	+#  Device2: DI1: OFF, DI2: OFF , DO1: OFF,  DO2: OFF
	332	+#
	333	+#  Step2  will cause below change:
	334	+#  Device1: DI1: ON, DI2: ON , DO1: OFF,  DO2: OFF
	335	+#  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
	336	+#
	337	+#  Step3 will cause below change:
	338	+#  Device1: DI1: ON, DI2: ON , DO1: ON,  DO2: ON
	339	+#  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
	340	+#  So if a person is in the Device 1 location, he can check if the DO LED match DI LEDs on Device 1 to confirm
	341	+#  whether the Device 2 has been changed.//
	342	+)))
261	261
262		-~1. Input keys
263	263
264		-[[image:https://wiki.dragino.com/images/thumb/b/bf/LPS8_LT-22222_1.png/600px-LPS8_LT-22222_1.png||height="335" width="600"]]
	345	+(% style="color:blue" %)**1. Input keys**
265	265
	347	+
	348	+[[image:image-20220527162450-3.png]]
	349	+
266	266	Input Keys in LPS8
267	267
268		-2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.
269	269
270		-3. Choose Built-in server
271	271
272		-[[image:https://wiki.dragino.com/images/thumb/d/d7/LPS8_LT-22222_2.png/600px-LPS8_LT-22222_2.png||height="264" width="600"]]
	354	+(% style="color:blue" %)**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
273	273
	356	+
	357	+(% style="color:blue" %)**3. Choose Built-in server**
	358	+
	359	+
	360	+[[image:image-20220527162518-4.png]]
	361	+
274	274	Choose Built-in server
275	275
276		-4. Run the script.
277	277
278		-[[image:https://wiki.dragino.com/images/thumb/3/39/LPS8_LT-22222_3.png/600px-LPS8_LT-22222_3.png||height="389" width="600"]]
279	279
	366	+(% style="color:blue" %)**4. Run the script.**
	367	+
	368	+
	369	+[[image:image-20220722115213-2.png]]
	370	+
280	280	Run the script
281	281
282		-5. Output:
283	283
284		-[[image:https://wiki.dragino.com/images/thumb/f/fe/LPS8_LT-22222_4.png/600px-LPS8_LT-22222_4.png||height="433" width="600"]]
285	285
	375	+(% style="color:blue" %)**5. Output:**
	376	+
	377	+
	378	+[[image:image-20220722115133-1.png]]
	379	+
286	286	Output from LPS8
287	287
288	288
289	289	= 4. Example 2: Communicate to TCP Server =
290	290
291		-[[image:https://wiki.dragino.com/images/thumb/7/75/LPS8_TCP_0.png/600px-LPS8_TCP_0.png||height="370" width="600"]]
292	292
	386	+[[image:image-20220527162648-7.png]]
	387	+
293	293	Network Structure
294	294
295	295
296	296	Full instruction video inlcude how to write scripts to fit server needed is here:
297	297
	393	+(% style="color:#037691" %)**Video Instruction**(%%): **[[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]**
298	298
299		-Video Instruction: [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]
	395	+(% style="display:none" %) (%%)
300	300
	397	+(% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
301	301
302		-Note: Firmware version must be higher than lgw-5.4.1607519907
303	303
304	304	Assume we already set up ABP keys in the gateway:
305	305
306		-[[image:https://wiki.dragino.com/images/thumb/b/bf/LPS8_LT-22222_1.png/600px-LPS8_LT-22222_1.png||height="335" width="600"]]
	402	+[[image:image-20220527162852-8.png]]
307	307
308	308	Input Keys in LPS8
309	309
310		-run socket tool in PC
311	311
312		-[[image:https://wiki.dragino.com/images/thumb/4/4b/LPS8_TCP_2.png/600px-LPS8_TCP_2.png||height="212" width="600"]]
313	313
	408	+(% style="color:blue" %)**run socket tool in PC**
	409	+
	410	+
	411	+[[image:image-20220527163028-9.png]]
	412	+
	413	+
314	314	Socket tool
315	315
316	316
317		-Input Server address and port
318	318
319		-[[image:https://wiki.dragino.com/images/thumb/c/c6/LPS8_TCP_3.png/600px-LPS8_TCP_3.png||height="306" width="600"]]
	418	+(% style="color:blue" %)**Input Server address and port**
320	320
	420	+
	421	+[[image:image-20220527163106-10.png]]
	422	+
321	321	Input Server address and port
322	322
323	323
324		-See value receive in socket tool. :
325	325
326		-[[image:https://wiki.dragino.com/images/thumb/2/20/LPS8_TCP_4.png/600px-LPS8_TCP_4.png||height="219" width="600"]]
	427	+(% style="color:blue" %)**See value receive in socket tool:**
327	327
	429	+
	430	+[[image:image-20220527163144-11.png||height="502" width="1371"]]
	431	+
328	328	value receive in socket tool
329	329
	434	+
330	330	If user want to modify the TCP connection method. He can refer: [[https:~~/~~/github.com/dragino/dragino-packages/blob/lg02/haserl-ui/root/usr/bin/tcp_process.sh>>url:https://github.com/dragino/dragino-packages/blob/lg02/haserl-ui/root/usr/bin/tcp_process.sh]]. Same script is on /usr/bin of gateway.

image-20220527161119-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+128.8 KB

Content

image-20220527161149-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+103.9 KB

Content

image-20220527162450-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+125.4 KB

Content

image-20220527162518-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+72.8 KB

Content

image-20220527162552-5.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+33.6 KB

Content

image-20220527162619-6.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+41.0 KB

Content

image-20220527162648-7.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+151.7 KB

Content

image-20220527162852-8.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+125.6 KB

Content

image-20220527163028-9.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+32.9 KB

Content

image-20220527163106-10.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+34.5 KB

Content

image-20220527163144-11.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+107.7 KB

Content

image-20220722115133-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+35.1 KB

Content

image-20220722115213-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+27.7 KB

Content