Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 1.10 >
edited by Xiaoling
on 2022/05/12 18:08
To version < 16.5 >
edited by Xiaoling
on 2022/07/22 11:45
>
Change comment: There is no comment for this version

Summary

Details

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

Applications

Navigation

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