In online mode, the FBD/LD/IL editor provides views for Monitoring and for writing and forcing the values and expressions on the controller.
Debugging functionality (breakpoints, stepping, and so on) is available, see Breakpoint or Halt Positions.
For information on how to open objects in online mode, refer to the chapter User Interface in Online Mode.
Keep in mind that the editor window of an FBD, LD, or IL object also includes the Declaration Editor in Online Mode.
in the upper part. Also refer to the chapterIf the inline monitoring is not explicitly deactivated in the
dialog box, it will be supplemented in FBD or LD editor by small monitoring windows behind each variable or by an additional monitoring column showing the actual values (inline monitoring). This is even the case for unassigned function block inputs and outputs.The inline monitoring window of a variable shows a little red triangle in the upper left corner if the variable is currently forced, a blue triangle in the lower left corner if the variable is currently prepared for writing or forcing. In LD, for contacts and coils the currently prepared value (TRUE or FALSE) will be displayed down right below the element.
Example for a variable which is currently forced and prepared for releasing the force
Example for a contact variable which is currently prepared to get written or forced with value TRUE
Online view of an FBD program
Online view of an IL program
In online view, ladder networks have animated connections:
Connections with value TRUE are displayed in bold blue.
Connections with value FALSE are displayed in bold black.
Connections with no known value or with an analog value are displayed in standard outline (black and not bold).
The values of the connections are calculated from the monitoring values.
Online view of an LD program
Open a function by double-click or execute the command User Interface in Online Mode for further information.
from the contextual menu. Refer to the description of theIn online mode, you can prepare a value for forcing or writing a variable either in the declaration editor or within the editor. Double-click a variable in the editor to open the following dialog box:
Dialog box
You find the name of the variable completed by its path within the device tree (
), its type, and current value. By activating the corresponding item, you can do the following:Preparing a new value which has to be entered in the edit field.
Removing a prepared value.
Releasing the forced variable.
Releasing the forced variable and resetting it to the value it was assigned to just before forcing.
The selected action will be carried out on executing the menu command
(in the menu) or by pressing F7.For information on how the current state of a variable (forced, prepared value) is indicated at the respective element in the network, refer to the section Monitoring.
Possible positions you can define for a breakpoint (halt position) for debugging purposes are those positions at which values of variables can change (statements), at which the program flow branches out, or at which another POU is called.
These are the following positions:
On the network as a whole such that the breakpoint will be applied to the first possible position within the network.
On a box, if this contains a statement. Therefore it is not possible on operator boxes like for example ADD, DIV
. See the Note below.
On an assignment.
At the end of a POU at the point of return to the caller; in online mode, automatically an empty network will be displayed for this purpose. Instead of a network number, it is identified by RET
.
For the currently possible positions, refer to the selection list within the
dialog box.A network containing any active breakpoint position is marked with the breakpoint symbol (red filled circle) right to the network number and a red-shaded rectangle background for the first possible breakpoint position within the network. Deactivated breakpoint positions are indicated by a non-filled red circle or a surrounding non-filled red rectangle.
Breakpoint set and breakpoint reached
1 breakpoint set
2 breakpoint reached
As soon as a breakpoint position is reached during stepping or program processing, a yellow arrow will be displayed in the breakpoint symbol and the red shaded area will change to yellow.
Halt positions shown in FBD
Halt position shown in IL