Software Status Bulletin

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

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

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

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

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

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

Keyword Glossary

Keyword Index

Keyword: Administration

KPR#:149835 LC instrument remains offline
KPR#:149886 EMF help information not available using the Instrument Control Framework
KPR#:149890 Do not install msi files by double-clicking the file
KPR#:217785 Installation Qualification Test fails when a newer RapidControlIF.dll is installed than has been expected by the LC Driver
KPR#:274555 Installation Qualification Test fails when A.02.19 SR2 is installed on OpenLab Chemstation Edition C.01.09
KPR#:431252 Driver release note states wrong firmware revision for G7104C
KPR#:1208692 Reauthorization Required for CDS–Assist Hub Connection after a half year

Keyword: CE Method

KPR#:149884 CE Method not working for CEC Mode and/or MSInstalled soft configuration option
KPR#:150050 Using timetable setting Internal Pressure in CE/p and CEC mode is not applied
KPR#:153012 Inconsistent labeling of G7100A - CE System
KPR#:462141 PSI pressure unit is not supported for 7100 Capillary Electrophoresis (CE)
KPR#:713054 Unload lifter" information is missing in the audit trail during cassette change
KPR#:1400354 CEC External Pressure Home Values are not cleared after changing CE Mode

Keyword: ColumnComp Driver

KPR#:149812 TCC Cluster, TCC2 shows always valve position 1
KPR#:149860 TCC CLuster remains offline with message "Initialization of ColumnCompCluster failed
KPR#:149912 Position number after run is reported wrongly for Multicolumn Thermostat G7116B in the report and audit trail
KPR#:149913 Field sizes for column description and comment have been increased from 16 to 32 characters for G7116B Multicolumn Thermostat
KPR#:149914 Method transfer from G1316A/B/C to G7116B failed if option "next position after run" was chosen
KPR#:149917 Wrong display for 2pos/10port and 2pos/6port valves in method UI for G1316A/B/C modules
KPR#:149918 No tooltip displayed if linked detector is missing for G7116B Multicolumn Thermostat
KPR#:149921 Incompatible change in behavior of 2-position/6-port and 2-position/10-port valves in G1170A, G7116B and G4227A compared to Thermostatted Column Compartments G1316A/B/C
KPR#:149925 Error dialog and error logbook entry for TCCs G1316A/B/C
KPR#:149929 Control UI for G1316C does not work when using the Instrument Control Framework ICF in client/server setups.
KPR#:149930 Changing control settings like switching on/off the Column Compartment Thermostat or Leak Detection in the instrument control UI does not work
KPR#:149943 Import/export functionality in Column Assignment dialog of MCT has been removed
KPR#:149962 No comments can be entered for virtual tags
KPR#:149976 Column information may get lost within VTCs during auto-configuration in some cases
KPR#:149977 Last injection date and injection counters are not updated in VTC in some cases
KPR#:149978 Valve-Thermostat-Cluster time table can be edited in read-only mode
KPR#:149985 Maximum column void volume is 50 mL
KPR#:149998 Auto configuration fails when changing the valve type in an MCT for an existing valve thermostat cluster
KPR#:272678 G1316C does not recognize 800 bar Quick Change Valve Heads configured in LabAdvisor
KPR#:544343 Enforce column in MCT method requires 14 characters or less
KPR#:696959 ICC column assignment unavailable in LC & CE Drivers 3.5
KPR#:736868 Run cannot be started due to the migration of MCT or VTC methods when using audit trail

Keyword: ColumnComp Driver,Pump Driver

KPR#:149832 PumpValve-Cluster & TCC-Cluster halts sequence once methods change valve position

Keyword: DAD/MWD Driver

KPR#:149811 Incomplete signal description in the online plot window
KPR#:149820 In localized CDS for ELSD detector G4218A no signal data is shown or stored
KPR#:149829 G1315A/B do not show spectral data and G1321A/B show wrong time stamps for spectra
KPR#:149830 High load on CAN may cause "Spectra runbuffer overflow" entries and a loss of spectra
KPR#:149837 Autobalace executed although in Sequence table set to "OFF"
KPR#:149851 Occasional shift in retention times for G1315A/B or G1365A/B
KPR#:149898 Lowest possible DAD wavelength is 190.5 nm
KPR#:150000 Retention times may be slightly too high for DAD data acquisition rates below 1 Hz
KPR#:458238 No spectra are collected when collection range divided by steps is non-integer

Keyword: Dashboard

KPR#:149949 Module stays offline after a configuration change using the "Modify" function
KPR#:238434 Runs not finishing intermittently due to SFC remaining in Prerun state

Keyword: ELSD Driver

KPR#:149823 ELSD G4218A can not handle change of Sample Time during run
KPR#:149825 The ELSD method cannot be called by a right-click from the context menu
KPR#:149856 Runtime of a G4218A ELSD cannot be changed during a run

Keyword: FLD Driver

KPR#:149862 FLD G1321 Scan ranges and threshold under certain conditions not available

Keyword: Globalization

KPR#:150035 Content of localized Online Help texts may not be complete (Japanese, Chinese and Portuguese version)
KPR#:150072 Flow Modulator requires regional settings in English
KPR#:475775 Brazilian Portuguese language setting causes driver UI to become irresponsive

Keyword: Globalization,Pump Driver

KPR#:149973 Pressure range settings may seem to change when using unit psi

Keyword: Performance

KPR#:150066 Analog Output and Digital Output signals of a detector do not fully match
KPR#:392755 Usage of "Next location" does not work as expected when using multiple Recovery Collectors in a cluster

Keyword: Pump Driver

KPR#:149819 Pump overpressure: impossible to turn off pump via UI
KPR#:149834 Wrong Flow setting displayed when re-opening the Method User Interface
KPR#:149836 Flow unit in Online Plot for Nano pump is incorrect.
KPR#:149838 Misrepresentation of Bottlefillings in Dashboad of PumpValveCluster
KPR#:149840 Solvent compositions during run do sometimes not sum up to 100%
KPR#:149845 PumpValveCluster with ISET - Solvent composition: resulting %A is wrong (at 1 line in timetable)
KPR#:149861 Memory leak in pump method dialog may cause performance drop
KPR#:149868 Blend Assist : Timetable not persisted properly
KPR#:149879 Unused solvents are handled differently for 1100/1200 Series/1260 Infinity vs. 1290 Infinity/Infinity II pumps
KPR#:149881 Prep-pump cluster stays not ready after restarting OL ChemStation (reconnect)
KPR#:149885 The 1290 Quaternary Pump G4204A is specified for a maximum flow rate of 5 ml/min
KPR#:149895 Purge function has been improved for Preparative Pump Clusters
KPR#:149909 Solvent type may change during a method transfer from 1290 Infinity/II Quaternary Pumps G4204A or G7104A to 1290 Infinity/II Binary Pumps G4220A/B or G7120A
KPR#:149928 Recorded Acquisition Method has Incorrect Pump Parameters
KPR#:149938 Implementation of seal wash behavior has been improved for G4220A/B and G4204A
KPR#:149950 Warning "No matching ISET solvent combination" for G4220A/B pump as emulated pump
KPR#:149951 Using the OpenLAB CDS EZChrom edition feature "Extend run" will disable ISET features in the 1290 pumps
KPR#:149986 Seal wash for Preparative Pump G1361A or Preparative Pump Cluster is displayed as "off" even when it's on
KPR#:149989 Wrong purge flow and duration shown in prepare pump dialog depending on regional settings
KPR#:149992 Shutdown recovery does not work for Preparative Pump Clusters in a Multi-Controller environment
KPR#:236386 Unexpected shutdown of Chromatographic Data System when executing a pump purge

Keyword: Pump Method

KPR#:529859 2DLC peak-based high resolution cut can be longer than expected

Keyword: Pump Status

KPR#:537392 Client/server environment: Pump status information not visible in LC Dashboard

Keyword: Reports

KPR#:149972 Columns are not reported correctly when switching valves
KPR#:150046 Not acquired signal A (VWD) leads to a "Manual Control" entry in the Result Set Audit Trail
KPR#:165636 FCC: When switching Fraction Collectors during a run in an asymmetrical setup, unexpected fractions might be collected and reported
KPR#:299468 "Delete" entry in the audit trail raises an audit concern
KPR#:729964 Firmware of hosted modules cannot be reported

Keyword: Sampler Configuration

KPR#:444022 Issues when re-configuring capillaries in Dual Loop and High Performance Autosamplers
KPR#:511237 Performing auto-configuration, the LC Driver does not write the thermostat/cooler information into the configuration. Once the hosting CDS connects to the instrument, the driver detects the thermostat/cooler and requests an configuration update

Keyword: Sampler Driver

KPR#:149808 Injection valve cleaning, entering new values does not work
KPR#:149815 Injection Volume not shown when loading a method (Inactive)
KPR#:149821 Control of Tray illumination missing for G1329B & G4303A
KPR#:149822 Parameter mismatch for custom-defined Well Plates
KPR#:149824 Control of Tray illumination missing for new G1329A
KPR#:149826 Control of tray illumination missing for G1329A/B & G4303A in Japanese and Chinese ChemStation
KPR#:149827 Larger injection volume with 90 ul head may be incorrectly displayed after injection
KPR#:149831 LC driver starts run with ALS Chiller turned off
KPR#:149841 ICF A.01.04 - No method download, if method contains pretreatment/injector program steps.
KPR#:149843 Injection specific injection volumes may get propagated to following injections
KPR#:149844 Dua Loop Sampler: ACQ method shows wrong loop with overlap injection
KPR#:149847 Bouncing menu
KPR#:149850 Wrong Inj Volume with German settings
KPR#:149852 the "edit Wellplate type" could not work in OpenLab ChemStation Edition Japanese .
KPR#:149855 Wrong Injection Volume using overlapped injection and setting InjVol in sequence table
KPR#:149863 Carry over with dual Loop Sampler: Injection cleaning: Rinse volume not set in Firmware
KPR#:149880 For overlapped injections in vial samplers G1313A and G1329A/B, injection volumes and sample locations are not updated synchronously in the status UI
KPR#:149940 In OpenLAB CDS ChemStation Edition C.01.07 and below, vial positions larger than 50 are not allowed for Vialsamplers G7129A/B
KPR#:149941 Description in user interface has been improved for Smart Overlap and Overlapped injections
KPR#:149948 How to handle configuration changes in EZChrom and OpenLAB 2.0
KPR#:149954 Older versions of ChemStation cannot handle trays in Vialsamplers G7129A/B with cartesian coordinates
KPR#:149990 G1329A Autosampler tray types are not updated in Thermo Chromeleon
KPR#:149999 Sampling diagram has been removed for Infinity II samplers
KPR#:150004 Do not use instructions Inject, Valve and Remote in injector programs in case of overlapped injections
KPR#:150005 Do not change injection method parameters during overlapped injection
KPR#:150009 Under special circumstances, wrong injection volumes may be reported for ChemStation sequences of overlapped injections by the Multisampler
KPR#:150014 When a method specifies a wash position, that is physically not available, the method will not be sent to the instrument
KPR#:350975 Sampler goes offline in rare cases during run
KPR#:540996 Power cycling a fraction collector in a fraction collector cluster could lead to an offline cluster
KPR#:642470 Too long sample names cause run to be aborted
KPR#:774879 Thermostat temperature control mode improvements

Keyword: Sampler Method

KPR#:187313 Method download fails when cooler is controlled in method
KPR#:564878 Changes made to the temperature mode in context menu for the G3167A have no effect

Keyword: User Interface

KPR#:149911 Time table graph of UV Detector ends before run time of system
KPR#:641732 G3162A user interface displays incorrect frequency values for peakwidth

Keyword: 

One-line Description:

Installing a lamp with tag may invalidate "alway use lamp" setting in detector's control

Problem:

Installing a lamp with tag may invalidate the detector's control setting "always use lamp" and silently modify it to "use lamp only if lamp tag is available".

Temporary Solution:

Check detector's Control setting after installing a new lamp.

Fix Information:

Fixed in A.02.04

Keyword: 

One-line Description:

Flexible Cube G4227A does not work with HiP ALS G1367E

Problem:

On Chinese or Japanese CDS only the 1290 Infinity Flexible Cube G4227A does not work with High Performance Autosampler G1367E. 
On English CDS the operation of 1290 Infinity Flexible Cube G4227A with High Performance Autosampler G1367E is not affected.

Temporary Solution:

n/a

Fix Information:

Resolved in revision A.02.02

Keyword: 

One-line Description:

Lamps and cells of G1314F show incorrect dates in the RFID tags

Problem:

Lamps and cells of G1314F show incorrect dates in the RFID tags

Temporary Solution:

n/a

Fix Information:

Fixed with the driver version A.02.06

Keyword: 

One-line Description:

Cannot Check "Pump and solvent selection valve installed" Box for Flex Cube if Once Clear it

Problem:

LC Driver version: A.02.06 [363] (Test application/Install on Japanese ChemStation)
1. Open Instrument configuration dialog
2. Select Flexible Cube
3. Open Flexible Cube Configuration dialog
4. Clear the "Pump and Solvent selection valve installed" check box, then press OK
5. Re-open Flexible Cube Configuration dialog
6. Thick that check box and press OK
7. Open Flexible Cube Configuration dialog again -> check mark is gone

Temporary Solution:

Workaround: use autoconfig to set up the FlexCube

Fix Information:

Fix in the next rev RC.Net A.02.07.

Keyword: 

One-line Description:

AFC & UIB II: AFC does not fractioning as expected

Problem:

System configuration:
1 DAD
1 UIB II
2 AFCs -> 1 AFC Cluster
Analog out of DAD connected to Analog In of UIB II
Simulated signal of DAD was used
Method settings for modules (expect threshold for UIB II signal): see attached method
1. Created a data file with the simulated signal recorded by the UIB II
2. Loaded data file into Fraction Preview
3. Used Fraction Preview to collect peakbased fractions with threshold > 0.12 V
4. The value 0.12 V is written into the table on the left side without conversion (the table shows mV as unit)
Using this method will cause that the AFC will fractioning all the time.
Cause:
The firmware interface expects the threshold in mV but the driver writes 0.12 (V) to the AFC
This causes that the AFC is fractioning all the time.

Temporary Solution:

n/a

Fix Information:

Fixed in UIB II signal is delivered as mV signal similar to  UIB I since LC Driver Release A.02.07.

Keyword: 

One-line Description:

Use Vial as Fraction collections

Problem:

Started a run with fraction collection.
The fraction collector config does not show 10 vials but only trays.

Temporary Solution:

If you have installed a 2 WP-Tray, vials are allways forbidden to use for fractionation, regardless if there are wellplates inserted or not.

Fix Information:

Issue fixed with LC and CE Driver revision A.02.07

Keyword: 

One-line Description:

Recovery volume and fraction volume: behaviour for reset volume

Problem:

I worked with one AFC.
Configured 2 wps +10 vials and 15 vial tray for recovery.
Started multiple runs. 
For each run a new Recovery location was used.
Then removed the recovery tray and entered it again.
Next run started with first recovery location --> this was already used.

Temporary Solution:

If you want to reset the Funnel Trays only, use "Reset Funnel Tray Volume"
If you want to reset Wellplates and vials (all except funnels), use "Reset Fraction Volume"

Fix Information:

Issue fixed with the LC and CE driver revision A.02.07

Keyword: 

One-line Description:

Wrong datarate for Vwd Aux signals for 'Board Temperature' and 'Optical Unit Temperature'

Problem:

Wrong lookup values in VwdDeviceCapabilities.xml.

Temporary Solution:

n/a

Fix Information:

OpenLAB CDS ChemStation Edition - SP2 for LC RC.Net Driver A.02.05 and A.02.06

Keyword: 

One-line Description:

Fraction collector stop times do not end runs

Problem:

For previous firmware revisions, fraction collectors could be stop time masters same as pumps and injectors. If a stop time is set for a stop time master, this will end the run after the time set. In case of multiple possible stop time masters, the shortest time will apply. Other modules can refer to the stop time master (option as pump/injector) or set their own stop times. For other modules, the stop time will not end the run but the module activity, e.g. if the detector has a shorter stop time than the pump, signal acquisition will end before the run.
Since firmware A.06.54, fraction collectors can no longer be stop time masters, i.e. their stop times will no longer end a run.

Temporary Solution:

If a stop time is set for the fraction collector, this change may cause a changed method behavior. If a run stop time is needed, please set it for the pump or injector.

Fix Information:

n/a

Keyword: 

One-line Description:

SFC remains in "Ready" (Idle) state while pump is in Error.

Problem:

Have set up a long sequence (600 injections). 
Pump run out of solvent in channel B und stopped with Error as it was defined in "Bottle fillings" UI. SFC remained in "Ready" (Idle) state. 
Should go to "Standby". 
System was in "SFC mode".

Temporary Solution:

Workaround could be to not use bottle fillings with SFC

Fix Information:

Solved with LC & CE Drivers A.02.08 SP1

Keyword: 

One-line Description:

Turning off the SFC device G4301A while connected to an online OL ChemStation will lead to an application crash

Problem:

If you turn off your SFC device while the OL ChemStation is connected to this instrument this will crash this application.

Temporary Solution:

Close the OL ChemStation before switching off the SFC module.

Fix Information:

n/a

Keyword: 

One-line Description:

Plate type changes are not reported in the config audit trail for fraction collectors G1364x/G5664A

Problem:

Plate type changes are not reported in the config audit trail for fraction collectors G1364x/G5664A

Temporary Solution:

Add manual entry to audit trail to track changes

Fix Information:

n/a

Keyword: 

One-line Description:

Changing the backpressure method parameter of the SFC pump during a run does not work properly

Problem:

If you try to change the back pressure of the SFC pump during a run, this change will be applied correctly to the module, i.e. the instrument control changes as requested. However the method parameter will not be updated correctly and if the method is saved, the original setting will be used.

Temporary Solution:

Change the method parameter outside a run.

Fix Information:

Since driver version A.02.16 backpressure can no longer be changed during a run.

Keyword: 

One-line Description:

Analytical SFC System (G4301A) delivers still CO2 even if the SFC binary pump has flow 0

Problem:

The 1260 Infinity Analytical SFC System (G4301A) still delivers CO2 even if the SFC binary pump has flow 0.

Temporary Solution:

n/a

Fix Information:

Upgrade to the most recent firmware version (minimum A.03.09) of the 1260 Infinity Analytical SFC System.

Keyword: 

One-line Description:

Driver does not start the run / CS stays in Run in Progress / Data Acquisition

Problem:

The ChemStation has prepared the run as expected but the driver didn't start the run from CS / User perspective.
It can be reproduced by opening the door of the sampler after the run preparation was done (need some tries to have the correct timing)

Temporary Solution:

Solved with LC & CE Drivers A.02.09

Fix Information:

n/a

Keyword: 

One-line Description:

Fraction start location in a sequence parameter cannot accept the number "1" when using 2P+10Funnel tray at RC.net driver.

Problem:

The customers want to use 10 Funnels at the tray 2P+10Funnel without plates.

Temporary Solution:

Solved with LC & CE Drivers A.02.09

Fix Information:

N/A

Keyword: 

One-line Description:

Analytical SFC System (G4301A) looses method settings when the module is powered off and on again while the application is connected

Problem:

The Analytical SFC System (G4301A) looses method settings when the module is powered off and on again while the application is connected. This may lead to a changed method depending on the used CDS.

Temporary Solution:

Do not turn off the Analytical SFC System (G4301A) while connected to a CDS.

Fix Information:

No fix available

Keyword: 

One-line Description:

Data acquisition rate changes when importing old methods to new detectors

Problem:

The definition of data acquisition rates/peak widths changed between detector types. This is because the data rate is saved as an index number (0 = 20 Hz, 1 = 40 Hz, ...) rather than the actual data acquisition rate and the index definition was changed.
DADs G1315A, B and D use the same indexing scheme. DADs G1315C, G4212A/B use a different indexing scheme.
MWDs G1365A, B and D use the same indexing scheme. MWD G1365C uses a different indexing scheme.
VWDs use several different indexing schemes.

Temporary Solution:

n/a

Fix Information:

Verify data acquisition rates/peak width settings when migrating to a different detector type.

Keyword: 

One-line Description:

HDR Cluster does not allow using additional detectors

Problem:

Using several detectors creates a large amount of data, which is communicated at the same time. In a HDR cluster setup, spectral data is communicated via LAN but single wavelength data is communicated via the internal CAN bus.
If detectors are used in addition to the HDR cluster, the very high data volume may impair data integrity, e.g missing data points.

Temporary Solution:

n/a

Fix Information:

Do not connect additional detectors to HDR clusters via CAN.

Keyword: 

One-line Description:

Incorrect lamp type settings for VWDs

Problem:

The G1314A/B/C VWDs allow the use of either VWD or DAD lamps, which can be configured in the module driver. In driver revisions A.02.09 and below the selection of DAD or VWD lamp is reversed.
The different lamps use a different lamp ignition process. The DAD filament heating is turned off after ignition while the VWD lamp filament heating is kept on a lower level.
RC.NET LC Driver (<= A.02.09)      CLASSIC driver
G1314A/B/C     REVERSED                                 OK
G1314D/E/F     OK                                               OK

Temporary Solution:

In case of noise and ignition issues please verify the setting. In ChemStation or LabAdvisor, you may use the command line command to check the actual setting in the VWD.
ChemStation: print sendmodule$(lvwd,"ltyp?")
LabAdvisor: send ltyp? to VWD module
Following instrument answers are possible:
0 = DAD lamp
1 = VWD lamp

Fix Information:

This issue has been fixed in LC Driver version A.02.10. If the correct setting has been used before (i.e. VWD lamp present and VWD setting has been chosen), the behavior will now be correct and has previously been wrong.
If a wrong setting has been used before (i.e. VWD lamp is present and DAD setting has been chosen) as a workaround, the behavior will then be wrong for A.02.10 and following and needs to be changed.

Keyword: 

One-line Description:

Tube heights and volumes are overwritten for inserted tube trays for G1364A/B/C/D, G5664A fraction collectors and their clusters

Problem:

Module firmware and driver store settings for tube heights and volumes for each tube tray type. If tray of any type is replaced by a tube tray, settings for this tube tray may be overwritten by a previous tray setting. These new and potentially wrong settings are stored in firmware and driver.

Temporary Solution:

After inserting a new tube tray, please verify settings for height and volume in the fraction collector configuration and correct them if needed.

Fix Information:

This has been fixed with driver release A.02.11 SP1. Additionally, height and volume settings need to be verified for each fraction collector and tube tray type.

Keyword: 

One-line Description:

HDR stays offline if one DAD of the HDR cluster has been switched off and on again

Problem:

HDR stays offline if one DAD of the HDR cluster has been switched off and on again

Temporary Solution:

Restart the CDS after switching on both HDR modules

Fix Information:

n/a

Keyword: 

One-line Description:

Status display for wavelengths and absorption values are not updated in dual wavelength mode for the VWD G7114B.

Problem:

For the dual wavelength mode of the VWD G7114B, both set wavelengths and measured absorptions are not updated in the extended status UI after switching between single and dual wavelength mode.

Temporary Solution:

not available

Fix Information:

Fixed with driver release A.02.11 SP1.

Keyword: 

One-line Description:

1290 Infinity II VWD G7114B shows only "Signal" instead of "Signal A"

Problem:

When using the dual-wavelength mode for the 1290 Infinity II VWD G7114B, the user interface for instrument curves shows signal A as "Signal without reference" and "Reference only"  for the reference wavelength of signal A. Signal B is shown correctly as "Signal B without reference" respectively "Reference B only"  for the reference wavelength signal.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Method screens may not be displayed correctly if the Windows text size is increased

Problem:

Windows allows adjusting the text size. If this size is increased beyond 100%, the display may distorted and become partially invisible or inaccessible.

Temporary Solution:

Please use the default Windows text size.

Fix Information:

n/a

Keyword: 

One-line Description:

Resetting tray volumes does not reset the fraction start location

Problem:

Resetting tray volumes does not automatically reset the fraction start location unless a dedicated start location is set. The fraction collector will continue from its current location.

Temporary Solution:

Set a fraction start location.

Fix Information:

Will be fixed in G1364A/B/C firmware A.07.01

Keyword: 

One-line Description:

Changed stoptime behavior for G1364x devices

Problem:

Due to different FW implementation (introduced with FW A.06.54 or later) of the stop time behavior, it can happen that, in case of defining the stop time ONLY in the fraction collector method, a run will not stop after the specified time.

Temporary Solution:

Define the stoptime in addition in the method of another device e.g. the pump or the sampler.

Fix Information:

n/a

Keyword: 

One-line Description:

ChemStation runs may not finish for SFC systems which are not operated in SFC mode

Problem:

In SFC systems, the SFC mode may be disabled for running a pump in normal HPLC mode (SFC off in instrument control). Such runs may not finish correctly

Temporary Solution:

Abort the run if the run has finished (by time).

Fix Information:

n/a

Keyword: 

One-line Description:

Pump pressure is limited by lowest pressure of a valve in a valve thermostat cluster

Problem:

If a valve thermostat  cluster is configured using one or multiple valves, the valve with the lowest possible maximum pressure determines the maximum pressure of the entire cluster, e.g. a 2-pos/6-port valve with 1300 bar is used for switching between to multicolumn thermostats with column selector valves of 600 bar and 800 bar. Then 600 bar would be the maximum pressure for that cluster and would limit the pump pressure accordingly.
In case of two 8-pos/9-port valves using topology 5 (V-C-V), one valve is before the column in the high pressure flow path and the other one after the column in the low pressure flow path. In that case, the valve in the low pressure flow path should not limit the pump pressure but it does.
In all other topologies, all valves are as well in the high pressure as low pressure flow path.

Temporary Solution:

n/a

Fix Information:

This has been fixed with driver version A.02.16.

Keyword: 

One-line Description:

Changing multiple trigger settings for Infinity II Fraction Collectors at the same time did not work properly

Problem:

When loading a method from the instrument, trigger settings with the same time are discarded.

Temporary Solution:

Avoid duplicate times for trigger settings in the method.

Fix Information:

This has been fixed with driver version A.02.16.

Keyword: 

One-line Description:

Unexpected run may start if the Analytical SFC System (G4301A) is switched on

Problem:

Unexpected run may start if the 1260 Infinity Analytical SFC System (G4301A) is switched on and the LC modules of the system connected via APG remote cable may also start the run.

Temporary Solution:

Ensure that the Analytical SFC System is the first module that is switched on in the entire system.

Fix Information:

Not available

Keyword: 

One-line Description:

The delay calibration does not work for the G1364A with preparative setup in ChemStation CDS

Problem:

The delay calibration does not work for the G1364A Automatic Fraction Collector with preparative setup in ChemStation CDS. The proposed steps for delay calibration are not provided. This results in a failure of the calibration process.

Temporary Solution:

Agilent Lab Advisor Software can be used for a delay calibration of the G1364A with preparative setup.

Fix Information:

This issue has been fixed in LC driver version A.02.17.

Keyword: 

One-line Description:

Pressure Limit Cluster is set to auto for any valve that is not used as switching valve in the VTC

Problem:

For any valve, which is not used as switching valve in the VTC, the pressure limit cluster is set to "auto", which is also displayed in the Control UI.
This means, that the valves, which are not used in the VTC determine nevertheless the pressure limits for all pumps because of the "auto" setting.

Temporary Solution:

Make sure to configure all connected valves either in a Cluster or as stand alone device.

Fix Information:

n/a

Keyword: 

One-line Description:

Tubing Kit cannot be modified from Dashboard for new Fraction Collectors

Problem:

The LC dashboard provides a Modify-dialog called "Needle and Tubing". It is not possible to modify the tubing kit of the G1364E/F or G5664B Fraction Collectors using this function.

Temporary Solution:

Modify the Tubing Kit with the ChemStation command line instead. 
The commands are as follows:
For a single fraction collector:
print sendmodule$(AFC,"AFC:CAPILLARYKIT 'G1364-68723' "), replace G1364-68723 with the desired Tubing Kit part number.
For G1364E/F and G5664B clustered:
print sendmodule$(AFC,"G1364E:AR42351409@AFC:CAPILLARYKIT 'G1364-68723' "), replace G1364E:AR42351409 with <Type>:<SerialNumber> of the Fraction Collector in a cluster for which the tubing kit should be set and G1364-68723 with the desired Tubing Kit part number.

Fix Information:

The behaviour will be changed with LC driver version A.02.18 so that the Tubing Kit can be set in the LC dashboard "Modify... Needle and Tubing" dialog.

Keyword: 

One-line Description:

Overfill Behavior unclear

Problem:

The Fraction Collectors (G7159B, G1364E/F, G5664B and G7166A) provide  a setting for "Overfill Behavior" with which it is possible to specify the action to be taken if the fill volume of a location reaches the max. fill volume per location. This can lead to samples / fractions being switched to waste. In case of using pooling the behavior is unclear to the user.

Temporary Solution:

N/A

Fix Information:

With driver version A.02.19 the parameter "Overfill Behavior" is removed, in order to prevent a loss of sample / fractions and to make the behavior more clear. The LC drivers now imply the following behavior: 
When Pooling: in case the fill volume of a location reaches the maximum fill volume, the run or sequence is stopped with an error.
When not Pooling: in case the fill volume of a location reaches the maximum fill volume, the collection switches to the next available location.

Keyword: 

One-line Description:

Fraction Collector Cluster: Vial 1-10 and right tray can now be used for fraction collection - consider behavior when working with "Next Location"

Problem:

With LC and CE driver A.02.18 and a Fraction Collection Cluster with 2 well plates + 10 Vials (or 2 well plates + 10 collecting funnels) configuration, the positions Vial 1-10 and the ones on the right tray can now also be used for fraction collection (in addition to P1 and P2 on the left tray).
Please consider that when working with "Next Location" as Fraction Start Location, locations may be used for fractioning, that were ignored with previous driver versions (Vial 1-10 and the right tray). In order to prevent that these locations are used for fractioning, specify Vial 1-10 and Vial 201-240 in the Collection Settings as "Forbidden Location" for all fraction collectors in the cluster. 
The modules affected are: G1364A/B/C and G5664A.

Temporary Solution:

N/A

Fix Information:

In order to prevent that locations that were previously ignored are now used for fractioning, specify Vial 1-10 and Vial 201-240 in the Collection Settings as "Forbidden Location" for all fraction collectors in the cluster.

Keyword: 

One-line Description:

Start location for fraction collection is reset when removing a tray and closing the fraction collector front door

Problem:

Start location for fraction collection is reset when removing a tray and closing the fraction collector front door. This behavior may not be wanted, if the same tray is inserted afterwards.

Temporary Solution:

If the same tray shall be inserted again, do not close the front door in order to retain the fraction collection start location.

Fix Information:

n/a

Keyword: 

One-line Description:

Fraction Collector Method Timetable must be empty in order to perform a delay volume calibration

Problem:

In order to perform a delay volume calibration with the Fraction Collectors G1364A/B/C it must be made sure that the timetable within the Fraction Collector Method is empty.
If this is not the case, the Fraction Collector will execute the timetable and collect fractions. 
Affected modules are the Agilent Fraction Collectors G1364A/B/C. Newer modules are not affected.

Temporary Solution:

n/a

Fix Information:

Make sure that the timetable in the Fraction Collector method is empty in order to perform a delay volume calibration.

Keyword: 

One-line Description:

Threshold limits not sufficient for Refractive Index Detectors in Fraction Collector II modules

Problem:

When using a Fraction Collector II module in combination with a Refractive Index Detector as peak trigger, the allowed limits for detector signal threshold are too narrow to allow for adequate peak triggering.

Temporary Solution:

None available

Fix Information:

Limits have been adapted with release of LC & CE Drivers 3.1

Keyword: 

One-line Description:

Use of injection pressure in a timetable is not allowed when external pressure is enabled

Problem:

The 7100 CE can apply pressure to the capillary using two different pressure sources: an internal pressure source and an external pressure source.
Because using internal and external pressure simultaneously could create conflicts, the system was designed to prevent internal pressure use in CEC or CE+P modes when external pressure is enabled.
When external pressure is enabled, a method can still contain an internal pressure command in the timetable, but the internal pressure does not change or get applied.

Temporary Solution:

n/a

Fix Information:

Resolution:
A new method parameter, "Enable Internal Pressure in Timetable", has been introduced in the Home Values section (CEP and CEC mode only) starting with LC&CE Driver revision 3.12. This feature also requires G7100A firmware B.07.46 or newer. 
This allows internal pressure to be applied during an analysis whenever it is specified in the timetable (CE+P or CEC mode), or through the Home Values settings (CEC mode only).
Important Restriction
Internal pressure and external pressure cannot be applied at the same time. 
Therefore, users must not configure CEC Home Values with external pressure while also using internal pressure commands in the timetable within the same method.
Backward Compatibility
If "Enable Internal Pressure in Timetable" remains unchecked, the system behaves exactly as before. Existing methods continue to run unchanged, ensuring full backward compatibility.

Keyword: 

One-line Description:

Purification - When the same recovery start location is used multiple times in a sequence, the instruments uses "Next Location" instead

Problem:

When a sequence is set up with the same absolute Recovery Start Location value in multiple sequence lines, then the instrument ignores these absolute settings and instead uses the next empty recovery location for each run. This is done to protect existing recovery locations from used multiple times accidentally.

Temporary Solution:

None, works as designed currently.

Fix Information:

None. Works as designed currently. A logbook entry has been created to show that a specified Recovery Start Location has been skipped by the instrument. 
An additional behavioral change to enhance usability will be implemented in a future revision.

Keyword: 

One-line Description:

Purification - G1364A-C - Using the Fraction or Recovery Start Location "Next Plate" in the first line of a sequence leads a sequence abort before injection

Problem:

When a sequence is created that has the Fraction Start Location or Recovery Start location value "Next Plate" and all fill volumes of the Purification instrument have been reset right before executing that sequence line, then the sequence execution will abort. No loss of sample is to be expected.

Temporary Solution:

Do not use the Fraction Start or Recovery Start Location value "Next Plate" in a sequence line.

Fix Information:

The issue has been fixed.

Keyword: 

One-line Description:

Purification - Specific Recovery Start Locations are currently ignored by the instrument when using OpenLab CDS Chemstation Ed. C.01.10 Update 1

Problem:

When using LC Drivers within Chemstation C.01.10 Update 1, specific Recovery Start Locations are ignored by the instrument. The driver instead defaults to "Next Location" and proceeds to the next free position.

Temporary Solution:

Either do not upgrade to OpenLab CDS ChemStation Ed. C.01.10 Update 1 or do not use specific Recovery Start Locations for the time being when upgrading to LC Drivers 3.1 at the same time. 
If your workflows do require OpenLab CDS ChemStation Ed. C.01.10 Update 1, then a workaround is to use Update 1 with LC Drivers 3.0 instead.

Fix Information:

None currently. Will be fixed in a future release of OpenLab CDS ChemStation Edition.

Keyword: 

One-line Description:

"Injection aborted" information may not be recorded in its injection audit trail due to unstable network

Problem:

Sequence or single sample analysis will be interrupted hence aborted when running an Agilent LC due to unstable/flaky network. However, in some cases, the reason why the injection was aborted may not be recorded in its injection audit trail due to the timing issue.

Temporary Solution:

Ensure a stable network

Fix Information:

The issue has been fixed.

Keyword: 

One-line Description:

Instrument goes offline when multiple data systems are connected

Problem:

When more than one data system is connected to the same instrument it can go offline.

Temporary Solution:

Disconnecting from all data systems and starting just one solves the issue.

Fix Information:

n/a

Keyword: 

One-line Description:

Purification in OpenLab CDS 2.5 - Error when using legacy Fraction Collector Cluster with added Recovery collector

Problem:

When using OpenLab CDS 2.5 together with the legacy Fraction Collector Cluster (supporting G1364A/B/C and G5664A), an error can occur during sequence setup. The error is caused by using the graphical "Sample Trays" UI when one of the collectors in the cluster is used as Recovery collector.

Temporary Solution:

As a temporary workaround, users are asked to not use the graphical "Sample Trays" UI when setting up sequences for the Legacy Fraction Collector Cluster.

Fix Information:

There is no fix for this issue at the moment.

Keyword: 

One-line Description:

Peak based fraction collection does not work

Problem:

If a pump time table starts with 0 flow and peak based fraction collection starts with RT=0 no fractions are collected.

Temporary Solution:

Either start the peak based faction collection with RT>0 or start the pump time table with a flow > 0

Fix Information:

n/a

Keyword: 

One-line Description:

Fraction Collector Cluster goes offline with error "Remote partner missing" during initialization

Problem:

In some rare situations a fraction collector cluster can go offline during initialization of the modules with the error "Remote partner missing".

Temporary Solution:

Power cycling the associated peak detector solves the problem.

Fix Information:

No fix planned.

Keyword: 

One-line Description:

Missing edit wellplate types from context menu for all multisamplers, HiP and open bed samplers

Problem:

The context menu option called "Edit Wellplate Types" of multi-, HiP and open bed samplers is not supported in some data systems.

Temporary Solution:

It is possible to edit the wellplate types in the configuration UI under "Define Wellplates"

Fix Information:

n/a

Keyword: 

One-line Description:

Using ranges for reserved/forbidden locations not possible

Problem:

Using FC G1364E  and 215 tube tray (G1364-84536) the customer wants to use reserved/forbidden location. It is not possible to enter a range.

Temporary Solution:

Specify the locations explicitly

Fix Information:

n/a

Keyword: 

One-line Description:

Unsigned installer for LC & CE Drivers 3.4

Problem:

The LC & CE Drivers installer for OpenLAB CDS, Chemstation and Masshunter 3.4 was not digitally signed and therefore a warning message from Windows Defender might be shown during the installation.

Temporary Solution:

n/a

Fix Information:

The issue will be fixed with the release of LC & CE Drivers 3.5.

Keyword: 

One-line Description:

The instrument may show ‘Not Ready’ when the capillary is replaced.

Problem:

G7167B dual needle: Instrument might be "Not Ready" when capillary is changed

Temporary Solution:

Download the resolved method or open method in instrument status UI and set needle selection to right or left needle.

Fix Information:

n/a

Keyword: 

One-line Description:

Pretreatment Valve function reverts to default "Bypass" when switching UI

Problem:

The parameter of the pretreatment Valve function will always revert to its default value of "Bypass" as soon as the user switches method interfaces.
Contrary to the value shown in the user interface the method script shows the parameter as set to "Mainpass".

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Sequence aborts when Channel A is not assigned in Level Sensing

Problem:

Started a Sequence with a method that includes a timetable entry, changing pump flow, or composition.
If Channel A is not assigned in the Level Sensing Assignment, the run aborts due to an exception.

Temporary Solution:

Assign Channel A in the Level Sensing Assignment to avoid the exception.

Fix Information:

Issue fixed with the LC and CE driver revision 3.10

Keyword: 

One-line Description:

Blend Assist fails when using LC Driver 3.9 or 3.10

Problem:

When running a sequence that uses a method with Blend Assist enabled, the sequence is aborted. The following error message is shown: “Sequence contains no matching element.”

Temporary Solution:

The user is recommened to downgrade the Driver version to 3.8

Fix Information:

n/a

Keyword: 

One-line Description:

Sequence aborts due to wrong call order.

Problem:

The reported “Wrong Call Order Exception” was observed occasionally during runs and sequence execution when LC Driver versions 3.9 or 3.10. The issue is related to a specific interaction between OpenLab CDS and the LC driver.

Temporary Solution:

There is no workaround; upgrading to LC Driver 3.11 is required.

Fix Information:

LC Driver 3.11

Keyword: 

One-line Description:

LC driver online help not accessible from instrument configuration UI

Problem:

The LC driver online help does not open when accessed by pressing the F1 key during instrument configuration.

Temporary Solution:

The help can be accessed by opening the LC driver help via the status dashboard in the Chromeleon console.

Fix Information:

n/a

Keyword: Administration

One-line Description:

LC instrument remains offline

Problem:

If during initialization of communication between RC.Net LC Drivers in ChemStation and the connected LC module a communication problem appeared, the LC driver might not be able to recover from any further communciation problems during initialization. Instead the instrument in ChemStation would (falsely) remain offline.

Temporary Solution:

If the network connction between ChemStation and LC is stable and operational, either a reboot of the ChemStation or of the connected LC module is able to resolve the problem arising from consecutive communication errors locking out the instrument into offline.

Fix Information:

n/a

Keyword: Administration

One-line Description:

EMF help information not available using the Instrument Control Framework

Problem:

Currently the EMF help information not available using the Instrument Control Framework

Temporary Solution:

The EMF (Early Maintenance Feedback) can only be used in conjunction with Agilent Lab Advisor.
Within ICF, the EMF (Early Maintenance Feedback) status of the module is displayed by its EMF-specific color-coding. The tooltip gives further information about the EMF status.  To modify EMF limits or clear EMF values, use the Agilent Lab Advisor.

Fix Information:

n/a

Keyword: Administration

One-line Description:

Do not install msi files by double-clicking the file

Problem:

Drivers and add-on software products are provided in .msi files (Microsoft Windows Installer). Double-clicking such files seems to create a valid installation. While the software may work correctly, this may create problems:
• the OpenLAB Additional Software and Drivers Deployment Wizard does not register and list this software product. This information is needed for getting support from Agilent Technologies
• uninstallation of the software may fail
• upgrade of the software may fail

Temporary Solution:

Do not use a double-click for installation. Use instead the OpenLAB Additional Software and Drivers Deployment Wizard, which can be started by going to Windows Start > Agilent Technologies > OpenLAB > OpenLAB Additional Software and Drivers. Follow steps described in the Wizard for installation or software upgrades.
If a software cannot be upgraded or uninstalled because of an invalid installation, it may help to install the software again using the procedure recommended here. Then uninstall the software using the wizard and try an upgrade again.

Fix Information:

Since LC and CE driver version A.02.18 a warning message appears which says that manual installs are not supported and the installation aborts.
This only affects OpenLab CDS ChemStation Edition and OpenLab CDS EZChrom Edition. With OpenLab 2.x manual installations are supported.

Keyword: Administration

One-line Description:

Installation Qualification Test fails when a newer RapidControlIF.dll is installed than has been expected by the LC Driver

Problem:

Due to a mismatch within the Installation Qualification Test (IQT) setup of the LC Driver Installation Package, IQT may fail, if the A.02.19SR2 LC Driver package is installed.
The issue occurs, when a previous installation of either the data system or another software package has installed the shared component "RapidControlIF.dll" with a more recent file version than expected by the LC Driver (Expected file version is 3.1.1.0).
IMPORTANT: This issue does not affect proper function of the LC driver. It is an issue within the logic of the IQT files as it is being processed after the installation of an LC Driver package.

Temporary Solution:

n/a

Fix Information:

This IQT issue can not be fixed for LC Driver versions below A.02.19 SR3, if it already has occurred once. That is, if IQT has failed once for the reasons mentioned in the description.
The issue can be PREVENTED, by directly installing A.02.19 SR3 onto a fresh installation of Chemstation C.01.09.

Keyword: Administration

One-line Description:

Installation Qualification Test fails when A.02.19 SR2 is installed on OpenLab Chemstation Edition C.01.09

Problem:

When trying to update the LC Drivers on an existing installation of OpenLab Chemstation Edition C01.09, Installation Qualification Test (IQT) fails with an unexpected file version of a RapidControl component.

Temporary Solution:

None available.

Fix Information:

n/a

Keyword: Administration

One-line Description:

Driver release note states wrong firmware revision for G7104C

Problem:

The LC and CE Driver release note wrongly mentions "D.07.20" as the minimum required firmware revision. The correct minimum required firmware revision is "B.07.20".
The issue is not impairing correct function or firmware installation on G7104C. It is a documentation-only issue and will be fixed in a later release of the LC&CE Drivers.

Temporary Solution:

Should you require evidence for the correct firmware revision of G7104C for documentation purposes in the meantime, please consider adding a copy or reference for this bulletin entry to your documentation.

Fix Information:

The issue has been fixed.

Keyword: Administration

One-line Description:

Reauthorization Required for CDS–Assist Hub Connection after a half year

Problem:

The connection between the CDS and the Assist Hub require reauthorization. If your initial connection was established more than six months ago, you will be prompted to accept the connection again on the AssistHub. This is necessary because the original access token was not refreshed as expected and has since expired.

Temporary Solution:

n/a

Fix Information:

Issue fixed with the LC and CE driver revision 3.10

Keyword: CE Method

One-line Description:

CE Method not working for CEC Mode and/or MSInstalled soft configuration option

Problem:

The pressure settings are not shown and therefore not working in the CEC Mode and/or MSInstalled soft configuration options. Vialtable implementation is not reliable.

Temporary Solution:

none

Fix Information:

Fixed in driver A.02.09 SP1

Keyword: CE Method

One-line Description:

Using timetable setting Internal Pressure in CE/p and CEC mode is not applied

Problem:

In CE/p and CEC mode, the method timetable offers the possibility to set internal and external pressure values. This function cannot be applied currently. 
When using CE in CEC mode, the timetable parameter "Internal pressure" can be set, but is not applied during run. 
When using CE in CE/p mode the parameter can be set, but results in a "download method failed" error during method download.

Temporary Solution:

As a workaround, make sure not to use the timetable parameter "Internal pressure".

Fix Information:

There is no fix available currently, It is planned to remove the "Internal pressure" parameter from the CE timetable in a future driver release.

Keyword: CE Method

One-line Description:

Inconsistent labeling of G7100A - CE System 

Problem:

There is a inconsistent labelling of the G7100A CE System in the drivers.
The G7100A consists out of two modules, which are the G7150A (CE Core Module) and G7151A (DAD).
Some software dialogues like the Method UI or Module List and reports show the product number G7100A, some show G7150A and G7151A.   
This is only a display issue, the functionality is not affected.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: CE Method

One-line Description:

PSI pressure unit is not supported for 7100 Capillary Electrophoresis (CE)

Problem:

The usage of PSI as pressure unit is not supported. 
After conversion of bar to psi the range verification check for the value inputs is not applied. In addition, the values in bar are still reported in the logbooks.

Temporary Solution:

N/A

Fix Information:

Fixed with the driver version 3.5

Keyword: CE Method

One-line Description:

Unload lifter" information is missing in the audit trail during cassette change

Problem:

During the context menu action 'Cassette change' ,the outlet vial is lowered and also the inlet lifter. This procedure is not logged in the audit trail.

Temporary Solution:

n/a

Fix Information:

Fixed in CE Driver 3.6

Keyword: CE Method

One-line Description:

CEC External Pressure Home Values are not cleared after changing CE Mode

Problem:

A method created in CEC mode with External Pressure Home Values could be saved as a standard CE method or a CE+P method after changing the pressure mode. However, the external pressure settings were not properly cleared.
If external pressure data was being recorded, the Instrument Curves could incorrectly indicate that external pressure had been applied during the run.

Temporary Solution:

n/a

Fix Information:

This behavior has been corrected.
Now, when a method created in CEC mode is loaded, and the instrument configuration has been changed to CE mode or CE+P mode, the software displays a Manual Resolution warning: Validation Errors: 'External' is no valid 'Pressure Mode' value.
The wording of the warning may vary depending on the version of the driver package used by the chromatography data system.
Users are alerted to the conflict before running the method and hidden external pressure settings can no longer be recorded in the Instrument Curves unintentionally.
Recommendation
When changing between CEC mode, CE+P and CE mode, it is recommended to create a new method from the default template rather than reusing a method created for a different pressure mode.

Keyword: ColumnComp Driver

One-line Description:

TCC Cluster, TCC2 shows always valve position 1

Problem:

In a TCC cluster of 2 G1316C TCC, the TCC2 shows always valve position 1. 
The TCC1 shows the correct position.

Temporary Solution:

n/a

Fix Information:

Resolved in Rc.net Driver Revision: A.02.03

Keyword: ColumnComp Driver

One-line Description:

TCC CLuster remains offline with message "Initialization of ColumnCompCluster failed

Problem:

After starting the application \ connecting to the instrument, the TCC Cluster remains offline.
HowTo reproduce:
• Configure an instrument with the single TCCs
• In all single TCC method UI select the Combined mode for the right temperature zone and download it to the instrument
• close \ disconnect the instrument
• Configure a 2nd instrument with a TCC cluster. Just one column (no waste or bypass) and put in the upper right corner of one TCC.
Trying to connect to this TCC cluster. It remains offline.

Temporary Solution:

N/A

Fix Information:

LC & CE Drivers A.02.08 SP1

Keyword: ColumnComp Driver

One-line Description:

Position number after run is reported wrongly for Multicolumn Thermostat G7116B in the report and audit trail

Problem:

The Multicolumn Thermostat G7116B allows setting a valve position to which the valve is switched after a run. This switch has been done correctly but was not reported correctly as well in the report as in the method audit trail. Offset between reported and actual valve position is 1, i.e. position 2 has been reported as 1.

Temporary Solution:

n/a

Fix Information:

This issue has been fixed with driver release A.02.11 SP1.

Keyword: ColumnComp Driver

One-line Description:

Field sizes for column description and comment have been increased from 16 to 32 characters for G7116B Multicolumn Thermostat

Problem:

For driver release A.02.11 and the corresponding firmware revisions, the maximum length for the column description and comment has been limited to 16 characters, which may not be sufficient for some columns. 16 characters apply to Latin characters, symbolic languages like Chinese or Japanese may require more memory for internal representation, which further limits the length of possible descriptions.

Temporary Solution:

not available

Fix Information:

This has been fixed with driver release A.02.11 SP1. Please note that this fix requires a firmware update for all relevant modules, which are the G7116B MCT module itself, which requires firmware C.06.72 as a hosted module and B.06.72/D.06.72 for all potential hosts. Please update all modules to the latest available firmware set including this fix. For details about the hosted module concept, please refer to the Firmware Update Manual.

Keyword: ColumnComp Driver

One-line Description:

Method transfer from G1316A/B/C to G7116B failed if option "next position after run" was chosen

Problem:

If a method with option "next position after run" was chosen for G1316A/B/C was loaded for a G7116B module, such a method became invalid and was rejected by the CDS and a CDS specific error message may be displayed or written to the log book.

Temporary Solution:

not available

Fix Information:

This issue has been fixed with driver release A.02.11 SP1.

Keyword: ColumnComp Driver

One-line Description:

Wrong display for 2pos/10port and 2pos/6port valves in method UI for G1316A/B/C modules

Problem:

For G1316A/B/C modules using the 2pos/10port valve or 2pos/6port valve, the method UI shows different port connections than the written connections, e.g. 1->2 is written but 1-> 10 is depicted. The description is correct but the display is wrong.

Temporary Solution:

Rely on written description.

Fix Information:

Fixed with A.02.11 SP1

Keyword: ColumnComp Driver

One-line Description:

No tooltip displayed if linked detector is missing for G7116B Multicolumn Thermostat

Problem:

If a detector has been linked optionally to a G7116B Multicolumn Thermostat (MCT) for aligning temperature control of MCT and detector flow cell and this detector is not present, the G7116B does not become ready as indicated by a yellow status LED. No tooltip is shown which would explain that reason.

Temporary Solution:

n/a

Fix Information:

Fixed with driver release A.02.11 SP1.

Keyword: ColumnComp Driver

One-line Description:

Incompatible change in behavior of 2-position/6-port and 2-position/10-port valves in G1170A, G7116B and G4227A compared to Thermostatted Column Compartments G1316A/B/C

Problem:

Multicolumn Thermostats (MCTs) G7116B, External Valve Drives G1170A and Flexible Cubes G4227A are controlling 2-position/6-port valves and 2-position/10-port valves differently from similar Thermostatted Column Compartments (TCCs) like G1316A/B/C. This change of internal valve positions has been introduced for the 1290 Infinity valve drive G1170A and the Flexible Cube G4227A but has not been relevant because no method transfer was needed between rather different modules.  
Both valves use two positions:
Modules                                           Valves                     Position 1   Position 2
G1316A/B/C                                    2pos/6port               1->2	           1->6
G7116B, G1170A, G4227A             2pos/6port               1->6	           1->2
G1316A/B/C                                    2pos/10port             1->2           1->10
G7116B, G1170A, G4227A            2pos/10port              1->10         1->2
Depending on the module type, different ports are connected by the same method parameter (valve position). If such valves were used e.g. for column selection and columns are connected to ports with same numbers in a new module, a different column may be used by a transferred method. This is displayed correctly in the user interface but may not be expected.

Temporary Solution:

n/a

Fix Information:

If your methods rely on valve positions, please verify that they are using correct connections. When transferring methods between different module categories (e.g. G1316C vs. G7116B), please either change your method parameters or corresponding connections to ports.

Keyword: ColumnComp Driver

One-line Description:

Error dialog and error logbook entry for TCCs G1316A/B/C

Problem:

When loading a method in OpenLab CDS EZChrom edition A.04.06, which includes any Thermostatted Column Compartment G1316A/B/C using LC and CE drivers A.02.11, an error dialog may be shown along with a log book entry "Error in RCNet_RCMethodUI::ReturnRequestResponse : There is an error in XML document (0, 0).". This error message has no impact and can be ignored.

Temporary Solution:

Ignore this error message

Fix Information:

This issues has been fixed with driver A.02.12.

Keyword: ColumnComp Driver

One-line Description:

Control UI for G1316C does not work when using the Instrument Control Framework ICF in client/server setups.

Problem:

In a client/server scenario, where the server has driver A.02.10 and the Client has been upgraded to A.02.11 SP1, the control user interface of the module dashboard a window may appear with the message that the settings are being read and stays unchanged.

Temporary Solution:

Close this dialog using "Cancel". For switching on the thermostat, use command "Switch on/off" from the context menu of the dashboard.

Fix Information:

This issue has been fixed with driver release A.02.12.

Keyword: ColumnComp Driver

One-line Description:

Changing control settings like switching on/off the Column Compartment Thermostat or Leak Detection in the instrument control UI does not work

Problem:

Two possibilities are available for switching on or off the thermostat of a column compartment
1. The Instrument Control User Interface (click "Control" in the context menu of the TCC). Then select Thermostat On or Off.
2. "Switch On" or "Switch Off" function in context menu.
Option 1 does not work with driver A.02.11. Switching between on and off does not switch the thermostat.
The same applies also to the settings for "Leak Detection".

Temporary Solution:

For switching the thermostat of the column compartment on or off, use Switch On or Off from the module dashboard context menu (option 2 above).
The leak detection settings can still be changed using the Instant Pilot.

Fix Information:

This issue has been fixed in driver release A.02.12.

Keyword: ColumnComp Driver

One-line Description:

Import/export functionality in Column Assignment dialog of MCT has been removed

Problem:

Importing of column information via Column Assignment dialog would overwrite existing tags. In most cases, this would not be the expected behavior. Expected behavior would be to import such information only for columns without or with empty tags.

Temporary Solution:

Column information import has been removed for driver A.02.12 in order to avoid issues. Do not use this functionality for driver A.02.11.

Fix Information:

n/a

Keyword: ColumnComp Driver

One-line Description:

No comments can be entered for virtual tags

Problem:

Column information can be either stored on Column tags (recommended), in a column database (if supported by a CDS, e.g. OpenLAB CDS ChemStation Edition C.01.07 SR2) or temporarily on the instrument mainboard (as a virtual tag). Not all possible information may be supported outside the driver. For example, column comments cannot be stored on the mainboard.
Previous drivers allowed entering comments or importing them from the ChemStation database but this information was not persisted for virtual tags.

Temporary Solution:

Do not try using comments for virtual tags, as they will not be saved.

Fix Information:

Since driver A.02.14, the comment field is no longer editable if no physical tag is present.

Keyword: ColumnComp Driver

One-line Description:

Column information may get lost within VTCs during auto-configuration in some cases

Problem:

A VTC allows handling of column information within clustered column thermostats or columns outside the system. This information is stored on column tags, on the system (mainboards) and - if applicable - in the ChemStation column database. Information for columns, which are either installed in column thermostats G1316C or outside the system may be reset during an auto-configuration. This is because modules configured in the VTC have changed their order.

Temporary Solution:

Re-order modules in the VTC configuration to the previous one after doing an auto-configuration.

Fix Information:

Fixed in LC and CE driver A.02.14

Keyword: ColumnComp Driver

One-line Description:

Last injection date and injection counters are not updated in VTC in some cases

Problem:

A VTC allows handling of column information within clustered column thermostats or columns outside the system. This information is stored on column tags, on the system (mainboards) and - if applicable - in the ChemStation column database. Information for columns, which are either installed in column thermostats G1316C or outside the system may not be updated correctly.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: ColumnComp Driver

One-line Description:

Valve-Thermostat-Cluster time table can be edited in read-only mode

Problem:

Chromatographic Data Systems (CDS) can temporarily set access to driver functions to read-only. By mistake, the time table of valve-thermostat clusters (VTC) is editable. This may cause issues for the CDS.

Temporary Solution:

Do not edit the VTC time table in read-only mode.

Fix Information:

This has been fixed in driver A.02.14.

Keyword: ColumnComp Driver

One-line Description:

Maximum column void volume is 50 mL

Problem:

Import of column information with a void volume larger than 50 mL from the OpenLAB CDS ChemStation Edition column database may fail because of a numeric limit in the driver.

Temporary Solution:

Avoid values larger than 50 mL. As a workaround, try to write void volume information e.g. to the comment field.

Fix Information:

This shall be fixed with an upcoming driver release.

Keyword: ColumnComp Driver

One-line Description:

Auto configuration fails when changing the valve type in an MCT for an existing valve thermostat cluster

Problem:

Auto configuration fails when changing the valve type in an MCT (Multi Column Thermostat) G7116A/B for an existing VTC (valve thermostat cluster). 
When trying to configure the valve thermostat cluster an unhandled exception is displayed.

Temporary Solution:

Do an auto configuration without clustering the modules, start the CDS and close it again, then do a second auto configuration and set up the VTC cluster as desired.

Fix Information:

This has been fixed with driver version A.02.16.

Keyword: ColumnComp Driver

One-line Description:

G1316C does not recognize 800 bar Quick Change Valve Heads configured in LabAdvisor

Problem:

The driver of G1316C Agilent 1200 Series Thermostatted Column Compartment is unable to recognize 800 bar Quick Change Valve Heads that have been configured in LabAdvisor.

Temporary Solution:

When configuring a 800 bar Quick Change Valve Head in a G1316C Agilent 1200 Series Thermostatted Column Compartment, use the built-in driver function only to manually configure the Valve Head. 
With the Valve Head installed, perform an auto-configuration. Start up your data system and connect to the instrument. Right-click on the dashboard tile of the G1316C and access the "Modify" > "Valve type..." function. Choose the correct valve type from the list and follow the instructions to modify the tag information on the device manually. Power down your device and install the 800 bar Valve Head. Perform an auto-configuration, connect to the instrument with your data system and verify that the proper Valve Head is displayed in the G1316C Dashboard tile.

Fix Information:

n/a

Keyword: ColumnComp Driver

One-line Description:

Enforce column in MCT method requires 14 characters or less

Problem:

When using the feature "Enforce column" for run on the MCT method screen, do not use more than 14 characters for the product number. Otherwise the method download fails.
G7116A/B and the valve-thermostat clusters (VTC) are affected

Temporary Solution:

Make sure 14 characters or less are being used for the product number field.

Fix Information:

The issue will be fixed with the release of driver 3.5.

Keyword: ColumnComp Driver

One-line Description:

ICC column assignment unavailable in LC & CE Drivers 3.5

Problem:

The column assignment for the Integrated Column Compartment (G7130A) is unavailable using the LC & CE Drivers 3.5. Existing column assignment works as designed, no changes are possible.

Temporary Solution:

n/a

Fix Information:

The issue will be fixed with the release of LC & CE Drivers 3.5 SR1.

Keyword: ColumnComp Driver

One-line Description:

Run cannot be started due to the migration of MCT or VTC methods when using audit trail

Problem:

During the migration of Multi-Column Thermostat (G7116A/B) methods or VTC cluster methods created with the LC Drivers 3.4 or older to 3.5 and 3.5 SR1, there could be missing audit trail entries. These missing entries could cause the run to not start.

Temporary Solution:

Manually opening and saving the affected methods using drivers 3.5 or newer.

Fix Information:

The issue will be fixed with the release of driver 3.5 SR2.

Keyword: ColumnComp Driver,Pump Driver

One-line Description:

PumpValve-Cluster & TCC-Cluster halts sequence once methods change valve position

Problem:

During sequence, if method change causes valve to be switched, the ChemStation hangs.

Temporary Solution:

n/a

Fix Information:

Fixed in A.02.04

Keyword: DAD/MWD Driver

One-line Description:

Incomplete signal description in the online plot window

Problem:

DAD 1A (no additional information) is shown
DAD 1A, wavelenght,bandwitdh,reference WL, ref. BW is requested

Temporary Solution:

n/a

Fix Information:

Resolved in Revision: A.02.03

Keyword: DAD/MWD Driver

One-line Description:

In localized CDS for ELSD detector G4218A no signal data is shown or stored

Problem:

On a localized chromatograpy data system the driver for ELSD detector throws an exception and fails to show or store the detector's signal data. On an English system the ELSD driver's operation is not affected.

Temporary Solution:

n/a

Fix Information:

For a localized (e.g. Chinese, Japanese...) system a patch for the ELSD driver is made available.

Keyword: DAD/MWD Driver

One-line Description:

G1315A/B do not show spectral data and G1321A/B show wrong time stamps for spectra

Problem:

RC.Net Driver's Interpretation of timestamp associated with spectra sent from device is wrong. So G1315A/B DADs appear to show no spectal data, while all spectral data of G1321A/B FLD appears to have a timestamp of "0".

Temporary Solution:

n/a

Fix Information:

ChemStation B.04.03 DSP2 was issued

Keyword: DAD/MWD Driver

One-line Description:

High load on CAN may cause "Spectra runbuffer overflow" entries and a loss of spectra

Problem:

If LAN is connected not to LC module generating most data (i.e. to Pump in spite of DAD's presence) then interconnecting CAN connection between modules might get overloaded. Potential consecutive loss of spectra may be observed and is flagged as "Spectra runbuffer overflow" in logbook and on report.

Temporary Solution:

Installation documentation for LC HW states that the LAN access should be in the module with the highest workload, i.e. by DAD/MWD - FLD - VWD - RID - Pump - ALS (in this order) and independent whether it is a 1100 - 1200 - 1290 - 1260 system.

Fix Information:

n/a

Keyword: DAD/MWD Driver

One-line Description:

Autobalace executed although in Sequence table set to "OFF"

Problem:

1) A method XYZ.M is saved with following DAD settings: Autobalance -> Prerun
2) A sequence table is saved using the method XYZ.M and AutoBalace set to "OFF"
3) The sequence gets started and although AutoBalace set to "OFF" it is executed.

Temporary Solution:

still under investigation

Fix Information:

none

Keyword: DAD/MWD Driver

One-line Description:

Occasional shift in retention times for G1315A/B or G1365A/B

Problem:

Occasionally some early data points (with negative time stamp) may occur that have not been handled correctly. Some slight deviation / jitter of retention times compared to similar runs may happen.

Temporary Solution:

n/a

Fix Information:

A patch for RC.Net Driver A.02.05 or A.02.06 is available: A.02.05 [SP1], respectively A.02.06 [SP1]

Keyword: DAD/MWD Driver

One-line Description:

Lowest possible DAD wavelength is 190.5 nm

Problem:

Lowest possible DAD wavelength is 190.5 nm. In earlier EZChrom and ChemStation revisions it was 190 nm. The midpoint wavelength or bandwidth need to be changed such that the lowest wavelength is 190.5 nm.

Temporary Solution:

Modify methods and set the wavelength and bandwidth such that their lowest wavelength is 190.5 nm.

Fix Information:

Has been fixed with driver A.02.11

Keyword: DAD/MWD Driver

One-line Description:

Retention times may be slightly too high for DAD data acquisition rates below 1 Hz

Problem:

If very low data acquisition rates are used for the DAD, these frequencies are rounded in the driver and chromatographic data system. Affected data rates are 0.3125 Hz (rounded to 0.31 Hz, corresponding to 16 seconds response time) and 0.625 Hz (rounded to 0.62 Hz, corresponding to 8 seconds response time).
Data acquisition rates are used by the data analysis for calculating the time values from the data point counter (e.g. at 2 Hz, the next data point comes 0.5 seconds later). Because of the rounding, the real module frequency is higher by 0.8% than what is shown in the UI/report and retention times are increased by the same factor. The effect increases with the run time, e.g. a peak coming at 10 minutes would be displayed at 10:05 minutes.
This issue has been introduced with LC driver A.02.11 in 2015. It affects all DADs regardless of the CDS. The issue only becomes visible when comparing measurements run with affected drivers and non-affected drivers, but not e.g. between calibration and quantitation runs with the same software.

Temporary Solution:

n/a

Fix Information:

This has been fixed with driver version A.02.16.

Keyword: DAD/MWD Driver

One-line Description:

No spectra are collected when collection range divided by steps is non-integer

Problem:

The following issue has been reported for the G1315A/B DAD and G7121A FLD detectors collecting spectra in Empower environment: 
If the method is set up to collect spectra and the Spectra range divided by the incremented steps results in a non-integer value, then only one spectra point or no spectra at all are collected.
Working example:                     Spectra range 190 - 400nm / 2 nm steps (210 /2 = 105)
Problem example:              Spectra range 190 - 400nm / 4 nm steps (210/4 = 52,5)

Temporary Solution:

Workaround: ensure that spectra range divided by the incremented steps results in an integer

Fix Information:

Solved with LC & CE Drivers 3.4

Keyword: Dashboard

One-line Description:

Module stays offline after a configuration change using the "Modify" function

Problem:

If method resolution occurs due to a configuration change, after applying a modify function and the user did not accept this resolution within one minute, the module goes offline.

Temporary Solution:

Either accept the resolution within one minute or restart the CDS (Chromatographic Data System).

Fix Information:

n/a

Keyword: Dashboard

One-line Description:

Runs not finishing intermittently due to SFC remaining in Prerun state

Problem:

When using an hybrid SFC instrument stack with two pumps, the SFC module (G4301A) intermittently remains in "Prerun" state after completion of the run. This prevents the run from finishing.

Temporary Solution:

n/a

Fix Information:

Fixed with driver version A.02.18 SR2

Keyword: ELSD Driver

One-line Description:

ELSD G4218A can not handle change of Sample Time during run

Problem:

With Rc.Net driver internal filters of ELSD G4218A get confused by change of "Sample Time" during run.

Temporary Solution:

n/a

Fix Information:

fixed with LC Drivers A.02.03

Keyword: ELSD Driver

One-line Description:

The ELSD method cannot be called by a right-click from the context menu

Problem:

In the method and run control view the ELSD has its own dashboard item. Unlike other modules in an RC.Net configuration the instrument setup is not available by right-clicking on it.

Temporary Solution:

Use the instrument menu to have access to all modules, including the ELSD.

Fix Information:

No fix available.

Keyword: ELSD Driver

One-line Description:

Runtime of a G4218A ELSD cannot be changed during a run

Problem:

The runtime of a G4218A ELSD cannot be changed explicitly during a run. However there are software mechanisms which implicitly change a run time, e.g. the function "ignore missing vessel" of an autosampler normally stops the run after some seconds if no vessel is present. In case of an G4218A ELSD this does not work and the run uses the full specified run time.

Temporary Solution:

A single run may be stopped manually.

Fix Information:

n/a

Keyword: FLD Driver

One-line Description:

FLD G1321 Scan ranges and threshold under certain conditions not available

Problem:

Scan ranges and threshold under certain conditions not available.

Temporary Solution:

n/a

Fix Information:

Solved with LC & CE Drivers A.02.08 SP1

Keyword: Globalization

One-line Description:

Content of localized Online Help texts may not be complete (Japanese, Chinese and Portuguese version)

Problem:

The version of the Online Help published with LC driver version A.02.17 SI32 has some incomplete pages when using the Japanese, Chinese or Portuguese version. This results in texts where keywords like module names are missing in the continuous text.

Temporary Solution:

Temporary workaround: The English help files are not affected. They can be browsed manually and used for reference.

Fix Information:

The issue will be fixed with the release of driver A.02.18.

Keyword: Globalization

One-line Description:

Flow Modulator requires regional settings in English

Problem:

The Flow Modulator dashboard requires the regional settings in english. If the regional settings are set to German, the values set in the method graphical interface are multiplied by a factor of 100 and 1000, respectively. This  results in incorrect split ratios and dilution factors.

Temporary Solution:

This issue can be circumvented by setting the system language to English (US).

Fix Information:

Fixed with driver version A.02.19.

Keyword: Globalization

One-line Description:

Brazilian Portuguese language setting causes driver UI to become irresponsive

Problem:

Running the driver with a Brazilian Portuguese operating system will cause the driver UI to become irresponsive. This affects all modules.

Temporary Solution:

Change the operating system language to English.

Fix Information:

A fix is planned

Keyword: Globalization,Pump Driver

One-line Description:

Pressure range settings may seem to change when using unit psi

Problem:

If the pressure unit psi is used for minimum or maximum pressure, the value seems to change if the setting is stored on the instrument (usually a pump module) after re-opening the user interface. This is due to a rounding of numbers, as values are internally always stored in unit bar.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: Performance

One-line Description:

Analog Output and Digital Output signals of a detector do not fully match

Problem:

Collecting detector signal outputs in two ways, one by recording the digital detector output and one by collecting its Analog Output with a G1390B Universal Interface Device, may lead to non-overlaying chromatography results when comparing both signals.

Temporary Solution:

Do not expect that a detector's analog output signal that is recorded by a G1390B Universal Interface Box fully correlates to the timings of that detector's digital signal output. Use either the analog output only or the direct output only.

Fix Information:

No fix available as this behavior is by design.

Keyword: Performance

One-line Description:

Usage of "Next location" does not work as expected when using multiple Recovery Collectors in a cluster

Problem:

When using a define Recovery position together with the Recovery location setting"Next location" in a purification system with multiple Recovery collectors, the setting will not behave as expected. 
For example, when the initial recovery position of a G7166A has been set to "2-8", the system will fill up locations "2-9", "2-10" and "2-11" and then - since all recovery locations on that module are filled - the system will start at the other module with "2-8" and not at "2-1" as would be expected.

Temporary Solution:

Not applicable

Fix Information:

Fixed in LC & CE Drivers 3.2

Keyword: Pump Driver

One-line Description:

Pump overpressure: impossible to turn off pump via UI

Problem:

In cases where the pump runs into an overpressure situation the user wants to turn off the pump as fast as possible, e.g. by clicking the ON/Off button of the UI.
However, the overpressure is interpreted as an not ready condition and button changes to "make device ready" and by clicking it, the pump won't turn off.

Temporary Solution:

The user needs to right-click the UI, go to control, select PUMP OFF and press o.k.

Fix Information:

Resolved in revision A.02.02 SP1

Keyword: Pump Driver

One-line Description:

Wrong Flow setting displayed when re-opening the Method User Interface

Problem:

Setting the Flow on the G1376A using the Method User Interface.
After pressing "OK" the flow is applied but opening again the Method User Interface the Flow=0 is displayed.

Temporary Solution:

None

Fix Information:

Fixed in Driver revision A.02.04 SP1

Keyword: Pump Driver

One-line Description:

Flow unit in Online Plot for Nano pump is incorrect.

Problem:

The flow unit in the Online Pot for the Nano Pump is displayed as ml/min.
The correct unit shoulf be µll/min.

Temporary Solution:

None.

Fix Information:

Fixed in driver revision A.02.04 SP1.

Keyword: Pump Driver

One-line Description:

Misrepresentation of Bottlefillings in Dashboad of PumpValveCluster

Problem:

When a Valve is configured for Channel A in PVC the visual presentations of the BottleFillings of ChannelB, ChannelC and ChannelD are wrong.
It will not show the BottleFillings of the corresponding Channel but the BottleFilling of Channel A Valve Pos 2 etc.

Temporary Solution:

none

Fix Information:

Will be fixed with the Rc.NET Drivers Rev . A.02.06

Keyword: Pump Driver

One-line Description:

Solvent compositions during run do sometimes not sum up to 100%

Problem:

In some cases, the real-time display for solvent compositions shown by the pump panel during a run may not sum up to 100% but to a percentage slightly higher or lower.
This is because the user interface updates solvent compositions indepently per channel, i.e. channel A may still read 50% while channel B has already increased to 50.1%.
This is a display issue, not a gradient formation issue. The gradient sent to and formed by the pump is correct, so the virtual display in the user interface has no relevance for chromatographic measurement results.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: Pump Driver

One-line Description:

PumpValveCluster with ISET - Solvent composition: resulting %A is wrong (at 1 line in timetable)

Problem:

1. Working with a G4220A pump with ISET enabled.
2. The emulated pump was: G1312B no mixer.
3. Set up a timetable.
4. Added a G1160A valve into the system.
5. Reconfigured the instrument and setup a pump-valve-cluster.
6. During startup selected "Save instrument settings in new method".
7. Enabled ISET and selected G1311A pump this time.
-> the timetable of previous configuration still exists, but on one line "95.1%A and 5%B" is displayed instead of "95%A, 5%B

Temporary Solution:

Select Method -> New Method

Fix Information:

Solved with RC.Net A.02.07

Keyword: Pump Driver

One-line Description:

Memory leak in pump method dialog may cause performance drop

Problem:

A memory leak in pump method dialog may cause performance drop of the LC ChemStation (C.01.03 or earlier) application if methods get changed very often and/or the ChemStation instrument is operated several weeks without restarting the instrument.
The memory leak is about 1-2 MB large and this portion of memory does not get released after opening the instrument method dialog - which does always show the pump parameters, first.

Temporary Solution:

In order to avoid a performance decrease due to permanent memory allocation it is recommended to restart each ChemStation instrument after 2-3 weeks of operation.
A user macro is under development and testing to remind users of restarting a specific instrument after 2 weeks of operation.

Fix Information:

This defect is fixed in LC/CE driver version A.02.05 or higher included in OpenLAB CDS ChemStation C.01.04.
OpenLAB CDS ChemStation C.01.03 installations can be updated with update HF 08 (or higher) and LC/CE instrument drivers version A.02.06.  The Update HF 08 and  instrument drivers are available for download from https://agilent.subscribenet.com/control/agil/product?child_plneID=589223&ver=ARC.

Keyword: Pump Driver

One-line Description:

Blend Assist : Timetable not persisted properly

Problem:

When configuring a G4204A Quat Pump with Blend Assist a value in the timetable is not "send" to the instrument properly. 
At least when opening the method UI again, the set value is not shown any longer but 0 % again.

Temporary Solution:

N/A

Fix Information:

solved with the LC & CE Drivers A.02.09

Keyword: Pump Driver

One-line Description:

Unused solvents are handled differently for 1100/1200 Series/1260 Infinity vs. 1290 Infinity/Infinity II pumps

Problem:

The time table of a pump allows the definition of a gradient table. Section "Solvents" allows setting, which solvents shall be used. Disabling a solvent by unchecking it in the solvent section is implemented differently depending on the module type.
A: Modules with firmware revision A, e.g. 1100/1200 Series and 1260 Infinity pumps. If a solvent is disabled, its contribution to the solvent composition will be set to zero and the contribution of channel A will increase accordingly. This is not displayed in the gradient table or report. The intended use of the checkbox is a temporary change of the composition for flushing solvent channels. Do not disable solvents during method runs.
B/D: Modules with firmware revision B or D, e.g. 1290 Infinity/Infinity II pumps and 1260 Infinity II pumps. If a solvent is disabled, this changes the solvent composition outside method runs (e.g. for flushing) and the start condition of the gradient. It does not change solvent conditions for any other lines in the gradient table. The gradient table is fully valid.
This different implementation also needs to be considered when transferring methods from previous to new pumps.

Temporary Solution:

n/a

Fix Information:

This is caused by different firmware interfaces of revision A vs. revisions B/D. This cannot be changed without negative side effects for existing methods. Therefore, no driver fix will be provided. All new pumps are using the better implementation B.

Keyword: Pump Driver

One-line Description:

Prep-pump cluster stays not ready after restarting OL ChemStation (reconnect)

Problem:

Prep-pump cluster stays not ready after restarting OL ChemStation (reconnect) while modules were still on.

Temporary Solution:

Switch prep pumps off and on again.

Fix Information:

n/a

Keyword: Pump Driver

One-line Description:

The 1290 Quaternary Pump G4204A is specified for a maximum flow rate of 5 ml/min

Problem:

The 1290 Quaternary Pump G4204A is specified for a maximum flow rate of 5 ml/min. The user interface allows setting a flow rate of up to 10 ml/min as a method parameter and for purging. Using a flow rate above 5 ml/min is not recommended and the pump may not meet performance specifications in this range. Agilent may not allow flow rates above 5 ml/min for future software/driver/firmware revisions.

Temporary Solution:

Use of maximum flow rate of 5 ml/min.

Fix Information:

n/a

Keyword: Pump Driver

One-line Description:

Purge function has been improved for Preparative Pump Clusters

Problem:

For drivers before A.02.12, all pumps in a preparative pump cluster were flushed through the purge valve in channel A. As a consequence solvent e.g. from channel B could enter the flow path of channel A potentially causing issues.

Temporary Solution:

not applicable

Fix Information:

If a composition is set for purging, multiple channels can be purged at the same time. Since driver A.02.12, purge valve A is still open whenever any pump within the cluster is purged. In addition, purge valves of all other channels, which have a composition to the purge flow, will open as well, such that solvent can leave through the corresponding valve. All purge valve outlets must be connected to waste lines.

Keyword: Pump Driver

One-line Description:

Solvent type may change during a method transfer from 1290 Infinity/II Quaternary Pumps G4204A or G7104A to 1290 Infinity/II Binary Pumps G4220A/B or G7120A

Problem:

When transferring a method from 1290 Infinity/II Quaternary Pumps G4204A or G7104A to 1290 Infinity/II Binary Pumps G4220A/B or G7120A, the solvent type may change, e.g. from Acetonitrile to generic aqueous.

Temporary Solution:

Verify solvent type after method transfer.

Fix Information:

Fixed with driver release A.02.11 SP1.

Keyword: Pump Driver

One-line Description:

Recorded Acquisition Method has Incorrect Pump Parameters

Problem:

Due to a memory leak in the Agilent LC Pump Driver an overflow occurred over time. This overflow led to a method with default parameters being reported in the data files instead of the actual method.

Temporary Solution:

n/a

Fix Information:

This issue has been fixed with the LC driver version A.02.10

Keyword: Pump Driver

One-line Description:

Implementation of seal wash behavior has been improved for G4220A/B and G4204A

Problem:

If seal wash run mode was "When pump is on" and the pump was off and Seal Wash Option was either "Single wash" or "Periodic", the seal wash was on. Additionally, when Seal Wash Run Mode was "Off" and Seal Wash Option was either "Single wash" or "Periodic", the seal wash was on.

Temporary Solution:

n/a

Fix Information:

The implementation has been simplified and improved for driver release A.02.12. as follows:
If the seal wash run mode is off, seal wash is always off. If it is on, it is always on. If seal wash run mode is "On when pump is on", seal wash is off, when the pump is off.

Keyword: Pump Driver

One-line Description:

Warning "No matching ISET solvent combination" for G4220A/B pump as emulated pump

Problem:

If pumps G4220A/B without a mixer shall be emulated by G7120A, a warning "No matching ISET solvent combination could be found..." is displayed in section ISET > Model parameter > Manually set ISET solvent model and only solvent model "generic" is available.

Temporary Solution:

Choose solvent model "Generic". This uses the correct solvent model defined for the emulating pump G7120A.

Fix Information:

n/a

Keyword: Pump Driver

One-line Description:

Using the OpenLAB CDS EZChrom edition feature "Extend run" will disable ISET features in the 1290 pumps

Problem:

When changing the run time of the currently ongoing run by "Extend Run" in EZChrom will disable ISET features in the pumps as the calculated gradient in the pump using ISET depends on the timetable. This may result in an unexpected or wrong gradient.

Temporary Solution:

Do not use "Extend run" if ISET is active.

Fix Information:

none

Keyword: Pump Driver

One-line Description:

Seal wash for Preparative Pump G1361A or Preparative Pump Cluster is displayed as "off" even when it's on

Problem:

Seal wash for Preparative Pump G1361A or Preparative Pump Cluster is displayed as "off" even when it's on

Temporary Solution:

n/a

Fix Information:

Shall be fixed with an upcoming release.

Keyword: Pump Driver

One-line Description:

Wrong purge flow and duration shown in prepare pump dialog depending on regional settings

Problem:

Some regional settings (e.g. German) interchange the digit grouping symbol with the decimal symbol, i.e. 1,234.56 in English is 1.234,56 in German. The prepare pump dialog for 1290 Infinity and 1290 Infinity II pumps (G4204A, G4220A, G7104A, G7120A) does not apply this logic correctly and displays e.g. a value 0.500 min read from the instrument as 500 min.

Temporary Solution:

As a workaround, correct the value manually, e.g. to 0,5 min (half a minute), then the correct value will be sent to the instrument.

Fix Information:

This has been fixed with driver A.02.15

Keyword: Pump Driver

One-line Description:

Shutdown recovery does not work for Preparative Pump Clusters in a Multi-Controller environment

Problem:

When multiple controllers are connected to a system with a Preparative Pump Cluster and one controller triggers a Shutdown, then that shutdown state cannot be recovered from the other controller.

Temporary Solution:

Either use the controller that initially caused the Shutdown to recover or disconnect that controller from the system and use any other controller to recover from the shutdown state.

Fix Information:

N/A

Keyword: Pump Driver

One-line Description:

Unexpected shutdown of Chromatographic Data System when executing a pump purge

Problem:

When executing a Pump Purge from a Pump Driver's Control Dialog, the chromatographic data system closes unexpectedly. The issue appears sporadically depending on computer system performance.

Temporary Solution:

n/a

Fix Information:

Fixed with driver version A.02.18 SR2

Keyword: Pump Method

One-line Description:

2DLC peak-based high resolution cut can be longer than expected

Problem:

Some scenarios (e.g. low 1D flow) where the detector delay is larger than the time between beginning of the peak and end bracket will lead to the cut to not being stopped by the end peak trigger. This will lead to a full sized cut.

Temporary Solution:

Moving the end bracket further to the right or increasing the 1D flow solves the issue.

Fix Information:

N/A

Keyword: Pump Status

One-line Description:

Client/server environment: Pump status information not visible in LC Dashboard 

Problem:

Under normal circumstances the used LC driver version on Clients and instrument control PC´s are the same. During an upgrade period, these version may differ.
In the case of an LC Driver 3.2 on the Client and a lower version on the instrument control PC, the pump status information (e.g. bottle fillings, pressure and flow) are not shown.

Temporary Solution:

N/A

Fix Information:

Ensure to have 3.2 LC driver in synch on the Client and the instrument control PC

Keyword: Reports

One-line Description:

Columns are not reported correctly when switching valves

Problem:

If valves are switched before or after a run using advanced options, the column is not reported correctly.

Temporary Solution:

use standard valve switching without advanced options

Fix Information:

This has been fixed in LC driver A.02.14

Keyword: Reports

One-line Description:

Not acquired signal A (VWD) leads to a "Manual Control" entry in the Result Set Audit Trail

Problem:

When signal A of an VWD is not acquired (according to the method settings), a "Manual Control" entry is reported in the Result Set Audit Trail.

Temporary Solution:

N/A

Fix Information:

This is fixed with driver version A.02.19.

Keyword: Reports

One-line Description:

FCC: When switching Fraction Collectors during a run in an asymmetrical setup, unexpected fractions might be collected and reported

Problem:

When having a Fraction Collector Cluster (FCC) with different delay volumes between the detector and the Fraction Collectors (FC) and it is switched from one Fraction Collector to another during a run, the following behavior can be observed:
Due to the different delay volumes, every FC has another delay time and thus its own timeline. When switching from one FC to another, timelines are also switched, which can lead to the effect that a certain time span is run through either twice or not at all. This depends on the different delay volumes.

Temporary Solution:

N/A

Fix Information:

When working with Fraction Collector Clusters it should be taken care to use exactly the same delay volumes between the detector and all FCs (symmetric structure).

Keyword: Reports

One-line Description:

"Delete" entry in the audit trail raises an audit concern

Problem:

With OpenLab CDS and a G7129A ALS sampler, a change to the instrument method from the default Flush Port to Wash Vial records the following entries in the audit trail:
• Added Needle Wash Location with value <vial location>
• Added Wash Cycles with value <value>
• Deleted Wash Time with value 3 s
• Changed Needle Wash Location from Flush Port to Wash Vial
 
The entry for Deleted Wash Time refers to the wash time in the Flush Port mode which does not apply to the Wash Vial mode. Since this value does not apply, it is deleted from the method.

Temporary Solution:

Agilent recommends users recognize that, when changing the ALS wash mode from Flush Port to Wash Vial, the Wash Time value no longer applies and is deleted from the method. Refer to the Wash Needle topic in the OpenLab Help & Learning documentation.

Fix Information:

No fix planned.

Keyword: Reports

One-line Description:

Firmware of hosted modules cannot be reported

Problem:

Some modules (e.g. MCT, Flexcube, UIB or external valve drives) require a host module for operation. In the instrument configuration and with the instrument report function, only the firmware of the host module is displayed.

Temporary Solution:

Use the system information in the instrument UI to check for the Slave Firmware of the hosted module

Fix Information:

The LC & CE Drivers 3.7 will add the hosted firmware version to the instrument report.

Keyword: Sampler Configuration

One-line Description:

Issues when re-configuring capillaries in Dual Loop and High Performance Autosamplers

Problem:

Dual Loop Autosamplers (G2258A)
A Dual-loop sampler will remain offline after updates to the Syringe, Front or Back Seat Capillary volumes, Lower or Upper Loop Capillary volumes are done in instrument configuration. 
High Performance Autosamplers (G1367A/B/C/D/E, G1368A, G1377A, G4226A, G5667A)
Any of the affected High-Performance samplers will remain offline will installing Syringes or Seat Capillaries with different volumes than originally configured.

Temporary Solution:

There is no temporary fix available.

Fix Information:

A fix is planned

Keyword: Sampler Configuration

One-line Description:

Performing auto-configuration, the LC Driver does not write the thermostat/cooler information into the configuration. Once the hosting CDS connects to the instrument, the driver detects the thermostat/cooler and requests an configuration update

Problem:

Hosting CDS applications that, due to architectural reasons, cannot update the global configuration after the connection is established, will detect a mismatch between the stored (global) configuration and the online configuration of the driver instance. This can cause the application to receive and handle continuous Configuration-Changed events resulting in unexpected behavior and logbook entries.

Temporary Solution:

n/a

Fix Information:

Starting with LC Drivers 3.4, the auto-configuration writes the thermostat/cooler information into the configuration and no subsequent configuration changes are triggered when a connection is established.

Keyword: Sampler Driver

One-line Description:

Injection valve cleaning, entering new values does not work

Problem:

Go to setup -> injector cleaning -> check time1 to 4 and enter a time.
Close dialog and open again.
Entry fields for time is disabled.

Temporary Solution:

You have to uncheck and check the time 1 to 4 again to enter new values

Fix Information:

Resolved in revision A.02.14

Keyword: Sampler Driver

One-line Description:

Injection Volume not shown when loading a method (Inactive)

Problem:

The injection volume on a method is only shown correctly after the start of the sequence.
After just loading the method, the previous used inj vol is shown.
ChemStation B.04.02

Temporary Solution:

n/a

Fix Information:

fixed with release A.02.04 of the LC Drivers.

Keyword: Sampler Driver

One-line Description:

Control of Tray illumination missing for G1329B & G4303A

Problem:

RC.Net driver for high performance autosampler does not present possibility to switch on or off tray illumination of G1329B or G4303A.

Temporary Solution:

On ChemStation's command line enter:
print SendModule$(LALS,"LGHT 1")
to switch on sampler's illumination and
print SendModule$(LALS,"LGHT 0")
to switch it off.
In ChemStation the use of a configuration with 'Cassic' drivers might also be an option.

Fix Information:

fixed in A.02.02 SP1

Keyword: Sampler Driver

One-line Description:

Parameter mismatch for custom-defined Well Plates

Problem:

The parameters that were offered to define customized well plates did not intuitively match the dimensions of a well plate.
It was not possible to define whether a plate contains wells or vials.
This could also lead to errors in the injected volume.

Temporary Solution:

No temporary fix available.

Fix Information:

fixed in A.02.02 SP1

Keyword: Sampler Driver

One-line Description:

Control of Tray illumination missing for new G1329A

Problem:

New G1329A ALS contain a tray illumination now. RC.Net driver for standard autosampler does not present possibility to switch on or off tray illumination of these new G1329A ALS.

Temporary Solution:

Check if G1329A is a new one and already has tray illumination.
On ChemStation's command line manually enter:
print SendModule$(LALS,"LGHT 1")
to switch on sampler's illumination and
print SendModule$(LALS,"LGHT 0")
to switch it off.
In ChemStation the use of a configuration with 'Classic' drivers might also be an option.

Fix Information:

fixed with LC Drivers A.02.03

Keyword: Sampler Driver

One-line Description:

Control of tray illumination missing for G1329A/B & G4303A in Japanese and Chinese ChemStation

Problem:

The following problem occurs in Japanese and Chinese ChemStation only:
RC.Net drivers for Agilent 1260 Infinity Standard Autosampler G1329A/B or Agilent 1260 Infinity SFC Standard Autosampler G4303A do not provide any possibility - neither on ChemStation's menu nor on sampler's context menu - to switch on or off tray illumination inside G1329A/B or G4303A.
Control of Agilent 1260 Infinity Standard Autosampler G1329B by 'classic' drivers of ChemStation is not affected.
Agilent 1260 Infinity SFC Standard Autosampler G4303A requires the RC.Net Driver. No 'classic' driver for it exists.

Temporary Solution:

On ChemStation's command line enter:
print SendModule$(LALS,"LGHT 1")
to switch on sampler's illumination and:
print SendModule$(LALS,"LGHT 0")
to switch it off.

Fix Information:

The issue will be solved in driver version A.02.03.

Keyword: Sampler Driver

One-line Description:

Larger injection volume with 90 ul head may be incorrectly displayed after injection

Problem:

With G1329A/B, a 90 ul head installed, and a large injection volume specified the RC.Net Drivers may display an irregular injection volume after the injection. Nevertheless the volume, which got injected, correctly represents the method's setpoint. It is a problem affecting only the presentation after the injection cycle. Neither the injected volume itself nor the display during the injection cycle are affected. For the duration of the injection cycle itself the correct injection volume is shown, and injected.

Temporary Solution:

n/a

Fix Information:

This issue has been fixed with driver release A.02.04.

Keyword: Sampler Driver

One-line Description:

LC driver starts run with ALS Chiller turned off

Problem:

Using the RC.NET Drivers to control the Autosampler Chiller the systems is injecting with the Autosampler Chiller turned off. This is a different behavior compared to the legacy Rapid Control drivers for EZChrom which forced an ON of the Autosampler Chiller.

Temporary Solution:

n/a

Fix Information:

This issue has been fixed with driver release A.02.01 SP1.

Keyword: Sampler Driver

One-line Description:

ICF A.01.04 - No method download, if method contains pretreatment/injector program steps.

Problem:

Methods including pretreatment/injector steps are not downloaded to the instrument, prior to a run.

Temporary Solution:

n/a

Fix Information:

The defect is fixed with the Driver Release A.02.06
In relation to the Instrument Control Framework, a PointPatch is available.
Please contact your Agilent Support Team.

Keyword: Sampler Driver

One-line Description:

Injection specific injection volumes may get propagated to following injections

Problem:

The following LC driver specific issue has been reported for OpenLAB CDS ChemStation C.01.03 and driver version A.02.05:
When overwriting the default injection volume defined in the method by an injection volume specified in the sequence table of OpenLAB CDS, non-integer formatted values (e.g. 0.8 ul,  2.4 ul,...) may get propagated to all following injections. If the injection specific injection volume is an integer value (1,2,3, ... ) this defect does not occur. 
The applied injection volume appears on classical as well as on intelligent reports.

Temporary Solution:

This defect does not affect workflows that do not include injection specific injection volumes. 
When using injection specific injection volumes it is recommended to write the default injection volume to each sequence line (e.g. by using the sequence fill down wizard) and modify the injection volume for those injections where a non-default values should be used.

Fix Information:

This defect is fixed LC/CE driver version A.02.06 introduced with OpenLAB CDS ChemStation C.01.04.  
This driver version can also be installed on top of OpenLAB CDS ChemStation C.01 with HF05 or later.
The driver and hot fix installation packages are available for download on
https://agilent.subscribenet.com/control/agil/product?child_plneID=589223&ver=ARC

Keyword: Sampler Driver

One-line Description:

Dua Loop Sampler: ACQ method shows wrong loop with overlap injection

Problem:

Pre Cond.: Overlapped injection wit overfill by factor with a DL with different loop sizes for upper and lower loop
Consequence: due FW automatism it happens that we will report the wrong loop and the wrong injection volume
Wrong injection volume reported in the case of 2 different loops
(does not make sense in the application).
A logbook entry: 
"Warning: Used injection volume can be different then specified in the method due to different loop size."

Temporary Solution:

no fix

Fix Information:

n/a

Keyword: Sampler Driver

One-line Description:

Bouncing menu

Problem:

This happens only if the user manually configures a thermostat along to his already set up sampler in the LC stack.
In this case the revision, serial number and type of the thermostat is not properly propagated to the internal configuration within the LC driver during the DownloadConfigSettings call.
That caused a ping pong situation where the CDS sends the complete configuration to the driver which detects the differences due to the incorrect internal configuration propagation and therefore triggers a new configchanged event. 
To fix this issue, the driver needs to propagate the serial number, revision and type of the manual configured thermostat to the actual configuration after a DownloadConfigSettings.

Temporary Solution:

n/a

Fix Information:

OpenLAB CDS ChemStation Edition - SP2 for LC RC.Net Driver A.02.05 and A.02.06

Keyword: Sampler Driver

One-line Description:

Wrong Inj Volume with German settings

Problem:

The firmware command was not formatted in a correct way on a German system.

Temporary Solution:

n/a

Fix Information:

OpenLAB CDS ChemStation Edition - SP2 for LC RC.Net Driver A.02.05 and A.02.06

Keyword: Sampler Driver

One-line Description:

the "edit Wellplate type" could not work in OpenLab ChemStation Edition Japanese .

Problem:

Within the 'Edit Wellplate' dialog a wrong property was used to validate the wellplate name. This led to an invisible error that prevented the saving of the new definition.
The validation checks if the name only contains ASCII characters. Depending on this the saving of wellplate definitions was only possible on English systems was possible because the property used for the validation is localized and contains non-ASCII characters.

Temporary Solution:

n/a

Fix Information:

OpenLAB CDS ChemStation Edition - SP2 for LC RC.Net Driver A.02.05 and A.02.06

Keyword: Sampler Driver

One-line Description:

Wrong Injection Volume using overlapped injection and setting InjVol in sequence table

Problem:

If an injection volume has been set in the method when using overlapped injection and this volume shall be overwritten by an injection volume in the sequence table, this only works for the first injection. Subsequent injections use the method parameter.

Temporary Solution:

n/a

Fix Information:

Solved in LC & CE Drivers A.02.08 SP1

Keyword: Sampler Driver

One-line Description:

Carry over with dual Loop Sampler: Injection cleaning: Rinse volume not set in Firmware

Problem:

The application chemists working with preparative LC (MSD) are struggling with carry over from the dual loop sampler G2258A needle from several months now. 
The carry over is about 10 % as can be seen in the next injection chromatogram. 
For example: After washing the needle, the blue dye of the delay time calibrant is still visible on the needle and in the next run. So, injection cleaning does not seem to work. 
ChemStation C.01.05.036 HF1 and RC.net drivers A.02.07 have been used.
Was found that the firmware command for rinse volume in injection cleaning is not sent to firmware, so it remains to its default value of zero.

Temporary Solution:

n/a

Fix Information:

Solved with LC & CE Drivers A.02.08 SP1

Keyword: Sampler Driver

One-line Description:

For overlapped injections in vial samplers G1313A and G1329A/B, injection volumes and sample locations are not updated synchronously in the status UI

Problem:

For overlapped injections in vial samplers G1313A and G1329A/B, injection volumes and sample locations are not updated synchronously in the status UI. This means that the second sample of an overlapped injection is drawn up already and the UI displays the injection volume of that sample but still the location of the sample which is currently being analyzed is shown

Temporary Solution:

n/a

Fix Information:

With LC driver A.02.10 the UI displays injection volume and sample location of the sample currrently being analyzed.

Keyword: Sampler Driver

One-line Description:

In OpenLAB CDS ChemStation Edition C.01.07 and below, vial positions larger than 50 are not allowed for Vialsamplers G7129A/B

Problem:

In OpenLAB CDS ChemStation Edition C.01.07 and below, vial positions larger than 50 are not allowed for Vialsamplers G7129A/B

Temporary Solution:

n/a

Fix Information:

This issue has been fixed in CDS ChemStation Edition C.01.07 SR1 HF1.

Keyword: Sampler Driver

One-line Description:

Description in user interface has been improved for Smart Overlap and Overlapped injections

Problem:

For the Multisamplers G7167A/B and  the Vialsamplers G7129A/B, the description for Smart Overlap and Overlapped Injections has been changed in the user interface from
"Enable Smart Overlap/Overlapped Injection After Period of Time <x> min" 
to
"Enable Smart Overlap/Overlapped Injection: Draw next sample <x> minutes after injection"
The functionality has not been changed.

Temporary Solution:

not applicable

Fix Information:

not applicable

Keyword: Sampler Driver

One-line Description:

How to handle configuration changes in EZChrom and OpenLAB 2.0

Problem:

In case of configuration changes like using different multisampler drawer types, changing seat capillaries or doing firmware upgrades, these are sometimes not reflected properly when using OpenLAB CDS EZChrom A.04.05, A.04.06 and OpenLAB 2.0 resulting in potential instrument control problems, e.g. modules staying offline or an abortion of a sequence.

Temporary Solution:

As a workaround, OpenLAB CDS EZChrom/OpenLAB 2.0 has to be closed after modifying the instrument configuration using this functionality of the status dashboard. Then, the instrument auto-configuration has to be repeated using the OpenLAB Control Panel.

Fix Information:

Has been fixed in EZChrom A.04.07. and OpenLAB 2.1

Keyword: Sampler Driver

One-line Description:

Older versions of ChemStation cannot handle trays in Vialsamplers G7129A/B with cartesian coordinates

Problem:

Older versions of OpenLAB CDS ChemStation Edition (C.01.04 and below) cannot handle vial trays in vial samplers G7129A/B with cartesian coordinates, i.e. wellplate like formats A1.

Temporary Solution:

For such ChemStation versions, please use so-called classic trays with continuously numbered plates (1 to 50 and 51 to 100). These are dedicated plates which can be ordered as G7129-68210 Drawer-Kit 100 x 2ml Vials Classic.

Fix Information:

This issue is fixed for ChemStation C.01.05 and above.

Keyword: Sampler Driver

One-line Description:

G1329A Autosampler tray types are not updated in Thermo Chromeleon

Problem:

In Thermo Chromeleon software with "Agilent Drivers for Thermo Chromeleon", the tray type is not updated if a tray of a G1329A Autosampler is replaced and if an external tray is configured.

Temporary Solution:

Close the Thermo Chromeleon console. Start the Chromeleon configuration manager. Re-configure the system and manually add the external tray of the autosampler.

Fix Information:

This has been fixed with LC & CE Drivers A.02.15., which will be made available through an upcoming "Agilent Drivers for Thermo Chromeleon" release.

Keyword: Sampler Driver

One-line Description:

Sampling diagram has been removed for Infinity II samplers

Problem:

For previous versions of samplers OpenLAB CDS ChemStation and EZChrom Edition showed a sampling diagram. For Infinity II samplers this functionality has been replaced by the sample entry. 
If the sampling diagram is opened, an empty window is displayed.

Temporary Solution:

N/A

Fix Information:

Use sample entry functionality.

Keyword: Sampler Driver

One-line Description:

Do not use instructions Inject, Valve and Remote in injector programs in case of overlapped injections

Problem:

When using instructions Inject, Valve with parameter "Main Start" or Remote with parameter "Start" in combination with overlapped injections, this may cause a second run start during the initial run. This may result in runs with infinite run times; the dashboard indicates that modules would have completed a run but actually the run continues. Also, several samples may be injected during the same run. 
In the special case of a customer using an injector program which is not intended for the use with overlapped injection, this may result in the injection of a second sample during the same run.

Temporary Solution:

Do not use instructions Inject, Valve and Remote in injector programs in case of overlapped injections

Fix Information:

Since LC driver A.02.16, the combination of these commands with overlapped injections is no longer possible. Runs with such methods will not be started. This may also stop a sequence with such a method.

Keyword: Sampler Driver

One-line Description:

Do not change injection method parameters during overlapped injection

Problem:

Overlapped injection means, that the next sample (injection 2) has already been drawn during the analysis of the current sample (injection 1). It may be possible to change injection parameters like the injection volume or sample location during a run. As the injection of a sample is done by switching the injection valve, changed injection parameters do not affect the injection of a sample, which has been drawn already.
Example:
1. The first injection injects 5  sample
2. During this run, 5 µl of the next sample are drawn per overlapped injection
3. The user changes the injection volume to 2 µl
4. After completion of run 1, the second injection is done with 5 µl (which is the sample volume in the needle/sample loop)
However, an injection volume of 2 µl may be reported for the second run, as the method has been changed before the start of this run.

Temporary Solution:

Changing method parameters during the run always carries a risk, as this may interfere with the current instrument status or ongoing chromatography, e.g. changing a gradient composition or flow rate. Use such functionality with care. Avoid using this functionality during overlapped injection. Agilent OpenLAB CDSs allow restricting the access to this feature (change during run) depending on the user role. This restriction is recommended for standard users.

Fix Information:

Driver A.02.16 and sampler firmware D.07.13 prohibit the change of injection parameters during an overlapped injection by aborting that run.

Keyword: Sampler Driver

One-line Description:

Under special circumstances, wrong injection volumes may be reported for ChemStation sequences of overlapped injections by the Multisampler

Problem:

This may be seen when Multisamplers G7167A/B or G5668A are used in overlapped injection mode in ChemStation sequences. If the injection volume (e.g. 2 µl) is set in the sequence table (line 1) and the subsequent line (line 2) in the sequence table does not set a volume, that injection will use the volume of the method (e.g. 5 µl) in line 2, which is the correct behavior. However the report will show the sequence injection volume (2 µl) of line 1 for the method injection volume (5 µl) in line 2, which may be a different volume. If the third line does not set a volume in the sequence table either, the method injection volume has been changed by the sequence. i.e. 2 µl will be injected and reported, while 5 µl would have been the expected volume.

Temporary Solution:

Do not use G7167A, B or G5668A with overlapped injection in combination with a sequence table that sets the injection volume in ChemStation. Either set the injection volume in the method or in all lines of the sequence table.

Fix Information:

This has been fixed in driver version A.02.16.

Keyword: Sampler Driver

One-line Description:

When a method specifies a wash position, that is physically not available, the method will not be sent to the instrument

Problem:

If a method is used, that specifies a wash position, which is actually physically not available in the current tray configuration (e.g. no tray inserted, tray inserted with different positions or no well-plate assigned), the complete method is NOT sent to the instrument and only a logbook entry is made. 
No error message occurs telling the application/user, that the method was NOT sent to the instrument. When starting a new analysis, this is executed with the previously used method. 
Please consider that the following samplers are NOT affected by this issue: G7167A/B, G5668, G7129A/B, G7157A and G4767A .

Temporary Solution:

Please make sure that the wash position specified in the method is physically available, so that the method can be sent successfully to the instrument.

Fix Information:

This issue will be fixed with driver version A.02.17.

Keyword: Sampler Driver

One-line Description:

Sampler goes offline in rare cases during run

Problem:

Affected modules are: G7129A/B/C, G7157A, G7167A/B, G4767A and G5668A.
If the cooler/thermostat is controlled in the method ("Variable temperature mode (method parameter)"), the sampler goes offline in rare cases (depends on timing) with driver version A.02.19.

Temporary Solution:

Use temperature mode "Constant temperature mode (control setting)".

Fix Information:

The defect is fixed with driver version 3.2.

Keyword: Sampler Driver

One-line Description:

Power cycling a fraction collector in a fraction collector cluster could lead to an offline cluster

Problem:

In rare cases it can happen that the Infinity II Fraction Collector Cluster (FCC) stays offline with the message "Configuration of module <Module Identifier> has changed, but the update within the driver failed (see driver logfile for details)" after one or more modules have been power cycled while the CDS Instrument is connected.

Temporary Solution:

Power cycle any module of the cluster or restart the CDS connected to the instrument.

Fix Information:

Will be fixed with driver version 3.5.

Keyword: Sampler Driver

One-line Description:

Too long sample names cause run to be aborted

Problem:

When entering a sample name with more than 32 ascii characters the run cannot start and the error "Couldn’t download injection parameters. At least one command was not accepted" is shown. The max length varies according to sampler type and also when using, for example, Chinese or Japanese characters.

Temporary Solution:

Reduce size of sample name

Fix Information:

This has been fixed with driver version 3.5

Keyword: Sampler Driver

One-line Description:

Thermostat temperature control mode improvements

Problem:

Thermostat temperature control "Turned off" will be renamed to "Not controlled" to make its function more clear for G1329A/B, G1389A, G1367A/B/C/D/E, G4226A, G1377A, G4303A, G5667A, G2260A, G2258A and G1364A/B/C/D. Furthermore, the thermostat tooltip and setpoint in the dashboard will be changed to display more relevant information.

Temporary Solution:

n/a

Fix Information:

The issue will be fixed with the release of LC & CE Drivers 3.7.

Keyword: Sampler Method

One-line Description:

Method download fails when cooler is controlled in method

Problem:

Affected modules are: G7167A/B, G7129A/B/C, G7157A and G4767A with Sampler Cooler installed.
If the cooler is controlled in the method ("Variable temperature mode (method parameter)"), the method download fails with driver version A.02.19. 
This applies only to modules with Sample Cooler (Option #100) installed. Modules with InfinityLab Sample Thermostat (Option #101) installed, are NOT affected.

Temporary Solution:

Use a driver version prior to A.02.19 or temperature mode "Constant temperature mode (control setting)".

Fix Information:

The defect is fixed with driver version A.02.19 SR1.

Keyword: Sampler Method

One-line Description:

Changes made to the temperature mode in context menu for the G3167A have no effect

Problem:

Changes made to the temperature mode of G3167A via the modify context menu do not take effect.

Temporary Solution:

Restarting the CDS after performing the change solves the problem.

Fix Information:

This has been fixed with driver 3.5.

Keyword: User Interface

One-line Description:

Time table graph of UV Detector ends before run time of system

Problem:

If no explicit stop time has been set for a detector with time table entries defined, the time table graph in OpenLab CDS Chemstation Edition may not show all of the time table entries. This is a display issue only. Measurements are carried out correctly as defined.

Temporary Solution:

Define a stop time in the method UI of the module whose time table entries are not shown correctly in the Time table graph. Setting a stop time will extend the display's time range and the information will be displayed correctly.

Fix Information:

No fix planned.

Keyword: User Interface

One-line Description:

G3162A user interface displays incorrect frequency values for peakwidth

Problem:

The graphical text information of the peakwidth frequency in the G1362A method is incorrect. All used frequencies for the measurements were always correct.
Incorrect value                                         Correct value
0.063 s response time (36.5 Hz)               0.063 s response time (37 Hz)
0.013 s response time (36.5 Hz)               0.013 s response time (37 Hz)
0.25 s response time (36.5 Hz)                 0.25 s response time (37 Hz)
0.5 s response time (18.25 Hz)                 0.5 s response time (18.5 Hz)
1 s response time (9.12 Hz)                      1 s response time (9.26 Hz)
2 s response time (4.56 Hz)                      2 s response time (4.63 Hz)
4 s response time (2.28 Hz)                      4 s response time (2.31 Hz)
8 s response time (1.14 Hz)                      8 s response time (1.16 Hz)

Temporary Solution:

N/A

Fix Information:

This has been fixed with driver version A.02.12