Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 13.1 >
edited by Xiaoling
on 2022/05/27 16:32
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,19 +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  
22 +
21 21  = 2. How it works =
22 22  
23 23  
24 -(% 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]]
25 25  
26 -
27 27  Assume we have the LoRaWAN tracker LGT92 which works in ABP mode and US915 band. It has below keys:
28 28  
29 29  (% class="box infomessage" %)
... ... @@ -39,7 +39,7 @@
39 39  
40 40  We need to input above keys in LG308 and enable ABP decryption.
41 41  
42 -[[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"]]
43 43  
44 44  Input the ABP keys in LG308
45 45  
... ... @@ -52,7 +52,7 @@
52 52  We can see the log of LG308 to know this packet arrive
53 53  )))
54 54  
55 -[[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"]]
56 56  
57 57  LG308 log by "logread -f" command
58 58  
... ... @@ -62,8 +62,8 @@
62 62  (% class="box" %)
63 63  (((
64 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
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
67 67  000001c
68 68  )))
69 69  
... ... @@ -73,8 +73,8 @@
73 73  
74 74  (% class="box" %)
75 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
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
78 78  root@dragino-1d25dc:~~# hexdump /var/iot/channels/2602111D
79 79  0000000 4646 4646 4646 3946 3030 3030 3030 3546
80 80  0000010 6865 6c6c 6f20 776f 726c 6400      ~-~-> Got ASCII code "hello world"    
... ... @@ -83,13 +83,12 @@
83 83  
84 84  (% class="box" %)
85 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 +(% 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.
87 87  )))
88 88  
89 -
90 90  === 2.2.1 Decode Method ===
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.
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.
93 93  
94 94  For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
95 95  
... ... @@ -107,7 +107,7 @@
107 107  (((
108 108  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**
110 +Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: ffffffe700000048ccd17fff7fff017fff7fff00
111 111  )))
112 112  
113 113  If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
... ... @@ -116,8 +116,8 @@
116 116  (((
117 117  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}(%%)**
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}
121 121  )))
122 122  
123 123  Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI.
... ... @@ -145,7 +145,6 @@
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 -
149 149  == 2.2 Downstream ==
150 150  
151 151  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
... ... @@ -152,11 +152,12 @@
152 152  
153 153  The file should use below format:
154 154  
155 -(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload**
156 156  
155 +dev_addr,imme/time,txt/hex,payload
156 +
157 157  Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option
158 158  
159 -(% 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
160 160  
161 161  * dev_addr: Inptu the device address
162 162  * imme/time:
... ... @@ -176,13 +176,15 @@
176 176  * Frequency: Transmit Frequency: example: 923300000
177 177  * rxwindow: transmit on Rx1Window or Rx2Window.
178 178  
179 +
179 179  Completely exmaple:
180 180  
181 181  * Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test
182 182  * New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
183 183  
184 -(% style="color:#037691" %)**Downstream Frequency**
185 185  
186 +Downstream Frequency
187 +
186 186  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
187 187  
188 188  * EU868: 869.525Mhz, DR0(SF12BW125)
... ... @@ -194,33 +194,23 @@
194 194  * IN865: 866.55Mhz, SF10 BW125
195 195  * RU864: 869.1Mhz, SF12 BW125
196 196  
197 -(% style="color:#037691" %)**Examples:**
198 198  
199 -(% class="box" %)
200 -(((
201 -we can use echo command to create files in LG308 for downstream.
202 -root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
203 -)))
200 +Examples:
204 204  
205 -(% class="box" %)
206 -(((
207 -1) From logread -f of gateway, we can see it has been added as pedning.
208 -lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
209 -lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
210 -lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
211 -)))
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
212 212  
213 -(% class="box" %)
214 -(((
215 -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:
216 216  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
217 217  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
218 -)))
219 219  
220 -(% class="box" %)
221 -(((
222 -3) and the end node will got:
223 -[5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
214 +3) and the end node will got:
215 +[5764825]***** UpLinkCounter= 98 *****
224 224  [5764827]TX on freq 905300000 Hz at DR 0
225 225  Update Interval: 60000 ms
226 226  [5765202]txDone
... ... @@ -230,13 +230,11 @@
230 230  [5767501]rxDone
231 231  Rssi= -41
232 232  Receive data
233 -(% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
234 -)))
225 +2:12345678 --> Hex
226 +}}}
235 235  
236 -(% class="box" %)
237 -(((
238 -4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
239 -[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 *****
240 240  [5955879]TX on freq 904100000 Hz at DR 0
241 241  Update Interval: 60000 ms
242 242  [5956254]txDone
... ... @@ -246,78 +246,71 @@
246 246  [5958595]rxDone
247 247  Rssi= -37
248 248  Receive data
249 -(% style="color:#037691" %)**2:3132333435363738**(%%) ~-~-> ASCII string "12345678"
250 -)))
239 +2:3132333435363738 --> ASCII string "12345678"
240 +}}}
251 251  
252 -
253 253  = 3. 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
246 +{{{#!/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 ;
249 +# Hardware Prepare:
250 +# 1. LT-22222-L x 2, both are configured to work in
251 +# a) Class C ;
252 +# 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)
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
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 -)))
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.}}}
294 294  
295 295  ~1. Input keys
296 296  
297 -[[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"]]
298 298  
299 299  Input Keys in LPS8
300 300  
301 -
302 302  2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.
303 303  
304 304  3. Choose Built-in server
305 305  
306 -[[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"]]
307 307  
308 308  Choose Built-in server
309 309  
310 -
311 311  4. Run the script.
312 312  
313 -[[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"]]
314 314  
315 315  Run the script
316 316  
317 -
318 318  5. Output:
319 319  
320 -[[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"]]
321 321  
322 322  Output from LPS8
323 323  
... ... @@ -324,7 +324,7 @@
324 324  
325 325  = 4. Example 2: Communicate to TCP Server =
326 326  
327 -[[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"]]
328 328  
329 329  Network Structure
330 330  
... ... @@ -332,29 +332,27 @@
332 332  Full instruction video inlcude how to write scripts to fit server needed is here:
333 333  
334 334  
335 -(% 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]]
336 336  
337 337  
338 -(% 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
339 339  
340 340  Assume we already set up ABP keys in the gateway:
341 341  
342 -[[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"]]
343 343  
344 344  Input Keys in LPS8
345 345  
346 -
347 347  run socket tool in PC
348 348  
349 -[[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"]]
350 350  
351 -
352 352  Socket tool
353 353  
354 354  
355 355  Input Server address and port
356 356  
357 -[[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"]]
358 358  
359 359  Input Server address and port
360 360  
... ... @@ -361,7 +361,7 @@
361 361  
362 362  See value receive in socket tool. :
363 363  
364 -[[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"]]
365 365  
366 366  value receive in socket tool
367 367  
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