Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 3.7 >
edited by Xiaoling
on 2022/05/27 16:22
To version < 1.2 >
edited by Xiaoling
on 2022/05/12 17:47
>
Change comment: There is no comment for this version

Summary

Details

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

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0