Last modified by Xiaoling on 2025/04/23 15:57

From version 29.13
edited by Xiaoling
on 2022/06/01 18:02
Change comment: There is no comment for this version
To version 29.38
edited by Xiaoling
on 2022/06/02 09:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -25,19 +25,19 @@
25 25  )))
26 26  
27 27  (((
28 -The Dragino RS485-BL is a **RS485 / UART to LoRaWAN Converter** for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.
28 +The Dragino RS485-BL is a (% style="color:blue" %)**RS485 / UART to LoRaWAN Converter**(%%) for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.
29 29  )))
30 30  
31 31  (((
32 -RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides **a 3.3v output** and** a 5v output** to power external sensors. Both output voltages are controllable to minimize the total system power consumption.
32 +RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides (% style="color:blue" %)**a 3.3v output**(%%) and** (% style="color:blue" %)a 5v output(%%)** to power external sensors. Both output voltages are controllable to minimize the total system power consumption.
33 33  )))
34 34  
35 35  (((
36 -RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years.
36 +RS485-BL is IP67 (% style="color:blue" %)**waterproof**(%%) and powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use for several years.
37 37  )))
38 38  
39 39  (((
40 -RS485-BL runs standard **LoRaWAN 1.0.3 in Class A**. It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server.
40 +RS485-BL runs standard (% style="color:blue" %)**LoRaWAN 1.0.3 in Class A**(%%). It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server.
41 41  )))
42 42  
43 43  (((
... ... @@ -54,8 +54,11 @@
54 54  
55 55  [[image:1652953304999-717.png||height="424" width="733"]]
56 56  
57 +
58 +
57 57  == 1.2 Specifications ==
58 58  
61 +
59 59  **Hardware System:**
60 60  
61 61  * STM32L072CZT6 MCU
... ... @@ -62,8 +62,6 @@
62 62  * SX1276/78 Wireless Chip 
63 63  * Power Consumption (exclude RS485 device):
64 64  ** Idle: 6uA@3.3v
65 -
66 -*
67 67  ** 20dB Transmit: 130mA@3.3v
68 68  
69 69  **Interface for Model:**
... ... @@ -93,8 +93,6 @@
93 93  * 127 dB Dynamic Range RSSI.
94 94  * Automatic RF Sense and CAD with ultra-fast AFC. ​​​
95 95  
96 -
97 -
98 98  == 1.3 Features ==
99 99  
100 100  * LoRaWAN Class A & Class C protocol (default Class A)
... ... @@ -106,8 +106,6 @@
106 106  * Support Modbus protocol
107 107  * Support Interrupt uplink
108 108  
109 -
110 -
111 111  == 1.4 Applications ==
112 112  
113 113  * Smart Buildings & Home Automation
... ... @@ -117,8 +117,6 @@
117 117  * Smart Cities
118 118  * Smart Factory
119 119  
120 -
121 -
122 122  == 1.5 Firmware Change log ==
123 123  
124 124  [[RS485-BL Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Firmware/||style="background-color: rgb(255, 255, 255);"]]
... ... @@ -127,6 +127,8 @@
127 127  == 1.6 Hardware Change log ==
128 128  
129 129  (((
125 +
126 +
130 130  v1.4
131 131  )))
132 132  
... ... @@ -209,8 +209,6 @@
209 209  )))
210 210  
211 211  
212 -
213 -
214 214  [[image:image-20220519174512-1.png]]
215 215  
216 216  [[image:image-20220519174512-2.png||height="328" width="731"]]
... ... @@ -234,6 +234,7 @@
234 234  
235 235  [[image:1652953568895-172.png||height="232" width="724"]]
236 236  
232 +
237 237  == 3.3 Configure Commands to read data ==
238 238  
239 239  (((
... ... @@ -320,6 +320,7 @@
320 320  )))
321 321  )))
322 322  
319 +
323 323  === 3.3.2 Configure sensors ===
324 324  
325 325  (((
... ... @@ -340,8 +340,9 @@
340 340  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
341 341  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
342 342  
343 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
340 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
344 344  
342 +
345 345  === 3.3.3 Configure read commands for each sampling ===
346 346  
347 347  (((
... ... @@ -439,7 +439,7 @@
439 439  
440 440  **Examples:**
441 441  
442 -1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
440 +1For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
443 443  
444 444  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
445 445  
... ... @@ -447,7 +447,7 @@
447 447  
448 448  [[image:1653271044481-711.png]]
449 449  
450 -1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
448 +2)For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
451 451  
452 452  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
453 453  
... ... @@ -466,16 +466,18 @@
466 466  * **c: define the position for valid value.  **
467 467  )))
468 468  
469 -Examples:
467 +**Examples:**
470 470  
471 471  * Grab bytes:
472 472  
473 473  [[image:1653271581490-837.png||height="313" width="722"]]
474 474  
473 +
475 475  * Grab a section.
476 476  
477 477  [[image:1653271648378-342.png||height="326" width="720"]]
478 478  
478 +
479 479  * Grab different sections.
480 480  
481 481  [[image:1653271657255-576.png||height="305" width="730"]]
... ... @@ -518,6 +518,7 @@
518 518  
519 519  [[image:1653271763403-806.png]]
520 520  
521 +
521 521  === 3.3.4 Compose the uplink payload ===
522 522  
523 523  (((
... ... @@ -525,7 +525,7 @@
525 525  )))
526 526  
527 527  (((
528 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
529 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
529 529  )))
530 530  
531 531  (((
... ... @@ -537,7 +537,7 @@
537 537  )))
538 538  
539 539  (((
540 -(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
541 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
541 541  )))
542 542  
543 543  (((
... ... @@ -546,8 +546,12 @@
546 546  
547 547  [[image:1653272787040-634.png||height="515" width="719"]]
548 548  
550 +
551 +
549 549  (((
550 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
553 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
554 +
555 +
551 551  )))
552 552  
553 553  (((
... ... @@ -559,7 +559,7 @@
559 559  )))
560 560  
561 561  (((
562 -(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
567 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
563 563  )))
564 564  
565 565  1. (((
... ... @@ -582,6 +582,7 @@
582 582  
583 583  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
584 584  
590 +
585 585  DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
586 586  
587 587  DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
... ... @@ -588,10 +588,12 @@
588 588  
589 589  DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
590 590  
597 +
591 591  Below are the uplink payloads:
592 592  
593 593  [[image:1653272901032-107.png]]
594 594  
602 +
595 595  (% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
596 596  
597 597   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
... ... @@ -602,6 +602,8 @@
602 602  
603 603   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
604 604  
613 +
614 +
605 605  === 3.3.5 Uplink on demand ===
606 606  
607 607  (((
... ... @@ -618,6 +618,8 @@
618 618  
619 619  (((
620 620  **0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
631 +
632 +
621 621  )))
622 622  
623 623  === 3.3.6 Uplink on Interrupt ===
... ... @@ -626,6 +626,7 @@
626 626  
627 627  [[image:1653273818896-432.png]]
628 628  
641 +
629 629  (((
630 630  AT+INTMOD=0  Disable Interrupt
631 631  )))
... ... @@ -640,6 +640,8 @@
640 640  
641 641  (((
642 642  AT+INTMOD=3  Interrupt trigger by rising edge.
656 +
657 +
643 643  )))
644 644  
645 645  == 3.4 Uplink Payload ==