NETLink
®
Ethernet Products
• Max. Tsdr This value is always ‘400’ for MPI –
whatever the baud rate. For PROFIBUS
the appropriate value should be read
from the PROFIBUS project.
• Min. Tsdr This value is always ‘20’ for MPI –
whatever the baud rate. For PROFIBUS
the appropriate value should be read
from the PROFIBUS project.
• Tset This value is always ‘12’ for MPI –
whatever the baud rate. For PROFIBUS
the appropriate value should be read
from the PROFIBUS project.
• Tqui This value is always ‘0’ for MPI –
whatever the baud rate. For PROFIBUS
the appropriate value should be read
from the PROFIBUS project.
• Gap This value is always ‘5’ for MPI –
whatever the baud rate. For PROFIBUS
the appropriate value should be read
from the PROFIBUS project.
• Retry This value is always ‘2’ for MPI –
whatever the baud rate. For PROFIBUS
the appropriate value should be read
from the PROFIBUS project.
Please note that under unfavorable circumstances an incorrectly
parameterized NETLink
®
Gateway can interfere with the bus to
the extent that regular bus operation is no longer possible.
9.2 Addressing with Routing over RFC
Since the RFC 1006 protocol normally cannot be used to transmit
PLC routing information (MPI<->PROFIBUS) in a “connect re-
quest” frame, it was necessary to implement various addressing
methods in order to make the device compatible with all possible
communication setups. The parameters that are required for this
purpose can all be configured on the web interface used to man-
age NETLink
®
products.
These addressing methods are “RFC Multicomputing with TSAP”
(see Section 9.2.1) and “RFC Routing via CPs with TSAP” (see Sec-
tion 9.2.2).
These two addressing methods, which cannot be used together,
make it possible to use most communication setups that can also
be used with NETLink-S7-NET drivers.
Incorrect bus parameters
can
interfere with the bus
The required paths within
the automation system
are defined and managed
by the CPU => Routing.
To Next Page
Loading...
Need help?
General
