iCAP 6000 7000 Errors and Causes
Issue
An issue occurred such as the plasma not igniting or going out and in iTEVA or Qtegra an error code was triggered. What does the error code refer to? And what potential corrective action are there? The list below is not comprehensive by any means but will list a lot of the error codes and corrective actions for some of them.
In iTEVA the error code will be displayed in the Journal and in Qtegra it will be displayed in the Log View. If you can't find the error in the Log View look in the most recent log file.
The Log file can be retrieved as follows:
1) Navigate to: Path: C:\ProgramData\Thermo\Qtegra\LogFiles
2) Sort the contents of the LogFiles directory with the newest files at top of list by clicking on the "Date Modfied" column
3) Locate the most recent log file of the type:
File Name: log-20140922-074323638.log (format: log-yyyymmdd-nnnnnnnnn.log)
Date & Time inside file: 2014-09-22T09:53:30.8412240-05:00|
(Date) (Time)
Note: If there is no general log file for the day in which the event occurred, please copy the general log file directly preceding the event in chronological order.
Environment
- iCAP 6000 Series
- iCAP 7000 Series
Resolution
| iCAP - 6000/7000 ICP / Errors List / | |||
| Category | Type | Error Codes / Description | Corrective Action |
| Initialization | Firmware initialization errors | 101#: Fatal Firmware error. If the condition persists please contact customer support with this error code. | |
| Initialization | Firmware initialization errors | 102#: Fatal Firmware error. If the condition persists please contact customer support with this error code. | |
| Initialization | Firmware initialization errors | 104#: Fatal Firmware error. If the condition persists please contact customer support with this error code. | |
| Initialization | Firmware initialization errors | 105#: Fatal Firmware error. If the condition persists please contact customer support with this error code. | |
| Initialization | Firmware initialization errors | 106#: Fatal Firmware error. If the condition persists please contact customer support with this error code. | |
| Initialization | Firmware initialization errors | 107#: Fatal Firmware error. If the condition persists please contact customer support with this error code. | |
| Initialization | Firmware initialization errors | 108#: Fatal Firmware error. If the condition persists please contact customer support with this error code. | |
| Initialization | Firmware initialization errors | 109#: Fatal Firmware error. If the condition persists please contact customer support with this error code. | |
| Initialization | Firmware initialization errors | 110#: Fatal Firmware error. If the condition persists please contact customer support with this error code. | |
| Initialization | Firmware initialization errors | 111#: Fatal Firmware error. If the condition persists please contact customer support with this error code. | |
| Initialization | Firmware initialization errors | 112#: Fatal Firmware error. If the condition persists please contact customer support with this error code. | |
| Initialization | Firmware initialization errors | 113#: Fatal Firmware error. If the condition persists please contact customer support with this error code. | |
| Initialization | Firmware initialization errors | 114#: Fatal Firmware error. If the condition persists please contact customer support with this error code. | |
| Initialization | Firmware initialization errors | 115#: Fatal Firmware error. If the condition persists please contact customer support with this error code. | |
| Initialization | Firmware initialization errors | 116#: Fatal Firmware error. If the condition persists please contact customer support with this error code. | |
| Initialization | Firmware initialization errors | 117#: Fatal Firmware error. If the condition persists please contact customer support with this error code. | |
| Initialization | Firmware configuration initialization errors | 200#: Firmware failed to initialise successfully due to incorrect or missing configuration files. The instrument may not be correctly configured, if the condition persists please contact customer support with this error code. | |
| Initialization | Firmware configuration initialization errors | 201#: Firmware failed to initialise successfully due to incorrect or missing configuration files. The instrument may not be correctly configured, if the condition persists please contact customer support with this error code. | |
| Initialization | Firmware configuration initialization errors | 202#: Firmware failed to initialise successfully due to incorrect or missing configuration files. The instrument may not be correctly configured, if the condition persists please contact customer support with this error code. | |
| Initialization | Firmware configuration initialization errors | 203#: Firmware failed to initialise successfully due to incorrect or missing configuration files. The instrument may not be correctly configured, if the condition persists please contact customer support with this error code. | |
| Initialization | Firmware configuration initialization errors | 204#: Firmware failed to initialise successfully due to incorrect or missing configuration files. The instrument may not be correctly configured, if the condition persists please contact customer support with this error code. | |
| Initialization | Firmware configuration initialization errors | 205#: Firmware failed to initialise successfully due to incorrect or missing configuration files. The instrument may not be correctly configured, if the condition persists please contact customer support with this error code. | |
| Initialization | Firmware configuration initialization errors | 206#: Firmware failed to initialise successfully due to incorrect or missing configuration files. The instrument may not be correctly configured, if the condition persists please contact customer support with this error code. | |
| Initialization | Firmware configuration initialization errors | 207#: Firmware failed to initialise successfully due to incorrect or missing configuration files. The instrument may not be correctly configured, if the condition persists please contact customer support with this error code. | |
| Initialization | Firmware configuration initialization errors | 208#: Firmware failed to initialise successfully due to incorrect or missing configuration files. The instrument may not be correctly configured, if the condition persists please contact customer support with this error code. | |
| Initialization | Firmware configuration initialization errors | 209#: Firmware failed to initialise successfully due to incorrect or missing configuration files. The instrument may not be correctly configured, if the condition persists please contact customer support with this error code. | |
| Initialization | Firmware configuration initialization errors | 210#: Firmware failed to initialise successfully due to incorrect or missing configuration files. The instrument may not be correctly configured, if the condition persists please contact customer support with this error code. | |
| Initialization | Firmware configuration initialization errors | 211#: Firmware failed to initialise successfully due to incorrect or missing configuration files. The instrument may not be correctly configured, if the condition persists please contact customer support with this error code. | |
| Initialization | Firmware configuration initialization errors | 212#: Firmware failed to initialise successfully due to incorrect or missing configuration files. The instrument may not be correctly configured, if the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 300#: Internal firmware error. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 301#: Internal firmware error. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 400#: Internal firmware error. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 401#: Internal firmware error. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 402#: Internal firmware error. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 500#: Internal Firmware error - Camera driver not initialised, check firmware log for details. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 501#: Internal Firmware error - Camera driver: Configuration appears to contain invalid parameters for this camera, check firmware log for details. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 502#: Internal firmware error - Camera driver: If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 503#: Internal firmware error - Camera driver: If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 504#: Internal firmware error - Camera driver: If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 505#: Internal Firmware error - Camera driver: Check firmware log for details. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 506#: Internal Firmware error - Camera driver: If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 507#: Internal Firmware error - Camera driver: If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 508#: Internal Firmware error - Camera driver: Check firmware log for details. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 509#: Internal Firmware error - Camera driver: Error programming FPGA. If the condition persists please contact customer support with this error code. | See Ver 5.2 - iCAP Diagnostics Manual.pdf |
| Firmware | Firmware error handler errors | 510#: Internal Firmware error - Camera driver: Error Installing DMA ISR. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 511#: Internal Firmware error - Camera driver: PCI comms loop-back test failed during initialisation. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 512#: Internal Firmware error - Camera driver: Device not found on the PCI bus. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 513#: Internal Firmware error - Camera driver: Timeout while polling FPGA. If the condition persists please contact customer support with this error code. | See Ver 5.2 - iCAP Diagnostics Manual.pdf |
| Firmware | Firmware error handler errors | 514#: Internal Firmware error - Camera driver: Invalid shutter timer value from FPGA, check firmware log for details. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 516#: Internal Firmware error - Camera driver: Invalid pixel locations detected in camera driver, check firmware log for details. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 517#: Autobias failure due to timeout - check flash up LED at rear of polychromator. If the condition persists please contact customer support with this error code. | See Ver 5.2 - iCAP Diagnostics Manual.pdf |
| Firmware | Firmware error handler errors | 600#: Internal Firmware error - CID86Process: Check firmware log for details. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 601#: Internal Firmware error - CID86Process: Check firmware log for details. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 602#: Internal Firmware error - CID86Process: Check firmware log for details. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 603#: Internal Firmware error - CID86Process: Check firmware log for details. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 604#: Internal Firmware error - CID86Process: Check firmware log for details. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 605#: Internal Firmware error - CID86Process: Invalid pixel locations detected, check firmware log for details. If the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 606#: Internal Firmware error - CID process - Invalid configuration settings detected. The instrument may not be correctly configured, if the condition persists please contact customer support with this error code. | |
| Firmware | Firmware error handler errors | 607#: Internal Firmware error - CID86Process: Invalid memory manager memory pointers, check firmware log for details. | |
| Firmware | Config commands | 1000#: File Download to instrument failed. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1001#: File Download to instrument failed. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1002#: File Download to instrument failed. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1003#: File Download to instrument failed. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1004#: File Download to instrument failed. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1005#: File Upload from instrument failed. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1006#: File Upload from instrument failed. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1007#: File Clear all on instrument failed. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1008#: File Clear all on instrument failed. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1009#: Writing Secondary Sample introduction settings error. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1010#: Sample introduction settings not found. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1011#: Firmware configuration setting error. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1012#: Firmware configuration setting error. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1013#: Firmware configuration setting error. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1014#: Firmware configuration setting error. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1015#: Firmware configuration setting error. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1016#: Secondary sample introduction error: Invalid pulse transition. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1017#: Firmware configuration setting error. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1018#: Firmware configuration setting error. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1019#: Firmware configuration setting error. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1020#: Firmware configuration setting error. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1021#: Firmware configuration setting error. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1022#: Firmware configuration setting error. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1023#: Firmware configuration setting error. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1024#: Firmware configuration setting error. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1025#: Firmware configuration setting error. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1026#: Firmware configuration setting error. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1027#: Firmware configuration setting error. If the condition persists please contact customer support with this error code. | |
| Firmware | Config commands | 1028#: Firmware configuration setting error: Check firmware log for details, if the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1101#: Analysis error (invalid number of subexposures) - exposure aborted | |
| Analysis | OES exposure commands | 1102#: Analysis error (invalid view type for this instrument) - exposure aborted | |
| Analysis | OES exposure commands | 1103#: Analysis error (invalid slit type for this instrument) - exposure aborted | |
| Analysis | OES exposure commands | 1104#: Analysis error - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1105#: Analysis error - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1106#: Analysis error - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1107#: Analysis error (invalid parameter) - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1108#: Analysis error (invalid parameter) - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1109#: Analysis error (invalid exposure type for this instrument) - exposure aborted | |
| Analysis | OES exposure commands | 1110#: Analysis error (invalid number of repeats) - exposure aborted | |
| Analysis | OES exposure commands | 1111#: Analysis error (invalid acquisition mode for this instrument) - exposure aborted | |
| Analysis | OES exposure commands | 1112#: Analysis error (invalid parameter) - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1113#: Analysis error (invalid parameter) - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1115#: Analysis error (invalid number of lines per subexposure) - exposure aborted | |
| Analysis | OES exposure commands | 1116#: Analysis error (number of lines exceeded) - exposure aborted | |
| Analysis | OES exposure commands | 1117#: Analysis error (invalid exposure time) - exposure aborted | |
| Analysis | OES exposure commands | 1118#: Analysis error (invalid exposure time) - exposure aborted | |
| Analysis | OES exposure commands | 1119#: Analysis error (invalid time increment) - exposure aborted | |
| Analysis | OES exposure commands | 1120#: Analysis error (invalid number of subexposures) - exposure aborted | |
| Analysis | OES exposure commands | 1121#: Analysis error (number of lines exceeded) - exposure aborted | |
| Analysis | OES exposure commands | 1122#: Analysis error (invalid exposure time) - exposure aborted | |
| Analysis | OES exposure commands | 1123#: Analysis error - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1124#: Analysis error (invalid exposure time) - exposure aborted | |
| Analysis | OES exposure commands | 1125#: Analysis error (unsupported exposure parameter) - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1126#: Analysis error (unsupported exposure parameter) - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1127#: Analysis error (unsupported exposure parameter) - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1128#: Analysis error (unsupported exposure parameter) - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1129#: Analysis error (unsupported exposure parameter) - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1130#: Analysis error - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1131#: Analysis error (invalid subarray coordinates) - exposure aborted | |
| Analysis | OES exposure commands | 1133#: Plasma went out during the exposure - exposure aborted | |
| Analysis | OES exposure commands | 1134#: Analysis error (invalid LED state for exposure) - exposure aborted | |
| Analysis | OES exposure commands | 1135#: Analysis error (invalid shutter position for exposure) - exposure aborted | |
| Analysis | OES exposure commands | 1136#: Analysis error (invalid number of time slices) - exposure aborted | |
| Analysis | OES exposure commands | 1137#: Analysis error (invalid viewing height) - exposure aborted | |
| Analysis | OES exposure commands | 1138#: Invalid torch compartment interlock detected during exposure - exposure aborted | |
| Analysis | OES exposure commands | 1139#: Invalid purge gas pressure interlock detected during exposure - exposure aborted | |
| Analysis | OES exposure commands | 1140#: Invalid torch gas pressure interlock detected during exposure - exposure aborted | |
| Analysis | OES exposure commands | 1141#: Invalid water flow interlock detected during exposure - exposure aborted | |
| Analysis | OES exposure commands | 1142#: Invalid drain flow sensor interlock detected during exposure - exposure aborted | |
| Analysis | OES exposure commands | 1143#: Invalid exhaust interlock detected during exposure - exposure aborted | |
| Analysis | OES exposure commands | 1200#: Analysis error - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1201#: Analysis error - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1202#: Analysis error - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1203#: Analysis error - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1204#: Analysis error - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1205#: Analysis error - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | OES exposure commands | 1206#: Analysis cancelled by user - exposure aborted | |
| Analysis | OES exposure commands | 1207#: Analysis error (exposure data too large) - exposure aborted | |
| Analysis | OES exposure commands | 1208#: Analysis error (invalid argument, check instrument configuration and firmware log for details) - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | Generic run exposure system errors | 1209#: Analysis error - exposure aborted, check firmware log for details. If the condition persists please contact customer support with this error code. | |
| Analysis | Generic run exposure system errors | 1210#: Analysis error - exposure aborted, check firmware log for details. If the condition persists please contact customer support with this error code. | |
| Analysis | Generic run exposure system errors | 1211#: Analysis error - (CID all zero's - Check detector and detector configuration) exposure aborted. If the condition persists please contact customer support with this error code. |
Check to see if system can run FF image. The instrument can be powered down. Remove camera RS 232 cables and reconnect them. Power up and check for analysis functions. |
| Analysis | Generic run exposure system errors | 1212#: Analysis error - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | Generic run exposure system errors | 1213#: Analysis error (return data buffer full) - exposure aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | Generic run exposure system errors | 1214#: Analysis error (invalid sample introduction method requested of instrument). | |
| Analysis | Generic run exposure system errors | 1215#: Analysis error - exposure aborted. If the condition persists please contact customer support with this error code. | |
| 1216#: RF Power could not maintain requested power - If the actual RF power is out of range (+/- 20 W) for more than 20 seconds you will get error E1216 | Is power reading back with set point? If so, Check Argon Pressure, Exhaust Flow, coil position, Nebulizer; basically anything which could be causing plasma conditions to change. | ||
| 1217#: Auxillary Gas Flow - Count not maintain requested value. | |||
| 1218#: Nebulizer Gas Flow Error - Could not maintain requested value. | |||
| 1219#: Coolant Gas Flow - Could not maintain requested value | |||
| Analysis | Generic run exposure system errors | 1250#: Detector not ready to process command - operation aborted. If the condition persists please contact customer support with this error code. | |
| Analysis | Generic run exposure system errors | 1251#: Firmware not ready to process command - operation aborted. If the condition persists please contact customer support with this error code. | Goto Empty Configuraon in Qtegra, Open up iTEVA and handshake with instrument through iTEVA, Close iTEVA, and then Go to active configuraon in Qtegra. Make sure camera config is correct |
| Miscellaneous | Misc commands | 1700#: Firmware download failed. If the condition persists please contact customer support with this error code. | |
| Miscellaneous | Misc commands | 1701#: Internal firmware error. If the condition persists please contact customer support with this error code. | |
| Miscellaneous | Misc commands | 1702#: Firmware retrieval of error logs failed. If the condition persists please contact customer support with this error code. | |
| Miscellaneous | Misc commands | 1703#: Internal firmware error. If the condition persists please contact customer support with this error code. | |
| Miscellaneous | Misc commands | 1704#: Firmware download IO Board firmware failed. If the condition persists please contact customer support with this error code. | |
| Miscellaneous | Misc commands | 1705#: Firmware download RF Unit firmware failed. If the condition persists please contact customer support with this error code. | |
| Miscellaneous | Misc commands | 1706#: Firmware download TSP FPGA firmware failed. If the condition persists please contact customer support with this error code. | |
| Miscellaneous | Misc commands | 1707#: CIDTEST Firmware download failed. If the condition persists please contact customer support with this error code. | |
| Miscellaneous | Misc commands | 1708#: Internal firmware error. If the condition persists please contact customer support with this error code. | |
| Miscellaneous | Misc commands | 1709#: Internal firmware error. If the condition persists please contact customer support with this error code. | |
| Miscellaneous | Misc commands | 1710#: Internal firmware error. If the condition persists please contact customer support with this error code. | |
| Miscellaneous | Misc commands | 1711#: Internal firmware error. If the condition persists please contact customer support with this error code. | |
| Miscellaneous | Misc commands | 1712#: Internal firmware error. If the condition persists please contact customer support with this error code. | |
| CID | CID commands | 1800#: Internal firmware error. If the condition persists please contact customer support with this error code. | |
| CID | CID commands | 1810#: Internal firmware error. If the condition persists please contact customer support with this error code. | |
| CID | CID commands | 1811#: Internal firmware error. If the condition persists please contact customer support with this error code. | |
| CID | CID commands | 1812#: Internal firmware error. If the condition persists please contact customer support with this error code. | |
| CID | CID commands | 1813#: Internal firmware error. If the condition persists please contact customer support with this error code. | |
| I/O | I/O commands | 2000#: Firmware serial port could not be initialised, instrument must be restarted. If the condition persists please contact customer support with this error code. | |
| I/O | I/O commands | 2002#: IO communications error (RX data error), check firmware log for details. If the condition persists please contact customer support with this error code. | |
| I/O | I/O commands | 2003#: IO Board firmware download failed, check firmware log for details. If the condition persists please contact customer support with this error code. | |
| I/O | I/O commands | 2005#: IO Board not in a state to process commands. If the condition persists please contact customer support with this error code. | |
| I/O | I/O commands | 2006#: RF firmware download failed, check firmware log for details. If the condition persists please contact customer support with this error code. | |
| I/O | I/O commands | 2007#: RF firmware download error, please restart the instrument to reset instrument communications. If the condition persists please contact customer support with this error code. | |
| RF | generated by RF commands | 2011#: Pump speed invalid: speed unchanged | |
| RF | generated by RF commands | 2012#: RF power invalid: power unchanged | |
| RF | generated by RF commands | 2013#: Auxiliary Gas flow invalid: flow unchanged | |
| RF | generated by RF commands | 2014#: Nebuliser Gas flow invalid: flow unchanged | |
| RF | generated by RF commands | 2015#: Coolant Gas flow invalid: flow unchanged | |
| RF | generated by RF commands | 2016#: Additional Gas flow invalid: flow unchanged | |
| RF | generated by RF commands | 2017#: Failed to set TE Power | |
| RF | generated by RF commands | 2018#: Failed to read TE Power | |
| RF | generated by RF commands | 2019#: Failed to read TE Status | |
| RF | generated by RF commands | 2020#: Failed to set Tank power | |
| RF | generated by RF commands | 2021#: Failed to read TE Power | |
| RF | generated by RF commands | 2022#: Failed to read Gas Solenoid Status | |
| RF | generated by RF commands | 2023#: Failed to set Gas Solenoid | |
| RF | generated by RF commands | 2024#: Failed to read water temperature | |
| RF | generated by RF commands | 2025#: Failed to read interlock status | |
| RF | generated by RF commands | 2026#: Failed to set pump speed | |
| RF | generated by RF commands | 2027#: Failed to read pump speed | |
| RF | generated by RF commands | 2028#: Failed to set pump direction | |
| RF | generated by RF commands | 2029#: Failed to read pump direction | |
| RF | generated by RF commands | 2030#: Failed to read nebuliser gas pressure | |
| RF | generated by RF commands | 2031#: Failed to set RF power | |
| RF | generated by RF commands | 2032#: Failed to read RF power | |
| RF | generated by RF commands | 2033#: Failed to read RF status | |
| RF | generated by RF commands | 2034#: Failed to set auxiliary gas flow | |
| RF | generated by RF commands | 2035#: Failed to read auxiliary gas flow | |
| RF | generated by RF commands | 2036#: Failed to set nebuliser gas flow | |
| RF | generated by RF commands | 2037#: Failed to read nebuliser gas flow | |
| RF | generated by RF commands | 2038#: Failed to set coolant gas flow | |
| RF | generated by RF commands | 2039#: Failed to read coolant gas flow | |
| RF | generated by RF commands | 2040#: Failed to set additional gas flow | |
| RF | generated by RF commands | 2041#: Failed to read additional gas flow | |
| RF | generated by RF commands | 2042#: Failed to set motor M1 position | |
| RF | generated by RF commands | 2043#: Failed to set motor M2Slit position | |
| RF | generated by RF commands | 2044#: Failed to set motor M2View position | |
| RF | generated by RF commands | 2045#: Failed to read motor M1 position | |
| RF | generated by RF commands | 2046#: Failed to read motor M2 position | |
| RF | generated by RF commands | 2047#: Failed to set SSEA triggers | |
| RF | generated by RF commands | 2048#: Failed to read SSEA triggers | |
| RF | generated by RF commands | 2049#: Failed to read IO Board status | |
| RF | generated by RF commands | 2050#: Failed to read IO Board version information | |
| RF | generated by RF commands | 2051#: Failed to read RF version information | |
| RF | generated by RF commands | 2052#: Failed to set view | |
| RF | generated by RF commands | 2053#: Failed to set slit | |
| RF | generated by RF commands | 2054#: Failed to set plasma | |
| RF | generated by RF commands | 2055#: Failed to abort IO operation | |
| RF | generated by RF commands | 2056#: Slit specified invalid for this instrument. | |
| RF | generated by RF commands | 2057#: View specified invalid for this instrument. | |
| RF | generated by RF commands | 2058#: Motor specified invalid for this instrument. | |
| RF | generated by RF commands | 2059#: Invalid Motor M1 position requested. | |
| RF | generated by RF commands | 2060#: Invalid Motor M2SLIT position requested | Misaligned fore optics. Check mirrors and perform foreoptic alignment |
| RF | generated by RF commands | 2061#: Invalid Motor M2VIEW position requested | |
| RF | generated by RF commands | 2062#: Failed to set plasma purge delay | |
| RF | generated by RF commands | 2063#: Invalid plasma purge delay specified requested | |
| RF | generated by RF commands | 2064#: Failed to set DAC value | |
| RF | generated by RF commands | 2065#: Failed to get ADC value | |
| RF | generated by RF commands | 2067#: Failed to initialise motors. If the condition persists please contact customer support with this error code. | |
| RF | generated by RF commands | 2068#: Unsupported command for this instrument type (Basic Gasbox) - Command failed. If the condition persists please contact customer support with this error code. | |
| RF | generated by RF commands | 2069#: Failed to find M2 View ( Major ) motor end-stop, fore-optics motor positions are now invalid. If the condition persists please contact customer support with this error code. | |
| RF | generated by RF commands | 2070#: Failed to find M2 Slit ( Minor ) motor end-stop, fore-optics motor positions are now invalid. If the condition persists please contact customer support with this error code. | |
| RF | generated by RF commands | 2071#: Plasma ignition failed, reason for failure unknown. | |
| RF | generated by RF commands | 2072#: Failed to read RF FET Temp | |
| RF | generated by RF commands | 2073#: Failed to read debug bytes | |
| RF | generated by RF commands | 2074#: Slit Mask motor position specified invalid | |
| RF | generated by RF commands | 2075#: Failed to set slit mask motor position | |
| RF | generated by RF commands | 2076#: Firmware failed to get a valid IO Board version number, system not initialised. Restart instrument and if the condition persists please contact customer support with this error code. | |
| RF | generated by RF commands | 2077#: Firmware failed to get a valid RF version number, system not initialised. Restart instrument and if the condition persists please contact customer support with this error code. | |
| RF | generated by RF commands | 2078#: Failed during wait for ETV Ready. | |
| RF | generated by RF commands | 2079#: Failed to set Drain Flow Sensor state. If the condition persists please contact customer support with this error code. | |
| RF | generated by RF commands | 2080#: One of the fore-optics motors timed-out before reaching desired position, fore-optics motor positions are now invalid. If the condition persists please contact customer support with this error code. | |
| RF | generated by RF commands | 2081#: The M2 View motor timed-out before reaching the desired position, fore-optics motor positions are now invalid. If the condition persists please contact customer support with this error code. | |
| RF | generated by RF commands | 2082#: The M2 Slit motor timed-out before reaching the desired position, fore-optics motor positions are now invalid. If the condition persists please contact customer support with this error code. | |
| RF | generated by RF commands | 2083#: The M1 motor timed-out before reaching the desired position, fore-optics motor positions are now invalid. If the condition persists please contact customer support with this error code. | |
| RF | generated by RF commands | 2084#: The Slit Mask motor timed-out before reaching the desired position, fore-optics motor positions are now invalid. If the condition persists please contact customer support with this error code. | |
| 2198#: Water flow error | |||
| RF | generated by RF commands | 2199#: Failed to extinguish plasma. | |
| RF | generated by RF commands | 2071#: Plasma ignition failed, reason for failure unknown. | |
| 2200#: Plasma ignition failed, 3kw Power supply reported bad AC input | |||
| RF | generated by RF commands | 2201#: Plasma ignition failed, RF status failed. If the condition persists please contact customer support with this error code. | |
| RF | generated by RF commands | 2202#: Plasma ignition failed, RF reported bad supply power output failure | |
| RF | generated by RF commands | 2203#: Plasma ignition failed, RF reported bad argon flow interlock failure | |
| RF | generated by RF commands | 2204#: Plasma ignition failed, RF reported bad water flow interlock failure | |
| RF | generated by RF commands | 2205#: Plasma ignition failed, RF reported over temperature failure | Could be RF Board or RF Interface board. This error can also be caused by low water flow |
| RF | generated by RF commands | 2206#: Plasma ignition failed, RF reported over current failure | |
| 2208#: Plasma ignition failed; RF seems OK. Check your sample introduction system as described in iTEVA Help. If the condition persists please contact customer support with this error code. | |||
| 2209#: Plasma ignition failed; low ignition current. If the condition persists please contact customer support with this error code | |||
| Interlocks instrument | instrument interlocks and not RF interlocks | 2210#: Plasma ignition failed, the torch compartment interlock is bad | |
| Interlocks instrument | instrument interlocks and not RF interlocks | 2211#: Plasma ignition failed, the purge gas interlock is bad | |
| Interlocks instrument | instrument interlocks and not RF interlocks | 2212#: Plasma ignition failed, the plasma gas interlock is bad | |
| Interlocks instrument | instrument interlocks and not RF interlocks | 2213#: Plasma ignition failed, the water flow interlock is bad | |
| Interlocks instrument | instrument interlocks and not RF interlocks | 2215#: Plasma ignition failed, the exhaust flow interlock is bad | |
| I/O | IO Board communications errors | 2900#: IO Board communications error - TX data write error. If the condition persists please contact customer support with this error code. | |
| I/O | IO Board communications errors | 2901#: IO Board communications error - wait for port timeout. If the condition persists please contact customer support with this error code. | |
| I/O | IO Board communications errors | 2902#: IO Board communications error - Mutex release error. If the condition persists please contact customer support with this error code. | |
| I/O | IO Board communications errors | 2903#: IO Board communications error - RX data timeout or incorrect number of bytes received. If the condition persists please contact customer support with this error code. | |
| I/O | IO Board communications errors | 2904#: IO Board communications error - IO Board detected protocol compare error. If the condition persists please contact customer support with this error code. | |
| I/O | IO Board communications errors | 2905#: IO Board communications error - IO Board detected protocol frame error. If the condition persists please contact customer support with this error code. | |
| I/O | IO Board communications errors | 2906#: IO Board communications error - IO Board detected parity error. If the condition persists please contact customer support with this error code. | |
| I/O | IO Board communications errors | 2907#: IO Board communications error - IO Board all zeros response. If the condition persists please contact customer support with this error code. | |
| I/O | IO Board communications errors | 2908#: IO Board communications error - IO Board detected undefined protocol error. If the condition persists please contact customer support with this error code. | |
| I/O | IO Board communications errors | 2909#: IO Board communications error - IO Board detected parameter error. If the condition persists please contact customer support with this error code. | |
| I/O | IO Board communications errors | 2910#: IO Board communications error - IO Board detected message sequencing error. If the condition persists please contact customer support with this error code. | |
| I/O | IO Board communications errors | 2911#: IO Board communications error - IO Board detected unknown message error. If the condition persists please contact customer support with this error code. | |
| I/O | IO Board communications errors | 2912#: IO Board communications error - IO Board detected undefined message error. If the condition persists please contact customer support with this error code. | |
| I/O | IO Board communications errors | 2913#: IO Board communications error - RX data protocol mismatch error. If the condition persists please contact customer support with this error code. | |
| I/O | IO Board communications errors | 2914#: IO Board communications error - RX data re-program protocol mismatch error. If the condition persists please contact customer support with this error code. | |
| I/O | IO Board communications errors | 2915#: IO Board communications error - IO Board comms time-out error. If the condition persists please contact customer support with this error code. | |
| I/O | IO Board communications errors | 2916#: IO Board communications error - IO Board comms overrun error. If the condition persists please contact customer support with this error code. | |
| RF | RF commands | 3001#: RF firmware download error (RF failed to enter program mode) - download failed. If the condition persists please contact customer support with this error code. | |
| RF | RF commands | 3002#: RF firmware download error (write data failed) - download failed. If the condition persists please contact customer support with this error code. | |
| RF | RF commands | 3003#: RF firmware download error (RF failed to exit program mode) - download failed. Please restart the instrument to reset instrument communications. If the condition persists please contact customer support with this error code. | |
| RF | RF commands | 3004#: RF firmware download error (checksum get failed) - download failed. If the condition persists please contact customer support with this error code. | |
| RF | RF commands | 3005#: RF firmware download error (checksum check failed) - download failed. If the condition persists please contact customer support with this error code. | |
| RF | RF commands | 3006#: RF firmware download error (firmware write failed) - download failed. If the condition persists please contact customer support with this error code. | |
| RF | RF commands | 3010#: RF firmware download error (RF failed to restart) - download failed. Please restart the instrument to reset instrument communications. If the condition persists please contact customer support with this error code./ | |
| 3542#: Not showing up in the subarray | Wavecal corrupted. Ran a new wavecal | ||
| 9000#: Plasma ignition failed; reason unknown | |||
| Plasma | Reasons for the plasma going out | 9002#: Plasma went out unexpectedly, reason unknown. | |
| Plasma | Reasons for the plasma going out | 9002#: Plasma went out unexpectedly, RF reported bad supply power output failure. | |
| Plasma | Reasons for the plasma going out | 9003#: Plasma went out unexpectedly, RF reported bad argon flow interlock failure. | |
| Plasma | Reasons for the plasma going out | 9004#: Plasma went out unexpectedly, RF reported bad water flow interlock failure. | |
| Plasma | Reasons for the plasma going out | 9005#: Plasma went out unexpectedly, RF reported over temperature failure. | |
| Plasma | Reasons for the plasma going out | 9006#: Plasma went out unexpectedly, RF reported over current failure. | |
| Interlocks instrument | instrument interlocks and not RF interlocks | 9010#: Plasma went out unexpectedly, the torch compartment interlock is bad. | |
| Interlocks instrument | instrument interlocks and not RF interlocks | 9011#: Plasma went out unexpectedly, the purge gas interlock is bad. | |
| Interlocks instrument | instrument interlocks and not RF interlocks | 9012#: Plasma went out unexpectedly, the plasma gas interlock is bad. | |
| Interlocks instrument | instrument interlocks and not RF interlocks | 9013#: Plasma went out unexpectedly, the water flow interlock is bad. | |
| Interlocks instrument | instrument interlocks and not RF interlocks | 9014#: Plasma went out unexpectedly, the drain flow interlock is bad. | |
| Interlocks instrument | instrument interlocks and not RF interlocks | 9015#: Plasma went out unexpectedly, the exhaust flow interlock is bad. | |
| 33015: | |||
| 33017: Spectrometer Optimization failed, peak too weak or not found | |||
| 33018: Unable to complete torch alignment. Can’t locate edges of plasma image. Carryout foreoptic prealignment again. | |||
| 33024: Debug Spectrometer Optimize failed | |||
| 33100: Debug IIO Internal software error. General error in comms, the command to take a sample failed for some unknown reason | This generally can be ignored. | ||
| 33101: Debug Invalid command response code returned | Bypass internal comm cable | ||
| 33203: Failed to set plasma conditions | |||
| 33204: Warning - Failure to load Wavelength Check file, calcheck bin | |||
| CID | Camera error | 33207#. Detector un-initialised | See Diagnostics Manual v2.2 - Instrument Error Codes |
| 33207: Unknown detector error has occurred | |||
| I/O | I/O commands | 33208#. I/O & RF Communications Errors | See Diagnostics Manual v2.2 - RF and I/O Problems |
| I/O | I/O commands | 33209#. I/O & RF Communications Errors | See Diagnostics Manual v2.2 - RF and I/O Problems |
| 33210# 33210# The configuration files(ini files) were incomplete or missing | Load empty configuration in Qtegra and leave program. Or reboot PC and Power off then on iCAP. Open iTEVA and allow the instrument to initialize. Once done. Start up plasma. Once you have confirmed plasma control and no problem, switch off plasma and close iTEVA. Open Qtegra and you should be okay. The INI files will be re-established from camera unless you have put in a new camera. If you have put in a new camera, one must run all the alignment and run the Wavelength calibration in the manufacturing to establish these missing files | ||
| Firmware | Firmware error | 33211#. The firmware recently rebooted due to a non recoverable error. The firmware Error log will be downloaded | See Diagnostics Manual v2.2 - Instrument Error Codes |
| I/O | I/O commands | 33212#. An I/O board communications error has occurred. Ensure the controller board is powered and connected correctly, if the condition persists please contact customer support. | See Diagnostics Manual v2.2 - RF and I/O Problems |
| RF | RF commands | 33213# - An RF generator communications error has occurred. Ensure the RF generator is powered and connected correctly, if the condition persists please contact customer support | RF power supply fan cycles continuously due to comm loop. Replace RF Interface board. See Diagnostics Manual v2.2 - RF and I/O Problems |
| 33214: A communications timeout has occurred during instrument initialization | I would have the customer to wait for 3 minutes after the instrument has been switch on before opening Qtegra. This would allow the RF gen to go thru its initialization phase, which all of them do. After 3 minutes, then open the software and tell system to turn on. | ||
| Analysis | Cetac Autosampler | 33450# - Cetac Autosampler error, No Response to Command | |
| 33495# plasma went out unexpectectedly; | RF Gen temp rose to exceed 27 deg; water flow blockage or pump head deteriated; check circulator pressure for drop when plasma starts; no drop then blockage or pump flow failure; | ||
| 33535 /*Error Updating Method with standard signals and coefficients*/ | |||
| 33536 /*"#33536#: Checksum invalid in %s table. Record ID %s. The database may have been edited outside iTEVA. Data invalid - this record should be deleted."*/ | |||
| 33537 /*"#33537#: Failed to write Audit Trail entry to database."*/ | |||
| 33538 /*"#33538#: Failed to write Signature to database."*/ | |||
| 33539# Error Updating Method with standard: Standard saturated. The reason for this is because the band of one of the analyzed elements is overlapping with something else with higher concentration.. |
|||
| 33540 ERROR_UPDATING_METHOD_WITH_STANDARD_SUBARRAY | |||
| 33541 ERROR_UPDATING_METHOD_WITH_STANDARD_PLASMA | |||
| 33542 ERROR_UPDATING_METHOD_WITH_STANDARD_PEAK_OFF_CHIP | |||
ce this text to add the Resolution.
Analysis
Cause