Command ‘Operating Mode’

Function: These commands set the controller in a state that 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 reboot.

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

• Debug: No restrictions
• Locked: The current state of debugging is locked on the application. No more breakpoints can be set and no variables can be forced. Writing of variables is still possible.
• Operational: Nothing can be changed. Breakpoints cannot be set. Writing of variables is still possible.

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

Conditions for activating the Operational mode

• A boot application for each application must be present on the controller.
• There must not be any active breakpoints set.
• All applications must be running.
• There must not be any forced values present.
• Moreover, the device can define more of its own restrictions.

Note

You cannot switch the operating mode between Locked and Operational.