Scribd
Upload
19 views

Error Codes

The document provides descriptions for various instrument manager error codes, including errors related to communication issues, invalid device numbers, software compilation errors, regional language settings, and the data system sending multiple close messages to the firmware.

Uploaded by

X-Samsul
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
19 views

Error Codes

The document provides descriptions for various instrument manager error codes, including errors related to communication issues, invalid device numbers, software compilation errors, regional language settings, and the data system sending multiple close messages to the firmware.

Uploaded by

X-Samsul
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Instrument Manager error codes

Glossary Item Box

Error code Description


Error: 1001 - End of segment failed to interrupt upon completion A loss of communication when the instrument is turned from Standby
mode to On mode might be caused by a disconnected Analyzer PCB/EM
Data RS422 ribbon cable P/N 70111-63048. The cable connects between
the Analyzer Control PCB and the Electrometer PCB. Restarting the
instrument will restore communication while the instrument is in standby
mode, but communication will be lost when the instrument is turned On
Error: 1002 - Device 0.000000 out of range, must be within 0 and 160 In the Full Instrument Control Workspace there is the Device View located
on the left side of the window. The device View lists the devices (for
example Capillary Offset, Skimmer Offset, Q2 Offset, etc.). Each device
has an associated number that is coded in the software. If there is a
change to a device or a device is removed it will no longer appear in the
Device view. Ideally, the device number should also be removed from the
software. When the FAIMS option was added to the software several
devices were created. The error messages that you observe are error
associated with a device that is not used and has not been removed from
the code. The instrument searches for the device and cannot find it so an
error is generated. The error does not affect the operation of the
instrument
Error: 1004 - CtrlBoard::ctrlDevRd: invalid control device number 0 In the Full Instrument Control Workspace there is the Device View located
on the left side of the window. The device View lists the devices (for
example Capillary Offset, Skimmer Offset, Q2 Offset, etc.). Each device
has an associated number that is coded in the software. If there is a
change to a device or a device is removed it will no longer appear in the
Device view. Ideally, the device number should also be removed from the
software. When the FAIMS option was added to the software several
devices were created. The error messages that you observe are error
associated with a device that is not used and has not been removed from
the code. The instrument searches for the device and cannot find it so an
error is generated. The error does not affect the operation of the
instrument
Error: 1100 - ICL compile error in procedure runxcalibur0.icl Remake Instrument Method from Scratch
Run several test samples with the new method to see if the system
exhibits the same error
If networked, determine if any programs were running that may have
interrupted communication at the time of the error (I.E. Data back
up/transfer, virus scan, etc)
If the system exhibits the same error, and no other programs were running
that may have affected communication, recommend updating TSQ driver
to TSQ 2.3 SP1
If this does not fix the problem, remove and reload Xcalibur and TSQ
drivers with the latest versions. Also Run the Diagnostics (System Control
board and Analyzer Control Board) in TSQTune

Error: 1103 - ITCL scan error: Syntax error Click on the Regional and Language Options icon in the Control Panel
In the Regional Options page, confirm the Standards and Formats is set to
English (United States) and the Location is set to United States. If either
option is not set correctly, perform a clean installation of the Microsoft
Windows operating system software and select the regional setting as
English

Error: 1402 The cause of this error message is that Data System may send multiple
messages to firmware to close the analysis (data acquisition). If the
analysis was already closed, the firmware will not do anything but prints
out this message. In fact, this message should not be treated as error as it
does not cause any harm to the system

You might also like