You are on page 1of 152

Installing and operating the

RFC 460R PN 3TX


Remote Field Controller as a
redundant control system

User manual
User manual
Installing and operating the RFC 460R PN 3TX Remote Field Controller
as a redundant control system

2016-05-20

Designation: UM EN RFC 460R PN 3TX

Revision: 03

Order No.: —

This user manual is valid for:

Designation As of version Order No.


RFC 460R PN 3TX HW: 01 2700784
FW: 5.00

PHOENIX CONTACT 8291_en_03


Please observe the following notes
User group of this manual
The use of products described in this manual is oriented exclusively to:
– Qualified electricians or persons instructed by them, who are familiar with applicable
standards and other regulations regarding electrical engineering and, in particular, the
relevant safety concepts.
– Qualified application programmers and software engineers, who are familiar with the
safety concepts of automation technology and applicable standards.
Explanation of symbols used and signal words

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.

Published by PHOENIX CONTACT GmbH & Co. KG


Flachsmarktstraße 8
32825 Blomberg
GERMANY
Should you have any suggestions or recommendations for improvement of the contents and
layout of our manuals, please send your comments to:
tecdoc@phoenixcontact.com

PHOENIX CONTACT
Please observe the following notes

General terms and conditions of use for technical documentation


Phoenix Contact reserves the right to alter, correct, and/or improve the technical
documentation and the products described in the technical documentation at its own
discretion and without giving prior notice, insofar as this is reasonable for the user. The
same applies to any technical changes that serve the purpose of technical progress.
The receipt of technical documentation (in particular user documentation) does not
constitute any further duty on the part of Phoenix Contact to furnish information on
modifications to products and/or technical documentation. You are responsible to verify the
suitability and intended use of the products in your specific application, in particular with
regard to observing the applicable standards and regulations. All information made
available in the technical data is supplied without any accompanying guarantee, whether
expressly mentioned, implied or tacitly assumed.
In general, the provisions of the current standard Terms and Conditions of Phoenix Contact
apply exclusively, in particular as concerns any warranty liability.
This manual, including all illustrations contained herein, is copyright protected. Any
changes to the contents or the publication of extracts of this document is prohibited.
Phoenix Contact reserves the right to register its own intellectual property rights for the
product identifications of Phoenix Contact products that are used here. Registration of such
intellectual property rights by third parties is prohibited.
Other product identifications may be afforded legal protection, even where they may not be
indicated as such.

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

2 The redundant control system ..................................................................................................11


2.1 General description of the redundant control system...........................................11
2.1.1 Extended ring redundancy protocol (extended ring redundancy) .........16
2.1.2 RSTP – Rapid Spanning Tree Protocol with fast ring detection ..........18
2.1.3 MRP – Media Redundancy Protocol ....................................................20
2.2 System states ......................................................................................................22
2.3 System behavior..................................................................................................22
2.4 Notes on operating the redundant control system ...............................................24
2.4.1 Switch-over conditions .........................................................................24
2.4.2 Operation with only one Remote Field Controller .................................25
2.4.3 Behavior of the redundant control system when the
synchronization connection is interrupted ............................................26

3 Description of the RFC 460R PN 3TX Remote Field Controller ................................................27


3.1 General description of the Remote Field Controller .............................................27
3.2 Indicators, interfaces, and operating elements ....................................................29
3.3 Fan module..........................................................................................................30
3.4 Status and diagnostic indicators (Ethernet) .........................................................31
3.5 Operating keys and LCD .....................................................................................31
3.6 LCD (diagnostic display)......................................................................................33
3.6.1 Main menu ...........................................................................................33
3.6.2 REDUNDANCY submenu ....................................................................34
3.6.3 System menu .......................................................................................35
3.6.4 Indicators in the LCD ............................................................................36
3.6.5 Status information ................................................................................37
3.6.6 Diagnostic indicators ............................................................................39
3.6.7 System menu – meaning of menu items ...............................................41
3.6.8 CONTROL DETAILS submenu ............................................................45
3.6.9 REDUNDANCY submenu – meaning of menu items ............................46
3.6.10 PROFINET CONTROL submenu PN-C DETAILS ...............................50
3.7 Mode selector switch ...........................................................................................51
3.8 Interfaces.............................................................................................................52
3.8.1 SYNC interface ....................................................................................52
3.8.2 Ethernet interfaces ...............................................................................52
3.8.3 USB interfaces .....................................................................................54
3.8.4 Connecting the power supply ...............................................................54

8291_en_03 PHOENIX CONTACT 5


RFC 460R PN 3TX

3.9 Power supply .......................................................................................................55


3.9.1 Sizing of the power supply ...................................................................55

4 Mounting, removal, electrical installation, and replacement .....................................................57


4.1 General................................................................................................................57
4.2 Mounting the RFC 460R PN 3TX.........................................................................59
4.2.1 Mounting the fan ..................................................................................60
4.3 Removing the RFC 460R PN 3TX .......................................................................60
4.4 Inserting/removing the parameterization memory................................................60
4.5 Connecting the interfaces ....................................................................................62
4.5.1 Connecting the synchronization connection to the SYNC interface
(fiber optics) .........................................................................................62
4.5.2 Connecting the Ethernet network .........................................................63
4.6 Connecting the supply voltage.............................................................................64
4.7 Replacing the RFC 460R PN 3TX........................................................................65

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

6 Integration of the RFC 460R PN 3TX in PC Worx ....................................................................85


6.1 Creating and saving a new project.......................................................................86
6.2 Specifying project information .............................................................................88
6.3 IP addresses of the Remote Field Controller (FIRST) ..........................................89
6.4 Communication paths for the RFC 460R PN 3TX ................................................90
6.5 Reading the PROFINET network/assigning PROFINET device names ...............92
6.5.1 Reading the PROFINET network .........................................................92
6.5.2 Naming PROFINET devices ................................................................94
6.5.3 PROFINET device name and IP address .............................................95
6.6 Compiling and sending a project to the Remote Field Controller .........................96
6.7 Performing a cold restart for the Remote Field Controller ....................................97

7 Errors, diagnostic messages, and removal ..............................................................................99


7.1 Display of errors...................................................................................................99
7.2 Possible errors...................................................................................................101

6 PHOENIX CONTACT 8291_en_03


Table of contents

8 Updating the firmware, repair, replacing the fan module ........................................................103


8.1 Updating the device firmware ............................................................................103
8.2 Repair ................................................................................................................105
8.3 Replacing the fan module ..................................................................................105

9 Additional settings/redundancy features in PC Worx .............................................................107


9.1 Setting the realtime clock...................................................................................107
9.2 Setting task properties .......................................................................................108
9.3 Device Details, Extended Settings – Network Settings ......................................109
9.4 Redundant variables..........................................................................................111
9.5 Switching redundancy roles...............................................................................113
9.6 Download changes ............................................................................................116
9.7 Parameterization memory and Internet Explorer................................................117
9.7.1 Internet Explorer FTP function ............................................................118
9.7.2 Activating/deactivating the FTP server ...............................................119
9.7.3 Activating/deactivating the HTTP server ............................................119
9.8 Substitute value behavior for PROFINET devices .............................................120
9.9 Function blocks for handling files in the parameterization memory ....................121
9.10 Function blocks for Ethernet communication .....................................................122

10 System variables ....................................................................................................................123


10.1 IEC 61131 runtime system.................................................................................123
10.2 Control processor (CPU) ...................................................................................124
10.3 PROFINET system variables .............................................................................125
10.4 System time.......................................................................................................126
10.5 Ethernet .............................................................................................................126
10.6 Remote Field Controller.....................................................................................127
10.7 Redundancy-specific system variables of the Remote Field Controller .............128

11 Technical data and ordering data ...........................................................................................133


11.1 Technical data ...................................................................................................133
11.2 Ordering data.....................................................................................................136
11.2.1 Products .............................................................................................136
11.2.2 Accessories .......................................................................................136
11.2.3 Software .............................................................................................137
11.2.4 Documentation ...................................................................................137

8291_en_03 PHOENIX CONTACT 7


RFC 460R PN 3TX

A Appendix: interfaces of the RFC 460R PN 3TX ......................................................................139


A1 Ethernet interfaces LAN1.1/LAN1.2 and LAN2 (10/100Base-T) ........................139
A2 USB interfaces...................................................................................................140
A3 SYNC interface..................................................................................................140
A4 Connecting the supply voltage...........................................................................141

B Appendixes.............................................................................................................................143
B1 List of figures .....................................................................................................143
B2 List of tables ......................................................................................................149
B3 Index..................................................................................................................151

8 PHOENIX CONTACT 8291_en_03


Introduction

1 Introduction

1.1 Purpose of this user manual

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.

1.2 Hardware and software requirements

– 2 x RFC 460R PN 3TX Remote Field Controller


– 2 x 256 MB or higher parameterization memory (CF card)

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.

8291_en_03 PHOENIX CONTACT 9


RFC 460R PN 3TX

1.3 Increased safety precautions

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).

10 PHOENIX CONTACT 8291_en_03


The redundant control system

2 The redundant control system

2.1 General description of the redundant control


system

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.

Features – Easy startup and automatic configuration of all redundancy functions


– Up to 80 km distance between the Remote Field Controllers via fiber optic
synchronization connection using SFP modules (small form factor plug-in modules)
– Uninterrupted process – even in the event of failure or when a Remote Field Controller
is replaced
– Display for displaying status and error messages in plain text
– Redundancy for your Ethernet network, thanks to device integration using the
PROFINET standard
– Uninterrupted visualization, thanks to redundancy-capable OPC servers

Figure 2-1 Redundant control system for distances up to 80 km

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.

The fiber optic synchronization connection is a direct point-to-point connection between


both Remote Field Controllers of the redundant control system.

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.

8291_en_03 PHOENIX CONTACT 11


RFC 460R PN 3TX

The Remote Field Controllers automatically establish a high-performance connection for


exchanging configuration data and project information. Both Remote Field Controllers
automatically configure and synchronize all the redundancy functions.
Before each cycle, the Remote Field Controller controlling the process (PRIMARY
redundancy role) transmits the data that is to be synchronized to the Remote Field
Controller that is in HotStandBy mode (BACKUP redundancy role).

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

+
-

Figure 2-2 Redundant control system

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.

Figure 2-4 on page 14 shows an example of a redundant (higher-level) control system


consisting of two RFC 460R PN 3TX devices. This redundantly connected control system
for synchronization via fiber optics has a lower-level PROFINET network which has been
designed redundantly, e.g., using the Media Redundancy Protocol (MRP). The PROFINET
devices (in the example: class 100 Inline controller and Inline bus coupler, both with
PROFINET device function) are connected to the infrastructure components of the network
(Smart Managed Compact Switches (SMCS) from Phoenix Contact).

12 PHOENIX CONTACT 8291_en_03


The redundant control system

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.

Figure 2-4 on page 14 shows a general PROFINET network structure.


The PC used for programming and visualization with PC Worx/OPC configurator is
connected to the LAN1.1 interfaces of the Remote Field Controllers. Alternatively, the PC
can also use infrastructure components to access the LAN2 Ethernet interface of the
Remote Field Controllers (see Figure 2-5 on page 15).
The examples below illustrate the special features of using the various different network
protocols.
– Extended ring redundancy protocol (extended ring redundancy), page 16
– RSTP – Rapid Spanning Tree Protocol with fast ring detection, page 18
– MRP – Media Redundancy Protocol, page 20

Switch-over times/monitoring times


Depending on the relevant example, there are different maximum switch-over times in the
implemented ring.
Please note that when setting update times for inputs and outputs and the number of faulty
telegrams for PROFINET devices in PC Worx, monitoring times must be greater than the
maximum switch-over time.
Enter these values under “Device Details” in the “PROFINET Settings” tab of the relevant
PROFINET device (see Figure 2-3).

Figure 2-3 Device Details: switch-over times/monitoring times

8291_en_03 PHOENIX CONTACT 13


RFC 460R PN 3TX

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

USB LAN2 USB LAN2


ACT ACT

24VDC 24VDC
+ +
SYNC - SYNC -

SYNC

C FL SWITCH SMSC 8GT


Ord. No. 2891123
MODE

1 3 5 7
C 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

MAC US1 US2 FAIL MAC US1 US2 FAIL

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

C FL SWITCH SMSC 8GT


Ord. No. 2891123
MODE

C FL SWITCH SMSC 8GT


Ord. No. 2891123
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

MAC
Address

X9
00.A0.45.06.04.02

US1 GND US2 GND


X10
R1 R2
X11
MEM
US1 US2 FAIL
1

Mode
2 3 4 5 6 7 8

X12
V.24
PROFINET MAC
Address

X9
00.A0.45.06.04.02

US1 GND US2 GND


X10
R1 R2
X11
MEM
US1 US2 FAIL
1

Mode
2 3 4 5 6 7 8

X12
V.24

D ILC 170 ETH 2TX


Order-No.: 2916532
HW/FW: 00/220
MAC Addr.: xx.xx.xx.xx FR E RDY FAIL BSA PF
E IL PN BK DI8 DO4 2TX-PAC
Order-No.: 2703994
HW/FW: 00/100
MAC Addr.: xx.xx.xx.xx
PWR O1
D E
I1 I2

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

PROFINET ETHERNET SYNC 8291B003

Figure 2-4 Redundant higher-level control system with RFC 460R PN 3TX and lower-
level network ring redundancy using MRP

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
C Infrastructure components (in the example: SMCS switches)

14 PHOENIX CONTACT 8291_en_03


The redundant control system

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 LNK LNK


LAN1.1 LAN1.2
RFC 460R PN 3TX LAN1.1 LAN1.2
RFC 460R PN 3TX
Ord.No. 2700784 Ord.No. 2700784
ACT ACT ACT ACT

LNK LNK

USB LAN2 USB LAN2


ACT ACT

24VDC 24VDC
+ +
SYNC - SYNC -

SYNC
PROFINET

C FL SWITCH SMSC 8GT


Ord. No. 2891123
MODE

1 3 5 7
C 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

MAC US1 US2 FAIL MAC US1 US2 FAIL


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

ETHERNET

C C MODE
PROFINET

MODE

FL SWITCH SMSC 8GT FL SWITCH SMSC 8GT


Ord. No. 2891123 Ord. No. 2891123

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 US1 US2 FAIL


MAC US1 US2 FAIL
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
PROFINET

D ILC 170 ETH 2TX


Order-No.: 2916532
HW/FW: 00/220
MAC Addr.: xx.xx.xx.xx FR E RDY FAIL BSA PF
E IL PN BK DI8 DO4 2TX-PAC
Order-No.: 2703994
HW/FW: 00/100
MAC Addr.: xx.xx.xx.xx
PWR O1
D E
I1 I2

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

PROFINET ETHERNET SYNC 8291A005

Figure 2-5 Programming and visualization using infrastructure components at LAN2

8291_en_03 PHOENIX CONTACT 15


RFC 460R PN 3TX

2.1.1 Extended ring redundancy protocol


(extended ring redundancy)

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

USB LAN2 USB LAN2


ACT ACT

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

PROFINET ETHERNET SYNC 8291A004

Figure 2-6 PROFINET network/PROFINET ring with extended ring redundancy

16 PHOENIX CONTACT 8291_en_03


The redundant control system

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 300... managed switches (nmax = 134)
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 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

Monitoring time of inputs and outputs: 24 ms

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.

8291_en_03 PHOENIX CONTACT 17


RFC 460R PN 3TX

2.1.2 RSTP – Rapid Spanning Tree Protocol with fast ring


detection

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

USB LAN2 USB LAN2


ACT ACT

24VDC 24VDC
+ +
SYNC - SYNC -

SYNC

C1 FL SWITCH SMSC 8GT


Ord. No. 2891123
MODE

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

C3 FL SWITCH SMSC 8GT


Ord. No. 2891123
MODE

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

ACT SPD FD 2 4 6 8 ACT SPD FD 2 4 6 8 ACT SPD FD 2 4 6 8

LINK LINK LINK

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

Mode Mode Mode


X9 X10 X11 X12 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 US1 GND US2 GND R1 R2 MEM V.24

PROFINET PROFINET

D ILC 170 ETH 2TX


Order-No.: 2916532
HW/FW: 00/220
MAC Addr.: xx.xx.xx.xx FR E RDY FAIL BSA PF
En IL PN BK DI8 DO4 2TX-PAC
Order-No.: 2703994
HW/FW: 00/100
MAC Addr.: xx.xx.xx.xx
PWR O1
D E
I1 I2
E1 IL PN BK DI8 DO4 2TX-PAC
Order-No.: 2703994
HW/FW: 00/100
MAC Addr.: xx.xx.xx.xx
PWR O1
D E
I1 I2

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

PROFINET ETHERNET SYNC 8291A006

Figure 2-7 PROFINET ring with RSTP – Rapid Spanning Tree Protocol with fast ring
detection

18 PHOENIX CONTACT 8291_en_03


The redundant control system

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

Monitoring time of inputs and outputs: 528 ms

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.

8291_en_03 PHOENIX CONTACT 19


RFC 460R PN 3TX

2.1.3 MRP – Media Redundancy Protocol

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

USB LAN2 USB LAN2


ACT ACT

24VDC 24VDC
+ +
SYNC - SYNC -

SYNC

C1 FL SWITCH SMSC 8GT


Ord. No. 2891123
MODE

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

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

D ILC 170 ETH 2TX


Order-No.: 2916532
HW/FW: 00/220
MAC Addr.: xx.xx.xx.xx FR E RDY FAIL BSA PF
En IL PN BK DI8 DO4 2TX-PAC
Order-No.: 2703994
HW/FW: 00/100
MAC Addr.: xx.xx.xx.xx
PWR O1
D E
I1 I2
E1 IL PN BK DI8 DO4 2TX-PAC
Order-No.: 2703994
HW/FW: 00/100
MAC Addr.: xx.xx.xx.xx
PWR O1
D E
I1 I2

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

PROFINET ETHERNET SYNC 8291A007

Figure 2-8 MRP – Media Redundancy Protocol

20 PHOENIX CONTACT 8291_en_03


The redundant control system

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

Monitoring time of inputs and outputs: 216 ms

In the PROFINET ring, when the Media Redundancy Protocol is used, a maximum of
50 PROFINET devices can be operated depending on the application.

8291_en_03 PHOENIX CONTACT 21


RFC 460R PN 3TX

2.2 System states

For information on the redundancy states of the redundant control system, please refer to
Section “Status information” on page 37.

2.3 System behavior

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

22 PHOENIX CONTACT 8291_en_03


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.

8291_en_03 PHOENIX CONTACT 23


RFC 460R PN 3TX

2.4 Notes on operating the redundant control system

2.4.1 Switch-over conditions

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.

Table 2-1 Switch-over conditions

Code Display in Diag+ Meaning


RSN_LST_SWTCHOV_1 Switch-Over by user The redundancy role switch-
(display) over was initiated by the user
via the display (menu:
Redundancy).
RSN_LST_SWTCHOV_2 Runtime error on PRIMARY A runtime error occurred on
PLC the PRIMARY Remote Field
Controller.
RSN_LST_SWTCHOV_3 Linkdown at the PROFINET The physical network
controller interface connection to the LAN2
interface was disconnected
(LNK LED: OFF).
RSN_LST_SWTCHOV_4 Parameterization memory of The parameterization
the PRIMARY PLC memory of the PRIMARY
removed. Remote Field Controller was
removed.
RSN_LST_SWTCHOV_5 Switch-Over by user The redundancy role switch-
(firmware service) over was initiated by the user
via the firmware service or
from Diag+.
RSN_LST_SWTCHOV_6 The PROFINET controller of At the LAN2 PROFINET
the PRIMARY PLC has lost controller interface, the
the connections to all Remote Field Controller has
devices. lost the communication
connection to all PROFINET
devices.
RSN_LST_SWTCHOV_7 Firmware update has A firmware update has
started. started on the PRIMARY
Remote Field Controller.
RSN_LST_SWTCHOV_8 Firmware has shutdown. The firmware of the
PRIMARY Remote Field
Controller has shut down; for
example, on a restart that
was initiated via the display
or from PC Worx.
RSN_LST_SWTCHOV_9 A timeout occurred on the A timeout occurred on the
SyncLink connection. fiber optic synchronization
connection.

24 PHOENIX CONTACT 8291_en_03


The redundant control system

2.4.2 Operation with only one Remote Field Controller

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.

8291_en_03 PHOENIX CONTACT 25


RFC 460R PN 3TX

2.4.3 Behavior of the redundant control system when the


synchronization connection is interrupted

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:

Figure 2-10 Fiber optic synchronization connection interrupted

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.

26 PHOENIX CONTACT 8291_en_03


Description of the RFC 460R PN 3TX Remote Field Controller

3 Description of the RFC 460R PN 3TX Remote Field


Controller

3.1 General description of the Remote Field Controller

The Remote Field Controller is a high-performance controller with integrated Ethernet


connection. When using the Ethernet connection, the PROFINET protocol can be used. The
I/O level is connected to the Remote Field Controller via PROFINET. Connection options for
Ethernet are available for networking with higher-level systems, such as the control level or
operating level.
When it comes to distributed, modular automation, Remote Field Controllers (RFCs) with
IEC 61131 control intelligence and network connection are the ideal solution. As compact
DIN-rail mountable controllers, Remote Field Controllers provide networked, PC-based
control performance locally on the DIN rail.

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.

8291_en_03 PHOENIX CONTACT 27


RFC 460R PN 3TX

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)

28 PHOENIX CONTACT 8291_en_03


Description of the RFC 460R PN 3TX Remote Field Controller

3.2 Indicators, interfaces, and operating elements

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.

8291_en_03 PHOENIX CONTACT 29


RFC 460R PN 3TX

3.3 Fan module

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.

Figure 3-2 Remote Field Controller with fan module

30 PHOENIX CONTACT 8291_en_03


Description of the RFC 460R PN 3TX Remote Field Controller

3.4 Status and diagnostic indicators (Ethernet)

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

+
-

Figure 3-3 LNK and ACT LEDs

3.5 Operating keys and LCD

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

Figure 3-4 Remote Field Controller keypad

8291_en_03 PHOENIX CONTACT 31


RFC 460R PN 3TX

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.

Table 3-1 Functions of the operating keys

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.

Increase selected value: “+1”.

Decrease selected value: “-1”.

Select next position of value to be edited.

– Execute selection (e.g., controller reset/restart).


– Apply changes and return to menu item.
– Horizontally left-scroll the selected value/displayed error message.

– Horizontally right-scroll the selected value/displayed error message.

Stop horizontal scrolling.

Return to home menu.

Call system menu.

Refresh display contents.

Return to previous menu. Changes are not applied. This is indicated by a


message (see Figure 5-7 on page 75).

32 PHOENIX CONTACT 8291_en_03


Description of the RFC 460R PN 3TX Remote Field Controller

3.6 LCD (diagnostic display)

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.

3.6.1 Main menu

The following figure shows the structure of the main menu:

1x + 2x + 3x +

B C D

8291A010

Figure 3-5 Structure of the main menu

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

8291_en_03 PHOENIX CONTACT 33


RFC 460R PN 3TX

3.6.2 REDUNDANCY submenu

The following figure shows the structure of the REDUNDANCY submenu:

1x + 3x + 5x +

2x + 4x + 6x +

C1 C2 C3 C4 C5 C6

8291A011

Figure 3-6 Structure of the REDUNDANCY submenu

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.

34 PHOENIX CONTACT 8291_en_03


Description of the RFC 460R PN 3TX Remote Field Controller

3.6.3 System menu

The following figure shows the structure of the system menu:

1x + 3x + 5x +

2x + 4x + 6x +

E1 E2 E3 E4 E5 E6

8291A012

Figure 3-7 Structure of the system menu

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.

E6 SYSTEM MENU – RESTART submenu: restart Remote Field Controller

For additional information on the system menu, please refer to Section “System menu –
meaning of menu items” on page 41.

8291_en_03 PHOENIX CONTACT 35


RFC 460R PN 3TX

3.6.4 Indicators in the LCD

The following figure shows the general meaning of the indicators in the LCD main menu.

PC Worx project name Status information

Control/PLC

Diagnostic
indicators: Redundancy status
LEDs

PROFINET controller

Figure 3-8 LCD: indicators in the main menu

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.

Local information, here the Status information, here the


Remote Field Controller that Remote Field Controller
controls the process defined as the SECOND
redundancy type

Diagnostic indicators:
LEDs

Figure 3-9 LCD: indicators in the submenu

36 PHOENIX CONTACT 8291_en_03


Description of the RFC 460R PN 3TX Remote Field Controller

3.6.5 Status information

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.

8291_en_03 PHOENIX CONTACT 37


RFC 460R PN 3TX

Table 3-3 Status information: REDUNDANCY

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.

38 PHOENIX CONTACT 8291_en_03


Description of the RFC 460R PN 3TX Remote Field Controller

3.6.6 Diagnostic indicators

The diagnostic indicators of all areas are displayed in each submenu using virtual LEDs.
They have the following meaning:

Figure 3-10 Diagnostic indicators in the submenus (LEDs)

Control (PLC)
Table 3-5 Diagnostic indicators: PLC

LED Color Meaning


The application program is in the RUN state.
ON [(Standard) operations are being processed
RUN Green cyclically.]
Flashing The application program is in the STOP state.
ON An error has occurred.
FAIL Red
Flashing The controller is in debug mode (HALT).

Redundancy status (RED)


Table 3-6 Diagnostic indicators: redundancy status (RED)

LED Color Meaning


The Remote Field Controller has the PRIMARY
ON
PR Green redundancy role.
OFF –
The Remote Field Controller has the BACKUP
ON
BA Green redundancy role.
OFF –
The SYNC interface is physically linked (Physical
ON
Green Link).
PL OFF –
ON The SYNC interface is not physically linked.
Red
OFF –
Monitoring of the synchronization connection via the
ON
Green SYNC interface is active (Logical Link).
OFF –
Monitoring of the synchronization connection via the
ON
LL Orange LAN2 interface is active.
OFF –
Monitoring of the synchronization connection is not
ON
Red (yet) active.
OFF –

8291_en_03 PHOENIX CONTACT 39


RFC 460R PN 3TX

PROFINET controller
(PN-C)
Table 3-7 Diagnostic indicators: PN-C (PROFINET controller)

LED Color Meaning


No link status at Ethernet port and/or no 100 Mbit
ON transmission and/or no full duplex operation
available.
Link status available, at least one configured
BF Red Flashing PROFINET device has no PROFINET
communication connection.
The PROFINET controller has established an active
OFF communication connection to each configured
PROFINET device.
Group error message:
ON
At least one diagnostic alarm present.
SF Red
Group error message not present. No diagnostic
OFF
alarms present.

40 PHOENIX CONTACT 8291_en_03


Description of the RFC 460R PN 3TX Remote Field Controller

3.6.7 System menu – meaning of menu items

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:

Figure 3-11 System menu

The following items can be selected in the system menu:


– IP settings for LAN1 Ethernet interface (IP CFG LAN1)
– IP settings for LAN2 Ethernet interface (IP CFG LAN2)
(See Section “Specifying the IP addresses of the Remote Field Controller defined as
FIRST” on page 78)
– System information (SYSTEM INFO)
(See page 42)
– Options that can be selected (OPTIONS):
Screensaver, Backlight, Language
(See page 42)
– Updating the device firmware of the Remote Field Controller (FW-UPDATE)
(See page 44)
– Resetting the Remote Field Controller (RESTART)
(See page 44)

8291_en_03 PHOENIX CONTACT 41


RFC 460R PN 3TX

SYSTEM INFO System information

• To view the system information, use the , , and keys in the system menu

to select the “SYSTEM INFO” menu item.

The following information is displayed (you can also view the version information for the
standard part of the Remote Field Controller here):

Figure 3-12 System menu – system information

OPTIONS Options for the built-in LCD


The following display settings can be modified in the OPTIONS submenu:
– Screensaver
– Backlight
– Language

Figure 3-13 System menu – OPTIONS

Screensaver for built-in LCD


To protect the LCD, a screensaver is activated after a preset time. The time after which the
screensaver is activated can be set as follows.

• To edit the screensaver switch-on time, select “Edit release time” using the , ,

and keys.

42 PHOENIX CONTACT 8291_en_03


Description of the RFC 460R PN 3TX Remote Field Controller

The following time information for the screensaver is displayed:

Figure 3-14 System menu – screensaver – time setting

• Use the , , and keys to set the switch-on time for the screensaver, e.g.,

13 minutes.

• Confirm your entries by pressing the key.

The following message appears in the display:

Figure 3-15 System menu – screensaver switch-on time set

• If you do not want to apply your settings, press the key instead of the key.

The following message is displayed:

Figure 3-16 System menu – no changes

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:

Figure 3-17 System menu – maximum screensaver switch-on time

8291_en_03 PHOENIX CONTACT 43


RFC 460R PN 3TX

LCD backlight and language


Backlighting can be enabled/disabled and the display language selected in a similar way to
setting the screensaver switch-on time in the OPTIONS submenu.

FW-UPDATE Updating the device firmware


The FW-UPDATE submenu starts the update of the device firmware of the Remote Field
Controller (see Section “Updating the device firmware” on page 103).

RESTART Resetting the Remote Field Controller


The RESTART submenu is used to reset the Remote Field Controller.

Use this menu item, for example, to activate IP settings in the controller that you made in
the “IP CFG LAN...” menu.

• Call the RESTART submenu using the , , and keys.

The following menu appears:

Figure 3-18 System menu – reset controller

• Use the and keys to set the “Yes” menu item.

• Confirm your entry by pressing the key.

The following message appears in the display:

Figure 3-19 System menu – resetting the Remote Field Controller

44 PHOENIX CONTACT 8291_en_03


Description of the RFC 460R PN 3TX Remote Field Controller

The Remote Field Controller is reset.

Changes that you have made in the system menu are stored on the parameterization

memory when you press the key.

If you have modified the IP settings, these changes only take effect when the Remote
Field Controller is restarted.

3.6.8 CONTROL DETAILS submenu

The elements of the CONTROL DETAILS submenu are described below in more detail.

• To call the menu, press the key and the key.

The following submenu appears:

Figure 3-20 CONTROL DETAILS submenu

The menu indicates whether the parameterization memory is inserted, the device
temperature, and the charging state of the battery inside the device.

8291_en_03 PHOENIX CONTACT 45


RFC 460R PN 3TX

3.6.9 REDUNDANCY submenu – meaning of menu items

The elements of the REDUNDANCY submenu are described below in more detail.

• To call the menu, press the key twice and the key.

The following submenu appears:

Figure 3-21 REDUNDANCY submenu

The following items can be selected in the system menu:


– Actions for the redundancy role of Remote Field Controllers (ACTIONS)
(see page 47)
– Information on the status of the local Remote Field Controller (LOCAL INFORMATION)
(see page 47)
– Information on the status of the remote Remote Field Controller
(REMOTE INFORMATION)
(see page 48)
– Information on the redundancy status (REDUNDANCY STATUS)
(see page 48)
– Information on the redundancy type for the local Remote Field Controller (SETTINGS)
(see page 49)
– Information on diagnostics for the redundant control system (DIAGNOSTICS)
(see page 49)

46 PHOENIX CONTACT 8291_en_03


Description of the RFC 460R PN 3TX Remote Field Controller

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.

Figure 3-22 REDUNDANCY submenu – ACTIONS

LOCAL INFORMATION Information on the local Remote Field Controller


The LOCAL INFORMATION submenu provides information on the local Remote Field
Controller.

Figure 3-23 REDUNDANCY submenu – LOCAL INFORMATION

8291_en_03 PHOENIX CONTACT 47


RFC 460R PN 3TX

REMOTE INFORMATION Information on the remote Remote Field Controller


The REMOTE INFORMATION submenu provides information on the remote Remote Field
Controller.

Figure 3-24 REDUNDANCY submenu – REMOTE INFORMATION

REDUNDANCY STATUS Information on the redundancy status


The REDUNDANCY STATUS submenu provides information on the:
– Number of redundancy role switch-overs since the last device power up.
– Interface currently being used to synchronize the redundant control system.

Figure 3-25 REDUNDANCY submenu – REDUNDANCY STATUS

48 PHOENIX CONTACT 8291_en_03


Description of the RFC 460R PN 3TX Remote Field Controller

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.

Figure 3-26 REDUNDANCY submenu – SETTINGS

DIAGNOSTICS Information on diagnostics for the redundant control system


The DIAGNOSTICS submenu provides the following information:
– Redundancy roles of the Remote Field Controllers
– Synchronization status of the redundant control system
– The last error that was diagnosed at the local Remote Field Controller
The “Reset last error” menu item can be used to reset the displayed last errors that
occurred.

Figure 3-27 REDUNDANCY submenu – DIAGNOSTICS

8291_en_03 PHOENIX CONTACT 49


RFC 460R PN 3TX

3.6.10 PROFINET CONTROL submenu PN-C DETAILS

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 following submenu appears:

Figure 3-28 PN-C DETAILS submenu – PROFINET IO Controller

This menu displays the following information:


– PROFINET device name of the PROFINET controller used – the device name is
assigned to the PROFINET controller in the PC Worx project (see Section “Naming
PROFINET devices” on page 94).
– Ethernet interface (adapter), which is used to connect the PROFINET controller to the
network
– Information on application relations (ARs)
– Projected ARs:
Application relations to PROFINET devices configured in the PC Worx project
If this menu item is selected, a list of configured PROFINET devices is displayed in
the LCD.
– Number of active ARs:
Number of active application relations to configured PROFINET devices
– No. of act. ARs driving BF:
Number of active application relations which control the BF LED at the PROFINET
controller.
– ARs with DiagInfo:
Number of application relations with available diagnostic information
If this menu item is selected, a list of PROFINET devices for which diagnostic
information is available is displayed in the LCD. The diagnostic information is
displayed as hexadecimal code.
For more detailed information on diagnostics/error codes, please refer to Section
“Errors, diagnostic messages, and removal” on page 99.

50 PHOENIX CONTACT 8291_en_03


Description of the RFC 460R PN 3TX Remote Field Controller

3.7 Mode selector switch

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.

Table 3-8 Operating modes of the Remote Field Controller

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.

If the mode selector switch of the Remote Field Controller


that controls the process (PRIMARY) is set to the STOP
position, both Remote Field Controllers (PRIMARY and
BACKUP) enter the STOP state (CONTROL). The
redundancy status for both Remote Field Controllers
changes to FollowUp Sync (FSYN).
If the mode selector switch of the BACKUP Remote Field
Controller is set to the STOP position, only this Remote
Field Controller enters the STOP state (CONTROL). The
redundancy status for both Remote Field Controllers
changes to FollowUp Sync (FSYN).

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

Figure 3-29 Mode selector switch

8291_en_03 PHOENIX CONTACT 51


RFC 460R PN 3TX

3.8 Interfaces

A B1 B2

LAN1.1
LAN1.2
LAN2

SYNC

Figure 3-30 Interfaces of the RFC 460R PN 3TX

A : Ethernet interfaces LAN1.1/LAN1.2 and LAN2


B1 : SYNC synchronization interface
B2 : Synchronization interface with inserted SFP module

3.8.1 SYNC interface

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.

3.8.2 Ethernet interfaces

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.

52 PHOENIX CONTACT 8291_en_03


Description of the RFC 460R PN 3TX Remote Field Controller

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.

Information on IP settings of the Ethernet interfaces

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.

Information on the installation of an Ethernet network

Use an Ethernet cable according to CAT5 of IEEE 802.3.


When working on PROFINET and its components, the following documents must always
be available and observed at all times.
– PROFINET Installation Guideline for Cabling and Assembly
– PROFIBUS Guideline
These documents are available on the Internet at www.profinet.com or you can contact
your local Phoenix Contact representative regarding these documents (see also Section
“Documentation” on page 137).

For the interface assignment, please refer to “Ethernet interfaces LAN1.1/LAN1.2 and
LAN2 (10/100Base-T)” on page 139.

8291_en_03 PHOENIX CONTACT 53


RFC 460R PN 3TX

3.8.3 USB interfaces

See Section “USB interfaces” on page 140

3.8.4 Connecting the power supply

See Section “Connecting the supply voltage” on page 64 and Section “Connecting the
supply voltage” on page 141.

54 PHOENIX CONTACT 8291_en_03


Description of the RFC 460R PN 3TX Remote Field Controller

3.9 Power supply

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.

3.9.1 Sizing of the power supply

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.

WARNING: Loss of electrical safety when using unsuitable power supplies


The RFC 460R PN 3TX is designed exclusively for protective extra-low voltage (PELV)
operation according to EN 60204-1. Only PELV according to the defined standard may be
used for supply purposes.
The following applies to the network (PROFINET) and the I/O devices used in it:
Only use power supply units that meet EN 61204 with safe isolation and PELV according
to EN 50178/VDE 0160 (PELV). This prevents short circuits between primary and
secondary sides.

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.

8291_en_03 PHOENIX CONTACT 55


RFC 460R PN 3TX

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

56 PHOENIX CONTACT 8291_en_03


Mounting, removal, electrical installation, and replacement

4 Mounting, removal, electrical installation, and


replacement

4.1 General

Only qualified personnel should pack and unpack the RFC 460R PN 3TX while observing
the following ESD regulations.

WARNING: Loss of electrical safety when using unsuitable power supplies


The RFC 460R PN 3TX is designed exclusively for protective extra-low voltage (PELV)
operation according to EN 60204-1. Only PELV according to the defined standard may be
used for supply purposes.
The following applies to the network and the I/O devices used in it:
Only use power supply units that meet EN 61204 with safe isolation and PELV according
to EN 50178/VDE 0160 (PELV). This prevents short circuits between primary and
secondary sides.

NOTE: Electrostatic discharge


The device contains components that can be damaged or destroyed by electrostatic
discharge. When handling the device, observe the necessary safety precautions against
electrostatic discharge (ESD) according to EN 61340-5-1.

WARNING: Unintentional machine startup


Do not mount or remove the RFC 460R PN 3TX while the power is connected.
Before mounting or removing the device, disconnect the power to the device and ensure
that it cannot be switched on again.
Make sure the entire system is reassembled before switching the power back on.
Observe the diagnostic indicators and any diagnostic messages.
The system may only be started provided neither the device nor the system poses a
hazard.

Observe the PROFINET Installation Guideline for Cabling and Assembly


Observe the PROFINET Installation Guideline for Cabling and Assembly when mounting
and installing the RFC 460R PN 3TX. The guideline can be downloaded at
www.profinet.com or you can contact your nearest Phoenix Contact representative
regarding this document.

Only mount the device on DIN rails according to DIN EN 60715.


Degree of protection of the device when mounted: IP20.
To ensure correct operation, the device mounted on a DIN rail must be installed in housing
or a control cabinet with a minimum of IP54 protection or higher.

8291_en_03 PHOENIX CONTACT 57


RFC 460R PN 3TX

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.

58 PHOENIX CONTACT 8291_en_03


Mounting, removal, electrical installation, and replacement

4.2 Mounting the RFC 460R PN 3TX

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

Figure 4-1 Mounting the RFC 460R PN 3TX

• 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.

8291_en_03 PHOENIX CONTACT 59


RFC 460R PN 3TX

4.2.1 Mounting the fan

• 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

4.3 Removing the RFC 460R PN 3TX

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.

4.4 Inserting/removing the parameterization memory

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.

The parameterization memory is recognized during initialization of the Remote Field


Controller. Ensure that the parameterization memory has been inserted before switching
on the Remote Field Controller to enable the device to use it.

NOTE: Parameterization memory (CF card) – formatting note


The CF card is preformatted and designed for use with Phoenix Contact devices. Ensure
that the CF card is not reformatted outside the RFC 460R PN 3TX.

60 PHOENIX CONTACT 8291_en_03


Mounting, removal, electrical installation, and replacement

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).

NOTE: Potential damage to the device


As the parameterization memory is inserted, ensure that the card is located in the guide
rails on both sides of the card holder. To prevent damage to the device, make sure that
the parameterization memory is properly aligned and never force it into the slot.

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.

Removing the • Press the ejector.


parameterization memory
The parameterization memory is ejected from the slot. It can then be removed (C).

A B C
Project
board
Controller
Plant
CF 64M ATA-PC
Order No. 2737054
64MB
CE

Figure 4-3 A: inserting the parameterization memory


B: moving the retaining clip
C: removing the parameterization memory

Replacing the Remove the old parameterization memory according to the method described above and
parameterization memory insert the new parameterization memory.

8291_en_03 PHOENIX CONTACT 61


RFC 460R PN 3TX

4.5 Connecting the interfaces

4.5.1 Connecting the synchronization connection to the SYNC


interface (fiber optics)

The fiber optic synchronization connection is a direct point-to-point connection between


both Remote Field Controllers of the redundant control system.

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.

• 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.

Figure 4-4 Inserting the SFP module

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.

62 PHOENIX CONTACT 8291_en_03


Mounting, removal, electrical installation, and replacement

Figure 4-5 Inserting the fiber optic plug into the SFP module

4.5.2 Connecting the Ethernet network

• 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.

8291_en_03 PHOENIX CONTACT 63


RFC 460R PN 3TX

4.6 Connecting the supply voltage

The RFC 460R PN 3TX is operated using a 24 V DC voltage.

WARNING: Loss of electrical safety when using unsuitable power supplies


The RFC 460R PN 3TX is designed exclusively for protective extra-low voltage (PELV)
operation according to EN 60204-1. Only PELV according to the defined standard may be
used for supply purposes.
The following applies to the network and the I/O devices used in it:
Only use power supply units that meet EN 61204 with safe isolation and PELV according
to EN 50178/VDE 0160 (PELV). This prevents short circuits between primary and
secondary sides.

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

Figure 4-7 Connecting the supply voltage

Please note that the Remote Field Controller requires some time to start up following
connection of the supply voltage.

64 PHOENIX CONTACT 8291_en_03


Mounting, removal, electrical installation, and replacement

4.7 Replacing the RFC 460R PN 3TX

NOTE: The following tasks must be carried out prior to mounting:


– Disconnect the supply voltage
– Ensure that the supply voltage cannot be switched on again by unauthorized persons

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.

WARNING: Unintentional machine startup


Do not replace the RFC 460R PN 3TX while the power is connected.
Do not remove the device until:
– The device has been disconnected from the power supply and it has been ensured
that it cannot be switched on again
– The COMBICON plug-in connector (supply voltage) has been disconnected
– The Ethernet cable plug(s) has/have been disconnected
– The fiber optic plug for the synchronization connection has been disconnected

1. Switch off the power supply to the Remote Field Controller.


2. Unplug the supply cable from the Remote Field Controller.

24
V
DC

Figure 4-8 Removing the supply cable

8291_en_03 PHOENIX CONTACT 65


RFC 460R PN 3TX

3. Remove the Ethernet plugs.


Push the locking mechanism of the RJ45 plug in the direction of the arrow (A) and
remove the plug from the socket (B).

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

+
-

Figure 4-9 Removing the Ethernet cable(s)

4. Remove the fiber optic plug for the synchronization connection.


Press the arresting latch (A) and pull out the plug (B).

B A
Figure 4-10 Removing the fiber optic plug

5. Remove the SFP module from the corresponding device slot.


Turn the release latch to the side (A) and pull the SFP module out of the slot (B).

B A

Figure 4-11 Removing the SFP module

Store the SFP module in a suitable place for reuse.

66 PHOENIX CONTACT 8291_en_03


Mounting, removal, electrical installation, and replacement

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

8. Take the new device out of its packaging.

If you wish to operate the new device with the fan module, proceed as follows:

8291_en_03 PHOENIX CONTACT 67


RFC 460R PN 3TX

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.

68 PHOENIX CONTACT 8291_en_03


Mounting, removal, electrical installation, and replacement

13. Insert the Ethernet plugs in the corresponding RJ45 sockets.

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-16 Establishing the Ethernet connection

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.

Figure 4-17 Inserting the SFP module

8291_en_03 PHOENIX CONTACT 69


RFC 460R PN 3TX

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

16. Connect the power supply to the Remote Field Controller.

24
V
DC

24 V DC
GND
FE

Figure 4-19 Plugging in the power supply

70 PHOENIX CONTACT 8291_en_03


Startup

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

Step Relevant section and literature


Remove the devices from the packaging
Section “General” on page 57.
while observing the ESD regulations.
Mount the devices according to your Section “Mounting the RFC 460R PN 3TX”
application. on page 59.
Section “Inserting/removing the
Insert the parameterization memory.
parameterization memory” on page 60.
Connect the devices to an Ethernet network Section “Connecting the Ethernet network”
according to your application. on page 63.
Establish the synchronization connection Section “Connecting the synchronization
between the two RFC 460R PN 3TX connection to the SYNC interface (fiber
Remote Field Controllers. optics)” on page 62.
Notes on using PELV power supply units in
Connect the power supply. Section “Connecting the supply voltage” on
page 64.

Make sure that the PROFINET devices (PROFINET controller, PROFINET


devices, and Inline devices) used in your application have been mounted and
installed correctly before connecting the supply voltage.

Switch on the power supply to the device.

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.

8291_en_03 PHOENIX CONTACT 71


RFC 460R PN 3TX

Table 5-1 Steps for starting up the RFC 460R PN 3TX/redundant control system

Step Relevant section and literature


Specify the IP address settings for Ethernet Section “Specifying the IP addresses of the
interfaces LAN1 and LAN2 of the Remote Remote Field Controller defined as FIRST”
Field Controller defined as FIRST. on page 78.
Section “Applying the settings –
Restart the Remote Field Controller defined
synchronizing the redundant control
as FIRST.
system” on page 82.

The following steps must be performed in the PC Worx software.


To this end, make sure that there is an online connection between the
PC Worx software and the controller that controls the process (PRIMARY).

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.

72 PHOENIX CONTACT 8291_en_03


Startup

5.2 Preparing the Remote Field Controllers of the


redundant control system for operation

5.2.1 Specifying the redundancy type of the RFC 460R PN 3TX


Remote Field Controllers

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.

Defining the FIRST Proceed as follows:


redundancy type 1. Switch on the power supply for the redundant control system and boot both Remote
Field Controllers until the following status appears in both displays:

Figure 5-1 Remote Field Controller not synchronized (NSYN: No Sync)

• Switch to the REDUNDANCY submenu using the , , and keys.

Figure 5-2 REDUNDANCY submenu

8291_en_03 PHOENIX CONTACT 73


RFC 460R PN 3TX

• Switch to the SETTINGS submenu using the , , and keys.

Figure 5-3 REDUNDANCY submenu – settings

• Select the “TYPE” menu item using the key.

Figure 5-4 Redundancy type not defined

• 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-

ample in Figure 5-5: FIRST).

74 PHOENIX CONTACT 8291_en_03


Startup

Figure 5-5 Redundancy type FIRST set

• Confirm your entry by pressing the key.

The LCD displays the following message:

Figure 5-6 Redundancy type changed – FIRST

• If you do not want to apply your settings, press the key instead of the key.

The LCD displays the following message:

Figure 5-7 No changes made

• Press the key to return to the main menu.

8291_en_03 PHOENIX CONTACT 75


RFC 460R PN 3TX

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.

Figure 5-8 SECOND redundancy type selected

• Confirm your entry by pressing the key.

The following menu appears:

Figure 5-9 Redundancy type changed – SECOND after restart

76 PHOENIX CONTACT 8291_en_03


Startup

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).

Figure 5-10 System menu – Remote Field Controller restart

After a successful restart, view the settings via the “REDUNDANCY –


LOCAL INFORMATION” submenu:

Figure 5-11 “REDUNDANCY – LOCAL INFORMATION” submenu – redundancy type:


SECOND

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.

8291_en_03 PHOENIX CONTACT 77


RFC 460R PN 3TX

5.2.2 Specifying the IP addresses of the Remote Field Controller


defined as FIRST

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.

IP settings for LAN1/LAN2 Ethernet 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.

• Press the key to switch to the system menu.

Figure 5-12 System menu

• In the system menu, use the , , and keys to select the “IP CFG LAN2”

menu item.

78 PHOENIX CONTACT 8291_en_03


Startup

The following menu appears:

Figure 5-13 System menu – IP settings – IP parameters for LAN2

• In the “IP CFG LAN2” submenu, use the , , and keys to select the “Edit

IP address (LAN2)” menu item.

The following menu appears:

Figure 5-14 System menu – Edit IP address (LAN2)

• 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

or decrease the value of the selected position.

• Confirm your entry by pressing the key.

8291_en_03 PHOENIX CONTACT 79


RFC 460R PN 3TX

The following message is displayed:

Figure 5-15 IP address will be changed after restart

If you have entered an invalid value while entering the above settings, this is indicated by
the following message:

Figure 5-16 System menu – invalid entry

• In this case, correct your settings as described above.

• 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 following menu appears with a suggested subnet mask:

Figure 5-17 System menu – IP settings – Edit subnetmask (LAN2)

• The required subnet mask in this example is “255.255.0.0”. If this is not present, use the

, , and keys to set it.

• Confirm your entry by pressing the key.

80 PHOENIX CONTACT 8291_en_03


Startup

The following message is displayed if you have changed the subnet mask (“255.255.0.0” in
the example):

Figure 5-18 System menu – subnet mask changed

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:

FIRST – LAN1 FIRST – LAN2

Figure 5-19 System menu – IP settings – settings applied following restart

The IP settings you have made are stored on the parameterization memory. The changes
take effect when the Remote Field Controller is restarted.

8291_en_03 PHOENIX CONTACT 81


RFC 460R PN 3TX

5.2.3 Applying the settings – synchronizing the redundant


control system

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).

Figure 5-20 System menu – Remote Field Controller restart

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.

82 PHOENIX CONTACT 8291_en_03


Startup

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.

LAN1 and LAN2: note IP addresses


Please note that for Ethernet interfaces LAN1 and LAN2 the Remote Field Controller
defined as SECOND by the redundant control system always has the IP address settings
of the FIRST increased by “+1” automatically: IP address SECOND = IP address FIRST
+ 1. Example:
– FIRST:
LAN1: 192.168.1.10/subnet mask: 255.255.255.0
LAN2: 172.16.1.2/subnet mask: 255.255.0.0
– SECOND:
LAN1: 192.168.1.11/subnet mask: 255.255.255.0
LAN2: 172.16.1.3/subnet mask: 255.255.0.0
Do not assign the IP addresses automatically occupied by the redundant control system
for other PROFINET devices. In addition, ensure that other devices in your network (PCs,
printers, etc.) do not use these IP addresses.

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.

PRIMARY (FIRST) – BSYN BACKUP (SECOND) – BSYN

Figure 5-21 Both Remote Field Controllers are in the “Basic Sync” state

8291_en_03 PHOENIX CONTACT 83


RFC 460R PN 3TX

84 PHOENIX CONTACT 8291_en_03


Integration of the RFC 460R PN 3TX in PC Worx

6 Integration of the RFC 460R PN 3TX in PC Worx


This section covers the following topics:
– Creating a new project in PC Worx
– Transferring the IP address settings of the Remote Field Controllers (FIRST/SECOND)
of the redundant control system to PC Worx
– Reading PROFINET devices that are available in the network
– Compiling the created project
– Downloading the compiled project to the PRIMARY Remote Field Controller
– Performing a cold restart for the PRIMARY Remote Field Controller after successfully
downloading the project
– Synchronizing the redundant control system

For the chronological sequence of the steps carried out, please refer to this section.

Interactions between PC Worx and the redundant control system


For all interactions with the redundant control system, PC Worx only accesses the
PRIMARY Remote Field Controller that controls the process, regardless of whether it is
the FIRST or SECOND Remote Field Controller. The only exception is for IP address
settings if these are made in the advanced settings in the “Device Details” window. Please
observe the notes in Section “Device Details, Extended Settings – Network Settings” on
page 109.

This section assumes the following:


– The PC Worx software has been installed on your PC according to the quick start guide.
– The connected PROFINET devices have been installed according to the device-
specific user documentation.
– The redundant control system is operating without errors and an online connection
exists to both Remote Field Controllers.

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.

8291_en_03 PHOENIX CONTACT 85


RFC 460R PN 3TX

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).

6.1 Creating and saving a new project

Creating a new project in Select the “New Project...” command from the “File” menu to create a new project using a
PC Worx template.

Figure 6-1 “File, New Project...” command

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.

86 PHOENIX CONTACT 8291_en_03


Integration of the RFC 460R PN 3TX in PC Worx

Figure 6-2 Project templates

• Confirm your selection with “OK”.

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.

Figure 6-3 “Save/Zip project as” dialog box

8291_en_03 PHOENIX CONTACT 87


RFC 460R PN 3TX

6.2 Specifying project information

• Switch to the bus configuration workspace.


After creating a new project, the project information is displayed in the bus configuration
workspace.

Figure 6-4 Project information after creating a new 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.

• Adapt the project information to your project.

88 PHOENIX CONTACT 8291_en_03


Integration of the RFC 460R PN 3TX in PC Worx

The following settings are used for the IP address area in the example project:

Figure 6-5 Project information in the example project

6.3 IP addresses of the Remote Field Controller


(FIRST)

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

8291_en_03 PHOENIX CONTACT 89


RFC 460R PN 3TX

Figure 6-6 Device Details – FIRST IP settings

6.4 Communication paths for the RFC 460R PN 3TX

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.

• Switch to the bus configuration workspace.


• Select the “RFC 460R PN 3TX” controller in the “Bus Structure” window.
• In the “Device Details” window, switch to the “Communication” tab.
Two different communication paths are displayed for the RFC 460R PN 3TX
(see Figure 6-7 on page 91: FIRST-LAN1 and FIRST-LAN2).

90 PHOENIX CONTACT 8291_en_03


Integration of the RFC 460R PN 3TX in PC Worx

Figure 6-7 “Device Details” window: selecting the communication path

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.

8291_en_03 PHOENIX CONTACT 91


RFC 460R PN 3TX

6.5 Reading the PROFINET network/assigning


PROFINET device names

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.

6.5.1 Reading the PROFINET network

• In the context menu of the PROFINET node, select the “Read PROFINET...” command
(see Figure 6-8).

Figure 6-8 PROFINET node: Read PROFINET

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.

92 PHOENIX CONTACT 8291_en_03


Integration of the RFC 460R PN 3TX in PC Worx

• Click on a device to select it (IL PN BK DI8 DO4 2TX in Figure 6-9).

Figure 6-9 “Read PROFINET” dialog box

• Click “Insert”.
• In the “Select PROFINET device description” dialog box that opens, select the
corresponding device description. Make sure the version is correct.

Figure 6-10 “Select PROFINET device description” dialog box

• Confirm your selection with “OK”.

8291_en_03 PHOENIX CONTACT 93


RFC 460R PN 3TX

6.5.2 Naming PROFINET devices

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”.

Figure 6-11 “Insert PROFINET Device” dialog box

• 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.

94 PHOENIX CONTACT 8291_en_03


Integration of the RFC 460R PN 3TX in PC Worx

6.5.3 PROFINET device name and IP address

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.

Figure 6-12 PROFINET device name and IP address

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.

8291_en_03 PHOENIX CONTACT 95


RFC 460R PN 3TX

6.6 Compiling and sending a project to the Remote


Field Controller

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.

Figure 6-13 “Rebuild Project” in 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.

Figure 6-14 Project control dialog box: “Download”

96 PHOENIX CONTACT 8291_en_03


Integration of the RFC 460R PN 3TX in PC Worx

6.7 Performing a cold restart for the Remote Field


Controller

• Start the PRIMARY Remote Field Controller by clicking on “Cold”.

Figure 6-15 Project control dialog box: “Cold”

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).

PRIMARY (FIRST) – SYNC BACKUP (SECOND) – HSBY

Figure 6-16 Redundant control system in HotStandBy

If an installation error prevents the system from starting up, a corresponding error message
appears in the LCD and in PC Worx.

8291_en_03 PHOENIX CONTACT 97


RFC 460R PN 3TX

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

Figure 6-17 Information on PROFINET (PROFINET controller SECOND)

Key:

A “PROFINET IO controller” – PROFINET device name (SECOND)


submenu: – IP address of the Ethernet interface used
– Application relations
B “AR list” submenu: List of PROFINET devices/application relations
configured in the project

98 PHOENIX CONTACT 8291_en_03


Errors, diagnostic messages, and removal

7 Errors, diagnostic messages, and removal


This section uses the example of the redundancy status to demonstrate how diagnosed
errors are displayed in the RFC 460R PN 3TX display. It also lists possible error codes/error
messages, their meanings, and how to remedy them.

7.1 Display of errors

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).

Figure 7-1 Redundancy status: display of error code

Figure 7-2 Redundancy status, diagnostics: display of error message

• If necessary, use the , , and keys to view the entire error text.

8291_en_03 PHOENIX CONTACT 99


RFC 460R PN 3TX

In the Diag+ software, the “Redundancy information” view displays the diagnosed errors
(see Figure 7-3).

Figure 7-3 Diag+, redundancy information: display of error information

100 PHOENIX CONTACT 8291_en_03


Errors, diagnostic messages, and removal

7.2 Possible errors

Table 7-1 Possible errors for the RFC 460R PN 3TX

Error Error message Meaning Remedy


code
0x002F Multiple ARP replies for LAN1 Check the IP addresses.
Multiple IP addresses are
Change the IP addresses if
0x0032 Multiple ARP replies for LAN2 available.
required.
0x0042 BACKUP: Wait for get ROLE timeout
0x0045 BACKUP: Wait for get ROLE request error
0x0046 No get info response received
0x0047 BACKUP: Wait for get info timeout
An error occurred during Acknowledge the error to restart
0x0048 BACKUP: Wait for get info request error Basic Sync redundancy status. Basic Sync redundancy status.
0x004D No change ROLE response received
0x004E BACKUP: Wait for change ROLE timeout
BACKUP: Wait for change ROLE request
0x004F
error
Check the redundancy type
The redundancy type settings
0x0065 Multiple peers conflict settings. Change the
are not unique.
redundancy type if required.
0x0067 Init remoting deamon failed
Internal initialization error Acknowledge the error.
0x006B Register runtime synchronization failed
Check whether the mode
The project could not be started selector switch is in the STOP
Start project on BACKUP failed
0x006C on the BACKUP Remote Field position. If so, set the mode
(KeySwitch in STOP position?)
Controller. selector switch to the
RUN/PROG position.
0x006E Init sync manager failed Internal synchronization error Acknowledge the error.
Check the synchronization
The synchronization connection connection. Replace the
0x0071 Sync link timeout
is interrupted. synchronization connection if
required.
Redundancy roles could not be
0x0072 Trigger switch-over failed
switched over.
Reconfiguring the Redundancy Interface
0x0073 Acknowledge the error.
failed
Internal initialization error
Reconfiguring the runtime synchronization
0x0074
failed

8291_en_03 PHOENIX CONTACT 101


RFC 460R PN 3TX

102 PHOENIX CONTACT 8291_en_03


Updating the firmware, repair, replacing the fan module

8 Updating the firmware, repair, replacing the fan module

8.1 Updating the device firmware

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.

NOTE: Potential device malfunction


Do not interrupt the RFC 460R PN 3TX supply voltage during the firmware update
process. Interruption of the supply voltage can result in a malfunction on the
RFC 460R PN 3TX. In this case, the device can no longer be used.

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.

8291_en_03 PHOENIX CONTACT 103


RFC 460R PN 3TX

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.

• If the required firmware file (Setup_Firmware_.......zip) is not available, download it from


the device download area to the hard disk of your PC.
• Extract the file. If necessary, execute the “exe” file and follow the instructions.
• Copy the extracted firmware container file (2700784_Revision.ctn) from the hard disk
of your PC to the main directory of the memory stick.
• Insert the memory stick in one of the two USB sockets.
Do not continue with the next step until the LED on the memory stick is permanently on.
• Call the “FW-UPDATE” menu item in the system menu using the operating keys (A in
Figure 8-1).

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.

• Start the firmware update using the key.

A B

Figure 8-1 Updating the firmware

The firmware update is complete after the Remote Field Controller has successfully
performed an automatic restart.

104 PHOENIX CONTACT 8291_en_03


Updating the firmware, repair, replacing the fan module

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.

8.3 Replacing the fan module

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

8291_en_03 PHOENIX CONTACT 105


RFC 460R PN 3TX

106 PHOENIX CONTACT 8291_en_03


Additional settings/redundancy features in PC Worx

9 Additional settings/redundancy features in PC Worx

9.1 Setting the realtime clock

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).

Figure 9-1 Selecting the interface/communication path

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.

8291_en_03 PHOENIX CONTACT 107


RFC 460R PN 3TX

9.2 Setting task properties

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.

Figure 9-2 Standard task: DEFAULT or CYCLIC type

For additional information on task properties, please refer to the quick start guide or the
online help for PC Worx.

108 PHOENIX CONTACT 8291_en_03


Additional settings/redundancy features in PC Worx

9.3 Device Details, Extended Settings – Network


Settings

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

Figure 9-3 Network Settings: FIRST-LAN2 (A), SECOND-LAN2 (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.

8291_en_03 PHOENIX CONTACT 109


RFC 460R PN 3TX

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.

Regardless of which network settings are displayed (FIRST-LAN1, ... SECOND-LAN2),


both the FIRST and the SECOND Remote Field Controllers can be reset using the “Reset
Control System” button after entering the corresponding IP address.
If the “Reset Control System” button is activated during system operation, for example, for
diagnostic purposes, make sure that the correct IP address is set for the Remote Field
Controller to be reset in the dialog box for setting the communication path.

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).

110 PHOENIX CONTACT 8291_en_03


Additional settings/redundancy features in PC Worx

9.4 Redundant variables

Variables used for redundancy operation must be marked as redundant variables in


PC Worx. The “Redundant Variable” column in the variable worksheet in PC Worx is used
for this. Select the corresponding checkbox to mark redundant variables.

Limited amount of data that can be synchronized


Please note that the amount of data that can be synchronized for redundancy purposes
is limited to a maximum of 62 kbytes. Make sure that this limit is not exceeded by the
redundant variables (see highlighted “Redundant Variable” in Figure 9-4).
As of AUTOMATIONWORX Software Suite 2016 Version 1.83, the amount of data used
is indicated in the PC Worx message window on the “Infos” tab.

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.

• Switch to the IEC programming workspace.


• Create the required variables for your application. Proceed as described in the online
help or quick start guide for PC Worx.
Check/set the variable marking as a redundant variable in the “Global Variables” worksheet
(see Figure 9-4) or in the “MainV” worksheet (see Figure 9-5 on page 112).

Figure 9-4 Redundant variables: “Global Variables” worksheet

8291_en_03 PHOENIX CONTACT 111


RFC 460R PN 3TX

Figure 9-5 Redundant variables: “MainV” worksheet

112 PHOENIX CONTACT 8291_en_03


Additional settings/redundancy features in PC Worx

9.5 Switching redundancy roles

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).

Figure 9-6 Diag+: “Redundancy information – Swap redundancy role”

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.

8291_en_03 PHOENIX CONTACT 113


RFC 460R PN 3TX

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.

Regardless of how the switch-over of redundancy roles is implemented, PC Worx displays


the switch-over using the following dialog box if an online connection exists between the
software and the redundant control system.

Figure 9-7 Redundancy role switched over

CPU_Set_Value_Request

Syntax: CPU_Set_Value_Request 02CBhex


Word 1 Code
Word 2 Parameter_Count
Word 3 Variable_Count
Word 4 Variable_ID
Word 5 Value

15 .............................. 8 7 .............................. 0

Key

Code: 02CBhex Command code of the request


Parameter_Count: 0003hex Number of subsequent words. The value depends
on the length of the system parameter.
In the example: 3 words
Variable_Count: 0001hex Number of system parameters to which new values
are assigned.
Variable_ID: 0195hex ID of the system parameter to which new values are
to be assigned.
Value 0001hex New value of the system parameter.

114 PHOENIX CONTACT 8291_en_03


Additional settings/redundancy features in PC Worx

CPU_Set_Value_Confirmation

Syntax: CPU_Set_Value_Confirmation 82CBhex


Positive message
Word 1 Code
Word 2 Parameter_Count
Word 3 Result
Negative message
Word 1 Code
Word 2 Parameter_Count
Word 3 Result
Word 4 Add_Error_Info

15 ...................................................................... 0

Key

Code: 82CBhex Message code of the confirmation


Parameter_Count: Number of subsequent words.
0001hex One parameter word with a positive message
0002hex Two parameter words with a negative message
Result Result of the service processing
0000hex Indicates a positive message
The Remote Field Controller processed the service
successfully.
xxxxhex Indicates a negative message
The Remote Field Controller could not process the
service successfully. The “Result” parameter
indicates why the service could not be processed.
Add_Error_Info Additional information regarding the error cause
(e.g., invalid parameter)

8291_en_03 PHOENIX CONTACT 115


RFC 460R PN 3TX

9.6 Download changes

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.

When downloading changes to the Remote Field Controllers, it is possible to specify


whether the system should ensure the realtime behavior of the PLC before starting the
download process. By default, realtime violations are not permitted.

Figure 9-8 Ensuring realtime

If the “Always allow real-time violations...” checkbox is deactivated in the “Download


Options” dialog box (recommended default setting), the system attempts to execute the
“Download Changes” function without violating the realtime conditions of the tasks
executed on the PLC.
If the modifications cannot be sent, for example, because the amount of data to be copied
is too large, an error message is output. In this case, activate the “Always allow real-time
violations...” option so that all modifications can be executed. (In this case, please refer to
the background information provided in the online help, realtime behavior section.)

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.

116 PHOENIX CONTACT 8291_en_03


Additional settings/redundancy features in PC Worx

9.7 Parameterization memory and Internet Explorer

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.

• Switch to the bus configuration workspace in PC Worx.


• Select the controller (“RFC 460R PN 3TX” in the example) in the “Bus Structure”
window.
• Select the “Extended Settings” tab in the “Device Details” window.
• Open Internet Explorer from this window by clicking on the “Open FTP Folder on
Device” button.

Figure 9-9 Extended Settings: Open FTP Folder on Device

8291_en_03 PHOENIX CONTACT 117


RFC 460R PN 3TX

The file structure, which is stored on the parameterization memory, is displayed in the
Internet Explorer window.

Figure 9-10 File structure on the parameterization memory

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.

9.7.1 Internet Explorer FTP function

• Activate this setting in Internet Explorer under “Tools, Internet Options, Advanced”.

Figure 9-11 Internet Options: Enable folder view for FTP sites

118 PHOENIX CONTACT 8291_en_03


Additional settings/redundancy features in PC Worx

9.7.2 Activating/deactivating the FTP server

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

Figure 9-12 Deactivating the FTP server

9.7.3 Activating/deactivating the HTTP 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

8291_en_03 PHOENIX CONTACT 119


RFC 460R PN 3TX

9.8 Substitute value behavior for PROFINET devices

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).

Figure 9-13 PROFINET device – “Substitute value behavior of inputs”

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.

120 PHOENIX CONTACT 8291_en_03


Additional settings/redundancy features in PC Worx

9.9 Function blocks for handling files in the


parameterization memory

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.

All file operations are subject to the following restrictions:


No directory hierarchies are supported. All file operations only affect the root directory of
the parameterization memory.

The function blocks are valid for:


Order designation From hardware version From firmware version
RFC 460R PN 3TX 00 5.00

Table 9-1 Overview of function blocks


Function block Short description
FILE_OPEN Opens a file with a specific name
FILE_CLOSE Closes a file with a specific handle
FILE_READ Reads from a file with a specific handle
FILE_WRITE Writes to a file with a specific handle
FILE_REMOVE Deletes a file with a specific name
FILE_TELL Determines the current position of the file pointer in a file
FILE_SEEK Moves the current file pointer to a new position
FILE_NOTIFY Displays files that have recently been created, deleted or
modified

The function blocks for handling files in the parameterization memory are described in the
PC Worx online help.

8291_en_03 PHOENIX CONTACT 121


RFC 460R PN 3TX

9.10 Function blocks for Ethernet communication

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

Table 9-2 Overview of function blocks

Function block Short description


IP_CONNECT Establishes a connection between two communication partners
IP_USEND Transmits data to a communication partner
IP_URCV Receives data from a communication partner

The communication blocks are described in the PC Worx online help.


The extensions for the TCP/IP and UDP/IP function blocks are described in the
“AH EN FB TCP/IP COMMUNICATION” application note.

122 PHOENIX CONTACT 8291_en_03


System variables

10 System variables

10.1 IEC 61131 runtime system

There is a separate group of system variables for the IEC 61131 runtime system.

Table 10-1 System variables of the IEC 61131 runtime system

System variable Type Meaning


PLCMODE_ON BOOL PLC status ON: the runtime system on the Remote Field
Controller is ready to operate.
PLCMODE_LOADING BOOL PLC status LOADING: the application program is loading.
PLCMODE_RUN BOOL PLC status RUN: the application program is running.
PLCMODE_STOP BOOL PLC status STOP: the application program is currently not
running.
PLCMODE_HALT BOOL PLC status HALT: the application program was stopped at an
unspecified point.
PLCDEBUG_BPSET BOOL Breakpoint set: at least one breakpoint has been set in the
application program.
PLCDEBUG_FORCE BOOL Variable(s) forced: at least one variable is being continuously
overwritten (forced) by PC Worx.
PLCDEBUG_POWERFLOW BOOL Powerflow ON: in “Powerflow” mode, you can see which parts of
your application program are being processed. This bit indicates
whether “Powerflow” mode is active.
PLC_TICKS_PER_SEC INT System ticks per second: this variable shows how many pulses
the system clock of the runtime system delivers per second.
PLC_SYS_TICK_CNT DINT Number of system ticks: this variable shows the total number of
pulses delivered by the system clock since the last startup.
PLC_TASK_AVAILABLE INT Number of available PLC tasks.
PLC_SYSTASK_AVAILABLE INT Number of available system tasks.
PLC_MAX_ERRORS DINT Maximum number of errors
PLC_ERRORS DINT Number of errors
PLC_TASK_DEFINED INT Number of PLC tasks used.
PLC_TASK_1 Extended_ Information on task 1
Task_Info
: : :
PLC_TASK_16 Extended_ Information on task 16
Task_Info
LICENSE DWORD License information

8291_en_03 PHOENIX CONTACT 123


RFC 460R PN 3TX

10.2 Control processor (CPU)

The system variables listed below show the states of the diagnostic status register on the
control processor (CPU) of the Remote Field Controller.

Table 10-2 System variables of the control processor

System variable Type Meaning


COP_DIAG_STATUS_REG_RT_ERR BOOL A runtime error (out of realtime) has occurred on the control
processor.
COP_DIAG_STATUS_REG_FAT_ERR BOOL A fatal error has occurred on the control processor. Division by
zero, for example, leads to a fatal error.
COP_DIAG_STATUS_REG_WARN BOOL A warning has been issued on the control processor.
COP_DIAG_STATUS_REG_PON BOOL Power ON (COP): the control processor is ready to operate.
COP_DIAG_STATUS_REG_FC_RUN BOOL Runtime system RUN
COP_DIAG_STATUS_REG_FC_STOP BOOL Runtime system STOP
COP_DIAG_STATUS_REG_FC_HALT BOOL Runtime system HALT
COP_DIAG_STATUS_REG_FC_LDG BOOL Runtime system LOADING
COP_DIAG_STATUS_REG_FC_DBG BOOL Runtime system DEBUG
COP_DIAG_STATUS_REG_FC_RDO BOOL Runtime system READONLY
COP_DIAG_PARAM_REG WORD Diagnostic parameter register of the control processor
COP_DIAG_PARAM_2_REG WORD Extended diagnostic parameter register of the control
processor

The system variable below shows status information regarding the control processor of the
Remote Field Controller.

Table 10-3 System variable of the control processor

System variable Type Meaning


COP_CPU_LOAD_WARNING BOOL The control processor is reaching the limits of its capacity.

124 PHOENIX CONTACT 8291_en_03


System variables

10.3 PROFINET system variables

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.

Table 10-4 PROFINET system variables (PROFINET controller function)

System variable Type Meaning


PNIO_FORCE_FAILSAFE BOOL All PROFINET devices are prompted to set/assume their
configured substitute values.
PNIO_CONFIG_STATUS BOOL Current configuration status of the context manager
PNIO_CONFIG_STATUS_READY BOOL Context manager active
PNIO_CONFIG_STATUS_ACTIVE BOOL Communication started
The PROFINET controller configuration has been applied
and the PROFINET controller is started. Connection
establishment is active.
PNIO_CONFIG_STATUS_CFG_FAULT BOOL Configuration error
The PROFINET controller configuration has not been applied
due to a serious error and the PROFINET controller is not
started. Please contact Phoenix Contact.
PNIO_SYSTEM_BF BOOL No connection to a configured PROFINET device
An error has occurred in the PROFINET network, i.e., a
connection could not be established to at least one
configured device. This value is not set if the “Control BF”
parameter is set to FALSE for a device. This device has
therefore been excluded from connection monitoring.
PNIO_SYSTEM_SF BOOL Diagnostic alarm on a configured PROFINET device
At least one PROFINET device is indicating a system error
(diagnostic alarm or maintenance alarm). The error priority
can be determined from the “PNIO_DIAG_AVAILABLE”,
“PNIO_MAINTENANCE_DEMANDED”, and
“PNIO_MAINTENANCE_REQUIRED” variables.
PNIO_DIAG_AVAILABLE BOOL Diagnostics available
At least one PROFINET device is indicating a diagnostic
alarm for an active connection. The corresponding device(s)
can be identified using the RALRM diagnostic block or by
requesting the diagnostic status byte of each
PN_DA_NO_DIAG device.
The application must decide, for example, whether outputs of
the other PROFINET devices in the network may continue to
be operated.

8291_en_03 PHOENIX CONTACT 125


RFC 460R PN 3TX

Table 10-4 PROFINET system variables (PROFINET controller function)

System variable Type Meaning


PNIO_MAINTENANCE_REQUIRED BOOL Maintenance required – maintenance requirement
At least one PROFINET device is indicating the
“maintenance requirement” alarm (low-priority maintenance
alarm) for the active connection. The device can be identified
using the RALRM diagnostic block.
PNIO_MAINTENANCE_DEMANDED BOOL Maintenance demanded – maintenance demand
At least one PROFINET device is indicating the
“maintenance demand” alarm (high-priority maintenance
alarm) for the active connection. The device can be identified
using the RALRM diagnostic block.

10.4 System time

Table 10-5 System variables of the system time

System variable Type Meaning


RTC_HOURS INT System time (hours)
RTC_MINUTES INT System time (minutes)
RTC_SECONDS INT System time (seconds)
RTC_DAY INT System time (day)
RTC_MONTH INT System time (month)
RTC_YEAR INT System time (year)

10.5 Ethernet

Table 10-6 System variables of the FTP, HTTP, and SNTP server

System variable Type Meaning


ETH_SRV_FTP_ACTIVE BOOL The FTP Ethernet service has been activated.
ETH_SRV_HTTP_ACTIVE BOOL The HTTP Ethernet service has been activated.
ETH_SRV_SNTP_ACTIVE BOOL The SNTP Ethernet service has been activated.

126 PHOENIX CONTACT 8291_en_03


System variables

10.6 Remote Field Controller

Table 10-7 System variables of the Remote Field Controller

System variable Type Meaning


TEMPERATURE BOOL Temperature of the control processor (CPU) of the Remote
Field Controller in Celsius.
TEMPERATURE_WARNING BOOL Temperature warning; the temperature of the control processor
(CPU) of the Remote Field Controller is at least 75°C.
TEMPERATURE_ERR BOOL Temperature error; the temperature of the control processor
(CPU) of the Remote Field Controller is at least 85°C.
FAN_FAIL BOOL Fan failure
FLASHCARD_PRESENT BOOL CompactFlash card from Phoenix Contact inserted that is
intended for use with the RFC 460R PN 3TX.
KEY_SWITCH_RESET BOOL Mode selector switch in the MRESET position.
KEY_SWITCH_STOP BOOL Mode selector switch in the STOP position.
KEY_SWITCH_RUN_PROG BOOL Mode selector switch in the RUN/PROG position.
LAN_PORT1_1_LINK BOOL The LAN 1.1 Ethernet interface is connected to another network
device.
LAN_PORT1_1_100MBIT BOOL The transmission speed of the LAN 1.1 Ethernet interface is 100
Mbps.
LAN_PORT1_1_FULL_DUPLEX BOOL A full duplex connection exists at the LAN 1.1 Ethernet
interface.
LAN_PORT1_2_LINK BOOL The LAN 1.2 Ethernet interface is connected to another network
device.
LAN_PORT1_2_100MBIT BOOL The transmission speed of the LAN 1.2 Ethernet interface is 100
Mbps.
LAN_PORT1_2_FULL_DUPLEX BOOL A full duplex connection exists at the LAN 1.2 Ethernet
interface.
LAN_PORT2_LINK BOOL The LAN 2 Ethernet interface is connected to another network
device.
LAN_PORT2_100MBIT BOOL The transmission speed of the LAN 2 Ethernet interface is 100
Mbps.
LAN_PORT2_FULL_DUPLEX BOOL A full duplex connection exists at the LAN 2 Ethernet interface.

8291_en_03 PHOENIX CONTACT 127


RFC 460R PN 3TX

10.7 Redundancy-specific system variables of the


Remote Field Controller

Table 10-8 Redundancy-specific variables of the Remote Field Controller

System variable Type Meaning


REDUNDANCY_OPC_STRUCT Redundancy_ OPC structure for redundancy; the OPC server
OPC_Struct accesses this structure.
RDNCY_IS_FIRST BOOL Redundancy type of the Remote Field Controller:
FIRST
RDNCY_IS_SECOND BOOL Redundancy type of the Remote Field Controller:
SECOND
RDNCY_IS_PRIMARY BOOL Redundancy role of the Remote Field Controller:
PRIMARY
RDNCY_IS_BACKUP BOOL Redundancy role of the Remote Field Controller:
BACKUP
RDNCY_BASICSYNC_OK BOOL The redundant control system is in the Basic Sync
state.
RDNCY_FULLSYNC_OK BOOL The redundant control system is in the FollowUp Sync
state.
RDNCY_HSBY BOOL The redundant control system is in the HotStandBy
state.
RDNCY_ERROR WORD Error code of the last diagnosed error in the redundant
control system; for error codes, seeSection “Possible
errors” on page 101.
RDNCY_NUMBER_OF_SWITCH_OVER INT Number of redundancy role switch-overs since the last
system start
RDNCY_LAST_SWITCH_OVER_REASON INT Cause of last redundancy role switch-over
RDNCY_SYNC_LINK_STATE INT Status of fiber optic synchronization connection
– 1 = OK
– 2 = Error
RDNCY_CURRENT_SYNC_PORT INT Interface that is used for synchronization.
– 1 = LAN 2
– 2 = SYNC interface
REMOTE_LICENSE DWORD License information
REMOTE_DIAG_STATUS_REG_RT_ERR BOOL A runtime error (out of realtime) has occurred on the
control processor.
REMOTE_DIAG_STATUS_REG_FAT_ERR BOOL A fatal error has occurred on the control processor.
Division by zero, for example, leads to a fatal error.
REMOTE_DIAG_STATUS_REG_WARN BOOL A warning has been issued on the control processor.
REMOTE_DIAG_STATUS_REG_PON BOOL Power ON (COP): the control processor is ready to
operate.
REMOTE_DIAG_STATUS_REG_FC_RUN BOOL Runtime system RUN

128 PHOENIX CONTACT 8291_en_03


System variables

Table 10-8 Redundancy-specific variables of the Remote Field Controller


System variable Type Meaning
REMOTE_DIAG_STATUS_REG_FC_STOP BOOL Runtime system STOP
REMOTE_DIAG_STATUS_REG_FC_HALT BOOL Runtime system HALT
REMOTE_DIAG_STATUS_REG_FC_LDG BOOL Runtime system LOADING
REMOTE_DIAG_STATUS_REG_FC_DBG BOOL Runtime system DEBUG
REMOTE_DIAG_STATUS_REG_FC_RDO BOOL Runtime system READONLY
REMOTE_DIAG_PARAM_REG WORD Diagnostic parameter register of the control processor
REMOTE_DIAG_PARAM_2_REG WORD Extended diagnostic parameter register of the control
processor
REMOTE_PN_FORCE_FAILSAFE BOOL All PROFINET devices are prompted to set/assume
their configured substitute values.
REMOTE_PN_CFG_STATUS BOOL Current configuration status of the context manager
REMOTE_PN_CF_STATUS_READY BOOL Context manager active
REMOTE_PN_CFG_STATUS_ACTIVE BOOL Communication started
The PROFINET controller configuration has been
applied and the PROFINET controller is started.
Connection establishment is active.
REMOTE_PN_CFG_STATUS_CFG_FLT BOOL Configuration error
The PROFINET controller configuration has not been
applied due to a serious error and the PROFINET
controller is not started.
Please contact Phoenix Contact.
REMOTE_PN_SYSTEM_BF BOOL No connection to a configured PROFINET device
An error has occurred in the PROFINET network, i.e., a
connection could not be established to at least one
configured device. This value is not set if the “Control
BF” parameter is set to FALSE for a device. This device
has therefore been excluded from connection
monitoring.
REMOTE_PN_SYSTEM_SF BOOL Diagnostic alarm on a configured PROFINET device
At least one PROFINET device is indicating a system
error (diagnostic alarm or maintenance alarm). The
error priority can be determined from the
“PNIO_DIAG_AVAILABLE”,
“PNIO_MAINTENANCE_DEMANDED”, and
“PNIO_MAINTENANCE_REQUIRED” variables.

8291_en_03 PHOENIX CONTACT 129


RFC 460R PN 3TX

Table 10-8 Redundancy-specific variables of the Remote Field Controller

System variable Type Meaning


REMOTE_PN_DIAG_AVAILABLE BOOL Diagnostics available
At least one PROFINET device is indicating a
diagnostic alarm for an active connection. The
corresponding device(s) can be identified using the
RALRM diagnostic block or by requesting the
diagnostic status byte of each PN_DA_NO_DIAG
device.
The application must decide, for example, whether
outputs of the other PROFINET devices in the network
may continue to be operated.
REMOTE_PN_MAINTENANCE_REQUIRED BOOL Maintenance required – maintenance requirement
At least one PROFINET device is indicating the
“maintenance requirement” alarm (low-priority
maintenance alarm) for the active connection. The
device can be identified using the RALRM diagnostic
block.
REMOTE_PN_MAINTENANCE_DEMANDED BOOL Maintenance demanded – maintenance demand
At least one PROFINET device is indicating the
“maintenance demand” alarm (high-priority
maintenance alarm) for the active connection. The
device can be identified using the RALRM diagnostic
block.
REMOTE_CPU_LOAD_WARNING BOOL The control processor is reaching the limits of its
capacity.
REMOTE_TEMPERATURE BOOL Temperature of the control processor (CPU) of the
Remote Field Controller in Celsius.
REMOTE_TEMPERATURE_WARNING BOOL Temperature warning; the temperature of the control
processor (CPU) of the Remote Field Controller is at
least 75°C.
REMOTE_TEMPERATURE_ERR BOOL Temperature error; the temperature of the control
processor (CPU) of the Remote Field Controller is at
least 85°C.
REMOTE_FAN_FAIL BOOL Fan failure
REMOTE_FLASHCARD_PRESENT BOOL CompactFlash card from Phoenix Contact inserted that
is intended for use with the RFC 460R PN 3TX.
REMOTE_KEY_SWITCH_RESET BOOL Mode selector switch in the MRESET position.
REMOTE_KEY_SWITCH_STOP BOOL Mode selector switch in the STOP position.
REMOTE_KEY_SWITCH_RUN_PROG BOOL Mode selector switch in the RUN/PROG position.
REMOTE_LAN_PORT1_1_LINK BOOL The LAN 1.1 Ethernet interface is connected to another
network device.
REMOTE_LAN_PORT1_1_100MBIT BOOL The transmission speed of the LAN 1.1 Ethernet
interface is 100 Mbps.
REMOTE_LAN_PORT1_1_FULL_DUPLEX BOOL A full duplex connection exists at the LAN 1.1 Ethernet
interface.

130 PHOENIX CONTACT 8291_en_03


System variables

Table 10-8 Redundancy-specific variables of the Remote Field Controller


System variable Type Meaning
REMOTE_LAN_PORT1_2_LINK BOOL The LAN 1.2 Ethernet interface is connected to another
network device.
REMOTE_LAN_PORT1_2_100MBIT BOOL The transmission speed of the LAN 1.2 Ethernet
interface is 100 Mbps.
REMOTE_LAN_PORT1_2_FULL_DUPLEX BOOL A full duplex connection exists at the LAN 1.2 Ethernet
interface.
REMOTE_LAN_PORT2_LINK BOOL The LAN 2 Ethernet interface is connected to another
network device.
REMOTE_LAN_PORT2_100MBIT BOOL The transmission speed of the LAN 2 Ethernet interface
is 100 Mbps.
REMOTE_LAN_PORT2_FULL_DUPLEX BOOL A full duplex connection exists at the LAN 2 Ethernet
interface.
REMOTE_REDUNDANCY_ERROR WORD Redundancy error of the redundant Remote Field
Controller

8291_en_03 PHOENIX CONTACT 131


RFC 460R PN 3TX

132 PHOENIX CONTACT 8291_en_03


Technical data and ordering data

11 Technical data and ordering data

11.1 Technical data

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.

Connection method CAT5 twisted pair cable


RJ45 socket
Functions – 10/100Base-T(X)
– Autocrossing
– Auto negotiation
– Auto polarity exchange
– Line monitoring

8291_en_03 PHOENIX CONTACT 133


RFC 460R PN 3TX

Diagnostic and status indicators


Ethernet LED: LINK (LNK, green), ACTIVITY (ACT, yellow)
Redundancy Diagnostic display, size: 8.9 cm (3.5" LCD)
PROFINET Diagnostic display, size: 8.9 cm (3.5" LCD)
IEC 61131 runtime system Diagnostic display, size: 8.9 cm (3.5" LCD)

IEC 61131 runtime system


Programming system PC Worx
Processor Intel® Celeron® M ULV 423, 800 MHz
Shortest cycle time (for cyclic task) tmin = 1 ms
Program memory 8 MB
Data memory 16 MB
Memory for retentive data 120 kB NVRAM
Number of control tasks 1
Parameterization memory ≥ 256 MB; CompactFlash card (CF)

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

134 PHOENIX CONTACT 8291_en_03


Technical data and ordering data

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

Buffer times of the integrated realtime clock (RTC)


Typical buffer time 250 days
Guaranteed buffer time 10 days

Conformance with EMC Directive 2014/30/EU


Noise immunity test according to EN 61000-6-2
Electrostatic discharge (ESD) EN 61000-4-2/ Criterion B
IEC 61000-4-2 6 kV contact discharge
8 kV air discharge
Electromagnetic fields EN 61000-4-3/ Criterion A
IEC 61000-4-3 Field strength: 10 V/m
Fast transients (burst) EN 61000-4-4/ Criterion B
IEC 61000-4-4 Supply lines: 2 kV
Signal/data lines: 2 kV
Surge test EN 61000-4-5/ Criterion B
IEC 61000-4-5 Signal/data lines: 1 kV
Supply lines: 0.5 kV
Conducted interference EN 61000-4-6/ Criterion A
IEC 61000-4-6 Test voltage: 10 V

Noise emission test according to EN 61000-6-4


Noise emission EN 55011 Class A

Approvals
For the latest approvals, please visit phoenixcontact.net/products.

8291_en_03 PHOENIX CONTACT 135


RFC 460R PN 3TX

11.2 Ordering data

11.2.1 Products

Description Type Order No. Pcs. / Pkt.


Remote Field Controller for Ethernet/PROFINET networks for creating a RFC 460R PN 3TX 2700784 1
redundant control system

11.2.2 Accessories

Description Type Order No. Pcs. / Pkt.


24 V DC/3.5 A DIN rail power supply unit, primary-switched, single-phase, QUINT-PS/ 1AC/24DC/ 3.5 2866747 1
with SFB technology for 6 times the nominal current; 3.5 A output current
24 V DC/5 A DIN rail power supply unit, primary-switched, single-phase, with QUINT-PS/1AC/24DC/5 2866750 1
SFB technology for 6 times the nominal current; 5 A output current
Active redundancy module with ACB technology and monitoring functions QUINT-ORING/24DC/2X10/1X20 2320173 1
DIN rail power supply unit, primary-switched, single-phase, output: 24 V TRIO-PS/ 1AC/24DC/ 2.5 2866268 1
DC/2.5 A
DIN rail power supply unit, primary-switched, single-phase, output: 24 V DC/5 TRIO-PS/ 1AC/24DC/ 5 2866310 1
A
Redundancy module with function monitoring, TRIO-DIODE/12-24DC/2X10/1X20 2866514 1
12 - 24 V DC, 2 x 10 A, 1 x 20 A
Small form factor plug-in module, a plug-in I/O module for fiber optics that is FL SFP SX 2891754 1
used in Gigabit Ethernet. Fiberglass module with a wavelength of 850 nm
(short).
Transmission length of up to 550 m
Small form factor plug-in module, a plug-in I/O module for fiber optics that is FL SFP LX 2891767 1
used in Gigabit Ethernet. Fiberglass module with a wavelength of 1300 nm
(long).
Transmission length of up to 30 km
Small form factor plug-in module, a plug-in I/O module for fiber optics that is FL SFP LH 2989912 1
used in Gigabit Ethernet. Fiberglass module with a wavelength of 1550 nm
(longhaul communication network).
Transmission length of up to 80 km
Assembled fiber optic cable, break-out cable, multi-mode fiberglass 50/125 FL MM PATCH 1,0 LC-LC 2989158 1
μm, plug: LC/LC, degree of protection: IP20, for installation in cable ducts or
control cabinets, length: 1 m
Assembled fiber optic cable, break-out cable, multi-mode fiberglass 50/125 FL MM PATCH 2,0 LC-LC 2989255 1
μm, plug: LC/LC, degree of protection: IP20, for installation in cable ducts or
control cabinets, length: 2 m
Assembled fiber optic cable, break-out cable, multi-mode fiberglass 50/125 FL MM PATCH 5,0 LC-LC 2901799 1
μm, plug: LC/LC, degree of protection: IP20, for installation in cable ducts or
control cabinets, length: 5 m
Parameterization memory, plug-in (CompactFlash card) CF FLASH 256MB 2988780 1
Parameterization memory, plug-in (CompactFlash card) CF FLASH 2GB 2701185 1
USB memory stick, IP20, USB 2.0 VS-04-MS-IP20 1402490 1
Fan module for Remote Field Controller RFC DUAL-FAN 2730239 1
Gray RJ45 plug set for linear cable FL PLUG RJ45 GR/2 2744856 2
Green RJ45 plug set for crossed cable FL PLUG RJ45 GN/2 2744571 2
Universal end clamp (fixed using a screw) E/NS 35 N 0800886 50

136 PHOENIX CONTACT 8291_en_03


Technical data and ordering data

Description Type Order No. Pcs. / Pkt.


Quick mounting end clamp (snapped on without tools) CLIPFIX 35 3022218 50
End clamp (fixed using screws) E/UK 1201442 50
Assembly tool for RJ45 plug FL CRIMPTOOL 2744869 1
Patch cable, CAT5, pre-assembled, 0.3 m long FL CAT PATCH 0,3 2832250 10
Patch cable, CAT5, pre-assembled, 0.5 m long FL CAT PATCH 0,5 2832263 10
Patch cable, CAT5, pre-assembled, 1.0 m long FL CAT PATCH 1,0 2832276 10
Patch cable, CAT5, pre-assembled, 1.5 m long FL CAT PATCH 1,5 2832221 10
Patch cable, CAT5, pre-assembled, 2.0 m long FL CAT PATCH 2,0 2832289 10
Patch cable, CAT5, pre-assembled, 3.0 m long FL CAT PATCH 3,0 2832292 10
Patch cable, CAT5, pre-assembled, 5.0 m long FL CAT PATCH 5,0 2832580 10
Patch cable, CAT5, pre-assembled, 7.5 m long FL CAT PATCH 7,5 2832616 10
Patch cable, CAT5, pre-assembled, 10.0 m long FL CAT PATCH 10 2832629 10

11.2.3 Software

Description Type Order No. Pcs. / Pkt.


PC Worx automation software See current catalog from Phoenix Contact (phoenixcontact.net/products)

11.2.4 Documentation

Description Type Order No. Pcs. / Pkt.


Quick start guide UM QS EN AXC 1050 PN – 1
Installing and starting up the AXC 1050 PN STARTERKIT STARTERKIT
User manual UM EN PROFINET SYS – 1
PROFINET basics
User manual UM EN PROFINET CTRL DEV – 1
PROFINET controller/device functions
Quick start guide UM QS EN PC WORX – 1
PC Worx

8291_en_03 PHOENIX CONTACT 137


RFC 460R PN 3TX

138 PHOENIX CONTACT 8291_en_03


A Appendix: interfaces of the RFC 460R PN 3TX
The following diagram shows the interfaces of the RFC 460R PN 3TX. The contact
assignment of the individual interfaces is described in the sections that follow. For notes on
connecting these interfaces, please refer to “Mounting, removal, electrical installation, and
replacement” on page 57.

4
Figure A-1 Interfaces of the RFC 460R PN 3TX

1 Ethernet ports LAN1.1/LAN1.2 and LAN2 (10/100Base-T(X); RJ45 sockets)


2 USB sockets (for updating the device firmware)
3 SYNC interface/slot for SFP modules (optional)
4 Supply voltage

A1 Ethernet interfaces LAN1.1/LAN1.2 and LAN2


(10/100Base-T)

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

Figure A-2 Contact assignment of the Ethernet port in RJ45 format

8291_en_03 PHOENIX CONTACT 139


RFC 460R PN 3TX

Table A-1 Contact assignment of the Ethernet ports in RJ45 format

PIN Assignment Meaning


1 TD+ Transmit data +
2 TD- Transmit data -
3 RD+ Receive data +
4 res. Reserved
5 res. Reserved
6 RD- Receive data -
7 res. Reserved
8 res. Reserved

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

Table A-2 Pin assignment of the USB interfaces


Pin Signal
1 VCC (+5 V DC)
2 Data-
3 Data+
4 GND

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.

140 PHOENIX CONTACT 8291_en_03


Connecting the supply voltage

A4 Connecting the supply voltage

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

Figure A-4 Connecting the supply voltage

8291_en_03 PHOENIX CONTACT 141


RFC 460R PN 3TX

142 PHOENIX CONTACT 8291_en_03


B Appendixes

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

8291_en_03 PHOENIX CONTACT 143


RFC 460R PN 3TX

Figure 3-17: System menu – maximum screensaver switch-on time .......................43


Figure 3-18: System menu – reset controller ...........................................................44
Figure 3-19: System menu – resetting the Remote Field Controller ........................44
Figure 3-20: CONTROL DETAILS submenu ...........................................................45
Figure 3-21: REDUNDANCY submenu ...................................................................46
Figure 3-22: REDUNDANCY submenu – ACTIONS ...............................................47
Figure 3-23: REDUNDANCY submenu – LOCAL INFORMATION .........................47
Figure 3-24: REDUNDANCY submenu – REMOTE INFORMATION ......................48
Figure 3-25: REDUNDANCY submenu – REDUNDANCY STATUS .......................48
Figure 3-26: REDUNDANCY submenu – SETTINGS .............................................49
Figure 3-27: REDUNDANCY submenu – DIAGNOSTICS .......................................49
Figure 3-28: PN-C DETAILS submenu – PROFINET IO Controller .........................50
Figure 3-29: Mode selector switch ..........................................................................51
Figure 3-30: Interfaces of the RFC 460R PN 3TX ...................................................52
Figure 3-31: Overload range with fall-back characteristic curve ..............................56
Figure 3-32: Overload range without fall-back characteristic curve .........................56

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

144 PHOENIX CONTACT 8291_en_03


List of figures

Figure 4-19: Plugging in the power supply ..............................................................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

8291_en_03 PHOENIX CONTACT 145


RFC 460R PN 3TX

Figure 6-11: “Insert PROFINET Device” dialog box ................................................94


Figure 6-12: PROFINET device name and IP address ............................................95
Figure 6-13: “Rebuild Project” in the “Build” menu ..................................................96
Figure 6-14: Project control dialog box: “Download” ...............................................96
Figure 6-15: Project control dialog box: “Cold” ........................................................97
Figure 6-16: Redundant control system in HotStandBy ..........................................97
Figure 6-17: Information on PROFINET (PROFINET controller SECOND) .............98

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

146 PHOENIX CONTACT 8291_en_03


List of figures

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

8291_en_03 PHOENIX CONTACT 147


RFC 460R PN 3TX

148 PHOENIX CONTACT 8291_en_03


B2 List of tables

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

8291_en_03 PHOENIX CONTACT 149


RFC 460R PN 3TX

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

150 PHOENIX CONTACT 8291_en_03


B3 Index

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

Gap during installation .......................................... 30, 59


P
H Parameterization memory ........................................... 28
Inserting/removing................................................. 60
Hardware requirements................................................. 9
PC Worx
Cold restart of the device....................................... 97
I Licenses .................................................................. 9
Interfaces Power supply .............................................................. 55
Ethernet........................................................... 27, 52 Sizing .................................................................... 55
SYNC .............................................................. 27, 52 PRIMARY.............................................................. 12, 22
USB....................................................................... 27 PROFINET devices
Naming.................................................................. 94
Project
Creation................................................................. 86

8291_en_03 PHOENIX CONTACT 151


RFC 460R PN 3TX

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

152 PHOENIX CONTACT 8291_en_03

You might also like