36
NETLink PRO ETH
and for PROFIBUS
‘126’
. However, any
values.
•
TSlot_Init This value is always
‘415’
for MPI –
whatever the baudrate. For PROFIBUS
the appropriate value should be read
from the PROFIBUS project.
•
Ttr
This value is always
‘9984’
for MPI –
whatever the baudrate. For PROFIBUS
the appropriate value should be read
from the PROFIBUS project.
•
Max. Tsdr This value is always
‘400’
for MPI –
whatever the baudrate. For PROFIBUS
the appropriate value should be read
from the PROFIBUS project.
•
Min. Tsdr This value is always
‘20’
for MPI –
whatever the baudrate. For PROFIBUS
the appropriate value should be read
from the PROFIBUS project.
•
Tset
This value is always
‘12’
for MPI –
whatever the baudrate. For PROFIBUS
the appropriate value should be read
from the PROFIBUS project.
•
Tqui
This value is always
‘0’
for MPI –
whatever the baudrate. For PROFIBUS
the appropriate value should be read
from the PROFIBUS project.
•
Gap
This value is always
‘5’
for MPI –
whatever the baudrate. For PROFIBUS
the appropriate value should be read
from the PROFIBUS project.
•
Retry
This value is always
‘2’
for MPI –
whatever the baudrate. For PROFIBUS
the appropriate value should be read
from the PROFIBUS project.
Please note that under unfavorable circumstances an incorrectly
parameterized NETLink PRO ETH can interfere with the bus to the extent
that regular bus operation is no longer possible.
For this reason, autobaud functionality is provided to ensure the correct
parameters are used, provided that the CPU supports this functionality.
8.1.4
Addressing (rack/slot mode ON/OFF)
RFC1006 connections are virtual point-to-point links, that is, links from the
PC to the programmable controller (possible branching within the
programmable controller is handled by the CPU => Routing).
Because NETLink PRO ETH is a point-to-multipoint communication
adapter (‘PC to NETLink PRO ETH’ on the one hand and ‘NETLink PRO
ETH to many bus stations’ on the other hand), it was necessary to implement
different addressing methods to permit all communication variations.
The addressing methods are
‘Addressed Mode’
(see Section 8.1.4.1) and
‘Rack/Slot Mode’
(see Section 8.1.4.2).
Incorrect bus parameters
can interfere with the bus
considerably!
