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 (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 14 added, 0 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
-
- Content
-
... ... @@ -33,40 +33,28 @@ 33 33 34 34 == 1.1 What is RS485-LN RS485 to LoRaWAN Converter == 35 35 36 -((( 37 -((( 38 -((( 39 - 40 40 37 +((( 41 41 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. 42 42 ))) 43 -))) 44 44 45 45 ((( 46 -((( 47 47 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. 48 48 ))) 49 -))) 50 50 51 51 ((( 52 -((( 53 53 (% 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. 54 54 ))) 55 -))) 56 56 57 57 ((( 58 -((( 59 59 (% 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. 60 60 ))) 61 61 62 62 ((( 63 63 (% 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 - 66 66 ))) 67 -))) 68 -))) 69 69 57 + 70 70 (% 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" %) 71 71 72 72 ... ... @@ -76,7 +76,7 @@ 76 76 77 77 (% style="color:#037691" %)**Hardware System:** 78 78 79 -* STM32L072 CZT6MCU67 +* STM32L072xxxx MCU 80 80 * SX1276/78 Wireless Chip 81 81 * Power Consumption (exclude RS485 device): 82 82 ** Idle: 32mA@12v ... ... @@ -303,10 +303,10 @@ 303 303 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: 304 304 305 305 306 -(% border="1" cellspacing=" 10" style="background-color:#ffffcc; color:green; width:510px" %)294 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 307 307 |=(% style="width: 110px;" %)((( 308 308 **AT Commands** 309 -)))|=(% style="width: 1 90px;" %)(((297 +)))|=(% style="width: 210px;" %)((( 310 310 **Description** 311 311 )))|=(% style="width: 190px;" %)((( 312 312 **Example** ... ... @@ -372,8 +372,8 @@ 372 372 ))) 373 373 ))) 374 374 375 -(% border="1" cellspacing=" 10" style="background-color:#ffffcc; color:green; width:510px" %)376 -|=(% style="width: 110px;" %)**AT Commands**|=(% style="width: 1 90px;" %)**Description**|=(% style="width: 190px;" %)**Example**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** 377 377 |AT+CFGDEV|(% style="width:110px" %)((( 378 378 ((( 379 379 This command is used to configure the RS485/TTL devices; they won’t be used during sampling. ... ... @@ -420,7 +420,7 @@ 420 420 421 421 (% border="1" style="background-color:#4bacc6; color:white; width:499px" %) 422 422 |(% style="width:496px" %)((( 423 - (% style="color:#037691" %)**AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**411 +**AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m** 424 424 425 425 **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent** 426 426 ... ... @@ -506,11 +506,15 @@ 506 506 Final Payload is (% style="color:#4f81bd" %)**PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA** 507 507 508 508 509 -1. PAYVER: Defined by AT+PAYVER 510 -1. PAYLOAD COUNT: Total how many uplinks of this sampling. 511 -1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 512 -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 497 +~1. PAYVER: Defined by AT+PAYVER 513 513 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 + 514 514 (% 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" %) 515 515 516 516 ... ... @@ -575,17 +575,18 @@ 575 575 576 576 == 3.4 Uplink Payload == 577 577 578 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:800px" %) 579 -|((( 570 + 571 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %) 572 +|=(% scope="row" style="width: 60px;" %)((( 580 580 Size(bytes) 581 -)))|1|((( 574 +)))|(% style="width:80px" %)1|(% style="width:360px" %)((( 582 582 Length depends on the return from the commands 583 583 ))) 584 -|((( 577 +|=(% style="width: 90px;" %)((( 585 585 Value 586 -)))|((( 579 +)))|(% style="width:114px" %)((( 587 587 PAYLOAD_VER 588 -)))|((( 581 +)))|(% style="width:353px" %)((( 589 589 If the valid payload is too long and exceed the maximum 590 590 591 591 support payload length in server, server will show payload not ... ... @@ -1193,23 +1193,26 @@ 1193 1193 ))) 1194 1194 1195 1195 1189 + 1190 + 1196 1196 ==== (% style="color:blue" %)**Configure Databit (Since Version 1.4.0)**(%%) ==== 1197 1197 1193 + 1198 1198 * ((( 1199 1199 (% style="color:#037691" %)** AT Command:** 1200 1200 ))) 1201 1201 1202 -** ~AT+DATABIT=7 **~/~/ Set the data bits to 71198 +(% style="color:#4472c4" %)** AT+DATABIT=7 **(%%)~/~/ Set the data bits to 7 1203 1203 1204 -** ~AT+DATABIT=8 **~/~/Set the data bits to 81200 +(% style="color:#4472c4" %)** AT+DATABIT=8 **(%%)~/~/ Set the data bits to 8 1205 1205 1206 1206 * ((( 1207 1207 (% style="color:#037691" %)**Downlink Payload:** 1208 1208 ))) 1209 1209 1210 -** ~A7 04 07**: Same as AT+DATABIT=71206 +(% style="color:#4472c4" %)** A7 04 07**(%%): Same as AT+DATABIT=7 1211 1211 1212 -** ~A7 04 08**: Same as AT+DATABIT=81208 +(% style="color:#4472c4" %)** A7 04 08**(%%): Same as AT+DATABIT=8 1213 1213 1214 1214 1215 1215 ... ... @@ -1288,20 +1288,17 @@ 1288 1288 1289 1289 (% style="color:#4472c4" %)** AT+RPL=5** (%%) ~/~/ After receiving the package from the server, it will immediately upload the content of the package to the server, the port number is 100. 1290 1290 1291 - 1292 1292 Example:**aa xx xx xx xx** ~/~/ aa indicates whether the configuration has changed, 00 is yes, 01 is no; xx xx xx xx are the bytes sent. 1293 1293 1294 1294 1295 1295 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173747-6.png?width=1124&height=165&rev=1.1||alt="image-20220823173747-6.png"]] 1296 1296 1297 - 1298 - 1299 1299 For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77. 1300 1300 1301 1301 1295 + 1302 1302 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]] 1303 1303 1304 - 1305 1305 For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. 1306 1306 1307 1307 ... ... @@ -1343,7 +1343,7 @@ 1343 1343 (% style="color:#037691" %)**Downlink Payload:** 1344 1344 ))) 1345 1345 1346 -(% style="color:#4472c4" %)** A6 aa bb bb ** (%%) ~/~/same as AT+RXMODE=aa,bb 1339 +(% style="color:#4472c4" %)** A6 aa bb bb ** (%%) ~/~/ same as AT+RXMODE=aa,bb 1347 1347 1348 1348 [[image:image-20220824144240-1.png]] 1349 1349 ... ... @@ -1460,8 +1460,8 @@ 1460 1460 == 3.7 Buttons == 1461 1461 1462 1462 1463 -(% border="1" cellspacing=" 10" style="background-color:#f7faff; width:430px" %)1464 -|=(% style="width: 50px;" %)**Button**|=(% style="width: 3 61px;" %)**Feature**1456 +(% border="1.5" cellspacing="4" style="background-color:#ffffcc; width:430px" %) 1457 +|=(% style="width: 50px;" %)**Button**|=(% style="width: 380px;" %)**Feature** 1465 1465 |(% 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** 1466 1466 |(% style="width:50px" %)**RST**|(% style="width:361px" %)Reboot RS485 1467 1467 |(% style="width:50px" %)**PRO**|(% style="width:361px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]] ... ... @@ -1469,7 +1469,7 @@ 1469 1469 == 3.8 LEDs == 1470 1470 1471 1471 1472 -(% border="1" cellspacing=" 10" style="background-color:#f7faff; width:430px" %)1465 +(% border="1.5" cellspacing="4" style="background-color:#ffffcc; width:430px" %) 1473 1473 |=(% style="width: 50px;" %)**LEDs**|=(% style="width: 380px;" %)**Feature** 1474 1474 |**PWR**|Always on if there is power 1475 1475 |**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. ... ... @@ -1672,7 +1672,7 @@ 1672 1672 == 6.5 Can i use point to point communication for RS485-LN? == 1673 1673 1674 1674 1675 -Yes, please refer [[Point to Point Communication for RS485-LN>>Point to Point Communication for RS485-LN]]. 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]],then refer [[Point to Point Communication for RS485-LN>>Point to Point Communication for RS485-LN]]. 1676 1676 1677 1677 1678 1678 ... ... @@ -1682,7 +1682,106 @@ 1682 1682 [[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/]] 1683 1683 1684 1684 1678 +== 6.7 How to judge whether there is a problem with the set COMMAND == 1685 1685 1680 +=== 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 +=== Set up PC to monitor RS485 network === 1699 + 1700 +=== With Serial tool === 1701 + 1702 +Note: Receive and send set to hex mode 1703 + 1704 +[[image:image-20221130104310-3.png||height="616" width="714"]] 1705 + 1706 + 1707 +=== With ModRSsim2: === 1708 + 1709 +(1)Select serial port MODBUS RS-232 1710 + 1711 +[[image:image-20221130104310-4.png||height="390" width="865"]] 1712 + 1713 + 1714 +(2)Click the serial port icon 1715 + 1716 +[[image:image-20221130104310-5.png||height="392" width="870"]] 1717 + 1718 + 1719 +(3)After selecting the correct serial port and baud rate, click ok 1720 + 1721 +[[image:image-20221130104310-6.png]] 1722 + 1723 +(4)Click the comms. 1724 + 1725 +[[image:image-20221130104310-7.png||height="376" width="835"]] 1726 + 1727 +=== Run RS485-LN/BL command and monitor if it is correct. === 1728 + 1729 +=== 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 +=== 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 +=== 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 + 1686 1686 = 7. Trouble Shooting = 1687 1687 1688 1688
- image-20221130104310-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +82.0 KB - Content
- image-20221130104310-10.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +17.4 KB - Content
- image-20221130104310-11.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +27.7 KB - Content
- image-20221130104310-12.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +392.9 KB - Content
- image-20221130104310-13.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +23.3 KB - Content
- image-20221130104310-14.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +25.4 KB - Content
- image-20221130104310-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +392.9 KB - Content
- image-20221130104310-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +30.4 KB - Content
- image-20221130104310-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +25.8 KB - Content
- image-20221130104310-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +22.9 KB - Content
- image-20221130104310-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +12.9 KB - Content
- image-20221130104310-7.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +25.1 KB - Content
- image-20221130104310-8.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +9.9 KB - Content
- image-20221130104310-9.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +29.1 KB - Content