Microlab
®
STAR Service Manual
10-1
10 Troubleshooting and Error Handling
10.1 Overview
This chapter is about how to respond to problems and errors identified by the
software which the user himself cannot resolve. The solution of the problem may
require the Service Technician to open up a component of the instrument.
This chapter takes the form of a list of such errors, and instructions how to handle
them.
Problems reported by the User Software
See User Manual. It contains all software-reported problems that the user himself
cannot solve. In the User Manual, the user is instructed to make a service call
whenever one of these problems occurs and there is not an obvious solution he can
implement himself. The last column, recommended action, is the action to be taken
by the Service Technician when called in by the user.
10.1.1 Version Information
For User Software a Version Info Program will be found on START Programs
HAMILTON
Version Info
For Service Software see section 3.3 Help Menu on page 3-6.
10.2 Trace Files
Trace Files can be of great help to the Service Technician with error investigation.
Typically when an undetected error occurs on the customer site - e.g. a damaged or
contaminated tip ejection tube which hinders a proper functioning of the Tip
presence sensor - checking these Files first for possible Hardware errors may help
to solve the problem very quickly. 2 Types of trace files are available:
10.2.1 Communication Trace files
A record of every single Firmware command sent to - and acknowledged by - the
ML Star Instrument.
Every Day when any method is started, a new Trace File is created and named for
the current day; it will be found in C:\ Program Files \ HAMILTON \ Logfiles \.
E.g. 20010112.trc which is the date format JJJJJMMDD, 12
th
of January 2001
To Next Page
Loading...