dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separatorCODESYS Development Systemdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorReference, User Interfacedl-breadcrumb-item__separatorMenu Commandsdl-breadcrumb-item__separatorMenu 'Online'dl-breadcrumb-item__separatorCommand 'Operating Mode'
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Command 'Operating Mode'dl-permalink__symbolPermalink

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

Call: Menu bar: “Online  Operating Mode”

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 that is set exactly the same way after restarting.

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

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

  • _cds_icon_operation_mode_debug “Debug”: No restrictions

  • _cds_icon_operation_mode_locked “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 active.

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

    With this operating mode, a developer can prevent himself or another developer 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 “Operational”:

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

    Conditions for activating the “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” operating modes are different in the use cases and in the requirements for activating the operating 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”.