38
NETLink PRO ETH
This is achieved by only communicating directly with one, pre-
parameterized station. This station routes the data packets not intended for it
to the required rack/slot and routes the response back to the NETLink PRO
ETH.
This makes it possible, for example, to communicate in S7-400 systems with
more than one CPU on a rack (
Multicomputing) without having to attach
further CPUs to the bus.
To use this functionality, it is necessary to parameterize the following on the
configuration page of the Web interface:
•
‘Rack/slot mode’
must be enabled (ON)
•
For
‘Fix destination address for R/S mode’
, the address of the
required communication partner must be entered.
No special aspects have to be observed in the visualization system. The
settings for the rack and slot or remote TSAP must be made as the described
for the specific visualization system.
Section 8.2.2 explains addressed mode using WinCC as an example.
8.2
Example of configuration for WinCC V6.0
The basic parameterization of RFC1006 connections in visualization systems
is explained here using the example of the WinCC V6.0 tool from Siemens
AG.
It is assumed you are familiar with the development environment of WinCC,
so that only points relating specifically to the connection need to be
mentioned.
Because it is the Windows RFC1006 driver that is parameterized, all
elements you will see in the WinCC example can also be found in similar
form on other visualization systems/OPC servers that support RFC1006.
To explain the special aspects of communication with the NETLink PRO
ETH, the same connection is explained once for addressed mode (see
Section 8.2.1) and again in rack/slot mode (see Section 8.2.2).
8.2.1
Using addressed mode
For the basics of addressed mode at the NETLink PRO ETH end, see
Section 8.1.4.1.
To parameterize a RFC1006 link in WinCC, a new TCP/IP link must first be
created in the
‘SIMATIC S7 PROTOCOL SUITE’
. Here, this connection is
called
‘NETLink_PRO’
.
