Lenze PLC Designer PLC Designer (R3-1) - Manual (Page 862)

L-force | PLC Designer
Device Editors
860 DMS 4.1 EN 03/2011 TD29

Bus cycle options:
Bus cycle task: The selection list offers all tasks currently defined in the Task
Configuration of the active application (for example "MainTask", "EtherCAT Master"
etc. The default setting as defined by the device description is automatically entered.
You might switch to another setting, but absolutely regard the following:
Note: Before modifying the setting to "<unspecified>", make sure to know about the
effect. "<unspecified>" means that the basic default behaviour as defined in the
device description will be applied. So check this description in this respect: As default
the task with the shortest cycle time might be defined, but just as well it could be
that with the longest cycle time!
Additional settings:
Generate force variables for IO mapping: This setting is only available if supported by
the device. If the option is activated, for each IO channel, which has got assigned to a
variable in the I/O Mapping dialog, two global variables will be created as soon as the
application gets built. These variables can be used e.g. in a HMI visualization for
forcing the I/O value. See I/O Mapping for detailed information.
I/O Mapping
This tab of the Device configuration dialog (Device Editor) is entitled with "<device
type> I/O Mapping" (for example "DP-Module I/O Mapping"). It serves to map the PLC
device I/Os on project variables, that is to assign the addresses of the device input,
output and memory locations to variables used in the application program.
The application which should handle the I/Os, must be defined in the PLC settings
dialog.
See in the following:
• General information on I/O mapping
• Using the I/O Mapping dialog
• Implicit variables for forcing I/Os