Chapter 8
MSC800
8011540/14B8/2019-06-06 Operating instructions | SICK 89
Subject to change without notice
8.2 Detailed fault analysis
8.2.1 System information
The MSC800 outputs faults in different ways. Fault output is staggered, allowing for
an increasingly detailed level of analysis:
• Communication errors can occur when transmitting telegrams to the MSC800.
The MSC800 then returns a fault code.
• For faults that occur during reading, fault codes are written to a status log.
8.2.2 Status log
• The status log is retained even after switching the device off and on again.
• The system distinguishes between four types of faults:
– Information
– Warning
– Fault
– Critical fault
The system saves only the last five entries for each fault type.
Display the status log using the SOPAS-ET configuration software.
To display the status log, the SOPAS-ET configuration software must be connected online
with the MSC800.
Connect the SOPAS-ET configuration software to the device.
Open the project tree
MSC800, SERVICE, SYSTEM STATUS, tab SYSTEM INFORMATION.
8.3 SICK support
If the fault cannot be rectified using the measures described above, the MSC800 may be
defective. The MSC800 components cannot be repaired by the user in order to restore its
functionality after a failure. However, the user can replace the MSC800 components
quickly. See chapter 7.5 Replacing components of the MSC800 on page 84.
If a fault cannot be rectified, please contact the SICK Service department:
• In Germany: technical hotline for SICK Vertriebs-GmbH,
Tel. +49 211 5301 031, fax. +49 211 5301-302, E-mail: Kundenservice@sick.de.
• Abroad: contact responsible SICK branch or SICK subsidiary.
For telephone numbers and email addresses, please see the back page of these
operating instructions. See www.sick.com for mailing addresses.
Please only dispatch devices after consulting SICK Service.
To Next Page
Loading...
Need help?
General
