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