Summary

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

Size

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

Content

image-20220527161149-2.png

Author

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

Size

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

Content

image-20220527162450-3.png

Author

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

Size

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

Content

image-20220527162518-4.png

Author

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

Size

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

Content

image-20220527162552-5.png

Author

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

Size

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

Content

image-20220527162619-6.png

Author

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

Size

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

Content

image-20220527162648-7.png

Author

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

Size

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

Content

image-20220527162852-8.png

Author

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

Size

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

Content

image-20220527163028-9.png

Author

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

Size

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

Content

image-20220527163106-10.png

Author

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

Size

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

Content

image-20220527163144-11.png

Author

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

Size

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

Content

image-20220722115133-1.png

Author

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

Size

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

Content

image-20220722115213-2.png

Author

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

Size

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

Content