Phoenix Contact RFC 4072R User manual

User manual
Installing and operating the RFC 4072R
Remote Field Controller

2022-01-25
PHOENIX CONTACT GmbH & Co. KG • Flachsmarktstraße 8 • 32825 Blomberg • Germany
phoenixcontact.com
110146_en_00
Installing and operating the RFC 4072R Remote Field Controller
This manual is valid for:
Designation Item No.
RFC 4072R 1136419
User manual
UM EN RFC 4072R, Revision 00

Table of contents
110146_en_00 PHOENIX CONTACT 3 / 128
Table of contents
1 For your safety ...........................................................................................................................7
1.1 Identification of warning notes ............................................................................... 7
1.2 Qualification of users ............................................................................................. 7
1.3 Field of application of the product.......................................................................... 8
1.3.1 Intended use ..........................................................................................8
1.3.2 Product changes .................................................................................... 8
1.4 Safety notes .......................................................................................................... 8
1.5 Security in the network .......................................................................................... 9
2 Transport, storage, and unpacking ..........................................................................................10
2.1 Transport............................................................................................................. 10
2.2 Storage................................................................................................................ 10
2.3 Unpacking ........................................................................................................... 10
3 The redundant control system .................................................................................................12
3.1 General description ............................................................................................. 12
3.2 System behavior and redundancy status............................................................. 14
3.2.1 Ideal typical system behavior ............................................................... 14
3.2.2 System behavior in the event of no synchronization connec-
tion ....................................................................................................... 15
3.2.3 System behavior on switching the PRIMARY controller to the
STOP operating mode .........................................................................15
3.2.4 “FollowUp Sync” redundancy status: Causes ...................................... 15
3.2.5 “No Sync” redundancy status: Causes ................................................. 15
3.2.6 “SingleMode” redundancy status: Cause ............................................. 16
3.3 Causes of switch-over ......................................................................................... 17
4 Description of the controller .....................................................................................................18
4.1 General description of the controller.................................................................... 18
4.2 Licensing information on open-source software .................................................. 20
4.3 Requesting the source code................................................................................ 20
4.4 Hardware and software requirements.................................................................. 21
4.5 Directory structure of the file system.................................................................... 22
4.6 Using SFTP to access the file system.................................................................. 22
4.7 Firewall ................................................................................................................ 23
4.8 Components of the controller ..............................................................................24
4.8.1 Connection and operating elements .................................................... 24
4.8.2 Information on the label ........................................................................ 25
4.9 Diagnostic and status indicators.......................................................................... 26

RFC 4072R
4 / 128 PHOENIX CONTACT 110146_en_00
4.10 Fan module .........................................................................................................27
4.11 Touch screen display........................................................................................... 28
4.11.1 Operating the display and navigating the menus ................................. 29
4.11.2 Home menu ......................................................................................... 30
4.11.3 “CONFIG DETAILS” menu ................................................................... 31
4.11.4 “PLCnext” menu ................................................................................... 49
4.11.5 “PN Control” menu ............................................................................... 51
4.11.6 “OPC UA” menu ................................................................................... 54
4.11.7 “Redundancy” menu ............................................................................ 56
4.12 Interfaces............................................................................................................. 63
4.12.1 USB ..................................................................................................... 63
4.12.2 Ethernet ............................................................................................... 64
4.12.3 SYNC interface .................................................................................... 67
4.13 Mode selector switch........................................................................................... 68
5 Mounting hardware ..................................................................................................................69
5.1 Safety notes ........................................................................................................ 69
5.2 Mounting the fan module ..................................................................................... 70
5.3 Mounting the controller........................................................................................ 72
5.4 Inserting the SD card........................................................................................... 74
6 Connecting and wiring the hardware ........................................................................................75
6.1 Power supply....................................................................................................... 75
6.1.1 Sizing of the power supply ................................................................... 75
6.1.2 Wiring and connecting the power supplies ........................................... 76
6.2 Connecting the USB flash drive........................................................................... 77
6.3 Connecting Ethernet............................................................................................ 78
6.4 Connecting the SFP module and FO cables........................................................ 79
7 Startup .....................................................................................................................................81
7.1 Startup steps on the device ................................................................................. 81
7.1.1 Preparing the first controller ................................................................. 81
7.1.2 Preparing the second controller ........................................................... 82
7.1.3 Preparing the controller for “SingleMode” ............................................ 82
7.2 Startup with PLCnext Engineer............................................................................ 83
7.2.1 Installing PLCnext Engineer ................................................................. 83
7.2.2 User interface ...................................................................................... 84
7.2.3 Creating a new project .........................................................................86
7.2.4 Setting the IP address range ................................................................ 88
7.2.5 Optional: Setting (system) IP addresses .............................................. 89
7.2.6 Connecting to the PRIMARY controller ................................................ 92
7.2.7 Further startup steps ............................................................................ 95

Table of contents
110146_en_00 PHOENIX CONTACT 5 / 128
7.2.8 Special features ................................................................................... 95
8 System variables and status information ..................................................................................98
9 Web-based management (WBM) ............................................................................................99
10 Removing hardware ...............................................................................................................100
10.1 Safety notes ...................................................................................................... 100
10.2 Removing the supply connectors ...................................................................... 100
10.3 Removing the USB flash drive........................................................................... 101
10.4 Removing the Ethernet connectors ................................................................... 102
10.5 Removing the FO cables ................................................................................... 102
10.6 Removing the SFP module................................................................................ 103
10.7 Removing the SD card....................................................................................... 104
10.8 Removing the controller..................................................................................... 105
10.9 Removing the fan module.................................................................................. 105
11 Device replacement, device defects, and repairs ..................................................................106
11.1 Device replacement........................................................................................... 106
11.1.1 Replacing the controller ..................................................................... 106
11.1.2 Replacing the fan module .................................................................. 107
11.1.3 Replacing the SD card ....................................................................... 107
11.2 Device defects and repairs................................................................................ 108
12 Maintenance, decommissioning, and disposal ......................................................................109
12.1 Maintenance...................................................................................................... 109
12.2 Decommissioning and disposal......................................................................... 109
13 Troubleshooting .....................................................................................................................110
14 Ordering data and technical data ...........................................................................................113
14.1 Ordering data .................................................................................................... 113
14.2 Technical data................................................................................................... 114
A Appendix ................................................................................................................................118
A 1 Updating the firmware via the shell.................................................................... 118
A 2 Shell commands for controlling the firmware..................................................... 118
A 3 Replacing the HTTPS certificate........................................................................ 118

RFC 4072R
6 / 128 PHOENIX CONTACT 110146_en_00
B Appendix for document lists....................................................................................................119
B 1 List of figures ..................................................................................................... 119
B 2 List of tables ...................................................................................................... 123
B 3 Index.................................................................................................................. 124

For your safety
110146_en_00 PHOENIX CONTACT 7 / 128
1 For your safety
Read this user manual carefully and keep it for future reference.
1.1 Identification of warning notes
1.2 Qualification of users
The use of products described in this user 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 stan-
dards and other regulations.
– Qualified application programmers and software engineers. The users must be familiar
with the relevant safety concepts of automation technology as well as applicable stan-
dards and other regulations.
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 warns the reader of actions that
might cause property damage or a malfunction.
Here you will find additional information or detailed sources of information.

RFC 4072R
8 / 128 PHOENIX CONTACT 110146_en_00
1.3 Field of application of the product
1.3.1 Intended use
The RFC 4072R Remote Field Controller is a high-performance controller with redundancy
function. The RFC 4072R has IP20 protection class and is designed for use in closed con-
trol cabinets or control boxes (junction boxes) with IP54 degree of protection or higher.
The device is designed for use in industrial environments.
1.3.2 Product changes
Modifications to hardware and firmware of the device are not permitted.
Incorrect operation or modifications to the device can endanger your safety or damage the
device. Do not repair the device yourself. If the device is defective, please contact
Phoenix Contact.
1.4 Safety notes
• Observe the country-specific installation, safety, and accident prevention regulations.
NOTE: Electrostatic discharge
Electrostatic discharge can damage or destroy components. When handling the de-
vice, observe the necessary safety precautions against electrostatic discharge (ESD)
in accordance with EN 61340-5-1 and IEC 61340-5-1.
NOTE: Property damage due to incorrect use
The IP20 degree of protection (IEC 60529/EN 60529) requires that the device be
used in a clean and dry environment. Using the device in an environment that is out-
side of the specified limits may cause damage to the device.
• Do not subject the device to mechanical and/or thermal stress that exceeds the
specified limits.
NOTE: Device failure due to foreign objects in device
Foreign objects in the device can lead to malfunctions or even device failure.
• Ensure that no foreign objects find their way into the device (e.g., into the vents).
NOTE: Device failure if operated outside the permitted ambient temperature
range
Operating the device in ambient temperatures that are not within the permitted range
may lead to malfunctions or even device failure.
• Ensure that the device is operated within the permitted ambient temperature range,
see Section 14.2.

For your safety
110146_en_00 PHOENIX CONTACT 9 / 128
NOTE: Device failure due to vibrations and shock levels above the permitted
specifications during operation
If the device is subjected to vibrations and shock levels above the permitted specifi-
cations during operation, this may lead to malfunctions or even device failure.
• Ensure that the permitted specifications for vibrations and shocks are adhered to
when operating the device, see Section 14.2.
1.5 Security in the network
NOTE: Risk of unauthorized network access
Connecting devices to a network via Ethernet always entails the risk of unauthorized
access to the network.
Therefore, please check for the option of disabling active communication channels in
your application (e.g., FTP, DCP, HTTP, HTTPS, etc.) or setting passwords to prevent
third parties from accessing the controller without authorization and modifying the sys-
tem.
Due to its communication interfaces, the controller should not be used in safety-critical
applications unless additional security appliances are used.
Please take additional precautions in accordance with the IT security requirements
and standards applicable to your application (e.g., virtual networks (VPN) for remote
maintenance access, firewalls, etc.) to prevent unauthorized network access.
On first request, you shall release Phoenix Contact and the companies associated
with Phoenix Contact GmbH & Co. KG, Flachsmarktstraße 8, 32825 Blomberg, Ger-
many in accordance with §§ 15 ff AktG (German Stock Corporation Act), hereinafter
collectively referred to as “Phoenix Contact”, from all third-party claims made due to
improper use.
For the protection of networks for remote maintenance via VPN, Phoenix Contact of-
fers the mGuard product range of security appliances, a description of which is pro-
vided in the latest Phoenix Contact catalog (phoenixcontact.net/products).
Additional measures for protection against unauthorized network access are listed in
the AH EN INDUSTRIAL SECURITY application note. The application note can be
downloaded at phoenixcontact.net/product/1136419.

RFC 4072R
10 / 128 PHOENIX CONTACT 110146_en_00
2 Transport, storage, and unpacking
2.1 Transport
The device is delivered in cardboard packaging.
• Only transport the device to its destination in its original packaging.
• Observe the instructions on how to handle the package, as well as the moisture, shock,
tilt, and temperature indicators on the packaging.
• Observe the humidity specifications and the temperature range specified for transport
(see Section 14.2).
• Protect the surfaces as necessary to prevent damage.
• When transporting the equipment or storing it temporarily, make sure that the surfaces
are protected against the elements and any external influences, and that they are kept
clean and dry.
2.2 Storage
The storage location must be:
– Dry
– Protected from unauthorized access
– Protected from harmful environmental influences such as UV light
– Temperature range: -25°C ... +70°C
– Air pressure: 58 kPa ... 108 kPa (up to 4500 m above mean sea level)
– Permissible humidity: 5% ... 95% (in accordance with DIN EN 61131-2)
2.3 Unpacking
The device is delivered in packaging together with a packing slip that provides installation
instructions.
• Read the complete packing slip carefully before unpacking the device.
NOTE: Electrostatic discharge
Electrostatic discharge can damage or destroy components. When handling the de-
vice, observe the necessary safety precautions against electrostatic discharge (ESD)
in accordance with EN 61340-5-1 and IEC 61340-5-1.
NOTE: Property damage due to noncompliance with ESD notes
If the ESD notes are not observed during unpacking and packing, the device may be-
come damaged.
• Observe the ESD notes during unpacking and packing.

Transport, storage, and unpacking
110146_en_00 PHOENIX CONTACT 11 / 128
Checking the delivery • Check the delivery for transport damage.
Damaged packaging is an indicator of potential damage to the device that may have oc-
curred during transport. This could result in a malfunction.
• Submit claims for any transport damage immediately, and inform Phoenix Contact or
your supplier as well as the shipping company without delay.
• Enclose photos that clearly document the damage to the packaging and/or delivery to-
gether with your claim.
• Immediately upon delivery, refer to the delivery note to ensure that the delivery is com-
plete.
Scope of supply – RFC 4072R Remote Field Controller
– 2 x FKCN 2,5/ 3-STF-5,08 BK supply connector

RFC 4072R
12 / 128 PHOENIX CONTACT 110146_en_00
3 The redundant control system
3.1 General description
A redundant control system with two RFC 4072R controllers enables you to ensure uninter-
rupted processes in complex systems and large plants.
Figure 3-1 Redundant control system with two RFC 4072R controllers
Features – Easy startup and automatic configuration of all redundancy functions
– Distance of up to 10 km between the controllers via FO
– Uninterrupted process – even in the event of failure or when a controller is replaced
– Display for displaying status and error messages in plain text
– Redundancy for your Ethernet network, thanks to device integration in accordance with
the PROFINET standard
– Redundant power supply
Structure To create a redundant control system, connect two RFC 4072R controllers together via SFP
(small form-factor pluggable) modules using a FO cable. The coupled RFC 4072R control-
lers are synchronized with each other via the device’s internal SYNC interface (synchroni-
zation connection).
Startup Prior to startup, assign redundancy type “First” to one of the controllers and redundancy
type “Second” to the other controller. The redundancy types do not change during opera-
tion. During initial startup, the redundancy role PRIMARY is automatically assigned to the
controller with redundancy type “First” and the redundancy role BACKUP is assigned to the
controller with redundancy type “Second”. The redundancy roles of the controllers can
change during operation.
For startup, program the controller that manages the process (PRIMARY controller). The
BACKUP controller will be started up automatically.
PLCnext Control
Ord.No. 1136419RFC 4072R
+
-
24VD
X2 X1
LAN
LAN
LAN
ACT
ACTACT
SYNC
ACT
12
3.1 3.2
LAN
www.plcnext-community.net
RUN/PROG
STP
MRESET
SD-CARD
USB
LNK LNK
LNKLNK
PLCnext Control
Ord.No. 1136419RFC 4072R
+
-
24VD
X2 X1
LAN
LAN
LAN
ACT
ACTACT
SYNC
ACT
12
3.1 3.2
LAN
www.plcnext-community.net
RUN/PROG
STP
MRESET
SD-CARD
USB
LNK LNK
LNK
LNK

The redundant control system
110146_en_00 PHOENIX CONTACT 13 / 128
Function The two controllers establish a high-performance synchronization connection via the SYNC
interface. Before each cycle, the PRIMARY controller transmits the data that is to be syn-
chronized to the BACKUP controller.
If one of the controllers fails, the other controller takes over the control tasks without inter-
ruption.
Data synchronization
times
The time required to synchronize the data between the PRIMARY and BACKUP controllers
depends on the amount of redundancy data that needs to be synchronized:
The amount of redundancy data represents the sum data of all variables marked as redun-
dant in PLCnext Engineer (see Figure 3-2).
Figure 3-2 Marking a variable as redundant in PLCnext Engineer
Recommended:
• For the cyclic task “SyncTask”, set a cycle time as follows:
Cycle time = Data synchronization time + 5 ms
This ensures that the entire amount of redundancy data is sent to the BACKUP con-
troller in each cycle.
Table 3-1 Data synchronization time depending on the amount of redundancy data
Amount of redundancy data Data synchronization time
32 MB 1265 ms
16 MB 635 ms
8 MB 320 ms
4 MB 160 ms
2 MB 80 ms
1 MB 40 ms
512 kB 20 ms
256 kB 10 ms
128 kB 5 ms
64 kB 5 ms
32 kB 5 ms

RFC 4072R
14 / 128 PHOENIX CONTACT 110146_en_00
3.2 System behavior and redundancy status
The sections below provide information on the behavior of the redundant control system as
well as changing the redundancy status of the control system and the controllers.
Information on the redundancy status is shown on the touch screen display of the controller,
see Section 4.11.7.
3.2.1 Ideal typical system behavior
Figure 3-3 shows the ideal typical system behavior of the redundant control system during
error-free startup of the controllers.
Figure 3-3 Ideal typical system behavior
First Second
Sync HotStandBy (HSBY)
No Sync
BACKUP-Controller
PRIMARY-Controller
Basic Sync
FollowUp Sync
Set redundancy type
No synchronization
Synchronization connec-
tion is active
PLCnext application is
synchronized
Redundancy functionality
is active
Establish synchronization
connection
Download
PLCnext application
HSBY conditions are met
(Section 4.11.7)

The redundant control system
110146_en_00 PHOENIX CONTACT 15 / 128
3.2.2 System behavior in the event of no synchronization con-
nection
If the synchronization connection via the SYNC interface is interrupted during runtime, con-
nection monitoring is performed at Ethernet interface LAN1. The redundant control system
switches to “Basic Sync” redundancy status.
3.2.3 System behavior on switching the PRIMARY controller to
the STOP operating mode
When you switch the PRIMARY controller to the STOP operating mode from
PLCnext Engineer or via the mode selector switch, this will not cause the redundancy roles
to be switched over. The PRIMARY controller and the BACKUP controller both switch to the
STOP operating mode.
3.2.4 “FollowUp Sync” redundancy status: Causes
Section 3.2.4.1 to Section 3.2.5.5 show what causes the redundant control system to switch
to the “FollowUpSync” redundancy status.
3.2.4.1 No redundancy variables in the PLCnext Engineer application
The PLCnext Engineer application does not contain any redundant variables (“Redundant”
check box has not been enabled for any variables).
The PLCnext Engineer application is synchronized between the PRIMARY and BACKUP
controllers; the redundant control system remains in the “FollowUp Sync” state.
3.2.4.2 Configured PROFINET devices cannot be reached
Some of the configured PROFINET devices in the PLCnext Engineer application cannot be
reached.
The PLCnext Engineer application is synchronized between the PRIMARY and BACKUP
controllers; the redundant control system remains in the “FollowUp Sync” state.
3.2.5 “No Sync” redundancy status: Causes
3.2.5.1 No redundancy type
One of the controllers has not been assigned a redundancy type. The controller has the re-
dundancy type “None”. The redundant control system remains in the “No Sync” state.
3.2.5.2 Duplicate assignment of the redundancy type
Both controllers have been assigned the same redundancy type (“First” or “Second”). The
redundant control system remains in the “No Sync” state.
3.2.5.3 Duplicate assignment of the redundancy role
Both controllers have the same redundancy role (PRIMARY or BACKUP). The redundant
control system remains in the “No Sync” state until the role conflict is automatically resolved.

RFC 4072R
16 / 128 PHOENIX CONTACT 110146_en_00
3.2.5.4 SD card of the PRIMARY controller removed during runtime
If you remove the SD card of the PRIMARY controller during runtime, while the redundant
control system is in the “Sync/HSBY” state, the PRIMARY controller will be restarted auto-
matically. The PRIMARY controller cannot be initialized successfully if an SD card is not in-
serted. The roles are switched over: The BACKUP controller becomes the PRIMARY con-
troller and switches to the “No Sync” state.
3.2.5.5 SD card of the BACKUP controller removed during runtime
If you remove the SD card of the BACKUP controller during runtime, the BACKUP controller
will be restarted automatically. The BACKUP controller cannot be initialized successfully if
an SD card is not inserted. The PRIMARY controller switches to the “No Sync” state.
3.2.5.6 No connection
If there is no synchronization connection via the SYNC interface and also no connection via
Ethernet interface LAN1, both controllers switch to the “No Sync” state.
3.2.5.7 Missing remote controller
One of the controllers initialized successfully. The second controller is missing or is not yet
fully initialized. The controller that is already initialized switches to the “No Sync” state.
3.2.6 “SingleMode” redundancy status: Cause
Both controllers have the redundancy type “None”. The redundant control system is in the
“SingleMode” state. The redundancy functionality is deactivated.

The redundant control system
110146_en_00 PHOENIX CONTACT 17 / 128
3.3 Causes of switch-over
The redundancy role of the controllers (PRIMARY or BACKUP) determines which of the two
controllers manages the process.
Table 3-2 shows what causes the redundancy roles to be switched over. Each cause has a
defined code.
The most recent cause of a switch-over is indicated in PLCnext Engineer as a digit in the
RDNCY_LAST_SWITCH_OVER_REASON system variable (see column 1 in Table 3-2). In
addition, the most recent cause of a switch-over is displayed in PLCnext Engineer in the
“Cockpit” editor (“Redundancy Status” view, “Switch Over Reason”).
Table 3-2 Causes of switch-over
Digit Display in the “Cockpit” edi-
tor
Description
0 None No switch-over of the redundancy role since
the last time the PRIMARY controller was re-
started.
1 FirmwareService The redundancy role was changed by the
user.
2 RuntimeException A runtime error occurred on the PRIMARY
controller.
3 LinkDownPnLan The physical network connection to Ethernet
interface LAN1 was disconnected (LNK LED:
off).
4 AllArsLost The PROFINET controller has lost the connec-
tion to all PROFINET devices via Ethernet in-
terface LAN1.
5 ArLost The PRIMARY controller has lost the connec-
tion to at least one PROFINET device.
6 SystemShutdown The firmware of the PRIMARY controller was
stopped by the user.
7 SystemTerminate The firmware of the PRIMARY controller was
stopped due to an operating system exception
that occurred.
8 PowerDown The PRIMARY controller was disconnected
from the power supply.
9 SyncLinkTimeout A timeout occurred on the SYNC interface and
on Ethernet interface LAN1.
10 InternalError An internal error occurred.

RFC 4072R
18 / 128 PHOENIX CONTACT 110146_en_00
4 Description of the controller
4.1 General description of the controller
The RFC 4072R is a high-performance controller with redundancy function.
Programming The controller can be programmed using the PLCnext Engineer automation software. For
this purpose, the IEC 61131-3 programming languages FBD/LD, ST, and SFC, as well as
suitable editors, are available in PLCnext Engineer.
SYNC interface An SFP module can be connected to the SYNC interface (synchronization interface) in
order to connect two RFC 4072R controllers via fiber optics (FO) and thus create a redun-
dant control system. The coupled RFC 4072R controllers are synchronized with each other
via the SYNC interface.
Ethernet interfaces The controller features four Ethernet interfaces for TCP/IP / UDP/IP communication within
the Ethernet network. Two of the Ethernet interfaces are switched internally.
System IP addresses You can always reach the controller that manages the process (PRIMARY controller) via the
system IP addresses of Ethernet interfaces LAN1, LAN2, LAN3.1, and LAN3.2.
PROFINET controller func-
tionality
The PROFINET protocol can be used via the Ethernet interfaces of the controller. The con-
troller can be used as a PROFINET controller via Ethernet interface LAN1.
For further information on how to integrate the controller as a PROFINET controller,
please refer to the PLCnext Engineer online help.
Web-based management In the web-based management (WBM), you can access static and dynamic controller infor-
mation and modify certain controller settings. To open the WBM, enter the IP address of the
controller in a web browser.
OPC UA server An embedded OPC UA server runs on the controller. It provides controller data in accor-
dance with the OPC UA protocol (currently supported: Data Access). You can use this data
for visualization purposes, for example.
PLCnext Engineer provides various system variables for the OPC UA server.
In order for process data variables to be processed with an OPC UA server, the “OPC”
check box must be enabled for the corresponding variables in the variables worksheet
in PLCnext Engineer.
USB interface The controller has a USB 3.0 type A interface. The USB interface has no function at present.

Description of the controller
110146_en_00 PHOENIX CONTACT 19 / 128
SD card The controller requires an SD card to operate.
You can save programs and configurations belonging to your project, e.g., the visualization
project, on the SD card.
The SD card is not supplied as standard with the controller.
• Only use an SD card provided by Phoenix Contact (see Section “Ordering data” on
page 113).
Data buffering/backup in
the event of voltage fail-
ures
In the event of a supply voltage failure, the controller saves control data, e.g., retain data and
log files, on the SD card.
Visualization You can create visualizations for the controller using the HMI integrated in
PLCnext Engineer.
Real-time clock In the event of a supply voltage failure, the real-time clock integrated in the controller is buff-
ered, see Section “Technical data” on page 114.
Function extensions with
PLCnext apps
You can easily extend the scope of functions of the controller with apps from the PLCnext
Store.
Visit the PLCnext Store at plcnextstore.com.
Please note:
Installed apps are not synchronized between the PRIMARY and BACKUP controllers.
If you wish to continue using the apps after replacing a device (see Section 11.1.1,
“Replacing the controller”), you need to install the apps again.

RFC 4072R
20 / 128 PHOENIX CONTACT 110146_en_00
4.2 Licensing information on open-source software
The controller works with a Linux operating system.
License information for the individual Linux packages can be found in the file system of the
controller under:
/usr/share/common-licenses
Information on the directory structure of the file system can be found in Section 4.5.
Alternatively, you can access the license information via the web-based management
of the controller, see Section 9.
Notes on LGPL software li-
braries
All open-source software used in the product is subject to the respective license terms that
are not affected by the Phoenix Contact Software License Terms (SLT) for the product. In
particular, the license holder can change the respective open-source software in accor-
dance with the applicable license terms. If the license holder wishes to change an LGPL
software library contained in this product, reverse engineering is permitted for debugging
such modifications.
Notes on OpenSSL This product includes software developed by the OpenSSL Project for use in the OpenSSL
Toolkit. (http://www.openssl.org/).
This product includes cryptographic software written by Eric Young ([email protected]).
4.3 Requesting the source code
The controller contains software components that are licensed by the rights holder as free
software or open-source software under the GNU General Public License.
You can request the source code of these software components in the form of a CD- or
DVD-ROM for a processing fee of 50 euros within three years after delivery of the controller.
To do so, contact the Phoenix Contact After Sales Service in writing at the following ad-
dress:
PHOENIX CONTACT GmbH & Co. KG
After Sales Service
Flachsmarktstraße 8
32825 Blomberg
GERMANY
Subject: “Source code for RFC 4072R”