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

L-force | PLC Designer
Device Editors
870 DMS 4.1 EN 03/2011 TD29

See in the following a description of the particular dialog windows:
Actions:
This part of the dialog lists the possible actions which might be performed during
runtime on files in the PLC file system resp. runtime objects like for example
applications. The tree is structured in the following way:
Object categories:
Top-level, for structuring purposes, there are two "folders" for File system objects and
Runtime objects.
Action types:
Indented below there are nodes for the four types of actions, which might be
performed on the particular objects. These nodes also just serve for structural
purposes:
Add/remove children (adding or removing of "child" objects to an existing object)
Execute (for example start/stop application, setting breakpoints etc.)
Modify (for example downloading application...)
View (monitoring)
Objects (action "targets"):
Below each action type node finally find the "targets" of the action, that is the PLC file
or runtime objects, for example Device.
These object entries are displayed in a tree structure mapping the device tree or the
file system structure.
Note: Assigning an access right definition to a "father" in the objects tree usually
means that the "children" will inherit this definition, as long as they do not get an
explicit own definition. However, depending on the device, this might be handled
differently. In any event, inheritances are not visualized here in the dialog.