• Home
• User Interface - Reference
• PLANT Area
• PLANT Tree Node Editors

PLANT Tree Node Editors

The following table lists the available editors for the various PLANT tree nodes. Clicking a hyperlink opens the corresponding editor help topic. Depending on the devices you are using in your application, different editors may be available.

Editor group called for PLANT tree node...	Editor short description
Project node	'Settings' editor used for defining identity settings (network name and top-level domain name) and IP settings applicable for all devices of the PLANT ('Ip subnet' category). Note When adding new devices to the PLANT, each new device automatically gets the first free IP address of the 'IP Range' specified here. setting the scan options that are applied when scanning the network for connected devices using the 'Physical Topology' editor. 'Physical Topology' editor for scanning the connected network and visualizing the network topology of the detected devices. 'IP Subnet' is a tabular editor that lists the Profinet bus devices which are contained in the PLANT ('Profinet' node). Here, the 'Function' and 'Location' of each device can be edited. 'Description' editor for documentation purposes and maintaining a project version history. Safety Information editor: if your project includes a Safety PLC, the Project node provides this editor. It displays checksums which were calculated over safety-related data on project level. Details on checksums on project level Editor category CRC Description Project Project Overall checksum on safety-related project parts. Note This project checksum includes the individual CRCs that are listed below in this table and which are also displayed in the editor. Project Complete Logic CRC over the complete logic, i.e., data of all instantiated programs and function blocks. Project Global Variables CRC over all global variables of the Safety PLC. Project Safety variable / Process data interconnection CRC over all mapped process data items. Only available if at least one safety-related assignment exists in the Data List of the Safety PLC. Project Devices / Modules CRC over the parameterization data of all safety-related devices contained in the project. Libraries Library name CRC over the data of each POU contained in an included library. Example: After including the PLCopen_SF library, the CRC for each contained safety-related PLCopen function block is listed under the heading 'PLCopen_SF'. POUs POU name CRC over the data of each individual safety-related POU. These CRCs also shown in the 'Safety Information' editor of the respective POU. Devices / Modules Device name CRC over parameterization data of safety-related devices in the PLANT. The checksum also includes the F-Parameters and the CRC of the device description file. Note This CRC is not to be confused with the checksum that is calculated when exporting safety-related parameter data (without considering the F-Parameters) and which is used to seal the export file. Editor functions You can copy single CRCs with the <Ctrl> + <C> shortcut or via context menu. The editor provides an export function which creates an Excel file containing the data visible in the editor. When printing the project, the Safety Information can be selected as printable item in the 'Print' dialog. You can use these checksums to find out whether the project has been modified compared to older project versions. For that purpose, you have to manually compare each checksum with the relating CRC in the printed project documentation of the older, archived project version. The Global Variables checksum is of particular importance when replacing the Safety PLC. Further Info A safety information editor is also available on POU level. See topic "COMPONENT Types Editors" for details. 'Online Controllers' for scanning the network for controllers and add a found controller to the project. The 'Online Controllers' editor also allows to write IP settings to the scanned controller.
Controller node	'Cockpit ‣ Controller Commissioning: From Compiling to Debugging ×‣ Cockpit: Controlling the Application ×‣ Controller Diagnostics out of the Cockpit ×' editor for displaying diagnostic information and controlling the application via a toolbar. 'Settings' editor for defining the 'Identity', the IP settings and the profile version of the controller used. For controllers that implement a secure device concept, the section 'IT Security' editor is provided in the controller 'Settings' editor. In the current version, the security settings are read-only and indicate the implemented security protocol, the authentication method as well as the security version. The 'Settings' editor may provide further controller-specific pages (categories), where you can define, for example, redundancy settings, or the update task for controller system variables. The Data List enables the assignment (mapping) ‣ Declaring Variables/FB Instances ×‣ Managing Declarations in Tables ×‣ Role Mapping in Data Lists: I/O Variables and Exchange Variables ×‣ HMI Tags Created From Controller Variables × of global variables and instance-related located variables to process data items and/or HMI tags. It also enables the creation and management ‣ Declaring Variables/FB Instances ×‣ Managing Declarations in Tables ×‣ Role Mapping in Data Lists: I/O Variables and Exchange Variables ×‣ HMI Tags Created From Controller Variables × of global variables. See topic "Data Lists" for details. Note that PLCnext Technology ports are not contained in the Data List but in separate GDS Port Lists (for example on the 'PLCnext' node and on program instances). 'Safety Parameter' editor displays and allows editing of safety-related device parameters. It is only available, if a Safety PLC is included. Refer to the topic "Safety-related device parameterization" for details. 'Statistics' editor for displaying project- and controller-related information such as status information, the current load of the controller, no. of variables and POUs (in general and also task-related), status of particular system variables, etc. Refer to the topic "Project Statistics" for further details.
PLCnext	'Tasks and Events' editor for creating and configuring the tasks to be executed by the various cores including all task properties (task type, cycle time, etc.). The editor allows to instantiate program POUs (IEC 61131-3 programs as well as non-IEC 61131-3 programs). GDS Port List displays all PLCnext ports which are available in the controller. These ports are either declared in a local program POU with one of the keywords 'IN Port' or 'OUT Port' or they are part of and handed over from instantiated external programs. IN and OUT ports can be assigned (mapped) ‣ Declaring Variables/FB Instances ×‣ Managing Declarations in Tables ×‣ Role Mapping in Data Lists: I/O Variables and Exchange Variables ×‣ HMI Tags Created From Controller Variables × to each other. 'Data Logger' enables the configuration of the Data Logger firmware service tool which allows the recording of data on PLCnext controllers. 'Online Parameters': firmware editor ‣ Device Configuration/Parameterization ×‣ Device Configuration/Parameterization × for device-specific settings. The contained parameters are defined in the device description file. The editor allows to read parameter values from and write values to the device.
IEC 61131-3	The 'IEC 61131-3' node represents the runtime according to the IEC 61131-3 standard. 'Settings' editor displays the controller runtime profile. The Data List enables the assignment (mapping) ‣ Declaring Variables/FB Instances ×‣ Managing Declarations in Tables ×‣ Role Mapping in Data Lists: I/O Variables and Exchange Variables ×‣ HMI Tags Created From Controller Variables × of global variables and instance-related located variables to process data items and/or HMI tags. It also enables the creation and management ‣ Declaring Variables/FB Instances ×‣ Managing Declarations in Tables ×‣ Role Mapping in Data Lists: I/O Variables and Exchange Variables ×‣ HMI Tags Created From Controller Variables × of global variables. See topic "Data Lists" for details.
Safety PLC	'Settings' editor for defining the runtime profile and selecting the Profisafe device diagnostic variables to be created in the Data List of the Safety PLC. 'Safety Cockpit ‣ Safety PLC Commissioning: From Compiling to Debugging ×‣ Controlling the Safety Application from the Safety Cockpit ×‣ Safety PLC Diagnostics out of the Safety Cockpit ×' editor for displaying diagnostic and Safety PLC status information and controlling the safety-related application via toolbar. Data List displays and allows editing of resource-global Safety PLC variables. The Data List enables the assignment (mapping) ‣ Declaring Variables/FB Instances ×‣ Managing Declarations in Tables ×‣ Role Mapping in Data Lists: I/O Variables and Exchange Variables ×‣ HMI Tags Created From Controller Variables × of global variables to process data items and/or HMI tags. It also enables the creation and management ‣ Declaring Variables/FB Instances ×‣ Managing Declarations in Tables ×‣ Role Mapping in Data Lists: I/O Variables and Exchange Variables ×‣ HMI Tags Created From Controller Variables × of global variables and the creation of HMI tags (only for exchange variables). Read-only 'Statistics' editor for displaying information on the used program resources such as the number of FB instances, the program and stack memory used etc.
Program instance or FB instance under the node... 'PLCnext' 'Safety PLC'	In programming mode: double-clicking an instance node opens the Data List and/or GDS Port List under the following conditions: The Data List is available if the respective program or POU instance contains instance-related located variables. Such variables result from program-global variables or local FB variables which are declared with a set data direction (variable property 'I/Q') in the POU type. Refer to the topic "Instance-related Located Variables: 'Instance' and 'Program'" for details. The Data List enables the assignment (mapping) ‣ Declaring Variables/FB Instances ×‣ Managing Declarations in Tables ×‣ Role Mapping in Data Lists: I/O Variables and Exchange Variables ×‣ HMI Tags Created From Controller Variables × of such instance-related located variables to process data items and/or HMI tags. It also enables the creation and management ‣ Declaring Variables/FB Instances ×‣ Managing Declarations in Tables ×‣ Role Mapping in Data Lists: I/O Variables and Exchange Variables ×‣ HMI Tags Created From Controller Variables × of resource-global variables and the creation of HMI tags. The GDS Port List is only available for program instances and if the respective program type contains ports. These ports may have been declared in the current project (by setting the property 'Usage' in a declaration to 'IN Port' or 'OUT Port') or they are contained in an externally developed program type. The GDS Port List allows the mapping IN and OUT ports. Note For safety-related program/FB instances, these editors are not available as neither instance-related located variables nor ports can be declared for the Safety PLC. Note For an FB instance, you can directly jump to the call of the function block in the relating code worksheet using the 'Cross References' context menu command. The submenu of the 'Cross References' context menu command of an FB instance contains the code worksheet where the FB instance is used. (The command is only active, if the cross references are collected and up-to-date in the "CROSS REFERENCES Window".) In debug mode, double-clicking an instance node opens the online code for the corresponding instance (can be used instead of the 'Go To Instance Editor' context menu command in worksheets).
HMI Webserver	'Settings' editor used to configure HMI-specific parameters. For example, you can define the HTTPS ports used to establish the connection to the web server of the controller or enable/disable the security for HMI. See the topic "HMI Web Server Settings" for details. Data List displays and allows editing of all data items of the 'HMI Webserver' node (see topic "Data Lists" for further details). The editor enables the assignment (mapping) of HMI tags to global variables ‣ HMI Tags ×‣ HMI Tags Created From Controller Variables × for creating dynamic visualizations (read variable values) and for controlling the application (write values) via the HMI.
Application	'Tags' is a tabular editor that is used to create and modify the application local HMI tags. See the topic "Local HMI Tags" for details. The 'Navigation' editor allows you to define how you can navigate between your HMI pages when running the HMI application. The editor reflects the relationship of the HMI pages to each other in a hierarchical manner. In the 'Resources' editor you can define translations of user-defined HMI text strings. These translations are displayed in the running HMI application after switching the language using the LanguageCode application local tag. An application local tag is specific to one client (station) but shared among all HMI pages in your project. By writing to the LanguageCode tag, an HMI client is able to switch the HMI language during execution of the application. Precondition is that a default language and the corresponding alternative language(s) have been set in the 'Options' dialog. See topic "Project Language Translation (Localization)" for details.
HMI Page	The 'Parameters' editor is used to create and edit the HMI page parameters. An HMI page parameter can be used to pass a specific parameter value (constant or variable) from another HMI page to the HMI page where the page parameter is defined. See the topic "Defining HMI Page Parameters" for details. 'Tags' is a tabular editor that is used to create and modify the page local HMI tags. See the topic "Local HMI Tags" for details. HMI Page editor for designing the HMI page.
OPC UA	OPC UA editor with several editor pages for configuring the following: OPC UA server: editor for basic and security settings and, if required, a discovery server. In a separate editor you can specify the access to the (Linux) file system on the PLCnext Technology controller by OPC UA clients. OPC UA PubSub communication for PLCnext Technology controllers with a firmware version 22.0 or newer.
Profinet	'Settings' displays information on the Profinet controller, and can be used for defining the task which is responsible for the update of I/Os. 'Devices List' (also referred to as station editor) is a tabular editor that lists the Profinet bus devices which are contained in the 'Profinet' node. Here, the 'Function' and 'Location' of each device can be edited. New devices can be added to the PLANT in this table. 'Interface List' is a tabular editor that lists the Profinet bus devices which are contained in the 'Profinet' node. Here, you can set Profinet interface parameters of the contained Profinet devices. It is not possible to add or delete devices. Data List displays and allows editing of all process data items contained in the 'Profinet' node (see topic "Data Lists" for further details). The editor enables the assignment (mapping) of process data items (i.e., terminals provided by all contained I/O devices) to global variables and/or HMI tags. 'Online Devices' for scanning the network for Profinet devices and add found devices to the project. The editor also allows to write IP settings to connected devices.
Profinet device under Profinet controller Profinet device property nodes according to Profinet device modeling (DAP, Interface, Ports, etc.)	'Settings' editor displays information and enables editing of properties of the Profinet device (for example 'Identity' and IP settings). Furthermore you can set Profinet parameters here, relating to the handling of ARs or for setting up Profinet redundancy. 'Module List': tabular editor (also referred to as station editor) lists the Profinet I/O modules which are contained in the device node. Here, the 'Function' and 'Location' of each device can be edited. New Profinet I/O devices can be added to the PLANT in this table. The Data List enables the assignment (mapping) of process data items (i.e., I/O terminals provided by all contained modules/submodules) to global variables and/or HMI tags.
Profinet I/O module	'Settings' editor displays and enables editing of properties of the Profinet I/O module. 'Submodule List' lists the Profinet submodules of the I/O module. Here, the 'Function' and 'Location' of each device can be edited. The Data List enables the assignment (mapping) of process data items (i.e., I/O terminals of all submodules) to global variables and/or HMI tags.
Profinet I/O submodule	'Settings' editor displays and enables editing of properties of the Profinet I/O submodule. 'Parameter' allows the parameterization of the submodule. The Data List enables the assignment (mapping) of process data items (i.e., I/O terminals of the submodule) to global variables and/or HMI tags. Only for safety-related modules: 'Safety Parameter' editor displays and allows editing of safety-related device parameters. Refer to the topic "Safety-related device parameterization" for details.
Axioline F	'Settings' displays information on the Axioline F controller. In addition, you can set which task is used to update the Axioline-specific system variables (variables start with 'AXIO') and the assigned global variables ('Update task') and which task is used to trigger the Axioline I/O update ('Trigger task'). 'Devices List' is a tabular editor (also referred to as station editor) that lists the Axioline F I/O devices which are connected to the local Axioline bus and are contained under the 'Axioline F' node. Here, the 'Function' and 'Location' of each device can be edited. New devices can be added to the PLANT in this table. The Data List enables the assignment (mapping) of process data items (i.e., terminals provided by all contained I/O devices) to global variables and/or HMI tags.
Axioline F module under Axioline F controller	'Settings' editor displays and enables editing of properties of the Axioline I/O module. 'Parameters' allows the parameterization of the submodule. The Data List enables the assignment (mapping) of process data items (i.e., terminals provided by the I/O device) to global variables and/or HMI tags.
PLCnext Components	'PLCnext Components' editor in which PLCnext component types (provided in a library) can be instantiated. Component instances are added automatically when instantiating a contained program type. They can also be created manually in the 'PLCnext Components' editor by selecting a 'Component type' from the drop-down list or by dragging a component type from the COMPONENTS area ('PLCnext Components and Programs' category) into the editor and dropping it on an empty grid row. Note that the component instance name may not be changed if a program type belonging to this component type is already instantiated in the 'Tasks and Events' editor.