Device Tab; Twincat 2.8; Twincat 2.9; Fig. 20 Twincat 2.8 - Fc310 Tab - Beckhoff FC3102 Documentation

FC310x as master
monitoring of the two PCs is triggered). The redundancy master only becomes active at the bus when the
StartRedundancyMaster flag is set (the startup takes approx. 10 times the min. slave interval (TwinCAT
2.8: see PROFIBUS [} 42] tab of the master, TwinCAT 2.9: see Bus Parameters [} 49] dialog). If the
StartRedundancyMaster flag is reset, the redundancy master stops its bus activity when the next token is
sent (at the end of the DP cycle, but no later than the Estimated Cycle Time (see "FC310x" tab (for
TwinCAT 2.8 [} 40] or TwinCAT 2.9 [} 48]) of the device)), without interrupting the connection to the slaves
(irrespective of the setting SetPrm-Unlock at Shutdown).
When setting the DP slave's DP watchdog (see the box's PROFIBUS [} 58] tab) it is important to ensure that
the DP watchdog time is longer than the application's monitoring time for the primary master plus the start-up
time of the redundancy master, so that the redundancy master can take over the DP slave without
interactions.
The redundancy master, furthermore, does not update any process data as long as it is only listening to the
bus. The DpState [} 25] of the boxes should be evaluated when it starts; if this is 0, the process data is also
up-to-date.
3.8

Device tab

3.8.1

TwinCAT 2.8

3.8.1.1 FC310x tab
Fig. 20: TwinCAT 2.8 - FC310 tab
PCI Slot/Irq: Indicates in which logical PCI slot the card was found.
Search...: Searches for all connected FC310x channels. Select those required. In the case of an FC3102
both channels A and B appear. These behave in logical terms like two FC3101 cards.
Hardware Configuration...: The hardware version number of the FC310x can be displayed here
40 Version: 3.0 FC3101 and FC3102