Difference between revisions of "Client"

From Proview Wiki
Jump to: navigation, search
 
(3 intermediate revisions by one user not shown)
Line 1: Line 1:
−
<h1 id="firstHeading" class="firstHeading">Client</h1>
+
The Modbus TCP client in Proview allows you to connect to equipment which acts as Modbus TCP servers, such as remote I/O, PLCs etc.
−
<p>The Modbus TCP client in Proview allows you to connect to equipment which acts as Modbus TCP servers, such as remote I/O, PLCs etc.</p>
+
 
−
<h2><span id="Instructions" class="mw-headline"> Instructions </span></h2>
+
== Instructions ==
−
<p><strong>Here are the steps required to add a Modbus TCP client in Proview:</strong></p>
+
 
−
<ul>
+
'''Here are the steps required to add a Modbus TCP client in Proview:'''
−
<li> Create a Modbus_Master module for your node </li>
+
* Create a Modbus_Master module for your node
−
<li> Under the Modbus_Master module, add a Modbus_TCP_Slave </li>
+
* Under the Modbus_Master module, add a Modbus_TCP_Slave
−
<li> Configure the Modbus_TCP_Slave module with the ip/port for your plc (e.g. 192.168.1.60 / 502) </li>
+
* Configure the Modbus_TCP_Slave module with the ip/port for your plc (e.g. 192.168.1.60 / 502)
−
<li> Configure a Modbus_Module under the Modbus_TCP_Slave for each function code you want to use (Read_Coil, Read_Registers etc). </li>
+
* Configure a Modbus_Module under the Modbus_TCP_Slave for each function code you want to use (Read_Coil, Read_Registers etc).
−
<li> Configure the channel objects of the appropriate type for each Modbus_Module </li>
+
* Configure the channel objects of the appropriate type for each Modbus_Module
−
</ul>
+
 
−
<p>Now you can connect each of the channel objects to the appropriate variables in your plant hierarchy.</p>
+
Now you can connect each of the channel objects to the appropriate variables in your plant hierarchy.
−
<h2><span id="Screenshots" class="mw-headline"> Screenshots </span></h2>
+
 
−
<p><strong>Node hierarchy</strong></p>
+
== Screenshots ==
−
<p><a class="image" href="http://www.maba.dk/wiki/index.php?title=File:NodeHier.png"><img src="http://www.proview.se/wiki/images/7/7c/NodeHier.png" alt="NodeHier.png" width="374" height="242" /></a></p>
+
 
−
<p><strong>The configuration of the Modbus_TCP_Client:</strong></p>
+
'''Node hierarchy'''
−
<p><strong><img src="/wiki/index.php?title=File:ModbusTCPClientConfig.png" alt="Modbus TCP Client" /><br /></strong></p>
+
 
−
<p>&nbsp;</p>
+
[[File: NodeHier.png]]
−
<p><strong>The configuration of the ModbusModule:</strong></p>
+
 
−
<p><img src="/wiki/index.php?title=File:ModbusModuleConfig.png" alt="Modbus TCP Client Module" /></p>
+
'''The configuration of the Modbus_TCP_Client:'''
 +
 
 +
[[File: ModbusTCPClientConfig.png]]
 +
 
 +
'''The configuration of the ModbusModule:'''
 +
 
 +
[[File: ModbusModuleConfig.png]]

Latest revision as of 04:44, 22 August 2013

The Modbus TCP client in Proview allows you to connect to equipment which acts as Modbus TCP servers, such as remote I/O, PLCs etc.

[edit] Instructions

Here are the steps required to add a Modbus TCP client in Proview:

  • Create a Modbus_Master module for your node
  • Under the Modbus_Master module, add a Modbus_TCP_Slave
  • Configure the Modbus_TCP_Slave module with the ip/port for your plc (e.g. 192.168.1.60 / 502)
  • Configure a Modbus_Module under the Modbus_TCP_Slave for each function code you want to use (Read_Coil, Read_Registers etc).
  • Configure the channel objects of the appropriate type for each Modbus_Module

Now you can connect each of the channel objects to the appropriate variables in your plant hierarchy.

[edit] Screenshots

Node hierarchy

NodeHier.png

The configuration of the Modbus_TCP_Client:

ModbusTCPClientConfig.png

The configuration of the ModbusModule:

ModbusModuleConfig.png

Retrieved from "http://maba.dk/wiki/index.php?title=Client&oldid=157"
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox