Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 38.4 >
edited by Xiaoling
on 2022/06/02 16:30
To version < 32.15 >
edited by Xiaoling
on 2022/06/02 15:26
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -76,6 +76,8 @@
76 76  * Automatic RF Sense and CAD with ultra-fast AFC.
77 77  * Packet engine up to 256 bytes with CRC.
78 78  
79 +
80 +
79 79  == 1.3 Features ==
80 80  
81 81  * LoRaWAN Class A & Class C protocol (default Class C)
... ... @@ -87,6 +87,8 @@
87 87  * Support Modbus protocol
88 88  * Support Interrupt uplink (Since hardware version v1.2)
89 89  
92 +
93 +
90 90  == 1.4 Applications ==
91 91  
92 92  * Smart Buildings & Home Automation
... ... @@ -96,6 +96,8 @@
96 96  * Smart Cities
97 97  * Smart Factory
98 98  
103 +
104 +
99 99  == 1.5 Firmware Change log ==
100 100  
101 101  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
... ... @@ -225,19 +225,19 @@
225 225  
226 226  To use RS485-LN to read data from RS485 sensors, connect the RS485-LN A/B traces to the sensors. And user need to make sure RS485-LN use the match UART setting to access the sensors. The related commands for UART settings are:
227 227  
228 -(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
229 -|(% style="width:128px" %)(((
234 +(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
235 +|(((
230 230  **AT Commands**
231 -)))|(% style="width:305px" %)(((
237 +)))|(% style="width:285px" %)(((
232 232  **Description**
233 -)))|(% style="width:346px" %)(((
239 +)))|(% style="width:347px" %)(((
234 234  **Example**
235 235  )))
236 -|(% style="width:128px" %)(((
242 +|(((
237 237  AT+BAUDR
238 -)))|(% style="width:305px" %)(((
244 +)))|(% style="width:285px" %)(((
239 239  Set the baud rate (for RS485 connection). Default Value is: 9600.
240 -)))|(% style="width:346px" %)(((
246 +)))|(% style="width:347px" %)(((
241 241  (((
242 242  AT+BAUDR=9600
243 243  )))
... ... @@ -246,11 +246,11 @@
246 246  Options: (1200,2400,4800,14400,19200,115200)
247 247  )))
248 248  )))
249 -|(% style="width:128px" %)(((
255 +|(((
250 250  AT+PARITY
251 -)))|(% style="width:305px" %)(((
257 +)))|(% style="width:285px" %)(((
252 252  Set UART parity (for RS485 connection)
253 -)))|(% style="width:346px" %)(((
259 +)))|(% style="width:347px" %)(((
254 254  (((
255 255  AT+PARITY=0
256 256  )))
... ... @@ -259,9 +259,9 @@
259 259  Option: 0: no parity, 1: odd parity, 2: even parity
260 260  )))
261 261  )))
262 -|(% style="width:128px" %)(((
268 +|(((
263 263  AT+STOPBIT
264 -)))|(% style="width:305px" %)(((
270 +)))|(% style="width:285px" %)(((
265 265  (((
266 266  Set serial stopbit (for RS485 connection)
267 267  )))
... ... @@ -269,7 +269,7 @@
269 269  (((
270 270  
271 271  )))
272 -)))|(% style="width:346px" %)(((
278 +)))|(% style="width:347px" %)(((
273 273  (((
274 274  AT+STOPBIT=0 for 1bit
275 275  )))
... ... @@ -304,34 +304,77 @@
304 304  === 3.3.3 Configure read commands for each sampling ===
305 305  
306 306  (((
307 -During each sampling, we need confirm what commands we need to send to the RS485 sensors to read data. After the RS485 sensors send back the value, it normally include some bytes and we only need a few from them for a shorten payload.
313 +RS485-BL is a battery powered device; it will sleep most of time. And wake up on each period and read RS485 / TTL sensor data and uplink.
314 +)))
308 308  
316 +(((
317 +During each sampling, we need to confirm what commands we need to send to the sensors to read data. After the RS485/TTL sensors send back the value, it normally includes some bytes and we only need a few from them for a shorten payload.
318 +)))
319 +
320 +(((
309 309  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
322 +)))
310 310  
324 +(((
311 311  This section describes how to achieve above goals.
326 +)))
312 312  
313 -During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
328 +(((
329 +During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
330 +)))
314 314  
332 +(((
333 +**Command from RS485-BL to Sensor:**
334 +)))
315 315  
316 -**Each RS485 commands include two parts:**
336 +(((
337 +RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
338 +)))
317 317  
318 -~1. What commands RS485-LN will send to the RS485 sensors. There are total 15 commands from **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF**. All commands are of same grammar.
340 +(((
341 +**Handle return from sensors to RS485-BL**:
342 +)))
319 319  
320 -2. How to get wanted value the from RS485 sensors returns from by 1). There are total 15 AT Commands to handle the return, commands are **AT+DATACUT1**,**AT+DATACUT2**,…, **AT+DATACUTF** corresponding to the commands from 1). All commands are of same grammar.
344 +(((
345 +After RS485-BL send out a string to sensor, RS485-BL will wait for the return from RS485 or TTL sensor. And user can specify how to handle the return, by **AT+DATACUT or AT+SEARCH commands**
346 +)))
321 321  
322 -3. Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example **AT+CMDDL1=1000** to send the open time to 1000ms
348 +* (((
349 +**AT+DATACUT**
350 +)))
323 323  
352 +(((
353 +When the return value from sensor have fix length and we know which position the valid value we should get, we can use AT+DATACUT command.
354 +)))
324 324  
356 +* (((
357 +**AT+SEARCH**
358 +)))
359 +
360 +(((
361 +When the return value from sensor is dynamic length and we are not sure which bytes the valid data is, instead, we know what value the valid value following. We can use AT+SEARCH to search the valid value in the return string.
362 +)))
363 +
364 +(((
365 +**Define wait timeout:**
366 +)))
367 +
368 +(((
369 +Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example, AT+CMDDL1=1000 to send the open time to 1000ms
370 +)))
371 +
372 +(((
325 325  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
374 +)))
326 326  
376 +**Examples:**
327 327  
328 328  Below are examples for the how above AT Commands works.
329 329  
380 +**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
330 330  
331 -**AT+COMMANDx : **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:
332 -
333 -(% border="1" style="background-color:#4bacc6; color:white; width:499px" %)
334 -|(% style="width:496px" %)(((
382 +(% border="1" class="table-bordered" %)
383 +|(((
335 335  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
336 336  
337 337  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -339,15 +339,49 @@
339 339  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
340 340  )))
341 341  
391 +(((
342 342  For example, if we have a RS485 sensor. The command to get sensor value is: 01 03 0B B8 00 02 46 0A. Where 01 03 0B B8 00 02 is the Modbus command to read the register 0B B8 where stored the sensor value. The 46 0A is the CRC-16/MODBUS which calculate manually.
393 +)))
343 343  
344 -In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
395 +(((
396 +In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
397 +)))
345 345  
399 +(((
400 +**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
401 +)))
346 346  
403 +(% border="1" class="table-bordered" %)
404 +|(((
405 +**AT+SEARCHx=aa,xx xx xx xx xx**
406 +
407 +* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
408 +* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
409 +
410 +
411 +)))
412 +
413 +**Examples:**
414 +
415 +~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
416 +
417 +If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
418 +
419 +The valid data will be all bytes after 1E 56 34 , so it is (% style="background-color:yellow" %)** 2e 30 58 5f 36 41 30 31 00 49**
420 +
421 +[[image:1653269403619-508.png]]
422 +
423 +2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
424 +
425 +If we set AT+SEARCH1=2, 1E 56 34+31 00 49
426 +
427 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is (% style="background-color:yellow" %)** 2e 30 58 5f 36 41 30**
428 +
429 +[[image:1653269438444-278.png]]
430 +
347 347  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
348 348  
349 -(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
350 -|(% style="width:722px" %)(((
433 +|(((
351 351  **AT+DATACUTx=a,b,c**
352 352  
353 353  * **a: length for the return of AT+COMMAND**
... ... @@ -355,37 +355,48 @@
355 355  * **c: define the position for valid value.  **
356 356  )))
357 357  
358 -**Examples:**
441 +Examples:
359 359  
360 360  * Grab bytes:
361 361  
362 -[[image:image-20220602153621-1.png]]
445 +[[image:1653269551753-223.png||height="311" width="717"]]
363 363  
364 -
365 365  * Grab a section.
366 366  
367 -[[image:image-20220602153621-2.png]]
449 +[[image:1653269568276-930.png||height="325" width="718"]]
368 368  
369 -
370 370  * Grab different sections.
371 371  
372 -[[image:image-20220602153621-3.png]]
453 +[[image:1653269593172-426.png||height="303" width="725"]]
373 373  
374 -
375 -)))
455 +(% style="color:red" %)**Note:**
376 376  
457 +AT+SEARCHx and AT+DATACUTx can be used together, if both commands are set, RS485-BL will first process AT+SEARCHx on the return string and get a temporary string, and then process AT+DATACUTx on this temporary string to get the final payload. In this case, AT+DATACUTx need to set to format AT+DATACUTx=0,xx,xx where the return bytes set to 0.
458 +
459 +Example:
460 +
461 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
462 +
463 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
464 +
465 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
466 +
467 +(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
468 +
469 +(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
470 +
471 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
472 +
473 +[[image:1653269618463-608.png]]
474 +
377 377  === 3.3.4 Compose the uplink payload ===
378 378  
379 379  (((
380 380  Through AT+COMMANDx and AT+DATACUTx we got valid value from each RS485 commands, Assume these valid value are RETURN1, RETURN2, .., to RETURNx. The next step is how to compose the LoRa Uplink Payload by these RETURNs. The command is **AT+DATAUP.**
381 -
382 -
383 383  )))
384 384  
385 385  (((
386 -(% style="color:#037691" %)**Examples: AT+DATAUP=0**
387 -
388 -
482 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
389 389  )))
390 390  
391 391  (((
... ... @@ -406,10 +406,8 @@
406 406  
407 407  [[image:1653269759169-150.png||height="513" width="716"]]
408 408  
503 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
409 409  
410 -(% style="color:#037691" %)**Examples: AT+DATAUP=1**
411 -
412 -
413 413  Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
414 414  
415 415  Final Payload is
... ... @@ -416,98 +416,138 @@
416 416  
417 417  (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
418 418  
419 -1. PAYVER: Defined by AT+PAYVER
420 -1. PAYLOAD COUNT: Total how many uplinks of this sampling.
421 -1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
422 -1. DATA: Valid value: max 8 bytes for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 8 bytes
511 +1. Battery Info (2 bytes): Battery voltage
512 +1. PAYVER (1 byte): Defined by AT+PAYVER
513 +1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
514 +1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
515 +1. DATA: Valid value: max 6 bytes(US915 version here, Notice*!) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
423 423  
424 -[[image:image-20220602155039-4.png]]
517 +[[image:1653269916228-732.png||height="433" width="711"]]
425 425  
426 426  
427 -So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
520 +So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
428 428  
429 -DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= **20 20 0a 33 90 41 02 aa**
522 +DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41
430 430  
431 -DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= **05 81 0a 20 20 20 20 2d**
524 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 02 aa 05 81 0a 20
432 432  
433 -DATA3=the rest of Valid value of RETURN10= **30**
526 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (% style="background-color:green; color:white" %)20 20 20 2d 30
434 434  
528 +Below are the uplink payloads:
435 435  
436 -(% style="color:red" %)Notice: In firmware v1.3, the Max bytes has been changed according to the max bytes in different Frequency Bands for lowest SF. As below:
530 +[[image:1653270130359-810.png]]
437 437  
438 - ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
439 439  
440 - * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
533 +(% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
441 441  
442 - * For US915 band, max 11 bytes for each uplink.
535 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
443 443  
444 - ~* For all other bands: max 51 bytes for each uplink.
537 + * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
445 445  
539 + * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
446 446  
447 -Below are the uplink payloads:
541 + ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
448 448  
449 -[[image:1654157178836-407.png]]
450 -
451 -
452 452  === 3.3.5 Uplink on demand ===
453 453  
454 -Except uplink periodically, RS485-LN is able to uplink on demand. The server send downlink command to RS485-LN and RS485 will uplink data base on the command.
545 +Except uplink periodically, RS485-BL is able to uplink on demand. The server sends downlink command to RS485-BL and RS485 will uplink data base on the command.
455 455  
456 456  Downlink control command:
457 457  
458 -**0x08 command**: Poll an uplink with current command set in RS485-LN.
549 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
459 459  
460 -**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors.
551 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
461 461  
462 462  
463 463  
464 -=== 3.3.6 Uplink on Interrupt ===
555 +1.
556 +11.
557 +111. Uplink on Interrupt
465 465  
466 -RS485-LN support external Interrupt uplink since hardware v1.2 release.
559 +Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
467 467  
468 -[[image:1654157342174-798.png]]
561 +AT+INTMOD=0  Disable Interrupt
469 469  
470 -Connect the Interrupt pin to RS485-LN INT port and connect the GND pin to V- port. When there is a high voltage (Max 24v) on INT pin. Device will send an uplink packet.
563 +AT+INTMOD=1  Interrupt trigger by rising or falling edge.
471 471  
565 +AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
472 472  
473 -== 3.4 Uplink Payload ==
567 +AT+INTMOD=3  Interrupt trigger by rising edge.
474 474  
475 -(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
476 -|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands**
477 -|Value|(% style="width:120px" %)(((
569 +
570 +1.
571 +11. Uplink Payload
572 +
573 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
574 +|Value|(((
478 478  Battery(mV)
479 479  
480 480  &
481 481  
482 482  Interrupt _Flag
483 -)))|(% style="width:116px" %)(((
580 +)))|(((
484 484  PAYLOAD_VER
485 485  
486 486  
487 -)))|(% style="width:386px" %)If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.
584 +)))|If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.
488 488  
489 489  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
490 490  
491 491  
492 -== 3.5 Configure RS485-BL via AT or Downlink ==
589 +function Decoder(bytes, port) {
493 493  
494 -User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
591 +~/~/Payload Formats of RS485-BL Deceive
495 495  
496 -There are two kinds of Commands:
593 +return {
497 497  
498 -* (% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
595 + ~/~/Battery,units:V
499 499  
500 -* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
597 + BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
501 501  
599 + ~/~/GPIO_EXTI 
502 502  
601 + EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
503 503  
504 -=== 3.5.1 Common Commands ===
603 + ~/~/payload of version
505 505  
506 -They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
605 + Pay_ver:bytes[2],
507 507  
607 + };
508 508  
509 -=== 3.5.2 Sensor related commands: ===
609 + }
510 510  
611 +
612 +
613 +
614 +
615 +
616 +
617 +TTN V3 uplink screen shot.
618 +
619 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
620 +
621 +1.
622 +11. Configure RS485-BL via AT or Downlink
623 +
624 +User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
625 +
626 +There are two kinds of Commands:
627 +
628 +* **Common Commands**: They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: http:~/~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands
629 +
630 +* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
631 +
632 +1.
633 +11.
634 +111. Common Commands:
635 +
636 +They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands>>url:http://wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands]]
637 +
638 +
639 +1.
640 +11.
641 +111. Sensor related commands:
642 +
511 511  ==== Choose Device Type (RS485 or TTL) ====
512 512  
513 513  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
1654157178836-407.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -179.9 KB
Content
1654157342174-798.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -31.9 KB
Content
image-20220602153621-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -23.4 KB
Content
image-20220602153621-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.2 KB
Content
image-20220602153621-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.3 KB
Content
image-20220602155039-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -24.6 KB
Content

Applications

Navigation

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