RFC 430

Installing and Starting Up Remote Field Controllers
With Ethernet Connection

User manual
User manual
Installing and Starting Up Remote Field Controllers With
Ethernet Connection
RFC 430/450 ETH-IB UM E, Revision 05 2021-07-22
This user manual is valid for:
Designation Order No.

RFC 430 ETH-IB 2730190
RFC 450 ETH-IB 2730200
6219_en_05
PHOENIX CONTACT GmbH & Co. KG • Flachsmarktstraße 8 • 32825 Blomberg • Germany

phoenixcontact.com
Table of contents
Table of contents
1.1 Labeling of warning notes...................................................................................... 7
1.2 Qualification of users ............................................................................................. 7
1.3 Purpose of this Manual .......................................................................................... 8
1.4 Hardware and Software Requirements.................................................................. 8
1.5 Additional Documentation ..................................................................................... 9
2 Description of the Remote Field Controller ..............................................................................11

2.1 General Description of the Remote Field Controller ............................................ 11
2.2 Unpacking the Remote Field Controller ............................................................... 12
2.3 Connecting and Operating Elements................................................................... 13
2.4 Status and Diagnostic Indicators (Ethernet) ........................................................ 14
2.5 Fan Module ......................................................................................................... 15
2.6 Mounting the Remote Field Controller on the DIN Rail ........................................ 16
2.7 Communication Paths ......................................................................................... 17
2.7.1 Ethernet Connection ............................................................................ 18
2.7.2 Diagnostic Interface (PRG) .................................................................. 19
2.8 Freely Programmable COM1 Interface ................................................................ 20
2.8.1 Function Blocks for Devices Connected to COM1 ............................... 21
2.8.2 COM_INIT ............................................................................................ 22
2.8.3 COM_CTRL ......................................................................................... 24
2.8.4 COM_RCV ........................................................................................... 24
2.8.5 COM_SND ........................................................................................... 24
2.9 Direct Inputs and Outputs .................................................................................... 25
2.10 INTERBUS Interface ........................................................................................... 26
2.11 Parameterization Memory ................................................................................... 26
2.12 Power Supply ...................................................................................................... 28
2.12.1 Sizing of the Power Supply .................................................................. 28
2.12.2 Connecting the Power Supply .............................................................. 29
2.13 Keypad and Diagnostic Display........................................................................... 30
2.13.1 Reset Button ........................................................................................ 30
2.13.2 Diagnostic Display ............................................................................... 31
2.13.3 Setting the IP Address Using the Diagnostic Display ........................... 32
2.13.4 Checking the IP Address Using the Diagnostic Display ....................... 37
2.14 Setting the Operating Mode Using the Key Switch .............................................. 38
2.14.1 Operating Modes ................................................................................. 38
2.14.2 Key Switch ........................................................................................... 38
2.15 Overall Reset of the Remote Field Controller....................................................... 40
6219_en_05 PHOENIX CONTACT 3 / 94

RFC 430/450 ETH-IB UM E
3 Startup Under PC Worx 2 ........................................................................................................41

3.1 Required Software............................................................................................... 41
3.2 Creating a Project................................................................................................ 41
3.3 Selecting the Remote Field Controller ................................................................. 43
3.4 Communication ................................................................................................... 44
3.4.1 Setting the Communication Path .......................................................... 44
3.4.2 Setting the IP Address Using PC Worx 2 ............................................. 46
3.5 Reading the New Configuration........................................................................... 48
3.6 Quick Startup....................................................................................................... 50
4 Startup Under PC Worx 3 ........................................................................................................53

4.1 Required Software............................................................................................... 53
4.2 Creating a New Project........................................................................................ 54
4.3 Setting the Communication Path ......................................................................... 56
4.4 Reading INTERBUS ............................................................................................ 61
4.5 Quick Startup....................................................................................................... 63
5 Safety Measures in Networks ..................................................................................................65

5.1 Problems ............................................................................................................. 65
5.2 SECURITY Add-on Program ............................................................................... 65
6 System Variables .....................................................................................................................69

6.1 General Notes ..................................................................................................... 69
6.2 Status Register for Digital Inputs and Outputs ..................................................... 69
6.3 Diagnostic Status Register .................................................................................. 70
6.4 Diagnostic Parameter Register............................................................................ 70
6.5 IEC 61131 Runtime System................................................................................. 72
6.6 Coprocessor........................................................................................................ 72
A Service and Maintenance .........................................................................................................73

A1 Replacing the Remote Field Controller ................................................................ 73
A2 Replacing the Fan Module................................................................................... 77
A3 Replacing the Parameterization Memory............................................................. 78
A4 Updating the Firmware ........................................................................................ 79
A5 Connecting Cable................................................................................................ 80
B Useful information about Remote Field Controllers...................................................................85

B1 RFC 430 ETH-IB – INTERBUS bus configuration................................................ 85
B2 Error Causes and Remedies ............................................................................... 85
4 / 94 PHOENIX CONTACT 6219_en_05

Table of contents
C Technical Data..........................................................................................................................87
D Index.........................................................................................................................................91


1 For your safety
Read this user manual carefully and keep it for future reference.
1.1 Labeling of warning notes

This symbol indicates hazards that could lead to personal injury.
There are three signal words indicating the severity of a potential injury.
DANGER
Indicates a hazard with a high risk level. If this hazardous situation is not
avoided, it will result in death or serious injury.
WARNING
Indicates a hazard with a medium risk level. If this hazardous situation is not
avoided, it could result in death or serious injury.
CAUTION
Indicates a hazard with a low risk level. If this hazardous situation is not avoided,
it could result in minor or moderate injury.
This symbol together with the NOTE signal word alerts the reader to a situation
which may cause damage or malfunction to the device, hardware/software, or
surrounding property.
Here you will find additional information or detailed sources of information.
1.2 Qualification of users

The use of products described in this manual is oriented exclusively to electrically skilled
persons or persons instructed by them. The users must be familiar with the relevant safety
concepts of automation technology as well as applicable standards and other regulations.

1.3 Purpose of this Manual

This user manual helps you to start up and operate the following Remote Field Controllers
in the INTERBUS system:
– Remote Field Controller 430 (RFC 430 ETH-IB)
– Remote Field Controller 450 (RFC 450 ETH-IB)
The structures of the RFC 430 ETH-IB and RFC 450 ETH-IB Remote Field Controllers are
identical and they differ only in terms of their performance. The Remote Field Controllers are
available in two performance classes:
RFC 430 ETH-IB: Average control performance

Network interface: 10Base-T, 100Base-T(X)
RFC 450 ETH-IB: Higher control performance than the
RFC 430 ETH-IB
Network interface: 10Base-T, 100Base-T(X)
1.4 Hardware and Software Requirements
Description Type Order No. Pcs./Pkt.

Remote Field Controller RFC 430 ETH-IB 2730190 1
Remote Field Controller RFC 450 ETH-IB 2730200 1
Fan module for Field Controller RFC DUAL-FAN 2730239 1
Connecting cable IBS PRG CAB 2806862 1
PC Worx 2 engineering software (or higher) IBS PCWORX E on request 1
PC Worx 3 engineering software (or higher) PC WORX 3 on request 1
DIN rail power supply unit, 24 V DC/5 A QUINT-PS/1AC/24DC/5 2866750 1
Parameterization memory IBS MC FLASH 2MB 2729389 1
Parameterization memory IBS MC FLASH 4MB 2729392 1
You must have a license to operate the IBS PC Worx 2 software with more than 40 I/O
points. To obtain a license, please contact Phoenix Contact.
You must have a license to operate the PC Worx 3 software with more than 2 bytes of input
and output data. To obtain a license for the different configuration levels (32 bytes
input/output data; unlimited input/output data; without/with MSFC), please contact
Phoenix Contact.

1.5 Additional Documentation
Description Type Order No. Pcs./Pkt.

User Manual "Configuring and Installing INTERBUS" IBS SYS PRO INST UM E – 1
User Manual "INTERBUS Diagnostics Guide" IBS SYS DIAG DSC UM E 2747293 1
Quick Start Guide "PC Worx 3" PC WORX 3 QS UM E – 1


Description of the Remote Field Controller
2 Description of the Remote Field Controller
2.1 General Description of the Remote Field Controller

The Remote Field Controller is a compact controller with integrated Ethernet and
INTERBUS connections. The I/O level is connected to the Remote Field Controller using
INTERBUS. Connections for INTERBUS and Ethernet are available to connect higher-level
systems such as the control level or operating level.
When it comes to distributed, modular automation, Remote Field Controllers (RFC) with
IEC 61131 control system intelligence and network connection are the ideal solution. As a
compact controller that can be mounted on DIN rails, Remote Field Controllers provide
networked, PC-based control performance locally on the DIN rail.
Integrated Ethernet Connection

The integrated Ethernet network connection (using twisted pair cable) provides for the
increasingly important Ethernet connectivity. Throughout the network Remote Field
Controllers can be reached via Ethernet and TCP/IP. When using the INTERBUS OPC
server, standardized coupling with various visualization packages is also available via
Ethernet.
IEC 61131 Control Performance

Remote Field Controllers are based on the international PC/104 standard for embedded PC
systems. All Remote Field Controllers are seamlessly configured and programmed
according to IEC 61131 using the PC Worx automation software. PC Worx can be used
locally on the serial interface or via the network (Ethernet). The powerful processor can be
programmed in all five IEC 61131 programming languages and ensures quick control task
processing.
Ethernet Communication
Integrated communication functions of the RFC ... ETH-IB modules enable direct and
effective data exchange via Ethernet. The Ethernet TCP/IP protocol is used for universal
possibilities to communicate with Remote Field Controllers. Using the TCP/IP send and
receive communication blocks according to the IEC 61131-5 standard, information between
Remote Field Controllers e.g., necessary coupling variables, can be exchanged via
Ethernet. This enables distributed, modular automation solutions to be configured. Time
synchronization is also possible via the Ethernet network. In the Ethernet network data is
available in a standardized format using the INTERBUS OPC server.

2.2 Unpacking the Remote Field Controller

The Remote Field Controller is supplied with a package slip, which contains installation
instructions. Please read the complete package slip carefully.
ESD Regulations
NOTE: Electrostatic discharge!

Persons who handle the Remote Field Controller must protect it by observing the ESD
instructions before packing or unpacking the module, opening control boxes or control
cabinets and before touching the module.

2.3 Connecting and Operating Elements
e-T
as
0B
/10
10
1 TR
K
LIN IC
AF
F
N
RU
FC OG
/PR M1
N CO
RU
FC
OP
ST
S
RE
FC
FC
/PRRUN
OG
FC
RU
N I/O
D BG
ST N FC
OP RU N
RU
FC FC
2
RE IL
S
SFA
SY
10
/10
0B
as T
LIN e -T SE
K
RE
TR
AF
FIC
+
–
TE
MO
RE
RU DC
V
SY
N
PR
G 24
SFA
Ord.No.: 27 30 20 0
IL CO S
BU
3
FC M1
RFC 450 ETH-IB

RU
N ER
FC
DB
G
INT
4 I/O
Ord.No.: 27 30 20 0
RFC 450 ETH-IB
RE
SE
T
PR
G
RE
5 MO
TE
6 INT
ER +
BU–
S
+
–
24
V
DC
7 12
11
10 13
8 9 6219A001
Figure 2-1 Structure of the RFC 450 ETH-IB Remote Field Controller
Key:
1 Diagnostic display
2 Key switch to select operating modes
3 Receptacle for parameterization memory
4 Keypad
5 Reset button
6 Diagnostic interface (9-pos. D-SUB male connector)
7 Remote bus connection (9-pos. D-SUB female connector)
8 Supply voltage connection (24 V DC)
9 Direct inputs and outputs
10 Serial interface COM1 (can only be operated under PC Worx 3 (or higher))
11 Ethernet connection (RJ45 female connector, 10/100 BASE-T(X))
12 Status and diagnostic indicators (Ethernet)
13 Fan module (optional)
NOTE: Electrostatic discharge!

The Remote Field Controller is supplied with caps for the D-SUB male connectors. The
caps protect the D-SUB male connectors from electrostatic discharges (ESD =
electrostatic discharge). When a D-SUB male connector is not in use, it must be protected
from electrostatic discharges using the appropriate cap.

2.4 Status and Diagnostic Indicators (Ethernet)

The LINK and TRAFFIC LEDs indicate the state of the Ethernet interface. The LEDs have
the following meanings:
LINK The LINK LED (yellow) is on when the Remote Field Controller is
able to establish contact with another network device.
TRAFFIC The TRAFFIC LED (green) is on when the Ethernet interface sends
or receives data.
A crossover twisted-pair cable is required for direct connection of the Remote Field
Controller to another Remote Field Controller or to a PC.

2.5 Fan Module

The Remote Field Controller can be operated in the ambient temperature range from 0 °C
to 45 °C.
NOTE:
The fan module is required if the Remote Field Controller is operated at an ambient
temperature higher than 45 °C. It is not supplied as standard with the Remote Field
Controller but is available as an accessory.
The fan module is attached 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 vibration).
The electrical connection between the Remote Field Controller and the fan module is
established automatically when the fan module is mounted. The fan module contains two
fans.
The vents are located on the bottom of the fan module. When installing the Remote Field
Controller, ensure that the vents are freely accessible. The Remote Field Controller can
overheat if the vents are covered. Leave a gap of 8 cm to 10 cm above and below the
Remote Field Controller to ensure good ventilation.
NOTE:
The fan module must not be replaced during operation. The Remote Field Controller must
be switched off before the fan module can be exchanged. To replace the fan module,
remove the Remote Field Controller from the DIN rail.
T
SE
RE
+
–
TE
MO
RE
DC
G 2 4V
PR
S
Ord.No.: 27 30 20 0
BU
RFC 450 ETH-IB
ER
INT
6219B051
Figure 2-2 Remote Field Controller with fan module

2.6 Mounting the Remote Field Controller on the DIN

Rail
CAUTION:
The following tasks must be carried out prior to mounting:
– Disconnect the supply voltage
– Ensure that the supply voltage cannot be reconnected by unauthorized persons
If the Remote Field Controller is to be operated with the fan module, the fan module must
be mounted on the DIN rail prior to mounting the Remote Field Controller.
1. Place the Remote Field Controller onto the DIN rail from above (A in Figure 2-3).
NOTE:
When mounting the Remote Field Controller, ensure that the vents are freely accessible
because otherwise the Remote Field Controller can overheat. Leave a gap of
8 cm to 10 cm above and below the Remote Field Controller to ensure good ventilation.
2. Swivel the Remote Field Controller downward until the elastic fixture snaps into place
with a click (B). If required, lightly press the fixture downward (C) using a screwdriver
ensuring in this way that it snapped in properly.
3. Finally, make sure that the Remote Field Controller is securely positioned on the DIN
rail.
H -IB
C ET
RF
C B
6219B002
Figure 2-3 Mounting the Remote Field Controller on the DIN rail

2.7 Communication Paths

The communication path to the Remote Field Controller must be determined before
communication with the Remote Field Controller can take place.
The following communication paths are available on the Remote Field Controller:
(A) Ethernet 10/100Base-T(X)

(B) PRG The serial interface (COM 1 to COM 4) of your PC is con-
nected directly to the Remote Field Controller.
10 10
/10 /10
0B 0B
as as
LIN e-T LIN e-T
K K
TR TR
AF AF
FIC FIC
RU RU
N N
SY SY
SFA SFA
IL CO IL CO
FC M1 FC M1
RU RU
N N
FC FC
D BG DBG
I/O I/O
Ord.No.: 27 30 20 0
Ord.No.: 27 30 20 0
RFC 450 ETH-IB
RFC 450 ETH-IB

RE RE
SE SE
T T
PR PR
G G
RE RE
MO MO
TE TE
INT INT
ER ER
BU + BU +
S – S –
24 24
V V
DC DC
A B
6219B019
Figure 2-4 Communication paths: (A) Ethernet (B) RS-232

2.7.1 Ethernet Connection

A standardized Ethernet interface is available for connecting the Ethernet network. The
Ethernet network is connected via a RJ45 female connector.
Use an Ethernet cable according to CAT 5 of IEEE 802.3.

Observe the bending radii of the Ethernet cables used.
The pin assignment of the interface is as follows:
- 8 RJ45 female connector

- 7 8-pos
Receive data - R- 6
8
- 5
- 4 10/100BASE-T(X)
Receive data + R+ 3 1
Send data - T- 2
Send data + T+ 1 6219B004
Figure 2-5 Ethernet interface 10/100BASE-T
10
/10
0B
as
LIN e-T
K
TR
AF
FIC
RU
N
SY
SFA
IL CO
FC M1
RU
N
FC
D BG
I/O
Ord.No.: 27 30 20 0
RFC 450 ETH-IB
RE
SE
T
PR
G
RE
MO
TE
INT
ER
BU +
S –
24
V
DC
6219A081
Figure 2-6 Connecting the Ethernet cable to the Remote Field Controller

2.7.2 Diagnostic Interface (PRG)

This serial interface providing the Ethernet interface enables communication with the
Remote Field Controller from a PC. A connecting cable is required for direct connection of
a Remote Field Controller and a PC. Connect the connecting cable to the programming
interface of the Remote Field Controller (designation "PRG") and the serial interface of the
PC (COM1 to COM4).
2 2
3 3
RX 5 5
WO
PC
FC
RU
/PRO N
G
FC
RU
N
ST
OP
FC
RE
S
10
/100
Ba
LIN se
K -T
TR
AF
FIC
RU
N
SY
SF
AIL CO
FC M1
RU
N
FC
DB
G
I/O
Ord.No.: 27 30 20 0
RFC 450 ETH-IB
RE
SE
T
PR
G
RE
MOT
E
INT
ER
B US
+
–
24
V
DC
6219A003
Figure 2-7 Cable between PC and Remote Field Controller
Ordering data: Connecting cable between Remote Field Controller and PC,
3 m in length (Designation: IBS PRG CAB; Order No. 2806862).

2.8 Freely Programmable COM1 Interface
This interface can only be operated under PC Worx 3 (or higher).
Different input or output devices can be connected to the Remote Field Controller using the
serial interface COM1. In Table 2-1 you will find a selection of devices and possible
application cases.
Table 2-1 Devices that can be connected to COM1

Device Application
Modem Remote monitoring
Printer Recording
Bar code scanner
Terminal
The devices are operated from the application program using function blocks.
1 DCD
2 RxD
3 TxD
4 DTR
5 GND
6 DSR
7 RTS
8 CTS
9 RI
5 FC
RU
/PRO N
9
G
FC
RU
N
ST
OP
1
FC
RE
6
S
10
/100
Bas
LIN e-T
K
TR
AF
FIC
RU
N
SY
SF
AIL CO
FC M1
RU
N
FC
DB
G
I/O
Ord.No.: 27 30 20 0
RFC 450 ETH-IB
RE
SE
T
PR
G
RE
MO
TE
INT
ER
B US
+
–
24
V
DC
6219A084
Figure 2-8 COM1 serial interface

2.8.1 Function Blocks for Devices Connected to COM1
Function blocks are not communication blocks according to IEC 61131-5.

Communication blocks according to IEC 61131-5 require a communication to be
established between two partners. The COM blocks listed in the following only establish a
connection to the serial interface.
Table 2-2 Function block overview

Function Block Short Description
COM_INIT Serial interface parameterization
COM_CTRL Control and request of status information after initialization
of the serial interface
COM_RCV Reading the internal receive buffer
COM_SND Data transmission to the internal send buffer
The function blocks cannot be instantiated. The second and the following instances return
a corresponding error code.
For detailed information on input/output values of the function blocks, please refer to the
relevant help in PC Worx 3 or later.

2.8.2 COM_INIT
The COM_INIT function block is used to parameterize the serial interface.
After parameterization further interface control is carried out by the COM_CTRL function
block.
The interface parameterization can be changed at any time. The changes come into effect
immediately.
Activate this function block with a rising edge at the IN_ACTIVATE input. When activating
the function block the OUT_BUSY output is set to TRUE and parameterization is started at
the same time. A separate asynchronous task carries out parameterization. This reduces
the function block runtime to a minimum.
When the function block is called the next time it is checked whether parameterization has
been finished or not. If parameterization has been finished, the OUT_BUSY, OUT_ERROR
and OUT_STATUS outputs are set depending on the result. In the event of an error the
OUT_ERROR output remains set.
The following interface parameters can be set using the function block.
Table 2-3 Interface parameters that can be set using COM_INIT
Parameter Meaning Note

protocol Protocol Transparent or end-to-end
baudrate Transmission rate From 110 bits/s to 115200 bits/s
databits Number and parity of data bits
stopbits Number of stop bits 1 or 2
flowcontrol Hardware flow control None, RTS/CTS or
CON/XOFF
Transparent Protocol
In the transparent protocol, data is sent or received without interpretation.
If the XON/XOFF method is used as flow control there is one restriction. In this case the
characters XON (11hex) and XOFF (13hex) are used for data flow control. This means that
these characters cannot be transmitted as user data.
End-to-End Protocol
The V.24 data is conditioned for the end-to-end protocol.
If V.24 data is sent from the user side (RFC side), a CR character (carriage return) is
attached for transmission to the V.24 side.
V.24 data transmitted from the V.24 side can only be read by the user if the Remote Field
Controller has received a CR character. The end character (CR) confirms that the V.24 data
has been received without error and the maximum data length has been observed. The end
character is filtered out when the data is read by the INTERBUS side.

RTS/CTS Hardware Flow Control

By canceling the RTS signal the receiver indicates that its receive buffer is about to
overflow. The transmitter then stops data transmission until the receiver indicates, by
setting the RTS signal, that it is ready to receive again.
The RTS output of the receiver is connected to the CTS input of the transmitter.
RFC xxx ETH-IB Device with serial

including COM1 interface
function block
CTS RTS
Transmitter Receiver
RTS CTS
Receiver Transmitter
6219A080
Figure 2-9 RTS/CTS hardware flow control
XON/XOFF Software Flow Control

Data transmission is controlled by means of the XON (11hex) and XOFF (13hex) characters.
If the module receives an XOFF, no more V.24 data will be transmitted until an XON is
received.
The receiver itself sends an XOFF, if its receive buffer is about to overflow. The transmitter
then stops data transmission. The transmitter sends a single XON and data transmission
continues as soon as more memory becomes available again.
V.24 data is not filtered when it is transmitted. Any characters, which occur with the code
defined for XON and XOFF, are thus transmitted and may trigger undesirable events at the
receiver. When V.24 data is received, the XON and XOFF characters are filtered and are
not made available as data. Any characters with the XON or XOFF code are lost. Ensure
that characters with these codes do not appear in the data stream.

2.8.3 COM_CTRL
The COM_CTRL function block is used to control and request status information after
initializing the serial interface.
Activate this function block with TRUE at the IN_ACTIVATE input. This input is not edge-
triggered. The OUT_BUSY output is set to TRUE. This indicates that the OUT_RCV_CTRL
and OUT_SND_CTRL outputs contain valid values.
The IN_RESET input is designed for future extensions and is not evaluated at present.
2.8.4 COM_RCV
The COM_RCV function block is used to read the internal receive buffer.
Activate this function block with a rising edge at the IN_ACTIVATE input. After activation the
OUT_BUSY output is set to TRUE in the same cycle. After processing the OUT_BUSY
output is reset and the OUT_ERROR and OUT_STATUS outputs are set accordingly. The
OUT_DATA_CNT output contains the number of characters read.
If the function block is called and there is no data to be read, the function block waits for
data. The OUT_BUSY output remains set.
2.8.5 COM_SND
The COM_SND function block is used to transmit data to the internal send buffer.
Activate this function block with a rising edge at the IN_ACTIVATE input. After activation the
OUT_BUSY output is set to TRUE in the same cycle. The IN_DATA_CNT input specifies
the number of characters to be transmitted.
If FALSE is set at the input, always the number of bytes in the data buffer (specified by the
array size) is transmitted. After successful processing the OUT_BUSY output is set to
FALSE.

2.9 Direct Inputs and Outputs

Besides connecting inputs and outputs to the Remote Field Controller via INTERBUS they
can also be connected directly using FLK connectors (FLK = flat-ribbon cable).
RU
N
SY
SFA
IL CO
FC M1
RU
N
FC
D BG
I/O
Ord.No.: 27 30 20 0
RFC 450 ETH-IB
RE
SE
T
PR
G
RE
MO
TE
INT
ER
BU +
S –
24
V
DC
6219B046
Figure 2-10 Establishing the connection for inputs and outputs
You can use the VARIOFACE product range from Phoenix Contact for the connection of
inputs and outputs. Combining the pin assignment with, for example, the VARIOFACE
initiator module FLKMS 14/8IM/LA/PLC (Order No. 2284536) and an assembled round
cable, e.g., FLK 14/EZ-DR/50KONFEK (14-pos.; 0.5 m; Order No. 2288901) results in the
following assignment.
Table 2-4 FLK connector pin assignment combined with FLKMS 14/8IM/LA/PLC
Pin on FLC Connector FLKMS ... Signal Signal

1 0 IN 1
2 1 IN 2
3 2 IN 3 Inputs
4 3 IN 4
1 2 5 4 IN 5
3 4
6 5 OUT 1
5 6
7 8 7 6 OUT 2 Outputs
8 7 OUT 3
9 10
11 12
13 14 9 9 (+) 24 V
10 10 (–) 0V
11 11 (+) 24 V 24 V DC voltage
6219A082 12 12 (–) 0V supply for sensors
13 13 (+) 24 V
14 14 (–) 0V

2.10 INTERBUS Interface

Connect the INTERBUS system to the Remote Field Controller using this interface.
FC
RU
/PRO N
G
FC
RU
N
ST
OP
FC
RE
S
10
/100
Bas
LIN e-T
K
TR
AF
FIC
RU
N
SY
SF
AIL CO
FC M1
RU
N
FC
DB
G
I/O
Ord.No.: 27 30 20 0
RFC 450 ETH-IB RE
SE
T
PR
G
RE
MO
TE
INT
ER
B US
+
–
24
V
DC
6219A083
Figure 2-11 Connecting INTERBUS to the Remote Field Controller
Please refer to “Connecting Cable” on page 80 for interface assignment and cable
assembly.
2.11 Parameterization Memory

The Remote Field Controller has a parameterization memory, which is placed in an opening
in the front plate of the Controller. The programs and configurations for your project can be
stored on the parameterization memory. The parameterization memory can be overwritten
as often as necessary. Retentive (resident) memory blocks are used for the
parameterization memory. Thus, data remains on the parameterization memory if it is
removed from the Remote Field Controller.
2-Mbyte and 4-Mbyte parameterization memories are available.
One side of the parameterization memory has a labeling field. The file name of your project,
for example, can be entered in the labeling field.

FC
/PRRUN
OG
FC
RU
N
ST
OP
FC
R ES
RU
N
SY
SF
AIL
FC
RU
N
FC
D BG
ard
yC
Ord.No.: 27 30 20 0
RFC 450 ETH-IB
RE
r
mo
Me
PR
G
sh
Fla
RE
MO
6219B005
Figure 2-12 Inserting the parameterization memory
Insert the parameterization memory into the card holder provided with the female connector
to the front.
Make sure that when the parameterization memory is pressed lightly, the ejector moves
outward and engages with a click.
CAUTION:
Note that the parameterization memory may only be inserted or removed if the supply
voltage of the Remote Field Controller is disconnected.
NOTE:
Only use parameterization memories from Phoenix Contact:
– 2-Mbyte parameterization memory
IBS MC FLASH 2MB Order No. 2729389
Configurations (projects) and programs can be stored on the parameterization memory so

that they are not lost in the event of a power failure.
IP addresses can be stored in the same way either on the internal memory or on the
parameterization memory (only with Remote Field Controllers with firmware 4.6x or later
and a parameterization memory with 2 Mbytes or more).
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 Remote Field Controller to use it.

2.12 Power Supply
2.12.1 Sizing of the Power Supply

The current required for the Remote Field Controller consists of the following elements:
– Remote Field Controller supply (2.0 A, maximum)
– Digital output supply:
– Normal operation of all outputs: 1.5 A, maximum
– Short circuit of all outputs: 3.0 A
Thus, a power supply unit with an output current of IOUT ≥ 5.0 A is recommended for
operation of 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 2-14 on page 29). When the Remote
Field Controller is switched on, an increased inrush current is temporarily triggered. The
Remote Field Controller behaves like a capacitive load when it is switched on.
Some electronically controlled power supplies have a fall-back characteristic curve (see
Figure 2-13 on page 28) – they are not suitable for operation with capacitive loads.
The following power supply (without a fall-back characteristic curve) is recommended for
operation of the Remote Field Controller:
– Primary-switched power supply unit with SFB technology for 6 times the nominal
current
Quint-PS/1AC/24DC/5; 24 V DC, 5.0 A (Order number 2866750)
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 2-13 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 2-14 Overload range without fall-back characteristic curve
2.12.2 Connecting the Power Supply

The Remote Field Controller is supplied from an external power supply (24 V DC). The
permissible voltage ranges from 19.2 V DC to 30.0 V DC (ripple included). The Remote
Field Controller power supply should be protected with a fuse (5 A, slow-blow).
Only use power supplies that are suitable for operation with capacitive loads (high inrush
current) (see Section “Sizing of the Power Supply” on page 28).
Ord.No.:
RFC 4
RE
MO
TE
INT
ER
BU +
S –
24
V
DC
6219A006
Figure 2-15 Connecting the Power Supply
The Remote Field Controller uses the TCP/IP protocol for communication via the Ethernet.
Thus, an IP address must always be set in the Remote Field Controller. The IP address is
set to 0.0.0.0 by default. This is why the message "FC 2112 0000" (no IP address
available) is indicated in the diagnostic display. Before the Remote Field Controller can be
used, an IP address that is valid in your network must be entered (see Section “Setting the
IP Address Using the Diagnostic Display” on page 32).

2.13 Keypad and Diagnostic Display

The keypad of the Remote Field Controller has six keys and enables menu-driven
operation.
INTERBUS
Diagnostic display
: Cursor up
RUN
: Cursor down
SYSFAIL FCRUN FCDBG
: Cursor right, selection of

menu items or addresses
Keypad
RESET
: Cursor left, selection of
menu items or addresses
: Enter, confirm selection
: Escape (ESC), exit menu item

6219B007
Figure 2-16 Keypad of the Remote Field Controller
2.13.1 Reset Button

The reset button is recessed in the front plate (see Figure 2-16). It can only be activated with
a pen or similar object to prevent accidental activation. When the reset button is pressed,
the Remote Field Controller is completely initialized and booted. INTERBUS outputs are
reset and inputs are not read. All parameter settings (logical addressing, event definitions,
etc.) are lost. The boot process is completed after approximately 40 seconds.

2.13.2 Diagnostic Display

The diagnostic display shows operating states, addresses, data, and in the event of an
error, the error location and code (partly in plain text).
The diagnostic display has background lighting. The background can display the following
colors:
GREEN: normal operation
RED: error
INTERBUS FAIL M O D E M O N I
HEX
E X P PARA CODE
Diagnostic display
SEG.POS H E X
VALUE CODE
RUN
SYSFAIL FCRUN FCDBG
HIGH LOW % HEX

Keypad RUN FAIL BSA P F
RESET
6219A008
SYSFAIL FCRUN FCDBG
Figure 2-17 Diagnostic display of the Remote Field Controller
For additional information on the diagnostic display and operation of the keypad, please
refer to the INTERBUS Diagnostics Guide (IBS SYS DIAG DSC UM E;
Order No. 2747293).

2.13.3 Setting the IP Address Using the Diagnostic Display
First IP address setting can always be carried out using the diagnostic display.
When using the PC Worx 2 software the first IP address setting can also be carried out
using the serial interface PRG.
If the Remote Field Controller already has an IP address that is valid in your network, the
IP address can also be changed using PC Worx 2 via the network (see Section “Setting
the IP Address Using PC Worx 2” on page 46).
The following example describes how to set the IP address using the diagnostic display.
Example:
The IP address 100.0.0.3 is to be assigned to the Remote Field Controller.
Byte 1 . Byte 2 . Byte 3 . Byte 4

100 . 0 . 0 . 3
FAIL M O MD OE N I MODE MODE FAIL M O MD OE N I
HEX HEX
E X PPA R CA O D E E X PPA R CA O D E
SEG.POSH E X SEG.POSH E X
VALUE CODE VALUE CODE
HIGH L O W% H E X H I G HL O W% H E X
L S AP F
R U NF A I B L S AP F
R U NF A I B
6219A010
Figure 2-18 Arrangement of bytes one to four in an IP address

1. Hold
down ESC
2. Press
RESET
NORM MODE MONI
CFG DIAG STAT OPT
ADDR SCANTIME OPTITIME FW-V HW-V RSET LCD TEST
IP SUB RTR
MODE MODE MODE MODE MODE
2 1 2 1 2 1
1 MODE
1 MODE
1 MODE
2 2 2
1 MODE
1 MODE
1 MODE
MODE
2 2
MODE MODE
1 MODE
1 MODE
MODE
Press
RESET 6219B017
Figure 2-19 Setting the IP address using the diagnostic display
Entry of IP addresses is based on dotted notation. The individual bytes of the IP address
are entered in separate windows (in decimal notation).

To set the IP address, proceed as follows:

1. Activate SETUP MODE 0.
Press the ESC key and hold it down. Press the RESET button. Press the ESC key until
the Remote Field Controller is in SETUP MODE. SETUP MODE is displayed as follows:
6219A011
Figure 2-20 Display for SETUP MODE 0 (SM 0)
2. Press the "Cursor right" or "Cursor left" key to select MODE from the menu. The MODE
menu item appears at the top of the display.
Confirm your selection by pressing ENTER.
3. Then press the "Cursor left" or "Cursor right" key to open the OPT submenu. This menu
item is displayed in the same line as FC or ADDR.
Confirm your selection by pressing ENTER.
4. Press the "Cursor left" or "Cursor right" key to open the ADDR submenu.
Confirm your selection by pressing ENTER. IP 1 appears in the diagnostic display.
MODE
6219A012
Figure 2-21 Display of the first byte of the IP address

5. Now use the "Cursor up" and "Cursor down" keys to set the value of the first byte of the
IP address (Figure 2-16 on page 30).
If you keep pressing the "Cursor up" or "Cursor down" key, the address will increase or
decrease continuously. As soon as the address is divisible by ten, counting is continued
in steps of ten. In this way, the desired value is reached quickly. To stop counting in steps
of ten, release the cursor key. To set the precise final value, press the "Cursor up" or
"Cursor down" key once.
If the value of the first byte of the IP address is set properly, use the "Cursor right" key
to jump to the second byte of the IP address (Figure 2-19 on page 33).
IP 2 appears in the diagnostic display.
6. Repeat the process described for the second, third, and fourth byte of the IP address.
Use the "Cursor right" key to jump to the next value each time.
After the fourth byte of the IP address has been set SUB 1 appears in the diagnostic
display.
7. Set the four bytes of the subnet mask according to the process described. Use the
"Cursor right" key to jump to the next value each time.
After the fourth byte of the subnet mask has been set RTR 1 appears in the diagnostic
display.
8. Set the four bytes of the router address according to the process described. Use the
"Cursor right" key to jump to the next value each time.
9. When you have entered all values, confirm them by pressing ENTER. The diagnostic
display shows the following:
MODE
6219A013
Figure 2-22 Safety prompt for saving data
10. Use the "Cursor left" or "Cursor right" key to jump to YES. Confirm your selection by
pressing ENTER.
If you confirm with NO, you will automatically jump back to IP address 1 (IP 1) at the start
of the menu.

MODE
6219A014
Figure 2-23 Display during data saving
Thereafter, it is displayed that the addresses are permanently written to the memory
(internal or parameterization memory depending on the firmware version and the memory
space, see page 27). Modifications can only be changed by calling the menu again.
After the new values have been saved successfully, you will be asked to press the reset
button to validate the settings. The following display appears:
FAILM O DM EO N I
HEX
E X PPA R CA O D E
SEG.POSH E X
VALUE CODE
HIGH L O W% H E X
L S AP F
R U NF A I B
6219A015
Figure 2-24 Request to run a reset
11. Press the reset button of the Remote Field Controller.
The values set are only valid after the Remote Field Controller has been reset.
If an error occurs while the new values are being saved, rather than the request to run a
reset, the following display will appear:

MODE
6219A016
Figure 2-25 Error message: IP address
In this case, you can quit the menu without accepting the modifications. Repeat the
procedure.
2.13.4 Checking the IP Address Using the Diagnostic Display

The IP address in the Remote Field Controller can always be checked, even during
operation. Select the OPT menu and then the ADDR submenu in the diagnostic display.
Confirm your selection by pressing ENTER each time. First, the first byte of the IP address
is indicated. The remaining bytes of the IP address, the subnet mask, and the router
address can be checked by pressing the "Cursor right" and "Cursor left" keys. Use the
ESCAPE key to quit the menu at any time.
Modifications are not possible in this mode. Only SETUP MODE 0 can be used for
modifications (see Section “Setting the IP Address Using the Diagnostic Display” on
page 32).

2.14 Setting the Operating Mode Using the Key Switch
2.14.1 Operating Modes

The operating modes of the Remote Field Controller are set using the key switch. The
following operating modes are available:
Table 2-5 Operating modes of the Remote Field Controller
Operating Mode Explanation

FCRUN/PROG The application program is in the RUN state.
The PC Worx software can be used for program and configuration
changes.
The monitoring and online functions can be used.
Can only be set using the administrator key.
FCRUN The application program is in the RUN state.
The PC Worx software cannot be used for program and configura-
tion changes. The PC Worx software can only be used for read
functions.
The monitoring and online functions can be used.
STOP The application program is in the STOP state.
FCRES Overall reset: An overall reset clears the application program in the
main memory and the retentive data in the NVRAM (see Section
“Overall Reset of the Remote Field Controller” on page 40).
Can only be set using the administrator key.
The FCRUN/PROG and FCRES functions can only be accessed using the red administrator
key.
2.14.2 Key Switch

In order to increase operating safety, the Remote Field Controller is supplied with a key for
the administrator (red) and a key for the operator (black). Both keys have different functions.
They can only be removed from the Remote Field Controller if they are in the FCRUN and
STOP positions.

The administrator key (red) is used to set all operating modes of the Remote Field
Controller.
90 FC
° /PRRUN
OG
FC
RU
N
ST
FC OP
/PRRUN FC
OG RES
FC
RU 90
ST
N
°
OP
FC
RES
FC
/PRRUN
OG
FC
RU
FC
N FC
/PRRUN
ST
/PRRUN
OP
FC
OG RES
OG
FC F
CR
RU
45 N UN
° FC
ST
OP
ST
OP
R FC
ES RES
6219A018
Figure 2-26 Operating modes with administrator key
The operator key (black) can only be used to set the FCRUN and STOP modes.
90 FC
° /PRRUN
OG
FC
RU
N
ST
FC OP
/PRRUN FC
OG RE
S
FC
RU
N
ST
OP
FC
RE
S
FC
/PRRUN
OG
FC
RU
N
ST
OP
FC
RE
S
6219A045
Figure 2-27 Operating modes with operator key

2.15 Overall Reset of the Remote Field Controller

An overall reset clears the application program in the main memory and the retentive data
in the NVRAM and is irreversible.
The red administrator key is required for an overall reset of the Remote Field Controller.
1. Turn the key to the STOP position.

2. Turn the key to the FCRES position. The FCDBG arrow is displayed. Hold the key in this
position until the FCDBG arrow disappears. Now turn the key back to the STOP
position.
Diagnostic display
FAIL MODE MONI
HEX
EXP PARA CODE
SEG.POS H E X
VALUE CODE
HIGH LOW % HEX

RUN FAIL BSA PF
SYSFAIL FCRUN FCDBG

6219A044
Figure 2-28 Diagnostic display (FCDBG)
3. Turn the key to the FCRES position again. The FCDBG arrow flashes for approximately
three seconds. When the FCDBG arrow disappears, the key can be turned back to the
STOP position. The application program has now been deleted from the main memory
and the retentive data has been deleted from the NVRAM.
The overall reset of the Remote Field Controller deletes the application program from the
main memory. It does not affect the application program stored on the parameterization
memory, which remains intact. The next time the Remote Field Controller is booted, the
application program is reloaded from the parameterization memory into the main memory
of the Remote Field Controller.

Startup Under PC Worx 2
3 Startup Under PC Worx 2
3.1 Required Software

The following software environment is required for configuring the Remote Field Controller:
– PC Worx version 2.01 or later
– Microsoft Windows NT 4.0 with Service Pack 4 or later
Please refer to the SYSTEM WORX online help and the following user manual for
information on the operation of PC Worx 2:
– INTERBUS Diagnostics Guide
IBS SYS DIAG DSC UM E Order No. 2747293
3.2 Creating a Project

Menu structure and SYSTEM WORX can be operated easily using menus. These menus are assigned to
operating concept devices and elements.
You can select a device or an element by clicking the left mouse button when the cursor is
on the device/element.
You can open the context menu by clicking the right mouse button when the cursor is on
the device/element. The context menu lists the menu items available for the
device/element.

Creating a project To create a new project, proceed as follows:

1. First select the "New" command from the "File" menu to create a project without bus
devices.
2. If you have already made changes in the previously loaded project, you will be asked
whether you want to reject or save these changes.
3. Enter a project name in the dialog box that follows, e.g., "System 01".
4. Confirm your entry with OK.
This creates a new project without INTERBUS devices.
Figure 3-1 New project in SYSTEM WORX
The elements "Project", "PLC/PC", "Program", "Controller Board", "Parameterization

Memory", and "Configuration Frame" are the basic elements of a project. These are
always available and cannot be deleted.

3.3 Selecting the Remote Field Controller

Now select the type of controller board used. For this description, the RFC 430 ETH-IB
Remote Field Controller is used.
Once you have created the project, the menu for selecting the controller board type
appears. In this case you can skip steps 1 to 3 described in the following.
If you want to select the controller board type at a different point in time, proceed as
described in the following.
1. Select the "Controller Board" element.
2. Open the context menu of the "Controller Board" element.
3. Select the "Type..." menu item from the context menu.
Figure 3-2 "Select Controller Board" dialog box
4. Select "RFC 430 ETH-IB" from the "Select Controller Board" dialog box.
5. Confirm the dialog box with OK. The Remote Field Controller is now selected.

3.4 Communication
The Ethernet connection and the diagnostic interface are available for communication (see
also Section “Communication Paths” on page 17).
3.4.1 Setting the Communication Path
Communication Under Windows NT

Under Windows NT one driver is available for communication with the Remote Field
Controller.
Once you have selected the controller board, the menu for setting the communication path
appears. In this case you can skip step 1 described in the following.
If you want to select the communication path at a different point in time, proceed as
described in the following.
1. Select the "Communication Path..." command from the "Controller Board" context
menu.
2. Select the communication path (e.g., via the serial interface) in the following dialog box.
Figure 3-3 "Communication Path Settings" dialog box

3. Select the "default" or "with preprocessing" project template from the menu that
appears.
If you select the "default" project template here, you can activate preprocessing at a later
point in time.
Selecting the "default" project template creates a project without preprocessing.

Selecting the "with preprocessing" template creates a project with preprocessing (also
process data preprocessing).
Preprocessing enables secure processing of signals that also only occur briefly. This may
be required if the bus cycle time is much shorter than the runtime of the application program.
Preprocessing can also be used for high-priority processing of signals independent of other
cyclic program tasks.
During preprocessing INTERBUS signals are linked with other INTERBUS signals or with
program variables. The signals are either linked between two INTERBUS cycles (sequential
preprocessing) or during one INTERBUS cycle (parallel preprocessing).
The IP address must be set in the Remote Field Controller for communication via the
Ethernet. The Sections “Setting the IP Address Using PC Worx 2” on page 46 and “Setting
the IP Address Using the Diagnostic Display” on page 32 describe how to set the address.
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 computer
and make changes, either intentionally or unintentionally. Prevent unauthorized access to
the Remote Field Controller and your PC. For additional information on this subject, please
refer to Section “Safety Measures in Networks” on page 65.

3.4.2 Setting the IP Address Using PC Worx 2
Only the serial interface or the diagnostic display of the Remote Field Controller can be
used to set the IP address with the PC Worx software for the first time. It is possible to
change the IP address later via the Ethernet using the PC Worx software.
To set the IP address using the PC Worx software, proceed as follows:

1. Press F3 to switch to the "Configuration (Online)" mode.
2. Select the "Configuration (Online)" operating state in the following dialog box.
Figure 3-4 "Operating State" dialog box
3. Confirm your selection with OK.

4. Open the context menu of the Remote Field Controller (controller board).
Figure 3-5 Context menu of the Remote Field Controller
5. Select the "Settings..." submenu from the context menu.

6. Select the "Configuration" tab from the "Controller Board Settings" dialog box.
Figure 3-6 "Controller Board Settings" dialog box
7. Enter the current time and date in the "System" field for the internal system clock of the
Remote Field Controller.
Enter the addresses that are valid for your network in the "IP Address", "Subnet Mask",
and "Router IP Address" fields.
8. Click on "Execute". The data contained in the "Configuration" tab is now transmitted to
the Remote Field Controller.
The time of the realtime clock of the Remote Field Controller is read only once and then
displayed. This is the reason why the time indication does not change.
When the settings have been successfully transmitted to the Remote Field Controller, a
message is displayed. This message states that the changes are only valid after a reset.
Figure 3-7 "Hardware Reset" information window

Execute a reset by taking the following steps:

– Press the reset button
– Switch off the supply voltage and then switch it back on again
– Trigger a reset using SYSTEM WORX
Execute the reset immediately. The Remote Field Controller can only be addressed
using the "new" IP address when the reset has taken place. If a reset is not executed, it
may not be possible to address the Remote Field Controller via the Ethernet.
3.5 Reading the New Configuration

Read the connected bus configuration in order to edit it in SYSTEM WORX.
If the Remote Field Controller has no active configuration (READY state),

SYSTEM WORX executes the "Create Configuration" command after a safety prompt.
This causes the Remote Field Controller to read the connected configuration. Data
already configured may be lost.
1. Select the "Configuration Frame" element.
2. Open the context menu of the "Configuration Frame" element. Select the "Read
connected Configuration" menu item and confirm the following messages with "Yes".
Figure 3-8 "Reading Bus Configuration" message
3. The connected bus configuration has now been read and can be adapted as required.
4. Save your settings. For this, select the "Save" command from the "File" menu.

For the configuration changes to be effective, these changes must be written to the
parameterization memory of the Remote Field Controller.
5. Select the "Parameterization Memory" element.
6. Open the context menu of the parameterization memory.
7. Select the "Save" submenu from the context menu. Specify whether saving is to be
carried out with or without project files.
Figure 3-9 "Parameterization Memory... " context menu
If saving without project files, not the entire PC Worx project will be stored on the controller
board. Large projects can only be saved without project files.
If a task is missing from the "Std_Res" resource, this is indicated by means of an error
message. If it appears, confirm this error message with OK.
8. Confirm the following safety prompt with OK.
Figure 3-10 Safety prompt
Execute a reset by taking the following steps:

– Press the reset button
– Switch off the supply voltage and then switch it back on again
– Trigger a reset using SYSTEM WORX ("Control... Reset Controller Board" from the
context menu of the controller board).
If there is not an immediate reset, the changes will only take effect upon the next reset. The
changes may have been done some time ago and the system may have already been
exited.

3.6 Quick Startup

In the previous steps you prepared your project in SYSTEM WORX in order for INTERBUS
to be started. You may now run INTERBUS cycles.
1. Open the context menu of the Remote Field Controller (controller board).
2. Select the "Parameterization" submenu and then the "Execute..." command.
Figure 3-11 Context menu of the Remote Field Controller
3. Select "Parameterize and start INTERBUS only" under "Parameterizations" in the

"Execute Parameterization" dialog box.
Figure 3-12 "Execute Parameterization" dialog box

4. Confirm your selection with OK.

5. Successful parameterization will be indicated by a message.
Figure 3-13 "Executing Parameterization" message
6. Confirm this message with OK.

The INTERBUS system can now be further configured and programmed using PC Worx 2.
If the system cannot be started up because of an installation error, the "FAIL" LED lights up
and a corresponding error message appears in PC Worx 2.
For an explanation of the error message, please refer to the Diagnostics Guide
(IBS SYS DIAG DSC UM E, Order No. 2747293) or the Appendix B 2 “Error Causes and
Remedies”.


4 Startup Under PC Worx 3
4.1 Required Software

The following software environment is required for configuring the Remote Field Controller:
– PC Worx version 3.01 or later
– Microsoft Windows NT 4.0 with Service Pack 4 or later
Please refer to the associated online help and the following user manual for information on
the operation of PC Worx 3:

4.2 Creating a New Project

Menu structure and PC Worx 3 can be operated easily using menus. These menus are assigned to devices and
operating concept elements.
You can select a device or an element by clicking the left mouse button when the cursor is
on the device/element.
You can open the context menu by clicking the right mouse button when the cursor is on
the device/element. The context menu lists the menu items available for the
device/element.
Creating a project To create a new project, proceed as follows:

1. Select the "New Project..." command from the "File" menu to create a new project using
a template.
Figure 4-1 "File... New Project..." command
The tree structure and the selection of the control system will now be prepared.
Figure 4-2 Project templates

2. Select the "RFC 430 ETH-IB" control system and confirm your selection with "OK".
3. Once the new project has been created, save it with the "File…Save Project As / Zip
Project As..." command.
Figure 4-3 "File...Save Project As / Zip Project As..." command
4. Enter a project name and save the project.
Figure 4-4 "Save/Zip project as" dialog box

4.3 Setting the Communication Path

The Ethernet connection and the diagnostic interface are available for communication (see
also Section “Communication Paths” on page 17).
The IP address must be set in the Remote Field Controller for communication via the
Ethernet. The Section “Setting the IP Address Using the Diagnostic Display” on page 32
describes how to set the address.
For setting the communication path between the programming PC with PC Worx 3 and the
Remote Field Controller change to the "Bus Configuration View" in the menu bar.
Figure 4-5 PC Worx 3 Bus Configuration View

1. Select the "# RFC 430 ETH IB 0.0" control system in the "Bus Structure" window.
Figure 4-6 "Bus Structure" window

2. Select the "Communication" tab in the "Device Details" window. Select the
communication path to the Remote Field Controller.
Figure 4-7 "Device Details" window: selecting the communication path

3. Enter the IP address set in the Remote Field Controller in the "IP Address" field or select
it from the menu.
Figure 4-8 "Device Details" window: specifying the IP address
Click on the "Test" button to test the communication path and to check the connection to
the Remote Field Controller.
The communication path has been tested successfully if a green status indicator appears
in the window.

4. Click on the "Apply" button to save the settings in the project.
Figure 4-9 Communication path
In the previous example, the following settings were made:

– Interface Type: TCP/IP (Ethernet/Localhost)
– Connection name: Manual input
– IP Address: 192.168.110.100
NOTE:
a risk that third parties may access the Remote Field Controller or the PC Worx computer
and make changes, either intentionally or unintentionally. Prevent unauthorized access to
the Remote Field Controller and your PC. For additional information on this subject, please
refer to Section “Safety Measures in Networks” on page 65.

4.4 Reading INTERBUS

To read the connected INTERBUS, proceed as follows:
1. Select the "Connected Bus" command from the "View" menu.
Figure 4-10 "View... Connected Bus" command
2. Select the control system in the "Connected Bus" dialog box.
Figure 4-11 Selecting the control system
This switches to the "online" operating state and the control system (Remote Field
Controller) reads the connected INTERBUS bus configuration.

Once the Remote Field Controller has read the connected INTERBUS the INTERBUS
devices have to be imported into the project.
3. For this, select the "RFC 430 ETH-IB" control system in the "Connected Bus" window.
Open the context menu and select the "Import to project… With device description"
command.
Figure 4-12 "Connected Bus" dialog box
The "Select device" window lists the modules, which correspond to the connected devices
according to the device description.
4. Select the device, which is actually connected in the INTERBUS system, and repeat
this step until all devices are linked to their device description.
Figure 4-13 "Select device" dialog box
5. Disconnect the link to the control system by selecting "Offline" in the "Selected control
system" selection box in the "Connected Bus" window.
6. Save your settings. For this, select the "Save" command from the "File" menu.

4.5 Quick Startup

In the previous steps you prepared your project in order for INTERBUS to be started. You
may now run INTERBUS cycles.
1. Compile the project and download it to the control system. For this, select the "Make"
command from the "Build" menu.
Figure 4-14 "Make" command in the "Build" menu
2. Open the "Project Control Dialog".
Figure 4-15 Project Control Dialog
3. Download the project to the control system.
Figure 4-16 "Download" Project Control Dialog

4. Then start to run INTERBUS cycles.
Figure 4-17 "Cold" Project Control Dialog
If an installation error prevents the system from starting normal operation a corresponding
error message appears on the diagnostic display and in PC Worx 3.
For an explanation of the error message, please refer to the Diagnostics Guide
(IBS SYS DIAG DSC UM E, Order No. 2747293).

Safety Measures in Networks
5 Safety Measures in Networks
5.1 Problems
NOTE:
a risk that third parties may access the Remote Field Controller, either intentionally or
unintentionally.
Prevent unauthorized access to your Remote Field Controller by taking appropriate safety
measures. The following safety measures are available:
– No connection to the Intranet/Internet
– Selection of suitable IP addresses
– Firewall/package filter with a suitable configuration
– Router with a suitable configuration
– SECURITY: Add-on program for PC Worx 2
5.2 SECURITY Add-on Program

The SECURITY program is supplied with PC Worx 2. SECURITY is used to protect a
Remote Field Controller from unauthorized access from PC Worx 2 via the network.
SECURITY can be found under:
...\pcworx\bin\security.exe
The safety settings that are made using SECURITY are stored in the Remote Field
Controller so that they are not lost in the event of a power failure. SECURITY can
communicate with the Remote Field Controller via the Ethernet or the serial interface.

Figure 5-1 The SECURITY program
SECURITY enables you to set the following safety levels for a Remote Field Controller:
– No protection ("kein Schutz"):
Other computers can access the Remote Field Controller via the network using
PC Worx 2. No password protection.
– Password protection ("Kennwortschutz"):
Other computers can access the Remote Field Controller via the network using
PC Worx 2. Access is password protected.
– IP protection ("IP-Schutz"):
Only computers with an IP address that has been entered in the SECURITY program
are able to access the Remote Field Controller via the network with PC Worx 2.
– IP and password protection ("IP- und Kennwortschutz"):
Only computers with an IP address that has been entered in the SECURITY program
are able to access the Remote Field Controller via the network with PC Worx 2. Access
is password protected.

Safety Measures in Networks
Defining Safety Settings

The following example illustrates how to define safety settings. The following marginal
conditions apply to this example:
– ACTUAL safety level: No protection ("kein Schutz")
– DESIRED safety level: IP and password protection ("IP- und
Kennwortschutz")
– Connection via: Ethernet (the device number of the Remote
Field Controller in this example is 01)
1. Call the SECURITY program. It can be found under

...\pcworx\bin\security.exe..
2. Select "Connection via Ethernet" ("Verbindung über Ethernet").
3. Enter the device number "01" in the "Device Number" ("Gerätenr.") field. Please use the
device number from PC Worx 2 in the SECURITY program.
If you want to use PC Worx 2 to communicate with a Remote Field Controller via the
Ethernet, the IP address of the Remote Field Controller must be entered in PC Worx 2. IP
addresses for several Remote Field Controllers can be entered in PC Worx 2.PC Worx 2
then assigns each of these Remote Field Controllers a device number. The device numbers
can be found in the "Communication Path Settings" window in PC Worx 2.
PC Worx 2 uses the term "Station No." ("Station Nr.") instead of "Device Number"
("Gerätenummer").
4. Click on "Read" ("Lesen"). The safety settings are now read from the Remote Field
Controller via the Ethernet and displayed in SECURITY.
5. Select "IP and Password Protection" ("IP und Kennwortschutz").
6. Enter the IP addresses of the computers with which the Remote Field Controller is to
communicate. The Remote Field Controller then only uses PC Worx 2 to communicate
with computers for which the IP address has been entered in SECURITY.
7. Enter a password in the "Password (8 - 16 characters)" ("Kennwort (8-16 Zeichen)")
field. The Remote Field Controller then only uses PC Worx 2 to communicate with
computers that identify themselves using the correct password.
8. Click on "Write" ("Schreiben"). The safety settings are now stored in the Remote Field
Controller and will not be lost in the event of a power failure. The safety settings are
activated.
If you have forgotten your password or entered incorrect settings in SECURITY, it is no

longer possible to access the Remote Field Controller via the network. However, the
Remote Field Controller can still be accessed via the serial interface. Connect the Remote
Field Controller to the PC Worx 2 computer using a serial connecting cable. Use
SECURITY to access the Remote Field Controller via the serial interface. A new password
can now be assigned or the incorrect settings corrected.


System Variables
6 System Variables
6.1 General Notes

This section describes the special program functions of the PC Worx 2 and 3 software that
are available for the Remote Field Controller.
The Remote Field Controller has a register set, which is used for diagnostics and easy
control of the bus system. The diagnostic data is stored in the diagnostic status register and
the diagnostic parameter register. These registers are available to the application program
as system variables (system flags, global variables).
Operating states, error states, and additional information about the INTERBUS system can
be evaluated in the application program.
For additional information on diagnostics, please refer to the following user manual:
6.2 Status Register for Digital Inputs and Outputs

The following system variable can be used to read the input and output states and to write
the output states.
Table 6-1 System variables of the status register for digital inputs and outputs
System Variable Type Meaning

ONBOARD_INPUT WORD State of all inputs and outputs
ONBOARD_INPUT_BIT0 BOOL State of input 1
ONBOARD_OUTPUT_BIT0 BOOL State of output 1
ONBOARD_OUTPUT_OVERLOAD BOOL Overload of an output

6.3 Diagnostic Status Register

Information about the operating state of the Remote Field Controller is stored in the
diagnostic status register. Every bit in the diagnostic status register is assigned a certain
Remote Field Controller state.
The following system variables can be used to read the diagnostic status register
information.
Table 6-2 System variables of the diagnostic status register

MASTER_DIAG_STATUS_REG_USER BOOL User error/parameterization error
MASTER_DIAG_STATUS_REG_PF BOOL Peripheral fault
MASTER_DIAG_STATUS_REG_BUS BOOL Bus error
MASTER_DIAG_STATUS_REG_CTRL BOOL Error on Remote Field Controller/hardware fault
MASTER_DIAG_STATUS_REG_DTC BOOL Diagnostic routine active
MASTER_DIAG_STATUS_REG_RUN BOOL Data transmission active
MASTER_DIAG_STATUS_REG_ACT BOOL Selected configuration ready to operate
MASTER_DIAG_STATUS_REG_RDY BOOL Remote Field Controller ready to operate
MASTER_DIAG_STATUS_REG_BSA BOOL Bus segment aborted
MASTER_DIAG_STATUS_REG_SYSFAIL BOOL Control program not running
MASTER_DIAG_STATUS_REG_RES BOOL Standard function processed negatively
MASTER_DIAG_STATUS_REG_SYNCRES BOOL Synchronization error occurred
MASTER_DIAG_STATUS_REG_DCR BOOL Faulty data cycles
MASTER_DIAG_STATUS_REG_WARN BOOL Defined waiting time exceeded
MASTER_DIAG_STATUS_REG_QUAL BOOL Defined error density exceeded
MASTER_DIAG_STATUS_REG_SSINFO BOOL Not relevant
MASTER_DIAG_STATUS_REG_HI BYTE Master diagnostic status register, high byte
MASTER_DIAG_STATUS_REG_LOW BYTE Master diagnostic status register, low byte
6.4 Diagnostic Parameter Register

The diagnostic parameter register provides additional information on the error indicated in
the diagnostic status register. The following information is stored in the diagnostic
parameter register:
– Error location
– Error code

System Variables
15 8 7 0
3 1
Segment number Position in the segment
Example: device number 3.1
6219A040
Figure 6-1 Error location in the diagnostic parameter register
15 8 7 0
0 A 5 0
Error code
Example: address overlap, code 0A50 hex
6219A041
Figure 6-2 Error code in the diagnostic parameter register
Special case: If a local bus error cannot be located, the value 128 is indicated in the
diagnostic parameter register i.e., bit 7 is set.
Table 6-3 Error code (example: 0A50hex)

Error Code: Type: Description and Remedy
0A50 USER Error when assigning a process data item. Input or
output address assigned more than once.
Remedy: Always assign only one process data item
to an input/output address. Alternatively, the process
data description "Multiple Assignment" can be acti-
vated in the CMD software.
Add_Error_Info: PDRL_Index of the incorrect
PDRL entry.
The diagnostic parameter register is rewritten whenever an error occurs. The diagnostic
parameter register contains the value "0" if no errors are detected.
Table 6-4 System variable of the diagnostic parameter register

MASTER_DIAG_PARAM_REG_HI BYTE Diagnostic parameter register, high byte
MASTER_DIAG_PARAM_REG_LOW BYTE Diagnostic parameter register, low byte
MASTER_DIAG_PARAM_REG_2_HI BYTE Extended diagnostic parameter register, high byte
MASTER_DIAG_PARAM_REG_2_LOW BYTE Extended diagnostic parameter register, low byte

6.5 IEC 61131 Runtime System

There is a separate group of variables for the IEC 61131 runtime system.
Table 6-5 System variables of the IEC 61131 runtime system

PLCMODE_ON BOOL The runtime system on the Remote Field Controller is ready to operate.
PLCMODE_RUN BOOL The application program is running.
PLCMODE_STOP BOOL The application program is currently not running.
PLCMODE_HALT BOOL The application program was stopped at an unspecified point.
PLCDEBUG_BPSET BOOL At least one breakpoint has been set in the application program.
PLCDEBUG_FORCE BOOL At least one variable is being continuously overwritten (forced) by PRO-
GRAM WORX.
PLCDEBUG_POWERFLOW BOOL In "Powerflow" mode, you can see which parts of your application program
are being processed. This bit indicates whether "Powerflow" mode is ac-
tive.
PLC_TICKS_PER_SEC INT This variable shows how many pulses the system clock of the Remote
Field Controller delivers per second.
PLC_SYS_TICK_CNT DINT This variable shows the total number of pulses delivered by the system
clock since the last startup.
6.6 Coprocessor
The system variables listed below show the states of the diagnostic status register on the
coprocessor of the Remote Field Controller.
Table 6-6 System variables of the coprocessor

COP_DIAG_STATUS_REG_PON BOOL The coprocessor is ready to operate.
COP_DIAG_STATUS_REG_RT_ERR BOOL A runtime error (out of realtime) has occurred on the coprocessor.
COP_DIAG_STATUS_REG_FAT_ERR BOOL A fatal error has occurred on the coprocessor. Division by zero, for
example, leads to a fatal error.
COP_DIAG_STATUS_REG_WARN BOOL A warning has been issued on the coprocessor.

Service and Maintenance
A Service and Maintenance
A1 Replacing the Remote Field Controller

If it is necessary to replace the Remote Field Controller, please proceed as follows:
1. Disconnect the power supply of the Remote Field Controller.
2. Unplug the supply cable from the Remote Field Controller.
Ord.No.:
RFC 4
RE
MO
TE
INT –
ER
BU +
S –
24
V
DC
6219A021
Figure A-1 Unplugging the power supply
3. Unplug the connector for the inputs and outputs, if inserted.

CO
M1
I/O
Ord.No.: 27 30 20 0
RFC 450 ETH-IB
RE
PR
G
RE
SE
T
A1
MO
TE
INT
ER
BU +
A2 S
24
V
DC
–
6219A048
Figure A-2 Unplugging the connector for inputs and outputs
4. Unplug the remote bus cable, if inserted.

Ord.No.:
RFC 4
RE
MO
TE
INT –
ER
BU +
S –
24
V
DC
6219A022
Figure A-3 Unplugging the remote bus cable

5. Unplug the Ethernet connection, if present.
10
/10
0B
as
LIN e-T
K
TR
AF
FIC
RU
N
SY
SFA
IL CO
FC M1
RU
N
FC
DB
G
I/O
Ord.No.: 27 30 20 0
RFC 450 ETH-IB
RE
SE
T
PR
G
RE
MO
TE
INT
ER
B US
+
–
24
V
DC
6219A042
Figure A-4 Unplugging the Ethernet connection
6. Unplug the connecting cable, if inserted.
RU
N
SY
SFA
IL CO
FC M1
RU
N
FC
D BG
I/O
Ord.No.: 27 30 20 0
RFC 450 ETH-IB
RE
SE
T
PR
G
RE
MO
TE
INT
ER
BU +
S –
24
V
DC
6219A023
Figure A-5 Unplugging the connecting cable

Replacing the Remote Field Controller
7. Remove the Remote Field Controller to be replaced from the DIN rail.
IB
T H-
FCE
R B
A
6219B024
Figure A-6 Removing the Remote Field Controller from the DIN rail
Please also refer to the notes in Section “Replacing the Fan Module” on page 77.
8. Take the new Remote Field Controller out of its packaging.

9. Snap the Remote Field Controller onto the DIN rail and check that it is securely locked.
H -IB
C ET
RF
B
C
6219B025
Figure A-7 Snapping the Remote Field Controller onto the DIN rail
Please also refer to the notes in Section “Replacing the Fan Module” on page 77.

10. Plug the remote bus cable in the female connector, if applicable, and fix it.
Ord.No.:
RFC 4
RE
MO
TE
INT
ER
BU +
S –
24
V
DC
6219A026
Figure A-8 Establishing the remote bus connection
11. Plug in the Ethernet cable, if applicable.
10
/10
0 Ba
LIN s e-T
K
TR
AF
FIC
RU
N
SY
SFA
IL CO
FC M1
RU
N
FC
DBG
I/O
Ord.No.: 27 30 20 0
RFC 450 ETH-IB
RE
SE
T
PR
G
RE
MO
TE
INT
ER
BU +
S –
24
V
DC
6219A043
Figure A-9 Establishing the Ethernet connection
12. Plug in the connector for the inputs and outputs, if applicable.
RU
N
SY
SFA
IL CO
FC M1
RU
N
FC
DBG
I/O
Ord.No.: 27 30 20 0
RFC 450 ETH-IB
RE
SE
T
PR
G
RE
MO
TE
INT
ER
BU +
S –
24
V
DC
6219A046
Figure A-10 Establishing the connection for inputs and outputs

Replacing the Fan Module
13. Connect the power supply to the Remote Field Controller.
Ord.No.:
RFC 4
RE
MO
TE
INT
ER
BU +
S –
24
V
DC
6219A006
Figure A-11 Plugging in the power supply
14. Switch on the power supply of the control system.
A2 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 exchanged. To replace the fan module,
remove the Remote Field Controller from the DIN rail.
Section “Replacing the Remote Field Controller” on page 73 describes how to install and
remove the Remote Field Controller.
T T
SE SE
RE RE
+ +
– –
TE TE
MO MO
RE RE
DC DC
V V
PR
G 24 PR
G 24
S S
Ord.No.: 27 30 20 0
Ord.No.: 27 30 20 0
BU BU
RFC 450 ETH-IB
RFC 450 ETH-IB
ER ER
INT INT
6219A052
Figure A-12 Replacing the fan module

A3 Replacing the Parameterization Memory

Please follow the instructions below if it becomes necessary to replace the parameterization
memory:
1. Disconnect the power supply of the Remote Field Controller.
CAUTION:
The parameterization memory must not be removed or inserted during normal operation.
First disconnect the power supply of the Remote Field Controller.
2. Remove the parameterization memory.
10
/10
LIN
K
TR
AF
RU
N
SY
SF
AIL CO
FC M1
RU
N
FC
D BG
I/O
Ord.No.: 27 30 20 0
RFC 450 ETH-IB
RE
SE
T
PR
G
RE
MO
TE
INT
ER
BU
S
6219B028
Figure A-13 Removing the parameterization memory
Press lightly on the ejector to release the parameterization memory, which you can then
remove by pulling it towards you.

Updating the Firmware
3. Insert a new parameterization memory.
FC
/PRRUN
OG
FC
RU
N
ST
OP
FC
R ES
RU
N
SY
SF
AIL
FC
RU
N
FC
D BG
ard
yC
Ord.No.: 27 30 20 0
RFC 450 ETH-IB
RE
r
mo
Me
PR
G
sh
Fla
RE
MO
6219B005
Figure A-14 Inserting the parameterization memory
Before inserting the new parameterization memory, you can write the name of the project
file to be stored on the memory in the labeling field.
Insert the parameterization memory into the card holder provided with the female connector
to the front. Make sure that when the parameterization memory is pressed lightly, the ejector
moves outward and engages with a click.
NOTE:
Only use parameterization memories from Phoenix Contact:
4. Reconnect the power supply of the Remote Field Controller.
A4 Updating the Firmware

The firmware is software that is permanently installed in the Remote Field Controller
(operating system, etc.). It is stored in a memory block that protects it in the event of a power
failure. The firmware can be updated using the PRG serial diagnostic and configuration
interface (for connection to a PC).
A firmware update is used exclusively for the addition of new functions. For example, new
functions can be implemented in the firmware within the scope of continuous product
improvement. The firmware does not need to be updated for normal system operation.
If necessary, please contact your Phoenix Contact representation.

A5 Connecting Cable
A 5.1 Connection to INTERBUS

Connect the remote bus cable to the remote bus interface of the Remote Field Controller
using a 9-pos. D-SUB female connector. An adapter for converting to fiber optics as the
transmission medium can be connected in the same way. The following pages provide
additional information about connector assembly and fiber optic connection options.
A 5.2 D-SUB Male Connector for Soldering

Designation: IBS DSUB 9/L, Order No. 2758473
20 mm
(0.79 in.)
8 mm (0.32 in.)
3 mm (0.12 in.)
Strain relief
Solder Remote bus cable (D9/D9) Solder

side side
DO 6 Green 6 DO
DO 1 Yellow 1 DO
1 6 6 1
DI 7 Pink 7 DI
DI 2 Gray 2 DI
5 9 COM 3 Brown 3 COM 9 5
5 Strain
9 relief
Strain 9-pos. D-SUB
relief female connector
9-pos. D-SUB
male connector 6219A030
Figure A-15 Remote bus cable with D-SUB male connector for soldering

Connecting Cable
1. Strip 20 mm off the cable sheath and shorten the braided shield to 8 mm.
Strip 3 mm off the wire ends, and solder the signal lines according to Figure A-15.
2. Fold the braided shield uniformly back over the cable sheath.
3. Clamp the shield under the strain relief so that a conductive connection to the metal-
plated connector housing is created.
Make sure to only use metal-plated connectors from Phoenix Contact.
A 5.3 D-SUB Male Connector for Screwing

Designation: SUBCON 9/M-SH, Order No. 2761509
1 50 mm (1.97 in.)
10 mm
(0.39 in.)
2 5 mm (0.20 in.)
3
1
6
6
2
7
7
8
3
9
8
4
9
5
1
2
3
4
5
Strain relief
Remote bus cable (SUBCON 9/SUBCON 9)

DO 6 Green 6 DO
DO 1 Yellow 1 DO
DI 7 Pink 7 DI
DI 2 Gray 2 DI
COM 3 Brown 3 COM
5 Strain
9 relief
Strain 9-pos. SUBCON
relief female connector
9-pos. SUBCON
male connector 6219A031
Figure A-16 Remote bus cable with D-SUB male connector for screwing
1. Strip 50 mm off the cable sheath and shorten the braided shield to 10 mm.
Strip 5 mm off the wire ends, and solder the signal lines according to Figure A-16.
2. Fold the braided shield uniformly back over the cable sheath.
3. Clamp the shield under the strain relief so that a conductive connection to the metal-
plated connector housing is created.

A 5.4 Fiber Optic Connector for Plastic/Polymer Fibers

Designation: IBS OPTOSUB-MA/M/R-LK
Ord.No.:
RFC 4
RE
MO
TE
INT
ER
BU +
S –
24
V
DC
OPT -LK 5 Out

IBS -MA/M/R.: 275012
B
OSU
No
der OrIN
6219A032
Figure A-17 IBS OPTOSUB-MA/M/R-LK cabling
The assembly of the polymer fiber cables is described in the package slips of the following
items and in the Fiber Optic Installation Guidelines:
Ordering data:
– Fiber optic interface connector
IBS OPTOSUB-MA/M/R-LK Order No. 2750125
– F-SMA/4 connector set (with 4 connectors)
PSM-SET-FSMA/4-KT Order No. 2799720
– Polishing set
PSM-SET-FSMA-POLISH Order No. 2799348
– Fiber Optic Installation Guidelines
DB GB IBS SYS FOC ASSEMBLY Order No. 9423439
Refer to the package slip and the Fiber Optic Installation Guidelines when assembling
your own fiber optic cable, or order pre-assembled cables from Phoenix Contact.
The Remote Field Controller supplies the IBS OPTOSUB-MA/M/R-LK connector with
power.
CAUTION:
If the power supply of the Remote Field Controller is switched on when the
IBS OPTOSUB-MA/M/R-LK connector is plugged in, the Remote Field Controller may
carry out a reset. Make sure that the power supply of the Remote Field Controller is
switched off.

Connecting Cable
A 5.5 Fiber Optic Connector for Glass Fibers

You need an interface converter to connect glass fibers to the fiber optic connection, e.g.,
PSI-MOS-RS422/FO 850 E, Order No. 2708355.
Refer to the package slip of the interface converter and the Fiber Optic Installation
Guidelines when assembling your own glass fiber cable, or order pre-assembled cables
from Phoenix Contact.


Useful information about Remote Field Controllers
B Useful information about Remote Field Controllers
B1 RFC 430 ETH-IB – INTERBUS bus configuration
NOTE: Dynamic INTERBUS bus configuration is not supported

Only static bus configuration should be performed for the INTERBUS system connected
to the RFC 430 ETH-IB. This means that each connected INTERBUS device must be
individually mapped in the bus configuration.
For correct operation of the RFC 430 ETH-IB, dynamic bus configuration is not permitted.
The number of INTERBUS devices could be varied in a practical way via a generic bus
device using special function blocks.
B2 Error Causes and Remedies

Table B-1 Error causes and remedies
Error Cause Remedy
The Remote Field Controller cannot be started Polarity of supply voltage re- Reverse polarity of supply voltage.
even though a supply voltage has been provided. versed.
The TRAFFIC LED (green) does not light up Error in the IP configuration. Check the IP address.
when another network device sends PING sig-
A data connection to another net- Check the subnet mask.
nals to the Remote Field Controller.
work device could not be estab-
Check the router IP address.
lished.
The TRAFFIC LED (green) lights up when an- Error in the IP configuration. Check the subnet mask.
other network device sends PING signals to the
Check the router IP address.
Remote Field Controller. However, there is no re-
sponse to the PING signals.
A program cannot be downloaded by PC Worx. The key switch is not in FCRUN/ Change the switch position. (Only
PROG position. possible with the administrator
key.)

Table B-2 Error codes in the diagnostic display

Display/Indication Cause Remedy
1422 The Remote Field Controller does not contain the main firm- Please send the Remote Field
ware. Controller to Phoenix Contact.
1430 Checksum error in the main firmware. Please send the Remote Field
1431 Controller to Phoenix Contact.
1433
1434 Checksum error in the main firmware. The firmware download Repeat firmware download.
was not completed correctly.
1435 The Remote Field Controller does not contain the main firm- Repeat firmware download.
ware. The firmware download was not completed correctly.
2112 The IP address has not yet been parameterized or has the value Parameterize the IP address.
"0.0.0.0".
This warning is always issued when using new devices.
2113 An error occurred during transmission of configuration data Repeat the data transmission.
from PC Worx (e.g., connection loss, voltage failure).
2116 Accumulator failure warning Connect the supply voltage and
charge the battery.
2211 Stack overflow in a ProConOS task Increase the stack.
2212 Memory exceeded in an array in ProConOS Check the array access.
Increase the array, if required.
2214 Division by zero in ProConOS task Remove the program error.
2216 Value range exceeded in ProConOS task Remove the program error.
2217 Watchdog of ProConOS task triggered. Remove the program error.
Execution time is too long.
2218 Runtime of the ProConOS task is too long. Remove the program error.
Low-priority tasks no longer have processor capacity.
221D String error Remove the program error.
221E Division by zero in ProConOS task Remove the program error.
or
Watchdog of ProConOS task triggered
Execution time is too long.

Technical Data
C Technical Data
General Data for the RFC 450 ETH-IB

Order designation RFC 450 ETH-IB
Order no. 2730200
Dimensions without fan 124 mm x 185 mm x 190 mm
Dimensions with fan 124 mm x 210 mm x 190 mm
Weight without fan 1550 g, approximately
Weight with fan 1700 g, approximately
Program memory 8 Mbytes
Data memory 16 Mbytes
General Data for the RFC 430 ETH-IB

Order designation RFC 430 ETH-IB
Order no. 2730200
Dimensions without fan 124 mm x 185 mm x 190 mm
Dimensions with fan 124 mm x 210 mm x 190 mm
Weight without fan 1550 g, approximately
Weight with fan 1700 g, approximately
Program memory 2 Mbytes
Data memory 4 Mbytes
Power Supply
Connection Using COMBICON connector
Us 24 V DC
Permissible range 19.2 V DC to 30.0 V DC
Ripple 3.6 Vpp
Power consumption P ≈ 20 W, typical (without direct inputs, outputs)
Protection 5 A, slow-blow
External power supply Only use power supplies without a fall-back characteristic
curve. The power supply must be suitable for use with ca-
pacitive loads.
INTERBUS
Number of I/O points 4096, maximum (firmware version 4.4x or later)
8192, maximum (firmware version 4.6x or later)
Number of data words 256, maximum
Number of bus segments 255, maximum

INTERBUS
Transmission speed 500 kbit/s or 2 Mbit/s
Transmission reliability CR check (hamming distance: 4)
Protocol EN 50254
Number of devices in the INTERBUS system

Total number of bus devices 512, maximum
Number of remote bus devices 254, maximum
Number of PCP devices 62, maximum (firmware version 4.4x or later)
126, maximum (firmware version 4.6x or later)
Number of remote bus levels 16, maximum
Network Interface
Type Ethernet
10Base-T and 100Base-TX
Speed 10 Mbits (10Base-T),
100 Mbits (100Base-TX)
half duplex, full duplex,
auto negotiation
Connection method CAT5 twisted pair cable
RJ45 female connector
INTERBUS Master Interface

Bus connection REMOTE OUT
INTERBUS interface 9-pos. D-SUB female connector
Interface type RS-422
Electrical isolation U = 500 V AC (test voltage)
Diagnostic Interface (PRG)

Connection method 9-pos. D-SUB male connector
Transmission rate 9600 baud or 19200 baud
Electrical isolation No
Freely Programmable COM1 Interface

Connection method 9-pos. D-SUB male connector
Transmission rate 9600 baud or 19200 baud
Electrical isolation No

Technical Data
Direct Inputs
Number 5
Input design According to EN 61131-2 Type 1
Definition of switching thresholds
Maximum low level voltage 5 V DC
Minimum high level voltage 11 V DC
Nominal input voltage 24 V DC
Nominal input current at 24 V 5 mA
Direct Outputs
Number 3
Output design According to EN 61131-2 Type 1
Nominal output voltage 24 V DC
Nominal output current 500 mA
Optical Diagnostics
Ethernet LEDs: LINK, TRAFFIC
INTERBUS Diagnostic display
IEC 61131 runtime system Additional LCD arrows: FCRUN, FCDBG
IEC 61131 Runtime System

Speed
RFC 450 ETH-IB t = 0.05 ms (for 1 K mix instructions)
RFC 430 ETH-IB t = 0.1 ms (for 1 K mix instructions)
Shortest cycle time t min = 1 ms
Number of control tasks 16
Memory for retentive data 96 Kbytes NVRAM
Realtime Clock
Precision 18 seconds per week
Power reserve 120 days

Fan Module
Number of fans 2
Storage Ball bearing
Speed monitoring Yes
Life 50000 h at an ambient temperature of 25 °C
At an ambient temperature of 45 °C or higher the Remote Field Controller must be operated with the base-
mountable fan module.
Ambient Conditions
Temperature (According to EN 60204-1)
Operation (without fans) 0 °C to +45 °C
Operation (with fan module) 0 °C to +55 °C
Storage and transport -25 °C to +70 °C
Humidity (according to EN 60204-1)
Storage and operation 10 to 95 %, no condensation
Air pressure
Operation 80 kPa to 108 kPa (up to 2000 m above sea level)
Storage and transport 66 kPa to 108 kPa (up to 3500 m above sea level)
Vibration 1.5g, criterion 1 according to IEC 60068-2-6
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 4 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 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 Class A
NOTE: Radio interference

This is a Class A item of equipment. When using the equipment in residential areas, it may cause radio
interference. In this case, the operator may be required to implement appropriate measures and to pay the
resulting costs.

Index
D Index
C Keypad ....................................................................... 30
Communication paths ................................................. 17

Set................................................................... 44, 56 M
Configuration Main memory .............................................................. 40
Read connected configuration............................... 48 Overall reset .......................................................... 40
Connecting cable ........................................................ 80 Mounting ..................................................................... 16
Assembling............................................................ 80
Fiber optic cable .................................................... 82 P
Parameterization memory ........................................... 26
D Replacing .............................................................. 78
Diagnostic display ....................................................... 30 PC Worx 2................................................................... 41
Direct inputs ................................................................ 25 PC Worx 3................................................................... 54
Direct outputs.............................................................. 25 Power supply .............................................................. 28
Connect................................................................. 29
E Project
Create ............................................................. 41, 54
Ethernet connection .................................................... 18
F R
Reset button ............................................................... 30
Fan module
Mounting ............................................................... 15
Replacing .............................................................. 77 S
Field Controller Safety measures ......................................................... 65
Replacing .............................................................. 73 Startup .................................................................. 50, 63
Firmware Status and diagnostic indicators (Ethernet)................. 14
Update................................................................... 79 SYSTEM WORX ......................................................... 41
Function blocks ........................................................... 21
G
Gap when mounting .................................................... 16
I
Interfaces
Diagnostics............................................................ 19
Ethernet................................................................. 18
Freely programmable ............................................ 20
INTERBUS ............................................................ 26
IP address
Set................................................................... 32, 46
K
Key switch................................................................... 38
Setting the operating modes.................................. 38


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 general 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 are 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 93 / 94
94
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
PHOENIX CONTACT Development and Manufacturing, Inc.
586 Fulling Mill Road
Middletown, PA 17057
USA
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
94 / 94 PHOENIX CONTACT GmbH & Co. KG • Flachsmarktstraße 8 • 32825 Blomberg • Germany

phoenixcontact.com
© PHOENIX CONTACT 2021-07-22
PHOENIX CONTACT GmbH & Co. KG

Flachsmarktstraße 8
32825 Blomberg, Germany
Phone: +49 5235 3-00
Fax: +49 5235 3-41200
6219_en_05
E-mail: info@phoenixcontact.com
phoenixcontact.com

RFC 430

Uploaded by

Copyright:

Available Formats

RFC 430

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RFC 430

Uploaded by

Copyright:

Available Formats

Installing and Starting Up Remote Field Controllers

With Ethernet Connection

RFC 430/450 ETH-IB UM E, Revision 05 2021-07-22

This user manual is valid for:

Designation Order No.

PHOENIX CONTACT GmbH & Co. KG • Flachsmarktstraße 8 • 32825 Blomberg • Germany

2 Description of the Remote Field Controller ..............................................................................11

6219_en_05 PHOENIX CONTACT 3 / 94

3 Startup Under PC Worx 2 ........................................................................................................41

4 Startup Under PC Worx 3 ........................................................................................................53

5 Safety Measures in Networks ..................................................................................................65

6 System Variables .....................................................................................................................69

A Service and Maintenance .........................................................................................................73

B Useful information about Remote Field Controllers...................................................................85

4 / 94 PHOENIX CONTACT 6219_en_05

6219_en_05 PHOENIX CONTACT 5 / 94

6 / 94 PHOENIX CONTACT 6219_en_05

1.1 Labeling of warning notes

1.2 Qualification of users

6219_en_05 PHOENIX CONTACT 7 / 94

1.3 Purpose of this Manual

RFC 430 ETH-IB: Average control performance

1.4 Hardware and Software Requirements

Description Type Order No. Pcs./Pkt.

8 / 94 PHOENIX CONTACT 6219_en_05

Description Type Order No. Pcs./Pkt.

6219_en_05 PHOENIX CONTACT 9 / 94

10 / 94 PHOENIX CONTACT 6219_en_05

2 Description of the Remote Field Controller

2.1 General Description of the Remote Field Controller

Integrated Ethernet Connection

IEC 61131 Control Performance

6219_en_05 PHOENIX CONTACT 11 / 94

2.2 Unpacking the Remote Field Controller

NOTE: Electrostatic discharge!

12 / 94 PHOENIX CONTACT 6219_en_05

2.3 Connecting and Operating Elements

RFC 450 ETH-IB

NOTE: Electrostatic discharge!

6219_en_05 PHOENIX CONTACT 13 / 94

2.4 Status and Diagnostic Indicators (Ethernet)

14 / 94 PHOENIX CONTACT 6219_en_05

2.5 Fan Module

Figure 2-2 Remote Field Controller with fan module

6219_en_05 PHOENIX CONTACT 15 / 94

2.6 Mounting the Remote Field Controller on the DIN

16 / 94 PHOENIX CONTACT 6219_en_05

2.7 Communication Paths

(A) Ethernet 10/100Base-T(X)

RFC 450 ETH-IB

Figure 2-4 Communication paths: (A) Ethernet (B) RS-232

6219_en_05 PHOENIX CONTACT 17 / 94

2.7.1 Ethernet Connection

Use an Ethernet cable according to CAT 5 of IEEE 802.3.

- 8 RJ45 female connector

Figure 2-5 Ethernet interface 10/100BASE-T

18 / 94 PHOENIX CONTACT 6219_en_05

2.7.2 Diagnostic Interface (PRG)

Figure 2-7 Cable between PC and Remote Field Controller