Hi,
I have recently seen the "Carousel Error 8" on one of our 7697A Headspace samplers and was curious if anyone knows what this particular error code indicates is the issue?
I has happened twice in my last run, about every 5 or so vials.
Thanks!
Find maintenance, best practice, and troubleshooting articles.
Hi,
I have recently seen the "Carousel Error 8" on one of our 7697A Headspace samplers and was curious if anyone knows what this particular error code indicates is the issue?
I has happened twice in my last run, about every 5 or so vials.
Thanks!
Need to update the headspace firmware to A.01.08.3
Thanks! Where do we get the firmware update? Can we download from Agilent and update ourselves?
Hello chrom . You can download the firmware utility from here: GC Firmware Update | Agilent. The procedure to update the firmware can be found in the following resources in the Agilent Knowledge Portal: Agilent GC Firmware Update Procedure - GC Articles - Gas Chromatography Portal - Agilent Community and Agilent GC Firmware Update - GC Videos - Gas Chromatography Portal - Agilent Community.
The resources show the procedure for GCs, but it is the same tool for the Agilent 7697A headspace sampler
Thanks!
Hello chrom ,
Do you still need assistance with this? If you do, please take into consideration the notes below. However, if the issue was resolved, could you please share what the resolution was?
To my knowledge, the Firmware upgrade is a solution for a particular case, specifically for a configuration including a cooling tray.
Carousel error #8, just as any carousel errors (regardless of the number) could be caused by a number of things. Page 63 in the manual below details possible causes for carousel errors, which applies to #8 as well.
Agilent 7697A Headspace Sampler Troubleshooting Guide
The easiest and more obvious things to check are obstructions in the oven, other parts in that list may require an Agilent engineer. For the latter, feel free to reach out to your local Agilent Team for assistance.
Hi,
We were able to resolve the issue and if I remember correctly it was the firmware update.
Thanks!