Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 29.34
edited by Xiaoling
on 2022/06/02 08:59
Change comment: There is no comment for this version
To version 26.1
edited by Xiaoling
on 2022/05/23 10:26
Change comment: Uploaded new attachment "1653272817147-600.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -7,15 +7,12 @@
7 7  **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
8 8  
9 9  
10 -
11 11  **Table of Contents:**
12 12  
13 -{{toc/}}
14 14  
15 15  
16 16  
17 17  
18 -
19 19  = 1.Introduction =
20 20  
21 21  == 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
... ... @@ -25,19 +25,19 @@
25 25  )))
26 26  
27 27  (((
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.
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.
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 (% 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.
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.
33 33  )))
34 34  
35 35  (((
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.
33 +RS485-BL is IP67 **waterproof** and powered by **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 (% 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.
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.
41 41  )))
42 42  
43 43  (((
... ... @@ -54,11 +54,8 @@
54 54  
55 55  [[image:1652953304999-717.png||height="424" width="733"]]
56 56  
57 -
58 -
59 59  == 1.2 Specifications ==
60 60  
61 -
62 62  **Hardware System:**
63 63  
64 64  * STM32L072CZT6 MCU
... ... @@ -65,6 +65,8 @@
65 65  * SX1276/78 Wireless Chip 
66 66  * Power Consumption (exclude RS485 device):
67 67  ** Idle: 6uA@3.3v
62 +
63 +*
68 68  ** 20dB Transmit: 130mA@3.3v
69 69  
70 70  **Interface for Model:**
... ... @@ -118,12 +118,9 @@
118 118  
119 119  [[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);"]]
120 120  
121 -
122 122  == 1.6 Hardware Change log ==
123 123  
124 124  (((
125 -
126 -
127 127  v1.4
128 128  )))
129 129  
... ... @@ -147,8 +147,6 @@
147 147  
148 148  (((
149 149  Release version ​​​​​
150 -
151 -
152 152  )))
153 153  
154 154  = 2. Pin mapping and Power ON Device =
... ... @@ -162,7 +162,6 @@
162 162  
163 163  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
164 164  
165 -
166 166  = 3. Operation Mode =
167 167  
168 168  == 3.1 How it works? ==
... ... @@ -169,8 +169,6 @@
169 169  
170 170  (((
171 171  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 -
174 174  )))
175 175  
176 176  == 3.2 Example to join LoRaWAN network ==
... ... @@ -206,6 +206,8 @@
206 206  )))
207 207  
208 208  
197 +
198 +
209 209  [[image:image-20220519174512-1.png]]
210 210  
211 211  [[image:image-20220519174512-2.png||height="328" width="731"]]
... ... @@ -229,13 +229,10 @@
229 229  
230 230  [[image:1652953568895-172.png||height="232" width="724"]]
231 231  
232 -
233 233  == 3.3 Configure Commands to read data ==
234 234  
235 235  (((
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 -
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.
239 239  )))
240 240  
241 241  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
... ... @@ -316,7 +316,6 @@
316 316  )))
317 317  )))
318 318  
319 -
320 320  === 3.3.2 Configure sensors ===
321 321  
322 322  (((
... ... @@ -337,9 +337,8 @@
337 337  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
338 338  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
339 339  
340 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
326 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
341 341  
342 -
343 343  === 3.3.3 Configure read commands for each sampling ===
344 344  
345 345  (((
... ... @@ -437,7 +437,7 @@
437 437  
438 438  **Examples:**
439 439  
440 -1）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
425 +1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
441 441  
442 442  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
443 443  
... ... @@ -445,7 +445,7 @@
445 445  
446 446  [[image:1653271044481-711.png]]
447 447  
448 -2）For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
433 +1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
449 449  
450 450  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
451 451  
... ... @@ -464,18 +464,16 @@
464 464  * **c: define the position for valid value.  **
465 465  )))
466 466  
467 -**Examples:**
452 +Examples:
468 468  
469 469  * Grab bytes:
470 470  
471 471  [[image:1653271581490-837.png||height="313" width="722"]]
472 472  
473 -
474 474  * Grab a section.
475 475  
476 476  [[image:1653271648378-342.png||height="326" width="720"]]
477 477  
478 -
479 479  * Grab different sections.
480 480  
481 481  [[image:1653271657255-576.png||height="305" width="730"]]
... ... @@ -519,86 +519,62 @@
519 519  [[image:1653271763403-806.png]]
520 520  
521 521  
522 -=== 3.3.4 Compose the uplink payload ===
523 523  
524 -(((
506 +
507 +1.
508 +11.
509 +111. Compose the uplink payload
510 +
525 525  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.**
526 -)))
527 527  
528 -(((
529 -(% style="color:#037691" %)**Examples: AT+DATAUP=0**
530 -)))
531 531  
532 -(((
533 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
534 -)))
514 +**Examples: AT+DATAUP=0**
535 535  
536 -(((
516 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
517 +
537 537  Final Payload is
538 -)))
539 539  
540 -(((
541 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
542 -)))
520 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
543 543  
544 -(((
545 545  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
546 -)))
547 547  
548 -[[image:1653272787040-634.png||height="515" width="719"]]
524 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
549 549  
550 550  
551 551  
552 -(((
553 -(% style="color:#037691" %)**Examples: AT+DATAUP=1**
528 +**Examples: AT+DATAUP=1**
554 554  
555 -
556 -)))
530 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
557 557  
558 -(((
559 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
560 -)))
561 -
562 -(((
563 563  Final Payload is
564 -)))
565 565  
566 -(((
567 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
568 -)))
534 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
569 569  
570 -1. (((
571 -Battery Info (2 bytes): Battery voltage
572 -)))
573 -1. (((
574 -PAYVER (1 byte): Defined by AT+PAYVER
575 -)))
576 -1. (((
577 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
578 -)))
579 -1. (((
580 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
581 -)))
582 -1. (((
583 -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
584 -)))
536 +1. Battery Info (2 bytes): Battery voltage
537 +1. PAYVER (1 byte): Defined by AT+PAYVER
538 +1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
539 +1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
540 +1. DATA: Valid value: max 6 bytes(US915 version here, [[Notice*!>>path:#max_byte]]) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
585 585  
586 -[[image:1653272817147-600.png||height="437" width="717"]]
542 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
587 587  
544 +
588 588  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
589 589  
590 -DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
547 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
591 591  
592 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
549 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
593 593  
594 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
551 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
595 595  
553 +
554 +
596 596  Below are the uplink payloads:
597 597  
598 -[[image:1653272901032-107.png]]
557 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
599 599  
600 600  
601 -(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
560 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
602 602  
603 603   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
604 604  
... ... @@ -608,121 +608,90 @@
608 608  
609 609   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
610 610  
611 -=== 3.3.5 Uplink on demand ===
612 612  
613 -(((
571 +
572 +1.
573 +11.
574 +111. Uplink on demand
575 +
614 614  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.
615 -)))
616 616  
617 -(((
618 618  Downlink control command:
619 -)))
620 620  
621 -(((
622 -**0x08 command**: Poll an uplink with current command set in RS485-BL.
623 -)))
580 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
624 624  
625 -(((
626 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
627 -)))
582 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
628 628  
629 -=== 3.3.6 Uplink on Interrupt ===
630 630  
631 -Put the interrupt sensor between 3.3v_out and GPIO ext.
632 632  
633 -[[image:1653273818896-432.png]]
586 +1.
587 +11.
588 +111. Uplink on Interrupt
634 634  
635 -(((
590 +Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
591 +
636 636  AT+INTMOD=0  Disable Interrupt
637 -)))
638 638  
639 -(((
640 640  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
641 -)))
642 642  
643 -(((
644 644  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
645 -)))
646 646  
647 -(((
648 648  AT+INTMOD=3  Interrupt trigger by rising edge.
649 -)))
650 650  
651 -== 3.4 Uplink Payload ==
652 652  
653 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
654 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
655 -|Value|(% style="width:130px" %)(((
656 -(((
601 +1.
602 +11. Uplink Payload
603 +
604 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
605 +|Value|(((
657 657  Battery(mV)
658 -)))
659 659  
660 -(((
661 661  &
662 -)))
663 663  
664 -(((
665 665  Interrupt _Flag
666 -)))
667 -)))|(% style="width:93px" %)(((
611 +)))|(((
668 668  PAYLOAD_VER
669 669  
670 670  
671 -)))|(% style="width:509px" %)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.
615 +)))|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.
672 672  
673 673  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
674 674  
675 -(((
619 +
676 676  function Decoder(bytes, port) {
677 -)))
678 678  
679 -(((
680 680  ~/~/Payload Formats of RS485-BL Deceive
681 -)))
682 682  
683 -(((
684 684  return {
685 -)))
686 686  
687 -(((
688 688   ~/~/Battery,units:V
689 -)))
690 690  
691 -(((
692 692   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
693 -)))
694 694  
695 -(((
696 696   ~/~/GPIO_EXTI 
697 -)))
698 698  
699 -(((
700 700   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
701 -)))
702 702  
703 -(((
704 704   ~/~/payload of version
705 -)))
706 706  
707 -(((
708 708   Pay_ver:bytes[2],
709 -)))
710 710  
711 -(((
712 712   };
713 -)))
714 714  
715 -(((
716 716   }
717 -)))
718 718  
719 -(((
642 +
643 +
644 +
645 +
646 +
647 +
720 720  TTN V3 uplink screen shot.
721 -)))
722 722  
723 -[[image:1653274001211-372.png||height="192" width="732"]]
650 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
724 724  
725 -== 3.5 Configure RS485-BL via AT or Downlink ==
652 +1.
653 +11. Configure RS485-BL via AT or Downlink
726 726  
727 727  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
728 728  
1653272901032-107.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -197.8 KB
Content
1653273818896-432.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -31.6 KB
Content
1653274001211-372.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -91.4 KB
Content