Tab 'PLC Settings'

On this tab of the generic device editor you make the basic settings for the configuration of the PLC, for example the handling of inputs and outputs and the bus cycle task.

“Application for I/O handling”

Application that is responsible for the I/O handling.

Table 445: “PLC Settings”
“ Refresh I/Os in stop”	: The values of the input and output channels are also refreshed when the PLC is in STOP mode. If the watchdog detects a malfunction, the outputs are set to the predefined default values. : The values of the input and output channels in STOP mode are not refreshed.
“Behavior of the outputs at stop”	Handling of the output channels when the controller enters the stop state: “Retain values”: The current values are retained. “All outputs to default value”: The default values resulting from the I/O mapping are assigned. “Execute program”: You can control the handling of the output values via a program contained in the project, which CODESYS executes at "STOP". Enter the name of the program in the field on the right.
“Always update variables”	Global setting that defines whether or not CODESYS updates the I/O variables in the bus cycle task. This setting is effective for I/O variables of the slaves and modules only if 'deactivated' is defined in their update settings. Deactivated (update only if used in a task): The I/O variables are updated only if they are used in a task. “Enabled 1 (use bus cycle task if not used in any task)”: CODESYS updates the I/O variables in the bus cycle task if they are not used in any other task. “Enabled 2 (always in bus cycle task)”: CODESYS updates all variables in each cycle of the bus cycle task, regardless of whether they are used and whether they are mapped to an input or output channel.

Table 446: “Bus Cycle Options”
“Bus cycle task”	Task that controls the bus cycle. By default the task defined by the device description is entered. By default the bus cycle setting of the superordinate bus device (use cycle settings of the superordinate bus) applies, i.e. the device tree is scanned upwards for the next valid bus cycle task definition.

NOTICE

Before you select the “<unspecified>” setting for the bus cycle task, you should be aware that "<unspecified>" means that the default setting given in the device description goes into effects. You should therefore check this description. Use of the task with the shortest cycle time may be defined as the default there, but use of the task with the longest cycle time could equally well be defined!

NOTICE

For fieldbuses, a fixed cycle matrix is necessary to assure a determined behavior. Therefore, do not use the type 'freewheeling' for a bus cycle task.

Table 447: “Additional Settings”
“Force variables for the I/O mapping ”	This setting is available only if it is supported by the device. : When compiling the application CODESYS creates two global variables for each I/O channel that is mapped to a variable in the dialog “I/O Mapping”. You can use these variables for the forcing of the input or output value on this channel, for example via an HMI visualization.
“Activate diagnostics for devices”	: The CAA Device Diagnosis library is integrated in the project. An implicit function block is generated for each device. If there is already a function block for the device, then either an extended function block is generated (example: EtherCAT) or another function block instance is added. This then contains a general implementation of the device diagnostics. By means of the function block instances you can determine the status of all devices in the application and evaluate errors. In addition, the library contains functions for the programmatic editing of the device tree. Example: Scanning of all children of a bus system, jumping to the parent element.
“Create additional parameters”	This setting is available only if it is supported by the device. Create additional parameters.
“ Display I/O warnings as errors ”	Warnings concerning the I/O configuration are displayed as errors.
“ Enable symbolic access for I/Os”	: Input and output variables (VAR_INPUT and VAR_OUTPUT) are automatically created for the I/O channels of the device. For this purpose, an extended function block is created for each slave. The basis is the existing function block of the slave. This kind of automatically generated function block can be accessed directly in the application code. This symbolic access works in parallel to the I/O mapping which was set up manually. : Access to I/O channels is not supported. It is necessary to manually set up a mapping and specifically assign new or existing variables per I/O channel.