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