Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 14.1 >
edited by Xiaoling
on 2022/05/27 16:33
To version < 1.9 >
edited by Xiaoling
on 2022/05/12 18:02
>
Change comment: There is no comment for this version

Summary

Details

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