Software Status Bulletin
GC/MS Acquisition GC/MS Acquisition
Known Problem Report as of Mar 14 2017 10:27AM
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
KPR#:140
The Oven Ramp table does not display correctly in IR with Acquisition method selected.
KPR#:141
6890 PTV Inlet not recognizable in OpenLAB EZChrom
KPR#:142
Multiple errors when the 6890 doesn't have any inlets
KPR#:37
ALS Errors Abort Sequence; no Retry/Abort dialog box option offered
KPR#:107
New Abort Behavior
KPR#:126
The Override Column Max Temp Checkbox Behavior
KPR#:127
Cryo Trap Run Time Event Support
KPR#:174
GC Keypad Lock Behavior
KPR#:189
It is not possible to set a positive pressure when column outlet is set to "other"
KPR#:230
7820 Back Injector Only Resets Injection Source to Manual
KPR#:252
MMI in Split or Pulsed Split Mode does not allow editing of Total Flow value
KPR#:266
The GC Maintenance View May Not Change Until the Software is Closed and Re-Opened
KPR#:267
Description of How to Delete Columns from the Inventory
KPR#:268
Behavior of the Maintenance Screen When Adding Modules to the GC
KPR#:269
ALS Behavior When Aborting a Sequence
KPR#:270
7890B GC Column Maintenance Counter Behavior
KPR#:271
Update GC Column Catalog dialog is limited to 10 items; no way to display the rest (...)
KPR#:272
Method Differences Viewer Behavior with Scanned Columns
KPR#:273
7890B GC Method Compatibility
KPR#:274
Logbook Messages for Scanned Consumables Items
KPR#:275
The Syringe and Liner are Not Shown in the Method
KPR#:276
The PC and GC Clocks Need to be Synchronized to Account for Daylight Savings Time
KPR#:279
Explanation for How Default Early Maintenance Feedback Counters Work
KPR#:281
The 7890 GC Goes Offline When Non-English Characters are Entered into the Column Information
KPR#:284
Data not collected, sequence stopped when vial removed from turret after injection
KPR#:297
Agilent Solvent Elimination Wizard issue
KPR#:322
"Error accessing the OLE registry" appears when uninstalling the B.07.03 build which was upgraded fron B.07.02 (Build 1938)
KPR#:357
Inlet pressure setpoint displayed assuming all thermal zones are turned ON, results in confusing mismatch when heated zones are Off.
KPR#:360
Method Editor for PP inlet & Packed Column incorrectly allows both flow and pressure setpoints to be entered
Keyword: 68xx Driver
One-line Description:
The Oven Ramp table does not display correctly in IR with Acquisition method selected.
Problem:
When you specify an Intellignet Report with Method Info report added to the Sample Summary report to get the Acquisition method it is formatted incorrectly..
Temporary Solution:
n/a
Fix Information:
The rows in tables now have the same names and IDs so that the data system can organize them into a table. Fixed in revision 6.25 (GC Driver revision A.02.05).
Keyword: 68xx Driver
One-line Description:
6890 PTV Inlet not recognizable in OpenLAB EZChrom
Problem:
The Extracted configuration shows PTV back inlet and AIB Back Detector. Launching the instrument offline shows the column connected to the Back Inlet and the Back Detector.The Module Configuration Lists the PTV Back Inlet with Blank Back Detector, however the Back Inlet is seen as Unrecognized inlet type.
Temporary Solution:
n/a
Fix Information:
The code wasn't checking for the right inlet type code for a PTV mounted in the back. Fixed in revision 6.25
Keyword: 68xx Driver
One-line Description:
Multiple errors when the 6890 doesn't have any inlets
Problem:
The OpenLAB CDS ChemStation gives errors when the 6890 doesn't have inlets installed and both inlets are configured as none on the 6890 GC.
Temporary Solution:
n/a
Fix Information:
The error was occurring in the code which set up the possible inlet connections for columns. Fixed in revision 6.25
Keyword: 78xx Driver
One-line Description:
ALS Errors Abort Sequence; no Retry/Abort dialog box option offered
Problem:
The setting is selected by opening the Tray/Overlap tab in Method Editor. The Instrument Status must be opened to view the dialog box. Pause is the default setting for ChemStation and MassHunter. Skip is the default setting for EZChrom.
Temporary Solution:
n/a
Fix Information:
Fixed in the 5.01 Driver. This driver is included in: A.01.05 OpenLAB CDS B.07.00 MassHunter
Keyword: 78xx Driver
One-line Description:
GC Keypad Lock Behavior
Problem:
In configuration we now offer the option to configure how the keypad lock will behave.
Temporary Solution:
n/a
Fix Information:
The driver with this new behavior is included in: A.01.05 OpenLAB CDS B.07.00 MassHunter
Keyword: 78xx Driver
One-line Description:
New Abort Behavior
Problem:
Once it detected a vial not found, everything would abort, including samples that were in process (that have already been injected and are being analyzed). The new behavior, is that the vial that is currently being processed will be finished. Everything else will abort, if the abort option is selected.
Temporary Solution:
n/a
Fix Information:
Fixed in the 5.01 Driver. This driver is included in: A.01.05 OpenLAB CDS B.07.00 MassHunter
Keyword: 78xx Driver
One-line Description:
The Override Column Max Temp Checkbox Behavior
Problem:
The override column max temp checkbox in the oven parameter screen is automaticaly checked by default in versions of the driver prior to 5.01. In driver version 5.01, it will not be checked and the box will by highlighted in yellow if the column maximum temperature exceeds the value that is recommended for the column that is installed. To make the box not yellow, either check the "override column max temp" checkbox, or enter a value that is lower than the recommended maximum temperature for the installed column.
Temporary Solution:
n/a
Fix Information:
Change of Behavior in Driver Version 5.01 This driver is included in: A.01.05 OpenLAB CDS B.07.00 MassHunter
Keyword: 78xx Driver
One-line Description:
Cryo Trap Run Time Event Support
Problem:
When a thermal aux zone is configured as a Cryo Trap, the cooling of the trap is accomplished via a run time event entitled Cryo trap cooling with an ON an OFF state.
Temporary Solution:
n/a
Fix Information:
Fixed in the 5.01 Driver. This driver is included in: A.01.05 OpenLAB CDS B.07.00 MassHunter
Keyword: 78xx Driver
One-line Description:
It is not possible to set a positive pressure when column outlet is set to "other"
Problem:
If the colum is configured from one inlet to other (in case for a non-purged CFT or other applications) it's not possible to define the pressure of the outlet. It's possble to set it from the GC keyboard.
Temporary Solution:
n/a
Fix Information:
Fixed in the 5.01 Driver. This driver is included in: A.01.05 OpenLAB CDS B.07.00 MassHunter
Keyword: 78xx Driver
One-line Description:
7820 Back Injector Only Resets Injection Source to Manual
Problem:
On a 7820, with only a Back Injector Installed the following message is displayed when launching the 7820: Upon launching the 7820A, the following message appears: DEF_GC.M: 7820 Resetting to Manual injection. For method 'DEF_GC.M, injection source 'GC Injector' conflicts with injection location. This does not happen when there is only a Front Injector installed.
Temporary Solution:
Open the injection source and change it to GC Injector.
Fix Information:
Fixed in the 5.01 Driver. This driver is included in: A.01.05 OpenLAB CDS B.07.00 MassHunter
Keyword: 78xx Driver
One-line Description:
MMI in Split or Pulsed Split Mode does not allow editing of Total Flow value
Problem:
MMI in Split or Pulsed Split Mode does not allow editing of Total Flow value. The Total Flow combo box is active, but any entry made there reverts to its original entry.
Temporary Solution:
Total Flow is editable in this mode from the GC keypad in driver versions prior to 5.01.
Fix Information:
Fixed in the 5.01 Driver. This driver is included in: A.01.05 OpenLAB CDS B.07.00 MassHunter
Keyword: 78xx Driver
One-line Description:
The Syringe and Liner are Not Shown in the Method
Problem:
The syringe and liner not shown in method. This is expected behavior for the 5.01 GC driver that is included in the C.01.05 OpenLAB CDS and B.07.00 MassHunter.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: 78xx Driver
One-line Description:
The GC Maintenance View May Not Change Until the Software is Closed and Re-Opened
Problem:
The Maintenance View May Not Change Until Software is Closed and Re-Opened
Temporary Solution:
In the Maintenance menu, the user has the option to change the view of the menu by changing it under the Options button. Sometimes the change may not go into effect until the software is closed and re-opened.
Fix Information:
n/a
Keyword: 78xx Driver
One-line Description:
Description of How to Delete Columns from the Inventory
Problem:
Editing can only take place in the catalog file and you can edit both the inventory data and the catalog data. For an inventory item, you can edit the actual length and the comments. For a catalog item, you can edit the keywords, comments, and check/uncheck favorites. You can only delete from the catalog, this is where you delete your items from inventory. You can remove a column or an inventory item by clicking on the minus sign in the navigation bar.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: 78xx Driver
One-line Description:
Behavior of the Maintenance Screen When Adding Modules to the GC
Problem:
You will not see the module ID that is installed, but the module location will be identified If you add a back injector, the back injector tab will come up and all relevant counters will show. The module ID will not be shown. To make it show up, you have to close the data system and reopen the datasystem.
Temporary Solution:
Add hardware modules when the hardware is turned off and the data system is disconnected.
Fix Information:
n/a
Keyword: 78xx Driver
One-line Description:
Explanation for How Default Early Maintenance Feedback Counters Work
Problem:
When "set default recommended values for limits" is selected for the first time, and if those values are not changed, the Maintenance window needs to be closed and re-opened for the values to take effect.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: 78xx Driver
One-line Description:
ALS Behavior When Aborting a Sequence
Problem:
If a sequence is aborted in the middle of a sequence, the vial will be left in the turret until the next run is started. At that time, it will be put back in the tray.
Temporary Solution:
This is expected behavior.
Fix Information:
n/a
Keyword: 78xx Driver
One-line Description:
7890B GC Column Maintenance Counter Behavior
Problem:
If you move a column from one GC to another that is using a different database, you will not see the current Maintenace Counters for the column. If you return the column to the original GC, it will have the old values.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: 78xx Driver
One-line Description:
Update GC Column Catalog dialog is limited to 10 items; no way to display the rest (...)
Problem:
Update Column Catalog dialog is limited to 10 items; no way to display the rest (...) When you view the catalog, all items will appear.
Temporary Solution:
Description of behavior in driver version 5.01: when you view the catalog, all items will appear.
Fix Information:
n/a
Keyword: 78xx Driver
One-line Description:
Method Differences Viewer Behavior with Scanned Columns
Problem:
When you scan a column in to the GC when you are not connected to the datasystem, and you connect with the data system, you will see differences in your method viewer upon opening the data system. The change will not be shown in highlight differences. No matter what is selected, the column that was scanned into the GC will be the column that is configured.
Temporary Solution:
Scan the column in with the data system connected.
Fix Information:
n/a
Keyword: 78xx Driver
One-line Description:
7890B GC Method Compatibility
Problem:
The7890B GC driver included in the new data systems (A.01.05 OpenLAB CDS and B.07.00 MassHunter) supports up to 12 valves. The GC driver in previous data systems only reported 8 valves. Because of this difference, you cannot develop a method on a new data system and run it on an old data sytem. You can take a method loaded on an old data system and run it on the new data system. If you try to load a new data system method on an old data system, the behavior that you will see is that after starting a run, the software and the GC just sit there waiting for prerun to start, but nothing happens.
Temporary Solution:
n/a
Fix Information:
Documented Behavior for GC Methods Developed Using A.01.05 OpenLAB CDS and B.07.00 MassHunter.
Keyword: 78xx Driver
One-line Description:
Logbook Messages for Scanned Consumables Items
Problem:
There is no logbook message about scanned consumables or reset of Maintenance Counter values if the consumable is scanned when the Data System is Offline.
Temporary Solution:
In order for the logbook to capture messages about the scanned consumables or reset of Maintenance Counter values, make sure the Data System is connected when scanning the barcode of the consumable.
Fix Information:
n/a
Keyword: 78xx Driver
One-line Description:
The PC and GC Clocks Need to be Synchronized to Account for Daylight Savings Time
Problem:
For the resource conservation feature, the GC and PC clocks need to be set to the same time(synchronized). After daylight savings time, make sure the GC and PC clocks are synchronized by pressing the synchronize clocks button, which is available from the configuration screen and from the maintenance screen. The times will not be synchronized automatically.
Temporary Solution:
Synchronize the clocks by opening the Maintenance Window, select the Maintenance Actions tab and synchronize the clocks.
Fix Information:
n/a
Keyword: 78xx Driver
One-line Description:
The 7890 GC Goes Offline When Non-English Characters are Entered into the Column Information
Problem:
The 7890 GC goes offline when non-english characters are entered into the column information screen. The issue has to do with the number of characters that the column description accepts.
Temporary Solution:
If non-english text is entered in the column information field and the GC can not connect to the data system, reboot the GC by holding the clear button down. Do not enter the column information in non-english text.
Fix Information:
n/a
Keyword: 78xx Driver
One-line Description:
Data not collected, sequence stopped when vial removed from turret after injection
Problem:
After the sample was injected, the vial was removed from the turrett. The tray showed an error and the log file reported that there was no vial in gripper. The Sequence was stopped when the vial was removed and the data was not collected.
Temporary Solution:
n/a
Fix Information:
Fixed in driver 5.03.
Keyword: 78xx Driver
One-line Description:
Agilent Solvent Elimination Wizard issue
Problem:
When select Solvent Vent mode in MMI, select 10uL syringe and Injection Volume 5uL in Solvent Elimination Calculator on first window. In second window, injected volume 5uL is out of the range. Because the range is 0.01-0.25uL. This is solvent elimination calculator issue.
Temporary Solution:
n/a
Fix Information:
Fixed in revision 5.05
Keyword: 78xx Driver
One-line Description:
"Error accessing the OLE registry" appears when uninstalling the B.07.03 build which was upgraded fron B.07.02 (Build 1938)
Problem:
"Error accessing the OLE registry" happens when uninstalling the GC driver that was upgraded on MassHunter Acquisition version B.07.02 in uninstalled. This is a problem with the installer.
Temporary Solution:
Do not uninstall the upgraded GC driver. The error happens with GC Driver version A.03.01.51 or greater.
Fix Information:
No fix at this time.
Keyword:
One-line Description:
Not allowed to set proper GC column max temp because it is less than 150degrees.
Problem:
Problem when a column has the following restrictions: The maximum allowable operating temperature Isothermal: 130 °C The maximum allowable operating temperature Programmed: 150 °C When they want to enter this number in this configuration the field becomes yellow. This value can can't be entered in the field due to value limitations of related field. Maximum value should be in the range of 150 ≤ °C ≤ 450.
Temporary Solution:
n/a
Fix Information:
Fixed in B.01.01
Keyword:
One-line Description:
Cannot Add User-Defined EMFs on Intuvo 9000 GC
Problem:
Unable to created a user defined EMF Intuvo 9000 GC. Enter a name and tracking type, but nothing appears on the User-defined panel or any other panel. There are five user defined (seemingly blank) entries on that panel.
Temporary Solution:
none
Fix Information:
To Be fixed in B.01.02
Keyword:
One-line Description:
The column flow calculator calculation is off by almost 3x the flow rate for the system
Problem:
The values which are setup for the column and the flow rates which were entered. The problem is when you look at the GC for the values they don't match the column flow calculator.
Temporary Solution:
n/a
Fix Information:
Fixed in B.01.01
Keyword:
One-line Description:
Method print is showing Solvent wash mode as A-A2, B-B2 when it should be A,B since it is a 16 vial turret
Problem:
Intuvo 9000 with a ALS and a 16 vial turret. MassHunter software, the configuration of the ALS is set to Solvent Wash Mode A,B. Saved and printed the method. Solvent Was Mode on the method print shows A-A2, B-B2.
Temporary Solution:
none
Fix Information:
to be resolved in B.01.02
Keyword: 78xx Driver
One-line Description:
Inlet pressure setpoint displayed assuming all thermal zones are turned ON, results in confusing mismatch when heated zones are Off.
Problem:
CDS displays inlet pressure setpoint assuming all thermal zones are turned ON, results in confusing mismatch when heated zones are Off.
Temporary Solution:
none
Fix Information:
To be resolved in B.01.02
Keyword:
One-line Description:
Error Unhandled Exception when changing columns and a Gerstel CIS4 in installed in the 7890.
Problem:
If e a Gerstel CIS4 installed and the columns is reconfigured, a msinctl error occurs and the MassHunter software shuts down.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: 78xx Driver
One-line Description:
Method Editor for PP inlet & Packed Column incorrectly allows both flow and pressure setpoints to be entered
Problem:
When in flow mode, pressure should not be allowed. Entering a value messes up the flow setpoint. When in pressure mode, flow should not be allowed. Entering a value messes up the pressure setpoint.
Temporary Solution:
Workaround is to only enter the appropriate setpoint.
Fix Information:
To be resolved in B.01.02
Keyword:
One-line Description:
QQQ: Exception occurred when closing GC/MS Acquisition
Problem:
This error occurs infrequently and is very random.
Temporary Solution:
Continue past the exception, nothing serious has happened.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: If a GC 7890 is already in use, the identity of the first user is not reported to the second user
Problem:
This problem only affects users in the remote connection situation. I tried to start an instrument while another PC was already running the GC that my instrument is configured with. An error message showed "ChemStation can not finish its initialization cycle". Opening the log, the log stated the GC is offline, but not who is using it.
Temporary Solution:
Do not connect to a GC that another PC is already connected to.
Fix Information:
Has been resolved in B.04.01
Keyword:
One-line Description:
QQQ: Wrong data file shown on System UI after "Pause" was used on the sequence
Problem:
When a sequence is paused, it appears that the wrong data file name is displayed next to the vial icon on the user interface.
Temporary Solution:
This is the designed behavior. UNLESS a SEQUENCE is running, the displayed data file name AND the loaded method will ALWAYS be the 'Run Method' CP variables. When a sequence is run, the current value of DATAFILE$ is saved. Whether the sequence is paused or is allowed to complete normally, the previously saved DATAFILE$ value is restored upon completion or pause. Since the Vial picture panel has the displayed data file name mapped to the variable DATAFILE$, the file name displayed in the panel will revert to that value when the sequence is complete or paused. This saving and restoring is accomplished as part of the Sequence Macro Machine.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: When hovering the mouse over the icons no assisting info is shown
Problem:
When I put the mouse over the icons on the Instrument Control panel, no assisting info is shown either on left bottom corner of the window or on top of the icon.
Temporary Solution:
Read the online help.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: When the sample type is Keyword, auto fill/increment should skip that sample
Problem:
In the sequence table, when the sample type is "Keyword", auto fill/increment is meaningless for many columns. So auto fill/increment should skip the samples with a type "Keyword"
Temporary Solution:
n/a
Fix Information:
Resolved in released version B.04.01 as "User Misunderstanding"
Keyword:
One-line Description:
QQQ: Error message can be more detailed when error occurs while importing Sequence Table from XML
Problem:
When importing a Sequence Table from a XML file created from the SequenceTableAssistant, if some file contains an item in a wrong format, there is error message on the status line, and importing stops. Anything after the line in a wrong format is chopped. This is expected behavior. However, it would be better to show a more detailed error message in the status line, such as on which line and column this error happened. It would be easier for the user to then locate the error.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Any directory can be selected and then filled into the Method File field in Sequence Table Editor
Problem:
In the Sequence Table Editor, using the Browse button to select method, any arbitrary directory can be selected and then filled into the Method File column. Preferably, only .m should be allowed.
Temporary Solution:
Only select .m directories.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Inconsistent information in sequence.log with Sequence Table Editor
Problem:
In Sequence Table Editor, load a method from ...GCMS\1\METHODS using Browse button, and then run sequence simulation. The verification result show that the method path is ...GCMS\2\METHODS.
Temporary Solution:
The default paths are related to where the initial method was loaded from in the default instrument control panel.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Edit Entire Method Missing from Method Menu
Problem:
There is no menu item (or icon) that sequentially presents all the edit method panels to the user.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Logbook doesn't provide error information on invalid vial number
Problem:
If the Sequence Table contains invalid vial information, the sequence will hang or abort at the problem line. Status line shows that an error has occurred, but no error information is given in the logbook. In one case, the logbook stated all data was acquired.
Temporary Solution:
n/a
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: Qualitative Analysis method cannot be selected by Browse button in Sequence Table Editor
Problem:
In DA method file of Sequence Table Editor, Qualitative Analysis method (.m folder) cannot be selected by the browse button. Only files can be selected (default file is .quantmethod., other format is supported too).
Temporary Solution:
User can type in the full name of the Qualitative Analysis method with the '.m' suffix and this will work.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Logbook and Printer Icons Always Look Grayed Out
Problem:
The Logbook and Printer Icons are the same color as grayed-out icons. They are still accessible but it is confusing to tell if they are active just be looking at them.
Temporary Solution:
Logbook and Printer icons are indeed always active.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Launching Qualitative Analysis causes Sequence Table Editor layout to disappear
Problem:
Steps to reproduce: 1) Start GC/MS Acquisition, open the Sequence Table Editor, and add some columns. Save them to a layout (for easy retrieval). OK the panel. 2) Run Qualitative Analysis. 3) Go back to GC/MS Acquisition, and open the Sequence Table Editor again, it has now reverted to 'default' layout.
Temporary Solution:
Do not use Qualitative Analysis while editing the Sequence Table.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: 7693A Injector Panel in Method Editor Needs Scroll Bar
Problem:
After installing the new driver (25), it seemed as though the 7693A Injection Types section was missing from the panel. The window get sized a certain way and it looks like the panel is complete.
Temporary Solution:
One needs to stretch the panel in order see the additional parameters. A scroll bar should be added to this panel so the users know the parameters are there. Full feature support for the 7693 will not be supported on the initial release of B.04.00
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: PAL: In the Sequence Table editor, the "Tray Name" column does not have a selection list
Problem:
The user must enter the tray name manually in the column. The name is case-sensitive and must match exactly with one of the names in the Location Map. Otherwise, the vial will not be found.
Temporary Solution:
Click the "Instrument->CTC PAL Show Location Mapping..." menu item to display the Location Map. Note the tray name to be used. Close the Location Map and open the Sequence Table. Type in the tray name exactly for each entry in the table. If the same tray is used for multiple samples in the sequence table, the "fill-down" feature can be used to duplicate the name in the rows below the current entry.
Fix Information:
Has been fixed in MassHunter GCMS Acquisition B.05.02.
Keyword:
One-line Description:
QQQ: Where is Injection Volume field in Sequence Table?
Problem:
Is there an injection volume field configurable in the sample log table. The only available field seemed to be Vol. Does this mean injection volume? If so, it should state injection volume and not be abbreviated.
Temporary Solution:
Yes, "Vol." does in fact mean injection volume.
Fix Information:
Resolved in released version B.04.00 as "User Misunderstanding"
Keyword:
One-line Description:
QQQ: PAL: CTC PAL - Problems if a vial is not found during the sequence
Problem:
If a vial is not found when running a sequence with the CTC PAL, the sequence stops and appropriate messages are logged in the sequence log file as well as the log book. Although everything appears to be fine, there may be problems when starting the next run. The next run may hang and the program crash when the run is aborted.
Temporary Solution:
When the "No vial found ..." message is displayed, do not start a 2nd run. Close and restart the application. Correct the vial location in the Sequence Table or move the vial to the right location. If the error persists, do the following: · If GC/MS Acquisition is still running, close it · In the Windows Task Manager, Process tab, end the following processes if they are listed: msinsctl.exe CTCPalPlus.exe CTCPAL~1.exe (you end these processes by right-clicking on them, then clicking on "End Process") · Power cycle the GC 7890 · Power cycle the CTC PAL · Restart GC/MS Acquisition In some situations, if the above does not fully correct the problem, you should reboot your PC.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: Always Says User Aborted Run Even If an Error Occurred
Problem:
The logbook always says User aborted run after it lists the correct error. User aborted run should only be used when the user stops the run from the software. For example, if an ALS injector error occurs, the logbook should not say the user aborted run.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: No way to create a dual injection sequence
Problem:
Method setup allows method specified with dual injection. There is no way however, in the sequence to set up a dual injection sequence.
Temporary Solution:
Do not run dual injection in the B.04.00 release.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: MS Connected To... on Start Run Panel Does Not Save the "Rear" option for Valve
Problem:
When Valve is selected as the Injection Source, one can change the MS Connect to section from front to rear. On this system, the MS is physically connected in the rear, but it would not save that option. This does not happen with the ALS.
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.05.01
Keyword:
One-line Description:
QQQ: Msinsctl.exe crashes when Solvent Elimination Calculator Button is selected on MMI
Problem:
Selected the Solvent Elimination Calculator button on the MMI (PTV2) Inlet panel. GC/MS Acquisition immediately stopped working.
Temporary Solution:
Don’t select that button.
Fix Information:
Fixed in the B.04.00 release.
Keyword:
One-line Description:
PAL - Invalid injection volume in the sequence
Problem:
Added Vol. column to the sample log table. During the sequence setup, specified an invalid volume for the first sample. OK'd panel and started sequence. The sequence started, but I got the following error "Term used is invalid. Please check injection volume and syringe." OK message. The sample goes into postrun and the software crashes. It also leaves the GC in a funny state. If I try to start back up the software, received message that "an attempt to download settings to the GC was blocked because the driver is in the wrong state". I had to reboot the GC too.
Temporary Solution:
Type in the an valid injection volume.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ: PAL - System crashes when trying to run a CTC-PAL method with the wrong syringe
Problem:
The run behavior is unpredictable when the syringe installed does not match the syringe specified in the method.
Temporary Solution:
Specify correct syringe. Make sure that the cycle and syringe selected in the CTC Method Edit panel matches the syringe installed.
Fix Information:
Fixed in released version B.05.02
Keyword:
One-line Description:
QQQ: Cal EI Val On-Off in Time Events does not work
Problem:
In the QQQ Method Editor, Cal EI Val On-Off in Time Events does not work.
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.05.01
Keyword:
One-line Description:
QQQ: Dual injection method not working properly
Problem:
Dual injection sequence is not supported; however the software allows you to specify a dual injection method. Sample is injected into both the front and rear inlets when the method is run. Two data files are created, however the rear data file does not contain an AcqData directory.
Temporary Solution:
Do not run dual injection in the B.04.00 release.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: PAL: CTC does not come online
Problem:
The following message was displayed at startup when there was a bad RS232 connector: "CTC connection problem. Exit and reboot CTC/PC if this persists."
Temporary Solution:
If this error is encountered, replace or clean the connector. If replacing or cleaning the connector does not fully correct the problem, do the following: · If GC/MS Acquisition is still running, close it · In the Windows Task Manager, Process tab, end the following processes if they are listed: msinsctl.exe CTCPalPlus.exe CTCPAL~1.exe (you end these processes by right-clicking on them, then clicking on “End Process”) · Power cycle the GC 7890 · Power cycle the CTC PAL · Run the PAL Loader program and click "Info". If that was successful, click "Start PAL", the PAL should move. If that was not successful, then power cycle the PAL. · Restart GC/MS Acquisition to make another connection. The CTC status panel will show "Ready" if there is a good connection. In some situations, if the above does not fully correct the problem, you should reboot your PC.
Fix Information:
Resolved in released version B.04.00 as "User Misunderstanding"
Keyword:
One-line Description:
QQQ: Pre and Post run programs don't run macro listed under Data Analysis
Problem:
Tried to run a method with macros specified in Pre and Post Run Programs. If the macro is specified under Instrument Control, it works correctly. Macros specified under Data Analysis however, do not work.
Temporary Solution:
Yes, this behavior was changed to ONLY RUN A [MassHunter Qualitative Analysis or MassHunter Quantitative Analysis] SCRIPT if MassHunter is being used.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: EM Voltage is not being shown in MS monitor
Problem:
EM voltage is not one of the available MS monitors to be displayed.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Not displaying the value of EM when selecting Gain Factor in QQQ Method Editor
Problem:
There is no indication of the actual EM value corresponding to the specified Gain Factor setting. It would help the user to know if the EM has reached the 3000 V limit or how much of a range is still possible.
Temporary Solution:
n/a
Fix Information:
Calculated value will be shown in Method Editor. Tune report will print out maximum gain which could be used on the system based on the EMV usage. Fixed items are in the MassHunter GC/MS Acquisition B.05.00 release version.
Keyword:
One-line Description:
QQQ: "New Method from Acquired Scan Data" displayed "MS1 Scan" as "MS2 Scan"
Problem:
Acquired data file with "MS1 Scan" but the "New Method from Acquired Scan Data" displays it as "MS2 Scan" data.
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.05.00
Keyword:
One-line Description:
QQQ: Unhandled Exception on Fr or Bck Inj panel after selection overlap option 2.
Problem:
Selected the second overlap option and then selected one of the injector panels. An unhandled exception error may occur.
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.04.00
Keyword:
One-line Description:
QQQ: GCMS Configuation Editor doesn't change QQQ quad polarity
Problem:
Although the configuration editor does update the msdchem.ini file, the settings from this file are not used to control the quad polarity.
Temporary Solution:
For the MS 7000A QQQ, ignore the quad polarity in the Configuration Editor since it doesn't have any effect on the actual quad polarity. Currently, the Agilent CE will ensure that the correct quad polarity and settings will be used, even after a firmware update.
Fix Information:
In the B.04.01 release, the quad polarity settings are grayed out in the configuration editor.
Keyword:
One-line Description:
QQQ: Allowed values on Plunger Speed are not consistent with the setting ranges
Problem:
On GC configuration panel, select "Variable" in Plunger Speed Some values can be saved, while some values cannot be saved, although all of them are within the allowed range.
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.04.01
Keyword:
One-line Description:
QQQ: Lag factor coefficients are cleared by reinstalling or reconfiguring the system
Problem:
Autotune sets the lag factor coefficients. Reconfiguring the 7000A will clear the lag factors.
Temporary Solution:
Any time the 7000A is reconfigured an Autotune is required.
Fix Information:
Fixed in revision B.05.01
Keyword:
One-line Description:
QQQ: Incorrect error message starting application when trying to connect to a GC in use by another user
Problem:
If user B tries to start GC/MS Acquisition configured with an instrument that is currently in use by user A, an error message appears during launching process: "The method is Invalid. Method must be uploaded from GC first". This is not a correct message.
Temporary Solution:
Don't try to start GC/MS Acquisition for a GC or MS instrument already in use.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: PAL: CTC-PAL shows incorrect behavior on Stop request.
Problem:
When the user clicks the stop button and the CTC-PAL is still active, the acquisition subsystem does not handle that STOP request properly.
Temporary Solution:
Do not hit the stop button.
Fix Information:
Has been fixed in MassHunter GCMS Acquisition B.05.02.
Keyword:
One-line Description:
QQQ: Irrelevant message is displayed during startup or loading of method in an offline session
Problem:
The following scenario may occur in an "offline" session of Mass Hunter GC/MS Data Acquisition when a GC 7890 is configured. When the session is started or a method is loaded, the following message may be displayed: "Method is invalid. Method must be uploaded from the GC first." After the user clicks OK, the method resolution window is displayed. The message and method resolution is not relevant for an offline session.
Temporary Solution:
Click OK on the message box and the method resolution panel, then save the method. The next time the method is loaded or the session is started with this method, the error message will not be displayed.
Fix Information:
Fixed in revision B.04.00
Keyword:
One-line Description:
QQQ: Help Does Not Include Direct Injection
Problem:
The help topic for the MMI does not talk about Direct Injection Mode, which is listed in the software drop-down Mode list.
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.05.00
Keyword:
One-line Description:
QQQ: Help Says that MMI Can Only Configure 3 Ramps
Problem:
The help topic for the MMI says that up to three ramps can be programmed, but 10 ramps can be programmed for the inlet.
Temporary Solution:
Ignore this part of the help.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Instrument control window pops up and then goes behind previously open window
Problem:
When starting the MassHunter GC/MS Acquisition program, the application will pop up on top of the last window which was being worked on. After the application finishes initialization, then the instrument control window goes behind the last window.
Temporary Solution:
Rearrange your windows on the screen to see the application.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: PAL: Occasional error when updating CTC PAL Configuration
Problem:
After clicking on the "CTC PAL Update Configuration" menu item, you see a "Trouble with download" error message.
Temporary Solution:
This seems to be an intermittent problem, so the first thing to try is just click on the menu item again. If the problem persists, close GC/MS Acquisition and restart it. The problem is then very unlikely to reoccur.
Fix Information:
Resolved in released version B.04.00 as "User Misunderstanding"
Keyword:
One-line Description:
QQQ: Problems When Stopping a Sequence with Overlapped Injections (7693 ALS)
Problem:
While running a three-line sequence, my Method was set to enable overlapped injections using the first option to obtain the next vial after the previous injection. On the first sample, after the injection was made but before the vial was returned, I selected Stop. Sequence went to line 2 but "Waiting for GC Ready" appeared even though the GC had no parameters that were not ready. Then I selected Override, but the GC seemed to be waiting for prep run. Then I selected Prep Run on the GC and it went ready. The software went into PreRun but did nothing. The status line said "loading vial". Then I selected Stop again, and the software crashed (msinsctl.exe has stopped working). I tried this scenario again but selected Pause/Stop at the end -- the sequence aborted. If the Pause/Stop is done after the overlap preps the vial, it seems to be OK and will just inject when you resume the sequence.
Temporary Solution:
1) Press the stop button on the GC front panel to force it into the idle state 2) Restart the MassHunter GCMS Acquisition software 3) Avoid aborting the sequence/run while the GC is in Pre-Run and/or the autosampler is moving. 4) Do not Stop during sequence run when Overlap Injection is selected on 7693 Autosampler.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Missing Devices.xml when running a method on 7693A Series
Problem:
Check "Data Analysis" when running a method with 7693A injector, the following message appears after the data was acquired: "Opening data file failed with error - File not found: D:\MassHunter\GCMS\1\Data\GC105_001.d\AcqData\Devices.xml"
Temporary Solution:
This "defect" was caused by not including a GC detector in the method. After adding the GC Oven Actual Temperature as a signal source, the file Devices.xml was created.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Cannot use Bar Code Reader to read barcode directly into Sequence Table
Problem:
Edit Sequence Table does not have the ability to read the Barcode label directly into the Expected Barcode field.
Temporary Solution:
Enter expected barcode value manually.
Fix Information:
Fixed in revision B.05.02
Keyword:
One-line Description:
QQQ: MassHunter Acquisition needs help edited to reflect changes to 7693/4515A BCR
Problem:
Somewhere in the Help, the changes to how the G4512A barcode reader works needs to be added.
Temporary Solution:
To disable the barcode reader in MassHunter Acquisition, the user must enter the stringin the Expected Barcode field in the sequence table for a run sequence or the Start Run panel for a run method. If this string is not entered, the barcorde reader will always be used.
Fix Information:
New feature has been added to the Run Sequence Panel which the user can disable the use of the BCR from all samples. Resolved in version B.05.00
Keyword:
One-line Description:
QQQ: The "Data File Directory" value entered in the "Start Sequence" dialog was ignored
Problem:
The "Data File Directory" value entered in the "Start Sequence" dialog was ignored when I expected it to be used.
Temporary Solution:
The Sequence Table contents override the Start Sequence panel; if one wants to use the Start Sequence dialog, then leave that column blank in the Sequence Table.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Application hangs if the GC goes into Shutdown like the Inlet flow shutdown.
Problem:
Application hangs if the GC goes into Shutdown like the Inlet flow shutdown. When the GC Shutdown, the GC must be rebooted or it will stay in a locked state.
Temporary Solution:
When the GC goes into a Shutdown state, the Workstation must be closed because the GC must be powered cycle to recover.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: PAL: Initialization of the CTC-PAL could fail/lockup the system depending on the GC
Problem:
If the GC and the CTC-PAL system are left in a bad state (improper shutdowns) it is possible when the CTC-PAL next starts communicating with the GC, the two instruments could freeze/fail/lockup.
Temporary Solution:
When this occurs, one should close and then restart GC/MS Acquisition. This is the easiest solution when this occurs. If the problem persists, do the following: · If GC/MS Acquisition is still running, close it · In the Windows Task Manager, Process tab, end the following processes if they are listed: msinsctl.exe CTCPalPlus.exe CTCPAL~1.exe (you end these processes by right-clicking on them, then clicking on "End Process") · Turn off power to MS 7000A, GC 7890, CTC PAL, LAN Switch and printer · Wait at least 1 minute · Turn on power to MS 7000A, GC 7890, CTC PAL, LAN Switch and printer · Restart GC/MS Acquisition In some situations, if the above does not fully correct the problem, you should reboot your PC and again power cycle the instruments.
Fix Information:
Was resolved in B.07.00
Keyword:
One-line Description:
QQQ: PAL: CTC PAL Controller Is Not Started Error
Problem:
On rare occasions, the user may encounter the following error, "Controller is not started", when running a method with the CTC PAL. Stopping the run at that point may cause the system to crash.
Temporary Solution:
If the error does happen, do the following: · If GC/MS Acquisition is still running, close it · In the Windows Task Manager, Process tab, end the following processes if they are listed: msinsctl.exe CTCPalPlus.exe CTCPAL~1.exe (you end these processes by right-clicking on them, then clicking on "End Process") · Power cycle the GC 7890 · Power cycle the CTC PAL · Restart GC/MS Acquisition In some situations, if the above does not fully correct the problem, you should reboot your PC.
Fix Information:
Has been fixed in B.05.01
Keyword:
One-line Description:
QQQ: Excessively long sequence and tune filenames can be generated in certain cases
Problem:
Filenames can get long although the name does still function correctly.
Filenames entered in the following forms result in the final filename indicated:
XXXXX XXXXX.sequence.xml (correct)
XXXXX.sequence.xml XXXXX.sequence.xml (correct)
XXXXX.xml XXXXX.sequence.xml (correct)
XXXXX.sequence XXXXX.sequence.sequence.xml (wrong!)
The fourth style is unlikely to be entered by a user, unless they have file extensions hidden. And even then only if they just change the displayed "YYYY.sequence" to literally "XXXX.sequence". If they do the more normal change
Temporary Solution:
Excessively long sequence and tune filenames can be generated.
In certain cases, especially if the user has file extensions for known file types hidden in Explorer, filenames like the following can be generated during a "Save As..." --
something.sequence.sequence.sequence.xml
This *only* happens when the filename is entered in the Save As... dialog in exactly this form:
something.sequence
Workaround: don't enter a filename in the form:
something.sequence
just enter it as either:
something (in which case .sequence.xml will be appended)
or
something.sequence.xml (in which case you are all set)
Same thing for tune files.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: "Continuous GC Real-Time Plot" checkbox is not functional
Problem:
In the "Real-Time Plots for GC 7890" dialog box, there is a "Continuous GC Real-Time Plot" check box. The GC Real-Time Plots are continuous regardless whether the box is checked or not.
Temporary Solution:
n/a
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: "Set MS System Pressure Units" does not work
Problem:
In the Agilent GC/MS Instrument Configuration panel, the user can select the "Configure" menu and then the "Set MS System Pressure Units" menu item to select the pressure units for vacuum readings. Although there are multiple options for pressure units, the software is not making use of these settings. In the MS monitors, Manual Tune User Interface, and the LCP, the values are displayed in "Torr".
Temporary Solution:
Use Torr as units.
Fix Information:
Fixed in revision B.05.01
Keyword:
One-line Description:
QQQ: House LAN could cause about 2.5 min delay for GC/MS Acquisition to start up
Problem:
When the House network is used together the MS network, the GC/MS Acquisition program starts with a delay around of 2.5 min.
Temporary Solution:
If the system uses the MS network with the House network disabled or without cable or with enabled access to Internet, then GC/MS Data Acquisition starts immediately after the double click on the icon.
Fix Information:
Also refer to entry KPR 229
Keyword:
One-line Description:
QQQ: House LAN causes about 1-1.5 min delay for MassHunter quant to start up.
Problem:
Masshunter Quant: when the House network is used together the MS network the Quant program starts with a delay around of 1-1.5 min. If the House network disabled or without cable or with enabled access to Internet the Acquisition start immediately after the double click on the icon.
Temporary Solution:
Investigation of the issue at Customer site showed by checking the firewall that the PC after the double click of the icon tries to reach on Internet IP starting on the network 199.7.xxx.xxx, some IP found are 199.7.52.190, 199.7.71.190, 199.7.50.72 and 199.7.48.190, from this IP I found ftp site with some software certificate (VeriSign Global Registry Services)
Fix Information:
Has been fixed in MassHunter GCMS Acquisition B.05.02.
Keyword:
One-line Description:
QQQ: TIME stamp of a method change is not printed when you print the acq method..
Problem:
The current contents of print-out of "Print the acq method" provide the detail information about method settings in GC and MS, but not include the information about the method-change history. The file of method.txt for method-change history should be as one option for printing the acr method
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
QQQ: PAL: Sample overlap selection is not loaded with the method
Problem:
Sometimes, the "Set Up Injector Overlap" panel fails to display the current method settings. Although the panel had saved the settings correctly from a previous edit session, the panel will show incorrect settings.
Temporary Solution:
1. To read the overlap setting in a method, go to the method directory (for example, D:\massHunter\GCMS\1\methods\HS.m), open the ctc.mth file and look at the Parameters section. [Parameters] Volume=300.00 Overlap=1 Delay=60 Overlap = 1 means overlap is enabled, 0 means disabled Delay= 60 means 60 seconds, so divide this by 60 to get time the value that was entered into the "mins after full completion of the CTC PAL cycle" field in the "Set Up Injector Overlap" panel. 2. To change the overlap setting, edit the ctc.mth file following the example in the parameters section shown above. Save the file. Load the method.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: PAL: Error editing CTC PAL method
Problem:
After editing a CTC Pal method, an "unknown error" error message appears after clicking on OK. This is caused by the CTC previously not correctly handling stopping a run in Pre-Run before GC/MS/CTC are still "Not Ready".
Temporary Solution:
If the error does happen, do the following: · If GC/MS Acquisition is still running, close it · In the Windows Task Manager, Process tab, end the following processes if they are listed: msinsctl.exe CTCPalPlus.exe CTCPAL~1.exe (you end these processes by right-clicking on them, then clicking on "End Process") · Power cycle the GC 7890 · Power cycle the CTC PAL · Restart GC/MS Acquisition In some situations, if the above does not fully correct the problem, you should reboot your PC. To avoid the problem in the first place, do not stop the run while the GC/MS/CTC are still "Not ready" in PreRun. If you want to stop a run in a system with a CTC, it is best to do it after the injection has occurred and the run has started.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: MS Tune and GC Method Windows Can Be Hidden Behind Main Window
Problem:
Tune window and GC method window hidden behind the Ins Control window
Temporary Solution:
However, a better workaround is to activate MS Tune and GC Edit Method from the icons in the toolbar. In this case, the new windows will always appear on top of the main window.
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QQQ: Difficult to set up backflush parameters by using backflush method editor
Problem:
Difficult to setup up backflush method in MassHunter GC/MS Acquisition. When editing the GC method parameters, by selecting the backflush icon one can set up the backflush parameters. But sometimes after applying the settings it is not correct and may require repeating the procedure (sometimes more than twice) to be correct.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: PAL: Overlapped injections are not surpported in GC-Inj cycles
Problem:
"CTC PAL Set Up Injector Overlap" is not relevant for GC-Inj cycles. Do not check the "Enable Overlapped Injection for this Method" box.
Temporary Solution:
n/a
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: PAL: Vial outside the range of the CTC tray is not handled gracefully
Problem:
The Sequence Table Editor does not check for invalid vial entries for a CTC PAL. If the vial location is not within the range of the tray, an error will occur when running the sequence. After clicking OK on the error message box, the user will find the system to be stuck in the PreRun state. Selecting Pause and then Stop will crash the system.
Temporary Solution:
Be sure to specify the correct vial location in the Sequence Table.
Fix Information:
Has been fixed in B.05.01
Keyword:
One-line Description:
QQQ: Missing Edit Entire Method for GC/MS Acquisition
Problem:
The GC/MS Acquisition does not have edit entire method so that the user can review the steps of the acquisition parameters. The user has to go through each method edit step manually by clicking on an icon or menu item.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Enabling all barcode options or "Checksum" makes BarCode Reader work improperly
Problem:
If all barcode options or "Checksum" have been enabled, BCR won't read the barcode or will read it incorrectly.
Temporary Solution:
NEVER enable "Checksum" and enable just the one barcode style the user needs. Be aware that the default settings (off or on) of barcode styles in different firmware versions are different, so the user needs to make sure the correct ones are enabled before using the barcode reader. Especially when the firmware has been updated to a new version.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Cannot start acquisition software if method contains more than 500 MRMs
Problem:
The user could create a method which has more than 500 MRMs. When starting the MassHunter Acquisition program the software goes through an initialization check. During this initialization check information is stored in an array. However, this array is limited to 500 entries so when an method with more than 500 MRMs has been loaded as the default method to load, it will cause the EMF (Early Maintenance Feedback) ini file to abort, and lock up the instrument control. The user will see the error message from C:\GCMS\msexe\icstart1.log An array or matrix must contain between 1 and 500 elements.
Temporary Solution:
Delete the EMF.INI file in the folder X:\MassHunter\GCMS\n folder where n=instrument number. Once the file has been deleted, there will be no check to cause the array to exceed 500.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: System error when starting up GC/MS Acquisition if default.m was deleted
Problem:
If default.m was deleted from the instrument method directory and it was the LAST loaded method before closing application, then when GC/MS Acquisition starts up, there is a system error when it tries to access the missing method.
Temporary Solution:
NEVER delete default.m -- regardless whether its settings have been changed or not.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QQQ: No prompt to save modified sequence table when exit MassHunter Acquisition
Problem:
Start up MassHunter GCMS Acquisition, open Sequence Table Editor (STE), make some changes, then click, click x or Method/Exit to exit the application, there was no prompt to save the modified sequence table.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QQQ: Improper evaluation of CP variable _barmismatch
Problem:
This defect caused two problems when barcode mismatch was encountered and 'inject anyway' was selected in the Start Sequence panel: 1. 'Barcode mismatch, sample not injected' seen in sequence log, but sample IS injected 2. NO post-run processing OR ENVIRONMENT CLEANUP is scheduled Problem #1 is very evident but rather benign. Problem #2 is more severe, in that post-run activities INCLUDING creation of pre_post.ini, cleanup of temp folders, etc. are skipped.
Temporary Solution:
n/a
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: The "X" (close) buttonon the GC method editor is not functioning
Problem:
The "X" (close) button on the GC method editor is not functioning, even though it is NOT grayed out.
Temporary Solution:
Use the "Cancel" button in bottom area to close the GC method editor panel.
Fix Information:
Has been resolved in B.05.01
Keyword:
One-line Description:
QQQ: System does not print the MS parameters to correct printer
Problem:
The default printer has been assigned to be the LaserJet, 4050 or the 3005. System has XPS loaded and then it was unloaded and the effects are the same. 1. Set default printer to "Printer 1" (for example, Microsoft XPS document writer) 2. Click "Print Method.." in the Method menu. Check all options and click OK 3. Three documents are printed. Adobe Reader starts for printing MS parameters. DO NOT close Adobe Reader. 4. Change default printer to "Printer 2" (for example, Send to OneNote 2007) 5. Click "PrintMethod..." in the Method menu again. Check all options and click OK. 6. Two documents are printed to "Printer 2". 7. However MS Parameters are printed to still "Printer 1", because Adobe Reader doesn't pick up default printer changed while it is running.
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.04.01
Keyword:
One-line Description:
QQQ: Venting the GCMS QQQ could cause the Workstation to lock up
Problem:
When following the instructions of the vent procedure, users have locked up the workstation. Users are not informed that they must shut down the workstation down prior to turning off the GCMS-QQQ. Failure to shut down the workstation will cause the workstation to lock up when you turn off the GCMS-QQQ.
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.00
Keyword:
One-line Description:
QQQ: Autotune allows the CFT gases to be turned on and gives bad tune results
Problem:
The manual tune/autotune section of the software should automatically turn off the CFT gases so that the autotune will have the correct flows into the source to do a tune. If turning off the gases is not possible, then it should automatically load a method with the desired gases turned off so that the tune will work, this will also be useful so customers will know if they are going into tune to save their existing method in case they want to save them.
Temporary Solution:
The manual tune/autotune section of the software should automatically turn off the CFT gases so that the autotune will have the correct flows into the source to do a tune. If turning off the gases is not possible, then it should automatically load a method with the desired gases turned off so that the tune will work, this will also be useful so customers will know if they are going into tune to save their existing method in case they want to save them.
Fix Information:
The CFT warning now actually checks the CFT gas flow before going into tune. If it is over a limit that is specified in the tune config file a message box will warn the user and they will not be allowed into tune. By default the limit is 2.5.
Keyword:
One-line Description:
QQQ: Column length to three decimals, invoke the method resolution and lock-up method
Problem:
When we configured a column as length 0.171 meters (the quickswap restrictor length), it caused the software to invoke the method resolution and lock-up every time you try to load a method.
Temporary Solution:
When we configured a column as length 0.171 meters (the quickswap restrictor length), it caused the software to invoke the method resolution and lock-up every time you try to load a method. This appeared to be because the 7890 only stores 2 decimal places in the column length and the SW lets you set 3dp, so the method never matches the G.C. config.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: “No GC or MS data collected” while using Profile Data only for the acquisition
Problem:
Using profile data “only” for the product ion scan method (not just product ion scan, any method which uses profile data). It was discovered if profile data is being used only the system will generate an error message “No GC or MS data collected” and this will terminate the sequence. The problem is that the system was looking for a file called MSPEAK.BIN but when Profile Data is being used the file that is being created is called MSPROFILE.BIN and at the end of the acquisition the check did not pick up this file.
Temporary Solution:
Point Patch is available. Please contact your software help representative.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: Qual cannnot process RTL runs on localized versions
Problem:
IN RTL run, the log shows that Qual was scheduled, the RTLTIMES.INI file was created, but there was no information in that file - it seems that Qual cannot find the peaks.
Temporary Solution:
Using local language characters for method and datafile names will prevent automated Qual and Quant processing. Use the standard ANSI character set if you need AUTOMATED post-run processing of any kind (including RTL). This does not impact manual processing.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: GCMSQQQ masshunter allows users to select too fast scanning speed
Problem:
GCMSQQQ masshunter allows users to select too fast scanning speed without warning message leading to 0.6-0.3 AMU mass accuracy shiftment in Scan mode Currently customer have to use scancalc.xlsx to calculate proper scan speed. If you set up your scan method, SW allows you put a fix number to set for scanning speed like 100 ms. Acquisition then calculates cycles/sec values, but does not indicate anything whether it is good or not. If you look example below and set number to excel, you get one sample, when scanning speed is 108 ms. Scan times less than 108 ms means that you actually try to scan too fast.
Temporary Solution:
Example: Mass peaks were shifted 0.3-0.6 AMU range, when customer was scanning by using 100 ms scan time and 50-600 scan range ending up having 11 cycles/sec. Solution: Scan time was set to 250-300 ms to slower scan speed. The Problem was related to too fast scan time
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: PostRun can not be stopped from software, when acquisition is stopped prematurely
Problem:
When the run is stopped prematurely from MH acquisition by clicking stop icon, the post run backflush kicks in. PostRun can not be stopped from SW and the only option is to stop it from the GC keypad. There should be a way to stop PostRun from the software.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Autotune screen locks up with "Get 3 resolution Plots" being displayed
Problem:
It has been reported that occasionally the MassHunter GC/MS Acquisition will lockup during Autotune. As a result, the user will be required to restart the software to recover. It seems that it is an Autotune reporting problem that is related to the printing process, which has difficulty handling printer errors, too long printer recovery times, etc. If the printer is ready, this lock-up has not been seen.
Temporary Solution:
You can try to set up printer preferences and turn sleep mode option off. To turn the Sleep Mode on or off, please turn OFF the Sleep Mode. Press Menu to open the menus Press Down button to highlight CONFIGURE DEVICE Press Select button to select CONFIGURE DEVICE Press Down button to highlight RESETS Press Select button to select RESETS Press Down button to highlight SLEEP MODE Press Select button to select SLEEP MODE Press Up button or Down button to select ON or OFF Press Select button to set the selection Press Menu to exit the menu
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: two browse buttons in "Method Information" panel don't work
Problem:
Click the "Edit method info" icon on instrument control, the upper two browse buttons don't work, i.e., nothing happens when click them.
Temporary Solution:
n/a
Fix Information:
Fixed in MassHunter GC/MS Acquisition released version B.04.01
Keyword:
One-line Description:
QQQ: In a run, one can use special characters in the filenames including a “:” colon
Problem:
In a single run mode (clicking the green arrow icon), if you use a “:” colon, it won’t create the directory and errors out. The system states, “lost communication, manual mode, make directory failed, rebooted".
Temporary Solution:
Never use Windows/DOS special characters in filenames.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: Truncated: Japanese Long file name is truncated in Printed Sequence log.
Problem:
1. Run sequence with 50 character data file name & method name (JPN characters, 2 byte char) 2. then Print Seq Log. Truncating could result depending upon the number of characters being used.
Temporary Solution:
Sequence Editor has limitation of file name.(50 Char).
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Sequence Log Reporting Wrong Error Message
Problem:
If an error occurs at the same time a barcode mismatch occurs (inject anyway was selected), then the sequence log reports "Barcode mismatch, sample not injected" instead of the actual error (e.g. sampler error).
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.00
Keyword:
One-line Description:
QQQ: Error Fault not detecting status of hardware before starting Autotune
Problem:
The system does not check the hardware status prior to opening the calibration valve for Autotune.
Temporary Solution:
Loading the default method, observe that the small square status box in the GC and MS icons are green color. You can add GC or MS Monitors to check the individual relevant GC and MS parameters.
Fix Information:
Fixed in MassHunter GC/MS Acquisition B.05.00
Keyword:
One-line Description:
QQQ: Wrong information in Logbook when overide InjVol in sequence table editor (STE)
Problem:
The GC has front and rear towers, but the method is set to Front Injection only. When running a sequence with this method and overiding the InjVol in STE, the following appears in the logbook: "Rear Injection Volume changed from 1.0 to xxx", which is not right since my method and sequence don't have back injection involved.
Temporary Solution:
If running the method, and overide vol in the Run Method panel, one gets the correct info.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: The Run Method panel needs to have "OFF" functionality to ignore BarCode Reader
Problem:
If using ALS 7693A, the barcode reader cannot be disabled from GC panel or GC configuration. Run Method needs to have an "OFF" functionality to ignore the BarCode Reader. User needs a simple way to bypass the barcode reader while doing the Run Method.
Temporary Solution:
To bypass the barcode reader: 1) If running a method, type in "off" in the expected barcode field (for both injectors, if applicable) on the Run Method panel 2) If running a sequence, edit the sequence table layout and add the "Expected Barcode" column, and type in "off" in that field for EACH line. In this way, the barcode reader can be bypassed in both method runs and sequence runs.
Fix Information:
Disable Barcode For This Sequence is in the Run Sequence Panel under the Sequence Barcode Options. Fixed in release version MassHunter GC/MS Acquisition B.05.00
Keyword:
One-line Description:
QQQ: Vial left in agitator should be return before next vial arrives on CTC seq-run
Problem:
On Sequence-running with CTC, if Clicking Stop button at PreRun (during agitating), The sequence will go to the next sample. However, the vial affected by clicking "Stop" was left in agitator and is NOT moved back to the original position on the tray before the new vial is transporting to the agitator; in addition, no warning message regarding this circumstance appears, so the error with z-collision will occur, when the next vial is transported to the agitator.
Temporary Solution:
User will need to verify that the vials are placed back in the original positions.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Dual injection sequence uses run method injection selection if they are in conflict
Problem:
When the method specified in the sequence was set to front (even though dual injectors are available), the sequence only ran the vials in the front injector although dual injection on Sequence Table Editor was checked.
Temporary Solution:
Selecting "Dual" ratio box on section of Inlet Location in the method AND selecting "Dual Inj." check box on Sequence Table Editor, also entering the values into column "Dual Inj. Vial" and "Dual Inj. Vol." properly, the sequence will run and collect data correctly.
Fix Information:
Fixed in MassHunter GC/MS Acquistion released version B.05.00
Keyword:
One-line Description:
QQQ: Sequence hangs when method set to dual but dual injection on STE not checked
Problem:
The method specified in the sequence table was set to dual injection but the dual injection column on Sample Table Editor is not checked. Ran the sequence. It started but stayed there in PreRun. Needed to shut down the software to start over.
Temporary Solution:
Select "Dual" radio box on section of Inlet Location in the method AND select "Dual Inj." check box on Sequence Table Editor. Also enter the values into column "Dual Inj. Vial" and "Dual Inj. Vol." properly, and the sequence will run and collect data correctly
Fix Information:
Fixed in MassHunter GC/MS Acquisition B.05.00
Keyword:
One-line Description:
QQQ: Resuming a paused sequence with Overlap On injects the wrong vial
Problem:
Running a sequence with sample overlap, pause the sequence in the moment that the current sample is running in the GC and the next sample has been prepared. Resuming the sequence will results in picking wrong sample.
Temporary Solution:
If the overlap feature is being used, do not click "Pause" when the processing for the next sample has already started.
Fix Information:
Fixed in released version B.05.00
Keyword:
One-line Description:
QQQ: Sequence with sample overlap and dual injection doesn't work properly
Problem:
Sample overlap does not work with a dual injection sequence. No overlap is observed. It waits until completion of the run to pick up the next sample.
Temporary Solution:
Do NOT use the feature of sample overlap with dual injection in a sequence run on this release. It is NOT supported in this release.
Fix Information:
Fixed in released version B.05.00
Keyword:
One-line Description:
QQQ: Intermittently the 7890's selected injector is not present
Problem:
Here are the steps to cause the problem: - Vials are transferred to the turret of the ALS (7683B) - All the vial washes will take place - The sample is transferred to the syringe and the plunger is up - Now there is an extra movement from the turret, sounds like the re-alignment AND At the same time there is the error in the log file: 2009/06/24 13:54:33 7890 The selected injector is not present. 2009/06/24 13:54:36 7890 Lost connection to Agilent 7890A at 192.168.254.11 2009/06/24 13:54:36 ManualMode Run Method Error - Consult Logbook 2009/06/24 13:54:36 ManualMode The selected injector is not present. 2009/06/24 13:54:37 7890 Connected to Agilent 7890A at 192.168.254.11 2009/06/24 13:54:37 7890 Runs cannot be started until the GC and injector are idle. - but the ALS is doing the injection anyway and the 7890A starts System configuration: - 7890 with firmware A.01.10, - 7683B A.11.03 - PTV septum less head
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Sequence with sample overlap AND with different methods results in picking wrong sample
Problem:
When running a Sequence with sample overlap AND with different methods for the samples, the wrong sample is picked.
Temporary Solution:
Current software does NOT support different methods with different overlap settings (even if the methods have the same settings but with different names) in a single sequence run. By design, the overlap settings are saved to the method. Other methods executed in a sequence that have different or no overlap settings will override these settings and transition samples will not have either overlap settings applied; and it may also result in picking up the wrong sample. If the overlap feature is enabled in sequence-run do NOT assign different methods for samples.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: GC/MS Acquisition does not allow GC configuration to be uploaded from the 7890
Problem:
The defect is that if the user makes Config changes on the GC front panel and then from the software selected Edit GC Configuration, before you can even select the Get GC Config button, the software downloads the method to the GC. So the user can never make Configuration changes at the gc level and upload them to the GC. It overwrites the changes. For example, I was testing the MMI Inlet Cryo Config Modes, and from the GC, I changed the cryo gas to compressed air. Restarting the software, method res appeared and one needs to select edit GC Config and save the method. The method was now showing the parameters for N2 instead of compressed air. When I looked at the GC, it has converted back to N2.
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.05.01
Keyword:
One-line Description:
QQQ: Dual injection does not catch dual vial out of range
Problem:
Set up a dual injection sequence on a 7683 with a tray. An invalid vial number for the dual vial will not be caught and the user will receive no message about this error. Run the sequence and it will hang in PreRun on the line with the invalid vial. No indication is made in the logbook. You will have to shut down the software.
Temporary Solution:
User should enter the correct vial number to match the suitable range of the installed tray or turrets.
Fix Information:
Fixed in released version MassHunter GC/MS Acquisition B.05.00
Keyword:
One-line Description:
QQQ: Range of Electron Energy in Edit MS parameter
Problem:
The current available Electron Energy Value is between -70eV and -300eV. GC QqQ customer wants to change Electron Energy to more lower Voltage by themself. How can I do change available input value of Electron Energy to more wider range ?
Temporary Solution:
n/a
Fix Information:
The dynamic range will be increased with the release of the MassHunter GC/MS Acquisition software B.05.00 release. The increased range will require the installation of the new Filament Drive Circuitry Board on 7000A Series Models, this board will be shipping on the 7000B Series Models.
Keyword:
One-line Description:
QQQ: "Run Method" panel is not updated to a new GC configuration
Problem:
After GC/MS Acquisition shuts down, change the GC configuration from front injector to rear injector. Start the software, it will then recognize a configuration change and bring up the GC configuration panel. Select Get GC Configuration and OK panel and save the method. When you select the Run Method icon, the Run Method panel still shows a front injector.
Temporary Solution:
Before opening Run Method panel, do these steps first: Edit GC Parameters, OK and save the method again; then open Run Method panel and it will reflect the correct configuration.
Fix Information:
Has been resolved in B.05.01
Keyword:
One-line Description:
QQQ: Information in B.04.01 Online Help about "Relock method" is wrong
Problem:
The information provided in the Help file incorrectly describes the process (pick a method file) for Relock method
Temporary Solution:
Ignore this part of help. Correct info is: RELOCK is to be used when column or other GC maintenance has been performed such that your locked method no longer results in the correct retention time for the locked compound, and the lock pressure needs to be recalculated. RELOCK is to ‘update’ a LOCKED method, not unlocked method. So to do "Relock method", the user needs to load the originally locked method, then select "Method>Relock Method" from the Instrument Control panel and follow the further instructions on the screen.
Fix Information:
Fixed in release version B.04.01
Keyword:
One-line Description:
QQQ: Lack of messages after ALS configuration changes
Problem:
ALS configuration changes don't trigger any warning messages
Temporary Solution:
ALS configuration changes don't trigger any warning messages
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: "Unhandled exception" error appears during sequence run
Problem:
Unhandled exception error happens very rarely DURING a sequence run. The error message says, "Object reference not set to an instance of an object". But it doesn't affect the sequence at all.
Temporary Solution:
Wait for reoccurrence and get more information for potential fix.
Fix Information:
Fixed in released version B.05.00
Keyword:
One-line Description:
QQQ: Can't complete RTL with localized method name
Problem:
Create a method with a localized name (e.g. in Chinese or Japanese) Execute "acquire RTL calibration Data" 5 Data files will be acquired correctly, then an error message will appear. "Incomplete RTL calibration information! Check RTL cal data for errors!" It does not happen with English file name.
Temporary Solution:
Using local language characters for method and datafile names will prevent automated Qual and Quant processing. Use the standard ANSI character set if you need AUTOMATED post-run processing of any kind (including RTL). This does not impact manual processing.
Fix Information:
MHBridge.mac (goes under the \msexe directory)
Keyword:
One-line Description:
QQQ: CTC-PAL: A Sequence with overlapped SPME injections will lock up the system
Problem:
Set up a sequence using the CTC-PAL with a SPME syringe. Enable sample overlap. The sequence will appear to hang with the vial in the agitator on line 8. No meaningful information is available.
Temporary Solution:
In order to get correct initial conditions for CTC-PAL sequence run, we strongly recommend this:
A. If LiveUpdate (Symantec) is installed in the computer, the feature of “automatic liveupdate” should be disabled;
B. In Control panel, Power Options, select “Higher Performance” AND “put the computer to sleep” to “Never”;
C. When doing new CTC connection, open CTC menu on Instrument top:
- do “Reset Injector”;
- do “Update configuration” one or more times until this message appears on CTC Status panel:
“Loading configuration …
Connected
READY”
If after doing this a few times the system still cannot set to “Ready”, close the GC/MS Acquisition application (check in Task Manager that msinstctl.exe and ctcplus.exe should be gone, otherwise, kill those processes manually), open the application again and repeat Step C.
Fix Information:
Fixed in MassHunter GC/MS Acquisition released version B.05.00
Keyword:
One-line Description:
QQQ: "Off" button on CI Reagent Gas Control panel should show "count down timing"
Problem:
On CI Reagent Gas Control panel, when the Off button is clicked, the gas status bar displays "Pumping out" in yellow background and stays for a while (actually, 4 minutes), but no "count down timing" shown such as that with clicking the Pumpout button. This may confuse the user about the CI gas status. Note: the information about "count down timing" (starting from 240 seconds to zero when clicking the Off button) can be obtained from a backdoor command, but this is not a regular use.
Temporary Solution:
n/a
Fix Information:
Fixed in release version B.05.01
Keyword:
One-line Description:
QQQ: "Profile" mass settings are missing after autotune done & file saved
Problem:
The default settings of masses for PCI (methane) profile mode are 41, 267 and 599 (see file default_pci.tune). However, one or two mass numbers are missing and not stored in the new tune file after autotune was done. For example, for MS1 Profile, masses 41, 267 and 599 may exist, but for MS2 Profile, only 41 is contained.
Temporary Solution:
n/a
Fix Information:
Fixed in release version B.05.01
Keyword:
One-line Description:
QQQ: Conflict Vent Status between Vent Panel and Tune Status bar
Problem:
On Vacuum Control of Manual Tune, clicking Vent button to start vent process, when all criteria for vent (temp, vac and turbo speed) are not matched yet, the Vent Status box on Vent panel shows "Venting" in yellow, but Tune Status bar shows "Vented" in red.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: PAL: Missing CTC-PAL configuration from Menu Configuration upon re-installation of MassHunter
Problem:
Was working on an earlier build of MassHunter GCMS Acquisition and then uninstalled the Acquisition software and reinstalled but now cannot configure the PAL unit.
Temporary Solution:
The PAL drivers are flagged in a file called CTC.INI under the \mssetup. When the user uninstalls the software, this directory is removed and then is re-created. This is the reason why PAL drivers did not show up.
Fix Information:
When uninstalling the MassHunter GCMS Acquisition software package, all related add-on packages should also be removed and then reinstalled for completeness. Was resolved in B.05.01
Keyword:
One-line Description:
QQQ: NCI mode: error in switching gas type without clicking "Set" button
Problem:
The error occurs in these circumstances: 1. Start MassHunter GC/MS Acquisition, load default_CI.m associate with ci_atune.tune.xml. The default mode is NCI, default Gas is A (methane); 2. Change CI Gas A to B (Ammonia) on Ion Source panel WITHOUT click “Set “ button; change Methane to Ammonia on Autotune panel; 3. Click Autotune to bring up the "wait" panel. Filament turns on when the Emission current is increasing from zero to 50 uA. Cal Valve is also on, but CI Gas Flow drifts between 99-100. 4. Filament is on for 5-6 minutes; when CI Gas Flow drops down to 1 or zero, the filament turns off, Cal Valve shuts off too, and CI Gas Flow back to 99 or 100, no tune starts, and this status stays forever until clicking “Cancel autotune”.
Temporary Solution:
This error can be avoided if click "Set" button first prior to clicking "Autotune" button.
Fix Information:
Fixed in release version B.05.00
Keyword:
One-line Description:
QQQ: Enable Sample Prep menu item shows wrong .pt method
Problem:
Associated different sample prep methods with methods. Some methods had no sample prep method. The checkmark seems to work appropriately however, the sample prep method is often incorrect. Sometimes Enable checked, but no method specified (before running the method). Other times the wrong sample prep method specified. It didn't seem to change the menu item after loading a method with a different sample prep method.
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.00
Keyword:
One-line Description:
QQQ: PAL: Tray name with lower letter is accepted on Seq table, but can't execute Seq Run.
Problem:
Install CTC-PAL Software, select CTC-PAL as Injector, Tray 1 = 32, 20 ml
1. Verify the run method with CTC-PAL complete
2. Try Run sequence with the method.
3. Set Tray name with lower letter "t1-3220", not "T1-3220"
4. Run seq. but an error occur immediately.
"Invalid argument"
because tray name is specified as lower letter "t1".
If Try name with lower letter is not allowed, a warning should be appeared when exit Seq table.
OR
Tray name should be converted to capital letter automatically.
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.00
Keyword:
One-line Description:
QQQ: Overlap injection option is not saved
Problem:
1. Open "Setup Injector Overlap" panel 2. Change the Start option from 2nd one to 1st one like above. ( x min after full...-> After full...) 3. Open "Setup injector overlap" panel again. 4. Start option is changed to "Start n minutes after..."
Temporary Solution:
n/a
Fix Information:
Fixed in release version B.05.00
Keyword:
One-line Description:
QQQ: Adding/Removing 7693 tray does not show up in method resolution
Problem:
I had a system with a 7693 ALS but no tray. The Sample Prep menu items were not displayed. Created a method. Shut down software and added a tray to the instrument. Started up software. There was no method resolution, and no sample prep menu items displayed. Went into GC Configuration to upload the GC configuration. Upload was successful and method was saved. Still no Sample Prep menu items. Shut down the software once more and started back up to get the menu items.
Temporary Solution:
Same scenario with removing a tray. It is not until the shutdown/startup after uploading the GC configuration that the Sample Prep menu items will be removed.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ: Unknown error occured with CTC SPME method after restarting GCMS Acquisition
Problem:
On a system configured with CTC and using a SPME method, an "Unknown error" occurred after restarting GCMS Acquisition
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: PAL: Unexpected Program termination occurs when restart MH after interrupt seq.
Problem:
CTC A.01.05 1. Start CTC HSS sequence 2. "Stop" sequence by "Stop" button(Red button) on SW. 3. Sequence is interrupted correctly. 4. Close MH Acq. 5. Start MH Acq again. 6. "Unexpected Program termination" always occurs.
Temporary Solution:
Do not press "Stop" during Prerun.
Fix Information:
Establishing the correct initial conditions is a sensitive issue to run CTC properly; it may eliminate several unexpected errors. We strong recommend checking and doing the following processes prior to running any CTC method or sequence: A. If LiveUpdate (Symantec) is installed in the computer, the feature of “automatic liveupdate” should be disabled; B. In Control panel, Power Options, select “Higher Performance” AND “put the computer to sleep” to “Never”; C. When doing new CTC connection, open CTC menu on Instrument top: • do “Reset Injector”; • do “Update configuration” once or more times until the following message appear on CTC Status panel: “Loading configuration … Connected READY” If doing this for a few times and the system still cannot set to “Ready”, close the MH GCMS data acquisition application (check Task Manager, msinstctl.exe and ctcplus.exe should be disappeared, otherwise, end these two processes manually), power cycle CTC, then open the application again and repeat Step C. Was resolved in B.07.00
Keyword:
One-line Description:
QQQ: Progress bar in Advanced Autotune doesn't work properly
Problem:
On Advanced Autotune, clicking any parameter button will trigger an autotune for the select parameter, and the Progress Bar on bottom should show the tune progress in green. But for some parameters, this bar doesn't show anything.
Temporary Solution:
n/a
Fix Information:
Fixed in release version B.05.01
Keyword:
One-line Description:
QQQ: PAL: CTC-PAL injection volume get reset to OLD value if method is not saved immeditately after editing
Problem:
Injection Volume modification in the method the value is not saved if immediately after the modification the method is not saved, when the “CTC PAL Edit Method” is reopened they show the old value and not the new one.
Temporary Solution:
n/a
Fix Information:
Fixed in release version B.05.01
Keyword:
One-line Description:
QQQ: MS Params has a GAIN entry limit of 100
Problem:
The user can enter a value upto 100 for the GAIN, while the tune report could show a higher value is possible.
Temporary Solution:
The tune report shows the maximum calculated GAIN value which could be possible based on the current tune parameters. If a user would like to enter a value greater than the maximum 100 GAIN value, then the user should use the delta EMV. Entering in the delta EMV value will show the corresponding/equivalent GAIN value. Note: Using higher GAIN values will/could cause the lifetime of the EMV to be shorter.
Fix Information:
Fixed in release version B.05.00
Keyword:
One-line Description:
QQQ: User does not know what type of tune report is being printed, Autotune or Generate
Problem:
When the user looks at the tune report, there is no real way of knowing if the tune report was from autotune or from generate report. Both reports are the same.
Temporary Solution:
n/a
Fix Information:
Fixed in release version B.05.01
Keyword:
One-line Description:
QQQ: Iris limit shows a false change from -100 to 100 to -70 to 70
Problem:
Manual Input on IRIS (mz 1050) some how ended up yielding an ERROR when inputting a value that fell outside the limit of -70 to 70 while the actual limit was -100 to 100. This error did not occur when making a change outside the error redefined limit, but once the error occured it always occurred, i.e., outside the bounds of -70 to 70 but inside the bounds of -100 to 100.
Temporary Solution:
n/a
Fix Information:
Fixed in release version B.05.00
Keyword:
One-line Description:
QQQ: Sample error 142 occurs during acquisition with 7693 back tower & tray
Problem:
1. Configure a 7890-only instrument. The 7890 has 7693 (dual tower and tray) 2. Create a method with back Injection (without sample prep) 3. Run Method 4. Can't start acquisition -- error message is "Sample error 142."
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Sample prep command to Back tower does not work
Problem:
1. Configure a 7890-only instrument with 7693 (Dual tower & tray) 2. Create a method. 3. Associate sample prep method (wash back tower command). 4. Save method. 5. Run method. 6. An error occurs, "Fail in command to back tower" the screen capture of mslogbk.htm and Slog are attached. also, I attached my method.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Copy button on 7890 GC Status window is not working
Problem:
Selecting the Copy button the GC Status window, it says "Not there yet..."
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Unexpected Program Termination While Running Seq with GC QQQ
Problem:
While running a sequence with a method which collects the ms signal as well as the GC's FID signal. The GC-QQQ was configured to the back inlet. Was unable to tune because of an error stating, Error in Autotune! Check Abundance failed." At the end of the sequence, an unexpected program termination error and intrument control closed. There was also an error message which was presented on the status line.
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Configure MS Source Dialog box pops up and then disapperars
Problem:
Configure MS Source Dialog box pops up and then disapperars, it works but distracting
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QQQ: Select "No" on saving changes to method will bring Method Resolution twice
Problem:
1. Launch the application; 2. Method Resolution appears if the loaded method has different configuration with instrument; 3. Click OK to close Method Resolution, and brings up the message box "Method has changed during ChemStation initialization. Save Changes?"; 4. Clicking "Yes" will prompt to input method name to save; 4. Clicking "No" will bring Method Resolution again.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: No method save after Get GC configuration
Problem:
Started up software using a 7890 with a front injector and tray (7693). Created and ran method. Shut down the software. Added a back injector and started software again. It now brought up method resolution (did not before) and states to Get GC configuration. After OKing that panel however, it did not bring up the method save.
Temporary Solution:
Aftering making any types of edits to a method, the user needs to make sure that the method has been saved.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Valve method associated with a sample prep method
Problem:
Edited a method that had a sample prep method associated with it. Changed the injection source from ALS to valve and saved the method to a new name. Enable Sample Prep menu item appropriately became grayed. Ran the valve method. Method completed. The Enable Sample Prep menu item became ungrayed and it showed a .pt association. Method print also showed the sample prep method association.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
QQQ: The software configuration should notify user on software/firmware mismatches.
Problem:
When starting instrument control, the software does not inform the user of mismatch firmware between the software package and the GCMS-QQQ. This could cause strange error messages to appear because the GCMS-QQQ may not understand the hardware command set which it is being asked to do.
Temporary Solution:
Update the firmware on the GCMS-QQQ with the supported version the MassHunter GC/MS Data Acquisition is expecting, this can be done via the MS Configuration of the instrument.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: MS Config, forgot to configure the sources, and it did not show up in the summary page
Problem:
Did the configuration of instrument #1, did not configure the source, when selecting save results, it did not show EI source as an available sources in the summary page.
Temporary Solution:
The system will automatically use the EI source type by default when loading the instrument control.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: PAL: Setup CTC-PAL Sample Overlap panel does not allow certain selections
Problem:
With the HS injector installed on the CTC-PAL was unable to select the second sample overlap selection (xxx min after completion of the cycle). With the SPME injector installed was unable to select the first sample overlap selection (after completion of the cycle). In both cases, select the option and OK the panel. When returning to the selection, it was changed.
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Dual injection with barcodes and overlap not working correctly
Problem:
The method specified in the sequence is set to dual injection with overlap on. Set up a sequence and entered dual injection vials and barcodes. On the run sequence panel, set to don't inject on a barcode mismatch. Although all my barcodes were correct in the sequence table, every other line failes on a barcode mismatch because it compared the actual barcode on the rear to the expected on the front.
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Setting CI reagent flow turns off CI cal valve
Problem:
When the CI reagent flow is 0 setting the flow will turn off the CI cal valve. This is a problem after autotune or any other time the instrument is turned off. Then when the user tries to manually tune, if they turn the cal valve on first, it will be turned off when the CI reagent gas flow is set.
Temporary Solution:
Turn the CI cal valve back on after setting the reagent gas flow.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Message about different source appears twice after selecting source from panel
Problem:
1. configure instrument, select all available sources (the currently installed source is CI); 2. Start the application, comes up the panel "Ion Source Selection"; 3. Select NCI source; 4. The message box appears, such as "D:\MassHunter\GCMS\1\METHODS\DEFAULT.M specifies a different ion source from the one currently installed in the MS" 5. Click "OK" on the message box;the message disappears; 6. The same message box appears again; 7. Click "OK", the message disappears.
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Log file is displayed with garbage Asian characters
Problem:
When Multivu was used to display a log file, the Japanese characters in the file were displayed as garbage.
Temporary Solution:
Manually use Microsoft Notepad.exe to view log files such as c:\gcms\msexe\icstart1.log
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Wrong sample prep program can get executed when overlap is on
Problem:
Sample overlap checked and sample prep program is also enabled for the method. The sequence using the same methods with sample overlap and same sample preps are able to complete without an issue. However, to override the sample prep method and enter different sample prep methods; this cause issues. The sample prep method run is from the previous sequence line. For example: line 1 prep1.pt line 2 prep2.pt line 3 prep1.pt line 4 prep2.pt When a sequence is running, prep1.pt is executed before lines 1,2 and 4. Prep2.pt is executed before line 3.
Temporary Solution:
The sequence needs to be closed and re-executed; continue with the sequence could cause problems with the sample prep method association.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: msinsctl.exe process is not cleaned up after tune and application was closed
Problem:
1.Launch Acq application; 2. Perform several operations that are only related to tune (such as autotune, manual tune or vacuum control); 3. Exit tune panel and close the application; 4. Frequently (80% probability), the msinsctl.exe process is not cleaned up after tune and application was closed. So user needs to kill this process first to start the application next time.
Temporary Solution:
Running a method or sequence after tune, this will not occur.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Q1 DC and Repeller power "walking" when executing multiple autotune in a row
Problem:
The following behaviors have been observed for NCI mode and EI with Extractor (no tests for PCI and EI mode were conducted yet): When executing multiple autotune in a row (the second autotune starts based on the first autotune, the third autotune starts based on the second autotune, and so on), Q1 DC and Repeller power will "walk" and increase in one direction (absolute values), although the delta between Q1 DC and repeller is relatively stable. (Please see the attached file for an example)
Temporary Solution:
Autotune for Default Setting does not have this kind of behaviors.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Read Barcode doesn't work for the DualInjExpectedBarcode column
Problem:
In the sequence table editor, read barcode button should work the same way for ExpectedBarcode column and DualInjExpectedBarcode field. Currently, no read barcode function is connected to the DualInjExpectedBarcode field.
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Incorrect display and processes in pumpdown and Select Ion Source
Problem:
1. After vent, turn MS, click “Pumpdown” button to bring up the panels "Pumpdown Manual Steps" -"Make sure Vent Valve is closed"; 2. Close Vent valve then click OK to close “Pumpdown Manual Steps”; 3. After a few seconds, the message box” Instrument Faults” appears, it indicates that “QqQ fault detected: 123 Vacuum system is not ready. ….”. It is normal; 4. The error is: the message box” Instrument Faults” cannot be moved and closed until user close the “Ion Source Selection” button that is displayed on the bottom bar and is difficult to be seen. --> This does not occur when you have just a single Ion Source configured.
Temporary Solution:
On the task bar, the user can select the task bar icon for the application and then move to move the image over to see the screen behind it.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Method name cut off in the sequence.log and printed "current sequence"
Problem:
A method name was "m2.nci.m" in the sequence table. In the sequence log, the method name was cut to "m2". If I click the Printer button, and select "print current sequence", same thing happens in the printed sequence.
Temporary Solution:
This is due to the new method naming, user should use an UNDERSCORE.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Selecting "Do not show this warning again" on CFT message box closes the box
Problem:
After clicking tune icon, the CFT remind message box appears "If installed, turn off CFT backflush before Tuning"; If user selects check box "Do not show this warning again" on bottom of this box, this box will disappear FOREVER unless uninstall and install the application again.
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.05.01
Keyword:
One-line Description:
QQQ: Editing the Sequence Table with Sample Overlap ON could cause mixed results
Problem:
The sequence log file does not reflect the actual sample vials which were
used during the sequence.
Starting sequence Wed Oct 14 17:57:48 2009
Instrument Name: QQQWAD002
Sequence File: D:\MassHunter\GCMS\1\sequence\overlap.sequence.xml
Comment:
Operator: QQQWAD02\Admin
Data Path: D:\MassHunter\GCMS\1\DATA\overlap\
Method Path: D:\MassHunter\GCMS\1\METHODS\
Line Type Vial DataFile Method Sample Name
-----------------------------------------------------------------------
1) Sample 1 Sample 1
Datafile vial 1
Method vialoverlap
2) Sample 7 vial 7
Datafile vial 7
Method vialoverlap
3) Sample 2 Sample 1
Datafile vial 2
Method vialoverlap
Sequence Table edit performed Wed Oct 14 18:11:56 2009
4) Sample 8 vial 8
Datafile vial 8
Method vialoverlap
5) Sample 9 vial 9
Datafile vial 9
Method vialoverlap
6) Sample 3 Sample 1
Datafile vial 3
Method vialoverlap
7) Sample 4 Sample 1
Datafile vial 4
Method vialoverlap
8) Sample 5 Sample 1
Datafile vial 5
Method vialoverlap
9) Sample 6 Sample 1
Datafile vial 6
Method vialoverlap
Sequence completed Wed Oct 14 18:35:27 2009
D:\MassHunter\GCMS\1\DATA\overlap\2009 Oct 14 1757 Sequence Log .LOG
However, the actual vial numbers which were used were
Vials 1, 2, 2, 3, 9, 3, 4, 5, 6 not the
Vials 1, 7, 2, 8, 9, 3, 4, 5, 6 as reported in the sequence log
Temporary Solution:
The issue to the mismatch of the sequence log file and the initial sequence
table is related to the Enable Sample Overlap was turned ON.
When the sequence run was started the initial sequence table had samples in
vials 1, 2, 3, 4, 5, 6. When the run was started a sample was added to the
table just after sample 1 (vial 1). But since the Sample Overlap was Turned
ON, the system has already preread the information from line 2 (Sample 2, vial
2). As a result, the system picked up the sample in vial 2 not sample in
vial 7.
To validate this process, when the system was picking up sample in vial 2
the sequence table was editted again. This time two new samples were added
to the table sample 8 (vial 8) and sample 9 (vial 9). Again because of the
Sample Overlap was turned ON, sample in vial 8 was ignored and the sample in
vial 3 was used, then the sample in vial 9 was processed and then the sample
in vial 3 was picked up. The rest of the samples were picked up as noted.
Presently, there are two workarounds for this while running a sequence which
has methods with Sample Overlap
1 -- DO NOT EDIT the Sequence Table while the sequence is running
2 -- If you need to edit the sequence while it is running, DO NOT ADD/INSERT
any lines just below the acquiring method. Insert two lines below the
acquiring method.
The sequence log table prints out a summary result of the sequence table which
was editted. For the case in which the system states that it injected from
sample in vial 7 in the sequence report, if the user looks at the datafile
look in the individual sample_info.xml file for the vial that was actually
injected -- under name for Sample Position, the value is the vial number:
Sample Position
Sample Position
21
The key bit of information one needs to remember about Sample Overlap is
as soon as one injection is made, the ALS begins its solvent wash and sample
pump cycle to prepare the next sample which means information from next sample
has already been taken into account so inserting a new sample at this point
will cause the previous line which was in the sample table to be performed and
not the newly inserted line if a sequence table has been editted.
Additional Information:
OnLine Help Files in the GC/MS Data Acquistion about Sample Overlap
Sample overlap can increase throughput by allowing the ALS to begin processing
the next sample before the current run finishes. ALS sample preparation does
not have to be finished before the current runs ends.
To use Sample Overlap, select Enable Sample Overlap, then select the preferred
timing for the overlap and enter a time (in minutes) as needed. The three
modes are:
After the previous injection is completed — As soon as one injection is made,
the ALS begins its solvent wash and sample pump cycle to prepare the next
sample. If the run time and oven cool down cycle is longer than the ALS sample
preparation time, the sample waits in the needle above the inlet until the GC
becomes ready for the next run. You can use this setting if the sample is not
likely to degrade in the syringe or evaporate from the needle.
Prepare sample __ min. before end of GC run — ALS sample preparation begins
at the specified number of minutes before the run ends. Depending on the total
run cycle time, this setting should reduce the time the sample spends in the
syringe waiting for the next run to start. If the time remaining in the
current run is less than the specified time for this setting, sample
preparation will begin immediately following the end of the active run.
Prepare sample __ min. after end of GC run — The sampler waits the specified
amount of time after the current GC run ends to begin ALS sample preparation.
When using oven temperature programming, the ALS will start to prepare the
next sample during the oven cool down cycle between runs. This setting should
reduce the time the sample spends in the syringe waiting for the next run to
start.
When selecting a mode, determine / consider the following:
The actual ALS sample preparation time for the method (time it using a watch).
The total run cycle time: the run time plus any cool-down time after the runs
ends.
The After the previous injection is completed and Prepare sample __ min.
before end of GC run settings increase sample throughput by preparing the
sampler to perform operations related to the next sample before the GC
completes the current sample run.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Acquiring Data, zooming in on chromatogram data jumps to undefined box field
Problem:
Occurs in B.04.01 and has been validated on B.05.00 During the acquisition the user can see the TIC being displayed. The user then wants to zoom in on a group and does a right click and drag over the region to be zoomed in. The zoomed in box is not the regions which was defined.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: When vent cycle program is over, Ion Source and Quad Temp are turned ON
Problem:
When vent cycle program is over, the current method with tune file is loaded again. As a result the heaters will be turned ON!
Temporary Solution:
Before run vent cycle in manual tune, the user should load special tune file with Ion source and Quad temp are OFF.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: The 'Sample Prep File Name' in the sequence table is only an override.
Problem:
The 'Sample Prep File Name' in the sequence table is only an override, leaving the field blank will run the method's pretreatment program by default. There is no way to disable sample prep from this column without having to create a new method.
Temporary Solution:
Make the default method have an Enabled Sample Prep Program with at least one command. For example, a single Wait command of '.1 min'. If no command is chosen, the sequence will not run. Then use the sequence queue's 'Sample Prep File Name' to override this dummy sample prep sequence with the needed Pretreatment Program.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Sample preparation does not allow sample overlap.
Problem:
There seems to be a functionality missing between sample overlap in combination with sample preparation.
Temporary Solution:
n/a
Fix Information:
The pre-treatment path and file name must agree between sample K and sample K+1 or else Overlapped experiment is inhibited.
Keyword:
One-line Description:
QQQ: Running the vent program could leave the source and quad temperatures above 100 deg.
Problem:
Vent the GCMS-QQQ If the heated zones are not cooled prior to starting the vent process, it is possible that the heated zones could be greater than 100 deg. Caution should be used when handling the parts. Presently, when the turbo pump speed drops to 50% spin speed, this will trigger a high vacuum fault in the electronics. there is a 7 minute timer which will then count down and at the end of 7 minutes, this will turn off the foreline pump.
Temporary Solution:
If you are going to be venting the instrument, cool down all of the temperature zones: the source temp, quad 1 temp, quad 2 temp and transferline. The temperature should be below 100 deg and then start the vent cycle.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Customer has a working method in EI and would like to convert this to PCI or NCI
Problem:
You cannot load an EI method if a ci source is selected and change the tune file to the EI method. The error of the workstation is that this method is not valid due to the installed CI source.
Temporary Solution:
To preserve the GC settings when changing from EI to CI:
1) Save existing EI method to a new name (e.g. xyz.m)
2) Copy qqqacqmethod.xml from default_pci.m or default_nci.m (depending
on the ion polarity) into xyz.m
3) Reload xyz.m
4) Edit the MS parameters
5) Save xyz.m
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Changed source type via MS Parameters but did not realize that it did not affect tune
Problem:
The implementation of the changing the tune type and then saving the method is good. But unaware that one had to go back under the Instrument section to change the source type to the new one if one wanted to proceed to the manual tune section.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: English (United Kingdom) prevents saving tune into PDF
Problem:
When the Regional and Language Options Current format are set for: English (United Kingdom) There is an error while autotuning: "An exception has occurred saving an autotune report as a PDF file" "An error occurred during local report processing." Otherwise autotune finishes OK.
Temporary Solution:
Change the Regional and Language Options Current format are set to: English (United States)
Fix Information:
Only supported local languages are US English, Japanese and Simplified Chinese. Any other language choices may cause erratic behavior. This also includes regional and language options.
Keyword:
One-line Description:
QQQ: When 16 Vial Turret is on the Back Injector and 3 Vial Turret is on the Front, vial ranges are incorrect.
Problem:
The configuration is 7693 ALS Tray unplugged with a 16-vial turret on the back injector and a 3-vial turret on the front. If one tries try to run the back injector with a vial number over 3, it will not run. It will sit in Prerun and to terminate the program one will need to shutdown through task manager. If you unplug the front injector, then it will use the appropriate vial range 1 - 16.
Temporary Solution:
When the 16 vial turret is on the front and the 3-vial turret on the back, it works correctly.
Fix Information:
Was resolved in B.05.01
Keyword:
One-line Description:
QQQ: Extended characters not being recognized and passed properly by the command shell.
Problem:
The command shell will stay open as long as one has Qualification open. Once Qualification program is closed, the command shell goes away. That’s the way the EXEC and DOSRUN functions work when a .bat file is used; the command shell will stay active until the processes it has started are all terminated. The use of the .bat file is to provide proper synchronization. The display one will see in the command shell is normal, because of what the ‘OPEN’ command does. Also, Qual indicating it ‘can’t find the method’ is normal, and doesn’t impact anything.
Temporary Solution:
n/a
Fix Information:
Has been fixed in MassHunter GCMS Acquisition B.05.02.
Keyword:
One-line Description:
QQQ: Relock Menu Should be Dimmed when unlocked method is loaded.
Problem:
If you have a locked method and you unlock the method (and even if you reload it after locking it), the relock menu item is available, but you cannot relock a method that is not locked.
Temporary Solution:
Need to validate the status of the method.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ: Cannot view the video on bundled PC Z400 (Win 7 or Vista)
Problem:
When the image recovery is used on the Z400 PC, the user may not be able to view all of the videos on the workstation. Some of the videos require the use of Media Flash to be installed on the PC.
Temporary Solution:
User will need to download Adobe Flash player from the internet to view the videos. Image recoveries for the PCs do not include Adobe Flash Player, the Adobe Flash Player is added onto the image after the media recovery process.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: There is no warning or message about MRM segments being resorted
Problem:
The segments are sorted by Precursor and then Parent Ion, which is from High to low for the parent ion, and if the parent ions are the same and only looking at the collision cell then they are sorted from high to low for the collision cell energy.
Temporary Solution:
Sorting by Precursor and Product ions are required by instrument control. The sorting by Collision Energy is required by AutoMRM application thus the reason why it is sorted.
Fix Information:
Has been fixed in MassHunter GCMS Acquisition B.05.02.
Keyword:
One-line Description:
Some libraries will not install on a system with only MassHunter installed and not ChemStation
Problem:
MassHunter supports libraries in the .L format however many of the shipping libraries look to see if ChemStation software is installed and if it is not will refuse to install the library. The following is a list of libraries that will install properly on a MassHunter only system as of March 2012 NIST08 NIST11 Wiley9/NIST08 Wiley9/NIST11 CWA - only available with 5975T Military Bundle MPW2011 The following is a list of all the libraries that do NOT install with only MassHunter: Agilent RTL Library Databases G1671AA Hazardous Chemical RTL Database G1672AA Pesticide RTL Database Library G1673AA Indoor Air Toxics RTL Database Library G1674AA Forensic Toxicology RTL Database G1675AA JPN Positive List Pesticide RTL Database G1676AA Fiehn GCMS Metabolomics RTL Library G1677AA Environmental Semi-VOAs RTL Database G1678AA Solvents Plus RTL Database G1039D (MPW - 2007 edition) All other libraries may fail to install. The libraries are valid and can be searched by MassHunter only the installer fails.
Temporary Solution:
Install the software on a system with ChemStation software installed then locate the .L folder and copy it and its contents to the MassHunter system. The library should then be functional in MassHunter.
Fix Information:
Plans exist to address the install issue on all library installers. Dates to be determined.
Keyword:
One-line Description:
QQQ: NIST Search Utility can cause acquisition to hang while using QUAL.
Problem:
Intermittent freeze up while having GCMS MassHunter Data Acquisition loaded not just running when user runs NIST 2.0 Search Utility software.
Temporary Solution:
1 – Qual and NIST only with no acquisition running in the background do they get a lockup – Our Problem is Acquisition SW Locking which means No lockup in this scenario. 2 – Qual and NIST are running but they are NOT using the current data file – sequence is not calling QUAL – Yes, only if they do NIST search again 3 – Qual and NIST are running and they are USING the current data file in the sequence – sequence is not calling QUAL – Yes, only if they do NIST search again 4 – same as #2 but sequence is calling QUAL -- Yes, only if they do NIST search again 5 – same as #3 but sequence is calling QUAL -- Yes, only if they do NIST search again "If they do NIST search again" ==> means if the NIST window is already opened and then you open Acq and run no problem. Acquisition will hang the moment you launch the NIST search from the Qual window meaning Acq is hanging when the search algorithm is running. Do not run Acquisition while using QUAL with NIST Search Utility
Fix Information:
Has been fixed in MassHunter GCMS Acquisition B.05.02.
Keyword:
One-line Description:
QQQ: Tune File Not Being Saved When Save Option is Checked
Problem:
In the Autotune panel, Save Tune File when Done was checked, but upon trying to exit autotune, a message saying that exiting without saving will discard any changes. So a manually save and then Exit Autotune may be required since it is not certain if the previous values were saved.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Pumpdown Temperature is not the same as the prompt
Problem:
When using the pumpdown button, the software prompts for low (100/100/100) or operating temps. Source operating temps are different by mode: EI=230, PCI=300, NCI=150. The prompt shows the correct operating temps however 230 is always loaded for operating temps for any ionization mode.
Temporary Solution:
When the system is pumping down without being connected to the Workstation then 100/100/100 is used. It is only when it is connected to the Workstation the source is set to 230.
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
QQQ: The GC parameter setting panel cannot be resized (larger or smaller)
Problem:
config 7890 only go to the GC edit panel. Place the cursor at the border, but no headed arrow appeared, the panel size cannot be changed
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
MSD: GC Status Panel is hidden by MassHunter GCMS Acquisition Instrument Control panel
Problem:
1. Show GC Status panel (Instrument/GC Status show/hide) 2. click QQQ InstCtrl pnal anywhere. (eg. click any menu) 3. GC Status panel is hidden
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: MassHunter GCMS Acquisition does not turn off AUX temp when Venting.
Problem:
MassHunter GCMS Acquisition does not turn off AUX temp when Venting. The user is given a prompt during the process to turn off the AUX temp.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Issues with Trace Ion Detection (TID)
Problem:
The SC DSP as it switches from one group to another group the SIM group changes, there is an 816 ms gap where no data is retained due to the fact that SC is collecting the 7 scans of the next ion to “prime” the digital filter known as TID.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ: PAL -- User should be able to view the PAL method during a run
Problem:
the PAL method should be viewable during a run just as the GC method. The GC Edit Parameters icon is ungrayed but the CTC-PAL icon is grayed and unavailable. The other data systems all you to view the method but not edit it.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QQQ: Software Installation -- there is font issue when installing the MassHunter
Problem:
There are three font types being used and also the size are different. Information being presented and step-by-step is correct.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Retention Time Locking Help is Incorrect
Problem:
n/a
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.06.00
Keyword:
One-line Description:
QQQ: Signal Event Signal Delay does not work
Problem:
Creating a signal event specifying delay signal does not work.
Temporary Solution:
n/a
Fix Information:
Was resolved in B.07.00
Keyword:
One-line Description:
QQQ: PAL -- CTC-PAL Status is always hidden
Problem:
Show CTC-PAL Status panel. select any menu/ try to start run. CTC-PAL status panel is hidden under Inst Control panel; this could be an inconvenience.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ: When tuning, the status bar does not always stay in the same place.
Problem:
When tuning, the status bar does not always stay in the same place. The information being presented is correct.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QQQ: Monitor Icon on Top panel is partially truncated.
Problem:
Monitor Icon on Top panel is partially truncated.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: MassHunter creates GC signal CH files that possess incorrect retention times when loaded into MSD ChemStataion or Ezchrom DA
Problem:
The second defect is the Retention Time Range of the data. The data was acquired from time 0.00 to 4.00 minutes. Since partial data collection is not supported, the data must start at time 0.00. However if you view this in MSD ChemStation Data Analysis or EzChrom Data Analysis, it displays from 1.00 to 4.99 minutes. Clearly, some aspect of the *.CH file written by MassHunter GCMS Acquisition doesn’t conform to the design specification. On a typical MassHunter GCMS Acquisition system with MassHunter Data Analysis, instead of MSD ChemStation Data Analysis or EzChrom Data Analysis, the GC/MS translator converts the .CH files into “archer” format. MassHunter displays the correct retention time range.
Temporary Solution:
A point patch (GC7890.dll and GC7890.pdb) is available as a temporary fix.
Fix Information:
To install the point patch: 1. In the directory C:\GCMS\MSexe, rename the existing files from: GC7890.dll to GC7890-orig.dll GC7890.pdb to GC7890-orig.pdb 2. Copy the new files GC7890.dll and GC7890.pdb to the directory C:\GCMS\MSexe Was resolved in B.06.00 Fixed in revision B.06.00
Keyword:
One-line Description:
QQQ: Numerous files will be left on the PC during uninstallation.
Problem:
The original files which were copied on PC and when they are updated due to the configuration. The Uninstallation will only touch the original files and leave the configuration and newer files alone.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Cannot copy message at the end of each run with sample prep
Problem:
Set up a sequence of three lines using a method with sample prep (sample overlap was on). At the end of each run, a message "Cannot copy D:/MassHunter/GCMS/3/PreTreat/prep1.pt to D:/MassHunter/GCMS/3/Data/g1.d/AcqData/meth1.m/prep1.m"
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Run does not complete until the sample prep of next sample is complete
Problem:
Set up a sample prep program with a 3 minute wait so that it would be longer than the the run time of the method. Associated it with a method and then setup a sequence using that method. While sample 1 was running, it executed the sample prep program of line 2. It was sitting in its wait state when the fist run finished. Software went into Post Run and sat there, -35791 appeared in the runtime field. When the sample prep was complete for line 2, the software completed it processing of sample 1.
Temporary Solution:
Sample prep program needs to be shorter than the run time of the method.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: There is no LTM related paremeter monitor in the instrument control.
Problem:
configure GC with LTM launch the software, goes to the instrument menu-->edit menu LTM related paremeters are not avaliable for monitors
Temporary Solution:
n/a
Fix Information:
Was resolved in B.07.00
Keyword:
One-line Description:
QQQ: Tunes save information to a PDF, the printed air-water check with graphics is not saved.
Problem:
Was trying to generate an air and water report and noticed the output gave a graphic but could not find the PDF.
Temporary Solution:
n/a
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QQQ: Translation -- Notes is untranslated when Retention Time Locking is finished.
Problem:
After Retention Time Locking running is finished, the information of Notes is not translated.
Temporary Solution:
n/a
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QQQ: Translation - Screenshots of online help for RT lock, lock method is remaining in English.
Problem:
Some of the Lock Method of RT Lock is in English, the should have been replaced by Japanese User Interface screens.
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.06.00
Keyword:
One-line Description:
QQQ: PAL -- "Starting GC Prerun but GC not idle" happens after CTC seq abort
Problem:
1. CTC-PAL Seq start 2. Abort Seq 3.CTC-PAL Control module become not "Remote control" 4. Check CTC-PAL configu does work. 5. Send "Reset CTC-PAL" by Reset CTC-PAL menu 6. Start Seq again. 7. seq can not start becasue "Starting GC Prerun but GC not idle" happens . Once it happens, user will need to reboot PC. After rebooting the PC, one can start Seq again without GC Reboot.
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QQQ: Simulate sequence.log has aligment issues, but all of the information is correct.
Problem:
Simulate sequence.log has aligment issues, but all of the information is correct.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: PAL, ICON -- CTC-PAL Icon does not show Edit Method Parameter panel
Problem:
1. Launch MassHunter GCMS Acquisition 2. Click CTC-PAL Icon. Edit Method Parameter panel is shown. 3. Change syringe. (Change PAL Config -> Release terninal lock ->(change syringe) -> Lock Terminal) 4. click CTC-PAL Icon again. Edit Method Parameter panel is not shown until re-load method.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: PAL -- parmaeter restore default by Change PAL Configuration
Problem:
1. Launch MassHunter GCMS Acquisition.
2. Change syringe.
(Change PAL Config -> Release terninal lock ->(change syringe) -> Lock Terminal)
3. Open PAL Parameter panel. The parameter resores default.
4. To recall the previous PAL parameters one needs re-load method to load the previous PAL parameter.
User may not realize "The parameter restore default value" because no message/no information about it.
Due to it, User may lost their correct PAL parameter.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Online help: no topic to TuneCheck to Sample Types in Seq table
Problem:
online help does not have contents about "TuneCheck" sample type.
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.06.00
Keyword:
One-line Description:
QQQ: [translation] some translation on tune report is not reported correctly.
Problem:
Tune report_EI auto tune report
1. Tune Date & Time: change the transaltion from“调谐数据和时间” Into “调谐日期和时间”
2. Tune File: change the translation from “数据路径”into “调谐文件”
3. Hexapole Accel: 六极杆加速仪-->六极杆加速
4.Iris: 光圈-->尾翼电压
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Cannot search " JPN strings" in tune report
Problem:
Open Tune report (PDF format) Find "アバンダンス" (translated "abundance") Cannot find it. English strings (eg. EI) can be found. (Search for word does not work all the time for translated text.)
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: "Invalid XML strings"
Problem:
Does not occur all the time, it appears occasionally.
Edit MS parameter.
select OK.
"Invalid XML strings" may appear on the display line. Nothing happens but the user may see this prompt.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ: PAL -- Undefined symbol: ok at the end of CTC method run
Problem:
Setup and ran a method with CTC-PAL injection. At the end of the run, one could see a Undefined Symbol: OK on the message line. It did not appear to cause any problems. If the method ended in an error (such as neither GC or MS data collected), I see the Undefined Symbol: OK in the logbook.
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QQQ: Sequence log has no sample type information in the summary report.
Problem:
Run Seq Seq log file does not have the sample type information.
Temporary Solution:
The user could cut and paste the infomation into an excel spread sheet and then print out the results.
Fix Information:
Fixed in revision B.06.00
Keyword:
One-line Description:
QQQ: PAL, Barcode: Software currently reads BarCode from a fixed vial location.
Problem:
Software currently reads BarCode from a fixed vial location. It should use the actual vial location that is known to the Sample Table Editor. "ReadBarCode$()" should use the fixed location when it is executed from the command line.
Temporary Solution:
User needs to use a fixed vial location to read the BarCode from the vial.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QTOF: The panel of Ion Source Selection doesn't appear automatically after multi-sources in re-configuration if it is NOT configured at the first time
Problem:
In user selects two or more ion sources in Instrument Configuration, the panel of Ion Source Selection should appear automatically and prompt user to select a correct source for the running instrument right after the application was launched.
Temporary Solution:
This behavior occurs ONLY for the configuration at the First time after the application was installed. For the re-configuration other than the first time, user must open the panel of Ion Source Selection manually.
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QTOF: Missing a print option to print out the TOF Calibration Results
Problem:
n/a
Temporary Solution:
n/a
Fix Information:
A text format of the results are automatically saved under the tune results directory.
Keyword:
One-line Description:
QTOF: For GC QTOF, missing steps on how to install a source when a source is not in the unit.
Problem:
Removing the Ion Source from the QTOF is based upon removing an ion source and placing a clean ion source back into the instrument. If the user wants to remove the source and not place one back in then an abort will need to be done. If the user would like to place a clean source into the instrument while there wasn't a source installed then the steps would not be correct.
Temporary Solution:
User needs to be aware if they abort the steps then the instructions may not match, but the re-installaton will still be funtional.
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QQQ: Lost connection to MS instrument if running EI with extractor ion source and Neutral Loss scan type
Problem:
n/a
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: Missing Method Tool for the QTOF for collision cell optimization
Problem:
Missing Method Tool for the QTOF for collision cell optimization Collision Cell Optimization Engeries
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: Cannot install MassHunter GCMS Acquisition to non-default location
Problem:
1. Install software to C:\y-gcms. 2. Indicate Data location to D:\y-MassHunter 3. Install is completed 4. Go into MS Configure Instrument, configure instrument 1as a (7890-7200) however "1" folder is not created under D:\y-MassHunter trying to launch Inst1. an error occurs
Temporary Solution:
Use default locations for installation of the software package
Fix Information:
Was resolved in B.07.00
Keyword:
One-line Description:
QTOF: Translation issues in Tune; TOF Mass Calibration, not all sections have been fully translated in Japanese and Chinese
Problem:
n/a
Temporary Solution:
n/a
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
SQ: Run/Resume Batch Gets Confused When Resuming on First LIne of Sequence
Problem:
In Drug Mode, started a Batch and then stopped it to edit the method. When selecting Run/Resume a Batch, It asks if one wanted to resume the aborted batch at line 1. Select No, and the batch was canceled.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: In manual tune loading from 'get defaulted value' may not work due to system set conditions
Problem:
n/a
Temporary Solution:
Reload from a known good tune value and then update with the new values.
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QTOF: The QTOF mass calibration result page is not fully localized
Problem:
n/a
Temporary Solution:
n/a
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QQQ: The number of injections displayed on 7890 panel and in GC parameters window do not match
Problem:
In MassHunter GC/MS Acquisition B.05.01, the method is initially set up to do two multiple injections. However when the method is reloaded, the GC Edit Parameters window shows only one repeat while the 7890 GC instrument panel shows two injections. Also the method stored along with data (txt file) shows only one injection.
Temporary Solution:
n/a
Fix Information:
The issue is fixed in version MassHunter GC/MS Acquisition B.05.02.1031.
Keyword:
One-line Description:
QQQ: Dual injection, if volumes are changed for front, must be filled in for rear also
Problem:
When setting up a dual injection sequence, if a value is entered to override injection volume for one of the samples in the front, the user must enter a volume for that sample in the back also. If not you will see the following message "Invalid injection volume specified: Back : 0" A blank volume in other cases means use the method value. No error message will be given if the front and rear injection volume is blank.
Temporary Solution:
n/a
Fix Information:
Was resolved in B.07.00
Keyword:
One-line Description:
QQQ: Wrong actual barcode in .CH file when running dual injections.
Problem:
When running a dual injection method (linked or unlinked), the .CH file from the second signal or rear datafile, shows the actual barcode from the front vial, instead of the rear vial. This issue is also observed when running sequence.
Temporary Solution:
A point patch (GC7890.dll and GC7890.pdb) is available as a temporary fix.
To install the point patch:
1. In the directory C:\GCMS\MSexe, rename the existing files from:
GC7890.dll to GC7890-orig.dll
GC7890.pdb to GC7890-orig.pdb
2. Copy the new files GC7890.dll and GC7890.pdb to the directory C:\GCMS\MSexe
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QTOF: Mass Range does not match Product Data Sheet
Problem:
Quad range was 20 to 1050 while the TOF has 15 to 1700. The screens in MS Parameters has 20 to 1700 which does not apply to either in the specifications.
Temporary Solution:
We allow a larger range for trouble shooting than we support for "specification".
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: User not warned about having scan range values below the TTI filter cutoff setpoint
Problem:
User not warned about having scan range values below the TTI filter cutoff setpoint
Temporary Solution:
Verify the cutoff range for the TTI filter is approximately the value of your low range in the MS parameters or it could result is a no response at the lower range.
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QTOF: Bakeout - At the completion of the cycle user must exit out and re-enter if they want to run again
Problem:
Bakeout - At the completion of the cycle user must exit out and re-enter if they want to run again
Temporary Solution:
At the completion of the Bakeout cycle, close the application and then click on Bakeout again if one will like to rerun the process.
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QQQ: Untranslate: 7000 Triple Quad, method report; title has English
Problem:
Print Method report to 7000 system. Triple Quad MS parameter is printed. the title has English. It has been same with B.05.02. Triple Quadrupole トリプル四重極 MS Parameters レポート MS パラメータレポート EM Saver EM セーバー Auto baseline subtract 自動的にベースラインを減算する
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QTOF: It is possible during manual tune depending upon the turn on sequence the filament is on and there is no signal.
Problem:
It is possible during manual tune depending upon the turn on sequence the filament is on and there is no signal. Changing the emission current and/or verifying the calibration valve is open does not display any response after pressing start.
Temporary Solution:
Exit out of the Manual Tune, Close instrument control, power cycle the GC Q-TOF (push the power button to off position, wait 10 seconds, push the switch so power is back on, wait about two (2) minutes), and now go back into instrument control.
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Welcome message is incorrect when there is no MS configured
Problem:
When I configure a GC only instrument (no MS), the welcome message states "Welcome to Agilent Unknown GC/MS Data Acquisition Workstation".
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QTOF: TOF HV Actuals, the setpoint versus monitors do not have monitors showing the accepted range
Problem:
n/a
Temporary Solution:
n/a
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
MSD: Offline Method Displays Wrong Instrument Configuration
Problem:
Offline Method Displays Wrong Instrument Configuration Offline Instruments shows the default configuration file for the offine instrumentation.
Temporary Solution:
To show the correct GC configuration the user will need to copy over the GC configuration files from the online GC instrument into the offline session.
Fix Information:
Was resolved in B.07.00
Keyword:
One-line Description:
QQQ: Cannot edit GC parameters during a run
Problem:
While a method or sequence is running, the user is able to bring up the GC edit parameters panel to view the parameters, but the OK/Apply buttons are grayed so changes cannot be made.
Temporary Solution:
A point patch (GC7890.dll and GC7890.pdb) is available as a temporary fix.
To install the point patch:
1. In the directory C:\GCMS\MSexe, rename the existing files from:
GC7890.dll to GC7890-orig.dll
GC7890.pdb to GC7890-orig.pdb
2. Copy the new files GC7890.dll and GC7890.pdb to the directory C:\GCMS\MSexe
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QTOF: Acquiring data files in 2GHz or 4GHz are tune centric.
Problem:
Acquiring data files in 2GHz or 4GHz are tune centric. Tune centric means the user will not be able to change the method parameters to change the data rate.
Temporary Solution:
Tune files are called via the Method, so to change the data rate which is being acquired the user will need to change the tune file which is being called. Each tune file name will need to be unique based upon the data type/rate being used for the method. It is also recommended when the acquisition mode is changed between 2GHz and 4GHz that a TOF mass calibration should be done. This can be done via a keyword in the sequence table.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: MH Acquisition B.05.02 crashes single injection or sequence with one CTC tray configured
Problem:
The instrument crashes with the error message "System.IndexOutOfRangeException - Index was outside the bounds of the array" when running single injection or sequence with one CTC tray configured and using: 7890 / 7000B / MH B.05.02 / CTC Driver B.02.01.1 / CTC FW 4.1.5
Temporary Solution:
A point patch (GC7890.dll and GC7890.pdb) is available as a temporary fix.
Fix Information:
To install the point patch: 1. In the directory C:\GCMS\MSexe, rename the existing files from: GC7890.dll to GC7890-orig.dll GC7890.pdb to GC7890-orig.pdb 2. Copy the new files GC7890.dll and GC7890.pdb to the directory C:\GCMS\MSexe Fixed in revision B.06.00
Keyword:
One-line Description:
QQQ: MassHunter Acquisition B.05.02 freezes during manual run
Problem:
MassHunter Acquisition B.05.02 freezes during manual run.
Temporary Solution:
A point patch (GC7890.dll and GC7890.pdb) is available as a temporary fix.
Fix Information:
To install the point patch: 1. In the directory C:\GCMS\MSexe, rename the existing file from: GC7890.dll to GC7890-orig.dll GC7890.pdb to GC7890-orig.pdb 2. Copy the new files GC7890.dll and GC7890.pdb to the directory C:\GCMS\MSexe Fixed in revision B.06.00
Keyword:
One-line Description:
QTOF: In MSMS mode the user interface will allow you to enter 4 digits but the MS1 is in unit mass resolution.
Problem:
n/a
Temporary Solution:
n/a
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QTOF: During the autotune steps the software shows the progress but does not show the area which is being tuned.
Problem:
During the autotune steps the software shows the progress but does not show the area which is being tuned.
Temporary Solution:
The tuning progress is shown via the Green Bar Status during the tune. Just below the lower left window the user can see what steps are currently being run. The section to which the steps are being done is not shown but could be determined if one looks at the Advanced Tuning segments.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ - Thermal setpoints higher than allowable readback....
Problem:
Manual tune window allow temperature setpoints of 360/210/210 to be input for source/Q1/Q2 respectively. However the sensors trigger a fault once the readback goes above 350/200/200 /- 2 degrees.
Temporary Solution:
Use the maximum values of 350/200/200 for the source/Q1/Q2 for the temperature setpoints.
Fix Information:
Resolved in revision B.06.01
Keyword:
One-line Description:
QTOF: Aborting Autotuning does not update the screen correctly, green bar process is not reset and voltages not turned back to starting point.
Problem:
If the user aborts an Autotune or Fast-Autotune it will terminate the program at this point and will not reset the status bar status. This is also true if the user uses the Advance Tune section of the software where the green bar status was not designed for. The Green Bar Status was designed to show the user the status of the Autotune steps.
Temporary Solution:
When the user starts the Fast-Autotune or Autotune the Green Bar Status will automatically reset to the initial conditions and shows the progress of the program.
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QTOF: "TOF Conditioning" icon appears on desktop when GCMS Acquisition Software is loaded
Problem:
TOF conditioning is for GC QTOF and TOF instruments. When the GCMS Acquisition software is loaded the desktop ICON will be placed on the desktop. This could give the impression to the user this could be used for GC QQQ instruments.
Temporary Solution:
When the user clicks on the 'TOF Conditioning' desktop ICON it will come up with a pull down dialog box. The pull down dialog box will only show GC QTOF/TOF instruments which have been configured. GC QQQ instruments will not appear or be a valid selection.
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QTOF: The acquisition software closed, there is no security even if actually running.
Problem:
After simulating a sequence, the user could click on the 'X' on the GCMS Acquisition software and closed the Workstation down.
Temporary Solution:
If a macro is running (which is the case if there is a method "running" or a sequence "running", the MassHunter GC/MS Acquisition will not close and an error message is displayed instead! If the user was editing the sequence table then there is no trap for closing the system down, the user will need to reload or recreate the sequence table which was being worked on.
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: Misconfiguration of an instrument will result in a connection but communication will not be possible.
Problem:
Instrument control checks for a valid IP address and then will bring up the Instrument Control Status Menus as well as showing the monitors for the configuration. If the configuration is not correct then the monitors will show "------" and when one clicks on the manual tune an error message of "Offline" or "Incorrect Firmware" will be displayed to the user.
Temporary Solution:
User will need to go into the MS Configuration and recheck the configuration of the instrumentation. With the correct hardware configuation the monitors will show the correct status information.
Fix Information:
Need to have the correct configuration or system will not report back the correct status information.
Keyword:
One-line Description:
QTOF: Failure of mass calibration in a sequence
Problem:
In the case of EI, the autotune process sets the emission current to a value appropriate for the pressure of PFTBA at the end of a 1.5 hour process, which is substantially lower than the value even several minutes after the valve is first opened. This is especially true if the system has been sitting idle for some time. Therefore, if a user launches a sequence that begins with a recal keyword after the system has been idle for a while, the recal is likely to fail due to saturated peaks. Since the previous calibration would be old, significant errors are likely. In CI this can also happen, but an additional similar scenario can result if the system is still approaching stability. On my system, I observed NCI ionization efficiency increasing dramatically over time, causing a reasonable starting tune to go into saturation over the course of several hours. Again, this resulted in recal failures during the sequence.
Temporary Solution:
n/a
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QQQ: Closing the "change configurigation windows in MassHunter" will lead to a not saved configuration.
Problem:
step to reproduce the error: - go to instrument --> Change PAL configuration - press unlock terminal - change something in the CTC-PAL configuration (i.e. a tray assigment) - press lock terminal and close the window using the red cross on the top right corner in this way the configuration is not uploaded, and can lead to wrong sample loaded.
Temporary Solution:
A possible solution is to remove the close red cross, in this way the user must wait until the real close button will be available.
Fix Information:
Was resolved in B.06.01
Keyword:
One-line Description:
QTOF: There are many untranslated strings in the tune parameter pane
Problem:
n/a
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QQQ - At the end of the autotune get an error message "Exception has been thrown by the target of an invocation. - Object is currently in use elsewhere."
Problem:
The error message is occuring while the system is trying to print out an autotune report. If connecting to a printer in network, the message "Exception has been thrown by the target of an invocation. - Object is currently in use elsewhere." came out always at the end of the autotune, no repot was printed out. While connecting to a local printer, the message would only appear when there was a communication issue with the printer.
Temporary Solution:
Use a local printer for the system, if a network printer is used then if there is a communication issue then the system will stop.
Fix Information:
Resolved in revision B.06.01
Keyword:
One-line Description:
QQQ - Reported values form the Air&Water check showing inconsistent information.
Problem:
The scan from the Air&Water check reports the following amu from Scan from report 18 5 5336 32 12 1224 69 82 3516
Temporary Solution:
The report was using profile data instead of scan data which will give different values and the Nitrogen amount is calculated out from the Oxygen reported which will be different from the display because the display will also show the Nitrogen from the collision cell.
Fix Information:
Resolved in revision B.06.01
Keyword:
One-line Description:
SQ: Allows Dual injection for Headspace
Problem:
Headspace can use only a single injection source at a time: front or rear. MassHunter GCMS Acquisition allows additional selection of Dual. This method actually runs but runs only the front vial.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
HS: does not remember 7319 HS license if configured as offline, then back to online
Problem:
Configure initially as online and enter HS license. Close session and configure as offline instrument. Reconfigure same instrument as online again. The IP is remembered, but the license is not and I must re-enter it.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Simulate sequence displays Method Path of the default path, not that of the sequence methods
Problem:
Create Methods that are stored in a different location: C:\GCMS\Methods. Do not change the default method path. Create a short sequence and browse to a method within that alternate folder. Save sequence. Simulate Sequence. The header shows the original default path: ' Method Path: C:\MassHunter\GCMS\1\methods\' This is very misleading. If it is the default, then it should say so. Probably true for Data path, too.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
HS: MSD with legacy HS does not include 'Set Tray position'
Problem:
MassHunter GCMS Acquisition/MSD Productivity Software with legacy Head Spaces' does not include any 'Set Tray Position' option.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Error in XML document (2,2,) on loading headspace methods created in previous build
Problem:
Load a 7890/LCV HS method that had been created in a recent previous build of MassHunter GCMS Acquisition. Get: '--------------------------- MethodUI Process.IsConsistent failure --------------------------- There is an error in XML document (2, 2). --------------------------- OK ---------------------------'
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: MassHunter GC/MS Acquisition does not invoke method resolution on cabling/uncabling of ALS/Tray
Problem:
7890B/7693 system configured, unplug the cable to the tray or ALS. No method resolution is invoked; nothing in logbook. Driver just silently resolves itself. There is not even a 'dirty' method flag. Close and reopen the session and only then does method resolution occur. Same for recabling. Even though the driver UI has updated if recabled, the sequence table ranges do not. Thus, saving the oddly resolved method to its same name, then starting a sequence using it fails with a range error.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QQQ: Foreline Pressure will not change to Torr
Problem:
If user changes the foreline pressure configuration to Torr, foreline pressure will remain in mtorr. Changing to another pressure display (Bar, Torr) will still display mTorr.
Temporary Solution:
n/a
Fix Information:
Resolved in revision B.06.01
Keyword:
One-line Description:
SQ: No Print Custom Report Option in the Sequence Table
Problem:
MSD Productivity Software had a Print Custom Report. Drop down box in the sequence table. There are no custom report options currently avaiable in the MassHunter GCMS Acquisition sequence table.
Temporary Solution:
User will need to define the report via the Data Analysis package with is being used.
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: no warning after change in instrument configuration when unable to configure the source
Problem:
When configuring the source after swapping, the source configuration window flashes and dissapears (does not allow to change configuration) without giving a warning that only one source type was configured in the instrument configuration.
Temporary Solution:
n/a
Fix Information:
Has been resolved in revision B.07.00
Keyword:
One-line Description:
SQ: Method print does not specify injector used
Problem:
A print of the method does not indicate which injector is designated as the specific source. The injection source is listed only as GC ALS. No mention of Front, Rear, or Dual.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Users need training in how MassHunter graphics work (Real-Time Plot, SCAN window, PROFILE window, etc.)
Problem:
1. Set up a run with real sample (MDL) with two saved signals; Front signal and Front-Back Signal, both of which were collected from the front inlet- front detector. 2. Set up for the first signal to be linked to large real time plot with default axis settings. Default Y-axis range from 0 -- 1 by tenths. (See pic) 3. Plot displayed large solvent peak but expected four smaller peaks not in evidence. 4. Opened Chromatogram Manager by right clicking on large plot. 5. Changed Y-axis range to 0 -- 20. Clicked OK. 6. No changed in Y-axis range of large plot. (Same pic) 7. Reran MDL sample. No change in result. 8. Set up delayed signal event to start posting after solvent peak. No change in large plot except to label point of signal start. 9. Printed Area Percent report displays solvent peak off the scale but smaller peaks remain not visible and indicated only by the time occurred.
Temporary Solution:
Double-click on plot area to switch between Normalized and Absolute modes of Y-Axis display.
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
QQQ: Compliance, Analyst I should be able to see GC Show/Hide Status Menu
Problem:
In Compliance mode and logged in as Analyst I, select the Instrument Menu. The option MS Show/Hide Status is Available, but GC Show/Hide Status is Not. If the user is connected to a 7890, this option should be available.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Print method only prints the saved method, it does not print any of the changes
Problem:
The parameters in the MS acq method report are from the saved file, not the current settings. If a method has been changed the report will be inacurate.
Temporary Solution:
When edits have been done to a method, before printing a method, save the method and then print the method parameters.
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Uninstallation needs manually open UAC windows to continue the process
Problem:
During uninstallation, UAC window does NOT automatically continue the processes; instead the UAC icon appears on the bottom bar without any message, and wait for the user to open it manually. If user does not pay attention for this icon, the process hangs forever.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: QTOF Firmware - Incorrect handling of IRM setting when there is no gas controller
Problem:
In an EI-only system (no gas controller), the firmware ignores an IRM setting to Vial 1. Instead the firmware sets IRM to OFF.
Temporary Solution:
Need to make sure gas is flowing or has been supplied for the IRM.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: GC Sleep Alert on connection should say 'GC' not 'Instrument'
Problem:
Connect to a GC/MS/HS system of which the GC is asleep. Alert advises: '--------------------------- Alert --------------------------- Instrument is in SLEEP mode. Do you want to Wake the instrument up? --------------------------- Yes No ---------------------------' I originally logged this against the HS, thinking it was asleep, but knowing that it was not. This wording should be clear about what part of the SYSTEM is asleep, in this case, the GC. 'Instrument' is much too general to be of any value.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: request for context-sensitive tool tip information for the 'Instrument Status' control
Problem:
The Status part of the GCMS Acquisition in the upper left corner is name 'Instrument Status' and reflects green, yellow, or red, reflecting any PART of the SYSTEM that is not ready or in a fault. This is too general to be of any use. I am told that the part of the 'Instrument' (also misnamed) will have a small light indicating which part is offending. A tooltip over the Status color would be additionally helpful since the indicator is not very obvious. (HS doesn't even have one.) However, what is now called an 'Instrument' can be comprised of several independent 'Instruments': the GC, MS, HS, CTC, 35900. Combined, they are a 'System', a more accurate term.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Stagger Keyword is Not Functioning
Problem:
GC Only EnviroQuant (Dual Injection) Setting a sequence that uses the Stagger Keyword, but it won't pass verification because the Dual Inj Vial column is blank (Rear vial 0 is out of range 1-100). It is not needed for the Stagger Option. The column can't be removed because the method specifies dual injection.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: GC Sleep/Wake menu items should activate only the relevant item; offer no qualifier; no log to logbook
Problem:
Menu items 'GC Sleep' and 'GC Wake UP' are both active. Only the relevant one should be active. Select either one and the action takes place if the GC is in the opposite state. However, there is no qualifier like 'do you wish to wake up the GC?' or 'Do you wish to put the GC to sleep?'.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
MSD: Make GC Method Printout consistent with MS Method Printout
Problem:
Currently, the layout of the GC Method printout and the MS Method printout are quite different. It would desirable to have a consistent look and feel to the System when one is printing methods and reports. The MS Method printout was well received and a request was made to make the GC one like it.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: 5975, Connecting to a MS that is already connected to
Problem:
While setting up a second GC/MS system using the same MS. Started up the instrument but did not receive any error - nothing was in logbook. Instrument Status was Ready. It appeared as if everything was OK, there is no indication to the user that the instrument is already in use.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Can't Run Unlinked Sequences: Undefined Symbol: dummy_name$
Problem:
When attempting to run an unlinked sequence, getting undefined symbol: dummy_name$.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ: System Verification result in PCI is incorrect
Problem:
The verification report could show Oxygen Abundance (Ab 22289) which is over the limit (100 counts); however the results section will show "OK"
Temporary Solution:
User will need to look at the abundance and limit to see if the values are within the range.
Fix Information:
Resolved in revision B.06.01
Keyword:
One-line Description:
SQ: Edit Entire Method... does not include Sample Prep, even when it has already been specified
Problem:
For any method, whether you have specified to add Sample Prep or not, select Edit Entire Method... Options do not include option to edit the Sample Prep dialog.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: When MS source or quad is not ready, statuses indicate ready
Problem:
Temperatures are not included in the set of criteria that determine when a SQ MSD is ready or not.
Temporary Solution:
Review the status display box to see all of the messages and status.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: No View menu item for GC only configuration after addition of DA
Problem:
Configure GC only and GCMS. Install Classic DA. Reconfigure both instruments. The Data Analysis icon is created on the desktop for both. However, there is no View menu item for DA selection within the GC only configuration.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: Scan Speed Method calculations and Actual calculations do not match up
Problem:
Scan Speed Setting Method Editor Calculation Actual Fast 20.0 12.42 Faster 22.7 15.05
Temporary Solution:
There are differences for N=0 and different scan ranges and this will show up as differences in the actuals.
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
QTOF: Selecting “single transient” will put the QTOF into a stage where you need to reboot the unit to be able to use the system again.
Problem:
Once you select the checkbox “Single Transient” (within the Acquisition tab from Manual Tune) AND then select the START button the counts display jumps up to about 10 * 9. After this the system does not react to any other software action and to recover a rebooted the QTOF from the telnet window.
Temporary Solution:
'Single Transient' is used for gain adjustment and should not be used for normal operation.
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
SQ: Allow CI Tune from Tune Icon
Problem:
the user is only able to do an EI Tune from the Tune icon.
Temporary Solution:
Clarification: The Tune icon should allow you to run the currently-selected (i.e., last) tune.
Fix Information:
n/a
Keyword:
One-line Description:
HS: HS Help Topics: Cannot find any file that matches either the OS culture or English; using default file name
Problem:
7890B with 7697 configured. Select Instrument\HS Help Topics. Get: '--------------------------- --------------------------- Cannot find any file that matches either the OS culture or English; using default file name --------------------------- OK ---------------------------' Click OK and 7697 Help opens. 'Overview of 7697...'
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QTOF: Instrument Status indicator shows incorrect sign: "Ready" in green when MS lost connection
Problem:
Depending upon how the communication signal was lost, the 'Ready' indicator may not show the correct status.
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
SQ: no indication on tune report that tune has failed
Problem:
Ran a 5975 autotune, the tune failed and the report printed. There is no indication on the report that the tune has failed.
Temporary Solution:
To see if the values in the tune report are valid, one should run the Tune Evaluation to check the Tune performance.
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: Source temperature of NCI rises during emission on
Problem:
There is a thermal equilibrium for the system. As a result, turning on the filaments (emission on) will cause the temperature of the source to rise if the previous setpoints used on the transferline, source and quad temperature are already at thermal equilibrium.
Temporary Solution:
To decrease the amount of temperature increase to the source with the turning on the filaments, one can decrease the temperature of the transferline and/or quadrupole or increase the setpoint temperature of the source.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Adding real time plots/monitors to instrument control are stacked
Problem:
When you add realtime plots or monitors to Instrument control, they are always stacked on each other.
Temporary Solution:
Use "Arrange Monitors" in Window menu to auto-arrange.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ: Changing default paths copies currently loaded file to new directory
Problem:
Changing the default method, data or sequence paths will also copy the curently loaded file to the new directory. If there is a file already there by that name, it will overwrite the file with no warning.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QQQ: Reset Counters panel in EMF Untilities Incorrectly specifies Pump Oil.
Problem:
In EMF Untilites, pump oil is in the Set Limits panel, which has it's own reset button. The Reset Counters panel shows pump oil as a selectable option. However, this panel resets the counters panel, not the limits panel, so pump oil is not reset through this selection.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: PAL Status menu item does not check/uncheck
Problem:
Select to view PAL Status. The menu item does not check.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: cancel on set tune masses does not cancel Tune Wizard
Problem:
If one hits cancel on the Set Tune Masses Dialog, you are sent to the next dialog and the Tune Wizard is not canceled. All the other dialogs cancel and return to Tune Window when you click cancel
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QTOF: Tune preview is inconsistent in showing disabled items
Problem:
Tune preview is inconsistent in showing disabled items. Some items are grayed out and others aren't.
Temporary Solution:
Go to the Mass Calibration entry and the viewable mass ions will be shown for the display. A maximum of six will be shown, the first six in the section.
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QTOF: Inserting a unicode control character in the QTOF method time segment table causes an error
Problem:
Using the 'insert unicode control character' context menu item causes an error.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: Validation in QTOF method editor needs additional checking for parameters.
Problem:
There are a few minor issues with the input validation in the QTOF method editor. 1. The run time range is given as 0.1 to 999.9, but won't take 999.9 as a valid entry. Same for the solvent delay. 2. The Centroid Data Thresold % will round 100.00001 to 100 and show an error icon. If 100 is entered after this the error will still be shown. If a lower value is entered then 100 will be accepted after it. 3. In the acquisition tab the range given for the acq rate is 0 to 50, but the field won't accept 0. 4. For targeted MS/MS the collision energy isn't limited to 0-60 as specified in the device info file.
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
SQ: Quick Tune Info appears in status line when click on Tune Icon in CI Mode
Problem:
When you click on the Tune Icon while in CI Mode, you get the correct dialog displayed.."Enter the CI Tune panel", but the information in the status line says this: "Tune MSD will tune the currently loaded tune file pcich4.u. Quick Tune adjusts mass axis and EM Only." This doesn't do Quick TUne, so that part is not applicable and should be ignored/removed
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: MSD Prod. Software to MassHunter GCMS Acq 5975 Method Migration not always clean
Problem:
Two methods were created in MassHunter GCMS Acq for a 5975 instrument (no GC). One of them is a Scan Method and the other is a Sim/Scan method. When trying to open both the methods in MSD Prod. Software (E.02.02 SP1), the SIm/Scan method loads properly, but the Scan method does not. In both cases a message saying "Edit entire message after method has loaded (or something like that)", which is fine. But, for the Scan method, "Acq - Global Lock Failed" message in the Status Line when selecting the edit method parameters icon. For Sim/Scan, the method parameters dialog.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Method editor doesn't fully validate chromatogram masses
Problem:
For several of the scan types the masses used aren't validated against the mass range supported by the QQQ. EIC - masses in the extracted mass or range can be above the upper limit for the QQQ MS1EIC and MS2EIC - the precursor range isn't checked and the product ion can be above the supported mass range BPC, MS1BPC and MS2BPC - excluded masses, product ion and precursor ion values aren't validated MRM - product ion and precursor ion values aren't checked to see if they are in the range supported by the QQQ
Temporary Solution:
Prior to running the method, validate the mass range(s) which have been specified.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Aux 1,2,3 Temp Monitors do not show Valve Box temps correctly; always green/Off
Problem:
GCMS B.07.00 , 7890 with heated zone plugged in and configured as Valve Box. Select Edit Monitors and view related Aux Temperature. Though the temp is on with a value, the monitor always shows 'Off'/green.
Temporary Solution:
Valve Box is not configured anymore as a Thermal Aux. You do not have a monitor for Valve Box.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: Execute => Ramp Lenses Graphs on printed report not labeled with name of lens ramped
Problem:
Execute => Ramp Lenses Graphs on report printout not labeled with name of lens ramped.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Run time is not counted up in software
Problem:
1. 7890B
2. Create a method. (Injection source = ALS), Signal 1 = FID
3. push "Start" button on 7890B HW
4. Signal is acquired,
In GC Status ; Run time is counted up,
but in SW, Status = Idle, Run time is not counted up.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Clicking Done in Manual Tune in Tune View does not prompt for Save Tune File
Problem:
When one clicks on the Manual Tune ICON in instrument control the Edit Manual Tune Parameters box will be displayed. Clicking on Done will prompt the user for the name of the tune file to be saved too. When one clicks on View and goes into Tune and Vacuum Control and then bring up the Edit Manual Tune Parameters box, clicking on Done here does not bring up the dialog box to save the tune file.
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
SQ: "Scan Speed" on Scan panel of Manual Tune is not consistent with the value in "Step size"
Problem:
The current values in Scan Speed comb box [6,50 (N=0), 3,125 (N=1) .....] is associated with Step Size 0.10. However, if Step Size is changed to 0.15, the options in Scan Speed are unchanged.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Function: Foreline Pressure; kPa ; significant figure is wrong.
Problem:
Configure 5975 Diffusion Pump When Fore line pressure unit = kPa, it is shown 0.004kPa because of the curernt "significant figure".
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Scan plot in manual tune shows incorrect information
Problem:
Although the scan range in Manual Tune settings and scan plot are correct, but the digital value being shown at the bottom part of the scan plot is not correct. This only happens in extreme cases, where there is no peak found at the first tune mass.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
QTOF: B.06.01 does not automatically create the TDA files at the end of acquisition
Problem:
The user must go into Quant to have the TDA associated files created and then go into QUAL even though they do not want to use QUANT. If the user is not careful then the files can be duplicated without the user realizing it and then when the original file is brought into QUAL and running deconvolution on it the system could lockup, about 75% of the time.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Tune Window Save function does not save text contained in graphics windows
Problem:
Information contained in graphic windows generated by capture, profile, etc, is lost when printed.
Temporary Solution:
All information shown in window text is saved in various CP variables.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Tuning ICON for the single quads is not the same type as in MS/MS or the QTOF
Problem:
SQ: Tuning ICON for the single quads is not the same type as in MS/MS or the QTOF The MS/MS and GC QTOF will launch a manual tune menu display while in Single Quad the ICON will ask the user what type of tune would you like to run and manual tune is part of the instrument control.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: GCMS always returns in Monitor mode following reconnection after Comm failure; somes crashes msinstcl.exe
Problem:
Connect to 7890 in GCMS. Disconnect the LAN cable. Following disconnection detection or when cable is reconnected, the software sometimes crashes: 'Msinstcl has stopped working'. If it doesn't crash, it always returns in Monitor mode.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Dynamic Ramp is blank if no tune file was loaded in Offline mode
Problem:
In Instrument Status "Offline" mode, the Dynamic Ramp panel is blank, until a tune file is loaded manually, even if the loaded method has already an associated tune file there. Also, all MS Params have default values associated with them too.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Sequence Table Assistant Contains Links To Missing File
Problem:
When the Sequence Table Assistant is launched on a PC where MassHunter Qual is not installed, an error saying that the spreadsheet contains links to the missing file 'MassHunter Reporting Qual.xlam' is displayed.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Sequence Table Assistant Problems when Installing MassHunter Data Acquisition onto PC without Excel
Problem:
When MassHunter Data Acquisition is installed onto a PC that does not have Excel, a shortcut to the Sequence Table Assistant is created, but when you click on the shortcut, Windows will display a error message that it does know how to open this file type (.xlsm). Also, without Excel, the STA spreadsheet and Help files will be installed to the C:\Library or D:\Library folder. If Excel is then installed onto the PC after MassHunter data acquisitiion, the Sequence Table Assistant will work, but help from the STA spreasheet will not work because it will look for the help file in the OfficeXX\\Library folder (Application.LibraryPath).
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: wrong column header on FlowSurvey.txt
Problem:
wrong column header on FlowSurvey.txt Ratio is done correctly but it shows the wrong ions
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: MSD editor panel, the EM default setting has issue
Problem:
configure 5977 MSD panel EM set as "EMV delta" the default relative voltage is -700. but the range is -500-500.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Stopping Run Method in Pre-run causes MassHunter GCMS Acq to hang
Problem:
If I have a method set-up with a GC/MS. Starting a run method. When the system is in Pre-Run (Run Status) and Instrument Status:ready, stop the run (using stop sign). Abort was recorded in the Log Book, but the system is stuck in the "Pre-run state" with Method xxx.m running. Only way out at this point is to Ctrl-Alt-Delete and kill it through task manager.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: Firmware geenrates error on method with many SIM time segments
Problem:
In MassHunter GCMS Acquisition when downloading a method with 100 sim time segment. Firmware show command error.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: While in Manual Tune view one cannot move the windows after clicking on EDParameters
Problem:
When the EDParameters screen is up and running, access to the other screens are locked out.
Temporary Solution:
Need to click on done, move the window to the new position and then start EDParameters again.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Open file in Qual before solvent delay results in error message
Problem:
Openning a data file while it is collecting and before the solvent delay Qual B.06.00 will display an error message about a missing file device.xml. Qual does not crash but the message will make customers wonder if the data file has been corrupted which it would be
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: it is confusing to users when you click on the tuning fork and it comes up with the Tune/Quick/Manual and you have to save
Problem:
When selecting the Tuning ICON one would expect to go into manual tune if one has a QQQ or QTOF instrument. Different instrument types has different functionality of how the tuning icon works.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Startup method behavior Always Upload GC method from Instrument
Problem:
Selected Specify Startup Method Behavior and selected "Always Upload GC method from Instrument". Shut down the software and started back up. It brought up a panel that requested User to "Press Yes to Upload GC Parameters from the instrument and overwrite the method" 1. It should not bring up this panel if one has selected "Always Upload GC method from Instrument" 2. It does not overwrite your method but creates a new startup method so the message is misleading. 3. If No has been stated to Upload GC parameters, it will download them instead.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: MSD Tune File Select (browse) does not show all parameters of the tune file.
Problem:
To see a preview of all the parameters just like the QQQ and the QTOF files one will have to go into the EDP parameters to view them. There is no preview of the tune parameters via the MS Parameters section of the software.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
MSD: Configured my GC as 7890 for offline, how do I know if it is a 7890A? 7890A+ or 7890B with the features
Problem:
MSD: Configured my GC as 7890 for offline, how do I know if it is a 7890A? 7890A+ or 7890B with the features For online instruments, the GC driver is automatically detected and will display the correct options for the 7890A --> 7890A+ --> 7890B. For offline instruments, instrument control will automatically default to a 7890A configuration.
Temporary Solution:
Copying a valid 7890B configuration file from an online instrument and copying it into an offline instrument will have the new features appear for the offline instrument.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: In SCAN window, "Speed" means either Samples (0 to 7) or Fast Scan (FS1 to FS3)
Problem:
"Type" means filter type. For Fast Scan FS1 to FS3, it will be "Fast"
Temporary Solution:
Fast basically means at this scan speed the normal 0.1 step size is not being used but 0.2 step size is being used.
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: At Instrument Control level, no visible way of knowing what tune file is loaded
Problem:
User can see what tune file is loaded by showing the MSD Temperatures, Method Edit or Edit MS Parameters dialog."
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Load Tune Wizard with default tune files, don't get Target Message
Problem:
When you select Tune Wizard from the Tune Menu Item with a default tune file (atune.u or etune.u) loaded, you get a window in which to pick masses. After clicking ok, you should get a message saying that "this tune file is not for Target tune" or something. You don't see the message if the tune files are the default tune files. Hitting ok brings you to the next dialog correctly. If you have a loaded tune file (named atunexxx.u or etunexxxx.u) and you select Tune WIzard, click ok on the masses, you get a message saying it is not a a target tune file. Click Ok and Tune Limits dialog are loaded.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Prompt for saving as tune reports *.pdf and *.xps now requires mouse click to be brought up
Problem:
Configure Printer for PDF or XPS and run a tune. The prompt at the end of the tune that pops up to ask you to save to a file never appears until you click the mouse somewhere on the UI. This could give the impression that the software has hung. Tune complete shows at the bottom of the Tune window.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Uninstalling the MassHunter GCMS Acq does not remove all of the Acquisition desktop ICONs
Problem:
Uninstalling the MassHunter GCMS Acq does not remove all of the Acquisition desktop ICONs The ICONs which have been left are not functional. Installing a new version of the MassHunter GCMS Acquisition will remove the old version of the ICONs and then create new desktop ICONs upon the configuration. This does not occur all the time, but when it does, it could be confusing to the user has the software been fully removed, yes it has.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: It is not clear what happens when a tune has been completed.
Problem:
One would expect to see the tune summary displayed and then click ok to continue, a hardcopy is printed but if the printer is not close then this could be an issue.
Temporary Solution:
Look at the prompt line and there is a statement which will show Tune is complete.
Fix Information:
n/a
Keyword:
One-line Description:
Sequence Assistance opening the file defaults to PatternConfiguration instead of SequenceTable Worksheet
Problem:
Sequence Assistance opening the file defaults to PatternConfiguration instead of SequenceTable Worksheet
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Manual Tune: Must start/stop scanning to incorporate changes to dynamically ramped parameters
Problem:
To see the effects of changing the dynamically ramp lens but when you enable this and start scanning it will take the initial values of the lenses and it will show up however if you start the editting of the dynamic it will not show up unless you stop the scan and restart it again.
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
SQ: When an old sequence table is loaded, the sample types are different
Problem:
When a sequence table from the MSD Productivity Software package is loaded into the MassHunter GCMS Acquisition different sample types will be assigned because of the different types which are now available.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: MassHunter sends garbled LUI:MSG:RECV 'xxxxxxxIdle' message to 5975/5977
Problem:
Information which is being sent from the MassHunter Workstation to the Local Control Panel (LCP) has word wrapped issues. The 5975 has two lines for display while the 5977 has 4 lines and at times the text is overwrapped due to the display types.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Dual vial ; no error message even when Front and Rear Vial is same
Problem:
1. Create a dual sequence. (Front = 1, Rear = 1)
2. OK to exit Sequence table
3. it is better error/warning message is shown when I click OK.
"Don't use same vial for Front and Rear"
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Selecting a different tune file...but the temperatures do not automatically change.
Problem:
After loading a new tune file with different temperatures, the MS Temperatures dialog is show. for the new Setpoints to be applied, the user must click "Apply"
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: CI gas purge takes longer than specified time
Problem:
The default purge time states the time will be 6 mins. But with the communication links this time is closer to 7 minutes not the 6 minutes.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Could not return to Instrument Control view from Tune View
Problem:
Started MassHunter GCMS Acquisition
Changed to Tune View
Loaded a new (CI) tune file Clicked on View \ Instrument Control
Got (expected) message - "Be sure tune file is save. Switch view now"?
Clicked "Yes"
Got (expected) message - "Update default.597x.m to use current tune file?"
Clicked "Yes"
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Monitors are hard to line up: spectrum, tic, scan 1-1
Problem:
If the window size is smaller than all of the current monitors being displayed then positioning the spectrum, tic, scan 1-1 monitor box will be difficult.
Temporary Solution:
Expand out the window so all of the monitors can be seen and then auto align the monitors.
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Need to have an autosave of the tune report to PDF automatically
Problem:
Started a sequence and walked away and came back and found the sequenced has stopped because it was waiting for a PDF file name. The system should automatically save a PDF image of the file under the directory so that it will not stop the sequence.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
PAL: For CTC multiple overlap - Don't inject on a barcode mismatch and continue sequence is invalid
Problem:
For a CTC multiple overlap sequence with barcodes, if there is a barcode mismatch and Don't inject is selected in the Start Sequence panel. the sequence will be aborted regardless of the users selection of Continue Sequence. Not sure if this should be noted somewhere.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Tune Report in View tunes to have extractor data
Problem:
In tune & vacuum control, select "view tunes" from file menu. Tune Report spreadsheet is opened. Click over to EI Lens Value report. The extractor and body voltage data is missing.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: TuneMS and Tune Menus are inconsistent
Problem:
When you enter tune from the Tune Icon or the Tune Menu item in Instrument control, the tune window has a TuneMS menu. In this menu, the following tunes are not listed, but are listed in the Tune Menu in the Tune and Vacuum View: Extraction Tune lomass autotune BFB Autotune
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Tune evaluation only evaluates autotune; evaluation results is based on an autotune.
Problem:
load etune, run tune evaluation from the tune menu of tune and vacuum control. The system only evaluates the atune file, not the currently loaded tune file
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04 This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
SQ: SimAcq doesn't set the scan window x axis range to include all ions
Problem:
The scan window's x axis is left at whatever the range was from the last scan command. It should be set to include all the ions listed in the SimAcq command. The data is acquired for all the ions, it just might not be displayed depending on the previous scan commands and the range of the ions.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Two copies of method are being saved if Save Method with Data is checked
Problem:
If Save Copy of Method with Data is checked in the Method Information screen, when the method is run two copies of the method are saved. One in the .D folder and one in the AcqData folder.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: While in Manual Tune, can't click directly on ramp Graphics Window to select a new maximum.
Problem:
While using the EDP and ramps the user will need to manually update the values into the EDP parameters section. One can click on the ramp plot and the value will appear and be highlighted but it will not be transfered to the EDP, this needs to be done manually.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: mass gain values for the speeds are stored in the smartcard not in the tune file
Problem:
If someone is tracking the mass gain values for different speeds the tune reports must be kept because the values are not saved in the Tune View Files nor in the tune file, the values are saved in the SmartCard and will be overwritten by the next tune.
Temporary Solution:
n/a
Fix Information:
MassHunter GCMS Acquisition B.07.00 Data Analysis Quantitation and Qualification . . Update notice
Keyword:
One-line Description:
SQ: Undefined symbol: dottune may appear, false error message.
Problem:
In the Tune Window, when you select Tune MSD from Instrument Control, the TuneMS menu item has Target Tune as an option. Selecting Target Tune gives you a undefined symbol: dotune Nothing bad happens, but just a false error message.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: LCP -- text is being wrapped around the display when communication is first being started
Problem:
SQ: LCP -- text is being wrapped around the display when communication is first being started
When the Bootrom comes up the word Loading is being wrapped around the display
.....lo
ading......
Temporary Solution:
This is just a visual flaw, the unit is fully functional and there are some other prompts and messages which does the same thing.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: add warning if user saves method in a format that will not run
Problem:
Currently, the user is allowed to save a method with xxxx.xxxx.xxxxx.m or something similar. the method saves and can be loaded and reloaded without issue. However, the method will not run and gives the impression that the system hangs when the user tries to RunMethod.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Checking/Unchecking "Use MS" option does not update icons reliably
Problem:
Check or uncheck the "use ms" option under the Inlet type icon, the MS icons are not updated reliably. Unchecking "Use MS" will cause the user to wait or perform mouse actions to gray out MS icons. Checking the "Use MS" (with icons grayed out) will not enable those icons until the user closes and restarts MassHunter GCMS Acquisition.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Edit Entire Method 'Instrument Information' does not remain checked
Problem:
On occasions when doing the Edit Entire Method the 'Instrument Information' does not remain checked.
Temporary Solution:
Going directly to Instrument Information, make the edits and save.
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: LCP of MS not updated
Problem:
LCP of the mass spec is not always updated. For example, bringing up the vacuum dialog and selected Vent. One can see the temps going down and pump off and eventually the panel showed vent cycle complete. However, looking at the LCP of the mass spec it shows vent prepare.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Print report produces bad report in CI
Problem:
Printing a report in CI starting with the reagent gas off, the wait is not long enough to establish the gas flow, and as a result the profiles for Quad 2 (which are done first) are bad.
Temporary Solution:
If you repeat it, it will look fine since stable flow will have been establish by then. Also, the report looks fine if the user starts with the gas on.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Deleting entries in dynamic ramp table doesn't work well
Problem:
When one tries to delete multiple entries of mass/voltage pairs from a dynamic ramp table, it often doesn't delete them all. For example, make 6 entries, highlight 4 and delete. Only the last 3 are deleted. If you highlight the retained one and delete it, however, it is deleted, so that is an acceptable workaround.
Temporary Solution:
If you highlight the retained one and delete it, however, it is deleted.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ: Aquisition dwell time parameter can't be adjusted to lower limit
Problem:
The acquisition dwell time parameter has a lower limit of 0.016 ms and a step size of 0.01 ms. The step size means the lowest value the slider can reach is 0.020 ms. So the limits displayed have a lower value that is unattainable. Also, sometimes this setpoint does say 0.016 ms until the user attempts to adjust it, then it jumps to 0.020 ms and 0.016 ms is never seen again. This is not reproducible but has been seen several times.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Peak logging produces invalid data
Problem:
While logging a maximum of 10 peaks to a file by checking the appropriate box. One of the files contained spurious values. Specifically, several of the lines have 0 as the target mass.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Object instance error happen when stopping Seq (CTC)
Problem:
1. CTC Seq start (5 line seq) 2. Abort Seq at Line 3 3. Line 4 is start, Stop again. 4. Objenct Instance error happens. (See CTC_Seq_abort.jpg) 5. Close MassHunter GCMS Acq, restart MassHunter GCMS Acq, but 7890B is monitor mode. 6. check 7890GC front panel, shows some message 7. unless pressing "User key 1" twice on 7890B HW, MassHunter GCMS Acq can not make 7890b online, becasue 7890B is monitor mode.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: The software installation does not allow the user to specify where they was to install the core software only the data/supporting files
Problem:
On newly installed systems the MassHunter GCMS Acquisition installer will prompt the user where they would like the core software to be installed. Once the Classic Data Analysis software has been installed the installer will see where it has been installed and then will install the core portion of the MassHunter GCMS Acquisition to the same location. So if you do not see the prompt for the core software installation, then the MassHunter GCMS Acquisition detects the installation fo the Classic Data Analysis software.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: If the wrong printer/driver is being used then the numbers in the tune report can look truncated.
Problem:
If the wrong printer/driver is being used then the numbers in the tune report can look truncated; this can be seen in the number fields. If the field is center justified then it looks okay but if the field is right justified then it will appear as the last column of pixels have been deleted.
Temporary Solution:
Use the correct supported printer driver for the system.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: error prompt box gets hiddens by the instrument control window
Problem:
error prompt box gets hiddens by the instrument control window; if one is not careful the prompt box could be moved and the user may not be able to see it.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
HS: MassHunter GC/MS Acquisition does not update Instrument Status following HS reconnection in-session
Problem:
Start 3 line sequence and at the conclusion of the first run, either unplug the LAN cable from the HS or power the unit off. Status goes 'offline' and logbook shows this. Following the 4 min wait to abort the sequence, recable the HS or power it back on. HS Status updates, but Run Status and Instrument Status continue to show 'Offline'. Start a sequence, but it aborts. Instrument Status eventually updated to Ready following power cycle reconnection, but not the Run Status. Must close and reopen.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: 4 min wait to abort sequence following comm interrupt
Problem:
When there is a communication lost, like a lost LAN connection, it can take about four (4) minutes for the system to abort from the sequence due to the reconnects.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: MSD failed to reconnect after several disconnections/reconnections
Problem:
About 3 or 4 successful disconenctions/reconnections (by removing LAN cable from my PC). On the next reconnect, got an "in use by" message, with my computer name and IP address
Temporary Solution:
Try to reconnect a couple of times If this fails, close MassHunter Acquisition and start up the instrument control again If that fiails, close MassHutner Acquisition, power-cycle the MSD, wait 2 minutes, then restart MassHunter Acquisition.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Drug Quant: Copying of sequence table copies non-DQ sample types
Problem:
Build a sequence table in drug quant select some of the DQ specific sample types (eg specimen, blank), copy, paste into excel. The non-drug quant equivilants are pasted.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: In the MSD Tune Report, Profile and Scan windows have poor scale
Problem:
These windows are scaled to an arbitrary size instead of the actual area on the report in which they are to be plotted.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Capturing data via EDP, in the window for Capture the usec always has 0.00
Problem:
Runnning the EDP with Capture,the number of points from 1000 to 10000 but the usec in the display window always stays at 0.00. The capture information is correct.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Automated quant reporting with .m method files
Problem:
Create a quant method save as .m format & .quantmethod.xml format. In acquisition, use the method file as the DA method file. The .quantmethod.xml file generates the proper report the .m file generates the generic qual report
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: LCP Display Times do not match actual date. LCP has 2/14/2013 when date is 2/16/2013
Problem:
LCP Display Times do not match actual date. LCP has 2/14/2013 when date is 2/16/2013 instrument available states 2/14/2013 is the date, but when you go to manual tune it will display the correct date and then instrument available will come back with the wrong date. The LCP has a memory stack and is displaying the wrong line. There are no errors for the acquisition times because they all get the timestamp from the PC and this is correctly being implemented.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Printing "Detailed Data Analysis method" w/ no printer results in error in status line
Problem:
Trying to delete "Detailed Data Analysis Method" section of the method with no printer attached, the following error message will appear in the status line: "Cannot delete methods\methodname\damethodprint.txt The reason why it appears is that there is no file by that name.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: In Run Method Panel, estimated disk space is reported for D: and value is actually C: capacity
Problem:
When selecting Run Method, the estimated free disk space is identified. In MassHunter GCMS Acquisition, it is specified as the D:\ or the data path selected. If D:\ is selected, the free disk space that is actually reported is for the C:\ drive NOT the D:\ drive. If you change the data path to C:\ the same value is reported correctly for the C drive.
Temporary Solution:
User can go and user windows explorer to view the available free space on the selected drive.
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Vent/Pumpdown from Instrument Control, get error in status line about Vent Prepare
Problem:
Venting the MSD from the Vacuum Dialog, and then pumped down, without power cycling the instrument. After clicking Pump Down, the following error appeared: ERR.LUIVentPrep_Not_Active No bad behavior happens because of this, but the message does persist and could cause confusion.
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
SQ: Pause batch if calibration expired is not working with Intelligent Sequencing and classic DA
Problem:
Intelligent Sequence set to Pause batch if calibration expired. Set up a sequence with two specimens. Ran the sequence and got message that the current calibration is out of date, responded Yes to continue. When prompted, chose a Med Control. Instead of pausing the batch, it asked for a reinjection.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package
Keyword:
One-line Description:
SQ: Ramping in Emission for CI system runs in improper manner
Problem:
5977: MS firmware 15
Ramping in Emission for EI system runs properly; but
Ramping in Emission for CI system runs improperly, the ramping curve is almost a straight without maximum;
5975: MS firmware 7.02.17
Ramping in Emission for EI system: NOT tested;
Ramping in Emission for CI system runs improperly, the ramping curve is almost a straight without maximum;
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Running CI Tune Report Options prints blank reports after first tune
Problem:
In EI, you get a message that you need to run the tune twice to see the customized tune reports (lens value, etc). In CI, the blank plots are printed after the first tune and no indication is given its needs run again.
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
SQ: In Manual Tune, the Step Size Edit box on the Profile Tab erroneously controls the step size for Scans, not Profiles.
Problem:
To control the step size for profiles, use the CP CFommand "stepsize" before entering Manual Tune. For example
STEPSIZE .05
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Changes to Profile scan speed not persisting in Manual Tune
Problem:
Go to Profiles tab Make sure that speed N=3 is slected Click "Profile" to start running profiles Change speed to N=7 -- you will see profiles slow way down (correct) Click "Profiles" again You will see profiles being run at N=3 speed (this is incorrect)
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Non-responsive UI when stopping scans, profiles, captures and ramps in Manual Tune
Problem:
After you click the "Stop" button, UI is fairly dead until the operation completes. This can be maybe up to a minute or two for a wide scan at .05 step size, or especially a ramp with max number (~256) points.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Index 2000 out of bounds at the end of sequence run
Problem:
5977/7890B/7693 (Drug Mode) Ran 2002 line sequence, and when checking the software, the sequence status bar was still in "running" mode with 2002 out of 2002 lines run. The status line said "Index 2000 is out of bounds."
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package
Keyword:
One-line Description:
SQ: Safe Handle Message and Crash of MassHunter GCMS Acquisition during sequence run
Problem:
Running fastest method on a system over the weekend. System got through 408 runs (less than 24 hours). The MassHunter GCMS Acquisition aborted when okay was selected.
Temporary Solution:
Data handling was errantly set-up to "Screen Print" a library reports, which caused many instances of the MultiVu application to be invoked. Furthermore, Alert boxes were displayed warning the user of a near out of memory condition and a swap bound system. Warning messages were display, but if the user was not near the system when the error messages were being display then an abort of the sequence could result.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Help for keywords in Drug Mode
Problem:
There are a number of keywords in DrugMode that are not in the help; Append, BatchRep, NewBatch, ReQtStds, etc. There are also keywords listed that are not in Drug Mode.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Help inaccurate for keywork UseDecisions
Problem:
According to Help for keyword UseDecisions "UseDecision is only applicable for MassHunter Data Acquisition sending data to MassHunter Quant. When working with MassHunter Data Acquisition in Drug mode sending data to ChemStation Data Analysis use Intelligent Sequencing instead." This is not true. The user must set up the sequence with the UseDecisions keyword when using Classic Data Analysis also. The use of this keyword will invoke Intelligent Sequencing. There is no more turning Intelligent Sequencing on/off in the method.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Strange Hivac gauge reading when conducting commands on CI systems
Problem:
When conducting commands, strange HiVac gauge reading (such xxe-10, or xxe-09) appears on software and LCP occasionally. The chances of this error appearing depends upon the orders and time-gap between the consecutive operations.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: During Tune, got "MS Communication Errors" flashing on status line
Problem:
During the tuning on the line prompt an error message "MS Communication Errors", tune completes fine, then reconnect, "MSD was already connected" in status line.
Temporary Solution:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: AutoTune does not use a secure default mass profiles for the tune, it uses the user entered values from profiles
Problem:
If one changes the profile masses and saves the tune file, the tune file will then use those new profile masses for the tuning masses which could result in an abort or end of the autotune.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Calibrant valve status on autotune report are consistent between EI and CI
Problem:
On EI system, atune Autotune report, "PFTBA" is "Open"; On CI system for both PCI and NCI, autotune report, "PFDTD" is "Closed". When tune is completed the calibrant is turned off.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package
Keyword:
One-line Description:
SQ: Enter out of range mass errors for Target Masses, inconsistent error handling
Problem:
If a out of range mass is entered on the Target Mass dialog from Tune Wizard, an error prompt does not appear like the other Tune Wizard dialogs. The only way you know there is an issue is that the dialog closes and there is a message in the status line. From the other dialogs, you get a "parameter out of range" dialog and then are brought back into the offending dialog.
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
MSD: Warning messages about certain icons appear during uninstllation of Acquisition software
Problem:
During MassHunter GCMS Acquisition uninstallation, the instrument icons and “QTOF Conditioning” icon will be removed automatically; however, three icons for Configuration, STA and Parts Finder are not go away automatically until clicking “OK" on the message box. This does not occur all the time.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Missing help information about the right key functions for Capture window on screen and search
Problem:
Capture window right function keys are missing help information.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Missing help information about the right key functions for SimRAMP window on screen and search
Problem:
Missing help informaiton on the right key function on the SimRamp window.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Missing help information about the right key functions for SCAN window on screen and search
Problem:
Missing help information for the right key functions.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ, Missing help information about the right key functions for Profile window on screen and search
Problem:
Missing help information about the right key functions for Profile window on screen and search
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Missing help information about the right key functions for Text window on screen and search
Problem:
Missing help information when using right function keys.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: User needs to make sure Graphic windows have stopped acquiring data before switching views
Problem:
The user can right click on the graphic windows options (SCAN, Profile, SIMRamp, Capture) to perform a single or continously acquisition. This is very important for troubleshooting and optimizing a tune. Before switchin the view (from instrument control to tune and vacuum control or the reverse) the user needs to make sure the acquisition has stopped. There is an MSOFF command which is implemented during the switching of the views and this could disrupt the software by creating a fault.
Temporary Solution:
The user will need to select stop acquisition prior to switching the view.
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Tune Error on bfb_autotune, extra dialog saying "Starting Autotune", but nothing happens
Problem:
Ran a bfb_atune on 5977 and a Tune Failure Message appeared: "Couldn't achieve ion Focus. Check Calibrant and lens connections." Hit Ok. But another dialog appears saying, "Starting Autotune". Hit Ok. The MS is turned off (status line), but nothing happens. Software is not frozen, can move between screens, etc. This could leave the user wondering why their autotune isn't running. Is it supposed to run? Or is there just an extra dialog? The second dialog box should not have appeared.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: .Net Exception When Clicking in the SIM Time Segments Table
Problem:
5975 Method Ediror panel: The SIM Time Segments table is difficult to manipulate if you are not used to it - different from G1701EA, Clicking around trying to get the time field to become editable, one can get a .net exception. After selecting Continue on the excption, ok and cancel were no longer functional, but one can close the panel from the X. Reopening the panel, it was fine.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Timed Events, EMVolts Monitor for Gain Factor does not match EMVolts specified on TIC
Problem:
Timed events for Gain Factor. When the method runs the TIC Shows the events labled with EMVolts 1103 and EMVolts 969, but during the timed events, the monitor showed 1106 and 965. All other events like Absolute EMV and Delta EMV had matching voltages.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: GC MS Acquisition IQ fails after FA uninstall
Problem:
After uninstalling MassHunter GCMS Acq, an IQ test was run. It fails with 1 file missing in GC MS acquisition.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: DrugQuant: Help Button on Post Batch Report Panel Not Working
Problem:
When you select the Help button on the Post Batch Report panel nothing happens.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: DrugQuant: Canceling the Save Batch Panel Causes Undefined symbol when Selecting Simulate Batch
Problem:
Testing the menu items by opening and canceling them. If one selects Save Batch and then cancel the panel, then going to Simulate Batch undefined symbol: pauseseq. This will occur when selecting either the menu item or the icon.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: No Cancel button on Method Resolution panel when loading the method
Problem:
Have a valid method loaded in Drug Mode, ran a simulted batch. Then attempted to load another method that brought up Method Resolution. The method resolution panel had no Cancel button . This does not occur all the time.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: No way of stopping sequence while waiting for an interval
Problem:
Setup a sequence using the interval keyword. First sample ran and then "Waiting for interval xxx" appeared on message line. During this time while the software is waiting the specified interval time before starting the next run, the stop button is grayed and there is no way to stop the sequence.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Shortcut Error Uninstalling MassHunter GCMS Acq from a Clean System
Problem:
When uninstalling MassHunter GCMS Acq from a clean system (nothing else was installed with MassHunter GCMS Acq), an error that says shortcuts could not be removed. The uninstall continues, but one is left with the extra icons that install with MassHunter GCMS Acq like Parts Finder.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Front Only inlet is available after configuring Headspace, though both inlets are available up to that point
Problem:
A GC with dual 7693's, no tray. Both GC ALS inlet sources are available. Create a Back ALS method. Close and configure with a headspace. Open session and both inlets are still seen. Create a front HS injection source method. Reload the Back ALS method. Select inlet/injection source and only the Front Inlet is available, though both ALS's are seen in ALSL and Configuration. Saw this on multiple GC's with different types of HS. The only way to escape is to deconfigure the headspace.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: No way to confirm import of method component(s) imported prior to save
Problem:
B.07.00. with Qual and Quant installed to activate 'Import method components from another method'. Select this and for any element, there is only a Save As dialog presented. User should be able to verify the display of whatever he imported before he is required to Save the method. The only time user sees the Method Edit dialog is if the import invokes Method Resolution.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Clicking "Cancel" button on "Printing" panel doesn't work and hangs the process if "XPS" is set as default printer
Problem:
1. Set XPS as default printer; 2. After tune is completed, TWO panels appears: “Printing” and “Save the file as”; 3. click “Cancel” button on “Printing” panel, nothing happens and it hangs in “Canceling Print” forever until user clicks “Cancel” button on “Save the file as” panel again. The problem is: during tuning, user may perform others operations, the panel “Save the file as” may hide behind tune panel and invisible for user; so user has no way to continue anything unless kill the application.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: PC fails to reconnect to MSD
Problem:
If the PC leaves the MSD in a "BUSY" state, the PC and the MSD are supposed to be able to reconnect. The MSD accomplishes this by telling the PC this by who it is in use by telling MassHunter GCMS Acq who it is "BUSY" with
If it is the PC running, then MassHunter GCMS Acq can try to reconnect
If it is another PC, then MassHunter GCMS Acq can tell the user who the MSD is in use by.
Unfortunately, when the MSD is reporting who it is in use by, it is clipping the computer name
Instead of reporting: "5CB20404CM.scs.agilent.com", it reports "5CB20904.scs.agi". This in turn cause MassHunter GCMS Acq to *NOT* try to reconnect and to erroneously show an "In use by 5CB20904.scs.agi" message.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: CI Reagent Gas B and Load Method yields undefined symbol : line
Problem:
use the CI tune wizard to specify reagent gas on Line B. Save the tune file. Switch to Acqview and specify that Line B tune file is to be used with the mehtod. You will get an undeifined symbol: Line.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Message in logbook with sequence calling a GC Wakeup
Problem:
GC/MS was asleep. Setup a sequence with keyword GC Wakeup as the first line followed by two samples. Ran the sequence. The sequence completed but when looking into the logbook, this was the last line. Time Stamp Source Message 2013/03/11 14:27:35 Sequence has not be reloaded because instrument is sleeping Sequence did complete but the logbook would indicate that it was not done.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Click on Ramp window, value is not saved in tune file
Problem:
A manual click on a ramp window should save that value into the tune file in memory. Which, in turn, may be persisted on disk.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Sequence hangs waiting for arm signal - intermittent
Problem:
The MS Status panel was displaying " Arming instrument for start of run" on occasions. The 1st sequence stalled at 22:30:03. The 7890B entered sleep mode at 5:25:17 during the next morning. The sequence was aborted at 10:11:38. Normally, the sequence would resume running at the next sample, but this sequence got stuck in pre-run for the next sample. The GC stayed asleep, despite our effort to wake it up through the command line. The red STOP sign was grayed out, so one had to use Task Manager to kill the msinsctl.exe program. This time the 7890B had not entered sleep mode. Both the GC and the MS status icons were green and the CTC was displaying blue for Running. Was able to abort the run and resume the sequence at 15:08:22 on Sunday afternoon. Then the sequence of 303 runs ran to completion.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Still possible to see HIVAC Pump not ready when running sequence after GC/MS asleep
Problem:
When running a sequence after the GC/MS had been asleep, it is still possible for the sequence to error out with the following error : MSD Fault -- 0X0000000000000080 HIVAC Pump Not Ready ----. It may depend on your sleep and wake methods. For most cases, the steps work, but on occasions it might fail.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
QQQ: Check "All peak Data in one file" only in Log Files section but no any log file has been created after autotune of QQQ
Problem:
1. Check "All peak Data in one file" only in Log Files section, do NOT check other checkboxes; 2. Run autotune; 3. No any log file has been created after autotune (expect that one relatively large peak_xxxx.txt file should be generated)
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: SIM/SCAN: data collected from first SIM group only
Problem:
Build a method in SIM/SCAN. Add multiple sim groups with different SIM ions in each group. Data is only collected for the SIM ions from the first group for the duration of the run. This also applies to data being collected from SCAN from the first group for the duration of the run.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Depending upon when override solvent delay is selected, either a slow response or lockup could occur.
Problem:
The issue is when the override solvent delay is selected prior to the solvent delay. The closer the override solvent delay is selected to the solvent delay there is an issue possibility of a run time delay being shown in instrument control or there could be a lockup of the system.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: 7890B vent method will be terminated during venting if switch masshunter view from "Tune and vacuum control" to "instrument" control
Problem:
7890B-5977A Vent the system from Masshunter a vent method will be loaded to 7890B.However if swtich the view to "instrument control" view the vent method will be terminated and transfer line teperature will increace following the previous GC method. And 7890B FRONT PANEL IS STILL BE LOCKED IN VENT STATUS. That' means you can't modify the setting value from front panel e.g. transfer line temperature can't be turned off. The only way is change the settign from Masshunger then load it to GC.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
MSD: The compliance for Masshunter GC ACQ does not have an IQT reference file and is not listed as add-on
Problem:
The compliance for MassHunter GC ACQ does not have an IQT reference file and is not listed as add-on. Only the registry entry is set and no file is installed as a reference file cannot be created.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ, Cannot enter the serial number of the MSD 5977A which is US1301L001 into the 7890B Aux Detector
Problem:
When you use the GC Panel and try to enter the serial number it will only allow numbers, the serial numbers for our MSDs has numbers and letters in it so it is not possible to enter in any 5977 serial number into the field.
Temporary Solution:
Instead of entering a Letter for the MSD serial number use a number like 0 or 1 for the letter.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: The turning on theSleep and Awake does not operate consistently when repeated
Problem:
When instrument control is started, sleep from the pulldown menu item is activated both the GC and MS go to sleep immediately, and then when you click on awake they both will come up. Without exiting instrument control, start the sleep mode again from the pulldown menu item the GC is activated immediately but the MS is not, it will take at least 2 minutes before it will detect the signal and display sleep but it may or may not start the powerdown of the turbo pump, this part is questionable at times also.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Why after clicking on Awake, why does the vacuum readings improve by almost 2 orders, this is not correct.
Problem:
The instrument is around e-6 for the vacuum and then when the awake is used the vacuum readings go to e-8 and then it will go back down to e-6, what makes this even stranger is that the system is also doing a pumpout at this point of time.
Temporary Solution:
What the user is seeing is the gauge was turned off and it was causing the values to get lower and then it was turned back on and it was recovering. This is the normal response for the system.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ,QTOF: "restart paused sequence" menu item missing for QQQ/QTOF/GC only
Problem:
The Menu item: Sequence\restart paused sequence should be visible for all instruments, not just MSD as it is currently. This menu item is normally grayed, but visible for the MSD, and only becomes enabled if you have paused a sequence. behavior should be the same for the other instruments. For the GC only (as an example), the only way to restart a paused sequence currently is to "Run Sequence" and then you are prompted to resume at the specified line. From ken: The ‘restart paused sequence’ does appear to be for a single quad configuration ONLY; I view this as a defect. Should be active for all instrumentation (QQQ, QTOF, GC only)
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
MSD: Add Zipcrit and Problem Steps Recorder items for all instruments (QQQ, QTOF, GC only)
Problem:
The Zipcrit and Problem Steps Recorder menu items and feature are only present for MSD configurations only.
Temporary Solution:
Testing "Gather diagnostic files" on two QTOF systems, System A with MSD Data Analysis software installed, while System B not (for QTOF users, it is normal). After clicking "Gather diagnostic files" and selecting certain options, a log file is created with extension .z in System A, while a file with extension .gz is generated in System B. The file with .z can be opened in System A without software from third party, while the file with extension .gz cannot be opened until a certain software from third party is installed.
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
QQQ, QTOF: Vacuum ICON on instrument control does not work
Problem:
This was a feature which was added for the 5977 instrument and it is part of all of the configurations now. Does not function for either of the QQQ or the QTOF
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
EMF Monitor is no longer available.
Problem:
This ICON has been removed from all MS Types and the pull down menu item under Instrument call EMF has also been removed. The 7890B has DComm between the GC and MSD which means we now have the capability of the GC storing maintenance items. The first product with this feature is the 5977 and as we expand the functionality and update firmware on other MS Types we will be adding this new feature.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: instrument control, profile, continuous, then switch view to tune and vacuum
Problem:
the profile scan was going continuously in instrumnent colntrol then I clicked on view to go to the tune and vacuum view. When it was done, I could see Welcome to Tune at the bottom of the screen and the profile has stopped. I right click on the profile window and it stated that I had to do a profile stop but it was already stopped. Had to type in MSOFF on the commandline to recove, or just click on profile stop.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: MSD I/O Time Out when running N=6 and N=7 scan speed methods
Problem:
Running methods on a 5975 with the following parameters: Scan Only, mass range 50-650, N=6 or N=7 (methods attached). Using B.07.00 shipping 5975 firmware. System Times out and the MSD goes offline. The first time it happens, reconnect to the MSD using the Menu Item and run a different method. If run the N=6 and N=7 methods again, the system times out again. unable to Reconnect to the MS via the menu item. Close and restart GCMS, unhandledexception.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: Truncation: Q-TOF Short Report, Tune file name is truncated
Problem:
Create Q-tof Short report. Tune file is truncated.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: CI Tune from Sleep mode produces MSDAT Exception and doesn't tune correctly
Problem:
With a good tune loaded, I put the system to sleep. While the instrument is sleeping, I initiated the tune MSD (menu item or icon). Window switches to CI Tune and Vacuum Control window as expected, and system is still asleep. Click CI Autotune (system wakes up) and CI Autotune does not begin until the GC and MSD are ready (all good). However, the tune that proceeds produces the attached error (tunefromsleep.png). The profile continues after I hit ok most of the time, but I have had it crash bronco once, and I get the dialogs about purging the CI gas line. A telnet log is attached. The tune never seems to get back on track. If I abort, and then just do a normal CI Autotune, using the same tune file, it proceeds without issue
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Can not enter over 10mins to Solvent Delay in MS Method Editor
Problem:
Load Default method Change Oven program to 15mins in GC Method Editor Go to MS Method Editor Try to change Solvent Delay to 12mins. But change to 10 mins automatically when the cursor move to the another field.
Temporary Solution:
Go to the Inlet and Injection Parameter menu and change Sample Inlet to Other/None Go to the MS Method Editor and now increase the amount of time for Run Time, this parameter is setting the maximum limit for the Solvent Delay when Sample Inlet is selected as GC. Go to the Inlet and Injection Parameter menu and change Sample Inlet to GC Go to the MS Method Editor and now increase the amount of time for Solvent Delay
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: GC Does Not Go Completely Out of Safe Mode After Download Method to GC is Selected
Problem:
5975/7890A system was in safe mode. In GC Edit Parameters some changes were made (changed oven temp, turned off some inlet pressures and flows). Right -clicked and selected Download Method to GC. The changes were downloaded, and the actuals should the parameters changing. Then changed the parameters again, and select Ok on the Edit GC Parameters panel, but the set points did not change.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: "Zip/Unzip methods and data" depends on character case of filename extension
Problem:
the function of "Zip/Unzip methods and data" depends on character case of filename extension: "Zip" is not case sensitive for filename extension, while "Unzip" works only for capital case in filename extension.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: Title of tune report different depending on how it is generated
Problem:
tune and vacuum control menu with stune.u loaded, select Tune MS. Tune report title will be Target Tune. tune and vacuum control menu, select Standard Spectra tune (stune.u). Tune report title will be Standard Spectra Target Tune In sequence, run a Check Tune. Tune report title will be Tune Report.
Temporary Solution:
When you select a menu item like Standard Spectrum Tune, the macros know exactly what you are doing and label the report accordingly. However, if you save STUNE.U as MAS.U, the macros cannot distinquish whether the file was originally an Stune, BFB, or DFTPP tune. Similarly, you could save the files as BFB.U even though it is an Standard Spectrum Tune.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: unhandled exception with no printers configured and tune report options selected
Problem:
Setup a computer with NO printers configured. In the Tune and Vacuum COntrol View, Select File\Set View Tunes Report Options, Select all of the options to be displayed. Run Tune (may have to run 2x to generate the TunePlots. After the tune is complete, an unhandled exception occurs. If you hit continue, the tuneplots show correctly, and there doesn't seem to be any damage to the system from the exception. Running a tune with none of the tune report options select is ok and does not result in the exception.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: check "Graphic Repots" check box, the subcheck boxed does not check by default
Problem:
tune and vacum view--> file menu--.> set view tunes report options check graphic reports, the sub checik boxes does not checked by default.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ, Sequnece Table should have "Critical columns" as default.
Problem:
1. Run Sequence as default Sequncetable column setting.
2. A message is always shown.
Critical columns contain data and are hidden:
method Path
Temporary Solution:
If the critical columns are show in the main view then the prompt will not be displayed. The prompt is just to inform the user there is some key items being hidden via the columns not being shown.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Fixed Electron energy is printed as 2 eV when printing the method
Problem:
Fixed Electron energy is printed as 2 eV when printing the method instead of the correct 70 eV which are used.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: change the spectrum name in spectrum manager, the monitor name did not changed as setting
Problem:
In the spectrum window, right click to the spectrum manager, change the display name from spectrum to something else, click ok, check the title of spectrum signal monitor, it did not change accordingly.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Unable to copy partial rows from Excel to SIM Table
Problem:
In the SIM Ion Tab, there are three columns. In order to successfully copy from Excel, the user needs to have all three columns defined in Excel. For instance, you cannot copy just the SIM Ion and Dwell Time, you also need to specify True or False for the Plot this ion.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Copy/Paste from Excel into SIM Table, any subsequent copy/paste from within in Method Editor will paste Excel values
Problem:
copied and pasted a group of values into the SIM Table. If copying a different set of SIM values from within the Method Editor and try to paste, the values that are pasted are those that are copied from Excel. After a copy/paste from excel, it seems that the Method Editor loses its copy/paste functionality.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Unhandled Exception when switch to SIM Time after Copy from SIM Table`
Problem:
Copy and Paste SIM rows from Excel into SIM Table (60 SIM Ions). SIM Ion Table is correct and there are no errors. Copy a partial group of the SIM Ions (complete rows, but only 10 or so ions). Go to SIM Time Segment line (empty and click as if to add a new time segment. Unhandled Exception occurs. Particularly bad because it does not go away after you hit Continue. Exception keeps appearing and then one may be forced to ctrl-alt-del the application since it was unusable.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: spectrum manager, the default colour is not working
Problem:
spectrum manager, right click the display name field, then select colour, change the colour, ok the panel. go back to the manager panel, check the display neme colour is applied. click default colours, ok it, go back to check the colors, it did not go back to the default.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
QQQ: the default label for chromatogram type should be the same with chromatogram type.
Problem:
instrument menu/MS parameters, click chromatogram tab. select the chromatogram type, the labels are always TIC even though the selection was BPC or EIC.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Help for Chromatogram Manager is missing Event Options description and Default color
Problem:
If you right click on the chromatogram, there is a dialog that appears. The help button brings up the "chromatogram manager" help as expected. However, the Event Options and Default Color items in the dialog are not explained.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Hitting Vent then Pumpdown on system with DCOMM enabled
Problem:
On a 5977-7890B system with DCOMM enabled, set up a GC Vent method. From the Vacuum control window, selected Vent. This activated the Vent Method on the GC. After a minute or two select Pump down. The Mass Spec went into Pump down and became ready. The GC temps were still falling according to the Vent Method
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: when you perform a check tune in QQQ, ion ratio for mid and high masses are wrong
Problem:
when you perform a check tune in QQQ, ion ratio for mid and high masses are wrong, they result to be exactly the half, compared to the values in the aTune. If you look at the "raw" data file in the txt file inside the checktune report folder, the values are acquired correctly. It look like when the system compile the report, the process do a wrong calculation: only "Ratio of mid mass to low mass" and "Ratio of high mass to low mass" are the half of what they really are in the aTune..
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Starting up MS that is in use by another PC
Problem:
MS was in use on one PC and trying to start up the instrument on a different PC. One can correctly see the message that Instrument is in use by host name. The instrument status showed offline. Nothing was recorded in the logbook such as when the GC is offline. Also, one is able to go into tune and initiate a tune.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: MSD wakes up on start-up even if you say no
Problem:
If you have the SYstem asleep, then close MassHunter Acquisition. When you restart MassHunter Acquisition, one is told that the system is asleep and would you like to wake it up? If you click No, the GC stays asleep, but the MSD spins up the turbo and becomes awake.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: No indication that in SafeMode
Problem:
When the system is placed in SafeMode and if you close the Vacuum Dialog while venting or vented, there is no indication one is in safe mode.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Run Method will begin even when Turbo not at 100% after waking up
Problem:
This seems to be vary by instrument. Set the instrument to sleep. While System is sleeping, run method. System will get all the commands to wakeup. Logbook and LCP all say, AWAKE or Ready. So according to the Run Method Panel appears and the user can run a method. However, the turbo pump speed on the LCP and on the Monitor are not at 100% or above the ok threshold. On one system, it was 40% (the turbo seems to spin down before spinning back up to 100%). If there is a lengthy Pre-run, this is fine since the pump comes up to speed fairly quickly. However, you might get a case where there is no pre-run and the run method begins with a less than spun up turbo.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Actions executed under Executed tab on Tune and Vacuum view are not consistent on Calibrant valve status
Problem:
On Tune and Vacuum view, under tab Execute, the status of CI Calibrant with the following actions seem not consistent: "Ramp Lenses": MS turns on automatically, CI Calibrants valve opens automatically after the button was clicked; "Profile scan": MS turns on automatically, but CI Calibrants valve doesn't open automatically after the button was clicked; "Spectrum scan": MS turns on automatically, but CI Calibrants valve doesn't open automatically after the button was clicked; "Find mass": MS turns on automatically, but CI Calibrants valve doesn't open automatically after the button was clicked;
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: MSD produces Faults when wake up during a conditioning run
Problem:
System is scheduled to wake up after a conditioning run. GC goes into conditioning run. From Menu item, select Wake. The MSD wakes up and the turbo spins up. There is a HiVacFault Registered and a HED Fault registered. Meanwhile, the GC stays in its conditioning run. If I hit Wake again, I get a message saying that the system can't be run in conditioning state and the "falloff" message is displayed in the status line. If I stop the conditioning run from the front panel, the system becomes alive again.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Run Method in offline mode, get "undefined symbol: wait for CIPI ready"
Problem:
While a simultaneous online system is running, startup up offline system. Green arrow is active, pressing the green arrow; the system went through the motions of trying to start a run, but getting a Run Method Error. Was expecting, "Offline" or something, but instead got "undefined symbol, wait for CIPIready"
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ, While in Vacuum Control, reconnect network cable of MSD, MSD remained offline while Instrument Status is Ready.
Problem:
While in Vacuum Control, 1. unplug network cable of MSD. Actuals show Offline in Vacuum Control panel while Instrument Status is Ready. 2. Reconnect network cable of MSD. Actuals still remain Offline and Instrument Status is Ready. 3. In addition, if click "Close", messages popped up indicated "MSD is offline. If exit out of the Vacuum Dialog, GC/MS Acq will terminate. "
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Fast Vent Text on display when GC is in vent mode
Problem:
GC mode of GC monitor display is “Fastven” during MSD vent cycle. I think this is “Fast Vent”.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Help/Using Help In Tune and Vacuum Control View Does Nothing
Problem:
In Tune and Vacuum Control view, selecting Help/Using Help. Nothing happens. No help opens.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Create EI Tune File for CI Source Not Working
Problem:
For a 5975CI instrument, go to tune an d vacuum control. Load a CI tune file and go to Tune/Create EI Tune File for CI Source. The status line said, "Could not open file D:\MassHunter\msexe\EI-CISource.mac.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Simulate sequence does not flag duplicate filenames, that is only done when exiting sequence table
Problem:
If you setup a sequence that has duplicate filenames, you will be warned on exiting the table as asked if you would still like to continue. Respond Yes. Then Simulated the sequence and it did not flag the duplicate filename but when the sequence is run and overwrite data file is not checked, the sequence will error out on the line with the duplicate filename.
Temporary Solution:
Simulate Sequence checks to see if the syntax is correct, the method names and paths are correct.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: Error when try to open Logbook after it has been cleared
Problem:
With the Logbook open, select File\Clear. The contents of the logbook is cleared. Close dialog, Click on logbook again, get an error saying cannot find mslogbk.html. Click OK. The blank book opens.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
QQQ: Log files have not been generated in QQQ autotune in case that the check boxes of log files are selected
Problem:
On QQQ autotune, select all check boxes (Log File, Ramp Data, Capture data, Spectra Data, Log 15 sets of peak data per file) of Log Files under panel of Files and Reports. After autotune is completed, tune report has been generated, but no any log was created.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: transfer line temp show wrong on tune report of 7820-5975
Problem:
config 7820-5975 run autotune, the transfer line temp showes wrong. when tune 7890-5975 or 7810-5975 (5975T), this issue did not happened.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: MS Instrument Control and Tune has been stopped working after vent cycle is finished
Problem:
Hardware configuration is 7890A+5975MSD+G7697A HeadSpace After vent cycle is finished, the message displayed. is "MS Instrument Control and Tune has been stopped working".
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Remote Access to unit, running the Sequence with Tune only, MSINSCTRL.EXE GPFs
Problem:
Running a system via a Remote Access with Tune only in the sequence error when the Remote Access to the system is terminated.
Temporary Solution:
Wait until the tune is completed before closing the Remote Access Connection, this includes timeouts/screensavers to the system also.
Fix Information:
n/a
Keyword:
One-line Description:
MSD, show_ipinfo.txt does not include HS
Problem:
Select Help\Show IP and Revision Information... The G1888 info is not included.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ, Run stops with excessive foreline pressure during solvent delay
Problem:
A customer is trying to run a locked method in constant pressure mode which is causing the system to start the run with an initial column flow of approx. 2.3 ml/min (inlet pressure 21.4 psi) which is above the recommend flow rate for the diffusion pump system. The system is also running large volume injections which is going to increase the amount of solvent pump out at the initial part of the run. Depending upon the system condition (foreline pump condition, last time PM has been done for the foreline pump oil, etc) the foreline pressure could reach 100 mTorr which will trip the excessive foreline pressure error. Typically, on new and well maintained systems we would see foreline pressures around 350 mTorr.
Temporary Solution:
Some applications which could run on a Turbo pump system may not run on Diffusion pump systems. Modifications/Preventive Maintenance/Updates may be required to the system to make it perform.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ, 5977 with extractor lens and tuned using ETUNE, the Tune Evaluation is done by MH using ATUNE instead
Problem:
If a unit has an extractor source the user can selected multiple types of autotunes to be done: etune, atune, bfb tune, dftpp tune, stune, and targert tune. The MassHunter GCMS Acquisition software will perform the tune evaluation based upon the atune criteria. So there could be some errors being reported from the tune evaluation report while there are no real issues because the system could be evaluated using a different type of tune while using the autotune criterias.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ-QTOF, "Use MS" not selected: QQQ/QTOF say offline and MS parameters still active
Problem:
If the user unselects the "Use MS" checkbox in the Injector parameters panel, the MS icons should all be greyed out. For QQQ and QTOF, this is not the case. Also the Instrument Status says OFFLINE, which is misleading since the GC is online and happy, as is the MS. We are just saying don't use the MS. It is still possible to run a method like this, it is just confusing. In the SQ case, all the MS icons are greyed out and the Instrument Status still says Ready.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ, air/water check report title needs to be updated
Problem:
MassHunter GCMS Acquisition Air and Water Check gives a generic title of 597x for the air/water check for the 5977. The 597x does not really represent just the 5977 series, the 597x actually represents the full single quad line which has been made. The title of the report should be updatedc to 5977 air/water check.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ, SIM/SCAN data files do not have the same number of records.
Problem:
For SIM/SCAN acquisition, firmware is supposed to alternate between SIM cycles and Scan cyles. The resultant data.ms and datasim.ms should have the same number of records, +/- one record. Some of transitions between time events is being counted as a record event which is causing a mismatch number of SIM/Scan record numbers.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD, In a GC-MS Manual Injection the Start Run panel behavior is inconsistent if the MS is configured as connected to the rear injector
Problem:
In a GC-MS system with the MS physically connected to the rear injector, the automatic injection mode runs fine. If you switch to Manual injection mode, without reconfiguring the MS connection, the Start Run panel only allows you to enter the sample info on the left hand side of the panel (normally, labelled front). The sample info on the right hand side of the panel (normally, labelled rear) is grayed out. Once the Start Run dialog box closes, a message box pops up asking if you want to overwrite the data file last used for the rear injection. It appears that the method is run with the sample info from the right hand side of the dialog box that was grayed out. The info that was entered on the enabled side is not being used. This is inconsistent behavior between the Start Run panel and the run method macro.
Temporary Solution:
In the Inlet/Injection dialog box, if you change the MS to be connected to the front injector, the behavior will be correct. This is not intuitive, because the hardware has not been changed. The MS is still connected to the rear injector.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ, Error message when specifying sandwich keyword but no keyword string
Problem:
Set up a 3 layer sandwich injection sequence. Specified the 3 Layer L2;L3 keyword but did not enter a keyword string. Received the following message "Alert "you must use the ' ; ' character to separate L2 from L3. Edit Sequence Table?" Message should be keyword string should not be blank.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ, Tune - Dynamic ramp geometric mean = undefined
Problem:
Autotune dynamically ramped lenses sometimes show geometric mean as undefined even after the previous mean was ok.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package
Keyword:
One-line Description:
MSD, Sequence process keywords prompt delayed
Problem:
When using sequence position and run feature, the user is prompted for whether or not to process keywords. The problem is that this prompt is delayed 2-5 seconds. On multiple occurrences, the user could have walked away thinking the sequence has started and to come back to find out the sequence just sat there.
Temporary Solution:
Wait until the first sequence line has started.
Fix Information:
This has been fixed with B.07.01 released software package
Keyword:
One-line Description:
QTOF, warning message for incorrectly selected time segment while using target MS/MS table
Problem:
When user has multiple time segments and also using target MS/MS table, there is no warning or prompt to indicate to the user the time window entered into MS/MS table is outside of the selected time segment.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ, Titles and contents are not aligned in Revision History.
Problem:
While running MS Configure, it could be awkward reading the Help/Review Revision History because the Titles and contents are not aligned. Information provided is correct and valid.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ, GC Signals Continue to Plot After method is finished.
Problem:
In GC Real Time Plots (RTP), four GC signals were selected to be displayed and saved however the continuous checkbox was not selected. All four signals collected in the RTP during the run and were supposed to stop at the end of the run. The RTP still shows the signals drawing even after the run is completed.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ, No error displays if Time event of MS On is shorter than Solvent Delay
Problem:
On MS Method Editor, set Time event of MS On shorter than Solvent Delay, an error sign and relevant message should appear, but no message or prompt appears even if "Apply" or "OK" button was clicked.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ, Methane Flow Adjust happens twice
Problem:
In the tune view, if one loads a CI tune file, the Methane Flow Setup occurs. After the Methane Flow setup occurs, the user is asked if they would like to run CI Autotune. Click Yes. The system then proceeds to do another methane flow adjust before beginning the autotune. Just a duplicate step, no changes in the results.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ never emits VacSysFail when running, so GC never goes into MS Shutdown mode when fault is triggered
Problem:
Turbo pump spins down to 1 % and MassHunter Acquisition emits a message: MS Fault Detected: 2.8 High Vacuum gauge is reading too high a pressure The MS never sends the "VacSysFail" message, so the GC never goes into shutdown. (waited at least 15 minutes after the turbo pump was at 1%) If you then start everything back up, the first message that is given is that the "Vacuum system is not ready". This sends the GC into shutdown mode.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ MS monitor; Reset Default reset to setting for SQ
Problem:
1. Config QQQ 2. start Inst#1, 3. Instruemnt > Edit Monitor 4. Reset default Selected monitors are reset as Single Quad monitor instead of QQQ selected monitor
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ, MS mthod Editor; Run time = 999.9 is not acceptable
Problem:
on QQQ MS Method Editor, Input Run time = 999.9. An eror message is shown. but it says, 0.1-999.9 is valid range. 999.8 is accepted.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ, Can not import scan segment becasue of garbage
Problem:
1. config QQQ,
2. Go to Method Editor,
3. Import CSV file to Scan segment,
Excel-csv-02.csv; created by Excel 2013
4. When import Excel-csv-02.csv, the header title can not recognized because of Garbage (Ansi format)
Temporary Solution:
1. Open Excel-csv-02.csv by NotePad 2. Change character code = UTF8 3. Save it (the attacehd UTF8-Excel-csv-02.csv) 4. UTF8 file can be load
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ, dynamic ramp panel, mass and value pair cannot be deleted
Problem:
go to manual tune panel, ion source tab click ion focus box, dynamic ramp part will be active. check enable checkbox and input some mass and value. try to delete one pair, it was impossible. when one cell value was deleted an excalmatory mark will display besides the cell.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ, Random Tune & Vac Control Actions Gray out MSD Icons
Problem:
This has occured a couple of times when, all the MSD icons gray out event though the MSD is still online and the menu items are active. The first time this happened was when some changes were made to the MSD Temps and saved the tune file to a new name and then reloaded the tune file. The second time was in Tune and Vac View, selecting various menu items. When switched back to Instrument Control View, they were grayed. See attached screen capture.
Temporary Solution:
You have to shutdown and restart to get your icons back.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ, 5977, MSD Temperature fluctuates by 20 - 50 degrees
Problem:
Powered cycled a CI system and applied new tune file temps (300 source, 150 quad) to it. During the ramping up process as the source temp approached and reached 300, the actual temp reported was jumping around by 20 to 30 degrees every time it was queried (about once / second). This does not occur all the time.
Temporary Solution:
Power cycle and/or reload the temperatures corrected this issue.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ, During Load Method, 7890Method.bin gets renamed in a MS-only configuration
Problem:
When loading a GC-MS method which includes the 7890 on a MS-only configuration, the 7890Method.bin file gets silently renamed to 7890Method.mth. Even without saving the method, the file name is. Later, when loading the same method on a GC-MS configuration, a new 7890Method.bin was created. The settings were not identical to the original 7890Method.bin.
Temporary Solution:
Generally, this is used for MS only for troubleshooting.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QTOF, Sequence hanging CTC system may be caused by long method name
Problem:
Sequence cannot start (stays in PreRun), although all related icons and windows are in green; no any warnings, no any message or sign. It is difficult to figure out the causes. The method name is xxxxxxx.m (38 characters prior to .m, only one dot). Have tried a short method name (e.g. Test1.m), this error doesn't occur.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ, 5977 print tune report has font issue
Problem:
config 5977 and run tune, except auto tune print report, other print tune report have font issues (larger font size with crowded characters in MS parameters section).
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
MSD, Problem running dual with sandwich injection
Problem:
Created a dual method where both the front and rear specified a 2 level sandwich injection. Set up the sequence appropriately. Place the L2 vial specified in the sequence in the front turret. The back turret will just use the vial that is already in the L2 slot of the turret. Now however, it placed the L2 vial specified in the sequence in the front turret and then tries to go back and place the same vial in the back turret. Of course it doesn't find it and no injection is made. It aborts or skips.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD, when in flow mode, incorrect RTLPressure recorded in pre_post.ini
Problem:
MSD, when in flow mode, incorrect RTLPressure recorded in pre_post.ini should really update acqlock.mac so both the recorded flow AND pressure are correct.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package
Keyword:
One-line Description:
SQ, Run Sequence from sleep produces HiVac fault
Problem:
If one is running in drug mode, and then start a run sequence while the system is sleeping, it couldl produce a hi vac fault and the sequence will not start.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ, Tune from sleep: "cannot assign or remove reserved variable: _sleep mode"
Problem:
Trying to tune from sleep (CI). The system goes into Tune and vacuum control view, but doesn't wake up anymore when you click CI Autotune. "cannot assign or remove reserved variable: _sleep mode"
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD, Uninstalling SP2 will corrupt B.07.00
Problem:
Unistalling the B.07.00 SP2 will corrupt the B.07.00 which is left on the system if you try to run it by itself. You cannot reinstall the B.07.00 SP1 so you will need uninstall the B.07.00 and then reload whole system.
Temporary Solution:
When uninstalling any service packs, uninstall the complete package and then reinstall.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ - When changing from a CI source to an EI source, the software should force pumping out of the reagent gas
Problem:
When the user configures a new ion source and the previous source was CI, there should be a check in the software to determine if the reagent gas needed to be pumped out. Another side effect of not pumping out the gas from the software side is that there may be inconsistent status messages displayed on the MS Status Panel. The Method Status message may indicate that the method has been applied, but the Ion Source status message will say the method has not been downloaded to the instrument. Going through the software to pump out the gas would put everything back in sync..
Temporary Solution:
When venting, the firmware will turn off the gas. But it is good practice to pump out the gas lines so that residual gas is not trapped in the line after the flow is turned off and the isolation valve is closed.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QQQ, After editing a QQQ method, some changes may not take effect when running the method
Problem:
There is a defect in the QQQ acquisition code that causes it to use some of the previous method settings after the method is edited. The affected method settings are Stop time, tune file, time segment settings, and acquisition settings.
Temporary Solution:
The workaround is to save the method and then reload the method from the disk. After reloading the method, the software will have all the correct settings.
Fix Information:
This has been resolved in released version MassHunter GCMS Acquisition B.07.01.
Keyword:
One-line Description:
QQQ, After editing a QTOF method, some changes may not take effect when running the method
Problem:
There is a defect in the QTOF acquisition code that causes it to use some of the previous method settings after the method is edited. The affected method settings are Stop time and some tune settings (mass axis settings for the quad and dynamic ramps). There is a similar issue with the QQQ method. However, there are fewer settings affected in the QTOF. Also, dynamic ramping is not currently being used in the QTOF.
Temporary Solution:
The workaround is to save the method and then reload the method from the disk. After reloading the method, the software will have all the correct settings.
Fix Information:
This has been resolved in released version MassHunter GCMS Acquisition B.07.01.
Keyword:
One-line Description:
SQ, "VACUUM VENT" hangs when done and trying to exit Vacuum dialog box
Problem:
There could be a timing issue when exiting the dialog box -- this is related to the background (vacuum values acquisition) and the foreground dialog box conflicts.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GCMS Acquisition B.07.01.
Keyword:
One-line Description:
QTOF NCI MS/MS runs in PCI MS/MS mode
Problem:
QTOF, NCI MS/MS Acquisition not working NCI Tune MS and MS/MS work fine. NCI MS Acquisition works fine. The firmware is not setting the pulser polarity correctly. It always set it to positive mode when doing MS/MS. It is a long existing defect when the MS/MS mode was introduced. Only NCI MS/MS mode is affected. Other modes are fully functional.
Temporary Solution:
New firmware is available via point patch
Fix Information:
n/a
Keyword:
One-line Description:
SQ: MassHunter GC/MS Acquisition Checkout procedure is not evaluating ETUNE.U.
Problem:
The Checkout/Tune Evaluation historically worked directly with ATUNE.U only. Exception being when HISENSE.U was used. Then the filament # had to be saved into the HISENSE.U file to be used by checkout tune and tune evaluation. Both ATUNE.U and HISENSE.U were updated and the only difference was in EMV. The extractor related tune ETUNE.U however is never checked by Checkout procedure so the extractor HW is not tested. That causes compliance problem when trying to validate the configurations.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
MSD: Wrong path for “Run Method” datafiles
Problem:
Wrong path for “Run Method” datafiles Open MassHunter Acquisition; Click on “Run Method”; after selecting the desired method, enter the data path (for example “D:\MassHunter\GCMS\data”) in the “Start Run” dialog; Click “OK and Run Method”: data acquired is correctly stored under the selected path; Click “Run Sequence”; enter data path (for example “D:\MassHunter\GCMS\data\sequence”); Start sequence: data is correctly stored under the selected path; Click again “Run Method”. Enter data path and start the run; Data is not stored in selected folder, but in last used sequence data path – e.g. “D:\MassHunter\GCMS\data\sequence” instead of “D:\MassHunter\GCMS\data”;
Temporary Solution:
Close and re-open MassHunter Acquisition before executing “Run Method”.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
MSD: Wrong window behavior when editing GC method:
Problem:
Wrong window behavior when editing GC method: Open the GC method edit dialog; Close the dialog (either by clicking “OK”, “Cancel” or “X” in top-right corner); If any other window (beside MassHunter Acquisition) is open, such window is focused and MassHunter main window is sent background;
Temporary Solution:
minimize any other window(s) before editing GC methods. Does not affect functionality, but is very frustrating.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: SIM ions is deleted by clicking OK button
Problem:
Create SIM method included some SIM ions. Then click OK button and leave MS method editor window. Then enter MS method editor again. Then click OK button and back to MS method editor again. The last SIM ions is deleted.
Temporary Solution:
Save method is required and then the information will be saved and then recalled.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: In Edit SIM method parameter, SIM ion is deleted by clicking dwell time and cycle time field.
Problem:
In Edit SIM method parameter, add some ions to SIM field. Then Click Dwell time field and Cycle time field in SIM Time Segment. Added ions are deleted.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: CheckBar keyword not working in Drug Mode
Problem:
Setup a sequence where the first line was the CheckBar keyword with PAUSE in the keyword string. According to help, use of this keyword should override any selection mode on the start sequence panel. On the start sequence panel, selected Inject Anyway. Ran the sequence with a barcode mismatch on the second sample. Sequence ran though instead of pausing. The logbook showed "continuing although barcode did not match expected".
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: SIM Table does not reflect the correct number of total Ions.
Problem:
Customer is building sim table with one group. In the sim time segments , number of Ions shows one less than what is in the sim table on the right.If she tries to adjust the number of ions to the correct number, the last ion is ignored during acquisition. Leaving the total number as the incorrect number, seems to work but is causing confusion.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Reprocess a sequence is not working
Problem:
In MassHunter Acquisition software B.07.00 SP2 with G1710FA as the Data Analysis software, it has been observed that the ALS starts every time when a sequence is to be reprocessed. The Use ChemStation DA is checked. When the customer selects Run Sequence and selects Reprocessing only, the ALS immediately starts to run. It has also been observed that the simulaterunmethod=1 is also starting the ALS.
Temporary Solution:
A point patch is available for this.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Cycle Time for one SIM ION pegged at 50.00, regardless of Dwell Time
Problem:
In the 597x Method Editor, the Cycle Time column does not update correctly if you only have one SIM ion specified. The Cycle Time is displayed as 50.000 regardless of the dwell time. To reproduce: 1) Open Method Editor and set to SIM mode. 2) Put one SIM ion in SIM Tab 3) Cycle Time in SIM Time Segments set to 50.00
Temporary Solution:
n/a
Fix Information:
This has been resolved in the B.07.01 release software package.
Keyword:
One-line Description:
MSD Method Editor - SIM ion gets deleted from SIM table by mistake.
Problem:
This will occur within the “SIM Time Segments” of the MSD method Editor. By clicking onto the field showing the “Number of ions” from one SIM group the user will remove one SIM ion from the SIM tab list.
Temporary Solution:
n/a
Fix Information:
This has been resolved with the B.07.01 release software package.
Keyword:
One-line Description:
SQ: Real time plot layout not retained from session to session
Problem:
When adding multiple Real-Time Plots (SIM or Scan), the plots are stacked correctly when you exit the MSD Method Editor (in the available space). Save Method. Exit MassHunter GCMS Acquisition. When MassHunter GCMS Acquisition is loaded the next time, some of the real time plots are not put back into the same place that they were when the method was saved. Some were, some weren't. All the monitors were placed in the correct place.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
HS: HeadSpace instrument status is not consistent with MassHunter GCMS Acquisition Instrument status.
Problem:
The inconsistent issue happens in following 2 situations. 1. Start a sequence and Disconnect HS Lan and RS232 cable following injection to GC, and then Reconnect the cables. MassHunter GCMS Acquisition instrument status always remains as Offline even the instrument status of HeadSpace and GC are all online. 2. Start a sequence and Power off the HeadSpace device, and then Power on HeadSpace. MassHunter GCMS Acquisition instrument status always remains as Offline even the instrument status of HeadSpace is online. MassHunter GCMS Acquisition instrument status won't change to online unless start a single run or sequence run.
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.01
Keyword:
One-line Description:
QQQ: No bake keyword in sequence for GCMS QQQ
Problem:
Configure a 7000 GCMS QQQ system Edit the sequence, for the keywords column, cannot find "bake" or "bake out" keywords from the drop down list.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: ENVDEMO does not have any demo files associated with it from the installation
Problem:
MSD: ENVDEMO does not have any demo files associated with it from the installation F.01.00 has the files but F.01.00 SP0 does not copy over the demo files
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Link to GC Help Broken
Problem:
Due to the GC driver being moved to a subdirectory, the acquisition software no longer has a link to the GC driver help from the MassHunter online help.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: ChemStation to MassHunter MSD Method Migration: Timed Events for Detector do not come through correctly
Problem:
In the ChemStation, have method set up with Absolute EMV, and the timed events for EMV have 200, 0, -200. When this method migrates to MassHunter, the Absolute EMV setting is correct in both the Main EMV Setting and the Timed Event, but the values of the Timed Events are still the Delta EMV values of 200, 0, 0 (since absolute can't go below zero). The method should be able to translate the EMV values based on the EMV Setting. ie if the Absolute EMV is set to 2000 (from tune), the timed events should have been 2200, 2000, and 1800
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Undefined symbol dummy_file$ if you specify unlinked sequence with rear samp as the second sample
Problem:
Set up a dual injection sequence with the Unlinked keyword. Added two sample lines and the RearSamp column. When it is specified correctly and check RearSamp for line 2, all works correctly. If however, it is set up and check RearSamp for line three instead, an error message "Undefined symbolL dummy_file$" and the sequence aborts. There should have been a better informative message about the sequence is incorrectly set up.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: 6890 method from MSD Productivity ChemStation is not migrated to 7890 MassHunter GCMS Acquisition
Problem:
There are no errors but none of the parameters from a 6890 method from MSD Productivity ChemStation is not migrated to 7890 MassHunter GCMS Acquisition. 6890 ChemPort in MSD Productivity ChemStation migrates correctly to MassHunter GCMS Acquisition 7890.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
MSD: "Alert (Instrument is in SLEEP mode)" does not appear
Problem:
While the instrument is in SLEEP mode the 'Alert' messages will not appear on the display of the instrument. The alert window will not appear.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: Sequence log files are not saved in specified DA path in STE.
Problem:
In STE with designed sequence table which is intented to test with Qual and Quant report. Although the DA path is defined in the STE, when sequence finished, the sequence logs are found under D:\MassHunter\GCMS\1 instead of defined DA path.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
Russian: Manual Tune boolean (on/off type) slider controls have an unexpected bias towards certain states. This behavior is inconsistent with English version.
Problem:
In Russian, the boolean-type slider controls have an odd bias. In a certain sequence (see attached screen capture), if you click on the slider control, it will unexpectedly switch to a certain state, such as an "Off" position. CORRECTION: Attached image step #1 should say "Put "HED Enable" into On position" --- not "Off position".
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
Russian: Manual Tune Profile / Scan / Capture tabs have incorrect floating point parsing/conversion.
Problem:
It appears string-to-floating point parsing/conversion in Manual Tune ==> Profile / Scan / Capture tabs is off by a significant digit...
For example, type "2,2" + {ENTER} and the text will be converted-and-displayed as "22,00".
The Profile, Scan, and Capture tabs may not be an exhaustive list of where this issue occurs.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
Russian: QQQ tune reports printout errors
Problem:
Missing lines in report. Tune file name is not printed. Numerous overlapings, word divisions.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: Pause batch if calibration expired is not working with Intelligent Sequencing and classic DA
Problem:
Intelligent Sequence set to Pause batch if calibration expired. Set up a sequence with two specimens. Ran the sequence and got message that the current calibration is out of date, responded Yes to continue. When prompted, chose a Med Control. Instead of pausing the batch, it asked for a re-injection.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QQQ: Sequence keyword help needs specific information for each instrument type
Problem:
The "Keyword / Keyword String" help topic only has information for the single quad. For the triple quad the 'Check Tune' section doesn't apply and the 'tune' keyword is missing. The 'Tune' keyword should then explain the use of the following keyword strings: Check - runs checktune, no further actions CheckPause - runs checktune and sets pause if fail AutoTune - runs autotune with all defaults, no further actions AutoTunePause - runs autotune with all defaults and sets pause if it doesn't complete CheckAuto - runs checktune , then autotune if check fails, then checktune again, no further actions CheckAutoPause - runs checktune , then autotune if check fails, then checktune again and sets pause if fail
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
MSD: 'Tune' sequence keyword should load the method from the sequence line
Problem:
When a tune function is used in the sequence the tune file that is used comes from the last method loaded. It seems like a reasonable expectation that the tune file would be the one associated with the method on the same sequence line as the tune function. This is not the case. If the sequence line is not the first then the tune file will be the one referenced in the method from the preceding sequence line. If the tune function is in the first line of the sequence then the currently loaded methods tune file is used. This can lead to an unexpected tune file being used if a method is given in the sequence line with the tune function. For the QTOF the tune file used in the mass calibration comes from the method on the same sequence line as the tune function. I think we should have behavior like the QTOF’s for the triple quad tune functions.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: Initialize MS Interface Does Not Reboot MSD
Problem:
In Tune and Vacuum Control view, selecting Vacuum/Initialize MS Interface is supposed to reboot the MSD Interface and the software verifies the firmware version. Verification of the firmware is okay but the MSD does not do a full rebooted.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
CTC: Synchronizing error in sequence using overlap function in Acquisition
Problem:
Intermittent, the sample overlap function without the CTC or Masshunter software works fine and they can run sequences without lockup; however, if they use overlap, customer can run 5 to 20 runs and then locks up with error “ waiting on synchronizing…..”
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Sequence table, if data file name contains a point the right part of the name will be truncated
Problem:
If the data file name has a ' . ' in the name, then the information to the right of the ' . ' will be truncated.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: Reconnect to MSD, temps do not go to setpoints and MSD status square not correct
Problem:
If you turn off the MSD, lose connection to MassHunter. When Offline, turn the MSD back on. Once it is on, use the help\reconnect to MSD menu item to reconnect. Once the MSD is reconnected, the status square and instrument status are green even though the temperatures are not at the setpoints (they are probably going to the "power on temps"). If you hit apply, the status does not change, even though the temperatures do in fact change and go to setpoints. When the source and quad are not at their setpoints, the MSD square should be yellow and instrument status should say "not ready".
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
SQ: " Undefined symbol; lockobj" happen by re-lock
Problem:
1. load locked method (5975_Scan_pressure_01.M.zip, it is 7890A-5975 method) 2. Go to RTLock view 3. select "RTlock/Relock Method" 4. select data (RTLock3.d) 5. "Undefined symbol; lockobj' will appear The file will re-lock but the error message is displayed
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QQQ: the settings about MS1(and MS2) Mass Axis Offset (and Width Offset) for Wide and for Widest of Peak Width are reversed between Autotune report and Tune file
Problem:
For Peak Width at "Unit": The settings about MS1 (and MS2) Mass Axis Offset and Width Offset are consistent between Autotune report and Tune file; For Peak Width at "Wide" and "Widest": The settings about MS1 Mass Axis Offset are reversed between Autotune report and Tune file; for instance, for MS1, Peak Width at "Wide" , the setting of Mass Axis Offset is -1.565 on Autotune report, while this value is set for Peak Width at "Widest" in the tune file. vise visa.; The same issue exists for MS1 Width Offset too. The same issue exists for MS2 as well.
Temporary Solution:
n/a
Fix Information:
This has been fixed in released version B.07.01
Keyword:
One-line Description:
SQ; Extration tune final ramp of extractor stops at 0,1 volt instead of 5 V
Problem:
Extration tune final ramp of extractor stops at 0,1 volt instead of 5 V
Temporary Solution:
User will need to go into manual tune and adjust ramp limit and then save tune file.
Fix Information:
Fixed with release version in B.07.01
Keyword:
One-line Description:
CTC PAL: Using a solvent delay of zero minutes will cause acquisition to fail to run the injection with the error “Operation is not valid due to the current state of the object”
Problem:
Using a solvent delay of zero minutes will cause acquisition to fail to run the injection with the error “Operation is not valid due to the current state of the object”
Temporary Solution:
Workaround is, use a solvent delay of 0.3 minutes
Fix Information:
This has been resolved in revision MassHunter GCMS Acquisition B.07.01
Keyword:
One-line Description:
SQ: MSD left BUSY after temporary network interruption and user Method, Exit
Problem:
MassHunter GCMS Acquisition was Idle after normal connection, then disconnect the Ethernet cable at the MSD SmartCard connection point. In less than 60 seconds, MassHunter GCMS Acquisition changed its display of Instrument Status from Ready to Offline. After 5 minutes of disconnection the cable was re-connected but the instrument will accessible while the SmartCard will state busy.
Temporary Solution:
If the user uses the reconnect feature in the vacuum status section this will reconnect the connection correctly. But if the user exits software package then a reboot may be required to re-establish the full connections.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
In sandwich injection, L2 vial and L3 vial doesn't return to the original position when the sequence finished
Problem:
In MassHunter Acq B.07.01, when use Keyword 2-Layer L2 and 3-Layer L2;L3, L2 vial and L3 vial doesn't return to the original position after finish to run sequence. When start to run sequence again, left L2 and L3 vials are returned to the original position before start to first run.
Temporary Solution:
Point Patch is available.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: Cannot automatically upload PDF reports from MassHunter Acquisition to ECM
Problem:
In MassHunter Acquisition B.07.00 and B.07.01 with ECM, if you run pdfwiz macro to automatically generate PDF of the reports (autotune, tune eval, air-water check, percent report, lib search report, and quant report) the PDF files are not automatically uploaded to ECM server.
Temporary Solution:
n/a
Fix Information:
MassHunter GC/MS Data Acquisition B.07.02 requires no point patch, however, MSD ChemStation Data Analysis F.01.01.2317 (released March 2014) still requires ecmendjob.mac (date stamp 5/28/14) to fix the problem. Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
CTC: Add the last modified date to the bottom in the sequence summary report
Problem:
n/a
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Start a tune, abort the tune, then try run method, system will not acknowledge a run start.
Problem:
From Instrument Control or Tune and Vacuum Control displays the user can start an autotune. When the autotune is started the system will automatically go into Tune and Vacuum Control menu view. If the user aborts the autotune (any type of tune) this will cause two things to happen. 1 - The autotune action has stopped and the system will display the Tune menu view. 2 - The abort action will cause an abnormal stop. It will inhibit the remote start for the system. This will cause the system to go into a complete lockup and will require a complete reboot of the WHOLE system to recover.
Temporary Solution:
Do not use the abort feature during a tune operation. If an abort is pressed during the tune operation then a run method is started, then the user will need to reboot the whole GCMS system to recover from the lockup: power cycle the MS, power cycle the GC, and a reboot of the MS Workstation.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
CTC: Adding one line to the end of a running sequence will cause the line above injecting to the wrong GC inlet using SINGLE OVERLAP or NO OVERLAP
Problem:
The customer using two methods, one for the rear inlet and the other one for the front inlet. They always adding NEW lines to the end of their sequence and then position and run the sequence with the new lines. If mixed injection ports are being used then the wrong injection could be used.
Temporary Solution:
Point Patch is available.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
Dual LAN card with FIxed IP address is not longer working since the installation of B.07.01 SW
Problem:
Dual LAN card with FIxed IP address is not longer working since the installation of B.07.01 SW.
Temporary Solution:
Point Patch for IP addresses update is available. Job Aid has Agilent recommended configuration.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: does not respond to 5977 faults when RunStatus=Idle,other?
Problem:
MassHunter Acquisition does not respond faults detected and reported correctly when RunStatus=Idle when communicating to 5977 and this also includes "VacSysFail" Instrument State when HiVacNotReady and HiVacOff faults are concurrently asserted.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
QQQ: DRUG MODE configuration will not allow Control samples to be run.
Problem:
In drug quant configuration, the use of a “control” in the sequence causes a crash. The verification at the start of run sequence looks for a gencont.mac that apparently is not included in the software – B.07.01, this shows up if MSD ChemStation DA is not installed, which will be the norm for a QQQ instrument.
Temporary Solution:
1. Install MSD ChemStation DA F.01.01 or 2. Use the attached 2 files to correct the issue without installing the MSD ChemStation
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
MSD: MassHunter Data Acquisition – protection of MS_Compliance.xml files
Problem:
Access levels for the different roles (Acquisition Analysts I, Acquisition Analysts II, Acquisition Analysts III, Acquisition Managers) defined in MassHunter Data Acquisition are defined in files named “MS_Compliance.xml”, which are found in:\Masshunter\GCMS\1 and :\Masshunter\GCMS\2 (where is the chosen drive for the installation). Folders :\Masshunter\GCMS\1 and :\Masshunter\GCMS\2 are set up by Agilent with groups “Everyone” and “Authenticated Users” having “Full Control” access. This means that anyone that can have access to the workstation can modify the access levels in MassHunter Data Acquisition, potentially giving an operator the right to create or modify acquisition methods, change system settings, etc. Since there is no audit trail linked to this file, and no audit trail in MassHunter Data Acquisition, this represents a very serious security problem , as such actions would leave no trace. We tried securing these files by changing the access rights on the files (leaving folder security unchanged), but ultimately this proved to be ineffective, because the “Full Control” setting applied on folders :\Masshunter\GCMS\1 and :\Masshunter\GCMS\2 takes precedence. Users can still edit these files.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ: "Improper masses for mass axis calibration" error occurs when running xTUNE.U
Problem:
In MassHunter Acquisition B.07.00 SP2 and B.07.01, if you use xTUNE.U to tune, you get error "Improper masses for mass axis calibration". This often happens after sequence was run the night before. The problem is when the method has more than three scan segments.
Temporary Solution:
Recommendation is to run the method with a wider scan range and run with one scan segment. A point patch is also available.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: 6890/7693 sequences allow override sample volumes only for values of the 7683 with 10uL syringe
Problem:
MassHunter GCMS Acquisition connected to 6890+ with 7693 system including BCR. The injection volume range should be from 1-50% of the syringe size. With a 10 uL syringe configured and 1uL volume specified in method, create a 6 line sequence with volume overrides of .2, 1, 2, 3, 4, 5. These are accepted and run. However, any other valid value, such as 1.5 (15%) is rejected after a lengthy wait for validation (Checking sequence line 0). If you try this sequence validation long enough with any values except the above, you may get 'Object reference not set to an instance of an object' or even crash the system with 'msinsctl has stopped working'.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: 6890 with 7683 Start Run Override Injection Volume does not advise of invalid entries; just rounds them silently to nearest stop value
Problem:
MassHunter GCMS Acquisition connected to 6890 with 7683 only. This ALS allows only 6 'stops': 2, 10, 20, 30, 40, 50% of the syringe size. Create a front ALS method with any size syringe. Select Start Run and opt to override Injection Volume. Enter any valid value and this is run correctly. However, enter an invalid number and this is rounded to the nearest valid stop without any advisory. Log shows the rounded value. e.g. 2.5 rounds to 2; 1.5 rounds to 1.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
QQQ: Find Compounds by MRM fails with an error - log file indicates - Invalid XY data. - X values must be unique
Problem:
Getting an error message if they run Find Compounds by MRM, in Qual. Problem is related to the multiple time segments of the MRM. Loading the data file into Quant B.07.00 works just fine.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: MRM Optimization tab does not have any type of workflow or help to explain how to use it.
Problem:
QQQ: MRM Optimization tab does not have any type of workflow or help to explain how to use it.
Temporary Solution:
The help information for the MRM Optimization is part of the supplemental disc. The feature was added to the software package as a convenience.
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MSD: Keyword"2-Layer L2" cannot work with dual injection method.
Problem:
Instrument: 7890B+ Front/Back Injector (7693) 1. Create a method with dual injection. For both front and back injectors, specify a 2-Layer Sandwich Injection. 2. Add the dual injection vial column to the sequence table and create a sequence with the 2-Layer L2 keyword. Run the sequence. 3. Sequence is aborted because the L2 vial for Back Injector is missing.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MSD: The Scaling for duty cycle is not correct for the Backflush Pressure
Problem:
The duty cycle for the Backflush channel is about 24% and it does not reflect the correct value in Qual.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Japanese; Online help: 597x manual Tune dialog Box; "Capture" is still in English
Problem:
Online help: 597x manual Tune dialog Box, the term "Capture" is not translated.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MSD: Save As to invalid method format does not return user to Save As dialog
Problem:
MassHunter GCMS Acquisition B.07.02 with CTC-PAL3 Save as a method to a name with a decimal point; e.g. PAL3LiqV1.12.M. There is a small text on the taskbar which shows 'Invalid path: C:\MassHunter\GCMS\4\METHODS\...1.12.' This failure to save should return the user to the Save As dialog awaiting a valid entry.
Temporary Solution:
Please look at the taskbar for confirmation of a saved method.
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
QQQ: Wrong Mass Assignment in Fast Scan Mode (Low Data Samples)
Problem:
In fast scan modes (i.e. simultaneous MRM/Full), the mass assignments could be off. If the assignments are off too much then library searching and compound identification for most compounds show poor or wrong mass assignments with 1 or 2 data sample. This wrong assignment is due to tuning of lag factors.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: lagfactors are intermittently reset.
Problem:
2) A more insidious issue is at work with respect to the mass axis lag factors. When the MSD is restarted with MassHunter open (as is often done when venting the instrument for cleaning or maintenance), the mass axis lag factors revert back to pre-2005 values that correspond to old electronics. The effect of this is most prominent at the “Fastest” scan speed, where mass 219 actually shows up at 223! This is also NOT calibrated out by the mass gain correction factors. There is a smaller effect at slower scan speeds, but this may affect our improved mass accuracy measurements.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
CTC: When using a 384 wellplate in CTC-PAL( GC Sampler 80), MassHunter GCMS Acq rejects over 100 vial position.
Problem:
When using a 384 wellplate in CTC-PAL( GC Sampler 80), MassHunter GCMS Acq rejects over 100 vial position.
Temporary Solution:
Will need multiple wellplates if using sample positions > 100.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: 7000 system is ending in a failure loop related to the source and MS1 heater regulation
Problem:
7000 system is ending in a failure loop related to the source and MS1 heater regulation resulting in a loss of communication to the 7000.
Temporary Solution:
n/a
Fix Information:
Has been resolved with firmware version Build 054.
Keyword:
One-line Description:
MSD: In B.07.02 release, Read Barcode button has been updated
Problem:
In B.07.02 release, Read Barcode button is updated. If you put a vial number larger than 0 in vial cell, step B and C should be the same all samplers will pick up the vial from the tray and send to Barcode reader to get a reading. If you want to read only from a default location, put a number zero in vial cell , CTC PAL and PAL-3 will pick up and read the default location specified in configuration panel. ALS and Head Space 7697 will need you hand set vial into Barcode reader(default location) to get a reading.
Temporary Solution:
Read Barcode button To enter a vial's barcode value into the Sequence Table at the cursor's location: a. Place a sample vial with a barcode label into the barcode reader mounted on an Agilent ALS tray, CTC sampler, or a 7696 Headspace sampler configured vial tray location. b. Place your cursor in that sample's Sequence Table Expected Barcode column or the Dual Inj Expected Barcode column. c. To enter the vial's barcode value into the table click Read Barcode. This button is active when a Barcode Reader is installed and the Expected Barcode column is visible in the Sequence Table.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QTOF: The x-range of the spectrum plots during mass calibration show the mass in the last line on the selected masses table on manual tune panel, even if this mass isn't the highest one
Problem:
The order of the selected masses on manual tune can be sorted based on the mass values. However, if user doesn't make sort, the x-range of the spectrum plots during mass calibration just show the mass in last line on this table even if this mass isn't the highest one.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
CTC PAL: Running a method with wrong script for tool installed on RSI
Problem:
Had a liquid script method loaded. Replace the tool with a HS. Without loading a new method, attempted to run the liquid script method. It brought up a method resolution panel which one is able to cancel. The PAL3 posted a message to the logbook :error while validating script" however MassHunter GCMS Acquisition just went into pre-run and sat there until the run has been stopped manually.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Read Barcode reads only single locations
Problem:
Enter sample locations and expected barcode column to table. The Read Barcode function picks up the vial from the designated location, but only one at a time.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
"Mist" value corruption
Problem:
Daily automated test shows the "Mist" value in PRE_POST.INI data file to be intermittently set as "Mist=0" instead of the expected "Mist=20". Initially investigation is going the Pre-Post ini file is corrupted but the data.ms file is okay. It could be Firmware/Hardware corruption or MassHunter GCMS Acquisition is sending the wrong value due to a corrupt file.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ: Filament 1 error, switch to filament 2, start a tune and still get filament 1 error
Problem:
There are some issues about filament 1 and filament 2 switching. If you have a blown filament 1, switch to filament 2 you must save the tune file and then start the tune msd to acquire the new tune. if you switch the filament and do not save then the tune msd will be using fialment 1 and create the error message.
Temporary Solution:
If you have a blown filament 1, switch to filament 2 you must save the tune file and then start the tune msd to acquire the new tune.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
RTL Calibration - Wrong pressures displayed
Problem:
When running RTL calibration for constant pressure method wrong pressure values are displayed in Locations and Pressures for RTL Calibration window. Actual pressures set during sequence run read from GC panel are OK.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ: Weird message if cancel picking valid tune file
Problem:
If you select an invalid tune file (ie a 5975 file on a 5977), you get a message saying, pick something else or cancel. , If you select cancel, you get the attached message. "Bad. Now need to inhibit any actions." Nothing bad seems to happen, except that it takes a little bit for the instrument control menu items to become active again.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
MSD: No barcode label on vial and expected barcode field blank reports error and not injected but sequence not stopped
Problem:
Setup a sequence and the second line did not have an expected barcode in the field. When the sequence ran, the vial for that line did not have a barcode label. It reported an error "Sample aborted due to a runtime error." :Barcode of target could not be read." The sequence did not stop however, it proceeded to the next line.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MSD: Readme.txt file \support\firewall references the wrong directory location
Problem:
states ... located in the \Documents folder of this disc. should be ...located in the \Documentation folder of this disc.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Number of plots for " MS1 Profile" or "MS2 Profile" is not consistent with the selected masses
Problem:
For all types of ion source, for both 7000 and 7010. The following is an example from 7000C: On manual Tune panel, 1. Turn on Emission; open calibrant valve; 2. The scan mode panel is in "MS1 Profile" by default; 3. Click "Start" button to monitor the plots on top area. The selected masses by default for EI are 69, 264 and 502 for both " MS1 Profile" or "MS2 Profile"; 4. Switching between "MS1 Profile" or "MS2 Profile", three plots appear, the plots and the behaviors of count changing look normal; 5. All above are as expected; 6. Add mass 131, 219 and 464 to "MS1 Profile", while add 219 only to "MS2 Profile; 7. Switching between "MS1 Profile" or "MS2 Profile". 6 plots appear for "MS1 Profile", the behaviors of count changing are right. However, there are also 6 plots appear for "MS2 Profile", two extra plots with "frozen" peaks and count number.
Temporary Solution:
Note: the issue occurs only when plot number is greater than 3.
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
SQ: Monitors are not saved in the correct location via the save layout or saving via the methods
Problem:
MS ONLY system. Under Instrument, edit monitors, selecting 4 more MS monitors to be displayed. Then moving the monitors to the new position and then saving layout and then saving the method (also occurs when using save method as). Once the method is saved the monitors are moved back to their original position and not what was saved in the method or layout.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ: Tune report does not present the same base peak results in Profile versus Scan section.
Problem:
The tune report shows 69 as the base peak for the Profile section while the Scan section uses the most abundant peak. Typically, the base peak is 69 and the Profile and Scan section will match up; but if the most abundant peak is 219 then the results for the Rel Abund will be different.
For example
(Profile) (Scan)
Mass Abund Rel Abund Rel Abund
69.00 371,752 100.0% 91.3%
219.00 407,093 109.5% 100.0%
502.00 37,032 10.0% 9.1%
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
QQQ: Wrong Mass Assignment in Simultaneous Mode
Problem:
1. The wrong mass has been observed in the “full scan” portion of the simultaneous scan with either MRM or SIM mode. 2. The mass miss assignment is not dependent on the filtering being ON or OFF. 3. Comparison for full or simultaneous scan was made at the same scan time (2 data samples)
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ: Cannot run a sequence that overrides the injection volume with liquid tool installed.
Problem:
Had the liquid tool installed with a 10 uL syrings such that the sample volume was 0 - 10. In the method, set the sample volume to 1 uL. Set up a sequence using that method and attempted to override the injection volume by entering values in the Vol colume that are valid (ie. 2 uL, 3 uL and 4 uL). Saved the sequence and attempted to run it. It runs a simulation first to determine that all of the values are valid and it states the injection volume is out of range. It will not let the sequence run until the vol from the field is removed.
Temporary Solution:
Remove the volume from the field and then restart the sequence.
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MSD: MassHunter GCMS Acquisition Injects Wrong Vial when PAL3 Run from the Back
Problem:
Set up a GC/PAL3 system with a Front and a Back Inlet. Set up a method to inject to the back inlet. Hit the start run button. Change the Tray name for the back injection and hit OK. MassHunter GCMS Acquisition will start the run but tell the PAL3 to inject from whichever tray was in the FRONT inject screen.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
QTOF: MS collision energy not recovering from MS/MS mode
Problem:
While running in the MS/MS-MS mode of operation; MS collision energy not recovering from MS/MS mode transitions.
Temporary Solution:
GC QTOF firmware G.7200.01.20 is available.
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MSD: Incorrect Sequence Simulation for Drug Mode
Problem:
In Drug mode, autonaming needs to use the ‘Drug mode way’ that includes the sample type in the datafile name (i.e. 001BL0098 for the blank using vial 98 as the first run). The acquisition works fine and will autoname correctly, but the simulation check uses the legacy ‘autoname’ that is simply -> vial number, index number, run number (i.e. 09801001). So, existing datafiles will not be caught
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ: Unhandled exception occurred when selecting File > View Tunes in Tune and Vacuum Control
Problem:
When you select File > View Tunes, you get error message "TunePlot: Unhandled exception has occurred in your application." This is due to incompatibility of ATUNE.CSV created from MassHunter GC/MS Acquisition pre-dating B.07.02.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in MassHunter GC/MS Acquisition B.07.03. The ATUNE.CSV created from versions pre-dating B.07.02 is renamed to ATUNE.CSV.txt and it contains past tune records.The mslogbk.htm logs the following messages: D:\MASSHUNTER\GCM1\5977\ATUNE.CSV has been renamed because it is not compatible. D:\MASSHUNTER\GCM1\5977\ATUNE.CSV.txt is the new name. This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MSD: G1701-90112_GCMS_Software_Installation_Guide has the wrong IP address for the QQQ and QTOF
Problem:
MSD: G1701-90112_GCMS_Software_Installation_Guide has the wrong IP address for the QQQ and QTOF Page 42 has 192.168.245.12 - QQQ and QTOF Page 43 has 192.168.245.11 - GC
Temporary Solution:
Yhe QQQ and QTOF IP address, the correct address should be 192.168.254.12. The GC IP address, the correct address should be 192.168.254.11.
Fix Information:
n/a
Keyword:
One-line Description:
MSD: The configuration file which holds the HS license is deleted after Masshunter configuration update.
Problem:
System is headspace (B.01.06) with MassHunter (B.07.01). When updating instrument configuration by clicking ok, the configuration license file is deleted. This causes the headspace license key to be deleted. Next boot up of the MassHutner GCMS Acquistion software causing a prompt for the license key.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ, Add / Remove ALL monitors will generate an exception error
Problem:
Add / Remove ALL available Monitors in / from Selected Monitors Instrument Control -> Instrument -> Edit Monitors -> add/remove ALL available Monitors to/from Selected Monitors (Do not use Add button, but double click over each monitor) always throws the following exception: InvalidArgument=Value of '-1' is not valid for 'index' Parameter name: index NOTE: Select ALL monitors except the last Available will not generate the exception. The exception occurs when the last AVAILABLE Monitor is selected (by double clicking over it).
Temporary Solution:
Use Add / Remove button instead of double clicking the monitor name.
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ B.07.02 Initialize MS Interface throws Alert window.
Problem:
From Tune and Vacuum Control Window Click Vacuum -> Initialize MS Interface -> this throws Alert window and never starts the Initialization of MS Interface. Alert: Agilent reCCommends that you exit MassHunter and power cycle the MSD.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MPV valve on 7890 is not controlled Properly
Problem:
MPV valve on 7890 is not controlled Properly
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ: MassHunter Acquisition B.07.01 and G1701FA Envquant not printing the correct detailed analysis parameters with 5977 Configured
Problem:
If one configures a 5977 system in the msdchem.ini file it sets ms_id=0. When printing from acquisition envinit.mac sees ms_id=0 and uses the macro from gcmacros folder. This then does not show the target ions or qualifiers. This only happens if a 5977 is configured, 5973 and 5975 work fine because the ms_id is either a 3 or 5.
Temporary Solution:
The modified attached macro envinit.mac looks at ms_type and now the report is correct. A point patch is available.
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
Inst# can not be launch with QQQ RTL method
Problem:
1. Configure 7890-7000 QQQ as Inst#4 2. Launch Inst#4 3. Show GC Status or MS Status 4. load RTL method 5. Close Inst#4 6. Re-launch Inst#4 > Acq SW became "No response".
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MSD: Low mass tune issue
Problem:
After low mass tuning, the system’s auto tune still keeps to capture ions 69/131/219 even when selecting new tune.
Temporary Solution:
Load a new tune file and check the parameters and then start the new tune.
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
QQQ: Running a method with multiple time segments with MRM plus SCAN could cause the system to go OFFLINE
Problem:
Running a method with multiple time segments with MRM plus SCAN could cause the system to go OFFLINE and when this occurs a power cycle will be required to re-establish the communication.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ 5977: Filament change is not saved and used in BFB_atune
Problem:
If atune.u is run with filament 2 and saved and the bfb_atune.u is saved to use filament 2, this does not stay. After saving filament to 2, and saving, then running the bfb_atune.u macro, the filament gets switched to filament 1.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ: Some 5975 Manual Tune trackbar sliders do not respond to right/left arrow key. Divergent behavior. Needed for test automation.
Problem:
Some 5975 Manual Tune trackbar sliders do not respond to right/left arrow key. The behavior is different than 5977. In test automation, we select the appropriate text box control, the matching trackbar control, send the right/left arrow keys, and then check if the value increment/decrements accordingly.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
SQ: NCI datafile does not reflect that it was acquired in NCI mode for MassHunter, ion polarity indicates positive
Problem:
This issue is only for single quad datafiles. Quant and Qual both show the ion polarity of all data file types for single quads as positive, even if it was acquired in negative mode for CI. The sample information is correct. It uses an NCI tune file and a method with the name NCI in it. The instrument’s polarity is tied to the acquisition tune file so if that is correct it’s all good.
Temporary Solution:
To validate the datafile type was acquired in NCI mode, look at the datafile in ChemStation datafile format.
If you look at the ChemStation data file format section, the pre_post.ini does indicate the mode of operation:
cimode = 0 means no 1 means yes
cipolarity = 0 means positive 1 means negative (0=PCI, 1=NCI)
ciflow = displays the CI Flow Module reagent gas flow rate
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
QQQ 7010: Gain Factor Used in Tune causing isotope ratio issues.
Problem:
The 7010 generates significantly more ion current than the 7000 series ion sources. The higher ion current that ends up at the detector often reaches or exceeds the saturation conditions on the electron multiplier resulting in isotope ratios exceeding the limits that we define as acceptable.
Temporary Solution:
Lower the abundance for the most abundant ion to be below 5M and then run Tune Evaluation for validation.
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MSD: Autorelock does not adjust the flow or pressure from the method
Problem:
Running a sequence with AutoRelock, but it looks like the AutoRelock is not executed.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
QTOF: QTOF Conditioning 7200B, values for -12V and +15V are not showing the correct actuals.
Problem:
QTOF Conditioning 7200B, values for -12V and +15V are not showing the correct actuals. The display values are not the actual values.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
Qual's Extract Defined Chromatograms fails to extract GC signal in nativity MassHunter data files
Problem:
What is happening is that a file collected under GCMS Acquisition B.07.02 for GC data only the GC signal can be extracted two of three ways. Extract Chromatogram and Extract all non-MS signals works as expected however the Extract Defined Chromatograms, using the drop down list item of “GC1” fails and gives a “No data points found” message.
Temporary Solution:
Run GCMS translator B.07.02 over the file (this should not be required as the file is collected in native MassHunter format) the Extract Defined Chromatograms, using the drop down list item of “GC1”.
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
CTC: Wrong individual injection volume values in sequence table
Problem:
Accepted range of Injection volume in sequence table (Mass Hunter Acquisition B 07.03) is always from 25 to 2500 no matter what instrument and syringe is installed on PAL3. No way to enter individual volumes for 10 uL liquid syringe.
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
MSD: CTC PAL add-on software: Data are going to the SEQUENCE FOLDER instead of the METHOD folder if the CTC is installed
Problem:
If the CTC PAL add-on software is installed a SINGLE RUN is using the sequence folder instead of the METHOD folder.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
TQ: RTL Calibration doesn’t correctly handle MRM data
Problem:
There is a problem with retention time locking a MRM method. When running an RTL acquisition the locking is done on a specified transition. The locking compound transition in this case is 323.9 -> 253.9; this transition is also in each of the appropriate time segments. The standard however also has another compound with the same MRM transition that elutes a little later. The software is choosing the RT on what looks to be higher response values, which then provides the RTL calculation with correct and incorrect RTs, providing a bad R2 value.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ: Prepost.ini showing incorrect sample prep method when overrided in Sequence Editor.
Problem:
Created meth1 and prep1 and assigned prep1 to meth1. Created meth2 and prep2 and assigned prep2 to meth2. In a three line sequence using meth1, using the Sample Prep File Name field to change the sample prep method to be used to prep2. The sequence ran the correct sample prep methods. While looking at prepost.ini within the first data file, it listed prep1, but it should have listed prep2, which was the sample prep method that was used.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
QTOF: If bakeout time is above 23 hours the time calculation will be incorrect.
Problem:
If set the bake out to 23 hours, all seems to be ok. If set to 24, 25 or even higher it seems that 20 hours are reduce from the calculated time. 24 hours would be 4 hours; likewise, 25 hours would be 5 hours.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
[Untranslation]First entry of Audit trail for Method, Sequence and Configuration is still in English.
Problem:
1. Print detailed audit trail for Method, Sequence and Configuration. 2. First entry of each is still in English.
Temporary Solution:
Default configuration files are being used. All recorded audits are localized.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
CTC: Unexpected Exception Error in Logbook When Trying to Run Sequence with LS tool.
Problem:
This error message occurs when trying to run a three-line sequence use the LS Tool while trying to perform a single sample overlap.
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
ECM: Only one method can be run at a time during the Sequence Table Editor
Problem:
Only one method can be run at a time during the Sequence Table Editor.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
GCMH Acquisition installer with compliance features has an issue with any ECMAPI version greater than 1.0.26.
Problem:
GCMH Acquisition installer with compliance features has an issue withany ECMAPI version greater than 1.0.26. A new hotfix was introduced by the ECM group and the GCMS Acq fails to work with the new version.
Temporary Solution:
A point patch is available for MassHunter GCMS Acquisition B.07.03 when using ECM 3.4.1 SP2 Hotfix 1.
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
Any vial position 2-16 on rear tower 7693N is causing 6890N GC to halt.
Problem:
Any vial position 2-16 on rear tower 7693N is causing 6890N GC to halt. If Vial 1 from the rear tower is injected it will work fine. This deffect will only show on 6890N with both conditions: - No autotray - Different front and rear turrets
Temporary Solution:
Point Patch available. Please refer to SN regarding B.07.03.
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
Sequence won't be aborted on GCMS Acquisition with sequence action set to abort when barcodes mismatch.
Problem:
1. Create a method with HeadSpace as Inlet source, single extraction.
2. Create a 5-line sequence, with Line 1 using wrong barcode, Line 2, Line 4-5 with blank barcode and only Line 3 with correct barcode.
3. When running sequence, select "Use barcode and Don't inject;Abort the sequence" for Sequence Barcode Option.
Wrong barcode line and blank barcode lines are skipped but the sequence continues not aborted.
Please refer to the attached "instctl.log".
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
Detector on timed event in acq method causes large spike on 5977
Problem:
Using a timed program event to turn off the detector (filament) after the first peak elutes then turn it back on after the solvent Elutes. However when the detector comes on there is a verylarge spike.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Collected GC signal files (*.CH) cannot be consistently loaded
Problem:
When MassHunter GCMS Acquisition is used to collect signals from GC detectors, the resultant *.CH files may not display properly. This has been traced down to a faulty scaling value placed in the file
Temporary Solution:
Point Patch available. See Service Note G1701-232
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
MH Compliance mode: Running a sequence with external sample configured like Headspace or CTC s will STOP with an error: “input string was in the wrong format”
Problem:
MH Compliance mode: Running a sequence with external sample configured like Headspace or CTC s will STOP with an error: “input string was in the wrong format”
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
CTC: could not override injection volume in the sequence table on RSI instrument
Problem:
Set up a method with the 10 ul liq syringe. Injection volume was set to 1. Created a sequence and for the second and third sample, changed injection volume to 2 and 3. Simulate sequence did not pick up any errors. Ran the sequence however, it showed aspirating 1 ul for each sample. The sample_info.xml file under the data file did show the correct injection volume of 2 and 3. Saw similar behavior with the HS syringe. On the RTC, saw the HS override inejction volume work OK. The liq syringe however, would not allow the entry of 2 or 3 in sequence table.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
B0703: Backflush Wizard stops with error message while configured for QTOF
Problem:
BackFlush should be working on all of the models, QTOF is not listed in the script to support this feature.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
MSD: MSD goes offline when try to run method with burnt out filament and override solvent delay
Problem:
Run a method with a burnt out filament and also overriding the solvent delay will cause the system to go offline. System seems to stall and when it "comes back" MS is offline. Using help/reconnect will not reestablish the connection.
Temporary Solution:
Power cycle the MSD and reboot the PC to reestablish the connection with the system.
Fix Information:
n/a
Keyword:
One-line Description:
GC-QTOF Autotune: Detector Gain Problems
Problem:
In EI and PCI modes, the detector gain does not work properly due to emission current adjust issues. The detector gain function SetDetectorGain() calls the emission current adjust function AdjstEmisson(TargetMass, TargetAbundance): the emission current adjustment does not converge, and the emission current thrashes between low and high settings (see attached data). In EI, PCI, and NCI modes, after completion of detector gain, the emission current must be readjusted to restore the base peak abundance of 1.2E6 counts. Currently, the autotune does not readjust the emission current. After the detector gain portion of the autotune completes, the next step in the autotune is Quad Tuning. The emission current must be readjusted so that the abundance is high enough for stable Quad Tuning.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
DQ: Programmatic increment of blank vial upon decision failure of blank does not properly set _alsbottle2 B.07.03 MassHunter Acq
Problem:
When a blank is run and it FAILS, if the current counter indicates to skip to the next blank, only_ALSBOTTLE is incremented, leaving _ALSBOTTLE2 as-is such that it will continuerunning the ‘contaminated’ blank vial. If that vial is truly contaminatedand continues to fail, the decision process will appear to cycle through allthe blank vials when in actuality it keeps running the same one. REARINLET ONLY
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
ECM; When compliance is installed the append keyword still shows up in sequence.
Problem:
Since in compliant mode you can only use 1 method in sequence, however the append keyword still shows up.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
ECM; When Compliance is installed, the usedecisions keyword is still available.
Problem:
In compliance mode decision based sequencing does not work. the usedecision keyword should be removed from sequence
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
SQ; 5977B mini-display or GC LCP do not display error messages of the the single quad.
Problem:
The mini-display and the GC LCP was not designed to report the 5977B error status if one occurs.
Temporary Solution:
User can use the WUI to view the status of the instrument and also to view any error messages.
Fix Information:
n/a
Keyword:
One-line Description:
Drug Quant will not automatically upload data to ECM during sequence for B.07.03 & B.07.04 (Drug mode only)
Problem:
The ECM datafile upload brakes during a Drug Mode sequence in B.07.03 - Repaired in the attached nticrunmeth.mac file, which goes to GCMS\MSEXE folder (for B.07.03)
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
The name of the Quant batch doesn’t always reset when you start another sequence (for B.07.03 & B.07.04)
Problem:
The NAME of the MH Quant Batch created during automation in Drug Mode is not reset. The new batch will have the same TimeStamp in the the datapath as the previous one - Repaired in the attached startseq.mac, which goes to GCMS\DRUGMACS folder (for B.07.03 and B.07.04) The ECM Quant batch files with space in the names could not be handled by MH Quant Actions script - Repaired in the attached SendToOpenLabECM.quant.script
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
ECM; Lock and Switch user does not track the users authorization level correctly.
Problem:
Logged into the system as a manager and have full access. Then switching from the manager level to the Analyst 1 level using the LOCK and SWITCH. This part is fine, however the access for the Analyst 1 is still at the Manger level.
Temporary Solution:
Log out of instrument control and then log back in with the correct user name if the levels are different.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
MSD; MassHunter Acq B.07.04 has wrong time stamp format so Quant and Qual cannot read it.
Problem:
Current format of TuneFileTime$, and what is written intosample_info.xml:
Monday, January 04, 2016 10:50:53 AM (UTC-05:00)
What is needed in sample_info.xml : 2016-01-04T10:50:53-05:00
Temporary Solution:
Point patch macro is available for this.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
SQ; Inlet Location "Rear" not enable in manual injection (MassHunter Acq)
Problem:
When you try to select Inlet Location "Rear" in manual injection mode, this results to be not enable, only front location is available. Is not possible to make a manual injection in rear location.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
ECM, Password creation for the MassHunter Acquisition looks for a maximum of 12 characters.
Problem:
MassHunter Acquisition has a maximum of 12 characters for the password.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
5977B HES seed values (default starting point) for the HES Tune could cause poor peak shapes.
Problem:
Some units don’t tune very well with the default HES tune values. Peak shapes are not ideal or are very bad. However, they can be manually tuned and they look good. However, customers would need to get a new default tune file with the new seed values otherwise they would risk having poor looking peak shapes or poor tunes.
Temporary Solution:
Point Patch is available for this issue with File Name atune7x.mac. Prior to replace or copy the atune7x.mac in your GCMS\MSEXE make sure to rename the original file with extension .ORG.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
QTOF Firmware 022 getting mid mirror and DC Post Filter Faults
Problem:
Was running the system on B.07.02 with version G7200.01.21 and there is no problem with the system. Loaded software B.07.04 with version G7200.01.22 and there is a problem with the system generating mid mirror faults and also DC Post Filter error messages and causing the system to shut down.
Temporary Solution:
Reflash the firmware with G7000.01.21 and then reflash again with firmware version G7000.01.22.
Fix Information:
n/a
Keyword:
One-line Description:
QTOF; Advanced Autotune 'Set EDR' run time information is not shown
Problem:
Each of the advanced autotune buttons should show how long that step takes to run in an information line of text below the buttons when the mouse is over the button. The 'Set EDR' button does not update this information when the mouse cursor is over the button.
Temporary Solution:
The text for Set EDR should be 'Set EDR takes approximately 1.0 minute to run'.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
QTOF Advanced autotune detector 'Gain' and 'Set EDR' leave the emission current set to 50 uA.
Problem:
The 'Gain' and 'Set EDR' advanced autotune functions set the emission for ion 264 or 130. Both of these should have no or very low signal, so the emission ends up of the autotune max limit of 50. This is OK for setting the gain but is too high for normal operation. The expected value for emission is around 5 uA. the gain and set EDR functions should save the existing emission current and restore it when they are finishing.
Temporary Solution:
Go to manual tune and restore the emission setting.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
QTOF advanced autotune 'Set EDR' calls wrong function
Problem:
The 'Set EDR' is calling the SetDetectorGain function. This can be checked by setting the 4GHz high resolution mode in the manual tune acquisition parameters tab. When the Set EDR is done the acquisition mode should be 2GHz EDR. The detector parameters should also be updated. .
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
QTOF: There are issues with N2OFF tune with bad final PMT value
Problem:
There is a combination of effects which is occuring. At the end of the gain calibration, there is a limit check for the PMT and emission current which is not being rechecked and as a result at times the calculated PMT and emission current values are incorrect which are then saved to the tune file.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
MSD; MassHunter Acquisition Software can't open in 7890B/5977 with 3rd party Gerstel TDS inlet.
Problem:
The error MSINSTLR.exe appear when Gerstel software is loaded on MassHunter Acquisition B.07.03 and B.07.04. [This problem is related to the 3rd Party software.]
Temporary Solution:
Downgrade to B.07.01, Acq Softwre is working well.
Fix Information:
n/a
Keyword:
One-line Description:
SQ; unable to run FID only method and MS only method in same sequence
Problem:
Investigated the MassHunter error generation, tried the following isolating the hardware as requested.
GC Manual, GC/MS Manual, GCCTC and GCMS-CTC all running the customers FID.M without incident.
The problem was only observed when running a sequence which included both the FID.M and GCMS.M in the same table. Starting with the MS.m the injection ran fine, 2nd line the FID.M loaded ok the CTC made the injection and the run started and the real time display appeared normal with the FID plot observed no problem. The 3 rd line CTC made the injection cycle complete to home position, the GC hardware went into run, MH SW did not start run time and created the errors found as in the previous cases. (errors already posted on this site ). Also both the FID.M runs from lines 1 and 2 had no data files generated in the sequence folder, no data collection even for line 2 of the sequence which appeared to be normal.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
QQQ; GCMS Autotune Report Time Issue, showing current local time as well as the UTC time on the tune report
Problem:
Autotune Report for TQ is having 4 hours time difference between the Tune Date & Time and the Reported Time. Upon investigation, there are two times being reported: the time the tune was done and the time the report was printed. The issue is that one of the times is showing the current local time which the other time is showing the UTC.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
QTOF, PMT value from autotune is greater than 1100V which should be the maximum value
Problem:
At the beginning of the autotune the PMT could be in the 860-900 range but at the end of the autotune one could see values in the 20,000+ range. This is also a gasoff tune.
Temporary Solution:
Manually go and enter in valid entries for the PMT and use the Advance Autotune functions.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
MSD: Not Ready Status turn on in 7890GC after injection due to "MS is not ready"
Problem:
In 7890B/5977B (LVDS) with MassHunter Acq B.07.04, GC front panel Not Ready status turn on after injection due to "MS is not ready".
STATUS - Not Ready
Run in progress
Host system not ready
MSD is not ready
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
TQ: Fast Scan doesn't work properly for TQ MS2 fast scan only, MRM+ fast scan and SIM+ fast scan
Problem:
The features of Fast Scan does not work properly for these three modes
(MS2): fast scan only,
MRM+ fast scan and
SIM+ fast scan.
The peak 272 from OFN could be missed. The part of MRM and SIM in mix-mode is functionally correct, but the part of fast scan in mix-mode is missing the peak.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: _secExpbarcode$ not being stored properly in B.07.04.
Problem:
The expected bar code reading was not being sent back correctly when using dual injection.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
TQ: large difference of scan speed for MS2 regular scan between calculaton and actual values for ms range > 800 amu
Problem:
For regular scan (MS2), the value calculated from the settings in Method Editor has large difference (> 20%) from the actual value based on the acquired data file for scam mass range > 800 amu; while the same comparison for the values for scan mass range < 700 amu has only <5% difference.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
7650 Tower is not working properly, other towers are when varying the injection volumes.
Problem:
MassHunter GC/MS Acquisition is detecting that the 7650 tower is connected however it is reading the tower as the wrong type. Standard injection volumes are possible but using fractions of a microliter injection is not possible.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
MSD: Sequence Table Editor (STE) Does Not Warn User if Quant Method is Not Found.
Problem:
GCMS Acq in Drug Mode with Quant in Drug Mode. Performed Intelligent Sequencing. In the Sequence Table Editor, the DA Method File location was pointing to the wrong location. There is no warning message to inform the user that the Quant method is not in the correction. The system will check for the acquisition methods.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MS does not establish communication after VENT
Problem:
Shutting down GC & MS for maintenance, using "VENT" for MS. Power OFF both instrument. On start-up, the MS shows no communication established. User is forced to close out GCMS acquisition and do a hard reboot of the systems to recover the system.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
ECM: user can switch methods during a sequence but system is mixed up after doing so.
Problem:
The sequence was paused during the run and then loaded another method and continued with the same sequence log file. The sequence log file did show the method was being switched. The log file states that there was a fatal error and then it stopped after the end of the second data file was acquired.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
MSD: For 5977 diffusion pump systems the Ion gauge does not turned off during vent cycle
Problem:
Only on a diffusion system, If ion gauge is on and the vent cycle is initiated from tune and vacuum control, the ion gauge does not automatically turn off. On a turbo system the ion gauge goes to "OFF" immediately after clicking on the vent button as expected. It was noticed that the gauge becomes "hot" during vent cycle on the diffusion system. This could result in a premature hardware failure of the ion gauge only on ion diffusion pump systems.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
MSD: It is possible to EDIT the sequence table MULTIPLE times with multiple screens remaining.
Problem:
While running a sequence if you edit the sequence table by mistake multiple times it will result in multiple versions of the sequence table being displayed.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
JPN: report; unnecessarily prints an extra white page always print our for JPN dMRM Method parameter report.
Problem:
1. load dMRM method. (Y_dMRM.M.zip) 2. Method > Print Method (select all check box) 3. report is created. 4. dMRM method report always has unnecessarily extra white page
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
MH with ECM: Retrieve a data file will add an extra subdirectory
Problem:
If you retrieve a data file from the ECM server it will add an extra subdirectory.
Selecting the data file and asked to "Unzip *.SSIZIP files as subfolders."
The result was the following, the *.d directory got produced two times.
\example.d
\example.d
all the files
Temporary Solution:
NOTE: this does NOT CHANGE .D.SSIZIP (and .m, too) FILES THAT RESIDE ON THE ECM SERVER IF THEY WERE UPLOADED BY BRONCO B.07.04 OR EARLIER. there is a new macro command called NoZipNest that can be used to change the way folders are zipped prior to upload to the ECM server. Users may type "NoZIpNest" in the command field of Bronco, followed by either the 'enter' key or 'execute' button. After that, files will be zipped such that the ECM 'retrieve with unzip' will no longer create nested folders. To revert back, type "NoZipNest 0". NOTE 2: methods and data that are zipped with this new structure CANNOT BE RETRIEVED USING MSD CHEMSTATION DATA ANALYSIS 'LOAD FROM ECM' unless a patch is installed. I have attached that patch to this defect. The patch serves to indicate how trivial it is to determine if there is or is not a nested folder in the unzipped file. I strongly encourage the 'unzip' action provided by the ECM Client be updated to determine the existence of the 'nested' structure and handle it accordingly. NOTE 3: existing customers can retrieve from ECM WITHOUT using the 'unzip' feature, and then use WinZip to extract the files - NO NESTING WILL RESULT.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
QQQ: Changing MS IP gets SmartCard NotConfig error
Problem:
The test processes: Do not open MassHunter GC/MS Acquisition MS Configure. Open Web User Interface (WUI); Change MS IP in WUI-NetConfig from 192.168.254.12 to 192.168.254.10 Power cycle MS, The MS IP showing on LUI of MS is updated correctly to new IP; Configure instrument with new IP, then launch Instrument Control; Instrument Control starts up properly. Check WUI (regardless Instrument Control is opened or closed) , on Status panel, Smartcard section, IP Address N.A.=getNetworkConfig ERROR-2 Click button "Return to Main Menu", get ERROR 404
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Configure MS Gases Info Does Not Appear In Audit Trail
Problem:
Startup an instrument configured for JetClean, the Configure MS Gases Automatically appears. When You Select Ok, this generates a Method Save. Looking in the Audit trail, there is no documentation of the save.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
Simulate sequence did not work if one of the lines has an invalid method or no method specified
Problem:
Created a sequence that had some errors and one of them was a missing method name or invalid method name (also had duplicate data file name). OK'd sequence table and saved sequence. Selected Simulate sequence. Received an error Input string was not in correct format on the message line.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MassHunter in Compliance mode: Not possible to change methods within a sequence
Problem:
The sequence table editor (STE) has a limitation of only one method can be used for MassHunter in Compliance mode. The STE does not have the method option to be used in the Compliance mode of operation.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Leaving the Secured Control Panel open for a period of time could cause the system to lockup.
Problem:
Leaving the secured control mode up and idle in "Standby" mode overnight could cause the system to lockup. Just closing the application is not applicable, one will need to use the task manager to close the application.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
TQ: PDF auto tune file not generated due to missing templates
Problem:
If a ChemStation/Workstation has an earlier version of MassHunter GC/MS Acquisition software loaded it is possible not all of the templates will be copied over. While tuning the MS the following message "an exception has occurred saving an autotune report as a PDF file..."
Temporary Solution:
For service updates and point patch updates loading on top of an existing software version is okay, however when changing from one revision to another, it is recommended to uninstall the existing version and then install the new software package.
Fix Information:
n/a
Keyword:
One-line Description:
TQ: When using dMRM the precursor ions shown in Qualitative analysis do not reflect the ions specified in acquisition method for methods created on previous revisions of acquisition.
Problem:
Setting up the dMRM acquisition and running the data. Looking in acquisition the precursor ion and the product ions look good. When you look at the data in qual the precusor ions do not match up with the ones in the data acquisition. the precusor ions are less than the product ions. This has shown up on existing methods and not on newly created methods.
Temporary Solution:
A point patch is available for this. Please contact your local representative for the patch.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05 SR1.
Keyword:
One-line Description:
TQ: When more than 4 MRM scans were defined for a time segment an error is displayed that 4 MRM scans is the limit. The correct limit is 100 MRM scans per time segment.
Problem:
User is given a warning about One can ONLY have 4 MRM scans in a time segment; but it is possible to have 100 scans.
Temporary Solution:
A point patch is available for this. Please contact your local group for additional information.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05 SR1.
Keyword:
One-line Description:
TQ: dsp 5.1 firmware fault which then clears almost immediately, this has shown up for the B.07.05 ONLY release, not in previous versions.
Problem:
Run with collision energy default set to 10 eV, then while it is running change the collision energy to 20eV, then back again to 10eV When you hit enter after changing the collision energy, the status at the bottom reflects a dsp 5.1 firmware fault which then clears almost immediately. Since the fault clears, the end result is still achievable.
Temporary Solution:
If this was an actual error message was real, then no data will be collected.
Fix Information:
n/a
Keyword:
One-line Description:
Wiley Library: Wrong Compound information of CAS No 120-61-6 in Wiley10Nist14.L and Wiley10Nist11.L
Problem:
CAS No 120-61-6 in Wiley10Nist14.L, hit to 1,4-Benzenedicarboxylic acid, dimethyl ester. But the spectrum and MW and Formula are wrong. As the result, MW = 189.1 and Formular C7H11NO5, but the correct result is MW = 194.1, Formula C10H10O4. And the structure is also wrong. Wiley10Nist11 and Wiley10Nist14 have wrong information. Nist2014 and Wiley9Nist11 have correct information.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Data System: Remoting Subsystem Error during startup of MassHunter Acquisition if Computer Name is Numeric only
Problem:
This error occurs on Acquisition startup if the computer name is numeric. Error: "An error has occurred initializing the MassHunter GC/MS Acquisition Remoting Subsystem: The requested name is valid, but no data of the requested type was found. Please close MassHunter GC/MS Acquisition and ensure all msinsctl.exe processes have been killed, or alternatively reboot your system and then restart MassHunter GC/MS Acquisition"
Temporary Solution:
Changing the computer name to alpha-numeric causes this error to go away.
Fix Information:
n/a
Keyword:
One-line Description:
TQ: The unit for dwell time in MRM mode or SIM mode in MH Acq B.07.05 should be seconds but is displayed as msec.
Problem:
In MassHunter GC/MS Acq B.07.05, MS method editor design has changed. Dwell time unit is msec in SIM or MRM mode; labels are showing incorrect units to be used. But Dwell time unit is sec in MassHunter GC/MS Acq B.07.05.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05 SR1.
Keyword:
One-line Description:
SQ: An injection time set longer than solvent delay results in no data being collected.
Problem:
When injection time is longer than solvent delay results in no data collection.
Temporary Solution:
Make sure that solvent delay is longer than injection time. Alternative fix: set a short solvent delay and then add a timed event to MS params to turn filament off for the "real" solvent delay. AEG
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05 SR1.
Keyword:
One-line Description:
HS with 9000 GC, Inlet Injection Parameters panel has a rear option
Problem:
MassHunter GC/MS Acquisition B.07.05 with Headspace B.01.07.2. Configured with a 9000 GC instrument with a 7697 or G1888. Went into the Inlet Injection Parameters panel and selected Headspace as the injection source. Both Front and Rear Inlet locations were available, it should only be Front.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Sequence table: The Rear Sample _miscinfo$ field is not retained when running in Unlinked mode.
Problem:
The front sample is receiving the Rear Sample’s miscinfo$ (i.e. comment in STE), and the rear sample ends up with NO _miscinfo$. This happens with gc and gcms configurations using unlinked mode.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05 SR1.
Keyword:
One-line Description:
TQ: Calibration valve on/off status will not update until the user changes window focus to a tab other than manual tune.
Problem:
In Manual Tune tab, when the CI cal valve is checked On, the status stays Off. If you move to any tab other than Manual Tune, the status changes to On. The same applies going in the opposite direction (status from On to Off).
Temporary Solution:
User needs to move to another field to display updates.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05 SR1.
Keyword:
One-line Description:
6890 GC detector signal naming problem with Masshunter Acq B.07.05
Problem:
When a GC detector signal is collected for 6890 the signal name for a front detector is front detector.ch and back detector.ch for the rear detector. This is counter to the tradition of naming based on detector type (ie, FID1a.ch for a front signal.) This problem has already been corrected (a fixed GCRC.dll was created). The solution has been tested but no TT entry had been made.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Exception occurred when closing GC/MS Acquisition
Problem:
This error occurs infrequently and is very random.
Temporary Solution:
Continue past the exception, nothing serious has happened.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: If a GC 7890 is already in use, the identity of the first user is not reported to the second user
Problem:
This problem only affects users in the remote connection situation. I tried to start an instrument while another PC was already running the GC that my instrument is configured with. An error message showed "ChemStation can not finish its initialization cycle". Opening the log, the log stated the GC is offline, but not who is using it.
Temporary Solution:
Do not connect to a GC that another PC is already connected to.
Fix Information:
Has been resolved in B.04.01
Keyword:
One-line Description:
QQQ: Wrong data file shown on System UI after "Pause" was used on the sequence
Problem:
When a sequence is paused, it appears that the wrong data file name is displayed next to the vial icon on the user interface.
Temporary Solution:
This is the designed behavior. UNLESS a SEQUENCE is running, the displayed data file name AND the loaded method will ALWAYS be the 'Run Method' CP variables. When a sequence is run, the current value of DATAFILE$ is saved. Whether the sequence is paused or is allowed to complete normally, the previously saved DATAFILE$ value is restored upon completion or pause. Since the Vial picture panel has the displayed data file name mapped to the variable DATAFILE$, the file name displayed in the panel will revert to that value when the sequence is complete or paused. This saving and restoring is accomplished as part of the Sequence Macro Machine.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: When hovering the mouse over the icons no assisting info is shown
Problem:
When I put the mouse over the icons on the Instrument Control panel, no assisting info is shown either on left bottom corner of the window or on top of the icon.
Temporary Solution:
Read the online help.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: When the sample type is Keyword, auto fill/increment should skip that sample
Problem:
In the sequence table, when the sample type is "Keyword", auto fill/increment is meaningless for many columns. So auto fill/increment should skip the samples with a type "Keyword"
Temporary Solution:
n/a
Fix Information:
Resolved in released version B.04.01 as "User Misunderstanding"
Keyword:
One-line Description:
QQQ: Error message can be more detailed when error occurs while importing Sequence Table from XML
Problem:
When importing a Sequence Table from a XML file created from the SequenceTableAssistant, if some file contains an item in a wrong format, there is error message on the status line, and importing stops. Anything after the line in a wrong format is chopped. This is expected behavior. However, it would be better to show a more detailed error message in the status line, such as on which line and column this error happened. It would be easier for the user to then locate the error.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Any directory can be selected and then filled into the Method File field in Sequence Table Editor
Problem:
In the Sequence Table Editor, using the Browse button to select method, any arbitrary directory can be selected and then filled into the Method File column. Preferably, only .m should be allowed.
Temporary Solution:
Only select .m directories.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Inconsistent information in sequence.log with Sequence Table Editor
Problem:
In Sequence Table Editor, load a method from ...GCMS\1\METHODS using Browse button, and then run sequence simulation. The verification result show that the method path is ...GCMS\2\METHODS.
Temporary Solution:
The default paths are related to where the initial method was loaded from in the default instrument control panel.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Edit Entire Method Missing from Method Menu
Problem:
There is no menu item (or icon) that sequentially presents all the edit method panels to the user.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Logbook doesn't provide error information on invalid vial number
Problem:
If the Sequence Table contains invalid vial information, the sequence will hang or abort at the problem line. Status line shows that an error has occurred, but no error information is given in the logbook. In one case, the logbook stated all data was acquired.
Temporary Solution:
n/a
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: Qualitative Analysis method cannot be selected by Browse button in Sequence Table Editor
Problem:
In DA method file of Sequence Table Editor, Qualitative Analysis method (.m folder) cannot be selected by the browse button. Only files can be selected (default file is .quantmethod., other format is supported too).
Temporary Solution:
User can type in the full name of the Qualitative Analysis method with the '.m' suffix and this will work.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Logbook and Printer Icons Always Look Grayed Out
Problem:
The Logbook and Printer Icons are the same color as grayed-out icons. They are still accessible but it is confusing to tell if they are active just be looking at them.
Temporary Solution:
Logbook and Printer icons are indeed always active.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Launching Qualitative Analysis causes Sequence Table Editor layout to disappear
Problem:
Steps to reproduce: 1) Start GC/MS Acquisition, open the Sequence Table Editor, and add some columns. Save them to a layout (for easy retrieval). OK the panel. 2) Run Qualitative Analysis. 3) Go back to GC/MS Acquisition, and open the Sequence Table Editor again, it has now reverted to 'default' layout.
Temporary Solution:
Do not use Qualitative Analysis while editing the Sequence Table.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: 7693A Injector Panel in Method Editor Needs Scroll Bar
Problem:
After installing the new driver (25), it seemed as though the 7693A Injection Types section was missing from the panel. The window get sized a certain way and it looks like the panel is complete.
Temporary Solution:
One needs to stretch the panel in order see the additional parameters. A scroll bar should be added to this panel so the users know the parameters are there. Full feature support for the 7693 will not be supported on the initial release of B.04.00
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: PAL: In the Sequence Table editor, the "Tray Name" column does not have a selection list
Problem:
The user must enter the tray name manually in the column. The name is case-sensitive and must match exactly with one of the names in the Location Map. Otherwise, the vial will not be found.
Temporary Solution:
Click the "Instrument->CTC PAL Show Location Mapping..." menu item to display the Location Map. Note the tray name to be used. Close the Location Map and open the Sequence Table. Type in the tray name exactly for each entry in the table. If the same tray is used for multiple samples in the sequence table, the "fill-down" feature can be used to duplicate the name in the rows below the current entry.
Fix Information:
Has been fixed in MassHunter GCMS Acquisition B.05.02.
Keyword:
One-line Description:
QQQ: Where is Injection Volume field in Sequence Table?
Problem:
Is there an injection volume field configurable in the sample log table. The only available field seemed to be Vol. Does this mean injection volume? If so, it should state injection volume and not be abbreviated.
Temporary Solution:
Yes, "Vol." does in fact mean injection volume.
Fix Information:
Resolved in released version B.04.00 as "User Misunderstanding"
Keyword:
One-line Description:
QQQ: PAL: CTC PAL - Problems if a vial is not found during the sequence
Problem:
If a vial is not found when running a sequence with the CTC PAL, the sequence stops and appropriate messages are logged in the sequence log file as well as the log book. Although everything appears to be fine, there may be problems when starting the next run. The next run may hang and the program crash when the run is aborted.
Temporary Solution:
When the "No vial found ..." message is displayed, do not start a 2nd run. Close and restart the application. Correct the vial location in the Sequence Table or move the vial to the right location. If the error persists, do the following: · If GC/MS Acquisition is still running, close it · In the Windows Task Manager, Process tab, end the following processes if they are listed: msinsctl.exe CTCPalPlus.exe CTCPAL~1.exe (you end these processes by right-clicking on them, then clicking on "End Process") · Power cycle the GC 7890 · Power cycle the CTC PAL · Restart GC/MS Acquisition In some situations, if the above does not fully correct the problem, you should reboot your PC.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: Always Says User Aborted Run Even If an Error Occurred
Problem:
The logbook always says User aborted run after it lists the correct error. User aborted run should only be used when the user stops the run from the software. For example, if an ALS injector error occurs, the logbook should not say the user aborted run.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: No way to create a dual injection sequence
Problem:
Method setup allows method specified with dual injection. There is no way however, in the sequence to set up a dual injection sequence.
Temporary Solution:
Do not run dual injection in the B.04.00 release.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: MS Connected To... on Start Run Panel Does Not Save the "Rear" option for Valve
Problem:
When Valve is selected as the Injection Source, one can change the MS Connect to section from front to rear. On this system, the MS is physically connected in the rear, but it would not save that option. This does not happen with the ALS.
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.05.01
Keyword:
One-line Description:
QQQ: Msinsctl.exe crashes when Solvent Elimination Calculator Button is selected on MMI
Problem:
Selected the Solvent Elimination Calculator button on the MMI (PTV2) Inlet panel. GC/MS Acquisition immediately stopped working.
Temporary Solution:
Don’t select that button.
Fix Information:
Fixed in the B.04.00 release.
Keyword:
One-line Description:
PAL - Invalid injection volume in the sequence
Problem:
Added Vol. column to the sample log table. During the sequence setup, specified an invalid volume for the first sample. OK'd panel and started sequence. The sequence started, but I got the following error "Term used is invalid. Please check injection volume and syringe." OK message. The sample goes into postrun and the software crashes. It also leaves the GC in a funny state. If I try to start back up the software, received message that "an attempt to download settings to the GC was blocked because the driver is in the wrong state". I had to reboot the GC too.
Temporary Solution:
Type in the an valid injection volume.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ: PAL - System crashes when trying to run a CTC-PAL method with the wrong syringe
Problem:
The run behavior is unpredictable when the syringe installed does not match the syringe specified in the method.
Temporary Solution:
Specify correct syringe. Make sure that the cycle and syringe selected in the CTC Method Edit panel matches the syringe installed.
Fix Information:
Fixed in released version B.05.02
Keyword:
One-line Description:
QQQ: Cal EI Val On-Off in Time Events does not work
Problem:
In the QQQ Method Editor, Cal EI Val On-Off in Time Events does not work.
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.05.01
Keyword:
One-line Description:
QQQ: Dual injection method not working properly
Problem:
Dual injection sequence is not supported; however the software allows you to specify a dual injection method. Sample is injected into both the front and rear inlets when the method is run. Two data files are created, however the rear data file does not contain an AcqData directory.
Temporary Solution:
Do not run dual injection in the B.04.00 release.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: PAL: CTC does not come online
Problem:
The following message was displayed at startup when there was a bad RS232 connector: "CTC connection problem. Exit and reboot CTC/PC if this persists."
Temporary Solution:
If this error is encountered, replace or clean the connector. If replacing or cleaning the connector does not fully correct the problem, do the following: · If GC/MS Acquisition is still running, close it · In the Windows Task Manager, Process tab, end the following processes if they are listed: msinsctl.exe CTCPalPlus.exe CTCPAL~1.exe (you end these processes by right-clicking on them, then clicking on “End Process”) · Power cycle the GC 7890 · Power cycle the CTC PAL · Run the PAL Loader program and click "Info". If that was successful, click "Start PAL", the PAL should move. If that was not successful, then power cycle the PAL. · Restart GC/MS Acquisition to make another connection. The CTC status panel will show "Ready" if there is a good connection. In some situations, if the above does not fully correct the problem, you should reboot your PC.
Fix Information:
Resolved in released version B.04.00 as "User Misunderstanding"
Keyword:
One-line Description:
QQQ: Pre and Post run programs don't run macro listed under Data Analysis
Problem:
Tried to run a method with macros specified in Pre and Post Run Programs. If the macro is specified under Instrument Control, it works correctly. Macros specified under Data Analysis however, do not work.
Temporary Solution:
Yes, this behavior was changed to ONLY RUN A [MassHunter Qualitative Analysis or MassHunter Quantitative Analysis] SCRIPT if MassHunter is being used.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: EM Voltage is not being shown in MS monitor
Problem:
EM voltage is not one of the available MS monitors to be displayed.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Not displaying the value of EM when selecting Gain Factor in QQQ Method Editor
Problem:
There is no indication of the actual EM value corresponding to the specified Gain Factor setting. It would help the user to know if the EM has reached the 3000 V limit or how much of a range is still possible.
Temporary Solution:
n/a
Fix Information:
Calculated value will be shown in Method Editor. Tune report will print out maximum gain which could be used on the system based on the EMV usage. Fixed items are in the MassHunter GC/MS Acquisition B.05.00 release version.
Keyword:
One-line Description:
QQQ: "New Method from Acquired Scan Data" displayed "MS1 Scan" as "MS2 Scan"
Problem:
Acquired data file with "MS1 Scan" but the "New Method from Acquired Scan Data" displays it as "MS2 Scan" data.
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.05.00
Keyword:
One-line Description:
QQQ: Unhandled Exception on Fr or Bck Inj panel after selection overlap option 2.
Problem:
Selected the second overlap option and then selected one of the injector panels. An unhandled exception error may occur.
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.04.00
Keyword:
One-line Description:
QQQ: GCMS Configuation Editor doesn't change QQQ quad polarity
Problem:
Although the configuration editor does update the msdchem.ini file, the settings from this file are not used to control the quad polarity.
Temporary Solution:
For the MS 7000A QQQ, ignore the quad polarity in the Configuration Editor since it doesn't have any effect on the actual quad polarity. Currently, the Agilent CE will ensure that the correct quad polarity and settings will be used, even after a firmware update.
Fix Information:
In the B.04.01 release, the quad polarity settings are grayed out in the configuration editor.
Keyword:
One-line Description:
QQQ: Allowed values on Plunger Speed are not consistent with the setting ranges
Problem:
On GC configuration panel, select "Variable" in Plunger Speed Some values can be saved, while some values cannot be saved, although all of them are within the allowed range.
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.04.01
Keyword:
One-line Description:
QQQ: Lag factor coefficients are cleared by reinstalling or reconfiguring the system
Problem:
Autotune sets the lag factor coefficients. Reconfiguring the 7000A will clear the lag factors.
Temporary Solution:
Any time the 7000A is reconfigured an Autotune is required.
Fix Information:
Fixed in revision B.05.01
Keyword:
One-line Description:
QQQ: Incorrect error message starting application when trying to connect to a GC in use by another user
Problem:
If user B tries to start GC/MS Acquisition configured with an instrument that is currently in use by user A, an error message appears during launching process: "The method is Invalid. Method must be uploaded from GC first". This is not a correct message.
Temporary Solution:
Don't try to start GC/MS Acquisition for a GC or MS instrument already in use.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: PAL: CTC-PAL shows incorrect behavior on Stop request.
Problem:
When the user clicks the stop button and the CTC-PAL is still active, the acquisition subsystem does not handle that STOP request properly.
Temporary Solution:
Do not hit the stop button.
Fix Information:
Has been fixed in MassHunter GCMS Acquisition B.05.02.
Keyword:
One-line Description:
QQQ: Irrelevant message is displayed during startup or loading of method in an offline session
Problem:
The following scenario may occur in an "offline" session of Mass Hunter GC/MS Data Acquisition when a GC 7890 is configured. When the session is started or a method is loaded, the following message may be displayed: "Method is invalid. Method must be uploaded from the GC first." After the user clicks OK, the method resolution window is displayed. The message and method resolution is not relevant for an offline session.
Temporary Solution:
Click OK on the message box and the method resolution panel, then save the method. The next time the method is loaded or the session is started with this method, the error message will not be displayed.
Fix Information:
Fixed in revision B.04.00
Keyword:
One-line Description:
QQQ: Help Does Not Include Direct Injection
Problem:
The help topic for the MMI does not talk about Direct Injection Mode, which is listed in the software drop-down Mode list.
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.05.00
Keyword:
One-line Description:
QQQ: Help Says that MMI Can Only Configure 3 Ramps
Problem:
The help topic for the MMI says that up to three ramps can be programmed, but 10 ramps can be programmed for the inlet.
Temporary Solution:
Ignore this part of the help.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Instrument control window pops up and then goes behind previously open window
Problem:
When starting the MassHunter GC/MS Acquisition program, the application will pop up on top of the last window which was being worked on. After the application finishes initialization, then the instrument control window goes behind the last window.
Temporary Solution:
Rearrange your windows on the screen to see the application.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: PAL: Occasional error when updating CTC PAL Configuration
Problem:
After clicking on the "CTC PAL Update Configuration" menu item, you see a "Trouble with download" error message.
Temporary Solution:
This seems to be an intermittent problem, so the first thing to try is just click on the menu item again. If the problem persists, close GC/MS Acquisition and restart it. The problem is then very unlikely to reoccur.
Fix Information:
Resolved in released version B.04.00 as "User Misunderstanding"
Keyword:
One-line Description:
QQQ: Problems When Stopping a Sequence with Overlapped Injections (7693 ALS)
Problem:
While running a three-line sequence, my Method was set to enable overlapped injections using the first option to obtain the next vial after the previous injection. On the first sample, after the injection was made but before the vial was returned, I selected Stop. Sequence went to line 2 but "Waiting for GC Ready" appeared even though the GC had no parameters that were not ready. Then I selected Override, but the GC seemed to be waiting for prep run. Then I selected Prep Run on the GC and it went ready. The software went into PreRun but did nothing. The status line said "loading vial". Then I selected Stop again, and the software crashed (msinsctl.exe has stopped working). I tried this scenario again but selected Pause/Stop at the end -- the sequence aborted. If the Pause/Stop is done after the overlap preps the vial, it seems to be OK and will just inject when you resume the sequence.
Temporary Solution:
1) Press the stop button on the GC front panel to force it into the idle state 2) Restart the MassHunter GCMS Acquisition software 3) Avoid aborting the sequence/run while the GC is in Pre-Run and/or the autosampler is moving. 4) Do not Stop during sequence run when Overlap Injection is selected on 7693 Autosampler.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Missing Devices.xml when running a method on 7693A Series
Problem:
Check "Data Analysis" when running a method with 7693A injector, the following message appears after the data was acquired: "Opening data file failed with error - File not found: D:\MassHunter\GCMS\1\Data\GC105_001.d\AcqData\Devices.xml"
Temporary Solution:
This "defect" was caused by not including a GC detector in the method. After adding the GC Oven Actual Temperature as a signal source, the file Devices.xml was created.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Cannot use Bar Code Reader to read barcode directly into Sequence Table
Problem:
Edit Sequence Table does not have the ability to read the Barcode label directly into the Expected Barcode field.
Temporary Solution:
Enter expected barcode value manually.
Fix Information:
Fixed in revision B.05.02
Keyword:
One-line Description:
QQQ: MassHunter Acquisition needs help edited to reflect changes to 7693/4515A BCR
Problem:
Somewhere in the Help, the changes to how the G4512A barcode reader works needs to be added.
Temporary Solution:
To disable the barcode reader in MassHunter Acquisition, the user must enter the stringin the Expected Barcode field in the sequence table for a run sequence or the Start Run panel for a run method. If this string is not entered, the barcorde reader will always be used.
Fix Information:
New feature has been added to the Run Sequence Panel which the user can disable the use of the BCR from all samples. Resolved in version B.05.00
Keyword:
One-line Description:
QQQ: The "Data File Directory" value entered in the "Start Sequence" dialog was ignored
Problem:
The "Data File Directory" value entered in the "Start Sequence" dialog was ignored when I expected it to be used.
Temporary Solution:
The Sequence Table contents override the Start Sequence panel; if one wants to use the Start Sequence dialog, then leave that column blank in the Sequence Table.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Application hangs if the GC goes into Shutdown like the Inlet flow shutdown.
Problem:
Application hangs if the GC goes into Shutdown like the Inlet flow shutdown. When the GC Shutdown, the GC must be rebooted or it will stay in a locked state.
Temporary Solution:
When the GC goes into a Shutdown state, the Workstation must be closed because the GC must be powered cycle to recover.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: PAL: Initialization of the CTC-PAL could fail/lockup the system depending on the GC
Problem:
If the GC and the CTC-PAL system are left in a bad state (improper shutdowns) it is possible when the CTC-PAL next starts communicating with the GC, the two instruments could freeze/fail/lockup.
Temporary Solution:
When this occurs, one should close and then restart GC/MS Acquisition. This is the easiest solution when this occurs. If the problem persists, do the following: · If GC/MS Acquisition is still running, close it · In the Windows Task Manager, Process tab, end the following processes if they are listed: msinsctl.exe CTCPalPlus.exe CTCPAL~1.exe (you end these processes by right-clicking on them, then clicking on "End Process") · Turn off power to MS 7000A, GC 7890, CTC PAL, LAN Switch and printer · Wait at least 1 minute · Turn on power to MS 7000A, GC 7890, CTC PAL, LAN Switch and printer · Restart GC/MS Acquisition In some situations, if the above does not fully correct the problem, you should reboot your PC and again power cycle the instruments.
Fix Information:
Was resolved in B.07.00
Keyword:
One-line Description:
QQQ: PAL: CTC PAL Controller Is Not Started Error
Problem:
On rare occasions, the user may encounter the following error, "Controller is not started", when running a method with the CTC PAL. Stopping the run at that point may cause the system to crash.
Temporary Solution:
If the error does happen, do the following: · If GC/MS Acquisition is still running, close it · In the Windows Task Manager, Process tab, end the following processes if they are listed: msinsctl.exe CTCPalPlus.exe CTCPAL~1.exe (you end these processes by right-clicking on them, then clicking on "End Process") · Power cycle the GC 7890 · Power cycle the CTC PAL · Restart GC/MS Acquisition In some situations, if the above does not fully correct the problem, you should reboot your PC.
Fix Information:
Has been fixed in B.05.01
Keyword:
One-line Description:
QQQ: Excessively long sequence and tune filenames can be generated in certain cases
Problem:
Filenames can get long although the name does still function correctly.
Filenames entered in the following forms result in the final filename indicated:
XXXXX XXXXX.sequence.xml (correct)
XXXXX.sequence.xml XXXXX.sequence.xml (correct)
XXXXX.xml XXXXX.sequence.xml (correct)
XXXXX.sequence XXXXX.sequence.sequence.xml (wrong!)
The fourth style is unlikely to be entered by a user, unless they have file extensions hidden. And even then only if they just change the displayed "YYYY.sequence" to literally "XXXX.sequence". If they do the more normal change
Temporary Solution:
Excessively long sequence and tune filenames can be generated.
In certain cases, especially if the user has file extensions for known file types hidden in Explorer, filenames like the following can be generated during a "Save As..." --
something.sequence.sequence.sequence.xml
This *only* happens when the filename is entered in the Save As... dialog in exactly this form:
something.sequence
Workaround: don't enter a filename in the form:
something.sequence
just enter it as either:
something (in which case .sequence.xml will be appended)
or
something.sequence.xml (in which case you are all set)
Same thing for tune files.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: "Continuous GC Real-Time Plot" checkbox is not functional
Problem:
In the "Real-Time Plots for GC 7890" dialog box, there is a "Continuous GC Real-Time Plot" check box. The GC Real-Time Plots are continuous regardless whether the box is checked or not.
Temporary Solution:
n/a
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: "Set MS System Pressure Units" does not work
Problem:
In the Agilent GC/MS Instrument Configuration panel, the user can select the "Configure" menu and then the "Set MS System Pressure Units" menu item to select the pressure units for vacuum readings. Although there are multiple options for pressure units, the software is not making use of these settings. In the MS monitors, Manual Tune User Interface, and the LCP, the values are displayed in "Torr".
Temporary Solution:
Use Torr as units.
Fix Information:
Fixed in revision B.05.01
Keyword:
One-line Description:
QQQ: House LAN could cause about 2.5 min delay for GC/MS Acquisition to start up
Problem:
When the House network is used together the MS network, the GC/MS Acquisition program starts with a delay around of 2.5 min.
Temporary Solution:
If the system uses the MS network with the House network disabled or without cable or with enabled access to Internet, then GC/MS Data Acquisition starts immediately after the double click on the icon.
Fix Information:
Also refer to entry KPR 229
Keyword:
One-line Description:
QQQ: House LAN causes about 1-1.5 min delay for MassHunter quant to start up.
Problem:
Masshunter Quant: when the House network is used together the MS network the Quant program starts with a delay around of 1-1.5 min. If the House network disabled or without cable or with enabled access to Internet the Acquisition start immediately after the double click on the icon.
Temporary Solution:
Investigation of the issue at Customer site showed by checking the firewall that the PC after the double click of the icon tries to reach on Internet IP starting on the network 199.7.xxx.xxx, some IP found are 199.7.52.190, 199.7.71.190, 199.7.50.72 and 199.7.48.190, from this IP I found ftp site with some software certificate (VeriSign Global Registry Services)
Fix Information:
Has been fixed in MassHunter GCMS Acquisition B.05.02.
Keyword:
One-line Description:
QQQ: TIME stamp of a method change is not printed when you print the acq method..
Problem:
The current contents of print-out of "Print the acq method" provide the detail information about method settings in GC and MS, but not include the information about the method-change history. The file of method.txt for method-change history should be as one option for printing the acr method
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
QQQ: PAL: Sample overlap selection is not loaded with the method
Problem:
Sometimes, the "Set Up Injector Overlap" panel fails to display the current method settings. Although the panel had saved the settings correctly from a previous edit session, the panel will show incorrect settings.
Temporary Solution:
1. To read the overlap setting in a method, go to the method directory (for example, D:\massHunter\GCMS\1\methods\HS.m), open the ctc.mth file and look at the Parameters section. [Parameters] Volume=300.00 Overlap=1 Delay=60 Overlap = 1 means overlap is enabled, 0 means disabled Delay= 60 means 60 seconds, so divide this by 60 to get time the value that was entered into the "mins after full completion of the CTC PAL cycle" field in the "Set Up Injector Overlap" panel. 2. To change the overlap setting, edit the ctc.mth file following the example in the parameters section shown above. Save the file. Load the method.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: PAL: Error editing CTC PAL method
Problem:
After editing a CTC Pal method, an "unknown error" error message appears after clicking on OK. This is caused by the CTC previously not correctly handling stopping a run in Pre-Run before GC/MS/CTC are still "Not Ready".
Temporary Solution:
If the error does happen, do the following: · If GC/MS Acquisition is still running, close it · In the Windows Task Manager, Process tab, end the following processes if they are listed: msinsctl.exe CTCPalPlus.exe CTCPAL~1.exe (you end these processes by right-clicking on them, then clicking on "End Process") · Power cycle the GC 7890 · Power cycle the CTC PAL · Restart GC/MS Acquisition In some situations, if the above does not fully correct the problem, you should reboot your PC. To avoid the problem in the first place, do not stop the run while the GC/MS/CTC are still "Not ready" in PreRun. If you want to stop a run in a system with a CTC, it is best to do it after the injection has occurred and the run has started.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: MS Tune and GC Method Windows Can Be Hidden Behind Main Window
Problem:
Tune window and GC method window hidden behind the Ins Control window
Temporary Solution:
However, a better workaround is to activate MS Tune and GC Edit Method from the icons in the toolbar. In this case, the new windows will always appear on top of the main window.
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QQQ: Difficult to set up backflush parameters by using backflush method editor
Problem:
Difficult to setup up backflush method in MassHunter GC/MS Acquisition. When editing the GC method parameters, by selecting the backflush icon one can set up the backflush parameters. But sometimes after applying the settings it is not correct and may require repeating the procedure (sometimes more than twice) to be correct.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: PAL: Overlapped injections are not surpported in GC-Inj cycles
Problem:
"CTC PAL Set Up Injector Overlap" is not relevant for GC-Inj cycles. Do not check the "Enable Overlapped Injection for this Method" box.
Temporary Solution:
n/a
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: PAL: Vial outside the range of the CTC tray is not handled gracefully
Problem:
The Sequence Table Editor does not check for invalid vial entries for a CTC PAL. If the vial location is not within the range of the tray, an error will occur when running the sequence. After clicking OK on the error message box, the user will find the system to be stuck in the PreRun state. Selecting Pause and then Stop will crash the system.
Temporary Solution:
Be sure to specify the correct vial location in the Sequence Table.
Fix Information:
Has been fixed in B.05.01
Keyword:
One-line Description:
QQQ: Missing Edit Entire Method for GC/MS Acquisition
Problem:
The GC/MS Acquisition does not have edit entire method so that the user can review the steps of the acquisition parameters. The user has to go through each method edit step manually by clicking on an icon or menu item.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Enabling all barcode options or "Checksum" makes BarCode Reader work improperly
Problem:
If all barcode options or "Checksum" have been enabled, BCR won't read the barcode or will read it incorrectly.
Temporary Solution:
NEVER enable "Checksum" and enable just the one barcode style the user needs. Be aware that the default settings (off or on) of barcode styles in different firmware versions are different, so the user needs to make sure the correct ones are enabled before using the barcode reader. Especially when the firmware has been updated to a new version.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Cannot start acquisition software if method contains more than 500 MRMs
Problem:
The user could create a method which has more than 500 MRMs. When starting the MassHunter Acquisition program the software goes through an initialization check. During this initialization check information is stored in an array. However, this array is limited to 500 entries so when an method with more than 500 MRMs has been loaded as the default method to load, it will cause the EMF (Early Maintenance Feedback) ini file to abort, and lock up the instrument control. The user will see the error message from C:\GCMS\msexe\icstart1.log An array or matrix must contain between 1 and 500 elements.
Temporary Solution:
Delete the EMF.INI file in the folder X:\MassHunter\GCMS\n folder where n=instrument number. Once the file has been deleted, there will be no check to cause the array to exceed 500.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: System error when starting up GC/MS Acquisition if default.m was deleted
Problem:
If default.m was deleted from the instrument method directory and it was the LAST loaded method before closing application, then when GC/MS Acquisition starts up, there is a system error when it tries to access the missing method.
Temporary Solution:
NEVER delete default.m -- regardless whether its settings have been changed or not.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QQQ: No prompt to save modified sequence table when exit MassHunter Acquisition
Problem:
Start up MassHunter GCMS Acquisition, open Sequence Table Editor (STE), make some changes, then click, click x or Method/Exit to exit the application, there was no prompt to save the modified sequence table.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QQQ: Improper evaluation of CP variable _barmismatch
Problem:
This defect caused two problems when barcode mismatch was encountered and 'inject anyway' was selected in the Start Sequence panel: 1. 'Barcode mismatch, sample not injected' seen in sequence log, but sample IS injected 2. NO post-run processing OR ENVIRONMENT CLEANUP is scheduled Problem #1 is very evident but rather benign. Problem #2 is more severe, in that post-run activities INCLUDING creation of pre_post.ini, cleanup of temp folders, etc. are skipped.
Temporary Solution:
n/a
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: The "X" (close) buttonon the GC method editor is not functioning
Problem:
The "X" (close) button on the GC method editor is not functioning, even though it is NOT grayed out.
Temporary Solution:
Use the "Cancel" button in bottom area to close the GC method editor panel.
Fix Information:
Has been resolved in B.05.01
Keyword:
One-line Description:
QQQ: System does not print the MS parameters to correct printer
Problem:
The default printer has been assigned to be the LaserJet, 4050 or the 3005. System has XPS loaded and then it was unloaded and the effects are the same. 1. Set default printer to "Printer 1" (for example, Microsoft XPS document writer) 2. Click "Print Method.." in the Method menu. Check all options and click OK 3. Three documents are printed. Adobe Reader starts for printing MS parameters. DO NOT close Adobe Reader. 4. Change default printer to "Printer 2" (for example, Send to OneNote 2007) 5. Click "PrintMethod..." in the Method menu again. Check all options and click OK. 6. Two documents are printed to "Printer 2". 7. However MS Parameters are printed to still "Printer 1", because Adobe Reader doesn't pick up default printer changed while it is running.
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.04.01
Keyword:
One-line Description:
QQQ: Venting the GCMS QQQ could cause the Workstation to lock up
Problem:
When following the instructions of the vent procedure, users have locked up the workstation. Users are not informed that they must shut down the workstation down prior to turning off the GCMS-QQQ. Failure to shut down the workstation will cause the workstation to lock up when you turn off the GCMS-QQQ.
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.00
Keyword:
One-line Description:
QQQ: Autotune allows the CFT gases to be turned on and gives bad tune results
Problem:
The manual tune/autotune section of the software should automatically turn off the CFT gases so that the autotune will have the correct flows into the source to do a tune. If turning off the gases is not possible, then it should automatically load a method with the desired gases turned off so that the tune will work, this will also be useful so customers will know if they are going into tune to save their existing method in case they want to save them.
Temporary Solution:
The manual tune/autotune section of the software should automatically turn off the CFT gases so that the autotune will have the correct flows into the source to do a tune. If turning off the gases is not possible, then it should automatically load a method with the desired gases turned off so that the tune will work, this will also be useful so customers will know if they are going into tune to save their existing method in case they want to save them.
Fix Information:
The CFT warning now actually checks the CFT gas flow before going into tune. If it is over a limit that is specified in the tune config file a message box will warn the user and they will not be allowed into tune. By default the limit is 2.5.
Keyword:
One-line Description:
QQQ: Column length to three decimals, invoke the method resolution and lock-up method
Problem:
When we configured a column as length 0.171 meters (the quickswap restrictor length), it caused the software to invoke the method resolution and lock-up every time you try to load a method.
Temporary Solution:
When we configured a column as length 0.171 meters (the quickswap restrictor length), it caused the software to invoke the method resolution and lock-up every time you try to load a method. This appeared to be because the 7890 only stores 2 decimal places in the column length and the SW lets you set 3dp, so the method never matches the G.C. config.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: “No GC or MS data collected” while using Profile Data only for the acquisition
Problem:
Using profile data “only” for the product ion scan method (not just product ion scan, any method which uses profile data). It was discovered if profile data is being used only the system will generate an error message “No GC or MS data collected” and this will terminate the sequence. The problem is that the system was looking for a file called MSPEAK.BIN but when Profile Data is being used the file that is being created is called MSPROFILE.BIN and at the end of the acquisition the check did not pick up this file.
Temporary Solution:
Point Patch is available. Please contact your software help representative.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: Qual cannnot process RTL runs on localized versions
Problem:
IN RTL run, the log shows that Qual was scheduled, the RTLTIMES.INI file was created, but there was no information in that file - it seems that Qual cannot find the peaks.
Temporary Solution:
Using local language characters for method and datafile names will prevent automated Qual and Quant processing. Use the standard ANSI character set if you need AUTOMATED post-run processing of any kind (including RTL). This does not impact manual processing.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: GCMSQQQ masshunter allows users to select too fast scanning speed
Problem:
GCMSQQQ masshunter allows users to select too fast scanning speed without warning message leading to 0.6-0.3 AMU mass accuracy shiftment in Scan mode Currently customer have to use scancalc.xlsx to calculate proper scan speed. If you set up your scan method, SW allows you put a fix number to set for scanning speed like 100 ms. Acquisition then calculates cycles/sec values, but does not indicate anything whether it is good or not. If you look example below and set number to excel, you get one sample, when scanning speed is 108 ms. Scan times less than 108 ms means that you actually try to scan too fast.
Temporary Solution:
Example: Mass peaks were shifted 0.3-0.6 AMU range, when customer was scanning by using 100 ms scan time and 50-600 scan range ending up having 11 cycles/sec. Solution: Scan time was set to 250-300 ms to slower scan speed. The Problem was related to too fast scan time
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: PostRun can not be stopped from software, when acquisition is stopped prematurely
Problem:
When the run is stopped prematurely from MH acquisition by clicking stop icon, the post run backflush kicks in. PostRun can not be stopped from SW and the only option is to stop it from the GC keypad. There should be a way to stop PostRun from the software.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Autotune screen locks up with "Get 3 resolution Plots" being displayed
Problem:
It has been reported that occasionally the MassHunter GC/MS Acquisition will lockup during Autotune. As a result, the user will be required to restart the software to recover. It seems that it is an Autotune reporting problem that is related to the printing process, which has difficulty handling printer errors, too long printer recovery times, etc. If the printer is ready, this lock-up has not been seen.
Temporary Solution:
You can try to set up printer preferences and turn sleep mode option off. To turn the Sleep Mode on or off, please turn OFF the Sleep Mode. Press Menu to open the menus Press Down button to highlight CONFIGURE DEVICE Press Select button to select CONFIGURE DEVICE Press Down button to highlight RESETS Press Select button to select RESETS Press Down button to highlight SLEEP MODE Press Select button to select SLEEP MODE Press Up button or Down button to select ON or OFF Press Select button to set the selection Press Menu to exit the menu
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: two browse buttons in "Method Information" panel don't work
Problem:
Click the "Edit method info" icon on instrument control, the upper two browse buttons don't work, i.e., nothing happens when click them.
Temporary Solution:
n/a
Fix Information:
Fixed in MassHunter GC/MS Acquisition released version B.04.01
Keyword:
One-line Description:
QQQ: In a run, one can use special characters in the filenames including a “:” colon
Problem:
In a single run mode (clicking the green arrow icon), if you use a “:” colon, it won’t create the directory and errors out. The system states, “lost communication, manual mode, make directory failed, rebooted".
Temporary Solution:
Never use Windows/DOS special characters in filenames.
Fix Information:
Fixed in the B.04.01 release.
Keyword:
One-line Description:
QQQ: Truncated: Japanese Long file name is truncated in Printed Sequence log.
Problem:
1. Run sequence with 50 character data file name & method name (JPN characters, 2 byte char) 2. then Print Seq Log. Truncating could result depending upon the number of characters being used.
Temporary Solution:
Sequence Editor has limitation of file name.(50 Char).
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Sequence Log Reporting Wrong Error Message
Problem:
If an error occurs at the same time a barcode mismatch occurs (inject anyway was selected), then the sequence log reports "Barcode mismatch, sample not injected" instead of the actual error (e.g. sampler error).
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.00
Keyword:
One-line Description:
QQQ: Error Fault not detecting status of hardware before starting Autotune
Problem:
The system does not check the hardware status prior to opening the calibration valve for Autotune.
Temporary Solution:
Loading the default method, observe that the small square status box in the GC and MS icons are green color. You can add GC or MS Monitors to check the individual relevant GC and MS parameters.
Fix Information:
Fixed in MassHunter GC/MS Acquisition B.05.00
Keyword:
One-line Description:
QQQ: Wrong information in Logbook when overide InjVol in sequence table editor (STE)
Problem:
The GC has front and rear towers, but the method is set to Front Injection only. When running a sequence with this method and overiding the InjVol in STE, the following appears in the logbook: "Rear Injection Volume changed from 1.0 to xxx", which is not right since my method and sequence don't have back injection involved.
Temporary Solution:
If running the method, and overide vol in the Run Method panel, one gets the correct info.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: The Run Method panel needs to have "OFF" functionality to ignore BarCode Reader
Problem:
If using ALS 7693A, the barcode reader cannot be disabled from GC panel or GC configuration. Run Method needs to have an "OFF" functionality to ignore the BarCode Reader. User needs a simple way to bypass the barcode reader while doing the Run Method.
Temporary Solution:
To bypass the barcode reader: 1) If running a method, type in "off" in the expected barcode field (for both injectors, if applicable) on the Run Method panel 2) If running a sequence, edit the sequence table layout and add the "Expected Barcode" column, and type in "off" in that field for EACH line. In this way, the barcode reader can be bypassed in both method runs and sequence runs.
Fix Information:
Disable Barcode For This Sequence is in the Run Sequence Panel under the Sequence Barcode Options. Fixed in release version MassHunter GC/MS Acquisition B.05.00
Keyword:
One-line Description:
QQQ: Vial left in agitator should be return before next vial arrives on CTC seq-run
Problem:
On Sequence-running with CTC, if Clicking Stop button at PreRun (during agitating), The sequence will go to the next sample. However, the vial affected by clicking "Stop" was left in agitator and is NOT moved back to the original position on the tray before the new vial is transporting to the agitator; in addition, no warning message regarding this circumstance appears, so the error with z-collision will occur, when the next vial is transported to the agitator.
Temporary Solution:
User will need to verify that the vials are placed back in the original positions.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Dual injection sequence uses run method injection selection if they are in conflict
Problem:
When the method specified in the sequence was set to front (even though dual injectors are available), the sequence only ran the vials in the front injector although dual injection on Sequence Table Editor was checked.
Temporary Solution:
Selecting "Dual" ratio box on section of Inlet Location in the method AND selecting "Dual Inj." check box on Sequence Table Editor, also entering the values into column "Dual Inj. Vial" and "Dual Inj. Vol." properly, the sequence will run and collect data correctly.
Fix Information:
Fixed in MassHunter GC/MS Acquistion released version B.05.00
Keyword:
One-line Description:
QQQ: Sequence hangs when method set to dual but dual injection on STE not checked
Problem:
The method specified in the sequence table was set to dual injection but the dual injection column on Sample Table Editor is not checked. Ran the sequence. It started but stayed there in PreRun. Needed to shut down the software to start over.
Temporary Solution:
Select "Dual" radio box on section of Inlet Location in the method AND select "Dual Inj." check box on Sequence Table Editor. Also enter the values into column "Dual Inj. Vial" and "Dual Inj. Vol." properly, and the sequence will run and collect data correctly
Fix Information:
Fixed in MassHunter GC/MS Acquisition B.05.00
Keyword:
One-line Description:
QQQ: Resuming a paused sequence with Overlap On injects the wrong vial
Problem:
Running a sequence with sample overlap, pause the sequence in the moment that the current sample is running in the GC and the next sample has been prepared. Resuming the sequence will results in picking wrong sample.
Temporary Solution:
If the overlap feature is being used, do not click "Pause" when the processing for the next sample has already started.
Fix Information:
Fixed in released version B.05.00
Keyword:
One-line Description:
QQQ: Sequence with sample overlap and dual injection doesn't work properly
Problem:
Sample overlap does not work with a dual injection sequence. No overlap is observed. It waits until completion of the run to pick up the next sample.
Temporary Solution:
Do NOT use the feature of sample overlap with dual injection in a sequence run on this release. It is NOT supported in this release.
Fix Information:
Fixed in released version B.05.00
Keyword:
One-line Description:
QQQ: Intermittently the 7890's selected injector is not present
Problem:
Here are the steps to cause the problem: - Vials are transferred to the turret of the ALS (7683B) - All the vial washes will take place - The sample is transferred to the syringe and the plunger is up - Now there is an extra movement from the turret, sounds like the re-alignment AND At the same time there is the error in the log file: 2009/06/24 13:54:33 7890 The selected injector is not present. 2009/06/24 13:54:36 7890 Lost connection to Agilent 7890A at 192.168.254.11 2009/06/24 13:54:36 ManualMode Run Method Error - Consult Logbook 2009/06/24 13:54:36 ManualMode The selected injector is not present. 2009/06/24 13:54:37 7890 Connected to Agilent 7890A at 192.168.254.11 2009/06/24 13:54:37 7890 Runs cannot be started until the GC and injector are idle. - but the ALS is doing the injection anyway and the 7890A starts System configuration: - 7890 with firmware A.01.10, - 7683B A.11.03 - PTV septum less head
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Sequence with sample overlap AND with different methods results in picking wrong sample
Problem:
When running a Sequence with sample overlap AND with different methods for the samples, the wrong sample is picked.
Temporary Solution:
Current software does NOT support different methods with different overlap settings (even if the methods have the same settings but with different names) in a single sequence run. By design, the overlap settings are saved to the method. Other methods executed in a sequence that have different or no overlap settings will override these settings and transition samples will not have either overlap settings applied; and it may also result in picking up the wrong sample. If the overlap feature is enabled in sequence-run do NOT assign different methods for samples.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: GC/MS Acquisition does not allow GC configuration to be uploaded from the 7890
Problem:
The defect is that if the user makes Config changes on the GC front panel and then from the software selected Edit GC Configuration, before you can even select the Get GC Config button, the software downloads the method to the GC. So the user can never make Configuration changes at the gc level and upload them to the GC. It overwrites the changes. For example, I was testing the MMI Inlet Cryo Config Modes, and from the GC, I changed the cryo gas to compressed air. Restarting the software, method res appeared and one needs to select edit GC Config and save the method. The method was now showing the parameters for N2 instead of compressed air. When I looked at the GC, it has converted back to N2.
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.05.01
Keyword:
One-line Description:
QQQ: Dual injection does not catch dual vial out of range
Problem:
Set up a dual injection sequence on a 7683 with a tray. An invalid vial number for the dual vial will not be caught and the user will receive no message about this error. Run the sequence and it will hang in PreRun on the line with the invalid vial. No indication is made in the logbook. You will have to shut down the software.
Temporary Solution:
User should enter the correct vial number to match the suitable range of the installed tray or turrets.
Fix Information:
Fixed in released version MassHunter GC/MS Acquisition B.05.00
Keyword:
One-line Description:
QQQ: Range of Electron Energy in Edit MS parameter
Problem:
The current available Electron Energy Value is between -70eV and -300eV. GC QqQ customer wants to change Electron Energy to more lower Voltage by themself. How can I do change available input value of Electron Energy to more wider range ?
Temporary Solution:
n/a
Fix Information:
The dynamic range will be increased with the release of the MassHunter GC/MS Acquisition software B.05.00 release. The increased range will require the installation of the new Filament Drive Circuitry Board on 7000A Series Models, this board will be shipping on the 7000B Series Models.
Keyword:
One-line Description:
QQQ: "Run Method" panel is not updated to a new GC configuration
Problem:
After GC/MS Acquisition shuts down, change the GC configuration from front injector to rear injector. Start the software, it will then recognize a configuration change and bring up the GC configuration panel. Select Get GC Configuration and OK panel and save the method. When you select the Run Method icon, the Run Method panel still shows a front injector.
Temporary Solution:
Before opening Run Method panel, do these steps first: Edit GC Parameters, OK and save the method again; then open Run Method panel and it will reflect the correct configuration.
Fix Information:
Has been resolved in B.05.01
Keyword:
One-line Description:
QQQ: Information in B.04.01 Online Help about "Relock method" is wrong
Problem:
The information provided in the Help file incorrectly describes the process (pick a method file) for Relock method
Temporary Solution:
Ignore this part of help. Correct info is: RELOCK is to be used when column or other GC maintenance has been performed such that your locked method no longer results in the correct retention time for the locked compound, and the lock pressure needs to be recalculated. RELOCK is to ‘update’ a LOCKED method, not unlocked method. So to do "Relock method", the user needs to load the originally locked method, then select "Method>Relock Method" from the Instrument Control panel and follow the further instructions on the screen.
Fix Information:
Fixed in release version B.04.01
Keyword:
One-line Description:
QQQ: Lack of messages after ALS configuration changes
Problem:
ALS configuration changes don't trigger any warning messages
Temporary Solution:
ALS configuration changes don't trigger any warning messages
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: "Unhandled exception" error appears during sequence run
Problem:
Unhandled exception error happens very rarely DURING a sequence run. The error message says, "Object reference not set to an instance of an object". But it doesn't affect the sequence at all.
Temporary Solution:
Wait for reoccurrence and get more information for potential fix.
Fix Information:
Fixed in released version B.05.00
Keyword:
One-line Description:
QQQ: Can't complete RTL with localized method name
Problem:
Create a method with a localized name (e.g. in Chinese or Japanese) Execute "acquire RTL calibration Data" 5 Data files will be acquired correctly, then an error message will appear. "Incomplete RTL calibration information! Check RTL cal data for errors!" It does not happen with English file name.
Temporary Solution:
Using local language characters for method and datafile names will prevent automated Qual and Quant processing. Use the standard ANSI character set if you need AUTOMATED post-run processing of any kind (including RTL). This does not impact manual processing.
Fix Information:
MHBridge.mac (goes under the \msexe directory)
Keyword:
One-line Description:
QQQ: CTC-PAL: A Sequence with overlapped SPME injections will lock up the system
Problem:
Set up a sequence using the CTC-PAL with a SPME syringe. Enable sample overlap. The sequence will appear to hang with the vial in the agitator on line 8. No meaningful information is available.
Temporary Solution:
In order to get correct initial conditions for CTC-PAL sequence run, we strongly recommend this:
A. If LiveUpdate (Symantec) is installed in the computer, the feature of “automatic liveupdate” should be disabled;
B. In Control panel, Power Options, select “Higher Performance” AND “put the computer to sleep” to “Never”;
C. When doing new CTC connection, open CTC menu on Instrument top:
- do “Reset Injector”;
- do “Update configuration” one or more times until this message appears on CTC Status panel:
“Loading configuration …
Connected
READY”
If after doing this a few times the system still cannot set to “Ready”, close the GC/MS Acquisition application (check in Task Manager that msinstctl.exe and ctcplus.exe should be gone, otherwise, kill those processes manually), open the application again and repeat Step C.
Fix Information:
Fixed in MassHunter GC/MS Acquisition released version B.05.00
Keyword:
One-line Description:
QQQ: "Off" button on CI Reagent Gas Control panel should show "count down timing"
Problem:
On CI Reagent Gas Control panel, when the Off button is clicked, the gas status bar displays "Pumping out" in yellow background and stays for a while (actually, 4 minutes), but no "count down timing" shown such as that with clicking the Pumpout button. This may confuse the user about the CI gas status. Note: the information about "count down timing" (starting from 240 seconds to zero when clicking the Off button) can be obtained from a backdoor command, but this is not a regular use.
Temporary Solution:
n/a
Fix Information:
Fixed in release version B.05.01
Keyword:
One-line Description:
QQQ: "Profile" mass settings are missing after autotune done & file saved
Problem:
The default settings of masses for PCI (methane) profile mode are 41, 267 and 599 (see file default_pci.tune). However, one or two mass numbers are missing and not stored in the new tune file after autotune was done. For example, for MS1 Profile, masses 41, 267 and 599 may exist, but for MS2 Profile, only 41 is contained.
Temporary Solution:
n/a
Fix Information:
Fixed in release version B.05.01
Keyword:
One-line Description:
QQQ: Conflict Vent Status between Vent Panel and Tune Status bar
Problem:
On Vacuum Control of Manual Tune, clicking Vent button to start vent process, when all criteria for vent (temp, vac and turbo speed) are not matched yet, the Vent Status box on Vent panel shows "Venting" in yellow, but Tune Status bar shows "Vented" in red.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: PAL: Missing CTC-PAL configuration from Menu Configuration upon re-installation of MassHunter
Problem:
Was working on an earlier build of MassHunter GCMS Acquisition and then uninstalled the Acquisition software and reinstalled but now cannot configure the PAL unit.
Temporary Solution:
The PAL drivers are flagged in a file called CTC.INI under the \mssetup. When the user uninstalls the software, this directory is removed and then is re-created. This is the reason why PAL drivers did not show up.
Fix Information:
When uninstalling the MassHunter GCMS Acquisition software package, all related add-on packages should also be removed and then reinstalled for completeness. Was resolved in B.05.01
Keyword:
One-line Description:
QQQ: NCI mode: error in switching gas type without clicking "Set" button
Problem:
The error occurs in these circumstances: 1. Start MassHunter GC/MS Acquisition, load default_CI.m associate with ci_atune.tune.xml. The default mode is NCI, default Gas is A (methane); 2. Change CI Gas A to B (Ammonia) on Ion Source panel WITHOUT click “Set “ button; change Methane to Ammonia on Autotune panel; 3. Click Autotune to bring up the "wait" panel. Filament turns on when the Emission current is increasing from zero to 50 uA. Cal Valve is also on, but CI Gas Flow drifts between 99-100. 4. Filament is on for 5-6 minutes; when CI Gas Flow drops down to 1 or zero, the filament turns off, Cal Valve shuts off too, and CI Gas Flow back to 99 or 100, no tune starts, and this status stays forever until clicking “Cancel autotune”.
Temporary Solution:
This error can be avoided if click "Set" button first prior to clicking "Autotune" button.
Fix Information:
Fixed in release version B.05.00
Keyword:
One-line Description:
QQQ: Enable Sample Prep menu item shows wrong .pt method
Problem:
Associated different sample prep methods with methods. Some methods had no sample prep method. The checkmark seems to work appropriately however, the sample prep method is often incorrect. Sometimes Enable checked, but no method specified (before running the method). Other times the wrong sample prep method specified. It didn't seem to change the menu item after loading a method with a different sample prep method.
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.00
Keyword:
One-line Description:
QQQ: PAL: Tray name with lower letter is accepted on Seq table, but can't execute Seq Run.
Problem:
Install CTC-PAL Software, select CTC-PAL as Injector, Tray 1 = 32, 20 ml
1. Verify the run method with CTC-PAL complete
2. Try Run sequence with the method.
3. Set Tray name with lower letter "t1-3220", not "T1-3220"
4. Run seq. but an error occur immediately.
"Invalid argument"
because tray name is specified as lower letter "t1".
If Try name with lower letter is not allowed, a warning should be appeared when exit Seq table.
OR
Tray name should be converted to capital letter automatically.
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.00
Keyword:
One-line Description:
QQQ: Overlap injection option is not saved
Problem:
1. Open "Setup Injector Overlap" panel 2. Change the Start option from 2nd one to 1st one like above. ( x min after full...-> After full...) 3. Open "Setup injector overlap" panel again. 4. Start option is changed to "Start n minutes after..."
Temporary Solution:
n/a
Fix Information:
Fixed in release version B.05.00
Keyword:
One-line Description:
QQQ: Adding/Removing 7693 tray does not show up in method resolution
Problem:
I had a system with a 7693 ALS but no tray. The Sample Prep menu items were not displayed. Created a method. Shut down software and added a tray to the instrument. Started up software. There was no method resolution, and no sample prep menu items displayed. Went into GC Configuration to upload the GC configuration. Upload was successful and method was saved. Still no Sample Prep menu items. Shut down the software once more and started back up to get the menu items.
Temporary Solution:
Same scenario with removing a tray. It is not until the shutdown/startup after uploading the GC configuration that the Sample Prep menu items will be removed.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ: Unknown error occured with CTC SPME method after restarting GCMS Acquisition
Problem:
On a system configured with CTC and using a SPME method, an "Unknown error" occurred after restarting GCMS Acquisition
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: PAL: Unexpected Program termination occurs when restart MH after interrupt seq.
Problem:
CTC A.01.05 1. Start CTC HSS sequence 2. "Stop" sequence by "Stop" button(Red button) on SW. 3. Sequence is interrupted correctly. 4. Close MH Acq. 5. Start MH Acq again. 6. "Unexpected Program termination" always occurs.
Temporary Solution:
Do not press "Stop" during Prerun.
Fix Information:
Establishing the correct initial conditions is a sensitive issue to run CTC properly; it may eliminate several unexpected errors. We strong recommend checking and doing the following processes prior to running any CTC method or sequence: A. If LiveUpdate (Symantec) is installed in the computer, the feature of “automatic liveupdate” should be disabled; B. In Control panel, Power Options, select “Higher Performance” AND “put the computer to sleep” to “Never”; C. When doing new CTC connection, open CTC menu on Instrument top: • do “Reset Injector”; • do “Update configuration” once or more times until the following message appear on CTC Status panel: “Loading configuration … Connected READY” If doing this for a few times and the system still cannot set to “Ready”, close the MH GCMS data acquisition application (check Task Manager, msinstctl.exe and ctcplus.exe should be disappeared, otherwise, end these two processes manually), power cycle CTC, then open the application again and repeat Step C. Was resolved in B.07.00
Keyword:
One-line Description:
QQQ: Progress bar in Advanced Autotune doesn't work properly
Problem:
On Advanced Autotune, clicking any parameter button will trigger an autotune for the select parameter, and the Progress Bar on bottom should show the tune progress in green. But for some parameters, this bar doesn't show anything.
Temporary Solution:
n/a
Fix Information:
Fixed in release version B.05.01
Keyword:
One-line Description:
QQQ: PAL: CTC-PAL injection volume get reset to OLD value if method is not saved immeditately after editing
Problem:
Injection Volume modification in the method the value is not saved if immediately after the modification the method is not saved, when the “CTC PAL Edit Method” is reopened they show the old value and not the new one.
Temporary Solution:
n/a
Fix Information:
Fixed in release version B.05.01
Keyword:
One-line Description:
QQQ: MS Params has a GAIN entry limit of 100
Problem:
The user can enter a value upto 100 for the GAIN, while the tune report could show a higher value is possible.
Temporary Solution:
The tune report shows the maximum calculated GAIN value which could be possible based on the current tune parameters. If a user would like to enter a value greater than the maximum 100 GAIN value, then the user should use the delta EMV. Entering in the delta EMV value will show the corresponding/equivalent GAIN value. Note: Using higher GAIN values will/could cause the lifetime of the EMV to be shorter.
Fix Information:
Fixed in release version B.05.00
Keyword:
One-line Description:
QQQ: User does not know what type of tune report is being printed, Autotune or Generate
Problem:
When the user looks at the tune report, there is no real way of knowing if the tune report was from autotune or from generate report. Both reports are the same.
Temporary Solution:
n/a
Fix Information:
Fixed in release version B.05.01
Keyword:
One-line Description:
QQQ: Iris limit shows a false change from -100 to 100 to -70 to 70
Problem:
Manual Input on IRIS (mz 1050) some how ended up yielding an ERROR when inputting a value that fell outside the limit of -70 to 70 while the actual limit was -100 to 100. This error did not occur when making a change outside the error redefined limit, but once the error occured it always occurred, i.e., outside the bounds of -70 to 70 but inside the bounds of -100 to 100.
Temporary Solution:
n/a
Fix Information:
Fixed in release version B.05.00
Keyword:
One-line Description:
QQQ: Sample error 142 occurs during acquisition with 7693 back tower & tray
Problem:
1. Configure a 7890-only instrument. The 7890 has 7693 (dual tower and tray) 2. Create a method with back Injection (without sample prep) 3. Run Method 4. Can't start acquisition -- error message is "Sample error 142."
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Sample prep command to Back tower does not work
Problem:
1. Configure a 7890-only instrument with 7693 (Dual tower & tray) 2. Create a method. 3. Associate sample prep method (wash back tower command). 4. Save method. 5. Run method. 6. An error occurs, "Fail in command to back tower" the screen capture of mslogbk.htm and Slog are attached. also, I attached my method.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Copy button on 7890 GC Status window is not working
Problem:
Selecting the Copy button the GC Status window, it says "Not there yet..."
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Unexpected Program Termination While Running Seq with GC QQQ
Problem:
While running a sequence with a method which collects the ms signal as well as the GC's FID signal. The GC-QQQ was configured to the back inlet. Was unable to tune because of an error stating, Error in Autotune! Check Abundance failed." At the end of the sequence, an unexpected program termination error and intrument control closed. There was also an error message which was presented on the status line.
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Configure MS Source Dialog box pops up and then disapperars
Problem:
Configure MS Source Dialog box pops up and then disapperars, it works but distracting
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QQQ: Select "No" on saving changes to method will bring Method Resolution twice
Problem:
1. Launch the application; 2. Method Resolution appears if the loaded method has different configuration with instrument; 3. Click OK to close Method Resolution, and brings up the message box "Method has changed during ChemStation initialization. Save Changes?"; 4. Clicking "Yes" will prompt to input method name to save; 4. Clicking "No" will bring Method Resolution again.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: No method save after Get GC configuration
Problem:
Started up software using a 7890 with a front injector and tray (7693). Created and ran method. Shut down the software. Added a back injector and started software again. It now brought up method resolution (did not before) and states to Get GC configuration. After OKing that panel however, it did not bring up the method save.
Temporary Solution:
Aftering making any types of edits to a method, the user needs to make sure that the method has been saved.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Valve method associated with a sample prep method
Problem:
Edited a method that had a sample prep method associated with it. Changed the injection source from ALS to valve and saved the method to a new name. Enable Sample Prep menu item appropriately became grayed. Ran the valve method. Method completed. The Enable Sample Prep menu item became ungrayed and it showed a .pt association. Method print also showed the sample prep method association.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
QQQ: The software configuration should notify user on software/firmware mismatches.
Problem:
When starting instrument control, the software does not inform the user of mismatch firmware between the software package and the GCMS-QQQ. This could cause strange error messages to appear because the GCMS-QQQ may not understand the hardware command set which it is being asked to do.
Temporary Solution:
Update the firmware on the GCMS-QQQ with the supported version the MassHunter GC/MS Data Acquisition is expecting, this can be done via the MS Configuration of the instrument.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: MS Config, forgot to configure the sources, and it did not show up in the summary page
Problem:
Did the configuration of instrument #1, did not configure the source, when selecting save results, it did not show EI source as an available sources in the summary page.
Temporary Solution:
The system will automatically use the EI source type by default when loading the instrument control.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: PAL: Setup CTC-PAL Sample Overlap panel does not allow certain selections
Problem:
With the HS injector installed on the CTC-PAL was unable to select the second sample overlap selection (xxx min after completion of the cycle). With the SPME injector installed was unable to select the first sample overlap selection (after completion of the cycle). In both cases, select the option and OK the panel. When returning to the selection, it was changed.
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Dual injection with barcodes and overlap not working correctly
Problem:
The method specified in the sequence is set to dual injection with overlap on. Set up a sequence and entered dual injection vials and barcodes. On the run sequence panel, set to don't inject on a barcode mismatch. Although all my barcodes were correct in the sequence table, every other line failes on a barcode mismatch because it compared the actual barcode on the rear to the expected on the front.
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Setting CI reagent flow turns off CI cal valve
Problem:
When the CI reagent flow is 0 setting the flow will turn off the CI cal valve. This is a problem after autotune or any other time the instrument is turned off. Then when the user tries to manually tune, if they turn the cal valve on first, it will be turned off when the CI reagent gas flow is set.
Temporary Solution:
Turn the CI cal valve back on after setting the reagent gas flow.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Message about different source appears twice after selecting source from panel
Problem:
1. configure instrument, select all available sources (the currently installed source is CI); 2. Start the application, comes up the panel "Ion Source Selection"; 3. Select NCI source; 4. The message box appears, such as "D:\MassHunter\GCMS\1\METHODS\DEFAULT.M specifies a different ion source from the one currently installed in the MS" 5. Click "OK" on the message box;the message disappears; 6. The same message box appears again; 7. Click "OK", the message disappears.
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Log file is displayed with garbage Asian characters
Problem:
When Multivu was used to display a log file, the Japanese characters in the file were displayed as garbage.
Temporary Solution:
Manually use Microsoft Notepad.exe to view log files such as c:\gcms\msexe\icstart1.log
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Wrong sample prep program can get executed when overlap is on
Problem:
Sample overlap checked and sample prep program is also enabled for the method. The sequence using the same methods with sample overlap and same sample preps are able to complete without an issue. However, to override the sample prep method and enter different sample prep methods; this cause issues. The sample prep method run is from the previous sequence line. For example: line 1 prep1.pt line 2 prep2.pt line 3 prep1.pt line 4 prep2.pt When a sequence is running, prep1.pt is executed before lines 1,2 and 4. Prep2.pt is executed before line 3.
Temporary Solution:
The sequence needs to be closed and re-executed; continue with the sequence could cause problems with the sample prep method association.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: msinsctl.exe process is not cleaned up after tune and application was closed
Problem:
1.Launch Acq application; 2. Perform several operations that are only related to tune (such as autotune, manual tune or vacuum control); 3. Exit tune panel and close the application; 4. Frequently (80% probability), the msinsctl.exe process is not cleaned up after tune and application was closed. So user needs to kill this process first to start the application next time.
Temporary Solution:
Running a method or sequence after tune, this will not occur.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Q1 DC and Repeller power "walking" when executing multiple autotune in a row
Problem:
The following behaviors have been observed for NCI mode and EI with Extractor (no tests for PCI and EI mode were conducted yet): When executing multiple autotune in a row (the second autotune starts based on the first autotune, the third autotune starts based on the second autotune, and so on), Q1 DC and Repeller power will "walk" and increase in one direction (absolute values), although the delta between Q1 DC and repeller is relatively stable. (Please see the attached file for an example)
Temporary Solution:
Autotune for Default Setting does not have this kind of behaviors.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Read Barcode doesn't work for the DualInjExpectedBarcode column
Problem:
In the sequence table editor, read barcode button should work the same way for ExpectedBarcode column and DualInjExpectedBarcode field. Currently, no read barcode function is connected to the DualInjExpectedBarcode field.
Temporary Solution:
n/a
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Incorrect display and processes in pumpdown and Select Ion Source
Problem:
1. After vent, turn MS, click “Pumpdown” button to bring up the panels "Pumpdown Manual Steps" -"Make sure Vent Valve is closed"; 2. Close Vent valve then click OK to close “Pumpdown Manual Steps”; 3. After a few seconds, the message box” Instrument Faults” appears, it indicates that “QqQ fault detected: 123 Vacuum system is not ready. ….”. It is normal; 4. The error is: the message box” Instrument Faults” cannot be moved and closed until user close the “Ion Source Selection” button that is displayed on the bottom bar and is difficult to be seen. --> This does not occur when you have just a single Ion Source configured.
Temporary Solution:
On the task bar, the user can select the task bar icon for the application and then move to move the image over to see the screen behind it.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Method name cut off in the sequence.log and printed "current sequence"
Problem:
A method name was "m2.nci.m" in the sequence table. In the sequence log, the method name was cut to "m2". If I click the Printer button, and select "print current sequence", same thing happens in the printed sequence.
Temporary Solution:
This is due to the new method naming, user should use an UNDERSCORE.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Selecting "Do not show this warning again" on CFT message box closes the box
Problem:
After clicking tune icon, the CFT remind message box appears "If installed, turn off CFT backflush before Tuning"; If user selects check box "Do not show this warning again" on bottom of this box, this box will disappear FOREVER unless uninstall and install the application again.
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.05.01
Keyword:
One-line Description:
QQQ: Editing the Sequence Table with Sample Overlap ON could cause mixed results
Problem:
The sequence log file does not reflect the actual sample vials which were
used during the sequence.
Starting sequence Wed Oct 14 17:57:48 2009
Instrument Name: QQQWAD002
Sequence File: D:\MassHunter\GCMS\1\sequence\overlap.sequence.xml
Comment:
Operator: QQQWAD02\Admin
Data Path: D:\MassHunter\GCMS\1\DATA\overlap\
Method Path: D:\MassHunter\GCMS\1\METHODS\
Line Type Vial DataFile Method Sample Name
-----------------------------------------------------------------------
1) Sample 1 Sample 1
Datafile vial 1
Method vialoverlap
2) Sample 7 vial 7
Datafile vial 7
Method vialoverlap
3) Sample 2 Sample 1
Datafile vial 2
Method vialoverlap
Sequence Table edit performed Wed Oct 14 18:11:56 2009
4) Sample 8 vial 8
Datafile vial 8
Method vialoverlap
5) Sample 9 vial 9
Datafile vial 9
Method vialoverlap
6) Sample 3 Sample 1
Datafile vial 3
Method vialoverlap
7) Sample 4 Sample 1
Datafile vial 4
Method vialoverlap
8) Sample 5 Sample 1
Datafile vial 5
Method vialoverlap
9) Sample 6 Sample 1
Datafile vial 6
Method vialoverlap
Sequence completed Wed Oct 14 18:35:27 2009
D:\MassHunter\GCMS\1\DATA\overlap\2009 Oct 14 1757 Sequence Log .LOG
However, the actual vial numbers which were used were
Vials 1, 2, 2, 3, 9, 3, 4, 5, 6 not the
Vials 1, 7, 2, 8, 9, 3, 4, 5, 6 as reported in the sequence log
Temporary Solution:
The issue to the mismatch of the sequence log file and the initial sequence
table is related to the Enable Sample Overlap was turned ON.
When the sequence run was started the initial sequence table had samples in
vials 1, 2, 3, 4, 5, 6. When the run was started a sample was added to the
table just after sample 1 (vial 1). But since the Sample Overlap was Turned
ON, the system has already preread the information from line 2 (Sample 2, vial
2). As a result, the system picked up the sample in vial 2 not sample in
vial 7.
To validate this process, when the system was picking up sample in vial 2
the sequence table was editted again. This time two new samples were added
to the table sample 8 (vial 8) and sample 9 (vial 9). Again because of the
Sample Overlap was turned ON, sample in vial 8 was ignored and the sample in
vial 3 was used, then the sample in vial 9 was processed and then the sample
in vial 3 was picked up. The rest of the samples were picked up as noted.
Presently, there are two workarounds for this while running a sequence which
has methods with Sample Overlap
1 -- DO NOT EDIT the Sequence Table while the sequence is running
2 -- If you need to edit the sequence while it is running, DO NOT ADD/INSERT
any lines just below the acquiring method. Insert two lines below the
acquiring method.
The sequence log table prints out a summary result of the sequence table which
was editted. For the case in which the system states that it injected from
sample in vial 7 in the sequence report, if the user looks at the datafile
look in the individual sample_info.xml file for the vial that was actually
injected -- under name for Sample Position, the value is the vial number:
Sample Position
Sample Position
21
The key bit of information one needs to remember about Sample Overlap is
as soon as one injection is made, the ALS begins its solvent wash and sample
pump cycle to prepare the next sample which means information from next sample
has already been taken into account so inserting a new sample at this point
will cause the previous line which was in the sample table to be performed and
not the newly inserted line if a sequence table has been editted.
Additional Information:
OnLine Help Files in the GC/MS Data Acquistion about Sample Overlap
Sample overlap can increase throughput by allowing the ALS to begin processing
the next sample before the current run finishes. ALS sample preparation does
not have to be finished before the current runs ends.
To use Sample Overlap, select Enable Sample Overlap, then select the preferred
timing for the overlap and enter a time (in minutes) as needed. The three
modes are:
After the previous injection is completed — As soon as one injection is made,
the ALS begins its solvent wash and sample pump cycle to prepare the next
sample. If the run time and oven cool down cycle is longer than the ALS sample
preparation time, the sample waits in the needle above the inlet until the GC
becomes ready for the next run. You can use this setting if the sample is not
likely to degrade in the syringe or evaporate from the needle.
Prepare sample __ min. before end of GC run — ALS sample preparation begins
at the specified number of minutes before the run ends. Depending on the total
run cycle time, this setting should reduce the time the sample spends in the
syringe waiting for the next run to start. If the time remaining in the
current run is less than the specified time for this setting, sample
preparation will begin immediately following the end of the active run.
Prepare sample __ min. after end of GC run — The sampler waits the specified
amount of time after the current GC run ends to begin ALS sample preparation.
When using oven temperature programming, the ALS will start to prepare the
next sample during the oven cool down cycle between runs. This setting should
reduce the time the sample spends in the syringe waiting for the next run to
start.
When selecting a mode, determine / consider the following:
The actual ALS sample preparation time for the method (time it using a watch).
The total run cycle time: the run time plus any cool-down time after the runs
ends.
The After the previous injection is completed and Prepare sample __ min.
before end of GC run settings increase sample throughput by preparing the
sampler to perform operations related to the next sample before the GC
completes the current sample run.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Acquiring Data, zooming in on chromatogram data jumps to undefined box field
Problem:
Occurs in B.04.01 and has been validated on B.05.00 During the acquisition the user can see the TIC being displayed. The user then wants to zoom in on a group and does a right click and drag over the region to be zoomed in. The zoomed in box is not the regions which was defined.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: When vent cycle program is over, Ion Source and Quad Temp are turned ON
Problem:
When vent cycle program is over, the current method with tune file is loaded again. As a result the heaters will be turned ON!
Temporary Solution:
Before run vent cycle in manual tune, the user should load special tune file with Ion source and Quad temp are OFF.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: The 'Sample Prep File Name' in the sequence table is only an override.
Problem:
The 'Sample Prep File Name' in the sequence table is only an override, leaving the field blank will run the method's pretreatment program by default. There is no way to disable sample prep from this column without having to create a new method.
Temporary Solution:
Make the default method have an Enabled Sample Prep Program with at least one command. For example, a single Wait command of '.1 min'. If no command is chosen, the sequence will not run. Then use the sequence queue's 'Sample Prep File Name' to override this dummy sample prep sequence with the needed Pretreatment Program.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Sample preparation does not allow sample overlap.
Problem:
There seems to be a functionality missing between sample overlap in combination with sample preparation.
Temporary Solution:
n/a
Fix Information:
The pre-treatment path and file name must agree between sample K and sample K+1 or else Overlapped experiment is inhibited.
Keyword:
One-line Description:
QQQ: Running the vent program could leave the source and quad temperatures above 100 deg.
Problem:
Vent the GCMS-QQQ If the heated zones are not cooled prior to starting the vent process, it is possible that the heated zones could be greater than 100 deg. Caution should be used when handling the parts. Presently, when the turbo pump speed drops to 50% spin speed, this will trigger a high vacuum fault in the electronics. there is a 7 minute timer which will then count down and at the end of 7 minutes, this will turn off the foreline pump.
Temporary Solution:
If you are going to be venting the instrument, cool down all of the temperature zones: the source temp, quad 1 temp, quad 2 temp and transferline. The temperature should be below 100 deg and then start the vent cycle.
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Customer has a working method in EI and would like to convert this to PCI or NCI
Problem:
You cannot load an EI method if a ci source is selected and change the tune file to the EI method. The error of the workstation is that this method is not valid due to the installed CI source.
Temporary Solution:
To preserve the GC settings when changing from EI to CI:
1) Save existing EI method to a new name (e.g. xyz.m)
2) Copy qqqacqmethod.xml from default_pci.m or default_nci.m (depending
on the ion polarity) into xyz.m
3) Reload xyz.m
4) Edit the MS parameters
5) Save xyz.m
Fix Information:
Fixed in released version B.05.01
Keyword:
One-line Description:
QQQ: Changed source type via MS Parameters but did not realize that it did not affect tune
Problem:
The implementation of the changing the tune type and then saving the method is good. But unaware that one had to go back under the Instrument section to change the source type to the new one if one wanted to proceed to the manual tune section.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: English (United Kingdom) prevents saving tune into PDF
Problem:
When the Regional and Language Options Current format are set for: English (United Kingdom) There is an error while autotuning: "An exception has occurred saving an autotune report as a PDF file" "An error occurred during local report processing." Otherwise autotune finishes OK.
Temporary Solution:
Change the Regional and Language Options Current format are set to: English (United States)
Fix Information:
Only supported local languages are US English, Japanese and Simplified Chinese. Any other language choices may cause erratic behavior. This also includes regional and language options.
Keyword:
One-line Description:
QQQ: When 16 Vial Turret is on the Back Injector and 3 Vial Turret is on the Front, vial ranges are incorrect.
Problem:
The configuration is 7693 ALS Tray unplugged with a 16-vial turret on the back injector and a 3-vial turret on the front. If one tries try to run the back injector with a vial number over 3, it will not run. It will sit in Prerun and to terminate the program one will need to shutdown through task manager. If you unplug the front injector, then it will use the appropriate vial range 1 - 16.
Temporary Solution:
When the 16 vial turret is on the front and the 3-vial turret on the back, it works correctly.
Fix Information:
Was resolved in B.05.01
Keyword:
One-line Description:
QQQ: Extended characters not being recognized and passed properly by the command shell.
Problem:
The command shell will stay open as long as one has Qualification open. Once Qualification program is closed, the command shell goes away. That’s the way the EXEC and DOSRUN functions work when a .bat file is used; the command shell will stay active until the processes it has started are all terminated. The use of the .bat file is to provide proper synchronization. The display one will see in the command shell is normal, because of what the ‘OPEN’ command does. Also, Qual indicating it ‘can’t find the method’ is normal, and doesn’t impact anything.
Temporary Solution:
n/a
Fix Information:
Has been fixed in MassHunter GCMS Acquisition B.05.02.
Keyword:
One-line Description:
QQQ: Relock Menu Should be Dimmed when unlocked method is loaded.
Problem:
If you have a locked method and you unlock the method (and even if you reload it after locking it), the relock menu item is available, but you cannot relock a method that is not locked.
Temporary Solution:
Need to validate the status of the method.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ: Cannot view the video on bundled PC Z400 (Win 7 or Vista)
Problem:
When the image recovery is used on the Z400 PC, the user may not be able to view all of the videos on the workstation. Some of the videos require the use of Media Flash to be installed on the PC.
Temporary Solution:
User will need to download Adobe Flash player from the internet to view the videos. Image recoveries for the PCs do not include Adobe Flash Player, the Adobe Flash Player is added onto the image after the media recovery process.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: There is no warning or message about MRM segments being resorted
Problem:
The segments are sorted by Precursor and then Parent Ion, which is from High to low for the parent ion, and if the parent ions are the same and only looking at the collision cell then they are sorted from high to low for the collision cell energy.
Temporary Solution:
Sorting by Precursor and Product ions are required by instrument control. The sorting by Collision Energy is required by AutoMRM application thus the reason why it is sorted.
Fix Information:
Has been fixed in MassHunter GCMS Acquisition B.05.02.
Keyword:
One-line Description:
Some libraries will not install on a system with only MassHunter installed and not ChemStation
Problem:
MassHunter supports libraries in the .L format however many of the shipping libraries look to see if ChemStation software is installed and if it is not will refuse to install the library. The following is a list of libraries that will install properly on a MassHunter only system as of March 2012 NIST08 NIST11 Wiley9/NIST08 Wiley9/NIST11 CWA - only available with 5975T Military Bundle MPW2011 The following is a list of all the libraries that do NOT install with only MassHunter: Agilent RTL Library Databases G1671AA Hazardous Chemical RTL Database G1672AA Pesticide RTL Database Library G1673AA Indoor Air Toxics RTL Database Library G1674AA Forensic Toxicology RTL Database G1675AA JPN Positive List Pesticide RTL Database G1676AA Fiehn GCMS Metabolomics RTL Library G1677AA Environmental Semi-VOAs RTL Database G1678AA Solvents Plus RTL Database G1039D (MPW - 2007 edition) All other libraries may fail to install. The libraries are valid and can be searched by MassHunter only the installer fails.
Temporary Solution:
Install the software on a system with ChemStation software installed then locate the .L folder and copy it and its contents to the MassHunter system. The library should then be functional in MassHunter.
Fix Information:
Plans exist to address the install issue on all library installers. Dates to be determined.
Keyword:
One-line Description:
QQQ: NIST Search Utility can cause acquisition to hang while using QUAL.
Problem:
Intermittent freeze up while having GCMS MassHunter Data Acquisition loaded not just running when user runs NIST 2.0 Search Utility software.
Temporary Solution:
1 – Qual and NIST only with no acquisition running in the background do they get a lockup – Our Problem is Acquisition SW Locking which means No lockup in this scenario. 2 – Qual and NIST are running but they are NOT using the current data file – sequence is not calling QUAL – Yes, only if they do NIST search again 3 – Qual and NIST are running and they are USING the current data file in the sequence – sequence is not calling QUAL – Yes, only if they do NIST search again 4 – same as #2 but sequence is calling QUAL -- Yes, only if they do NIST search again 5 – same as #3 but sequence is calling QUAL -- Yes, only if they do NIST search again "If they do NIST search again" ==> means if the NIST window is already opened and then you open Acq and run no problem. Acquisition will hang the moment you launch the NIST search from the Qual window meaning Acq is hanging when the search algorithm is running. Do not run Acquisition while using QUAL with NIST Search Utility
Fix Information:
Has been fixed in MassHunter GCMS Acquisition B.05.02.
Keyword:
One-line Description:
QQQ: Tune File Not Being Saved When Save Option is Checked
Problem:
In the Autotune panel, Save Tune File when Done was checked, but upon trying to exit autotune, a message saying that exiting without saving will discard any changes. So a manually save and then Exit Autotune may be required since it is not certain if the previous values were saved.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Pumpdown Temperature is not the same as the prompt
Problem:
When using the pumpdown button, the software prompts for low (100/100/100) or operating temps. Source operating temps are different by mode: EI=230, PCI=300, NCI=150. The prompt shows the correct operating temps however 230 is always loaded for operating temps for any ionization mode.
Temporary Solution:
When the system is pumping down without being connected to the Workstation then 100/100/100 is used. It is only when it is connected to the Workstation the source is set to 230.
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
QQQ: The GC parameter setting panel cannot be resized (larger or smaller)
Problem:
config 7890 only go to the GC edit panel. Place the cursor at the border, but no headed arrow appeared, the panel size cannot be changed
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
MSD: GC Status Panel is hidden by MassHunter GCMS Acquisition Instrument Control panel
Problem:
1. Show GC Status panel (Instrument/GC Status show/hide) 2. click QQQ InstCtrl pnal anywhere. (eg. click any menu) 3. GC Status panel is hidden
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: MassHunter GCMS Acquisition does not turn off AUX temp when Venting.
Problem:
MassHunter GCMS Acquisition does not turn off AUX temp when Venting. The user is given a prompt during the process to turn off the AUX temp.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Issues with Trace Ion Detection (TID)
Problem:
The SC DSP as it switches from one group to another group the SIM group changes, there is an 816 ms gap where no data is retained due to the fact that SC is collecting the 7 scans of the next ion to “prime” the digital filter known as TID.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ: PAL -- User should be able to view the PAL method during a run
Problem:
the PAL method should be viewable during a run just as the GC method. The GC Edit Parameters icon is ungrayed but the CTC-PAL icon is grayed and unavailable. The other data systems all you to view the method but not edit it.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QQQ: Software Installation -- there is font issue when installing the MassHunter
Problem:
There are three font types being used and also the size are different. Information being presented and step-by-step is correct.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Retention Time Locking Help is Incorrect
Problem:
n/a
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.06.00
Keyword:
One-line Description:
QQQ: Signal Event Signal Delay does not work
Problem:
Creating a signal event specifying delay signal does not work.
Temporary Solution:
n/a
Fix Information:
Was resolved in B.07.00
Keyword:
One-line Description:
QQQ: PAL -- CTC-PAL Status is always hidden
Problem:
Show CTC-PAL Status panel. select any menu/ try to start run. CTC-PAL status panel is hidden under Inst Control panel; this could be an inconvenience.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ: When tuning, the status bar does not always stay in the same place.
Problem:
When tuning, the status bar does not always stay in the same place. The information being presented is correct.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QQQ: Monitor Icon on Top panel is partially truncated.
Problem:
Monitor Icon on Top panel is partially truncated.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: MassHunter creates GC signal CH files that possess incorrect retention times when loaded into MSD ChemStataion or Ezchrom DA
Problem:
The second defect is the Retention Time Range of the data. The data was acquired from time 0.00 to 4.00 minutes. Since partial data collection is not supported, the data must start at time 0.00. However if you view this in MSD ChemStation Data Analysis or EzChrom Data Analysis, it displays from 1.00 to 4.99 minutes. Clearly, some aspect of the *.CH file written by MassHunter GCMS Acquisition doesn’t conform to the design specification. On a typical MassHunter GCMS Acquisition system with MassHunter Data Analysis, instead of MSD ChemStation Data Analysis or EzChrom Data Analysis, the GC/MS translator converts the .CH files into “archer” format. MassHunter displays the correct retention time range.
Temporary Solution:
A point patch (GC7890.dll and GC7890.pdb) is available as a temporary fix.
Fix Information:
To install the point patch: 1. In the directory C:\GCMS\MSexe, rename the existing files from: GC7890.dll to GC7890-orig.dll GC7890.pdb to GC7890-orig.pdb 2. Copy the new files GC7890.dll and GC7890.pdb to the directory C:\GCMS\MSexe Was resolved in B.06.00 Fixed in revision B.06.00
Keyword:
One-line Description:
QQQ: Numerous files will be left on the PC during uninstallation.
Problem:
The original files which were copied on PC and when they are updated due to the configuration. The Uninstallation will only touch the original files and leave the configuration and newer files alone.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Cannot copy message at the end of each run with sample prep
Problem:
Set up a sequence of three lines using a method with sample prep (sample overlap was on). At the end of each run, a message "Cannot copy D:/MassHunter/GCMS/3/PreTreat/prep1.pt to D:/MassHunter/GCMS/3/Data/g1.d/AcqData/meth1.m/prep1.m"
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Run does not complete until the sample prep of next sample is complete
Problem:
Set up a sample prep program with a 3 minute wait so that it would be longer than the the run time of the method. Associated it with a method and then setup a sequence using that method. While sample 1 was running, it executed the sample prep program of line 2. It was sitting in its wait state when the fist run finished. Software went into Post Run and sat there, -35791 appeared in the runtime field. When the sample prep was complete for line 2, the software completed it processing of sample 1.
Temporary Solution:
Sample prep program needs to be shorter than the run time of the method.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: There is no LTM related paremeter monitor in the instrument control.
Problem:
configure GC with LTM launch the software, goes to the instrument menu-->edit menu LTM related paremeters are not avaliable for monitors
Temporary Solution:
n/a
Fix Information:
Was resolved in B.07.00
Keyword:
One-line Description:
QQQ: Tunes save information to a PDF, the printed air-water check with graphics is not saved.
Problem:
Was trying to generate an air and water report and noticed the output gave a graphic but could not find the PDF.
Temporary Solution:
n/a
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QQQ: Translation -- Notes is untranslated when Retention Time Locking is finished.
Problem:
After Retention Time Locking running is finished, the information of Notes is not translated.
Temporary Solution:
n/a
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QQQ: Translation - Screenshots of online help for RT lock, lock method is remaining in English.
Problem:
Some of the Lock Method of RT Lock is in English, the should have been replaced by Japanese User Interface screens.
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.06.00
Keyword:
One-line Description:
QQQ: PAL -- "Starting GC Prerun but GC not idle" happens after CTC seq abort
Problem:
1. CTC-PAL Seq start 2. Abort Seq 3.CTC-PAL Control module become not "Remote control" 4. Check CTC-PAL configu does work. 5. Send "Reset CTC-PAL" by Reset CTC-PAL menu 6. Start Seq again. 7. seq can not start becasue "Starting GC Prerun but GC not idle" happens . Once it happens, user will need to reboot PC. After rebooting the PC, one can start Seq again without GC Reboot.
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QQQ: Simulate sequence.log has aligment issues, but all of the information is correct.
Problem:
Simulate sequence.log has aligment issues, but all of the information is correct.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: PAL, ICON -- CTC-PAL Icon does not show Edit Method Parameter panel
Problem:
1. Launch MassHunter GCMS Acquisition 2. Click CTC-PAL Icon. Edit Method Parameter panel is shown. 3. Change syringe. (Change PAL Config -> Release terninal lock ->(change syringe) -> Lock Terminal) 4. click CTC-PAL Icon again. Edit Method Parameter panel is not shown until re-load method.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: PAL -- parmaeter restore default by Change PAL Configuration
Problem:
1. Launch MassHunter GCMS Acquisition.
2. Change syringe.
(Change PAL Config -> Release terninal lock ->(change syringe) -> Lock Terminal)
3. Open PAL Parameter panel. The parameter resores default.
4. To recall the previous PAL parameters one needs re-load method to load the previous PAL parameter.
User may not realize "The parameter restore default value" because no message/no information about it.
Due to it, User may lost their correct PAL parameter.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Online help: no topic to TuneCheck to Sample Types in Seq table
Problem:
online help does not have contents about "TuneCheck" sample type.
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.06.00
Keyword:
One-line Description:
QQQ: [translation] some translation on tune report is not reported correctly.
Problem:
Tune report_EI auto tune report
1. Tune Date & Time: change the transaltion from“调谐数据和时间” Into “调谐日期和时间”
2. Tune File: change the translation from “数据路径”into “调谐文件”
3. Hexapole Accel: 六极杆加速仪-->六极杆加速
4.Iris: 光圈-->尾翼电压
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Cannot search " JPN strings" in tune report
Problem:
Open Tune report (PDF format) Find "アバンダンス" (translated "abundance") Cannot find it. English strings (eg. EI) can be found. (Search for word does not work all the time for translated text.)
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: "Invalid XML strings"
Problem:
Does not occur all the time, it appears occasionally.
Edit MS parameter.
select OK.
"Invalid XML strings" may appear on the display line. Nothing happens but the user may see this prompt.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ: PAL -- Undefined symbol: ok at the end of CTC method run
Problem:
Setup and ran a method with CTC-PAL injection. At the end of the run, one could see a Undefined Symbol: OK on the message line. It did not appear to cause any problems. If the method ended in an error (such as neither GC or MS data collected), I see the Undefined Symbol: OK in the logbook.
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QQQ: Sequence log has no sample type information in the summary report.
Problem:
Run Seq Seq log file does not have the sample type information.
Temporary Solution:
The user could cut and paste the infomation into an excel spread sheet and then print out the results.
Fix Information:
Fixed in revision B.06.00
Keyword:
One-line Description:
QQQ: PAL, Barcode: Software currently reads BarCode from a fixed vial location.
Problem:
Software currently reads BarCode from a fixed vial location. It should use the actual vial location that is known to the Sample Table Editor. "ReadBarCode$()" should use the fixed location when it is executed from the command line.
Temporary Solution:
User needs to use a fixed vial location to read the BarCode from the vial.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QTOF: The panel of Ion Source Selection doesn't appear automatically after multi-sources in re-configuration if it is NOT configured at the first time
Problem:
In user selects two or more ion sources in Instrument Configuration, the panel of Ion Source Selection should appear automatically and prompt user to select a correct source for the running instrument right after the application was launched.
Temporary Solution:
This behavior occurs ONLY for the configuration at the First time after the application was installed. For the re-configuration other than the first time, user must open the panel of Ion Source Selection manually.
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QTOF: Missing a print option to print out the TOF Calibration Results
Problem:
n/a
Temporary Solution:
n/a
Fix Information:
A text format of the results are automatically saved under the tune results directory.
Keyword:
One-line Description:
QTOF: For GC QTOF, missing steps on how to install a source when a source is not in the unit.
Problem:
Removing the Ion Source from the QTOF is based upon removing an ion source and placing a clean ion source back into the instrument. If the user wants to remove the source and not place one back in then an abort will need to be done. If the user would like to place a clean source into the instrument while there wasn't a source installed then the steps would not be correct.
Temporary Solution:
User needs to be aware if they abort the steps then the instructions may not match, but the re-installaton will still be funtional.
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QQQ: Lost connection to MS instrument if running EI with extractor ion source and Neutral Loss scan type
Problem:
n/a
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: Missing Method Tool for the QTOF for collision cell optimization
Problem:
Missing Method Tool for the QTOF for collision cell optimization Collision Cell Optimization Engeries
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: Cannot install MassHunter GCMS Acquisition to non-default location
Problem:
1. Install software to C:\y-gcms. 2. Indicate Data location to D:\y-MassHunter 3. Install is completed 4. Go into MS Configure Instrument, configure instrument 1as a (7890-7200) however "1" folder is not created under D:\y-MassHunter trying to launch Inst1. an error occurs
Temporary Solution:
Use default locations for installation of the software package
Fix Information:
Was resolved in B.07.00
Keyword:
One-line Description:
QTOF: Translation issues in Tune; TOF Mass Calibration, not all sections have been fully translated in Japanese and Chinese
Problem:
n/a
Temporary Solution:
n/a
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
SQ: Run/Resume Batch Gets Confused When Resuming on First LIne of Sequence
Problem:
In Drug Mode, started a Batch and then stopped it to edit the method. When selecting Run/Resume a Batch, It asks if one wanted to resume the aborted batch at line 1. Select No, and the batch was canceled.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: In manual tune loading from 'get defaulted value' may not work due to system set conditions
Problem:
n/a
Temporary Solution:
Reload from a known good tune value and then update with the new values.
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QTOF: The QTOF mass calibration result page is not fully localized
Problem:
n/a
Temporary Solution:
n/a
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QQQ: The number of injections displayed on 7890 panel and in GC parameters window do not match
Problem:
In MassHunter GC/MS Acquisition B.05.01, the method is initially set up to do two multiple injections. However when the method is reloaded, the GC Edit Parameters window shows only one repeat while the 7890 GC instrument panel shows two injections. Also the method stored along with data (txt file) shows only one injection.
Temporary Solution:
n/a
Fix Information:
The issue is fixed in version MassHunter GC/MS Acquisition B.05.02.1031.
Keyword:
One-line Description:
QQQ: Dual injection, if volumes are changed for front, must be filled in for rear also
Problem:
When setting up a dual injection sequence, if a value is entered to override injection volume for one of the samples in the front, the user must enter a volume for that sample in the back also. If not you will see the following message "Invalid injection volume specified: Back : 0" A blank volume in other cases means use the method value. No error message will be given if the front and rear injection volume is blank.
Temporary Solution:
n/a
Fix Information:
Was resolved in B.07.00
Keyword:
One-line Description:
QQQ: Wrong actual barcode in .CH file when running dual injections.
Problem:
When running a dual injection method (linked or unlinked), the .CH file from the second signal or rear datafile, shows the actual barcode from the front vial, instead of the rear vial. This issue is also observed when running sequence.
Temporary Solution:
A point patch (GC7890.dll and GC7890.pdb) is available as a temporary fix.
To install the point patch:
1. In the directory C:\GCMS\MSexe, rename the existing files from:
GC7890.dll to GC7890-orig.dll
GC7890.pdb to GC7890-orig.pdb
2. Copy the new files GC7890.dll and GC7890.pdb to the directory C:\GCMS\MSexe
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QTOF: Mass Range does not match Product Data Sheet
Problem:
Quad range was 20 to 1050 while the TOF has 15 to 1700. The screens in MS Parameters has 20 to 1700 which does not apply to either in the specifications.
Temporary Solution:
We allow a larger range for trouble shooting than we support for "specification".
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: User not warned about having scan range values below the TTI filter cutoff setpoint
Problem:
User not warned about having scan range values below the TTI filter cutoff setpoint
Temporary Solution:
Verify the cutoff range for the TTI filter is approximately the value of your low range in the MS parameters or it could result is a no response at the lower range.
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QTOF: Bakeout - At the completion of the cycle user must exit out and re-enter if they want to run again
Problem:
Bakeout - At the completion of the cycle user must exit out and re-enter if they want to run again
Temporary Solution:
At the completion of the Bakeout cycle, close the application and then click on Bakeout again if one will like to rerun the process.
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QQQ: Untranslate: 7000 Triple Quad, method report; title has English
Problem:
Print Method report to 7000 system. Triple Quad MS parameter is printed. the title has English. It has been same with B.05.02. Triple Quadrupole トリプル四重極 MS Parameters レポート MS パラメータレポート EM Saver EM セーバー Auto baseline subtract 自動的にベースラインを減算する
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QTOF: It is possible during manual tune depending upon the turn on sequence the filament is on and there is no signal.
Problem:
It is possible during manual tune depending upon the turn on sequence the filament is on and there is no signal. Changing the emission current and/or verifying the calibration valve is open does not display any response after pressing start.
Temporary Solution:
Exit out of the Manual Tune, Close instrument control, power cycle the GC Q-TOF (push the power button to off position, wait 10 seconds, push the switch so power is back on, wait about two (2) minutes), and now go back into instrument control.
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Welcome message is incorrect when there is no MS configured
Problem:
When I configure a GC only instrument (no MS), the welcome message states "Welcome to Agilent Unknown GC/MS Data Acquisition Workstation".
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QTOF: TOF HV Actuals, the setpoint versus monitors do not have monitors showing the accepted range
Problem:
n/a
Temporary Solution:
n/a
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
MSD: Offline Method Displays Wrong Instrument Configuration
Problem:
Offline Method Displays Wrong Instrument Configuration Offline Instruments shows the default configuration file for the offine instrumentation.
Temporary Solution:
To show the correct GC configuration the user will need to copy over the GC configuration files from the online GC instrument into the offline session.
Fix Information:
Was resolved in B.07.00
Keyword:
One-line Description:
QQQ: Cannot edit GC parameters during a run
Problem:
While a method or sequence is running, the user is able to bring up the GC edit parameters panel to view the parameters, but the OK/Apply buttons are grayed so changes cannot be made.
Temporary Solution:
A point patch (GC7890.dll and GC7890.pdb) is available as a temporary fix.
To install the point patch:
1. In the directory C:\GCMS\MSexe, rename the existing files from:
GC7890.dll to GC7890-orig.dll
GC7890.pdb to GC7890-orig.pdb
2. Copy the new files GC7890.dll and GC7890.pdb to the directory C:\GCMS\MSexe
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QTOF: Acquiring data files in 2GHz or 4GHz are tune centric.
Problem:
Acquiring data files in 2GHz or 4GHz are tune centric. Tune centric means the user will not be able to change the method parameters to change the data rate.
Temporary Solution:
Tune files are called via the Method, so to change the data rate which is being acquired the user will need to change the tune file which is being called. Each tune file name will need to be unique based upon the data type/rate being used for the method. It is also recommended when the acquisition mode is changed between 2GHz and 4GHz that a TOF mass calibration should be done. This can be done via a keyword in the sequence table.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: MH Acquisition B.05.02 crashes single injection or sequence with one CTC tray configured
Problem:
The instrument crashes with the error message "System.IndexOutOfRangeException - Index was outside the bounds of the array" when running single injection or sequence with one CTC tray configured and using: 7890 / 7000B / MH B.05.02 / CTC Driver B.02.01.1 / CTC FW 4.1.5
Temporary Solution:
A point patch (GC7890.dll and GC7890.pdb) is available as a temporary fix.
Fix Information:
To install the point patch: 1. In the directory C:\GCMS\MSexe, rename the existing files from: GC7890.dll to GC7890-orig.dll GC7890.pdb to GC7890-orig.pdb 2. Copy the new files GC7890.dll and GC7890.pdb to the directory C:\GCMS\MSexe Fixed in revision B.06.00
Keyword:
One-line Description:
QQQ: MassHunter Acquisition B.05.02 freezes during manual run
Problem:
MassHunter Acquisition B.05.02 freezes during manual run.
Temporary Solution:
A point patch (GC7890.dll and GC7890.pdb) is available as a temporary fix.
Fix Information:
To install the point patch: 1. In the directory C:\GCMS\MSexe, rename the existing file from: GC7890.dll to GC7890-orig.dll GC7890.pdb to GC7890-orig.pdb 2. Copy the new files GC7890.dll and GC7890.pdb to the directory C:\GCMS\MSexe Fixed in revision B.06.00
Keyword:
One-line Description:
QTOF: In MSMS mode the user interface will allow you to enter 4 digits but the MS1 is in unit mass resolution.
Problem:
n/a
Temporary Solution:
n/a
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QTOF: During the autotune steps the software shows the progress but does not show the area which is being tuned.
Problem:
During the autotune steps the software shows the progress but does not show the area which is being tuned.
Temporary Solution:
The tuning progress is shown via the Green Bar Status during the tune. Just below the lower left window the user can see what steps are currently being run. The section to which the steps are being done is not shown but could be determined if one looks at the Advanced Tuning segments.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ - Thermal setpoints higher than allowable readback....
Problem:
Manual tune window allow temperature setpoints of 360/210/210 to be input for source/Q1/Q2 respectively. However the sensors trigger a fault once the readback goes above 350/200/200 /- 2 degrees.
Temporary Solution:
Use the maximum values of 350/200/200 for the source/Q1/Q2 for the temperature setpoints.
Fix Information:
Resolved in revision B.06.01
Keyword:
One-line Description:
QTOF: Aborting Autotuning does not update the screen correctly, green bar process is not reset and voltages not turned back to starting point.
Problem:
If the user aborts an Autotune or Fast-Autotune it will terminate the program at this point and will not reset the status bar status. This is also true if the user uses the Advance Tune section of the software where the green bar status was not designed for. The Green Bar Status was designed to show the user the status of the Autotune steps.
Temporary Solution:
When the user starts the Fast-Autotune or Autotune the Green Bar Status will automatically reset to the initial conditions and shows the progress of the program.
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QTOF: "TOF Conditioning" icon appears on desktop when GCMS Acquisition Software is loaded
Problem:
TOF conditioning is for GC QTOF and TOF instruments. When the GCMS Acquisition software is loaded the desktop ICON will be placed on the desktop. This could give the impression to the user this could be used for GC QQQ instruments.
Temporary Solution:
When the user clicks on the 'TOF Conditioning' desktop ICON it will come up with a pull down dialog box. The pull down dialog box will only show GC QTOF/TOF instruments which have been configured. GC QQQ instruments will not appear or be a valid selection.
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QTOF: The acquisition software closed, there is no security even if actually running.
Problem:
After simulating a sequence, the user could click on the 'X' on the GCMS Acquisition software and closed the Workstation down.
Temporary Solution:
If a macro is running (which is the case if there is a method "running" or a sequence "running", the MassHunter GC/MS Acquisition will not close and an error message is displayed instead! If the user was editing the sequence table then there is no trap for closing the system down, the user will need to reload or recreate the sequence table which was being worked on.
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: Misconfiguration of an instrument will result in a connection but communication will not be possible.
Problem:
Instrument control checks for a valid IP address and then will bring up the Instrument Control Status Menus as well as showing the monitors for the configuration. If the configuration is not correct then the monitors will show "------" and when one clicks on the manual tune an error message of "Offline" or "Incorrect Firmware" will be displayed to the user.
Temporary Solution:
User will need to go into the MS Configuration and recheck the configuration of the instrumentation. With the correct hardware configuation the monitors will show the correct status information.
Fix Information:
Need to have the correct configuration or system will not report back the correct status information.
Keyword:
One-line Description:
QTOF: Failure of mass calibration in a sequence
Problem:
In the case of EI, the autotune process sets the emission current to a value appropriate for the pressure of PFTBA at the end of a 1.5 hour process, which is substantially lower than the value even several minutes after the valve is first opened. This is especially true if the system has been sitting idle for some time. Therefore, if a user launches a sequence that begins with a recal keyword after the system has been idle for a while, the recal is likely to fail due to saturated peaks. Since the previous calibration would be old, significant errors are likely. In CI this can also happen, but an additional similar scenario can result if the system is still approaching stability. On my system, I observed NCI ionization efficiency increasing dramatically over time, causing a reasonable starting tune to go into saturation over the course of several hours. Again, this resulted in recal failures during the sequence.
Temporary Solution:
n/a
Fix Information:
Has been resolved in revision B.06.01
Keyword:
One-line Description:
QQQ: Closing the "change configurigation windows in MassHunter" will lead to a not saved configuration.
Problem:
step to reproduce the error: - go to instrument --> Change PAL configuration - press unlock terminal - change something in the CTC-PAL configuration (i.e. a tray assigment) - press lock terminal and close the window using the red cross on the top right corner in this way the configuration is not uploaded, and can lead to wrong sample loaded.
Temporary Solution:
A possible solution is to remove the close red cross, in this way the user must wait until the real close button will be available.
Fix Information:
Was resolved in B.06.01
Keyword:
One-line Description:
QTOF: There are many untranslated strings in the tune parameter pane
Problem:
n/a
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QQQ - At the end of the autotune get an error message "Exception has been thrown by the target of an invocation. - Object is currently in use elsewhere."
Problem:
The error message is occuring while the system is trying to print out an autotune report. If connecting to a printer in network, the message "Exception has been thrown by the target of an invocation. - Object is currently in use elsewhere." came out always at the end of the autotune, no repot was printed out. While connecting to a local printer, the message would only appear when there was a communication issue with the printer.
Temporary Solution:
Use a local printer for the system, if a network printer is used then if there is a communication issue then the system will stop.
Fix Information:
Resolved in revision B.06.01
Keyword:
One-line Description:
QQQ - Reported values form the Air&Water check showing inconsistent information.
Problem:
The scan from the Air&Water check reports the following amu from Scan from report 18 5 5336 32 12 1224 69 82 3516
Temporary Solution:
The report was using profile data instead of scan data which will give different values and the Nitrogen amount is calculated out from the Oxygen reported which will be different from the display because the display will also show the Nitrogen from the collision cell.
Fix Information:
Resolved in revision B.06.01
Keyword:
One-line Description:
SQ: Allows Dual injection for Headspace
Problem:
Headspace can use only a single injection source at a time: front or rear. MassHunter GCMS Acquisition allows additional selection of Dual. This method actually runs but runs only the front vial.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
HS: does not remember 7319 HS license if configured as offline, then back to online
Problem:
Configure initially as online and enter HS license. Close session and configure as offline instrument. Reconfigure same instrument as online again. The IP is remembered, but the license is not and I must re-enter it.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Simulate sequence displays Method Path of the default path, not that of the sequence methods
Problem:
Create Methods that are stored in a different location: C:\GCMS\Methods. Do not change the default method path. Create a short sequence and browse to a method within that alternate folder. Save sequence. Simulate Sequence. The header shows the original default path: ' Method Path: C:\MassHunter\GCMS\1\methods\' This is very misleading. If it is the default, then it should say so. Probably true for Data path, too.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
HS: MSD with legacy HS does not include 'Set Tray position'
Problem:
MassHunter GCMS Acquisition/MSD Productivity Software with legacy Head Spaces' does not include any 'Set Tray Position' option.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Error in XML document (2,2,) on loading headspace methods created in previous build
Problem:
Load a 7890/LCV HS method that had been created in a recent previous build of MassHunter GCMS Acquisition. Get: '--------------------------- MethodUI Process.IsConsistent failure --------------------------- There is an error in XML document (2, 2). --------------------------- OK ---------------------------'
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: MassHunter GC/MS Acquisition does not invoke method resolution on cabling/uncabling of ALS/Tray
Problem:
7890B/7693 system configured, unplug the cable to the tray or ALS. No method resolution is invoked; nothing in logbook. Driver just silently resolves itself. There is not even a 'dirty' method flag. Close and reopen the session and only then does method resolution occur. Same for recabling. Even though the driver UI has updated if recabled, the sequence table ranges do not. Thus, saving the oddly resolved method to its same name, then starting a sequence using it fails with a range error.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QQQ: Foreline Pressure will not change to Torr
Problem:
If user changes the foreline pressure configuration to Torr, foreline pressure will remain in mtorr. Changing to another pressure display (Bar, Torr) will still display mTorr.
Temporary Solution:
n/a
Fix Information:
Resolved in revision B.06.01
Keyword:
One-line Description:
SQ: No Print Custom Report Option in the Sequence Table
Problem:
MSD Productivity Software had a Print Custom Report. Drop down box in the sequence table. There are no custom report options currently avaiable in the MassHunter GCMS Acquisition sequence table.
Temporary Solution:
User will need to define the report via the Data Analysis package with is being used.
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: no warning after change in instrument configuration when unable to configure the source
Problem:
When configuring the source after swapping, the source configuration window flashes and dissapears (does not allow to change configuration) without giving a warning that only one source type was configured in the instrument configuration.
Temporary Solution:
n/a
Fix Information:
Has been resolved in revision B.07.00
Keyword:
One-line Description:
SQ: Method print does not specify injector used
Problem:
A print of the method does not indicate which injector is designated as the specific source. The injection source is listed only as GC ALS. No mention of Front, Rear, or Dual.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Users need training in how MassHunter graphics work (Real-Time Plot, SCAN window, PROFILE window, etc.)
Problem:
1. Set up a run with real sample (MDL) with two saved signals; Front signal and Front-Back Signal, both of which were collected from the front inlet- front detector. 2. Set up for the first signal to be linked to large real time plot with default axis settings. Default Y-axis range from 0 -- 1 by tenths. (See pic) 3. Plot displayed large solvent peak but expected four smaller peaks not in evidence. 4. Opened Chromatogram Manager by right clicking on large plot. 5. Changed Y-axis range to 0 -- 20. Clicked OK. 6. No changed in Y-axis range of large plot. (Same pic) 7. Reran MDL sample. No change in result. 8. Set up delayed signal event to start posting after solvent peak. No change in large plot except to label point of signal start. 9. Printed Area Percent report displays solvent peak off the scale but smaller peaks remain not visible and indicated only by the time occurred.
Temporary Solution:
Double-click on plot area to switch between Normalized and Absolute modes of Y-Axis display.
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
QQQ: Compliance, Analyst I should be able to see GC Show/Hide Status Menu
Problem:
In Compliance mode and logged in as Analyst I, select the Instrument Menu. The option MS Show/Hide Status is Available, but GC Show/Hide Status is Not. If the user is connected to a 7890, this option should be available.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Print method only prints the saved method, it does not print any of the changes
Problem:
The parameters in the MS acq method report are from the saved file, not the current settings. If a method has been changed the report will be inacurate.
Temporary Solution:
When edits have been done to a method, before printing a method, save the method and then print the method parameters.
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Uninstallation needs manually open UAC windows to continue the process
Problem:
During uninstallation, UAC window does NOT automatically continue the processes; instead the UAC icon appears on the bottom bar without any message, and wait for the user to open it manually. If user does not pay attention for this icon, the process hangs forever.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: QTOF Firmware - Incorrect handling of IRM setting when there is no gas controller
Problem:
In an EI-only system (no gas controller), the firmware ignores an IRM setting to Vial 1. Instead the firmware sets IRM to OFF.
Temporary Solution:
Need to make sure gas is flowing or has been supplied for the IRM.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: GC Sleep Alert on connection should say 'GC' not 'Instrument'
Problem:
Connect to a GC/MS/HS system of which the GC is asleep. Alert advises: '--------------------------- Alert --------------------------- Instrument is in SLEEP mode. Do you want to Wake the instrument up? --------------------------- Yes No ---------------------------' I originally logged this against the HS, thinking it was asleep, but knowing that it was not. This wording should be clear about what part of the SYSTEM is asleep, in this case, the GC. 'Instrument' is much too general to be of any value.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: request for context-sensitive tool tip information for the 'Instrument Status' control
Problem:
The Status part of the GCMS Acquisition in the upper left corner is name 'Instrument Status' and reflects green, yellow, or red, reflecting any PART of the SYSTEM that is not ready or in a fault. This is too general to be of any use. I am told that the part of the 'Instrument' (also misnamed) will have a small light indicating which part is offending. A tooltip over the Status color would be additionally helpful since the indicator is not very obvious. (HS doesn't even have one.) However, what is now called an 'Instrument' can be comprised of several independent 'Instruments': the GC, MS, HS, CTC, 35900. Combined, they are a 'System', a more accurate term.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Stagger Keyword is Not Functioning
Problem:
GC Only EnviroQuant (Dual Injection) Setting a sequence that uses the Stagger Keyword, but it won't pass verification because the Dual Inj Vial column is blank (Rear vial 0 is out of range 1-100). It is not needed for the Stagger Option. The column can't be removed because the method specifies dual injection.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: GC Sleep/Wake menu items should activate only the relevant item; offer no qualifier; no log to logbook
Problem:
Menu items 'GC Sleep' and 'GC Wake UP' are both active. Only the relevant one should be active. Select either one and the action takes place if the GC is in the opposite state. However, there is no qualifier like 'do you wish to wake up the GC?' or 'Do you wish to put the GC to sleep?'.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
MSD: Make GC Method Printout consistent with MS Method Printout
Problem:
Currently, the layout of the GC Method printout and the MS Method printout are quite different. It would desirable to have a consistent look and feel to the System when one is printing methods and reports. The MS Method printout was well received and a request was made to make the GC one like it.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: 5975, Connecting to a MS that is already connected to
Problem:
While setting up a second GC/MS system using the same MS. Started up the instrument but did not receive any error - nothing was in logbook. Instrument Status was Ready. It appeared as if everything was OK, there is no indication to the user that the instrument is already in use.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Can't Run Unlinked Sequences: Undefined Symbol: dummy_name$
Problem:
When attempting to run an unlinked sequence, getting undefined symbol: dummy_name$.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ: System Verification result in PCI is incorrect
Problem:
The verification report could show Oxygen Abundance (Ab 22289) which is over the limit (100 counts); however the results section will show "OK"
Temporary Solution:
User will need to look at the abundance and limit to see if the values are within the range.
Fix Information:
Resolved in revision B.06.01
Keyword:
One-line Description:
SQ: Edit Entire Method... does not include Sample Prep, even when it has already been specified
Problem:
For any method, whether you have specified to add Sample Prep or not, select Edit Entire Method... Options do not include option to edit the Sample Prep dialog.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: When MS source or quad is not ready, statuses indicate ready
Problem:
Temperatures are not included in the set of criteria that determine when a SQ MSD is ready or not.
Temporary Solution:
Review the status display box to see all of the messages and status.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: No View menu item for GC only configuration after addition of DA
Problem:
Configure GC only and GCMS. Install Classic DA. Reconfigure both instruments. The Data Analysis icon is created on the desktop for both. However, there is no View menu item for DA selection within the GC only configuration.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: Scan Speed Method calculations and Actual calculations do not match up
Problem:
Scan Speed Setting Method Editor Calculation Actual Fast 20.0 12.42 Faster 22.7 15.05
Temporary Solution:
There are differences for N=0 and different scan ranges and this will show up as differences in the actuals.
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
QTOF: Selecting “single transient” will put the QTOF into a stage where you need to reboot the unit to be able to use the system again.
Problem:
Once you select the checkbox “Single Transient” (within the Acquisition tab from Manual Tune) AND then select the START button the counts display jumps up to about 10 * 9. After this the system does not react to any other software action and to recover a rebooted the QTOF from the telnet window.
Temporary Solution:
'Single Transient' is used for gain adjustment and should not be used for normal operation.
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
SQ: Allow CI Tune from Tune Icon
Problem:
the user is only able to do an EI Tune from the Tune icon.
Temporary Solution:
Clarification: The Tune icon should allow you to run the currently-selected (i.e., last) tune.
Fix Information:
n/a
Keyword:
One-line Description:
HS: HS Help Topics: Cannot find any file that matches either the OS culture or English; using default file name
Problem:
7890B with 7697 configured. Select Instrument\HS Help Topics. Get: '--------------------------- --------------------------- Cannot find any file that matches either the OS culture or English; using default file name --------------------------- OK ---------------------------' Click OK and 7697 Help opens. 'Overview of 7697...'
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QTOF: Instrument Status indicator shows incorrect sign: "Ready" in green when MS lost connection
Problem:
Depending upon how the communication signal was lost, the 'Ready' indicator may not show the correct status.
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
SQ: no indication on tune report that tune has failed
Problem:
Ran a 5975 autotune, the tune failed and the report printed. There is no indication on the report that the tune has failed.
Temporary Solution:
To see if the values in the tune report are valid, one should run the Tune Evaluation to check the Tune performance.
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: Source temperature of NCI rises during emission on
Problem:
There is a thermal equilibrium for the system. As a result, turning on the filaments (emission on) will cause the temperature of the source to rise if the previous setpoints used on the transferline, source and quad temperature are already at thermal equilibrium.
Temporary Solution:
To decrease the amount of temperature increase to the source with the turning on the filaments, one can decrease the temperature of the transferline and/or quadrupole or increase the setpoint temperature of the source.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Adding real time plots/monitors to instrument control are stacked
Problem:
When you add realtime plots or monitors to Instrument control, they are always stacked on each other.
Temporary Solution:
Use "Arrange Monitors" in Window menu to auto-arrange.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ: Changing default paths copies currently loaded file to new directory
Problem:
Changing the default method, data or sequence paths will also copy the curently loaded file to the new directory. If there is a file already there by that name, it will overwrite the file with no warning.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QQQ: Reset Counters panel in EMF Untilities Incorrectly specifies Pump Oil.
Problem:
In EMF Untilites, pump oil is in the Set Limits panel, which has it's own reset button. The Reset Counters panel shows pump oil as a selectable option. However, this panel resets the counters panel, not the limits panel, so pump oil is not reset through this selection.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: PAL Status menu item does not check/uncheck
Problem:
Select to view PAL Status. The menu item does not check.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: cancel on set tune masses does not cancel Tune Wizard
Problem:
If one hits cancel on the Set Tune Masses Dialog, you are sent to the next dialog and the Tune Wizard is not canceled. All the other dialogs cancel and return to Tune Window when you click cancel
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QTOF: Tune preview is inconsistent in showing disabled items
Problem:
Tune preview is inconsistent in showing disabled items. Some items are grayed out and others aren't.
Temporary Solution:
Go to the Mass Calibration entry and the viewable mass ions will be shown for the display. A maximum of six will be shown, the first six in the section.
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
QTOF: Inserting a unicode control character in the QTOF method time segment table causes an error
Problem:
Using the 'insert unicode control character' context menu item causes an error.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: Validation in QTOF method editor needs additional checking for parameters.
Problem:
There are a few minor issues with the input validation in the QTOF method editor. 1. The run time range is given as 0.1 to 999.9, but won't take 999.9 as a valid entry. Same for the solvent delay. 2. The Centroid Data Thresold % will round 100.00001 to 100 and show an error icon. If 100 is entered after this the error will still be shown. If a lower value is entered then 100 will be accepted after it. 3. In the acquisition tab the range given for the acq rate is 0 to 50, but the field won't accept 0. 4. For targeted MS/MS the collision energy isn't limited to 0-60 as specified in the device info file.
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.00
Keyword:
One-line Description:
SQ: Quick Tune Info appears in status line when click on Tune Icon in CI Mode
Problem:
When you click on the Tune Icon while in CI Mode, you get the correct dialog displayed.."Enter the CI Tune panel", but the information in the status line says this: "Tune MSD will tune the currently loaded tune file pcich4.u. Quick Tune adjusts mass axis and EM Only." This doesn't do Quick TUne, so that part is not applicable and should be ignored/removed
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: MSD Prod. Software to MassHunter GCMS Acq 5975 Method Migration not always clean
Problem:
Two methods were created in MassHunter GCMS Acq for a 5975 instrument (no GC). One of them is a Scan Method and the other is a Sim/Scan method. When trying to open both the methods in MSD Prod. Software (E.02.02 SP1), the SIm/Scan method loads properly, but the Scan method does not. In both cases a message saying "Edit entire message after method has loaded (or something like that)", which is fine. But, for the Scan method, "Acq - Global Lock Failed" message in the Status Line when selecting the edit method parameters icon. For Sim/Scan, the method parameters dialog.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Method editor doesn't fully validate chromatogram masses
Problem:
For several of the scan types the masses used aren't validated against the mass range supported by the QQQ. EIC - masses in the extracted mass or range can be above the upper limit for the QQQ MS1EIC and MS2EIC - the precursor range isn't checked and the product ion can be above the supported mass range BPC, MS1BPC and MS2BPC - excluded masses, product ion and precursor ion values aren't validated MRM - product ion and precursor ion values aren't checked to see if they are in the range supported by the QQQ
Temporary Solution:
Prior to running the method, validate the mass range(s) which have been specified.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Aux 1,2,3 Temp Monitors do not show Valve Box temps correctly; always green/Off
Problem:
GCMS B.07.00 , 7890 with heated zone plugged in and configured as Valve Box. Select Edit Monitors and view related Aux Temperature. Though the temp is on with a value, the monitor always shows 'Off'/green.
Temporary Solution:
Valve Box is not configured anymore as a Thermal Aux. You do not have a monitor for Valve Box.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: Execute => Ramp Lenses Graphs on printed report not labeled with name of lens ramped
Problem:
Execute => Ramp Lenses Graphs on report printout not labeled with name of lens ramped.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Run time is not counted up in software
Problem:
1. 7890B
2. Create a method. (Injection source = ALS), Signal 1 = FID
3. push "Start" button on 7890B HW
4. Signal is acquired,
In GC Status ; Run time is counted up,
but in SW, Status = Idle, Run time is not counted up.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Clicking Done in Manual Tune in Tune View does not prompt for Save Tune File
Problem:
When one clicks on the Manual Tune ICON in instrument control the Edit Manual Tune Parameters box will be displayed. Clicking on Done will prompt the user for the name of the tune file to be saved too. When one clicks on View and goes into Tune and Vacuum Control and then bring up the Edit Manual Tune Parameters box, clicking on Done here does not bring up the dialog box to save the tune file.
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
SQ: "Scan Speed" on Scan panel of Manual Tune is not consistent with the value in "Step size"
Problem:
The current values in Scan Speed comb box [6,50 (N=0), 3,125 (N=1) .....] is associated with Step Size 0.10. However, if Step Size is changed to 0.15, the options in Scan Speed are unchanged.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Function: Foreline Pressure; kPa ; significant figure is wrong.
Problem:
Configure 5975 Diffusion Pump When Fore line pressure unit = kPa, it is shown 0.004kPa because of the curernt "significant figure".
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Scan plot in manual tune shows incorrect information
Problem:
Although the scan range in Manual Tune settings and scan plot are correct, but the digital value being shown at the bottom part of the scan plot is not correct. This only happens in extreme cases, where there is no peak found at the first tune mass.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
QTOF: B.06.01 does not automatically create the TDA files at the end of acquisition
Problem:
The user must go into Quant to have the TDA associated files created and then go into QUAL even though they do not want to use QUANT. If the user is not careful then the files can be duplicated without the user realizing it and then when the original file is brought into QUAL and running deconvolution on it the system could lockup, about 75% of the time.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Tune Window Save function does not save text contained in graphics windows
Problem:
Information contained in graphic windows generated by capture, profile, etc, is lost when printed.
Temporary Solution:
All information shown in window text is saved in various CP variables.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Tuning ICON for the single quads is not the same type as in MS/MS or the QTOF
Problem:
SQ: Tuning ICON for the single quads is not the same type as in MS/MS or the QTOF The MS/MS and GC QTOF will launch a manual tune menu display while in Single Quad the ICON will ask the user what type of tune would you like to run and manual tune is part of the instrument control.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: GCMS always returns in Monitor mode following reconnection after Comm failure; somes crashes msinstcl.exe
Problem:
Connect to 7890 in GCMS. Disconnect the LAN cable. Following disconnection detection or when cable is reconnected, the software sometimes crashes: 'Msinstcl has stopped working'. If it doesn't crash, it always returns in Monitor mode.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Dynamic Ramp is blank if no tune file was loaded in Offline mode
Problem:
In Instrument Status "Offline" mode, the Dynamic Ramp panel is blank, until a tune file is loaded manually, even if the loaded method has already an associated tune file there. Also, all MS Params have default values associated with them too.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Sequence Table Assistant Contains Links To Missing File
Problem:
When the Sequence Table Assistant is launched on a PC where MassHunter Qual is not installed, an error saying that the spreadsheet contains links to the missing file 'MassHunter Reporting Qual.xlam' is displayed.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Sequence Table Assistant Problems when Installing MassHunter Data Acquisition onto PC without Excel
Problem:
When MassHunter Data Acquisition is installed onto a PC that does not have Excel, a shortcut to the Sequence Table Assistant is created, but when you click on the shortcut, Windows will display a error message that it does know how to open this file type (.xlsm). Also, without Excel, the STA spreadsheet and Help files will be installed to the C:\Library or D:\Library folder. If Excel is then installed onto the PC after MassHunter data acquisitiion, the Sequence Table Assistant will work, but help from the STA spreasheet will not work because it will look for the help file in the OfficeXX\\Library folder (Application.LibraryPath).
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: wrong column header on FlowSurvey.txt
Problem:
wrong column header on FlowSurvey.txt Ratio is done correctly but it shows the wrong ions
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: MSD editor panel, the EM default setting has issue
Problem:
configure 5977 MSD panel EM set as "EMV delta" the default relative voltage is -700. but the range is -500-500.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Stopping Run Method in Pre-run causes MassHunter GCMS Acq to hang
Problem:
If I have a method set-up with a GC/MS. Starting a run method. When the system is in Pre-Run (Run Status) and Instrument Status:ready, stop the run (using stop sign). Abort was recorded in the Log Book, but the system is stuck in the "Pre-run state" with Method xxx.m running. Only way out at this point is to Ctrl-Alt-Delete and kill it through task manager.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: Firmware geenrates error on method with many SIM time segments
Problem:
In MassHunter GCMS Acquisition when downloading a method with 100 sim time segment. Firmware show command error.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: While in Manual Tune view one cannot move the windows after clicking on EDParameters
Problem:
When the EDParameters screen is up and running, access to the other screens are locked out.
Temporary Solution:
Need to click on done, move the window to the new position and then start EDParameters again.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Open file in Qual before solvent delay results in error message
Problem:
Openning a data file while it is collecting and before the solvent delay Qual B.06.00 will display an error message about a missing file device.xml. Qual does not crash but the message will make customers wonder if the data file has been corrupted which it would be
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: it is confusing to users when you click on the tuning fork and it comes up with the Tune/Quick/Manual and you have to save
Problem:
When selecting the Tuning ICON one would expect to go into manual tune if one has a QQQ or QTOF instrument. Different instrument types has different functionality of how the tuning icon works.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Startup method behavior Always Upload GC method from Instrument
Problem:
Selected Specify Startup Method Behavior and selected "Always Upload GC method from Instrument". Shut down the software and started back up. It brought up a panel that requested User to "Press Yes to Upload GC Parameters from the instrument and overwrite the method" 1. It should not bring up this panel if one has selected "Always Upload GC method from Instrument" 2. It does not overwrite your method but creates a new startup method so the message is misleading. 3. If No has been stated to Upload GC parameters, it will download them instead.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: MSD Tune File Select (browse) does not show all parameters of the tune file.
Problem:
To see a preview of all the parameters just like the QQQ and the QTOF files one will have to go into the EDP parameters to view them. There is no preview of the tune parameters via the MS Parameters section of the software.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
MSD: Configured my GC as 7890 for offline, how do I know if it is a 7890A? 7890A+ or 7890B with the features
Problem:
MSD: Configured my GC as 7890 for offline, how do I know if it is a 7890A? 7890A+ or 7890B with the features For online instruments, the GC driver is automatically detected and will display the correct options for the 7890A --> 7890A+ --> 7890B. For offline instruments, instrument control will automatically default to a 7890A configuration.
Temporary Solution:
Copying a valid 7890B configuration file from an online instrument and copying it into an offline instrument will have the new features appear for the offline instrument.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: In SCAN window, "Speed" means either Samples (0 to 7) or Fast Scan (FS1 to FS3)
Problem:
"Type" means filter type. For Fast Scan FS1 to FS3, it will be "Fast"
Temporary Solution:
Fast basically means at this scan speed the normal 0.1 step size is not being used but 0.2 step size is being used.
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: At Instrument Control level, no visible way of knowing what tune file is loaded
Problem:
User can see what tune file is loaded by showing the MSD Temperatures, Method Edit or Edit MS Parameters dialog."
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Load Tune Wizard with default tune files, don't get Target Message
Problem:
When you select Tune Wizard from the Tune Menu Item with a default tune file (atune.u or etune.u) loaded, you get a window in which to pick masses. After clicking ok, you should get a message saying that "this tune file is not for Target tune" or something. You don't see the message if the tune files are the default tune files. Hitting ok brings you to the next dialog correctly. If you have a loaded tune file (named atunexxx.u or etunexxxx.u) and you select Tune WIzard, click ok on the masses, you get a message saying it is not a a target tune file. Click Ok and Tune Limits dialog are loaded.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Prompt for saving as tune reports *.pdf and *.xps now requires mouse click to be brought up
Problem:
Configure Printer for PDF or XPS and run a tune. The prompt at the end of the tune that pops up to ask you to save to a file never appears until you click the mouse somewhere on the UI. This could give the impression that the software has hung. Tune complete shows at the bottom of the Tune window.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Uninstalling the MassHunter GCMS Acq does not remove all of the Acquisition desktop ICONs
Problem:
Uninstalling the MassHunter GCMS Acq does not remove all of the Acquisition desktop ICONs The ICONs which have been left are not functional. Installing a new version of the MassHunter GCMS Acquisition will remove the old version of the ICONs and then create new desktop ICONs upon the configuration. This does not occur all the time, but when it does, it could be confusing to the user has the software been fully removed, yes it has.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: It is not clear what happens when a tune has been completed.
Problem:
One would expect to see the tune summary displayed and then click ok to continue, a hardcopy is printed but if the printer is not close then this could be an issue.
Temporary Solution:
Look at the prompt line and there is a statement which will show Tune is complete.
Fix Information:
n/a
Keyword:
One-line Description:
Sequence Assistance opening the file defaults to PatternConfiguration instead of SequenceTable Worksheet
Problem:
Sequence Assistance opening the file defaults to PatternConfiguration instead of SequenceTable Worksheet
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Manual Tune: Must start/stop scanning to incorporate changes to dynamically ramped parameters
Problem:
To see the effects of changing the dynamically ramp lens but when you enable this and start scanning it will take the initial values of the lenses and it will show up however if you start the editting of the dynamic it will not show up unless you stop the scan and restart it again.
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
SQ: When an old sequence table is loaded, the sample types are different
Problem:
When a sequence table from the MSD Productivity Software package is loaded into the MassHunter GCMS Acquisition different sample types will be assigned because of the different types which are now available.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: MassHunter sends garbled LUI:MSG:RECV 'xxxxxxxIdle' message to 5975/5977
Problem:
Information which is being sent from the MassHunter Workstation to the Local Control Panel (LCP) has word wrapped issues. The 5975 has two lines for display while the 5977 has 4 lines and at times the text is overwrapped due to the display types.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Dual vial ; no error message even when Front and Rear Vial is same
Problem:
1. Create a dual sequence. (Front = 1, Rear = 1)
2. OK to exit Sequence table
3. it is better error/warning message is shown when I click OK.
"Don't use same vial for Front and Rear"
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Selecting a different tune file...but the temperatures do not automatically change.
Problem:
After loading a new tune file with different temperatures, the MS Temperatures dialog is show. for the new Setpoints to be applied, the user must click "Apply"
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: CI gas purge takes longer than specified time
Problem:
The default purge time states the time will be 6 mins. But with the communication links this time is closer to 7 minutes not the 6 minutes.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Could not return to Instrument Control view from Tune View
Problem:
Started MassHunter GCMS Acquisition
Changed to Tune View
Loaded a new (CI) tune file Clicked on View \ Instrument Control
Got (expected) message - "Be sure tune file is save. Switch view now"?
Clicked "Yes"
Got (expected) message - "Update default.597x.m to use current tune file?"
Clicked "Yes"
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Monitors are hard to line up: spectrum, tic, scan 1-1
Problem:
If the window size is smaller than all of the current monitors being displayed then positioning the spectrum, tic, scan 1-1 monitor box will be difficult.
Temporary Solution:
Expand out the window so all of the monitors can be seen and then auto align the monitors.
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Need to have an autosave of the tune report to PDF automatically
Problem:
Started a sequence and walked away and came back and found the sequenced has stopped because it was waiting for a PDF file name. The system should automatically save a PDF image of the file under the directory so that it will not stop the sequence.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
PAL: For CTC multiple overlap - Don't inject on a barcode mismatch and continue sequence is invalid
Problem:
For a CTC multiple overlap sequence with barcodes, if there is a barcode mismatch and Don't inject is selected in the Start Sequence panel. the sequence will be aborted regardless of the users selection of Continue Sequence. Not sure if this should be noted somewhere.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Tune Report in View tunes to have extractor data
Problem:
In tune & vacuum control, select "view tunes" from file menu. Tune Report spreadsheet is opened. Click over to EI Lens Value report. The extractor and body voltage data is missing.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: TuneMS and Tune Menus are inconsistent
Problem:
When you enter tune from the Tune Icon or the Tune Menu item in Instrument control, the tune window has a TuneMS menu. In this menu, the following tunes are not listed, but are listed in the Tune Menu in the Tune and Vacuum View: Extraction Tune lomass autotune BFB Autotune
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Tune evaluation only evaluates autotune; evaluation results is based on an autotune.
Problem:
load etune, run tune evaluation from the tune menu of tune and vacuum control. The system only evaluates the atune file, not the currently loaded tune file
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04 This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
SQ: SimAcq doesn't set the scan window x axis range to include all ions
Problem:
The scan window's x axis is left at whatever the range was from the last scan command. It should be set to include all the ions listed in the SimAcq command. The data is acquired for all the ions, it just might not be displayed depending on the previous scan commands and the range of the ions.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Two copies of method are being saved if Save Method with Data is checked
Problem:
If Save Copy of Method with Data is checked in the Method Information screen, when the method is run two copies of the method are saved. One in the .D folder and one in the AcqData folder.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: While in Manual Tune, can't click directly on ramp Graphics Window to select a new maximum.
Problem:
While using the EDP and ramps the user will need to manually update the values into the EDP parameters section. One can click on the ramp plot and the value will appear and be highlighted but it will not be transfered to the EDP, this needs to be done manually.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: mass gain values for the speeds are stored in the smartcard not in the tune file
Problem:
If someone is tracking the mass gain values for different speeds the tune reports must be kept because the values are not saved in the Tune View Files nor in the tune file, the values are saved in the SmartCard and will be overwritten by the next tune.
Temporary Solution:
n/a
Fix Information:
MassHunter GCMS Acquisition B.07.00 Data Analysis Quantitation and Qualification . . Update notice
Keyword:
One-line Description:
SQ: Undefined symbol: dottune may appear, false error message.
Problem:
In the Tune Window, when you select Tune MSD from Instrument Control, the TuneMS menu item has Target Tune as an option. Selecting Target Tune gives you a undefined symbol: dotune Nothing bad happens, but just a false error message.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: LCP -- text is being wrapped around the display when communication is first being started
Problem:
SQ: LCP -- text is being wrapped around the display when communication is first being started
When the Bootrom comes up the word Loading is being wrapped around the display
.....lo
ading......
Temporary Solution:
This is just a visual flaw, the unit is fully functional and there are some other prompts and messages which does the same thing.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: add warning if user saves method in a format that will not run
Problem:
Currently, the user is allowed to save a method with xxxx.xxxx.xxxxx.m or something similar. the method saves and can be loaded and reloaded without issue. However, the method will not run and gives the impression that the system hangs when the user tries to RunMethod.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Checking/Unchecking "Use MS" option does not update icons reliably
Problem:
Check or uncheck the "use ms" option under the Inlet type icon, the MS icons are not updated reliably. Unchecking "Use MS" will cause the user to wait or perform mouse actions to gray out MS icons. Checking the "Use MS" (with icons grayed out) will not enable those icons until the user closes and restarts MassHunter GCMS Acquisition.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Edit Entire Method 'Instrument Information' does not remain checked
Problem:
On occasions when doing the Edit Entire Method the 'Instrument Information' does not remain checked.
Temporary Solution:
Going directly to Instrument Information, make the edits and save.
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: LCP of MS not updated
Problem:
LCP of the mass spec is not always updated. For example, bringing up the vacuum dialog and selected Vent. One can see the temps going down and pump off and eventually the panel showed vent cycle complete. However, looking at the LCP of the mass spec it shows vent prepare.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Print report produces bad report in CI
Problem:
Printing a report in CI starting with the reagent gas off, the wait is not long enough to establish the gas flow, and as a result the profiles for Quad 2 (which are done first) are bad.
Temporary Solution:
If you repeat it, it will look fine since stable flow will have been establish by then. Also, the report looks fine if the user starts with the gas on.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Deleting entries in dynamic ramp table doesn't work well
Problem:
When one tries to delete multiple entries of mass/voltage pairs from a dynamic ramp table, it often doesn't delete them all. For example, make 6 entries, highlight 4 and delete. Only the last 3 are deleted. If you highlight the retained one and delete it, however, it is deleted, so that is an acceptable workaround.
Temporary Solution:
If you highlight the retained one and delete it, however, it is deleted.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ: Aquisition dwell time parameter can't be adjusted to lower limit
Problem:
The acquisition dwell time parameter has a lower limit of 0.016 ms and a step size of 0.01 ms. The step size means the lowest value the slider can reach is 0.020 ms. So the limits displayed have a lower value that is unattainable. Also, sometimes this setpoint does say 0.016 ms until the user attempts to adjust it, then it jumps to 0.020 ms and 0.016 ms is never seen again. This is not reproducible but has been seen several times.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Peak logging produces invalid data
Problem:
While logging a maximum of 10 peaks to a file by checking the appropriate box. One of the files contained spurious values. Specifically, several of the lines have 0 as the target mass.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Object instance error happen when stopping Seq (CTC)
Problem:
1. CTC Seq start (5 line seq) 2. Abort Seq at Line 3 3. Line 4 is start, Stop again. 4. Objenct Instance error happens. (See CTC_Seq_abort.jpg) 5. Close MassHunter GCMS Acq, restart MassHunter GCMS Acq, but 7890B is monitor mode. 6. check 7890GC front panel, shows some message 7. unless pressing "User key 1" twice on 7890B HW, MassHunter GCMS Acq can not make 7890b online, becasue 7890B is monitor mode.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: The software installation does not allow the user to specify where they was to install the core software only the data/supporting files
Problem:
On newly installed systems the MassHunter GCMS Acquisition installer will prompt the user where they would like the core software to be installed. Once the Classic Data Analysis software has been installed the installer will see where it has been installed and then will install the core portion of the MassHunter GCMS Acquisition to the same location. So if you do not see the prompt for the core software installation, then the MassHunter GCMS Acquisition detects the installation fo the Classic Data Analysis software.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: If the wrong printer/driver is being used then the numbers in the tune report can look truncated.
Problem:
If the wrong printer/driver is being used then the numbers in the tune report can look truncated; this can be seen in the number fields. If the field is center justified then it looks okay but if the field is right justified then it will appear as the last column of pixels have been deleted.
Temporary Solution:
Use the correct supported printer driver for the system.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: error prompt box gets hiddens by the instrument control window
Problem:
error prompt box gets hiddens by the instrument control window; if one is not careful the prompt box could be moved and the user may not be able to see it.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
HS: MassHunter GC/MS Acquisition does not update Instrument Status following HS reconnection in-session
Problem:
Start 3 line sequence and at the conclusion of the first run, either unplug the LAN cable from the HS or power the unit off. Status goes 'offline' and logbook shows this. Following the 4 min wait to abort the sequence, recable the HS or power it back on. HS Status updates, but Run Status and Instrument Status continue to show 'Offline'. Start a sequence, but it aborts. Instrument Status eventually updated to Ready following power cycle reconnection, but not the Run Status. Must close and reopen.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: 4 min wait to abort sequence following comm interrupt
Problem:
When there is a communication lost, like a lost LAN connection, it can take about four (4) minutes for the system to abort from the sequence due to the reconnects.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: MSD failed to reconnect after several disconnections/reconnections
Problem:
About 3 or 4 successful disconenctions/reconnections (by removing LAN cable from my PC). On the next reconnect, got an "in use by" message, with my computer name and IP address
Temporary Solution:
Try to reconnect a couple of times If this fails, close MassHunter Acquisition and start up the instrument control again If that fiails, close MassHutner Acquisition, power-cycle the MSD, wait 2 minutes, then restart MassHunter Acquisition.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Drug Quant: Copying of sequence table copies non-DQ sample types
Problem:
Build a sequence table in drug quant select some of the DQ specific sample types (eg specimen, blank), copy, paste into excel. The non-drug quant equivilants are pasted.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: In the MSD Tune Report, Profile and Scan windows have poor scale
Problem:
These windows are scaled to an arbitrary size instead of the actual area on the report in which they are to be plotted.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Capturing data via EDP, in the window for Capture the usec always has 0.00
Problem:
Runnning the EDP with Capture,the number of points from 1000 to 10000 but the usec in the display window always stays at 0.00. The capture information is correct.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Automated quant reporting with .m method files
Problem:
Create a quant method save as .m format & .quantmethod.xml format. In acquisition, use the method file as the DA method file. The .quantmethod.xml file generates the proper report the .m file generates the generic qual report
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: LCP Display Times do not match actual date. LCP has 2/14/2013 when date is 2/16/2013
Problem:
LCP Display Times do not match actual date. LCP has 2/14/2013 when date is 2/16/2013 instrument available states 2/14/2013 is the date, but when you go to manual tune it will display the correct date and then instrument available will come back with the wrong date. The LCP has a memory stack and is displaying the wrong line. There are no errors for the acquisition times because they all get the timestamp from the PC and this is correctly being implemented.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Printing "Detailed Data Analysis method" w/ no printer results in error in status line
Problem:
Trying to delete "Detailed Data Analysis Method" section of the method with no printer attached, the following error message will appear in the status line: "Cannot delete methods\methodname\damethodprint.txt The reason why it appears is that there is no file by that name.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: In Run Method Panel, estimated disk space is reported for D: and value is actually C: capacity
Problem:
When selecting Run Method, the estimated free disk space is identified. In MassHunter GCMS Acquisition, it is specified as the D:\ or the data path selected. If D:\ is selected, the free disk space that is actually reported is for the C:\ drive NOT the D:\ drive. If you change the data path to C:\ the same value is reported correctly for the C drive.
Temporary Solution:
User can go and user windows explorer to view the available free space on the selected drive.
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Vent/Pumpdown from Instrument Control, get error in status line about Vent Prepare
Problem:
Venting the MSD from the Vacuum Dialog, and then pumped down, without power cycling the instrument. After clicking Pump Down, the following error appeared: ERR.LUIVentPrep_Not_Active No bad behavior happens because of this, but the message does persist and could cause confusion.
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
SQ: Pause batch if calibration expired is not working with Intelligent Sequencing and classic DA
Problem:
Intelligent Sequence set to Pause batch if calibration expired. Set up a sequence with two specimens. Ran the sequence and got message that the current calibration is out of date, responded Yes to continue. When prompted, chose a Med Control. Instead of pausing the batch, it asked for a reinjection.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package
Keyword:
One-line Description:
SQ: Ramping in Emission for CI system runs in improper manner
Problem:
5977: MS firmware 15
Ramping in Emission for EI system runs properly; but
Ramping in Emission for CI system runs improperly, the ramping curve is almost a straight without maximum;
5975: MS firmware 7.02.17
Ramping in Emission for EI system: NOT tested;
Ramping in Emission for CI system runs improperly, the ramping curve is almost a straight without maximum;
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Running CI Tune Report Options prints blank reports after first tune
Problem:
In EI, you get a message that you need to run the tune twice to see the customized tune reports (lens value, etc). In CI, the blank plots are printed after the first tune and no indication is given its needs run again.
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
SQ: In Manual Tune, the Step Size Edit box on the Profile Tab erroneously controls the step size for Scans, not Profiles.
Problem:
To control the step size for profiles, use the CP CFommand "stepsize" before entering Manual Tune. For example
STEPSIZE .05
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Changes to Profile scan speed not persisting in Manual Tune
Problem:
Go to Profiles tab Make sure that speed N=3 is slected Click "Profile" to start running profiles Change speed to N=7 -- you will see profiles slow way down (correct) Click "Profiles" again You will see profiles being run at N=3 speed (this is incorrect)
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Non-responsive UI when stopping scans, profiles, captures and ramps in Manual Tune
Problem:
After you click the "Stop" button, UI is fairly dead until the operation completes. This can be maybe up to a minute or two for a wide scan at .05 step size, or especially a ramp with max number (~256) points.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Index 2000 out of bounds at the end of sequence run
Problem:
5977/7890B/7693 (Drug Mode) Ran 2002 line sequence, and when checking the software, the sequence status bar was still in "running" mode with 2002 out of 2002 lines run. The status line said "Index 2000 is out of bounds."
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package
Keyword:
One-line Description:
SQ: Safe Handle Message and Crash of MassHunter GCMS Acquisition during sequence run
Problem:
Running fastest method on a system over the weekend. System got through 408 runs (less than 24 hours). The MassHunter GCMS Acquisition aborted when okay was selected.
Temporary Solution:
Data handling was errantly set-up to "Screen Print" a library reports, which caused many instances of the MultiVu application to be invoked. Furthermore, Alert boxes were displayed warning the user of a near out of memory condition and a swap bound system. Warning messages were display, but if the user was not near the system when the error messages were being display then an abort of the sequence could result.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Help for keywords in Drug Mode
Problem:
There are a number of keywords in DrugMode that are not in the help; Append, BatchRep, NewBatch, ReQtStds, etc. There are also keywords listed that are not in Drug Mode.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Help inaccurate for keywork UseDecisions
Problem:
According to Help for keyword UseDecisions "UseDecision is only applicable for MassHunter Data Acquisition sending data to MassHunter Quant. When working with MassHunter Data Acquisition in Drug mode sending data to ChemStation Data Analysis use Intelligent Sequencing instead." This is not true. The user must set up the sequence with the UseDecisions keyword when using Classic Data Analysis also. The use of this keyword will invoke Intelligent Sequencing. There is no more turning Intelligent Sequencing on/off in the method.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Strange Hivac gauge reading when conducting commands on CI systems
Problem:
When conducting commands, strange HiVac gauge reading (such xxe-10, or xxe-09) appears on software and LCP occasionally. The chances of this error appearing depends upon the orders and time-gap between the consecutive operations.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: During Tune, got "MS Communication Errors" flashing on status line
Problem:
During the tuning on the line prompt an error message "MS Communication Errors", tune completes fine, then reconnect, "MSD was already connected" in status line.
Temporary Solution:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: AutoTune does not use a secure default mass profiles for the tune, it uses the user entered values from profiles
Problem:
If one changes the profile masses and saves the tune file, the tune file will then use those new profile masses for the tuning masses which could result in an abort or end of the autotune.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Calibrant valve status on autotune report are consistent between EI and CI
Problem:
On EI system, atune Autotune report, "PFTBA" is "Open"; On CI system for both PCI and NCI, autotune report, "PFDTD" is "Closed". When tune is completed the calibrant is turned off.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package
Keyword:
One-line Description:
SQ: Enter out of range mass errors for Target Masses, inconsistent error handling
Problem:
If a out of range mass is entered on the Target Mass dialog from Tune Wizard, an error prompt does not appear like the other Tune Wizard dialogs. The only way you know there is an issue is that the dialog closes and there is a message in the status line. From the other dialogs, you get a "parameter out of range" dialog and then are brought back into the offending dialog.
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
MSD: Warning messages about certain icons appear during uninstllation of Acquisition software
Problem:
During MassHunter GCMS Acquisition uninstallation, the instrument icons and “QTOF Conditioning” icon will be removed automatically; however, three icons for Configuration, STA and Parts Finder are not go away automatically until clicking “OK" on the message box. This does not occur all the time.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Missing help information about the right key functions for Capture window on screen and search
Problem:
Capture window right function keys are missing help information.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Missing help information about the right key functions for SimRAMP window on screen and search
Problem:
Missing help informaiton on the right key function on the SimRamp window.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Missing help information about the right key functions for SCAN window on screen and search
Problem:
Missing help information for the right key functions.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ, Missing help information about the right key functions for Profile window on screen and search
Problem:
Missing help information about the right key functions for Profile window on screen and search
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Missing help information about the right key functions for Text window on screen and search
Problem:
Missing help information when using right function keys.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: User needs to make sure Graphic windows have stopped acquiring data before switching views
Problem:
The user can right click on the graphic windows options (SCAN, Profile, SIMRamp, Capture) to perform a single or continously acquisition. This is very important for troubleshooting and optimizing a tune. Before switchin the view (from instrument control to tune and vacuum control or the reverse) the user needs to make sure the acquisition has stopped. There is an MSOFF command which is implemented during the switching of the views and this could disrupt the software by creating a fault.
Temporary Solution:
The user will need to select stop acquisition prior to switching the view.
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Tune Error on bfb_autotune, extra dialog saying "Starting Autotune", but nothing happens
Problem:
Ran a bfb_atune on 5977 and a Tune Failure Message appeared: "Couldn't achieve ion Focus. Check Calibrant and lens connections." Hit Ok. But another dialog appears saying, "Starting Autotune". Hit Ok. The MS is turned off (status line), but nothing happens. Software is not frozen, can move between screens, etc. This could leave the user wondering why their autotune isn't running. Is it supposed to run? Or is there just an extra dialog? The second dialog box should not have appeared.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: .Net Exception When Clicking in the SIM Time Segments Table
Problem:
5975 Method Ediror panel: The SIM Time Segments table is difficult to manipulate if you are not used to it - different from G1701EA, Clicking around trying to get the time field to become editable, one can get a .net exception. After selecting Continue on the excption, ok and cancel were no longer functional, but one can close the panel from the X. Reopening the panel, it was fine.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Timed Events, EMVolts Monitor for Gain Factor does not match EMVolts specified on TIC
Problem:
Timed events for Gain Factor. When the method runs the TIC Shows the events labled with EMVolts 1103 and EMVolts 969, but during the timed events, the monitor showed 1106 and 965. All other events like Absolute EMV and Delta EMV had matching voltages.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: GC MS Acquisition IQ fails after FA uninstall
Problem:
After uninstalling MassHunter GCMS Acq, an IQ test was run. It fails with 1 file missing in GC MS acquisition.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: DrugQuant: Help Button on Post Batch Report Panel Not Working
Problem:
When you select the Help button on the Post Batch Report panel nothing happens.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: DrugQuant: Canceling the Save Batch Panel Causes Undefined symbol when Selecting Simulate Batch
Problem:
Testing the menu items by opening and canceling them. If one selects Save Batch and then cancel the panel, then going to Simulate Batch undefined symbol: pauseseq. This will occur when selecting either the menu item or the icon.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: No Cancel button on Method Resolution panel when loading the method
Problem:
Have a valid method loaded in Drug Mode, ran a simulted batch. Then attempted to load another method that brought up Method Resolution. The method resolution panel had no Cancel button . This does not occur all the time.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: No way of stopping sequence while waiting for an interval
Problem:
Setup a sequence using the interval keyword. First sample ran and then "Waiting for interval xxx" appeared on message line. During this time while the software is waiting the specified interval time before starting the next run, the stop button is grayed and there is no way to stop the sequence.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Shortcut Error Uninstalling MassHunter GCMS Acq from a Clean System
Problem:
When uninstalling MassHunter GCMS Acq from a clean system (nothing else was installed with MassHunter GCMS Acq), an error that says shortcuts could not be removed. The uninstall continues, but one is left with the extra icons that install with MassHunter GCMS Acq like Parts Finder.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Front Only inlet is available after configuring Headspace, though both inlets are available up to that point
Problem:
A GC with dual 7693's, no tray. Both GC ALS inlet sources are available. Create a Back ALS method. Close and configure with a headspace. Open session and both inlets are still seen. Create a front HS injection source method. Reload the Back ALS method. Select inlet/injection source and only the Front Inlet is available, though both ALS's are seen in ALSL and Configuration. Saw this on multiple GC's with different types of HS. The only way to escape is to deconfigure the headspace.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: No way to confirm import of method component(s) imported prior to save
Problem:
B.07.00. with Qual and Quant installed to activate 'Import method components from another method'. Select this and for any element, there is only a Save As dialog presented. User should be able to verify the display of whatever he imported before he is required to Save the method. The only time user sees the Method Edit dialog is if the import invokes Method Resolution.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Clicking "Cancel" button on "Printing" panel doesn't work and hangs the process if "XPS" is set as default printer
Problem:
1. Set XPS as default printer; 2. After tune is completed, TWO panels appears: “Printing” and “Save the file as”; 3. click “Cancel” button on “Printing” panel, nothing happens and it hangs in “Canceling Print” forever until user clicks “Cancel” button on “Save the file as” panel again. The problem is: during tuning, user may perform others operations, the panel “Save the file as” may hide behind tune panel and invisible for user; so user has no way to continue anything unless kill the application.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: PC fails to reconnect to MSD
Problem:
If the PC leaves the MSD in a "BUSY" state, the PC and the MSD are supposed to be able to reconnect. The MSD accomplishes this by telling the PC this by who it is in use by telling MassHunter GCMS Acq who it is "BUSY" with
If it is the PC running, then MassHunter GCMS Acq can try to reconnect
If it is another PC, then MassHunter GCMS Acq can tell the user who the MSD is in use by.
Unfortunately, when the MSD is reporting who it is in use by, it is clipping the computer name
Instead of reporting: "5CB20404CM.scs.agilent.com", it reports "5CB20904.scs.agi". This in turn cause MassHunter GCMS Acq to *NOT* try to reconnect and to erroneously show an "In use by 5CB20904.scs.agi" message.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: CI Reagent Gas B and Load Method yields undefined symbol : line
Problem:
use the CI tune wizard to specify reagent gas on Line B. Save the tune file. Switch to Acqview and specify that Line B tune file is to be used with the mehtod. You will get an undeifined symbol: Line.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Message in logbook with sequence calling a GC Wakeup
Problem:
GC/MS was asleep. Setup a sequence with keyword GC Wakeup as the first line followed by two samples. Ran the sequence. The sequence completed but when looking into the logbook, this was the last line. Time Stamp Source Message 2013/03/11 14:27:35 Sequence has not be reloaded because instrument is sleeping Sequence did complete but the logbook would indicate that it was not done.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Click on Ramp window, value is not saved in tune file
Problem:
A manual click on a ramp window should save that value into the tune file in memory. Which, in turn, may be persisted on disk.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Sequence hangs waiting for arm signal - intermittent
Problem:
The MS Status panel was displaying " Arming instrument for start of run" on occasions. The 1st sequence stalled at 22:30:03. The 7890B entered sleep mode at 5:25:17 during the next morning. The sequence was aborted at 10:11:38. Normally, the sequence would resume running at the next sample, but this sequence got stuck in pre-run for the next sample. The GC stayed asleep, despite our effort to wake it up through the command line. The red STOP sign was grayed out, so one had to use Task Manager to kill the msinsctl.exe program. This time the 7890B had not entered sleep mode. Both the GC and the MS status icons were green and the CTC was displaying blue for Running. Was able to abort the run and resume the sequence at 15:08:22 on Sunday afternoon. Then the sequence of 303 runs ran to completion.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Still possible to see HIVAC Pump not ready when running sequence after GC/MS asleep
Problem:
When running a sequence after the GC/MS had been asleep, it is still possible for the sequence to error out with the following error : MSD Fault -- 0X0000000000000080 HIVAC Pump Not Ready ----. It may depend on your sleep and wake methods. For most cases, the steps work, but on occasions it might fail.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
QQQ: Check "All peak Data in one file" only in Log Files section but no any log file has been created after autotune of QQQ
Problem:
1. Check "All peak Data in one file" only in Log Files section, do NOT check other checkboxes; 2. Run autotune; 3. No any log file has been created after autotune (expect that one relatively large peak_xxxx.txt file should be generated)
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: SIM/SCAN: data collected from first SIM group only
Problem:
Build a method in SIM/SCAN. Add multiple sim groups with different SIM ions in each group. Data is only collected for the SIM ions from the first group for the duration of the run. This also applies to data being collected from SCAN from the first group for the duration of the run.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: Depending upon when override solvent delay is selected, either a slow response or lockup could occur.
Problem:
The issue is when the override solvent delay is selected prior to the solvent delay. The closer the override solvent delay is selected to the solvent delay there is an issue possibility of a run time delay being shown in instrument control or there could be a lockup of the system.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
SQ: 7890B vent method will be terminated during venting if switch masshunter view from "Tune and vacuum control" to "instrument" control
Problem:
7890B-5977A Vent the system from Masshunter a vent method will be loaded to 7890B.However if swtich the view to "instrument control" view the vent method will be terminated and transfer line teperature will increace following the previous GC method. And 7890B FRONT PANEL IS STILL BE LOCKED IN VENT STATUS. That' means you can't modify the setting value from front panel e.g. transfer line temperature can't be turned off. The only way is change the settign from Masshunger then load it to GC.
Temporary Solution:
n/a
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
MSD: The compliance for Masshunter GC ACQ does not have an IQT reference file and is not listed as add-on
Problem:
The compliance for MassHunter GC ACQ does not have an IQT reference file and is not listed as add-on. Only the registry entry is set and no file is installed as a reference file cannot be created.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ, Cannot enter the serial number of the MSD 5977A which is US1301L001 into the 7890B Aux Detector
Problem:
When you use the GC Panel and try to enter the serial number it will only allow numbers, the serial numbers for our MSDs has numbers and letters in it so it is not possible to enter in any 5977 serial number into the field.
Temporary Solution:
Instead of entering a Letter for the MSD serial number use a number like 0 or 1 for the letter.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: The turning on theSleep and Awake does not operate consistently when repeated
Problem:
When instrument control is started, sleep from the pulldown menu item is activated both the GC and MS go to sleep immediately, and then when you click on awake they both will come up. Without exiting instrument control, start the sleep mode again from the pulldown menu item the GC is activated immediately but the MS is not, it will take at least 2 minutes before it will detect the signal and display sleep but it may or may not start the powerdown of the turbo pump, this part is questionable at times also.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Why after clicking on Awake, why does the vacuum readings improve by almost 2 orders, this is not correct.
Problem:
The instrument is around e-6 for the vacuum and then when the awake is used the vacuum readings go to e-8 and then it will go back down to e-6, what makes this even stranger is that the system is also doing a pumpout at this point of time.
Temporary Solution:
What the user is seeing is the gauge was turned off and it was causing the values to get lower and then it was turned back on and it was recovering. This is the normal response for the system.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ,QTOF: "restart paused sequence" menu item missing for QQQ/QTOF/GC only
Problem:
The Menu item: Sequence\restart paused sequence should be visible for all instruments, not just MSD as it is currently. This menu item is normally grayed, but visible for the MSD, and only becomes enabled if you have paused a sequence. behavior should be the same for the other instruments. For the GC only (as an example), the only way to restart a paused sequence currently is to "Run Sequence" and then you are prompted to resume at the specified line. From ken: The ‘restart paused sequence’ does appear to be for a single quad configuration ONLY; I view this as a defect. Should be active for all instrumentation (QQQ, QTOF, GC only)
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
MSD: Add Zipcrit and Problem Steps Recorder items for all instruments (QQQ, QTOF, GC only)
Problem:
The Zipcrit and Problem Steps Recorder menu items and feature are only present for MSD configurations only.
Temporary Solution:
Testing "Gather diagnostic files" on two QTOF systems, System A with MSD Data Analysis software installed, while System B not (for QTOF users, it is normal). After clicking "Gather diagnostic files" and selecting certain options, a log file is created with extension .z in System A, while a file with extension .gz is generated in System B. The file with .z can be opened in System A without software from third party, while the file with extension .gz cannot be opened until a certain software from third party is installed.
Fix Information:
Has been resolved in the MassHunter GCMS Acquisition B.07.00 SP1
Keyword:
One-line Description:
QQQ, QTOF: Vacuum ICON on instrument control does not work
Problem:
This was a feature which was added for the 5977 instrument and it is part of all of the configurations now. Does not function for either of the QQQ or the QTOF
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
EMF Monitor is no longer available.
Problem:
This ICON has been removed from all MS Types and the pull down menu item under Instrument call EMF has also been removed. The 7890B has DComm between the GC and MSD which means we now have the capability of the GC storing maintenance items. The first product with this feature is the 5977 and as we expand the functionality and update firmware on other MS Types we will be adding this new feature.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: instrument control, profile, continuous, then switch view to tune and vacuum
Problem:
the profile scan was going continuously in instrumnent colntrol then I clicked on view to go to the tune and vacuum view. When it was done, I could see Welcome to Tune at the bottom of the screen and the profile has stopped. I right click on the profile window and it stated that I had to do a profile stop but it was already stopped. Had to type in MSOFF on the commandline to recove, or just click on profile stop.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: MSD I/O Time Out when running N=6 and N=7 scan speed methods
Problem:
Running methods on a 5975 with the following parameters: Scan Only, mass range 50-650, N=6 or N=7 (methods attached). Using B.07.00 shipping 5975 firmware. System Times out and the MSD goes offline. The first time it happens, reconnect to the MSD using the Menu Item and run a different method. If run the N=6 and N=7 methods again, the system times out again. unable to Reconnect to the MS via the menu item. Close and restart GCMS, unhandledexception.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: Truncation: Q-TOF Short Report, Tune file name is truncated
Problem:
Create Q-tof Short report. Tune file is truncated.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: CI Tune from Sleep mode produces MSDAT Exception and doesn't tune correctly
Problem:
With a good tune loaded, I put the system to sleep. While the instrument is sleeping, I initiated the tune MSD (menu item or icon). Window switches to CI Tune and Vacuum Control window as expected, and system is still asleep. Click CI Autotune (system wakes up) and CI Autotune does not begin until the GC and MSD are ready (all good). However, the tune that proceeds produces the attached error (tunefromsleep.png). The profile continues after I hit ok most of the time, but I have had it crash bronco once, and I get the dialogs about purging the CI gas line. A telnet log is attached. The tune never seems to get back on track. If I abort, and then just do a normal CI Autotune, using the same tune file, it proceeds without issue
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Can not enter over 10mins to Solvent Delay in MS Method Editor
Problem:
Load Default method Change Oven program to 15mins in GC Method Editor Go to MS Method Editor Try to change Solvent Delay to 12mins. But change to 10 mins automatically when the cursor move to the another field.
Temporary Solution:
Go to the Inlet and Injection Parameter menu and change Sample Inlet to Other/None Go to the MS Method Editor and now increase the amount of time for Run Time, this parameter is setting the maximum limit for the Solvent Delay when Sample Inlet is selected as GC. Go to the Inlet and Injection Parameter menu and change Sample Inlet to GC Go to the MS Method Editor and now increase the amount of time for Solvent Delay
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: GC Does Not Go Completely Out of Safe Mode After Download Method to GC is Selected
Problem:
5975/7890A system was in safe mode. In GC Edit Parameters some changes were made (changed oven temp, turned off some inlet pressures and flows). Right -clicked and selected Download Method to GC. The changes were downloaded, and the actuals should the parameters changing. Then changed the parameters again, and select Ok on the Edit GC Parameters panel, but the set points did not change.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: "Zip/Unzip methods and data" depends on character case of filename extension
Problem:
the function of "Zip/Unzip methods and data" depends on character case of filename extension: "Zip" is not case sensitive for filename extension, while "Unzip" works only for capital case in filename extension.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: Title of tune report different depending on how it is generated
Problem:
tune and vacuum control menu with stune.u loaded, select Tune MS. Tune report title will be Target Tune. tune and vacuum control menu, select Standard Spectra tune (stune.u). Tune report title will be Standard Spectra Target Tune In sequence, run a Check Tune. Tune report title will be Tune Report.
Temporary Solution:
When you select a menu item like Standard Spectrum Tune, the macros know exactly what you are doing and label the report accordingly. However, if you save STUNE.U as MAS.U, the macros cannot distinquish whether the file was originally an Stune, BFB, or DFTPP tune. Similarly, you could save the files as BFB.U even though it is an Standard Spectrum Tune.
Fix Information:
n/a
Keyword:
One-line Description:
SQ: unhandled exception with no printers configured and tune report options selected
Problem:
Setup a computer with NO printers configured. In the Tune and Vacuum COntrol View, Select File\Set View Tunes Report Options, Select all of the options to be displayed. Run Tune (may have to run 2x to generate the TunePlots. After the tune is complete, an unhandled exception occurs. If you hit continue, the tuneplots show correctly, and there doesn't seem to be any damage to the system from the exception. Running a tune with none of the tune report options select is ok and does not result in the exception.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: check "Graphic Repots" check box, the subcheck boxed does not check by default
Problem:
tune and vacum view--> file menu--.> set view tunes report options check graphic reports, the sub checik boxes does not checked by default.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ, Sequnece Table should have "Critical columns" as default.
Problem:
1. Run Sequence as default Sequncetable column setting.
2. A message is always shown.
Critical columns contain data and are hidden:
method Path
Temporary Solution:
If the critical columns are show in the main view then the prompt will not be displayed. The prompt is just to inform the user there is some key items being hidden via the columns not being shown.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Fixed Electron energy is printed as 2 eV when printing the method
Problem:
Fixed Electron energy is printed as 2 eV when printing the method instead of the correct 70 eV which are used.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: change the spectrum name in spectrum manager, the monitor name did not changed as setting
Problem:
In the spectrum window, right click to the spectrum manager, change the display name from spectrum to something else, click ok, check the title of spectrum signal monitor, it did not change accordingly.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Unable to copy partial rows from Excel to SIM Table
Problem:
In the SIM Ion Tab, there are three columns. In order to successfully copy from Excel, the user needs to have all three columns defined in Excel. For instance, you cannot copy just the SIM Ion and Dwell Time, you also need to specify True or False for the Plot this ion.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Copy/Paste from Excel into SIM Table, any subsequent copy/paste from within in Method Editor will paste Excel values
Problem:
copied and pasted a group of values into the SIM Table. If copying a different set of SIM values from within the Method Editor and try to paste, the values that are pasted are those that are copied from Excel. After a copy/paste from excel, it seems that the Method Editor loses its copy/paste functionality.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Unhandled Exception when switch to SIM Time after Copy from SIM Table`
Problem:
Copy and Paste SIM rows from Excel into SIM Table (60 SIM Ions). SIM Ion Table is correct and there are no errors. Copy a partial group of the SIM Ions (complete rows, but only 10 or so ions). Go to SIM Time Segment line (empty and click as if to add a new time segment. Unhandled Exception occurs. Particularly bad because it does not go away after you hit Continue. Exception keeps appearing and then one may be forced to ctrl-alt-del the application since it was unusable.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: spectrum manager, the default colour is not working
Problem:
spectrum manager, right click the display name field, then select colour, change the colour, ok the panel. go back to the manager panel, check the display neme colour is applied. click default colours, ok it, go back to check the colors, it did not go back to the default.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
QQQ: the default label for chromatogram type should be the same with chromatogram type.
Problem:
instrument menu/MS parameters, click chromatogram tab. select the chromatogram type, the labels are always TIC even though the selection was BPC or EIC.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Help for Chromatogram Manager is missing Event Options description and Default color
Problem:
If you right click on the chromatogram, there is a dialog that appears. The help button brings up the "chromatogram manager" help as expected. However, the Event Options and Default Color items in the dialog are not explained.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Hitting Vent then Pumpdown on system with DCOMM enabled
Problem:
On a 5977-7890B system with DCOMM enabled, set up a GC Vent method. From the Vacuum control window, selected Vent. This activated the Vent Method on the GC. After a minute or two select Pump down. The Mass Spec went into Pump down and became ready. The GC temps were still falling according to the Vent Method
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: when you perform a check tune in QQQ, ion ratio for mid and high masses are wrong
Problem:
when you perform a check tune in QQQ, ion ratio for mid and high masses are wrong, they result to be exactly the half, compared to the values in the aTune. If you look at the "raw" data file in the txt file inside the checktune report folder, the values are acquired correctly. It look like when the system compile the report, the process do a wrong calculation: only "Ratio of mid mass to low mass" and "Ratio of high mass to low mass" are the half of what they really are in the aTune..
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Starting up MS that is in use by another PC
Problem:
MS was in use on one PC and trying to start up the instrument on a different PC. One can correctly see the message that Instrument is in use by host name. The instrument status showed offline. Nothing was recorded in the logbook such as when the GC is offline. Also, one is able to go into tune and initiate a tune.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: MSD wakes up on start-up even if you say no
Problem:
If you have the SYstem asleep, then close MassHunter Acquisition. When you restart MassHunter Acquisition, one is told that the system is asleep and would you like to wake it up? If you click No, the GC stays asleep, but the MSD spins up the turbo and becomes awake.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: No indication that in SafeMode
Problem:
When the system is placed in SafeMode and if you close the Vacuum Dialog while venting or vented, there is no indication one is in safe mode.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Run Method will begin even when Turbo not at 100% after waking up
Problem:
This seems to be vary by instrument. Set the instrument to sleep. While System is sleeping, run method. System will get all the commands to wakeup. Logbook and LCP all say, AWAKE or Ready. So according to the Run Method Panel appears and the user can run a method. However, the turbo pump speed on the LCP and on the Monitor are not at 100% or above the ok threshold. On one system, it was 40% (the turbo seems to spin down before spinning back up to 100%). If there is a lengthy Pre-run, this is fine since the pump comes up to speed fairly quickly. However, you might get a case where there is no pre-run and the run method begins with a less than spun up turbo.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Actions executed under Executed tab on Tune and Vacuum view are not consistent on Calibrant valve status
Problem:
On Tune and Vacuum view, under tab Execute, the status of CI Calibrant with the following actions seem not consistent: "Ramp Lenses": MS turns on automatically, CI Calibrants valve opens automatically after the button was clicked; "Profile scan": MS turns on automatically, but CI Calibrants valve doesn't open automatically after the button was clicked; "Spectrum scan": MS turns on automatically, but CI Calibrants valve doesn't open automatically after the button was clicked; "Find mass": MS turns on automatically, but CI Calibrants valve doesn't open automatically after the button was clicked;
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: MSD produces Faults when wake up during a conditioning run
Problem:
System is scheduled to wake up after a conditioning run. GC goes into conditioning run. From Menu item, select Wake. The MSD wakes up and the turbo spins up. There is a HiVacFault Registered and a HED Fault registered. Meanwhile, the GC stays in its conditioning run. If I hit Wake again, I get a message saying that the system can't be run in conditioning state and the "falloff" message is displayed in the status line. If I stop the conditioning run from the front panel, the system becomes alive again.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Run Method in offline mode, get "undefined symbol: wait for CIPI ready"
Problem:
While a simultaneous online system is running, startup up offline system. Green arrow is active, pressing the green arrow; the system went through the motions of trying to start a run, but getting a Run Method Error. Was expecting, "Offline" or something, but instead got "undefined symbol, wait for CIPIready"
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ, While in Vacuum Control, reconnect network cable of MSD, MSD remained offline while Instrument Status is Ready.
Problem:
While in Vacuum Control, 1. unplug network cable of MSD. Actuals show Offline in Vacuum Control panel while Instrument Status is Ready. 2. Reconnect network cable of MSD. Actuals still remain Offline and Instrument Status is Ready. 3. In addition, if click "Close", messages popped up indicated "MSD is offline. If exit out of the Vacuum Dialog, GC/MS Acq will terminate. "
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Fast Vent Text on display when GC is in vent mode
Problem:
GC mode of GC monitor display is “Fastven” during MSD vent cycle. I think this is “Fast Vent”.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Help/Using Help In Tune and Vacuum Control View Does Nothing
Problem:
In Tune and Vacuum Control view, selecting Help/Using Help. Nothing happens. No help opens.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Create EI Tune File for CI Source Not Working
Problem:
For a 5975CI instrument, go to tune an d vacuum control. Load a CI tune file and go to Tune/Create EI Tune File for CI Source. The status line said, "Could not open file D:\MassHunter\msexe\EI-CISource.mac.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Simulate sequence does not flag duplicate filenames, that is only done when exiting sequence table
Problem:
If you setup a sequence that has duplicate filenames, you will be warned on exiting the table as asked if you would still like to continue. Respond Yes. Then Simulated the sequence and it did not flag the duplicate filename but when the sequence is run and overwrite data file is not checked, the sequence will error out on the line with the duplicate filename.
Temporary Solution:
Simulate Sequence checks to see if the syntax is correct, the method names and paths are correct.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: Error when try to open Logbook after it has been cleared
Problem:
With the Logbook open, select File\Clear. The contents of the logbook is cleared. Close dialog, Click on logbook again, get an error saying cannot find mslogbk.html. Click OK. The blank book opens.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
QQQ: Log files have not been generated in QQQ autotune in case that the check boxes of log files are selected
Problem:
On QQQ autotune, select all check boxes (Log File, Ramp Data, Capture data, Spectra Data, Log 15 sets of peak data per file) of Log Files under panel of Files and Reports. After autotune is completed, tune report has been generated, but no any log was created.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: transfer line temp show wrong on tune report of 7820-5975
Problem:
config 7820-5975 run autotune, the transfer line temp showes wrong. when tune 7890-5975 or 7810-5975 (5975T), this issue did not happened.
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: MS Instrument Control and Tune has been stopped working after vent cycle is finished
Problem:
Hardware configuration is 7890A+5975MSD+G7697A HeadSpace After vent cycle is finished, the message displayed. is "MS Instrument Control and Tune has been stopped working".
Temporary Solution:
n/a
Fix Information:
NOTE: Has been resolved in MassHunter GCMS Acquisition B.07.00 SP2
Keyword:
One-line Description:
SQ: Remote Access to unit, running the Sequence with Tune only, MSINSCTRL.EXE GPFs
Problem:
Running a system via a Remote Access with Tune only in the sequence error when the Remote Access to the system is terminated.
Temporary Solution:
Wait until the tune is completed before closing the Remote Access Connection, this includes timeouts/screensavers to the system also.
Fix Information:
n/a
Keyword:
One-line Description:
MSD, show_ipinfo.txt does not include HS
Problem:
Select Help\Show IP and Revision Information... The G1888 info is not included.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ, Run stops with excessive foreline pressure during solvent delay
Problem:
A customer is trying to run a locked method in constant pressure mode which is causing the system to start the run with an initial column flow of approx. 2.3 ml/min (inlet pressure 21.4 psi) which is above the recommend flow rate for the diffusion pump system. The system is also running large volume injections which is going to increase the amount of solvent pump out at the initial part of the run. Depending upon the system condition (foreline pump condition, last time PM has been done for the foreline pump oil, etc) the foreline pressure could reach 100 mTorr which will trip the excessive foreline pressure error. Typically, on new and well maintained systems we would see foreline pressures around 350 mTorr.
Temporary Solution:
Some applications which could run on a Turbo pump system may not run on Diffusion pump systems. Modifications/Preventive Maintenance/Updates may be required to the system to make it perform.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ, 5977 with extractor lens and tuned using ETUNE, the Tune Evaluation is done by MH using ATUNE instead
Problem:
If a unit has an extractor source the user can selected multiple types of autotunes to be done: etune, atune, bfb tune, dftpp tune, stune, and targert tune. The MassHunter GCMS Acquisition software will perform the tune evaluation based upon the atune criteria. So there could be some errors being reported from the tune evaluation report while there are no real issues because the system could be evaluated using a different type of tune while using the autotune criterias.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ-QTOF, "Use MS" not selected: QQQ/QTOF say offline and MS parameters still active
Problem:
If the user unselects the "Use MS" checkbox in the Injector parameters panel, the MS icons should all be greyed out. For QQQ and QTOF, this is not the case. Also the Instrument Status says OFFLINE, which is misleading since the GC is online and happy, as is the MS. We are just saying don't use the MS. It is still possible to run a method like this, it is just confusing. In the SQ case, all the MS icons are greyed out and the Instrument Status still says Ready.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ, air/water check report title needs to be updated
Problem:
MassHunter GCMS Acquisition Air and Water Check gives a generic title of 597x for the air/water check for the 5977. The 597x does not really represent just the 5977 series, the 597x actually represents the full single quad line which has been made. The title of the report should be updatedc to 5977 air/water check.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ, SIM/SCAN data files do not have the same number of records.
Problem:
For SIM/SCAN acquisition, firmware is supposed to alternate between SIM cycles and Scan cyles. The resultant data.ms and datasim.ms should have the same number of records, +/- one record. Some of transitions between time events is being counted as a record event which is causing a mismatch number of SIM/Scan record numbers.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD, In a GC-MS Manual Injection the Start Run panel behavior is inconsistent if the MS is configured as connected to the rear injector
Problem:
In a GC-MS system with the MS physically connected to the rear injector, the automatic injection mode runs fine. If you switch to Manual injection mode, without reconfiguring the MS connection, the Start Run panel only allows you to enter the sample info on the left hand side of the panel (normally, labelled front). The sample info on the right hand side of the panel (normally, labelled rear) is grayed out. Once the Start Run dialog box closes, a message box pops up asking if you want to overwrite the data file last used for the rear injection. It appears that the method is run with the sample info from the right hand side of the dialog box that was grayed out. The info that was entered on the enabled side is not being used. This is inconsistent behavior between the Start Run panel and the run method macro.
Temporary Solution:
In the Inlet/Injection dialog box, if you change the MS to be connected to the front injector, the behavior will be correct. This is not intuitive, because the hardware has not been changed. The MS is still connected to the rear injector.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ, Error message when specifying sandwich keyword but no keyword string
Problem:
Set up a 3 layer sandwich injection sequence. Specified the 3 Layer L2;L3 keyword but did not enter a keyword string. Received the following message "Alert "you must use the ' ; ' character to separate L2 from L3. Edit Sequence Table?" Message should be keyword string should not be blank.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ, Tune - Dynamic ramp geometric mean = undefined
Problem:
Autotune dynamically ramped lenses sometimes show geometric mean as undefined even after the previous mean was ok.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package
Keyword:
One-line Description:
MSD, Sequence process keywords prompt delayed
Problem:
When using sequence position and run feature, the user is prompted for whether or not to process keywords. The problem is that this prompt is delayed 2-5 seconds. On multiple occurrences, the user could have walked away thinking the sequence has started and to come back to find out the sequence just sat there.
Temporary Solution:
Wait until the first sequence line has started.
Fix Information:
This has been fixed with B.07.01 released software package
Keyword:
One-line Description:
QTOF, warning message for incorrectly selected time segment while using target MS/MS table
Problem:
When user has multiple time segments and also using target MS/MS table, there is no warning or prompt to indicate to the user the time window entered into MS/MS table is outside of the selected time segment.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ, Titles and contents are not aligned in Revision History.
Problem:
While running MS Configure, it could be awkward reading the Help/Review Revision History because the Titles and contents are not aligned. Information provided is correct and valid.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ, GC Signals Continue to Plot After method is finished.
Problem:
In GC Real Time Plots (RTP), four GC signals were selected to be displayed and saved however the continuous checkbox was not selected. All four signals collected in the RTP during the run and were supposed to stop at the end of the run. The RTP still shows the signals drawing even after the run is completed.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ, No error displays if Time event of MS On is shorter than Solvent Delay
Problem:
On MS Method Editor, set Time event of MS On shorter than Solvent Delay, an error sign and relevant message should appear, but no message or prompt appears even if "Apply" or "OK" button was clicked.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ, Methane Flow Adjust happens twice
Problem:
In the tune view, if one loads a CI tune file, the Methane Flow Setup occurs. After the Methane Flow setup occurs, the user is asked if they would like to run CI Autotune. Click Yes. The system then proceeds to do another methane flow adjust before beginning the autotune. Just a duplicate step, no changes in the results.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ never emits VacSysFail when running, so GC never goes into MS Shutdown mode when fault is triggered
Problem:
Turbo pump spins down to 1 % and MassHunter Acquisition emits a message: MS Fault Detected: 2.8 High Vacuum gauge is reading too high a pressure The MS never sends the "VacSysFail" message, so the GC never goes into shutdown. (waited at least 15 minutes after the turbo pump was at 1%) If you then start everything back up, the first message that is given is that the "Vacuum system is not ready". This sends the GC into shutdown mode.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ MS monitor; Reset Default reset to setting for SQ
Problem:
1. Config QQQ 2. start Inst#1, 3. Instruemnt > Edit Monitor 4. Reset default Selected monitors are reset as Single Quad monitor instead of QQQ selected monitor
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ, MS mthod Editor; Run time = 999.9 is not acceptable
Problem:
on QQQ MS Method Editor, Input Run time = 999.9. An eror message is shown. but it says, 0.1-999.9 is valid range. 999.8 is accepted.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ, Can not import scan segment becasue of garbage
Problem:
1. config QQQ,
2. Go to Method Editor,
3. Import CSV file to Scan segment,
Excel-csv-02.csv; created by Excel 2013
4. When import Excel-csv-02.csv, the header title can not recognized because of Garbage (Ansi format)
Temporary Solution:
1. Open Excel-csv-02.csv by NotePad 2. Change character code = UTF8 3. Save it (the attacehd UTF8-Excel-csv-02.csv) 4. UTF8 file can be load
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
QQQ, dynamic ramp panel, mass and value pair cannot be deleted
Problem:
go to manual tune panel, ion source tab click ion focus box, dynamic ramp part will be active. check enable checkbox and input some mass and value. try to delete one pair, it was impossible. when one cell value was deleted an excalmatory mark will display besides the cell.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ, Random Tune & Vac Control Actions Gray out MSD Icons
Problem:
This has occured a couple of times when, all the MSD icons gray out event though the MSD is still online and the menu items are active. The first time this happened was when some changes were made to the MSD Temps and saved the tune file to a new name and then reloaded the tune file. The second time was in Tune and Vac View, selecting various menu items. When switched back to Instrument Control View, they were grayed. See attached screen capture.
Temporary Solution:
You have to shutdown and restart to get your icons back.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ, 5977, MSD Temperature fluctuates by 20 - 50 degrees
Problem:
Powered cycled a CI system and applied new tune file temps (300 source, 150 quad) to it. During the ramping up process as the source temp approached and reached 300, the actual temp reported was jumping around by 20 to 30 degrees every time it was queried (about once / second). This does not occur all the time.
Temporary Solution:
Power cycle and/or reload the temperatures corrected this issue.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ, During Load Method, 7890Method.bin gets renamed in a MS-only configuration
Problem:
When loading a GC-MS method which includes the 7890 on a MS-only configuration, the 7890Method.bin file gets silently renamed to 7890Method.mth. Even without saving the method, the file name is. Later, when loading the same method on a GC-MS configuration, a new 7890Method.bin was created. The settings were not identical to the original 7890Method.bin.
Temporary Solution:
Generally, this is used for MS only for troubleshooting.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QTOF, Sequence hanging CTC system may be caused by long method name
Problem:
Sequence cannot start (stays in PreRun), although all related icons and windows are in green; no any warnings, no any message or sign. It is difficult to figure out the causes. The method name is xxxxxxx.m (38 characters prior to .m, only one dot). Have tried a short method name (e.g. Test1.m), this error doesn't occur.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ, 5977 print tune report has font issue
Problem:
config 5977 and run tune, except auto tune print report, other print tune report have font issues (larger font size with crowded characters in MS parameters section).
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
MSD, Problem running dual with sandwich injection
Problem:
Created a dual method where both the front and rear specified a 2 level sandwich injection. Set up the sequence appropriately. Place the L2 vial specified in the sequence in the front turret. The back turret will just use the vial that is already in the L2 slot of the turret. Now however, it placed the L2 vial specified in the sequence in the front turret and then tries to go back and place the same vial in the back turret. Of course it doesn't find it and no injection is made. It aborts or skips.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD, when in flow mode, incorrect RTLPressure recorded in pre_post.ini
Problem:
MSD, when in flow mode, incorrect RTLPressure recorded in pre_post.ini should really update acqlock.mac so both the recorded flow AND pressure are correct.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package
Keyword:
One-line Description:
SQ, Run Sequence from sleep produces HiVac fault
Problem:
If one is running in drug mode, and then start a run sequence while the system is sleeping, it couldl produce a hi vac fault and the sequence will not start.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ, Tune from sleep: "cannot assign or remove reserved variable: _sleep mode"
Problem:
Trying to tune from sleep (CI). The system goes into Tune and vacuum control view, but doesn't wake up anymore when you click CI Autotune. "cannot assign or remove reserved variable: _sleep mode"
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD, Uninstalling SP2 will corrupt B.07.00
Problem:
Unistalling the B.07.00 SP2 will corrupt the B.07.00 which is left on the system if you try to run it by itself. You cannot reinstall the B.07.00 SP1 so you will need uninstall the B.07.00 and then reload whole system.
Temporary Solution:
When uninstalling any service packs, uninstall the complete package and then reinstall.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ - When changing from a CI source to an EI source, the software should force pumping out of the reagent gas
Problem:
When the user configures a new ion source and the previous source was CI, there should be a check in the software to determine if the reagent gas needed to be pumped out. Another side effect of not pumping out the gas from the software side is that there may be inconsistent status messages displayed on the MS Status Panel. The Method Status message may indicate that the method has been applied, but the Ion Source status message will say the method has not been downloaded to the instrument. Going through the software to pump out the gas would put everything back in sync..
Temporary Solution:
When venting, the firmware will turn off the gas. But it is good practice to pump out the gas lines so that residual gas is not trapped in the line after the flow is turned off and the isolation valve is closed.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QQQ, After editing a QQQ method, some changes may not take effect when running the method
Problem:
There is a defect in the QQQ acquisition code that causes it to use some of the previous method settings after the method is edited. The affected method settings are Stop time, tune file, time segment settings, and acquisition settings.
Temporary Solution:
The workaround is to save the method and then reload the method from the disk. After reloading the method, the software will have all the correct settings.
Fix Information:
This has been resolved in released version MassHunter GCMS Acquisition B.07.01.
Keyword:
One-line Description:
QQQ, After editing a QTOF method, some changes may not take effect when running the method
Problem:
There is a defect in the QTOF acquisition code that causes it to use some of the previous method settings after the method is edited. The affected method settings are Stop time and some tune settings (mass axis settings for the quad and dynamic ramps). There is a similar issue with the QQQ method. However, there are fewer settings affected in the QTOF. Also, dynamic ramping is not currently being used in the QTOF.
Temporary Solution:
The workaround is to save the method and then reload the method from the disk. After reloading the method, the software will have all the correct settings.
Fix Information:
This has been resolved in released version MassHunter GCMS Acquisition B.07.01.
Keyword:
One-line Description:
SQ, "VACUUM VENT" hangs when done and trying to exit Vacuum dialog box
Problem:
There could be a timing issue when exiting the dialog box -- this is related to the background (vacuum values acquisition) and the foreground dialog box conflicts.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GCMS Acquisition B.07.01.
Keyword:
One-line Description:
QTOF NCI MS/MS runs in PCI MS/MS mode
Problem:
QTOF, NCI MS/MS Acquisition not working NCI Tune MS and MS/MS work fine. NCI MS Acquisition works fine. The firmware is not setting the pulser polarity correctly. It always set it to positive mode when doing MS/MS. It is a long existing defect when the MS/MS mode was introduced. Only NCI MS/MS mode is affected. Other modes are fully functional.
Temporary Solution:
New firmware is available via point patch
Fix Information:
n/a
Keyword:
One-line Description:
SQ: MassHunter GC/MS Acquisition Checkout procedure is not evaluating ETUNE.U.
Problem:
The Checkout/Tune Evaluation historically worked directly with ATUNE.U only. Exception being when HISENSE.U was used. Then the filament # had to be saved into the HISENSE.U file to be used by checkout tune and tune evaluation. Both ATUNE.U and HISENSE.U were updated and the only difference was in EMV. The extractor related tune ETUNE.U however is never checked by Checkout procedure so the extractor HW is not tested. That causes compliance problem when trying to validate the configurations.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
MSD: Wrong path for “Run Method” datafiles
Problem:
Wrong path for “Run Method” datafiles Open MassHunter Acquisition; Click on “Run Method”; after selecting the desired method, enter the data path (for example “D:\MassHunter\GCMS\data”) in the “Start Run” dialog; Click “OK and Run Method”: data acquired is correctly stored under the selected path; Click “Run Sequence”; enter data path (for example “D:\MassHunter\GCMS\data\sequence”); Start sequence: data is correctly stored under the selected path; Click again “Run Method”. Enter data path and start the run; Data is not stored in selected folder, but in last used sequence data path – e.g. “D:\MassHunter\GCMS\data\sequence” instead of “D:\MassHunter\GCMS\data”;
Temporary Solution:
Close and re-open MassHunter Acquisition before executing “Run Method”.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
MSD: Wrong window behavior when editing GC method:
Problem:
Wrong window behavior when editing GC method: Open the GC method edit dialog; Close the dialog (either by clicking “OK”, “Cancel” or “X” in top-right corner); If any other window (beside MassHunter Acquisition) is open, such window is focused and MassHunter main window is sent background;
Temporary Solution:
minimize any other window(s) before editing GC methods. Does not affect functionality, but is very frustrating.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: SIM ions is deleted by clicking OK button
Problem:
Create SIM method included some SIM ions. Then click OK button and leave MS method editor window. Then enter MS method editor again. Then click OK button and back to MS method editor again. The last SIM ions is deleted.
Temporary Solution:
Save method is required and then the information will be saved and then recalled.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: In Edit SIM method parameter, SIM ion is deleted by clicking dwell time and cycle time field.
Problem:
In Edit SIM method parameter, add some ions to SIM field. Then Click Dwell time field and Cycle time field in SIM Time Segment. Added ions are deleted.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: CheckBar keyword not working in Drug Mode
Problem:
Setup a sequence where the first line was the CheckBar keyword with PAUSE in the keyword string. According to help, use of this keyword should override any selection mode on the start sequence panel. On the start sequence panel, selected Inject Anyway. Ran the sequence with a barcode mismatch on the second sample. Sequence ran though instead of pausing. The logbook showed "continuing although barcode did not match expected".
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: SIM Table does not reflect the correct number of total Ions.
Problem:
Customer is building sim table with one group. In the sim time segments , number of Ions shows one less than what is in the sim table on the right.If she tries to adjust the number of ions to the correct number, the last ion is ignored during acquisition. Leaving the total number as the incorrect number, seems to work but is causing confusion.
Temporary Solution:
n/a
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Reprocess a sequence is not working
Problem:
In MassHunter Acquisition software B.07.00 SP2 with G1710FA as the Data Analysis software, it has been observed that the ALS starts every time when a sequence is to be reprocessed. The Use ChemStation DA is checked. When the customer selects Run Sequence and selects Reprocessing only, the ALS immediately starts to run. It has also been observed that the simulaterunmethod=1 is also starting the ALS.
Temporary Solution:
A point patch is available for this.
Fix Information:
This has been fixed with B.07.01 released software package.
Keyword:
One-line Description:
SQ: Cycle Time for one SIM ION pegged at 50.00, regardless of Dwell Time
Problem:
In the 597x Method Editor, the Cycle Time column does not update correctly if you only have one SIM ion specified. The Cycle Time is displayed as 50.000 regardless of the dwell time. To reproduce: 1) Open Method Editor and set to SIM mode. 2) Put one SIM ion in SIM Tab 3) Cycle Time in SIM Time Segments set to 50.00
Temporary Solution:
n/a
Fix Information:
This has been resolved in the B.07.01 release software package.
Keyword:
One-line Description:
MSD Method Editor - SIM ion gets deleted from SIM table by mistake.
Problem:
This will occur within the “SIM Time Segments” of the MSD method Editor. By clicking onto the field showing the “Number of ions” from one SIM group the user will remove one SIM ion from the SIM tab list.
Temporary Solution:
n/a
Fix Information:
This has been resolved with the B.07.01 release software package.
Keyword:
One-line Description:
SQ: Real time plot layout not retained from session to session
Problem:
When adding multiple Real-Time Plots (SIM or Scan), the plots are stacked correctly when you exit the MSD Method Editor (in the available space). Save Method. Exit MassHunter GCMS Acquisition. When MassHunter GCMS Acquisition is loaded the next time, some of the real time plots are not put back into the same place that they were when the method was saved. Some were, some weren't. All the monitors were placed in the correct place.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
HS: HeadSpace instrument status is not consistent with MassHunter GCMS Acquisition Instrument status.
Problem:
The inconsistent issue happens in following 2 situations. 1. Start a sequence and Disconnect HS Lan and RS232 cable following injection to GC, and then Reconnect the cables. MassHunter GCMS Acquisition instrument status always remains as Offline even the instrument status of HeadSpace and GC are all online. 2. Start a sequence and Power off the HeadSpace device, and then Power on HeadSpace. MassHunter GCMS Acquisition instrument status always remains as Offline even the instrument status of HeadSpace is online. MassHunter GCMS Acquisition instrument status won't change to online unless start a single run or sequence run.
Temporary Solution:
n/a
Fix Information:
Has been resolved in B.07.01
Keyword:
One-line Description:
QQQ: No bake keyword in sequence for GCMS QQQ
Problem:
Configure a 7000 GCMS QQQ system Edit the sequence, for the keywords column, cannot find "bake" or "bake out" keywords from the drop down list.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: ENVDEMO does not have any demo files associated with it from the installation
Problem:
MSD: ENVDEMO does not have any demo files associated with it from the installation F.01.00 has the files but F.01.00 SP0 does not copy over the demo files
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Link to GC Help Broken
Problem:
Due to the GC driver being moved to a subdirectory, the acquisition software no longer has a link to the GC driver help from the MassHunter online help.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: ChemStation to MassHunter MSD Method Migration: Timed Events for Detector do not come through correctly
Problem:
In the ChemStation, have method set up with Absolute EMV, and the timed events for EMV have 200, 0, -200. When this method migrates to MassHunter, the Absolute EMV setting is correct in both the Main EMV Setting and the Timed Event, but the values of the Timed Events are still the Delta EMV values of 200, 0, 0 (since absolute can't go below zero). The method should be able to translate the EMV values based on the EMV Setting. ie if the Absolute EMV is set to 2000 (from tune), the timed events should have been 2200, 2000, and 1800
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Undefined symbol dummy_file$ if you specify unlinked sequence with rear samp as the second sample
Problem:
Set up a dual injection sequence with the Unlinked keyword. Added two sample lines and the RearSamp column. When it is specified correctly and check RearSamp for line 2, all works correctly. If however, it is set up and check RearSamp for line three instead, an error message "Undefined symbolL dummy_file$" and the sequence aborts. There should have been a better informative message about the sequence is incorrectly set up.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: 6890 method from MSD Productivity ChemStation is not migrated to 7890 MassHunter GCMS Acquisition
Problem:
There are no errors but none of the parameters from a 6890 method from MSD Productivity ChemStation is not migrated to 7890 MassHunter GCMS Acquisition. 6890 ChemPort in MSD Productivity ChemStation migrates correctly to MassHunter GCMS Acquisition 7890.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
MSD: "Alert (Instrument is in SLEEP mode)" does not appear
Problem:
While the instrument is in SLEEP mode the 'Alert' messages will not appear on the display of the instrument. The alert window will not appear.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QTOF: Sequence log files are not saved in specified DA path in STE.
Problem:
In STE with designed sequence table which is intented to test with Qual and Quant report. Although the DA path is defined in the STE, when sequence finished, the sequence logs are found under D:\MassHunter\GCMS\1 instead of defined DA path.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
Russian: Manual Tune boolean (on/off type) slider controls have an unexpected bias towards certain states. This behavior is inconsistent with English version.
Problem:
In Russian, the boolean-type slider controls have an odd bias. In a certain sequence (see attached screen capture), if you click on the slider control, it will unexpectedly switch to a certain state, such as an "Off" position. CORRECTION: Attached image step #1 should say "Put "HED Enable" into On position" --- not "Off position".
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
Russian: Manual Tune Profile / Scan / Capture tabs have incorrect floating point parsing/conversion.
Problem:
It appears string-to-floating point parsing/conversion in Manual Tune ==> Profile / Scan / Capture tabs is off by a significant digit...
For example, type "2,2" + {ENTER} and the text will be converted-and-displayed as "22,00".
The Profile, Scan, and Capture tabs may not be an exhaustive list of where this issue occurs.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
Russian: QQQ tune reports printout errors
Problem:
Missing lines in report. Tune file name is not printed. Numerous overlapings, word divisions.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: Pause batch if calibration expired is not working with Intelligent Sequencing and classic DA
Problem:
Intelligent Sequence set to Pause batch if calibration expired. Set up a sequence with two specimens. Ran the sequence and got message that the current calibration is out of date, responded Yes to continue. When prompted, chose a Med Control. Instead of pausing the batch, it asked for a re-injection.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QQQ: Sequence keyword help needs specific information for each instrument type
Problem:
The "Keyword / Keyword String" help topic only has information for the single quad. For the triple quad the 'Check Tune' section doesn't apply and the 'tune' keyword is missing. The 'Tune' keyword should then explain the use of the following keyword strings: Check - runs checktune, no further actions CheckPause - runs checktune and sets pause if fail AutoTune - runs autotune with all defaults, no further actions AutoTunePause - runs autotune with all defaults and sets pause if it doesn't complete CheckAuto - runs checktune , then autotune if check fails, then checktune again, no further actions CheckAutoPause - runs checktune , then autotune if check fails, then checktune again and sets pause if fail
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
MSD: 'Tune' sequence keyword should load the method from the sequence line
Problem:
When a tune function is used in the sequence the tune file that is used comes from the last method loaded. It seems like a reasonable expectation that the tune file would be the one associated with the method on the same sequence line as the tune function. This is not the case. If the sequence line is not the first then the tune file will be the one referenced in the method from the preceding sequence line. If the tune function is in the first line of the sequence then the currently loaded methods tune file is used. This can lead to an unexpected tune file being used if a method is given in the sequence line with the tune function. For the QTOF the tune file used in the mass calibration comes from the method on the same sequence line as the tune function. I think we should have behavior like the QTOF’s for the triple quad tune functions.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: Initialize MS Interface Does Not Reboot MSD
Problem:
In Tune and Vacuum Control view, selecting Vacuum/Initialize MS Interface is supposed to reboot the MSD Interface and the software verifies the firmware version. Verification of the firmware is okay but the MSD does not do a full rebooted.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
CTC: Synchronizing error in sequence using overlap function in Acquisition
Problem:
Intermittent, the sample overlap function without the CTC or Masshunter software works fine and they can run sequences without lockup; however, if they use overlap, customer can run 5 to 20 runs and then locks up with error “ waiting on synchronizing…..”
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Sequence table, if data file name contains a point the right part of the name will be truncated
Problem:
If the data file name has a ' . ' in the name, then the information to the right of the ' . ' will be truncated.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: Reconnect to MSD, temps do not go to setpoints and MSD status square not correct
Problem:
If you turn off the MSD, lose connection to MassHunter. When Offline, turn the MSD back on. Once it is on, use the help\reconnect to MSD menu item to reconnect. Once the MSD is reconnected, the status square and instrument status are green even though the temperatures are not at the setpoints (they are probably going to the "power on temps"). If you hit apply, the status does not change, even though the temperatures do in fact change and go to setpoints. When the source and quad are not at their setpoints, the MSD square should be yellow and instrument status should say "not ready".
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
SQ: " Undefined symbol; lockobj" happen by re-lock
Problem:
1. load locked method (5975_Scan_pressure_01.M.zip, it is 7890A-5975 method) 2. Go to RTLock view 3. select "RTlock/Relock Method" 4. select data (RTLock3.d) 5. "Undefined symbol; lockobj' will appear The file will re-lock but the error message is displayed
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QQQ: the settings about MS1(and MS2) Mass Axis Offset (and Width Offset) for Wide and for Widest of Peak Width are reversed between Autotune report and Tune file
Problem:
For Peak Width at "Unit": The settings about MS1 (and MS2) Mass Axis Offset and Width Offset are consistent between Autotune report and Tune file; For Peak Width at "Wide" and "Widest": The settings about MS1 Mass Axis Offset are reversed between Autotune report and Tune file; for instance, for MS1, Peak Width at "Wide" , the setting of Mass Axis Offset is -1.565 on Autotune report, while this value is set for Peak Width at "Widest" in the tune file. vise visa.; The same issue exists for MS1 Width Offset too. The same issue exists for MS2 as well.
Temporary Solution:
n/a
Fix Information:
This has been fixed in released version B.07.01
Keyword:
One-line Description:
SQ; Extration tune final ramp of extractor stops at 0,1 volt instead of 5 V
Problem:
Extration tune final ramp of extractor stops at 0,1 volt instead of 5 V
Temporary Solution:
User will need to go into manual tune and adjust ramp limit and then save tune file.
Fix Information:
Fixed with release version in B.07.01
Keyword:
One-line Description:
CTC PAL: Using a solvent delay of zero minutes will cause acquisition to fail to run the injection with the error “Operation is not valid due to the current state of the object”
Problem:
Using a solvent delay of zero minutes will cause acquisition to fail to run the injection with the error “Operation is not valid due to the current state of the object”
Temporary Solution:
Workaround is, use a solvent delay of 0.3 minutes
Fix Information:
This has been resolved in revision MassHunter GCMS Acquisition B.07.01
Keyword:
One-line Description:
SQ: MSD left BUSY after temporary network interruption and user Method, Exit
Problem:
MassHunter GCMS Acquisition was Idle after normal connection, then disconnect the Ethernet cable at the MSD SmartCard connection point. In less than 60 seconds, MassHunter GCMS Acquisition changed its display of Instrument Status from Ready to Offline. After 5 minutes of disconnection the cable was re-connected but the instrument will accessible while the SmartCard will state busy.
Temporary Solution:
If the user uses the reconnect feature in the vacuum status section this will reconnect the connection correctly. But if the user exits software package then a reboot may be required to re-establish the full connections.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
In sandwich injection, L2 vial and L3 vial doesn't return to the original position when the sequence finished
Problem:
In MassHunter Acq B.07.01, when use Keyword 2-Layer L2 and 3-Layer L2;L3, L2 vial and L3 vial doesn't return to the original position after finish to run sequence. When start to run sequence again, left L2 and L3 vials are returned to the original position before start to first run.
Temporary Solution:
Point Patch is available.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: Cannot automatically upload PDF reports from MassHunter Acquisition to ECM
Problem:
In MassHunter Acquisition B.07.00 and B.07.01 with ECM, if you run pdfwiz macro to automatically generate PDF of the reports (autotune, tune eval, air-water check, percent report, lib search report, and quant report) the PDF files are not automatically uploaded to ECM server.
Temporary Solution:
n/a
Fix Information:
MassHunter GC/MS Data Acquisition B.07.02 requires no point patch, however, MSD ChemStation Data Analysis F.01.01.2317 (released March 2014) still requires ecmendjob.mac (date stamp 5/28/14) to fix the problem. Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
CTC: Add the last modified date to the bottom in the sequence summary report
Problem:
n/a
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Start a tune, abort the tune, then try run method, system will not acknowledge a run start.
Problem:
From Instrument Control or Tune and Vacuum Control displays the user can start an autotune. When the autotune is started the system will automatically go into Tune and Vacuum Control menu view. If the user aborts the autotune (any type of tune) this will cause two things to happen. 1 - The autotune action has stopped and the system will display the Tune menu view. 2 - The abort action will cause an abnormal stop. It will inhibit the remote start for the system. This will cause the system to go into a complete lockup and will require a complete reboot of the WHOLE system to recover.
Temporary Solution:
Do not use the abort feature during a tune operation. If an abort is pressed during the tune operation then a run method is started, then the user will need to reboot the whole GCMS system to recover from the lockup: power cycle the MS, power cycle the GC, and a reboot of the MS Workstation.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
CTC: Adding one line to the end of a running sequence will cause the line above injecting to the wrong GC inlet using SINGLE OVERLAP or NO OVERLAP
Problem:
The customer using two methods, one for the rear inlet and the other one for the front inlet. They always adding NEW lines to the end of their sequence and then position and run the sequence with the new lines. If mixed injection ports are being used then the wrong injection could be used.
Temporary Solution:
Point Patch is available.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
Dual LAN card with FIxed IP address is not longer working since the installation of B.07.01 SW
Problem:
Dual LAN card with FIxed IP address is not longer working since the installation of B.07.01 SW.
Temporary Solution:
Point Patch for IP addresses update is available. Job Aid has Agilent recommended configuration.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: does not respond to 5977 faults when RunStatus=Idle,other?
Problem:
MassHunter Acquisition does not respond faults detected and reported correctly when RunStatus=Idle when communicating to 5977 and this also includes "VacSysFail" Instrument State when HiVacNotReady and HiVacOff faults are concurrently asserted.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
QQQ: DRUG MODE configuration will not allow Control samples to be run.
Problem:
In drug quant configuration, the use of a “control” in the sequence causes a crash. The verification at the start of run sequence looks for a gencont.mac that apparently is not included in the software – B.07.01, this shows up if MSD ChemStation DA is not installed, which will be the norm for a QQQ instrument.
Temporary Solution:
1. Install MSD ChemStation DA F.01.01 or 2. Use the attached 2 files to correct the issue without installing the MSD ChemStation
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
MSD: MassHunter Data Acquisition – protection of MS_Compliance.xml files
Problem:
Access levels for the different roles (Acquisition Analysts I, Acquisition Analysts II, Acquisition Analysts III, Acquisition Managers) defined in MassHunter Data Acquisition are defined in files named “MS_Compliance.xml”, which are found in:\Masshunter\GCMS\1 and :\Masshunter\GCMS\2 (where is the chosen drive for the installation). Folders :\Masshunter\GCMS\1 and :\Masshunter\GCMS\2 are set up by Agilent with groups “Everyone” and “Authenticated Users” having “Full Control” access. This means that anyone that can have access to the workstation can modify the access levels in MassHunter Data Acquisition, potentially giving an operator the right to create or modify acquisition methods, change system settings, etc. Since there is no audit trail linked to this file, and no audit trail in MassHunter Data Acquisition, this represents a very serious security problem , as such actions would leave no trace. We tried securing these files by changing the access rights on the files (leaving folder security unchanged), but ultimately this proved to be ineffective, because the “Full Control” setting applied on folders :\Masshunter\GCMS\1 and :\Masshunter\GCMS\2 takes precedence. Users can still edit these files.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ: "Improper masses for mass axis calibration" error occurs when running xTUNE.U
Problem:
In MassHunter Acquisition B.07.00 SP2 and B.07.01, if you use xTUNE.U to tune, you get error "Improper masses for mass axis calibration". This often happens after sequence was run the night before. The problem is when the method has more than three scan segments.
Temporary Solution:
Recommendation is to run the method with a wider scan range and run with one scan segment. A point patch is also available.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
SQ: 6890/7693 sequences allow override sample volumes only for values of the 7683 with 10uL syringe
Problem:
MassHunter GCMS Acquisition connected to 6890+ with 7693 system including BCR. The injection volume range should be from 1-50% of the syringe size. With a 10 uL syringe configured and 1uL volume specified in method, create a 6 line sequence with volume overrides of .2, 1, 2, 3, 4, 5. These are accepted and run. However, any other valid value, such as 1.5 (15%) is rejected after a lengthy wait for validation (Checking sequence line 0). If you try this sequence validation long enough with any values except the above, you may get 'Object reference not set to an instance of an object' or even crash the system with 'msinsctl has stopped working'.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: 6890 with 7683 Start Run Override Injection Volume does not advise of invalid entries; just rounds them silently to nearest stop value
Problem:
MassHunter GCMS Acquisition connected to 6890 with 7683 only. This ALS allows only 6 'stops': 2, 10, 20, 30, 40, 50% of the syringe size. Create a front ALS method with any size syringe. Select Start Run and opt to override Injection Volume. Enter any valid value and this is run correctly. However, enter an invalid number and this is rounded to the nearest valid stop without any advisory. Log shows the rounded value. e.g. 2.5 rounds to 2; 1.5 rounds to 1.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
QQQ: Find Compounds by MRM fails with an error - log file indicates - Invalid XY data. - X values must be unique
Problem:
Getting an error message if they run Find Compounds by MRM, in Qual. Problem is related to the multiple time segments of the MRM. Loading the data file into Quant B.07.00 works just fine.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: MRM Optimization tab does not have any type of workflow or help to explain how to use it.
Problem:
QQQ: MRM Optimization tab does not have any type of workflow or help to explain how to use it.
Temporary Solution:
The help information for the MRM Optimization is part of the supplemental disc. The feature was added to the software package as a convenience.
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MSD: Keyword"2-Layer L2" cannot work with dual injection method.
Problem:
Instrument: 7890B+ Front/Back Injector (7693) 1. Create a method with dual injection. For both front and back injectors, specify a 2-Layer Sandwich Injection. 2. Add the dual injection vial column to the sequence table and create a sequence with the 2-Layer L2 keyword. Run the sequence. 3. Sequence is aborted because the L2 vial for Back Injector is missing.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MSD: The Scaling for duty cycle is not correct for the Backflush Pressure
Problem:
The duty cycle for the Backflush channel is about 24% and it does not reflect the correct value in Qual.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: Japanese; Online help: 597x manual Tune dialog Box; "Capture" is still in English
Problem:
Online help: 597x manual Tune dialog Box, the term "Capture" is not translated.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MSD: Save As to invalid method format does not return user to Save As dialog
Problem:
MassHunter GCMS Acquisition B.07.02 with CTC-PAL3 Save as a method to a name with a decimal point; e.g. PAL3LiqV1.12.M. There is a small text on the taskbar which shows 'Invalid path: C:\MassHunter\GCMS\4\METHODS\...1.12.' This failure to save should return the user to the Save As dialog awaiting a valid entry.
Temporary Solution:
Please look at the taskbar for confirmation of a saved method.
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
QQQ: Wrong Mass Assignment in Fast Scan Mode (Low Data Samples)
Problem:
In fast scan modes (i.e. simultaneous MRM/Full), the mass assignments could be off. If the assignments are off too much then library searching and compound identification for most compounds show poor or wrong mass assignments with 1 or 2 data sample. This wrong assignment is due to tuning of lag factors.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ: lagfactors are intermittently reset.
Problem:
2) A more insidious issue is at work with respect to the mass axis lag factors. When the MSD is restarted with MassHunter open (as is often done when venting the instrument for cleaning or maintenance), the mass axis lag factors revert back to pre-2005 values that correspond to old electronics. The effect of this is most prominent at the “Fastest” scan speed, where mass 219 actually shows up at 223! This is also NOT calibrated out by the mass gain correction factors. There is a smaller effect at slower scan speeds, but this may affect our improved mass accuracy measurements.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
CTC: When using a 384 wellplate in CTC-PAL( GC Sampler 80), MassHunter GCMS Acq rejects over 100 vial position.
Problem:
When using a 384 wellplate in CTC-PAL( GC Sampler 80), MassHunter GCMS Acq rejects over 100 vial position.
Temporary Solution:
Will need multiple wellplates if using sample positions > 100.
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: 7000 system is ending in a failure loop related to the source and MS1 heater regulation
Problem:
7000 system is ending in a failure loop related to the source and MS1 heater regulation resulting in a loss of communication to the 7000.
Temporary Solution:
n/a
Fix Information:
Has been resolved with firmware version Build 054.
Keyword:
One-line Description:
MSD: In B.07.02 release, Read Barcode button has been updated
Problem:
In B.07.02 release, Read Barcode button is updated. If you put a vial number larger than 0 in vial cell, step B and C should be the same all samplers will pick up the vial from the tray and send to Barcode reader to get a reading. If you want to read only from a default location, put a number zero in vial cell , CTC PAL and PAL-3 will pick up and read the default location specified in configuration panel. ALS and Head Space 7697 will need you hand set vial into Barcode reader(default location) to get a reading.
Temporary Solution:
Read Barcode button To enter a vial's barcode value into the Sequence Table at the cursor's location: a. Place a sample vial with a barcode label into the barcode reader mounted on an Agilent ALS tray, CTC sampler, or a 7696 Headspace sampler configured vial tray location. b. Place your cursor in that sample's Sequence Table Expected Barcode column or the Dual Inj Expected Barcode column. c. To enter the vial's barcode value into the table click Read Barcode. This button is active when a Barcode Reader is installed and the Expected Barcode column is visible in the Sequence Table.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition revision B.07.02.
Keyword:
One-line Description:
QTOF: The x-range of the spectrum plots during mass calibration show the mass in the last line on the selected masses table on manual tune panel, even if this mass isn't the highest one
Problem:
The order of the selected masses on manual tune can be sorted based on the mass values. However, if user doesn't make sort, the x-range of the spectrum plots during mass calibration just show the mass in last line on this table even if this mass isn't the highest one.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
CTC PAL: Running a method with wrong script for tool installed on RSI
Problem:
Had a liquid script method loaded. Replace the tool with a HS. Without loading a new method, attempted to run the liquid script method. It brought up a method resolution panel which one is able to cancel. The PAL3 posted a message to the logbook :error while validating script" however MassHunter GCMS Acquisition just went into pre-run and sat there until the run has been stopped manually.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Read Barcode reads only single locations
Problem:
Enter sample locations and expected barcode column to table. The Read Barcode function picks up the vial from the designated location, but only one at a time.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
"Mist" value corruption
Problem:
Daily automated test shows the "Mist" value in PRE_POST.INI data file to be intermittently set as "Mist=0" instead of the expected "Mist=20". Initially investigation is going the Pre-Post ini file is corrupted but the data.ms file is okay. It could be Firmware/Hardware corruption or MassHunter GCMS Acquisition is sending the wrong value due to a corrupt file.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ: Filament 1 error, switch to filament 2, start a tune and still get filament 1 error
Problem:
There are some issues about filament 1 and filament 2 switching. If you have a blown filament 1, switch to filament 2 you must save the tune file and then start the tune msd to acquire the new tune. if you switch the filament and do not save then the tune msd will be using fialment 1 and create the error message.
Temporary Solution:
If you have a blown filament 1, switch to filament 2 you must save the tune file and then start the tune msd to acquire the new tune.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
RTL Calibration - Wrong pressures displayed
Problem:
When running RTL calibration for constant pressure method wrong pressure values are displayed in Locations and Pressures for RTL Calibration window. Actual pressures set during sequence run read from GC panel are OK.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ: Weird message if cancel picking valid tune file
Problem:
If you select an invalid tune file (ie a 5975 file on a 5977), you get a message saying, pick something else or cancel. , If you select cancel, you get the attached message. "Bad. Now need to inhibit any actions." Nothing bad seems to happen, except that it takes a little bit for the instrument control menu items to become active again.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
MSD: No barcode label on vial and expected barcode field blank reports error and not injected but sequence not stopped
Problem:
Setup a sequence and the second line did not have an expected barcode in the field. When the sequence ran, the vial for that line did not have a barcode label. It reported an error "Sample aborted due to a runtime error." :Barcode of target could not be read." The sequence did not stop however, it proceeded to the next line.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MSD: Readme.txt file \support\firewall references the wrong directory location
Problem:
states ... located in the \Documents folder of this disc. should be ...located in the \Documentation folder of this disc.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
QQQ: Number of plots for " MS1 Profile" or "MS2 Profile" is not consistent with the selected masses
Problem:
For all types of ion source, for both 7000 and 7010. The following is an example from 7000C: On manual Tune panel, 1. Turn on Emission; open calibrant valve; 2. The scan mode panel is in "MS1 Profile" by default; 3. Click "Start" button to monitor the plots on top area. The selected masses by default for EI are 69, 264 and 502 for both " MS1 Profile" or "MS2 Profile"; 4. Switching between "MS1 Profile" or "MS2 Profile", three plots appear, the plots and the behaviors of count changing look normal; 5. All above are as expected; 6. Add mass 131, 219 and 464 to "MS1 Profile", while add 219 only to "MS2 Profile; 7. Switching between "MS1 Profile" or "MS2 Profile". 6 plots appear for "MS1 Profile", the behaviors of count changing are right. However, there are also 6 plots appear for "MS2 Profile", two extra plots with "frozen" peaks and count number.
Temporary Solution:
Note: the issue occurs only when plot number is greater than 3.
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
SQ: Monitors are not saved in the correct location via the save layout or saving via the methods
Problem:
MS ONLY system. Under Instrument, edit monitors, selecting 4 more MS monitors to be displayed. Then moving the monitors to the new position and then saving layout and then saving the method (also occurs when using save method as). Once the method is saved the monitors are moved back to their original position and not what was saved in the method or layout.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ: Tune report does not present the same base peak results in Profile versus Scan section.
Problem:
The tune report shows 69 as the base peak for the Profile section while the Scan section uses the most abundant peak. Typically, the base peak is 69 and the Profile and Scan section will match up; but if the most abundant peak is 219 then the results for the Rel Abund will be different.
For example
(Profile) (Scan)
Mass Abund Rel Abund Rel Abund
69.00 371,752 100.0% 91.3%
219.00 407,093 109.5% 100.0%
502.00 37,032 10.0% 9.1%
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
QQQ: Wrong Mass Assignment in Simultaneous Mode
Problem:
1. The wrong mass has been observed in the “full scan” portion of the simultaneous scan with either MRM or SIM mode. 2. The mass miss assignment is not dependent on the filtering being ON or OFF. 3. Comparison for full or simultaneous scan was made at the same scan time (2 data samples)
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ: Cannot run a sequence that overrides the injection volume with liquid tool installed.
Problem:
Had the liquid tool installed with a 10 uL syrings such that the sample volume was 0 - 10. In the method, set the sample volume to 1 uL. Set up a sequence using that method and attempted to override the injection volume by entering values in the Vol colume that are valid (ie. 2 uL, 3 uL and 4 uL). Saved the sequence and attempted to run it. It runs a simulation first to determine that all of the values are valid and it states the injection volume is out of range. It will not let the sequence run until the vol from the field is removed.
Temporary Solution:
Remove the volume from the field and then restart the sequence.
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MSD: MassHunter GCMS Acquisition Injects Wrong Vial when PAL3 Run from the Back
Problem:
Set up a GC/PAL3 system with a Front and a Back Inlet. Set up a method to inject to the back inlet. Hit the start run button. Change the Tray name for the back injection and hit OK. MassHunter GCMS Acquisition will start the run but tell the PAL3 to inject from whichever tray was in the FRONT inject screen.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
QTOF: MS collision energy not recovering from MS/MS mode
Problem:
While running in the MS/MS-MS mode of operation; MS collision energy not recovering from MS/MS mode transitions.
Temporary Solution:
GC QTOF firmware G.7200.01.20 is available.
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MSD: Incorrect Sequence Simulation for Drug Mode
Problem:
In Drug mode, autonaming needs to use the ‘Drug mode way’ that includes the sample type in the datafile name (i.e. 001BL0098 for the blank using vial 98 as the first run). The acquisition works fine and will autoname correctly, but the simulation check uses the legacy ‘autoname’ that is simply -> vial number, index number, run number (i.e. 09801001). So, existing datafiles will not be caught
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ: Unhandled exception occurred when selecting File > View Tunes in Tune and Vacuum Control
Problem:
When you select File > View Tunes, you get error message "TunePlot: Unhandled exception has occurred in your application." This is due to incompatibility of ATUNE.CSV created from MassHunter GC/MS Acquisition pre-dating B.07.02.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in MassHunter GC/MS Acquisition B.07.03. The ATUNE.CSV created from versions pre-dating B.07.02 is renamed to ATUNE.CSV.txt and it contains past tune records.The mslogbk.htm logs the following messages: D:\MASSHUNTER\GCM1\5977\ATUNE.CSV has been renamed because it is not compatible. D:\MASSHUNTER\GCM1\5977\ATUNE.CSV.txt is the new name. This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MSD: G1701-90112_GCMS_Software_Installation_Guide has the wrong IP address for the QQQ and QTOF
Problem:
MSD: G1701-90112_GCMS_Software_Installation_Guide has the wrong IP address for the QQQ and QTOF Page 42 has 192.168.245.12 - QQQ and QTOF Page 43 has 192.168.245.11 - GC
Temporary Solution:
Yhe QQQ and QTOF IP address, the correct address should be 192.168.254.12. The GC IP address, the correct address should be 192.168.254.11.
Fix Information:
n/a
Keyword:
One-line Description:
MSD: The configuration file which holds the HS license is deleted after Masshunter configuration update.
Problem:
System is headspace (B.01.06) with MassHunter (B.07.01). When updating instrument configuration by clicking ok, the configuration license file is deleted. This causes the headspace license key to be deleted. Next boot up of the MassHutner GCMS Acquistion software causing a prompt for the license key.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ, Add / Remove ALL monitors will generate an exception error
Problem:
Add / Remove ALL available Monitors in / from Selected Monitors Instrument Control -> Instrument -> Edit Monitors -> add/remove ALL available Monitors to/from Selected Monitors (Do not use Add button, but double click over each monitor) always throws the following exception: InvalidArgument=Value of '-1' is not valid for 'index' Parameter name: index NOTE: Select ALL monitors except the last Available will not generate the exception. The exception occurs when the last AVAILABLE Monitor is selected (by double clicking over it).
Temporary Solution:
Use Add / Remove button instead of double clicking the monitor name.
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ B.07.02 Initialize MS Interface throws Alert window.
Problem:
From Tune and Vacuum Control Window Click Vacuum -> Initialize MS Interface -> this throws Alert window and never starts the Initialization of MS Interface. Alert: Agilent reCCommends that you exit MassHunter and power cycle the MSD.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MPV valve on 7890 is not controlled Properly
Problem:
MPV valve on 7890 is not controlled Properly
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ: MassHunter Acquisition B.07.01 and G1701FA Envquant not printing the correct detailed analysis parameters with 5977 Configured
Problem:
If one configures a 5977 system in the msdchem.ini file it sets ms_id=0. When printing from acquisition envinit.mac sees ms_id=0 and uses the macro from gcmacros folder. This then does not show the target ions or qualifiers. This only happens if a 5977 is configured, 5973 and 5975 work fine because the ms_id is either a 3 or 5.
Temporary Solution:
The modified attached macro envinit.mac looks at ms_type and now the report is correct. A point patch is available.
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
Inst# can not be launch with QQQ RTL method
Problem:
1. Configure 7890-7000 QQQ as Inst#4 2. Launch Inst#4 3. Show GC Status or MS Status 4. load RTL method 5. Close Inst#4 6. Re-launch Inst#4 > Acq SW became "No response".
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MSD: Low mass tune issue
Problem:
After low mass tuning, the system’s auto tune still keeps to capture ions 69/131/219 even when selecting new tune.
Temporary Solution:
Load a new tune file and check the parameters and then start the new tune.
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
QQQ: Running a method with multiple time segments with MRM plus SCAN could cause the system to go OFFLINE
Problem:
Running a method with multiple time segments with MRM plus SCAN could cause the system to go OFFLINE and when this occurs a power cycle will be required to re-establish the communication.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SQ 5977: Filament change is not saved and used in BFB_atune
Problem:
If atune.u is run with filament 2 and saved and the bfb_atune.u is saved to use filament 2, this does not stay. After saving filament to 2, and saving, then running the bfb_atune.u macro, the filament gets switched to filament 1.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ: Some 5975 Manual Tune trackbar sliders do not respond to right/left arrow key. Divergent behavior. Needed for test automation.
Problem:
Some 5975 Manual Tune trackbar sliders do not respond to right/left arrow key. The behavior is different than 5977. In test automation, we select the appropriate text box control, the matching trackbar control, send the right/left arrow keys, and then check if the value increment/decrements accordingly.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
SQ: NCI datafile does not reflect that it was acquired in NCI mode for MassHunter, ion polarity indicates positive
Problem:
This issue is only for single quad datafiles. Quant and Qual both show the ion polarity of all data file types for single quads as positive, even if it was acquired in negative mode for CI. The sample information is correct. It uses an NCI tune file and a method with the name NCI in it. The instrument’s polarity is tied to the acquisition tune file so if that is correct it’s all good.
Temporary Solution:
To validate the datafile type was acquired in NCI mode, look at the datafile in ChemStation datafile format.
If you look at the ChemStation data file format section, the pre_post.ini does indicate the mode of operation:
cimode = 0 means no 1 means yes
cipolarity = 0 means positive 1 means negative (0=PCI, 1=NCI)
ciflow = displays the CI Flow Module reagent gas flow rate
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
QQQ 7010: Gain Factor Used in Tune causing isotope ratio issues.
Problem:
The 7010 generates significantly more ion current than the 7000 series ion sources. The higher ion current that ends up at the detector often reaches or exceeds the saturation conditions on the electron multiplier resulting in isotope ratios exceeding the limits that we define as acceptable.
Temporary Solution:
Lower the abundance for the most abundant ion to be below 5M and then run Tune Evaluation for validation.
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
MSD: Autorelock does not adjust the flow or pressure from the method
Problem:
Running a sequence with AutoRelock, but it looks like the AutoRelock is not executed.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
QTOF: QTOF Conditioning 7200B, values for -12V and +15V are not showing the correct actuals.
Problem:
QTOF Conditioning 7200B, values for -12V and +15V are not showing the correct actuals. The display values are not the actual values.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
Qual's Extract Defined Chromatograms fails to extract GC signal in nativity MassHunter data files
Problem:
What is happening is that a file collected under GCMS Acquisition B.07.02 for GC data only the GC signal can be extracted two of three ways. Extract Chromatogram and Extract all non-MS signals works as expected however the Extract Defined Chromatograms, using the drop down list item of “GC1” fails and gives a “No data points found” message.
Temporary Solution:
Run GCMS translator B.07.02 over the file (this should not be required as the file is collected in native MassHunter format) the Extract Defined Chromatograms, using the drop down list item of “GC1”.
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
CTC: Wrong individual injection volume values in sequence table
Problem:
Accepted range of Injection volume in sequence table (Mass Hunter Acquisition B 07.03) is always from 25 to 2500 no matter what instrument and syringe is installed on PAL3. No way to enter individual volumes for 10 uL liquid syringe.
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
MSD: CTC PAL add-on software: Data are going to the SEQUENCE FOLDER instead of the METHOD folder if the CTC is installed
Problem:
If the CTC PAL add-on software is installed a SINGLE RUN is using the sequence folder instead of the METHOD folder.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
TQ: RTL Calibration doesn’t correctly handle MRM data
Problem:
There is a problem with retention time locking a MRM method. When running an RTL acquisition the locking is done on a specified transition. The locking compound transition in this case is 323.9 -> 253.9; this transition is also in each of the appropriate time segments. The standard however also has another compound with the same MRM transition that elutes a little later. The software is choosing the RT on what looks to be higher response values, which then provides the RTL calculation with correct and incorrect RTs, providing a bad R2 value.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
SQ: Prepost.ini showing incorrect sample prep method when overrided in Sequence Editor.
Problem:
Created meth1 and prep1 and assigned prep1 to meth1. Created meth2 and prep2 and assigned prep2 to meth2. In a three line sequence using meth1, using the Sample Prep File Name field to change the sample prep method to be used to prep2. The sequence ran the correct sample prep methods. While looking at prepost.ini within the first data file, it listed prep1, but it should have listed prep2, which was the sample prep method that was used.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
QTOF: If bakeout time is above 23 hours the time calculation will be incorrect.
Problem:
If set the bake out to 23 hours, all seems to be ok. If set to 24, 25 or even higher it seems that 20 hours are reduce from the calculated time. 24 hours would be 4 hours; likewise, 25 hours would be 5 hours.
Temporary Solution:
n/a
Fix Information:
This has been revolved in MassHunter GCMS Acquisition B.07.03.
Keyword:
One-line Description:
[Untranslation]First entry of Audit trail for Method, Sequence and Configuration is still in English.
Problem:
1. Print detailed audit trail for Method, Sequence and Configuration. 2. First entry of each is still in English.
Temporary Solution:
Default configuration files are being used. All recorded audits are localized.
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
CTC: Unexpected Exception Error in Logbook When Trying to Run Sequence with LS tool.
Problem:
This error message occurs when trying to run a three-line sequence use the LS Tool while trying to perform a single sample overlap.
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
ECM: Only one method can be run at a time during the Sequence Table Editor
Problem:
Only one method can be run at a time during the Sequence Table Editor.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
GCMH Acquisition installer with compliance features has an issue with any ECMAPI version greater than 1.0.26.
Problem:
GCMH Acquisition installer with compliance features has an issue withany ECMAPI version greater than 1.0.26. A new hotfix was introduced by the ECM group and the GCMS Acq fails to work with the new version.
Temporary Solution:
A point patch is available for MassHunter GCMS Acquisition B.07.03 when using ECM 3.4.1 SP2 Hotfix 1.
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
Any vial position 2-16 on rear tower 7693N is causing 6890N GC to halt.
Problem:
Any vial position 2-16 on rear tower 7693N is causing 6890N GC to halt. If Vial 1 from the rear tower is injected it will work fine. This deffect will only show on 6890N with both conditions: - No autotray - Different front and rear turrets
Temporary Solution:
Point Patch available. Please refer to SN regarding B.07.03.
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
Sequence won't be aborted on GCMS Acquisition with sequence action set to abort when barcodes mismatch.
Problem:
1. Create a method with HeadSpace as Inlet source, single extraction.
2. Create a 5-line sequence, with Line 1 using wrong barcode, Line 2, Line 4-5 with blank barcode and only Line 3 with correct barcode.
3. When running sequence, select "Use barcode and Don't inject;Abort the sequence" for Sequence Barcode Option.
Wrong barcode line and blank barcode lines are skipped but the sequence continues not aborted.
Please refer to the attached "instctl.log".
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
Detector on timed event in acq method causes large spike on 5977
Problem:
Using a timed program event to turn off the detector (filament) after the first peak elutes then turn it back on after the solvent Elutes. However when the detector comes on there is a verylarge spike.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Collected GC signal files (*.CH) cannot be consistently loaded
Problem:
When MassHunter GCMS Acquisition is used to collect signals from GC detectors, the resultant *.CH files may not display properly. This has been traced down to a faulty scaling value placed in the file
Temporary Solution:
Point Patch available. See Service Note G1701-232
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
MH Compliance mode: Running a sequence with external sample configured like Headspace or CTC s will STOP with an error: “input string was in the wrong format”
Problem:
MH Compliance mode: Running a sequence with external sample configured like Headspace or CTC s will STOP with an error: “input string was in the wrong format”
Temporary Solution:
n/a
Fix Information:
This item has been resolved in MassHunter GCMS Acquisition B.07.04
Keyword:
One-line Description:
CTC: could not override injection volume in the sequence table on RSI instrument
Problem:
Set up a method with the 10 ul liq syringe. Injection volume was set to 1. Created a sequence and for the second and third sample, changed injection volume to 2 and 3. Simulate sequence did not pick up any errors. Ran the sequence however, it showed aspirating 1 ul for each sample. The sample_info.xml file under the data file did show the correct injection volume of 2 and 3. Saw similar behavior with the HS syringe. On the RTC, saw the HS override inejction volume work OK. The liq syringe however, would not allow the entry of 2 or 3 in sequence table.
Temporary Solution:
n/a
Fix Information:
Has been resolved in MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
B0703: Backflush Wizard stops with error message while configured for QTOF
Problem:
BackFlush should be working on all of the models, QTOF is not listed in the script to support this feature.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GCMS Acquisition B.07.04.
Keyword:
One-line Description:
MSD: MSD goes offline when try to run method with burnt out filament and override solvent delay
Problem:
Run a method with a burnt out filament and also overriding the solvent delay will cause the system to go offline. System seems to stall and when it "comes back" MS is offline. Using help/reconnect will not reestablish the connection.
Temporary Solution:
Power cycle the MSD and reboot the PC to reestablish the connection with the system.
Fix Information:
n/a
Keyword:
One-line Description:
GC-QTOF Autotune: Detector Gain Problems
Problem:
In EI and PCI modes, the detector gain does not work properly due to emission current adjust issues. The detector gain function SetDetectorGain() calls the emission current adjust function AdjstEmisson(TargetMass, TargetAbundance): the emission current adjustment does not converge, and the emission current thrashes between low and high settings (see attached data). In EI, PCI, and NCI modes, after completion of detector gain, the emission current must be readjusted to restore the base peak abundance of 1.2E6 counts. Currently, the autotune does not readjust the emission current. After the detector gain portion of the autotune completes, the next step in the autotune is Quad Tuning. The emission current must be readjusted so that the abundance is high enough for stable Quad Tuning.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
DQ: Programmatic increment of blank vial upon decision failure of blank does not properly set _alsbottle2 B.07.03 MassHunter Acq
Problem:
When a blank is run and it FAILS, if the current counter indicates to skip to the next blank, only_ALSBOTTLE is incremented, leaving _ALSBOTTLE2 as-is such that it will continuerunning the ‘contaminated’ blank vial. If that vial is truly contaminatedand continues to fail, the decision process will appear to cycle through allthe blank vials when in actuality it keeps running the same one. REARINLET ONLY
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
ECM; When compliance is installed the append keyword still shows up in sequence.
Problem:
Since in compliant mode you can only use 1 method in sequence, however the append keyword still shows up.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
ECM; When Compliance is installed, the usedecisions keyword is still available.
Problem:
In compliance mode decision based sequencing does not work. the usedecision keyword should be removed from sequence
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
SQ; 5977B mini-display or GC LCP do not display error messages of the the single quad.
Problem:
The mini-display and the GC LCP was not designed to report the 5977B error status if one occurs.
Temporary Solution:
User can use the WUI to view the status of the instrument and also to view any error messages.
Fix Information:
n/a
Keyword:
One-line Description:
Drug Quant will not automatically upload data to ECM during sequence for B.07.03 & B.07.04 (Drug mode only)
Problem:
The ECM datafile upload brakes during a Drug Mode sequence in B.07.03 - Repaired in the attached nticrunmeth.mac file, which goes to GCMS\MSEXE folder (for B.07.03)
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
The name of the Quant batch doesn’t always reset when you start another sequence (for B.07.03 & B.07.04)
Problem:
The NAME of the MH Quant Batch created during automation in Drug Mode is not reset. The new batch will have the same TimeStamp in the the datapath as the previous one - Repaired in the attached startseq.mac, which goes to GCMS\DRUGMACS folder (for B.07.03 and B.07.04) The ECM Quant batch files with space in the names could not be handled by MH Quant Actions script - Repaired in the attached SendToOpenLabECM.quant.script
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
ECM; Lock and Switch user does not track the users authorization level correctly.
Problem:
Logged into the system as a manager and have full access. Then switching from the manager level to the Analyst 1 level using the LOCK and SWITCH. This part is fine, however the access for the Analyst 1 is still at the Manger level.
Temporary Solution:
Log out of instrument control and then log back in with the correct user name if the levels are different.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
MSD; MassHunter Acq B.07.04 has wrong time stamp format so Quant and Qual cannot read it.
Problem:
Current format of TuneFileTime$, and what is written intosample_info.xml:
Monday, January 04, 2016 10:50:53 AM (UTC-05:00)
What is needed in sample_info.xml : 2016-01-04T10:50:53-05:00
Temporary Solution:
Point patch macro is available for this.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
SQ; Inlet Location "Rear" not enable in manual injection (MassHunter Acq)
Problem:
When you try to select Inlet Location "Rear" in manual injection mode, this results to be not enable, only front location is available. Is not possible to make a manual injection in rear location.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
ECM, Password creation for the MassHunter Acquisition looks for a maximum of 12 characters.
Problem:
MassHunter Acquisition has a maximum of 12 characters for the password.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
5977B HES seed values (default starting point) for the HES Tune could cause poor peak shapes.
Problem:
Some units don’t tune very well with the default HES tune values. Peak shapes are not ideal or are very bad. However, they can be manually tuned and they look good. However, customers would need to get a new default tune file with the new seed values otherwise they would risk having poor looking peak shapes or poor tunes.
Temporary Solution:
Point Patch is available for this issue with File Name atune7x.mac. Prior to replace or copy the atune7x.mac in your GCMS\MSEXE make sure to rename the original file with extension .ORG.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
QTOF Firmware 022 getting mid mirror and DC Post Filter Faults
Problem:
Was running the system on B.07.02 with version G7200.01.21 and there is no problem with the system. Loaded software B.07.04 with version G7200.01.22 and there is a problem with the system generating mid mirror faults and also DC Post Filter error messages and causing the system to shut down.
Temporary Solution:
Reflash the firmware with G7000.01.21 and then reflash again with firmware version G7000.01.22.
Fix Information:
n/a
Keyword:
One-line Description:
QTOF; Advanced Autotune 'Set EDR' run time information is not shown
Problem:
Each of the advanced autotune buttons should show how long that step takes to run in an information line of text below the buttons when the mouse is over the button. The 'Set EDR' button does not update this information when the mouse cursor is over the button.
Temporary Solution:
The text for Set EDR should be 'Set EDR takes approximately 1.0 minute to run'.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
QTOF Advanced autotune detector 'Gain' and 'Set EDR' leave the emission current set to 50 uA.
Problem:
The 'Gain' and 'Set EDR' advanced autotune functions set the emission for ion 264 or 130. Both of these should have no or very low signal, so the emission ends up of the autotune max limit of 50. This is OK for setting the gain but is too high for normal operation. The expected value for emission is around 5 uA. the gain and set EDR functions should save the existing emission current and restore it when they are finishing.
Temporary Solution:
Go to manual tune and restore the emission setting.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
QTOF advanced autotune 'Set EDR' calls wrong function
Problem:
The 'Set EDR' is calling the SetDetectorGain function. This can be checked by setting the 4GHz high resolution mode in the manual tune acquisition parameters tab. When the Set EDR is done the acquisition mode should be 2GHz EDR. The detector parameters should also be updated. .
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
QTOF: There are issues with N2OFF tune with bad final PMT value
Problem:
There is a combination of effects which is occuring. At the end of the gain calibration, there is a limit check for the PMT and emission current which is not being rechecked and as a result at times the calculated PMT and emission current values are incorrect which are then saved to the tune file.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
MSD; MassHunter Acquisition Software can't open in 7890B/5977 with 3rd party Gerstel TDS inlet.
Problem:
The error MSINSTLR.exe appear when Gerstel software is loaded on MassHunter Acquisition B.07.03 and B.07.04. [This problem is related to the 3rd Party software.]
Temporary Solution:
Downgrade to B.07.01, Acq Softwre is working well.
Fix Information:
n/a
Keyword:
One-line Description:
SQ; unable to run FID only method and MS only method in same sequence
Problem:
Investigated the MassHunter error generation, tried the following isolating the hardware as requested.
GC Manual, GC/MS Manual, GCCTC and GCMS-CTC all running the customers FID.M without incident.
The problem was only observed when running a sequence which included both the FID.M and GCMS.M in the same table. Starting with the MS.m the injection ran fine, 2nd line the FID.M loaded ok the CTC made the injection and the run started and the real time display appeared normal with the FID plot observed no problem. The 3 rd line CTC made the injection cycle complete to home position, the GC hardware went into run, MH SW did not start run time and created the errors found as in the previous cases. (errors already posted on this site ). Also both the FID.M runs from lines 1 and 2 had no data files generated in the sequence folder, no data collection even for line 2 of the sequence which appeared to be normal.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
QQQ; GCMS Autotune Report Time Issue, showing current local time as well as the UTC time on the tune report
Problem:
Autotune Report for TQ is having 4 hours time difference between the Tune Date & Time and the Reported Time. Upon investigation, there are two times being reported: the time the tune was done and the time the report was printed. The issue is that one of the times is showing the current local time which the other time is showing the UTC.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
QTOF, PMT value from autotune is greater than 1100V which should be the maximum value
Problem:
At the beginning of the autotune the PMT could be in the 860-900 range but at the end of the autotune one could see values in the 20,000+ range. This is also a gasoff tune.
Temporary Solution:
Manually go and enter in valid entries for the PMT and use the Advance Autotune functions.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
MSD: Not Ready Status turn on in 7890GC after injection due to "MS is not ready"
Problem:
In 7890B/5977B (LVDS) with MassHunter Acq B.07.04, GC front panel Not Ready status turn on after injection due to "MS is not ready".
STATUS - Not Ready
Run in progress
Host system not ready
MSD is not ready
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
TQ: Fast Scan doesn't work properly for TQ MS2 fast scan only, MRM+ fast scan and SIM+ fast scan
Problem:
The features of Fast Scan does not work properly for these three modes
(MS2): fast scan only,
MRM+ fast scan and
SIM+ fast scan.
The peak 272 from OFN could be missed. The part of MRM and SIM in mix-mode is functionally correct, but the part of fast scan in mix-mode is missing the peak.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: _secExpbarcode$ not being stored properly in B.07.04.
Problem:
The expected bar code reading was not being sent back correctly when using dual injection.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
TQ: large difference of scan speed for MS2 regular scan between calculaton and actual values for ms range > 800 amu
Problem:
For regular scan (MS2), the value calculated from the settings in Method Editor has large difference (> 20%) from the actual value based on the acquired data file for scam mass range > 800 amu; while the same comparison for the values for scan mass range < 700 amu has only <5% difference.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
7650 Tower is not working properly, other towers are when varying the injection volumes.
Problem:
MassHunter GC/MS Acquisition is detecting that the 7650 tower is connected however it is reading the tower as the wrong type. Standard injection volumes are possible but using fractions of a microliter injection is not possible.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
MSD: Sequence Table Editor (STE) Does Not Warn User if Quant Method is Not Found.
Problem:
GCMS Acq in Drug Mode with Quant in Drug Mode. Performed Intelligent Sequencing. In the Sequence Table Editor, the DA Method File location was pointing to the wrong location. There is no warning message to inform the user that the Quant method is not in the correction. The system will check for the acquisition methods.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MS does not establish communication after VENT
Problem:
Shutting down GC & MS for maintenance, using "VENT" for MS. Power OFF both instrument. On start-up, the MS shows no communication established. User is forced to close out GCMS acquisition and do a hard reboot of the systems to recover the system.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
ECM: user can switch methods during a sequence but system is mixed up after doing so.
Problem:
The sequence was paused during the run and then loaded another method and continued with the same sequence log file. The sequence log file did show the method was being switched. The log file states that there was a fatal error and then it stopped after the end of the second data file was acquired.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
MSD: For 5977 diffusion pump systems the Ion gauge does not turned off during vent cycle
Problem:
Only on a diffusion system, If ion gauge is on and the vent cycle is initiated from tune and vacuum control, the ion gauge does not automatically turn off. On a turbo system the ion gauge goes to "OFF" immediately after clicking on the vent button as expected. It was noticed that the gauge becomes "hot" during vent cycle on the diffusion system. This could result in a premature hardware failure of the ion gauge only on ion diffusion pump systems.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
MSD: It is possible to EDIT the sequence table MULTIPLE times with multiple screens remaining.
Problem:
While running a sequence if you edit the sequence table by mistake multiple times it will result in multiple versions of the sequence table being displayed.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
JPN: report; unnecessarily prints an extra white page always print our for JPN dMRM Method parameter report.
Problem:
1. load dMRM method. (Y_dMRM.M.zip) 2. Method > Print Method (select all check box) 3. report is created. 4. dMRM method report always has unnecessarily extra white page
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
MH with ECM: Retrieve a data file will add an extra subdirectory
Problem:
If you retrieve a data file from the ECM server it will add an extra subdirectory.
Selecting the data file and asked to "Unzip *.SSIZIP files as subfolders."
The result was the following, the *.d directory got produced two times.
\example.d
\example.d
all the files
Temporary Solution:
NOTE: this does NOT CHANGE .D.SSIZIP (and .m, too) FILES THAT RESIDE ON THE ECM SERVER IF THEY WERE UPLOADED BY BRONCO B.07.04 OR EARLIER. there is a new macro command called NoZipNest that can be used to change the way folders are zipped prior to upload to the ECM server. Users may type "NoZIpNest" in the command field of Bronco, followed by either the 'enter' key or 'execute' button. After that, files will be zipped such that the ECM 'retrieve with unzip' will no longer create nested folders. To revert back, type "NoZipNest 0". NOTE 2: methods and data that are zipped with this new structure CANNOT BE RETRIEVED USING MSD CHEMSTATION DATA ANALYSIS 'LOAD FROM ECM' unless a patch is installed. I have attached that patch to this defect. The patch serves to indicate how trivial it is to determine if there is or is not a nested folder in the unzipped file. I strongly encourage the 'unzip' action provided by the ECM Client be updated to determine the existence of the 'nested' structure and handle it accordingly. NOTE 3: existing customers can retrieve from ECM WITHOUT using the 'unzip' feature, and then use WinZip to extract the files - NO NESTING WILL RESULT.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
QQQ: Changing MS IP gets SmartCard NotConfig error
Problem:
The test processes: Do not open MassHunter GC/MS Acquisition MS Configure. Open Web User Interface (WUI); Change MS IP in WUI-NetConfig from 192.168.254.12 to 192.168.254.10 Power cycle MS, The MS IP showing on LUI of MS is updated correctly to new IP; Configure instrument with new IP, then launch Instrument Control; Instrument Control starts up properly. Check WUI (regardless Instrument Control is opened or closed) , on Status panel, Smartcard section, IP Address N.A.=getNetworkConfig ERROR-2 Click button "Return to Main Menu", get ERROR 404
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Configure MS Gases Info Does Not Appear In Audit Trail
Problem:
Startup an instrument configured for JetClean, the Configure MS Gases Automatically appears. When You Select Ok, this generates a Method Save. Looking in the Audit trail, there is no documentation of the save.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
Simulate sequence did not work if one of the lines has an invalid method or no method specified
Problem:
Created a sequence that had some errors and one of them was a missing method name or invalid method name (also had duplicate data file name). OK'd sequence table and saved sequence. Selected Simulate sequence. Received an error Input string was not in correct format on the message line.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MassHunter in Compliance mode: Not possible to change methods within a sequence
Problem:
The sequence table editor (STE) has a limitation of only one method can be used for MassHunter in Compliance mode. The STE does not have the method option to be used in the Compliance mode of operation.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
MSD: Leaving the Secured Control Panel open for a period of time could cause the system to lockup.
Problem:
Leaving the secured control mode up and idle in "Standby" mode overnight could cause the system to lockup. Just closing the application is not applicable, one will need to use the task manager to close the application.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05.
Keyword:
One-line Description:
TQ: PDF auto tune file not generated due to missing templates
Problem:
If a ChemStation/Workstation has an earlier version of MassHunter GC/MS Acquisition software loaded it is possible not all of the templates will be copied over. While tuning the MS the following message "an exception has occurred saving an autotune report as a PDF file..."
Temporary Solution:
For service updates and point patch updates loading on top of an existing software version is okay, however when changing from one revision to another, it is recommended to uninstall the existing version and then install the new software package.
Fix Information:
n/a
Keyword:
One-line Description:
TQ: When using dMRM the precursor ions shown in Qualitative analysis do not reflect the ions specified in acquisition method for methods created on previous revisions of acquisition.
Problem:
Setting up the dMRM acquisition and running the data. Looking in acquisition the precursor ion and the product ions look good. When you look at the data in qual the precusor ions do not match up with the ones in the data acquisition. the precusor ions are less than the product ions. This has shown up on existing methods and not on newly created methods.
Temporary Solution:
A point patch is available for this. Please contact your local representative for the patch.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05 SR1.
Keyword:
One-line Description:
TQ: When more than 4 MRM scans were defined for a time segment an error is displayed that 4 MRM scans is the limit. The correct limit is 100 MRM scans per time segment.
Problem:
User is given a warning about One can ONLY have 4 MRM scans in a time segment; but it is possible to have 100 scans.
Temporary Solution:
A point patch is available for this. Please contact your local group for additional information.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05 SR1.
Keyword:
One-line Description:
TQ: dsp 5.1 firmware fault which then clears almost immediately, this has shown up for the B.07.05 ONLY release, not in previous versions.
Problem:
Run with collision energy default set to 10 eV, then while it is running change the collision energy to 20eV, then back again to 10eV When you hit enter after changing the collision energy, the status at the bottom reflects a dsp 5.1 firmware fault which then clears almost immediately. Since the fault clears, the end result is still achievable.
Temporary Solution:
If this was an actual error message was real, then no data will be collected.
Fix Information:
n/a
Keyword:
One-line Description:
Wiley Library: Wrong Compound information of CAS No 120-61-6 in Wiley10Nist14.L and Wiley10Nist11.L
Problem:
CAS No 120-61-6 in Wiley10Nist14.L, hit to 1,4-Benzenedicarboxylic acid, dimethyl ester. But the spectrum and MW and Formula are wrong. As the result, MW = 189.1 and Formular C7H11NO5, but the correct result is MW = 194.1, Formula C10H10O4. And the structure is also wrong. Wiley10Nist11 and Wiley10Nist14 have wrong information. Nist2014 and Wiley9Nist11 have correct information.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Data System: Remoting Subsystem Error during startup of MassHunter Acquisition if Computer Name is Numeric only
Problem:
This error occurs on Acquisition startup if the computer name is numeric. Error: "An error has occurred initializing the MassHunter GC/MS Acquisition Remoting Subsystem: The requested name is valid, but no data of the requested type was found. Please close MassHunter GC/MS Acquisition and ensure all msinsctl.exe processes have been killed, or alternatively reboot your system and then restart MassHunter GC/MS Acquisition"
Temporary Solution:
Changing the computer name to alpha-numeric causes this error to go away.
Fix Information:
n/a
Keyword:
One-line Description:
TQ: The unit for dwell time in MRM mode or SIM mode in MH Acq B.07.05 should be seconds but is displayed as msec.
Problem:
In MassHunter GC/MS Acq B.07.05, MS method editor design has changed. Dwell time unit is msec in SIM or MRM mode; labels are showing incorrect units to be used. But Dwell time unit is sec in MassHunter GC/MS Acq B.07.05.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05 SR1.
Keyword:
One-line Description:
SQ: An injection time set longer than solvent delay results in no data being collected.
Problem:
When injection time is longer than solvent delay results in no data collection.
Temporary Solution:
Make sure that solvent delay is longer than injection time. Alternative fix: set a short solvent delay and then add a timed event to MS params to turn filament off for the "real" solvent delay. AEG
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05 SR1.
Keyword:
One-line Description:
HS with 9000 GC, Inlet Injection Parameters panel has a rear option
Problem:
MassHunter GC/MS Acquisition B.07.05 with Headspace B.01.07.2. Configured with a 9000 GC instrument with a 7697 or G1888. Went into the Inlet Injection Parameters panel and selected Headspace as the injection source. Both Front and Rear Inlet locations were available, it should only be Front.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Sequence table: The Rear Sample _miscinfo$ field is not retained when running in Unlinked mode.
Problem:
The front sample is receiving the Rear Sample’s miscinfo$ (i.e. comment in STE), and the rear sample ends up with NO _miscinfo$. This happens with gc and gcms configurations using unlinked mode.
Temporary Solution:
n/a
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05 SR1.
Keyword:
One-line Description:
TQ: Calibration valve on/off status will not update until the user changes window focus to a tab other than manual tune.
Problem:
In Manual Tune tab, when the CI cal valve is checked On, the status stays Off. If you move to any tab other than Manual Tune, the status changes to On. The same applies going in the opposite direction (status from On to Off).
Temporary Solution:
User needs to move to another field to display updates.
Fix Information:
This has been resolved in released version MassHunter GC/MS Acquisition B.07.05 SR1.
Keyword:
One-line Description:
6890 GC detector signal naming problem with Masshunter Acq B.07.05
Problem:
When a GC detector signal is collected for 6890 the signal name for a front detector is front detector.ch and back detector.ch for the rear detector. This is counter to the tradition of naming based on detector type (ie, FID1a.ch for a front signal.) This problem has already been corrected (a fixed GCRC.dll was created). The solution has been tested but no TT entry had been made.
Temporary Solution:
n/a
Fix Information:
n/a