deleting via tree of action or command group with linked intelocking condition can cause strange behaviour of Editor

• Related Articles

• When you copy command group with an action with invalid interlocking conditions - the new group disappears after project reopen

  Summary In Command processing module you can copy actions from one command group to another. When you copy an action also all linked interlocking conditions are copied. But when in the aim group there are no variables for pasted conditions then: - ...

• Variable name linked in action in command group cannot exceed 100 chars

  Summary When in command group an action has command variable name longer as 100 chars the compiler in Editor hangs or even crashes. In zenon, in general a variable name can be 128 chars long. Description When in command group an action has command ...

• By action 'Lock' in Editor an interlocking condition can be created but is not used in the Runtime.

  Summary In Command Processing, the action type 'Lock' is not supporting interlocking conditions. But in Editor you can create a "condition" - from icon in toolbar or context menu; only copy&paste of conditions from another action type to 'Lock' is ...

• Action Buttons which are embedded in a symbol can not be selected as an action button for a command

  Summary In actions of a command group you can select which action button of a command screen shall execute this action. When command screen contains a symbol with buttons with screen type specific functions, these buttons cannot be linked in the ...

• Historian Editor tree doesn't update aggregation archive overview after change.

  Summary In the Editor Archives tree if you want add new variable via edit archive configuration screen aggregation archive are not up to date with new configuration. DescriptionIn the Editor Archives tree if you want add new variable via edit archive ...