Whatever EMV you got some large response, keep that level, save the tune file, again as COLD_Tune.U. If the signal goes up, and up, and up.the EMV and signal processing are probably working fine. If it does, great! If it doesn't there is another test to do. Even with no peaks, you want to see if turning the EM up changes the signal. Do you see anything remotely resembling a peak? With AMU Gain and Offset at 0, the 'peak' may be wider than the window and that's OK for now. Do you see anything remotely resembling a really wide peak? If not, turn the EMV up, up, up. Change Entrance Lens offset to 12 and the Entrance Lens to 28. Change the AMU Gain to 400 and AMU Offset to 50. ![]() Then, before venting it to check out inside, go into Manual Tune. That will start it cooling off if you need to vent it. Turn the Source Temperature and Quad Temperature both to 40☌. What's the vacuum level? Column flow ~1.2 ml/min? Is there a way I can verify this is the case? Furthermore, what are the chances that this breaks on two of our instruments just a few months apart? Am I doing something to damage the side board?īelow are some screenshots that help show the issue. I'm really at a loss and the leading theory is that the analyzer side board is broken and needs to be replaced. I checked and all cables are connected just fine. I also did a few power cycles of everything. I hear the solenoid click everytime I do a manual tune "profile" or "scan".Ħ) Vacuum & He flow look fine. The MSD reset but no luck.ĥ) The PFTBA does look low but I was able to run a perfectly fine tune just minutes before I turned the system off to cut the column. Then I pressed item and clicked reset controller. We haven't changed the EM Horn, could this be it? If so, how do we test for this?Ĥ) I tried resetting the MSD by pressing the "menu" button until I saw the "controller" item. Regardless, we tried another filament change and no luck. I tried all the other tune files on our system, no luck.ģ) We changed the filaments and cleaned the ion source very recently. Here are some of the things I've tried:ġ) I tried re-cutting the column and making sure that it was only sticking out ~1-2mM into the analyzer.Ģ) Perhaps a corrupt tune file? I changed atune.u to atune.old and loaded a fresh copy of atune.u. The instrument was working perfectly fine, we just had a slight leak which was causing our peaks to look small (N2 abundance was 20%). This issue happened after I vented, turned off the GCMS, cut the column (we had a small leak), turned the GCMS back on, pumped down, and then tried to run a tune. ![]() Extremely few peaks, only 6 reported with an abundance of 962. If I do a manual tune it looks like a lawn, maybe I see a little higher peak corresponding to the PFTBA standard ion peaks but overall it just looks like noise. I can't do an autotune because it says "Tune action stopped: Cannot achieve constant peak widths". The detector seems completely dead, if I run a sample I get a complete flatline. It would also be a good idea to clear the local memory of the GC (by holding the button while power cycling) just to make sure that the corrupt method is not being stored locally on the instrument.I recently have experienced an issue on not one, but TWO of our Agilent 5973 detectors that we have connected to GCs. The best way to deal recover from that would be to create a new method in the software from the default method. Agilent's recommendation is to always use the latest firmware and driver releases to avoid any possible defects.Īnother possible explanation would be a corrupt method. This might also be linked to the firmware and driver versions that you are using to control your GC. ![]() Which do you select? (Depending on your instrument configuration you might not see this popup). If you are uploading from the instrument, then it is possible that the method stored locally on the instrument is not setup properly. ![]() When you launch the online session for your instrument, you have the option of either downloading a method to the instrument, uploading from the instrument, or creating a new method.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |