Changes for page 1 Communication
Last modified by Hunter on 2024/07/01 10:54
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 7 removed)
Details
- Page properties
-
- Content
-
... ... @@ -2000,82 +2000,13 @@ 2000 2000 2001 2001 The following example is using the Linfee meter LNF96EY to demonstrate how to set up the Modbus communication. 2002 2002 2003 -~1. Wiring theRS485cablefirst. Because thepin 58 isA, thepin 59isB formeter.Herewe usetheCOM1 toconnect. Sothediagramlikefollows:2003 +~1. Check the specific Modbus parameter in the communication menu from LED display. 2004 2004 2005 -(% style="text-align:center" %) 2006 -[[image:LinfeeTerminalDiagram.png]] 2007 - 2008 -2. Check the specific Modbus parameter in the communication menu from LED display. 2009 - 2010 2010 So from the following pictures, we can know the Meter Address is 85, Baud rate is 9600, CRC None. 2011 2011 2012 -{{info}} 2013 -**✎Note: **Meter address usually corresponding to the Modbus Slave Station No. on the Modbus communication. 2014 -{{/info}} 2015 - 2016 2016 (% style="text-align:center" %) 2017 2017 [[image:MeterModbusAllView.png]] 2018 2018 2019 -(% class="wikigeneratedid" %) 2020 -3. Set up the communication in the Configuration tab. 2021 - 2022 -(% class="wikigeneratedid" %) 2023 -Select the protocol as **ModBus RTU Slave (All Function)**. And set the communication parameters like below. 2024 - 2025 -(% style="text-align:center" %) 2026 -[[image:VNETCommunicationtabmeter.png]] 2027 - 2028 -(% class="wikigeneratedid" %) 2029 -4. Create new real-time monitoring tag accroding to Modbus manual 2030 - 2031 -(% class="wikigeneratedid" %) 2032 -Enter the address we want to read from the meter. The following table is intercept part of the manual for Linfee Modbus manual. 2033 - 2034 -(% class="wikigeneratedid" %) 2035 -**0x03/0x04 command data register address**: 2036 - 2037 -(% style="width:1142.22px" %) 2038 -|(% style="display:none" %) |=(% colspan="2" rowspan="1" style="width: 165px;" %)Address(% style="display:none" %) |=Description|=Data Format|=(% style="width: 254px;" %)Data Length(Word)|=(% style="width: 282px;" %)Remark 2039 -|(%%)(% style="display:none" %) (%%) HEX|(% style="width:107px" %)DEC|(%%)(% style="display:none" %) (%%) |(% style="width:100px" %) |(%%)(% style="display:none" %) (%%) |(% style="width:318px" %) 2040 -|(% style="width:107px" %)0x00|(% style="width:100px" %)0|Reserved| | |(% style="width:318px" %) 2041 -|(% style="width:107px" %)0x02|(% style="width:100px" %)2|Reserved| | |(% style="width:318px" %) 2042 -|(% style="width:107px" %)0x04|(% style="width:100px" %)4|Reserved| | |(% style="width:318px" %) 2043 -|(% style="width:107px" %)0x06|(% style="width:100px" %)6|Ua|float|2|(% style="width:318px" %)Phase Voltage data, Unit V 2044 -|(% style="width:107px" %)0x08|(% style="width:100px" %)8|Ub|float|2|(% style="width:318px" %)Phase Voltage data, Unit V 2045 -|(% style="width:107px" %)0x0A|(% style="width:100px" %)10|Uc|float|2|(% style="width:318px" %)Phase Voltage data, Unit V 2046 -|(% style="width:107px" %)0x0C|(% style="width:100px" %)12|Uab|float|2|(% style="width:318px" %)Line Voltage data, Unit V 2047 -|(% style="width:107px" %)0x0E|(% style="width:100px" %)14|Ubc|float|2|(% style="width:318px" %)Line Voltage data, Unit V 2048 -|(% style="width:107px" %)0x10|(% style="width:100px" %)16|Uca|float|2|(% style="width:318px" %)Line Voltage data, Unit V 2049 -|(% style="width:107px" %)0x12|(% style="width:100px" %)18|Ia|float|2|(% style="width:318px" %)Phase Current data, Unit A 2050 -|(% style="width:107px" %)0x14|(% style="width:100px" %)20|Ib|float|2|(% style="width:318px" %)Phase Current data, Unit A 2051 -|(% style="width:107px" %)0x16|(% style="width:100px" %)22|Ic|float|2|(% style="width:318px" %)Phase Current data, Unit A 2052 - 2053 -{{info}} 2054 -**✎Note: **We usually use the Data Type 4 for read the Modbus registers(Function Code 03) 2055 -{{/info}} 2056 - 2057 -For example, here we want to read the Phase Voltage Ua (Modbus offset 0006), the Modbus register main No. requires input decimal number, and check whether the actual address has one address offset, so the tag configured like the following screenshot: 2058 - 2059 -(% style="text-align:center" %) 2060 -[[image:VNETModbusTagSettings.png]] 2061 - 2062 -(% style="text-align:center" %) 2063 -[[image:VNETModbusTagByteSettings.png]] 2064 - 2065 -{{info}} 2066 -**✎Note: **If the read value is incorrect, please check whether need to change the Byte order. 2067 -{{/info}} 2068 - 2069 -Set the Modbus Slave Station No. 2070 - 2071 -(% style="text-align:center" %) 2072 -[[image:ModbusStationSettings.png]] 2073 - 2074 -If the communication is setup successfully, the tag will show green light. 2075 - 2076 -(% style="text-align:center" %) 2077 -[[image:Monitoringtaggreenlight.png]] 2078 - 2079 2079 == **MODBUS RTU Master** == 2080 2080 2081 2081 Select the protocol "Modbus RTU Master",
- 1679563870401-671.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Hunter - Size
-
... ... @@ -1,1 +1,0 @@ 1 -39.3 KB - Content
- LinfeeTerminalDiagram.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Hunter - Size
-
... ... @@ -1,1 +1,0 @@ 1 -8.6 KB - Content
- ModbusStationSettings.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Hunter - Size
-
... ... @@ -1,1 +1,0 @@ 1 -35.8 KB - Content
- Monitoringtaggreenlight.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Hunter - Size
-
... ... @@ -1,1 +1,0 @@ 1 -7.5 KB - Content
- VNETCommunicationtabmeter.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Hunter - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.0 KB - Content
- VNETModbusTagByteSettings.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Hunter - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.2 KB - Content
- VNETModbusTagSettings.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Hunter - Size
-
... ... @@ -1,1 +1,0 @@ 1 -35.7 KB - Content