Software Status Bulletin
GC/LC/CE CHEMSTATION G2070AA
Known Problem Report as of Mar 1 2010 2:49PM
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
'System Off' button changes method on the 1046 FLD
KPR#:342
Stars SCR#: 1653178376
Mixed 1050 and HP1100 system does not calculate k'
KPR#:785
Stars SCR#: 1653293316
Running User Contributed Macro #10, INJSTEP MAC on 1050: Close crashes
KPR#:917
Stars SCR#: 5003309773
Injector Program 1050
KPR#:1143
Stars SCR#: B400102079
A/D and 1050 system can not be used with 2 instrument sessions
KPR#:1749
Stars SCR#: B400109819
Oven Not Ready message disappears after another Not Ready event occured
KPR#:55
Stars SCR#: 1653120550
HP 1090 gradient method not executed if solvent channel switched off
KPR#:144
Stars SCR#: 1653135327
1090 DAD online plot: low resolution of the online plot
KPR#:295
Stars SCR#: 1653171330
LC1090: Balancing in online plot doesn't go to zeroline
KPR#:648
Stars SCR#: 1653256495
%B signal shows only gradient definition - not what pump really does
KPR#:1116
Stars SCR#: B400100578
Working with the HP 79880 DAD (HP 1040, HP 1090 DAD)
KPR#:1173
Stars SCR#: B400102566
system hangs if 1040 DAD peakwidth=10 min and runtime < 10 min
KPR#:1532
Stars SCR#: B400106906
Error message POST_MESSAGE failed when closing ChemStation
KPR#:1760
Stars SCR#: B400109942
1100 LC system does not show status of 1046 FLD if connected.
KPR#:283
Stars SCR#: 1653169086
HP1100: System exception 8009 in seqeng.c / GPF IN HPCP00.DLL
KPR#:423
Stars SCR#: 1653193896
WL accuracy check does not use method IVWLACC, but loads method IVNOISE
KPR#:445
Stars SCR#: 1653200048
HP 1100: Adding gradient step during run is executed instantaneously
KPR#:493
Stars SCR#: 1653217711
Gradient test of OQ/PV procedures failed
KPR#:608
Stars SCR#: 1653245860
Generating a sequence with blank injections not possible
KPR#:696
Stars SCR#: 1653267385
What error method is used on a HP1100 system with ChemStation
KPR#:722
Stars SCR#: 1653272518
HP 1100 DAD wavelength accuracy test fails with 2D ChemStation
KPR#:730
Stars SCR#: 1653275594
wrong concentration 25ug/mL should be 5 ug/ml.
KPR#:758
Stars SCR#: 1653285312
HP1100 RID: Autom. zero and purge do not work in certain configurations
KPR#:812
Stars SCR#: 1653306175
HP1100 RID and 1090 LC: Not possible doing purge before analysis
KPR#:826
Stars SCR#: 1653309377
OQ/PV testresult for injector precision / caryover can be negative
KPR#:830
Stars SCR#: 1653309542
1100: Multi-gradients created off line, don't import to online instance.
KPR#:979
Stars SCR#: 5003343244
Holmium Oxide Test Results Window Inactive
KPR#:1427
Stars SCR#: B400105692
DAD Wavelength Calibration Data from Control Module Ignored
KPR#:1428
Stars SCR#: B400105700
HP1100 OQ/PV Noise/Drift with DAD+VWD installed allows 1 set of limits
KPR#:1640
Stars SCR#: B400108233
Multiple rows with the same time for the FLD time table do not work
KPR#:1710
Stars SCR#: B400109272
DIAGNOSIS: thermostat test is not stopped if no HP 1100 pump is config.
KPR#:1761
Stars SCR#: B400109959
On line spectra wavelength display does not match stored spectra WL
KPR#:1793
Stars SCR#: B400110775
1100 bottle filling: pump status in GUI does not reflect not ready condition
KPR#:1861
Stars SCR#: n/a
pressure set to "setpoint" in the online plot of LC cs rev.A.09.01
KPR#:2231
Stars SCR#: n/a
Fraction Collector: Upslope and downslope are not working
KPR#:2239
Stars SCR#: n/a
Signal change in LC Detector during a run
KPR#:2320
Stars SCR#: n/a
two MWD in one instrument: problem to control MWD 2 via GUI
KPR#:2493
Stars SCR#: n/a
Online and Offline method print out not the same
KPR#:2541
Stars SCR#: n/a
Using flow gradients during Fraction Collection results in Wrong times in Report
KPR#:2556
Stars SCR#: n/a
Inconsistent Valve Order in ChemStation Configuration
KPR#:2568
Stars SCR#: n/a
incorrect injection time stamps on report
KPR#:2594
Stars SCR#: n/a
The menu task "Instrument" has no submenu to configure a 35900.
KPR#:705
Stars SCR#: 1653269233
F1 Help doesn't work for ADC Dialog Box
KPR#:1150
Stars SCR#: B400102145
35900E: Status box does not reflect actual events.
KPR#:1350
Stars SCR#: B400104901
35900E status window does not indicate postrun mode during data analysis
KPR#:1359
Stars SCR#: B400104992
Pres/Flow box is incorrect during a run when channel is not linked
KPR#:1187
Stars SCR#: B400102780
Inlet grayed out in Packed Column when linked to non-existent channel
KPR#:1189
Stars SCR#: B400102806
5890 GC: Software can only invert TCD polarity ONCE during the run.
KPR#:2055
Stars SCR#: n/a
In 6890 it is not possible to "de-install" a column from the software.
KPR#:187
Stars SCR#: 1653143214
6890 GC: Intrument Actuals stay at "0" instead of true value. Cosmetic!
KPR#:368
Stars SCR#: 1653185520
6890: Extd/Perf report overprints when full column information entered.
KPR#:403
Stars SCR#: 1653189753
It is possible to set runtime events past the end of the real runtime.
KPR#:1232
Stars SCR#: B400103283
The runtime stops counting on 6890 GC intermittently. All data is good.
KPR#:1270
Stars SCR#: B400103770
It is possible to get the GC/software confused about run time (6890)
KPR#:1301
Stars SCR#: B400104331
6890 Logbook entries are trunkated at 46 characters, information lost.
KPR#:1354
Stars SCR#: B400104943
6890 GC: Real time plot does not show correct values after event switch.
KPR#:1369
Stars SCR#: B400105106
6890, the online signal toolset is enabled in the offline session.
KPR#:1501
Stars SCR#: B400106443
6890 sequence/method toolset button is grayed out in error.
KPR#:1508
Stars SCR#: B400106518
6890 GC with fast oven will not run the on line tutorial correctly.
KPR#:1537
Stars SCR#: B400106955
6890 GC: HP Core has caused a GPF in module TBPO3W.DLL at 0001:302B
KPR#:1587
Stars SCR#: B400107607
6890: Syntax Error when sending setpoints to the GC.
KPR#:1608
Stars SCR#: B400107904
6890: Cannot make automated runs with 6890/35900C/G1512 as single inst.
KPR#:1617
Stars SCR#: B400107995
6890 Syntax Error CCER IFxxVI P3 E14 EN when VI setpoints are changed.
KPR#:1679
Stars SCR#: B400108852
6890: Pressure entered in 6890 software different than value at GC.
KPR#:1691
Stars SCR#: B400109066
6890: Error message "Power off/on detected" intermittently.
KPR#:1715
Stars SCR#: B400109462
6890: Autosampler setpoints may be lost during method resolution.
KPR#:1799
Stars SCR#: B400110866
6890: Tower fan off/on on GC gives wrong info with ChemStation running.
KPR#:1802
Stars SCR#: B400110890
Initialisation Problem ( Please Report to HP) when adding a new column.
KPR#:1840
Stars SCR#: n/a
Companion: Parsing error when using Companion and 6850GC
KPR#:2035
Stars SCR#: n/a
6890 GC: Floating point exception INVALID NUMBER detected.
KPR#:2037
Stars SCR#: n/a
6890: Method resolution needs better explanation in the HELP system.
KPR#:2052
Stars SCR#: n/a
Companion. Cannot SAVE GPL data when running a sequence.
KPR#:2077
Stars SCR#: n/a
6890: Help for FID makeup flow shows invalid options. (Software is correct).
KPR#:2078
Stars SCR#: n/a
6890N: After startup the 6890N time is one hour ahead of the PC time.
KPR#:2185
Stars SCR#: n/a
Error, Vial Number field 1. Value = 101, range (1,100)
KPR#:417
Stars SCR#: 1653193417
7673 abort is unpredictable.
KPR#:1184
Stars SCR#: B400102756
STOP or ABORT have timing windows that can cause problems.
KPR#:1234
Stars SCR#: B400103309
Inj volume in sequence table only uses the syringe size from the front.
KPR#:1320
Stars SCR#: B400104539
G1513A viscosity delay in the MANUAL does not match the real behaviour.
KPR#:1323
Stars SCR#: B400104570
6890 / 7673 with 5 uL syringe injects the wrong volume.
KPR#:1419
Stars SCR#: B400105619
Injector changes may be lost when entered on 6890 keypad.
KPR#:1717
Stars SCR#: B400109496
35900: First (only) session wil not start up after installation.
KPR#:1795
Stars SCR#: B400110791
Online Session Crashed Without HP-IB Card Installed
KPR#:67
Stars SCR#: 1653123000
Elapsed run-time of last run displayed shorter than stop-time
KPR#:294
Stars SCR#: 1653171322
FLD with A.04.03 showed unexpected chromatogram after installing
KPR#:573
Stars SCR#: 1653239178
shift in spectra create incorrect apex spectra
KPR#:2457
Stars SCR#: n/a
Calibration Settings: Activate "Use ISTD"
KPR#:17
Stars SCR#: 1653114280
RT Window Color Bar not updated correctly
KPR#:316
Stars SCR#: 1653173518
Correlation coefficient r from ChemStation not same as in Excel
KPR#:452
Stars SCR#: 1653203786
No. of digits for smpl prm in Calib. setting, seq. tbl, smpl info differ
KPR#:522
Stars SCR#: 1653227579
Wants to specify what recalibration should be reported in a sequence
KPR#:568
Stars SCR#: 1653238402
'CalTabMain parameter 3: a value is outside legal range'
KPR#:821
Stars SCR#: 1653308056
Unknown Error Message, 1 Unknown CP Identifier, 640x480 VGA monitor.
KPR#:915
Stars SCR#: 5003308460
Calculation Formulae used for ISTD recalibrations
KPR#:943
Stars SCR#: 5003325449
Info for amount ratio and area ratio ISTD missing in calibration tbl.
KPR#:983
Stars SCR#: 5003344788
Multi level calibration not possible with Manual calibration table
KPR#:1037
Stars SCR#: 5003393074
Manual calibration table warns for more cal. points
KPR#:1038
Stars SCR#: 5003393082
Compound specific multipliers got set to zero
KPR#:1039
Stars SCR#: 5003393264
Single peak summing table entry is missing in calibration table printout
KPR#:1084
Stars SCR#: 5003447771
There are missing shortcut keys in the "Calibration Settings" dialogbox.
KPR#:1386
Stars SCR#: B400105270
A report after a change in the calibration table contains old values
KPR#:1743
Stars SCR#: B400109751
RT corrections are not used for on-line (no report) peak identification
KPR#:1744
Stars SCR#: B400109769
Calibration table: 'Parameter2: Table was not found'
KPR#:1784
Stars SCR#: B400110445
Reference to ISTD # in calibration table view is not visibly updated
KPR#:1785
Stars SCR#: B400110452
Linear regression using force through origin option is not correct
KPR#:1794
Stars SCR#: B400110783
Printing ISTD calibration table causes error: A value is outside the legal range
KPR#:1813
Stars SCR#: n/a
ISTD calibration: warning message - curve requires more calibration points
KPR#:2029
Stars SCR#: n/a
Settings for Origin Incorrect for "Average Resp/Amt"
KPR#:2144
Stars SCR#: n/a
Calibrated compound found as uncalibrated one using library search report
KPR#:2318
Stars SCR#: n/a
Autobalance option for CE does not appear in the time table
KPR#:1677
Stars SCR#: B400108837
HPCORE caused a GPF in module HPTED01.DLL at 1c:069a
KPR#:1528
Stars SCR#: B400106815
Current, voltage, temperature not available if only DAD signal is loaded
KPR#:1830
Stars SCR#: n/a
Shortage of Global Memory after hours of CE fraction collection
KPR#:1430
Stars SCR#: B400105726
CE: exiting 'Setup injection' dialog box during run sets current to zero
KPR#:1804
Stars SCR#: B400110916
CE-MS: Electropherogram disappears from screen when running sequence.
KPR#:1972
Stars SCR#: n/a
CE system: Pressure are not applied correctly
KPR#:2577
Stars SCR#: n/a
CE: Partial Sequence initializes very slowly directly after loading a method
KPR#:2587
Stars SCR#: n/a
HPCED02 caused a GPF in HPUTIL02.DLL at 000c:0000 0020
KPR#:1425
Stars SCR#: B400105676
Custom Report Designer: Logos in Header/Footer
KPR#:35
Stars SCR#: 1653115063
Error 17923 occurred in Command TabText$ in macro FRPT_PrintDispatcher
KPR#:198
Stars SCR#: 1653146548
Calibration Reports in Customized Reports
KPR#:233
Stars SCR#: 1653153312
Sequence: Customized reports may start with empty lines
KPR#:296
Stars SCR#: 1653171454
Could not execute user defined Macro USR_ Libcompare
KPR#:482
Stars SCR#: 1653212910
Custom Report Layout: missing chromatogram when using autoscale
KPR#:761
Stars SCR#: 1653285619
Custom report uses wrong time format for AM / PM in printout
KPR#:990
Stars SCR#: 5003347583
Adding HP 1100 Column Info in Customized Reports
KPR#:1004
Stars SCR#: 5003364604
Customized Reports, calibration curve not complete
KPR#:1139
Stars SCR#: B400102038
Report template can be removed, although used in a method
KPR#:1157
Stars SCR#: B400102210
Custom Report layout generates extra row of peak Data
KPR#:1265
Stars SCR#: B400103721
Header section of custom report is omitted in sequence summary
KPR#:1949
Stars SCR#: n/a
Custom Reports "Injection Date" and "Injection Time" don't work correctly.
KPR#:1984
Stars SCR#: n/a
Header section from report template is not printed in Sequence summary report
KPR#:2137
Stars SCR#: n/a
Fraction Collector and Report LAyout
KPR#:2421
Stars SCR#: n/a
Report Layout problem with CE ChemStation only.
KPR#:2452
Stars SCR#: n/a
Signal Options: Autoscale
KPR#:16
Stars SCR#: 1653114272
Instrument Curves displayed twice
KPR#:26
Stars SCR#: 1653114421
"Could not open data file" reported on Novell Netware client
KPR#:59
Stars SCR#: 1653121012
Graphics (Overlaid/Fullscale) does not correctly display curves
KPR#:60
Stars SCR#: 1653121053
Chromatogram integrates after a change in the Signal Options
KPR#:117
Stars SCR#: 1653130658
Shoulder Peak Name annotations are missing in the chromatogram
KPR#:130
Stars SCR#: 1653132373
No column is installed: for the selectivity still some values are given
KPR#:208
Stars SCR#: 1653147363
Pick Mode does not work in fullscale
KPR#:235
Stars SCR#: 1653153668
Error message misleading when typing error in "Cust Data Analysis Macro"
KPR#:243
Stars SCR#: 1653157651
Integ Events for removed signal are printed/cannot be removed
KPR#:261
Stars SCR#: 1653163832
Use ranges dont work if data file has large numbers and Y range is small
KPR#:591
Stars SCR#: 1653242180
Data Analysis does not remember the last screen settings.
KPR#:638
Stars SCR#: 1653253328
GPF in HPDOP_00.DLL.
KPR#:684
Stars SCR#: 1653263822
Data files are missing in the batch register file *.b
KPR#:726
Stars SCR#: 1653274795
Output of batch report in XLS format not possible from graphical user interface
KPR#:764
Stars SCR#: 1653286708
Save Window: "This file already exists" when saving multiple files
KPR#:852
Stars SCR#: 5003238808
Data Analysis online interacts with same data analysis manual mode.
KPR#:937
Stars SCR#: 5003321570
Data analysis does not always display ALL of the calibrated peak names.
KPR#:984
Stars SCR#: 5003345272
Upgrade a method to new spectra options not possible
KPR#:1034
Stars SCR#: 5003392241
Incorrect method reported in batch report
KPR#:1091
Stars SCR#: 5003455741
Perform manual calculations for all quantitative report
KPR#:1095
Stars SCR#: 5003457101
Signal Options Dialog ignores invalid range parameters
KPR#:1122
Stars SCR#: B400101865
Modifications in Specify Report zoom out the chromatogram
KPR#:1126
Stars SCR#: B400101907
Changing window width influences displayed peak height
KPR#:1131
Stars SCR#: B400101956
AIA Import: Report to .TXT or .CSV file fails
KPR#:1246
Stars SCR#: B400103424
Unable to select data files: "No datafile selected"
KPR#:1296
Stars SCR#: B400104281
Cannot enter more than one ISTD amount in the sequence table.
KPR#:1406
Stars SCR#: B400105486
In data analysis task list, the tutorial tasks are truncated.
KPR#:1422
Stars SCR#: B400105643
The calibration table is somehow linked to the toolbars.
KPR#:1507
Stars SCR#: B400106500
Library search finds match factor of 1000 for obviously different spec.
KPR#:1592
Stars SCR#: B400107698
Injection time in File->Load Signal->FileInf differs from printed report
KPR#:1595
Stars SCR#: B400107722
Response ranges do not work if scale is set to "Each in Full Scale".
KPR#:1613
Stars SCR#: B400107953
The peak sum table appies to all signals by design.
KPR#:1615
Stars SCR#: B400107979
Statistical moment 0 does not equal peak area
KPR#:1708
Stars SCR#: B400109256
Excel charting capabilities is limited to 10 compounds per method.
KPR#:1721
Stars SCR#: B400109538
ERr. Proc. Run: specified register is already locked during batchreview
KPR#:1806
Stars SCR#: B400111138
Batch review does not display correct calibration level for samples
KPR#:1807
Stars SCR#: B400111146
Annotation might be hidden for overlaid spectra
KPR#:1808
Stars SCR#: B400111161
Uncalibrated peaks at same RT in 2 diff signals ignores the smaller peak
KPR#:1812
Stars SCR#: n/a
Manual setup of calibration table fails
KPR#:1851
Stars SCR#: n/a
Peak summing with non-linear calibration curves
KPR#:1866
Stars SCR#: n/a
File BATCH.B is not installed on the system for a GC ChemStation
KPR#:1869
Stars SCR#: n/a
Strange behavior of combo box in "Add Column to Batch Table" dialog
KPR#:1899
Stars SCR#: n/a
peak summing with multiple signals reports incorrect areas
KPR#:1951
Stars SCR#: n/a
Main peak is not integrated if "advanced baseline" function is activated
KPR#:2068
Stars SCR#: n/a
A.09.01, 'Zoom separate' does not work in Graphics-signal Options.
KPR#:2264
Stars SCR#: n/a
Application error, stack overflow
KPR#:2347
Stars SCR#: n/a
Cannot resize chromatogram after you have resized it to a little box
KPR#:2370
Stars SCR#: n/a
Chemstation Data Analysis Overlay function shows limited signals per window
KPR#:2405
Stars SCR#: n/a
Problem with signal overlay information in A.10.01.
KPR#:2458
Stars SCR#: n/a
Only 35 levels can be recalibrated
KPR#:2528
Stars SCR#: n/a
extended performance Weight % ISTD% gives wrong units.
KPR#:2567
Stars SCR#: n/a
Adding Data Analysis to OQFLUSH.M Runtime Checklist Produces Error -3.42 x10E38
KPR#:2578
Stars SCR#: n/a
importing pascal libraries did not work
KPR#:464
Stars SCR#: 1653208645
Difference in peak start/end for different shoulder modes
KPR#:1429
Stars SCR#: B400105718
Precision of calculation in the ChemStation, differences to Excel calc.
KPR#:1706
Stars SCR#: B400109231
7673 Vs 7683 Autosampler information in method printout
KPR#:2026
Stars SCR#: n/a
different description G1362A in ChemStation and Reference manual
KPR#:2453
Stars SCR#: n/a
Print Method: 'Det.A-Comp1' truncated in report
KPR#:232
Stars SCR#: 1653152900
Possible to damage column in dual column operation.
KPR#:439
Stars SCR#: 1653199141
The date format for a 6890 and 5890 in a report are different.
KPR#:461
Stars SCR#: 1653207837
Parameters not listed correctly for Aux channel in method print
KPR#:1193
Stars SCR#: B400102848
It is possible to set the flows to zero and damage a NP bead.
KPR#:1228
Stars SCR#: B400103242
6890 GC:- Error #98: Could not Login on network
KPR#:1299
Stars SCR#: B400104315
6890 ONLY: With manual FID, the ChemStation does not turn on the air.
KPR#:1321
Stars SCR#: B400104547
5890 GC:You can start run (with acquisition on) and no instrument.
KPR#:1360
Stars SCR#: B400105007
6890: In the Edit Column ID table, there are no cut / paste buttons.
KPR#:1483
Stars SCR#: B400106260
HP 6890: Firmware revision A.03.05 is needed for LAN control.
KPR#:1738
Stars SCR#: B400109702
5890: Change column diameter is not saved with method.
KPR#:2056
Stars SCR#: n/a
Time stamp errors in LC Chemstation & Chemstore, Win 2000 time format ignored.
KPR#:2349
Stars SCR#: n/a
Error 17923 - Parameter 3: A value is outside the legal range
KPR#:2527
Stars SCR#: n/a
Displaying method in control module prevents other meth download during seq
KPR#:2586
Stars SCR#: n/a
Second Signal Handling in the Run Time Checklist
KPR#:101
Stars SCR#: 1653129213
Method Printout: Signal Descriptions are confusing (mixed up?).
KPR#:135
Stars SCR#: 1653133322
In the RID control dialog box there is no help available
KPR#:827
Stars SCR#: 1653309385
Wrong online help text on retention time limits (calibration table)
KPR#:1080
Stars SCR#: 5003445288
Exportspectrum cmd can not export to JCAMP-DX format in LC ChemStation
KPR#:1093
Stars SCR#: 5003456855
Syntax of "ExportSpectrum" command in Help Text wrong
KPR#:1098
Stars SCR#: 5003457184
HELP/COMMANDS: Incorrect variable for GENERATE ERROR
KPR#:1100
Stars SCR#: 5003457366
Help system does not function when the system resources are low.
KPR#:1451
Stars SCR#: B400105940
f1, HELP, does not always display the associated HELP topic.
KPR#:1454
Stars SCR#: B400105973
The HELP file is difficult to use when looking for command examples.
KPR#:1475
Stars SCR#: B400106187
Any open HELP window does not close when the ChemStation is closed.
KPR#:1482
Stars SCR#: B400106252
HELP in the LOGBOOK is inconsistent and sometimes wrong.
KPR#:1504
Stars SCR#: B400106476
Items of batch review report items are not all described in help text
KPR#:1741
Stars SCR#: B400109736
Installation Verification displays an empty window
KPR#:1811
Stars SCR#: B400111260
GLP data register can be overwritten
KPR#:1916
Stars SCR#: n/a
RID Control help file link is missing
KPR#:1953
Stars SCR#: n/a
Calibration using force through origin described incorrect
KPR#:1960
Stars SCR#: n/a
SCHEDULER. Spelling mistakes in the Help file.
KPR#:2090
Stars SCR#: n/a
Online Help: Sequence Summary Parameters
KPR#:2127
Stars SCR#: n/a
No display of Help topic for Sample Purity Options panel
KPR#:2371
Stars SCR#: n/a
ChemStation invisible or an icon after start
KPR#:318
Stars SCR#: 1653173880
hpcore caused a gpf in module isoapg.dll at 0003:0561, config. editor
KPR#:492
Stars SCR#: 1653217521
ChemStation path can not be found after installation
KPR#:521
Stars SCR#: 1653227397
Instruments two doesn't start up when the Icon is in "STARTUP GROUP".
KPR#:1302
Stars SCR#: B400104349
Hangup during initialization of multiple instances
KPR#:1426
Stars SCR#: B400105684
82341C: Windows Fatal Exception 0D when the HP-IB board is accesses.
KPR#:1616
Stars SCR#: B400107987
Problems with leading zero in IP address when configuring instr. on LAN.
KPR#:1718
Stars SCR#: B400109504
GPF in PLICOP.DLL during simultaneous startup of 2 online ChemStations
KPR#:1722
Stars SCR#: B400109546
LAN communication: General Protection Fault in PLICOP.DLL at 2:512a
KPR#:1737
Stars SCR#: B400109694
Opening Reprocessing copy opens also C:\WINNT\System32\CMD.exe
KPR#:2336
Stars SCR#: n/a
Autostart macro failed, error 41297 occured
KPR#:2565
Stars SCR#: n/a
Install Data Analysis only over G2170AA: PCS section is overwritten
KPR#:28
Stars SCR#: 1653114447
Installation fails if network drive is not mapped in Win95
KPR#:367
Stars SCR#: 1653185512
Data anal.module (G2090AA) can not be upgraded from A.04.01 to A.04.02
KPR#:431
Stars SCR#: 1653196287
Startup: Creation of SysVars for HPPROD00.DLL failed,Error Code=260
KPR#:523
Stars SCR#: 1653227736
G2077AA License Number not valid for installation
KPR#:528
Stars SCR#: 1653228767
Error message Can not open c:\hpchem\core\hpcore.exe, but path is set
KPR#:585
Stars SCR#: 1653240507
install.log file changed even if update not performed
KPR#:590
Stars SCR#: 1653242115
Time attribute on installed version is different for CD
KPR#:604
Stars SCR#: 1653244830
After installing a patch on a ChemStation installation, IQ fails
KPR#:609
Stars SCR#: 1653246330
Update to A.05.04 does not work, stops responing with no error message
KPR#:614
Stars SCR#: 1653246397
Client server installation fails with \\client\core\disk8 not found
KPR#:724
Stars SCR#: 1653273334
Bootp server does not automatically start
KPR#:832
Stars SCR#: 1653310151
G209xAA cannot be installed from the A.05.01 CD ROM.
KPR#:1027
Stars SCR#: 5003389072
Cannot install 4th instrument if it is a 35900(LC type), GC type works.
KPR#:1040
Stars SCR#: 5003394387
35900D ROM address space not excluded in system.ini
KPR#:1162
Stars SCR#: B400102269
No warning given when installing over existing directory.
KPR#:1439
Stars SCR#: B400105817
Installation of additional GCs creates extra WIN 95 task bar items.
KPR#:1506
Stars SCR#: B400106492
Co-execution with the UV/Vis ChemStation A.02.04
KPR#:1515
Stars SCR#: B400106609
Cannot find HPNLS01.DLL
KPR#:1531
Stars SCR#: B400106898
Intermittent "General Protection Fault in INST20" during installation.
KPR#:1620
Stars SCR#: B400108027
Installation qualification reports wrong data of ref. files
KPR#:1630
Stars SCR#: B400108134
Instalation qualification failes with Cooled autosampler and CE instrume
KPR#:1644
Stars SCR#: B400108274
"Config HP-IB Card" is displayed during install of Data Analysis Only SW
KPR#:1733
Stars SCR#: B400109652
G2730AA LC/MS DA product changed to G2190AA LC 3D if reinstalling S/W
KPR#:1788
Stars SCR#: B400110494
35900 - LOADTEST.M method is not loaded for the 35900 A/D module.
KPR#:2044
Stars SCR#: n/a
Information during installation needs updating.
KPR#:2060
Stars SCR#: n/a
Installed two A/D licences, one instrument appears
KPR#:2386
Stars SCR#: n/a
Manual Integration Events not Visible in Events Table
KPR#:38
Stars SCR#: 1653115238
Solvent peak integration very sensitive to integration parameters
KPR#:323
Stars SCR#: 1653175216
Edit Entire Method: "MWD Default" integration events table
KPR#:360
Stars SCR#: 1653183020
Baseline construction for two adjacent solvent peaks incorrect
KPR#:451
Stars SCR#: 1653202408
Standard integration: do not remove the default integr events table.
KPR#:687
Stars SCR#: 1653266197
Integration results (enh. integ.) may differ between A.04.xx and A.06.01
KPR#:753
Stars SCR#: 1653284075
Initial area reject affects manual integration, peaks are not integrated
KPR#:1041
Stars SCR#: 5003397836
Manual integration of chromatograms extrcated from isoplot causes error
KPR#:1045
Stars SCR#: 5003402255
Edit Integration Events box has missing accelerator keys.
KPR#:1437
Stars SCR#: B400105791
DerivObj causes manual baseline on display to jump
KPR#:1624
Stars SCR#: B400108068
Integrator reports peaks with hight, width = zero, independent of params
KPR#:1669
Stars SCR#: B400108753
Manual integration does not produce same area as "Genie" integrator.
KPR#:1678
Stars SCR#: B400108845
Tangent Skim Mode value not printed in method printout.
KPR#:1720
Stars SCR#: B400109520
Wrong peak height calculated for extremly unsymmetrical peaks
KPR#:1843
Stars SCR#: n/a
Incorrect integration results on trace substance peaks using Split Peak Event
KPR#:2392
Stars SCR#: n/a
Deletion of tangent skimmed front peak may cause inconsistent results
KPR#:2593
Stars SCR#: n/a
Isoabsorbance Plot: floating point exception DIVIDE by ZERO detected
KPR#:99
Stars SCR#: 1653129197
IsoAbsorbance Plot: Contour Line Printout Printed With Wrong Scale
KPR#:107
Stars SCR#: 1653129270
Very large UV-files cannot be loaded into isoplot
KPR#:1078
Stars SCR#: 5003445155
1049A ECD displayed signal.
KPR#:267
Stars SCR#: 1653164764
Prevent analysis... option in Solvent Bottles filling Screen inactive
KPR#:526
Stars SCR#: 1653228221
Injection volume not printed after data acquisition
KPR#:562
Stars SCR#: 1653236901
Printing of method does not include ALS temperature
KPR#:626
Stars SCR#: 1653250555
HP1100 VWD dark current test does not work
KPR#:695
Stars SCR#: 1653267344
ECD 1049 does not start from scheduler
KPR#:1590
Stars SCR#: B400107664
Save GLP data without standard data analysis - error message in logbook
KPR#:1050
Stars SCR#: 5003408559
The logbook entries are listed in the wrong order.
KPR#:1342
Stars SCR#: B400104828
System Exception 200 in lbkproc.c at 742. Please report to HP.
KPR#:1496
Stars SCR#: B400106393
Sequence logbook is inconsistent and confusing.
KPR#:1500
Stars SCR#: B400106435
A.08.03: Sample name is not correct in logbooks.
KPR#:2109
Stars SCR#: n/a
Load GLP Method: Method Modifications in current method are lost
KPR#:149
Stars SCR#: 1653135871
Method does not print information from Specify Report and Signal Options
KPR#:388
Stars SCR#: 1653187690
Method Change History: only 10 characters of operator name are printed
KPR#:663
Stars SCR#: 1653260000
"Syntax Error In cmd/fct macro": Trailing comma in Sample Info
KPR#:857
Stars SCR#: 5003251595
"Save Method" and "Datefiles" accept illegal file names. (ex blanks)
KPR#:1120
Stars SCR#: B400101840
Possible GLP issues with "Save Method With Data".
KPR#:1236
Stars SCR#: B400103325
Injection SRC/Loc in the print method screen is confusing.
KPR#:1465
Stars SCR#: B400106088
A method or sequence may still appear in list even after being deleted.
KPR#:1495
Stars SCR#: B400106385
5890: Aux Channel not listed correctly in method printout.
KPR#:1606
Stars SCR#: B400107888
1050 MWD: time table entries for signal C are not saved with method
KPR#:1765
Stars SCR#: B400110254
'Error 41313 in pre-run macro occured' when starting a run
KPR#:1780
Stars SCR#: B400110403
Very long entries for the method information are partially truncated
KPR#:1958
Stars SCR#: n/a
35900E. Run time gets rounded up in print method. .
KPR#:2217
Stars SCR#: n/a
35900E "units/volt" gets rounded down in print method.
KPR#:2218
Stars SCR#: n/a
Pressure unit is not correct on CE ChemStation method printout
KPR#:2275
Stars SCR#: n/a
1050 VWD method printout shows too many digits for the Peak Width setting
KPR#:2298
Stars SCR#: n/a
AM/PM in time for entries in Method History, also with 24 hour time format
KPR#:2339
Stars SCR#: n/a
method with many peaks might give an error when trying to print the results
KPR#:2579
Stars SCR#: n/a
AIA export of MS data contains pointer to original data
KPR#:500
Stars SCR#: 1653219915
Error "load signal for datafile containing spectra!" when create isoplot
KPR#:603
Stars SCR#: 1653244749
Current baseline marks shift up when draw new manual baseline.
KPR#:686
Stars SCR#: 1653265454
"Error 17923 occurred in command TABTEXT$..." when printing report
KPR#:778
Stars SCR#: 1653291286
No object titles for Deconvolution's Charge States and Components spectr
KPR#:1723
Stars SCR#: B400109553
MSD FIA parameters displayed on UV chromatogram
KPR#:1728
Stars SCR#: B400109603
GPF in module HPGRCL00.DLL if too many ions are found in mass spectrum
KPR#:1734
Stars SCR#: B400109660
HPCORE cause GPF in module CTL3DV2.DLL when running LC/MSD Ref Coll. CD
KPR#:1776
Stars SCR#: B400110361
LC/MSD System Verification test gives error in online ChemStation session
KPR#:1979
Stars SCR#: n/a
LCMS Standard report in A.08.03 is on 2 pages
KPR#:2018
Stars SCR#: n/a
Error "Identifier (MSO_PPwidth) is illegal or variable can't be manipulated"
KPR#:2257
Stars SCR#: n/a
TIC and EICs Overlap Mass Spectra in Target Report
KPR#:1766
Stars SCR#: B400110262
The ChemStation starts up minimized after MSD Anyone has been installed
KPR#:1767
Stars SCR#: B400110270
Multiple snapshot windows sometimes printed as part of the report.
KPR#:1768
Stars SCR#: B400110288
If you select a method with arrow keys, the method won't run.
KPR#:1769
Stars SCR#: B400110296
An error on the ChemStation is not displayed on the MSD Anyone screen
KPR#:1770
Stars SCR#: B400110304
When there is an ALS fault, MSD Anyone S/W thinks it has moved samples
KPR#:1771
Stars SCR#: B400110312
Error message "Insufficient positions are available"
KPR#:1772
Stars SCR#: B400110320
Note date is shown in the 'Login Time' field in the Status window
KPR#:1773
Stars SCR#: B400110338
Sporadically, the system hangs wihen a method is being loaded.
KPR#:1774
Stars SCR#: B400110346
System can lock up if capillary voltage is set to less than 500V
KPR#:777
Stars SCR#: 1653291278
Upper time limit for MSD should be the same as for LC pump
KPR#:1724
Stars SCR#: B400109561
In Diagnosis, the Vaporizer heater reports connected with API-ES source
KPR#:1725
Stars SCR#: B400109579
F1 Help topic hot link not working for some Instrument menu items
KPR#:1727
Stars SCR#: B400109595
A "+" in the sample prefix may lead to a crash during acquisition.
KPR#:1729
Stars SCR#: B400109611
Most MSD Run log errors cannot be decoded
KPR#:1730
Stars SCR#: B400109629
'Explain' button in Diagnosis view should be labeled 'Help'
KPR#:1732
Stars SCR#: B400109645
Changing groups in acq. while Buffer Overflow present will give error
KPR#:1777
Stars SCR#: B400110379
Multiple FIA does not run if group name contains a dash
KPR#:2134
Stars SCR#: n/a
MSD icon is yellow when all temperatures/flows are at setpoints
KPR#:2262
Stars SCR#: n/a
Application Error in DLLHOST.EXE when setting up for running Multiple FIA
KPR#:2263
Stars SCR#: n/a
Get application error in DLLHOST.EXE when setting up for running Multiple FIA
KPR#:2369
Stars SCR#: n/a
During a sequence: GPF in HPCORE, module HPDOP_00.dll at 001a:0001f5
KPR#:569
Stars SCR#: 1653238683
Exchange of volumetric unit in Gilson autosampler not possible
KPR#:620
Stars SCR#: 1653248724
Plates per meter calculation on peak tools macro is incorrect
KPR#:1010
Stars SCR#: 5003374983
Draw ADC signal: "[Graphic-Window]: Could not create window"
KPR#:132
Stars SCR#: 1653132647
CP2: CANNOT ADDRESS EXTERNAL DEVICE: PRINTER
KPR#:252
Stars SCR#: 1653162099
Method name is not in output if Method is printed to a file
KPR#:420
Stars SCR#: 1653193771
ISO 9660 standard does not allow for .D extension on directories
KPR#:468
Stars SCR#: 1653209007
Print Module cannot start HPSPL00.EXE, Error Code 2
KPR#:968
Stars SCR#: 5003337683
Printing to a networked printer may not work from ChemStation
KPR#:985
Stars SCR#: 5003347021
Printing problems using Epson printer at 360x360 resolution
KPR#:1136
Stars SCR#: B400102004
WMF export problems on import into various graphics programs
KPR#:1138
Stars SCR#: B400102020
printspooler cannot print, when Environment var TEMP with ANSI != OEM
KPR#:1142
Stars SCR#: B400102061
Curve Segments of zoomed-in graphic missing on serial plotter
KPR#:1179
Stars SCR#: B400102632
Peak Purity Preferences Influence Calculated Library Match Factors
KPR#:127
Stars SCR#: 1653132043
Peak Purity: Peak Purity does not always discard spectra below threshold
KPR#:159
Stars SCR#: 1653137638
Selected Reference Spectra different for Select Purity/Select Spectrum
KPR#:160
Stars SCR#: 1653137646
Peak purity causes the error "Register out of range"
KPR#:612
Stars SCR#: 1653246371
Peak Purity: "The specified register does not exist"
KPR#:1053
Stars SCR#: 5003414797
A09.03 Peak Purity calculation
KPR#:2311
Stars SCR#: n/a
NO DDE communication possible with Visual basic 5.0
KPR#:579
Stars SCR#: 1653239798
The command IsAppLoaded does not work with Windows NT 4.0
KPR#:1029
Stars SCR#: 5003390377
Amount (Amount Ratios) = 0.000 in report
KPR#:140
Stars SCR#: 1653134577
Report: "Sort by" option does not work for some report types
KPR#:151
Stars SCR#: 1653137091
Performance and Noise Report (GC): "Out of Memory"
KPR#:182
Stars SCR#: 1653141994
Performance+Library Report: Performance part not printed
KPR#:237
Stars SCR#: 1653154492
Sample info not printed with injector program
KPR#:414
Stars SCR#: 1653193243
Sequence summary not printed for non-chromatographic signals
KPR#:462
Stars SCR#: 1653207985
Excel 4.0 does not read the XLS reports generated by the ChemStation
KPR#:510
Stars SCR#: 1653223016
On NT printer settings in ChemStation always show default size
KPR#:515
Stars SCR#: 1653225078
Reports contained blank lines using a deskjet 870cxi on NT 4.0
KPR#:527
Stars SCR#: 1653228353
Area% report: Summed peaks, lib. search and short give different area%
KPR#:538
Stars SCR#: 1653230623
Instrument name not printed in custom report
KPR#:559
Stars SCR#: 1653236760
Peak summing reports can not be used with the custome report generator
KPR#:578
Stars SCR#: 1653239616
Overlay signal does not print the correct chromatogram in report
KPR#:581
Stars SCR#: 1653240275
Print setting shows wrong print orientation under NT
KPR#:589
Stars SCR#: 1653241240
Laserjet 5n/m driver does not print with LaserJet 5 connected
KPR#:598
Stars SCR#: 1653243477
Library search causes error in macro optimizeProposals in IDBYLIB.MAC
KPR#:606
Stars SCR#: 1653245290
Want: uncalibrated peaks included in sequence summary report
KPR#:644
Stars SCR#: 1653255679
GC report: method 2 comment is obtaind from method 1
KPR#:647
Stars SCR#: 1653256487
lmport of custom. report templates from Rev. prior to A.03 incomplete
KPR#:683
Stars SCR#: 1653263798
Uncalibrated peaks warning in area% report shows
KPR#:699
Stars SCR#: 1653267732
Summed peaks table do not summ up to 100%
KPR#:714
Stars SCR#: 1653270504
Perform. report (Area%): undefined rows for missing calibrated compounds
KPR#:751
Stars SCR#: 1653283564
SSR: "Statistic results for Resolution (tangent method) not available"
KPR#:752
Stars SCR#: 1653283697
Extended performance report: wrong USP tailing factor may be calculated
KPR#:767
Stars SCR#: 1653286872
Ext.perf.report: missing or wrong acquisition information may be printed
KPR#:771
Stars SCR#: 1653289108
Date format in the ChemStation reports
KPR#:788
Stars SCR#: 1653295816
Error 16166 occurred in Command MoveObj in macro PExtStatisticReport
KPR#:907
Stars SCR#: 5003296194
Control sample always fails when # plates is used as limit
KPR#:997
Stars SCR#: 5003354514
Sequence summary report for individual data files incorrect.
KPR#:1057
Stars SCR#: 5003417527
Extended performance report to file does not generate WMF files
KPR#:1086
Stars SCR#: 5003448688
Extended Performance Report: graphics truncated for unresolved peaks
KPR#:1109
Stars SCR#: 5003462853
Missing Sequence Summary Report
KPR#:1115
Stars SCR#: B400097014
Report to file using a write protected data file
KPR#:1133
Stars SCR#: B400101972
ISTD report reports ISTD signal that is not in the Compound Details
KPR#:1147
Stars SCR#: B400102111
Report contains wrong data file name
KPR#:1224
Stars SCR#: B400103200
6890 ONLY: The chromatogram does not print correctly with a LJ4.
KPR#:1325
Stars SCR#: B400104604
Error, In command tabHdrVal in macro SSR_deleteseque at line 654 in file
KPR#:1382
Stars SCR#: B400105239
Problems with laserjets when printing chromatograms at 600 x 600 dpi.
KPR#:1440
Stars SCR#: B400105825
Can access the Sequence Summary menu when running a sequence.
KPR#:1469
Stars SCR#: B400106120
Lower combo box of the main toolbar in report layout is clipped.
KPR#:1489
Stars SCR#: B400106328
GLP Sequence Summary reports may fail if reprocessed on different instr.
KPR#:1618
Stars SCR#: B400108001
File->Printer Setup always shows Document defaults with NT.
KPR#:1634
Stars SCR#: B400108175
Print of Peak purity results do contain additional line
KPR#:1684
Stars SCR#: B400108993
Lib search rpt causes err in IDBYLIB.MAC at line 616, table not found
KPR#:1692
Stars SCR#: B400109074
Printing a HPCE method with HPCE timetable does not work correctly
KPR#:1698
Stars SCR#: B400109157
Statistical moments are not calculated for tangent skimmed peaks
KPR#:1709
Stars SCR#: B400109264
Missing help on timed event 'baseline backward'
KPR#:1757
Stars SCR#: B400109918
Temp file might not be deleted after multi page report generation
KPR#:1781
Stars SCR#: B400110411
HTML reporting looses handles under Win 95
KPR#:1782
Stars SCR#: B400110429
Print to file: "Result obtained with enhanced integegrator" is missing
KPR#:1786
Stars SCR#: B400110460
Performance reports: Missing characters for not found compounds
KPR#:1789
Stars SCR#: B400110502
Peaks with retention time 0.0 printed in report
KPR#:1859
Stars SCR#: n/a
Printer Setup dialog always shows default values
KPR#:1947
Stars SCR#: n/a
Sample amount is not stored in Chromres
KPR#:2140
Stars SCR#: n/a
Incorrect column description data in the report a08.03
KPR#:2174
Stars SCR#: n/a
Report parameter ("% of page" - Time )changing when printing HTM-report
KPR#:2317
Stars SCR#: n/a
method chnaged ater loading appears on report even if method has not been change
KPR#:2401
Stars SCR#: n/a
spectra options are not printed correctly
KPR#:2410
Stars SCR#: n/a
cannot load logo in wmf into report layout of chemstation
KPR#:2427
Stars SCR#: n/a
Peak Type PARABOLIC INTERPOLATION mentioned in GC
KPR#:2454
Stars SCR#: n/a
Customer can't scroll with the mouse in ChemStation
KPR#:2464
Stars SCR#: n/a
problem with sizing of the chromatogram in a Short Report
KPR#:2524
Stars SCR#: n/a
"Seq Line"(Sequence line) value for Calibration samples printed wrong in report
KPR#:2535
Stars SCR#: n/a
G1600A CE method print out in CEC mode reports mbar
KPR#:2546
Stars SCR#: n/a
some imported logos are not working in custom report layout
KPR#:2552
Stars SCR#: n/a
Time Ranges not applied correctly in short report
KPR#:2588
Stars SCR#: n/a
Printing problems with LJ 5L when running in HOST BASED mode (WIN-95).
KPR#:1560
Stars SCR#: B400107326
GC Inst: Only 1st column information is printed on custom reports.
KPR#:1621
Stars SCR#: B400108035
GC plus 7673, The injection volume is not printed out in some reports.
KPR#:1685
Stars SCR#: B400109009
Floating point exception INVALID number detected.
KPR#:1792
Stars SCR#: B400110767
35900E: Splitting channels cause problems if using different protocols
KPR#:1719
Stars SCR#: B400109512
Sequence table user interface displayes wrong method
KPR#:540
Stars SCR#: 1653230870
Sequence Recalibration fails if report style 'Libsearch' is selected
KPR#:676
Stars SCR#: 1653262220
No datafile name may be entered in sequence table for calibration sample
KPR#:820
Stars SCR#: 1653307728
Using Copy/Paste during running sequence potenially corrupts config register
KPR#:839
Stars SCR#: 1653312033
Using sequences of different sampling units in different ChemStations.
KPR#:982
Stars SCR#: 5003344077
Change of sample type in sequence table during run has no effect
KPR#:1068
Stars SCR#: 5003436352
No sample name in data file if vial number is left blank is sequence
KPR#:1088
Stars SCR#: 5003450718
The sequence table buttons have inconsistent descriptions/operations.
KPR#:1467
Stars SCR#: B400106104
The order of entering the sequence recalibration is restricted.
KPR#:1474
Stars SCR#: B400106179
The 7673 tray graphics are not updated after partial sequence.
KPR#:1498
Stars SCR#: B400106419
System allows loading a sequence from toolbar while a method is running.
KPR#:1499
Stars SCR#: B400106427
Dual signal CSV files generation does not work
KPR#:2089
Stars SCR#: n/a
Batch Report: duplicated results for multiple signals in Cal table
KPR#:2120
Stars SCR#: n/a
Printout of Partial Sequence table misses essential information
KPR#:2333
Stars SCR#: n/a
Cannot import XML worklist from "long" path
KPR#:2422
Stars SCR#: n/a
1100 DAD noise test fails in combination with ChemStore B.03.01
KPR#:2519
Stars SCR#: n/a
comX with X = 1, 2,... as datafile name in sequence table generates errors
KPR#:2557
Stars SCR#: n/a
XML Import: Import of LimsId fails if sample amount has been set in import XML f
KPR#:2576
Stars SCR#: n/a
Partial sequence creates the wrong data file name.
KPR#:416
Stars SCR#: 1653193383
Wrong sample names in partial sequence table for cyclic recalibration
KPR#:743
Stars SCR#: 1653280453
Print Selected Window containing UV Spectra
KPR#:39
Stars SCR#: 1653115246
User is not prompted to save modified spectra library before lib search
KPR#:100
Stars SCR#: 1653129205
Automated Library Search: No Calibrated Compounds Are Identified
KPR#:103
Stars SCR#: 1653129239
Library Search: Compounds with high match factors missing in rpt
KPR#:137
Stars SCR#: 1653133694
Reference Spectra Selection for Library Search
KPR#:201
Stars SCR#: 1653147116
Iso plot reference option
KPR#:535
Stars SCR#: 1653230300
Access Spectra Library: "Specified Register not found"
KPR#:544
Stars SCR#: 1653232066
Print Library Entry: "the specified register does not exist"
KPR#:889
Stars SCR#: 5003280016
Library search generates error insertResults in macro idbylib.mac
KPR#:1694
Stars SCR#: B400109090
Refrence spectra are not taken near the peak
KPR#:582
Stars SCR#: 1653240309
Normalization options for spectra can not be selected in dialog box
KPR#:616
Stars SCR#: 1653246652
Library search is not done on peak purity peak
KPR#:805
Stars SCR#: 1653303990
Adding noisy spectra to spectra library can cause GPF in HPGRCL00.DLL
KPR#:1716
Stars SCR#: B400109488
GPF in module HPGRCL00.DLL at 0004:00001ada
KPR#:1779
Stars SCR#: B400110395
Automated Library Search Does NOT work as expected with 4 library's
KPR#:2034
Stars SCR#: n/a
using the screen resolution 800x600 on a XM2 and XM4.
KPR#:305
Stars SCR#: 1653172767
Chromatogram sometimes overlays the calibration table.
KPR#:393
Stars SCR#: 1653187773
It is possible to overwrite a name in the calibration curve screen.
KPR#:394
Stars SCR#: 1653187781
Compund names not shown on all overlaid chromatograms
KPR#:413
Stars SCR#: 1653193235
Method history text is truncated after 40 characters
KPR#:421
Stars SCR#: 1653193789
DAD 1040 can not be controlled by System diagram, only via menu
KPR#:440
Stars SCR#: 1653199257
Display of elapsed run time dissappers
KPR#:623
Stars SCR#: 1653250134
A/D-ChemStation: System Diagram not available (Error Message)
KPR#:642
Stars SCR#: 1653255455
One pump missing in instrument menu if 2 different ones are configured
KPR#:645
Stars SCR#: 1653255760
Column Description is not updated in the Graphical User Interface
KPR#:652
Stars SCR#: 1653258921
Zoom not possible in 3D Signal overlay
KPR#:711
Stars SCR#: 1653270090
GUI for sequence table not correctly displayed
KPR#:725
Stars SCR#: 1653273920
HPCORE caused an invalid page fault in module ATIWDDE.DLL at 0137:10001b
KPR#:762
Stars SCR#: 1653285924
Online plot occasionally disappears from system diagram
KPR#:770
Stars SCR#: 1653288795
The setting for the y scaling is ignored
KPR#:835
Stars SCR#: 1653311365
Sporadically, no control menu in list contents window
KPR#:909
Stars SCR#: 5003298745
Macro DIALOG box with a CHECKBOX may cause error message when removed.
KPR#:921
Stars SCR#: 5003312488
Tutorial does not work correctly when running the GC portion.
KPR#:993
Stars SCR#: 5003348417
Inconsisten behaviour of spectra library menu vs toolbar button
KPR#:1005
Stars SCR#: 5003366427
In Calibration Table, Compound Details, there is no column for CSL
KPR#:1021
Stars SCR#: 5003381061
A zoomed calibration curve is not correctly copied to the clipboard
KPR#:1052
Stars SCR#: 5003412569
Activating User Access Level Method Protection from all sessions
KPR#:1160
Stars SCR#: B400102244
6890 GC only: Quick setup operates differently with Dashboard as shell.
KPR#:1319
Stars SCR#: B400104521
The "Fn" function keys are hidden by Signal 2 real time plot.
KPR#:1333
Stars SCR#: B400104737
User signals options menu allows only three places, user can set more.
KPR#:1339
Stars SCR#: B400104794
The Data View pull down is not active until mouse button is released.
KPR#:1390
Stars SCR#: B400105312
Method Information dialog box is the old style, needs updated.
KPR#:1392
Stars SCR#: B400105338
Resource problem with tutorial and Windows for Workgroups, rev 3.11
KPR#:1404
Stars SCR#: B400105460
ChemStation loses focus after switch to Method and Run control.
KPR#:1408
Stars SCR#: B400105502
System performance is compromised by redrawing he online plot over/over.
KPR#:1447
Stars SCR#: B400105908
Often the UP and DOWN arrow keys are not used correctly.
KPR#:1452
Stars SCR#: B400105957
The tutorial covers the "BUSY" message, menus seem not to work.
KPR#:1460
Stars SCR#: B400106039
Hide and show Status toolbars does not restore screen to previous.
KPR#:1466
Stars SCR#: B400106096
The scroll bard in many screens are one of three different types.
KPR#:1470
Stars SCR#: B400106138
The OQ/PV tests does not display the allowed values.
KPR#:1472
Stars SCR#: B400106153
Annotation "tool buttons" and "signal options" are not linked.
KPR#:1478
Stars SCR#: B400106211
GPF ERRORS from Windows caused by Instrument name being too long.
KPR#:1570
Stars SCR#: B400107425
Peak Graphics Highlights in data analysis may not be visible.
KPR#:1622
Stars SCR#: B400108043
Task icons in Data Analysis view overlayed by File icons
KPR#:1639
Stars SCR#: B400108225
Floating point exception INVALID NUMBER detected.
KPR#:1798
Stars SCR#: B400110858
Tutorial skips step3
KPR#:1814
Stars SCR#: n/a
scaling - each in full scale
KPR#:1818
Stars SCR#: n/a
7673: Missing sampling tray diagram in A08.03
KPR#:2020
Stars SCR#: n/a
6850 GC: The correct tray and Injector Icons are not displayed.
KPR#:2054
Stars SCR#: n/a
Disk Drive space remaining icon
KPR#:2167
Stars SCR#: n/a
Signal Task: Time reference lines only visible with 256 colors on Compaq bundle
KPR#:2322
Stars SCR#: n/a
Fraction collection module error message given at different Fraction Collector
KPR#:2355
Stars SCR#: n/a
Timetable MWD disappears when shifting from 'table' to 'grapics'
KPR#:2384
Stars SCR#: n/a
GC ChemStation Scheduler: incomplete screen display
KPR#:92
Stars SCR#: 1653127928
Error "Can't get dimension file" when AIA Import of Beckman Gold Nouveau
KPR#:395
Stars SCR#: 1653187815
AIA data from TurboChrom: Can't get required attribute of the AIA file
KPR#:576
Stars SCR#: 1653239442
Companion: Selecting French in the Preference Dialog Box uses English.
KPR#:732
Stars SCR#: 1653276634
Scheduler: "THE MAXIMUM # OF ENTRIES IS 200"
KPR#:930
Stars SCR#: 5003317446
Help information for Scheduler is incorrect
KPR#:932
Stars SCR#: 5003318808
Scheduler: "Rejected" displayed in the result status line
KPR#:950
Stars SCR#: 5003328450
Data Interchange to Excel: "Could connect to Excel"
KPR#:966
Stars SCR#: 5003335653
Import Pascal Library: "While without endwhile in macro" [convlib.g]
KPR#:1222
Stars SCR#: B400103184
System Verification Test does not run if method=current method
KPR#:1545
Stars SCR#: B400107144
A.08.03: Companion does not recognize GC-Als methods
KPR#:2033
Stars SCR#: n/a
Export of data file to AIA is adding a wrong date-time stamp
KPR#:2098
Stars SCR#: n/a
Installation verification report: Timestamp of ref files varies with seasons
KPR#:2118
Stars SCR#: n/a
Ambigous reference for HPLC1100.HLP in Inst Verification after A.08.04 update
KPR#:2219
Stars SCR#: n/a
XML : LIMIDs modified during reprocessing
KPR#:2485
Stars SCR#: n/a
XML using manual upload places result.xml file to sample info directory
KPR#:2512
Stars SCR#: n/a
Multiplier not taken when running Data Acq. only
KPR#:2545
Stars SCR#: n/a
wrong pressure description using Japanese fonts
KPR#:2571
Stars SCR#: n/a
Keyword: 1046 CONTROL
One-line Description:
'System Off' button changes method on the 1046 FLD
Problem:
|
Using the HP ChemStation System Diagram (for LC) to turn off the system (pump, column compartment, detector lamps), the following may occur in a configuration that includes an HP 1046 Fluorescence Detector (FLD): 'System Off' will turn off the 1046 lamp. 'Lamp off' is a normal status of the 1046 which is also viable during an analysis (chemo-luminescence) and will not result in a 'not-ready' condition. Turning the lamp on will set the so-called 'method-modification' flag in the ChemStation. |
Problem Cause:
|
n/a |
Temporary Solution:
|
When working with the 1046 FLD, use the individual 'on/off' buttons for the pump and other devices instead of the 'system off' button/menu. |
Fix Information:
|
n/a |
Keyword: 1050 CONTROL
One-line Description:
Mixed 1050 and HP1100 system does not calculate k'
Problem:
|
If a HP1050 pump is used with HP1100 detector and autosampler, the value for k' is not calculated. |
Problem Cause:
|
Caused by function getdead time not returning a valid value |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned |
Keyword: 1050 CONTROL
One-line Description:
Running User Contributed Macro #10, INJSTEP MAC on 1050: Close crashes
Problem:
|
Running User Contributed Macro #10, InjStep.MAC on 1050. Close crashes system. When clicking on CLOSE get a Stack Error. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned |
Keyword: 1050 CONTROL
One-line Description:
Injector Program 1050
Problem:
|
Injector Program 1050: a) part of the bitmap of previous edit field stay on the screen when context is switched. b) Error/mistake recovery not obvious: when one parameter of a selection is not set, but you want to enter the command, the line stays empty/blank without warning what has happened. Expectations: ""Part of Settings missing . line not complete |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: 1050 CONTROL
One-line Description:
A/D and 1050 system can not be used with 2 instrument sessions
Problem:
|
On some PC modells it is not possible to use 2 A/D converters together with a 1090 or a 1050 system. During startup of the ChemStation the ChemStation hangs during initialization of the second A/D converter. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Try separating the system to use only one A/D converter or use a different PC. |
Fix Information:
|
No fix planned |
Keyword: 1090 CONTROL
One-line Description:
Oven Not Ready message disappears after another Not Ready event occured
Problem:
|
If the 1090 oven door is open, and another not ready message appears (e.g. open cover) and the cover is closed, the not ready oven message may disappear. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 1090 CONTROL
One-line Description:
HP 1090 gradient method not executed if solvent channel switched off
Problem:
|
The timetable entries defined for the HP 1090 pumps are not checked for consistency if one of the solvent channels used in the timetable is initially switched off. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Delete the solvent channel that is not used from the timetable entries. |
Fix Information:
|
No fix planned. |
Keyword: 1090 CONTROL
One-line Description:
1090 DAD online plot: low resolution of the online plot
Problem:
|
The Signal monitor of the 1090 DAD signal frequently shows peaks that look like built up of the steps of a staircase. This is only on the signal monitor, not in the data file. |
Problem Cause:
|
The problem is caused by the limited resolution (8 bits) of the plot data delivered from the 1090 DAD firmware. |
Temporary Solution:
|
n/a |
Fix Information:
|
This problem is inherent to the firmware design of the HP 1090 DAD and will not be fixed. |
Keyword: 1090 CONTROL
One-line Description:
LC1090: Balancing in online plot doesn't go to zeroline
Problem:
|
If a signal is balanced in the online plot it doesn't go exactly to the zeroline (LC 1090 only). |
Problem Cause:
|
This is due to the DAD (LC 1090 only) acquiring data with 2 channels, one of which is used for the online plot and has a minor resolution. The 2nd one has a better resolution and is used to generate the raw datafile. |
Temporary Solution:
|
The datafile and therefore the results are not affected by the deviation from the zeroline because of the better resolution of the corresponding channel. |
Fix Information:
|
No Fix planned. |
Keyword: 1090 CONTROL
One-line Description:
%B signal shows only gradient definition - not what pump really does
Problem:
|
When setting up a gradient time table with the HP1090L, the gradient can be programmed in 0.01 minute steps. When entering a time value >= 100.00 min, this does no longer work. e.g. 96.00 min 75%B 1090 does 96.00min 75%B 100.00min 75%B 1090 does 100.0min 75%B 100.01min 50%B 1090 dose 100.0min 50%B 106.00min 50%B 1090 does 106.0min 50%B 106.01min 25%B 1090 does 106.0min 25%B The HP1090 firmware truncates the time value after 4 digits. This is HP1090 firmware defect, it also happens when entering the timetable at the local user interface of the LC. The software does not show the actual %B curve (i.e. the theoretical curve is displayed, not what the HP1090 actually does). |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 1090 CONTROL
One-line Description:
Working with the HP 79880 DAD (HP 1040, HP 1090 DAD)
Problem:
|
1) Aborting an analysis: Aborting an analysis while the HP 1090 DAD is in "RUN" mode but not yet acquiring data may cause the ChemStation to hung up. The probability for the system failure increases with higher peakwidth settings (longer sampling intervals). 2) Varying peakwidth settings in each run After a change of the peakwidth setting, raw data of the following run may be missing or incomplete. It was reported that in a sequence with 20 runs, each with a different peakwidth varieing with each run between 0.1 and 1.0 min, 7 runs had incomplete raw data. The failure has not been seen when using peak- width values less than 0.1 min. 3) DAD idle time between Autobalance and Injection When a run is started from the ChemStation and the DAD does an Autobal lance, the DAD is idle between Autobalance and the injection. The idle time corresponds to the specified peakwidth, ranging from 0.007 to 10.000 minutes. There is no indication on the user interface. The ChemStation's Status Monitor Window reports "Run" and the DAD status window shows "Prerun" and "Ready". "Stop Run" or "Abort" do not work during that wait period. A message box "Stop of Instrument Failed" is displayed instead. |
Problem Cause:
|
n/a |
Temporary Solution:
|
It is recommended to use peakwidth settings smaller than 0.1 min. |
Fix Information:
|
n/a |
Keyword: 1090 CONTROL
One-line Description:
system hangs if 1040 DAD peakwidth=10 min and runtime < 10 min
Problem:
|
The following behaviour has been observed for the HP 1090 DAD (HP 1040 DAD): The system will hang if the stoptime for the LC is less than the configured peakwidth time. Due to the firmware implementation, the DAD remains in an idle state after the autobalance. The idle time corresponds to the configured peakwidth (i.e. up to 10 minutes!). There is no indication on the user interface. The ChemStation's Status Monitor Window reports "Run" and the DAD status window shows "Prerun" and "Ready". "Stop Run" or "Abort" do not work during that wait period. A message box "Stop of Instrument Failed" is displayed instead. See SR # B400102566 for more information. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: 1090 CONTROL
One-line Description:
Error message POST_MESSAGE failed when closing ChemStation
Problem:
|
Closing the HP ChemStation can cause the error message POST_MESSAGE failed in a dialog box. |
Problem Cause:
|
n/a |
Temporary Solution:
|
This is caused if the ChemStation runs in separate memory space under Windows NT. This can be selected in the properties of the link pointing the the HP ChemStation. Use the Windows Explorer to navigate to the, selected properties from the context menue (right mouse click) and ensure that the check mark run in separate memory space is not selected. For further details refer to the installing your LC ChemStation manual. |
Fix Information:
|
n/a |
Keyword: 1100 CONTROL
One-line Description:
1100 LC system does not show status of 1046 FLD if connected.
Problem:
|
When a 1046A FLD is configures as part of an 1100 series LC the system diagram does not show the status of the FLD. The FLD detector symbol is present, but is always greyed out. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use the instrument actuals window to display the status of the FLD. |
Fix Information:
|
No fix planned |
Keyword: 1100 CONTROL
One-line Description:
HP1100: System exception 8009 in seqeng.c / GPF IN HPCP00.DLL
Problem:
|
It has been reported by several customers that very intermittently on start up of the ChemStation the following message is displayed... "System exception error 8009 in seqeng.c at 657" This error is normally only reported once per system. It has also been reported that during startup of the ChemStation the same message with: "System exception error 8009 in seqeng.c at 232" appeared, followed by a "General Protection Fault in HPCP00.DLL at 0006:1997" and the ChemStation closing down again. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The error can be corrected by power cycling the HP 1100 system and restarting the instrument session. No second occurrences have been reported. To prevent the error from occuring, make sure that there is no sequence running on the control module when starting the ChemStation. |
Fix Information:
|
n/a |
Keyword: 1100 CONTROL
One-line Description:
WL accuracy check does not use method IVWLACC, but loads method IVNOISE
Problem:
|
The wavelength accuracy test loads method IVNOISE.M instead of IVWLACC.M after start of the test. |
Problem Cause:
|
n/a |
Temporary Solution:
|
This is correct, because the blank spectrum is acquired using this method. |
Fix Information:
|
n/a |
Keyword: 1100 CONTROL
One-line Description:
HP 1100: Adding gradient step during run is executed instantaneously
Problem:
|
Changes in the time table during runtime are send to the HP1100 module imediatly. |
Problem Cause:
|
n/a |
Temporary Solution:
|
If the time of the event has already passed, the change will take place imediatly. |
Fix Information:
|
n/a |
Keyword: 1100 CONTROL
One-line Description:
Gradient test of OQ/PV procedures failed
Problem:
|
The gradient test of the OQ/PV on an HP1100 system might fail with the signal beeing completly out of range. |
Problem Cause:
|
If multiple detectors are installed only one signal is used for the gradient test. The gradient test requires a HP1100 VWD or a HP1100 DAD. |
Temporary Solution:
|
Disconnect all detectors except for one. This can be a HP1100 DAD or a HP1100 VWD. |
Fix Information:
|
No fix planned |
Keyword: 1100 CONTROL
One-line Description:
Generating a sequence with blank injections not possible
Problem:
|
It is not possible to use the Insert vial range function in the sequence table setup to insert a blank vial range. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Create the blank sequence using the sequence table directly by leaving the vial field empty and use Inj/vial field for the number of injections. |
Fix Information:
|
No fix planned |
Keyword: 1100 CONTROL
One-line Description:
What error method is used on a HP1100 system with ChemStation
Problem:
|
What method is used by the HP1100 modules in case of an error? |
Problem Cause:
|
n/a |
Temporary Solution:
|
All HP1100 have internal memory to store parameters. If use as error method is selected, the current parameters are store in the HP1100 modules and will be loaded after an error event has occured and was cleared. Because the methods stored in the HP ChemStation are independent from the ones stored in the HP1100 modules, the data acquisition parameters of the currently loaded method in the ChemStation will be changed by the new parameters loaded in the HP1100 modules. |
Fix Information:
|
n/a |
Keyword: 1100 CONTROL
One-line Description:
HP 1100 DAD wavelength accuracy test fails with 2D ChemStation
Problem:
|
The HP1100 DAD wavelength accuracy test fails if the ChemStation has no spectral evaluation module (2D ChemStation). |
Problem Cause:
|
To perform the HP 1100 DAD wavelength accuracy test from the ChemStation the spectral capabilities offered by the 3D ChemStation are required. |
Temporary Solution:
|
This is now noted in the help. |
Fix Information:
|
No fix planned. |
Keyword: 1100 CONTROL
One-line Description:
wrong concentration 25ug/mL should be 5 ug/ml.
Problem:
|
n/a |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 1100 CONTROL
One-line Description:
HP1100 RID: Autom. zero and purge do not work in certain configurations
Problem:
|
In certain mixed configuration (with HP 1090 or with third party instruments which start the RID remotely) the 'automatic zero' and the 'automatic purge before analysis' do not function. |
Problem Cause:
|
For technical reasons the LC 1090 does not support these features. Third party instruments are not able to initiate these actions either. |
Temporary Solution:
|
A macro to solve this problem is available. Please contact the response centre or a local support person. Refer to the servicenote G1362-002. |
Fix Information:
|
For technical reasons there is no fix possible. |
Keyword: 1100 CONTROL
One-line Description:
HP1100 RID and 1090 LC: Not possible doing purge before analysis
Problem:
|
Using a HP1100 RID and a 1090 system the automatic purge before run function of the HP1100 RID does not work. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Add the text macro purge.mac to the line Pre-Run Command / Macro in the ChemStation run time check list dialog box. Create a file named purge .mac in the directory hpchem\core with the following text print Sendmodule$(lrid,"VREF 1,10") !Opens purge valve for 10 minutes b = MTIME() + 900000 ! add summ of purge and wait time for run to start WHILE MTIME() <= b DO Print Using "###.#", (b-MTIME())/1000/60 print ENDWHILE ! A run can not be stopped, only aborted |
Fix Information:
|
This will be fixed in the HP1100 RID firmware, rev > 3.80 |
Keyword: 1100 CONTROL
One-line Description:
OQ/PV testresult for injector precision / caryover can be negative
Problem:
|
When performing the precision/caryover test for an HP1100 system, the result might be negative and the test passes. |
Problem Cause:
|
n/a |
Temporary Solution:
|
This indicates that the precision/carover is better than 0. |
Fix Information:
|
n/a |
Keyword: 1100 CONTROL
One-line Description:
1100: Multi-gradients created off line, don't import to online instance.
Problem:
|
On a system with an HP 1100, a method created on the off-line session with multiple line gradients will only have the FIRST line of the gradient table imported when the method is loaded on the on-line system. All other lines in the gradient table are deleted. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Create gradient methods for HP 1100s using the on-line session only. |
Fix Information:
|
n/a |
Keyword: 1100 CONTROL
One-line Description:
Holmium Oxide Test Results Window Inactive
Problem:
|
After running the holmium filter test, the holmium test results window cannot be resized in order to see whether the test passed or failed. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The ChemStation stores the relative size and position of the Results window. Leave the OQ/PV dialog and resize the Results window before displaying the results. |
Fix Information:
|
n/a |
Keyword: 1100 CONTROL
One-line Description:
DAD Wavelength Calibration Data from Control Module Ignored
Problem:
|
The handheld Control Module and the HP ChemStation both can perform wavelength calibrations. The HP ChemStation does not store wavelength calibrations performed on the local Control Module in its calibration history. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: 1100 CONTROL
One-line Description:
HP1100 OQ/PV Noise/Drift with DAD+VWD installed allows 1 set of limits
Problem:
|
Scenario: HP1100 DAD & VWD Installed The OQ/PV Noise/Drift test dialogue only allows one set of acceptance limits to be entered even though the performance of both detectors is evaluated. In parts of the test where acceptance limits for the two detectors are different it is possible to obtain a false pass or fail result depending on which detector's limit is entered. |
Problem Cause:
|
The OQ/PV feature was not designed to support multiple detectors. |
Temporary Solution:
|
The following workaround is suggested for using the customizing feature of OQ/PV with multiple detectors: 1) Create for each detector one new method and one sequence. 2) Add the detector signal to the signal table. 3) Set the method parts of the sequence to 'According to Runtime Checklist' for one sequence and to 'Reprocessing for all others. 4) Create an OQ/PV starting with the 'According to Runtime Checklist' sequence and followed by the other sequences. 5) Define the limits now individually for each test. |
Fix Information:
|
n/a |
Keyword: 1100 CONTROL
One-line Description:
Multiple rows with the same time for the FLD time table do not work
Problem:
|
Selecting to display graphics in the FLD time table when multiple entries with the same time are made causes the time table to disappear. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Select the table button and graphics button again, to display the table and the graphics correctly. No data will be lost. |
Fix Information:
|
n/a |
Keyword: 1100 CONTROL
One-line Description:
DIAGNOSIS: thermostat test is not stopped if no HP 1100 pump is config.
Problem:
|
If running the thermostat test from the diagnosis view without an HP 1100 pump (G1310A/G1311A/G1312A) configured, the test is not working correctly. The test is not stopped automatically and has to be aborted. |
Problem Cause:
|
In the method used for diagnosis the stop time for the other modules are set to 'as pump'. If no pump is configured this setting is auto- matically changed to 'no limit'. |
Temporary Solution:
|
Change the attributes of the method used for diagnosis (dgthmtst.m for the thermostat test) by removing the 'read only' flag for each file in the dgthmtst-directory. This can be done from the Explorer in the file properties. Start the offline session of the ChemStation, configure a complete HP 1100 system and load the corresponding method. Change the run time for each module from 'as pump' to 6 min (like specified for the pump). Save the method. To change the setting for the injector the configuration has to be changed to the the autosampler only. |
Fix Information:
|
n/a |
Keyword: 1100 CONTROL
One-line Description:
On line spectra wavelength display does not match stored spectra WL
Problem:
|
The online spectra screen of a HP 1100 DAD does not display the same spectra as in a spectra that would be acquired during a run. |
Problem Cause:
|
The HP1100 DAD has a built in wavelength calibration function. The wavelength correction is only applied to the spectra that are transferred to be part of a data file. This correction is not applied to the on-line spectra, that can be displayed in the HP ChemStation. |
Temporary Solution:
|
Do not use the on-line spectra for wavelength calibration and WL accuracy checks. |
Fix Information:
|
There is no fix planned. |
Keyword: 1100 CONTROL
One-line Description:
1100 bottle filling: pump status in GUI does not reflect not ready condition
Problem:
|
If the 1100 bottle filling options are used to prevent analysis and the solvent level is already below the limit specified the pump is not turned on. The status in the GUI does not reflect this. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 1100 CONTROL
One-line Description:
pressure set to "setpoint" in the online plot of LC cs rev.A.09.01
Problem:
|
It is not possible anymore to adjust the scale for the pressure in the online plot. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
shall be fixed in the A.09.03 |
Keyword: 1100 CONTROL
One-line Description:
Fraction Collector: Upslope and downslope are not working
Problem:
|
Within the setup of the fraction collector you can specify under the peak detectors dialog box an upslope, downslope and threshold value for peak triggerering. For the DAD, MWD and VWD is the upslope and downslope not working correctly. The values are ignored and internally is 0 used. This results that each small increase of the baseline above the specified threshold is triggerd. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
Fixed in A09.03 |
Keyword: 1100 CONTROL
One-line Description:
Signal change in LC Detector during a run
Problem:
|
Running LC Sequences in operator mode it is possible to change signal parameter for various LC detectors. Multiple changes during acquisition are possible and the change will be documented on the Report. A change history list is missing. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The change will be documented by the Chemstation using the method changed flag/ time stamp and by the sequence logbook (method changed). |
Fix Information:
|
n/a |
Keyword: 1100 CONTROL
One-line Description:
two MWD in one instrument: problem to control MWD 2 via GUI
Problem:
|
For ChemStaiton A.10.x revsion following issue has been reported for systems using a stack including 2 times a MWD: The graphical user interface control for the secound MWD in the configuration is controlling the settings of the first MWD of the configuration. This issue only applies fo the graphical user interface. The Instrument menu allows to control the VWD in the correct way. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use the instrument menu to control two MWDs in one 1100 stack. |
Fix Information:
|
n/a |
Keyword: 1100 CONTROL
One-line Description:
Online and Offline method print out not the same
Problem:
|
Comparing the method printout offline to online modus, the online modus will give more information on the report: As example: Agilent 1100 AutoSampler Section dealing with Auxillary settings: In online there is printed out: Store Temperature NO This line is missing in the offline. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Please use the onlilne method print out in case for audit reasons. |
Fix Information:
|
n/a |
Keyword: 1100 CONTROL
One-line Description:
Using flow gradients during Fraction Collection results in Wrong times in Report
Problem:
|
Following issue has been reported, using ChemStation A.10.0x and higher: Using flow gradients during Fraction Collection results in wrong times for the collected fractions in the Report (in the fraction table). However, tickmarks are displayed and generated correctly, so there is a mismatch betqween tickmarks and the reported fraction table times. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 1100 CONTROL
One-line Description:
Inconsistent Valve Order in ChemStation Configuration
Problem:
|
In an instrument with several valves the order of the valves in the "Configure 1100 Access" dialog is not always adopted during operation of the instrument. In these cases you will observe that the order in the "Serial and Firmware Revisions" dialog differs from that in the "Configure 1100 Access" dialog. The order in "Serial and Firmware Revisions" is the one actually adopted during operation. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Make sure to hold the physical connection order of the valves like the one set in the "Serial and Firmware Revisions" dialog. |
Fix Information:
|
fixed in B:01.03 |
Keyword: 1100 CONTROL
One-line Description:
incorrect injection time stamps on report
Problem:
|
In some cases it may be observed, that reports generated by ChemStation show wrong injection time stamps. In case of long sequences with a single method or few method changes, reported injection times may not be consistent with other time stamps printed on a report, for example the print date. Data integrity is not affected as the injection time is not used for any evaluation of measurement results like retention times, areas etc. Following modules with production dates or main board replacements since April 2007 can show this effect: G1329A Standard Autosampler (vials) G1329B Standard Autosampler SL (vials) G2260A Preparative Autosampler G1313A Standard Autosampler |
Problem Cause:
|
n/a |
Temporary Solution:
|
ChemStation regularly synchronizes the LC system to the PC time. This is done implicitly each time a new method is loaded or changed. If a method is used many times within a long sequence, there will be no synchronization within that sequence and as a consequence LC time stamps may differ from PC time stamps in the same report or log file. As a workaround, it is possible to include periodically a sequence line using a second method which has a different name but the same instrument parameters (flow, composition, temperature etc.) and a short stop time. In the sequence table, leave the location parameter empty when using this method, so that no injection is done in these cases. |
Fix Information:
|
Agilent Technologies is currently working on a patch for released versions of ChemStation. I addition, the patch will be included in revision B.04.01. |
Keyword: 35900 CONTROL
One-line Description:
The menu task "Instrument" has no submenu to configure a 35900.
Problem:
|
The A/D ChemStation G2072 installed as an LC instrument with only a 35900 configured does not have a menue item to setup the instrument |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use Edit Entire method from the Menu Method to open the instrument setup dialog box for the 35900 or Install the G2072AA as GC type (which works) instead of LC type. |
Fix Information:
|
n/a |
Keyword: 35900 CONTROL
One-line Description:
F1 Help doesn't work for ADC Dialog Box
Problem:
|
F1 Help doesn't work in ADC setpoints Dialog Box (and not in ""Revison and Serials"" Box). The index Help file is shown, the one where no Acquisiton is in. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 35900 CONTROL
One-line Description:
35900E: Status box does not reflect actual events.
Problem:
|
The following problems have been observed when running 35900E. 1) During 'before injection' timed events, the status box displays data acquistion and it should not. It should display "Executing Time Table". 2) During 'after run ends' timed events, the status box displays "Ready" and it should not. The timed events are not complete. 3) During "before injection" and "after run ends" the status box does not display "Remaining x.xx minutes". This is inconsistent. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 35900 CONTROL
One-line Description:
35900E status window does not indicate postrun mode during data analysis
Problem:
|
The 35900E status window does not indicate a postrun mode during data analysis. It goes directly to "prerun", and "not ready" which is incorrect. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned |
Keyword: 5890 CONTROL
One-line Description:
Pres/Flow box is incorrect during a run when channel is not linked
Problem:
|
Set inlet A to constant flow with some initial pressure. Calculate a split flow program on channel C linked to inlet A. Start a run. Return to the split flow screen and the pres/flow box in the bottom right of the screen will correctly display Inlet A Constant Flow and the correct pressure values. If I switch channels however, the pres/flow box will also read Inlet A Constant Flow although the channel is not linked. If the channel is not linked, it appears to take on the characteristic of the previously selected channel. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 5890 CONTROL
One-line Description:
Inlet grayed out in Packed Column when linked to non-existent channel
Problem:
|
Enter a pressure program on A and link it to aux channel D through split flow control or auxiliary pressure programs. Save method. If the method is loaded on a system which does not have an aux channel D, inlet A will still be grayed in the packed column screen even though the link cannot exist anymore. |
Problem Cause:
|
n/a |
Temporary Solution:
|
If the channel had been linked through the Aux Pressure Program, make a change to the inlet and channel and make the inlet available in the Packed Column screen. If the channel had been linked through Inlet Split Flow Control, cannot use the method for Packed Column Flow Control on the previously linked inlet. Must use another method. |
Fix Information:
|
n/a |
Keyword: 5890 CONTROL
One-line Description:
5890 GC: Software can only invert TCD polarity ONCE during the run.
Problem:
|
5890 GC with a TCD. The G2070AA Software can only invert TCD polarity ONCE during the run. The 5890 GC allows the polarity to be inverted multiple times. They should both be the same. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
In 6890 it is not possible to "de-install" a column from the software.
Problem:
|
It is not possible to de-install a column from the software in a 6890 GC. It can only be changed to another. Software should reflect configuration of the actual GC. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned |
Keyword: 6890 CONTROL
One-line Description:
6890 GC: Intrument Actuals stay at "0" instead of true value. Cosmetic!
Problem:
|
It has been reported that with ChemStation software A.04.01 on a 6890 GC the signal (1 and 2) stays at "0" in the INSTRUMENT ACTUALS display. Both signals are correctly shown in the online screen. The data file and reports are always correct. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
6890: Extd/Perf report overprints when full column information entered.
Problem:
|
Extended + Performance Report generated on a 6890 online system gives overprinting in the column information area when full column info is entered into the columns database. If partial column info is present, the overwriting does not occur. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
It is possible to set runtime events past the end of the real runtime.
Problem:
|
On a HP 6890 it is possible to set up a 20 minute run for example. It is then possible to enter an event in the runtime screen at 30 minutes and apply (download) this to the 6890 GC. Neither the GC or the software flags this as an error. . Software should be modified as follows. . . . . . . Runtime events should not be allowed past the current run time. Data analysis events should not be allowed past the current run time. If the runtime is changed from 30 to 20 minutes for example, all events that are now past the end of new run time should flag an error message to the user warning them that they will not be executed. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Check the runtime events and data analysis events when a run is made shorter or when unusual results are observed (valves on/off etc.) |
Fix Information:
|
No fix planned |
Keyword: 6890 CONTROL
One-line Description:
The runtime stops counting on 6890 GC intermittently. All data is good.
Problem:
|
It has been reported that the run time clock on the ChemStation status stops incrementing during the run very intermittently. There is no data loss. The run completes normally. Cosmetic defect only. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
It is possible to get the GC/software confused about run time (6890)
Problem:
|
During a run, it is possible to download a run length that has already passed. Ex, a twenty minute run, after ten minutes download a setpoint to set the run to five minutes. The GC stops since the run time is up. The software is still in the instrument setpoints screen. When the screen is exited, the stop has been missed. The software gets confused. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Do not change the runtime during the run to less than the current "time in run". Change after the run is finished. If you simply want to end the current run, use the STOP on the GC, or STOP RUN under instrument control. |
Fix Information:
|
No fix planned |
Keyword: 6890 CONTROL
One-line Description:
6890 Logbook entries are trunkated at 46 characters, information lost.
Problem:
|
The logbook only accepts string lengths of 46 characters. The 6890 DLL returns string lengths of up to 60 characters. The remaining characters are trunkated and information is lost. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
6890 GC: Real time plot does not show correct values after event switch.
Problem:
|
If you use a runtime event to switch from inlet pressure to FID sig for example, the values observed from holding the mouse over the real time plot (RTP) do not match what is reported by the 6890 GC. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
6890, the online signal toolset is enabled in the offline session.
Problem:
|
In a 6890 offline session, the toolset button Display online signals and instrument actuals is not grayed. It is supposed to be grayed since there are no online signals in an offline session. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned |
Keyword: 6890 CONTROL
One-line Description:
6890 sequence/method toolset button is grayed out in error.
Problem:
|
One of the sequence/method toolset buttons is grayed. This was originally done when its selection was used to bring up the online signals. These buttons are now simply view switches and not specific to the online signls, they should be ungrayed. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned |
Keyword: 6890 CONTROL
One-line Description:
6890 GC with fast oven will not run the on line tutorial correctly.
Problem:
|
When the 6890 has a fast oven the A.04.01 tutorial does not work. Error message, With this configuration cannot perform :Edit the oven parameter. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
6890 GC: HP Core has caused a GPF in module TBPO3W.DLL at 0001:302B
Problem:
|
HP Core has caused a GPF in module TBPO3W.DLL at 0001:302B. This problem occurs only when the Novell network is enabled. Problem is with VLM.EXE Novell network file. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Only solution at the moment is to set up dual boot system. |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
6890: Syntax Error when sending setpoints to the GC.
Problem:
|
Very intermittently, When using flow rates (ex for an inlet) that are at or near the maximum allowable value, it is possible that when these values are sent to the HP6890 GC that the GC will return a "Syntax Error". A Synax Error is when the GC recieves a command with a variable out of limits. |
Problem Cause:
|
This is caused by converting the setpoint into a GC recognizable form and exceeding the maximum allowed. This situation may also occur when one setpoint is set that causes another to approach their maximum. |
Temporary Solution:
|
These situations involve corner cases of operation and should not be encountered when operating the system under normal conditions. Often just slightly lowering the contributing setpoint value will remedy the situation. |
Fix Information:
|
No fix planned |
Keyword: 6890 CONTROL
One-line Description:
6890: Cannot make automated runs with 6890/35900C/G1512 as single inst.
Problem:
|
User is unable to make automated runs with the HP 6890 GC, HP 35900C A/D and HP G1512 Sampler set up as a single instrument session. Note, 35900C only, the 35900D (Win 95 only) and 35900E work correctly. |
Problem Cause:
|
The start/stop logic of the 35900C was designed for the HP 5890 GC and is not compatable with the HP 6890 when the sampler is attached. The 6890 is designed to not inject if any external device reports not ready. |
Temporary Solution:
|
Use a 35900E instead. Works with Windows 95 and Windows NT. Use a 35900D instead. Works with Windows 95 only. |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
6890 Syntax Error CCER IFxxVI P3 E14 EN when VI setpoints are changed.
Problem:
|
Splitless Mode with a Headspace or P&T. At the end of each run, the 6890 goes into Prep Run Mode when the GC becomes ready. When the system is in this mode and the operator changes a flow or loads another method which is set up as splitless, there will be the VI syntax error. Explanation of the Syntax Error is as follows...... A SYNTAX error is generated in the 6890 GC when it receives a command it cannot, or will not, execute. ccer ifgcvi p3 e14;en CCER Communications error IFGCVI Inlet Front (GC) Volatiles Interface P3 Parameter 3 is in error, depends on mode of operation. E14 Parameter is actually valid, but not allowed at this time. EN END of information. In this case, the command string sent by the software is a valid string, but the GC will not execute the command because it is in pre run mode. |
Problem Cause:
|
n/a |
Temporary Solution:
|
At low flows, there is not enough control to ensure accurate chromatography. It is highly recommended that customers run in split mode which works correctly. Only temporary workaround at the moment if the user want to modify the setpoints after a run is to turn auto prep run OFF from the GC front panel, make the changes, save the method, then turn auto prep run back ON before running the method. To turn prep run ON/OFF from the GC front panel select CONFIG, scroll down, INSTRUMENT, enter, AUTO PREP RUN (ON/OFF). Press START/STOP to have the setting take effect. |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
6890: Pressure entered in 6890 software different than value at GC.
Problem:
|
n/a |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
6890: Error message "Power off/on detected" intermittently.
Problem:
|
There are now multiple sites where the error message "power off/on detected" is apearing on the ChemStation. This is sometimes caused by turning the oven off or on, or opening or closing the oven door which has the same effect. There are also sites where computer loading has caused a similar effect. This has been duplicated by running "Pinball" and also by printing complex colour chromatograms. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Workarounds are... Do not play PC games, do not play music. Run the printer at lower resolution, or replace with a laserjet. 6890 AC boards have been modified (starting June 98) to eliminate the problem when opening and closing the oven door. |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
6890: Autosampler setpoints may be lost during method resolution.
Problem:
|
Autosampler setpoints (washes, pumps, strokes, etc.) might be lost during Method Resolution when starting up a 6890 GC Instrument session. Note. Method Resolution is invoked when the method being loaded has a different instrument hardware configuration, for any reason, than the actual on-line instrument configuration. |
Problem Cause:
|
Autosampler setpoints are lost when they are edited DURING method resolution because the software does not know what type of injector is installed. Defaults are loaded. |
Temporary Solution:
|
Workaround. DO NOT edit the autosampler setpoints during method resolution. After the method is saved, the original setpoints will be retained and available for editing. |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
6890: Tower fan off/on on GC gives wrong info with ChemStation running.
Problem:
|
Configuration is a 6890 with an I-ALS and an injector. A3.05 firmware. With the ChemStation running, from the 6890 front panel, if you select Configure Injector, Tower Fan OFF/ON, and then select INFO, you get the wrong information. From the 6890 front panel and NO ChemStation, or the ChemStation is not running, if you select Configure Injector, Tower Fan OFF/ON, and then INFO, you get the correct information. NOTE. Without the Chemstation running, there is an additional line on the 6890 display for the nanoliter adapter ON/OFF. With the ChemStation running, the line is eliminated by choice since the software controls all of the nanoliter setpoints. |
Problem Cause:
|
Reason is that when the ChemStation is running the 6890, the user is not allowed to select the nanoliter adapter from the 6890 front panel. The line on the display is removed and the next line moved up. When INFO is selected, the wrong information is displayed. |
Temporary Solution:
|
Workaround. Do not use the info key. |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
Initialisation Problem ( Please Report to HP) when adding a new column.
Problem:
|
n/a |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
Companion: Parsing error when using Companion and 6850GC
Problem:
|
In the last screen for editing sample data: .....If here the [ENTER] key is used The sequence is not started The error message: Parsing error. The PC must be rebooted. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
6890 GC: Floating point exception INVALID NUMBER detected.
Problem:
|
6890 GC chemstation. "Floating point exception INVALID NUMBER detected" when selecting "PLOT" with zero channels selected. Selecting PLOTwith no channels selected causes an error in..... "C:\HPCHEM\CORE\HPCORE.EXE Pressing the OK Button "An error has occurred in your application. If you choose ignore you should save your work in a new file. If you choose close your application will terminate. Pressing close button: "HPCORE casused a GPF in module HPCORE.EXE at 0003:36C5, choose close HPCORE will close" |
Problem Cause:
|
n/a |
Temporary Solution:
|
DO NOT select PLOTwith no channels selected. Select at least ONE or more channels, before selecting PLOT. |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
6890: Method resolution needs better explanation in the HELP system.
Problem:
|
The method resolution is very confusing to customers. We need a better explanation of why method resolution happens, and what it does, in the HELP system. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
Companion. Cannot SAVE GPL data when running a sequence.
Problem:
|
The sequence will not run when the SAVE GLP DATA has been choosen. Single runs do work, (Run Method) . |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
6890: Help for FID makeup flow shows invalid options. (Software is correct).
Problem:
|
Revision A.08.03 with a 6890 with a FID. The Help system shows invalid entries for FID makeup flow. These are N2 (Nitrogen), H2 (Hydrogen), He (Helium), and ArCH4(Argon Methane). Should be N2 (Nitrogen) and He (Helium). |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: 6890 CONTROL
One-line Description:
6890N: After startup the 6890N time is one hour ahead of the PC time.
Problem:
|
After starting the G2070AA ChemStation with a 6890N connected, the local 6890N time is one hour ahead of the local computer time. Problem only appears between approximately November 1st and April 1st. During Daylight Savings Time (DST) April to end of October, the time is correct on the GC. NOTE. This affects the 6890N only, the 6890A does not get the date/time from the ChemStation. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The defect is benign. It has no effect on the operation of the ChemStation or the 6890N. The 6890N time is NOT read back into teh ChemStation and is not used in any of the ChemStation reports. WORKAROUND. If required, set the 6890N time to the local time using the 6890N front panel. |
Fix Information:
|
n/a |
Keyword: 7673 CONTROL
One-line Description:
Error, Vial Number field 1. Value = 101, range (1,100)
Problem:
|
It has been reported that with certain configurations when there is only a single injector that the following error message will appear at the end of a sequence or a partial sequence..... Value out of range in method/sequence file for command VialNumber field1 Value=2, Range[201,203] |
Problem Cause:
|
n/a |
Temporary Solution:
|
Click on the OK button. The error will not appear again until the HP 7673 automatic sampler configuration is changed, and then only the first time again. |
Fix Information:
|
n/a |
Keyword: 7673 CONTROL
One-line Description:
7673 abort is unpredictable.
Problem:
|
Choosing Abort immediately after a 7673 injection and selecting Abort on the 7673 error report dialog box can cause unpredictable results. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Wait a few seconds after injection before aborting the run. |
Fix Information:
|
n/a |
Keyword: 7673 CONTROL
One-line Description:
STOP or ABORT have timing windows that can cause problems.
Problem:
|
Because of the many necessary liaisons between the autosampler, the GC and the core software, there are "windows of opportunity" to stop and / or abort runs that causes problems to the software. Example, aborting the run after the autosampler has received the vial(s) but before the injection is made, or opening the sampler door during one of the vial transfer operations sometimes causes recovery errors. STOPing or ABORTing the run immediately at injection time may not STOP or ABORT the run until the end. Manual injection methods started from run control, as opposed to the start button on the GC, cannot be stopped from the software. (USE ABORT) |
Problem Cause:
|
n/a |
Temporary Solution:
|
After an abort, "return vials to tray", do not start the next run while the robot arm is transporting the vials back to the tray. The system does show ready during the return operation AND SHOULD NOT. Do not abort the run immediately at, or after the injection takes place. Wait 6 seconds (0.1 minute) to abort. This works correctly. Do not open the door to abort to run, but if you do, select ABORT at the "door open" error message and return the vials by hand. Errors have been reported depending where the robot arm, turret, and injector stop. This is very very difficult to reproduce. |
Fix Information:
|
n/a |
Keyword: 7673 CONTROL
One-line Description:
Inj volume in sequence table only uses the syringe size from the front.
Problem:
|
The syringe size specified in the FRONT configuration parameters of the Injector setpoints screen, is used for both front and rear in the Inj Volume of the sequence table, and should not. Each one shoud be independant. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
To be fixed in the next release. |
Keyword: 7673 CONTROL
One-line Description:
G1513A viscosity delay in the MANUAL does not match the real behaviour.
Problem:
|
The description of the viscosity delay in the G1513A manual does not match the actual operation of the software. This is included here for reference only. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The software is correct, for a more complete description of the operation refer to the INJECTOR help. |
Fix Information:
|
To be fixed in the next printing of the manual. |
Keyword: 7673 CONTROL
One-line Description:
6890 / 7673 with 5 uL syringe injects the wrong volume.
Problem:
|
A 6890 / G1512 autosampler will inject the wrong volume if the syringe is configured as a 5 uL in the Edit parameters/Injector/configure screen. One half the selected volume is injected. The actual injected volume is correctly listed on the report. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Workaround is to use a 10 uL syringe, or if a 5 uL syringe is used, configure it is a 10 uL syringe to get the correct volume injected. The problem is that with a 10 uL syringe, one stop gives 1 uL. With the new 5 uL syringe, a full stroke (5 uL), only moves the plunger as far as a 5 uL sample on a 10 uL stringe. |
Fix Information:
|
n/a |
Keyword: 7673 CONTROL
One-line Description:
Injector changes may be lost when entered on 6890 keypad.
Problem:
|
When making chages in the GC Sampler paramether from the HP 6890 Keyboard, some changes may be lost. Reason: As the computer is interacting with the GC to upload one change, if the user makes another change, the second change may be lost. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Do not use the 6890 keyboard to make changes. After all changes are entered, the user should verify that they have been retained. This may be done by scrolling the parameters so that the changed parameters are not displayed and then scroll until they are displayed. If any value is lost, re-enter it and verify again. The parameters may also be verified with the method dialog on the PC. |
Fix Information:
|
n/a |
Keyword: 7673 CONTROL
One-line Description:
35900: First (only) session wil not start up after installation.
Problem:
|
After installing the ONLY session and it is a 35900 (GC), the session will not start up because of problems with the language files. . Error message is in a HPNLS window stating: "ERROR: NLS could not load the base resource DLL: C:\HPCHEM\DRIVERS\LANGUAGE\HBAD0A00.ENU". Clicking OK, locks the session. . This is true for windows 95 and Windows NT. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Install a GC session either at the same time, or after the 35900 session. This installs the correct language files on the system. |
Fix Information:
|
n/a |
Keyword: ACQ
One-line Description:
Online Session Crashed Without HP-IB Card Installed
Problem:
|
The HP ChemStation may crash if an online session is started and there is no HP-IB or 35900E card present in the PC. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Do not run online sessions of the HP ChemStation if no HP-IB card is present in the PC. All instrument screens are available from the offline session as well. |
Fix Information:
|
n/a |
Keyword: ACQ
One-line Description:
Elapsed run-time of last run displayed shorter than stop-time
Problem:
|
Sometimes, the 'Last run' time displayed changes after the end. This was observed with a 1090. The stop time was 4 minutes. After the end of the run the 'Last run' time changed to 3.9. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: ACQ
One-line Description:
FLD with A.04.03 showed unexpected chromatogram after installing
Problem:
|
After updating A.04.02 to A.04.03 on a system comprising an HP1100 and a 1046 FLD the chromatogram might have digital drop outs. |
Problem Cause:
|
There is no cause of this problem known. This was a one time event only. |
Temporary Solution:
|
Reinstall the software. |
Fix Information:
|
n/a |
Keyword: ACQ
One-line Description:
shift in spectra create incorrect apex spectra
Problem:
|
Using DAD and FLD system following issue has been reported using ChemStation: Acquiring "Full spectra" in 1 nm stepsizes with various peakwitdth settings the datafile may show 1. missing spectra information within over the chromatogram time 2 shifted apex spectrum for the certain peaks, so that the apex seems to be located at the downslope of the peak |
Problem Cause:
|
ChemStation running on fragmented operating systems or system without a maintained operating system are not able to save the continously delivered information from the DAD/FLD due to high fragmentation on the PC. The PC is then not able to store the data information in time, spectra information might be delayed, because the ChemStation has higher priority set for the signal. |
Temporary Solution:
|
This problem is seeems to be related to systems, which will need PC maintance. Cleaning up the temp files and running defragmentation will solve the problem for nearly all cases. |
Fix Information:
|
n/a |
Keyword: CALIBRATION
One-line Description:
Calibration Settings: Activate "Use ISTD"
Problem:
|
How activate the "Use ISTD" field in the Calibration Settings? In order to use a specific ISTD compound for quantification of uncali- brated peaks, set the calulation mode to ISTD or ISTD% (Specify Report/ Quantitative Results), then activate "With Rsp Factor" in the options for the calculation of uncalibrated peaks in the Calibration Settings dialog and specify the appropriate ISTD compound name. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: CALIBRATION
One-line Description:
RT Window Color Bar not updated correctly
Problem:
|
If one has a different RT Window for a 'Reference Peak' than for an 'Other Peak', and defines the compound in the calibration table to be a reference peak, the width of the color bar of that peak in the chromatogram window is not modified. If one first declares the peak to be a time reference, and afterwards modifies the time window, it is done correctly. The same phenomenon occurs if one declares a 'time ref' peak as 'other'. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: CALIBRATION
One-line Description:
Correlation coefficient r from ChemStation not same as in Excel
Problem:
|
How is the correlation coefficient displayed in the calibration curve calculated ? |
Problem Cause:
|
n/a |
Temporary Solution:
|
The manual indicates a formula for the regression coefficient r^2. The correlation coefficient is the square root of this. |
Fix Information:
|
n/a |
Keyword: CALIBRATION
One-line Description:
No. of digits for smpl prm in Calib. setting, seq. tbl, smpl info differ
Problem:
|
The sample information amount, multiplier and dilution can be set in three different places with three different accuracies. The customer perceives this as inconsistent, as the report looks always the same. Here is a summary for the multipier. 1.Report Always reports the multiplier with 4 decimal digits and maximal 7 (3.4) digits, before switching to exponential notation. Trailing zeros are reported. 2.Multiplier in Calibration->Calibration settings->Sample defaults The field accepts many digits, but after closing and reopening they will be rounded to 3 decimal digits with trailing zeros. A maximum of 6 digits (3.3) is allowed. If more than 3 digits are before the decimal point, trailing decimal digits will be displayed as 0. Report A multipier of 5.555 will be reported as 5.5550 3.Multiplier in Sequence table A total of 12 digits (including decimal point) is allowed, no rounding or truncation happens. Report A multipier of 5.55555 will be reported as 5.5556 4.Multiplier in RunControl->Sample Info->Sample Parameters The field accepts 13 digits (including decimal point). After closing and reopening of the dialog box, the value will be rounded to 6 decimal digits without trailing zeros. A maximum of 7 digits (3.4) is allowed. Report A multipier of 5.55555 will be reported as 5.5556 Summary Using the multiplier from the calibration settings dialog can be misleading, as it will be rounded to 3 decimal digits and the report will indicate 4 digits with trailing zeros. Generally the setting of the multiplier should be consistent in the different areas and the report. |
Problem Cause:
|
n/a |
Temporary Solution:
|
When the report does not deliver the accuracy required, use a combination of dilution and multiplier to display the required value. |
Fix Information:
|
n/a |
Keyword: CALIBRATION
One-line Description:
Wants to specify what recalibration should be reported in a sequence
Problem:
|
n/a |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: CALIBRATION
One-line Description:
'CalTabMain parameter 3: a value is outside legal range'
Problem:
|
When opening the calibration table a message is displayed: 'CalTabMain parameter 3: a value is outside legal range' |
Problem Cause:
|
This might be caused when adding compound names after selecting to delete lines with zero amount without closing the calibrationtable. |
Temporary Solution:
|
Do not select "Return to Calibration table" when lines were deleted in teh calibration table. Close the calibration table and open it again from the menu Calibration -> Calibration table |
Fix Information:
Keyword: CALIBRATION
One-line Description:
Unknown Error Message, 1 Unknown CP Identifier, 640x480 VGA monitor.
Problem:
|
Using the calibration user interface with a screen resolution of 640*480 will result in an error message Parameter 1, Unknown CP Identifier in Calibration Table |
Problem Cause:
|
n/a |
Temporary Solution:
|
Set the video resolution to SVGA or better, 800x600 minimum. With some video drivers, Windows does not pass the correct resolution information on the HP ChemStation, even if it is set correctly. In this case, you can add the following line to C:\HPCHEM\CORE\TOP.MAC: SetTabHdrVal _Config, Window, CrtXResolution, 800 This command should be the first command in the macro named "Top". |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - and more in this context these issues are fixed. |
Keyword: CALIBRATION
One-line Description:
Calculation Formulae used for ISTD recalibrations
Problem:
|
In the HP ChemStation, Response factor is defined as: Area of X Concentration Istd EQTN 1 RF = --------- * ----------------- Area Istd Concentration of X Normally, the Response Factor would be calculated according to EQTN2 after a number of recalibrations: __ RF1 + RF2 + RF3 + RF4 + RF5 + RF6 EQTN 2 RF = --------------------------------- 6 or: - - Sum i=1,n __ EQTN 3 RF = ------------------------------------------------ n Whereas the Chemstation calculates this to be Sum { Area X(i) } Sum { Conc Istd(i) } __ i=1,6 i=1,6 EQTN 4 RF = ---------------------- * ---------------------- Sum { Area Isd(i) } Sum {Conc X(i)} i=1,6 i=1,6 Equation 3 and 4 do not give the same values. The Chemstation to perform the calculations in Equation 3 rather than those in equation 4. For instance X INT Std area ng area ng RF level --------- ------- ------ 1 1000 100 500 50 1.00000 2 900 100 510 50 0.88235 3 850 100 505 50 0.84158 sum 2750 300 1515 150 Equation 3 gives (1.0000 + 0.88235 + 0.84158) / 3 = 0.90798 2750 150 Equation 4 gives ---- * --- = 0.90759 1515 300 |
Problem Cause:
|
The observation is correct. In order to satisfy backward compatiblity needs (all HP ChemStation since the HP ChemStation Pascal Series), the current algorithms use the formulae described above. |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: CALIBRATION
One-line Description:
Info for amount ratio and area ratio ISTD missing in calibration tbl.
Problem:
|
Area ratio and amount ratio of ISTD calibration are not displayed in calibration table. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Click on the calibration curve, select View, Window Function, and List Content. Then click on List Data. This will display the ratios. |
Fix Information:
|
n/a |
Keyword: CALIBRATION
One-line Description:
Multi level calibration not possible with Manual calibration table
Problem:
|
Multi level calibration is not possible with a manual calibration table. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use Automatic Setup if you need a multi level calibration. |
Fix Information:
|
n/a |
Keyword: CALIBRATION
One-line Description:
Manual calibration table warns for more cal. points
Problem:
|
The message "Warning: Curve requires more calibration points" appears upon closing a manual calibration table and the report always contains a calibration warning. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Set the Calibration Settings to: Curve = linear Origin = include Weight = equal |
Fix Information:
|
n/a |
Keyword: CALIBRATION
One-line Description:
Compound specific multipliers got set to zero
Problem:
|
Compounds are reported with amount zero even if they are identified. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Check the individual multiplier for this compound in the calibration table. It needs to be set to 1 (or the multiplier required). Also check the calibration table settings if all amounts of identified peaks are reported as 0. |
Fix Information:
|
n/a |
Keyword: CALIBRATION
One-line Description:
Single peak summing table entry is missing in calibration table printout
Problem:
|
If only one entry for peak summing exists in the calibration table it is ignored during calibration table printout. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Add an additional line to the peak summing calibration table . Do not enter any parameters for quantification (i.e. RT range, RF, Ref.). Calculated results are not affected by this defect. |
Fix Information:
|
n/a |
Keyword: CALIBRATION
One-line Description:
There are missing shortcut keys in the "Calibration Settings" dialogbox.
Problem:
|
There are many missing shortcut keys in the "Calibration Settings" dialog box. This is inconsistent with other screens. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: CALIBRATION
One-line Description:
A report after a change in the calibration table contains old values
Problem:
|
A report generated after a change in the calibration table might contain use the previous data. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Make sure that Enter is pressed on the keyboard or selected in the calibration table after the change. |
Fix Information:
|
No fix planned |
Keyword: CALIBRATION
One-line Description:
RT corrections are not used for on-line (no report) peak identification
Problem:
|
If a time reference peak is used in the calibration table UI, the corrected RT is not used for the on-line peak identification: - The colored RT windows are not corrected - The peaks are labled as identified without time reference peaks. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Generate an on-screen report to check the identification using a time reference peak. The user interface is than updated with this identification (except for the colored RT windows). You can also use batch review for updatinng the identification based on a time reference peak. |
Fix Information:
|
n/a |
Keyword: CALIBRATION
One-line Description:
Calibration table: 'Parameter2: Table was not found'
Problem:
|
When mixing automatic and manual calibration table setup an error message might occur: 'Parameter2: Table was not found'. |
Problem Cause:
|
The calibration table setup does not support mixing of manual and automatic setup. |
Temporary Solution:
|
Do not mix automatic and manual setup of the calibration table. In case you experience this error reload the default method and create a new calibration table. |
Fix Information:
|
n/a |
Keyword: CALIBRATION
One-line Description:
Reference to ISTD # in calibration table view is not visibly updated
Problem:
|
When changing the identification number assigned to an internal standard in the calibration table it was reported that the identifier of the compounds referencing to this standard may not be visibly updated in the current view. |
Problem Cause:
|
This is due to the calibration table view not being properly updated. Internally all entries are handled correctly. |
Temporary Solution:
|
Closing and reopening the calibration table reveals the correct assignments. |
Fix Information:
|
n/a |
Keyword: CALIBRATION
One-line Description:
Linear regression using force through origin option is not correct
Problem:
|
The calculations used for the linear regression curve with the option force through origin are not correctly explained in the Understanding your ChemStation manual and the help text. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The calculations use the formula Y = A x Y to calculate the slope. The points used to calculate this curve are generated by mirroring the data points in the origin. The mirrored points are used together with the original data points to calculate the regression curve resulting in the slope A. -------------------------------- (x) (x) (x) |
Fix Information:
|
n/a |
Keyword: CALIBRATION
One-line Description:
Printing ISTD calibration table causes error: A value is outside the legal range
Problem:
|
The error message Parameter 3: A value is outside the legal range. CalTabMain: Execution error in macro evaluate at level 3 in cmd/fct TabVal CalTabMain: loaded from STDIN's line 1 with CRC DEDA CalTabMain: Parameter 3: A value is outside the legal range. can appear if a calibration table using an ISTD is printed without selecting the ENTER button of the calibration table first. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Always click on the ENTER button of the Calibration table user interface before printing the calibration table. |
Fix Information:
|
n/a |
Keyword: CALIBRATION
One-line Description:
ISTD calibration: warning message - curve requires more calibration points
Problem:
|
When closing the calibration table a warning message appears: 'Curve requires more calibration points' |
Problem Cause:
|
In the calibration settings the default origin usage is set to 'Ignore' for all compounds in a linear multi-level calibration including the ISTD. Only one ISTD with a constant amount is used for all levels. When closing the calibration table the consistency check for the calibration table detects a mismatch with the default setting for the origin usage and reports it. The reason is that at least two datapoints are required for a linear calibration curve. This warning does NOT AT ALL affect the ISTD calculation. For each level of a particular peak the individual response and amount ratios are calculated. These ratios are then used to construct the calibration curve. The warning does only notify the user of the insufficient number of datapoints and at the same time corrects the detected problem by changing the origin usage to 'Include' for the ISTD. This warning generally appears if the number of available datapoints for a compound is not sufficient for the calibration curve type specified in the calibration settings. |
Temporary Solution:
|
To get rid of the calibration warning the following procedure may be applied: 1. Change the calibration table view to 'Peak Details'. 2. Remove the checkmark for the ISTD compound from the 'Def' column. This will prevent the software from overriding the origin usage specified in the calibration table for the individual compound with the default value specified in the calibration settings. The warning will no longer appear. |
Fix Information:
|
n/a |
Keyword: CALIBRATION
One-line Description:
Settings for Origin Incorrect for "Average Resp/Amt"
Problem:
|
In the "Calibration settings" dialog box you can select the Option "Ignore" for the origin in the "Default Calibration curve" group. However this option is not used if the curve type is set to be "Average Resp/Amt". |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: CALIBRATION
One-line Description:
Calibrated compound found as uncalibrated one using library search report
Problem:
|
In case a multi-wavelength calibration table is setup to calculate signals seperately, it can happen that a calibrated compound appears in the listing of uncalibrated compounds of a library search report, while it is not listed in the calibrated compounds part. |
Problem Cause:
|
This happens if the compound is also found in the second signal, wich is not calibrated for this compound and the retention time is closer to the expected retention time of the calibration table. The time difference is usually so small that it cannot be judged by the retention times listed on the report. The defect is that the algorithm does not check the signal number when comparing retention times and 'calculate seperately' is selected. |
Temporary Solution:
|
The problem can be avoided either by - not calculating signals seperately when using a library search report or - calibrating all signals where a compound actually shows a response |
Fix Information:
|
n/a |
Keyword: CE ACQ
One-line Description:
Autobalance option for CE does not appear in the time table
Problem:
|
The autobalance feature is not displayed in the time table of the CE ChemStation. Loading a method that has a time table using this function cause an error message. |
Problem Cause:
|
n/a |
Temporary Solution:
|
You need to update the CE firmware to a newer revision. |
Fix Information:
|
n/a |
Keyword: CE ANALYSIS
One-line Description:
HPCORE caused a GPF in module HPTED01.DLL at 1c:069a
Problem:
|
Resource problems on multi instrument CE ChemStation A.04.01 running under Win95. "Edtab 24: out of memory", "system dangerously low on system resources" HPCORE caused a GPF in module HPTED01.DLL at 1c:069a |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: CE ANALYSIS
One-line Description:
Current, voltage, temperature not available if only DAD signal is loaded
Problem:
|
If a CE signal is loaded using signal details the report displays not available for current and other instrument signals. |
Problem Cause:
|
Signal details specifies what signals should be loaded. If the current or othe rinstrument signals are not explicitly specified there, they will not be loaded and are thus not available for data analysis and reporting. |
Temporary Solution:
|
If signals are loaded with the load "Using signal details" option selected, make sure that also the instrument signals are selected. |
Fix Information:
|
n/a |
Keyword: CE CONTROL
One-line Description:
Shortage of Global Memory after hours of CE fraction collection
Problem:
|
When acquiring noisy signals using a peak detector threshold of 1 mAU in the fraction collection mode of the CE, the PCs global memory resources may decrease dramatically within a couple of hours of data acquisition. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Increase the threshold for the peak detector. For fraction collection mode, you should set an absorbance threshold that is slightly below the absorbance maximum of the fraction's peak. The default setting is 100mAU. |
Fix Information:
|
n/a |
Keyword: CE CONTROL
One-line Description:
CE: exiting 'Setup injection' dialog box during run sets current to zero
Problem:
|
When a CE system is in 'Run Mode' and the 'Setup Injection' dialog box is accessed and closed clicking ok (Instrument menu) the voltage goe to zero within the analysis. This does only happen when a time table used for the voltage. If no ramp is used the voltage doesn't drop. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use the offline copy to review the method parameters. |
Fix Information:
|
n/a |
Keyword: CE CONTROL
One-line Description:
CE-MS: Electropherogram disappears from screen when running sequence.
Problem:
|
In CE-MS, when a method with standard data analysis is run in a sequence, after the run the window "current electropherogram" and the window "current mass spectrum" appear. However, while the mass spectrum stays correctly on the screen , the electropherogram disappears after a few seconds, while the empty window with the axes stays on the screen. This does not happen after a single run. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: CE CONTROL
One-line Description:
CE system: Pressure are not applied correctly
Problem:
|
Running A.10.02 CE ChemStation in serial mode, using external pressure following behavior is seen: 1. without pre or post conditioning the correct high pressure from the main method setting is used 2. As soon as pre or post conditioning is used and a pressure setting is defined in the timetable, that pressure remains during the whole run and the system is not going back to the system pressure. --This problem is intermittend 3. as soon as pre and post conditing are used, the problem is always using the pre condition set pressure and changes only the pressure for the post conditing. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Following workaround should be used to avoid this issue: 1. using pre and post condition Please add an additional line in the pre conditioning using exactly the same pressure like it should be applied during the run, even a short time will be enough. By doing so the correct value will be used to run the method and it works as well in the sequence. 2. only post condition Please add an additional line in the post conditioning using exactly the same pressure like it should be applied during the run, even a short time will be enough. By doing so the correct value will be used to run the method and it works as well in the sequence. 3. only pre condition this failure is intermittent, To avoid that intermittent failure, please add an additional line in the p reconditioning using exactly the same pressure like it should be applied during the run, even a short time will be enough. |
Fix Information:
|
n/a |
Keyword: CE CONTROL
One-line Description:
CE: Partial Sequence initializes very slowly directly after loading a method
Problem:
|
When you open the Partial Sequence dialog immediately after you loaded a method, the Partial Sequence dialog takes very long to open (up to 2 minutes). |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: CONFIGURATION
One-line Description:
HPCED02 caused a GPF in HPUTIL02.DLL at 000c:0000 0020
Problem:
|
The following error occurs in the HP ChemStation configuration editor if the HP ChemStation is installed on a networked drive and no drive designator was specified (e.g. \\server\hpchem). Windows 95 does not require a drive designator for Microsoft Client network drives. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Avoid the GPF by specifying drive designators for all installation directories. |
Fix Information:
|
No fix planned |
Keyword: CUSTOM REPORT
One-line Description:
Custom Report Designer: Logos in Header/Footer
Problem:
|
Due to limititations in the ChemStation's print module, it is currently not possible to add a bitmap to the header or footer sections of a customized report template. |
Problem Cause:
|
n/a |
Temporary Solution:
|
As a work-around, add the required bitmap (e.g. your company logo) to a general section. Unfortunately, this will not print the graphic on every page. |
Fix Information:
|
No fix planned. |
Keyword: CUSTOM REPORT
One-line Description:
Error 17923 occurred in Command TabText$ in macro FRPT_PrintDispatcher
Problem:
|
When printing a report using a template of the Report Layout Designer that requires printing of 'Column parameters', the following error message may be printed on the report: Error 17923 occurred in Command TabText$ in macro FRPT_PrintDispatcher at line 1099 in file C:\CORE\FRPT.MCX: Parameter 3: A value is outside of the legal range. |
Problem Cause:
|
This error was caused by a reference to a ChemStation table that was not present in the current data file. The table cell was referenced in a "computed text" field. The macro implementation of the "computed" field must check for the existence of the referenced table items, e.g. by trapping error returns with an appropriate "on error" statement. |
Temporary Solution:
|
n/a |
Fix Information:
|
no fix planned. |
Keyword: CUSTOM REPORT
One-line Description:
Calibration Reports in Customized Reports
Problem:
|
Calibration Reports are not printed if a customized report is used in the data analysis method. During run-time of the customized reports, this information (calib. table before/after recalibration) is not available. The calibration report settings (Advanced Calibration) are ignored when customized reports are used. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
no fix planned. |
Keyword: CUSTOM REPORT
One-line Description:
Sequence: Customized reports may start with empty lines
Problem:
|
If in a sequence, one method uses a customized report style and the previous method used a standard report, then occasionally the customized reports may include a number of blank (empty) lines in the header. All following reports are correct (no blank lines). |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use the following command as a pre-run macro in the method that uses the customized report style: SetPageLoc 0,0 |
Fix Information:
|
No fix planned |
Keyword: CUSTOM REPORT
One-line Description:
Could not execute user defined Macro USR_ Libcompare
Problem:
|
With some data files and libraries the following error message is generated when printing a customized report using the library template installed with the HP ChemStation. The error message is: Could not execute user defined Macro USR_ Libcompare (c:\hpchem\repstyle library.mac,115,Parameter3 : A value is outside the legal range) |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: CUSTOM REPORT
One-line Description:
Custom Report Layout: missing chromatogram when using autoscale
Problem:
|
n/a |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: CUSTOM REPORT
One-line Description:
Custom report uses wrong time format for AM / PM in printout
Problem:
|
If custom time format with the default entry of hh:mm:ss #am #pm is used in a custom report, times between 12PM and 1PM will be printed as 00 for the hour. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Do not use custom time format. Select use Settings from Windows Control Panel. |
Fix Information:
|
No fix planned |
Keyword: CUSTOM REPORT
One-line Description:
Adding HP 1100 Column Info in Customized Reports
Problem:
|
Error 17923 occurred in Command TabText$ in macro FRPT_PrintDispatcher at line 1208 in file C:\HPCHEM Parameter 3: A value is outside the legal range. With some data files, including the DEMO\INKS files, when column description, column batch and column serial # is placed as a variable or a field in the general section of a Report Layout .FRP file, this error occurs. |
Problem Cause:
|
n/a |
Temporary Solution:
|
This error should not occure with data acquired on the same revision as the report is generated. |
Fix Information:
|
No fix planned |
Keyword: CUSTOM REPORT
One-line Description:
Customized Reports, calibration curve not complete
Problem:
|
Calibration Curve output graphics added to a customized report template may be printed incompletely. The graphics borders of the calibration curves may be missing. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: CUSTOM REPORT
One-line Description:
Report template can be removed, although used in a method
Problem:
|
The ChemStation does not store a customized report as part of a Chem- Station method. If a customized report template is deleted, no consistency check is performed to indicated that the template was actually in use by a method. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: CUSTOM REPORT
One-line Description:
Custom Report layout generates extra row of peak Data
Problem:
|
n/a |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned |
Keyword: CUSTOM REPORT
One-line Description:
Header section of custom report is omitted in sequence summary
Problem:
|
The header section of a custom report which is printed as part of a sequence summary report does not get printed. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Turn off sequence summary reporting but print the same report as part of the method. The header is correctly printed that way. |
Fix Information:
|
n/a |
Keyword: CUSTOM REPORT
One-line Description:
Custom Reports "Injection Date" and "Injection Time" don't work correctly.
Problem:
|
Defect is when you select Injection date OR Injection time in the General section of Custom Reports, you always get "mm/dd/yy hh:mm:ss". This is the complete string for each instead of half for date and half for time. Changing the format does not work either. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: CUSTOM REPORT
One-line Description:
Header section from report template is not printed in Sequence summary report
Problem:
|
Setup for sequence summary is to print individual reports , Task #6 Print analysis reports is selected The report type is a selfmade custom report with Header and General Section (like the area%report template) The header section of the individual report is missing in each individual report. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Workaround is not to use a Header section and put all Header info's in to a "General" section. |
Fix Information:
|
n/a |
Keyword: CUSTOM REPORT
One-line Description:
Fraction Collector and Report LAyout
Problem:
|
Using the report layout to create reports for fraction collection, the ChemStation does not show the fraction collection tickmarks within the customized report layout. The fraction tickmark option has to be set in the Data Analysis, Specify Report section. Enabling the selection will put the fraction tickmarks to the standard ChemStation reports. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
Starting with B.03.01 Fractions will be printed in the customized report, no fraction tickmarks. |
Keyword: CUSTOM REPORT
One-line Description:
Report Layout problem with CE ChemStation only.
Problem:
|
Using CE Chemstation A.08.01 or higher following issue has been reported using Customized Report Layout under following special conditions: Including a "result table" within the customized report layout and set it in the Specify Report option of the ChemStation, the system will give following red message: Could not format table |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use one of the predefined report layouts with a "result table" already placed in the template. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Signal Options: Autoscale
Problem:
|
Signal Options/Autoscale should only be used for GC Chromatograms to prevent the solvent peak from defining the y-axis scaling. For a GC Chromatogram, autoscale scales the chromatogram to the size of the peaks that come after the (large) solvent peak. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Instrument Curves displayed twice
Problem:
|
The instrument curves (data curves for solvent composition, flow, temperature etc.) can be selected for display either by... 1) adding the appropriate data curve to the list of signals to be used by the data analysis method (Signal Details dialog) or 2) by selecting the appropriate settings in the "Edit Instrument Curves" dialog. It is possible to specify data curves in both ways at the same time which will result in duplicate representation of the corresponding instrument curve. |
Problem Cause:
|
n/a |
Temporary Solution:
|
To display instrument curves, either add them in the Signal Details dialog OR using the Edit Instrument Curves dialog. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
"Could not open data file" reported on Novell Netware client
Problem:
|
The error messages "Could not open data file" has been reported on Novell Netware clients. File access failed on data files that do not contain spectra. The frequency of the problem can be drastically reduced by installing a patch for Novell Netware 4.1. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Graphics (Overlaid/Fullscale) does not correctly display curves
Problem:
|
Set Graphics Options to: Overlaid/Fullscale and specify a sub-range on the x-axis. Overlay two signals. The resulting graphics does not display a normalized plot of the two curves within the specified x-range. In fact, the display shows the two curve segments in un-normalized (not fullscale) mode. The y-axis does not display the "Norm." label. Note: This problem becomes evident when there is a significant offset in the baseline of the two signals. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use the new signal alignment tool introduced in A.04.01 to adjust the graphical representation of the signals. |
Fix Information:
|
No fix planned. |
Keyword: DATA ANALYSIS
One-line Description:
Chromatogram integrates after a change in the Signal Options
Problem:
|
When loading a chromatogram, the "Load Signal" dialog allows the user to prevent the chromatogram to be integrated after loading. This is useful when dealing with long chromatograms with a large number of peaks. However, when modifying a setting in the signal options (e.g. switching from Separated display mode to Overlaid), the chromatogram is integrated even if retention time annotations are disabled. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: DATA ANALYSIS
One-line Description:
Shoulder Peak Name annotations are missing in the chromatogram
Problem:
|
ESTD report shows a positive identified compound, but the chromatogram does not contain the name for this peak. Other peaks are OK. By changing some integration parameters, to more accurately identify the peak, it is labeled with the name. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: DATA ANALYSIS
One-line Description:
No column is installed: for the selectivity still some values are given
Problem:
|
Performance report prints a value for selectivity even though no column information was entered. |
Problem Cause:
|
When no column is installed actually no k' and no selectivity can be calculated. However the ratio of two consecutive peak retention times is calculated in this case and printed in the selectivity column of the report. This means in other words that instaed of having calculated (Tn+1 - T0)/(Tn - T0) which is the selectivity, you will get the Tn+1/Tn which is just the ratio of the retention times. |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Pick Mode does not work in fullscale
Problem:
|
The so-called "pick-mode" (trace mode) of the mouse cursor in the graphics window is not available in fullscale mode (see graphics options). |
Problem Cause:
|
n/a |
Temporary Solution:
|
Set graphics options to "All the same scale". Position the cursor on the curve that you want to inspect. Click the right hand mouse button and observe the mouse cursor change to a black arrow pointing downwards. The cursor is now locked onto the signal curve. Another right mouse click toggles back to normal mouse mode. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Error message misleading when typing error in "Cust Data Analysis Macro"
Problem:
|
The wrong, or at least misleading, error message is given when there is a typing mistake in the command line of the "Customized Data Analysis Macro" when the method is run. The error message 'In macro DoCustomDA at line 540 in file C:\HPCHEM\CORE\SIGNAL.MCX error 40996 occurred. Syntax error in CMD/FCT Evaluate' is misleading. The actual error is the syntax on the 'Customized Data Analysis macro' line. Error message should state that error is syntax error in command entered in the 'Customized Data Analysis Macro' field. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Integ Events for removed signal are printed/cannot be removed
Problem:
|
The ChemStation integrators allow discrete integration events tables per signal. The method shows generic (i.e. valid for signals w/o a signal specific table) and signal specific events tables. In some cases the following scenario has been observed: A print-out of the integration events may show events tables for signals that have already been deactivated for acquisition, but the integration events editor does not allow deletion of an "obsolete" events table. a) create method with 2 signals activated for acquisition b) create signal specific integration event tables c) save method d) disable one of the signals for acquisition e) the "obsolete" signal's event's table is no longer accessible in the edit events dialog, but the settings are still printed by 'print method'. |
Problem Cause:
|
n/a |
Temporary Solution:
|
To get access to the "obsolete" signal specific events table: a) delete the obsolete events table BEFORE disabling the signal in the instrument screen b) load a data file that contains the corresponding signal channel |
Fix Information:
|
Problem only occurs with the standard integrator - see work-around described above. Problem has been fixed in enhanced integrator. No further fix planned. This issue is resolved with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - html help, reworked help items - and more... in this context these issues are resolved. |
Keyword: DATA ANALYSIS
One-line Description:
Use ranges dont work if data file has large numbers and Y range is small
Problem:
|
n/a |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Data Analysis does not remember the last screen settings.
Problem:
|
When using signal options, full or automatic scale in Data Analysis, if you zoom in a chromatogram and you leave the screen (change integration, plotting in cs report) the system doesn't remember the Data Analysis steps when you return. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use the Use ranges setting from the Signal Options dialog in the Graphics menu to always see the same zoom. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
GPF in HPDOP_00.DLL.
Problem:
|
n/a |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Data files are missing in the batch register file *.b
Problem:
|
In rare cases data files are missing in the batch review .b file. It was observed only in conjunction with the following settings: - "Acqusition Only" in the method runtime checklist and - "Acquistion Only" in the sequence paramter dialog box. It is also observed if during data acquisition the data analyses view was openend in the online session. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Reprocess the sequence to include all runs if files were missing. Choose "According to Runtime Checklist" in the sequence parameter dialog box in the future to prevent missing files. |
Fix Information:
|
No fix planned. |
Keyword: DATA ANALYSIS
One-line Description:
Output of batch report in XLS format not possible from graphical user interface
Problem:
|
Batch review does not generate Excel files using the GUI buttons. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use Output batch review from the batch menu to generate the output according to the settings in the report options for batch review. The tool buttons only generate a report on screen or a report on the printer. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Save Window: "This file already exists" when saving multiple files
Problem:
|
When utilizing the Data Analysis/View/Window Functions/Save Window, after saving an initial window into a data file, loading another data file and saving it results in the data file name not being updated from the 1st to the 2nd data file. Example: 1st data file: 001-0101.d Window Save File: 001-0101.d\chromreg.win 2nd data file: 002-0202.d Window Save File: 001-0101.d\chromreg.win <------- If defaulted, the user is presented with "This file already exists" warning. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: DATA ANALYSIS
One-line Description:
Data Analysis online interacts with same data analysis manual mode.
Problem:
|
Running a method or sequence that includes Data Analysis processing in the same instance of the HP ChemStation that one is using for interactive Data Analysis leads to problems. When the method or sequence completes acquisition and starts Data Analysis, it will use some of the same resources (such as the chromatographic register and window) that are used during interactive Data Analysis. There is no problem if the method or sequence is performing acquistion only. The problem occurs if the method or sequence does Data Analysis. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use the offline instance of the HP ChemStation for interactive Data Analysis. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Data analysis does not always display ALL of the calibrated peak names.
Problem:
|
When in data analysis with multiple signals, and all signals have multiple calibrated peaks, and all of the chromatograms are shown in the data analysis screen, and peak naming is turned on, some of the peak names may not be displayed. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Upgrade a method to new spectra options not possible
Problem:
|
The first time the spectra options are opened in a method one has to decide for the new options or the old options. It is not possible to go to the new spectra / purity options later on. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Type SPC_ResetDefaults on the command line of the ChemStation. This will restore the method to the initial settings of the Spectra options. The next time Spectra or Purity options are selected the ChemStation will prompt you again for upgrading to the new Spectra / Purity options. ATTENTION: You will loose all settings for Spectra and Purity options you already made, as this command will reset all default values. |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - tutorial removed and replaced by "Getting Started Manual" -Co execution UV vis ChemStation and HPLC systems is not supported. - and more in this context these issues are fixed. |
Keyword: DATA ANALYSIS
One-line Description:
Incorrect method reported in batch report
Problem:
|
When a method is loaded during batch review, the batch review report does not display the new method information, especially the method name is the name of the method initially loaded. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Do not load a method during batch review, always select the method when loading the batch. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Perform manual calculations for all quantitative report
Problem:
|
Calculating quantitative results or calibration tables using Excel or other means gives different results than the ChemStation report indicates. |
Problem Cause:
|
n/a |
Temporary Solution:
|
You need to use the raw data used for calculations and not the displayed rounded values to avoid accumulation of rounding errors. Usually these values can be obtained from the registers using the UCL macro tools (contribution 11). |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Signal Options Dialog ignores invalid range parameters
Problem:
|
The range input fields in the Signal Options dialog box accept illegal entries. The input is ignored when loading and displaying the file. No error message is generated when the inputs are made. #, $, %, and alpha characters can be entered in the range fields. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Modifications in Specify Report zoom out the chromatogram
Problem:
|
When 'Specify Report' settings are modified, the chromatogram in the graphics window is redrawn. A zoomed-in chromatogram is then displayed fully zoomed out. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: DATA ANALYSIS
One-line Description:
Changing window width influences displayed peak height
Problem:
|
In some cases, when displaying very sharp "needle" shaped peaks, the following effect may occur: The height of CE peaks in the electropherogram may appear to change when adjusting the size of the graphics window. |
Problem Cause:
|
This is a "cosmetic" artifact. The ChemStation graphics library uses an algorithm that speeds up the drawing of a curve by building it up of line segments (instead of drawing every individual data point). With very sharp peaks, the algorithm produces approximations of lesser quality. |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: DATA ANALYSIS
One-line Description:
AIA Import: Report to .TXT or .CSV file fails
Problem:
|
Printing an imported AIA file to file (print destination: file) does not work. |
Problem Cause:
|
n/a |
Temporary Solution:
|
As a workaround, set the following variables: DADATApath$="c:\hpchem\1\aia\" DADATAfile$="reports" and make sure the corresponding directories exist. Alternatively, use the interactive file export functions available in A.04.01. |
Fix Information:
|
No fix planned. |
Keyword: DATA ANALYSIS
One-line Description:
Unable to select data files: "No datafile selected"
Problem:
|
Error message "no datafiles selected" in the load signal dialog box; When trying to reload the method at this point, another error message occurs: "fatal error, check system resources". The errors occur after manually integrating numerous data files in an offline session of the HP 3DCE ChemStation. The only remedy is to close and restart the ChemStation and Windows. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The problem has been reported on A.04.01 and A.04.02, but not on A.05.01. This problem only affects the loading of a data file. Data acquisition will continue to operate normally. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Cannot enter more than one ISTD amount in the sequence table.
Problem:
|
It is impossible to enter in the sequence table more than one ISTD amount. The system can work with multiple ISTD's, but the user can put only one into the sequence table. It is not obvious which ISTD peak will use the new ISTD amount, and what will happen to the other ISTD peak(s). |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
In data analysis task list, the tutorial tasks are truncated.
Problem:
|
When in Data Analysis view, the names of the tutorial tasks in the tasks list are truncated. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: DATA ANALYSIS
One-line Description:
The calibration table is somehow linked to the toolbars.
Problem:
|
With the calibration table displayed, and you remove the top and status toolbars, OR you redisplay the toolbars, the system will act as if the OK button on the calibration table was selected. You might view a message similar to "Delete lines with amount of zero", and should not. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: DATA ANALYSIS
One-line Description:
Library search finds match factor of 1000 for obviously different spec.
Problem:
|
A match factor of 1000 is reported in a libray search for a completly different spectrum. |
Problem Cause:
|
If the library search algorithm has only two points in the spectra to match because the threshold in the search template is to high, a macth factor of 1000 will be reported. |
Temporary Solution:
|
Set the threshold seting in the search template to a value that allow more points to be taken into account. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Injection time in File->Load Signal->FileInf differs from printed report
Problem:
|
The Injection time in File->Load Signal->FileInf can differ from the printed report, if the data was acquired on a system were tz was set to a value different from 0, or the report was printed on a system were tz does not equal 0. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Set the variable tz to the correct value on your system for your location in the autoexec.bat. Syntax: SET tz=XXX[difference to GMT]. [Difference to GMT] can be a positive or negative integer, denoting the time difference in hours to GMT on your location. XXX is a three letter string used for your time zone, e.g. GST for German standard time, or PST for pacific standard time. If no tz is set on your system, tz=PST-8 is the default value. |
Fix Information:
|
No fix planned |
Keyword: DATA ANALYSIS
One-line Description:
Response ranges do not work if scale is set to "Each in Full Scale".
Problem:
|
In Data Analysis/Graphics/Signal Options, response ranges do not work if scale is set to 'Each in full Scale'. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
The peak sum table appies to all signals by design.
Problem:
|
Only one peak sum table exists for all of the signals. It is not possible to enter a different peak sum range for each signal. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Statistical moment 0 does not equal peak area
Problem:
|
The peak area and the statistical moment zero may vary up to 1.5% though they should be the same. |
Problem Cause:
|
This is caused by the fact that the algorithm that calculates the statistical moment zero uses a different approach than the integration algorithm. As described in the understanding your ChemStation manual, the rectangular area slices are created by multipling the data point with the time to the next point. This creates an aera slice smaller than the peak on the upslope and an are slice larger than the peak on the downslope. The integration algorithm used to calculate the peak area partly corrects for this. |
Temporary Solution:
|
The correct figure for the peak area is the number reported for the peak area. This number is used for all further calculations. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Excel charting capabilities is limited to 10 compounds per method.
Problem:
|
Excel charting capabilities is limited to 10 compounds per method. Using more than 10 compounds per method will result in multiple instances of Excel that remain loaded which cause vitual memory problems. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Limit 10 compounds per method when using Excel Charting. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
ERr. Proc. Run: specified register is already locked during batchreview
Problem:
|
In certain cases the error message ERROR Processing Run: specified register is already locked does appear when loading a batch for batch review. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Click OK and ignor the error message. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Batch review does not display correct calibration level for samples
Problem:
|
When loading a batch from a sequence with calibration samples from different levels, the calibration levels for the samples are displayed incorrectly in the batch table. |
Problem Cause:
|
n/a |
Temporary Solution:
|
This does not affect the re-calibration. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Annotation might be hidden for overlaid spectra
Problem:
|
When annotating a window containing overlaid spectra it can happen that the annotations are not visible. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Select the spectrum with the lowest maximum absorbance first and overlay the others. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Uncalibrated peaks at same RT in 2 diff signals ignores the smaller peak
Problem:
|
If an uncalibrated peak in signal A has approcimatley the same retention time as an uncalibrated peak in signal B, only the higher of the unclaibrated peaks will be reported. |
Problem Cause:
|
In LC chromatography signals typically are not independend from each other, thus the default calibration mode is to regard one peak as the main peak and smaller peaks with the same retention time in other signals as belonging to this component. |
Temporary Solution:
|
When creating the calibration table, select the option calculate signals separatly, to report all peaks individually. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Manual setup of calibration table fails
Problem:
|
When opening the calibration table the error message: CalTabMain: EDTAB 24: Missing ENUMSTRINGS value in row 1 of DDT_CONFIG[3]. Appears and the calibration table stays empty. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Close the ChemStation and delete the files hpchem\1\conf_off.reg and hpchem\1\config.reg for instrument 1. Forinstrument 2 - 3 delete the according files. This will reset the ChemStation to the inital setup. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Peak summing with non-linear calibration curves
Problem:
|
If a reference compound with a non-linear calibration curve is used in peak summing amounts for the peak sums are not calculated properly. |
Problem Cause:
|
Peak summing is done by: 1.) Sum areas of all uncalibrated peaks in the specified time window. 2.) Estimate a response factor for the summed area according to the calibration curve. 3.) Calculate the amount. The order should be: 1.) Estimate a response factor for the area of each uncalibrated peak in the specified time window. 2.) Calculate the amount for each uncalibrated peak. 3.) Sum the amounts. |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
File BATCH.B is not installed on the system for a GC ChemStation
Problem:
|
For a GC ChemStation the demo file batch.b is not installed. This file is used in the tutorial on batch review. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Strange behavior of combo box in "Add Column to Batch Table" dialog
Problem:
|
In the 'Add Column to Batch Table' dialog in 'Options for Batch Review - Report Table' it is not possible to select all columns with the cursor up / cursor down keys. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use the mouse to select the columns you want to include in the batch report. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
peak summing with multiple signals reports incorrect areas
Problem:
|
Results from peak summing calculation are not correct if multiple signals of a data file are loaded in the ChemStation. The results are correct if only one signal is loaded at a time. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
With the updated integrator for B.01.01 the reported issue could not be reproduced. These issue as been reported for a "standard integration method". Issue is resolved with B.01.01. |
Keyword: DATA ANALYSIS
One-line Description:
Main peak is not integrated if "advanced baseline" function is activated
Problem:
|
The usage of the Advanced Baseline (enhanced integrator) in combination with "tangent skim on" and a certain "height reject" can lead to unsuspected integration results (no integration found, also for peaks with a height above the height reject) |
Problem Cause:
|
n/a |
Temporary Solution:
|
You can switch off the "Advanced Baseline". |
Fix Information:
|
The problem will be fixes within ChemStation B01.01 |
Keyword: DATA ANALYSIS
One-line Description:
A.09.01, 'Zoom separate' does not work in Graphics-signal Options.
Problem:
|
The checkbox "Zoom Separately" in the Signal Options dialog does not have any effect. When you zoom one of the signals, all signals will be zoomed in the same way. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
This defect will be fixed with Rev. B.01.03. |
Keyword: DATA ANALYSIS
One-line Description:
Application error, stack overflow
Problem:
|
Running Batch reprocess in Chemstation systems while perfoming copy/cut/paste actions in Microsoft Office applications, the Chemsation might run into an application error: stack overflow. The Chemstation will close down after pressing OK for the error message and needs to be restarted. The problem is related to the Clipboard functionality. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The problem is caused by the clipboard handling between Office and Chemstation. Office Applications will fill up ChemStation clipboards while copy/paste in the Office application. Agilent improved the clipboard handling, so that the system will run batch reprocess during a normal copying rate in Excel. Huge Data amounts: During reprocessing a batch in Chemstation, do not copy/paste huge data amounts in Office Applications. |
Fix Information:
|
with A.10.01 ChemStation the stability of co-executing copy/paste functions is significantly improved. |
Keyword: DATA ANALYSIS
One-line Description:
Cannot resize chromatogram after you have resized it to a little box
Problem:
|
In LC/MSD Data Analysis, in spectral task mode, if you load a MSD signal, you will have a chromatogram displayed in the upper have of the data analysis. If you then put your cursor on the lower right corner of the chromatogram window, and click and drag the window to the upper left, you will have a small box in the upper left corner. At that point you cannot resize the window back to its original diminesion. You put the cursor on the little box and try to click and drag it out, it does not expand. The only solution is to shut down chemstation and delete config.reg and restart chemstation. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Chemstation Data Analysis Overlay function shows limited signals per window
Problem:
|
With ChemStation system A.09.01 or higher follwing issue has been reported during printing multiple overlayed signals: E.g. six signal overlay will be printed out in 2 different chromatograms when you request a Print Report. The first 4 signals print on the first page, and the second 2 print on a separate chromatogram on the second page. |
Problem Cause:
|
n/a |
Temporary Solution:
|
This issue has been seen sporadicly and depends on the used printer driver. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Problem with signal overlay information in A.10.01.
Problem:
|
For ChemStation Rev. A.10.x following issue as been reported for graphical information. Using the overlay function for datafiles within the Data Analysis- Integration task section, the datafile information in the lower left corner are displayed when a signal channel is selected. Using this option the file information box will be updated with the correct information except the file name, which will refer to the first loaded datafile of the overlaid set. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The correct file name is displayed in the header of the loaded chromatogram. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
Only 35 levels can be recalibrated
Problem:
|
There is a maximum number of recalibration levels within the ChemStation. The max. levels for recalibration are 35, the recalibration will stop after level 35 . |
Problem Cause:
|
n/a |
Temporary Solution:
|
In case that more than 35 calibration levels are needed, the following levels needs to be manually recalibrated. |
Fix Information:
|
n/a |
Keyword: DATA ANALYSIS
One-line Description:
extended performance Weight % ISTD% gives wrong units.
Problem:
|
There is a problem with the reported unit on the Extended Performance report style using the ESTD% or ISTD%. If you print the report the calculated numerical values are correct, but it displays the unit that has been specified in the calibration settings in the field amount units. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
This defect is fixed in ChemStation Rev. B.01.03. However, a left-over defect is still present that is described as #351 in SSB for ChemStation B.xx.xx. |
Keyword: DATA ANALYSIS
One-line Description:
Adding Data Analysis to OQFLUSH.M Runtime Checklist Produces Error -3.42 x10E38
Problem:
|
Following issue has been reported printing the verification test results from an OQPV, the following error appears in the verification logbook following the execution of the OQFLUSH.M Method.: In Command TabVal in macro BatchAddNewRun at line 337 in file C:\HPCHEM\CORE\BATCH.MCX Error 17923 occurred: Parameter 3: A value is outside the legal range. This error was also documented in PVCS entries 2527 and 2419, which refers to a missing entry for Data Analysis in the Runtime Checklist of a method. When attempting to reprocess the OQPV data to eliminate the error by adding 'Data Analysis' to the Runtime Checklist of OQFLUSH.M and reprocessing the OQPV data offline, an error occurs (-3.4 x10E38) and the reprocess can't be completed. This occurred in both A.10.01 and A.10.02 software. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
This issue is fixed in B.01.01. |
Keyword: DOCUMENTATION
One-line Description:
importing pascal libraries did not work
Problem:
|
Errata in the Installation Manual, p/n G2170-90001 and G2170-90002: When converting a Pascal Library to the Windows format, an intermediate PLF file is used. This .PLF file must be converted to ASCII using the Pascal FILER which requires the extension .ASC. Convert the .ASC file using HPCOPY or the LIF Utilities to DOS format. Rename the resulting DOS file to .PLF before importing the library into the ChemStation. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: DOCUMENTATION
One-line Description:
Difference in peak start/end for different shoulder modes
Problem:
|
The two shoulders modes, tangent skim and dropline, will result in different peak start/end times being reported by the integrator. Dropline shoulders should be specified when dealing with peaks that separated well enough so that splitting the peak makes sense. Tangent skimmed shoulders should be used for real shoulders in which case the start and end times are the optimal tangent points found on the shoulder. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: DOCUMENTATION
One-line Description:
Precision of calculation in the ChemStation, differences to Excel calc.
Problem:
|
Manually recalculated results such as calibration curves, standard deviations, correlation coefficients, %RSD, the number of theoretical plates etc., for example by using Excel or a pocket calculator, differ from the the values reported by the ChemStation. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The result mismatch between the ChemStation and manual calculation procedures can be explained by rounding errors. For all numbers in the calibration calculations the C data type DOUBLE is used. This data type allows 14 significant digits to be stored and used in calculations. The implementation adheres to the Microsoft implementation of the IEEE standard for the C data type double and the associated rounding rules (see Microsoft documents Q42980, Q145889 and Q125056). The calibration table displays a maximum of 10 significant digits for all values. If an external calculation for validation is required, we advise to use the TabVal command (see Appendix), to access all digits used for the internal calculations of the displayed results. Using the displayed and rounded data for external recalculation of a result may cause different results due to rounding errors. Appendix: To display for example the area of the first peak of the calibration table with the full precision, type the following two commands on the command line: Print using "#.##############", TabVal (_damethod, calpoint,1,Area) Print Refer to the Macro Programming Guide or the appropriate help file for more information about the TabVal command. |
Fix Information:
|
n/a |
Keyword: DOCUMENTATION
One-line Description:
7673 Vs 7683 Autosampler information in method printout
Problem:
|
The 7683 ALS is reported as 7673 when you printout a method. Customer requested it to be properly identified due to GLP |
Problem Cause:
|
n/a |
Temporary Solution:
|
The 7673 is the old family name and covers all of the Autosampler components including the various controllers, multiple different injector modules, and the tray(s). |
Fix Information:
|
n/a |
Keyword: DOCUMENTATION
One-line Description:
different description G1362A in ChemStation and Reference manual
Problem:
|
The description related to G1362A is different between ChemStation and Reference Manual in the following: ChemStation(A.10.01) ================= Help -> Help Topics -> Instrument Reference -> Error Messages -> Agilent 1100 ... -> Detectors -> RID -> "Reference Valve" Fuse Blown Reference Manual (G1362-90001, page 66) ================================ "Purge Valve" Fuse Blown |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
The help text is correct for B.01.01 |
Keyword: GC ACQ
One-line Description:
Print Method: 'Det.A-Comp1' truncated in report
Problem:
|
Printing a method with signal "det - compensation" gives the error message: Data 'Det.A-Comp1'truncated in report. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: GC ACQ
One-line Description:
Possible to damage column in dual column operation.
Problem:
|
In a GC with two quite different columns with different maximum temperatures, as methods are loaded, either single or dual column operation, the column max is not linked to the lowest temperature column and should be to protect the column. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: GC ACQ
One-line Description:
The date format for a 6890 and 5890 in a report are different.
Problem:
|
If the same computer is used to control the 5890 and the 6890 The following command gives 2 different date formats. OBJHDRTEXT$(CHROMRES[1],"INJDATETIME") Ex: 17 Mar 95 02:08 PM for a 5890A 3/17/95 2:08:31 PM for a 6890A |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: GC ACQ
One-line Description:
Parameters not listed correctly for Aux channel in method print
Problem:
|
When a method is printed, it may show some information incorrectly: 1. If an aux channel is used for makeup gas compensation, it is listed correctly under the auxiliary channel however, values are also filled into the calibration parameters, split flow plumbing environment and equation sections of the auxiliary channel split flow settings. 2. Conversely, if an aux channel is used for split flow control, values are also filled into the pressure program, calibration parameters and makeup gas compensation sections of the auxiliary channel makeup gas settings. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: GC ACQ
One-line Description:
It is possible to set the flows to zero and damage a NP bead.
Problem:
|
It is not possible to turn a NP bead ON if the flow is zero to protect the bead. However, it is possible to have the bead turned on and then turn the flows to zero (zero is a setpoint) and damage the bead. The software should not let you do this. Note. The software works the same as the GC. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Turn the NP bead OFF before setting the flow to zero. |
Fix Information:
|
No fix planned |
Keyword: GC ACQ
One-line Description:
6890 GC:- Error #98: Could not Login on network
Problem:
|
During startup of the 6890 GC, there is an error message as follows "ERROR #98: Could not login on network." If you OK, there is another, OK again, and the instrument session stars up correctly. If you then try and enter a column, you get the same error message. The problem is caused by the PARADOX ENGINE used by the columns database. The database is invisible to the user. There is no entry in the WIN.INI file. When the user loads ANOTHER program that uses the paradox engine, it may put an entry in the WIN.INI file. LATER, on startup of the 6890 GC, the paradox engine is called, it checks the WIN.INI first, and the error messages occur because the columns files cannot be found. |
Problem Cause:
|
n/a |
Temporary Solution:
|
There is NO WORKAROUND at the moment to make this work with the conflicting program, whatever it may be. Only way to make the ChemStation work is to delete the entry in the WIN.INI file. This of course kills the other program that requires the entry. Entry in the WIN.INI file looks like . . . . . [Paradox Engine] NetNamepath = C:\ etc, etc, This must be removed to make the ChemStation operational. |
Fix Information:
|
n/a |
Keyword: GC ACQ
One-line Description:
6890 ONLY: With manual FID, the ChemStation does not turn on the air.
Problem:
|
On a 6890 GC with both Manual and EPC pneumatics installed, the manual FID detector air cannot be turned on by the ChemStation. All of the other gases are turned on correctly. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Turn the air on from the GC front panel. |
Fix Information:
|
No fix planned |
Keyword: GC ACQ
One-line Description:
5890 GC:You can start run (with acquisition on) and no instrument.
Problem:
|
When an online instrument session is started with the GC powered OFF, the user is able to start a data acquisition run. The system will hang and abort will produce a "Stop of the instrument failed" message although the run will stop. It should not be possible to "start" a run when the instrument is off, or, data acquisition should be disabled automatically to allow reprocessing only. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: GC ACQ
One-line Description:
6890: In the Edit Column ID table, there are no cut / paste buttons.
Problem:
|
In other ChemStation tables (Injector program, sequence table) there are [Copy] and [Paste] buttons for editing. There are no buttone in the Edit Column ID table and should be for consistency and usability. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use Ctrl C (copy) and Ctrl V (Paste). |
Fix Information:
|
n/a |
Keyword: GC ACQ
One-line Description:
HP 6890: Firmware revision A.03.05 is needed for LAN control.
Problem:
|
n/a |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: GC ACQ
One-line Description:
5890: Change column diameter is not saved with method.
Problem:
|
In the 5890 Inlet Pressure screen, if you change the column diameter, the change is not saved when the method is saved. The default (530) is saved instead. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Workaround is to change another value as well, length for example, then save the method. If all of the other setpoints are to remain the same, except the diameter, make the changes twice, the second time setting the first time changes back. |
Fix Information:
|
n/a |
Keyword: GC ACQ
One-line Description:
Time stamp errors in LC Chemstation & Chemstore, Win 2000 time format ignored.
Problem:
|
LC ChemStation A0903 ignore the Win 2000 time format HH:mm:ss and will put always a PM stamp on the injection time for injections done in the morning onto the report. The rawdata information will show the correct injection time. LC Data spooled to Chemstore will use the right time stamp and will give the correct injection, processing & transfer times. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Remove the PM symbol in Start>Settings>Control panel> Regional Options, Time Tab. All injections times for LC runs are correctly shown now without the PM stamp. |
Fix Information:
|
n/a |
Keyword: GC ACQ
One-line Description:
Error 17923 - Parameter 3: A value is outside the legal range
Problem:
|
For GC ChemStation systems using the back tower and back seqeunce, following issue as been reported in the instrument logbook: CP Macro Error in Hook PostRun : BatchPostDA CP Macro ======================================== CP Macro In Command TabText$ in macro BatchAddNewRun CP Macro at line 284 in file C:\HPCHEM\CORE\BATCH.MCX CP Macro Error 17923 occurred: CP Macro Parameter 3: A value is outside the legal ran CP Macro ======================================== |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
The issue is fixed with B.01.01 ChemStation. |
Keyword: GC ACQ
One-line Description:
Displaying method in control module prevents other meth download during seq
Problem:
|
The handheld control module was used to view and display Method B parameters while running a sequence. The handheld control module was left connected to the 6850 and was displaying the Method B parameters. Leaving the control module displaying the parameters of Method B will cause the sequence to use Method B parameters such as runtime for each line in the sequence. Other methods were not downloaded. The reports however, will have the correct method that was supposed to be used printed on them but the ChemStation used Method B parameters. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: GC ANALYSIS
One-line Description:
Second Signal Handling in the Run Time Checklist
Problem:
|
In the RunTime Checklist of the GC ChemStation an Analysis Method for the Second Signal can be defined. This is misleading and confusing. It will only be used if there is a SECOND DATAFILE. Help needs to be expanded to explain how this works. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: GC ANALYSIS
One-line Description:
Method Printout: Signal Descriptions are confusing (mixed up?).
Problem:
|
The descriptors "Signal 1" and "Signal 2" are confusing when applied to the GC, the plot monitors on the screen and in data analysis. Also in the descriptors and reports they are occasionally mixed up. This is especially confusing when the real time plot monitors can be selected in the order 2, then 1. This results in the title bar being "Signal 1:GC signal2" and "Signal 2:GC Signal 1". |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned |
Keyword: HELP
One-line Description:
In the RID control dialog box there is no help available
Problem:
|
When selecting help in the RID control dialog box an error message is displayed. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Open the ChemStation help from the main help menu, got index and type Control (HP 1100 RID) Select Display to display help on the HP1100 RID control dialog box |
Fix Information:
|
This will be fixed in the HP1100 RID firmware, rev > 3.80 |
Keyword: HELP
One-line Description:
Wrong online help text on retention time limits (calibration table)
Problem:
|
Unlike the description in the online help retention time limits are always adjusted when doing a recalibration even when they are not set to default. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
Fixed in A.10.01 |
Keyword: HELP
One-line Description:
Exportspectrum cmd can not export to JCAMP-DX format in LC ChemStation
Problem:
|
Exportspectrum can not export a spectrum to JCAMP-DX format as specified in the commands help. |
Problem Cause:
|
This function is only available in the UV-Vis ChemStation. |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: HELP
One-line Description:
Syntax of "ExportSpectrum" command in Help Text wrong
Problem:
|
The two parameters "ToFile" and "FileTypes" are reversed with "ExportSpectrum" command in the Commands help. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The correct syntax of the "ExportSpectrum" command is: ExportSpectrum FromRegObj, FileType, ToFile |
Fix Information:
|
fixed in A.10.01 |
Keyword: HELP
One-line Description:
HELP/COMMANDS: Incorrect variable for GENERATE ERROR
Problem:
|
The documentation in the commands online help on 'GENERATE ERROR' is wrong. The system variable when an error is detected is _ERRMSG$ not _ERRORMSG$. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: HELP
One-line Description:
Help system does not function when the system resources are low.
Problem:
|
The help system does not alwaws work correctly, especially when the GUI is turned on, and the system resources are low. Also happens in a multi instrument system. There is often no error message. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Close some other programs. Update to Windows 95 which has much better resource management. |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - tutorial removed and replaced by "Getting Started Manual" -Co execution UV vis ChemStation and HPLC systems is not supported. - and more in this context these issues are fixed. |
Keyword: HELP
One-line Description:
f1, HELP, does not always display the associated HELP topic.
Problem:
|
f1, HELP, does not always display the associated HELP topic. |
Problem Cause:
|
n/a |
Temporary Solution:
|
When F1 help does not display the help topic, the help system displays one of the following - * A list of topics, including the one associated with the selected menu or dialog box. * The top level list of help topics Select the desired help topics dialog box being displayed. |
Fix Information:
|
No fix planned. |
Keyword: HELP
One-line Description:
The HELP file is difficult to use when looking for command examples.
Problem:
|
When looking up a Command reference such as BeginDialog, an Example button is provided. When using this button, the next screen is "SeeShowDialog Function" with no hyperlink provided to jump to the page. This is cumbersome, the user must then back out two levels, find the ShowDialog function, and then go back down two levels in the help file. This should be much easier to use. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - tutorial removed and replaced by "Getting Started Manual" -Co execution UV vis ChemStation and HPLC systems is not supported. - HTML Help - and more in this context these issues are fixed. |
Keyword: HELP
One-line Description:
Any open HELP window does not close when the ChemStation is closed.
Problem:
|
If Help topics have been opened from the ChemStation, these windows do not close when the ChemStation is shut down and should. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Close the open HELP windows manually. |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - tutorial removed and replaced by "Getting Started Manual" -Co execution UV vis ChemStation and HPLC systems is not supported. - HTML Help - and more in this context these issues are fixed. |
Keyword: HELP
One-line Description:
HELP in the LOGBOOK is inconsistent and sometimes wrong.
Problem:
|
Within the logbook there are the following HELP problems. Double click on 'Analyzing Raw Data' and one gets 'Logbook' Double click on 'Method Completed' and one gets 'Run Method' Double click on 'Saving Sequence' and one gets 'Logbook' Double click on the first line of a 6890 GC session at startup "Welcome to the HP ChemStation" and one gets "How to perform LC tasks" which is obviously wrong. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: HELP
One-line Description:
Items of batch review report items are not all described in help text
Problem:
|
The batch report items *AreaRelErr *AreaAbsErr *Arealim *Amountcal *amountRelErr *AmountAbsErr *AmountLim are not described in the batch review help |
Problem Cause:
|
n/a |
Temporary Solution:
|
The values of the items are RelErr (only calibration samples) Relative error with respect to th expected value AbsErr (only calibration samples) Relative error with respect to th expected value Cal (only calibration samples) Value entered in Calib-table for this value Lim (only control samples) Either "PASSED", if value for is in the expected range or "FAILED |
Fix Information:
|
n/a |
Keyword: HELP
One-line Description:
Installation Verification displays an empty window
Problem:
|
The Installation Verification program displays an empty window when running it from the command line with the example syntax stated in the online help. |
Problem Cause:
|
The utility was run from a path other than |
Temporary Solution:
|
Run the program from the |
Fix Information:
|
No fix planned. |
Keyword: HELP
One-line Description:
GLP data register can be overwritten
Problem:
|
The GLP data register is overwritten in a reprocessing sequence if "Save GLP Data" is checked in the "Run Time Checklist". |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use ChemStore C/S to keep track of all revisions of your data. |
Fix Information:
|
n/a |
Keyword: HELP
One-line Description:
RID Control help file link is missing
Problem:
|
The the link to the help on the RID control dialog box is missing. |
Problem Cause:
|
n/a |
Temporary Solution:
|
As a workaround select 'Help Topics' from the Help menu and choose 'RID Control' from the index. |
Fix Information:
|
fixed with FW Rev, 3.80 |
Keyword: HELP
One-line Description:
Calibration using force through origin described incorrect
Problem:
|
The information in the help "Default calibration curve" exaplains that Tthe regression curve is calculated using the equation without the linear terms. But in addition all calibration points are mirrored at the origin and the mirrored and the original points are used to calculate the calibration curve. Thus the resulting regression curve will go through the origin. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
Fixed in A.10.01 |
Keyword: HELP
One-line Description:
SCHEDULER. Spelling mistakes in the Help file.
Problem:
|
There are four instances in the Help system for the Scheduler in A.08.03 where the word "about" is spelled "aout". |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
This issue is resolved with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - html help, reworked help items - and more... in this context these issues are resolved. |
Keyword: HELP
One-line Description:
Online Help: Sequence Summary Parameters
Problem:
|
In the online help for Sequence Summary Parameters has the following to be corrected-completed: Incorrect: 5. Methods, a printout of all the methods at the time of the analysis Correction: 5. Methods, a printout of all the methods specified in the sequence at the time of the analysis, this does NOT mean that methods which are updated during a sequence are printed in the updated version. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: HELP
One-line Description:
No display of Help topic for Sample Purity Options panel
Problem:
|
When in Methods/Sampler Purity Options panel, if you click the Help button no help topic is displayed. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: INITIALIZATION
One-line Description:
ChemStation invisible or an icon after start
Problem:
|
The ChemStation is invisible or only an icon after startup. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Check the value for WinDim in the PCS section of the win.ini. If the values are out of the maximum screen width or hight. Insert a ; in front of the line containing the windim value. |
Fix Information:
|
No fix planned. |
Keyword: INITIALIZATION
One-line Description:
hpcore caused a gpf in module isoapg.dll at 0003:0561, config. editor
Problem:
|
After installation of the ChemStation software and connecting all instruments, no instruments are found, even if everything is configured correctly. A global protection fault may occure. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Switch off the PC and the analytical instument, check all cable connections. Switch on the PC and the analytical instrument. |
Fix Information:
|
No fix planned |
Keyword: INITIALIZATION
One-line Description:
ChemStation path can not be found after installation
Problem:
|
At startup several error messages like Cannot find HPRTPL00.DLL do appear and the ChemStation does not start. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Make sure the PC was restarted completly. Make sure the PATH is set correctly in the AUTOEXEC.BAT. Windows NT only reads the path and omitts everything else, so only the path statement should be included in the AUTOEXEC.BAT. You can also set the path in NT. Select Start -> Settings -> Control Panel -> System -> Environment and add the path variable to the System Variables section, or append the ChemStation path PATH=C:\HPCHEM\SYS;C:\HPCHEM Change the path accordingly if you did not use the default installation path. |
Fix Information:
|
This issue is resolved with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - html help, reworked help items - and more... in this context these issues are resolved. |
Keyword: INITIALIZATION
One-line Description:
Instruments two doesn't start up when the Icon is in "STARTUP GROUP".
Problem:
|
On a multi instrument system, if you copy or drag and drop the inst icons into the "STARTUP" group box, instrument one always start. Inst two never starts, and instrument three and four also start up. Seems to be a problem with the timing. The server is too busy starting instrument one to start inst two but is finished in time to start instruments three and four. There are no error messages. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Instrument two can be started in the normal way by double clicking on the Icon later. |
Fix Information:
|
No fix planned. |
Keyword: INITIALIZATION
One-line Description:
Hangup during initialization of multiple instances
Problem:
|
The initialization of a new HP 1100 instance may fail if multiple sessions (online and/or reprocessing copies) are already running. The restricting factor is the number of HP 1100 modules that are being controlled by the same computer. |
Problem Cause:
|
The HP ChemStation can control a maximum of 4 ChemStation instruments. The maximum number of HP 1100 modules that can be controlled from one HP ChemStation is... 12 individual modules (no DADs!) 8 individual modules if configuration includes a maximum of 2 DADs |
Temporary Solution:
|
HP 1100 Instrument configurations --------------------------------- HP 1100 chromatography instrument configurations, without diode array detectors (DADs), are limited to a total of 12 individual modules configured as up to 4 instruments with a limit of 4 detectors. If DADs are included in the configuration there is a limit of 2 DADs and 8 modules that may be configured as two seperate instruments. For example : You can run two HP 1100 DAD (G1315A) based instruments on one PC each with a pump (G1310A or G1311A or G1312A), an autosampler (G1313A) and a thermostatic column compartment (G1316A). A 4 instrument configuration based on the HP 1100 Series modules can comprise 12 modules out of autosamplers (G1313A), VWD (G1314A), pumps (G1310A or G1311A or G1312A) or thermostatic column compartment (G1316A). Only 4 HP1100 VWDs are allowed per PC. If you wish to use your HP ChemStation interactively while it is acquiring data from instrumentation we do not recommend three and four instrument confiruarations. HP 1100 modules may be used in mixed configurations with HP 1050 or HP 1090 liquid chromatographs, HP 5890 and 6890 gas chromatographs and capillary electrophoresis instruments. The configuration limits for these instrument combinations are : HP 1100 and Capillary Electrophoresis combinations: One CE instrument and 1 HP 1100 system with a DAD Two HP 1100 chromatography systems with one CE instrument HP 1100 and 8453 UV-VIS combinations: One UV-VIS instrument and 1 HP 1100 system with a DAD Two HP 1100 chromatography systems with one UV-VIS instrument HP 1100 and HP 1050 or HP 1090 LC mixed module combinations : Any of the HP 1050 modules, the 35900 Dual Channel Interfaces, the HP 1090 LC, the HP 1046 FLD or the HP 1049 ECD counts as the equivalent of one HP 1100 module. HP 1100 and HP 1050 or HP 1090 LC mixed instrument combinations : One HP 1100 instrument with a DAD with one HP 1090 or 1050 LC also with a DAD One HP 1100 instrument, without a DAD, with up to three HP 1090 or HP 1050 LCs Two HP 1100 instruments, without a DAD, with up to two HP 1090 or HP 1050 LCs HP 1100 and HP 5890 and HP 6890 combinations : One HP 1100 instrument (NO DAD) with up to three HP 5890/HP 6890 GCs One HP 1100 instrument (DAD) with up to two HP 5890/6890 GCs Two HP 1100 instruments (NO DAD) with up to two HP 5890/6890 GCs |
Fix Information:
|
No fix planned |
Keyword: INITIALIZATION
One-line Description:
82341C: Windows Fatal Exception 0D when the HP-IB board is accesses.
Problem:
|
Windows Fatal Exception 0D when the HP-IB board is accesses. This is normally during start up of the first instrument session. |
Problem Cause:
|
This is caused due to memory conflicts with the 82341C HPIB card and MS Windows, either Widows NT or Windows 95. |
Temporary Solution:
|
Memory conflicts may avoided by selecting areas of memory that are not used by other devices on the PC. |
Fix Information:
|
This issue is resolved with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - html help, reworked help items - and more... in this context these issues are resolved. |
Keyword: INITIALIZATION
One-line Description:
Problems with leading zero in IP address when configuring instr. on LAN.
Problem:
|
n/a |
Problem Cause:
|
n/a |
Temporary Solution:
|
Workaround: When configuring instruments on the LAN, do not add leading zero to the IP address. |
Fix Information:
|
fixed with B.01.01 |
Keyword: INITIALIZATION
One-line Description:
GPF in PLICOP.DLL during simultaneous startup of 2 online ChemStations
Problem:
|
When simultaneously starting two online ChemStations with at least one being a LAN-controlled instrument a General Protection Fault occurs in PLICOP.DLL. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Don't start two online ChemStation sessions simultaneously. |
Fix Information:
|
n/a |
Keyword: INITIALIZATION
One-line Description:
LAN communication: General Protection Fault in PLICOP.DLL at 2:512a
Problem:
|
Only when running a LAN-controlled instrument (HP 1100): In very few cases the ChemStation crashes with a General Protection in PLICOP.DLL at 2:512a during startup. |
Problem Cause:
|
This is due to a major change in the firmware of the HP 1100 modules and occurs with firmware rev. A.02.32 or below. |
Temporary Solution:
|
Perform a firmware upgrade of all HP 1100 modules to the latest revision (A.03.3x or higher). Use the firmware upgrade utility supplied with your A.06.0x CD-ROM in the support\firmware\ subdirectory. |
Fix Information:
|
The problem is fixed by a firmware upgrade. |
Keyword: INITIALIZATION
One-line Description:
Opening Reprocessing copy opens also C:\WINNT\System32\CMD.exe
Problem:
|
When opening a reprocessing copy of Chemstation A.09.03 (View - Reprocessing copy) it opens also C:\WINNT\System32\CMD.exe. It appears in the toolbar and when opening it, an empty black window appears and cannot be edited. Chemstation sessions are not effected, the cmd.exe window can be closed. When closing the reprosessing session, also the cmd.exe window dissappears. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Either open the Offline Version of the ChemStation via Start>Programs>ChemStation>offline version or close the cmd.exe window. For revision B.01.01 the cmd window needs to be closed manually. Regarding CFR 21 part 11security: The CMD window will be only displayed. The user (even adminsitrator) cannot type or execute commands in the window. So there is no violation of CFR 21 part 11 securtiy. |
Fix Information:
|
n/a |
Keyword: INITIALIZATION
One-line Description:
Autostart macro failed, error 41297 occured
Problem:
|
If you start the ChemStation in the Data Analysis View as an Operator you get the following error message: Autostart Macro Failed, error 41297. On the command line you get the message: Undefined scalar (or scalar function):GetCalWinNum After pressing OK you shall see that the Calibration - Signal and Spectral Task Icons or not greyed out but there functionality is disabled as it has to be. |
Problem Cause:
|
n/a |
Temporary Solution:
|
-to prevent the error, avoid to close the ChemStation while the calibration is open In case the error occurred: - Close ChemStation and rename the configuration register <\\hpchem\X\config.reg> (online session) or <\\hpchem\x\conf_off.reg> (offline session) to config.old or conf_off.old respectively. (Where X stands for the instrument's number 1-4). This action could be performed by an operator. |
Fix Information:
|
Will be fixed in Rev. B.01.03 |
Keyword: INSTALLATION
One-line Description:
Install Data Analysis only over G2170AA: PCS section is overwritten
Problem:
|
When installing G2190AA on a system where G2170AA and G2180AA were already installed as instrument 1, the PCS section for this instrument (and any other instrument that is already installed) is overwritten without any warning. As a result, the ChemStation installation may be inconsistent. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Delete the PCS sections from win.ini. Backup your data, methods and sequences and delete the HPCHEM directory tree. Reinstall the appropriate software package (G2170AA and G2180AA or G2190AA if you only need the Data Analysis Only package). |
Fix Information:
|
n/a |
Keyword: INSTALLATION
One-line Description:
Installation fails if network drive is not mapped in Win95
Problem:
|
The HP ChemStation installation may not be performed correctly if the source or target drives are network drives that have not been mapped with a drive letter (this feature is available in Win95 client networking). |
Problem Cause:
|
n/a |
Temporary Solution:
|
When connecting network drives that store or contain ChemStation files, make sure to assign a valid drive designator in Win95. |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - tutorial removed and replaced by "Getting Started Manual" -Co execution UV vis ChemStation and HPLC systems is not supported. - and more in this context these issues are fixed. |
Keyword: INSTALLATION
One-line Description:
Data anal.module (G2090AA) can not be upgraded from A.04.01 to A.04.02
Problem:
|
When trying to upgrade a data analysis only module (G2090AA or G2190AA) from revision A.04.01 to A.04.02 the setup program does not allow an upgrade because of a missing license number. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The files necessary for upgrading a data analysis only module are to be found only on Disk4, Disk5 and Disk6. Disk4 contains a setup program. Run the setup program located on the Upgrade CD ROM in the directory Disk4 to install the upgraded macros and core components. |
Fix Information:
|
No fix planned for A.04.01 |
Keyword: INSTALLATION
One-line Description:
Startup: Creation of SysVars for HPPROD00.DLL failed,Error Code=260
Problem:
|
During startup the error message The _Product$ variable is missing from the Instrument PCS Section Creation of SysVars for HPPROD00.DLL failed,Error Code=260 appears and the ChemStation does not start. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The currently logged on user does not have read write access to the WIN.INI file. Ensure that the currently logged on user does have read write permission for this files, as important information will be stored each time the ChemStation is started or closed. |
Fix Information:
|
n/a |
Keyword: INSTALLATION
One-line Description:
G2077AA License Number not valid for installation
Problem:
|
A licence number for product G2077AA may not be recognised by the installation program. This may also happen for any other product. |
Problem Cause:
|
It is possible that one licence number is valid for two products, caused by a basic problem with the algorithm that generates the licence. As a valid licence number is checked against a list of product numbers, the licence number will be assigned to the first valid product, even if it is not the one selected for installing. This will only occure in very rare cases, as these licence numbers do rarely occure and in addition to that the other product must be first in the list of checked products. |
Temporary Solution:
|
Install product G2072AA. If this does not work, try installing every product on the list, until you found the one that fits to the licence number. Do not proceed with the install process, but rather select Delete to delete the product and now install the correct product. |
Fix Information:
|
n/a |
Keyword: INSTALLATION
One-line Description:
Error message Can not open c:\hpchem\core\hpcore.exe, but path is set
Problem:
|
The error message Can not open c:\hpchem\core\hpcore.exe appears when starting the HP ChemStation on a Windows NT system, but the path is correctly set. This was reported on Novell Intra Netware client 4.10a using Novell Application launcher. |
Problem Cause:
|
This is probably caused by a Novell Network installation. The DLL SAMSRV.DLL is replaced by a DLL supplied from Novell. This might be the cause of the problem. |
Temporary Solution:
|
Open Start->Settings->Control Panel->System->Environment Select OK and close the Control panel. This will set the environment variables again correctly and the ChemStation will start as expected. |
Fix Information:
|
n/a |
Keyword: INSTALLATION
One-line Description:
install.log file changed even if update not performed
Problem:
|
The install.log file tracks all changes don during updates and installations. If an update operation is canceled, the install.log files contains the two lines Installing HP ChemStation Update on .... Target directory:... |
Problem Cause:
|
This is normal, as these sections are skipped during the install process they are still "touched", but nothing happens. |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: INSTALLATION
One-line Description:
Time attribute on installed version is different for CD
Problem:
|
The time stamp on different ChemStation installation can be different, even if the same revision is installed. |
Problem Cause:
|
This is caused by the fact that the time stamp is relative to the time zone the stamp was created in. So if the stamp is for example 25.09.97 05:02 in the original time zone (which is GMT) and the tz variable is correctly set for Europe to tz=GST+1 the time stamp will read 25.09.97 06:02 This is because when it was 05:02 in the GMT time zone, it was 06:02 in the local time zone. Usually tz is not set on any systems. Also refer to the Microsoft documentation on time zone settings and usage. |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: INSTALLATION
One-line Description:
After installing a patch on a ChemStation installation, IQ fails
Problem:
|
In some cases Installation qualification fails after updating the ChemStation using a patch floppy. |
Problem Cause:
|
This might be caused by a process locking the access to some files, like a virus scan or a running APG_TOP. |
Temporary Solution:
|
Before installing the patch, restart the PC. If an installation has already failed, delete the ChemStation installation (save the data files) and install again. |
Fix Information:
|
n/a |
Keyword: INSTALLATION
One-line Description:
Update to A.05.04 does not work, stops responing with no error message
Problem:
|
An update using the HP ChemStation from A.05.02 to A.05.04 or A.05.03 using the HP ChemStation revision update floppy disk might hang. The symptom is, that the processing of the patch seems to be stopped, the hard disk is not working. The operating system is fully functional. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Stop the update process, restart the PC, reinstall ChemStation A.05.02 (remove the current version, but make sure to save your data files). |
Fix Information:
|
n/a |
Keyword: INSTALLATION
One-line Description:
Client server installation fails with \\client\core\disk8 not found
Problem:
|
in certain cases it is not possible to installe the ChemStation as client server software. The installation software askes for the location of the disk \\client\core\disk8 |
Problem Cause:
|
n/a |
Temporary Solution:
|
If the first instrument is a G2070AA put as location for disk8: \\G2070\disk8 For other products replace the correct product number. |
Fix Information:
|
This issue is resolved with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - html help - and more... in this context these issues are resolved. |
Keyword: INSTALLATION
One-line Description:
Bootp server does not automatically start
Problem:
|
After installation of the bootp server, the bootp server is supposed to start each time the PC is started. On localised versions of the operating system this might not be the case. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Copy the link to the bootp server from the menu Start->Programs->Startup to the equivalent folder of the localized version. For example: Italian: Esecuzione automatica German: Autostart |
Fix Information:
|
n/a |
Keyword: INSTALLATION
One-line Description:
G209xAA cannot be installed from the A.05.01 CD ROM.
Problem:
|
Verified on CD-ROM Revision A.05.01 dated May 1997 Rev A.05.01 Setup does not include G2092 as an option. Customers with a G2092 Resistration License number cannot update their existing system. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Workaround is to load the software using the service numbers, then enter the customers license numbers to operate. Contact HP for new license numbers. |
Fix Information:
|
n/a |
Keyword: INSTALLATION
One-line Description:
Cannot install 4th instrument if it is a 35900(LC type), GC type works.
Problem:
|
On a multi instrument installation it is not possible to install the fourth instrument if it is a 35900 (LC type). The software does not instal correctly and the instrument Icons are Windows flags instead of the correct instrument Icons. There are no error messages. |
Problem Cause:
|
n/a |
Temporary Solution:
|
There are two workarounds. One. Install the fourth instrument as a 35900 (GC type) which works the same way and installs correctly. Two. Select each of the four instruments one at a time from the "Select Instrument to be installed" screen, and then click on "INSTALL" once after all four are selected. This will install all four in one operation which also works correctly. |
Fix Information:
|
n/a |
Keyword: INSTALLATION
One-line Description:
35900D ROM address space not excluded in system.ini
Problem:
|
The HP ChemStation installation program does not automatically add a line in the [386Enh] section of system.ini that forces Windows to exclude the memory address space allocated for the 35900D card from Windows memory management. Currently, no cases are known where the missing statement for the HP 35900D card as caused problems. The HP 3365 GC ChemStation ships the same configuration (no emmexclude in system.ini). |
Problem Cause:
|
n/a |
Temporary Solution:
|
After installing and configuring an HP 35900D, specify the following line in the [386Enh] section of system.ini: emmexclude=d800-dbff ; matches 35900D select code 6 If you did not configure the HP 35900D at the default select code, consult the product documentation for the corresponding memory address range. The software includes a utility that helps you determine a select code compatible with your system setup. The utility is called cfg35900.exe and is located in the hpchem direct- ory. This program also sets the appropriate exclude statement for the expanded memory manager (if present in your config.sys). |
Fix Information:
|
n/a |
Keyword: INSTALLATION
One-line Description:
No warning given when installing over existing directory.
Problem:
|
No warning is given if you install over an existing directory and it should. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Check the system beforehand to check that the installation will not overwrite a previous "HPCHEM" if it might be required later. |
Fix Information:
|
No fix planned. |
Keyword: INSTALLATION
One-line Description:
Installation of additional GCs creates extra WIN 95 task bar items.
Problem:
|
Windows 95 system, single instrument, Instrument name has been changed. If you add an additional GC(s) to this existing system, the installation will go correctly and create Win 95 task bar menu items for the newly installad instruments. However, the installation will also create two new test bar menu items for the already installed instruments, one on-line and one off-line, and should not. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Delete the additional task bar menu items from Windows. |
Fix Information:
|
No fix planned. |
Keyword: INSTALLATION
One-line Description:
Co-execution with the UV/Vis ChemStation A.02.04
Problem:
|
Co-execution installations of the HP ChemStation for LC, version A.04.01 and the HP ChemStation for UV/Vis version A.02.04 currently requires the following order of installation: 1. Install LC Instrument first (Instrument 1) 2. Install UV/Vis Instrument second (Instrument 2) 3. Install the supplemental drivers disk delivered with the LC ChemStation. Copy the 8453.dll to the C:\HPCHEM\UVEXE directory. Co-execution does not work correctly if UV/Vis is installed first and LC installed last. Several core component libraries are not installed in this combination and none of the two instruments initialize properly. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Note: The problem does not exist with A.02.05 of the HP ChemStation for UV/Vis and A.04.0x of the HP ChemStation for LC. |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - tutorial removed and replaced by "Getting Started Manual" -Co execution UV vis ChemStation and HPLC systems is not supported. - and more in this context these issues are fixed. |
Keyword: INSTALLATION
One-line Description:
Cannot find HPNLS01.DLL
Problem:
|
Starting the application gave an error about HPNLS01.DLL missing. A.04.01 was installed from a CD-ROM. Reinstalling from a set of floppies (after cleaning manually WIN.INI) the software was able to start without errors. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Delete all sections containing PCS in the WIN.INI file and install the softare again. This problem should be solved after rebooting the PC. |
Fix Information:
|
No fix planned. |
Keyword: INSTALLATION
One-line Description:
Intermittent "General Protection Fault in INST20" during installation.
Problem:
|
Occasionally during a ChemStation installation, a Windows message box may indicate a "GPF in INST20". The installation will fail. |
Problem Cause:
|
This failure is an infrequent General Protection Fault occurring in the InstallShield 2.0 program when installing in the Windows 95 or Windows NT operating system environment. |
Temporary Solution:
|
Close all applications and reboot your computer to clear any effects of the GPF. Then install the ChemStation software again. Failure is very intermittent. |
Fix Information:
|
n/a |
Keyword: INSTALLATION
One-line Description:
Installation qualification reports wrong data of ref. files
Problem:
|
An installation qualification on a new installed system reports a wrong date for the reference file. |
Problem Cause:
|
When selecting File -> Save All as and storing the IQ to a different directory than the default one, the reference files can not be found afterwards to obtain the date stamp, as the DOS path is also changed. |
Temporary Solution:
|
If you use File -> Save all as do not select a different directory, or use File -> Print. The date reported will be correct. If the reported time for the refernce file is off by up to 23h, check if a variable tz is set on your system. tz sets your local time zone, so the time reported for the reference file is correct for your time zone. Set tz=0 if you want the original time for the reference file reported. |
Fix Information:
|
In A.05.02 no date gets reported when the reference file can not be accessed. This is only the case when File -> Save All as is used. |
Keyword: INSTALLATION
One-line Description:
Instalation qualification failes with Cooled autosampler and CE instrume
Problem:
|
The installation qualification reports the files \hpchem\ce\systgui.mac \hpchem\ce\language\enuleom.reg as changed in HP ChemStation A.04.03 and A.05.02beta. |
Problem Cause:
|
n/a |
Temporary Solution:
|
This does not affect the integrity of the ChemStation installation. |
Fix Information:
|
n/a |
Keyword: INSTALLATION
One-line Description:
"Config HP-IB Card" is displayed during install of Data Analysis Only SW
Problem:
|
During installation of the Data Analysis Only LC/MSD ChemStation product, the "Configure HP-IB Card" dialog box is displayed. The HP-IB card is not used with the Data Analysis Only product. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: INSTALLATION
One-line Description:
G2730AA LC/MS DA product changed to G2190AA LC 3D if reinstalling S/W
Problem:
|
If you install the G2730AA LC/MS Data Analysis only product, then you want to go back and install a second module, you will notice that the Installation Setup panel has G2190AA LC 3D listed under the products installed for Instrument #1. This is incorrect. It should show G2730AA. If you try to install the G2720AA BioAnalysis software, you will get the message: "This product cannot be added since it is incompatible with the current product you have selected," and you will not be able to install G2720AA. |
Problem Cause:
|
n/a |
Temporary Solution:
|
To install the G2720AA Bioanalysis software after you have installed the G2730AA LC/MS Data Analysis only software, go into the Installation Setup panel, click the Add/Change button, highlight the G2190AA product listed under installed products, then click Delete. Now add the G2730AA and G2720AA products, click OK, then select Install from the Installation Setup main panel. The G2720AA will now install correctly with the G2730AA LC/MS Data Analysis software. |
Fix Information:
|
n/a |
Keyword: INSTALLATION
One-line Description:
35900 - LOADTEST.M method is not loaded for the 35900 A/D module.
Problem:
|
The method LOADTEST.M is not loaded when the ChemStation is loaded for the 35900 A/D module. It is loaded correctly for the 5890 and 6890 GC. LOADTEST.M is required to run the OQ/PV tests. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Copy the method over from a GC session, or from the support folder of the AUTODOC creator. |
Fix Information:
|
n/a |
Keyword: INSTALLATION
One-line Description:
Information during installation needs updating.
Problem:
|
When installing the ChemStation software revision A.08.03 additional information is presented in an "Information" window. This information is out of date and needs to be updated. File is "INSTALL.TXT" Problem Text. If you do not allow the install program to make changes to the PATH setting in your AUTOEXEC.BAT file, you must add the ChemStation and SYS directories yourself (default: C:\HPCHEM;C:\HPCHEM\SYS). This is not necessary with Windows NT. Problem Text. If you are using the 82341C GP-IB interface, you also need to:.... This should read..... If you are using the 82341C/D or 82350 GPIB interface, you also need to: Problem Text. 2) run IOCFG.EXE and..... This should read..... 2) run \GPIB\HPIOLIBS.EXE and........ |
Problem Cause:
|
n/a |
Temporary Solution:
|
Follow instructions in "Problem Text". |
Fix Information:
|
Fixed with B.01.01 |
Keyword: INSTALLATION
One-line Description:
Installed two A/D licences, one instrument appears
Problem:
|
During the installation of ChemStation Rev. A.09.03, A.10.01 and A.10.02 following issue has been reported: Installing Product G2077aa (A/D licence) as instrument 1 and Product G2073aa (A/D control module) as instrument 2, the configuration editor will install and set up instrument one only. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The installation needs to be done in two steps: First install G2077a A/D system as instrument one and finish the installation. Then add the second instrument G2073a and finish the installation. Both instruments are available in the configuration editor. |
Fix Information:
|
n/a |
Keyword: INTEGRATION
One-line Description:
Manual Integration Events not Visible in Events Table
Problem:
|
Manual integration events may now be added a Data Analysis Method using the appropriate submenu in Data Analysis/Integration. In the "Edit Integration Events" dialog box, manual integration events can be activated for the method using a checkbox. Manual integration events are not displayed in the integration events table. |
Problem Cause:
|
n/a |
Temporary Solution:
|
To view the currently defined integration events, use "Print Method" and request a printout of the integration events tables. |
Fix Information:
|
n/a |
Keyword: INTEGRATION
One-line Description:
Solvent peak integration very sensitive to integration parameters
Problem:
|
The integration of a solvent peak is very sensitive to timed integration events defined near its start and end. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Do not define timed integration events near the baseline of a solvent peak in routine use. |
Fix Information:
|
n/a |
Keyword: INTEGRATION
One-line Description:
Edit Entire Method: "MWD Default" integration events table
Problem:
|
Start with default method. Proceed with Edit Entire Method. Update to the enhanced integrator. Since no signal is loaded, the event editor displays the first default events table that it stores: MWD Default The events table description is greyed out. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use the select table button to switch to the appropriate signal specific events table. |
Fix Information:
|
No fix planned. |
Keyword: INTEGRATION
One-line Description:
Baseline construction for two adjacent solvent peaks incorrect
Problem:
|
Under certain circumstances, the standard integrator does not display the baseline construction correctly when two adjacent solvent peaks are detected. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use either the enhanced integrator, or make sure that no two adjacent solvent peaks are detected, e.g. do not use tangent skim or change the time for tangent skimm on. |
Fix Information:
|
No fix planned |
Keyword: INTEGRATION
One-line Description:
Standard integration: do not remove the default integr events table.
Problem:
|
The below text was taken from HELP. Basically, removing the DEFAULT integration events table will then cause the Method to be converted from the Stardard integrator to using the ENHANCED INTEGRATOR. For proper operation, the default table must not be deleted. The ChemStation, however will allow you to delete the default integration events table. The integration events control how a peak in the signal is integrated. The system uses the default integration events table for all the signals unless you setup individual tables for specific signals. The Autointegrate function automatically creates individual integration event tables for each signal. If for example, you have a TCD signal and your integration events table does not have the TCD signal in the list, then the integration happens using the DEFAULT integration events table. This happens because the TCD signal is not contained in the table. The signals combo box displays all the signals used to date. You can select a signal from this list and create or edit the integration events table for this signal. If a signal in the signal combo box is marked by an asterisk, this indicates that an integration events table exists specifically for this signal. The COPY TABLE button copies the selected integration events table to the current integration events table. The REMOVE TABLE button deletes the selected integration events table. BUT, the REMOVE TABLE button must not be used to delete the default integration events table even though the ChemStation will let you. If there is a FID2 signal in the table and marked with an asterisk, it will be used instead of the DEFAULT integration events table. [DMC June 1998] |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: INTEGRATION
One-line Description:
Integration results (enh. integ.) may differ between A.04.xx and A.06.01
Problem:
|
When integrating the same data file using the enhanced integrator with a revision prior to A.06.01 (e.g. A.04.03) in very rare cases it might happen that the results differ slightly. This was mainly observed in conjunction with tangent skimming. |
Problem Cause:
|
The deviations are due to defect repairs which were done between the revisions. A defect fix affects the integration result if tangent skimming is used in the integration events table. This might result in some small deviations for the calculated area(s) of affected peak(s) where tangent skimming is used. |
Temporary Solution:
|
We would recommend to create a system verification test with a typical method and datafile from the old Version of the software. You should test this method and datafile with later revisions to verify that the method has not been affected by the mentioned change. |
Fix Information:
|
n/a |
Keyword: INTEGRATION
One-line Description:
Initial area reject affects manual integration, peaks are not integrated
Problem:
|
Peaks can not be integrated manually. |
Problem Cause:
|
The settings of the events of the built in integrator do also apply to manually integrated peaks. Especially height reject and area reject can prevent manually integrated peaks from beeing integrated. |
Temporary Solution:
|
Check the settings of the events of the built in integrator. Integrator -> Integration Events... and set them to values that will allow to display the manually integrated peaks. |
Fix Information:
|
n/a |
Keyword: INTEGRATION
One-line Description:
Manual integration of chromatograms extrcated from isoplot causes error
Problem:
|
Manual integration does not work on signals that were extracted from an isoplot. The error message "item doesn't exists is displayed. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Export the extrcated data as an AIA file and than load the data again, using File -> Import File -> Load AIA File. Now the manual integration works. Or perform the following Determine the object number [x] of the extracted signal in CHROMREG using the Window Functions, and then type SetObjHdrVal ChromReg[x],"SignalSource",0 on the command line, to integrate the signal manually. |
Fix Information:
|
No fix planned |
Keyword: INTEGRATION
One-line Description:
Edit Integration Events box has missing accelerator keys.
Problem:
|
The "new" integrator has missing accelerator keys in the Edit Integration Events box. Example, return should act as Enter. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: INTEGRATION
One-line Description:
DerivObj causes manual baseline on display to jump
Problem:
|
Using the command DerivObj Chromreg[1],7,0,3 for smoothing of a chromatogram, the display of baselines from manually integrated peaks is not correct. Only the display is affected, tha area calculation is correct. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned |
Keyword: INTEGRATION
One-line Description:
Integrator reports peaks with hight, width = zero, independent of params
Problem:
|
The standard integrator reports peaks with area, height, width and symmetry to be zero, independent of the filter settings. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use the enhanced integrator. |
Fix Information:
|
n/a |
Keyword: INTEGRATION
One-line Description:
Manual integration does not produce same area as "Genie" integrator.
Problem:
|
User has a single (huge) peak that starts at 12 min and end at 47 min. Using manual integration to cut the peak up into slices does not produce the same total area as the single peak calculated by the system. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Workaround is to use the newer "enhanced integrator". This has been thoroughly tested and produces the same, correct results with the system, and with manual integration. |
Fix Information:
|
n/a |
Keyword: INTEGRATION
One-line Description:
Tangent Skim Mode value not printed in method printout.
Problem:
|
Added 3 tangent skim mode events in the integration events dialog box. Each one had a different mode (EXP, STRGT, STD). When printing the integration events of the method, the lines read Tangent Skim Mode 2.600 Tangent Skim Mode 2.800 Tangent Skim Mode 3.000 The mode never listed on the printout. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: INTEGRATION
One-line Description:
Wrong peak height calculated for extremly unsymmetrical peaks
Problem:
|
For extremely unsymmetric peaks it has been observed that the calculated peak height is sometimes too small. This happens only with an awkward setting for the initial peak width. If the initial peak width is chosen too large, the peak apex of an unsymmetric peak might not be correctly determined. In that case the retention time label in the chromatogram is not shown at the peak apex as it is done otherwise. If you are dealing with extremely unsymmetric peaks you should choose the initial peak width as small as possible. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Choose the initial peak width in "Integration Events" as small as possible. |
Fix Information:
|
n/a |
Keyword: INTEGRATION
One-line Description:
Incorrect integration results on trace substance peaks using Split Peak Event
Problem:
|
Under the condition of a high and dominating peak followed by small shoulder peak, the area and peak width results might be incorrect if the two peaks are sperated by a split peak event. |
Problem Cause:
|
The problem is caused by a peak width testing of the integrator that generate area slices too broad for the shoulder peak. |
Temporary Solution:
|
Decrease the initial peak width setting in order to allow a sufficient slicing of the shoudler peak. Using a manual split peak event might be preferable, since fixed split peak events cannot always be applied to a whole series of chromatograms. |
Fix Information:
|
This defect will be fixed in a new ChemStation revision, planned for summer 2004. |
Keyword: INTEGRATION
One-line Description:
Deletion of tangent skimmed front peak may cause inconsistent results
Problem:
|
The following integrator problem has been found for the deletion of tangent skimmed front peaks: Whenever deleting a tangent skimmed front peak by dragging the “delete peak” cursor just over the front peak, the base peak's integration result get added multiple time to the integration results. Redrawing the tangent skimmed baseline does not delete this additional integration result and reports based on these integration results become inconsistent. Affected revisions: Rev. A.10.01 and A.10.02. Affected workflows The defect is limited to workflows that include the deletion of tangent skimmed front peaks. It only affects the uncommon work practice of dragging the “delete peak”cursor over the front peak. This defect does not affect: o The common case of tangent skimmed tail peaks. o Manually integrated tangent skimmed front peaks without further manual modification o Correction of the front peak baseline using the “Draw tangent skim baseline” function (most common work practice for baseline correction) o Deletion of a tangent skimmed front peak using a single mouse click (second common work practice for baseline correction) |
Problem Cause:
|
n/a |
Temporary Solution:
|
Manual correction of a tangent skimmed front peak baseline position should be done either by simply re-drawing the tangent baseline. Deletion of tangent skimmed front peak should be done with a single mouse click or by dragging the “delete peak”cursor over a larger area including the base peak. |
Fix Information:
|
There is currently no fix planned. |
Keyword: ISOPLOT
One-line Description:
Isoabsorbance Plot: floating point exception DIVIDE by ZERO detected
Problem:
|
When displaying the Isoabsorbance plot with a ratio scale, a floating point exception (division by zero) can occur, if the upper limit for the color scaling is set to 0.0. |
Problem Cause:
|
n/a |
Temporary Solution:
|
As a temporary work-around, use a different number, slightly greater than 0.0 (e.g. 0.1 or 0.01). |
Fix Information:
|
n/a |
Keyword: ISOPLOT
One-line Description:
IsoAbsorbance Plot: Contour Line Printout Printed With Wrong Scale
Problem:
|
When printing a Contour Plot from Isoplot, the prinout may have an in- correct scale: e.g. 'Log' while 'Ratio' is selected, or 'Ratio' when 'Lin' is selected. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: ISOPLOT
One-line Description:
Very large UV-files cannot be loaded into isoplot
Problem:
|
As soon as the *.uv file containing the spectral data exceeds a certain size limit of approximately 4 MB it cannot be loaded into isoabsorbance plot. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Generate the isoplot for a smaller wavelength or time range. These ranges can be set in the isoplot options. |
Fix Information:
|
No fix planned. |
Keyword: LC ACQ
One-line Description:
1049A ECD displayed signal.
Problem:
|
The on line plot of a HP1049 ECD detector is 10 times higher that the actual reading. The raw data is not affected by this. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: LC ACQ
One-line Description:
Prevent analysis... option in Solvent Bottles filling Screen inactive
Problem:
|
In the Solvent Bottles filling Screen, the items: Prevent analysis if level falls below x Liters and Turn pump off if running out of solvent are grayed out. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Pump firmware versions below A.2.32 do not support this feature. Update the firmware of your pump to the latest revision. |
Fix Information:
|
n/a |
Keyword: LC ACQ
One-line Description:
Injection volume not printed after data acquisition
Problem:
|
The injection volume is not included in the report on a single run. |
Problem Cause:
|
If the runtime of the detector is shorter than the runtime of the pump the injector also stays in run time and this information is not ported to the report. |
Temporary Solution:
|
Use the post time feature of the pump and select the same stop time for the pump and the detector. or Reprocess the run with data analysis only. |
Fix Information:
|
n/a |
Keyword: LC ACQ
One-line Description:
Printing of method does not include ALS temperature
Problem:
|
The temperature of the thermostatted autosampler G1329A is not printed using Print method |
Problem Cause:
|
The temperature setting is not part of the method in A.05.0X. It is part of the system configuration, just like for example the volume of the seat capillary. |
Temporary Solution:
|
The temperature is not part of the method. Store additional signals from the thermostatted autosampler during data acquisition to prove the temperature of the thermostatted ALS. |
Fix Information:
|
No fix planned |
Keyword: LC ACQ
One-line Description:
HP1100 VWD dark current test does not work
Problem:
|
The dark current test for the HP1100 VWD from the diagnostics does work correctly if no HP1100 pump is configured in the system. |
Problem Cause:
|
This is caused by the fact that the pump stop time is required and the VWD dark current test method only contains the stoptime for an HP1100 pump. |
Temporary Solution:
|
Load the dark current test method, set a stop time of 2 min and save the method. The test will perform OK now. |
Fix Information:
|
n/a |
Keyword: LC ACQ
One-line Description:
ECD 1049 does not start from scheduler
Problem:
|
Not possible to turn on ECD 1049 from scheduler with the PrepRun command. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use Print SendModule$(ECD,"Cell=ON") after the PrepRun command. Make sure that the pump is already working, because a flow of 0 ml/min damages the ECD. |
Fix Information:
|
No fix planned |
Keyword: LOGBOOK
One-line Description:
Save GLP data without standard data analysis - error message in logbook
Problem:
|
If a method is set up with a custom data analysis macro and 'Save GLP data' enabled, but without standard data analysis, following error entry appears in the logbook: Saving GPL Data for rawdata ============================================ In Command DelTab in macro evaluate at line 1 in file STDIN Error 16289 occurred: the specified register does not exist ============================================ |
Problem Cause:
|
If only a customized data analysis macro is selected the 'Save GLP Data' option does not work. This can be explained by the fact that some registers are required for this which are only generated during standard data analysis. |
Temporary Solution:
|
To generate a GLPsave-register the standard data analysis has to be enabled. |
Fix Information:
|
No fix planned. |
Keyword: LOGBOOK
One-line Description:
The logbook entries are listed in the wrong order.
Problem:
|
Some logbook entries are too long to fit on one line and are split over multiple lines. The order of viewing is incorrect and inconsistent with other places. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - tutorial removed and replaced by "Getting Started Manual" -Co execution UV vis ChemStation and HPLC systems is not supported -long file names support - and more in this context these issues are fixed. |
Keyword: LOGBOOK
One-line Description:
System Exception 200 in lbkproc.c at 742. Please report to HP.
Problem:
|
If you move or delete the LOGBOOK file from the temp directory you will get an error "System exception 200 in lbkproc.c at 742. Please report to HP". File should not be kept in the temp directory or it should be protected so thet it cannot be moved or deleted when the instrument session is enabled. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Do not move or delete this file. |
Fix Information:
|
No fix planned. |
Keyword: LOGBOOK
One-line Description:
Sequence logbook is inconsistent and confusing.
Problem:
|
If a sequence Logbook happens to be open for on-screen viewing at the time that a Sequence of the same name is started, the new INSTRx.LOG book is not displayed. The displayed logbook show on the screen does not appear to get updated during the sequence as it runs. It appears that nothing is being recorded. But, it is. Selecting the Sequence logbook later shows the correct information, however, it was appended to the previous sequence log of the same name. In contrast, if the logbook is NOT on screen when a sequence of the same name is is initiated, a NEW version of the sequence logbook is opened, the happenings are recorded on-screen, and the 'old' version is lost. This is inconsistent. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: LOGBOOK
One-line Description:
A.08.03: Sample name is not correct in logbooks.
Problem:
|
n/a |
Problem Cause:
|
In GC Chemstation A.08.03 the sample names are not shown correctly in logbooks. Instead of the sample name there is just some squares, pound signs, etc, on the line starting with Method, Instrument running sample.... Problem is benign and has no effect on the operation of the software. |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: METHOD
One-line Description:
Load GLP Method: Method Modifications in current method are lost
Problem:
|
If the currently loaded method has the same name as a method that will be loaded using the GLP Save register, it is not obvious that the method loaded before the GLP method was loaded will be changed to the parameters of the method from the GLP Save register. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Load DEF_LC.M before loading GLP data |
Fix Information:
|
No fix planned |
Keyword: METHOD
One-line Description:
Method does not print information from Specify Report and Signal Options
Problem:
|
Printing the method does not print the information from: Specify Report and Signal Otions screen This was printed in revisions A.3.xx. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: METHOD
One-line Description:
Method Change History: only 10 characters of operator name are printed
Problem:
|
In the method printout only a maximum of 10 characters is printed for the operator name in the method change history. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Restrict the entered operator name to 10 characters and use the comment on method change history for entering more information. An entry of 30 characters is possible there. |
Fix Information:
|
No fix planned. |
Keyword: METHOD
One-line Description:
"Syntax Error In cmd/fct macro": Trailing comma in Sample Info
Problem:
|
As a consequence of a trailing decimal point in the amount field of the sample info dialog, the following error message is displayed for every analysis: "Syntax Error In cmd/fct macro" Full error message is: Parsing problem in \SAMPLE.MAC at line 4. SAMPLECALAMT 0.,1,1 ^!!!(16.char) Unknown character: .(ASCII code: 46) PARSING Error |
Problem Cause:
|
n/a |
Temporary Solution:
|
Remove the trailing decimal point from the Sample Information dialog box. |
Fix Information:
|
n/a |
Keyword: METHOD
One-line Description:
"Save Method" and "Datefiles" accept illegal file names. (ex blanks)
Problem:
|
"Method Save" accepts illegal characters for the file name, e.g. blank characters. Saving the methods leads to an error message. The directory cannot be deleted from Windows File Manager. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Avoid using blank characters for file names. You can delete the directory from the MS-DOS prompt using the MS-DOS DELTREE command. |
Fix Information:
|
No fix planned. Windows 95 allows using file names that include blank characters. |
Keyword: METHOD
One-line Description:
Possible GLP issues with "Save Method With Data".
Problem:
|
One can enable save method with data in the run time checklist and the saved method is not the same as the executed method. This can happen if the user loads a method. Then changes instrument setpoints for example, and runs the method. The method saved in the data file is simply copied from the method on the disc which in this case may not be the same. |
Problem Cause:
|
n/a |
Temporary Solution:
|
1. Do not change instrument or method setpoints before making a run. or 2. Save the method before making a run. NOTE. This only happens with run method. Run sequence forces the method to be saved first and also downloads all setpoints to the instrument, correcting changes. |
Fix Information:
|
n/a |
Keyword: METHOD
One-line Description:
Injection SRC/Loc in the print method screen is confusing.
Problem:
|
The term "Injection SRC/Loc in the print method screen is confusing to a non English speaking person. It is not obvious what it means. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The term SRC/Loc stands for Source/Location. |
Fix Information:
|
n/a |
Keyword: METHOD
One-line Description:
A method or sequence may still appear in list even after being deleted.
Problem:
|
If a method (or a sequence) is deleted from the disk with the Windows File manager, it will still appear in the method (or sequence) combination box in the top toolbar (Method & Run Control). Clicking on this file has no effect, no message that this file does not exist. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Do not use Windows File manager to delete methods/sequences. Use the ChemStation FILE / DELETE submenu which updates the most recently used (MRU) list. |
Fix Information:
|
No fix planned. |
Keyword: METHOD
One-line Description:
5890: Aux Channel not listed correctly in method printout.
Problem:
|
The HP5890 requires the user to define the plumbing environment for implementing either makeup gas compensation or split vent flow. Because of this the default method lists the aux epc under two headings. The first heading is under Auxiliary Channel and the other is Aux Channel Split Flow Settings. Because the print method task uses the default method as the template for printing the method, the printed method will include both listings even though the function is not available under the Instrumentation menu for that particular channel. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: METHOD
One-line Description:
1050 MWD: time table entries for signal C are not saved with method
Problem:
|
Time table entries for the 1050 MWD signal C are not saved with the method. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Add the time table entries for the signal C manually to the mwd1.mth file in the *.m method directory. This can be done by opening this file file with an editor such as notepad. Add the line(s) specifying the settings for signal C at the end e.g. at 1.00 SignalC=200, 4, 550, 100 In the example the wavelength of signal C will be changed to 200 nm (bandwidth 4 nm, reference 550 nm) at a run time of 1.00 min. Save the changes. This has to be redone any time the method was saved in the ChemStation. |
Fix Information:
|
n/a |
Keyword: METHOD
One-line Description:
'Error 41313 in pre-run macro occured' when starting a run
Problem:
|
When starting a run a dialog box appears stating: 'Overwrite directory c:\hpchem\x\temp? OK/Cancel' Selecting 'Cancel' results in an error message 'Error 41313 in pre run macro occured' |
Problem Cause:
|
The method was loaded from the HPCHEM\x\TEMP directory. |
Temporary Solution:
|
Do not store methods in the temp directory. |
Fix Information:
|
n/a |
Keyword: METHOD
One-line Description:
Very long entries for the method information are partially truncated
Problem:
|
The method information is limited to a certain number of characters corresponding to approximately 9 lines of continuous text. Additional characters will be truncated. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: METHOD
One-line Description:
35900E. Run time gets rounded up in print method. .
Problem:
|
n/a |
Problem Cause:
|
If you set the run time on a 35900E A/D converter to 9.5 minutes, it appears as 9.51 minutes when the method is PRINTED. Defect is cosmetic. The "real" run time used internally in the software is correct. |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: METHOD
One-line Description:
35900E "units/volt" gets rounded down in print method.
Problem:
|
If you set the "units/volt" on a 35900E A/D converter to 1000000 or 1e6, it appears as 999999,978 uV when the method is PRINTED. Defect is cosmetic. The "real" units /volt used internally in the software is correct. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: METHOD
One-line Description:
Pressure unit is not correct on CE ChemStation method printout
Problem:
|
The printout of a CE method shows mbar instead of bar for the High Pressure Value. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Printout this Known Problem Report and keep it with your method printouts. |
Fix Information:
|
This defect is planned to be fixed with ChemStation A.10.01 |
Keyword: METHOD
One-line Description:
1050 VWD method printout shows too many digits for the Peak Width setting
Problem:
|
The method printout for the 1050 VWD shows more significant figures compared to the selection list of the VWD user interface. This does not affect the ability to restore the method using the printed information, since the peakwidth can only be choosen from a selection list. |
Problem Cause:
|
n/a |
Temporary Solution:
|
A printout of this Known Problem Report should be stored along with the method printouts. The following table shows the corresponding printed values to the setting in the user interface. It can be used to recreate the method starting from the printout. UI setting method printout ------------------------------------------------------------- 0.013 min 0.013 min 0.026 min 0.027 min 0.053 min 0.053 min 0.13 min 0.133 min 0.27 min 0.266 min 0.53 min 0.532 min 1.06 min 1.064 min 1.60 min 1.596 min |
Fix Information:
|
No fix planned. |
Keyword: METHOD
One-line Description:
AM/PM in time for entries in Method History, also with 24 hour time format
Problem:
|
The time format for entries in Method History is taken from Windows, according to the settings in control Panel, Regional Options, Time. Regarding this settings "AM l" and "PM l" symbol will appear in Method History. The behavoir remains when the 24 hour time format is configured. |
Problem Cause:
|
n/a |
Temporary Solution:
|
To get the proper 24 time stamp just delete "PM" "PM symbol" (and AM from "AM symbol") in Regional Options. Then the above mentioned time will be displayed in 24h time format. This applies for Windows 2000 and Windows XP Professional. |
Fix Information:
|
No fix planned |
Keyword: METHOD
One-line Description:
method with many peaks might give an error when trying to print the results
Problem:
|
If a calibrated method is contains many compounds it may happen that a red macro error is observed when the user tries to display the results. Report creation is not possible. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD ANALYSIS
One-line Description:
AIA export of MS data contains pointer to original data
Problem:
|
If you load a ms tic signal and convert it to an AIA-file, the file is created. When you load that AIA-file again and try to get a spectra out of it that works! The problem is that the AIA file is only the 2-d total ion chromatogram. All spectral information is gone. In the AIA file there is a pointer to the msd1.ms file, but if the msd1.ms file is deleted then there are no spectra available. The ChemStation does not tell the user that it gets the spectra from another file. The user might delete the msd1.ms file to save disk space thinking that the spectral data is contained in the AIA file. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD ANALYSIS
One-line Description:
Error "load signal for datafile containing spectra!" when create isoplot
Problem:
|
Loading MS files, all kind of spectra, create isoplot: red line: " do a load signal for a datafile containing spectra! To verify the problem: 1. Load cafcal01.d and try to get the isoplot--error message 2. Load MSpurity.d , get isoplot --works fine Mixing some files i found: you can only run the iosplot for a msfile if a *.uv file exist. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD ANALYSIS
One-line Description:
Current baseline marks shift up when draw new manual baseline.
Problem:
|
With the LC/MSD ChemStation, if you load a chromatogram in in data analysis, then smooth that signal (Savitzky-Golay algorithm) integrate the chromatogram, then draw a manual baseline at some point in the chromatogram, the current baseline marks will shift up. This only will occur if the chromatogram has already been smoothed. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD ANALYSIS
One-line Description:
"Error 17923 occurred in command TABTEXT$..." when printing report
Problem:
|
Printing a custom report or ChemStaitn report. Include the column information. The system gives an error during printout: error 17923 occured in command TABTEXT$ in macro FRPT_printdispatcher at line 906 in file \core\frpt.mcx Paramter 3: a value is outside the legal range This problem is due to: set a column in column description, BUT don't mark it -set installed to NO : system gives error -set installed to YES: system prints fine |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD ANALYSIS
One-line Description:
No object titles for Deconvolution's Charge States and Components spectr
Problem:
|
In Deconvolution, the windows showing Charge States and Components have spectra with no object titles. When these windows are copied and pasted into a foreign application, there are no titles describing what they are. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD ANALYSIS
One-line Description:
MSD FIA parameters displayed on UV chromatogram
Problem:
|
If you set up an FIA run with a ramped MSD parameter (for example Fragmentor), sometimes on the graphic report the MSD parameter values will appear in the UV chromatogram instead of the MSD TIC. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD ANALYSIS
One-line Description:
GPF in module HPGRCL00.DLL if too many ions are found in mass spectrum
Problem:
|
If too many ions are found in a mass spectrum, you can get the error message HPCore caused a GPF in module HPGRCL00.DLL at xxxx:xxxx when the software goes to label the spectrum. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD ANALYSIS
One-line Description:
HPCORE cause GPF in module CTL3DV2.DLL when running LC/MSD Ref Coll. CD
Problem:
|
The error HPCORE cause a general protection fault in module CTL3DV2.DLL at 0002:1A3T can occur when running the LC/MSD Reference Collection rev. B.00.00 CD while the LC/MSD ChemStation online or offline session is also running. |
Problem Cause:
|
n/a |
Temporary Solution:
|
You must close the LC/MSD ChemStation offline and online sessions before running the LC/MSD Reference Collection. |
Fix Information:
|
n/a |
Keyword: MSD ANALYSIS
One-line Description:
LC/MSD System Verification test gives error in online ChemStation session
Problem:
|
n/a |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD ANALYSIS
One-line Description:
LCMS Standard report in A.08.03 is on 2 pages
Problem:
|
The standard LCMS report now is on 2 pages. It used to be on 1 page in A.06.03. This is seen as a severe defect. Want to have the old report back. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD ANALYSIS
One-line Description:
Error "Identifier (MSO_PPwidth) is illegal or variable can't be manipulated"
Problem:
|
After upgrading from rev. A.09.01 to A.09.03 LC/MSD ChemStation, then go into Data Analysis and select the Peak Purity tool and click on the first peak, the error "Identifier (MSO_PPwidth) is illegal or variable can't be manipulated" can occur. This does not occur with a clean load of rev. A.09.03. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD ANYONE
One-line Description:
TIC and EICs Overlap Mass Spectra in Target Report
Problem:
|
In both Target report styles, the time axis in the merged TIC/ EICs overlap into the mass spectra. This overlap is seen with all paper types and both orientations. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD ANYONE
One-line Description:
The ChemStation starts up minimized after MSD Anyone has been installed
Problem:
|
After you install the MSD Anyone software, then you want to start up the ChemStation software separately, the ChemStation software will start up minimized on the Task Bar. You have to click the right mouse button and select Maximize to start up the ChemStation. The MSD Anyone software installation seems to change how the ChemStation software starts up. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD ANYONE
One-line Description:
Multiple snapshot windows sometimes printed as part of the report.
Problem:
|
If you have the real time display selected, occasionally you will get a series of snaphsot windows printed together with the MSD Anyone reports. |
Problem Cause:
|
n/a |
Temporary Solution:
|
You can usually correct the problem by closing the MSD Anyone software and restarting it. If that doesn't help, close down the software, delete ...\hpchem\1\config.reg, then restart the software. This should fix the problem. |
Fix Information:
|
n/a |
Keyword: MSD ANYONE
One-line Description:
If you select a method with arrow keys, the method won't run.
Problem:
|
When you are logging in a sample, if you click on the method but then use the up or down arrows to select the method, the method that is displayed and that you think you have selected is not the method that will be used. |
Problem Cause:
|
n/a |
Temporary Solution:
|
This screen requires that you select a method by using the mouse. |
Fix Information:
|
n/a |
Keyword: MSD ANYONE
One-line Description:
An error on the ChemStation is not displayed on the MSD Anyone screen
Problem:
|
If the ChemStation has an error or is hung, the error is not displayed in the MSD Anyone Status screen. The MSD Anyone software will just stop running samples. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD ANYONE
One-line Description:
When there is an ALS fault, MSD Anyone S/W thinks it has moved samples
Problem:
|
When there is an ALS fault, the MSD Anyone software thinks samples have already been moved from the external to the internal tray, but actually they haven't. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD ANYONE
One-line Description:
Error message "Insufficient positions are available"
Problem:
|
If there are samples in the internal tray positions 84-100, and you go to enter a batch, you will get a error message: "Insufficient positions are available", eventhough vial positions 1-83 are empty. The system has to finish running vials in positions 84-100 before you can enter any additional samples. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD ANYONE
One-line Description:
Note date is shown in the 'Login Time' field in the Status window
Problem:
|
Note date is shown in the 'Login Time' field in the Status window. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD ANYONE
One-line Description:
Sporadically, the system hangs wihen a method is being loaded.
Problem:
|
Sporadically, the system just hangs when a method is being loaded. The ChemStation status is ready (green) and the MSD Anyone status window looks normal. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The hang might be associated with having the real time display turned on in the MSD Anyone software and having a Post Run time specified in the ChemStation method. The workaround is to either turn off the real time display or eliminate the Post Run time. |
Fix Information:
|
n/a |
Keyword: MSD CONTROL
One-line Description:
System can lock up if capillary voltage is set to less than 500V
Problem:
|
If the capillary voltage is set to less than 500 volts, the system sometimes will lock up when you start a run and you will have to reboot. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Set the capillary voltage to a value above 600 volts. |
Fix Information:
|
n/a |
Keyword: MSD CONTROL
One-line Description:
Upper time limit for MSD should be the same as for LC pump
Problem:
|
The upper time limit for the MSD is 650 minutes as compared to the upper time limit of 99999 minutes for the LC pump. Both limits should be the same. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD CONTROL
One-line Description:
In Diagnosis, the Vaporizer heater reports connected with API-ES source
Problem:
|
In Diagnosis, the Vaporizer heater reports "connected" when you have an API-ES source. It should say "disconnected". |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD CONTROL
One-line Description:
F1 Help topic hot link not working for some Instrument menu items
Problem:
|
The F1 Help topic link key will not work and will give the error message "The help topic does not exist. Contact your application vendor for an updated Help file. (129)" for the following menu items in the Instrument menu in Method and Run Control view: Set up Pump Set up Injector Set up Column Thermostat Set up DAD Signals |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD CONTROL
One-line Description:
A "+" in the sample prefix may lead to a crash during acquisition.
Problem:
|
If the sample prefix in a file name (sample info dialog) has a "+" (for example 160+DNA), this will lead to a crash during acquisition. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD CONTROL
One-line Description:
Most MSD Run log errors cannot be decoded
Problem:
|
The MSDLogBook register contains an error table with the last 20 MSD run errors represented as 256-bit hex numbers. The macro dgMSReportFault decodes only the last error in the log. A utility is needed to decode (with time stamps) all errors in the MSD logbook. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD CONTROL
One-line Description:
'Explain' button in Diagnosis view should be labeled 'Help'
Problem:
|
In the graphical user interface in the Diagnosis View, you can use the Edit/Review Limits dialog box to set caution and warning limits for some parameters. This dialog box has a button labeled Explain that links to online help. This button should be labeled Help. Explain is inconsistent with NT 4.0 standards and inconsistent with the rest of the software. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD CONTROL
One-line Description:
Changing groups in acq. while Buffer Overflow present will give error
Problem:
|
When changing groups in an acquisition (as specified in Set up MSD Signals panel) while "Buffer Overflow" is present, an error will occur. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Eliminate the occurrence of the "Buffer Overflow" error by increasing the threshold in acquisition. |
Fix Information:
|
n/a |
Keyword: MSD CONTROL
One-line Description:
Multiple FIA does not run if group name contains a dash
Problem:
|
n/a |
Problem Cause:
|
If when setting up to run a multiple FIA series, the group name contains a dash (-), the multiple FIA series will not run. Also, after adding an FIA method to the group and selecting File/Close, then going back into multiple FIA and selecting the group again, the method will no longer be associated with the group. |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD CONTROL
One-line Description:
MSD icon is yellow when all temperatures/flows are at setpoints
Problem:
|
After the LC/MSD ChemStation software is loaded and the first time an acquisition is started, the MSD icon may be yellow and the MSD not ready when all temperatures and flows are at their setpoints. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Stop the aquisition, then press the RST button on the SmartCard, and then after the SmartCard reboots the MSD will go green and become ready. |
Fix Information:
|
n/a |
Keyword: MSD CONTROL
One-line Description:
Application Error in DLLHOST.EXE when setting up for running Multiple FIA
Problem:
|
When going into Run Control/Run Multiple FIA Methods, then select Edit/Group/Add and then enter a group name, then select Edit/Method/Append, intermittently the following error will occur: "An application error has occurred... DLLLHOST.EXE Exception: access violation: (0xc0000005,Address: 0x10011c5b After closing and restarting ChemStation, running Multiple FIA will work without error. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: MSD CONTROL
One-line Description:
Get application error in DLLHOST.EXE when setting up for running Multiple FIA
Problem:
|
If you into Run Control/Run Multiple FIA Methods, then select Edit/Group/Add and give it a group name (eg testgroup), then select Edit/Method/Append, intermittent you will get an error: "An application error has occurred... DLLHOST.EXE Exception: access violation: (0xc0000005, Address: 0x10011c5b If you then close ChemStation, you will get an HPCORE error (no other details, no GPF message), then you click okay to that and ChemStaiton window will close. It occurs with WIndows 2000 or WInNT |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: OTHERS
One-line Description:
During a sequence: GPF in HPCORE, module HPDOP_00.dll at 001a:0001f5
Problem:
|
During a run the following error can occure GPF in HPCORE, module HPDOP_00.dll at 001a:0001f5 |
Problem Cause:
|
n/a |
Temporary Solution:
|
This was a one time event. Only logged for information. |
Fix Information:
|
n/a |
Keyword: OTHERS
One-line Description:
Exchange of volumetric unit in Gilson autosampler not possible
Problem:
|
There is no function to drive down the plunger of the gillson 215 autosampler. This is necessary to change the volumetric unit. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Start "Rinse Syringe Pump" from the Sampler menu, switch of the sampler when the plunger is at the correct position. Now the syringe can be exchanged. Switch on the sampler and selecte Reset sampler from the menu Sampler. |
Fix Information:
|
To be fixed with next release of CombiChem. |
Keyword: OTHERS
One-line Description:
Plates per meter calculation on peak tools macro is incorrect
Problem:
|
The plates per mater calulated by the peak tools macro differ from the value calculated by the extended performance report. |
Problem Cause:
|
The peak tools macro is wrong by a factor of 10. |
Temporary Solution:
|
If using an change the line if _HPCE=1 then; v = 100; else; v = 1000; endif in the file PKSTOOLS.MAC. macro GetColumnPlatesPerMeter. To if _HPCE=1 then; v = 100; else; v = 100; endif The length of a LC column is also measure in mm. |
Fix Information:
|
n/a |
Keyword: OUTPUT
One-line Description:
Draw ADC signal: "[Graphic-Window]: Could not create window"
Problem:
|
When displaying an ADC signal in data analysis, the following error message may occur: "Graphic-Window: Could not create window" The behaviour is observed, when the signal options are set to overlay/ use ranges/each in full scale and the range parameters are below the minimum signal level (e.g. 0 to 40 mAU). |
Problem Cause:
|
n/a |
Temporary Solution:
|
Change the range specifications for the response axis so that the maximum value is really greater than the minimum response in the signal. |
Fix Information:
|
No fix planned. |
Keyword: OUTPUT
One-line Description:
CP2: CANNOT ADDRESS EXTERNAL DEVICE: PRINTER
Problem:
|
The HP ChemStation may generate error messages when running under Win95 and no default printer has been assigned in Control Panel. When trying to print without an assigned default printer, the following errors may be reported: CP2: CAN NOT ADDRESS EXTERNAL DEVICE:PRINTER when continuing. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Make sure your Win95 is set up with a defined default printer. The HP ChemStation needs to access the default printer's driver to retrieve device settings required for the formatting calculations. |
Fix Information:
|
No fix planned. |
Keyword: OUTPUT
One-line Description:
Method name is not in output if Method is printed to a file
Problem:
|
Information about the file name and location of a method is not included in the output file generated by using File->Print->Method destination: File. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Type in the required information in the dialogbox Method->Method Information of the Method and Run control view. |
Fix Information:
|
n/a |
Keyword: OUTPUT
One-line Description:
ISO 9660 standard does not allow for .D extension on directories
Problem:
|
The HP ChemStation stores its data and methods in directories and uses an extension (.D or .M) for them. This is not in line with the ISO9660 standard supported by CD-ROM recording software. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Disable the ISO9660 compliance checking in the CD-ROM recording software |
Fix Information:
|
n/a |
Keyword: OUTPUT
One-line Description:
Print Module cannot start HPSPL00.EXE, Error Code 2
Problem:
|
At start-up, it has been reported that the ChemStation generates an error message, not being able to start HPSPL00.EXE. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Try starting HPSPL00.EXE manually or restart Windows. |
Fix Information:
|
No fix planned |
Keyword: OUTPUT
One-line Description:
Printing to a networked printer may not work from ChemStation
Problem:
|
The HP ChemStation is not able to print to a networked printer if the corresponding printer port is set up using a UNC (Universal Naming Convention) style port name and the port name exceeds 8 characters or uses extended or blank characters. Example: The following assignment does NOT work: "\\PrintServer\Laserjet 3 in Building AZ 2nd Floor Next to Copier" The following assignment does work: "\\PrintServer\LJ3AZ-2" |
Problem Cause:
|
n/a |
Temporary Solution:
|
Do not use UNC names, capture a printer port and print to this port. |
Fix Information:
|
n/a |
Keyword: OUTPUT
One-line Description:
Printing problems using Epson printer at 360x360 resolution
Problem:
|
A variety of problems are seen printing from the ChemStation to the Epson printer at high (360x360) resolution. Examples of the problems: Text Report - rows of the peak table seem to overlap - unreadable Multi-page chromatogram - size printed is at approx 50% of page. |
Problem Cause:
|
n/a |
Temporary Solution:
|
This is a design issue. The printer driver is only supported when the printer is operated at 180 x 180 dpi and not 360 x 360. |
Fix Information:
|
No fix planned. |
Keyword: OUTPUT
One-line Description:
WMF export problems on import into various graphics programs
Problem:
|
Importing chromatogram metafiles into other graphics packages may lead to problems when the chromatogram is in a zoomed-in state (e.g. clipping a large solvent peak to view the real data). Many import filters do not handle the clipping correctly and the graphic either goes beyond the picture frame or displays extra ghost lines. The same problem occurs when exporting ChemStation graphics as HPGL files (using a plotter printer driver redirected to a file). |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: OUTPUT
One-line Description:
printspooler cannot print, when Environment var TEMP with ANSI != OEM
Problem:
|
The ChemStation Print Spooler does not print if the TEMP environment variable contains characters belonging to the extended character set (e.g German "Umlauts"). |
Problem Cause:
|
n/a |
Temporary Solution:
|
Make sure the TEMP environment variable points to a directory that does not contain extended characters in its name. |
Fix Information:
|
No fix planned. |
Keyword: OUTPUT
One-line Description:
Curve Segments of zoomed-in graphic missing on serial plotter
Problem:
|
When using the plotter driver delivered with Microsoft Windows and a serial ColorPro with or without Graphics Enhancement Cartdridge, curve segments of the chromatogram may be missing, e.g. when plotting a zoomed-in view of the data. Apparently, the clipping of the curve is not handled correctly by the plotter driver. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: PEAK PURITY
One-line Description:
Peak Purity Preferences Influence Calculated Library Match Factors
Problem:
|
In an automated library search, a different match factor may be reported if the peak purity preferences are modified. E.g. When changing the spectrum wavelength range in the purity preferences, a different library match factor may be reported. |
Problem Cause:
|
If the peak purity preference lead to a peak purity factor that does not meet the purity criterion (exceeds the threshold), the automated library search algorithm performs a multi step search on the spectra acquired at the front and at the tail of the peak and generating match factors for the upslope and downslope spectra. Due to the smaller signal to noise ratio of the up-/downslope spectra, the match numbers found when comparing with the library spectra may be somewhat smaller than when comparing apex spectra. |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: PEAK PURITY
One-line Description:
Peak Purity: Peak Purity does not always discard spectra below threshold
Problem:
|
Spectra seem to be taken for Peak Purity that should be discarded be- cause their absorbance amplitude is less than the defined absorbance threshold. |
Problem Cause:
|
Spectra selection is done according to the following criteria: - set 2 reference spectra and calculate the difference spectrum considering the absorbance threshold that was set - evaluate all spectra in the data matrix and find one that exceeds the threshold after it has been background corrected. - refine the reference spectra: the spectra before the first and after the last one that exceed the threshold are the new reference spectra. Considering the redefined reference spectra can lead to absorbance am- plitudes that are smaller than the initially set absorbance threshold. |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: PEAK PURITY
One-line Description:
Selected Reference Spectra different for Select Purity/Select Spectrum
Problem:
|
The reference spectra chosen by the system in "Select Peak Purity" and "Select Peak Spectra" are not identical even if the preferences are the same. |
Problem Cause:
|
The algorithms used for the selection of reference spectra are different in peak purity and the "select peak spectra" function. In peak purity, an additional adjustment step is performed which takes the absorbance threshold into account. This is necessary to prevent artifacts resulting from negative difference spectra when background correcting and comparing all individual spectra with the selected spectrum. |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: PEAK PURITY
One-line Description:
Peak purity causes the error "Register out of range"
Problem:
|
Using Peak Purity causes the error message A register is out of range and the ChemStation seems to be locked. |
Problem Cause:
|
Peak Purity allows to select only part of the spectra for analyzing and if the number of spectra selected is not enaugh this error messages appears. |
Temporary Solution:
|
Select more spectra to be used for the calculation. |
Fix Information:
|
n/a |
Keyword: PEAK PURITY
One-line Description:
Peak Purity: "The specified register does not exist"
Problem:
|
If 2 DAD Signals are loaded to Offline Data Analysis with only the 2nd containing any stored spectra and a peak from the first signal is selected for Peak Purity Determination, following error message appears: "The specified register does not exist" At the same time the displayed signals disappear. |
Problem Cause:
|
n/a |
Temporary Solution:
|
To re-display the loaded signals switch to calibration task and back to spectral task. The described problem has no further impact on operation and is caused by the fact that selected peak contains no spectral information. |
Fix Information:
|
n/a |
Keyword: PEAK PURITY
One-line Description:
A09.03 Peak Purity calculation
Problem:
|
In Peak Purity Task the Purity Calculation of the peak will change after hitting the option button and leaving the window without changes. The Purity Factor of the Peak will be recalculated and the result can differ. |
Problem Cause:
|
n/a |
Temporary Solution:
|
When working with peak purity, Agilent stronly recomments to update to the new spectra/purify options. After a new method is created based on def_lc.m and you are going to use the purify option For the first time, the system will ask you to chose the newer version - select YES. Methods already specified with the older spectra/purity options can be updated by Typing following command into the command line: SPC_NewVersion=1 The system will update to the newer spectra/purify options. |
Fix Information:
|
n/a |
Keyword: PROGRAMMING
One-line Description:
NO DDE communication possible with Visual basic 5.0
Problem:
|
No DDE communication is possible with the ChemStation and Visual Basic 5.0. |
Problem Cause:
|
The 16bit and 32bit versions of DDE do not work together. As the ChemStation uses 16bit DDE, only programming languages that also use 16bit DDE can be used. |
Temporary Solution:
|
Use a 16bit version of Visual Basic. |
Fix Information:
|
n/a |
Keyword: PROGRAMMING
One-line Description:
The command IsAppLoaded does not work with Windows NT 4.0
Problem:
|
The DDE command IsAppLoaded does not work with Windows NT 4.0. It will always return 0, even if the application is running. |
Problem Cause:
|
The command IsAppLoaded does only work for programs that are in the same virtual DOS machine (VDM) as the ChemStation. This will work for other 16bit applications that run in th esame VDM just as with WIN95. |
Temporary Solution:
|
Use 16 bit applications to perform this command that run in the same VDM as the ChemStation. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Amount (Amount Ratios) = 0.000 in report
Problem:
|
In some cases, Amount/Area ratios (Amounts) are reported as 0.000 in a report although the corresponding compound was successfully measured and identified. |
Problem Cause:
|
This can occur if the measured response (resp. ratio) is smaller than the respponse (ratio) of the smallest level of the calibration curve so that an amount < 0 is calculated when using the calibration curve equation. e.g. y = mx + b m = 8.59858e-1 b = 2.92420e-2 and measured response is 2.08272e-2 ====> resulting amount < 0 ! The HP ChemStation report module does not report amount < 0 and outputs 0.000 instead. This is true for both ESTD and ISTD reports. |
Temporary Solution:
|
The only secure method to avoid this effect is to force the calibration curve through the origin (using "force origin" or "connect origin"). |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Report: "Sort by" option does not work for some report types
Problem:
|
The "Sorted by" option is ignored with some report styles. Report is not sorted by Signal if performance report is chosen. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Performance and Noise Report (GC): "Out of Memory"
Problem:
|
The performance report may generate an "out of memory" error message when using data files with several hundred peaks (e.g. some GC chromatograms) and many data points (e.g. using sampling rate of 5Hz). |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Performance+Library Report: Performance part not printed
Problem:
|
Sometimes, the Performance part of an Performance and Library report is not printed. This can be caused by the Calibration Settings. If 'Uncalibrated Peaks' have to be calculated (with a fixed response factor, or using one of the compounds of the calibration table), the Performance part of the report is omitted. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Sample info not printed with injector program
Problem:
|
In a printout of an injector program that uses a vial number, the information (sample name, or sample info for vial no) is not printed, only the vial number is printed. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Sequence summary not printed for non-chromatographic signals
Problem:
|
Sequence Summary report is printed without any calculations, only the header and method listing are printed. |
Problem Cause:
|
This is cause by a non chromatographic signal included in the report, like pump pressure or composition. |
Temporary Solution:
|
Ensure that only chromatographic signals are reported. Do not include any instrument curves in the report. Check in data analysis view: Report->Edit Instrument curves that no instrument curves are selected. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Excel 4.0 does not read the XLS reports generated by the ChemStation
Problem:
|
Excel 4.0 can not read a report generated as an XLS file from the ChemStation. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use a Excel version higher than Excel 4.0. |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - and more in this context these issues are fixed. |
Keyword: REPORT
One-line Description:
On NT printer settings in ChemStation always show default size
Problem:
|
The paper format with printer and Windows NT can not be changed from the ChemStation. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use the Windows NT setting to Change the default paper size. Select Start->Setting->Printers. Highlight the printer you want to change the default paper size setting for and Select File->Document Defaults. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Reports contained blank lines using a deskjet 870cxi on NT 4.0
Problem:
|
Reports printed with the ChemStation doe contain blank rows. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Install the appropriate driver for the used printer. To obtain the latest printer drivers from HP, refer to http://www.hp.com:80/cposupport/indexes1/prhome.html For Windows NT 4.0 printer drivers can also be found on the microsoft home page http://www.microsoft.com |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - tutorial removed and replaced by "Getting Started Manual" -Co execution UV vis ChemStation and HPLC systems is not supported - and more in this context these issues are fixed. |
Keyword: REPORT
One-line Description:
Area% report: Summed peaks, lib. search and short give different area%
Problem:
|
The area% value for a compound reported in the area% report with a summed peaks table is different in the area percent report and the final summed peaks report. |
Problem Cause:
|
This is caused by two calibrated peaks having the same name assigned. The summed peaks report reports each compound only once, and compounds are identified by compound name and not retention time. The areas of the two peaks are added and reported as one compound. |
Temporary Solution:
|
Make sure that each calibrated compound has a unique name. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Instrument name not printed in custom report
Problem:
|
The item Instrument Name in the custom report generator reports not the name of the instrument the data was aquired with, but the name of the instrument the report was printed with. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use a standard report or use a calculated text to print the acquisition instrument. Append the following macro frame to the file shortutl.mac using the computed text element of the customer report generator: !*********************** name USR_AcqInstName$ !* !*********************** local Text$ Text$=ObjHdrText$(ChromRes,AcqInstName) return Text$ ************************************************************************ |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Peak summing reports can not be used with the custome report generator
Problem:
|
The Peak summing report is not available from the custom report generator. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Please contact the analytical response center referring to this SR number to obtain an approprite example macro. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Overlay signal does not print the correct chromatogram in report
Problem:
|
If multiple files are loaded using the function Overlay signal, only the last loaded data file name is displayed in the header of a report. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The data file name is also printed with each individual signal. Use this information to get the correct data file name. |
Fix Information:
|
No fix planned |
Keyword: REPORT
One-line Description:
Print setting shows wrong print orientation under NT
Problem:
|
The report is printed in an incorrect orientation. That is landscape if portrait was selected or portrait if landscape was selected. |
Problem Cause:
|
If the Printer setup dialog box is called from the Print selected window function, the default setting is changed, but not displayed in the printer setup dialog box. |
Temporary Solution:
|
Open the Printer setup dialog box, select the correct orientation (even if already selected) and select OK. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Laserjet 5n/m driver does not print with LaserJet 5 connected
Problem:
|
The LaserJet 5 does not work with the printer driver for the Laserjet 5n/M. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Install the driver for the LaserJet 5. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Library search causes error in macro optimizeProposals in IDBYLIB.MAC
Problem:
|
A library search can cause the following error message Execution error in macro optimizeProposals at level 4 in cmd/fct ObjHdrText$ loaded from C:\HPCHEM\CORE\IDBYLIB.MAC's line 894 with CRC 714 Not a range. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Change the allowed time range for the library to be searched bigger, so more proposals can be found. Go to Report -> Automated library search Select Search Parameters and increase the value for Left or Right Window |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Want: uncalibrated peaks included in sequence summary report
Problem:
|
The Sequence Summary Report (A.05.0x) does not include the amount for uncalibrated peaks in the Compound Summary. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
GC report: method 2 comment is obtaind from method 1
Problem:
|
n/a |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
lmport of custom. report templates from Rev. prior to A.03 incomplete
Problem:
|
Customized report templates created in the ChemStation rev.'s A.01.00 or A.02.0x containing variables related to the extended performance report cannot be imported into subsequent ChemStation revisions. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Create a new customized report template if extended performance results are required or use the available ChemStation templates. |
Fix Information:
|
No fix planned. |
Keyword: REPORT
One-line Description:
Uncalibrated peaks warning in area% report shows
Problem:
|
The area percent report shows the warning "Calibrated peaks not found" if a peak that is in the calibration table is not in the Chromatogram |
Problem Cause:
|
n/a |
Temporary Solution:
|
Copy the following macro to the file \HPCHEM\CORE\USER.MAC It will delete the zero RTs befor the report prints, so the warning does not appear. !---------------------- !Delete zero RT lines from area percent report !---------------------- Name MyAddHook Parameter MyHook$, MyCommand$ If RowByText(HOOK[1],MyHook$,,Command,"=",MyCommand$) = -1 Then InsTabRow HOOK[1],MyHook$ SetTabText HOOK[1],MyHook$, \ TabHdrVal(HOOK[1],MyHook$,NumberOfRows), "Command",MyCommand$ EndIf EndMacro Name MyDel0 Local Row SortTabRows CHROMRES, "Compound", "FirstPeak~MeasRetTime", "<" Row = RowByVal(CHROMRES, "Compound", ,"FirstPeak~MeasRetTime", ">", 0) If Row > 1 Then DelTabRow CHROMRES, "Compound", 1:Row-1 EndIf EndMacro MyAddHook "PostQuant", "MyDel0" !---------------------- |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Summed peaks table do not summ up to 100%
Problem:
|
The summed peak table of an are% report does not display 100% if two peaks have the same compound name in the calibration table. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Do not use the same compound name twice in the calibration table. Use peak summing or are summing to indicate two peaks belonging to one compound. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Perform. report (Area%): undefined rows for missing calibrated compounds
Problem:
|
When an Area% Performance Report is generated for a calibrated method an additional line appears in the results table for each missing compound with "-" stated for the retention time and 0/- for the other parameters. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: REPORT
One-line Description:
SSR: "Statistic results for Resolution (tangent method) not available"
Problem:
|
The extended statistic results in the sequence summary report can only report standard performance parameters when the selected report style is a standard performance report style. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use another report style (any other standard report style or the extended performance report) either in general or reprocess the sequence with the short report style and suppress individual ChemStation reports to receive the sequence summary report with all desired parameters. |
Fix Information:
|
No fix planned. |
Keyword: REPORT
One-line Description:
Extended performance report: wrong USP tailing factor may be calculated
Problem:
|
In some rare cases the USP tailing factor reported in the extended performance report might be wrong. This was only observed for peaks coded as VB or BV during integration. |
Problem Cause:
|
In cases where the baseline strongly deviates from a horizontal line the calculation algorithm fails. |
Temporary Solution:
|
n/a |
Fix Information:
|
A fix is currently under assessment. |
Keyword: REPORT
One-line Description:
Ext.perf.report: missing or wrong acquisition information may be printed
Problem:
|
It was reported that in very rare cases the acquisition information in the extended performance report might not be correctly printed. This was only observed during online acquisition in a sequence consisting of long runs and with "all spectra" selected for spectral data storage (DAD only). |
Problem Cause:
|
n/a |
Temporary Solution:
|
The correct reports are printed during sequence reprocessing. As an alternative it is recommended to reduce spectra acquisition rate if possible, e.g. by taking peak controlled spectra. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Date format in the ChemStation reports
Problem:
|
The date in the ChemStation reports is only printed with two digits, e.g. 99 instead of 1999. |
Problem Cause:
|
The date format applied in the reports is determined by the operating system. It depends on the regional settings which are specified in the control panel. |
Temporary Solution:
|
There are different sources for dates in the ChemStation reports. A date is printed for - footer - injection date - last changed acquisition method - last changed analysis method - Calibration Data Modified etc. These may all be printed in different formats: 1) Footer and/or header date, date of last change of the analysis method or date of calibration data modification correspond to the short date format from the regional settings. 2) Injection date and the date of the last change of the acquisition method are taken from the raw data file. Therefore these depend on the software version the data was acquired with. Since A.04.01 the data 'file' (actually directory) contains two date sources, one in acqres.reg in binary (xxx sec since 1970) and one in the signal data files as a string (e.g. Dad1a.ch). For injection date the binary information is used and therefore any format available in the regional settings (short date) can be applied. Data files acquired with a software revision prior to A.04.01 do only contain the string. In this case the date format is fixed. 3) In some cases the long date format may be applied instead. . The date format in the logbook printout can't be changed as it is hardcoded. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Error 16166 occurred in Command MoveObj in macro PExtStatisticReport
Problem:
|
The following error message can occur when generating a sequence summary report. Error 16166 occurred in Command MoveObj in macro PExtStatisticReport at line 691 in file C:\HPCHEM\CORE\SSR.MCX: A register is out of range. The sequence summary report includes only the Standard Injection/ Extended Statistics reproducibility report. Sequence Table Line Vial Method Inj CalLine ---- ---- ------ --- ------- 1 1 Meth1 1 1 2 2 Meth1 1 2 3 3 Meth1 1 3 4 4 WASH 1 5 5 Meth1 1 |
Problem Cause:
|
n/a |
Temporary Solution:
|
The error is related to the fact that a NON-CALIBRATED injection is made with method Meth1 immediately after the WASH injection. Insert a calibrated injection after the wash, the sequence summary completes normally. |
Fix Information:
|
No fix planned |
Keyword: REPORT
One-line Description:
Control sample always fails when # plates is used as limit
Problem:
|
Theoretical plates do not work as a Control sample limit in the sequence when performance report style is selected. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use the extended performance report or another control sample limit. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Sequence summary report for individual data files incorrect.
Problem:
|
Individual Reports generated using the sequence summary feature printing individual reports that contain a custom report layout using spectra information report an incorrect data file. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use the standard library search report if peak purity values are needed in a sequence summary report that includes the individual reports. Printing the individual reports during the sequence run works fine for custom and standard library search reports. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Extended performance report to file does not generate WMF files
Problem:
|
If a WMF file is selected for report output and the report style is set to Extended Performance, no WMF file is generated to the data file subdirectory. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Select a different report style and print the WMF file. |
Fix Information:
|
No fix planned. |
Keyword: REPORT
One-line Description:
Extended Performance Report: graphics truncated for unresolved peaks
Problem:
|
In the extended performance report the graphical representation of a peak is cut off at the start and end point of the integration. The integration of the adjacent peaks which are not baseline-separated is done by dropping a peripendicular from the valley to the baseline. This may cause the tangent baseline (4 sigma) to be truncated at the peripendicular drop point for closely eluting peaks in the graphics only. However the calculation of the base width is done correctly. |
Problem Cause:
Temporary Solution:
|
n/a |
Fix Information:
|
A fix is under assessment. |
Keyword: REPORT
One-line Description:
Missing Sequence Summary Report
Problem:
|
In some cases, no sequence summary report will be printed. If the first sequence line contains a method that has Data Analysis disabled in its Run Time Checklist, the sequence summary feature will not be initialized resulting in a missing sequence summary (even if all following sequence lines contain methods that activate Data Analysis). |
Problem Cause:
|
n/a |
Temporary Solution:
|
If you want to run a sequence and want to perform the Data Evaluation part of the analyses at a later point in time, you will disable Data Analysis in all methods listed in the sequence table. If however, a sequence summary report is required, the first sequence line must contain a method that has Data Analysis activated in its Run Time Checklist. Specify a single "Dummy" method that includes Data Analysis in the first sequence line. This will initialize the sequence summary report engine appropriately. |
Fix Information:
|
No fix planned. Use Partial Sequence instead. |
Keyword: REPORT
One-line Description:
Report to file using a write protected data file
Problem:
|
When processing data located on a write protected remote drive (e.g. a Magneto-Optical disk), the following situation may occur: Load the data file from the write protected remote drive. Specify a ".TXT" file as the report destination. The ChemStation report generator produces an error message as it attempts to store the report txt-file into the write-protected source directory. If the report destination is a ".WMF" Windows Metafile, no error message is generated although the report file cannot be stored on the write- protected disk. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
ISTD report reports ISTD signal that is not in the Compound Details
Problem:
|
The ChemStation can be forced to perform ISTD calculations across detector signals by setting the main peak of the ISTD compound in the compound details dialog appropriately and deleting the correlated ISTD peaks (qualifiers) from the table. In this case, ISTD corrections are performed using the ISTD main peak. However, the report still lists the ISTD qualifiers in the report even though they are not relevant for the calculation. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: REPORT
One-line Description:
Report contains wrong data file name
Problem:
|
wrong data file name on report Situation 1: Run a sequence (data acq + data analysis) While seq is running, switch to data analysis, load a file (DEMODAD.D). While the file is loaded, data acquisition of the current sequence run terminates. Now the data analysis portion of the sequence run is executed. For some reason, the data analysis of the sequence run fails (e.g. because the corresponding signals do not exist in the data file). Effect: If the user specifies "Print Report" now, the report shows the data file path and name of the last sequence run in the top line of the report. All other report details, including the chromatogram and sample information are accurate for DEMODAD.D. Situation 2: Run an online sequence. Sequence Parameters specify "According to Run- Time Checklist", Run-Time checklist does not include data analysis. Go to Data Analysis, load a data file and print a report after the first run of the sequence has completed. The report shows the wrong data file name (should be the name of the data file that was interactively loaded, but is actually the name of the last data file that was processed by the online sequence. in its run-time checklist. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Situation 1: Make sure the data analysis part of the analysis runs performed by the sequence do not terminate in error, e.g. because data files cannot be found. Situation 2: Make sure the sequence parameters are set to "Acquisition Only". In this case the data analysis method will not be performed and the mismatch does not occur. In both cases, this will prevent the data analysis method to be termi- nated prematurely (Situation 1) or from being called. Remember, the ChemStation online session only uses one register to process the chromatograms. To prevent interactions between the two processes (online sequence and interactive reprocessing in one session), we recommend to perform reprocessing activities in a Reprocessing Copy of the ChemStation. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
6890 ONLY: The chromatogram does not print correctly with a LJ4.
Problem:
|
There appears to be a very intermittent problem when printing chromatograms from a 6890 GC to a LJ 4 printer. Sometimes the chromatogram trace (or portions only) is missing. Axes, RTs, baselines, tickmarks are always correct. Reports (text only) are always correct. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use the tested driver, 31.v1.35 or 31.v1.50, is recommended. The problem normally appears after a week or so of intensive use where there have been hundreds and hundreds of short runs. The problem often goes away, for another week or so, if the following actions are taken to recover a large single disk area. Once a week. . . . Shut down the ChemStation, shut down Windows. SCANDISK the drive. Delete all lost clusters. Delete all temp files, make sure there is enough temp work space. DEFRAG the disk drive, full defragmentation. Start WINDOWS and the ChemStation. |
Fix Information:
|
Install Windows-95 and GC Chemstation revision A.04.01 or greater to fix this problem. ^^^ No other fix planned. |
Keyword: REPORT
One-line Description:
Error, In command tabHdrVal in macro SSR_deleteseque at line 654 in file
Problem:
|
If you have Sequence Summary Report selected, and you start a sequence but Abort immedialely because you thought of an error you made, or an instrument error, you will get an error in the sequence summary report as follows, :'In command tabHdrVal in macro SSR_DeleteSeque at line 654 in file SSR.MCX error 1791 occured: Parameter 2: the table was not found.' |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: REPORT
One-line Description:
Problems with laserjets when printing chromatograms at 600 x 600 dpi.
Problem:
|
Printing multi page chromatograms to a LaserJet at 600 x 600 dpi may result in an "Internal Arithmetic Overflow". Only some of the ten page limit will be printed. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Run the LaserJet at 300 x 300 dpi which works correctly. |
Fix Information:
|
No fix planned. |
Keyword: REPORT
One-line Description:
Can access the Sequence Summary menu when running a sequence.
Problem:
|
When running a sequence, it is possible to access the Sequence Summary menu item, make changes to the options (X the items) but cannot exit the screen without loosing the selected choices. The OK button is disabled! It should not be allowed to access the Sequence Summary screen when a sequence is running. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Wait until the sequence is finished before selecting the options in the sequence summary menu. |
Fix Information:
|
No fix planned. |
Keyword: REPORT
One-line Description:
Lower combo box of the main toolbar in report layout is clipped.
Problem:
|
Report Layout - Main Toolbar - 1024 x 768, Large font. The lower combo box of the two stacked combo boxes in the toolbar is truncated at the bottom whan large font is selected. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use small font if this is a problem. |
Fix Information:
|
No fix planned. |
Keyword: REPORT
One-line Description:
GLP Sequence Summary reports may fail if reprocessed on different instr.
Problem:
|
If the customer generates a GLP Sequence Summary Report on a different system, or on a different instrument session on the same system, from where the data was collected, the GLP report may fail, and there may be error messages in the logbook. There is no problem if one generates a GLP Sequence Summary Report from an ONLINE instrument session. Nor is there a problem in producing the same report if reprocessing the data from an OFFLINE session of the SAME instrument. |
Problem Cause:
|
This behavior is as designed: the ChemStation with the ORIGINAL online instrument used to acquire the analytical data is also the one having stored specific hardware configuration information for the instrument used. This information is not present on the alternate ChemStation system (or alternate instrument on the same system) used for offline reprocessing. |
Temporary Solution:
|
Correct behavior is to run the offline session on the same system and instrument as was used to originally collect the data. If (and only if) it is CRITICAL that data be reprocessed offline on a different system or instrument, one can emulate the original instru ment by copying all files found in the original instrument's home directory ( HPCHEM\1 or \2 or \3 or \4 ) to the equivalent instrume nt home directory on the alternate system or instrument. Be sure to backup all files found in the target directory first so as to be able to restore the original instrument configuration informati on once finished. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
File->Printer Setup always shows Document defaults with NT.
Problem:
|
File->Printer setup does not display the correct paper size. |
Problem Cause:
|
n/a |
Temporary Solution:
|
File->Printer Setup always displays the Document default setting, but the correct paper will be used. To change the default setting, use Settings->Printers, right mouse click->Document Defaults under Windows NT 4.0. |
Fix Information:
|
No fix planned |
Keyword: REPORT
One-line Description:
Print of Peak purity results do contain additional line
Problem:
|
The purity report contains an additional line. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Ignore the third line with the Similarity curve. The heading should read Peak curves and not Peak signals. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Lib search rpt causes err in IDBYLIB.MAC at line 616, table not found
Problem:
|
A library search report can generate the error meesage Execution error in macro insertResults at level 5 in cmd/fct rowByVal loaded from E:\HPCHEM\CORE\IDBYLIB.MAC's line 616 with CRC 7A23 Parameter 2: The table was not found. When more than on library is used for searching. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Printing a HPCE method with HPCE timetable does not work correctly
Problem:
|
Printing a method on a CE ChemStation can cause the error message Field 8000 current new '1 HIFLUSH 7.0 bar, 0.0kV, 0.50 min, I: Vial number one, O,3: Vial with an OK button might appear. The method printout will not contain the complete method information. |
Problem Cause:
|
This is caused by the description string in the CE preconditioning table containing to many characters. |
Temporary Solution:
|
Assign shorter names to the vials in the vial table. |
Fix Information:
|
No fix planned. |
Keyword: REPORT
One-line Description:
Statistical moments are not calculated for tangent skimmed peaks
Problem:
|
The statistical moments are not calculated for tangent skimm peaks in an extended performance report. Tangent skimmed peaks are marked with an X in the peak type row. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned |
Keyword: REPORT
One-line Description:
Missing help on timed event 'baseline backward'
Problem:
|
n/a |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Temp file might not be deleted after multi page report generation
Problem:
|
When selecting 'Multi page (landscape)' for the chromatographic output in the report together with 'Sample Info on each page' a temporary file generated during reporting may not be deleted (report styles 'short' or 'detail' only). |
Problem Cause:
|
n/a |
Temporary Solution:
|
Remove the files ~p3d*.tmp (* stands for 4 characters or numbers) from the directory specified by the TEMP environmental variable after you have finished reporting. |
Fix Information:
|
No fix planned. |
Keyword: REPORT
One-line Description:
HTML reporting looses handles under Win 95
Problem:
|
When doing extensive printing of HTML reports the performance might decrease. This was only observed under Windows 95. |
Problem Cause:
|
The printing of HTML reports under Windows 95 looses handles. |
Temporary Solution:
|
n/a |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - tutorial removed and replaced by "Getting Started Manual" -Co execution UV vis ChemStation and HPLC systems is not supported. - and more in this context these issues are fixed. |
Keyword: REPORT
One-line Description:
Print to file: "Result obtained with enhanced integegrator" is missing
Problem:
|
When printing a report to a text file the line indicating that the integration was done with the enhanced integrator is missing. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Print the report to the printer or to HTM instead. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Performance reports: Missing characters for not found compounds
Problem:
|
In calibrated performance reports missing compounds are marked as 'not f' instead of 'not found' or '-' in the amount column of the results table. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Peaks with retention time 0.0 printed in report
Problem:
|
Sporadically ChemStation reports include peaks with a retention time of 0.0. Those peaks are reported in addition to the 'real' peaks, i.e. the rest of the report is correct. So far the defect has only be observed with GC ChemStations Rev. A.06.01. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Create a text file "user.mac" in HPCHEM\core with following content: ===================================================== Name DelZeroPeaks Local Row SortTabRows ChromRes[1], "Compound", \ "FirstPeak~MeasRetTime", "<" ! search for first row with a measured retention time > 0.0 Row = RowByVal (ChromRes[1], "Compound", -1, \ "FirstPeak~MeasRetTime", ">", 0) if (Row > 1) ! delete all rows before this one DelTabRow ChromRes[1], "Compound", 1:Row-1 endif EndMacro SetHook "PostQuant", "DelZeroPeaks" |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Printer Setup dialog always shows default values
Problem:
|
The Printer Setup dialog box always shows default values for orientation, paper size and paper source. If you change any of these values, close the dialog and open it again it does not show your modifications but still the default values. Nevertheless your modifications are reflected in a printed report. |
Problem Cause:
|
It seems, that there is a problem with Windows code, because Windows 2000 handles this box correctly (last settings will be displayed). Windows NT always shows the default settings, which have been set through Control Panel/Printers. |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned in the ChemStation (problem caused by WinNT) |
Keyword: REPORT
One-line Description:
Sample amount is not stored in Chromres
Problem:
|
Printing a ESTD% or ISTD% report after manually loading a datafile is not printing the amount in %. The reports generated by a sequence or a reprocessing sequence or printing the correct amount in %. |
Problem Cause:
|
The sample amount specified in the sequence is not transfered to the Chromres register. |
Temporary Solution:
|
It is always possible to reprocess an injection with a single line sequence with a different value for sample amount. This value is considered for the report. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Incorrect column description data in the report a08.03
Problem:
|
In the columns database, the data for the columns 19095P-MS6E and 19095P-MS0E, the film thicknesses have been swapped. The report prints this wrong column data. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Enter the correct column data manually. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Report parameter ("% of page" - Time )changing when printing HTM-report
Problem:
|
It has been reported, that the usage of the HTM-function with in the Specify Report of the Data Analysis is might result in a method changed flag of the method under following certain circumstances: Settting anything else than 95 for the "% of page" - Time, this value isl automatically changed back to 95 printing a report. This change back to the default value will result in a "method modified" flag. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
This behavior has been fixed with ChemStation B01.01. |
Keyword: REPORT
One-line Description:
method chnaged ater loading appears on report even if method has not been change
Problem:
|
Using the print function within the calibration table (PRINT BUTTON) of the Data Analysis, the "method modification flag" will be set and printed on the following ChemStation reports till the method is saved. |
Problem Cause:
|
The "method modified after loading" flag will be set and printed on the ChemStation reports in A09.0x and A10.0x after following circumstance. |
Temporary Solution:
|
Instead of using the print function from the calibration table window, the print function of File\Print\Calibration Table in Data Analysis can be used. The "method modified flag" will not be set. |
Fix Information:
|
fixed with B.01.01 |
Keyword: REPORT
One-line Description:
spectra options are not printed correctly
Problem:
|
n/a |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
cannot load logo in wmf into report layout of chemstation
Problem:
|
Within A10.0x Report Layout some usercreated *.wmf will be displayed either as path or will appear misaligned on screen and printout. This will depend on the version of *wmf of the created file. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Peak Type PARABOLIC INTERPOLATION mentioned in GC
Problem:
|
n/a |
Problem Cause:
|
On some GC instruments, running ChemStation Rev,. A.08.03. WinNT it has been reported, that on the printed method information report the following remark is stated in the "Events" are listed the "Peak Top Type:" PARABOLIC INTERPOLATION is stated. Online help of the ChemStation tells that under "Peak Top Type" that Parabolic Interpolation is always used for gas chromatography, only Capillary Electrophoresis is using different Peak Top Types. Therefore this information is usually not printed on a GC ChemStation Method. The situation is that the customer has in all 3 gas chromatographic systems with Vers.A.08.03 and WinNT. But only one system shows this behaviour. After reinstalling the software on that PC we had at once the same behaviour. By viewing a Vers.A.08.03 with WinNT in the office we had the same problem. It was not possible to reproduce the remark (PARABOLIC INTERPOLATION) on Vers.A.09.03, Win2000. The point is that the customer needs a declaration from Agilent Technologies for that behaviour. For example an explanation that tells that this problem is recognized by Agilent. |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Customer can't scroll with the mouse in ChemStation
Problem:
|
With ChemStation it has been reported, that the mouse wheel function to scroll within reports and tables is not functioning. This seems to be Windows XP/2000 related issue, the scroling function is working within NT systems. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
This problem will be fixed with Rev. B.01.03. |
Keyword: REPORT
One-line Description:
problem with sizing of the chromatogram in a Short Report
Problem:
|
In the Specify Report dialog it is possible to size the chromatogram output in terms of % of the page size. However, sizing the response in the range between 20% and 40% does not have any effect on the chromatogram output in the report. The feature only works in the range 40% to 100%. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
"Seq Line"(Sequence line) value for Calibration samples printed wrong in report
Problem:
|
Following issue can be seen on ChemStation A.10.02 reports, using intervall options within the sequence table:
Running a sequence with follwing setup:
1. line: "Sample type" => "Calibration",
"Cal Level" => "1", "Interval" => "2"
2, 3 and 4. line: "Sample type" => "Sample"
"Datafile" => " |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
G1600A CE method print out in CEC mode reports mbar
Problem:
|
Printing the method of a G1600A CE instrument in CEC mode, the method is printing the pressure value is given in mbar, instead off bar. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Please make a manual correction to bar on the report accordingly. |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
some imported logos are not working in custom report layout
Problem:
|
Importing EMF formated picutres (used for logos) in ChemStation Rev. A10.x may not displayed correctly on the previewed and as well on the printed report. |
Problem Cause:
|
n/a |
Temporary Solution:
|
In case of problems, use vector graphics for logo implementation in ChemStation. (e.g created with CorelDraw) |
Fix Information:
|
n/a |
Keyword: REPORT
One-line Description:
Time Ranges not applied correctly in short report
Problem:
|
Within the Data Analysis of B.01.01 Chemstation following issue has been reported: Defining User Ranges in the "Signal options" the Time Ranges are applied to the chromatogram and displayed/printed accordingly, for Response ranges are not taken into account. The issue can only be seen when in addition the Multi Chromatogramm Scaling is set to "each in full scale". |
Problem Cause:
|
n/a |
Temporary Solution:
|
Applying "all the same scale" for the Multi Chromatogramm will fix the issue and the scaling is working correctly. |
Fix Information:
|
n/a |
Keyword: REPORTS
One-line Description:
Printing problems with LJ 5L when running in HOST BASED mode (WIN-95).
Problem:
|
There are problems when printing reports with chromatograms on a system runing a 6890 GC, Windows 95, and a Laserjet 5L printer when the printer driver is in HOST BASED mode. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Set the LaserJet driver to PCL mode which works correctly. |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - tutorial removed and replaced by "Getting Started Manual" -Co execution UV vis ChemStation and HPLC systems is not supported. - and more in this context these issues are fixed. |
Keyword: REPORTS
One-line Description:
GC Inst: Only 1st column information is printed on custom reports.
Problem:
|
On a dual-column setup the only column information that is printed on a custom report (if column info is added to the report) is column #1. Columns #2 information is not printed. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use "standard" report types instead. |
Fix Information:
|
n/a |
Keyword: REPORTS
One-line Description:
GC plus 7673, The injection volume is not printed out in some reports.
Problem:
|
With a GC and Autosampler, the injection volume is not printed in some report styles. This is not GLP compliant. In summary... 1) The injection volume will print out on the standard reports. i.e. if you select the SHORT, DETAIL, PERFORMANCE, etc. from the specify report area, the area percent report will print. 2) If you go into the REPORT EDITOR, and open any of the templates that are available (i.e. AREAPCT.FRP, EXTSTD.FRP, etc.) None of these will print the injection volume... 3) If you create a custom report, and insert your own actual injection volume, or method injection volume, it does not appear in the report. (What you select for a default value when setting up these fields appears.) |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: REPORTS
One-line Description:
Floating point exception INVALID number detected.
Problem:
|
If you have a NORM% method based on area, and you have a summed peak table, when you print the report and include the sumed peak table in the report, there will be an error...... floating point exception INVALID number detected. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Only workaround at the moment is DO NOT PRINT the "summed peak table" in the specify report screen. |
Fix Information:
|
n/a |
Keyword: RUNCONTROL
One-line Description:
35900E: Splitting channels cause problems if using different protocols
Problem:
|
Splitting the 35900E data channels between two instances of the ChemStation will not properly function if one channel is configured using the instrument's HOST address, and the second channel is configured using the instrument's IP address. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Workaround: When splitting the 35900E data channels, address both using the same link protocol. |
Fix Information:
|
n/a |
Keyword: SEQ
One-line Description:
Sequence table user interface displayes wrong method
Problem:
|
When the key down is pressed on the last line of the sequence table the current displayed method will be displayed for all following sequence lines, but after closing and reopening the sequence table dialogbox, the change of the method was not stored. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use the scrollbar to make further lines of the sequence table visible. |
Fix Information:
|
n/a |
Keyword: SEQ
One-line Description:
Sequence Recalibration fails if report style 'Libsearch' is selected
Problem:
|
For the report styles 'Library Search' and 'Performance + Lib Search' it is not possible to perform a recalibration during a sequence run. There is no warning concerning this problem. It is only stated in the sequence logbook that a recalibration in conjunction with a library search report is not possible. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Choose another report style during sequence run and reprocess data with a library search report style afterwards. |
Fix Information:
|
n/a |
Keyword: SEQ
One-line Description:
No datafile name may be entered in sequence table for calibration sample
Problem:
|
When entering data file names in the sequence table it is not possible to enter a name for calibration samples. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: SEQ
One-line Description:
Using Copy/Paste during running sequence potenially corrupts config register
Problem:
|
After a deleting a line in a running sequence where file naming is done using prefix/counter wrong sample names may be assigned to samples following the deleted line. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: SEQ
One-line Description:
Using sequences of different sampling units in different ChemStations.
Problem:
|
Reprocessing of sequences made for a 1090 on a ChemStation that is configured for a 1100 or a 1050 is not possible if vial 0 is used. This is because vial numbering starts with 0 in the 1090 and with 1 in the 1100 and 1050 LC systems. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Configure the system for reprocessing to use the correct instrument, or change the vial number in the sequence table before starting a partial sequence. |
Fix Information:
|
No fix planned. |
Keyword: SEQ
One-line Description:
Change of sample type in sequence table during run has no effect
Problem:
|
A change of the sample type in the sequence table done while a sequence is already running is ignored. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Make all required changes before starting the sequence or insert a new line in the sequence table with the required sample type. |
Fix Information:
|
No fix planned. |
Keyword: SEQ
One-line Description:
No sample name in data file if vial number is left blank is sequence
Problem:
|
If there is no vial number in the sequence table, tha sample name will not be transferred to the data file. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: SEQ
One-line Description:
The sequence table buttons have inconsistent descriptions/operations.
Problem:
|
The buttons in the sequence table only operate with a complete line. However by their description, one would think that they might operate with single cells. Append line - insert line after Insert - insert line before should be called - Insert Line Cut - cut line should be called - Cut Line Copy - copy line should be called - Copy Line Paste - paste line Should be called - Paste Line |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: SEQ
One-line Description:
The order of entering the sequence recalibration is restricted.
Problem:
|
The sequence setup screen doesn't allow the user to start a recalibration at line x>1 if the first sequence line was not a calibration line. The use gets an error message "Calibration run must preceed a sample run". This is very difficult and confusing to set up. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: SEQ
One-line Description:
The 7673 tray graphics are not updated after partial sequence.
Problem:
|
After preparing a partial sequence, the 7673 sampling diagram is still displaying the COMPLETE sequence from the previous time and should display ONLY the vials for the new partial sequence. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: SEQ
One-line Description:
System allows loading a sequence from toolbar while a method is running.
Problem:
|
The system allows you to load a sequence from the toolbar whie a method is running. This is not allowed from the menu (its grayed out). This is inconsistent. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: SEQ
One-line Description:
Dual signal CSV files generation does not work
Problem:
|
Select in the Specify report section : ESTD short report, signal based on area and sorted by RT. Save also a file as CSV file. In the report00.csv it details 9 column to be listed (last rows of the file), when viewing the report01.csv it is missing column number 2 for the signal. It is dropping this column then shifting other columns from the report left one Column. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: SEQ
One-line Description:
Batch Report: duplicated results for multiple signals in Cal table
Problem:
|
If you setup an calibration table for multiple signals and treat the signals separately, the batch output reports the multiple peaks of the same name, but the reported data (RT and Amount) for each peak are duplicates of the first occurance of that peak. Example Calibration table: # RT Signals Compound Amount Area Respf 1 1.001 DAD1 A Peak1 2.000 200 0.0100 2 1.001 DAD1 B Peak1 2.000 400 0.0050 3 2.001 DAD1 A Peak2 2.000 300 0.0066 4 2.001 DAD1 B Peak2 2.000 350 0.0057 Batch report: the reported RT and Amount for Compound nr 2 and 4 are respectively a duplicate of nr 1 and 3. |
Problem Cause:
|
The program generates a link in between the compounds since the names are identical. |
Temporary Solution:
|
This option is only used in case the user preferres are confirmation result rather than a qualifier ratio. To get the confirmation result calculated in the batch table it's recommended to name the compounds different for each wavelength. (e.g. by adding the wavelength information in brackets). This helps as well to differenciate the results on the batch report. |
Fix Information:
|
n/a |
Keyword: SEQ
One-line Description:
Printout of Partial Sequence table misses essential information
Problem:
|
The partial sequence dialog offers the option to print the run list. This printout does not contain: operator date/time information page number total page number instrument name |
Problem Cause:
|
n/a |
Temporary Solution:
|
There is currently no adequate workaround available. |
Fix Information:
|
n/a |
Keyword: SEQ
One-line Description:
Cannot import XML worklist from "long" path
Problem:
|
Using the XML import worklist function with in ChemStation toghether with very long path statements ( more than 18 characters) the system will give the warning: "Nothing imported!", and no worklist will be uploaded into the sequence table. Reducing the path to 17 characters will allow an import of all data. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
The limitation is gone with ChemStation B.01.01 |
Keyword: SEQ
One-line Description:
1100 DAD noise test fails in combination with ChemStore B.03.01
Problem:
|
For LC ChemStation A.10.02 in combination with ChemStore B.03.01 the execution of 1100 DAD noise and temperature stability test fails with "No results available". Other hardware tests that utilize a sequence summary report are affected as well. |
Problem Cause:
|
The test consists of a sequence summary report and the ChemStore code runs a clean-up of temporary result registers when the SSR was generated. Those results are missing when evealuating the test results. |
Temporary Solution:
|
To validate an 1100 hardware module it is possible to connect the instrument to a plain ChemStation PC and execute the tests. |
Fix Information:
|
A ChemStation patch is available. The patch CD (P/N G2183-60074) is included in all new shipments or can ordered from your Agilent support representative. A defect fix is included in ChemStation B.01.01. |
Keyword: SEQ
One-line Description:
comX with X = 1, 2,... as datafile name in sequence table generates errors
Problem:
|
COMx (where x is a number from 1 till 9) cannot be used as file name in ChemStation, because it is a reserved file name. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
With B.01.01, the "Understanding Your ChemStation" manual contains a chapter "File Naming Conventions" where this is explained. |
Keyword: SEQ
One-line Description:
XML Import: Import of LimsId fails if sample amount has been set in import XML f
Problem:
|
Using ChemStation A.10.0x following issue has been reported using the XML functionality: As soon as a Sample Amount is predefined in the XML import file, the import of LimsId fails during "import worklist". |
Problem Cause:
|
n/a |
Temporary Solution:
|
The problem is only seen using a comma instead of a point in the number section Sample Amoung: Because the XML file gets converted into CSV-file (literally COMMA SEPARATED...) the values for Sample Amount which contain "," (e.g.: "274,42") will break the structure of the file and confuse the parser engine. So the values have to be setted using a point. or After the import of the XML worklist the sequence table need to be checked and the Sample Amount need to be added manually. |
Fix Information:
|
n/a |
Keyword: SEQUENCE
One-line Description:
Partial sequence creates the wrong data file name.
Problem:
|
Under certain circumstances, when partial sequence is run, the last data file has the wrong name. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: SEQUENCE
One-line Description:
Wrong sample names in partial sequence table for cyclic recalibration
Problem:
|
When using cyclic recalibration with multiple vials containing the same dilution of a standard the sample name stated in the partial sequence table as well as in the file information of the acquired standard data file does not reflect the names given in the sequence table. Regardless of the the vial number always the name of the first of multiple standards is applied. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: SPECTRA
One-line Description:
Print Selected Window containing UV Spectra
Problem:
|
When printing a selected window containing multiple spectra, the spectra titles are always printed even if the title annotation were disabled in the spectra preferences. If the window contains a large number of spectra in overlay mode, this can result in the titles overwriting the data range in the coordinate system. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Title annotations on the window printout can be influenced by setting the following variable accordingly: Win_PrintTitles = 0 ;(switches titles off on the printout) Win_PrintTitles = 1 ;(titles always on on printout) Win_PrintTitles = 2 ;(title display same as on screen) The variable can be set on the ChemStation command line or in a macro. |
Fix Information:
|
No fix planned |
Keyword: SPECTRA
One-line Description:
User is not prompted to save modified spectra library before lib search
Problem:
|
Modifications made to a spectra library are lost if a library search report is performed without saving the new/modified spectra library to disk. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Save your modifications before running a new library search report. The automated library search feature reloads the original library from disk without prompting the user to save changes to the current library. |
Fix Information:
|
n/a |
Keyword: SPECTRA
One-line Description:
Automated Library Search: No Calibrated Compounds Are Identified
Problem:
|
Occasionally, library search reports do not identify any compounds. The LibrarySearch settings are set to "Identify by library search" In this case, the report indicates that... "No calibrated compounds could be identified!" and lists all peaks in the uncalibrated compounds listing. |
Problem Cause:
|
The library search is based on compound names and retention times. If the spectra library search does not identify any compounds, check whether the compound names in the library and the calibration table match. The compound names in the library must be the same as the names used in the calibration table. |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: SPECTRA
One-line Description:
Library Search: Compounds with high match factors missing in rpt
Problem:
|
Occasionally, library search reports do not list compounds that satisfy the purity and match thresholds in the report. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: SPECTRA
One-line Description:
Reference Spectra Selection for Library Search
Problem:
|
In a multi-signal calibrated method that performs an automated library search, reference spectra for library search are always selected for the largest peak detected for a compound (RT and peak-start/peak-end values may vary for each peak of a compound). This cannot be controlled by redefining the main peak in the compound details dialog box. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
Currently, no fix planned. |
Keyword: SPECTRA
One-line Description:
Iso plot reference option
Problem:
|
The normalization in the isoabsorbance plot window is different from the normalization used in the standard spectral windows. |
Problem Cause:
|
The isobasorbance plot window always uses "Maximum" (or each in full scale) normalization. In the standard spectrum display normalization can be selected to be in a certain wavelength range, based on area, or based on best match. See ChemStation help for further details on normalization techniques. |
Temporary Solution:
|
Use the command loadspectrum to load a spectrum without normalization to the specreg. An example to load the complete wavelength range of the spectra at 11.747 min would be: loadspectrum ,11.474:11.474,0:0,,,,specreg |
Fix Information:
|
n/a |
Keyword: SPECTRA
One-line Description:
Access Spectra Library: "Specified Register not found"
Problem:
|
When accessing the spectra library right after starting up the HP ChemStation and without loading a data file, the following error message is generated: "specified register not found". |
Problem Cause:
|
n/a |
Temporary Solution:
|
Before accessing the spectra library, load a datafile. |
Fix Information:
|
n/a |
Keyword: SPECTRA
One-line Description:
Print Library Entry: "the specified register does not exist"
Problem:
|
Data Analysis / File / Print / Print Library Entry does not function correctly unless a data file has been previously loaded. I. Initialize Chemstation II. Got to Spectra Library View III. Load DemoDAD library IV. Select File / Print / Print Library Entry V. Select Output Format = Short List VI. Print the list - get the following error: "the specified register does not exist " Loading a data file and performing steps IV --> VI works correctly. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: SPECTRA
One-line Description:
Library search generates error insertResults in macro idbylib.mac
Problem:
|
Library search can cause the error message Execution error in macro insertResults at level 5 in cmd/fct rowByVal loaded from E:\HPCHEM\CORE\IDBYLIB.MAC's line 616 with CRC 7A23 Parameter 2: The table was not found. |
Problem Cause:
|
If the first peak has no match in the first library, some tables are not generated, so after searching the second library this error occures. |
Temporary Solution:
|
There are several options to solve this, all have the aim that the first peak has a proposed match in the first library. - Select a different library to be the first - Make the allowed retention time window for the first library bigger |
Fix Information:
|
No fix planned |
Keyword: SPECTRA ANALYSIS
One-line Description:
Refrence spectra are not taken near the peak
Problem:
|
Automatic selection of reference spectra selects spectra far of the selected peak. |
Problem Cause:
|
If the peaks are not separated by the integration and the baseline is connected, the spectra at the start and the end of the basine are used as reference peaks. |
Temporary Solution:
|
Set the integration events so that the peaks are separated. |
Fix Information:
|
No fix planned |
Keyword: SPECTRA ANALYSIS
One-line Description:
Normalization options for spectra can not be selected in dialog box
Problem:
|
The old spectral options dialog sometimes does not correctly set the opt ions for normalization of spectra, once multiple spectra are selected. O ne of the three normalization can not be used. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Select the normalization option you want to use and than start to select the necessary spectra. You can also update to the new spectra options, which allow easier settings (No best match normalization is available). |
Fix Information:
|
n/a |
Keyword: SPECTRA ANALYSIS
One-line Description:
Library search is not done on peak purity peak
Problem:
|
If peak purity and library search are used at the same time it might appear that an incorrect peak is used for the library search. |
Problem Cause:
|
Peak purity and library search use independend methods to find out on what peak the function should be performed. |
Temporary Solution:
|
Always select the peak you want to search for in the library before selecting Search, to make sure that the correct peak is selected. |
Fix Information:
|
n/a |
Keyword: SPECTRA ANALYSIS
One-line Description:
Adding noisy spectra to spectra library can cause GPF in HPGRCL00.DLL
Problem:
|
If a very noisy spectrum (more or less just a noisy baseline) is added to the spectral library it happens in very rare cases that a General Protection Fault in HPGRCL00.DLL occurrs when the button for automatic selection of minima and maxima in Wavetable Editor is pressed. |
Problem Cause:
|
n/a |
Temporary Solution:
|
This appears very seldom. Very noisy (baseline) spectra should not be added to the library. |
Fix Information:
|
No fix planned. |
Keyword: SPECTRA ANALYSIS
One-line Description:
GPF in module HPGRCL00.DLL at 0004:00001ada
Problem:
|
When adding a noisy spectrum to a spectral library a general protection fault in module HPGRCL00.DLL was observed in very rare cases. |
Problem Cause:
|
This is due to the spectrum being very noisy. The option "autom." for selecting the wave table entries generates an overflow. |
Temporary Solution:
|
Do not use the "autom." key to generate the wave table. |
Fix Information:
|
n/a |
Keyword: SPECTRA ANALYSIS
One-line Description:
Automated Library Search Does NOT work as expected with 4 library's
Problem:
|
The automated library search report failed under some circumstances when using multiple libraries. |
Problem Cause:
|
The register which should contain the result of the library search was empty. |
Temporary Solution:
|
n/a |
Fix Information:
|
A patch is available on demand |
Keyword: USER INTERFACE
One-line Description:
using the screen resolution 800x600 on a XM2 and XM4.
Problem:
|
In some screen resolutions (e.g. 800*600 large fonts) with some graphics adapters, several ChemStation dialog boxes are too big for the display. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Different graphics driver settings (e.g. small fonts) or updated graphics drivers usually solve the problem. |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - and more in this context these issues are fixed. |
Keyword: USER INTERFACE
One-line Description:
Chromatogram sometimes overlays the calibration table.
Problem:
|
Sometimes the windows overlap if. . . . . 1. No toolbars are loaded 2. A task switch from the integration event screen to Calibrate + Calibration Table is done. then the calibration table is full size and is overlayed by the chromatogram. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Run at a higher resolution (1024 x 1280) and resize the windows. |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - tutorial removed and replaced by "Getting Started Manual" -Co execution UV vis ChemStation and HPLC systems is not supported. - and more in this context these issues are fixed. |
Keyword: USER INTERFACE
One-line Description:
It is possible to overwrite a name in the calibration curve screen.
Problem:
|
If calibration table and calibration curve screen is open and the user changes a peak name, then this name will overwrite the name in the calibration curve screen without deleting it first. This works correctly if the user clicks on another peak and then returns to the original peak of interest. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned |
Keyword: USER INTERFACE
One-line Description:
Compund names not shown on all overlaid chromatograms
Problem:
|
With multiple chromatograms loaded and displayed in separated windows the compund names are only displayed once for each compound. So some peaks might not be labeled on the screen. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Load only one chromatogram to display the compund names correctly. |
Fix Information:
|
No fix planned |
Keyword: USER INTERFACE
One-line Description:
Method history text is truncated after 40 characters
Problem:
|
Method change history text is truncated in Method print out. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Do not type in text longer than 40 characters in the 'Comment for method history' dialog box. |
Fix Information:
|
No fix planned |
Keyword: USER INTERFACE
One-line Description:
DAD 1040 can not be controlled by System diagram, only via menu
Problem:
|
The DAD 1040 can not be controlled by the system diagram. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use the Instrument menu to set the DAD settings. |
Fix Information:
|
No fix planned |
Keyword: USER INTERFACE
One-line Description:
Display of elapsed run time dissappers
Problem:
|
The numbers of the elapsed run time in the Method and run control view dissapear sometimes. |
Problem Cause:
|
With certain combinations of video drivers, font size, number of colors, etc. the numbers can not be correctly disaply in the appropriate Window. |
Temporary Solution:
|
Try other font size, resolution and screen settings. We recommend 1024 x 768 pixels, using 65265 colors and large fonts. |
Fix Information:
|
No fix planned |
Keyword: USER INTERFACE
One-line Description:
A/D-ChemStation: System Diagram not available (Error Message)
Problem:
|
Selecting the system diagram from the view menu of the A/D-ChemStation leads to a series of error messages: 1) Not a directory or file "D:\HPCHEM\LC\LANGUAGE\ENULSAM.REG" 2) "Missing default diagram resolution NLsed ini file. (LSysCont on DRIVERS)" 3) Graphical object LSYSCONT in internal path "" must be loaded first". No system diagram is displayed. |
Problem Cause:
|
A system diagram does not exist for A/D-ChemStation. |
Temporary Solution:
|
Do not use the item "System Diagram" from View menu. |
Fix Information:
|
n/a |
Keyword: USER INTERFACE
One-line Description:
One pump missing in instrument menu if 2 different ones are configured
Problem:
|
If 2 different pumps (1050 pump and 1100 pump) are configured for the same instrument only the 1100 pump is visible as an Instrument menu item (Setup Pump...). The 'More Pump...' submenu is available for both pumps. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: USER INTERFACE
One-line Description:
Column Description is not updated in the Graphical User Interface
Problem:
|
The column description [pulldown menu item "Names (Col/Solv)"] in the lower right corner of the graphical user interface of the "Method & Run Control" view is not updated automatically if a change was made in the Column table (instrument menu). |
Problem Cause:
|
n/a |
Temporary Solution:
|
If the user clicks on the pulldown menu item "Names (Col/Solv)" the column description is updated. |
Fix Information:
|
No fix planned |
Keyword: USER INTERFACE
One-line Description:
Zoom not possible in 3D Signal overlay
Problem:
|
If the default offset values are changed in the 3d signal overlay of the data analysis view, it is not possible to use the zoom function. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Load the signals using signal details and select only the part of the data file of interest, typically the time window where the solvent peak is not included. |
Fix Information:
|
n/a |
Keyword: USER INTERFACE
One-line Description:
GUI for sequence table not correctly displayed
Problem:
|
If a sample is added to the sequence during a run, the GUI of the HP1100 autosampler is not correctly updated. |
Problem Cause:
|
n/a |
Temporary Solution:
|
When the next sample is injected, the GUI is updated correctly. |
Fix Information:
|
n/a |
Keyword: USER INTERFACE
One-line Description:
HPCORE caused an invalid page fault in module ATIWDDE.DLL at 0137:10001b
Problem:
|
It was reported that the HP ChemStation might terminate with the message "HPCORE caused an invalid page fault in module ATIWDDE.DLL at 0137:10001b56" when being operated for an extended period of time. This does only happen if the DirectX utility is installed. ATIWDDE.DLL is a special driver that works with DirectX. DirektX is a utility that enhances multimedia capabilities on your computer and is required for some high-performance games or 3D graphics. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Remove the DirectX utility from the system by choosing "Add/Remove Programs" from the Control Panel and selecting the DirectX utility from the list of installed applications. |
Fix Information:
|
No fix planned. |
Keyword: USER INTERFACE
One-line Description:
Online plot occasionally disappears from system diagram
Problem:
|
Occasionally the online plot integrated into the HP 1100 system diagram turns grey if another method is loaded while an additional online signal window is open. This was only observed when the "use method settings" check box in the "Edit Signal Plot" dialog box is enabled. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Update the view by selecting the method and run control view from the view menu/dropdown list box or remove the check mark for "use method settings" if it isn't required. |
Fix Information:
|
No fix planned. |
Keyword: USER INTERFACE
One-line Description:
The setting for the y scaling is ignored
Problem:
|
When typing in a range for the Y axis in the signal options dialog box on the data analysis view, the range setting is ignored. |
Problem Cause:
|
n/a |
Temporary Solution:
|
You also need to select "All the same scale" in multi chromatogram. |
Fix Information:
|
n/a |
Keyword: USER INTERFACE
One-line Description:
Sporadically, no control menu in list contents window
Problem:
|
Sometimes the list content Window cannot be closed. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Workaround: Select the "list contents" window (by clicking on it). Type the following command on the command line: ClearWin |
Fix Information:
|
No fix planned. |
Keyword: USER INTERFACE
One-line Description:
Macro DIALOG box with a CHECKBOX may cause error message when removed.
Problem:
|
When defining a macro DIALOG box with a CHECKBOX in the definition if the CHECKBOX return variable is not declared (preset to a value), and the CHECKBOX is never selected, execution of the REMOVEDIALOG command produces the following error: Execution Error in macro |
Problem Cause:
|
n/a |
Temporary Solution:
|
Addition of trial = 0 prior to BEGINDIALOG function prevents the error from occurring. |
Fix Information:
|
No fix planned. |
Keyword: USER INTERFACE
One-line Description:
Tutorial does not work correctly when running the GC portion.
Problem:
|
Error message "Not Yet Implemented" when running the tutorial as a GC session and running the system suitability portion. To duplicate do the following steps...... 1. Data Analysis view and Start the Tutorial. 2. Select "To Setup a System Suitability Report" on task panel 3. Select "To Identify your Separation System" (Green text on message panel) Get error message box: Not yet Implemented! |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use the HELP system to learn about the system suitability. |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - tutorial removed and replaced by "Getting Started Manual" - and more in this context these issues are fixed. |
Keyword: USER INTERFACE
One-line Description:
Inconsisten behaviour of spectra library menu vs toolbar button
Problem:
|
When an LC instrument is collecting data, the user cannot load a library file from the Spectra toolbar button. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: USER INTERFACE
One-line Description:
In Calibration Table, Compound Details, there is no column for CSL
Problem:
|
Control sample limits can not be set from the menue Calibration -> Control sample limits and there is no option in the Calibration table (Compound view) to set Control sample limits (CSL). |
Problem Cause:
|
n/a |
Temporary Solution:
|
Select Calibration -> Calibration table Options -> Edit Options and add the column Are Ctrl Smpl. Limits set. Select OK to close the dialog box and select Yes in the column CSL for the compound you want control sample limist for. |
Fix Information:
|
n/a |
Keyword: USER INTERFACE
One-line Description:
A zoomed calibration curve is not correctly copied to the clipboard
Problem:
|
It is not possible to copy the active graphical window to the clipboard in a maximized form. After pasting it to another application it is resized to its original format. |
Problem Cause:
|
n/a |
Temporary Solution:
|
For copying a graphical window to the clipboard and pasting it to another application in its original (shown) size, a macro from the user- contributed library (LC-UCL) is available (HPLC ChemStation Revision A.03.xx or higher). The UCL is on the HP Analytical CD-ROM in the directory: D:\LC_UCL\MACROS The subdirectory "1" corresponds to the required macro. For the installation procedure and a brief description of how to use the macro please refer to the README file. |
Fix Information:
|
No fix planned. |
Keyword: USER INTERFACE
One-line Description:
Activating User Access Level Method Protection from all sessions
Problem:
|
Once defined, the ChemStation User Access Level is applied in all ChemStation sessions, i.e. in all instruments, online and offline sessions and the ChemStore database. When defining the User Access Level, the "Prompt at Startup" dialog box MUST be checked. Otherwise, the User Access Level check will not be activated in the other sessions. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: USER INTERFACE
One-line Description:
6890 GC only: Quick setup operates differently with Dashboard as shell.
Problem:
|
6890 GC only. If Dashboard is installed as the Windows shell, during quick setup the columns screen comes up in another Dashboard window. The system appears to be locked up. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Select the alternate window, select the column, OK the screen. Switch back to the original Dashboard window. NOTE. It is highly recommended NOT to run Dashboard as the shell. |
Fix Information:
|
Will not be fixed. |
Keyword: USER INTERFACE
One-line Description:
The "Fn" function keys are hidden by Signal 2 real time plot.
Problem:
|
The "Fn" softkey images appear just above the message line and are hidden behind the default Signal 2 real time plot window forcing the user to resize the plot window, or not know that they exist. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Resize the windows and close the instrument session if this is a problem. The position will be remembered. |
Fix Information:
|
No fix planned. |
Keyword: USER INTERFACE
One-line Description:
User signals options menu allows only three places, user can set more.
Problem:
|
In the siganl options menu setting min/max values only allows you to see up to three decimal points (.000) even though the user can set higher resolution, more places. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: USER INTERFACE
One-line Description:
The Data View pull down is not active until mouse button is released.
Problem:
|
The pull down list box that allows you to change to each of the three data views does not bring up the list box when you click on the pull down arrow. You must release the mouse button while over the arrow to see the list box. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Release the mouse button while over the arrow to see the list box. |
Fix Information:
|
No fix planned. |
Keyword: USER INTERFACE
One-line Description:
Method Information dialog box is the old style, needs updated.
Problem:
|
The Method information box is the old style Windows format, should be updated to be the new style. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: USER INTERFACE
One-line Description:
Resource problem with tutorial and Windows for Workgroups, rev 3.11
Problem:
|
If there is another application running in the background (i.e. EXCEL) sometimes the window "Pump Setup: LEO" (To Setup a Method" - task, step 3 of 8) comes up incorrectly. There are buttons inactive, which should be active, and no or wrong words are written on them. It also happened, that while ending a task and starting the next one an application error occured: GPF in module HPGGL_00.DLL at 0005:01F4. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Either, close other aplications when running the tutorial, or, update the system to Windows 95 which has better resource management. |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - tutorial removed and replaced by "Getting Started Manual" - and more in this context these issues are fixed. |
Keyword: USER INTERFACE
One-line Description:
ChemStation loses focus after switch to Method and Run control.
Problem:
|
The ChemStation does not return the focus after a selected window switch to Method and Run Control. No application has the focus. (Alt-Tab does not work either). |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use the mouse to return the focus to the ChemStation. |
Fix Information:
|
n/a |
Keyword: USER INTERFACE
One-line Description:
System performance is compromised by redrawing he online plot over/over.
Problem:
|
When scaling a online plot window of 60 minutes and display 2 or more signals, when the internal signal buffer is full, i.e. there are 60 minutes of signals availabloe, saving the current method will cause up to four redraws to occur which is extremely annoying and slows the system down. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: USER INTERFACE
One-line Description:
Often the UP and DOWN arrow keys are not used correctly.
Problem:
|
Up and down arrow keys not meaningful at parameter entry fields like stoptime. Both keys have the same function. They are not doing any scrolling but just deactivate or active the field. This is inconsistent use of the arrow keys. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: USER INTERFACE
One-line Description:
The tutorial covers the "BUSY" message, menus seem not to work.
Problem:
|
When the TUTORIAL is running it covers the "BUSY" indicator on the macro command line. The user does not see the system is busy and tries to select the next, or another, task which does not work, of course. This is particularly annoying on a slow PC where tasks take a longer time. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Move the Tutorial window so that the "BUSY" indicator is visible. |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - tutorial removed and replaced by "Getting Started Manual" -Co execution UV vis ChemStation and HPLC systems is not supported. - and more in this context these issues are fixed. |
Keyword: USER INTERFACE
One-line Description:
Hide and show Status toolbars does not restore screen to previous.
Problem:
|
While in the Data Analysis View, if you delete the signal window, using the (View\WindowFunctions\Delete) then Hide and Show the Status Toolbar it now restores the previously deleted window(s) and it shouldn't. It should restore the wind to the same state it was in when it was hidden. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Delete the windows(s) again. |
Fix Information:
|
No fix planned. |
Keyword: USER INTERFACE
One-line Description:
The scroll bard in many screens are one of three different types.
Problem:
|
If the sequence table is greater than one page, you have to move down the drop cursor on the right side, to read all lines. At the end of the sequence table the drop cursor should be located on the bottom of the screen (drop line) but is not. This is inconsistent. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: USER INTERFACE
One-line Description:
The OQ/PV tests does not display the allowed values.
Problem:
|
When running the OQ/PV tests, the ChemStation does not show the legal values as does many of the other screens. The user has to use trial error to find the correct value. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: USER INTERFACE
One-line Description:
Annotation "tool buttons" and "signal options" are not linked.
Problem:
|
The annotation tool button (toggle compound names on/off, RT on/off axes on/off etc.) do not influence the settings in the signal options dialog box which have the same functionality. They should be linked. Changes made to the chromatogram display with the annotation task-set are lost when switching back to the integration task set. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
No fix planned. |
Keyword: USER INTERFACE
One-line Description:
GPF ERRORS from Windows caused by Instrument name being too long.
Problem:
|
Windows GPF errors have been reported in various GC configurations when the instrument name has "many" characters. Errors is normally VERY intermittent, and has been observed in different screens. Failing instrument name length seems to be a function of the PC speed. Default length is 12 characters (Instrument n) which has also been reported to cause the error. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Workaround is to set a shorter name in the Configuration Editor program for each configured instrument. Change "Instrument 1" to "Inst 1" for example. |
Fix Information:
|
n/a |
Keyword: USER INTERFACE
One-line Description:
Peak Graphics Highlights in data analysis may not be visible.
Problem:
|
When more than 256 colors are selected for the Windows display, the highlights used for integration peak graphics may not be visible. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Change the Video settings to only use 256 colours. |
Fix Information:
|
n/a |
Keyword: USER INTERFACE
One-line Description:
Task icons in Data Analysis view overlayed by File icons
Problem:
|
The task switching GUI is not visible in the data analysis screen. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Close the ChemStation and delete the file CONFIG.REG in the instrument directory for the on line session and the file CONFIG_OFF.REG in the instrument directory for the off line session. |
Fix Information:
|
n/a |
Keyword: USER INTERFACE
One-line Description:
Floating point exception INVALID NUMBER detected.
Problem:
|
Floating point exception INVALID NUMBER detected [OK]. Users click on [OK] then [IGNORE] and the system continues, apparently without problems This is frequently observed during data analysis, but has also been observed at the start of a sequence. Reports appear to be correct. Floating point exception INVALID NUMBER detected [OK]. Users click on [OK] then [IGNORE] and the system often continues. Infrequently the error is followed by a GPF which requires a reboot. This happens on an infrequent random basis, |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: USER INTERFACE
One-line Description:
Tutorial skips step3
Problem:
|
n/a |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - tutorial removed and replaced by "Getting Started Manual" -Co execution UV vis ChemStation and HPLC systems is not supported. - and more in this context these issues are fixed. |
Keyword: USER INTERFACE
One-line Description:
scaling - each in full scale
Problem:
|
Using "Overlaid" and "Each in separate scale" together with a range for the x-axis in the signal options might cause an incorrect y-axis range in certain cases. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Verify the correct settings and options, select a different x-axis range to display the signal correctly. |
Fix Information:
|
n/a |
Keyword: USER INTERFACE
One-line Description:
7673: Missing sampling tray diagram in A08.03
Problem:
|
In A.08.03 software the tray graphical user interface (GUI) is not visible when selected. The tray is "painted" in the correct place but is then painted over and is not viewable. The "hot link" does work. Clicking in the GUI area does bring up the sequence table as before. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Tempory solution for customers who insist on having the GUI available to see the vial locations is to downgrade the software to A.08.01 which works correctly. NOTE. A.08.03 must be deleted and A.08.01 installed as new. Do not overwrite A.08.03 with A.08.01 or the problem will still exist. |
Fix Information:
|
n/a |
Keyword: USER INTERFACE
One-line Description:
6850 GC: The correct tray and Injector Icons are not displayed.
Problem:
|
In all revisions of the software that support the 6850 GC, the injector graphical Icon always displays the eight position turret irrespective of the configuration. If the 6850 is configured for valved injection (no injector), or a three or eight vial location turret, the graphics displays the EIGHTposition turret in error. In addition, there is no GUI for the G2880A, the 22/27 position "mini tray". This is a cosmetic error only, the software works correctly. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Click on the ICON and check the sequence table. The sequence table works correctly. |
Fix Information:
|
n/a |
Keyword: USER INTERFACE
One-line Description:
Disk Drive space remaining icon
Problem:
|
Within ChemStation A10.0x the diskspace icon within the Sample diagram in the Method and Run Control screen does not report remaining disk space on Drive. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
This defect is fixed with ChemStation B01.01. |
Keyword: USER INTERFACE
One-line Description:
Signal Task: Time reference lines only visible with 256 colors on Compaq bundle
Problem:
|
Compaq chemstation bundle PC EVO 510 only: Prod ID: X1155AV with Windows 2000, SR 2 or SR3 In Data Analysis signal Tasks the Time Reference Lines are not shown when selected. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The solution will be to change the hardware acceleration for the video card from the desktop properties. Beware system settings True color 32-bit and a resolution 1024x768. To perform the change: 1. right click on desktop --> select Properties tab 2. set colors to true color and resolution to 1024x768 à go to advanced button 3. select Troubleshoot tab à access to slid bar for hardware acceleration on the video card. 4. Set the hardware acceleration to NONE. |
Fix Information:
|
No fix is planned for this problem. |
Keyword: USER INTERFACE
One-line Description:
Fraction collection module error message given at different Fraction Collector
Problem:
|
Using a system with two or three Fraction collection modules (but no recovery Fraction collector set) the first Fraction collector will show the message "Could not find a valid next position" even if that event occured on one of the other Fraction collectors. If a system is used as recovery fraction collection, the message is shown at the right module. |
Problem Cause:
|
n/a |
Temporary Solution:
|
The graphical userinferface will give the right information about the event occured. In case this error message pops up, the user should watch the Fraction collector modules, to see which one is causing the problem. |
Fix Information:
|
n/a |
Keyword: USER INTERFACE
One-line Description:
Timetable MWD disappears when shifting from 'table' to 'grapics'
Problem:
|
With ChemStation A.10.0x it is reported, that the timetable entries for the MVD are deleted when switching to the Graphic mode for the time table and back to the Time table view. |
Problem Cause:
|
n/a |
Temporary Solution:
|
After defining a timetable for the MVD save the method BEFORE changing the timetable view to graphics. |
Fix Information:
|
fixed with B.01.01 |
Keyword: UTILITIES
One-line Description:
GC ChemStation Scheduler: incomplete screen display
Problem:
|
If large fonts are used, the displayed text in the SCHEDULER looses the last letter depending on the video driver and resolution. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use small fonts or a different resolution to view the entire word. |
Fix Information:
|
n/a |
Keyword: UTILITIES
One-line Description:
Error "Can't get dimension file" when AIA Import of Beckman Gold Nouveau
Problem:
|
Error message "Can't get dimension file" when trying to Import a Beckman Gold Nouveau file in AIA format. |
Problem Cause:
|
Unfortunately, there are different versions of the AIA specification. Different vendors may be generating AIA files according to different specifications and may not be compatible with one another. Hewlett-Packard Co. has developed its AIA support according to the AIA specification 1.0 and is currently participating in a forum of manufacturers of analytical equipment to consolidate AIA import/export formats. |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: UTILITIES
One-line Description:
AIA data from TurboChrom: Can't get required attribute of the AIA file
Problem:
|
Importing PE TurboChrom AIA files into the ChemStation causes the error Can't get required attribute of the AIA file |
Problem Cause:
|
Unfortunately, there are different versions of the AIA specification. Different vendors may be generating AIA files according to different specifications and may not be compatible with one another. Hewlett-Packard Co. has developed its AIA support according to the AIA specification 1.0 and the NetCDF software component 2.3 HP is currently participating in a forum of manufacturers of analytical equipment to consolidate AIA import/export formats. The attribute Injection_Date_Time_Stamp is a AIA mandatory attribute that must be included. |
Temporary Solution:
|
Please contact Perkin Elmer for an updated veriosn of their AIA export that includes the injection_Date_Time_Stamp attribute, as this is a mandatory attirbute of the AIA specification. |
Fix Information:
|
n/a |
Keyword: UTILITIES
One-line Description:
Companion: Selecting French in the Preference Dialog Box uses English.
Problem:
|
ChemStation Companion is not available in French. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: UTILITIES
One-line Description:
Scheduler: "THE MAXIMUM # OF ENTRIES IS 200"
Problem:
|
After multiple days of running the scheduler daily, the following error message may occur: "THE MAXIMUM # OF ENTRIES IS 200" The scheduler should roll the entries off the top once they have been executed, or operate in a FIFO manner. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: UTILITIES
One-line Description:
Help information for Scheduler is incorrect
Problem:
|
Help system of the Scheduler utility: Select "How To" and then "Prepare a Schedule"; HELP text states for the command entry "Enter the command you want to be sent. Click on ? for a complete listing of commands." If you click on "?", the standard "How To" reference info is displayed. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Go into "Reference" and then "What is the Scheduler" sections to find the hypertext for commands. |
Fix Information:
|
n/a |
Keyword: UTILITIES
One-line Description:
Scheduler: "Rejected" displayed in the result status line
Problem:
|
User reports that he has been using the Scheduler application to load a method and then load/execute a system suitability sequence each morning. Suddenly all "Result" status lines were return REJECTED for the same commands that he had always been running. |
Problem Cause:
|
n/a |
Temporary Solution:
|
1. Delete all HPSCHED.xxx files and rebuild the schedule from scratch 2. Reboot the sytstem. |
Fix Information:
|
No fix planned |
Keyword: UTILITIES
One-line Description:
Data Interchange to Excel: "Could connect to Excel"
Problem:
|
When using the Data Interchange Tools (UCL contribution "DAITOOLS.MAC) or File/Export to export say the chromatogram to EXCEL 7.0, the following error messages are presented: Could connect to Microsoft Excel (but EXCEL does start if the PATH is set up correctly) This is followed by question: Do you want the EXCEL chromatogram to be annotated with retention times? Answering NO to this question ends the macro. Answering YES gives an EXCEL message panel (File Reservation) that states: 'HPDAIN' is being modified by |
Problem Cause:
|
n/a |
Temporary Solution:
|
Use a 16-bit version of Excel (e.g. version 4.0 or 5.0). |
Fix Information:
|
No fix planned. |
Keyword: UTILITIES
One-line Description:
Import Pascal Library: "While without endwhile in macro" [convlib.g]
Problem:
|
While trying to run CONVLIB.G on a Pascal ChemStation to export a UV/VIS Spectra library to the HP ChemStation, the Pascal system reports "while without endwhile in macro". |
Problem Cause:
|
n/a |
Temporary Solution:
|
Make sure that the CONVLIB.G macro delivered with the HP ChemStation (Windows) is converted as ASCII text to the PASCAL format. When using the LIF utilities, the conversion type must be set to "DOS text as HP BASIC ASCII". When using the HP Copy Utility delivered with Foreground/Background 5.3, the conversion settings must be "ascii" |
Fix Information:
|
This issue is fixed with Rev. B.01.01. There are major enhanged/changes done to - Operation system requirement Win 2000 SP4, Windows XP SP1a - resolution changed to min. 1024x768 - path changes from HPCHEM to Chem32 - Font styles - spectra option tool set - integration tool set - tutorial removed and replaced by "Getting Started Manual" -Co execution UV vis ChemStation and HPLC systems is not supported. - HTML Help - and more in this context these issues are fixed. |
Keyword: UTILITIES
One-line Description:
System Verification Test does not run if method=current method
Problem:
|
ChemStation verification test does not generate a test if the specified method is the same as the currently loaded method |
Problem Cause:
|
n/a |
Temporary Solution:
|
Work-around: Load a different method before defining a test. |
Fix Information:
|
No fix planned. |
Keyword: UTILITIES
One-line Description:
A.08.03: Companion does not recognize GC-Als methods
Problem:
|
A method that uses the GC autoinjector as injection source, is not used correctly by companion in A.08.03 software. A message box pops up: Configuration Error: Unknown ChemStation injector configuration. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Problem is caused by the "Agilentization" of the software. Workaround is to drop back to revision A.07.01. |
Fix Information:
|
n/a |
Keyword: UTILITIES
One-line Description:
Export of data file to AIA is adding a wrong date-time stamp
Problem:
|
f you create an AIA data file and import it in Waters Mill it has a wrong date-time stamp. As injection date it shows 01/01/1900. Loading this file into chemstation with the AIA import function is giving the correct time-date. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: UTILITIES
One-line Description:
Installation verification report: Timestamp of ref files varies with seasons
Problem:
|
If the user reperforms an installation verfication, the time stamp of the reference file might differ by one hour depending of the season. The default WinNT settings allows the system to adapt the system time automatically to summer time. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Deactivate the automated adjustment of the system time and work in winter time only. (Date/Time properties) |
Fix Information:
|
n/a |
Keyword: UTILITIES
One-line Description:
Ambigous reference for HPLC1100.HLP in Inst Verification after A.08.04 update
Problem:
|
I installed the following ChemStation products revision A.08.03: Instrument 1: G2170AA Instrument 2: G2170AA Instrument 3: G2070AA Instrument 4: G2070AA IQ was OK After I updated this to A.08.04 and run the Installation Verification I had the error: Ambigous reference: HPLC1100.HLP Changed file: HPLC1100.HLP Further checking showed the reference files for gc2d.ref and lc2d.ref showed differnt checksums for this file. |
Problem Cause:
|
n/a |
Temporary Solution:
|
n/a |
Fix Information:
|
n/a |
Keyword: UTILITIES
One-line Description:
XML : LIMIDs modified during reprocessing
Problem:
|
Enabling the XML feature set within ChemStation allows to import XML based sequence files containing LIMS based information, e.g. LIMSIDs. Executing the sequence will create two files, placed in the datafile and the destination file on the pre-set server: Created files in data files: result.xml and LimsID.xml Create file on server : Samplename.xml (equals the result.xml of the particular datafile) Both files contain the LIMSID coming from the LIMS system. The result.xml is file of interest and will be spooled to the server, the LIMSID.xml is only used to handle the LIMID information during reprocess. The result.xml file is created at the end of the sample run, the LIMSID file is created twice, once during Data Acquisition and at the end of the Data Analysis part of the method. The LIMSID.xml file created after Data Aquisition will be placed into the previous run and overwrite the correct LIMSID.xml. As long as the system is not going to reprocess that data, this problem is not visible. During reprocess, the LIMSID.xml file is read out again and the wrong LIMSID information is placed into the result file. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Run the XML sequence using Automation mode to get the result.xml and rename the result file within the datafile, if you need to reprocess the data. The data moved to the defined Weblocation will have the correct result.xml file. |
Fix Information:
|
A patch to correct this problem will be distributed. Please contact your local Agilent Administrator. This issue will be fixed within B.01.01. |
Keyword: UTILITIES
One-line Description:
XML using manual upload places result.xml file to sample info directory
Problem:
|
Following issue has been reported using the XML interface on ChemStation revision A.10.0x: During the usage of manual upload function within the Data Analysis the result.xml file is uploaded using a manual process. By uploading the result file manually, the result.xml is stored into the data directory defined in the method/run control item: sample info. Any existing result.xml file in that directory will be replaced. |
Problem Cause:
|
n/a |
Temporary Solution:
|
A patch is under investigation and will be delivered in a short time frame. Please contact your Agilent Representative. This patch will obsolute the patch delivered for PVCS 2485, delivered with Service Note: G2170AA-118 |
Fix Information:
|
n/a |
Keyword: UTILITIES
One-line Description:
Multiplier not taken when running Data Acq. only
Problem:
|
With ChemStation A.10.01 the following issue has been reported: Setting a multiplier in the sequence table and run the sequence with the option " according to run time checklist" while in the method in "Run Time Checklist" only Data Acqistion is selected will not be present in the created batch file. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Select "Data Analysis" in the Method "Run Time Checklist", and select the option "print to screen" in the Print - Specify Report menu. |
Fix Information:
|
This problem is fixed in revision B.03.01. |
Keyword: UTILITIES
One-line Description:
wrong pressure description using Japanese fonts
Problem:
|
Using english ChemStation A.10.02 and English Operating system, but changing the fonts to Japanese the values in the e.g. pressure fields will be set to a strange value. |
Problem Cause:
|
n/a |
Temporary Solution:
|
Please remove Japanese fonts, than the system will show the correct values. |
Fix Information:
|
n/a |