Page 1 of 1

PFTBA Fragmentation pattern

Posted: Mon Jul 17, 2017 10:19 am
by environeer
Hello Forum!
On an Agilent GCMS system (7890A/5975C) we weekly check if the recommended PFTBA- fragmentation conditions (69mz: 100%, 219mz:~50%, 502:~1%) are met, which was the case for months.

After cleaning the ion source and a following tuning procedure however, the PFTBA fragmentation pattern changed and now turns out to be: 69mz:100%, 219:~90%, 502:~10%.

Has anyone experienced this phenomenon before?

Re: PFTBA Fragmentation pattern

Posted: Mon Jul 17, 2017 12:17 pm
by dblux_
Hello Forum!
On an Agilent GCMS system (7890A/5975C) we weekly check if the recommended PFTBA- fragmentation conditions (69mz: 100%, 219mz:~50%, 502:~1%) are met, which was the case for months.

After cleaning the ion source and a following tuning procedure however, the PFTBA fragmentation pattern changed and now turns out to be: 69mz:100%, 219:~90%, 502:~10%.

Has anyone experienced this phenomenon before?
After cleaning the source you gained proper sensitivity for high masses.

Re: PFTBA Fragmentation pattern

Posted: Tue Jul 18, 2017 7:21 pm
by James_Ball
Also if there is still some water hanging around in the analyzer it will bias the high mass abundance. I usually let mine pump down overnight before tuning, and then after a week do it again just in case. It takes a while for all that metal to come to a thermal equilibrium, but once it does it holds for a long time.

Re: PFTBA Fragmentation pattern

Posted: Wed Jul 19, 2017 9:28 am
by environeer
Solved!

It turned out that a wrong/different tune file caused these issues. stune and atune were somehow mixed up and falsely attached to the current method.

Air/Water checks are performed weekly, and indeed, after maintenance on the MS, an adequate amount of time is given for proper equilibration.

Thanks.

Re: PFTBA Fragmentation pattern

Posted: Wed Jul 19, 2017 10:02 am
by dblux_
Solved!
It turned out that a wrong/different tune file caused these issues. stune and atune were somehow mixed up and falsely attached to the current method.
...
But you don't invoke tuning procedure from analytical method, do you ?
Then, no matter what tune file is attached to the analytical method you may stune or atune instrument.

Re: PFTBA Fragmentation pattern

Posted: Thu Jul 20, 2017 2:53 pm
by James_Ball
Solved!
It turned out that a wrong/different tune file caused these issues. stune and atune were somehow mixed up and falsely attached to the current method.
...
But you don't invoke tuning procedure from analytical method, do you ?
Then, no matter what tune file is attached to the analytical method you may stune or atune instrument.
Could be the tune file that the method uses for operating parameters.

Re: PFTBA Fragmentation pattern

Posted: Fri Jul 21, 2017 7:32 am
by environeer
But you don't invoke tuning procedure from analytical method, do you ?
Then, no matter what tune file is attached to the analytical method you may stune or atune instrument.
No. The tuning is done manually.