COMPONENT Types Editors
The following table lists the available editors for the various COMPONENTS types. Clicking a hyperlink opens the corresponding editor help topic.
By double-clicking an
editable component type icon in one of the COMPONENTS categories, its properties are opened and can be edited in a group of editors which appear in the editors area. The number and style of the available editors depend on the type.
Some types, such as devices or HMI objects, cannot be edited.
Note
When editing the properties or content of a component provided in one of the categories of the COMPONENTS area, the reusable type is modified. As a result, each existing or future instance of this type is affected by the modification. |
| Editor group called for component type (COMPONENTS area) | Editor short description |
| Data types worksheet | for defining user-defined data
types. |
| Program/function block/function POU, method, coded transition/action | Depending on the programming language of the POU:
-
Variables editor: tabular editor for declaring variables/ports (for programs only) and function block instances of the respective POU.
-
for developing code in the IEC 61131-3 programming languages FBD/LD and SFC.
Besides the classic free-graphic FBD/LD code, PLCnext Engineer supports a second variant
of mixed FBD/LD networks referred to as NOLD (network-oriented Ladder Diagram).PLCnext Engineer supports programming of safety-related code using the SNOLD (Safety Network Oriented Ladder) editor if a Safety PLC is included in your application. Basically, the SNOLD editor works like the NOLD editor but provides additional safety-related features. The SNOLD editor performs a continuous verification of the worksheet data consistency. Any detected inconsistency (i.e., possible data corruptions) results in an editor error and a safety violation notification is output in the Error List (MESSAGES window).Several code worksheets per POU are possible.
-
for developing code in the IEC 61131-3 programming language ST.
Several code worksheets per POU are possible.
-
'Description' editor for documentation purposes and maintaining a version history of the POU.
- 'Settings' editor that you use to define:
- namespaces for a POU and add namespaces to the 'Usings' list of a POU.See topic "Namespaces" for details.
- the return data type for function POUs and to set the access specifier for methods of user-defined function blocks.See topic "Methods of FBs" for details.
- In the 'Resources' editor you can define translations of variable comments, user-defined texts (e.g., message texts) as well as free code comments.
Such translations can be read by the GET_LANG_STRING/GET_LANG_WSTRING function blocks. After integrating these FBs in the application code, the FBs can read a translation and write it into a user-defined string variable.Structure of the table:
- The 'Variables' section contains each variable/FB instance for which the 'Translate' flag has been set in the 'Variables' grid of a POU.
- In the 'User' section you can define free text strings.
- The 'Code' section contains each free comment inserted in any code worksheet of the POU.
- Which language columns are available depends on your Default Language Setting in the 'Options' dialog.
See topic "Project Language Translation (Localization)" for details.
- Safety Information editor (for safety-related POUs only)
Safety-related POUs additionally provide a 'Safety Information' editor. Here, the checksums are listed which were calculated for each verified network after setting the verification mark. You can use these checksums to find out whether code networks have 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 editor provides an export function which creates an Excel file containing the data visible in the editor.
Refer to the topic "" for details.
Note
PLCnext Engineer supports multi-language POUs: code worksheets in different IEC programming languages can be added in one POU node. |
Note
In debug mode, the editors can display read from the controller and provide . |
|
| HMI symbol |
- The 'Parameters' editor is used to create and edit the HMI symbol parameters. HMI symbol parameters are linked to dynamic/action properties of an object contained inside the HMI symbol. Thus, a symbol parameter provides access to one particular dynamic property or action of an HMI symbol.See the topic "Working with User-defined HMI Symbols" for details.
-
'HMI Symbol' editor for editing user-defined symbols.
-
'Description' editor for documentation purposes and maintaining a version history of the HMI symbol.
|
| HMI text list |
- 'Text List' editor for editing text lists. Text lists can be used for displaying various texts in the visualization at runtime depending on the value of a numeric variable (HMI tag). This allows you to show a descriptive and more meaningful text in the visualization instead of the numeric variable value.
- 'Resources' editor for translating text list entries. This allows you to use the text lists in localized applications and show them in different languages at runtime.
See the topic "Working with Text Lists" for details. |
| HMI image list |
- 'Image List' editor for editing image lists. Image lists can be used for displaying various images in the visualization at runtime depending on the value of a numeric variable (HMI tag).
- 'Resources' editor for defining language-specific images. This allows you to use the image lists in localized applications and show the images in different languages at runtime.
See the topic "Working with Image Lists" for details. |
The categories 'Network' and 'Libraries' do not provide any editors for modifying types.
‣ Programming ST