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, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -24,23 +24,33 @@ 24 24 25 25 ((( 26 26 ((( 27 +((( 27 27 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. 28 28 ))) 30 +))) 29 29 30 30 ((( 33 +((( 31 31 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. 32 32 ))) 36 +))) 33 33 34 34 ((( 39 +((( 35 35 (% 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. 36 36 ))) 42 +))) 37 37 38 38 ((( 45 +((( 39 39 (% 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 +))) 40 40 49 +((( 41 41 (% 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]] 42 42 ))) 43 43 ))) 53 +))) 44 44 45 45 [[image:1653267211009-519.png||height="419" width="724"]] 46 46 ... ... @@ -93,6 +93,7 @@ 93 93 * Support Modbus protocol 94 94 * Support Interrupt uplink (Since hardware version v1.2) 95 95 106 + 96 96 == 1.4 Applications == 97 97 98 98 * Smart Buildings & Home Automation ... ... @@ -102,6 +102,7 @@ 102 102 * Smart Cities 103 103 * Smart Factory 104 104 116 + 105 105 == 1.5 Firmware Change log == 106 106 107 107 [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]] ... ... @@ -111,9 +111,13 @@ 111 111 112 112 ((( 113 113 ((( 126 +((( 114 114 v1.2: Add External Interrupt Pin. 128 +))) 115 115 130 +((( 116 116 v1.0: Release 132 +))) 117 117 118 118 119 119 ))) ... ... @@ -141,7 +141,9 @@ 141 141 == 3.1 How it works? == 142 142 143 143 ((( 160 +((( 144 144 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 +))) 145 145 146 146 147 147 ))) ... ... @@ -231,19 +231,19 @@ 231 231 232 232 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: 233 233 234 -(% border="1" style="background-color:#ffffcc; color:green; width: 782px" %)235 -|(% style="width:1 28px" %)(((252 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 253 +|=(% style="width: 110px;" %)((( 236 236 **AT Commands** 237 -)))|(% style="width: 305px" %)(((255 +)))|=(% style="width: 190px;" %)((( 238 238 **Description** 239 -)))|(% style="width: 346px" %)(((257 +)))|=(% style="width: 190px;" %)((( 240 240 **Example** 241 241 ))) 242 -|(% style="width:1 28px" %)(((260 +|(% style="width:110px" %)((( 243 243 AT+BAUDR 244 -)))|(% style="width: 305px" %)(((262 +)))|(% style="width:190px" %)((( 245 245 Set the baud rate (for RS485 connection). Default Value is: 9600. 246 -)))|(% style="width: 346px" %)(((264 +)))|(% style="width:190px" %)((( 247 247 ((( 248 248 AT+BAUDR=9600 249 249 ))) ... ... @@ -252,11 +252,11 @@ 252 252 Options: (1200,2400,4800,14400,19200,115200) 253 253 ))) 254 254 ))) 255 -|(% style="width:1 28px" %)(((273 +|(% style="width:110px" %)((( 256 256 AT+PARITY 257 -)))|(% style="width: 305px" %)(((275 +)))|(% style="width:190px" %)((( 258 258 Set UART parity (for RS485 connection) 259 -)))|(% style="width: 346px" %)(((277 +)))|(% style="width:190px" %)((( 260 260 ((( 261 261 AT+PARITY=0 262 262 ))) ... ... @@ -265,9 +265,9 @@ 265 265 Option: 0: no parity, 1: odd parity, 2: even parity 266 266 ))) 267 267 ))) 268 -|(% style="width:1 28px" %)(((286 +|(% style="width:110px" %)((( 269 269 AT+STOPBIT 270 -)))|(% style="width: 305px" %)(((288 +)))|(% style="width:190px" %)((( 271 271 ((( 272 272 Set serial stopbit (for RS485 connection) 273 273 ))) ... ... @@ -275,7 +275,7 @@ 275 275 ((( 276 276 277 277 ))) 278 -)))|(% style="width: 346px" %)(((296 +)))|(% style="width:190px" %)((( 279 279 ((( 280 280 AT+STOPBIT=0 for 1bit 281 281 ))) ... ... @@ -289,6 +289,8 @@ 289 289 ))) 290 290 ))) 291 291 310 + 311 + 292 292 === 3.3.2 Configure sensors === 293 293 294 294 ((( ... ... @@ -297,16 +297,18 @@ 297 297 ))) 298 298 ))) 299 299 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" %)(((320 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 321 +|=(% style="width: 110px;" %)**AT Commands**|=(% style="width: 190px;" %)**Description**|=(% style="width: 190px;" %)**Example** 322 +|AT+CFGDEV|(% style="width:110px" %)((( 303 303 This command is used to configure the RS485/TTL devices; they won’t be used during sampling. 304 304 305 305 AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx, 306 306 307 307 mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 308 -)))|(% style="width: 256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m328 +)))|(% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 309 309 330 + 331 + 310 310 === 3.3.3 Configure read commands for each sampling === 311 311 312 312 ((( ... ... @@ -352,8 +352,8 @@ 352 352 353 353 **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes. 354 354 355 -(% border="1" style="background-color:#4bacc6; color:white; width: 725px" %)356 -|(% style="width: 722px" %)(((377 +(% border="1" style="background-color:#4bacc6; color:white; width:510px" %) 378 +|(% style="width:510px" %)((( 357 357 **AT+DATACUTx=a,b,c** 358 358 359 359 * **a: length for the return of AT+COMMAND** ... ... @@ -479,33 +479,35 @@ 479 479 480 480 == 3.4 Uplink Payload == 481 481 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) 486 486 487 - &505 +[[image:image-20220606110929-1.png]] 488 488 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 - 496 496 Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors. 497 497 498 498 499 499 == 3.5 Configure RS485-BL via AT or Downlink == 500 500 512 +((( 501 501 User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands 514 +))) 502 502 516 +((( 503 503 There are two kinds of Commands: 518 +))) 504 504 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]] 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 +))) 506 506 507 -* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN. User can see these commands below: 524 +* ((( 525 +(% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN. User can see these commands below: 526 +))) 508 508 528 +((( 529 + 530 +))) 531 + 532 + 509 509 === 3.5.1 Common Commands === 510 510 511 511 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]] ... ... @@ -524,82 +524,159 @@ 524 524 525 525 526 526 551 + 527 527 ==== **RS485 Debug Command** ==== 528 528 554 +((( 529 529 This command is used to configure the RS485 devices; they won’t be used during sampling. 556 +))) 530 530 531 -* **AT Command** 558 +* ((( 559 +**AT Command** 560 +))) 532 532 533 533 (% class="box infomessage" %) 534 534 ((( 564 +((( 535 535 **AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m** 536 536 ))) 567 +))) 537 537 569 +((( 538 538 m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 571 +))) 539 539 540 -* **Downlink Payload** 573 +* ((( 574 +**Downlink Payload** 575 +))) 541 541 577 +((( 542 542 Format: A8 MM NN XX XX XX XX YY 579 +))) 543 543 581 +((( 544 544 Where: 583 +))) 545 545 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. 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 +))) 553 553 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 +((( 554 554 **Example 1** ~-~-> Configure without ask for uplink (YY=0) 612 +))) 555 555 614 +((( 556 556 To connect a Modbus Alarm with below commands. 616 +))) 557 557 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. 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 +))) 559 559 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. 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 +))) 561 561 626 +((( 562 562 So if user want to use downlink command to control to RS485 Alarm, he can use: 628 +))) 563 563 630 +((( 564 564 (% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm 632 +))) 565 565 634 +((( 566 566 (% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm 636 +))) 567 567 638 +((( 568 568 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 +))) 569 569 642 +((( 643 + 644 +))) 570 570 646 +((( 571 571 **Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**) 648 +))) 572 572 650 +((( 573 573 User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY** 652 +))) 574 574 654 +((( 655 + 656 +))) 575 575 658 +((( 576 576 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 +))) 577 577 662 +((( 578 578 **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00 **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00** 664 +))) 579 579 666 +((( 580 580 [[image:1654159460680-153.png]] 668 +))) 581 581 582 582 583 583 584 584 ==== **Set Payload version** ==== 585 585 674 +((( 586 586 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. 676 +))) 587 587 588 -* **AT Command:** 678 +* ((( 679 +**AT Command:** 680 +))) 589 589 590 590 (% class="box infomessage" %) 591 591 ((( 684 +((( 592 592 **AT+PAYVER: Set PAYVER field = 1** 593 593 ))) 687 +))) 594 594 595 -* **Downlink Payload:** 689 +* ((( 690 +**Downlink Payload:** 691 +))) 596 596 693 +((( 597 597 **0xAE 01** ~-~-> Set PAYVER field = 0x01 695 +))) 598 598 697 +((( 599 599 **0xAE 0F** ~-~-> Set PAYVER field = 0x0F 699 +))) 600 600 601 601 602 602 703 + 603 603 ==== **Set RS485 Sampling Commands** ==== 604 604 605 605 AT+COMMANDx or AT+DATACUTx ... ... @@ -855,7 +855,6 @@ 855 855 |**RST**|(% style="width:1420px" %)Reboot RS485 856 856 |**PRO**|(% style="width:1420px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]] 857 857 858 - 859 859 == 3.8 LEDs == 860 860 861 861 (% border="1" style="background-color:#f7faff; width:500px" %) ... ... @@ -863,7 +863,6 @@ 863 863 |**PWR**|Always on if there is power 864 864 |**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. 865 865 866 - 867 867 = 4. Case Study = 868 868 869 869 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]] ... ... @@ -1041,7 +1041,6 @@ 1041 1041 * (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865 1042 1042 1043 1043 1044 - 1045 1045 = 9.Packing Info = 1046 1046 1047 1047 ... ... @@ -1059,33 +1059,62 @@ 1059 1059 * Weight / pcs : 170g 1060 1060 1061 1061 1062 - 1063 1063 = 10. FCC Caution for RS485LN-US915 = 1064 1064 1162 +((( 1065 1065 Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment. 1164 +))) 1066 1066 1166 +((( 1067 1067 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. 1168 +))) 1068 1068 1170 +((( 1171 + 1172 +))) 1069 1069 1174 +((( 1070 1070 **IMPORTANT NOTE:** 1176 +))) 1071 1071 1178 +((( 1072 1072 **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: 1180 +))) 1073 1073 1182 +((( 1074 1074 —Reorient or relocate the receiving antenna. 1184 +))) 1075 1075 1186 +((( 1076 1076 —Increase the separation between the equipment and receiver. 1188 +))) 1077 1077 1190 +((( 1078 1078 —Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. 1192 +))) 1079 1079 1194 +((( 1080 1080 —Consult the dealer or an experienced radio/TV technician for help. 1196 +))) 1081 1081 1198 +((( 1199 + 1200 +))) 1082 1082 1202 +((( 1083 1083 **FCC Radiation Exposure Statement:** 1204 +))) 1084 1084 1206 +((( 1085 1085 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. 1208 +))) 1086 1086 1087 1087 1088 1088 = 11. Support = 1089 1089 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]]. 1213 +* ((( 1214 +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. 1215 +))) 1216 +* ((( 1217 +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]]. 1218 +)))
- image-20220606110929-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +13.9 KB - Content