Siemens SIMATIC HMI OP 73micro Operating Instructions Manual page 156

Appendix
A.2 System alarms
Number Effect/cause
80003 The copying process for logging was not
successful.
In this case, it is advisable to check any
subsequent system alarms, too.
80006 Since logging is not possible, this causes a
permanent loss of the functionality.
80009 A copying action has been completed successfully.
80010 Since the storage location was incorrectly entered
in WinCC flexible, this causes a permanent loss of
the functionality.
80012 Log entries are stored in a buffer. If the values are
read to the buffer faster than they can be physically
written (using a hard disk, for example),
overloading may occur and recording is then
stopped.
80013 The overload status no longer applies. Archiving
resumes the recording of all values.
80014 The same action was triggered twice in quick
succession. Since the process is already in
operation, the action is only carried out once.
80015 This system alarm is used to report DOS or
database errors to the user.
80016 The logs are separated by the system function
"CloseAllLogs" and the incoming entries exceed the
defined buffer size.
All entries in the buffer are deleted.
80017 The number of incoming events cause a buffer
overflow. his can be caused, for example, by
several copying actions being activated at the same
time.
All copy jobs are deleted.
80018 All connections between WinCC flexible and the
logs have been reestablished, for example, after
executing the system function "OpenAllLogs".
Entries are written into the logs again.
80019 The connection between WinCC flexible and all
logs were closed, for example, after executing the
system function "CloseAllLogs".
Entries are written to the buffer and are then written
to the logs when a connection is re-established.
There is no connection to the storage location and
the storage medium may be replaced, for example.
80020 The maximum number of simultaneously copy
operations has been exceeded. Copying is not
executed.
80021 An attempt was made to delete a log which is still
busy with a copy action. Deletion has not been
executed.
156
Remedy
-
In the case of databases, check if the corresponding data
source exists and start up the system again.
-
Configure the storage location for the respective log
again and restart the system when the full functionality is
required.
Archive fewer values.
Or:
Increase the logging cycle.
-
-
-
Reconnect the logs.
Stop the copy action.
-
-
Wait until the current copying actions have been
completed, then restart the last copy action.
Wait until the current copying actions have been
completed, then restart the last action
OP 73micro, TP 177micro (WinCC flexible)
Operating Instructions, 09/2007, 6AV6691-1DF01-0AB0