IFM Electronic ecomot mobile R 360 Serie Starterset-Handbuch Seite 184

A small ecolog CoDeSys project as a start
Figure 60: Vary Values
You should make it a matter of habit to use 'Write Values', if possible. The
menu item 'Force Values' may be dangerous in practical use,
and 4-9!
If you like to work using the keys you had better use <Ctrl><F7> instead of
simply <F7>!
Those who want to know more about the difference should study the following
paragraph.
Besides the "manual" preset of input states, e.g. on the simulator box (
is also possible to force the states in the controller. This means that e.g. the
state of an input is defined without any consideration of the actual state. When
playing with the software without any inputs and outputs connected there is,
however, no difference to the off-line program test in the simulation mode. In
practice this function is more useful to the skilled user for debugging. The user
Forcing
should be skilled because forcing might start unintended processes when the
controller is connected to the peripheral equipment. If you use this function you
should know exactly the kind of damage that might be caused by a possible
avoidance of safety scans in the program.
Example When a new program or a new machine construction is tested, it is possible that
a drive stops in an interim position without the end position having been
reached. Then the drive has to be driven to the end position "manually". When
the limit switch is used as a condition in a program module to stop the drive, the
output for the drive can be set to TRUE using 'Write Values'. As soon as the
limit switch has been reached, the drive is stopped by the program. Here the
program is of higher priority (
If 'Force Values' is used, the drive will no longer be stopped by the limit switch.
This means that forcing the outputs should be avoided, if possible. It is only for
inputs that forcing cannot be avoided.
3-18
also page 4-9). E.g.:
Pages 3-18
3.3), it