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