4Control Engineering Objects | |
Objects in 4Control can be considered as elements of a 4Control project to which properties and entries have been assigned. They include e.g. variable lists, POUs, instances and libraries. In the various views of the Navigator and in the object list, objects are identified by corresponding icons. | |
| Resources | |
Resources are displayed and managed in the Class view of the Navigator and in the object list The resource can be opened in the 4C text editor | |
| Constants | |
A constant has a fixed identifier (name), a fixed data type and a fixed value which matches the data type. Constants are defined using constant lists which are valid for the entire project. Thus, you can use them in all objects of the project instead of literals. Constant lists are displayed and managed in the Class view of the Navigator and in the object list.
The constant list can be opened in the 4C text editor | |
| Global Variables | |
Global variable lists (GVL) are ASCII text files used to define global variables. The variable declarations of the GVLs are enclosed by the VAR_GLOBAL and END_VAR keywords and separated by semicolons. In addition, the CONSTANT and RETAIN attributes can be specified directly after the VAR_GLOBAL keyword. They refer to all variable declarations specified before END_VAR. Global variable lists are displayed and managed in the Class view of the Navigator and in the object list. The global variable list can be opened in the 4C text editor.
| |
| Structured Data Types | |
Different data types can be grouped in a new, structured data type which is called a structure. Structures are displayed and managed in the Class view of the Navigator and in the object list The structured data type is opened in the 4C text editor.
| |
| Programs | |
The POU classes of the Program type are displayed and managed in the Programs folder of the Class view of the Navigator and in the object list. In 4CONTROL, programs are not directly called by tasks, but after a program instance has been created within the task. Program instances are not stored in separate files, but they are declared by instantiation in the calling task (in the source code of the resource).
| |
| Function Blocks | |
Function blocks are displayed and managed in the Function Blocks folder of the Class view of the Navigator and in the object list. Since function block instances are declared by instantiation within the calling POU, they are not saved in separate files. In the Instance view of the Navigator, they are indicated by the icon and displayed below the POU in which the function block was instantiated.
| |
| Functions | |
Functions are parameterizable POUs which have no internal memory. Function calls with identical input values produce identical output values. Functions are displayed and managed in the Functions folder of the Class view of the Navigator and in the object list. | |
| Tasks | |
Each resource can include one or more tasks which, in turn, call one or more POUs of the Program type. Tasks are displayed and managed in the Class or Instance view of the Navigator and in the object list. | |
| Libraries | |
Libraries are collections of the following 4C objects:
Libraries are stored as separate files so that they can be made available and used in any 4C project. There are two different types of libraries:
The libraries belonging to a project are displayed and managed in the Libraries folder of the Class view of the Navigator and in the object list | |






