This test function returns the condition of a selected operand (inputs, outputs, flags, data
word, counters or timers) at the end of program execution. This information is obtained
from the corresponding area of the selected operands. During the controlling of variables
respectively in operating mode STOP the input area is directly read. Otherwise only the
process image of the selected operands is displayed.
n
Control of outputs
–
Serves to check the wiring and proper operation of output modules.
–
If the CPU is in RUN mode, so only outputs can be controlled, which are not con-
trolled by the user program. Otherwise values would be instantly overwritten.
–
If the CPU is in STOP - even without user program, so you need to disable the
command output lock BASP (
‘Enable PO’
). Then you can control the outputs
arbitrarily
n
Controlling variables
–
The following variables may be modified: I, Q, M, T, C and D.
–
The process image of binary and digital operands is modified independently of the
operating mode of the CPU.
–
When the operating mode is RUN the program is executed with the modified
process variable. When the program continues they may, however, be modified
again without notification.
n
Forcing variables
–
You can pre-set individual variables of a user program with fixed values so that
they can not be changed or overwritten by the user program of the CPU.
–
By pre-setting of variables with fixed values, you can set certain situations for
your user program and thus test the programmed functions.
CAUTION!
–
Please consider that controlling of output values represents a poten-
tially dangerous condition.
–
Even after a power cycle forced variables remain forced with its
value, until the force function is disabled.
–
These functions should only be used for test purposes respectively
for troubleshooting. More information about the usage of these func-
tions may be found in the manual of your configuration tool.
4.19 Diagnostic entries
Appendix ‘System specific event IDs’ on page 213
n
You may read the diagnostics buffer of the CPU via the Siemens SIMATIC Manager.
Besides of the standard entries in the diagnostics buffer, the VIPA CPUs support
some additional specific entries as Event-IDs.
n
To monitor the diagnostics entries you choose in the Siemens SIMATIC manager
‘PLC
è
Module information’
. Via the register "Diagnostics Buffer" you reach the diag-
nostics window.
n
The current content of the diagnostic buffer is stored at the memory card by means of
the CMD DIAGBUF.
Chapter 4.17 ‘CMD - auto commands’ on page 82
n
The diagnostic is independent from the operating mode of the CPU. You may store a
max. of 100 diagnostic entries in the CPU.
‘PLC
è
Monitor/Modify
Variables’
Accessing diagnostic data
VIPA System MICRO
Deployment CPU M13-CCF0000
Diagnostic entries
HB400 | CPU | M13-CCF0000 | en | 16-47
85
Содержание VIPA System MICRO M13-CCF0000
Страница 35: ...3 2 2 Interfaces VIPA System MICRO Hardware description Structure Interfaces HB400 CPU M13 CCF0000 en 16 47 35 ...
Страница 211: ...Appendix VIPA System MICRO Appendix HB400 CPU M13 CCF0000 en 16 47 211 ...
Страница 212: ...Content A System specific event IDs B Integrated blocks VIPA System MICRO Appendix HB400 CPU M13 CCF0000 en 16 47 212 ...