Varian Saturn 2200 RF problem
Posted: Mon Jul 27, 2015 11:41 am
We have been using a Varian Saturn 2200 MS for the past 9 years without any particular problems (other than turbopump replacement). Recently an error has been cropping up and is preventing us from using the MS.
Under diagnostics we are getting an error, under RF test:
The RF DAC failed at DAC 56. Likely causes include: The Rf Generator board is defective (RF DAC instrumentation AMP.)
Sometimes it is DAC 57 or 59, but usually 56.
(Filament 2 is also reported as OPEN even if this has never been used - I don't know if it is related to the RF error).
This started to appear after we were getting errors during a runs, (we do not run diagnostics regularly). The run starts normally with filament 1 off but when the filament should be turned on an error occurs:
Module 2000:40 : Error downloading scan function (1900906)
This was a minor occurrence but now it is very common and it has now become so common that it is no longer possible to do any analysis. At this point we ran diagnostics and got the error, though it may not be related.
The problem is that we no longer have any support and am hoping that it may be something that can be done by an experienced user. Anyone had similar problems?
Under diagnostics we are getting an error, under RF test:
The RF DAC failed at DAC 56. Likely causes include: The Rf Generator board is defective (RF DAC instrumentation AMP.)
Sometimes it is DAC 57 or 59, but usually 56.
(Filament 2 is also reported as OPEN even if this has never been used - I don't know if it is related to the RF error).
This started to appear after we were getting errors during a runs, (we do not run diagnostics regularly). The run starts normally with filament 1 off but when the filament should be turned on an error occurs:
Module 2000:40 : Error downloading scan function (1900906)
This was a minor occurrence but now it is very common and it has now become so common that it is no longer possible to do any analysis. At this point we ran diagnostics and got the error, though it may not be related.
The problem is that we no longer have any support and am hoping that it may be something that can be done by an experienced user. Anyone had similar problems?