Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 29.12
edited by Xiaoling
on 2022/06/01 18:02
Change comment: There is no comment for this version
To version 25.1
edited by Xiaoling
on 2022/05/23 10:26
Change comment: Uploaded new attachment "1653272787040-634.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 ==
... ... @@ -104,8 +104,6 @@
104 104  * Support Modbus protocol
105 105  * Support Interrupt uplink
106 106  
107 -
108 -
109 109  == 1.4 Applications ==
110 110  
111 111  * Smart Buildings & Home Automation
... ... @@ -115,13 +115,10 @@
115 115  * Smart Cities
116 116  * Smart Factory
117 117  
118 -
119 -
120 120  == 1.5 Firmware Change log ==
121 121  
122 122  [[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);"]]
123 123  
124 -
125 125  == 1.6 Hardware Change log ==
126 126  
127 127  (((
... ... @@ -148,8 +148,6 @@
148 148  
149 149  (((
150 150  Release version ​​​​​
151 -
152 -
153 153  )))
154 154  
155 155  = 2. Pin mapping and Power ON Device =
... ... @@ -163,7 +163,6 @@
163 163  
164 164  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
165 165  
166 -
167 167  = 3. Operation Mode =
168 168  
169 169  == 3.1 How it works? ==
... ... @@ -170,8 +170,6 @@
170 170  
171 171  (((
172 172  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.
173 -
174 -
175 175  )))
176 176  
177 177  == 3.2 Example to join LoRaWAN network ==
... ... @@ -235,9 +235,7 @@
235 235  == 3.3 Configure Commands to read data ==
236 236  
237 237  (((
238 -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.
239 -
240 -
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.
241 241  )))
242 242  
243 243  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
... ... @@ -516,82 +516,64 @@
516 516  
517 517  [[image:1653271763403-806.png]]
518 518  
519 -=== 3.3.4 Compose the uplink payload ===
520 520  
521 -(((
505 +
506 +
507 +1.
508 +11.
509 +111. Compose the uplink payload
510 +
522 522  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.**
523 -)))
524 524  
525 -(((
526 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
527 -)))
528 528  
529 -(((
530 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
531 -)))
514 +**Examples: AT+DATAUP=0**
532 532  
533 -(((
516 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
517 +
534 534  Final Payload is
535 -)))
536 536  
537 -(((
538 -(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
539 -)))
520 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
540 540  
541 -(((
542 542  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
543 -)))
544 544  
545 -[[image:1653272787040-634.png||height="515" width="719"]]
524 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
546 546  
547 -(((
548 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
549 -)))
550 550  
551 -(((
552 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
553 -)))
554 554  
555 -(((
528 +**Examples: AT+DATAUP=1**
529 +
530 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
531 +
556 556  Final Payload is
557 -)))
558 558  
559 -(((
560 -(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
561 -)))
534 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
562 562  
563 -1. (((
564 -Battery Info (2 bytes): Battery voltage
565 -)))
566 -1. (((
567 -PAYVER (1 byte): Defined by AT+PAYVER
568 -)))
569 -1. (((
570 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
571 -)))
572 -1. (((
573 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
574 -)))
575 -1. (((
576 -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
577 -)))
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
578 578  
579 -[[image:1653272817147-600.png||height="437" width="717"]]
542 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
580 580  
544 +
581 581  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
582 582  
583 -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
584 584  
585 -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
586 586  
587 -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
588 588  
553 +
554 +
589 589  Below are the uplink payloads:
590 590  
591 -[[image:1653272901032-107.png]]
557 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
592 592  
593 -(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
594 594  
560 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
561 +
595 595   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
596 596  
597 597   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
... ... @@ -600,121 +600,90 @@
600 600  
601 601   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
602 602  
603 -=== 3.3.5 Uplink on demand ===
604 604  
605 -(((
571 +
572 +1.
573 +11.
574 +111. Uplink on demand
575 +
606 606  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.
607 -)))
608 608  
609 -(((
610 610  Downlink control command:
611 -)))
612 612  
613 -(((
614 -**0x08 command**: Poll an uplink with current command set in RS485-BL.
615 -)))
580 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
616 616  
617 -(((
618 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
619 -)))
582 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
620 620  
621 -=== 3.3.6 Uplink on Interrupt ===
622 622  
623 -Put the interrupt sensor between 3.3v_out and GPIO ext.
624 624  
625 -[[image:1653273818896-432.png]]
586 +1.
587 +11.
588 +111. Uplink on Interrupt
626 626  
627 -(((
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 +
628 628  AT+INTMOD=0  Disable Interrupt
629 -)))
630 630  
631 -(((
632 632  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
633 -)))
634 634  
635 -(((
636 636  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
637 -)))
638 638  
639 -(((
640 640  AT+INTMOD=3  Interrupt trigger by rising edge.
641 -)))
642 642  
643 -== 3.4 Uplink Payload ==
644 644  
645 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
646 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
647 -|Value|(% style="width:130px" %)(((
648 -(((
601 +1.
602 +11. Uplink Payload
603 +
604 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
605 +|Value|(((
649 649  Battery(mV)
650 -)))
651 651  
652 -(((
653 653  &
654 -)))
655 655  
656 -(((
657 657  Interrupt _Flag
658 -)))
659 -)))|(% style="width:93px" %)(((
611 +)))|(((
660 660  PAYLOAD_VER
661 661  
662 662  
663 -)))|(% 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.
664 664  
665 665  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
666 666  
667 -(((
619 +
668 668  function Decoder(bytes, port) {
669 -)))
670 670  
671 -(((
672 672  ~/~/Payload Formats of RS485-BL Deceive
673 -)))
674 674  
675 -(((
676 676  return {
677 -)))
678 678  
679 -(((
680 680   ~/~/Battery,units:V
681 -)))
682 682  
683 -(((
684 684   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
685 -)))
686 686  
687 -(((
688 688   ~/~/GPIO_EXTI 
689 -)))
690 690  
691 -(((
692 692   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
693 -)))
694 694  
695 -(((
696 696   ~/~/payload of version
697 -)))
698 698  
699 -(((
700 700   Pay_ver:bytes[2],
701 -)))
702 702  
703 -(((
704 704   };
705 -)))
706 706  
707 -(((
708 708   }
709 -)))
710 710  
711 -(((
642 +
643 +
644 +
645 +
646 +
647 +
712 712  TTN V3 uplink screen shot.
713 -)))
714 714  
715 -[[image:1653274001211-372.png||height="192" width="732"]]
650 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
716 716  
717 -== 3.5 Configure RS485-BL via AT or Downlink ==
652 +1.
653 +11. Configure RS485-BL via AT or Downlink
718 718  
719 719  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
720 720  
1653272817147-600.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -143.3 KB
Content
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