Changes for page RS485-LN – RS485 to LoRaWAN Converter User Manual
Last modified by Bei Jinggeng on 2025/01/16 11:36
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 14 removed)
- image-20221130104310-1.png
- image-20221130104310-10.png
- image-20221130104310-11.png
- image-20221130104310-12.png
- image-20221130104310-13.png
- image-20221130104310-14.png
- image-20221130104310-2.png
- image-20221130104310-3.png
- image-20221130104310-4.png
- image-20221130104310-5.png
- image-20221130104310-6.png
- image-20221130104310-7.png
- image-20221130104310-8.png
- image-20221130104310-9.png
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Bei1 +XWiki.Xiaoling - Content
-
... ... @@ -33,28 +33,40 @@ 33 33 34 34 == 1.1 What is RS485-LN RS485 to LoRaWAN Converter == 35 35 36 - 37 37 ((( 37 +((( 38 +((( 39 + 40 + 38 38 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. 39 39 ))) 43 +))) 40 40 41 41 ((( 46 +((( 42 42 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. 43 43 ))) 49 +))) 44 44 45 45 ((( 52 +((( 46 46 (% 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. 47 47 ))) 55 +))) 48 48 49 49 ((( 58 +((( 50 50 (% 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. 51 51 ))) 52 52 53 53 ((( 54 54 (% 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]] 64 + 65 + 55 55 ))) 67 +))) 68 +))) 56 56 57 - 58 58 (% aria-label="1653267211009-519.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1653267211009-519.png||data-widget="image" height="419" width="724"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) 59 59 60 60 ... ... @@ -64,7 +64,7 @@ 64 64 65 65 (% style="color:#037691" %)**Hardware System:** 66 66 67 -* STM32L072 xxxxMCU79 +* STM32L072CZT6 MCU 68 68 * SX1276/78 Wireless Chip 69 69 * Power Consumption (exclude RS485 device): 70 70 ** Idle: 32mA@12v ... ... @@ -96,6 +96,8 @@ 96 96 * Automatic RF Sense and CAD with ultra-fast AFC. 97 97 * Packet engine up to 256 bytes with CRC 98 98 111 + 112 + 99 99 == 1.3 Features == 100 100 101 101 ... ... @@ -108,6 +108,8 @@ 108 108 * Support Modbus protocol 109 109 * Support Interrupt uplink (Since hardware version v1.2) 110 110 125 + 126 + 111 111 == 1.4 Applications == 112 112 113 113 ... ... @@ -118,6 +118,8 @@ 118 118 * Smart Cities 119 119 * Smart Factory 120 120 137 + 138 + 121 121 == 1.5 Firmware Change log == 122 122 123 123 ... ... @@ -291,10 +291,10 @@ 291 291 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: 292 292 293 293 294 -(% border="1" cellspacing=" 5" style="background-color:#ffffcc; color:green; width:510px" %)312 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 295 295 |=(% style="width: 110px;" %)((( 296 296 **AT Commands** 297 -)))|=(% style="width: 210px;" %)(((315 +)))|=(% style="width: 190px;" %)((( 298 298 **Description** 299 299 )))|=(% style="width: 190px;" %)((( 300 300 **Example** ... ... @@ -349,6 +349,8 @@ 349 349 ))) 350 350 ))) 351 351 370 + 371 + 352 352 === 3.3.2 Configure sensors === 353 353 354 354 ... ... @@ -360,8 +360,8 @@ 360 360 ))) 361 361 ))) 362 362 363 -(% border="1" cellspacing=" 5" style="background-color:#ffffcc; color:green; width:510px" %)364 -|=(% style="width: 110px;" %)**AT Commands**|=(% style="width: 210px;" %)**Description**|=(% style="width: 190px;" %)**Example**383 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 384 +|=(% style="width: 110px;" %)**AT Commands**|=(% style="width: 190px;" %)**Description**|=(% style="width: 190px;" %)**Example** 365 365 |AT+CFGDEV|(% style="width:110px" %)((( 366 366 ((( 367 367 This command is used to configure the RS485/TTL devices; they won’t be used during sampling. ... ... @@ -376,6 +376,8 @@ 376 376 ))) 377 377 )))|(% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 378 378 399 + 400 + 379 379 === 3.3.3 Configure read commands for each sampling === 380 380 381 381 ... ... @@ -408,7 +408,7 @@ 408 408 409 409 (% border="1" style="background-color:#4bacc6; color:white; width:499px" %) 410 410 |(% style="width:496px" %)((( 411 -**AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m** 433 +(% style="color:#037691" %)**AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m** 412 412 413 413 **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent** 414 414 ... ... @@ -494,15 +494,11 @@ 494 494 Final Payload is (% style="color:#4f81bd" %)**PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA** 495 495 496 496 497 -~1. PAYVER: Defined by AT+PAYVER 519 +1. PAYVER: Defined by AT+PAYVER 520 +1. PAYLOAD COUNT: Total how many uplinks of this sampling. 521 +1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 522 +1. DATA: Valid value: max 8 bytes for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 8 bytes 498 498 499 -2. PAYLOAD COUNT: Total how many uplinks of this sampling. 500 - 501 -3. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 502 - 503 -4. DATA: Valid value: max 8 bytes for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 8 bytes 504 - 505 - 506 506 (% aria-label="image-20220602155039-4.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602155039-4.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) 507 507 508 508 ... ... @@ -568,13 +568,13 @@ 568 568 == 3.4 Uplink Payload == 569 569 570 570 571 -(% border="1" cellspacing=" 5" style="background-color:#ffffcc; color:green; width:500px" %)572 -| =(% scope="row" style="width:60px;" %)(((589 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 590 +|(% style="width:90px" %)((( 573 573 Size(bytes) 574 -)))|(% style="width: 80px" %)1|(% style="width:360px" %)(((592 +)))|(% style="width:114px" %)1|(% style="width:353px" %)((( 575 575 Length depends on the return from the commands 576 576 ))) 577 -| =(% style="width:;" %)(((595 +|(% style="width:90px" %)((( 578 578 Value 579 579 )))|(% style="width:114px" %)((( 580 580 PAYLOAD_VER ... ... @@ -1186,26 +1186,23 @@ 1186 1186 ))) 1187 1187 1188 1188 1189 - 1190 - 1191 1191 ==== (% style="color:blue" %)**Configure Databit (Since Version 1.4.0)**(%%) ==== 1192 1192 1193 - 1194 1194 * ((( 1195 1195 (% style="color:#037691" %)** AT Command:** 1196 1196 ))) 1197 1197 1198 - (% style="color:#4472c4" %)** AT+DATABIT=7(%%)~/~/ Set the data bits to 71213 +**~ AT+DATABIT=7 **~/~/ Set the data bits to 7 1199 1199 1200 - (% style="color:#4472c4" %)** AT+DATABIT=8(%%)~/~/ Set the data bits to 81215 +**~ AT+DATABIT=8 **~/~/ Set the data bits to 8 1201 1201 1202 1202 * ((( 1203 1203 (% style="color:#037691" %)**Downlink Payload:** 1204 1204 ))) 1205 1205 1206 - (% style="color:#4472c4" %)** A7 04 07**(%%): Same as AT+DATABIT=71221 +**~ A7 04 07**: Same as AT+DATABIT=7 1207 1207 1208 - (% style="color:#4472c4" %)** A7 04 08**(%%): Same as AT+DATABIT=81223 +**~ A7 04 08**: Same as AT+DATABIT=8 1209 1209 1210 1210 1211 1211 ... ... @@ -1454,11 +1454,13 @@ 1454 1454 1455 1455 1456 1456 (% border="1.5" cellspacing="4" style="background-color:#ffffcc; width:430px" %) 1457 -|=(% style="width: 50px;" %)**Button**|=(% style="width: 3 80px;" %)**Feature**1472 +|=(% style="width: 50px;" %)**Button**|=(% style="width: 361px;" %)**Feature** 1458 1458 |(% style="width:50px" %)**ACT**|(% style="width:361px" %)If RS485 joined in network, press this button for more than 1 second, RS485 will upload a packet, and the SYS LED will give a (% style="color:blue" %)**Blue blink** 1459 1459 |(% style="width:50px" %)**RST**|(% style="width:361px" %)Reboot RS485 1460 1460 |(% style="width:50px" %)**PRO**|(% style="width:361px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]] 1461 1461 1477 + 1478 + 1462 1462 == 3.8 LEDs == 1463 1463 1464 1464 ... ... @@ -1467,6 +1467,8 @@ 1467 1467 |**PWR**|Always on if there is power 1468 1468 |**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. 1469 1469 1487 + 1488 + 1470 1470 = 4. Case Study = 1471 1471 1472 1472 ... ... @@ -1665,7 +1665,7 @@ 1665 1665 == 6.5 Can i use point to point communication for RS485-LN? == 1666 1666 1667 1667 1668 -Yes, please updating point-to-point [[firmware>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACP33wo_ZQLsxW2MJ70oUoba/RS485-LN/Firmware?dl=0&subfolder_nav_tracking=1]],thenrefer[[Point to Point Communication for RS485-LN>>Point to Point Communication for RS485-LN]].1687 +Yes, please refer [[Point to Point Communication for RS485-LN>>Point to Point Communication for RS485-LN]]. 1669 1669 1670 1670 1671 1671 ... ... @@ -1675,107 +1675,7 @@ 1675 1675 [[Use RS485-BL or RS485-LN to connect to RS232 devices. - DRAGINO>>url:http://8.211.40.43:8080/xwiki/bin/view/Main/RS485%20to%20RS232/]] 1676 1676 1677 1677 1678 -== 6.7 How to judge whether there is a problem with the set COMMAND == 1679 1679 1680 -=== 6.7.1 Introduce: === 1681 - 1682 - 1683 -Users can use below the structure to fast debug the communication between RS485BL and RS485-LN. The principle is to put the PC in the RS485 network and sniff the packet between Modbus MTU and RS485-BL/LN. We can use this way to: 1684 - 1685 -1. Test if Modbus-MTU works with PC commands. 1686 -1. Check if RS485-LN sent the expected command to Mobus-MTU 1687 -1. Check if Modbus-MTU return back the expected result to RS485-LN. 1688 -1. If both b) and c) has issue, we can compare PC’s output and RS485-LN output. 1689 - 1690 -[[image:image-20221130104310-1.png||height="380" width="680"]] 1691 - 1692 - 1693 -Example Connection: 1694 - 1695 -[[image:image-20221130104310-2.png]] 1696 - 1697 - 1698 -=== 6.7.2 Set up PC to monitor RS485 network With Serial tool === 1699 - 1700 -Note: Receive and send set to hex mode 1701 - 1702 -[[image:image-20221130104310-3.png||height="616" width="714"]] 1703 - 1704 - 1705 -=== 6.7.3 With ModRSsim2: === 1706 - 1707 -(1)Select serial port MODBUS RS-232 1708 - 1709 -[[image:image-20221130104310-4.png||height="390" width="865"]] 1710 - 1711 - 1712 -(2)Click the serial port icon 1713 - 1714 -[[image:image-20221130104310-5.png||height="392" width="870"]] 1715 - 1716 - 1717 -(3)After selecting the correct serial port and baud rate, click ok 1718 - 1719 -[[image:image-20221130104310-6.png]] 1720 - 1721 -(4)Click the comms. 1722 - 1723 -[[image:image-20221130104310-7.png||height="376" width="835"]] 1724 - 1725 -(% class="wikigeneratedid" id="HRunRS485-LN2FBLcommandandmonitorifitiscorrect." %) 1726 -Run RS485-LN/BL command and monitor if it is correct. 1727 - 1728 - 1729 -=== 6.7.4 Example – Test the CFGDEV command === 1730 - 1731 -RS485-LN sent below command: 1732 - 1733 -AT+CFGDEV=01 03 20 00 01 85 c0,1 to RS485 network, and PC is able to get this command and return commands from MTU to show in the serial tool. 1734 - 1735 - 1736 -We can see the output from the Serial port tool to analyze. And check if they are expected result. 1737 - 1738 -[[image:image-20221130104310-8.png||height="214" width="797"]] 1739 - 1740 -We can also use ModRSsim2 to see the output. 1741 - 1742 -[[image:image-20221130104310-9.png||height="531" width="729"]] 1743 - 1744 - 1745 - 1746 -=== 6.7.5 Example – Test CMD command sets. === 1747 - 1748 -Run AT+SENSORVALUE=1 to test the CMD commands set in RS485-LN. 1749 - 1750 - 1751 -Serial port tool: 1752 - 1753 -[[image:image-20221130104310-10.png||height="339" width="844"]] 1754 - 1755 -ModRSsim2: 1756 - 1757 -[[image:image-20221130104310-11.png||height="281" width="962"]] 1758 - 1759 - 1760 - 1761 -=== 6.7.6 Test with PC === 1762 - 1763 -If there is still have problem to set up correctly the commands between RS485-LN and MTU. User can test the correct RS485 command set in PC and compare with the RS485 command sent out via RS485-LN. as long as both commands are the same, the MTU should return correct result. 1764 - 1765 - 1766 -Or User can send the working commands set in PC serial tool to Dragino Support to check what should be configured in RS485-LN. 1767 - 1768 -Connection method: 1769 - 1770 -[[image:image-20221130104310-12.png]] 1771 - 1772 -Link situation: 1773 - 1774 -[[image:image-20221130104310-13.png||height="458" width="486"]] 1775 - 1776 -[[image:image-20221130104310-14.png||height="371" width="823"]] 1777 - 1778 - 1779 1779 = 7. Trouble Shooting = 1780 1780 1781 1781 ... ... @@ -1811,6 +1811,8 @@ 1811 1811 * (% style="color:red" %)**RU864**(%%): frequency bands RU864 1812 1812 * (% style="color:red" %)**KZ865**(%%): frequency bands KZ865 1813 1813 1733 + 1734 + 1814 1814 = 9.Packing Info = 1815 1815 1816 1816 ... ... @@ -1827,6 +1827,8 @@ 1827 1827 * Package Size / pcs : 14.5 x 8 x 5 cm 1828 1828 * Weight / pcs : 170g 1829 1829 1751 + 1752 + 1830 1830 = 10. FCC Caution for RS485LN-US915 = 1831 1831 1832 1832
- image-20221130104310-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -82.0 KB - Content
- image-20221130104310-10.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -17.4 KB - Content
- image-20221130104310-11.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -27.7 KB - Content
- image-20221130104310-12.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -392.9 KB - Content
- image-20221130104310-13.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -23.3 KB - Content
- image-20221130104310-14.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -25.4 KB - Content
- image-20221130104310-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -392.9 KB - Content
- image-20221130104310-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -30.4 KB - Content
- image-20221130104310-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -25.8 KB - Content
- image-20221130104310-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -22.9 KB - Content
- image-20221130104310-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -12.9 KB - Content
- image-20221130104310-7.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -25.1 KB - Content
- image-20221130104310-8.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -9.9 KB - Content
- image-20221130104310-9.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -29.1 KB - Content