Appendix
A.2 System alarms
TP 270, OP 270, MP 270B (WinCC flexible)
Operating Instructions, Edition 03/2004, 6AV6691-1DD01-0AB0
A-21
Number Effect/cause Remedy
260006 The entry is rejected.
Use a shorter or longer password.
260007 The logoff time you entered is outside the valid
range of 0 to 60 minutes.
The entered value will be discarded and the original
value retained.
Enter a value between 0 and 60 minutes for the logoff
time.
260008 An attempt was made to read a PTProRun.pwl file
created with ProTool V 6.0 in UTAH.
Reading the file was interrupted due to format
incompatibility.
-
270000 A tag is not displayed in the alarm because it
attempts to access an invalid address in the PLC.
Check if the data area for the tag in the controller exists,
whether the configured address is correct and whether
the value range for the tag is correct.
270001 There is a unit-dependent limit as to how many
alarms may be queued simultaneously in order to
be displayed (see Commissioning Instructions).
This limit has been exceeded.
The display no longer contains all the alarms.
However, all the alarms are recorded in the alarm
buffer.
-
270002 Alarms are displayed from a log for which there is
no data in the current project.
Placeholders are issued for the alarms.
Delete older log data, if necessary.
270003 The service cannot be set up because too many
devices want to set up this service.
A maximum of four devices may execute this
action.
Connect fewer HMI devices which want to use the
service.
280000 Connection is reestablished because the cause of
the interruption has been eliminated.
-
280001 No additional data is read or written. Possible
causes:
•
The cable is defective.
•
The PLC does not respond, is defective, etc.
•
Connection has been established via the wrong
interface.
•
The system is overloaded.
Check if
•
The cable is plugged in
•
The PLC is OK
•
The correct interface is used.
Reboot the system if the system alarm is displayed
continuously.
280002 A connection is used which requires a function
module in the PLC.
The function block has replied. Communication can
now proceed.
-
