Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 29.3
edited by Xiaoling
on 2022/05/23 10:48
Change comment: There is no comment for this version
To version 29.41
edited by Xiaoling
on 2022/06/02 09:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,12 +7,15 @@
7 7  **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
8 8  
9 9  
10 +
10 10  **Table of Contents:**
11 11  
13 +{{toc/}}
12 12  
13 13  
14 14  
15 15  
18 +
16 16  = 1.Introduction =
17 17  
18 18  == 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
... ... @@ -22,19 +22,19 @@
22 22  )))
23 23  
24 24  (((
25 -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.
26 26  )))
27 27  
28 28  (((
29 -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.
30 30  )))
31 31  
32 32  (((
33 -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.
34 34  )))
35 35  
36 36  (((
37 -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.
38 38  )))
39 39  
40 40  (((
... ... @@ -51,8 +51,11 @@
51 51  
52 52  [[image:1652953304999-717.png||height="424" width="733"]]
53 53  
57 +
58 +
54 54  == 1.2 Specifications ==
55 55  
61 +
56 56  **Hardware System:**
57 57  
58 58  * STM32L072CZT6 MCU
... ... @@ -59,8 +59,6 @@
59 59  * SX1276/78 Wireless Chip 
60 60  * Power Consumption (exclude RS485 device):
61 61  ** Idle: 6uA@3.3v
62 -
63 -*
64 64  ** 20dB Transmit: 130mA@3.3v
65 65  
66 66  **Interface for Model:**
... ... @@ -114,9 +114,12 @@
114 114  
115 115  [[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);"]]
116 116  
121 +
117 117  == 1.6 Hardware Change log ==
118 118  
119 119  (((
125 +
126 +
120 120  v1.4
121 121  )))
122 122  
... ... @@ -140,6 +140,8 @@
140 140  
141 141  (((
142 142  Release version ​​​​​
150 +
151 +
143 143  )))
144 144  
145 145  = 2. Pin mapping and Power ON Device =
... ... @@ -153,6 +153,7 @@
153 153  
154 154  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
155 155  
165 +
156 156  = 3. Operation Mode =
157 157  
158 158  == 3.1 How it works? ==
... ... @@ -159,6 +159,8 @@
159 159  
160 160  (((
161 161  The RS485-BL is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join network. To connect a local LoRaWAN network, user just need to input the OTAA keys in the network server and power on the RS485-BL. It will auto join the network via OTAA.
172 +
173 +
162 162  )))
163 163  
164 164  == 3.2 Example to join LoRaWAN network ==
... ... @@ -194,8 +194,6 @@
194 194  )))
195 195  
196 196  
197 -
198 -
199 199  [[image:image-20220519174512-1.png]]
200 200  
201 201  [[image:image-20220519174512-2.png||height="328" width="731"]]
... ... @@ -219,10 +219,13 @@
219 219  
220 220  [[image:1652953568895-172.png||height="232" width="724"]]
221 221  
232 +
222 222  == 3.3 Configure Commands to read data ==
223 223  
224 224  (((
225 -There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>path:#AT_COMMAND]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors.
236 +There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors.
237 +
238 +
226 226  )))
227 227  
228 228  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
... ... @@ -323,8 +323,9 @@
323 323  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
324 324  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
325 325  
326 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
339 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
327 327  
341 +
328 328  === 3.3.3 Configure read commands for each sampling ===
329 329  
330 330  (((
... ... @@ -422,7 +422,7 @@
422 422  
423 423  **Examples:**
424 424  
425 -1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
439 +1）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
426 426  
427 427  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
428 428  
... ... @@ -430,7 +430,7 @@
430 430  
431 431  [[image:1653271044481-711.png]]
432 432  
433 -1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
447 +2）For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
434 434  
435 435  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
436 436  
... ... @@ -449,16 +449,18 @@
449 449  * **c: define the position for valid value.  **
450 450  )))
451 451  
452 -Examples:
466 +**Examples:**
453 453  
454 454  * Grab bytes:
455 455  
456 456  [[image:1653271581490-837.png||height="313" width="722"]]
457 457  
472 +
458 458  * Grab a section.
459 459  
460 460  [[image:1653271648378-342.png||height="326" width="720"]]
461 461  
477 +
462 462  * Grab different sections.
463 463  
464 464  [[image:1653271657255-576.png||height="305" width="730"]]
... ... @@ -501,6 +501,7 @@
501 501  
502 502  [[image:1653271763403-806.png]]
503 503  
520 +
504 504  === 3.3.4 Compose the uplink payload ===
505 505  
506 506  (((
... ... @@ -508,7 +508,7 @@
508 508  )))
509 509  
510 510  (((
511 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
528 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
512 512  )))
513 513  
514 514  (((
... ... @@ -520,7 +520,7 @@
520 520  )))
521 521  
522 522  (((
523 -(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
540 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
524 524  )))
525 525  
526 526  (((
... ... @@ -529,8 +529,12 @@
529 529  
530 530  [[image:1653272787040-634.png||height="515" width="719"]]
531 531  
549 +
550 +
532 532  (((
533 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
552 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
553 +
554 +
534 534  )))
535 535  
536 536  (((
... ... @@ -542,7 +542,7 @@
542 542  )))
543 543  
544 544  (((
545 -(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
566 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
546 546  )))
547 547  
548 548  1. (((
... ... @@ -565,6 +565,7 @@
565 565  
566 566  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
567 567  
589 +
568 568  DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
569 569  
570 570  DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
... ... @@ -571,10 +571,12 @@
571 571  
572 572  DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
573 573  
596 +
574 574  Below are the uplink payloads:
575 575  
576 576  [[image:1653272901032-107.png]]
577 577  
601 +
578 578  (% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
579 579  
580 580   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
... ... @@ -585,6 +585,8 @@
585 585  
586 586   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
587 587  
612 +
613 +
588 588  === 3.3.5 Uplink on demand ===
589 589  
590 590  (((
... ... @@ -601,6 +601,8 @@
601 601  
602 602  (((
603 603  **0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
630 +
631 +
604 604  )))
605 605  
606 606  === 3.3.6 Uplink on Interrupt ===
... ... @@ -609,6 +609,7 @@
609 609  
610 610  [[image:1653273818896-432.png]]
611 611  
640 +
612 612  (((
613 613  AT+INTMOD=0  Disable Interrupt
614 614  )))
... ... @@ -623,6 +623,8 @@
623 623  
624 624  (((
625 625  AT+INTMOD=3  Interrupt trigger by rising edge.
655 +
656 +
626 626  )))
627 627  
628 628  == 3.4 Uplink Payload ==
... ... @@ -650,47 +650,49 @@
650 650  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
651 651  
652 652  (((
653 -function Decoder(bytes, port) {
684 +{{{function Decoder(bytes, port) {}}}
654 654  )))
655 655  
656 656  (((
657 -~/~/Payload Formats of RS485-BL Deceive
688 +{{{//Payload Formats of RS485-BL Deceive}}}
658 658  )))
659 659  
660 660  (((
661 -return {
692 +{{{return {}}}
662 662  )))
663 663  
664 664  (((
665 - ~/~/Battery,units:V
696 +{{{ //Battery,units:V}}}
666 666  )))
667 667  
668 668  (((
669 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
700 +{{{ BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,}}}
670 670  )))
671 671  
672 672  (((
673 - ~/~/GPIO_EXTI 
704 +{{{ //GPIO_EXTI }}}
674 674  )))
675 675  
676 676  (((
677 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
708 +{{{ EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",}}}
678 678  )))
679 679  
680 680  (((
681 - ~/~/payload of version
712 +{{{ //payload of version}}}
682 682  )))
683 683  
684 684  (((
685 - Pay_ver:bytes[2],
716 +{{{ Pay_ver:bytes[2],}}}
686 686  )))
687 687  
688 688  (((
689 - };
720 +{{{ }; }}}
690 690  )))
691 691  
692 692  (((
693 - }
724 +}
725 +
726 +
694 694  )))
695 695  
696 696  (((
... ... @@ -699,29 +699,30 @@
699 699  
700 700  [[image:1653274001211-372.png||height="192" width="732"]]
701 701  
735 +
702 702  == 3.5 Configure RS485-BL via AT or Downlink ==
703 703  
704 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
738 +User can configure RS485-BL via AT Commands or LoRaWAN Downlink Commands
705 705  
706 706  There are two kinds of Commands:
707 707  
708 -* **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
742 +* (% 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]]
709 709  
710 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
744 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-BL.  User can see these commands below:
711 711  
712 -1.
713 -11.
714 -111. Common Commands:
715 715  
716 -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]]
747 +=== 3.5.1 Common Commands: ===
717 717  
749 +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]]
718 718  
719 -1.
720 -11.
721 -111. Sensor related commands:
722 722  
723 -==== Choose Device Type (RS485 or TTL) ====
752 +=== 3.5.2 Sensor related commands: ===
724 724  
754 +(% class="wikigeneratedid" %)
755 +==== ====
756 +
757 +==== **Choose Device Type (RS485 or TTL)** ====
758 +
725 725  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
726 726  
727 727  * AT Command