Command: Generator Configuration

This command (category "Composer") opens a dialog with all available generators.

In this dialog, each single generator can be enabled or disabled. A click on the "Tools" icon opens a detailed dialog with specific settings on the currently selected and enabled generator.

Device generator

This generator tries to generate the necessary devices and connects them to the module IOs, if possible.

In the current release of the Application Composer plug in, no configuration dialog is available for the device generator.

SourceTemplate generator

This generator copies existing function blocks from the POUs pool to the application. The copied function blocks are added in the AC_SourceTemplate folder. In this folder the additional function AC_SourceTemplateInit is also added. This function block is used to initialize the copied function blocks. Created function blocks can be edited and are not overwritten by a new generator run. Unused function blocks are renamed and moved to the UnusedSourceTemplate subfolder. Then the extension _unused is added. Requirement: The standard generator must be activated.

Standard generator

Default task settings
High priority task	Definition of Priority and Interval of the user-defined tasks The user-defined tasks can be set in the editor of the toplevel modules (see Deployment).
Medium priority task
Low priority task
Communication settings
Enable RMP communication	: The elements required for the RMP communication will be created.
Task priority	Priority of the RMP task
Task interval	Task interval of the RMP task
Compiler pragmas
GVLs	Definition of compiler pragmas These pragmas will be inserted before the generated GVLs or function blocks.
Function Blocks
Symbol Configuration
Create symbol configuration	: The symbol configuration object will be added to the application.

Persistence generator

The persistence generator reads the persistence configuration from the module tree and creates a persistence configuration object below each application that uses persistence.

For more information, see also: Persistence Manager

Tip

An application uses the application composer persistence feature if a Persistence Manager instance is mapped to that application.

DataLog generator

The DataLog generator creates a DataLog configuration object from the module tree configuration. This object will be added to the application to which the instance of the DataLog Manager is mapped. In the current release of the CODESYS Application Composer, no configuration dialog is available for the DataLog generator.

Trend generator

The trend generator reads the trend definitions from the module descriptions and creates a trend configuration with associated visualizations. These visualizations will be embedded in existing visualizations.

Alarm Generator

The alarm generator reads the alarm definitions from the module descriptions and creates or expands the associated components of the alarm management. Additionally, a visualization is created from a template. In this visualization an alarm table is inserted. The visualization will be added to the other visualization templates of the visualization generator as toplevel visualization.

Template

Template for the visualization screen.

Note: To use a visualization as template it must satisfy the following conditions:

A rectangle with the name Placeholder_AlarmTable
The variables bAckVisible, bAckSel, bHistory, and bFreezeScrlPos of type BOOL

Alarm Storage Template

Objects of type AlarmStorageTemplate, which are found in the current project and referenced libraries

The selected template will be used for all generated alarm configurations.

Create Toplevel Tab

standard icon : A toplevel tab will be created for the created alarm visualization.

The defined name will be displayed in the toplevel tab.

Device diagnosis generator

This generator creates visualization screens for the device diagnosis. In the settings, the visualization templates and the layout of the screens can be defined.

Figure 40. Device Diagnosis Generator settings

In the dialog, the templates for Base Visualization, PLC Template, Bus Template, Stack Template, Parent Device Template, and Child Device Template can be defined. The combo boxes list all available visualization templates which match the respective template types.

In the lower part of the dialog, the minimal size of the visualization screen and the space between the device diagnosis visualization elements can be defined.

CFC program generator

The CFC generator is used to create CFC programs.

Always regenerate all CFC pins: standard icon : Application Composer always tries to generate all function block I/Os for module instance FB calls.

Visualization generator

This generator creates visualization screens for the CODESYS Application Composer from visualizations which are available in the CODESYS project.

Toplevel Name: Enter a symbolic name for the visualization template ("toplevel template").
Template: The selection list offers all available (in the project and the loaded libraries) and compatible visualizations. If you select Default, the default template from library AC_Module will be used. If a template configured here in the dialog, is later removed from the project or library, it remains available in this dialog.
TargetVisu, WebVisu: Activate the respective option, if the page template should be used for this display variant.
Width:Width of the generated visualization in pixels (default value: 640, minimal 100, maximal 10000)
Height: Height of the generated visualization in pixels (default value: 480, minimal 100, maximal 10000)
Minimal ToplevelTab width: Minimum width for the generated toplevel tabs in pixels. If 0 is entered here, the setting is not taken into account.
Maximal ToplevelTab width: Maximum width for the generated toplevel tabs in pixels. If 0 is entered here, the setting is not taken into account.

For more information about toplevel templates, see: Toplevel templates

Maximum number of clients: Maximal number of parallel running clients (default 8, minimal 1, maximal 128).

Ignore generated visus if SVN is available: If the project is stored in Subversion this option should be activated. standard icon : CODESYS makes sure that the generated visualizations are ignored in SVN. Otherwise problems might occur.

Recreate visus when regenerating: standard icon : With each code generation, all visualizations are also regenerated and the existing visualizations are overwritten. This option should be selected if it is not desired that the module user makes changes to the generated visualizations after generation. However, if changes to the visualizations are still necessary after generation, the option should be deactivated. Then CODESYS tries to keep the subsequent changes also with the regenerations.

Use instance name as default for toplevel tabs: standard icon : Instead of the complete instance path, only the instance name is displayed in the top level tab.

If there is an error in the configuration, it is displayed with an error provider icon, and the OK button is disabled.