Microlab
®
STAR Service Manual
10-3
Investigtation of Errors with Trace files (continued):
Focusing on the higlighted section of the above window, we can see the following:
As seen from the editor Commands
< 16:36:28.976 8AF#8000#00:
C0DIid0046xp13400&yp4050 3925 3800 3675 3550
3425 3300 3175 3050 2925 2800 2675 2550 2425
2300 2175tp1970tz1870te2450tm1&
Command from PC to Instrument:
C0DI
a typical Initialize command
< 16:36:35.395 8AF#8000#00:
C0HDid0047
> 16:36:35.405 8AF#8000#00:
C0HDid0047er00/00
Command from PC to Instrument:
C0HD
Return Message from Instrument
to PC:
C0HDid0047er00/00
> 16:36:44.638 8AF#8000#00:
C0DIid0046er99/00 X003/00
Return Message from Instrument
to PC:
C0DIid0046er99/00 X003/00
Note: Always check for the complete command, which may include several lines in
the Trace File Editor, to gather all information.
In this case the Master (C0) has sent a general Initialize Command (DI) for his
Slaves (refer to Firmware reference Guide "Command Specifications Master
Module").
Disregard any Identification Number e.g. id0081
While initializing a Halt command has been sent, which interrupted the initialize
command.
The Slave is Pipetting Arm X Drive (X0) with Error 03 which is "Command not
completed" (refer to Firmware reference Guide "Command Specifications X0
Module").
In this case the method could have been aborted by the user e.g. by selecting the
ABORT Button in the Run Screen, or by opening the front window while running the
method, which has the same effect.
This Information could be found in the System Trace File, by checking the same
time, when the Error occurred.
To Next Page
