Um en Axc F XT SPLC 1000 109449 en 01
Um en Axc F XT SPLC 1000 109449 en 01
Um en Axc F XT SPLC 1000 109449 en 01
User manual
UM EN AXC F XT SPLC 1000
User manual
Installation and operation of the left-alignable
AXC F XT SPLC 1000 safety-related controller
Table of contents
1 For your safety ............................................................................................................................ 9
1.1 Identification of warning notes ............................................................................... 9
1.2 Qualification of users ............................................................................................. 9
1.3 Information about this user manual........................................................................ 9
1.3.1 Purpose of this user manual ................................................................... 9
1.3.2 Validity of the user manual ................................................................... 10
1.4 Information on Open source software licenses and
requesting source code ....................................................................................... 10
1.5 General safety notes............................................................................................ 11
1.6 Field of application of the product........................................................................ 13
1.6.1 Intended use ........................................................................................ 13
1.6.2 Foreseeable misuse ............................................................................. 14
1.6.3 Product changes .................................................................................. 14
1.6.4 Note on security ................................................................................... 14
1.7 Safety notes ........................................................................................................ 15
1.8 Electrical safety ................................................................................................... 16
1.9 Safety of the machine or system.......................................................................... 17
1.10 Standards and directives..................................................................................... 18
1.11 Documentation ................................................................................................... 18
1.12 System requirements (hardware and software) ................................................... 20
1.13 Abbreviations used.............................................................................................. 21
1.14 Safety hotline....................................................................................................... 22
4 Mounting hardware...................................................................................................................51
4.1 Safety notes .................................................................................................... 51
4.2 Basic information................................................................................................. 52
4.3 Structure of an Axioline F station ......................................................................... 54
4.4 Mounting the SPLC 1000..................................................................................... 55
4.4.1 Removing the PLCnext Control supply connector ................................ 56
4.4.2 Removing other connectors from the PLCnext Control ........................ 57
4.4.3 Unlatching electronics modules ........................................................... 57
4.4.4 Mounting the bus base modules .......................................................... 58
4.4.5 Snapping on electronics modules ........................................................ 60
4.4.6 Connecting connectors to the PLCnext Control device ........................ 60
4.4.7 Connecting the supply connector ......................................................... 60
9 Removing hardware................................................................................................................153
9.1 Safety notes ................................................................................................... 153
9.2 Removing cables............................................................................................... 154
9.3 Removing the connector.................................................................................... 154
9.4 Unlatching the SPLC 1000 ................................................................................ 155
9.5 Removing the bus base module ........................................................................ 155
It also describes how the AXC F XT SPLC 1000 is integrated into the software tools listed in
Section “System requirements (hardware and software)” on page 20.
This information will enable you to use the device in accordance with your requirements.
Please note:
Information on the following subjects is available in the UM EN AXL F X152 user manual:
– Licensing information on Open source software
– Requesting the source code
– Web-based management system of the PLCnext Control device used
Qualified personnel In the context of the use of the PROFIsafe system, the following operations may only be car-
ried out by qualified personnel:
– Planning
– Configuration, parameterization, programming
– Installation, commissioning, servicing
– Maintenance, decommissioning
This user manual is therefore aimed at:
– Qualified personnel who plan and design safety equipment for machines and systems
and are familiar with regulations governing occupational safety and accident preven-
tion.
– Qualified personnel who install and operate safety equipment in machines and sys-
tems.
In terms of the safety notes in this user manual, qualified personnel are persons who, be-
cause of their education, experience and instruction, and their knowledge of relevant stan-
dards, regulations, accident prevention, and service conditions, have been authorized to
carry out any required operations, and who are able to recognize and avoid any possible
dangers.
Documentation You must observe all information and especially all safety notes in this user manual as well
as in the documents listed in Section “Documentation” on page 18.
Safety of personnel and The safety of personnel and equipment can only be assured if the SPLC 1000 is used cor-
equipment rectly (see Section “Intended use” on page 13).
Error detection Depending on the wiring and the parameterization of the safe input/output devices, the
PROFIsafe system can detect various errors within the safety equipment.
Observe startup behavior The PROFIsafe system and the SPLC 1000 as the central component do not prevent auto-
matic startup/restart of the safety function. The user must program this independently in the
safety program using the programming software for PROFIsafe (PLCnext Engineer).
After power up of the supply voltage or a software reset, the SPLC 1000 starts immediately
if:
– An SD card with a valid project is inserted in the PLCnext Control or
– A valid project exists on the internal flash memory of the PLCnext Control and
By selecting one of the options “Write and Start Project...” or “Write and Start Project
Changes...”, the safety function becomes active immediately after downloading the
PLCnext Engineer project and following the startup phase of the SPLC 1000 and the
PLCnext Control device. The outputs of the F-Devices and the non-safety-relevant
PROFINET devices can be set in accordance with the programming.
Measures to prevent mis- Take measures to prevent mismatching, polarity reversal, and manipulation of connections.
matching and polarity re-
Observe the country-specific installation, safety, and accident prevention regulations.
versal
NOTE:
The IP20 degree of protection (IEC 60529/EN 60529) of the device is intended for use in
a clean and dry environment. Do not subject the device to mechanical and/or thermal
stress that exceeds the specified limits.
To ensure correct operation, the SPLC 1000 must be installed in a lockable housing or a
lockable control cabinet with a minimum degree of protection of IP54.
Assembly guidelines During installation of the device, observe the sections 4 “Mounting hardware” and
5 “Connecting and wiring the hardware”.
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 specifications
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 13.2.
Direct/indirect contact Protection against direct and indirect contact according to VDE 0100 Part 410
(IEC 60364-4-41) must be ensured for all components connected to the system. In the
event of an error, parasitic voltages must not occur (single-fault tolerance). This also applies
to devices and components with dangerous contact voltages that are permanently con-
nected to the network and/or diagnostic interfaces of the devices used.
This requirement can be met by:
– Using power supplies with safe isolation (PELV)
– Decoupling circuits that are not PELV systems using optocouplers, relays, and other
components that meet the requirements of safe isolation.
Safe isolation Only use devices with safe isolation if dangerous contact voltages can occur at their con-
nections during normal operation or as a result of an insulation error.
Power supply
WARNING: Loss of electrical safety and the safety function when using unsuit-
able power supplies
The SPLC 1000 is designed exclusively for protective extra-low voltage (PELV) operation
in accordance with EN 60204-1. Only protective extra-low voltages in accordance with
the listed standard may be used for the supply.
The following applies to the network (PROFINET and Axioline F) and the I/O devices used
in it:
Only use power supplies that satisfy the requirements of EN 61204-1 and feature safe iso-
lation with PELV in accordance with IEC 61010-2-201 (PELV). They prevent short circuits
between the primary and secondary side.
Insulation rating When selecting the equipment, please take into consideration the dirt and surge voltages
that may occur during operation.
The SPLC 1000 is designed for overvoltage category III (in accordance with
DIN EN 60664-1). If you expect surge voltages in the system, which exceed the values
defined in overvoltage category III, take into consideration additional measures for
voltage limitation.
Installation and configura- Please observe the instructions for installing and configuring the PROFIsafe system (see
tion Section “Documentation” on page 18).
Draw up and implement a In order to use the device described in this document, you must have drawn up an appro-
safety concept priate safety concept for your machine or system. This includes a hazard and risk analysis,
among others, in accordance with the directives and standards specified in Section “Stan-
dards and directives” on page 18, as well as a test report (checklist) for validating the safety
function (see Section “Appendix: Checklists” on page 175).
The target safety integrity level (SIL in accordance with IEC 61508, SIL CL in accordance
with EN 62061 or performance level (and category) in accordance with EN ISO 13849-1) is
ascertained on the basis of the risk analysis. The required safety integrity level ascertained
in this way determines how to use and parameterize the safety-related SPLC 1000 control-
ler within the overall safety function.
Checking hardware and • Carry out a validation every time you make a safety-related modification to your overall
parameterization system.
Use your test report to ensure that:
– The safe PROFIsafe devices (F-Devices) are connected to the correct safe sensors
and actuators.
– The safe input and output devices have been parameterized correctly.
– The variables have been linked to the safe sensors and actuators correctly (single-
channel or two-channel).
1.11 Documentation
The symbol informs you that you have to observe the instructions. Only install and operate
the device once you have familiarized yourself with its properties by means of the user
documentation.
When working on the PROFIsafe system and/or PROFINET its components, you must al-
ways keep this user manual and other items of product documentation to hand and observe
the information therein.
Document Description
PROFIsafe – PROFIsafe System Description For more detailed information on these
– PROFIBUS Guideline, PROFIsafe Policy documents, please refer to Section
– PROFIsafe – Environmental Requirements “Documentation” on page 166.
Guideline Please also observe the relevant
information on PROFINET and
PROFIsafe, which is available on the
Internet at www.profisafe.net and
www.profinet.com.
– User manuals for the PROFIsafe I/O mod- For example, Axioline F,
ules used in your application Axioline Smart Elements.
PROFINET – PROFINET Assembling Guideline For more detailed information on these
– Guideline for PROFIBUS and PROFINET documents, please refer to Section
“Functional Bonding and Shielding of “Documentation” on page 166.
PROFIBUS and PROFINET”
– UM EN PROFINET SYS PROFINET basic principles
– UM EN PROFINET CTRL DEV PROFINET controller/device functions
Software – Online help for the PLCnext Engineer software
PLCnext Technology – PLCnext Info Center Comprehensive documentation for
PLCnext Technology
– plcnext-community.net Information on troubleshooting and
answers to frequently asked questions
(FAQs) in the PLCnext Community
Security – AH EN INDUSTRIAL SECURITY Application note with measures to pro-
tect network-capable devices with
Ethernet connection against unautho-
rized access
Axioline F – UM EN AXL F SYS INST User manual
Axioline F: System and installation
– UM EN AXL F X152 User manual
Installing, commissioning, and operat-
ing the AXC F 1152, AXC F 2152, and
AXC F 3152 controllers
– UM EN AXL SE SYS INST User manual
Axioline Smart Elements
Please note:
The PLCnext Engineer engineering software platform for Phoenix Contact automation
controllers is compliant with IEC 61131-3. Its functionality can be extended with add-ins.
PLCnext Engineer can be used as an editor for programming safety-related user
applications. In this way, F-Devices operated with safety-related controllers with
PLCnext Technology can be configured and started up. PLCnext Engineer is certified
by TÜV-Rheinland.
Abbreviation Meaning
SPLC 1000 Left-alignable safety-related controller of performance class 1000
In this document, the AXC F XT SPLC 1000 is also referred to as a
safety-related controller.
PLCnext Control Controller with PLCnext Technology with which, thanks to the open
control platform, automation projects can be realized without the re-
strictions of proprietary systems. Programming languages and devel-
opment tools are freely selectable here.
The SPLC 1000 can only be operated with a controller of the product
family PLCnext Control AXC F 2152 or AXC F 3152. Therefore,
these devices are meant when the term “PLCnext Control” is used in
this manual.
PELV Protective Extra-Low Voltage
Circuit in which, under normal conditions or under the conditions of
an individual error, the voltage of 30 V AC, 42.4 V peak value, or
60 V DC is not exceeded, except by grounding errors in other cir-
cuits.
A PELV circuit is like a SELV circuit, but is connected to protective
ground.
(In accordance with to EN 61131-2)
F_Source_Add F-Source Address (F-Parameter)
PROFIsafe source address:
– Address of the SPLC 1000 in its function as the F-Host.
– Address of one of the SPLC 1000 (F-Device) superordinate
F-Hosts.
F_Dest_Add F-Destination Address (F-Parameter)
PROFIsafe destination address:
– Address of the SPLC 1000 in its function as the F-Device.
– Address of F-Devices in the application.
For terms and abbreviations used for PROFIsafe, please refer to “Appendix: Terms for
PROFIsafe” on page 173.
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 “Technical data” on page 168).
• Protect the surfaces as necessary to prevent damage.
• When transporting the equipment or storing it temporarily, make sure that the surfaces
are protected from the elements and any external influences, and that they are kept
clean and dry.
2.2 Storage
The storage location must meet the following requirements:
– Dry
– Protected from unauthorized access
– Protected from harmful environmental influences such as UV light
– Temperature range: -40°C ... +85°C
– Air pressure: 58 kPa ... 106 kPa (up to 4500 m above sea level)
– Permissible air humidity: 5% to 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.
Programming You can configure and program the SPLC 1000 using the PLCnext Engineer automation
software. PLCnext Engineer is connected to the SPLC 1000 via the PLCnext Control device
used.
Web-based management The SPLC 1000 itself does not have an integrated Web-based management interface.
WBM system
Information on the WBM system of the PLCnext Control used is available in the
UM EN AXC F X152 user manual (see Section “Documentation” on page 166)
Internal flash memory or Operating the SPLC 1000 on the PLCnext Control AXC F 2152/AXC F 3152 is permitted
SD card with and without an SD card.
The safety-related programs and configurations are saved as part of the PLCnext Engineer
project in the internal flash memory of the PLCnext Control device or on the optional SD
card plugged into the PLCnext Control device.
Operation with an SD card Please note in this case that, when replacing the PLCnext Control device used with an iden-
tical device with suitable firmware, you can reuse the previously used SD card in the re-
placement device. This means that the application of the previously used safety-related and
non-safety-related project is available again after plugging the SD card into the
PLCnext Control.
Operation without an SD Please note in this case that, when replacing the PLCnext Control device used with an iden-
card tical device with suitable firmware, you must use the PLCnext Engineer software to
1. Download the non-safety-related project to the PLCnext Control (standard controller)
used and
2. Download the safety-related project to the SPLC 1000.
Further information on the internal flash memory of the PLCnext Control device and on the
optional pluggable SD card is available in the user manual of the PLCnext Control
UM EN AXC F X152 used (see Section “Documentation” on page 166).
Diagnostics and status in- Diagnostics and status information is displayed directly on the SPLC 1000 via LEDs (see
dicators (LEDs) also Table 3-1 on page 47):
Behavior of the SPLC 1000 The SPLC 1000 can be operated subordinately as an F-Device, for example on a safety-re-
as the F-Device in lated compact controller such as the RFC 4072S. It will then be treated by this superordinate
PROFIsafe F-Host as an F-Device.
The SPLC 1000 can be used simultaneously as an F-Host and as an F-Device in two dif-
ferent PROFIsafe networks.
Request for a pro- Following the request for a programmed safety function (e.g., safety door open), the
grammed safety function SPLC 1000 executes the programmed safety function. The relevant safe outputs of the
F-Devices are set to the programmed value of the safety function.
Behavior in the event of an The integrated diagnostics function detects errors that have occurred. All serious errors de-
error / safe state (Failure tected in the SPLC 1000 that can lead to the loss of or adversely affect the programmed
State) safety function switch the device to the safe state (Failure State). In this state, the safe out-
puts of the F-Devices are set to zero (FALSE).
The safe state will be displayed via the FS (Failure State) LED lighting up red.
In the event of an error, if you are connected online to the PLCnext Engineer, information
about the error is also displayed in the software.
For descriptions of error states, associated effects, and appropriate measures for error re-
moval, please refer to Section “Errors: Diagnostics, messages, and removal” on page 121.
Passivation and reintegra- If the communication relationship between the SPLC 1000 and an F-Device is aborted, for
tion example due to a communication error, the F-Device will be passivated. Passivation pre-
vents the F-Device from starting up immediately as soon as the communication relationship
is reactivated. Passivation and reintegration are displayed via Boolean variables, which the
PLCnext Engineer automatically generates for each F-Device. F-Devices can also be pas-
sivated or reintegrated from the application program via these variables.
If an operator acknowledge request of the passivated F-Device is present, PROFIsafe-spe-
cific acknowledgment can be performed with a subsequent operator acknowledge reinte-
gration. A non-safety-related signal can be used, for example. This overrides the passiva-
tion. As a result, the F-Device is reintegrated.
For more information about passivation and reintegration, please refer to Section 6,
“Commissioning and validation” and Sections “Management/diagnostic variables for
F-Devices” on page 98, “Management/diagnostic variables for each configured F-Device”
on page 144 and “Global management/diagnostic variables for F-Devices” on page 147.
PROFIsafe: F-Host com- The SPLC 1000 supports the user in monitoring and checking the communication relation-
munication diagnostics ships of the device-internal F-Host. The PLCnext Engineer software indicates why the com-
munication relationship was disabled. A distinction is made between the F_WD_Time being
exceeded (F_WD_Time OUT) and an F_CRC error (see Figure 3-1).
PROFIsafe: F-Device com- The SPLC 1000 supports the user in monitoring and checking the communication relation-
munication diagnostics ships of the device-internal F-Device. For this purpose, analogous to the above described
management / diagnostic variables of the F-Host, management / diagnostic variables can
also be created in the PLCnext Engineer for the F-Device of the SPLC 1000. The default
setting for these variables is “Do not create”.
Address area for manage- The following total maximum address area is available for exchange variables:
ment/diagnostic variables – The sum of the standard input data (NSI, inputs exchange area) may not exceed
128 bytes (data direction “I”: SPLC 1000 standard controller).
– The sum of the standard output data (NSQ, outputs exchange area) may not exceed
128 bytes (data direction “Q”: SPLC 1000 standard controller).
The data direction “I” and “Q” is specified from the point of view of the safety-related con-
troller.
Also observe the information in section “Characteristic data of the SPLC 1000 safety-re-
lated controller” on page 171 regarding this.
Device identification/num- In PROFIsafe, safe devices (F-Devices) are identified by means of F-Addresses, which
ber of safe devices must be assigned uniquely for each safe device. PROFIsafe destination address
F_Dest_Add (F_Destination_Address) is used to uniquely identify safe devices. This
address is defined on the F-Device via DIP switch (see Section 6.9.1) and in the
PLCnext Engineer software and checked immediately after it is entered in
PLCnext Engineer. PLCnext Engineer checks the entered addresses for uniqueness
in the configured network and for correct value range.
The value of the F_Destination_Address can be set from 0dec to 65534dec. It must be unique
throughout the entire network.
For safety modules from Phoenix Contact, you can set PROFIsafe destination addresses
from 1 to 999dec, maximum. For safety modules from other manufacturers, you can set
PROFIsafe destination addresses from 1dec to 65534dec.
NOTE:
Please note that each F-Address assigned within a network must be unique and must not
overlap with other addresses.
Also observe the information in section “Characteristic data of the SPLC 1000 safety-
related controller” on page 171 regarding this.
In the application, the maximum permissible SFRT must be determined for each safety
function implemented in the application. This maximum permissible SFRT also includes the
part of the SFRT that applies to the PROFIsafe system if PROFIsafe and the SPLC 1000 are
involved in the safety function.
A method of calculation for determining the part of the SFRT that applies to PROFIsafe is
specified in the PROFIsafe system description (see Figure 3-3). The method of calculation
specified is subject to certain general conditions.
For detailed information regarding the PROFIsafe system description, please refer to
Section “Documentation” on page 166.
The TWCDT (total worst case delay time) is therefore the sum of all maximum signal run-
times that may occur in the individual elements during normal operation.
The individual elements are:
– (PROFIsafe) F-Devices
– Transmission (PROFIsafe via PROFINET including all network infrastructure compo-
nents and subordinate subsystems, for example of the Axioline F local bus) and
– SPLC 1000.
Due to a closely synchronized sequence of F-Host / SPLC 1000 processing, this model is
simplified when using the SPLC 1000. The runtimes, cycle times, and watchdog times of the
SPLC 1000 (processing delay and F-Host_WD) are not actually relevant when determining
the SFRT.
Input Output
Delay Delay
Device WD Device WD
F_WD_Time INmax + F_WD_Time OUTmax t
Safety Function Response Time SFRT (TWCDT + t of the longest “Device WD Time” *) )
Maximum Safety Function Response Time SFRTmax (determined via Safety Function)
107586A021
Key:
WCDT OUT Worst case delay time of the F-Device with output function.
For this time, please refer to the device-specific user documen-
tation for the F-Device used.
Device WD Internal watchdog time of the F-Device involved in the safety
function.
The central component in Figure 3-4 on page 33 is deemed to be the sum of
F_WD_Time INmax and F_WD_Time OUTmax.
The sum of these times specifies the maximum internal processing time that is required for
point-to-point communication via PROFIsafe between the PROFIsafe input device and the
PROFIsafe output device using the SPLC 1000, even in the event of an error, such as a tele-
gram delay.
The actual SFRT to be implemented for the PROFIsafe system can be determined accord-
ing to the following equation:
Always take into consideration all the links that are involved in the safety function and pro-
grammed in the safety-related application program.
Please refer to the F-Device-specific user documentation to check whether further infor-
mation is available regarding watchdog times within the internal device function.
If F-Devices are used where there is a difference ( t) between their worst case delay time
(WCDT) and the implemented device watchdog time (Device WD), this difference must
be taken into consideration in accordance with the PROFIsafe model for determining the
SFRT.
Timer functions that are used within the safety function in the safety-related application
program must be taken into consideration.
The F_WD_Time, which you as the user must determine according to your application, is
set in the PLCnext Engineer software (“Safety Parameters” editor, see Figure 6-27 on
page 95). If the safety-related communication relationship has been established between
the partners, monitoring is performed independently by both F-Host (SPLC 1000) and
F-Device to ensure that the set F_WD_Time is observed during safety-related commu-
nication.
Please note that if the F_WD_Time is too short for a safety-related communication
relationship, systems and applications will not be available.
This is because the value for F_WD_Time must be greater than or equal to the total max-
imum telegram runtime from F-Host to F-Device and back again to at least be able to es-
tablish safety-related communication via PROFIsafe during error-free network operation.
In addition to the transmission times on the network (PROFINET cycle), internal stack and
firmware runtimes in devices, delays caused by subsystem buses (e.g., device bus for
modular I/O systems), etc. must also be taken into consideration.
The following figure from the PROFIsafe specification illustrates the relationship:
For detailed information on the PROFIsafe specification (PROFIsafe – Profile for Safety
Technology on PROFIBUS DP and PROFINET IO, Item No. 3.192), please refer to
Section “Documentation” on page 166.
Key:
DAT Cycle time of the F-Device (F-Device acknowledge time)
Bus Bus runtime including all relevant runtime components in the devices, back-
plane buses, bus heads (bus couplers or controllers) etc. of modular systems
HAT Cycle time of the SPLC 1000 (F-Host Acknowledge Time: TZSPLC)
DAT For the cycle time of the F-Devices, please refer to the device-specific user doc-
umentation for the F-Devices used.
Bus The “Bus” value is the sum of all the following times in the network/bus system
used:
1. External bus runtime in the network:
– Update time of the I/O data between PROFINET controller and device
set via the “Reduction ratio” multiplied by the “Monitor factor” (multipli-
er of the update time).
The result (monitor time) determines the time at which the communi-
cation relationship is disconnected if no cyclic data has been transmit-
ted in the specified time (see Figure 3-6).
In the following example, the setting “Symmetric” has been selected
for the “Timing”. An adjustment of the values may be necessary if the
setting “Asymmetric” is selected.
Program runtime Idle First, the program runtime for an “empty” safety-related program (number of safety-related
function-block instances = 0) is considered.
The relationship for this is:
70
Program runtime Idle = 1 ms + ms * n
1000
4
3,24
3
0 n
0 10 20 30
109449A009 32
Figure 3-9 Program runtimeIdle in relation to the number of F-Devices used.
Key:
Program runtime In addition to the dependency of the program runtime on the number of F-Devices used in
the application described above, there is an additional dependency. The program runtime
also depends on the number of safety-related function-block instances (parameter a) used
in the safety-related program.
With each safety-related function-block instance used in the safety-related program, the
program runtime is extended on average by 20 µs.
As a result, the following applies:
20
Program runtime = Program runtime Idle + a * ms
1000
70 20
= 1 ms + ms * n + a * ms
1000 1000
20 70
(
= 1+a*
1000 ) ms + 1000
ms * n
20
(1+ a * 1000 )
0 n
0 10 20 30
109449A015
Key:
a: Number of safety-related function-block instances used in the safety-re-
lated program
n: Number of F-Devices used in the application
The value of the SPLC 1000 program runtime determined approximately in the planning
phase must comply with the following ratio to the cycle time of the SPLC 1000 TZSPLC:
Program runtime
⇒ Cycle time
≤ 0.7
This results in the SPLC 1000 cycle time TZSPLC to be set by the user in accordance with
the formula determined in the planning phase:
Program runtime
⇒ Cycle time TZSPLC≥
0.7
Example calculation This example results in the following progression of the program runtime for a number of 0
to a maximum of 32 F-Devices and a number of 20 safety-related function blocks (a = 20):
Program runtime / ms
4
3,64
3
2
1,4
1
0 n
0 10 20 30
109449A016 32
Figure 3-11 SPLC 1000 program runtime in the example
Continuing with a = 20 and the maximum 32 F-Devices, the program runtime is:
(
Program runtime = 1 + 20 *
20
1000 ) ms + 1000
70
ms * 32
= 3.64 ms
With the above equation for the cycle time, the following results:
3.64 ms
⇒ Cycle time TZSPLC ≥
0.7
Verification necessary! Verify the times determined above during the commissioning phase as follows online.
For verification, use two system variables shown in the PLCnext Engineer software.
If the PLCnext Engineer software is connected online with the SPLC 1000 and the
PLCnext Control device, you can display the cycle time and the program runtime of the
SPLC 1000 in the software (see Figure 3-12) with the following two system variables (see
Section “SPLC system variable” on page 135):
– Cycle time: CYCLE_TIME
– Program runtime: EXEC_TIME
To learn how you can access the SPLC 1000 online with the PLCnext Engineer software,
refer to sections “Transferring projects to the PLCnext Control device and SPLC 1000
and displaying online values” on page 110 and “SPLC system variable” on page 135 as
well as to the software online help function.
Figure 3-12 Online values of the SPLC 1000 cycle time and program runtime
The SPLC 1000 cycle time is also displayed in the “Safety Cockpit” editor:
Based on the actual determined value of the SPLC 1000 cycle time, it may be necessary
to adjust the F_WD_Time in order to increase system availability, for example.
WARNING: Avoid possible danger that may be caused by the safety function be-
ing triggered too late
Make sure that the maximum permissible values for F_WD_TIME INmax and F_WD_TIME
OUTmax are not exceeded (see Section “Determining SFRTmax and F_WD_Time INmax/
F_WD_Time OUTmax” on page 32).
The minimum F_WD_Time that can be set can be determined for each communication re-
lationship using the following equation:
Communication between 1. The F-Host of the SPLC 1000 communicates with an F-Device via PROFINET.
F-Host and F-Device via In this case, the F-Device is connected, for example, via a PROFINET bus coupler with
PROFINET the PLCnext Control device used (here, AXC F 3152) to which the SPLC 1000 is left-
aligned.
Since the SPLC 1000 cycle and the PROFINET cycle run asynchronously with one an-
other, the SPLC 1000 cycle must be included twice in the total when determining the
minimum F_WD_Time, once as the “HAT” and again as the “internal bus runtime”. The
external bus runtime is based on the relevant times of the PROFINET
configuration.
F_WD_Timemin > DAT + 2 x (external bus runtime + internal bus runtime) + HAT
Communication between 2. The F-Host of the SPLC 1000 communicates with an F-Device via the Axioline F local
F-Host and F-Device via bus.
the Axioline F local bus In this case, the F-Device is aligned to the right of the PLCnext Control device used
(here, AXC F 3152). Via the Axioline F local bus, the F-Device is connected directly to
the PLCnext Control device to which the SPLC 1000 is left-aligned.
In this case, the internal bus runtime is the sum of the internal update time
TUPD AXIO PLCnext (see point “Internal update time TUPD AXIO PLCnext:” on page 37) and
TZSPLC. As in the first case, HAT equals TZSPLC.
With TUPD AXIO PLCnext = TZSPLC, the following applies (see point “Internal update time
TUPD AXIO PLCnext:” on page 37):
Calculation for the exam- For the example configuration in Section “The SPLC 1000 as the F-Host with safety-related
ple configuration communication via PROFINET/PROFIsafe” on page 73 considered here, the following
calculated minimum F_WD_Time OUT for communication with the F-Device
AXL F PSDO8/3 1F results from the equation [4] from the above case 1 and taking the
following values into account:
TBus = 24 + 1 x 1 ms + 2 x 0 ms
TBus = 25 ms
The F_WD_Time OUT for available and robust system behavior with the specified
PROFINET settings results as follows for the example configuration from the bus head (bus
coupler AXL F BK PN TPS) and the Axioline F output module (AXL F PSDO8/3 1F). The
values listed and calculated above must be used in the following equation based on [4].
TBus = 3 ms + 1 x 1 ms + 2 x 0 ms
TBus = 4 ms
The minimum F_WD_Time OUT is calculated as follows for the example configuration:
(F_WD_Time INmin + F_WD_Time OUTmin) < (F_WD_Time IN + F_WD_Time OUT) < (F_WD_Time INmax + F_WD_Time OUTmax)
The relationship between the values for F_WD_Time IN and F_WD_Time OUT is based on
the relationship for the minimum F_WD_Time and the system availability determined in
Section 3.3.2 on page 35.
Example Based on the maximum possible safety function response time, the following requirement
must be met:
F_WD_Time INmax + F_WD_Time OUTmax = 200 ms (Upper limit from the safety
function)
F_WD_Time IN = 2 x 50 ms = 100 ms
Factor 2 has been chosen here so that it is still possible to later increase the PROFINET
repeat cycles by the monitor factor or the PROFINET update time without endangering
system availability by exceeding the F_WD_Time monitoring time.
As a result, the values selected in the example project (see Figure 6-27 on page 95)
described in Section 6.4.2.1 are within the permissible range:
Minimum F_WD_Time (IN+OUT) < F_WD_Time (IN+OUT) to be parameterized < Maximum F_WD_Time (IN+OUT)
Information on the possible fields of application for the SPLC 1000 is available in Sections
“Example: The SPLC 1000 as the F-Host for Axioline F and Axioline Smart Elements
F-Devices” on page 72 and “Further example configurations” on page 73.
1
2
3 4
Figure 3-14 SPLC 1000 connection and operating elements
Key:
1 Function identification
2 AXL F BS BK XT bus base module (item no.: 1141222)
3 Electronics module
4 Supply connector (connector for connecting the supply voltage
(communications voltage UL, 24 V DC))
5 Diagnostic and status indicators
PLCnext Control
Axioline
AXC F XT SPLC 1000
Extension
XX
2
Safety
3
P RUN
C FS
HW/FW: xx/x.x.x
Flachsmarktstraße 8
Phoenix Contact GmbH & Co. KG
32825 Blomberg / Germany
www.phoenixcontact.com
Ord.No.1159811
XXXXXXXXXX
5
6 109449a005
Figure 3-15 SPLC 1000 printing, including test mark
Key:
1 Item designation
2 Year of manufacture
3 Item number
4 Revision versions (HW/FW)
5 Serial number
6 Test mark
P RUN
C FS
UL
109449A013
Figure 3-16 Diagnostic and status indicators
Logic / FE
P RUN
UL
C FS
UL
UL
24 V
Key:
24 V
Extension Left-aligned
S-CPU Safety-related processor bus “PLCnext Control Extension”
extension modules
4 Mounting hardware
For basic information on the Axioline F system and its installation, particularly
mounting/removing Axioline F modules, please refer to the UM EN AXL F SYS INST
user manual (“Axioline F: System and installation”).
Please note:
During any work on the Axioline F station, the SPLC 1000, the PLCnext Control device, or
a module, switch off the power supply to the Axioline F station and make sure the supply
voltage is protected against unauthorized reactivation.
The SPLC 1000 is automatically grounded (FE) when it is snapped onto a ground-
ed DIN rail.
On the rear of the SPLC 1000, there are two FE springs that make contact with the DIN rail
when the SPLC 1000 is placed on the DIN rail.
Mounting location The SPLC 1000 meets the IP20 degree of protection.
• It is imperative that you mount the SPLC 1000 in a lockable housing or in a lockable
control cabinet with at least IP54 degree of protection.
Mounting/DIN rail The SPLC 1000 is mounted on a 35 mm standard DIN rail without any tools using the bus
base module. It is mounted perpendicular to the DIN rail.
The local bus is created automatically when the bus base modules of the PLCnext Control
device and the Axioline F device are aligned next to one another.
The extension bus is created automatically when the bus base modules of the SPLC 1000
and PLCnext Control device are aligned next to one another.
Observe the notes on securing the DIN rail and fastening elements as well as the notes
on mounting distances in the UM EN AXL F SYS INST user manual.
Supply connector The SPLC 1000 has a supply connector for connecting the power supply. The connector is
fitted with spring-cage terminal blocks. When using suitable conductors, the conductors can
be connected by means of direct connection technology (Push-in technology).
FE connection There are two FE springs (metal contacts) on the bottom of the SPLC 1000 which establish
the connection to functional ground when the device is snapped onto a grounded DIN rail.
End brackets Mount end brackets on both sides of the Axioline F station. The end brackets ensure that
the Axioline F station is correctly mounted. End brackets secure the station on both sides
and keep it from moving from side to side on the DIN rail. Phoenix Contact recommends the
following end brackets:
Mounting position As standard, mount the SPLC 1000 in a horizontal position (A in Figure 4-2) on the DIN rail
provided for that purpose.
A B
C
109449A001
Figure 4-2 Mounting positions for the AXC F XT SPLC 1000 in an Axioline F station
Key:
Figure 4-3 shows an example structure of an Axioline F station with the SPLC 1000:
2 3 4 5 6 7 8
9
1 1
10
109449A002
Figure 4-3 Example: Structure of an Axioline F station with left-aligned safety-related
AXC F XT SPLC 1000 controller
Key:
1 End brackets (for securing the station; see Section “Accessories” on page 166)
2 Left-alignable safety-related AXC F XT SPLC 1000 controller
3 PLCnext Control
4 Safety-related Axioline F I/O module
5 Axioline F backplane (AXL F BP SE4) for Axioline Smart Elements
6 Safety-related Axioline Smart Elements I/O modules
7 Slot covers for unused Axioline Smart Elements slots
8 Axioline F I/O module
9 Bus base module
10 DIN rail
An Axioline F station is set up by mounting the individual components side by side. No tools
are required. Mounting the components side by side automatically creates potential and bus
signal connections between the individual components of the Axioline F station.
Left alignment of the You can align the AXC F XT SPLC 1000 as a “PLCnext Control Extension” extension
AXC F XT SPLC 1000 module to the left of the PLCnext Control AXC F 2152 and AXC F 3152.
Please note:
Before you can mount the SPLC 1000, you must:
– Remove the PLCnext Control AXC F 2152 or AXC F 3152 used.
– Remove the PLCnext Control supply connector if necessary.
– Remove any further electronics modules and then remount them.
– Remove any bus base modules and remount them.
Follow the descriptions listed in this section.
Please note:
Mount all necessary modules before supplying power to the Axioline F station. Modules
to which power is only supplied following the PLCnext Control boot process are not de-
tected or may result in a malfunction.
To ensure that the left-alignable SPLC 1000 is detected correctly, follow the specifica-
tions of the voltage supply for the SPLC 1000 (see Section 5.2.2).
Please note:
Before you can mount the SPLC 1000, you must first remove the PLCnext Control device.
• Release the locking latch (A), tilt the supply connector upwards slightly (B), and remove
it from the PLCnext Control (C).
D
R
A
-C
D
S
R
4
X
X
.X
X
.X
52
X
.X
21
X
.X
F
X
.X
C
X
X
X
A
r.:
67
dd
A
2
04
C
A
4
M
2
o.
.N
rd
O
2
X
1
X
A
B
52
21
F
C
X
X
.X
A
X
.X
67
X
42
.X
S
0
D
24
.X
-C
R
X
A
o.
R
.X
D
.N
X
r.:X
rd
X
O
4
dd
A
C
A
M
A
X
1
X
2
X2
X1
Please note:
– When snapping a bus base module onto a DIN rail, ensure that there are no electronic
modules on the preceding or following bus base module.
– To operate the SPLC 1000 on a PLCnext Control AXC F 2152, this requires a special
bus base module (1 in Figure 4-8 on page 59).
The bus base module is not supplied with the AXC F 2152. For the ordering data,
please refer to the UM EN AXC F X152 user manual.
– For the left alignment of a further module (AXC F XT ...) the cover cap of the previous
bus base module must first be removed (A in Figure 4-8 on page 59).
– Read further information on mounting the bus base and electronics modules and in
particular on the left alignment of the controller of the PLCnext Control product group
in the UM EN AXL F SYS INST user manual.
AXC F 2152 When using the PLCnext Control AXC F 2152, you must first replace the bus base module
present with the special bus base module.
To do so, proceed as follows:
• Remove the AXC F 2152 bus base module from the bus base of the first module
aligned to the right.
• Remove the AXC F 2152 bus base module from the DIN rail.
When mounting the bus base modules, proceed as illustrated in Figure 4-6:
C
D
A
B
• Place the special bus base module for the AXC F 2152 on the DIN rail (A in Figure 4-6).
• Push the special bus base module for the AXC F 2152 into the connection for the bus
base module of the module aligned to the right (B in Figure 4-6).
• Place the bus base module for the SPLC 1000 on the DIN rail (C in Figure 4-6).
• Push the bus base module for the SPLC 1000 into the connection of the special bus
base module for the AXC F 2152 (D in Figure 4-6).
AXC F 3152 When using the PLCnext Control AXC F 3152, you do not need to replace the bus base
module.
When mounting the bus base module for the SPLC 1000, proceed as illustrated in
Figure 4-7:
A
B
109449A010
Figure 4-7 Mounting bus base module(s): AXC F 3152
• Remove the cover cap of the bus base module for the AXC F 3152 (A in Figure 4-8).
• Place the bus base module for the SPLC 1000 on the DIN rail (A in Figure 4-7).
• Push the bus base module for the SPLC 1000 into the connection of the bus base mod-
ule for the AXC F 3152 (B in Figure 4-7).
A
C B
1
Figure 4-8 Mounting the bus base modules of further AXC F XT ... modules
• Remove the cover cap of the preceding bus base module (A in Figure 4-8).
• Place the bus base modules of the additional AXC F XT ... modules to be aligned on the
left on the DIN rail (B in Figure 4-8).
• Push each subsequent bus base module into the connection of the previous bus base
module (C in Figure 4-8).
• Working from right to left, place each electronics module vertically on the correspond-
ing bus base module and on the DIN rail until it snaps into place with a click. Make sure
that the device plug for the bus base connection is situated above the corresponding
socket on the bus base module.
• Place all supply connectors in position and press them down firmly. Make sure that the
respective locking latch snaps into place.
• Mount the left end bracket on the Axioline F station.
Only use power supplies that are suitable for operation with capacitive loads (increased
inrush current).
• Select a power supply that is suitable for the currents in your application. The selection
depends on the bus configuration and the resulting maximum currents.
WARNING: Loss of electrical safety and the safety function when using unsuit-
able power supplies
The SPLC 1000 is designed exclusively for protective extra-low voltage (PELV) operation
in accordance with EN 60204-1. Only protective extra-low voltages in accordance with
the listed standard may be used for the supply.
The following applies to the network (PROFINET and Axioline F) and the I/O devices used
in it:
Only use power supplies that satisfy the requirements of EN 61204-1 and feature safe iso-
lation with PELV in accordance with IEC 61010-2-201 (PELV). They prevent short circuits
between the primary and secondary side.
Please also observe the information in Section “Electrical safety” on page 16.
A power supply without a fall-back characteristic curve must be used for correct oper-
ation of the SPLC 1000 (see Figure 5-2).
When the SPLC 1000 is switched on, an increased inrush current is temporarily triggered.
The SPLC 1000 behaves like a capacitive load when it is switched on.
Make sure the power supply and the externally required fuse are compatible. The power
supply must be able to temporarily provide the tripping current. Observe the information
in Section “Technical data” on “Power supply” from page 169.
Some electronically controlled power supplies have a fall-back characteristic curve (see
Figure 5-1). These are not suitable for operation with capacitive loads.
24 24
I OUT I OUT
IN [A] [ A]
Figure 5-1 Overload range with fall-back characteristic Figure 5-2 Overload range without fall-back charac-
curve teristic curve
Please note:
The supply voltage of the left-alignable SPLC 1000 and the PLCnext Control device used
must be fed in via a shared power supply unit.
For further information on this, also read the information in the controller-specific
UM EN AXC F X152 user manual.
• Connect the supply voltage via the Axioline F connector.
A B
24 V
GND
Key:
a1 b1
a1 b1
a2 b2
a2 b2
Figure 5-4 Terminal points for the supply voltage (communications voltage UL)
Key:
Rigid conductor/ferrule • Insert the conductor into the terminal point. It is clamped into place automatically.
Flexible conductor • Open the spring by pressing on the spring lever with a screwdriver (A in Figure 5-6).
• Insert the conductor into the terminal point (B in Figure 5-6).
• Remove the screwdriver to secure the conductor (recommended: bladed screwdriver,
blade width: 2.5 mm (e.g., SZS 0,4x2,5 VDE, item no. 1205037)).
A
B
109449A004.des
Supply the SPLC 1000 (together with the PLCnext Control used) with an external 24 V DC
voltage supply. The permissible voltage range is 19.2 V DC to 30 V DC (ripple included).
Only use power supplies that are suitable for operation with capacitive loads (increased
inrush current) (see Section 5.1).
• Connect the power supply to the supply connector as shown in Figure 5-5 and in
Figure 5-6. Note the information in Section 5.2.3.
The PLCnext Engineer software is required for commissioning the SPLC 1000.
The following topics are also available in the PLCnext Info Center:
– Configuring Axioline F modules
– Adding left-alignable “PLCnext Control Extension extension modules” to the bus con-
figuration
– Configuring PROFINET devices
– Programming in accordance with IEC 61131-3
– Instantiating programs
– Assigning process data
– Specifying the refresh interval for Axioline F I/O data
– Transmitting projects to the PLCnext Control
– Creating a PLCnext Engineer HMI application
The following table describes all the steps from unpacking the SPLC 1000 through mount-
ing/installation, right through to commissioning.
WARNING:
Follow the instructions in the note
“WARNING: Organizational or technical mea-
sures for checking the CRC checksum after a
voltage reset or restart necessary” on page 67.
4 Connect the power supply to the device. – Notes on using PELV power supplies in Section “Elec-
trical safety” on page 16
– Section “Supply voltage” on page 63
Make sure that the PLCnext Control device as well as the PROFINET and F-Devices used in your application
have been mounted and installed correctly before switching on the supply voltage.
WARNING:
The planned system/machine safety function is
only available following validation.
Please note:
The SPLC 1000 and the PLCnext Control device used take approximately 1 minute to start up. This is due to
the comprehensive self-tests the devices must perform. The LEDs on the two devices indicate the status.
6 Carry out all the steps in order to be able to integrate the – Online help for PLCnext Engineer
device as a PROFIsafe F-Host into a PLCnext Engineer – Section “Integration of the SPLC 1000 as the F-Host in
project. PLCnext Engineer” on page 76
7 Create the safety-related bus configuration in – Section “Adding PROFINET devices” on page 84
PLCnext Engineer. – Section “Adding I/O modules (F-Devices)” on page 86
8 In PLCnext Engineer, set the F_Source_Address Section “Assigning/checking the PROFIsafe address
(F_Source_Add) and the F_Destination_Addresses (F-Address) of PROFIsafe devices” on page 93
(F_Dest_Add) that are set on the safe F-Devices.
9 Check the settings for management/diagnostic vari- – Section “Description of the safety-related functioning of
ables and adapt the settings, if necessary. the SPLC 1000” on page 27
– Section “Management/diagnostic variables for
F-Devices” on page 98
– Section “Management/diagnostic variables for each
configured F-Device” on page 144
– Section “Global management/diagnostic variables for
F-Devices” on page 147
10 Specify a new project password. Section “Defining a project password” on page 81
11 Create the variables for the safety-related devices for Section “Creating safety-related variables” on page 104
process data exchange.
12 Link the created variables to the process data in accor- Section “Assigning safety-related process data” on
dance with your application. page 108
13 Carry out the necessary device parameterization in the Section “Programming in accordance with IEC 61131-3 –
PLCnext Engineer software. Safety-related example program” on page 93
14 Check the bus configuration and variable assignment
(exchange variables).
15 Specify a new SafePLC password. Section “Specifying the SPLC 1000 controller password” on
page 112
16 Carry out the validation using the checklist ““Initial com- Section “Appendix: Checklists” on page 175
missioning” and “recommissioning/device replace-
ment” validation” on page 185.
The device does not have to be configured again during recommissioning after replacing
the SPLC 1000 (see steps 6 to 15 in Table 6-1 “Steps for initial commissioning of the
SPLC 1000”).
Depending on the operating mode (see page 26: “Operation with an SD card” or “Opera-
tion without an SD card”), the safety-related project is either in the internal flash memory
of the PLCnext Control device used or on the SD card inserted in the PLCnext Control
device.
For recommissioning after the device has been replaced, proceed as described in steps 1
to 5 and 16 in Table 6-1 on page 68.
The prerequisite for this is that the device to be replaced has been removed from the appli-
cation in accordance with the instructions in Section “Removing hardware” on page 153.
The device does not have to be configured again during recommissioning after replacing
the PLCnext Control device (see steps 6 to 15 in Table 6-1 “Steps for initial commission-
ing of the SPLC 1000”) if an SD card that contains a safety-related project is inserted into
the PLCnext Control device.
For recommissioning after the device has been replaced, proceed as described in steps 1
to 5 and 16 in Table 6-1 on page 68.
The prerequisite for this is that the device to be replaced has been replaced with a new de-
vice in the application in accordance with the instructions in UM EN AXC F X152.
WARNING:
Follow the instructions in the note “WARNING: Organizational or technical measures for
checking the CRC checksum after a voltage reset or restart necessary” on page 67.
6.4.1 Example: The SPLC 1000 as the F-Host for Axioline F and
Axioline Smart Elements F-Devices
To make your introduction to working with the SPLC 1000 as straightforward as possible,
the descriptions in later sections are based on the following configuration.
The SPLC 1000 communicates as the F-Host via PROFINET/PROFIsafe with the safety-
related Axioline F I/O modules and via the Axioline F local bus with the safety-related
Axioline Smart Elements I/O modules.
In the following example configuration in Figure 6-1, an Axioline F bus coupler is coupled to
an Axioline F station as a subordinate. The Axioline F station consists of the modular
AXC F 3152 controller and an SPLC 1000 left-aligned to this.
Communication between the SPLC 1000 and the safety-related Axioline F I/O modules is
done via PROFINET/PROFIsafe through the Axioline F PROFINET bus coupler.
Furthermore, the SPLC 1000 communicates via the PLCnext Control AXC F 3152 directly
via the Axioline F local bus with the safety-related Axioline Smart Elements I/O modules.
AXC F XT AXL SE
SPLC 1000 AXC F 3152 PSDO4/2 2A
AXL SE SC-A
AXL SE SC-A
AXL SE AXL F
PSDI8/3 PSDO8/3 1F
PROFINET
PROFINET
AXL F AXL F
BK PN TPS DI16/1 HS 1H 109449A008
Figure 6-1 Example configuration: The SPLC 1000 as the F-Host with safety-related
communication via the Axioline F local bus and via PROFINET/PROFIsafe
6.4.2.1 The SPLC 1000 as the F-Host with safety-related communication via
PROFINET/PROFIsafe
AXC F XT AXC F
SPLC 1000 2152
PROFINET
AXL F AXL F
PSDI8/4 1F PSDO8/3 1F
PROFINET 109449A012
Figure 6-2 Example configuration: The SPLC 1000 as the F-Host with safety-related
communication via PROFINET/PROFIsafe
In this example configuration, two Axioline F bus couplers are coupled to an Axioline F
station as subordinates. The Axioline F station consists of the modular AXC F 2152 small-
scale controller and an SPLC 1000 left-aligned to this.
Communication between the SPLC 1000 as the F-Host and the safety-related Axioline F
I/O modules is via PROFINET/PROFIsafe via the Axioline F PROFINET bus coupler.
6.4.2.2 The SPLC 1000 as the F-Host with safety-related communication via the
Axioline F local bus
AXL SE
PSDO4/2 2A
AXC F XT AXC F AXL F AXL F AXL SE SC-A
SPLC 1000 2152 PSDO8/3 1F PSDI8/4 1F
AXL SE AXL F
PSDI8/3 DI16/1 HS 1H
AXL SE SC-A
109449A011
Figure 6-3 Example configuration: The SPLC 1000 as the F-Host with safety-related
communication via the Axioline F local bus
In this example configuration, the SPLC 1000 is aligned to the left of the modular
AXC F 2152 small-scale controller in an Axioline F station.
In the Axioline F station, various F-Devices are aligned to the right of the PLCnext Control
AXC F 2152. These are safety-related Axioline F and Axioline Smart Elements
I/O modules.
The SPLC 1000 as the F-Host communicates via the PLCnext Control AXC F 2152 with the
safety-related Axioline Smart Elements and Axioline F I/O modules directly via the
Axioline F local bus.
6.4.2.3 The SPLC 1000 as the subordinate F-Device with safety-related commu-
nication via PROFINET/PROFIsafe and as the F-Host with safety-related
communication via the Axioline F local bus
RUN/PROG
STP DISPLAY
MRESET
LAN LAN
1 2
LAN LAN
3.1 3.2
PROFINET
AXL F AXC F XT AXC F AXL SE
PSDO8/3 1F SPLC 1000 2152 PSDO4/2 2A
-A
SC
SE
L
AX
-A
SC
SE
L
AX
AXL F AXL F AXL SE
BK PN TPS DI16/1 HS 1H PSDI8/3
PROFINET 109449A007
Figure 6-4 Example configuration: The SPLC 1000 as the subordinate F-Device with
safety-related communication via PROFINET/PROFIsafe and as the
F-Host with safety-related communication via the Axioline F local bus
In this example configuration, the SPLC 1000 communicates as the subordinate F-Device
with the safety-related RFC 4072S compact controller (F-Host) via PROFINET/PROFIsafe.
Furthermore, the SPLC 1000 communicates as the F-Host via the PLCnext Control
AXC F 2152 with the safety-related Axioline Smart Elements and Axioline F I/O modules
directly via the Axioline F local bus.
For the chronological sequence of the steps carried out, please refer to the example
application.
When carrying out the following steps, please refer to the online help of the
PLCnext Engineer software. The online help assists you in programming and parameter-
izing the software.
1
2
3
5
7
Figure 6-5 PLCnext Engineer user interface
1. Menu bar
2. Toolbar
3. “PLANT” area
4. Editors area
5. “COMPONENTS” area
6. Cross-functional area
7. Status bar
“PLANT” area All of the physical and logical components of your application are mapped in the form of a
hierarchical tree structure in the “PLANT” area.
Editors area Double-clicking on a node in the “PLANT” area or an element in the “COMPONENTS” area
opens the associated editor group in the Editors area. Editor groups are always displayed
in the center of the user interface. The color of the editor group indicates whether it is an in-
stance editor (green; opened from the “PLANT” area) or a type editor (blue; opened from
the “COMPONENTS” area). Each editor group contains several editors that can be opened
and closed via buttons in the editor group.
“COMPONENTS” area The “COMPONENTS” area contains all of the components available for the project.
The components can be divided into the following types based on their function:
– Developing program code (“Data Types”, “Programs”, and “Functions and Function
Blocks”)
– Showing all devices available for the “PLANT” area and adding them via GSDML or
FDCML (“Devices”)
– Editing HMI pages (“HMI”)
– Adding libraries such as firmware libraries, IEC user libraries or libraries provided by
Phoenix Contact (“References”)
Cross-functional area The cross-functional area contains functions that extend across the entire project.
– ERROR LIST:
Shows all errors, warnings, and messages for the current project.
– GLOBAL FIND AND REPLACE:
Finds and replaces strings in the project.
– CROSS REFERENCES:
Displays all cross-references within the project, for example, the use and declaration of
all variable types or HMI tags.
– WATCHES:
Debug tool; shows the current values of the added variables in online mode.
– BREAKPOINTS:
Debug tool for setting and resetting breakpoints when debugging within the application.
– CALL STACKS:
Debug tool that shows the order for calling up when executing the code and that con-
tains commands for debugging with breakpoints.
– LOGIC ANALYZER:
Records and visualizes variable values at runtime.
– ONLINE STATE:
While there is an online connection established to the controller and to the safety-
related controller, a superordinate symbol of their operating state is displayed in the
ONLINE STATE window.
– LOGGING:
Shows all errors, warnings, and messages. A distinction is made between “online”
(messages regarding the runtime environment, as well as errors and warnings that con-
cern online communication) and “engineering” (messages regarding software events,
e.g., GSDML and FDCML files; not project-related).
– RECYCLE BIN:
Elements that have recently been deleted from the “PLANT” or “COMPONENTS” areas
are moved to the recycle bin. Deleted elements can be restored from here, if needed.
• Drag the selected PLCnext Control into the “PLANT” area while pressing the mouse
button.
• Paste the PLCnext Control to the project node.
• Open the “File, save project as…” menu.
• Enter a unique and meaningful name for the project (in the example:
“UM_SPLC_1000”).
• Click the “Save” button.
Further information on creating a new project is available in the UM EN AXC F X152 user
manual and in the PLCnext Engineer software online help function.
• For the following steps/settings in the project, proceed in accordance with the
descriptions in the UM EN AXC F X152 user manual.
• Specify an IP address range for the project to be able to operate it in your network.
The user name, the password, and further information on user authentication preset in the
delivery state can be found in the UM EN AXC F X152 user manual.
A successful connection will be displayed in the “PLANT” area on the node of the controller.
Further information is available in the PLCnext Info Center and in the PLCnext Engineer
online help function.
Figure 6-14 PROFINET devices in the “PLANT” area and in the Device List
A description of the procedure for adding I/O modules is available in the PLCnext
Community at plcnext-community.net and in particular in the PLCnext Info Center as well
as in the PLCnext Engineer online help function.
This section describes how to manually add I/O modules (here, F-Devices) to PROFINET
devices and to the “Axioline F (x)” node.
Adding I/O modules to Double-click in the “PLANT” area on the PROFINET device whose I/O modules you wish to
PROFINET devices add.
The editor group of the selected PROFINET device opens; “axf-f-bk-pn-tps-1” in the exam-
ple.
• Select the “Module List” editor.
• Select “Select type here” in the first row of the “Module List” editor.
The role picker opens.
Project password: Log- In this area, you will be changing the safety-related project by adding F-Devices. If you are
ging into the Safety-relat- not logged into the “Safety-related Area”, PLCnext Engineer will prompt you to enter a pass-
ed Area word.
Through the targeted distribution of the password, you can specify the circle of users who
may make changes to the safety-related project.
• Enter the password in the following dialog and confirm your entry by clicking on the
arrow.
The I/O module is added and shown in the “PLANT” area under the “Profinet (x)” node for
the respective PROFINET device (see Figure 6-18).
• Proceed as described above to add more I/O modules.
Adding I/O modules to the • Double-click the “Axioline F (x)” node in the “PLANT” area.
“Axioline F (x)” node
The “/ Axioline F” controller editor group opens.
• Select the “Device List” editor.
Add the I/O modules in the “Device List” editor. To do so, proceed as follows:
• Select “Select type here” in the first row of the “Device List” editor.
The role picker opens.
The figure below shows all I/O modules contained in the example project.
Please note:
Due to the creation of a new project for the SPLC 1000 described in Section 6.5.5, you
have to carry out the steps in sections 6.8.1 “Creating a POU” and 6.8.2 “Instantiating
programs” for the SPLC 1000 yourself.
Opening the “Tasks and To open the “Tasks and Events” editor, proceed as follows:
Events” editor • Double-click on the “PLCnext (x)” node in the “PLANT” area.
The “/ PLCnext” editor group opens.
• Select the “Tasks and Events” editor.
Figure 6-24 Tasks and program instances in the “Tasks and Events” editor
If you are not currently logged into the safety-related area, you will now be prompted to
enter the password in the “PROJECT AUTHENTICATION” dialog that opens (see
“Project password: Logging into the Safety-related Area” on page 86).
• In the “PROFIsafe Addressing” view, check the setting for the F_Source_Add
F-Address. In the example, set F_Source_Add to “1024”. If necessary, adapt the
value of F_Source_Add to your application.
An adjustable range of “1 ... 65534dec”, maximum, is permitted.
F_Destination_Address
(F_Dest_Add)
When using the SPLC 1000 as an F-Host, an adjustable range of “1 ... 65534dec”
maximum is permitted for the F-Addresses of the safety modules used (F_Dest_Add /
F_Destination_Address). Please note the following points:
– Only assign F_Dest_Add values once.
– For safety modules from Phoenix Contact, you can set PROFIsafe destination
addresses from 1 to 999dec maximum.
– For safety modules from other manufacturers, you can set PROFIsafe destination
addresses from 1 to 65534dec.
• In the “F_Parameter” view, check the setting for the F_Dest_Add F-Address.
• Set F_Dest_Add to the value that corresponds to the DIP switch setting of the safety
module.
• In the example, set F_Dest_Add for the safety modules used to the following values:
– “1” for the AXL F PSDO8/3 1F (see Figure 6-26)
– “2” for the AXL SE PSDO4/2 2A
– “3” for the AXL SE PSDI8/3
• If necessary, adapt the F_Dest_Add values to your application.
For further information on selecting the watchdog time, please refer to Section 3.3 on
page 31.
In the “Profisafe – summarizing diagnostic variables” view, you can specify which manage-
ment/diagnostic variables are to be globally generated once for all PROFIsafe F-Devices
configured in the project (see Figure 6-31).
Created variables are displayed in the “Data List” editor of the controller node:
For the three F-Devices used in the example, PLCnext Engineer creates
21 management/diagnostic variables by default.
After you have created the exchange variables, you need to specify the data direction (I/Q).
Data direction Set the data direction for the exchange variables. Refer to the information provided at the
start of this section on page 101.
• Set the data direction in turn for each variable created earlier as shown in Figure 6-35.
For further information on opening and creating POUs, please refer to Section “Creating
a POU” on page 90.
For detailed notes on operating the PLCnext Engineer software, please refer to the online
help for the software.
When you create a project, a POU with the name “S_Main” is created automatically for
safety-related controllers in the “COMPONENTS” area under “Programs” (see Figure 6-23
on page 91).
• Click on “Programming (x)” in the “COMPONENTS” area.
• Then click on the arrow next to “Local (x)”, then on “Programs (x)”.
• Double-click on the desired safety-related POU (in the example: “S_Main” program).
The editor group for the selected POU opens.
Variables in the example The following table lists the safety-related variables used in the safety-related example pro-
project gram.
Figure 6-36 Creating variables for a POU (in the example: for the “S_Main” POU)
Selecting diagnostic/man- Before the diagnostic/management variables and exchange variables that you created ear-
agement variables and ex- lier can be used in the code worksheet, you must select these variables in the variables
change variables worksheet.
• Select the “Variables” editor.
• Open the selection list by clicking on the arrow in the “Name” field (see Figure 6-37).
Once you have created all of the necessary variables, create the program for the selected
POU, see Section 6.9.7.
Safety-related example The safety-related example program in Figure 6-38 on page 107 includes the following
program functions:
– In the first part of the example, two inputs of the safety-related AXL SE PSDI8/3 input
module are linked to two outputs of the safety-related AXL SE PSDO4/2 2A.
– In the second part of the example, two inputs of the safety-related AXL SE PSDI8/3
input module are linked with AND logic via the safety-related AND_S function block.
The result will be linked to an output of the safety-related AXL F PSDO8/3 1F output
module.
– In the third part of the example, exchange variables for the safety-related
AXL SE PSDI8/3 input module from the “Exchange” variable group will be linked with
the diagnostic/management variables. In the example, the passivation of an F-Device
will be canceled via the variables with an operator acknowledge request and subse-
quent operator acknowledge reintegration (see Section “Operator acknowledge” on
page 118).
The input/output variables are connected to process data in due course.
The errors and warnings shown in Figure 6-38 on page 107 (color-coded input and output
variables in networks 1 to 3) are due to the fact that no process data has yet been assigned
to these variables. You will execute this step in the following section.
The following figure shows all safety-related variables created and the assigned process
data:
User authentication
If necessary, refer to the note on user authentication in Section 6.6.4.
• If necessary, enter the user name and password in the dialog that opens.
The non-safety-related project will be compiled and transferred to the controller. Project ex-
ecution will be initiated.
If the non-safety-related commissioning has been completed successfully, the controller
changes to the RUN state, indicated by the RUN LED continuously lit green.
If the system cannot be commissioned, for example due to an installation error, a corre-
sponding error message appears in PLCnext Engineer.
The LEDs on the controller indicate this status. Read further information on the controller
diagnostics and status indicators in the UM EN AXC F X152 user manual.
The SPLC 1000 is in the safe state (Failure State) because so far, a safety-related project
has not been transferred to the SPLC 1000.
User authentication
If necessary, refer to the note on user authentication in Section 6.6.4.
• If necessary, enter the user name and password in the dialog that opens.
Specifying the SPLC 1000 The SPLC 1000 is protected by a controller password. Writing data to the SPLC 1000 or
controller password changing its operating mode is only possible after entering the controller password in
PLCnext Engineer.
If this is the first time you are establishing a connection to the SPLC 1000,
PLCnext Engineer will prompt you to specify a controller password.
• Specify a controller password, if you have not already done so, and the following dialog
will be displayed.
Please note: read information dialogs carefully and follow the instructions
provided
If information dialogs appear, please refer to the online help for the PLCnext Engineer
software for further information.
• Acknowledge the messages in accordance with your application.
In the example:
Make sure no hazard is posed when the SPLC 1000 is started and/or stopped, e.g., after
downloading a project.
Ensure the safety function is in order.
Figure 6-45 Info dialog: Avoid any hazard posed when starting and stopping the
SPLC 1000
The project will be compiled and transferred to the SPLC 1000. Execution of the safety-
related project will be initiated and the SPLC 1000 switches to the “RUN” state.
If commissioning was successful, the RUN LED is continuously lit green.
Figure 6-46 Safety Cockpit: SPLC 1000 in the “RUN” state – Safe Run
If the system cannot be commissioned, for example due to an installation error, a corre-
sponding error message appears in PLCnext Engineer.
The LEDs on the SPLC 1000 indicate this status (see Section “Diagnostic and status indi-
cators” on page 47).
• Click on the button (“Enables or disables the monitoring mode for safety-related
editors to see online values.”).
• Open the instance editor of the “S_Main” POU by double-clicking on the “S_Main :
S_Main” node.
The online values of the variables used in the “S_Main” POU are displayed in the “Variables”
and “Code” editors.
Figure 6-47 “Variables” editor (S_Main): Online values of the variables used
Figure 6-48 “Code” editor (S_Main): Online values of the variables used
• To enable debug mode, click on the button (“Enables or disables the debug mode
at the safety-related PLC.”).
WARNING:
Switching to debug mode means that you will exit normal mode.
Make sure that your system/machine cannot pose a hazard to people or equipment.
P RUN
C FS
UL
109449A014
Figure 6-50 LEDs in debug mode
Refer to Section “Diagnostic and status indicators” on page 47 for additional information
on the LEDs.
• To disable debug mode and switch to safe mode, click on the button.
WARNING:
Make sure that your system/machine cannot pose a hazard to people or equipment.
In the following example, the communication relationship between the AXL SE PSDI8/3
F-Device and the SPLC 1000 is broken. The subsequent passivation of the F-Device
prevents it from starting up again immediately once the communication relationship is re-
established. This passivation is indicated by the Boolean diagnostic/management variable
F_ADDR_00003_PASS_OUT.
Once the communication relationship has been re-established successfully, the passivated
F-Device signals an operator acknowledge request via the Boolean
diagnostic/management variable F_ADDR_00003_ACK_REQ. The F-Device thus waits for
a reintegration acknowledgement.
Setting the Boolean exchange variable AXLSE_PSDI_ACK_REI in the non-safety-related
part of the example program cancels the passivation of the F-Device. As a result, the
F-Device can be reintegrated into the network and can re-establish the communication
relationship.
The following Figure 6-52 shows the passivated AXL SE PSDI8/3 F-Device.
In the example in Figure 6-52, the safe inputs and outputs have entered the SAFEFALSE
state. This behavior is due to the passivation of the F-Device.
You will find further information on diagnostics for, among others, PLCnext Technology,
Axioline F and PROFINET online at the listed addresses, in the listed user manuals, and
in the PLCnext Engineer online help function:
– PLCnext Community at plcnext-community.net
and in particular in the PLCnext Info Center
– “Installing, commissioning, and operating the AXC F 1152, AXC F 2152, and
AXC F 3152 controllers” (UM EN AXC F X152)
– “Axioline F: Diagnostic registers and error messages” (UM EN AXL F SYS DIAG).
Refer to the device-specific user documentation for the F-Devices being used.
The diagnostic and monitoring function integrated in the SPLC 1000 detects errors that
have occurred. All serious errors detected in the SPLC 1000, which can lead to the loss of
or adversely affect the programmed safety function, switch the device to the failure state. In
this state, the outputs of the F-Devices are set to zero after the parameterized F_WD_TIME
for the relevant output has elapsed at the latest. The PROFIsafe system switches to the safe
state.
For detailed information on diagnostics in the PLCnext Engineer software, please refer to
the online help for the software.
Important notes:
Configuration memory
The terms “SD card” and “(pluggable) configuration memory” used in this user manual are
synonyms.
Phoenix Contact
If the measures/remedies listed in the following tables do not help to remove the error,
please contact your nearest Phoenix Contact representative.
7.3.1 Errors and error codes of the SPLC 1000 as the F-Host
The product documentation for the modules used contains an overview of the diagnosed
errors, their causes, effects, and possible measures for error removal. It also includes in-
formation regarding module behavior following acknowledgment of diagnostic messages.
• For every error that occurs, the cause of the error must first be removed. If necessary,
the error is then acknowledged.
Phoenix Contact provides special function blocks for device-specific diagnostics for the
Axioline F backplane bus system. These function blocks enable global or local device-spe-
cific diagnostics.
For this purpose, the AsynCom_PN_1 function block from the AsynCom_9 library for
PLCnext Engineer must be used. This function block is used for reading information of the
connected PROFINET devices. The function block receives this information from the con-
figuration of the SPLC 1000 (device IDs, PROFINET names, etc.).
In addition, function blocks from the PN_Dev_Diag_5 library for PLCnext Engineer
must also be used. An example of device-specific PROFIsafe diagnostics is the
PNFD_AXL_Diag_2 function block. This function block is used to perform diagnostics on
a safety-related device of the Axioline F product group via the PROFIsafe address.
Displayed diagnostic messages can be confirmed (acknowledged) with the help of the
function block.
This section describes the system variables that are available for the SPLC 1000.
The SPLC 1000 has a register set that is used for diagnostics and simple control of the
SPLC 1000.
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 (sys-
tem flags, global variables).
Alternatively, you can open the “Data List” editor via the controller node in the “PLANT”
area.
The Init Value Configuration for the selected system variable organized as a data structure
opens below the “Data List” editor.
Figure 8-1 Example AXC F 3152: Init Value Configuration for the SPLC system vari-
able organized as a data structure (SPNSV2_TYPE data type)
The “Member name” column in the Init Value Configuration displays all the system variables
contained in the system variable which is organized as a data structure.
Table 8-1 SPLC system variable and elements of the SPNSV2_TYPE data structure
System variable/elements Type Meaning
SPLC SPNSV2_TYPE The SPLC system variable provides the information in the
SPNSV2_TYPE data structure.
PRJ
NAME STRING PLCnext Engineer project name.
CRC DWORD Project CRC (32 bits) of the SPLC 1000 boot project.
EXEC_TIME UDINT Runtime of the SPLC 1000 program cycle in µs.
HAS_PRJ BOOL The safety-related application program and the program sources
are contained in the memory of the SPLC 1000.
DIAG
STATUS_REG WORD Diagnostic status register of the SPLC 1000
The diagnostic status register of the SPLC 1000 contains the sta-
tus information of the SPLC 1000. It mirrors the state of the
SPLC 1000 at all times including any error states that have oc-
curred on the SPLC 1000. Additional information and error pa-
rameters, in particular in the failure state (FS), are included in the
relevant diagnostic parameter registers of the SPLC 1000 (ele-
ments SPNS.DIAG.PARAM_REG and SPNS.DIAG.PARAM_2).
The information in the diagnostic status register is detailed in
Table 8-2 on page 137.
PARAM_REG WORD Diagnostic parameter register 1 of the SPLC 1000 (error code).
PARAM_2_REG WORD Diagnostic parameter register 2 of the SPLC 1000 (additional
error messages for service/support).
EXT_PARAM_REG DWORD Extended diagnostic parameter register of the SPLC 1000 (addi-
tional error messages for service/support).
CH2_PARAM_REG WORD Diagnostic parameter register 1 of the SPLC 1000 channel 2
(CH2) (error code).
CH2_PARAM_2_REG WORD Diagnostic parameter register 2 of the SPLC 1000 channel 2
(CH2) (additional error messages for service/support).
CH2_EXT_PARAM_REG DWORD Extended diagnostic parameter register of the SPLC 1000 chan-
nel 2 (CH2) (additional error messages for service/support).
INFO
CYCLE_TIME UDINT SPLC 1000 cycle in µs
TEMP
TEMP_CURRENT INT Currently measured SPLC 1000 temperature
Table 8-1 SPLC system variable and elements of the SPNSV2_TYPE data structure
System variable/elements Type Meaning
TEMP_MIN INT Minimum measured SPLC 1000 temperature since the last
power-on of the device.
TEMP_MAX INT Maximum measured SPLC 1000 temperature since the last
power-on of the device.
STATUS_REG WORD SPLC 1000 temperature status register
0x0000: The temperature of the SPLC 1000 is in the non-critical
range.
0x0080: The temperature of the SPLC 1000 is in the critical
range, close to the tolerance threshold. The
SPLC 1000 remains in RUN state and, in parallel, is-
sues a warning with error code 0xFA41.
0x8000: The temperature of the SPLC 1000 is beyond the per-
mitted range. The SPLC 1000 goes into safe state and
issues an error message with error code 0x924D.
CPU
LOAD_CURRENT INT Current SPLC 1000 CPU load
LOAD_MIN INT Minimum measured SPLC 1000 CPU load since the last power-
on of the device.
LOAD_MAX INT Maximum measured SPLC 1000 CPU load since the last power-
on of the device.
STATUS_REG WORD SPLC 1000 CPU status register
FW_VERSION
VERSION_MAJOR BYTE Major version of the SPLC 1000 firmware
VERSION_MINOR BYTE Minor version of the SPLC 1000 firmware
VERSION_BUILD WORD Build number of the SPLC 1000 firmware
FPGA_VERSION
VERSION_MAJOR BYTE Major version of the SPLC 1000 hardware FPGA
VERSION_MINOR BYTE Minor version of the SPLC 1000 hardware FPGA
VERSION_BUILD WORD Build number of the SPLC 1000 hardware FPGA
NUM_OF_ACTIVE_ARS UINT Number of active PROFINET application relations (AR)
FW_UPDATE_STATUS UINT Status of safety-related firmware update
SOFT_RESET_REG WORD Software reset register of the SPLC 1000
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
FS POST Res. EST Res Res. Res Res WARN DBG RUN I/O SYN PRO INIT PON
. . .
Bits 0 to 4
Bits 0 to 4 indicate the startup status of the SPLC 1000. The startup sequence of the
SPLC 1000 is divided into the following five steps:
Bits 5 and 6
The RUN and DBG bits indicate the operating status of the SPLC 1000.
Bits 7 and 10
WARN The set WARN (WARNING) bit indicates a group warning message of the SPLC 1000.
Bit 12
EST The EST (error stack) bit indicates that diagnostic and error messages for the safe
SPLC 1000 operating system are present. These messages can be read and evaluated via
PLCnext Engineer.
This bit is always set if there is at least one entry in the error memory of the safe operating
system. As soon as the error memory has been read and emptied via PLCnext Engineer,
this bit is automatically reset to zero.
Bit 14
Bit 15
FS Failure State
This bit is set as soon as an error has been detected, which sets the SPLC 1000 to the fail-
ure state. The corresponding additional error code is included in this state in the diagnostic
parameter registers of the SPLC 1000 (SPLC.DIAG.PARAM_REG and
SPLC.DIAG.PARAM_2_REG).
Res. Reserved
Table 8-4 SPLC_PROFISAFE_DIAG system variable and elements of the PROFISAFE_DIAG_OUT structure
SPLC_CONTROL_COMMAND
This system variable requests the resetting of diagnostic values from the non-safety-related
project.
Table 8-5 SPLC_CONTROL_COMMAND system variable and elements of the SPNS_CONTROL_TYPE data struc-
ture
SPLC_CONTROL_CONFIRM
This system variable shows in the non-safety-related project the acknowledgement from the
SPLC 1000 that diagnostic values have been reset.
Table 8-6 SPLC_CONTROL_CONFIRM system variable and elements of the SPNS_CONTROL_TYPE data struc-
ture
WARNING:
Resetting this variable to FALSE means that the safe input
and output data is transmitted immediately.
Take appropriate measures to ensure that your system/
machine does not present any danger when passivation of
the F-Device is reset.
WARNING:
Depending on the application, applying the iParameters
can result in hazardous states
Take appropriate measures to ensure that your system/
machine does not present any danger when the applica-
tion of the iParameters is initiated and/or iParameters are
applied.
F_ADDR_XXXXX_CHF_ACK_REQ *) BOOL A channel error in the F-Device can be acknowledged
(CHF_ACK_REQ_S).
(Only for F-Devices in accordance with PROFIsafe profile version
2.6MU1)
F_ADDR_XXXXX_CHF_ACK_REI *) BOO Channel error acknowledgement (CHF_ACK_C)
(Only for F-Devices in accordance with PROFIsafe profile version
2.6MU1)
F_ADDR_XXXXX_CE_CRC_H *) BOOL Communication error (F_CE_CRC_H)
Local F-Host driver reports communication error.
F_ADDR_XXXXX_WD_TIMEOUT_H *) BOOL Communication error (F_WD_TIMEOUT_H)
Local F-Host driver reports communication error.
F_ADDR_XXXXX_LOOPBACK *) BOOL Communication error (loopback check)
Local F-Host driver reports communication error.
*) XXXXX = Number of the F-Device (e.g., F_ADDR_00001_PASS_ON, see Figure 6-32 on page 100)
WARNING:
The variables specified in the table can be toggled. Program an evaluation function in the
PLCnext Engineer software (e.g., using edge detection).
The table below describes management/diagnostic variables, which are globally created in
PLCnext Engineer for all F-Devices. These variables indicate that the condition for setting
these variables applies to at least one configured F-Device. The variables are not created
by default. To create them, the relevant parameters must be set to “Create” in
PLCnext Engineer (see Figure 6-31 on page 99).
In terms of system availability, this type of CRC error should only oc-
cur once every 10 hours at the most (see PROFIsafe specification
regarding “SIL Monitor” and “Operator Acknowledge”).
WARNING:
The variables specified in the table can be toggled. Program an evaluation function in the
PLCnext Engineer software (e.g., using edge detection).
WARNING:
Resetting this variable to FALSE means that the safe
input and output data is transmitted immediately.
Take appropriate measures to ensure that your sys-
tem/machine does not present any danger when pas-
sivation of the SPLC 1000 (F-Device) is reset.
WARNING:
Depending on the application, applying the
iParameters can lead to dangerous states. Take
appropriate measures to ensure that your
system/machine does not present any danger when
the application of the iParameters is initiated and/or
iParameters are applied.
F_ADDR_[nnnn]_IPAR_OK_DEV *) BOOL The SPLC 1000 (F-Device) reports “adoption of the iParameters”.
This variable is set when the SPLC 1000 (F-Device) indicates that
it has adopted the iParameters.
F_ADDR_[nnnn]_DEVICE_FAULT_DEV *) BOOL Error in the SPLC 1000 (F-Device).
If this variable was set to TRUE during operation, the cause of the
error must be removed first to enable the superordinate safety-
related controller (F-Host) to carry out acknowledgment and
reintegration. If the cause has been removed, the
F_ADDR_[nnnn]_DEVICE_FAULT_DEV variable is set to
FALSE again.
F_ADDR_[nnnn]_CHF_ACK_REQ_DEV *) BOOL A channel error in the SPLC 1000 (F-Device) can be acknowl-
edged.
F_ADDR_[nnnn]_CHF_ACK_REI_DEV *) BOOL Channel error acknowledgement
F_ADDR_[nnnn]_WD_TIME_OUT_DEV *) BOOL Communication error (F_WD_TIME_OUT)
Set if the SPLC 1000 (F-Device) has detected a communication
error caused by the parameterized F_WD_Time being exceeded.
If this variable was set to TRUE during operation, the cause of the
error must be removed first to enable the superordinate safety-
related controller (F-Host) to carry out acknowledgment and
reintegration. If the cause has been removed, the
F_ADDR_[nnnn]_WD_TIME_OUT_DEV variable is set to
FALSE again.
*) [nnnn] = F_Destination-Adresse (F_Dest_Add) of the SPLC 1000 used in the application as an F-Device is in the
range: 1 ... 65534.
WARNING:
The variables specified in the table can be toggled. Program an evaluation function in the
PLCnext Engineer software (e.g., using edge detection).
WARNING:
The variables specified in the table can be toggled. Program an evaluation function in the
PLCnext Engineer software (e.g., using edge detection).
9 Removing hardware
For basic information on the Axioline F system and its installation, particularly mount-
ing/removing Axioline F modules, please refer to the UM EN AXL F SYS INST user man-
ual (“Axioline F: System and installation”).
Please note:
During any work on the Axioline F station, the SPLC 1000, the PLCnext Control device, or
a module, switch off the power supply to the Axioline F station and make sure the supply
voltage is protected against unauthorized reactivation.
A
B
B
A
Figure 9-3 SPLC 1000: Removing the connector
A A
B . 240
426
7
AXC
.XX
F 21
.XX
52
.XX
.XX
SD
.XX
-CA
.No
RD
Ord r.: XX
X4
C Add
MA
X1
X2
X2
X1
Please note:
The bus base module of the SPLC 1000 has snap-in latches that are held in place by the
electronics module on the right.
• First remove the electronics module on the right before you pull off and remove the
SPLC 1000 bus base module.
• Remove the bus base module in accordance with the description in the
UM EN AXL F SYS INST user manual.
Read the information on removing bus base modules of the Axioline F modules in the
UM EN AXL F SYS INST user manual (Axioline F: System and installation).
Observe the device type The replacement device must satisfy the following conditions:
and version – Same device type (pos. 1 in Figure 3-15 on page 46)
– Same or later version (pos. 4 in Figure 3-15 on page 46)
Procedure If you want to replace the device, proceed in accordance with the following section:
– “Removing hardware” on page 153
– “Mounting hardware” on page 51
– “Connecting and wiring the hardware” on page 61
– “Commissioning and validation” on page 67
• Disconnect the Axioline F station from the power supply.
• Replace the SPLC 1000 in your application with an identical device (same item
number).
• Once the controller is replaced, restore all the necessary connections.
Device defects/repairs Please contact Phoenix Contact. Repairs may only be carried out by Phoenix Contact.
• Send defective devices back to Phoenix Contact for repair or to receive a replacement
device.
• We strongly recommend using the original packaging to return the product.
• Include a note in the packaging indicating that the contents are returned goods.
• Where possible, provide a detailed description of the errors that have occurred.
• If the original packaging is no longer available, observe the following points:
– Observe the humidity specifications and the temperature range specified for trans-
port (see Section “Technical data” on page 168).
– If necessary, use dehumidifying agents.
– Use suitable ESD packaging to protect components that are sensitive to electro-
static discharge.
– Secure any loose parts.
– Make sure that the packaging you select is large enough and the material is suffi-
ciently thick.
– Only use plastic bubble wrap sheets as wadding.
– Attach warnings to the transport packaging so that they are clearly visible.
– Please be aware that the delivery note is to be placed inside the package if the
package is sent within the same country. If the package is being sent abroad, the
delivery note must be placed inside a delivery note pocket and attached to the out-
side so that it is clearly visible.
11.1 Maintenance
The device is maintenance-free.
Device disposal • Do not dispose of the device with household waste; it should be disposed of in accor-
dance with the currently applicable national regulations.
Packaging disposal • Dispose of packaging materials that are no longer needed (cardboard packaging,
paper, bubble wrap sheets, tubular bags, etc.) with household waste in accordance
with the currently applicable national regulations.
Make sure that the basic specifications of a PROFINET controller (e.g., maximum number
of PROFINET devices that can be connected) cannot be exceeded by deactivating
devices in the configuration.
In the “Settings” editor of the PROFINET device, you must specify whether the controller
establishes an application relationship when the PROFINET device is started.
When set to “No”, an application relationship is created for each PROFINET device but is
not started; it remains inactive. In this case, an application relationship to the PROFINET
device can be established using the AR_MGT function block (see Section “Function block
for managing PROFINET application relationships (AR)” on page 163).
When set to “Yes”, the PROFINET device is started up directly. If an application relationship
is not started, the PROFINET device is not started up.
This option is set to “Yes” by default.
The function block supports multiple instantiation. The maximum possible number of func-
tion block instances that can be activated simultaneously is limited by the maximum number
of application relationships permitted by the PROFINET controller.
If the connection to a PROFINET device is interrupted, the “Set to zero” option means that
the corresponding input data of the PLCnext Control is set to zero. The “Keep values” option
means that if the connection to a PROFINET device is interrupted, the input values that were
valid immediately before the interruption are present as the input data in the application pro-
gram.
When the connection to the PROFINET device is restored, the substitute values remain
valid as input data until the PROFINET device has been started up completely. Once the
connection has been established again, the latest input data is used.
13.1.2 Controller
13.1.3 Modules
13.1.4 Accessories
13.1.5 Software
13.1.6 Documentation
Information on troubleshooting and answers to frequently asked questions (FAQs) can be found in the
PLCnext Community at plcnext-community.net.
Axioline F documentation
User manual UM EN AXL F SYS INST – –
Axioline F: System and installation
User manual UM EN AXL F SYS DIAG – –
Axioline F: Diagnostic registers and error messages
User manual UM EN AXL SE SYS INST – –
Axioline Smart Elements
45 75
126,93
123
Outer dimensions (width x height x depth) 45 mm x 126.93 mm x 75 mm (the depth applies when a
TH 35-7.5 DIN rail is used (in accordance with EN 60715)).
General data
Color Yellow
Weight 142 g
Design Axioline
Mounting type DIN rail mount
Power supply
WARNING: Loss of electrical safety and the safety function when using unsuitable power supplies
The AXC F XT SPLC 1000 is designed exclusively for protective extra-low voltage (PELV) operation according
to EN 60204-1. Only protective extra-low voltages in accordance with the listed standard may be used for the
supply.
The following applies to the network (PROFINET and Axioline F) and the I/O devices used in it:
Only use power supplies that satisfy the requirements of EN 61204-1 and feature safe isolation with PELV in
accordance with IEC 61010-2-201 (PELV). They prevent short circuits between the primary and secondary
side.
Please also observe the information in Section “Electrical safety” on page 16.
Use a power supply without fall-back characteristic curve (see Section “Sizing of the power supply” on
page 61).
Connection data
Designation Axioline F connector
Connection method Push-in connection
Conductor cross-section, rigid/flexible 0.2 mm2 ... 1.5 mm2 / 0.2 mm2 ... 1.5 mm2
Conductor cross-section [AWG] 24 ... 16
Stripping length 8 mm
Protective circuit
Polarity reversal protection for supply voltage Polarity protection diode
Transient protection Suppressor diode
Ambient conditions
Ambient temperature (operation) -25°C ... 60°C up to 2,000 m above mean sea level
-25°C ... 55°C up to 3,000 m above mean sea level
-25°C ... 50°C up to 4,000 m above mean sea level
Ambient temperature (storage/transport) -40°C ... 85°C
Permissible humidity (operation) 5% ... 95% (in accordance with DIN EN 61131-2)
Permissible humidity (storage/transport) 5% ... 95% (in accordance with DIN EN 61131-2)
Air pressure (operation) 70 kPa ... 106 kPa (up to 3000 m above mean sea level)
Air pressure (storage/transport) 58 kPa ... 106 kPa (up to 4500 m above mean sea level)
Degree of protection IP20
To ensure correct operation, the AXC F XT SPLC 1000 must be installed in a lockable housing or a lockable
control cabinet with a minimum degree of protection of IP54.
Approvals
For information on the current approvals, visit phoenixcontact.net/product/1159811.
Reintegration Removal of passivation for the reintegration of previously passivated F-Devices (see also
“Passivation”).
F-Parameters (In accordance with PROFIsafe System Description, version April 2016)
F-Parameters contain information for adapting the PROFIsafe layer to specific customer
specifications and for checking the parameterization by means of a separate method (di-
verse). The main F-Parameters are:
F_Source_Address / Unique address for F-Devices within a PROFIsafe island. The
F_Destination_Address / technology part of the F-Device compares the value with the
F_Source_Add / local address switch or with an assigned F-Address in order to
F_Dest_Add (F-Address check authenticity of the connection.
for short)
As of PROFIsafe profile V2.6.1, a distinction is made between
two address types, which must be specified by the manufac-
turer in the F-Device-specific user documentation:
Address type 1: The F-Device only checks the
F_Destination_Address.
Address type 2: The F-Device checks the
F_Destination_Address and the
F_Source_Address.
F_WD_Time Specifies the time for the watchdog timer in milliseconds. The
timer monitors the time that elapses until the next valid
PROFIsafe message is received.
F_SIL Indicates the SIL that the user can expect from the relevant
F-Device. It is compared with the manufacturer‘s specification
that is stored locally.
F_iPar_CRC Checksum that is calculated from all iParameters of the tech-
nology-specific part of the F-Device.
F_Par_CRC CRC signature that is created across all F-Parameters and
ensures error-free transmission of the F-Parameters.
Passivation If the safety module detects an error, it switches the affected channel or all channels of the
module to the safe state; the channels are then passivated. The detected errors are re-
ported to the safety-related controller.
For a safe input module, when passivation is enabled, substitute values (0) are provided for
the safety program instead of the process values present at the safe inputs.
For a safe output module, when passivation is enabled, substitute values (0) are transferred
to the safe outputs instead of the output values provided by the safety program.
PROFIsafe Safety-related bus profile based on PROFIBUS DP or PROFINET. It defines the communi-
cation between a safety program and the safe I/O devices in a safe system.
PROFIsafe address Each safe module has a PROFIsafe address. This address must be set on the safety mod-
ule via DIP switches, for example, and then configured in the configuration tool for the
safety-related controller used.
PROFIsafe monitoring Monitoring time for safety-related communication between the SPLC 1000 and the safe
time I/O devices.
This time is parameterized in the F_WD_Time F-Parameter.
B Appendix: Checklists
Key:
Device type/equipment identi- Enter the device type and/or the equipment identification for the relevant device.
fication
Version: Enter the hardware and firmware version of the device (see revision specification on the
HW/FW label, item 4 in Figure 3-15 on page 46).
Date Enter the date on which you began to fill in this checklist.
Editor Enter the name of the editor.
Test engineer Enter the name of the test engineer.
Comment Where necessary, enter a comment.
Requirement (mandatory) These requirements must be met for a safety application, in order to complete the relevant
phase using the checklist.
Requirement (optional) These requirements are optional. For points that are not met (No), please enter an appro-
priate remark in the relevant field.
B1 System-specific checklists
This section contains checklists that relate to the phases of life of the PROFIsafe system.
B 1.1 Planning
Date
Comment
No. Requirement Yes Comment
1 Have the applicable standards for the system/machine been selected
and are the resulting requirements known for each safety function and
phase of life of the system/machine?
2 Has risk assessment for the system/machine been carried out?
5 Does the planned PROFIsafe system meet the required safety integrity
for all defined safety functions?
6 Has the power supply been planned in accordance with the specifica-
tions on protective extra-low voltage (PELV) in accordance with
EN 60204-1 (including safe isolation with PELV in accordance with
IEC 61010-2-201)?
7 Has the maximum permissible response time (SFRT) for each individual
safety function within the PROFIsafe system in your system/machine
been determined and documented?
8 Can the planned system/machine be implemented when the determined
SFRT is observed with the specified PROFINET infrastructure?
9 Can the planned application be realized with the programming capaci-
ties (for example by using function blocks) and has a specification of the
safety-related application program been created?
10 Have the user rights for the safety-related application program been
specified in the PLCnext Engineer software?
11 Has a project password been provided?
14 Were the settings for user authentication defined in the web-based man- Names:
agement system of the PLCnext Control used?
15 Has the location where the software is to be installed (e.g., on the sys-
tem PC) been specified?
B 1.2 Programming
11 Has project information been entered in the “Description” field in the Type:
“Properties” editor in the “Project” editor group?
Location:
12 Are possible reciprocal effects due to exchange variables between the
programming of the standard controller (PLCnext Control) and the
SPLC 1000 taken into consideration and clear?
13 Has the following been observed when programming/configuring your
safety logic?
– Switching from the safe state (substitute value = 0) to the operating
state can generate an edge change (zero/one edge).
– In the safety logic, take measures to prevent this edge change re-
sulting in unexpected machine/system startup or restart.
Date Signature (editor)
B 1.3 Commissioning
Date
Comment
No. Requirement Yes Comment
1 Have the requirements from the applicable standards for the sys-
tem/machine been observed and met in the commissioning phase?
2 Is safety ensured during the commissioning phase by means of addi-
tional measures and if so what are these measures (see also No. 1)?
1 ______________________________________________________
2 ______________________________________________________
3 ______________________________________________________
4 ______________________________________________________
5 ______________________________________________________
6 ______________________________________________________
7 ______________________________________________________
8 ______________________________________________________
9 ______________________________________________________
10 _____________________________________________________
Additional requirements in: __________________________________
3 Are adjustments to the F_WD_Time min required in order to ensure
ruggedness of the system and system availability, since the actual
SPLC 1000 cycle time may deviate from the SPLC 1000 cycle time
estimated during the planning phase?
B 1.4 Validation
Date
Comment
No. Requirement Yes Comment
1 Have the requirements from the applicable standards for the
system/machine been observed and met for validation?
2 Have the requirements from the previous planning, programming, and
commissioning phases been met?
3 Has validation of the F-Devices used been carried out and are the
results available?
4 Have safety distances to be observed been calculated and checked
according to the implemented response and delay times (response
times, SFRT, F_WD_Time max)?
5 Have all the safety functions been checked successfully?
6 Do the two CRC checksums displayed in the “Safety PLC” editor group
in the “Safety Cockpit” editor in the “Overview” view (“Safety PLC project
information” and “Engineering project information”) match?
If you are connected online to the safety-related controller, the
checksums are displayed in PLCnext Engineer.
7 Have measures against unauthorized network access been imple-
mented and checked?
12 Completion of validation
Has the latest program version (including the “Project information”) been
downloaded to the safety-related SPLC 1000 controller on automatic
startup?
Have organizational or technical measures been introduced for check-
ing the CRC checksum expected for the respective system/machine
after a voltage reset or system restart? The CRC checksum is displayed
by the CRC element of the SPLC system variable (see Table 8-1 “SPLC
system variable and elements of the SPNSV2_TYPE data structure”).
B2 Device-specific checklists
This section contains checklists that relate to the phases of life of the SPLC 1000.
B 2.1 Planning
Comment
No. Requirement Yes Comment
1 Has the systematic “Planning” checklist been observed?
2 Are all measures that are based on applicable standards and the PROFINET
Assembling Guideline planned?
3 Has the current AXC F XT SPLC 1000 user manual been used as the basis for
planning?
4 Have the power supply for the device and direct I/Os been planned as per the
specifications for protective extra-low voltage (PELV) in accordance with
EN 60204-1 (including safe isolation with PELV in accordance with
IEC 61010-2-201)?
5 Are measures planned to prevent simple tampering? If so, what are they?
1 _____________________________________________________________
2 _____________________________________________________________
3 _____________________________________________________________
4 _____________________________________________________________
5 _____________________________________________________________
6 Does the planned use correspond to the intended use?
7 Have the ambient conditions according to the technical data been observed?
8 Has the degree of protection been observed?
9 Have the accessories to be used been planned in accordance with the ordering
data in this user manual (cables, plugs)?
10 Have specifications for assembly and electrical installation been defined (e.g.,
EPLAN) and communicated to the relevant personnel?
11 Have specifications for parameterization been defined and communicated to the
relevant personnel?
12 Have specifications for startup been defined and communicated to the relevant
personnel?
13 Has the technical data of the interfaces been observed?
Date Signature (editor)
Checklist for assembly and electrical installation of the AXC F XT SPLC 1000
Device type/equipment identification
Version:
Date
HW/FW
Editor Test engineer
Comment
No. Requirement Yes Comment
1 Has assembly and electrical installation been carried out according to
the specifications of the planning phase?
2 Has assembly and electrical installation been carried out according to
the specifications in the user manual for the AXC F XT SPLC 1000?
3 Has assembly and electrical installation been carried out according to
the specifications of the applicable standards and the PROFINET
Assembling Guideline?
4 Have the power supply for the device and direct I/Os been installed as
per the specifications for protective extra-low voltage (PELV) in
accordance with EN 60204-1 (including safe isolation with PELV in
accordance with IEC 61010-2-201)?
5 Have measures been taken to prevent simple tampering (e.g., control
cabinet can be locked, PLCnext Engineer access rights (user authoriza-
tion), etc.)? If so, what are they?
1 ______________________________________________________
2 ______________________________________________________
3 ______________________________________________________
4 ______________________________________________________
5 ______________________________________________________
6 ______________________________________________________
7 ______________________________________________________
8 ______________________________________________________
9 ______________________________________________________
10 _____________________________________________________
Date Signature (editor)
Comment
No. Requirement Yes Comment
1 Have the systematic “Programming” and “Startup” checklists been
observed?
2 Was commissioning completed in accordance with the specifications
(specifications from the planning phase and/or in accordance with the
AXC F XT SPLC 1000 user manual, see Table 6-1 “Steps for initial
commissioning of the SPLC 1000”)?
3 Is it ensured that when the supply voltage of the AXC F XT SPLC 1000
is switched on, automatic startup does not cause a hazardous move-
ment on the machine/system?
In addition, refer to the online help for the PLCnext Engineer software.
Comment
No. Requirement Yes Comment
1 Has the systematic “Validation” checklist been observed?
2 Have all the requirements of the “Planning” checklist been met?
3 Have all the requirements of the “Assembly and electrical installation”
checklist been met?
4 Have all the requirements of the “Commissioning and parameterization”
checklist been met?
5
5a Initial commissioning:
Has a function test been performed to check all the safety functions in
which the AXC F XT SPLC 1000 is involved?
5b Recommissioning after replacing the AXC F XT SPLC 1000:
The CRC checksum of the PLCnext Engineer project corresponds to the
version validated and documented for the machine/system under 5a
(see also checklist item No. 12 in Section B 1.4 “Validation”).
6 Does the power supply for the device and direct I/Os comply with the
specifications on protective extra-low voltage (PELV) in accordance
with EN 60204-1 (including safe isolation with PELV in accordance with
IEC 61010-2-201)?
7 Do all cables correspond to the specifications?
8 Wiring check:
Have all the inputs and outputs of all F-Devices physically present in the
network and configured in PLCnext Engineer been wired correctly?
9 Have measures been taken to prevent simple tampering?
Date Signature (editor)
C1 List of figures
Section 1
Section 2
Section 3
Figure 3-1: PROFIsafe: Management/diagnostic variables for communication
diagnostics of the SPLC 1000 F-Host ................................................. 28
Figure 3-2: PROFIsafe: Management/diagnostic variables for communication
diagnostics of the SPLC 1000 F-Device ............................................. 29
Figure 3-3: Calculation of the SFRT response time
( *) = Not necessarily the output device .............................................. 32
Figure 3-4: Simplified calculation of the SFRT response time
( *) = Not necessarily the output device .............................................. 33
Figure 3-5: F_WD_Time (minimum) ...................................................................... 35
Figure 3-6: “Settings” editor of the interface editor group of the
PROFINET device (settings of the AXL F BK PN TPS PROFINET
bus coupler) ........................................................................................ 36
Figure 3-7: “Tasks and Events” editor in the editor group“ / Safety PLC”:
Cycle time setting TZSPLC in ms .......................................................... 37
Figure 3-8: “Settings” editor of the PROFINET editor group of the
AXC F 3152; Update tasks for IO controller system variables
and global variables: SafetyProxyTask ............................................... 37
Figure 3-9: Program runtimeIdle in relation to the number of F-Devices
used. ................................................................................................... 38
Figure 3-10: SPLC 1000 program runtime .............................................................. 39
Figure 3-11: SPLC 1000 program runtime in the example ...................................... 40
Figure 3-12: Online values of the SPLC 1000 cycle time and program
runtime ................................................................................................ 41
Figure 3-13: PLCnext Engineer: “Safety PLC cycle time” ........................................ 41
Figure 3-14: SPLC 1000 connection and operating elements ................................. 45
Figure 3-15: SPLC 1000 printing, including test mark ............................................. 46
Figure 3-16: Diagnostic and status indicators ......................................................... 47
Figure 3-17: Internal basic circuit diagram SPLC 1000 ........................................... 50
Section 4
Figure 4-1: Placing the module vertically ............................................................. 51
Figure 4-2: Mounting positions for the AXC F XT SPLC 1000 in an
Axioline F station ................................................................................ 53
Figure 4-3: Example: Structure of an Axioline F station with left-aligned
safety-related AXC F XT SPLC 1000 controller .................................. 54
Figure 4-4: Removing the supply plug ................................................................... 56
Figure 4-5: Remove electronics module ............................................................... 57
Figure 4-6: Mounting bus base module(s): AXC F 2152 ....................................... 58
Figure 4-7: Mounting bus base module(s): AXC F 3152 ....................................... 59
Figure 4-8: Mounting the bus base modules of further AXC F XT ...
modules .............................................................................................. 59
Figure 4-9: Snapping on electronics modules ....................................................... 60
Figure 4-10: Connecting the supply connector ....................................................... 60
Section 5
Figure 5-1: Overload range with fall-back characteristic curve ............................. 62
Figure 5-2: Overload range without fall-back characteristic curve ....................... 62
Figure 5-3: Connection of the supply voltage ........................................................ 63
Figure 5-4: Terminal points for the supply voltage (communications
voltage UL)........................................................................................... 64
Figure 5-5: Connecting a rigid conductor .............................................................. 64
Figure 5-6: Connecting a flexible conductor .......................................................... 65
Figure 5-7: Connecting the supply connector ....................................................... 65
Section 6
Figure 6-1: Example configuration: The SPLC 1000 as the F-Host with
safety-related communication via the Axioline F local bus and
via PROFINET/PROFIsafe .................................................................. 72
Figure 6-2: Example configuration: The SPLC 1000 as the F-Host with
safety-related communication via PROFINET/PROFIsafe .................. 73
Figure 6-3: Example configuration: The SPLC 1000 as the F-Host with
safety-related communication via the Axioline F local bus .................. 74
Figure 6-4: Example configuration: The SPLC 1000 as the subordinate
F-Device with safety-related communication via
PROFINET/PROFIsafe and as the F-Host with safety-related
communication via the Axioline F local bus ......................................... 75
Figure 6-5: PLCnext Engineer user interface ........................................................ 78
Figure 6-6: Selecting the PLCnext Control AXC F 3152 ........................................ 80
Figure 6-7: Defining a project password ............................................................... 81
Section 7
Figure 7-1: AsynCom_PN_1 function block
(instance: AsynCom_PN_1) ............................................................. 131
Figure 7-2: PNFD_AXL_Diag_2 function block
(instance: PNFD_AXL_Diag_2) ........................................................ 132
Section 8
Figure 8-1: Example AXC F 3152: Init Value Configuration for the SPLC
system variable organized as a data structure (SPNSV2_TYPE
data type) .......................................................................................... 134
Section 9
Figure 9-1: Removing the module vertically ...................................................... 153
Figure 9-2: SPLC 1000: Removing cables .......................................................... 154
Figure 9-3: SPLC 1000: Removing the connector ............................................... 154
Figure 9-4: Unlatching the SPLC 1000 ................................................................ 155
Section 10
Section 11
Section 12
Figure 12-1: PROFINET device – “Start AR on startup” ........................................ 161
Figure 12-2: AR_MGT function block .................................................................... 163
Figure 12-3: PROFINET device – “Substitute value behavior of inputs” ................ 164
Section 13
Appendix A
Appendix B
Appendix C
Appendix D
C2 List of tables
Section 1
Section 2
Section 3
Table 3-1: Diagnostic and status indicators .......................................................... 47
Section 4
Table 4-1: Recommended end brackets............................................................... 52
Section 5
Table 5-1: Feed-in of the supply voltage............................................................... 64
Section 6
Table 6-1: Steps for initial commissioning of the SPLC 1000................................ 68
Table 6-2: Safety-related parameters in the example ........................................... 97
Table 6-3: Input/output variables in the example ................................................ 104
Section 7
Table 7-1: Errors codes of the SPLC 1000 as the F-Host ................................... 124
Table 7-2: Errors codes of the SPLC 1000 as an F-Device................................. 130
Section 8
Table 8-1: SPLC system variable and elements of the SPNSV2_TYPE
data structure..................................................................................... 135
Table 8-2: Elements in the diagnostic status register
(SPLC.DIAG.STATUS_REG.xxx)...................................................... 137
Table 8-3: Diagnostic status register of the SPLC 1000:
SPLC.DIAG.STATUS_REG............................................................... 139
Table 8-4: SPLC_PROFISAFE_DIAG system variable and elements of the
PROFISAFE_DIAG_OUT structure ................................................... 141
Table 8-5: SPLC_CONTROL_COMMAND system variable and elements of
the SPNS_CONTROL_TYPE data structure ..................................... 142
Table 8-6: SPLC_CONTROL_CONFIRM system variable and elements of
Section 9
Section 10
Section 11
Section 12
Section 13
Appendix A
Appendix B
Appendix C
Appendix D
C3 Index
R U
Reintegration................................................................27 User authentication
Reintegration (Depassivation)....................................173 AXC F X152 ........................................................... 25
Reintegration (Reintegration) ....................................173 User name
Repairs .............................................................. 157, 158 AXC F X152 ........................................................... 25
S W
Safe state Watchdog time
Failure State ...........................................................27 F_WD_Time IN ...................................................... 32
Safety Function Response Time F_WD_Time OUT ..................................................32
SFRT......................................................................31
Safety hotline ...............................................................22
SFRT
Safety Function Response Time.............................31
Sizing of the power supply ...........................................61
SPLC 1000
Behavior in the event of an error.............................27
Mounting ................................................................55
Safe state (Failure State)........................................27
Test mark ...............................................................46
Supply connector
Connecting .............................................................65
System-specific checklists
Commissioning.....................................................179
Planning ...............................................................176
Programming........................................................178
Validation .............................................................180
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.
200 / 200 PHOENIX CONTACT GmbH & Co. KG • Flachsmarktstraße 8 • 32825 Blomberg • Germany
phoenixcontact.com
© PHOENIX CONTACT 2021-11-11
E-mail: info@phoenixcontact.com
phoenixcontact.com