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