About PLCnext Engineer

PLCnext Engineer is a software suite for developing controller-based automation solutions. It includes all engineering disciplines necessary to completely develop and commission an automation application project. These engineering tasks are:

Networking: Structuring of the logical and physical components of the machine to be controlled. This is done by editing the PLANT on the left. The PLANT reflects the automation-relevant parts of the machine.
Structuring can be done by inserting device types from the COMPONENTS area or by scanning the connected network.
Networking includes parameterization of the physical devices involved (for example, controller, Profinet devices, I/O modules).
Programming: Development of the application code. For that purpose, the IEC 61131-3 programming languages FBD/LD, ST and SFC and suitable editors are available. According to the 3rd edition of the IEC 61131-3 standard, object-oriented function blocks with methods can be used. This engineering discipline also includes the controller runtime configuration, i.e., the definition of task/event settings, instantiation of programs, etc.
If a Safety PLC is included in your application, the programming of safety-related code and configuration of the Safety PLC runtime are supported too. See section "Safety integrated" below.
For starting up and commissioning the application, PLCnext Engineer provides an online mode ‣ Debug mode: Monitoring the Application Execution
×‣ Monitoring/Debugging the Safety PLC
×‣ Monitoring Mode: Displaying Online Values
× for monitoring the behavior of the application logic as well as powerful debugging tools ‣ WATCHES: Monitoring/Debugging the Application
×‣ Debugging Code: Forcing/Overwriting
×‣ Debugging Code: Breakpoints
×‣ Debugging Safety-Related Code: Forcing/Overwriting
×‣ WATCHES: Monitoring/Debugging the Safety-Related Application
× (breakpoints, forcing/overwriting, WATCHES window). The LOGIC ANALYZER allows the recording and curve representation of online values.
PLCnext Technology controllers implement a Data Logger service tool which provides a further possibility to record (non-safety-related) data from the running application.
HMI (Human Machine Interface) of the automation application: With the integrated HMI editor, you can design your own HMI application which allows you to visualize, monitor and control the running process. HMI objects/symbols can be animated depending on variable values read from the controller and they can write values in order to control the process.
OPC UA server: PLCnext Technology controllers include an embedded OPC UA server, which is integrated in the controller besides the controller runtime. The OPC UA server is represented by the 'OPC UA' icon in the PLANT and can be configured in PLCnext Engineer via this tree node. Refer to the chapter "OPC UA Server" for details.
OPC UA PubSub communication: PLCnext Technology controllers with a firmware version 22.0 or newer support the OPC UA PubSub (publisher/subscriber) communication model according to Part 14 of the OPC Unified Architecture specification (separate paid license). This enables the controller-to-controller communication independent of the OPC UA server-client model. Refer to the chapter "OPC UA PubSub Communication" for details.

PLCnext Technology controllers supported - the next controller generation by Phoenix Contact

PLCnext Engineer supports the programming and configuration of the PLCnext Technology controller generation.

The use of ports (in addition to or instead of resource-global variables) in PLCnext Engineer as well as the core-specific creation of tasks and the instantiation of externally created non-IEC 61131-3 programs (developed, for example, with C++) enables the unrestricted use of the controllers with the new PLCnext Technology firmware architecture by Phoenix Contact.

Refer to the topic "PLCnext Technology Controller Generation" for details.

Safety integrated

PLCnext Engineer supports the complete implementation of a safety-related application if a Safety PLC is included in your project. This includes the adding of safety-related devices to the PLANT, safety-related device parameterization, programming of safety-related code including the assignment of safety-related I/Os.

In the project, the standard (non-safety-related) controller and the Safety PLC are strictly separated. Each of it executes its own application, has its own global variables, and its own runtime configuration. Therefore, the Safety PLC is represented by its own icon in the PLANT. The safety-related project data (device structure, code, and device parameterization) as well as the configuration and operation mode of the safety-related controller are protected by two separate passwords. For editing safety-related parts of the project, you have to logon to the Safety-related Area.

Safety-related code and data processed in and generated by PLCnext Engineer is based on the IEC 61131-3 standard and meets the safety requirements defined in the standards IEC 61508, EN IEC 13849 and EN 62061 (depending on the language profile set in the project).

Further Info
Refer to the topics "Safety-related Application" and "Safety-Related Area with Password Protection" for details.

Security concept

PLCnext Engineer implements security-related features in several aspects, such as user access control, certificates for securing the communication connection between controller and engineering software, or library tamper protection. These features are described in separate chapters or in the context of the corresponding software component.

Note
Besides the security-related features provided by PLCnext Engineer, you as a user have to observe particular security rules and take suitable measures to protect your programming system, controller and project/configuration data against malicious or erroneous change.

Further Info
In topic "Security in PLCnext Engineer" an overview on these security-related rules and implementations is given and links to detailed information are provided.

Automation Modules

PLCnext Engineer provides the possibility of using Automation Modules, which are used together with so-called Aspect Hierarchies. Automation Modules can only be activated together with Aspect Hierarchies. Refer to the chapter "Automation Modules and Aspect Hierarchies" for details.

Note
The use of Automation Modules is a tool extension and has to be enabled in the 'Options' dialog. Select 'Extras > Options | Extensions | Aspect Hierarchies' and mark the 'Enable Hierarchies' checkbox. After restarting PLCnext Engineer, the PLANT provides new views and the category 'Automation Modules' is available in the COMPONENTS area.

Role mapping in Data Lists: logical interlinking of engineering disciplines

In traditional programming systems, the mapping of IEC 61131-3 data, bus configuration data and HMI data was mostly laborious because the different engineering tasks were located in different views or even in external tools. PLCnext Engineer introduces a new philosophy called Role Mapping which considerably simplifies the mapping of IEC 61131-3 data, process data and HMI data.

Role mapping is also possible for ports of PLCnext Technology controllers.

Refer to the topic "Data List" for details.

IEC 61131-3 beginner or coming from PC WORX 6.x?

Depending on your starting situation, the following help topics may be helpful:

"Coming from PC WORX 6.x" lists the main differences between the PC WORX 6.x suite and PLCnext Engineer. This topic is recommended to lateral entrants for a first orientation.
"Quickstart: Overview on Engineering Steps" gives a brief outline of the various engineering steps when setting up a project from scratch.
Consult the "User Interface" chapter to discover the different areas (PLANT, COMPONENTS, Cross Functions) and find hyperlinks to topics with detailed information and step-by-step procedures.