Software Status Bulletin

QTOF/TOF Acquisition     QTOF/TOF Acquisition

Preface
-------------------------
This Software Status Bulletin (SSB) documents all known problems in the software
product designated above. The SSB is derived from Known Problem Reports (KPR)
which result from user problems that have been classified as documentation
problems or software defects. When a KPR is written, an identifying number is
assigned to it, and the KPR is added to the next edition of the SSB.

User inputs that have been classified as Enhancement Requests are not documented
in the SSB. User problems that have been submitted, but that have not been
classified by the time the SSB is generated are not included in the SSB.

How to use the SSB
-------------------------
When you experience a problem with a product, first check this SSB to see if the
problem has been reported already, and if there is a temporary workaround
available for the problem, or if the problem has already been fixed by a new
revision. If the problem is not listed in this SSB then you may wish to report
it to the Response Center or to your field support representative.

To determine if your problem is documented in this SSB, first look in the
Keyword Index section of the SSB. Under each keyword is a listing of one-line
descriptions of related KPRs. If any of these sound like yours, locate the KPR
# in the Known Problem Reports section of the SSB, and read the full KPR. The
KPRs in the Known Problem Reports section are sorted by KPR #.

There are two sections in the SSB:
Keyword Index: This index is categorized by keyword. For each KPR there is a
brief description and a KPR #. A KPR may be associated with more than one
keyword.

Known Problem Reports: This section contains KPRs, with all the available
information relevant to the problem. KPRs in this section are sorted by KPR #.

Keyword Glossary

Keyword Index

Keyword: 

One-line Description:

Method Pane Initialization Failure When Configured LC Device is Powered Off

Problem:

n/a

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Column device would not come back after power outtage

Problem:

n/a

Temporary Solution:

The user must shutdown and restart AppUI and engines to get the system working again.

Fix Information:

n/a

Keyword: 

One-line Description:

Forced engine restart at initial installation

Problem:

n/a

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Real Time Reference Mass Indicators working when no reference mass ion selected

Problem:

n/a

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

System should stop run with incorrect reference mass correction settings

Problem:

n/a

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Wrong Polarity Settings Can Be Saved in Parameters Tab

Problem:

n/a

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Column - Incorrect minimum temperature

Problem:

n/a

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Quad Tune Does Not Turn Off The Calibrant If Quad Tune Fails To Complete

Problem:

n/a

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Concurrent Qual execution of Acquisition Method Report and Tune report fails

Problem:

n/a

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Acquisition should report fault when Injection volume is larger than syringe

Problem:

Changed syringe volume from 40ul to 8 ul in the configuration of the uWPS.
Left the method injection volume at 40 ul.
Save the method.
Reloaded the method per the warning mesage.
The method should now be bad for the injection volume since the syringe volume is 8 ul but the injection volume is 40 ul.

Saved method.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Isolated peak on RTD turns into triangle at the beginning of the tune

Problem:

If the user at the beginning of a tune zooms the right Real Time Display to a single peak, then at the beginning of a tune this peak turns into a 8 amu width triangle and transfered this way into the report.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

User needs to know correct input range for source parameters.

Problem:

Currently the user has no way of knowing what the correct input ranges are for the source parameters in Acquisition.

In Acquisition, enter 600 into the Gas Temp field and click <apply>

You get a message saying the MS QTOF tab has errors but the message does not tell you what the error is and how to correct it.

The message should be more specific and tell you the correct inpur range or there should be a right-click menu that displays the min/max/default values for that field.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Logbook does not capture "Lamp Ignition Failure" nor does it report a fault

Problem:

The user was starting a run with all the modules in standby or off.

When the VWD lamp was turned on, it failed to ignite. This error is captured and reported by ChemStation. However, it does not appear in either the VWD: Not Ready Text Long or the MassHunter Acquisition logbook. 

The VWD module icon turns RED but fails to report anything to the user.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

User should be prompted to disable FPS when manually performing Quad profiling

Problem:

With Fast Polarity Switching (FPS) enabled, the user switched to Manual Tune.  They then selected the Quad tab and started manually profiling the tune ions.  When they couldn't see any profile peaks, they realized they should have disabled FPS.  

The user should be prompted to disable FPS when they start to profile.

Temporary Solution:

The user should not perform Quad Profiling with Fast Polarity Switching enabled.

Fix Information:

n/a

Keyword: 

One-line Description:

Nozzle voltage cannot be shown in Actual Parameters

Problem:

Nozzle voltage for Agilent Jet Stream does not appear in the list for Parameters Actual for TOF QTOF, so it cannot be monitored.  All other parameters in the <source> tab appear in this list and so can be monitored as their value is changed during e.g., time segments.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Data Acquisition Baseline is offset after changing mode of operation

Problem:

Sometimes when an operator changes 1 GHz to 2 GHz, reverses polarity, or a high voltage arc over event occurs, the baseline is offset 600,000 counts or higher.  Occansionally, the baseline can be restored by changing mode of operation back and forward. (1 GHz- 2 GHz).

Temporary Solution:

The user must restart the Acquisition software and possibly the Q-TOF or TOF itself.

This will be address in a service release.

Fix Information:

n/a

Keyword: 

One-line Description:

No error message reported when out of range entry is made into TOF/Mass Range fields

Problem:

-go to manual tune
-select the TOF tab
-make an invalid entry in one of the mass range fields.

The field turns red but there is no error message that gives the valid range for the field.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Poor Error Message Description When Using Solvent Bottle Filling Feature

Problem:

The user activated the Solvent Bottle Filling monitoring for the 1290 solvent bottle.  When the bottle reached the level to trigger a fault and stop the analysis, the masshunter logbook only captured that the system did not inject due to system not ready during the 10 minute window. 

The only message reported was using the Ready State Description in the actuals window. It reported "Solvent A1". Nothing else was reported.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

The User Interface Freezes when acquisition computer HDD is Full.  Also, the HPLC Keeps Running.

Problem:

Unintentionally, a Worklist was started with not enough space remaining on the Acquisition computer fard drive. 

Upon reaching the limit of the hard drive, the User Interface froze.  This left the pumps of HPLC running.

Temporary Solution:

Customers are reminded to check the remaining hard drive space of the Acquisition computer before running a Worklist.

Fix Information:

n/a

Keyword: 

One-line Description:

Pause Between Tunes Checkbox Not Working With CheckTune

Problem:

Reported by a customer:

The Pause between tune checkbox does not work with Checktune. This feature is needed to obtain the best calibration.  This issue only happens with the Single AJS source. It appears to work with the Dual ESI source correctly.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

HPLC-Chip type cannot be defined in MassHunter Offline Method Editor

Problem:

There is no way to open the configuration User Interface of the HPLC Chip Cube in the Offline Method editor.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Open data file folder dialog is not consistent with normal explorer behaviour of sorting data file on basis of Name.

Problem:

Prerequisite: Create around 120 data file incrementally like WKL 1.d, WKL 2.d.....

1) Open MassHunter application.
2) Select worklist pane and open "Open data file" dialog from data file column.

Verify that sorted data is not according to normal behaviour of explorer where data is sorted properly however in "Open data file" dialog it is WKL 1.d, WKL 10.d, WKL 100.d.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Server Busy <Switch to>/<Retry> Message Displayed When LAN Cable Accidently Unplugged

Problem:

Inadvertently the LAN connection to the LC was disconnected while starting MassHunter. The error message "Server Busy" was displayed.

Temporary Solution:

Use the "Stop MassHunter Processes" tool to recover the system.

Fix Information:

n/a

Keyword: 

One-line Description:

Migration of a QTOF method to TOF resets parameters to default

Problem:

Migration of a QTOF method written on B.00.4 to a TOF with B.05.00 resets parameters to default values. 

This was found when a negative QTOF method would be reset to positive after the migration, an APCI method would be reset to default ESI.

Temporary Solution:

Users should carefully examine any migrated methods for incorrect set points.

Fix Information:

n/a

Keyword: 

One-line Description:

Spectral Parameters not Modifiable in Offline Method Editor

Problem:

Spectral acquisition rates and parameters are not adjustable in the offline method editor software.

Temporary Solution:

Modify spectral parameters in the online Acquisition software.

Fix Information:

n/a

Keyword: 

One-line Description:

Targeted MSMS "Time between spectra" setting being ignored after first instance in a method: MS spectra are always initial use value (in seconds) apart

Problem:

In Targeted MSMS Acquisition mode, whatever value for Max Time between MS1 spectra" is used and saved to a method will prevail over all other values set, regardless of input in new Targeted Methods if "Max Time between MS1 Spectra Is turned on".

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

35900E ADC Acquisition rate causes scaling issues with X-axis (time)

Problem:

QTOF Acquisition has a defect in recording ADC signals at various ADC acquisition rates. The signal is collected correctly - but recorded as a scalar multiple of the acquisition rate. For example, a 1 minute run at 10 Hz will be displayed over a 1 minute time period. The same method set to 20 Hz will display the same chromatogram over a 30 second time period.

Temporary Solution:

It is recommended that we use the UIB2 (universal interface box) as the analog to digital converter - which does not suffer from this problem but offers the same analog-to-digital functionality.

Fix Information:

n/a

Keyword: 

One-line Description:

Instrument communication error may cause Autotune or Worklist to fail.

Problem:

Instrument communication errors have been logged several times and against several releases. Because of the inconsistent nature of these errors, the defects are generally closed as "cannot reproduce".
When the communication error occurs, Autotune may fail or a Worklist or single sample acquisition may stop. The Software needs to be shut down, MassHunter engines restarted and on occasion the Instrument firmware rebooted.

Temporary Solution:

Report this error to Agilent personnel, especially if reproducible.

Fix Information:

n/a

Keyword: 

One-line Description:

TOF energy offset ramp in classic tune in 6530 does not ramp Octopole 2 DC.

Problem:

TOF energy offset ramp in classic tune in 6530 does not ramp Octopole 2 DC.

Temporary Solution:

Run SWARM tune

Fix Information:

n/a

Keyword: 

One-line Description:

AcquireCalibrantData and CalibrantOff scripts do not work for worklist parameters

Problem:

Done in method not worklist. Does not work as worklist parameter when multiple methods are used.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

MS1 Scans May Run Consecutively During In a Targeted MS/MS Method

Problem:

If 1000 or more lines are input in the Targeted Table of a Targeted MS/MS method, 2 MS1 scans may follow each other before MS2 is run.

Temporary Solution:

Shorten the targeted list below 1000 lines to assume normal behavior.

Fix Information:

n/a

Keyword: 

One-line Description:

Transmission Tune in Extended Mass Range Only Reports to 4000 m/z

Problem:

When the instrument is in the Extended Mass Range mode, the tune report for a Transmission Tune in either polarity will show a spectrum that is truncated at 4000 m/z. The true operating range of this mode is out to 10,000 m/z; the tune is still valid up to this value, despite the truncated window.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Iterative MS/MS Does Not Select Ions In Subsequent Injections If the Retention Time Difference Exceeds Threshold

Problem:

If an ion in an Iterative MS/MS run was previously selected, but is found in another injection outside of the retention time threshold, the Decision Engine should choose the ion for an MSMS scan. Currently, the ions that meet these criteria are not selected.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Mass Calibration/Check Tune Report  Displays Low Abundance for mz<600 with Multimode Source

Problem:

Mass Calibration/Check Tune Abundance Values with a Multimode source may report lower than that of a completed System Tune with an AJS Source. This is caused by the source parameters that are applied in each tune; a system tune will optimize source parameters for an AJS source, but the Mass Calibration/Check Tune will use a "Default" set of source parameters to be compatible with multiple sources. As a result, tune ion abundances may be lower when a Mass Calibration/Check Tune is run.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

The Isotope Grouper "Common Organic Molecules" Is Overridden to "Unknown" If too Many Isotopes are Assigned

Problem:

The isotope grouper "Common Organic Molcules" was not getting called if the number of peaks was higher than 8192.  This would lead to all peaks being assigned a charge state of "Unk".

Temporary Solution:

Decrease the number of isotope peaks to less than 8192.

Fix Information:

n/a

Keyword: 

One-line Description:

Worklist sample checkboxes disappear when columns are added using "Add Column" in UI

Problem:

When a column is added to the worklist table in the Acquisition Context, Worklist tab, the sample checkboxes disappear. The addition of new column actually causes a window navigation slider to appear at the bottom of the window, and you can view the checkboxes again by moving the slider to the right.

Temporary Solution:

Move the slider at the bottom of the page to navigate the worklist table.

Fix Information:

n/a

Keyword: 

One-line Description:

AgtVoyAcqEng.exe Will Crash If Method and Data File Name Are Too Long

Problem:

Users may experience "AgtVoyAcqEng.exe Has Stopped Working" error if both the method and data file name are too long. This includes the full path length.

Temporary Solution:

Shorten the method/ data file name or folder name in which they are saved.

Fix Information:

n/a