Last modified by Bei Jinggeng on 2025/01/16 11:36
<
From version < 58.5 >
edited by Xiaoling
on 2022/06/06 11:21
To version < 57.40 >
edited by Xiaoling
on 2022/06/06 09:35
>
Change comment: There is no comment for this version

Summary

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: 110px;" %)(((
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:110px" %)(((
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:110px" %)(((
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:110px" %)(((
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: 190px;" %)**Description**|=(% style="width: 190px;" %)**Example**
322 -|AT+CFGDEV|(% style="width:110px" %)(((
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,m
308 +)))|(% 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:510px" %)
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]]
... ... @@ -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 -)))
531 +* **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 -)))
540 +* **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 -)))
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.
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 -)))
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.
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 -)))
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.
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 -)))
588 +* **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 -)))
595 +* **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  
... ... @@ -954,6 +954,7 @@
954 954  |**RST**|(% style="width:1420px" %)Reboot RS485
955 955  |**PRO**|(% style="width:1420px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]]
956 956  
858 +
957 957  == 3.8 LEDs ==
958 958  
959 959  (% border="1" style="background-color:#f7faff; width:500px" %)
... ... @@ -961,6 +961,7 @@
961 961  |**PWR**|Always on if there is power
962 962  |**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.
963 963  
866 +
964 964  = 4. Case Study =
965 965  
966 966  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]]
... ... @@ -1138,6 +1138,7 @@
1138 1138  * (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
1139 1139  
1140 1140  
1044 +
1141 1141  = 9.Packing Info =
1142 1142  
1143 1143  
... ... @@ -1155,6 +1155,7 @@
1155 1155  * Weight / pcs : 170g
1156 1156  
1157 1157  
1062 +
1158 1158  = 10. FCC Caution for RS485LN-US915 =
1159 1159  
1160 1160  (((
image-20220606110929-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -13.9 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0