Appendix
A.2 System alarms
OP 73micro, TP 177micro (WinCC flexible)
Operating Instructions, 09/2007, 6AV6691-1DF01-0AB0
161
Number Effect/cause
Remedy
140016 The hardware does not support the configured
interrupt.
Change the interrupt number.
140017 The set interrupt is in use by another driver.
Change the interrupt number.
140018 The consistency check was disabled by SIMOTION
Scout. Only a corresponding note appears.
Enable the consistency check with SIMOTION Scout and
once again download the project to the PLC.
140019 SIMOTION Scout is downloading a new project to
the controller. Connection to the controller is
canceled.
Wait until the end of the reconfiguration.
140020 The version in the controller and that of the project
(FWX file) do not match.
Connection to the controller is canceled
The following remedies are available:
Download the current version to the PLC using
SIMOTION Scout.
Regenerate the project using WinCC flexible ES, close
WinCC flexible Runtime and restart with a new
configuration.
150000 No more data is read or written. Possible causes:
•
The cable is defective.
•
The PLC does not respond, is defective, etc.
•
The wrong port is used for the connection.
•
System overload.
Ensure that the cable is plugged in, the controller is
operational, the correct interface is being used.
Restart the system if the system alarm persists.
150001 Connection is up because the cause of the
interruption has been eliminated.
-
160000 No more data is read or written. Possible causes:
•
The cable is defective.
•
The PLC does not respond, is defective, etc.
•
The wrong port is used for the connection.
•
System overload.
Ensure that the cable is plugged in, the controller is
operational, the correct interface is being used.
Restart the system if the system alarm persists.
160001 Connection is up because the cause of the
interruption has been eliminated.
-
160010 No connection to the server because the server
identification (CLS-ID) cannot be determined.
Values cannot be read or written.
Check access rights.
160011 No connection to the server because the server
identification (CLS-ID) cannot be determined.
Values cannot be read or written.
Check, for example, if
•
the server name is correct
•
the computer name is correct
•
the server is registered
160012 No connection to the server because the server
identification (CLS-ID) cannot be determined.
Values cannot be read or written.
Check, for example, if
•
the server name is correct
•
the computer name is correct
•
the server is registered
Note for advanced users:
Interpret the value from HRESULT.
160013 The specified server was started as InProc server.
This has not been released and may possibly lead
to incorrect behavior because the server is running
in the same process area as the WinCC flexible
Runtime software.
Configure the server as OutProc Server or Local Server.