Changes for page RS485-LN – RS485 to LoRaWAN Converter User Manual
Last modified by Bei Jinggeng on 2025/01/16 11:36
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Content
-
... ... @@ -501,35 +501,33 @@ 501 501 502 502 == 3.4 Uplink Payload == 503 503 504 +(% border="1" style="background-color:#4bacc6; color:white; width:734px" %) 505 +|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands** 506 +|Value|(% style="width:120px" %)((( 507 +Battery(mV) 504 504 505 - [[image:image-20220606110929-1.png]]509 +& 506 506 511 +Interrupt _Flag 512 +)))|(% style="width:116px" %)((( 513 +PAYLOAD_VER 514 + 515 + 516 +)))|(% style="width:386px" %)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. 517 + 507 507 Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors. 508 508 509 509 510 510 == 3.5 Configure RS485-BL via AT or Downlink == 511 511 512 -((( 513 513 User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands 514 -))) 515 515 516 -((( 517 517 There are two kinds of Commands: 518 -))) 519 519 520 -* ((( 521 -(% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]] 522 -))) 527 +* (% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]] 523 523 524 -* ((( 525 -(% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN. User can see these commands below: 526 -))) 529 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN. User can see these commands below: 527 527 528 -((( 529 - 530 -))) 531 - 532 - 533 533 === 3.5.1 Common Commands === 534 534 535 535 They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]] ... ... @@ -548,251 +548,128 @@ 548 548 549 549 550 550 551 - 552 552 ==== **RS485 Debug Command** ==== 553 553 554 -((( 555 555 This command is used to configure the RS485 devices; they won’t be used during sampling. 556 -))) 557 557 558 -* ((( 559 -**AT Command** 560 -))) 553 +* **AT Command** 561 561 562 562 (% class="box infomessage" %) 563 563 ((( 564 -((( 565 565 **AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m** 566 566 ))) 567 -))) 568 568 569 -((( 570 570 m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 571 -))) 572 572 573 -* ((( 574 -**Downlink Payload** 575 -))) 562 +* **Downlink Payload** 576 576 577 -((( 578 578 Format: A8 MM NN XX XX XX XX YY 579 -))) 580 580 581 -((( 582 582 Where: 583 -))) 584 584 585 -* ((( 586 -MM: 1: add CRC-16/MODBUS ; 0: no CRC 587 -))) 588 -* ((( 589 -NN: The length of RS485 command 590 -))) 591 -* ((( 592 -XX XX XX XX: RS485 command total NN bytes 593 -))) 594 -* ((( 595 -((( 596 -YY: How many bytes will be uplink from the return of this RS485 command, 597 -))) 568 +* MM: 1: add CRC-16/MODBUS ; 0: no CRC 569 +* NN: The length of RS485 command 570 +* XX XX XX XX: RS485 command total NN bytes 571 +* YY: How many bytes will be uplink from the return of this RS485 command, 572 +** if YY=0, RS485-LN will execute the downlink command without uplink; 573 +** if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200 574 +** if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200. 598 598 599 -* ((( 600 -if YY=0, RS485-LN will execute the downlink command without uplink; 601 -))) 602 -* ((( 603 -if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200 604 -))) 605 -* ((( 606 -if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200. 607 -))) 608 -))) 609 - 610 -((( 611 611 **Example 1** ~-~-> Configure without ask for uplink (YY=0) 612 -))) 613 613 614 -((( 615 615 To connect a Modbus Alarm with below commands. 616 -))) 617 617 618 -* ((( 619 -The command to active alarm is: 0A 05 00 04 00 01 4C B0. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually. 620 -))) 580 +* The command to active alarm is: 0A 05 00 04 00 01 4C B0. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually. 621 621 622 -* ((( 623 -The command to deactivate alarm is: 0A 05 00 04 00 00 8D 70. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually. 624 -))) 582 +* The command to deactivate alarm is: 0A 05 00 04 00 00 8D 70. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually. 625 625 626 -((( 627 627 So if user want to use downlink command to control to RS485 Alarm, he can use: 628 -))) 629 629 630 -((( 631 631 (% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm 632 -))) 633 633 634 -((( 635 635 (% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm 636 -))) 637 637 638 -((( 639 639 A8 is type code and 01 means add CRC-16/MODBUS at the end, the 3^^rd^^ byte is 06, means the next 6 bytes are the command to be sent to the RS485 network, the final byte 00 means this command don’t need to acquire output. 640 -))) 641 641 642 -((( 643 - 644 -))) 645 645 646 -((( 647 647 **Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**) 648 -))) 649 649 650 -((( 651 651 User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY** 652 -))) 653 653 654 -((( 655 - 656 -))) 657 657 658 -((( 659 659 RS485-LN got this downlink command and send (% style="color:#4f81bd" %)**0A 08 00 04 00 01 **(%%)to Modbus network. One of the RS485 sensor in the network send back Modbus reply **0A 08 00 04 00 00**. RS485-LN get this reply and combine with the original downlink command and uplink. The uplink message is: 660 -))) 661 661 662 -((( 663 663 **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00 **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00** 664 -))) 665 665 666 -((( 667 667 [[image:1654159460680-153.png]] 668 -))) 669 669 670 670 671 671 672 - 673 673 ==== **Set Payload version** ==== 674 674 675 -((( 676 676 This is the first byte of the uplink payload. RS485-BL can connect to different sensors. User can set the PAYVER field to tell server how to decode the current payload. 677 -))) 678 678 679 -* ((( 680 -**AT Command:** 681 -))) 610 +* **AT Command:** 682 682 683 683 (% class="box infomessage" %) 684 684 ((( 685 -((( 686 686 **AT+PAYVER: Set PAYVER field = 1** 687 687 ))) 688 -))) 689 689 690 -* ((( 691 -**Downlink Payload:** 692 -))) 617 +* **Downlink Payload:** 693 693 694 -((( 695 695 **0xAE 01** ~-~-> Set PAYVER field = 0x01 696 -))) 697 697 698 -((( 699 699 **0xAE 0F** ~-~-> Set PAYVER field = 0x0F 700 -))) 701 701 702 702 703 703 704 - 705 705 ==== **Set RS485 Sampling Commands** ==== 706 706 707 -((( 708 708 AT+COMMANDx or AT+DATACUTx 709 -))) 710 710 711 -((( 712 712 These three commands are used to configure how the RS485-LN polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]]. 713 -))) 714 714 715 -((( 716 - 717 -))) 718 718 719 -* ((( 720 -**AT Command:** 721 -))) 632 +* **AT Command:** 722 722 723 723 (% class="box infomessage" %) 724 724 ((( 725 -((( 726 726 **AT+COMMANDx: Configure RS485 read command to sensor.** 727 727 ))) 728 -))) 729 729 730 730 (% class="box infomessage" %) 731 731 ((( 732 -((( 733 733 **AT+DATACUTx: Configure how to handle return from RS485 devices.** 734 734 ))) 735 -))) 736 736 737 -((( 738 - 739 -))) 740 740 741 -* ((( 742 -**Downlink Payload:** 743 -))) 645 +* **Downlink Payload:** 744 744 745 -((( 746 746 **0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx. 747 -))) 748 748 749 -((( 750 750 (% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink. 751 -))) 752 752 753 -((( 754 754 Format: AF MM NN LL XX XX XX XX YY 755 -))) 756 756 757 -((( 758 758 Where: 759 -))) 760 760 761 -* ((( 762 -MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F, 763 -))) 764 -* ((( 765 -NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value. 766 -))) 767 -* ((( 768 -LL: The length of AT+COMMAND or AT+DATACUT command 769 -))) 770 -* ((( 771 -XX XX XX XX: AT+COMMAND or AT+DATACUT command 772 -))) 773 -* ((( 774 -YY: If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-LN will execute an uplink after got this command. 775 -))) 655 +* MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F, 656 +* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value. 657 +* LL: The length of AT+COMMAND or AT+DATACUT command 658 +* XX XX XX XX: AT+COMMAND or AT+DATACUT command 659 +* YY: If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-LN will execute an uplink after got this command. 776 776 777 -((( 778 778 **Example:** 779 -))) 780 780 781 -((( 782 782 (% style="color:#037691" %)**AF 03 01 06 0A 05 00 04 00 01 00**(%%): Same as AT+COMMAND3=0A 05 00 04 00 01,1 783 -))) 784 784 785 -((( 786 786 (% style="color:#037691" %)**AF 03 02 06**(% style="color:orange" %)** 10 **(% style="color:red" %)**01 **(% style="color:green" %)**05 06 09 0A**(% style="color:#037691" %)** 00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**16**(%%),(% style="color:red" %)**1**(%%),(% style="color:green" %)**5+6+9+10** 787 -))) 788 788 789 -((( 790 790 (% style="color:#037691" %)**AF 03 02 06 **(% style="color:orange" %)**0B**(% style="color:red" %)** 02 **(% style="color:green" %)**05 07 08 0A **(% style="color:#037691" %)**00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**11**(%%),(% style="color:red" %)**2**(%%),(% style="color:green" %)**5~~7+8~~10** 791 -))) 792 792 793 793 794 794 795 - 796 796 ==== **Fast command to handle MODBUS device** ==== 797 797 798 798 AT+MBFUN is valid since v1.3 firmware version. The command is for fast configure to read Modbus devices. It is only valid for the devices which follow the [[MODBUS-RTU protocol>>url:https://www.modbustools.com/modbus.html]].
- image-20220606110929-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -13.9 KB - Content