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