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
-
... ... @@ -24,33 +24,23 @@ 24 24 25 25 ((( 26 26 ((( 27 -((( 28 28 The Dragino RS485-LN is a (% style="color:blue" %)**RS485 to LoRaWAN Converter**(%%). It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost. 29 29 ))) 30 -))) 31 31 32 32 ((( 33 -((( 34 34 RS485-LN allows user to (% style="color:blue" %)**monitor / control RS485 devices**(%%) and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, smartphone detection, building automation, and so on. 35 35 ))) 36 -))) 37 37 38 38 ((( 39 -((( 40 40 (% style="color:blue" %)**For data uplink**(%%), RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server. 41 41 ))) 42 -))) 43 43 44 44 ((( 45 -((( 46 46 (% style="color:blue" %)**For data downlink**(%%), RS485-LN runs in LoRaWAN Class C. When there downlink commands from LoRaWAN server, RS485-LN will forward the commands from LoRaWAN server to RS485 devices. 47 -))) 48 48 49 -((( 50 50 (% style="color:blue" %)**Demo Dashboard for RS485-LN**(%%) connect to two energy meters: [[https:~~/~~/app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a>>url:https://app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a]] 51 51 ))) 52 52 ))) 53 -))) 54 54 55 55 [[image:1653267211009-519.png||height="419" width="724"]] 56 56 ... ... @@ -103,7 +103,6 @@ 103 103 * Support Modbus protocol 104 104 * Support Interrupt uplink (Since hardware version v1.2) 105 105 106 - 107 107 == 1.4 Applications == 108 108 109 109 * Smart Buildings & Home Automation ... ... @@ -113,7 +113,6 @@ 113 113 * Smart Cities 114 114 * Smart Factory 115 115 116 - 117 117 == 1.5 Firmware Change log == 118 118 119 119 [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]] ... ... @@ -123,13 +123,9 @@ 123 123 124 124 ((( 125 125 ((( 126 -((( 127 127 v1.2: Add External Interrupt Pin. 128 -))) 129 129 130 -((( 131 131 v1.0: Release 132 -))) 133 133 134 134 135 135 ))) ... ... @@ -157,9 +157,7 @@ 157 157 == 3.1 How it works? == 158 158 159 159 ((( 160 -((( 161 161 The RS485-LN is configured as LoRaWAN OTAA Class C 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-LN. It will auto join the network via OTAA. 162 -))) 163 163 164 164 165 165 ))) ... ... @@ -249,19 +249,19 @@ 249 249 250 250 To use RS485-LN to read data from RS485 sensors, connect the RS485-LN A/B traces to the sensors. And user need to make sure RS485-LN use the match UART setting to access the sensors. The related commands for UART settings are: 251 251 252 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)253 -| =(% style="width:10px;" %)(((234 +(% border="1" style="background-color:#ffffcc; color:green; width:782px" %) 235 +|(% style="width:128px" %)((( 254 254 **AT Commands** 255 -)))| =(% style="width:190px;" %)(((237 +)))|(% style="width:305px" %)((( 256 256 **Description** 257 -)))| =(% style="width:190px;" %)(((239 +)))|(% style="width:346px" %)((( 258 258 **Example** 259 259 ))) 260 -|(% style="width:1 10px" %)(((242 +|(% style="width:128px" %)((( 261 261 AT+BAUDR 262 -)))|(% style="width: 190px" %)(((244 +)))|(% style="width:305px" %)((( 263 263 Set the baud rate (for RS485 connection). Default Value is: 9600. 264 -)))|(% style="width: 190px" %)(((246 +)))|(% style="width:346px" %)((( 265 265 ((( 266 266 AT+BAUDR=9600 267 267 ))) ... ... @@ -270,11 +270,11 @@ 270 270 Options: (1200,2400,4800,14400,19200,115200) 271 271 ))) 272 272 ))) 273 -|(% style="width:1 10px" %)(((255 +|(% style="width:128px" %)((( 274 274 AT+PARITY 275 -)))|(% style="width: 190px" %)(((257 +)))|(% style="width:305px" %)((( 276 276 Set UART parity (for RS485 connection) 277 -)))|(% style="width: 190px" %)(((259 +)))|(% style="width:346px" %)((( 278 278 ((( 279 279 AT+PARITY=0 280 280 ))) ... ... @@ -283,9 +283,9 @@ 283 283 Option: 0: no parity, 1: odd parity, 2: even parity 284 284 ))) 285 285 ))) 286 -|(% style="width:1 10px" %)(((268 +|(% style="width:128px" %)((( 287 287 AT+STOPBIT 288 -)))|(% style="width: 190px" %)(((270 +)))|(% style="width:305px" %)((( 289 289 ((( 290 290 Set serial stopbit (for RS485 connection) 291 291 ))) ... ... @@ -293,7 +293,7 @@ 293 293 ((( 294 294 295 295 ))) 296 -)))|(% style="width: 190px" %)(((278 +)))|(% style="width:346px" %)((( 297 297 ((( 298 298 AT+STOPBIT=0 for 1bit 299 299 ))) ... ... @@ -307,8 +307,6 @@ 307 307 ))) 308 308 ))) 309 309 310 - 311 - 312 312 === 3.3.2 Configure sensors === 313 313 314 314 ((( ... ... @@ -317,18 +317,16 @@ 317 317 ))) 318 318 ))) 319 319 320 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)321 -| =(% style="width: 110px;" %)**AT Commands**|=(% style="width:90px;" %)**Description**|=(% style="width:190px;" %)**Example**322 -|AT+CFGDEV|(% style="width:1 10px" %)(((300 +(% border="1" style="background-color:#ffffcc; color:green; width:806px" %) 301 +|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example** 302 +|AT+CFGDEV|(% style="width:418px" %)((( 323 323 This command is used to configure the RS485/TTL devices; they won’t be used during sampling. 324 324 325 325 AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx, 326 326 327 327 mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 328 -)))|(% style="width: 190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m308 +)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 329 329 330 - 331 - 332 332 === 3.3.3 Configure read commands for each sampling === 333 333 334 334 ((( ... ... @@ -374,8 +374,8 @@ 374 374 375 375 **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes. 376 376 377 -(% border="1" style="background-color:#4bacc6; color:white; width:5 10px" %)378 -|(% style="width: 510px" %)(((355 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %) 356 +|(% style="width:722px" %)((( 379 379 **AT+DATACUTx=a,b,c** 380 380 381 381 * **a: length for the return of AT+COMMAND** ... ... @@ -501,35 +501,33 @@ 501 501 502 502 == 3.4 Uplink Payload == 503 503 482 +(% border="1" style="background-color:#4bacc6; color:white; width:734px" %) 483 +|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands** 484 +|Value|(% style="width:120px" %)((( 485 +Battery(mV) 504 504 505 - [[image:image-20220606110929-1.png]]487 +& 506 506 489 +Interrupt _Flag 490 +)))|(% style="width:116px" %)((( 491 +PAYLOAD_VER 492 + 493 + 494 +)))|(% 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. 495 + 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 -))) 505 +* (% 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 -))) 507 +* (% 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,282 +548,142 @@ 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 -))) 531 +* **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 -))) 540 +* **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 -))) 546 +* MM: 1: add CRC-16/MODBUS ; 0: no CRC 547 +* NN: The length of RS485 command 548 +* XX XX XX XX: RS485 command total NN bytes 549 +* YY: How many bytes will be uplink from the return of this RS485 command, 550 +** if YY=0, RS485-LN will execute the downlink command without uplink; 551 +** if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200 552 +** 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 -))) 558 +* 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 -))) 560 +* 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 -))) 588 +* **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 -))) 595 +* **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 -))) 610 +* **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 -))) 623 +* **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 -))) 633 +* MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F, 634 +* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value. 635 +* LL: The length of AT+COMMAND or AT+DATACUT command 636 +* XX XX XX XX: AT+COMMAND or AT+DATACUT command 637 +* 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 -((( 799 799 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]]. 800 -))) 801 801 802 -((( 803 803 This command is valid since v1.3 firmware version 804 -))) 805 805 806 -((( 807 807 AT+MBFUN can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore. 808 -))) 809 809 810 -((( 811 - 812 -))) 813 813 814 -((( 815 815 **Example:** 816 -))) 817 817 818 -* ((( 819 -AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN. 820 -))) 821 -* ((( 822 -AT+COMMAND1= 01 03 00 10 00 08,1 ~-~-> read slave address 01 , function code 03, start address 00 01, quantity of registers 00 08. 823 -))) 824 -* ((( 825 -AT+COMMAND2= 01 02 00 40 00 10,1 ~-~-> read slave address 01 , function code 02, start address 00 40, quantity of inputs 00 10. 826 -))) 660 +* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN. 661 +* AT+COMMAND1= 01 03 00 10 00 08,1 ~-~-> read slave address 01 , function code 03, start address 00 01, quantity of registers 00 08. 662 +* AT+COMMAND2= 01 02 00 40 00 10,1 ~-~-> read slave address 01 , function code 02, start address 00 40, quantity of inputs 00 10. 827 827 828 828 [[image:image-20220602165351-6.png]] 829 829 ... ... @@ -831,260 +831,144 @@ 831 831 832 832 833 833 834 - 835 835 ==== **RS485 command timeout** ==== 836 836 837 -((( 838 838 Some Modbus device has slow action to send replies. This command is used to configure the RS485-LN to use longer time to wait for their action. 839 -))) 840 840 841 -((( 842 842 Default value: 0, range: 0 ~~ 65 seconds 843 -))) 844 844 845 -* ((( 846 -**AT Command:** 847 -))) 676 +* **AT Command:** 848 848 849 849 (% class="box infomessage" %) 850 850 ((( 851 -((( 852 852 **AT+CMDDLaa=hex(bb cc)*1000** 853 853 ))) 854 -))) 855 855 856 -((( 857 857 **Example:** 858 -))) 859 859 860 -((( 861 861 **AT+CMDDL1=1000** to send the open time to 1000ms 862 -))) 863 863 864 -((( 865 - 866 -))) 867 867 868 -* ((( 869 -**Downlink Payload:** 870 -))) 688 +* **Downlink Payload:** 871 871 872 -((( 873 873 **0x AA aa bb cc** 874 -))) 875 875 876 -((( 877 877 Same as: AT+CMDDLaa=hex(bb cc)*1000 878 -))) 879 879 880 -((( 881 881 **Example:** 882 -))) 883 883 884 -((( 885 885 0xAA 01 00 01 ~-~-> Same as **AT+CMDDL1=1000 ms** 886 -))) 887 887 888 888 889 889 890 - 891 891 ==== **Uplink payload mode** ==== 892 892 893 -((( 894 894 Define to use one uplink or multiple uplinks for the sampling. 895 -))) 896 896 897 -((( 898 898 The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]] 899 -))) 900 900 901 -* ((( 902 -**AT Command:** 903 -))) 706 +* **AT Command:** 904 904 905 905 (% class="box infomessage" %) 906 906 ((( 907 -((( 908 908 **AT+DATAUP=0** 909 909 ))) 910 -))) 911 911 912 912 (% class="box infomessage" %) 913 913 ((( 914 -((( 915 915 **AT+DATAUP=1** 916 916 ))) 917 -))) 918 918 919 -((( 920 - 921 -))) 922 922 923 -* ((( 924 -**Downlink Payload:** 925 -))) 719 +* **Downlink Payload:** 926 926 927 -((( 928 928 **0xAD 00** **~-~->** Same as AT+DATAUP=0 929 -))) 930 930 931 -((( 932 932 **0xAD 01** **~-~->** Same as AT+DATAUP=1 933 -))) 934 934 935 935 936 936 937 - 938 938 ==== **Manually trigger an Uplink** ==== 939 939 940 -((( 941 941 Ask device to send an uplink immediately. 942 -))) 943 943 944 -* ((( 945 -**AT Command:** 946 -))) 731 +* **AT Command:** 947 947 948 -((( 949 949 No AT Command for this, user can press the [[ACT button>>||anchor="H3.7Buttons"]] for 1 second for the same. 950 -))) 951 951 952 -((( 953 - 954 -))) 955 955 956 -* ((( 957 -**Downlink Payload:** 958 -))) 736 +* **Downlink Payload:** 959 959 960 -((( 961 961 **0x08 FF**, RS485-LN will immediately send an uplink. 962 -))) 963 963 964 964 965 965 966 - 967 967 ==== **Clear RS485 Command** ==== 968 968 969 -((( 970 970 The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them. 971 -))) 972 972 973 -* ((( 974 -**AT Command:** 975 -))) 746 +* **AT Command:** 976 976 977 -((( 978 978 **AT+CMDEAR=mm,nn** mm: start position of erase ,nn: stop position of erase 979 -))) 980 980 981 -((( 982 982 Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10 983 -))) 984 984 985 -((( 986 986 Example screen shot after clear all RS485 commands. 987 -))) 988 988 989 -((( 990 - 991 -))) 992 992 993 -((( 994 994 The uplink screen shot is: 995 -))) 996 996 997 997 [[image:1654160691922-496.png]] 998 998 999 999 1000 -* ((( 1001 -**Downlink Payload:** 1002 -))) 760 +* **Downlink Payload:** 1003 1003 1004 -((( 1005 1005 **0x09 aa bb** same as AT+CMDEAR=aa,bb 1006 -))) 1007 1007 1008 1008 1009 1009 1010 - 1011 1011 ==== **Set Serial Communication Parameters** ==== 1012 1012 1013 -((( 1014 1014 Set the Rs485 serial communication parameters: 1015 -))) 1016 1016 1017 -* ((( 1018 -**AT Command:** 1019 -))) 770 +* **AT Command:** 1020 1020 1021 -((( 1022 1022 Set Baud Rate: 1023 -))) 1024 1024 1025 1025 (% class="box infomessage" %) 1026 1026 ((( 1027 -((( 1028 1028 **AT+BAUDR=9600** ~/~/ Options: (1200,2400,4800,14400,19200,115200) 1029 1029 ))) 1030 -))) 1031 1031 1032 -((( 1033 1033 Set UART Parity 1034 -))) 1035 1035 1036 1036 (% class="box infomessage" %) 1037 1037 ((( 1038 -((( 1039 1039 **AT+PARITY=0** ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity 1040 1040 ))) 1041 -))) 1042 1042 1043 -((( 1044 1044 Set STOPBIT 1045 -))) 1046 1046 1047 1047 (% class="box infomessage" %) 1048 1048 ((( 1049 -((( 1050 1050 **AT+STOPBIT=0** ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits 1051 1051 ))) 1052 -))) 1053 1053 1054 -((( 1055 - 1056 -))) 1057 1057 1058 -* ((( 1059 -**Downlink Payload:** 1060 -))) 794 +* **Downlink Payload:** 1061 1061 1062 -((( 1063 1063 **A7 01 aa bb**: Same AT+BAUDR=hex(aa bb)*100 1064 -))) 1065 1065 1066 -((( 1067 1067 **Example:** 1068 -))) 1069 1069 1070 -* ((( 1071 -A7 01 00 60 same as AT+BAUDR=9600 1072 -))) 1073 -* ((( 1074 -A7 01 04 80 same as AT+BAUDR=115200 1075 -))) 800 +* A7 01 00 60 same as AT+BAUDR=9600 801 +* A7 01 04 80 same as AT+BAUDR=115200 1076 1076 1077 -((( 1078 1078 A7 02 aa: Same as AT+PARITY=aa (aa value: 00 , 01 or 02) 1079 -))) 1080 1080 1081 -((( 1082 1082 A7 03 aa: Same as AT+STOPBIT=aa (aa value: 00 , 01 or 02) 1083 -))) 1084 1084 1085 1085 1086 - 1087 - 1088 1088 == 3.6 Listening mode for RS485 network == 1089 1089 1090 1090 This feature support since firmware v1.4 ... ... @@ -1135,6 +1135,7 @@ 1135 1135 |**RST**|(% style="width:1420px" %)Reboot RS485 1136 1136 |**PRO**|(% style="width:1420px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]] 1137 1137 858 + 1138 1138 == 3.8 LEDs == 1139 1139 1140 1140 (% border="1" style="background-color:#f7faff; width:500px" %) ... ... @@ -1142,6 +1142,7 @@ 1142 1142 |**PWR**|Always on if there is power 1143 1143 |**SYS**|After device is powered on, the SYS will (% style="color:green" %)**fast blink in GREEN** (%%)for 5 times, means RS485-LN start to join LoRaWAN network. If join success, SYS will be (% style="color:green" %)**on GREEN for 5 seconds**(%%)**. **SYS will (% style="color:green" %)**blink Blue**(%%) on every upload and (% style="color:green" %)**blink Green**(%%) once receive a downlink message. 1144 1144 866 + 1145 1145 = 4. Case Study = 1146 1146 1147 1147 User can check this URL for some case studies: [[APP RS485 COMMUNICATE WITH SENSORS>>doc:Main.Application Note \: Communicate with Different Sensors ----- RS485-LN RS485-BL.WebHome]] ... ... @@ -1319,6 +1319,7 @@ 1319 1319 * (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865 1320 1320 1321 1321 1044 + 1322 1322 = 9.Packing Info = 1323 1323 1324 1324 ... ... @@ -1336,62 +1336,33 @@ 1336 1336 * Weight / pcs : 170g 1337 1337 1338 1338 1062 + 1339 1339 = 10. FCC Caution for RS485LN-US915 = 1340 1340 1341 -((( 1342 1342 Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment. 1343 -))) 1344 1344 1345 -((( 1346 1346 This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. 1347 -))) 1348 1348 1349 -((( 1350 - 1351 -))) 1352 1352 1353 -((( 1354 1354 **IMPORTANT NOTE:** 1355 -))) 1356 1356 1357 -((( 1358 1358 **Note: **This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: 1359 -))) 1360 1360 1361 -((( 1362 1362 —Reorient or relocate the receiving antenna. 1363 -))) 1364 1364 1365 -((( 1366 1366 —Increase the separation between the equipment and receiver. 1367 -))) 1368 1368 1369 -((( 1370 1370 —Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. 1371 -))) 1372 1372 1373 -((( 1374 1374 —Consult the dealer or an experienced radio/TV technician for help. 1375 -))) 1376 1376 1377 -((( 1378 - 1379 -))) 1380 1380 1381 -((( 1382 1382 **FCC Radiation Exposure Statement:** 1383 -))) 1384 1384 1385 -((( 1386 1386 This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment.This equipment should be installed and operated with minimum distance 20cm between the radiator& your body. 1387 -))) 1388 1388 1389 1389 1390 1390 = 11. Support = 1391 1391 1392 -* ((( 1393 -Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 1394 -))) 1395 -* ((( 1396 -Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]. 1397 -))) 1090 +* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 1091 +* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].
- image-20220606110929-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -13.9 KB - Content