Appendix
A.2 System alarms
TP 270, OP 270, MP 270B (WinCC flexible)
Operating Instructions, Edition 03/2004, 6AV6691-1DD01-0AB0
A-9
Number Effect/cause Remedy
80021 An attempt was made to delete a log which is still
involved with a copy action. Deletion has not been
executed.
Wait until the current copying actions have been
completed and restart the last action
80022 Using the system function "StartSequenceLog", an
attempt was made to start a sequential log for a log
not configured as such. No sequential log is
created.
Check the project for the following:
•
The system function "StartSequenceLog" is
configured correctly.
•
The tag parameters are being correctly provided on
the HMI device.
80023 An attempt was made to copy a log to itself.
The log is not copied.
Check the project for the following:
•
The system function "CopyLog" is configured
correctly.
•
The tag parameters are being correctly provided on
the HMI device.
80024 The system function "CopyLog" is configured not to
permit copying when the target log already contains
data (Parameter: "Mode"). The log is not copied.
If necessary, modify the system function "CopyLog" in the
project. Before initiating the system function, delete the
target log.
80025 You have interrupted the copy process.
Data written up to this point is retained. Deletion of
the target log (if configured) is not executed.
The cancellation is documented by a $RT_ERR$
error entry at the end of the target log.
-
80026 This notification is issued after all the logs have
been successfully initialized. Values are written to
the logs from this moment on. Prior to this, no
entries are written to the logs even though WinCC
flexible Runtime is running.
-
80027 The internal Flash memory has been specified as
the storage location for a log. This is not
permissible.
No values will be logged for this log and the log will
not be created.
Configure "Storage Card" or a network path as the
storage location.
80028 The alarm serves as a status acknowledgment that
initialization of the logs is currently running. No
values are logged until system alarm 80026 is
issued.
-
80029 The number of logs specified in the event could not
be initialized. Initialization of the logs has been
completed.
The faulty logs are not available for logging jobs.
Evaluate the additional system alarms generated for this
alarm.
Check the configuration, the ODBC (Open Database
Connectivity) and the specified drive.
80030 The structure of existing log does not match the
expected log structure.
The logging process is stopped for this log.
Delete the existing log data manually in advance.
80031 The log in CSV format is corrupted.
The log cannot be used.
Delete the corrupt file.
80032 Logs can be configured with events. These are
triggered as soon as the log is full. If WinCC flexible
Runtime is started and the log is already full, the
event will not be triggered.
The log specified no longer logs data because it is
full.
Stop the WinCC flexible Runtime, delete the log and
restart the WinCC flexible Runtime.
or:
Configure a button which contains the same actions as
the event and press it.
