dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separatorAutomation Builderdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorReference: User Interface dl-breadcrumb-item__separatorMenu Commands dl-breadcrumb-item__separatorOnline dl-breadcrumb-item__separatorCommand: Operating Mode – Debug, Locked, and Operational
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Command: Operating Mode – Debug, Locked, and Operational dl-permalink__symbolPermalink

Function: The commands set the controller to a state which prevents an accidental change to the project.

Call: “Online” menu

You can use these commands, for example, to lock the state of a controller in order to prevent the controller from switching to another state while you program another controller.

When programming is complete, the controller should then be switched to a defined and externally visible state which is set exactly the same way after restarting.

The _cds_icon_operation_mode_debug.png, _cds_icon_operation_mode_locked.png, and _cds_icon_operation_mode_operational.png symbols in the status bar indicate the current operating mode. Double-clicking one of these symbols opens a help window.

If the controller supports it, then you can switch the controller to the following operating modes:

  • _cds_icon_operation_mode_debug.png: “Debug”

    No restrictions

  • _cds_icon_operation_mode_locked.png: “Locked”

    The current state of debugging is locked on the application. No additional breakpoints can be set and no additional variables can be forced. Writing variables is still possible and breakpoints which are already set remain enabled.

    Only the "RUN" state of an application is preserved in _cds_icon_operation_mode_locked.png “Locked” mode, even when the controller is restarted.

    With this operating mode, developers can be prevented from changing the application on the controller, for example by setting or deleting a breakpoint, by forcing, or by making changes to the file system. This operating mode is helpful to prevent a download to an incorrect controller when, for example, multiple controllers of a plant are programmed.

  • _cds_icon_operation_mode_operational.png: “Operational”

    This operating mode makes sure that the controller reloads the same applications after a restart and that no debug features are enabled anymore. The operating mode is set when a controller is completely programmed and should be accepted or already is.

    Conditions for enabling “Operational” mode:

    • A boot application for each application has to exist on the controller.

    • There must not be any active breakpoints set.

    • All applications have to be running.

    • There must not exist any forced values.

    • Furthermore, the device can define more of its own restrictions.

The “Locked” and “Operational” modes are different in the use cases and in the requirements for enabling the mode. However, for both operating modes the runtime system prevents the following actions:

  • Regarding the application

    • Download of an application

    • Online Change

    • Force variables

    • Set breakpoints

    • Stop application

    • Reset application

    • Start application

    • Delete application

  • Regarding the file transfer of the controller

    • Download of a file to the controller

    • Delete a file on the controller

    • Rename a file on the controller

    • Create a directory on the controller

    • Delete a directory on the controller

    • Rename a directory on the controller

You cannot switch the operating mode between “Locked” and “Operational”.