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

Summary

Details

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