<
From version < 79.7 >
edited by Xiaoling
on 2022/10/27 11:03
To version < 97.1 >
edited by Bei Jinggeng
on 2022/11/30 10:55
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -64,7 +64,7 @@
64 64  
65 65  (% style="color:#037691" %)**Hardware System:**
66 66  
67 -* STM32L072CZT6 MCU
67 +* STM32L072xxxx MCU
68 68  * SX1276/78 Wireless Chip 
69 69  * Power Consumption (exclude RS485 device):
70 70  ** Idle: 32mA@12v
... ... @@ -96,8 +96,6 @@
96 96  * Automatic RF Sense and CAD with ultra-fast AFC.
97 97  * Packet engine up to 256 bytes with CRC
98 98  
99 -
100 -
101 101  == 1.3 Features ==
102 102  
103 103  
... ... @@ -110,8 +110,6 @@
110 110  * Support Modbus protocol
111 111  * Support Interrupt uplink (Since hardware version v1.2)
112 112  
113 -
114 -
115 115  == 1.4 Applications ==
116 116  
117 117  
... ... @@ -122,8 +122,6 @@
122 122  * Smart Cities
123 123  * Smart Factory
124 124  
125 -
126 -
127 127  == 1.5 Firmware Change log ==
128 128  
129 129  
... ... @@ -355,8 +355,6 @@
355 355  )))
356 356  )))
357 357  
358 -
359 -
360 360  === 3.3.2 Configure sensors ===
361 361  
362 362  
... ... @@ -384,8 +384,6 @@
384 384  )))
385 385  )))|(% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
386 386  
387 -
388 -
389 389  === 3.3.3 Configure read commands for each sampling ===
390 390  
391 391  
... ... @@ -1200,21 +1200,22 @@
1200 1200  
1201 1201  ==== (% style="color:blue" %)**Configure Databit (Since Version 1.4.0)**(%%) ====
1202 1202  
1193 +
1203 1203  * (((
1204 1204  (% style="color:#037691" %)** AT Command:**
1205 1205  )))
1206 1206  
1207 -**~ AT+DATABIT=7    **~/~/ Set the data bits to 7
1198 +(% style="color:#4472c4" %)** AT+DATABIT=7    **(%%)~/~/ Set the data bits to 7
1208 1208  
1209 -**~ AT+DATABIT=8    **~/~/ Set the data bits to 8
1200 +(% style="color:#4472c4" %)** AT+DATABIT=8    **(%%)~/~/ Set the data bits to 8
1210 1210  
1211 1211  * (((
1212 1212  (% style="color:#037691" %)**Downlink Payload:**
1213 1213  )))
1214 1214  
1215 -**~ A7 04 07**: Same as  AT+DATABIT=7
1206 +(% style="color:#4472c4" %)** A7 04 07**(%%): Same as  AT+DATABIT=7
1216 1216  
1217 -**~ A7 04 08**: Same as  AT+DATABIT=8
1208 +(% style="color:#4472c4" %)** A7 04 08**(%%): Same as  AT+DATABIT=8
1218 1218  
1219 1219  
1220 1220  
... ... @@ -1468,8 +1468,6 @@
1468 1468  |(% style="width:50px" %)**RST**|(% style="width:361px" %)Reboot RS485
1469 1469  |(% style="width:50px" %)**PRO**|(% style="width:361px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]]
1470 1470  
1471 -
1472 -
1473 1473  == 3.8 LEDs ==
1474 1474  
1475 1475  
... ... @@ -1478,8 +1478,6 @@
1478 1478  |**PWR**|Always on if there is power
1479 1479  |**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.
1480 1480  
1481 -
1482 -
1483 1483  = 4. Case Study =
1484 1484  
1485 1485  
... ... @@ -1678,7 +1678,7 @@
1678 1678  == 6.5 Can i use point to point communication for RS485-LN? ==
1679 1679  
1680 1680  
1681 -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]].
1682 1682  
1683 1683  
1684 1684  
... ... @@ -1688,7 +1688,107 @@
1688 1688  [[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/]]
1689 1689  
1690 1690  
1678 +== 6.7 How to judge whether there is a problem with the set COMMAND ==
1691 1691  
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 +
1692 1692  = 7. Trouble Shooting =
1693 1693  
1694 1694  
... ... @@ -1724,8 +1724,6 @@
1724 1724  * (% style="color:red" %)**RU864**(%%):  frequency bands RU864
1725 1725  * (% style="color:red" %)**KZ865**(%%):  frequency bands KZ865
1726 1726  
1727 -
1728 -
1729 1729  = 9.Packing Info =
1730 1730  
1731 1731  
... ... @@ -1742,8 +1742,6 @@
1742 1742  * Package Size / pcs : 14.5 x 8 x 5 cm
1743 1743  * Weight / pcs : 170g
1744 1744  
1745 -
1746 -
1747 1747  = 10. FCC Caution for RS485LN-US915 =
1748 1748  
1749 1749  
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
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0