Dialog ‘Input Configuration’¶
Symbol:
Function: This dialog is used for assigning input actions to specific input events. In addition, it includes specific settings for the selected input action.
Call: Click Configure in the Input configuration property.
Requirement: An element is selected in the editor.
See also
Input action ‘User management’
Dialogs and actions | Configures which one of the possible user management dialogs or which action follows the input event. Note: The actual dialog used is configured in the visualization manager (Dialog settings tab). See also
Dialogs from the |
Login | Dialog prompt for logging in: Preset: |
Logout | The current user is logged out. |
Change user password | Dialog for changing the password: Preset: |
Open user configuration | The dialog opens for changing the password. Preset: |
See also
Input action ‘Close Dialog’
Dialog | The visualization of type Dialog that is closed.
Example: Standard dialogs of the
Note: The setting in the object property (Visualization tab) of a visualization determines whether or not a visualization can be used as a dialog. |
Result | Return value for closing the dialog. Note: If there are more input actions after closing, then they configured in the property of the element. |
None | ![]() |
OK | ![]() OK is returned for the “OK” button. The value Cancel is returned for the “Cancel” button. |
Cancel | |
Exit | |
Retry | |
Ignore | |
Yes | |
No |
See also
Input action ‘Open Dialog’
Dialog | Visualization (type Dialog). The dialog opens.
Note: The VisuDialogs library provides visualizations (type Dialog).
|
Transfer parameters of the dialog | |
Parameters | Interface parameter as declared in the interface editor of the visualization. Example: |
Type | Data type of the parameter as declared in the interface editor of the visualization. Example: |
Value | Variable (data type conforms to data type of the parameter). The value of the variables is read when the dialog opens and transferred to the parameter. Example:
|
The return value of the dialog is activated here for which the Var_OUTPUT variables and VAR_IN_OUT variables are written. Then the dialog closes. |
|
Update ![]() ![]() |
Note: The parameters are updated before the dialog is closed. The values are stored temporarily until then. They are stored as a copy, not as a reference. |
None | ![]() |
OK | ![]() |
Cancel | |
Exit | |
Retry | |
Ignore | |
Yes | |
No |
Open in dialog mode | ![]() |
Position to open | |
Centered | The dialog opens in the center of the visualization. |
Position | The dialog opens at the position defined by X and Y. |
X | Position (in pixels) or as a variable (integer data type) |
Y | Position (in pixels) or as a variable (integer data type) |
See also
Input action ‘Change language’
Language | Switched language Example:
|
Input action ‘Change visualization’
Assign | Switched visualization from the project or a library. Example: |
Assign expression | Variable ( Example: Tip: If a visualization change depends on a state, then the variable can be set accordingly. |
The application saves the order that the visualizations are called. This can be used for | |
Previous visualization |
Requirement: A visualization has already been switched. |
Next visualization |
Requirement: There has already been a visualization change that was called by Previous visualization. |
Visualization that is displayed at the user input. | |
Assign | Visualization that is selected from all available visualizations in the project or libraries. Example: |
Assign expression | Variable ( Example: |
The order in which visualizations are displayed by user inputs is saved internally. For the options below use this information. | |
Previous visualization |
Requirement: A visualization has already been switched. |
Next visualization |
Requirement: There has already been a visualization change that was called by Previous visualization. |
Input Action ‘Execute command’
A list of commands is configured here with transfer parameters that the visualization processes upon specifying the input event.
Configure commands | Command from the drop-down list. Click the add symbol (
|
![]() |
This command in Configure commands is added to the list. |
![]() |
The command is removed. Requirement: A command is selected. |
The order in the list defines the order of execution. | |
![]() |
The selected command is shifted one position downwards in the list. |
![]() |
The selected command is shifted one position upwards in the list. |
Command | 1st parameter | 2nd parameter |
ExecutePlcProgram |
'C:\\programs\\notepad.exe' |
'Notes_A.txt' |
EXE file that is executed on the PLC. The program is executed on the PLC and therefore it must not be interactive or hay any user interfaces. It is possible, for example, for a program to copy a file. |
Program name with directory as STRING in single straight quotation marks |
Arguments of the program as Example: Name of the file that the program opens. |
Command | 1st parameter | 2nd parameter |
ExecuteClientProgram |
'C:\\programs\\notepad.exe' |
'Notes_A.txt' |
EXE file that is executed on the display variant Exception: WebVisu. The program is executed in the context of the display variant. For this, the program can then be interactive with a user interface. |
Program name with directory as STRING in single straight quotation marks |
Arguments of the program as Example: Name of the file that the program opens. |
Attention
If the visualization is displayed as CODESYS Web Visualization, then no program (*.exe file) can be started.
Command | 1st parameter | 2nd parameter |
NavigateURL |
|
'replace' |
The visualization navigates to the website of the URL. Requirement: The visualization is executed as a CODESYS Web Visualization. |
URL
|
If no parameter is provided, the web page is displayed in a new window or a new tab. If |
Command | 1st parameter | 2nd parameter |
ReadRecipe |
'RecipeDefinitionForModules' |
'RecipeModuleA' |
Name of the recipe definition
|
Name of the recipe
|
|
At visualization runtime, the PLC reads the current values from the variables of the recipe definition and writes them to the given recipe. The values are saved implicitly (to a file on the PLC) and displayed in the recipe definition in the recipe manager of CODESYS. In other words, the recipe that is managed in CODESYS is updated with values from the PLC. |
Command | 1st parameter | 2nd parameter |
WriteRecipe |
PLC_PRG.stRecipeDef |
PLC_PRG.stRecipe |
Name of the affected recipe definition
|
Name of the recipe (from the recipe definition)
|
|
At visualization runtime, the values of the recipe are written to the variables on the PLC as they are in the recipe manager. |
Command | 1st parameter | 2nd parameter |
SaveRecipeAs |
PLC_PRG.stRecipeDef |
PLC_PRG.stRecipe |
Name of the affected recipe definition
|
Name of the affected recipe that is updated and saved to a file.
(optional parameter) If you do not specify a transfer parameter here, then the values from the recipe variables are saved in the specified file only. The implicit recipe files are not updated. |
|
At visualization runtime, the Save Recipe as dialog opens and prompts the user for a storage location on the PLC and a file name. The file name The user can then save the file that includes the actual values from the recipe variables. If no transfer parameter is given in the 2nd parameter, then the file is saved without changing an implicit recipe file. If a transfer parameter is given in the 2nd parameter, then the implicit recipe file is also updated. Note: If the Save recipe changes to recipe files automatically option is selected in the Recipe Manager - General tab, then the recipe definition in CODESYS and the implicit recipe files are kept the same automatically. Note: On the PLC, there are implicit (automatically generated) recipe files with the names |
Command | 1st parameter | 2nd parameter |
LoadRecipeFrom |
PLC_PRG.stRecipeDef |
PLC_PRG.stRecipe |
Name of the affected recipe definition
|
Name of the affected recipe
|
|
In visualization runtime, the Load recipe dialog opens. It provides the visualization user with a file list that is located in the file system for control and filtered by the extension Requirement: The file was created with the |
Command | 1st parameter | 2nd parameter |
WriteRecipe |
PLC_PRG.stRecipeDef |
PLC_PRG.stRecipe_New |
Name of the affected recipe definition
|
Name of the new recipe
|
|
At visualization runtime, a new recipe is created in the given recipe definition. |
Command | 1st parameter | 2nd parameter |
WriteRecipe |
PLC_PRG.stRecipeDef |
PLC_PRG.stRecipe |
Name of the affected recipe definition
|
Name of the recipe
|
|
At visualization runtime, the given recipe is deleted from the recipe definition. |
See also
- Changing Values with Recipes: Changing Values with Recipes
- Object ‘Recipe Definition’: Object ‘Recipe Definition’
Input action ‘Switch Frame visualization’
When the input event occurs, the display switches to another visualization within one frame.
Selection type | |
Local visualization | The Frame selection group is visible. |
Any visualization | The Frame and visualization selection group is visible. |
Requirement: Local visualization is activated. | |
Frame selection | List of all frames that contain the active visualization. The referenced visualizations are listed below each frame, as determined in the Referenced visualizations property of the respective frame. Example: |
Assign selection | The selection in the Frame selection input field is taken and it appears in the Selected frame and Selected visualization settings. Requirement: A visualization is selected in the Frame selection input field. |
Selected frame | Name of the switched frame. Example: Tip: Use the Assign selection command for changing the setting here. |
Visualization selection | Name of the switched visualization. Example: Tip: Use the Assign selection command for changing the setting here. |
Requirement: Any visualization is activated. | |
Frame and visualization selection | Contains the switched frame. |
Assign | Switched frame with complete path. The index determines the visualization. Example: The path is specified in the following format: Note: Visualizations can be nested in any depth. The path is accordingly complex. |
Assign expression | Variable ( Example: |
Index to select | Index that determines which of the referenced visualizations is displayed.
Note: The referenced visualizations of a frame are indexed automatically by their sorting order. |
Requirement: The project contains visualizations that form a structure.
See also
Input action ‘Write variable’
The configuration of the input action defines how a visualization user specifies a value and to which variable the value is written.
Input type How the input is prompted. |
|
Default | An input field also opens, or a virtual keyboard if necessary (if the display variant does not have a physical keyboard. Note: The default for text input in runtime mode is set in the Visualization Manager: Dialog settings tab, Settings for default text input. |
Text input | An input field appears. It allows you to specify a number or text from the keyboard. Requirement: The display variant is provided with a keyboard as input device. |
Text input with limits | An input field appears. It allows you to specify a number or text from the keyboard. The field also shows the value range for the input. When a limit is exceeded, the input value is displayed in red. Requirement: The display variant is provided with a keyboard as input device. |
VisuDialogs.Keypad | A virtual keyboard opens. It allows you to specify a number or text. |
VisuDialogs.Numpad | A virtual keyboard opens. It allows you to specify a number. |
VisuDialogs.NumpadExtended | A virtual keyboard opens. It allows you to specify a number. The hexadecimal or exponential format is also permitted here. |
Choose variable to edit | |
Use text output variable | ![]() |
Use another variable |
Example: |
Initial display format | Placeholder with format definition. It determines the output format for the variable value and the input limits. Example: |
Min | Minimum value of the input limit. If a user specifies a lesser value, then it is not accepted.
|
Max | Maximum value of the input limit. If a user specifies a greater value, then it is not accepted.
|
Dialog title | Text displayed in the caption bar of the dialog. Optional.
|
Password field | ![]() \*\*\* is displayed instead of the input text. |
Use global settings (from Visualization Manager) | ![]() |
Centered | ![]() |
Position |
X, Y: Variable or explicit number (in pixels) for the definition of the upper left corner of the dialog in the coordinate system of the visualization window. You can use the placeholders |
See also
- Object ‘Visualization Manager’ - ‘Settings’
- Placeholders with Format Definition in the Output Text
- Calling Dialogs in a Visualization
- Dialog Box ‘Properties’ of Visualization Objects
- Placeholders with Format Definition in the Output Text
- Tab ‘Visualization Manager’ - ‘Dialog settings’
Input action ‘Execute ST code’
Input field | Editor for code as structured text |
Input action ‘Toggle variable’
Variable | Variable ( Example: |
Input action ‘File transfer’
Direction | From PLC to visualization From visualization to PLC |
Type | File Streaming |
File name | Variable of type Requirement: The type of transfer is File. |
Streaming instance name | Instance name of the object that yields the data for the transfer in streaming mode. The object must implement the interface Requirement: The type of transfer is Streaming. |
Transfer in progress | Boolean variable (optional)
|
Transfer successful | Boolean variable (optional)
|
Error code |
|
Behavior in online mode (type File)
- Transfer from the controller to the operator panel: The Save file dialog opens. The file with the name from the File name setting can be saved as any name on the operator panel.
- Transfer from the operator panel to the controller: The Open file dialog opens. Any file can be selected that is saved on the controller as the name from the File name setting.