Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 16.1 >
edited by Xiaoling
on 2022/07/22 11:33
To version < 1.7 >
edited by Xiaoling
on 2022/05/12 17:54
>
Change comment: There is no comment for this version

Summary

Details

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

Applications

Navigation

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