Professional Documents
Culture Documents
User manual
User manual
Installing and operating the RFC 460R PN 3TX Remote Field Controller
as a redundant control system
2016-05-20
Revision: 03
Order No.: —
This is the safety alert symbol. It is used to alert you to potential personal injury
hazards. Obey all safety measures that follow this symbol to avoid possible
injury or death.
There are three different categories of personal injury that are indicated with a
signal word.
DANGER This indicates a hazardous situation which, if not avoided, will
result in death or serious injury.
WARNING This indicates a hazardous situation which, if not avoided, could
result in death or serious injury.
CAUTION This indicates a hazardous situation which, if not avoided, could
result in minor or moderate injury.
This symbol together with the signal word NOTE and the accompanying text
alert the reader to a situation which may cause damage or malfunction to the
device, hardware/software, or surrounding property.
This symbol and the accompanying text provide the reader with additional
information or refer to detailed sources of information.
How to contact us
Internet Up-to-date information on Phoenix Contact products and our Terms and Conditions can be
found on the Internet at:
phoenixcontact.com
Make sure you always use the latest documentation.
It can be downloaded at:
phoenixcontact.net/products
Subsidiaries If there are any problems that cannot be solved using the documentation, please contact
your Phoenix Contact subsidiary.
Subsidiary contact information is available at phoenixcontact.com.
PHOENIX CONTACT
Please observe the following notes
PHOENIX CONTACT
Table of contents
1 Introduction ................................................................................................................................9
1.1 Purpose of this user manual ..................................................................................9
1.2 Hardware and software requirements....................................................................9
1.3 Increased safety precautions...............................................................................10
5 Startup .....................................................................................................................................71
5.1 Startup .................................................................................................................71
5.2 Preparing the Remote Field Controllers of
the redundant control system for operation..........................................................73
5.2.1 Specifying the redundancy type of the RFC 460R PN 3TX
Remote Field Controllers .....................................................................73
5.2.2 Specifying the IP addresses of
the Remote Field Controller defined as FIRST .....................................78
5.2.3 Applying the settings – synchronizing the redundant control system ....82
B Appendixes.............................................................................................................................143
B1 List of figures .....................................................................................................143
B2 List of tables ......................................................................................................149
B3 Index..................................................................................................................151
1 Introduction
This user manual is intended to familiarize you with how the redundant control system,
which consists of two RFC 460R PN 3TX Remote Field Controllers connected via fiber optic
synchronization connection, works and how the RFC 460R PN 3TX Remote Field
Controller works, its operating and connection elements, and its integration into the
PC Worx software.
This information will also guide you through the startup and operation of the redundant
control system and the RFC 460R PN 3TX Remote Field Controller.
The parameterization memory is not supplied as standard with the RFC 460R PN 3TX.
Only use CompactFlash cards from Phoenix Contact that are intended for use with the
RFC 460R PN 3TX. For the ordering data, please refer to Section “Accessories” on
page 136.
– 2 x Small form factor plug-in module (SFP module), a plug-in I/O module for fiber
optics that is used in Gigabit Ethernet. For transmission lengths up to 80 km.
The SFP module is not supplied as standard with the RFC 460R PN 3TX.
Only use SFP modules from Phoenix Contact that are intended for use with the
RFC 460R PN 3TX. For the ordering data, please refer to Section “Accessories” on
page 136.
– Assembled fiber optic cable, break-out cable, multi-mode fiberglass 50/125 μm, plug:
LC/LC, degree of protection: IP20, for installation in cable ducts or control cabinets
(e.g., FL MM PATCH 1,0 LC-LC, length: 1 m, Order No. 2989158)
– PC Worx automation software in the following version:
PC Worx Version 6.10 Service Pack 2 or later (redundancy)
Full licenses
Please note that the software described above is a demo version of the PC Worx software
with limited resources, which is sufficient for programming the examples described in this
user manual. If your application requires further resources, please order the full license for
the corresponding software from Phoenix Contact.
For the ordering data for hardware, software, and additional documentation, please refer
to Section “Ordering data” on page 136.
If errors that occur in machines and/or systems could cause personal injury or damage to
property, the manufacturers and operators (of these machines/systems) are responsible for
developing a suitable safety concept for your machine and/or system while adhering to all
applicable standards, directives, and laws.
In particular, the risk arising from the machine and/or system when using electronic
controllers, which are also responsible for safety in the machine and/or system, determines
whether additional measures are required in order to prevent and/or control errors that
occur.
If this is the case, for example, because safety functions with requirements from safety
standards are to be implemented, which exceed the scope of the application of the device
described in this user manual, then manufacturers and operators of the machine and/or
system must implement the additional required measures through the use of safety-related
controllers (e.g., RFC 470S PN 3TX).
The redundant control system from Phoenix Contact with the RFC 460R PN 3TX Remote
Field Controller enables you to provide maximum availability throughout your system – from
the I/O level to the control level. This is vital for uninterrupted processes in complex systems
and large plants. Using the redundant control system, you can ensure the continuous
operation of your automation.
Structure The RFC 460R PN 3TX Remote Field Controller is a high-performance controller that has
been extended to offer redundancy functionality. The redundant control system consists of
two synchronized RFC 460R PN 3TX controllers connected via fiber optics. The built-in
fiber optic interface is used for synchronization and adjustment between the connected
devices.
Depending on the distance between the Remote Field Controllers, three plug-in SFP
modules (small form factor plug-in modules) are available to connect the fiber optics. You
can therefore cover distances of 550 m, 30 km or up to 80 km.
Function You program just one Remote Field Controller as usual, while the second is started up
automatically. If one Remote Field Controller fails, the other takes over immediately
ensuring smooth operation.
Configuration/ In PC Worx, only one RFC 460R PN 3TX is visible in the project. Once the project has been
programming/ compiled and downloaded to the Remote Field Controllers, both connected devices are
visualization/ synchronized via fiber optics using the synchronization connection, whereby the
redundancy type/role downloaded project is transmitted to the connected Remote Field Controllers. In order to
ensure that this occurs, during initial startup redundancy type FIRST must be assigned to
one of the Remote Field Controllers and redundancy type SECOND to the other. The
redundancy type does not change during operation. The redundancy role of the Remote
Field Controller (PRIMARY/BACKUP) may change depending on the status of the
redundant control system. The redundancy role determines which of the two Remote Field
Controllers controls the process.
The OPC server required for visualization supports redundancy, i.e., it automatically detects
when a switch-over has taken place. Immediately after switch-over of the redundancy role,
the OPC server supplies the data from the Remote Field Controller that has taken over the
process to the visualization software.
Redundant control system Figure 2-2 shows an example of a redundant control system consisting of two
RFC 460R PN 3TX Remote Field Controllers connected via a synchronization connection.
RU
N/P
RO
G
MR ST
P
ES
ET
DIS
PL
AY
LN
K
LAN
1.1
AC
T
LN
K
LA
US 1.2N
B AC
T
RF
C
Or 460R
LN d.N
K o.2 PN
LA 70 3TX RU
N 07 N/P
2 84 RO
AC G
T
MR ST
SY P
ES
NC ET
DIS
PL
AY
+
-
LN
K
LAN
1.1
AC
T
LN
K
LA
US 1.2N
B AC
T
RF
C
Or 460R
LN d.N
K o.2 PN
LA 70 3TX
N 07
2 84
AC
T
SY
NC
+
-
Please note that the PROFINET network, which is at a lower level than the redundant
control system, should be designed according to the requirements of the application.
The network topologies listed below should be viewed as examples.
Above the redundant control system, a PC can be connected directly to the Ethernet
interfaces of the Remote Field Controllers via an Ethernet connection. This connection can
also be used for program creation and program download, as well as visualization via OPC
server.
The higher-level PC always accesses the Remote Field Controller that controls the process
(PRIMARY) via the PC Worx software.
A
PC Wo
rx
B1 RUN/PROG
STP
MRESET
DISPLAY
B2 RUN/PROG
MRESET
STP
DISPLAY
ETHERNET
LNK LNK
RFC 460R PN 3TX
ETHERNET ETHERNET LNK LNK
RFC 460R PN 3TX
LAN1.1 LAN1.2 LAN1.1 LAN1.2
Ord.No. 2700784 Ord.No. 2700784
ACT ACT ACT ACT
LNK LNK
24VDC 24VDC
+ +
SYNC - SYNC -
SYNC
1 3 5 7
C FL SWITCH SMSC 8GT
Ord. No. 2891123
MODE
1 3 5 7
LINK LINK
PROFINET
Address 1 2 3 4 5 6 7 8 Address 1 2 3 4 5 6 7 8
00.A0.45.06.04.02 00.A0.45.06.04.02
Mode Mode
X9 X10 X11 X12 X9 X10 X11 X12
US1 GND US2 GND R1 R2 MEM V.24 US1 GND US2 GND R1 R2 MEM V.24
1 3 5 7
1 3 5 7
ACT SPD FD 2 4 6 8
ACT SPD FD 2 4 6 8
LINK
LINK
MAC
Address
X9
00.A0.45.06.04.02
Mode
2 3 4 5 6 7 8
X12
V.24
PROFINET MAC
Address
X9
00.A0.45.06.04.02
Mode
2 3 4 5 6 7 8
X12
V.24
AUTOMATIONWORX
MRESET
STOP
UL FF
US
UM
Q1 Q2
Q3 Q4
I1 I2
I3 I4
I5 I6
I7 I8 PROFINET PROFINET UL
US BF
UM SF
1 2
3 4
1 2
3 4
5 7
6 8
RUN / PROG
X1
RESET RESET
PRG
LNK ACT LNK1 ACT1
X2.1 X1
LNK ACT
LNK2 ACT2
X2.2 X2
Figure 2-4 Redundant higher-level control system with RFC 460R PN 3TX and lower-
level network ring redundancy using MRP
Key:
D PROFINET device with control function; in the example: ILC 170 ETH 2TX
E PROFINET device without control function; in the example: IL PN BK DI8 DO4 2TX-
PAC
Alternatively, the PC for programming and visualization can also use infrastructure
components (in Figure 2-5: Smart Managed Compact Switch) to access the LAN2 Ethernet
interfaces of the Remote Field Controllers.
B1 RUN/PROG
STP
DISPLAY
A B2 RUN/PROG
STP
DISPLAY
MRESET MRESET
PC Wo
rx
LNK LNK
24VDC 24VDC
+ +
SYNC - SYNC -
SYNC
PROFINET
1 3 5 7
C FL SWITCH SMSC 8GT
Ord. No. 2891123
MODE
1 3 5 7
LINK LINK
Mode Mode
X9 X10 X11 X12 X9 X10 X11 X12
US1 GND US2 GND R1 R2 MEM V.24 US1 GND US2 GND R1 R2 MEM V.24
ETHERNET
C C MODE
PROFINET
MODE
1 3 5 7
1 3 5 7
ACT SPD FD 2 4 6 8
ACT SPD FD 2 4 6 8
LINK
LINK
UL FF UL
AUTOMATIONWORX PROFINET
US Q1 Q2 I1 I2 I5 I6 US BF 1 2 1 2 5 7
MRESET UM Q3 Q4 I3 I4 I7 I8 UM SF 3 4 3 4 6 8
STOP
RUN / PROG
X1
RESET RESET
PRG
LNK ACT LNK1 ACT1
X2.1 X1
LNK ACT
LNK2 ACT2
X2.2 X2
A
PC Wo
rx
B1 RUN/PROG
STP
MRESET
DISPLAY
B2 RUN/PROG
STP
MRESET
DISPLAY
ETHERNET
LNK LNK
RFC 460R PN 3TX
ETHERNET ETHERNET LNK LNK
RFC 460R PN 3TX
LAN1.1 LAN1.2 LAN1.1 LAN1.2
Ord.No. 2700784 Ord.No. 2700784
ACT ACT ACT ACT
LNK LNK
24VDC 24VDC
+ +
SYNC - SYNC -
SYNC
PROFINET C1 C2
PROFINET
C3 Cn C4
PROFINET
D En E1
ILC 170 ETH 2TX IL PN BK DI8 DO4 2TX-PAC IL PN BK DI8 DO4 2TX-PAC
Order-No.: 2916532 Order-No.: 2703994 Order-No.: 2703994
PWR O1 I1 I2 PWR O1 I1 I2
HW/FW: 00/220 HW/FW: 00/100 HW/FW: 00/100
MAC Addr.: xx.xx.xx.xx FR E RDY FAIL BSA PF MAC Addr.: xx.xx.xx.xx D E MAC Addr.: xx.xx.xx.xx D E
UL FF UL UL
AUTOMATIONWORX PROFINET PROFINET
US Q1 Q2 I1 I2 I5 I6 US BF 1 2 1 2 5 7 US BF 1 2 1 2 5 7
MRESET UM Q3 Q4 I3 I4 I7 I8 UM SF 3 4 3 4 6 8 UM SF 3 4 3 4 6 8
STOP
RUN / PROG
X1
RESET RESET RESET
PRG
LNK ACT LNK1 ACT1 LNK1 ACT1
X2.1 X1 X1
LNK ACT
LNK2 ACT2 LNK2 ACT2
X2.2 X2 X2
Key:
In this example for the extended ring redundancy protocol, below the two redundant
RFC 460R PN 3TX Remote Field Controllers there is a PROFINET ring, which consists of 1
to n FL SWITCH 300... managed switches. PROFINET devices with and without control
function are positioned directly below the managed switches. They are outside the ring.
In a ring with extended ring redundancy protocol, maximum switch-over times of up to
15 ms can be expected.
When setting update times for inputs and outputs and the number of faulty telegrams for
PROFINET devices, please observe the note about “Switch-over times/monitoring times”
on page 13.
Example
Reduction ratio inputs and outputs: 8 ms
Faulty telegrams until connection is aborted: 3
In the PROFINET ring, when the extended ring redundancy protocol (extended ring
redundancy) is used, a maximum of 134 PROFINET devices can be operated depending
on the application.
A
PC Wo
rx
B1 RUN/PROG
MRESET
STP
DISPLAY
B2 RUN/PROG
MRESET
STP
DISPLAY
ETHERNET
LNK LNK
RFC 460R PN 3TX
ETHERNET ETHERNET LNK LNK
RFC 460R PN 3TX
LAN1.1 LAN1.2 LAN1.1 LAN1.2
Ord.No. 2700784 Ord.No. 2700784
ACT ACT ACT ACT
LNK LNK
24VDC 24VDC
+ +
SYNC - SYNC -
SYNC
1 3 5 7
C2 FL SWITCH SMSC 8GT
Ord. No. 2891123
MODE
1 3 5 7
ACT SPD FD 2 4 6 8 ACT SPD FD 2 4 6 8
LINK LINK
PROFINET
MAC US1 US2 FAIL US1 US2 FAIL
MAC
Address 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
00.A0.45.06.04.02 Address 00.A0.45.06.04.02
Mode Mode
X9 X10 X11 X12 X9 X10 X11 X12
US1 GND US2 GND R1 R2 MEM V.24 US1 GND US2 GND R1 R2 MEM V.24
PROFINET
1 3 5 7
Cn FL SWITCH SMSC 8GT
Ord. No. 2891123
MODE
1 3 5 7
C4 FL SWITCH SMSC 8GT
Ord. No. 2891123
MODE
1 3 5 7
MAC US1 US2 FAIL MAC US1 US2 FAIL MAC US1 US2 FAIL
1 2 3 4 5 6 7 8 Address 1 2 3 4 5 6 7 8 Address 1 2 3 4 5 6 7 8
Address 00.A0.45.06.04.02 00.A0.45.06.04.02 00.A0.45.06.04.02
PROFINET PROFINET
UL FF UL UL
AUTOMATIONWORX PROFINET PROFINET
US Q1 Q2 I1 I2 I5 I6 US BF 1 2 1 2 5 7 US BF 1 2 1 2 5 7
MRESET UM Q3 Q4 I3 I4 I7 I8 UM SF 3 4 3 4 6 8 UM SF 3 4 3 4 6 8
STOP
RUN / PROG
X1
RESET RESET RESET
PRG
LNK ACT LNK1 ACT1 LNK1 ACT1
X2.1 X1 X1
LNK ACT
LNK2 ACT2 LNK2 ACT2
X2.2 X2 X2
Figure 2-7 PROFINET ring with RSTP – Rapid Spanning Tree Protocol with fast ring
detection
Key:
A PC for programming and visualization (PC Worx/OPC configurator)
B1 FIRST PROFINET controller;
the redundancy role (PRIMARY/BACKUP) may change depending on the
redundancy status
B2 SECOND PROFINET controller;
the redundancy role (PRIMARY/BACKUP) may change depending on the
redundancy status
C1...n Infrastructure components;
in the example: FL SWITCH SMCS... (nmax = 57)
D PROFINET device with control function;
in the example: ILC 170 ETH 2TX
E1...n PROFINET device without control function;
in the example: IL PN BK DI8 DO4 2TX-PAC
In this example for the Rapid Spanning Tree Protocol with fast ring detection, below the two
redundant RFC 460R PN 3TX Remote Field Controllers there is a PROFINET ring, which
consists of 1 to n FL SWITCH SMCS ... Smart Managed Compact Switches (SMCS).
PROFINET devices with and without control function are positioned directly below the
SMCS switches. They are outside the ring.
In a ring with Rapid Spanning Tree Protocol with fast ring detection, maximum switch-over
times of up to 500 ms can be expected.
When setting update times for inputs and outputs and the number of faulty telegrams for
PROFINET devices, please observe the note about “Switch-over times/monitoring times”
on page 13.
Example
Reduction ratio inputs and outputs: 16 ms
Faulty telegrams until connection is aborted: 33
In the PROFINET ring, when the Rapid Spanning Tree Protocol with fast ring detection
is used, a maximum of 57 PROFINET devices (with Large Tree Support enabled) can be
operated depending on the application.
A
PC Wo
rx
B1 RUN/PROG
MRESET
STP
DISPLAY
B2 RUN/PROG
MRESET
STP
DISPLAY
ETHERNET
LNK LNK
RFC 460R PN 3TX
ETHERNET ETHERNET LNK LNK
RFC 460R PN 3TX
LAN1.1 LAN1.2 LAN1.1 LAN1.2
Ord.No. 2700784 Ord.No. 2700784
ACT ACT ACT ACT
LNK LNK
24VDC 24VDC
+ +
SYNC - SYNC -
SYNC
1 3 5 7
C2 FL SWITCH SMSC 8GT
Ord. No. 2891123
MODE
1 3 5 7
ACT SPD FD 2 4 6 8
PROFINET
ACT SPD FD 2 4 6 8
LINK LINK
PROFINET
UL FF UL UL
AUTOMATIONWORX PROFINET PROFINET
US Q1 Q2 I1 I2 I5 I6 US BF 1 2 1 2 5 7 US BF 1 2 1 2 5 7
MRESET UM Q3 Q4 I3 I4 I7 I8 UM SF 3 4 3 4 6 8 UM SF 3 4 3 4 6 8
STOP
RUN / PROG
X1
RESET RESET RESET
PRG
LNK ACT LNK1 ACT1 LNK1 ACT1
X2.1 X1 X1
LNK ACT
LNK2 ACT2 LNK2 ACT2
X2.2 X2 X2
Key:
A PC for programming and visualization (PC Worx/OPC configurator)
B1 FIRST PROFINET controller;
the redundancy role (PRIMARY/BACKUP) may change depending on the
redundancy status
B2 SECOND PROFINET controller;
the redundancy role (PRIMARY/BACKUP) may change depending on the
redundancy status
C1,2 Infrastructure components;
in the example: FL SWITCH SMCS... with adjustable master/client function
D PROFINET device with control function;
in the example: ILC 170 ETH 2TX
E1...n PROFINET device without control function (nmax = 50-3);
in the example: IL PN BK DI8 DO4 2TX-PAC
F MRP client
In this example for the Media Redundancy Protocol, below the two redundant
RFC 460R PN 3TX Remote Field Controllers there is a PROFINET ring, which consists of 2
FL SWITCH SMCS ... Smart Managed Compact Switches (SMCS), one PROFINET device
with control function, and 1 to n PROFINET devices without control function. Switch C1 is
operated with set master function and switch C2 is operated with set client function in the
ring.
In a ring with Media Redundancy Protocol, maximum switch-over times of up to 200 ms can
be expected.
When setting update times for inputs and outputs and the number of faulty telegrams for
PROFINET devices, please observe the note about “Switch-over times/monitoring times”
on page 13.
Example
Reduction ratio inputs and outputs: 8 ms
Faulty telegrams until connection is aborted: 26
In the PROFINET ring, when the Media Redundancy Protocol is used, a maximum of
50 PROFINET devices can be operated depending on the application.
For information on the redundancy states of the redundant control system, please refer to
Section “Status information” on page 37.
The BACKUP Remote Field Controller is synchronized by the Remote Field Controller that
controls the process (PRIMARY) after the project has been fully compiled in PC Worx and
downloaded to the PRIMARY Remote Field Controller. During synchronization, the boot
project is transferred from the PRIMARY to the BACKUP Remote Field Controller and
processed accordingly.
In this case, the boot project must always be downloaded consistently to the actual project
on the PRIMARY Remote Field Controller.
The Basic Sync state is not achieved during the synchronization phase on Remote Field
Controller startup, even though the connection between the LAN2 interfaces of the Remote
Field Controllers is working perfectly, if the fiber optic synchronization connection is
interrupted during this period. This system behavior is due to the fact that configuration data
may only be transmitted via the fiber optic synchronization connection.
If the synchronization connection (SYNC) is not connected, the Remote Field Controller can
also be operated in single mode. The redundancy type for the Remote Field Controller
should be set to NOT DEFINED. During operation, the Remote Field Controller assumes
the NOT DEFINED redundancy role.
If the fiber optic synchronization connection is interrupted during runtime, the redundant
control system is synchronized via the LAN2 interface as long as an active connection exists
between the Remote Field Controllers via this interface. In this case, the redundancy roles
of the Remote Field Controllers are not switched over. If synchronization is also impossible
via LAN2, the redundancy role of the BACKUP Remote Field Controller is switched over to
PRIMARY. The previous PRIMARY Remote Field Controller remains set to PRIMARY
because without the synchronization connection it is not possible to determine whether the
previous BACKUP Remote Field Controller has been set to PRIMARY. The PRIMARY
Remote Field Controller with the FIRST redundancy type takes over the function of the
PROFINET controller that controls the process.
If the PRIMARY Remote Field Controller is set to the STOP state by PC Worx (CONTROL:
STOP), this does not switch over the redundancy role. In this case, the BACKUP Remote
Field Controller is also set to the STOP state (CONTROL: STOP). Setting the mode selector
switch to the STOP position has the same effect (see Section “Mode selector switch” on
page 51).
When the parameterization memory of the BACKUP Remote Field Controller is removed
during runtime, the redundant control system switches to the FollowUp Sync state. When
the parameterization memory is inserted, the system remains in this state. Only after a
successful restart of the BACKUP Remote Field Controller can the redundant control
system switch back to HotStandBy state (SYNC/HSBY) in the event of error-free operation.
When the parameterization memory of the PRIMARY Remote Field Controller is removed
during runtime, the redundancy roles of both Remote Field Controllers are switched over.
The BACKUP Remote Field Controller becomes the new PRIMARY and takes over process
control. When the parameterization memory is removed, the redundant control system
switches to the FollowUp Sync state. When the parameterization memory is inserted, the
system remains in this state. Only after a successful restart of the current BACKUP Remote
Field Controller can the redundant control system switch back to HotStandBy state
(SYNC/HSBY) in the event of error-free operation. In the event of error-free operation, both
Remote Field Controllers keep the redundancy roles that they were switched to when the
parameterization memory was removed.
The redundant control system permits the use of one user task. Either the default task or a
cyclic task can be selected in PC Worx. If a cyclic task is used, please note that the cycle
time must be selected so that synchronization can be performed in addition to the task
runtime. If the default task is used, this is not necessary. This means that processing may
be faster when using the default task, however processing is equidistant when using a cyclic
task.
Users cannot access the BACKUP Remote Field Controller because PC Worx and the OPC
server only communicate with the PRIMARY Remote Field Controller. Therefore the state
of the BACKUP Remote Field Controller can be mapped using the corresponding system
variables, which are mirrored to the PRIMARY Remote Field Controller and can be read in
PC Worx (see “REMOTE_...” variables in Section “Redundancy-specific system variables
of the Remote Field Controller” on page 128). These variables are only updated by the
BACKUP Remote Field Controller.
The Remote Field Controller supports the “Download Changes” function. This function can
be used to send project modifications to the Remote Field Controllers and activate them
there without having to stop the active PLC. Once PC Worx has sent the entire project to the
PRIMARY Remote Field Controller, it then transmits the project to the BACKUP Remote
Field Controller. Users are not aware of this action as the redundant control system remains
available throughout.
The redundancy role that determines which of the two Remote Field Controllers controls the
process (PRIMARY or BACKUP) may change depending on the status of the redundant
control system. The conditions listed below can lead to the switch-over of the redundancy
role. They are displayed in the Diag+ software.
A redundancy system can be operated with only one Remote Field Controller. The
redundancy type for the Remote Field Controller should be set to NOT DEFINED.
Figure 2-9 Redundancy type for the Remote Field Controller: NOT DEFINED
This enables the operation of applications with only one Remote Field Controller, but
without redundancy properties. In this case, the Remote Field Controller assumes the NOT
DEFINED redundancy role.
Use this setting, for example, during initial startup of a project or for debugging.
If the fiber optic synchronization connection is interrupted during error-free operation, the
system continues running without interruption. Synchronization is then carried out via the
LAN2 PROFINET controller interface. The redundancy status does not change, and the
redundancy roles of the Remote Field Controllers remain the same.
The interruption is indicated by the PL and LL LEDs in the redundancy status area:
Meaning of the LEDs (see also Section “Diagnostic indicators” on page 39):
PL = Physical Link (physical link to the SYNC interface)
LL = Logical Link (connection monitoring active at the SYNC interface)
If the system continues running without errors while there is an interrupted fiber optic
synchronization connection, the system is synchronized again using this connection once
the interruption to the fiber optic synchronization connection has been removed. The green
PL and LL LEDs indicate that the connection has been established successfully.
IEC 61131 control For all Remote Field Controllers configuration and programming is carried out consistently
performance (Ethernet) under IEC 61131 using PC Worx automation software. PC Worx can be operated via the
network (Ethernet). The powerful processor can be programmed in all five IEC 61131
programming languages and ensures quick control task processing.
SYNC interface The SYNC interface supports the connection of the Remote Field Controller to a second
Remote Field Controller via fiber optics. This connection is used to synchronize the two
devices. Various SFP modules, which can be inserted in the corresponding device slot, are
available to cover the connection distances between the Remote Field Controllers of the
redundant control system, which vary according to the application. For the ordering data for
these modules, please refer to Section “Accessories” on page 136.
Integrated Ethernet The integrated Ethernet connections provide Ethernet connectivity. Throughout the
connection/PROFINET network, the Remote Field Controller can be accessed via Ethernet and TCP/IP or UDP/IP.
In addition, the Remote Field Controller can be integrated into a PROFINET system using
the Ethernet connections. Via interface LAN2, the Remote Field Controller operates in a
PROFINET system as a PROFINET controller.
At present, the device supports the Phoenix Redundancy Layer (PRL). The connection of
redundant devices from other manufacturers is not possible at present.
Time synchronization is also possible via the Ethernet network.
When using the AX OPC server provided in the AUTOMATIONWORX Software Suite,
Remote Field Controller data is available in the Ethernet network in a standardized format
and can be used for the different visualization packages.
USB interfaces The USB interfaces are used to update the device firmware (see Section “Updating the
device firmware” on page 103).
Internal battery The Remote Field Controller has a maintenance-free battery for buffering the internal
realtime clock. Under some circumstances the battery may be flat. In this case, connect the
Remote Field Controller to the 24 V DC supply voltage for approximately 48 hours to
recharge the battery.
Parameterization memory In order to operate, the RFC 460R PN 3TX requires a (plug-in) parameterization memory in
(CF card) the form of a CompactFlash card (see Figure 3-1 on page 29: item 3).
The parameterization memory is not supplied as standard with the RFC 460R PN 3TX.
Only use CompactFlash cards from Phoenix Contact that are intended for use with the
RFC 460R PN 3TX. For the ordering data, please refer to Section “Accessories” on
page 136.
The parameterization memory can be used to save programs and configurations, which
belong to your project, e.g., the visualization project and the PROFINET device name. The
IP addresses assigned to the Remote Field Controller and the assigned redundancy type
(FIRST/SECOND) are also stored on the parameterization memory. The data is retained in
the parameterization memory, even if the CompactFlash card is removed from the Remote
Field Controller.
Indication elements Diagnostic information can be displayed directly on the RFC 460R PN 3TX via the
(LCD/LEDs) diagnostic indicators (LCD and LEDs) without additional software.
The following status information is displayed:
– Control program (CONTROL)
– Redundancy (REDUNDANCY)
– PROFINET (PROFINET CONTROL)
– Ethernet connection (LEDs)
2
RU
N/P
RO
G
MRE STP
3
SE
T
DIS
PL
AY
4
LN
K
LAN
1.1
AC
5
T
LN
K
LA
USB 1.2N
AC
T
RF
C
Ord 460
LN .N R P
K o.2 N
LA 70 3TX
N 07
2 84
AC
T
6
SYN
C
7 10
+
-
8 11
9
Figure 3-1 Structure of the RFC 460R PN 3TX Remote Field Controller including fan
module
Key:
1 Mode selector switch
2 LCD
3 Slot for the parameterization memory/card holder (CF card)
4 Retaining clip
5 Ethernet interfaces (RJ45 sockets)
6 USB interfaces (only for firmware updates)
7 SYNC interface/slot for SFP modules
8 Label with MAC address, license number, and HW/FW/COP FW version
9 Supply voltage connection (24 V DC)
10 Operating keys
11 Fan module (optional)
Scope of supply
Please note that the SFP modules, the CF card, and the fan module are not supplied as
standard with the RFC 460R PN 3TX.
For the ordering data, please refer to Section “Accessories” on page 136.
The Remote Field Controller can be operated at ambient temperatures of 0°C to 45°C
without a fan module.
NOTE:
If the Remote Field Controller is operated at ambient temperatures higher than 45°C, the
fan module is required. The maximum permissible temperature for operation with a fan is
55°C (see also Section “Technical data” on page 133).
We recommend using the fan module at even lower ambient temperatures so as to
increase the service life of the Remote Field Controller.
The fan module is not supplied as standard with the Remote Field Controller; it is available
as an accessory.
The fan module is secured to the bottom of the Remote Field Controller using four screws.
Tighten the screws so that they do not loosen accidentally, e.g., due to vibrations (see
Section “Mounting the fan” on page 60).
The electrical connection between the Remote Field Controller and the fan module is
established automatically when the fan module is fitted. The fan module contains two fans.
The vents for the fan module are located on the bottom of the module. When installing the
Remote Field Controller make sure that the vents can be freely accessed. The Remote
Field Controller can overheat if the vents are covered. To ensure good ventilation, leave
a gap of 8 to 10 cm above and below the Remote Field Controller.
NOTE:
The fan module must not be replaced during operation. The Remote Field Controller must
be switched off before the fan module can be replaced. To replace the fan module,
remove the Remote Field Controller from the DIN rail. Refer to the information in Section
“Replacing the fan module” on page 105 and Section “Replacing the RFC 460R PN 3TX”
on page 65.
The LNK and ACT LEDs indicate the status of the Ethernet interface. The LEDs have the
following meaning:
LNK The LNK LED (Link, green) lights up when the Remote Field Controller is able
to contact another network device.
ACT The ACT LED (Activity, yellow) flashes when the Ethernet interface is
transmitting or receiving data.
RU
N/P
RO
G
MR ST
P
ES
ET
DIS
PLA
Y
LN
K
LAN
1.1
AC
T
LN
K
LA
US 1.2N
B AC
T
RF
C
Or 460R
LN d.N
K o.2 PN
LA 70 3TX
N 07
2 84
AC
T
SY
NC
+
-
The operating keys on the front of the Remote Field Controller enable menu-driven
operation. Both operating keys can be pressed (A) and tilted (B). When tilting the key
(B: up/down), you can switch between menu items or increase/decrease values or apply
settings. By pressing the key, you can select/deselect a menu item (A, bottom key) or switch
to the next value to be set (A, top key).
DISPLAY
A B
The following menu-specific functions can be activated by pressing the buttons. The
functions are shown on the right-hand side of the LCD by icons.
Icon Description
– Move to next menu item/selection up.
– Scroll up list of values.
– Select highlighted menu item/selection.
– Execute selection (e.g., execute switch-over).
– Move to next menu item down.
– Scroll down list of values.
– Edit value of highlighted menu item.
The LCD contains important diagnostic and status information for the Remote Field
Controller and its interfaces. Depending on the selected display, more detailed information
can be selected for individual items. For example, the IP addresses of the Remote Field
Controller can be requested via the display and operating keys and set if necessary.
Possible indicators in the LCD are described below.
1x + 2x + 3x +
B C D
8291A010
Key:
A Main menu
B CONTROL/CONTROL DETAILS submenu: control details
C REDUNDANCY submenu: redundancy
D PROFINET CONTROL/PN-C DETAILS submenu: PROFINET controller
E SYSTEM MENU: system menu
1x + 3x + 5x +
2x + 4x + 6x +
C1 C2 C3 C4 C5 C6
8291A011
Key:
C REDUNDANCY submenu
C1 REDUNDANCY submenu – Actions
C2 REDUNDANCY submenu – Local Information
C3 REDUNDANCY submenu – Remote Information
C4 REDUNDANCY submenu – Redundancy Status
C5 REDUNDANCY submenu – Settings
C6 REDUNDANCY submenu – Diagnostics
For additional information on the system menu, please refer to Section “REDUNDANCY
submenu – meaning of menu items” on page 46.
1x + 3x + 5x +
2x + 4x + 6x +
E1 E2 E3 E4 E5 E6
8291A012
Key:
E System menu (SYSTEM MENU)
E1 SYSTEM MENU – IP CFG LAN1 submenu: configure LAN1
E2 SYSTEM MENU – IP CFG LAN2 submenu: configure LAN2
E3 SYSTEM MENU – SYSTEM INFO submenu: system information
E4 SYSTEM MENU – OPTIONS submenu: screensaver (release time), display
backlight (on/off), display language (German/English)
E5 SYSTEM MENU – FW-UPDATE submenu: start firmware update via USB
interfaces
Only select this item if you have inserted the necessary USB stick for
the firmware update into the USB interface. There is no cancel for this
operation.
For additional information on the system menu, please refer to Section “System menu –
meaning of menu items” on page 41.
The following figure shows the general meaning of the indicators in the LCD main menu.
Control/PLC
Diagnostic
indicators: Redundancy status
LEDs
PROFINET controller
The diagnostic indicators (LEDs) and status information for the controller inside the device
and the redundancy status are displayed within the individual areas in Figure 3-8. In
addition, the diagnostic indicators (LEDs) and status information for the Remote Field
Controller as a PROFINET controller are displayed.
The background color in the individual areas varies depending on the state.
The diagnostic indicators (LEDs) at the bottom of the display appear in submenus. The
example shows the local information of the Remote Field Controller that controls the
process in the REDUNDANCY submenu in Figure 3-9.
Diagnostic indicators:
LEDs
The status information for the individual areas is displayed both in the main menu (all areas)
and in the corresponding submenu (the selected area only). The background color of the
areas in the diagnostic display varies depending on which states are represented in the
display.
The status information in the individual areas has the following meaning:
Controller (CONTROL)
Table 3-2 Status information: CONTROL
Display Meaning
INIT Controller initialization.
RUN The controller is in the RUN state.
STOP The controller is in the STOP state.
FAIL An error has occurred.
HALT The controller is in debug mode.
The controller is ready. There is no project on the parameterization memory
RDY
(CF card).
Redundancy status
(REDUNDANCY)
Table 3-3 Status information: REDUNDANCY
Display Meaning
No Sync
NSYN
No synchronization
Basic Sync
– The fiber optic synchronization connection is working without errors.
– The IP addresses of the LAN2 interfaces for each Remote Field
Controller are assigned.
BSYN – The redundancy type of each Remote Field Controller is set.
– The redundancy role of each Remote Field Controller is set.
– The realtime clocks (RTC) of both Remote Field Controllers are
synchronized.
– The “Remote Information” in the REDUNDANCY submenu is known.
FollowUp Sync
– The PC Worx project has been downloaded to the PRIMARY Remote
FSYN Field Controller.
– The boot project is synchronized between the PRIMARY and BACKUP
Remote Field Controllers.
Display Meaning
Sync – PRIMARY in Sync state/BACKUP in HSBY state
– The controller is in the RUN state (CONTROL/PLC).
– The parameterization memory is inserted.
– All configured application relations have been The PRIMARY
established. and BACKUP
– Data synchronization is active. Remote Field
SYNC System variables are not synchronized. A selection of Controllers run
system variables are exchanged between the two Remote simultaneously.
Field Controllers in redundancy mode. This ensures that Process data is
each of the two Remote Field Controllers knows the status mirrored in
of the other at all times in error-free operation. This is realtime so that
important, for example, because only the Remote Field both Remote
Controller that controls the process communicates with Field Controllers
PC Worx or the OPC server. of the redundant
HotStandBy – BACKUP in HSBY state control system
are processing
– The controller is in the RUN state (CONTROL/PLC). identical data.
HSBY – The parameterization memory is inserted.
– All configured application relationships have been
established.
– Data synchronization is active.
PROFINET controller
(PROFINET CONTROL)
Table 3-4 Status information: PROFINET controller
Display Meaning
The PROFINET controller is waiting for the Ethernet interfaces to be
INIT configured
(IP addresses to be set).
RDY The Ethernet interfaces are configured. The PROFINET controller is waiting
(Ready) for a PROFINET configuration.
A desired configuration has been loaded to the PROFINET controller. In this
state the PROFINET controller attempts to establish a connection cyclically to
all devices in the desired configuration. In this way, it attempts to find each
device with the corresponding “PROFINET device name” in the current
ACT subnetwork.
(Active)
For inaccessible devices, the PROFINET controller cyclically attempts to
establish a connection.
A connection cannot be established, e.g., if the corresponding device is
ready, but a correct PROFINET device name has not yet been assigned to it.
An error occurred when configuring the PROFINET controller. E.g., a faulty
CNF
GSDML file was used.
CFG Configuring the PROFINET network parameterized in the PC Worx project.
ERR Display of PROFINET errors.
The diagnostic indicators of all areas are displayed in each submenu using virtual LEDs.
They have the following meaning:
Control (PLC)
Table 3-5 Diagnostic indicators: PLC
PROFINET controller
(PN-C)
Table 3-7 Diagnostic indicators: PN-C (PROFINET controller)
The elements of the system menu are described below in more detail.
• To call the system menu, press the “System menu” operating key at the bottom of the
main menu.
The following submenu appears:
• To view the system information, use the , , and keys in the system menu
The following information is displayed (you can also view the version information for the
standard part of the Remote Field Controller here):
• To edit the screensaver switch-on time, select “Edit release time” using the , ,
and keys.
• Use the , , and keys to set the switch-on time for the screensaver, e.g.,
13 minutes.
• If you do not want to apply your settings, press the key instead of the key.
If you have entered an invalid value while entering the above settings, e.g., 39 minutes, the
maximum switch-on time of 30 minutes is set. The following message appears in the
display:
Use this menu item, for example, to activate IP settings in the controller that you made in
the “IP CFG LAN...” menu.
Changes that you have made in the system menu are stored on the parameterization
If you have modified the IP settings, these changes only take effect when the Remote
Field Controller is restarted.
The elements of the CONTROL DETAILS submenu are described below in more detail.
The menu indicates whether the parameterization memory is inserted, the device
temperature, and the charging state of the battery inside the device.
The elements of the REDUNDANCY submenu are described below in more detail.
• To call the menu, press the key twice and the key.
ACTIONS Actions for the redundancy role of the Remote Field Controller
In the ACTIONS submenu, you can switch over the redundancy role of the Remote Field
Controller or reset to a default value. The default value depends on the redundancy type that
has been assigned to the Remote Field Controller. The assignment always refers only to the
Remote Field Controller on which the action is executed. In the HotStandBy redundancy
state, the redundancy roles of the Remote Field Controllers are synchronized accordingly.
By default, the Remote Field Controller is assigned the FIRST redundancy type and the
PRIMARY redundancy role. The Remote Field Controller with the SECOND redundancy
type is assigned the BACKUP redundancy role by default.
NOTE:
Please note before executing this action that resetting the redundancy roles to the default
value may interrupt redundancy mode.
• Select the desired menu item using the or keys and execute the action using
the key.
SETTINGS Information on the redundancy type of the local Remote Field Controller
The SETTINGS submenu indicates the redundancy type that is currently set for the Remote
Field Controller. As an option, this menu can be used to modify the redundancy type using
the operating keys.
The change to the redundancy type only takes effect after a Remote Field Controller restart.
The elements of the submenu for the PROFINET controller details are described below in
more detail.
• To call the menu, press the key three times and the key.
The mode selector switch is used to define the operating state of the standard application
program.
The RUN/PROG and STOP positions have a toggle button function and the MRESET
position a pushbutton function. After releasing the button in the MRESET position, it returns
to STOP.
Operating Explanation
mode
RUN/PROG The application program in the main memory is in the RUN state.
The PC Worx software can be used for program and configuration
modifications.
The monitoring and online functions can be used.
STOP The application program is in the STOP state.
MRESET Retain data and the application program in the main memory are
deleted.
Press the mode selector switch as follows to delete the retain data and
application program:
• Set the switch to the MRESET position for three seconds.
• Release the switch for less than three seconds.
• Set the switch to the MRESET position for three seconds.
RUN/PROG
STP
MRESET
3.8 Interfaces
A B1 B2
LAN1.1
LAN1.2
LAN2
SYNC
The SYNC interface is available at the Remote Field Controller for the synchronization of
both Remote Field Controllers of the redundant control system (B1 in Figure 3-30). The
operation of the SYNC interface requires the use of standardized SFP modules, which
support different transmission lengths (B2 in Figure 3-30).
See also Section “Connecting the synchronization connection to the SYNC interface (fiber
optics)” on page 62.
Three standardized Ethernet interfaces are available at the Remote Field Controller.
Interfaces LAN1.1/LAN1.2 are switched inside the device. They are used to connect an
Ethernet network. A PROFINET network can be connected using the LAN2 interface at the
Remote Field Controller. The Remote Field Controller operates as a PROFINET controller
via this interface. In addition, if the fiber optic synchronization connection is interrupted
during runtime, the redundant control system is synchronized via the LAN2 interface as long
as an active connection exists between the Remote Field Controllers via this interface.
A programming PC can be operated at each Ethernet interface of the Remote Field
Controller.
A MAC address is assigned to the LAN1.1/LAN1.2 interfaces (LAN1). An additional MAC
address is assigned to interface LAN2.
The Ethernet interfaces are RJ45 sockets and have the following function:
Interface Description
LAN1 10/100Base-T(X)
(LAN1.1/LAN1.2)
LAN2 10/100Base-T(X) and function as a PROFINET controller interface
The LAN1.1/LAN2 Ethernet interfaces of the Remote Field Controller support the
autocrossing function (auto crossover) and the auto negotiation function. In order to use
the auto negotiation function, the LAN1.1 Ethernet interface requires a communication
partner with activated auto negotiation function.
Please note:
– The IP addresses of the LAN1/LAN2 interfaces must be in different subnetworks.
– The LAN2 interface must be assigned an IP address because the PROFINET
controller function of the Remote Field Controller is available at this interface.
– The LAN1 interface must not necessarily be assigned an IP address if, for example,
communication between a PC with PC Worx and the Remote Field Controller is also
implemented via the LAN2 interface.
For additional information on the interfaces, in particular the assignment of IP addresses,
please refer to Section “Specifying the IP addresses of the Remote Field Controller
defined as FIRST” on page 78.
For the interface assignment, please refer to “Ethernet interfaces LAN1.1/LAN1.2 and
LAN2 (10/100Base-T)” on page 139.
See Section “Connecting the supply voltage” on page 64 and Section “Connecting the
supply voltage” on page 141.
Please note that a separate power supply unit should be provided for each Remote Field
Controller in the redundant control system.
If a corresponding redundancy module is used, the power supply units can be designed
to create a redundant system.
A corresponding signal from the alarm contact inside the module in the redundant control
system can be evaluated to monitor the redundant power supply units. Please refer to the
information in the module-specific user documentation.
For the ordering data, please refer to “Accessories” on page 136.
The maximum current required for the Remote Field Controller is 2.0 A.
A power supply unit with an output current of IOUT ≥ 2.5 A is therefore recommended for
operating the Remote Field Controller.
A power supply without a fall-back characteristic curve must be used for correct
operation of the Remote Field Controller (see Figure 3-32 on page 56). When the Remote
Field Controller is switched on, an increased inrush current is temporarily triggered. The
Remote Field Controller behaves like a capacitive load when it is
switched on.
Some electronically controlled power supply units have a fall-back characteristic curve (see
Figure 3-31 on page 56). They are not suitable for operation with capacitive loads.
The following power supply unit (without fall-back characteristic curve) is recommended for
operating the Remote Field Controller:
– Primary-switched power supply unit with SFB technology for 6 times the nominal current
QUINT-PS/1AC/24DC/3.5; 24 V DC, 3.5 A (Order No. 2866747)
Other power supply units can be used as an alternative. For examples of suitable
Phoenix Contact power supply units, please refer to “Accessories” on page 136.
Overload range
UOUT with fall-back
[V] characteristic curve
24
I OUT
IN [A]
1.1 x I N 2.4 x I N
6219B070
Figure 3-31 Overload range with fall-back characteristic curve
Overload range
UOUT without fall-back
[ V] characteristic curve
24
I OUT
[ A]
IN 1.5 x I N
6219B071
Figure 3-32 Overload range without fall-back characteristic curve
4.1 General
Only qualified personnel should pack and unpack the RFC 460R PN 3TX while observing
the following ESD regulations.
Shielding
The shielding ground of the connected twisted pair cables is electrically connected to the
RJ45 socket of the RFC 460R PN 3TX. When connecting network segments, avoid
ground loops, potential transfers, and voltage equalization currents via the braided shield.
NOTE:
Please observe the following notes when using a shield connection clamp.
– Ensure the cable shields for Ethernet and INTERBUS are correctly secured in the plug-
in connectors and when routing a cable through a control cabinet.
– Only use shielded data cables. As much of the shield as possible must be connected
to ground on both sides.
– Immediately following entry in the control cabinet or housing, connect as much of the
cable shield as possible to a shield/protective conductor bar and secure the shield with
a cable clamp. Lead the shield to the module without interruption; connect it here but
not to ground.
– The connection between the shield/protective conductor bar and the control
cabinet/housing must have no impedance.
Only use metal or metal-plated plug housing for shielded data cables.
To avoid contact resistance only use clean, corrosion-free DIN rails. Before mounting the
devices, an end clamp should be mounted on the left-hand side next to the
RFC 460R PN 3TX to stop the devices from slipping on the DIN rail. The end clamp
should only be mounted on the right-hand side once the RFC 460R PN 3TX has been
mounted.
The following end clamps can be used:
– E/NS 35N (Order No. 0800886, fixed using a screw)
– CLIPFIX 35 (Order No. 3022218, snapped on without tools)
– E/UK (Order No. 1201442, fixed using screws)
Fan module
If you wish to operate the Remote Field Controller with the fan module, you must mount
the fan module first, before mounting the Remote Field Controller on the DIN rail. Please
refer to the instructions in Section “Mounting the fan” on page 60.
A
X
3T
PN
0R
46
R FC
• Place the Remote Field Controller onto the DIN rail from above (A in Figure 4-1).
NOTE:
When installing the Remote Field Controller make sure that the vents can be freely
accessed, because otherwise the Remote Field Controller can overheat. To ensure good
ventilation, leave a gap of 8 to 10 cm above and below the Remote Field Controller.
• Tilt the Remote Field Controller downwards until the spring-loaded holder snaps into
place with a click (B).
• Finally, make sure that the Remote Field Controller is securely mounted on the DIN rail.
• Mount the fan on the bottom of the Remote Field Controller using the four screws, as
shown in Figure 4-2.
A
B
B
Figure 4-2 Mounting the fan
To remove the device, follow the instructions in Section “Replacing the RFC 460R PN 3TX”
on page 65 up to step 6. If the fan is mounted on the Remote Field Controller, please also
observe step 7.
NOTE: Please note that the parameterization memory may not be inserted or
removed during operation.
Always disconnect the power supply to the RFC 460R PN 3TX before inserting or
removing the parameterization memory.
Inserting the • Insert the parameterization memory into the slot provided as shown in Figure 4-3, with
parameterization memory the socket strip to the front.
When pressed lightly, the parameterization memory slots in and the ejector moves
outwards (A).
Retaining clip Depending on the hardware version, a retaining clip can protect the ejector against
accidental actuation. To remove the parameterization memory, move the retaining clip
downwards (B) to allow the ejector to be actuated. To protect the ejector against accidental
actuation, you can move the retaining clip over the ejector after inserting the
parameterization memory.
A B C
Project
board
Controller
Plant
CF 64M ATA-PC
Order No. 2737054
64MB
CE
Replacing the Remove the old parameterization memory according to the method described above and
parameterization memory insert the new parameterization memory.
Before you can insert the fiber optic connection that is used to connect the two
RFC 460R PN 3TX Remote Field Controllers for synchronization purposes, a suitable SFP
module must be inserted in the corresponding slot (SYNC interface) of each Remote Field
Controller. Which module is suitable for your application depends, for example, on the
distance to be covered between the two Remote Field Controllers. For a list of available
modules, please refer to Section “Accessories” on page 136.
Mounting the SFP module Mount the appropriate SFP module for your application in the corresponding slot (SYNC
interface) of the Remote Field Controller.
Ensure correct mechanical alignment of the SFP module before pushing it into the slot.
Make sure that the SFP module is correctly snapped in to protect it against accidental
removal.
Inserting the fiber optic Establish the fiber optic connection for synchronization between the two RFC 460R PN 3TX
connection devices.
Ensure correct mechanical alignment of the fiber optic plug before inserting it into the SFP
module.
• Applying light pressure, push the fiber optic plug for the synchronization connection into
the SFP module until it engages with a click.
Make sure that the fiber optic plug is correctly snapped in to protect it against accidental
removal.
Figure 4-5 Inserting the fiber optic plug into the SFP module
• Connect the Ethernet cable to the Ethernet interface (RJ45 sockets: LAN1.1/1.2 or
LAN2) of the RFC 460R PN 3TX.
This connects the device to a higher-level/lower-level Ethernet network. Use an Ethernet
cable according to CAT5 of IEEE 802.3.
Observe the information on the Ethernet interfaces of the device in Section “Ethernet
interfaces LAN1.1/LAN1.2 and LAN2 (10/100Base-T)” on page 139.
For the ordering data for the Ethernet cable, please refer to Section “Accessories” on
page 136.
RU
N/P
RO
G
MR ST
P
ES
ET
DIS
PLA
Y
LN
K
LAN
1.1
AC
T
LN
K
LA
US 1.2N
B AC
T
RF
C
Or 460R
LN d.N
K o.2 PN
LA 70 3TX
N 07
2 84
AC
T
SY
NC
+
-
Figure 4-6 Cabling between an Ethernet network and the RFC 460R PN 3TX
PROFINET
The PROFINET controller function of the Remote Field Controller is available at interface
LAN2. To use as a PROFINET controller, please connect a PROFINET network to
interface LAN2.
The Remote Field Controller is supplied from an external power supply (24.0 V DC). The
permissible voltage ranges from 19.2 V DC to 30.0 V DC (ripple included).
• Insert the assembled COMBICON plug-in connector into the socket provided as shown
in Figure 4-7.
24
V
DC
24 V DC
GND
FE
Please note that the Remote Field Controller requires some time to start up following
connection of the supply voltage.
Only qualified personnel should pack and unpack the device while observing ESD
regulation at the beginning of Section “General” on page 57.
Only replace the device with a device with the same hardware/firmware version or a
compatible device approved by Phoenix Contact. Information on compatible devices can
be found on the Internet at phoenixcontact.net/products.
24
V
DC
A
B
RUN
/PR
OG
MRE STP
SET
DIS
PLA
Y
LNK
LAN
1.1
ACT
LNK
LAN
USB 1.2
ACT
RF
C
Ord 460
LNK .No R PN
LAN
.27 3TX
007
2 84
ACT
SYN
C
+
-
B A
Figure 4-10 Removing the fiber optic plug
B A
6. Remove the old Remote Field Controller from the DIN rail.
X
N 3T
RP
60
C4
RF
B
A
Figure 4-12 Removing the Remote Field Controller from the DIN rail
If the fan module is mounted on the Remote Field Controller, proceed as follows:
7. Unscrew the four screws used to fix the fan module to the bottom of the Remote Field
Controller. Make sure that the fan module does not fall after unscrewing the screws.
B A
Figure 4-13 Removing the fan
If you wish to operate the new device with the fan module, proceed as follows:
9. Mount the fan on the bottom of the Remote Field Controller using the four screws, as
shown in.
A
B
B
Figure 4-14 Mounting the fan
10. Mount the new device according to Section “Mounting the RFC 460R PN 3TX” on
page 59. Ensure that the device is locked on the DIN rail.
11. Snap the Remote Field Controller onto the DIN rail and check that it is securely locked
in place (see Figure 4-15).
A
X
3T
PN
0R
46
C
RF
B
Figure 4-15 Snapping the Remote Field Controller onto the DIN rail
12. Remove the parameterization memory from the old device and insert it in the new
device. See Section “Inserting/removing the parameterization memory” on page 60.
RU
N/P
RO
G
MR ST
P
ES
ET
DIS
PLA
Y
LN
K
LAN
1.1
AC
T
LN
K
LA
US 1.2N
B AC
T
RF
C
Or 460R
LN d.N
K o.2 PN
LA 70 3TX
N 07
2 84
AC
T
SY
NC
+
-
14. Mount the SFP module that was removed from the old device in step 5. or another SFP
module suitable for the application in the corresponding slot (SYNC interface) of the
Remote Field Controller.
Ensure correct mechanical alignment of the SFP module before pushing it into the slot.
Push the SFP module into the slot. Turn the release latch towards the module.
Make sure that the SFP module is correctly snapped in to protect it against accidental
removal.
15. Restore the fiber optic connection for synchronization between the two
RFC 460R PN 3TX devices.
Ensure correct mechanical alignment of the fiber optic plug before inserting it into the SFP
module.
Applying light pressure, push the fiber optic plug for the synchronization connection into
the SFP module until it engages with a click.
Make sure that the fiber optic plug is correctly snapped in to protect it against accidental
removal.
Figure 4-18 Inserting the fiber optic plug into the SFP module
24
V
DC
24 V DC
GND
FE
5 Startup
5.1 Startup
This section describes the steps that must be taken before and during startup of a
redundant control system that consists of two RFC 460R PN 3TX Remote Field Controllers
connected together via a synchronization connection, plus connected PROFINET devices.
Please note that after power up, the RFC 460R PN 3TX starts up immediately if a
parameterization memory with a valid project is inserted.
To start up, proceed as described in Table 5-1 on page 71.
The following table describes all the steps from unpacking the two RFC 460R PN 3TX
Remote Field Controllers required for the redundant control system and mounting/
installation to startup.
Table 5-1 Steps for starting up the RFC 460R PN 3TX/redundant control system
Please note that the RFC 460R PN 3TX Remote Field Controllers require
approximately 2 minutes to start up. This is due to the comprehensive
selftests the devices must perform. The status is indicated in the LCD.
Define the redundancy type for both Section “Specifying the redundancy type of
Remote Field Controllers (FIRST or the RFC 460R PN 3TX Remote Field
SECOND). Controllers” on page 73.
Table 5-1 Steps for starting up the RFC 460R PN 3TX/redundant control system
To carry out the following steps, please refer to the user manuals for PC Worx
and the AXC 1050 PN STARTERKIT:
– UM QS EN AXC 1050 PN STARTERKIT
– UM QS EN PC WORX
Both user manuals provide a quick start guide to programming and
parameterizing a PROFINET configuration within the PC Worx software.
– UM QS EN AXC 1050 PN
STARTERKIT
Carry out all the steps in order to integrate
– UM QS EN PC WORX
the device as a PROFINET controller in a
PC Worx project. – Section “Integration of the
RFC 460R PN 3TX in PC Worx” on
page 85
Check the PROFINET controller settings
and adapt the settings, if necessary.
Section “Reading the PROFINET network”
Create your bus configuration in PC Worx.
on page 92.
Assign a PROFINET device name for the Section “Naming PROFINET devices” on
connected devices (device naming). page 94.
Create the variables for the devices for
Section “Redundant variables” on page 111.
process data exchange.
– UM QS EN AXC 1050 PN
Link the created variables to process data STARTERKIT
according to your application.
– UM QS EN PC WORX
Compile the project in the PC Worx
software. Section “Compiling and sending a project to
the Remote Field Controller” on page 96.
Send the compiled project to the controller.
Section “Performing a cold restart for the
Start the controller.
Remote Field Controller” on page 97.
Once you have correctly mounted and installed both RFC 460R PN 3TX Remote Field
Controllers, define the redundancy type (FIRST or SECOND) for both Remote Field
Controllers. The redundancy type only needs to be defined once during startup.
• Use the or key to set the redundancy type. One of the controllers should be
assigned redundancy type FIRST and the other redundancy type SECOND (in the ex-
• If you do not want to apply your settings, press the key instead of the key.
Defining the SECOND To set the redundancy type of the second Remote Field Controller, please proceed as
redundancy type described above. Using the same procedure as above, set the redundancy type as
SECOND.
Perform restart for Now restart this Remote Field Controller. Select “RESTART” in the system menu of the
SECOND LCD.
• Initiate the restart by selecting the “Yes” option using the and keys (see
Figure 5-10).
Synchronizing Before the Remote Field Controllers of the redundant control system can be synchronized,
redundancy types in order to apply the above settings first make the IP address settings of the Remote Field
Controller defined as FIRST above. To do this, proceed as described in Section “Specifying
the IP addresses of the Remote Field Controller defined as FIRST” on page 78.
This section describes how to specify the IP address settings for Ethernet interfaces LAN1
and LAN2 of the Remote Field Controller defined as FIRST. The procedure for assigning the
IP settings is essentially the same for the LAN1 and LAN2 interfaces. The example below
shows the general procedure using the LAN2 interface.
The initial assignment of the IP settings can be carried out using the diagnostic display.
Please note:
– The IP addresses of the LAN1/LAN2 interfaces must be in different subnetworks.
– The LAN2 interface must be assigned an IP address because the PROFINET
controller function of the Remote Field Controller is available at this interface.
– The LAN1 interface must not necessarily be assigned an IP address if, for example,
communication between a PC with PC Worx and the Remote Field Controller is also
implemented via the LAN2 interface.
If the Remote Field Controller already has IP settings that are valid in your network, the IP
settings can be modified via the network using PC Worx (see Section “IP addresses of the
Remote Field Controller (FIRST)” on page 89).
The IP settings of the Remote Field Controller can be checked at any time, even during
operation.
• In the system menu, use the , , and keys to select the “IP CFG LAN2”
menu item.
• In the “IP CFG LAN2” submenu, use the , , and keys to select the “Edit
• Set the IP address shown in Figure 5-14 using the , , and keys. Use the
key to change position in the IP address. Use the and keys to increase
If you have entered an invalid value while entering the above settings, this is indicated by
the following message:
• Once you have set the IP address, use the , , and keys to switch to the
“IP CFG LAN2” submenu and the “Edit Subnetmask (LAN2)” menu item in order to
check and, if necessary, set the subnet mask for interface LAN2.
• The required subnet mask in this example is “255.255.0.0”. If this is not present, use the
The following message is displayed if you have changed the subnet mask (“255.255.0.0” in
the example):
Now make the IP address settings for the LAN1 interface according to the above
description:
IP address: 192.168.1.10
Subnet mask: 255.255.255.0
Following successful entry of the desired settings, the display looks like this:
The IP settings you have made are stored on the parameterization memory. The changes
take effect when the Remote Field Controller is restarted.
To apply the IP address (FIRST) and redundancy settings (FIRST and SECOND) previously
stored on the parameterization memories, i.e., to synchronize the redundant control system,
please proceed as described in this section.
The SECOND redundancy type must have been assigned to one of the Remote Field
Controllers of the redundant control system by a restart (see Section “Specifying the
redundancy type of the RFC 460R PN 3TX Remote Field Controllers” on page 73).
First reset the Remote Field Controller defined as FIRST by means of a RESTART or switch
its supply voltage off and then on again.
During the boot phase that follows, the Remote Field Controller defined as FIRST
synchronizes itself with the Remote Field Controller defined as SECOND by performing a
controlled reset of the controller via the fiber optic synchronization connection. As a result
the redundancy states of both Remote Field Controllers are adjusted.
Perform restart for FIRST Perform a restart for the Remote Field Controller defined as FIRST. Select “RESTART” in
the system menu.
• Initiate the restart by selecting the “Yes” option using the and keys (see
Figure 5-20).
Once the Remote Field Controller defined as FIRST has been restarted, it automatically
initiates the restart of the Remote Field Controller defined as SECOND during
synchronization.
Once both Remote Field Controllers have been restarted successfully, they are both
assigned the redundancy type that was previously set. In addition, the IP address settings
of the Remote Field Controller defined as SECOND are assigned during startup.
Both controllers assume their redundancy role. The Remote Field Controller defined as
FIRST assumes the PRIMARY redundancy role and the Remote Field Controller defined as
SECOND assumes the BACKUP redundancy role.
Both Remote Field Controllers are in the “No Sync” state (NSYN). Following successful
synchronization, both Remote Field Controllers change to the “Basic Sync” state (BSYN,
see Figure 5-21), i.e., there is a communication connection between the PRIMARY (FIRST)
and BACKUP (SECOND) Remote Field Controllers.
Figure 5-21 Both Remote Field Controllers are in the “Basic Sync” state
For the chronological sequence of the steps carried out, please refer to this section.
When carrying out the following steps, please refer to the quick start guide for PC Worx
as well as the online help for the software and the user manual for the AXC 1050 PN
STARTERKIT:
– UM QS EN AXC 1050 PN STARTERKIT
– UM QS EN PC WORX
These user manuals provide a quick start guide to programming and parameterizing a
PROFINET configuration within the PC Worx software.
Selecting and inserting There are two options available in the PC Worx software for integrating the
devices in the bus RFC 460R PN 3TX as a PROFINET controller together with the PROFINET devices
configuration connected to it.
PROFINET
Either automatically read the PROFINET devices in the network, then check the settings of
the device(s), and adapt the settings to your application, if necessary, or manually insert the
device(s) as a PROFINET device in the bus configuration and then adapt the settings of the
device(s).
Creating a new project in Select the “New Project...” command from the “File” menu to create a new project using a
PC Worx template.
The tree structure and the selection of the controller are now prepared.
• In the “New Project” dialog box, select the “RFC 460R PN 3TX” controller.
Saving the project • Once the new project has been created, select the “Save Project As / Zip Project As...”
command in the “File” menu.
• Enter a name for your project in the “Save/Zip project as” dialog box (here:
UM_RFC_460R) and save the project.
First and last IP address, During project creation, PC Worx automatically assigns an IP address area for a local
subnet mask network (range from 192.168.0.2 to 192.168.0.254). If you would like to use another
address area (e.g., a global network), adapt the start and end address on the project node
(here: UM_RFC_460R) to your application.
If the IP parameters are modified in the project settings, the IP addresses of the controller
may have to be modified manually.
If you are using the addresses of a local network in your project, also assign a
corresponding address for the local network (e.g., 192.168.0.225) to the PC on which
PC Worx is installed. Otherwise the devices in the local network cannot be accessed.
For information on the IP addresses to be used within your system, please contact your
system administrator.
If the start address of the new address area to be entered is higher than the previous end
address, please modify the end address first.
If you manually assign IP parameters that are outside the defined area, they will be
accepted and displayed with a warning.
The following settings are used for the IP address area in the example project:
In order to address the FIRST Remote Field Controller in PC Worx, the IP address settings
that were entered via the LCD during startup (see Section “Specifying the IP addresses of
the Remote Field Controller defined as FIRST” on page 78) must also be applied in
PC Worx.
Select the Remote Field Controller node. The necessary settings can be made in the
“Device Details” window (see Figure 6-6 on page 90).
Please note:
– The IP addresses of the LAN1/LAN2 interfaces must be in different subnetworks.
– The LAN2 interface must be assigned an IP address because the PROFINET
controller function of the Remote Field Controller is available at this interface.
– The LAN1 interface must not necessarily be assigned an IP address if, for example,
communication between a PC with PC Worx and the Remote Field Controller is also
implemented via the LAN2 interface.
In this example, the following settings apply:
FIRST-LAN1: IP address: 192.168.1.10
Subnet mask: 255.255.255.0
FIRST-LAN2: IP address: 172.16.1.2
Subnet mask: 255.255.0.0
The Ethernet connections are available for communication (see also Section “Ethernet
interfaces” on page 52).
The IP addresses of the Ethernet interfaces of the Remote Field Controller must be set for
communication via Ethernet. The procedure is described in Section “Specifying the IP
addresses of the Remote Field Controller defined as FIRST” on page 78.
To set the communication path between the programming PC with PC Worx and the
Remote Field Controller, proceed as described below.
The “FIRST-LAN2” interface is selected in Figure 6-7 (see highlighted item). The
corresponding IP address and subnet mask are displayed.
• To change the set interface, click on “FIRST-LAN1” for example.
• Click “Apply”.
The message “Apply successful!” is displayed in the status window. After a short update
time, “FIRST-LAN1” appears highlighted as the communication path.
• To test the set communication path, click on “Test”.
To this end, there must be a connection between the FIRST-LAN1 interface and the PC
on which the PC Worx software is running.
A successful test is indicated by a green background in the status window. The
communication path has been successfully set.
NOTE: The Remote Field Controller can be accessed via a network using the Ethernet
interface and the TCP/IP protocol. Please note that with all networked devices/
computers, there is a risk that third parties may access the Remote Field Controller or the
PC Worx PC and make changes, either intentionally or unintentionally. Prevent
unauthorized access to the Remote Field Controller and your PC.
Please note that in order to read the PROFINET network, the Ethernet network card via
which the PROFINET devices in the network can be accessed must be selected in the
“Extras, PROFINET Configuration ...” menu in PC Worx.
To read the PROFINET network connected to the LAN2 interface of the PRIMARY Remote
Field Controller in the example, and to name the read PROFINET devices (if necessary),
proceed as described in this section.
• In the context menu of the PROFINET node, select the “Read PROFINET...” command
(see Figure 6-8).
In the “Read PROFINET” dialog box that opens, select the corresponding devices for your
application one after the other. Alternatively, you can select and read all the necessary
devices in the “Read PROFINET” dialog box.
The following describes how to read the devices one after the other.
• Click “Insert”.
• In the “Select PROFINET device description” dialog box that opens, select the
corresponding device description. Make sure the version is correct.
Since the PROFINET bus terminal to be inserted has not yet been given a PROFINET
device name, the following dialog box opens (see Figure 6-11).
• Enter the desired PROFINET device name and confirm your entries with “OK”.
• Repeat this step until you have inserted all of the PROFINET devices in your network in
the project. In the example, you still need to insert the second PROFINET bus terminal.
• Click on the “Close” button to close the “Read PROFINET” dialog box.
When reading the PROFINET network, PC Worx automatically assigns an IP address for
the read devices. The previously assigned PROFINET device name is also displayed. The
IP addresses displayed in Figure 6-12 for both PROFINET bus terminals have been
adapted according to the application.
If necessary, adapt the device names and IP addresses for your application.
Please note that the IP addresses of the devices connected to the Remote Field
Controller only exist in the project at this point. If you switch the supply voltage off and on
again at this point, the devices read in the “Read PROFINET” dialog box (see Figure 6-9
on page 93) as described above will appear again without IP addresses. It is only once
the project has been compiled in PC Worx and downloaded to the Remote Field
Controller (see Section “Compiling and sending a project to the Remote Field Controller”
on page 96), that the Remote Field Controller assigns the settings saved in the
project on every power up.
The previous steps have prepared the project so that the example structure can be started
up. Compile the project and then send the project to the PRIMARY Remote Field Controller.
• To compile the project, select the “Rebuild Project” command from the “Build” menu.
Following successful compilation without any errors (display in the message window of
PC Worx), the project can be sent to the PRIMARY Remote Field Controller.
• Open the “Project control” dialog box. To do this, click the corresponding button.
• Click on “Download” to send the project to the PRIMARY Remote Field Controller.
Once the redundant control system and the connected PROFINET network have been
started up successfully, the Remote Field Controllers change to the “HotStandBy”
redundancy status. The PRIMARY Remote Field Controller that controls the process
indicates the “SYNC” state in the display, the BACKUP Remote Field Controller indicates
the “HSBY” state (see Figure 6-16).
If an installation error prevents the system from starting up, a corresponding error message
appears in the LCD and in PC Worx.
Information on PROFINET The following information on the PROFINET controller and the connected PROFINET
devices can now be displayed in the “PROFINET IO controller” (PN-C DETAILS) submenu.
A B
Key:
Diagnosed errors are displayed in the RFC 460R PN 3TX display as an error code with a
red background (see Figure 7-1) and as an error text (see Figure 7-2).
• If necessary, use the , , and keys to view the entire error text.
In the Diag+ software, the “Redundancy information” view displays the diagnosed errors
(see Figure 7-3).
The firmware of the device (integrated software on the RFC 460R PN 3TX) can be updated
via the USB interfaces. Such firmware updates are exclusively used for adding new
functions that are implemented within the scope of continuous product improvement for the
RFC 460R PN 3TX firmware. No firmware update is required for normal system operation.
WARNING:
Take appropriate measures to ensure that the system/machine does not present any
danger during the firmware update phase.
Please note any other information available regarding firmware updates. If available, this
will be included with the firmware update files.
After updating the firmware, perform a voltage reset so that the entire device is
reinitialized.
Please note that only combinations of firmware and device versions that have been
approved by Phoenix Contact may be created.
For information on compatible and approved firmware versions for your devices and
instructions on how to perform updates, please visit phoenixcontact.net/products.
How to proceed
To update the firmware, always use the following USB memory stick:
VS-04-MS-IP20 (Order No. 1402490) USB memory stick, IP20, USB 2.0
Always update the firmware for both Remote Field Controllers of the redundant control
system one after the other. The order does not matter.
If you start the firmware update on the PRIMARY Remote Field Controller first, the
redundancy roles of both Remote Field Controllers are switched. If the switch-over is
completed without errors, the previous BACKUP becomes the PRIMARY Remote Field
Controller and takes control of the process, i.e., the application continues running.
Please note that the firmware update process starts as soon as the following step is
executed.
Only select this item if you have inserted the necessary USB stick for the firmware update
into the USB interface. There is no cancel for this operation.
A B
The firmware update is complete after the Remote Field Controller has successfully
performed an automatic restart.
8.2 Repair
Repair work may not be carried out on the RFC 460R PN 3TX. Send faulty devices with
detailed error information (see Section “Errors, diagnostic messages, and removal” on
page 99) to Phoenix Contact.
NOTE:
The fan module must not be replaced during operation. The Remote Field Controller must
be switched off before the fan module can be replaced. To replace the fan module,
remove the Remote Field Controller from the DIN rail.
The procedure for installing and removing the Remote Field Controller is described in
“Replacing the RFC 460R PN 3TX” on page 65.
A
A B
B A B
Figure 8-2 Replacing the fan module
In the “Extended Settings” tab in the “Device Details” window, the time and date can be set
for the internal system clock of the Remote Field Controller (see Figure 9-3 on page 109:
“Real-time Clock Settings” area.
The system clock can only be set using PC Worx for the PRIMARY Remote Field
Controller that controls the process. Make sure that the system clock setting from
PC Worx is only sent to this Remote Field Controller.
Once the system clock setting has been made in the “Real-time Clock Settings” area, click
on the relevant “Send” button. Then select the required interface (see Figure 9-1).
On synchronization of the redundant control system, the setting is transmitted from the
PRIMARY to the BACKUP Remote Field Controller.
The setting must be sent to the PRIMARY Remote Field Controller because a setting sent
to the BACKUP Remote Field Controller by the PRIMARY Remote Field Controller that
controls the process would be overwritten immediately on synchronization.
To set the realtime clock, refer to the quick start guide for the PC Worx version used.
The redundant control system permits the use of one user task. Either the default task or a
cyclic task can be selected in PC Worx (see Figure 9-2). If a cyclic task is used, please note
that the cycle time must be selected so that synchronization can be performed in addition to
the task runtime. If the default task is used, this is not necessary. This means that
processing may be faster when using the default task, however processing is equidistant
when using a cyclic task.
When using a cyclic task, please ensure that both inputs and outputs are linked and created
as one task. If this is not the case, PC Worx will automatically generate I/O groups, which
are implicitly assigned to the default task. During compilation, this will result in the error
message that more than one task is used.
If necessary, adapt the task properties for your application. The task properties can be set
in the IEC programming workspace under the “Hardware Structure” for the “STD_TSK:
DEFAULT” standard task.
For additional information on task properties, please refer to the quick start guide or the
online help for PC Worx.
The “Device Details” window in PC Worx can be used to view the IP settings and the
PROFINET device names of the FIRST and SECOND Remote Field Controllers. The data
for the FIRST Remote Field Controller can be modified if required by the application, but the
data for the SECOND Remote Field Controller can only be viewed.
A B
Read The “Read” button can be used to read in the network settings for the selected interface, the
PROFINET device name, and the settings for the internal realtime clock in PC Worx.
Reset Control System The “Reset Control System” button can be used to reset the Remote Field Controller after
entering the required IP address (communication path), for example, to activate the network
settings that were previously sent to the device.
NOTE:
Do not modify the IP address settings using the advanced settings in the “Device Details”
window of PC Worx if the redundant control system is in the HotStandBy operating state.
The SECOND Remote Field Controller (BACKUP) becomes the PRIMARY Remote Field
Controller once the IP address settings of the FIRST Remote Field Controller (previously
PRIMARY) have been changed and the FIRST Remote Field Controller performs a restart
when the “Reset Control System” button is pressed. Since the SECOND Remote Field
Controller now controls the process, it will immediately overwrite the previous IP address
settings on subsequent synchronization.
Open FTP Folder on Use the “Open FTP Folder on Device” button to access the parameterization memory of the
Device Remote Field Controller via FTP (File Transfer Protocol).
New variables that are inserted in the “Global Variables” (see Figure 9-4) or “MainV” (see
Figure 9-5 on page 112) worksheets are assigned the “Redundant Variable” marking by
default. For variables created in the “Main” worksheet using the “Variable Properties” dialog
box, the default marking is not applied. If necessary, make this setting in the “Global
Variables” or “MainV” worksheet yourself.
The redundancy roles for the Remote Field Controllers of the redundant control system can
be switched over via the LCD, using Diag+ or using the CPU_Set_Value firmware service
(02CBhex).
For information on switch-over via the LCD, please refer to Section “REDUNDANCY
submenu – meaning of menu items” on page 46.
In Diag+ the redundancy roles are switched over using the “Swap redundancy role” button
(see Figure 9-6).
Information on switching over the redundancy role using the firmware service is given
below.
Please ensure that the redundancy role is only switched over via firmware service for the
PRIMARY Remote Field Controller that controls the process in the application program. The
redundant control system synchronizes the redundancy role of the BACKUP Remote Field
Controller accordingly.
Use the CPU_Set_Value firmware service (02CBhex) for switch-over. It can be called using
the CPU_CONTROL function block in your application program.
In order to prevent the BACKUP Remote Field Controller from also switching redundancy
role, assign the execution of the firmware service only to the Remote Field Controller with
the PRIMARY redundancy role. To do this, send a request to the RDNCY_IS_PRIMARY
system variable in your application program.
For test purposes, this service can be executed in the CPU service editor in PC Worx. For
your application, program the service accordingly in your application program.
For information on the PC Worx CPU service editor and programming in PC Worx, please
refer to the quick start guide and the online help for the version of PC Worx used.
CPU_Set_Value_Request
15 .............................. 8 7 .............................. 0
Key
CPU_Set_Value_Confirmation
15 ...................................................................... 0
Key
The RFC 460R PN 3TX Remote Field Controller supports the “Download Changes”
function. This function can be used to send project modifications to the Remote Field
Controllers and activate them there without having to stop the active PLC.
For more detailed information on this function, please refer to the online help for PC Worx.
NOTE:
If realtime violations are permitted, first ensure that your PLC application is running within
safe limits. Please note that each realtime violation may result in unexpected
consequences in the automation system, as under certain circumstances user tasks are
not processed for a short time. Therefore, check the level of risk before disabling this
option.
To delete files or store user-specific files on the internal parameterization memory, proceed
as follows:
The FTP function must be activated in Internet Explorer. See Section “Internet Explorer
FTP function” on page 118.
The file structure, which is stored on the parameterization memory, is displayed in the
Internet Explorer window.
Data may only be copied or deleted in the parameterization memory. Do not edit any files
as Internet Explorer does not store modified data.
For the current state to be displayed, update the display after every action by means of
the “View, Refresh” command.
• Activate this setting in Internet Explorer under “Tools, Internet Options, Advanced”.
Figure 9-11 Internet Options: Enable folder view for FTP sites
To protect the Remote Field Controller against unauthorized access, it may be necessary
to deactivate the FTP server. The CPU_Set_Value_Request service with Var ID 0172hex is
used for this. This service activates or deactivates the FTP server for the runtime of the
firmware. The set FTP server state is stored retentively and mapped to the
ETH_SRV_FTP_ACTIVE system variable. This setting is restored the next time the Remote
Field Controller is rebooted.
Value range for the CPU_Set_Value_Request service:
Var ID 0172hex
Value 0000hex Deactivate FTP server
0001hex Activate FTP server
To protect the Remote Field Controller against unauthorized access, it may be necessary
to deactivate the HTTP server. The CPU_Set_Value_Request service with Var ID 0173hex
is used for this. This service activates or deactivates the HTTP server for the runtime of the
firmware. The set HTTP server state is stored retentively and mapped to the
ETH_SRV_HTTP_ACTIVE system variable. This setting is restored the next time the
Remote Field Controller is restarted.
Value range for the CPU_Set_Value_Request service:
Var ID 0173hex
Value 0000hex Deactivate HTTP server
0001hex Activate HTTP server
The substitute value behavior for the input data of the controller must be specified in your
PC Worx project. By default, the input data of the controller is set to zero if the connection
to a PROFINET device is interrupted.
Set the substitute value behavior for each PROFINET device individually in PC Worx (see
Figure 9-13).
If the connection to a PROFINET device is interrupted, the “Set to zero” option means that
the corresponding input data of the controller is set to zero. The “Keep values” option means
that if the connection to a PROFINET device is interrupted, the input values that were valid
immediately before the interruption remain as the input data in the application program.
When the connection to the PROFINET device is restored, the substitute values remain
valid as input data until the PROFINET device has been started up completely. Once the
connection has been established again, the latest input data is used.
The function blocks are used to access files from within the application program. Some of
the blocks support multiple instantiation. This means that it is possible to work with a number
of different files within the same project. The blocks perform the standard functions that are
required for typical file access operations.
The FILE_NOTIFY block is available in addition to the blocks for typical file access
operations. This block can be used to detect files that have been modified in a directory
containing user files. These modifications may include:
– Deletion of one or more files
– Writing one or more new files
– Modification of one or more existing files
Both modifications made to this directory via FTP (remote) and modifications made locally
via function blocks or firmware services can be detected.
The function blocks for handling files in the parameterization memory are described in the
PC Worx online help.
The function blocks are used to establish Ethernet communication between two
communication partners.
The IP communication blocks listed below enable IEC 61131-5-compliant communication
between controllers via Ethernet or communication between controllers and Ethernet
devices via TCP/IP or UDP/IP.
Implement all time and connection monitoring in the application program.
The function blocks are valid for:
Order designation Blocks From From Ethernet connections
hardware firmware to other
version version communication
partners
(maximum)
IEC 61131-5
RFC 460R PN 3TX TCP/IP 00 5.00 32
UDP/IP
10 System variables
There is a separate group of system variables for the IEC 61131 runtime system.
The system variables listed below show the states of the diagnostic status register on the
control processor (CPU) of the Remote Field Controller.
The system variable below shows status information regarding the control processor of the
Remote Field Controller.
PROFINET provides extremely detailed diagnostic information from each device down to
the channel.
Diagnostic states are important for system operation. If error messages occur, the process
has to be stopped in case of doubt. To this end, PROFINET controllers from
Phoenix Contact provide the following status information for the PROFINET network.
The table below describes the PROFINET system variables of the integrated PROFINET
controller function.
10.5 Ethernet
Table 10-6 System variables of the FTP, HTTP, and SNTP server
General data
Dimensions without fan (width x height x depth) 124 mm x 185 mm x 190 mm
Dimensions with fan (width x height x depth) 124 mm x 210 mm x 190 mm
Weight without fan 2 kg, approximately
Weight with fan 2.2 kg, approximately
Power supply
Connection Via COMBICON plug-in connector
US 24 V DC
Permissible range 19.2 V DC to 30.0 V DC
Ripple 3.6 VPP
Power consumption 24 W (typical, without fan module)
Fuse protection 4 A, slow-blow, required externally
External power supply Only use power supplies without fall-back characteristic curve. The power
supply must be suitable for operation with capacitive loads. Ensure the power
supply unit and fuse are compatible. The power supply unit must be able to
temporarily provide the tripping current.
PROFINET
Type Modular PROFINET controller
Conformance class B
Performance class RT
Vendor ID 00B0hex/176dec
Device ID 003Dhex/61dec
Supported functions Topology detection, automatic device replacement, parameterizable alarm
and startup behavior
Network interfaces
Type 3 x Ethernet; 10Base-T and 100Base-TX
Transmission speed 10 Mbps (10Base-T), 100 Mbps (100Base-TX),
half duplex, full duplex, auto negotiation
This speed cannot be set manually. It is set automatically by means of auto negotiation.
Redundancy
Amount of data that can be synchronized ≤ 62 kB
Fan module
Number of fans 2
Bearings Ball bearings
Speed monitoring Yes
Service life 50,000 h at an ambient temperature of 25°C
NOTE:
If the Remote Field Controller is operated at ambient temperatures higher than 45°C, the fan module which can be mounted on the bottom is
required.
We recommend using the fan module at 35°C and above so as to increase the service life of the Remote Field Controller.
The fan module is not supplied as standard with the Remote Field Controller; it is available as an accessory.
Ambient conditions
Degree of protection IP20 (EN 60529:1991)
To ensure correct operation, the Remote Field Controller must be installed in housing or a control cabinet with a minimum of IP54 protection.
Pollution degree 2, when installed in housing or a control cabinet with IP54 protection or higher
Air and creepage distances According to IEC 60439-1
Class of protection III, IEC 61140, EN 61140, VDE 0140-1
Permissible temperature (operation, without fan) 0°C ... +45°C
Permissible temperature (operation, with fan) 0°C ... +55°C
Permissible temperature (storage/transport) -25°C ... +75°C
Permissible humidity (operation) 10% to 95%, no condensation
Ambient conditions
Permissible humidity (storage/transport) 10% to 95%, no condensation
Permissible air pressure (operation) 80 kPa to 108 kPa (up to 2000 m above sea level)
Permissible air pressure (storage/transport) 66 kPa to 108 kPa (up to 3500 m above sea level)
Mechanical requirements
Shock test according to IEC 60068-2-27 (Criterion 1) 25g
Operation/storage/transport
Vibration test according to IEC 60068-2-6 (Criterion 1) 1g; 2g additional fixing of the CF card required
Operation/storage/transport
Approvals
For the latest approvals, please visit phoenixcontact.net/products.
11.2.1 Products
11.2.2 Accessories
11.2.3 Software
11.2.4 Documentation
4
Figure A-1 Interfaces of the RFC 460R PN 3TX
Only one twisted pair cable with an impedance of 100 Ω may be connected to one of the two
Ethernet interfaces. Depending on the Ethernet network used, the data transmission rate is
10 Mbps or 100 Mbps. The Ethernet ports of the RFC 460R PN 3TX can detect a pair of
incorrectly connected receive cables (RD+/RD-) and correct them using the auto polarity
correction function.
The following diagram shows the contact assignment of an Ethernet port (RJ45 socket).
RJ45 Pin 1
Pin 2
Pin 3
Pin 4
Pin 5
Pin 6
Pin 7
Pin 8
A2 USB interfaces
The USB interfaces are used to update the device firmware (see Section “Updating the
device firmware” on page 103).
1
2
3
4
8291A008
Figure A-3 Pin assignment of the USB interfaces
A3 SYNC interface
See also Section “SYNC interface” on page 52 and Section “Connecting the
synchronization connection to the SYNC interface (fiber optics)” on page 62.
The Remote Field Controller is supplied from an external power supply (24.0 V DC). The
permissible voltage ranges from 19.2 V DC to 30.0 V DC (ripple included).
RUN/PROG DISPLAY
STP
MRESET
24 V DC
LNK
LAN1.1
LNK
LAN1.2
RFC 460R PN 3TX
Ord.No. 2700784
GND
ACT ACT
USB
LNK
LAN2
FE
ACT
24VDC
+
SYNC -
8291A002
B1 List of figures
Section 2
Figure 2-1: Redundant control system for distances up to 80 km ..........................11
Figure 2-2: Redundant control system ..................................................................12
Figure 2-3: Device Details: switch-over times/monitoring times ............................13
Figure 2-4: Redundant higher-level control system with RFC 460R PN 3TX
and lower-level network ring redundancy using MRP .........................14
Figure 2-5: Programming and visualization using infrastructure components
at LAN2 ...............................................................................................15
Figure 2-6: PROFINET network/PROFINET ring with extended ring redundancy .16
Figure 2-7: PROFINET ring with RSTP – Rapid Spanning Tree Protocol
with fast ring detection ........................................................................18
Figure 2-8: MRP – Media Redundancy Protocol ...................................................20
Figure 2-9: Redundancy type for the Remote Field Controller: NOT DEFINED ....25
Figure 2-10: Fiber optic synchronization connection interrupted .............................26
Section 3
Figure 3-1: Structure of the RFC 460R PN 3TX Remote Field Controller
including fan module ...........................................................................29
Figure 3-2: Remote Field Controller with fan module ............................................30
Figure 3-3: LNK and ACT LEDs ............................................................................31
Figure 3-4: Remote Field Controller keypad ..........................................................31
Figure 3-5: Structure of the main menu .................................................................33
Figure 3-6: Structure of the REDUNDANCY submenu ..........................................34
Figure 3-7: Structure of the system menu .............................................................35
Figure 3-8: LCD: indicators in the main menu .......................................................36
Figure 3-9: LCD: indicators in the submenu ..........................................................36
Figure 3-10: Diagnostic indicators in the submenus (LEDs) ....................................39
Figure 3-11: System menu ......................................................................................41
Figure 3-12: System menu – system information ....................................................42
Figure 3-13: System menu – OPTIONS ..................................................................42
Figure 3-14: System menu – screensaver – time setting .........................................43
Figure 3-15: System menu – screensaver switch-on time set .................................43
Figure 3-16: System menu – no changes ................................................................43
Section 4
Figure 4-1: Mounting the RFC 460R PN 3TX ........................................................59
Figure 4-2: Mounting the fan .................................................................................60
Figure 4-3: A: inserting the parameterization memory
B: moving the retaining clip
C: removing the parameterization memory .........................................61
Figure 4-4: Inserting the SFP module ....................................................................62
Figure 4-5: Inserting the fiber optic plug into the SFP module ...............................63
Figure 4-6: Cabling between an Ethernet network and the RFC 460R PN 3TX .....63
Figure 4-7: Connecting the supply voltage ............................................................64
Figure 4-8: Removing the supply cable .................................................................65
Figure 4-9: Removing the Ethernet cable(s) ..........................................................66
Figure 4-10: Removing the fiber optic plug ..............................................................66
Figure 4-11: Removing the SFP module .................................................................66
Figure 4-12: Removing the Remote Field Controller from the DIN rail .....................67
Figure 4-13: Removing the fan ................................................................................67
Figure 4-14: Mounting the fan .................................................................................68
Figure 4-15: Snapping the Remote Field Controller onto the DIN rail ......................68
Figure 4-16: Establishing the Ethernet connection ..................................................69
Figure 4-17: Inserting the SFP module ....................................................................69
Figure 4-18: Inserting the fiber optic plug into the SFP module ...............................70
Section 5
Figure 5-1: Remote Field Controller not synchronized (NSYN: No Sync) .............73
Figure 5-2: REDUNDANCY submenu ...................................................................73
Figure 5-3: REDUNDANCY submenu – settings ...................................................74
Figure 5-4: Redundancy type not defined .............................................................74
Figure 5-5: Redundancy type FIRST set ...............................................................75
Figure 5-6: Redundancy type changed – FIRST ...................................................75
Figure 5-7: No changes made ...............................................................................75
Figure 5-8: SECOND redundancy type selected ...................................................76
Figure 5-9: Redundancy type changed – SECOND after restart ...........................76
Figure 5-10: System menu – Remote Field Controller restart ..................................77
Figure 5-11: “REDUNDANCY – LOCAL INFORMATION” submenu –
redundancy type: SECOND ................................................................77
Figure 5-12: System menu ......................................................................................78
Figure 5-13: System menu – IP settings – IP parameters for LAN2 .........................79
Figure 5-14: System menu – Edit IP address (LAN2) ..............................................79
Figure 5-15: IP address will be changed after restart ..............................................80
Figure 5-16: System menu – invalid entry ...............................................................80
Figure 5-17: System menu – IP settings – Edit subnetmask (LAN2) ........................80
Figure 5-18: System menu – subnet mask changed ...............................................81
Figure 5-19: System menu – IP settings – settings applied following restart ............81
Figure 5-20: System menu – Remote Field Controller restart ..................................82
Figure 5-21: Both Remote Field Controllers are in the “Basic Sync” state ...............83
Section 6
Figure 6-1: “File, New Project...” command ...........................................................86
Figure 6-2: Project templates ................................................................................87
Figure 6-3: “Save/Zip project as” dialog box .........................................................87
Figure 6-4: Project information after creating a new project ..................................88
Figure 6-5: Project information in the example project ..........................................89
Figure 6-6: Device Details – FIRST IP settings ......................................................90
Figure 6-7: “Device Details” window: selecting the communication path ...............91
Figure 6-8: PROFINET node: Read PROFINET ....................................................92
Figure 6-9: “Read PROFINET” dialog box .............................................................93
Figure 6-10: “Select PROFINET device description” dialog box ..............................93
Section 7
Figure 7-1: Redundancy status: display of error code ...........................................99
Figure 7-2: Redundancy status, diagnostics: display of error message ................99
Figure 7-3: Diag+, redundancy information: display of error information .............100
Section 8
Figure 8-1: Updating the firmware .......................................................................104
Figure 8-2: Replacing the fan module .................................................................105
Section 9
Figure 9-1: Selecting the interface/communication path .....................................107
Figure 9-2: Standard task: DEFAULT or CYCLIC type ........................................108
Figure 9-3: Network Settings: FIRST-LAN2 (A), SECOND-LAN2 (B) .................109
Figure 9-4: Redundant variables: “Global Variables” worksheet .........................111
Figure 9-5: Redundant variables: “MainV” worksheet .........................................112
Figure 9-6: Diag+: “Redundancy information – Swap redundancy role” ..............113
Figure 9-7: Redundancy role switched over ........................................................114
Figure 9-8: Ensuring realtime ..............................................................................116
Figure 9-9: Extended Settings: Open FTP Folder on Device ...............................117
Figure 9-10: File structure on the parameterization memory .................................118
Figure 9-11: Internet Options: Enable folder view for FTP sites .............................118
Figure 9-12: Deactivating the FTP server ..............................................................119
Figure 9-13: PROFINET device – “Substitute value behavior of inputs” ................120
Appendix A
Figure A-1: Interfaces of the RFC 460R PN 3TX .................................................139
Figure A-2: Contact assignment of the Ethernet port in RJ45 format ...................139
Figure A-3: Pin assignment of the USB interfaces ...............................................140
Figure A-4: Connecting the supply voltage ..........................................................141
Section 2
Table 2-1: Switch-over conditions.........................................................................24
Section 3
Table 3-1: Functions of the operating keys ...........................................................32
Table 3-2: Status information: CONTROL ............................................................37
Table 3-3: Status information: REDUNDANCY.....................................................37
Table 3-4: Status information: PROFINET controller ............................................38
Table 3-5: Diagnostic indicators: PLC...................................................................39
Table 3-6: Diagnostic indicators: redundancy status (RED)..................................39
Table 3-7: Diagnostic indicators: PN-C (PROFINET controller) ............................40
Table 3-8: Operating modes of the Remote Field Controller.................................51
Section 5
Table 5-1: Steps for starting up the RFC 460R PN 3TX /
redundant control system ....................................................................71
Section 7
Table 7-1: Possible errors for the RFC 460R PN 3TX .........................................101
Section 9
Table 9-1: Overview of function blocks ...............................................................121
Table 9-2: Overview of function blocks ...............................................................122
Section 10
Table 10-1: System variables of the IEC 61131 runtime system ...........................123
Table 10-2: System variables of the control processor .........................................124
Table 10-3: System variable of the control processor ...........................................124
Table 10-4: PROFINET system variables (PROFINET controller function) ...........125
Table 10-5: System variables of the system time..................................................126
Table 10-6: System variables of the FTP, HTTP, and SNTP server......................126
Table 10-7: System variables of the Remote Field Controller ...............................127
Table 10-8: Redundancy-specific variables of the Remote Field Controller..........128
Appendix A
Table A-1: Contact assignment of the Ethernet ports in RJ45 format ..................140
Table A-2: Pin assignment of the USB interfaces................................................140
B L
BACKUP ............................................................... 12, 22 LCD
Diagnostic indicators ............................................. 39
D Indicators in the LCD ............................................. 36
Diagnostic indicators Main menu............................................................. 33
Control (PLC) ........................................................ 39 Redundancy submenu .......................................... 34
PROFINET controller (PN-C)................................. 40 Status information.................................................. 37
Redundancy status (RED)..................................... 39 System menu ........................................................ 35
Lower-level network ring redundancy
E MRP ...................................................................... 14
Error
Display .................................................................. 99
M
Error messages......................................................... 101 Media Redundancy Protocol ....................................... 20
Extended ring redundancy .......................................... 16 Menu items
Extended ring redundancy protocol ............................ 16 REDUNDANCY submenu ..................................... 46
System menu ........................................................ 41
F Mode selector switch .................................................. 51
Monitoring times.......................................................... 13
Fan module ................................................................. 30
Mounting ..................................................................... 59
Replacement ....................................................... 105
Mounting the fan ......................................................... 60
Firmware
MRP ............................................................................ 20
Updating.............................................................. 103
FTP functionality ....................................................... 117
O
G Operating keys and LCD ............................................. 31
R S
Rapid Spanning Tree Protocol SFP module
with fast ring detection ................................................ 18 Mounting ............................................................... 62
Realtime clock Software requirements .................................................. 9
Setting ................................................................. 107 Startup ........................................................................ 71
Redundancy role......................................................... 12 Status and diagnostic indicators (Ethernet)................. 31
Redundancy roles Status information
Switching............................................................. 113 Controller (CONTROL).......................................... 37
Redundancy type ........................................................ 12 PROFINET controller (PROFINET CONTROL) ..... 38
FIRST .................................................................... 12 Redundancy status (REDUNDANCY) ................... 37
SECOND............................................................... 12 Switch-over conditions ................................................ 24
Redundant control system .......................................... 12 Synchronization connection
Description ............................................................ 11 Interruption ............................................................ 26
Features ................................................................ 11 System behavior ......................................................... 22
Function ................................................................ 11 System states.............................................................. 22
Structure................................................................ 11 System variables....................................................... 123
Redundant variables ................................................. 111
Remote Field Controller T
General description ............................................... 27
Task properties ......................................................... 108
Removal...................................................................... 60
Repair ....................................................................... 105
Replacement............................................................... 65
Requirements
Hardware and software ........................................... 9
Restart
FIRST .................................................................... 82
SECOND............................................................... 77
RFC 460R PN 3TX
Fan module ........................................................... 30
Indicators............................................................... 29
Interfaces .............................................................. 29
Mounting ............................................................... 59
Operating elements ............................................... 29
Scope of supply......................................... 29, 34, 35
RSTP .......................................................................... 18