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)
Details
- Page properties
-
- Content
-
... ... @@ -550,152 +550,77 @@ 550 550 551 551 ==== **RS485 Debug Command** ==== 552 552 553 -((( 554 554 This command is used to configure the RS485 devices; they won’t be used during sampling. 555 -))) 556 556 557 -* ((( 558 -**AT Command** 559 -))) 555 +* **AT Command** 560 560 561 561 (% class="box infomessage" %) 562 562 ((( 563 -((( 564 564 **AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m** 565 565 ))) 566 -))) 567 567 568 -((( 569 569 m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 570 -))) 571 571 572 -* ((( 573 -**Downlink Payload** 574 -))) 564 +* **Downlink Payload** 575 575 576 -((( 577 577 Format: A8 MM NN XX XX XX XX YY 578 -))) 579 579 580 -((( 581 581 Where: 582 -))) 583 583 584 -* ((( 585 -MM: 1: add CRC-16/MODBUS ; 0: no CRC 586 -))) 587 -* ((( 588 -NN: The length of RS485 command 589 -))) 590 -* ((( 591 -XX XX XX XX: RS485 command total NN bytes 592 -))) 593 -* ((( 594 -((( 595 -YY: How many bytes will be uplink from the return of this RS485 command, 596 -))) 570 +* MM: 1: add CRC-16/MODBUS ; 0: no CRC 571 +* NN: The length of RS485 command 572 +* XX XX XX XX: RS485 command total NN bytes 573 +* YY: How many bytes will be uplink from the return of this RS485 command, 574 +** if YY=0, RS485-LN will execute the downlink command without uplink; 575 +** if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200 576 +** if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200. 597 597 598 -* ((( 599 -if YY=0, RS485-LN will execute the downlink command without uplink; 600 -))) 601 -* ((( 602 -if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200 603 -))) 604 -* ((( 605 -if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200. 606 -))) 607 -))) 608 - 609 -((( 610 610 **Example 1** ~-~-> Configure without ask for uplink (YY=0) 611 -))) 612 612 613 -((( 614 614 To connect a Modbus Alarm with below commands. 615 -))) 616 616 617 -* ((( 618 -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. 619 -))) 582 +* 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 620 621 -* ((( 622 -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. 623 -))) 584 +* 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 624 625 -((( 626 626 So if user want to use downlink command to control to RS485 Alarm, he can use: 627 -))) 628 628 629 -((( 630 630 (% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm 631 -))) 632 632 633 -((( 634 634 (% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm 635 -))) 636 636 637 -((( 638 638 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. 639 -))) 640 640 641 -((( 642 - 643 -))) 644 644 645 -((( 646 646 **Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**) 647 -))) 648 648 649 -((( 650 650 User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY** 651 -))) 652 652 653 -((( 654 - 655 -))) 656 656 657 -((( 658 658 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: 659 -))) 660 660 661 -((( 662 662 **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00 **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00** 663 -))) 664 664 665 -((( 666 666 [[image:1654159460680-153.png]] 667 -))) 668 668 669 669 670 670 671 671 ==== **Set Payload version** ==== 672 672 673 -((( 674 674 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. 675 -))) 676 676 677 -* ((( 678 -**AT Command:** 679 -))) 612 +* **AT Command:** 680 680 681 681 (% class="box infomessage" %) 682 682 ((( 683 -((( 684 684 **AT+PAYVER: Set PAYVER field = 1** 685 685 ))) 686 -))) 687 687 688 -* ((( 689 -**Downlink Payload:** 690 -))) 619 +* **Downlink Payload:** 691 691 692 -((( 693 693 **0xAE 01** ~-~-> Set PAYVER field = 0x01 694 -))) 695 695 696 -((( 697 697 **0xAE 0F** ~-~-> Set PAYVER field = 0x0F 698 -))) 699 699 700 700 701 701