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: Acquisition

KPR#:146928 ACQUITY: Chromatograms cannot be monitored unless a run is started
KPR#:146972 The response from the ACQUITY is displayed in Absorbance units (Au) while the response from the Acquity driver is measured in milli absorbance unit (mAu).
KPR#:257676 With Waters Alliance LC v6.2.2, every time the sequence is being edited while in a live run, the active run gets truncated (when viewed in DA). The issue was observed with CDS 2.3.
KPR#:293230 Auxilary Traces Might Be Missing from Online Plot in Alliance LC
KPR#:350774 Alliance LC Front Panel Not Locked While Being Controlled by OpenLab CDS
KPR#:355707 Injection source "No injection/instrument blank" is not supported by the Alliance driver
KPR#:379831 Alliance driver: Online Signals are Not Available Outside a Run.

Keyword: Acquisition Audit Trail

KPR#:178180 ACQUITY LC: No unit for flow rate in Method's Audit trail report
KPR#:474435 Alliance LC: Solvent Name in Method Audit Trail
KPR#:1074117 Alliance LC: Absorbance - MBF Does Not Collect Signal in 2695+2489

Keyword: Audit Trail

KPR#:272157 Alliance LC: Events set in UV 2489 and RI 2414 method are not completely displayed in the Method Audit Trail

Keyword: CDS

KPR#:370691 ACQUITY: Some Untranslation in some areas of OpenLab CDS
KPR#:506032 Waters Alliance: Running a Sequence Alternating 2D/3D Methods Throws Error After a Waters DP Upgrade
KPR#:542170 ACQUITY LC: Shutdown Run from the Run Queue Has No Means of Entering a Vial
KPR#:545689 Alliance LC: Submit Shutdown Function Does Not Work for DP-Related Detectors
KPR#:560027 Alliance LC: Aux Trace Names Changed in Data Analysis
KPR#:563805 ACQUITY LC: Next Line in Sequence Locked for Editing

Keyword: Configuration

KPR#:146941 A/D converter configurations are not supported by the Acquity Driver A.01.0x
KPR#:146957 Waters ACQUITY LC: Advanced Mode for Column Manager Not Supported
KPR#:146961 Setting up Sample Organizer needs to be done via ACQUITY Console and not in the OpenLab CDS interface
KPR#:147690 Reconfiguring the existing instruments limitations
KPR#:262882 Alliance LC: Blank method UI
KPR#:420987 Waters ACQUITY LC: change in instrument configuration not tracked in Audit Trail
KPR#:425463 Alliance LC: no method resolution or warning happens upon configuration modification
KPR#:434234 ACQUITY: Cannot disconnect gracefully from the AIC when same modules are used for different instrument configurations
KPR#:515671 Waters ACQUITY LC: Cannot Configure the Instrument From the Client
KPR#:610151 Alliance LC: Unchecking a Detector Method Parameter in Instrument Method Leads to Several Issues

Keyword: External Component

KPR#:370696 Waters ACQUITY Console: Truncation in Chinese Translation
KPR#:590799 Waters Console for Simultaneous Work for ACQUITY and Alliance LC
KPR#:592726 ACQUITY LC: Downgrading Waters DP Makes "Verify Instrument Driver Files Report" Disappear

Keyword: Help

KPR#:146901 Acquity LC: Help is Untranslated

Keyword: Installation

KPR#:147726 ACQUITY LC: Waters DP verification shows modified files on new installation
KPR#:264851 Waters File Verification lists Alliance Driver

Keyword: Instrument Control

KPR#:184699 Waters Alliance timetable graph (expected traces) not displayed properly
KPR#:189194 Error handling is different for Alliance 2695 and e2695 modules
KPR#:191143 ACQUITY TUV signal description contains no wavelength in Online Plot
KPR#:195986 Alliance LC: UV2489 in “Dual” wavelength Mode “Sampling rate” issue
KPR#:233122 Acquity: Gradient Pump Program causes instrument crash if >9 lines
KPR#:262880 Alliance: Waiting for trigger issue (during sequence, empty method)
KPR#:263191 Alliance: “Waiting for Trigger” during sequence (timeout)
KPR#:314653 Alliance LC: The current run is aborted but the sequence continues upon encountering an instrument error
KPR#:316617 Direct Control in ACQUITY driver still possible if instrument is "taken" by another user already
KPR#:345031 ACQUITY LC - Arc QSM-r: No Direct Control Via Instrument Status
KPR#:347461 ACQUITY LC: not possible to use ELSD
KPR#:399172 Alliance LC: Incorrect Gradient When Initial Flow > 0
KPR#:427695 Waters ACQUITY: ELSD does not trigger ready status for acquisition
KPR#:584003 ACQUITY LC: Flow Gradient Starts Before the Start of the Run
KPR#:586851 ACQUITY LC: Sample Manager Does Not Show Correct Value for Set Temperature
KPR#:590444 ACQUITY: Instrument Status of ACQUITY Stays in Prerun for a Run with Flow of 0 ml/min
KPR#:604720 ACQUITY LC: Solvent Composition Not Changed When Initial Flow is Zero
KPR#:636876 ACQUITY LC: Running a Method with PDA/TUV Lamp Off Does Not Switch into Run and Hangs in Aborting State If Aborted
KPR#:1182193 ACQUITY: AutoBlend Plus Method Cannot Be Saved: Root Element Missing

Keyword: Instrument Control,User Interface

KPR#:146987 Waters Console- Sample Manager FTN Interactive display reports false temp setpoint and limits when a Column Manager is connected in an ACQUITY system

Keyword: Localization (Chinese)

KPR#:146888 ACQUITY LC: Audit Trail Content Not Translated
KPR#:569297 ACQUITY LC: Truncations in Instrument Status UI in Chinese Localization

Keyword: Method

KPR#:346052 Truncation in ACQUITY Method UI - Chinese
KPR#:412543 Chinese localization: CDS crashes when wrong number format is entered in ACQUITY
KPR#:569467 Waters ACQUITY (Chinese): Missing Droplist for Column Temperature in CM Method Tab
KPR#:583986 ACQUITY LC: Flow Gradient in Method Not Executed When Initial Flow is 0
KPR#:597439 Waters Alliance: "Autozero" has No Effect on 2475 FLR in 3D Mode
KPR#:698003 ACQUITY LC: Method Printing From Acquisition Might Cause Issues

Keyword: Performance

KPR#:597416 Waters Alliance LC: Waters 2475 FLR Does Not Contain Spectra for the First Few Seconds
KPR#:597427 Waters Alliance LC: 2475 FLR and 2487 UV Signals in DA Shifted Compared to the Online Plot
KPR#:610125 ACQUITY LC: Poor Resolution of PDA 2D Signals in Online Plot
KPR#:710756 Alliance 2489 UV/VIS: Stepwise Online Signal

Keyword: Report Templates

KPR#:379694 Alliance LC: RID 2414 Runtime is Missing in the Method Report
KPR#:639818 ACQUITY LC: ELSD Analog Out "Gas Pressure" Incorrectly Displayed as "Column Heater Temperature" in Method Report

Keyword: User Interface

KPR#:692602 ACQUITY LC: The Instrument Status UI Displays Single Wavelength in Dual Mode

Keyword: 

One-line Description:

Create Content Management Database fails when NT username includes special character

Problem:

OpenLab Server and WorkStation Plus fail to install at the Content Management Database step when the Windows username includes a special character such as ! ' "/[]:;|=,+*?<>.
 

Temporary Solution:

Correct windows login name or connect as a different local administrator and repeat the installation

Fix Information:

n/a

Keyword: Acquisition

One-line Description:

ACQUITY: Chromatograms cannot be monitored unless a run is started

Problem:

Preview run is not supported by this driver version. A signal coming from the Waters Acquity Driver cannot be monitored unless a run is started.  However, AUX Signals can always be monitored.
Applies to all CDSs.

Temporary Solution:

Use AUX signals outside a run.

Fix Information:

Fixed in A.02.01.

Keyword: Acquisition

One-line Description:

The response from the ACQUITY is displayed in Absorbance units (Au) while the response from the Acquity driver is measured in milli absorbance unit (mAu).

Problem:

Currently there is a mismatch between the ACQUITY absorbance untis and those used by the driver. This applies to all CDSs.

Temporary Solution:

n/a

Fix Information:

This is fixed by ACQUITY driver A.02.03.

Keyword: Acquisition

One-line Description:

With Waters Alliance LC v6.2.2, every time the sequence is being edited while in a live run, the active run gets truncated (when viewed in DA). The issue was observed with CDS 2.3. 

Problem:

With Waters Alliance LC v6.2.2, every time the sequence is being edited while in a live run, the active run gets truncated (when viewed in DA). The issue was observed with CDS 2.3. 

Temporary Solution:

 Temporary work around is not to edit the running sequence as this may lead to data loss.

Fix Information:

This is fixed in 6.2.4 version of Alliance driver. This is currently in the test review stage.

Keyword: Acquisition

One-line Description:

Auxilary Traces Might Be Missing from Online Plot in Alliance LC

Problem:

Aux Traces might be missing in the Online plot but are available in Data Acquisition. Both OpenLab EZChrom and OpenLab CDS are affected.

Temporary Solution:

n/a

Fix Information:

This is fixed in Waters Alliance driver v6.3.0 

Keyword: Acquisition

One-line Description:

Alliance LC Front Panel Not Locked While Being Controlled by OpenLab CDS

Problem:

During a run, the keyboard on the Alliance instrument should be locked, which is not the case with the Alliance driver. This is found with Alliance driver v6.2.4 and Open CDS 2.4 but may occur with other versions as well.

Temporary Solution:

n/a

Fix Information:

This is fixed in Waters Alliance driver v6.3.0 

Keyword: Acquisition

One-line Description:

Injection source "No injection/instrument blank" is not supported by the Alliance driver

Problem:

Injection source "No injection/instrument blank" is not supported by the Alliance driver. This applies to all CDSs.

Temporary Solution:

NA

Fix Information:

Blank Run is not supported for Waters 2489 UV/ 2998 PDA/ 2414 RI. Instead, use vial 1 and set injection volume to 0 to perform a blank run.

Keyword: Acquisition

One-line Description:

Alliance driver: Online Signals are Not Available Outside a Run.

Problem:

For the Alliance driver in OpenLab CDS, online signals are not available outside a run.

Temporary Solution:

n/a

Fix Information:

This is fixed in the Alliance driver 6.3.0: 
with the exception of PDA detectors, signals outside a run can now be seen.
For PDA detectors, one needs to use Waters Console outside of OpenLab CDS to monitor the outside of the run PDA signals.

Keyword: Acquisition Audit Trail

One-line Description:

ACQUITY LC: No unit for flow rate in Method's Audit trail report

Problem:

There are no units specified for the flow rate in the Method Audit trail report for ACQUITY instrument. This happens in all CDSs.

Temporary Solution:

n/a

Fix Information:

Fixed in Waters DP2019R2 (comes with ACQUITY A.02.02 and Alliance v6.3.0)

Keyword: Acquisition Audit Trail

One-line Description:

Alliance LC: Solvent Name in Method Audit Trail

Problem:

This happens in all CDSs with Alliance: the solvent names removed in the method show up as blanks in the method audit trail such as "From Acetonitril to "

Temporary Solution:

None

Fix Information:

To be addressed in "Waters Support Layer for Agilent CDS".

Keyword: Acquisition Audit Trail

One-line Description:

Alliance LC: Absorbance - MBF Does Not Collect Signal in 2695+2489

Problem:

MBF feature in Alliance driver 6.3.1 (2695+2489) does not collect signal in OpenLab CDS.

If Absorbance-MBF is selected for the Detector Data Mode for any of the channels, the signal is not collected.

Temporary Solution:

Avoid using the Absorbance - MBF option and use Absorbance instead. If Absorbance is selected, the signal is collected.

Fix Information:

The issue does not occur with Waters Support Layer for Agilent CDS 3.0.0

Keyword: Audit Trail

One-line Description:

Alliance LC: Events set in UV 2489 and RI 2414 method are not completely displayed in the Method Audit Trail

Problem:

Only "Time" information is displayed; information about Event type, Action and Channel are missing. 
However, event settings are correctly displayed for PDA 2998.
The issue appears on all CDSs.
The issue does not appear with UV 2489 on an ACQUITY Arc.

Temporary Solution:

n/a

Fix Information:

This is fixed in Waters Alliance driver v6.3.0 

Keyword: CDS

One-line Description:

ACQUITY: Some Untranslation in some areas of OpenLab CDS

Problem:

When using a Quaternary Pump on Chinese version of OpenLab CDS, some areas of OpenLab CDS are displayed in English instead of Chinese.

Temporary Solution:

There is no workaround.

Fix Information:

There is no fix at this time.

Keyword: CDS

One-line Description:

Waters Alliance: Running a Sequence Alternating 2D/3D Methods Throws Error After a Waters DP Upgrade

Problem:

After an upgrade from the Waters DP 2019 R1 to the Waters DP 2020 R1 has been performed, running a sequence alternating 2D/3D methods causes the sequence to abort when the method changing occurs with the following error:
Destination array is not long enough to copy all the items in the collection. Check array index and length.

Temporary Solution:

Workaround:
Uninstall the older Waters DP prior to installing the newer one. Do not upgrade the DP without the uninstallation first.

Fix Information:

To be addressed in the future revision of Waters DP.

Keyword: CDS

One-line Description:

ACQUITY LC: Shutdown Run from the Run Queue Has No Means of Entering a Vial

Problem:

ACQUITY A.02.02, OpenLab CDS:
Shutdown run type submitted from the Run Queue window does not have any means of entering the vial. The run gets aborted due to Wrong Vial error.

Temporary Solution:

n/a

Fix Information:

Fixed in ACQUITY driver v2.4.

Keyword: CDS

One-line Description:

Alliance LC: Submit Shutdown Function Does Not Work for DP-Related Detectors

Problem:

 If a shtudown method is submitted via "Submit Shutdown" function in OpenLab CDS Run Queue, the run does not end in case a DP related detector (2475, 2414, 2489, 2998) is part of the instrument. The DP detector stays in "Prerun".

Temporary Solution:

Adding the shutdown method to the end of a sequence or submit it as a regular single run works.

Fix Information:

To be addressed in the future Waters DP.

Keyword: CDS

One-line Description:

Alliance LC: Aux Trace Names Changed in Data Analysis

Problem:

Aux Trace Names for Alliance are changing starting in v6.3.1. If an Aux Trace name was used as a filter criteria in previous version, the filter needs to be updated accordingly.

Temporary Solution:

n/a

Fix Information:

Aux Trace Names for Alliance are changed in v6.3.1. If an Aux Trace name was used as a filter criteria in previous version, the filter needs to be updated accordingly.

Keyword: CDS

One-line Description:

ACQUITY LC: Next Line in Sequence Locked for Editing

Problem:

With ACQUITY driver, it is not possible to edit the next line in a sequence after the one currently being "Acquired".

The root cause is that the ACQUITY driver has no insight in the method settings and cannot say for each method if "Load ahead" is enabled or disabled. Instead, the Acquity driver reports to the CDS for EVERY method that it is capable of Load Ahead resp. Overlap injection.

Hence, the following conditions must be met for this issue to be observed:
 1. "Load Ahead" in Method is disabled (otherwise this behavior is as designed)
 2. Methods in sequence are identical (CDS will not trigger overlap injection if different methods are being used)

Temporary Solution:

n/a

Fix Information:

Fixed in ACQUITY driver v2.4.

Keyword: Configuration

One-line Description:

A/D converter configurations are not supported by the Acquity Driver A.01.0x

Problem:

The Acquity driver versions A.01.xx for OpenLab CDS currently do not allow adding A/D converters to the instrument configuration.

Temporary Solution:

n/a

Fix Information:

Fixed in Acquity driver A.02.01.

Keyword: Configuration

One-line Description:

Waters ACQUITY LC: Advanced Mode for Column Manager Not Supported

Problem:

 Waters Column Managers' Advanced Mode is not supported with ACQUITY driver.

Temporary Solution:

N/A

Fix Information:

None

Keyword: Configuration

One-line Description:

Setting up Sample Organizer needs to be done via ACQUITY Console and not in the OpenLab CDS interface

Problem:

There are two ways to set up the plate configuration:
1. Click on "Plate Configuration..." in "Instrument Actuals" window in the OpenLab CDS Interface
2. Open the Acquity Console from "Instrument Actuals" window and select  "Sample Manager"  on the left-hand side and open the Plate Setup window via main menu by selecting "Configure" > "Plate setup..."

Using a Sample Organizer it is not possible to set up the plates from the driver's UI (point 1 above). 
This interface offers only the configuration from two of the nine plates. Using this interface and closing the window with ok, all Plate 3 to Plate 9 will be lost.
This applies to all CDSs.

Temporary Solution:

n/a

Fix Information:

One can no longer change the plate setup through the button "Plate Configuration..." in "Instrument Actuals". The change is only allowed via the Waters ACQUITY console.

How to assign the Sample Organizer to the Sample Manager:
1. Open the Acquity Console from the "Instrument Actuals"
2. Select the "Sample Manager" on the left-hand side
3. open the Sample Organizer Configuration window via main menu by selecting "Configure" > "Sample Organizer..."
4. Select the Serial number of the Sample Organizer and close the window with "OK"

Keyword: Configuration

One-line Description:

Reconfiguring the existing instruments limitations

Problem:

For ACQUITY, the instrument might not get online properly after reconfiguring an existing instrument should its configuration be changed. The issue happens in all CDSs.

Temporary Solution:

Use either of the two possible work arounds:
1. Reboot the controller after reconfiguring the existing instruments via OpenLab Control panel if their configuration has changed before starting to use these instruments.
2. Use a unique name in "System Name" text box in configuration UI when changing  the modules list.

Fix Information:

n/a

Keyword: Configuration

One-line Description:

Alliance LC: Blank method UI

Problem:

While creating a new method or after opening a method on the instrument, click on detector tab below Alliance 2695,
 sometimes method UI for the detector is not populating. Issue appears on OpenLab CDS 2.3.

Temporary Solution:

n/a

Fix Information:

This is fixed in Waters Alliance driver v6.3.0 

Keyword: Configuration

One-line Description:

Waters ACQUITY LC: change in instrument configuration not tracked in Audit Trail

Problem:

With Waters ACQUITY LC driver in all three CDSs, the change in instrument configuration is not tracked in Audit Trail. This applies to both module addition/removal and module exchange.

Temporary Solution:

Keep the configuration constant. If a new configuration is needed, create a brand new instrument.

Fix Information:

Fixed in ACQUITY v2.4 revision.

Keyword: Configuration

One-line Description:

Alliance LC: no method resolution or warning happens upon configuration modification

Problem:

This only happens when another module is added to the configuration, on all CDSs. Then when starting a run, if no manual resolution is done, the run on the newly added module will be done with the default parameters.

Temporary Solution:

n/a

Fix Information:

This is fixed in the Alliance driver v.6.3.1

Keyword: Configuration

One-line Description:

ACQUITY: Cannot disconnect gracefully from the AIC when same modules are used for different instrument configurations

Problem:

Sometimes when different detectors need to be used and the two different instrument configurations are being switched between, the instrument would not come on-line easily. This happens due to the fact that some ACQUITY processes linger in the background. Simply power cycling the AIC and the instrument after the switching between the two instrument configurations does not always help.

Temporary Solution:

Instead of rebooting the AIC, run the "StopProcesses.exe" included in the Waters DP (usually in C:\Program Files (x86)\Waters Instruments\Bin).
(Note: This will affect all Waters instruments on the same AIC).
One needs to have administrator privileges (right click -> run as Administrator) to perform this task.
After that, in case the instrument is launched but the modules still show "Communication failure" in the instrument status, perform the right-click on the module in the Status UI and choose "Reset <module>" from the context menu.

Fix Information:

There is currently no fix for this.

Keyword: Configuration

One-line Description:

Waters ACQUITY LC: Cannot Configure the Instrument From the Client

Problem:

In an OpenLab CDS client/server environment, it is not possible to configure a Waters Acquity instrument from the client.
A message "Please check your Server Hostname IP Address and Acquity System Name" appears if the instrument is being configured from the client. 

Temporary Solution:

Configure the instrument from the AIC.

Fix Information:

N/A

Keyword: Configuration

One-line Description:

Alliance LC: Unchecking a Detector Method Parameter in Instrument Method Leads to Several Issues

Problem:

When the Waters Driver Pack (2022 R1) is installed in typical mode (complete installation), a checkbox with detector name appears in detector method.
Unchecking this checkbox means that detector is not used for an acquisition. It means the detector is not included in the configuration anymore.
This leads to several issues:
1. Configuration mismatch: a run cannot be started with a method with detector unchecked due to a configuration mismatch error.
2. Method resolution: every time a method with detector unchecked is opened, method resolution screen is displayed.
3. Method print: method is not printed for unchecked detector.

Temporary Solution:

n/a

Fix Information:

To be addressed n the future revision of the Alliance driver/Waters DP.

Keyword: External Component

One-line Description:

Waters ACQUITY Console: Truncation in Chinese Translation

Problem:

For the Chinese localization, there are several truncations that produce a different meaning in the Waters ACQUITY console window under the Sample Manager module. For the Column and Sample Temperature it should display "Off" instead of "day".

Temporary Solution:

None

Fix Information:

There is no fix available at this point.

Keyword: External Component

One-line Description:

Waters Console for Simultaneous Work for ACQUITY and Alliance LC

Problem:

If a Waters Console is first opened for Alliance and THEN for ACQUITY, both Consoles can be opened without issues.
However, if a Waters Console is first opened for ACQUITY and then for Alliance, a message "Waters Console is already launched. Please wait for the window to appear" is shown. 

Temporary Solution:

At this point one can close the Waters Console for ACQUITY, and the Alliance Console can be opened without issues.

Fix Information:

N/A

Keyword: External Component

One-line Description:

ACQUITY LC: Downgrading Waters DP Makes "Verify Instrument Driver Files Report" Disappear

Problem:

After downgrading the Waters DP, the "Verify Instrument Driver Files Report" might disappear from the Start Menu.

Temporary Solution:

One can run the VerifyICSFiles.exe utility from
C:\ProgramFiles(86)\WatersInstruments\Utilities

Fix Information:

To be addressed by the future revisions of Waters DP.

Keyword: Help

One-line Description:

Acquity LC: Help is Untranslated

Problem:

Acquity LC help is untranslated.

Temporary Solution:

None

Fix Information:

This is fixed in Waters SL for Agilent CDS control 3.0.

Keyword: Installation

One-line Description:

ACQUITY LC: Waters DP verification shows modified files on new installation

Problem:

Waters DP verification shows modified files on new installation (for ACQUITY driver). This happens in all CDSs.

Temporary Solution:

n/a

Fix Information:

Fixed with Waters DP2019R2 (comes with ACQUITY driver A.02.02 and Alliance v6.3.0)

Keyword: Installation

One-line Description:

Waters File Verification lists Alliance Driver

Problem:

Waters File Verification report lists the Waters Alliance driver as an Installed Instrument, which should not be the case.
Also, uninstalling the Waters DP will start but not gracefully finish the uninstalling of the Alliance driver. This issue only appears on EZChrom and OpenLab CDS.

Temporary Solution:

Fix Information:

This is fixed in Waters Alliance driver v6.3.0 

Keyword: Instrument Control

One-line Description:

 Waters Alliance timetable graph (expected traces) not displayed properly

Problem:

The method editor time graph for Waters Alliance 2695 gradient is not displayed properly when the curve is set to anything other than 6. THis happens in all CDSs.

Temporary Solution:

n/a

Fix Information:

This is fixed in Waters Alliance driver v6.3.0 

Keyword: Instrument Control

One-line Description:

Error handling is different for Alliance 2695 and e2695 modules

Problem:

Errors are handled differently by W2695 and e2695. 
For Alliance instruments, a column heater provides an error message and a severity for this error (Warning or Error) depending on the instrument. The run is aborted in case of an 2690/2695 but not with an e2695. It's working as designed and therefore won't be fixed.

Temporary Solution:

This issue is described in the Installation & User Guide.

Fix Information:

There is not fix for it. This is working AS DESIGNED.

Keyword: Instrument Control

One-line Description:

ACQUITY TUV signal description contains no wavelength in Online Plot

Problem:

TUV signal description does not contain the wavelength that is used for acquisition in the Online Plot window.

Temporary Solution:

This is planned to be fixed in the future revisions of the driver. The instrument setup method report contains the information on the wavelength that was used for TUV.

Fix Information:

There is no workaround at this time.

Keyword: Instrument Control

One-line Description:

Alliance LC: UV2489 in “Dual” wavelength Mode “Sampling rate” issue

Problem:

For the UV 2489 detector configured in “Dual” wavelength Mode (in the method), if the user changes the “Sampling rate” value in the Channel A tab, he also has to check the Channel B tab settings before closing the method window. 

The “Sampling rate” parameter is linked to the filter time constant parameter. For the same filter type, the filter time constant value is different for a sampling rate of 1 Hz or 2 Hz. For example, for a sampling rate of 1 Hz, for the “Normal” filter, the corresponding time constant value is 2 sec, for 2Hz, this value is equal to 1 sec. 

If the sampling rate parameter is modified in Channel A tab and if the user doesn’t check the Channel B tab, the method keeps in memory the filter time constant value set before the modification and the filter type will change for Channel B (in the last example, changing sampling rate from 1Hz to 2Hz will change the filter type as “Slow” instead of “Normal” for Channel B. The method kept 1 sec as time constant value and its corresponds to the “Slow” filter.)
This issue is observed on all CDSs.

Temporary Solution:

Fix Information:

Fixed with Waters DP2019R2 (comes with ACQUITY driver A.02.02 and Alliance v6.3.0)

Keyword: Instrument Control

One-line Description:

Acquity: Gradient Pump Program causes instrument crash if >9 lines

Problem:

When loading a method with 10 lines or more in QSM gradient program, the instrument crashes.

Temporary Solution:

n/a

Fix Information:

Fixed in DP2017 R2 SR1.

Keyword: Instrument Control

One-line Description:

Alliance: Waiting for trigger issue (during sequence, empty method)

Problem:

Description: During a sequence, it is observed that the sequence gets stuck with the “Waiting for Trigger” status when moving to the next line that uses a different method. Investigation of log files showed that a method with empty parameters for the detector was passed from CDS.

Temporary Solution:

n/a

Fix Information:

This is fixed in Waters Alliance driver v6.3.0 

Keyword: Instrument Control

One-line Description:

Alliance: “Waiting for Trigger” during sequence (timeout)

Problem:

During a sequence, it is observed that the sequence gets stuck with the “Waiting for Trigger” status. Investigation showed that the instrument runs into a timeout that is implemented in the driver.

Temporary Solution:

n/a

Fix Information:

This is fixed in Waters Alliance driver v6.3.0 

Keyword: Instrument Control

One-line Description:

Alliance LC: The current run is aborted but the sequence continues upon encountering an instrument error

Problem:

If a fatal error occurs on a detector of an Alliance system, the current run gets aborted but the subsequent runs of the sequence continue.
Fatal errors should lead to abortion of the entire sequence.
This was observed in OpenLab CDS but might have similar behavior in all other CDs.

Temporary Solution:

N/A

Fix Information:

This behavior has been changed in Alliance driver v6.2.5. Fatal errors now lead to abortion of the entire sequence, and not just the current run.

Keyword: Instrument Control

One-line Description:

Direct Control in ACQUITY driver still possible if instrument is "taken" by another user already

Problem:

With ACQUITY A.02.01 and OpenLab CDS 2.4, it is possible to perform Direct Control actions in the Instrument Status window by another user even when the first user "blocked" the instrument with the "Take" functionality.

Temporary Solution:

n/a

Fix Information:

This is fixed with ACQUITY A.02.02.

Keyword: Instrument Control

One-line Description:

ACQUITY LC - Arc QSM-r: No Direct Control Via Instrument Status

Problem:

With Waters DP2019R2 (used with ACQUITY A.02.02), the Instrument Status for QSM-r (Arc pump) always displays flow  as 0 and each solvent at 100%. 
Direct control pop up cannot be opened and stop flow button does not work.

Temporary Solution:

Fix Information:

This is fixed in Waters Driver Pack DP 2020 R1.

Keyword: Instrument Control

One-line Description:

ACQUITY LC: not possible to use ELSD

Problem:

It is not possible to use ELS Detector with Acquity driver A.02.01 and OpenLab CDS, OpenLab ChemStation and EZChrom editions.
An error message is given: InitializeDeviceForRun() failed! when trying to submit a run for the instrument that has ELSD.

Temporary Solution:

n/a

Fix Information:

Fixed in ACQUITY driver A.02.02

Keyword: Instrument Control

One-line Description:

Alliance LC: Incorrect Gradient When Initial Flow > 0

Problem:

The gradient start is not detected at the correct time if the initial flow is not 0.
◦In case of a real injection, this means the detectors will lag at the beginning of the gradient; the gradient aux trace / monitor trace will be shifted (in time) compared to expected trace.

◦In case of a blank run, the gradient aux trace / monitor trace will be shifted (in time) compared to expected trace.

Delaying the start of the gradient has no effect on data acquisition since except increasing injection length all detectors will start when injection occurs.

Temporary Solution:

NA

Fix Information:

This is working AS DESIGNED. No fix is available.

Keyword: Instrument Control

One-line Description:

Waters ACQUITY: ELSD does not trigger ready status for acquisition

Problem:

The issue was observed only on one customer system that has OpenLab EZChrom A.04.09, Waters DP2017R2 and Acquity A.02.01 driver, where it is reproducible. The issue was not reproducible on analogous test systems.
When ELSD is in the configuration, system does not switch into the run mode and stays in "Waiting for trigger". The issue does not occur if ELSD is not part of the configuration.
It is likely the issue might also be observed with ACQUITY Driver A.02.02 that uses Waters DP 2019 R2 since the fix was not incorporated into this driver pack yet.

Temporary Solution:

n/a

Fix Information:

This is addressed in the Waters Driver Pack 2020 R1 (comes with ACQUITY A.02.03)

Keyword: Instrument Control

One-line Description:

ACQUITY LC: Flow Gradient Starts Before the Start of the Run

Problem:

There is an offset between the actual flow gradient and the settings for it in the pump tab of the method setup. The flow rises already before the start of the run and is not synchronous with the solvent gradient.

Temporary Solution:

If the gradient is starting before injection, an offset can be entered in the method setup under the "Misc" tab of the pump as following:
change the Gradient Start settings to "After Injection"
choose "min" as unit (also uL is listed as option)
enter an appropriate value for the desired offset.

Fix Information:

Not planned as there is a workaround.

Keyword: Instrument Control

One-line Description:

ACQUITY LC: Sample Manager Does Not Show Correct Value for Set Temperature

Problem:

In some cases, the Dashboard for the Sample Manager does not show the correct value for the set in the Method Setup temperature, but the set value is correct (also, Waters Instrument Console shows the correct value).

Temporary Solution:

Waters Instrument Console shows the correct value for the temperature.

Fix Information:

To be addressed in the future revisions of Waters DP.

Keyword: Instrument Control

One-line Description:

ACQUITY: Instrument Status of ACQUITY Stays in Prerun for a Run with Flow of 0 ml/min

Problem:

If a method with initial zero flow (in the pump timetable) is used, the instrument status shows it is in Prerun state although the Waters console displays the elapsed time of the run. Upon completion of such run, the run needs to be aborted manually as otherwise the Prerun status persists.

Temporary Solution:

Use the following workaround:
If the initial pump flow is > 0, one could still create a functional shutdown method with a time program which turns the flow to 0 after the run has started. This run will end normally.

Fix Information:

To be addressed in the future revision of Waters Driver Pack/ Driver.

Keyword: Instrument Control

One-line Description:

ACQUITY LC: Solvent Composition Not Changed When Initial Flow is Zero

Problem:

When the initial solvent gradient flow is zero, the changes to the % solvent via a direct control are not applied.
Similarly, when a method with the initial flow of zero is downloaded to the instrument, the previous % solvent is kept. 
When a method with a flow and solvent gradient with the initial flow of zero is run, the solvent gradient is not executed, the % solvent before the beginning of the run is kept.

Temporary Solution:

Do not use a zero initial flow to avoid such situation.

Fix Information:

This is fixed in Waters Support Layer for Agilent CDS Control 3.0.

Keyword: Instrument Control

One-line Description:

ACQUITY LC: Running a Method with PDA/TUV Lamp Off Does Not Switch into Run and Hangs in Aborting State If Aborted

Problem:

When submitting a method that has the PDA/TUV Lamp disabled in the method, the lamp goes off after the method has been downloaded.
However, immediately after, the lamp is ignited again. The run does not start. The Run Queue stays in "Acquiring" while the Instrument State is on "Idle". In the Status UI and in the Waters Console, no pre-run actions are performed.
When aborting this run manually, it stays in "Aborting" state. Instrument connection cannot be gracefully closed. AIC/Workstation needs to be restarted to bring the system in a proper state again.
This issue is reported with DP2020R1.

Temporary Solution:

The workaround to turn off the lamp in a method is to use the PDA/TUV timetable and turn the lamp off with an event.

Fix Information:

Fixed in Waters SL for Agilent CDS Control 3.0.

Keyword: Instrument Control

One-line Description:

ACQUITY: AutoBlend Plus Method Cannot Be Saved: Root Element Missing

Problem:

When using the Auto•Blend Plus function with Waters Acquity (Arc) instrument, upon saving the method the following error message is shown: "Cannot save the method. Root element is missing."

Temporary Solution:

There is no known workaround.

Fix Information:

This is reported to Waters.

Keyword: Instrument Control,User Interface

One-line Description:

Waters Console- Sample Manager FTN Interactive display reports false temp setpoint and limits when a Column Manager is connected in an ACQUITY system

Problem:

When using the Waters Console and viewing the Sample Manager FTN, the Interactive display reports false temp setpoint and limits when a Column Manager is connected in an Acquity system.
This applies to all CDSs.

Temporary Solution:

n/a

Fix Information:

This is fixed in Acquity driver A.02.01.

Keyword: Localization (Chinese)

One-line Description:

ACQUITY LC: Audit Trail Content Not Translated

Problem:

OpenLab EZChrom: Audit Trail content for Waters Acquity Instrument is not translated.

Temporary Solution:

None.

Fix Information:

Issue depends on Waters DP provided by Waters. This has been reported to Waters for consideration.

Keyword: Localization (Chinese)

One-line Description:

ACQUITY LC: Truncations in Instrument Status UI in Chinese Localization

Problem:

On Chinese systems, truncation issues can occur in the Instrument Status UI. 

Temporary Solution:

As a workaround, open the Waters Console from the Status UI and check the truncated values there.

Fix Information:

To be addressed in the future revision.

Keyword: Method

One-line Description:

Truncation in ACQUITY Method UI - Chinese

Problem:

On Chinese systems (with Waters DP2017R2 SR1 and higher), the Method UI for some Waters modules is truncated so that the comment line at the bottom of the UI is not completely visible and readable. This happens in all CDSs.

Temporary Solution:

Workaround: If one opens the comment pop up (on the bottom of the screen)by clicking on the button right to the input line, the whole content of the comment line is visible and editable.

Fix Information:

There is no fix available a this point. 

Keyword: Method

One-line Description:

Chinese localization: CDS crashes when wrong number format is entered in ACQUITY

Problem:

All three CDSs (EZChrom, ChemStation, OpenLab CDS) crash when wrong number format is entered in the method. This only happens in Chinese localization systems. All other systems perform input validation gracefully and display an error message.

Temporary Solution:

There is no work around except to avoid the incorrect input and save the method frequently upon changes.

Fix Information:

There is no fix available at this point.

Keyword: Method

One-line Description:

Waters ACQUITY (Chinese): Missing Droplist for Column Temperature in CM Method Tab

Problem:

Waters driver ACQUITY A.02.03:
In the method editor, the dropdown list for CM column temperature does not have any options.

Temporary Solution:

One can either enter a temperature in the field or type "关" for "Off".

Fix Information:

To be addressed in the future Waters DP.

Keyword: Method

One-line Description:

ACQUITY LC: Flow Gradient in Method Not Executed When Initial Flow is 0

Problem:

If the initial flow in the pump gradient program starts at 0, once the run is submitted, the system stays in a Prerun state and the flow program does not proceed further staying at 0 flow.

Temporary Solution:

Do not use methods with gradients starting from zero or runs where the flow is 0 throughout the whole run.

Fix Information:

None

Keyword: Method

One-line Description:

Waters Alliance: "Autozero" has No Effect on 2475 FLR in 3D Mode

Problem:

Timed event "autozero"  on Waters 2475 FLR detector has no effect in 3D mode.

Temporary Solution:

None.

Fix Information:

To be addressed by Waters Driver Pack.

Keyword: Method

One-line Description:

ACQUITY LC: Method Printing From Acquisition Might Cause Issues

Problem:

When printing a method setup using a Printer icon ("Open print dialog") causes an error in opening the file. This happen, when there was no printer previously configured, which can be used from the system.

Temporary Solution:

- Instead of using a Printer icon, use Export button to print a method as PDF to a file.
- Configure a printer before using the Printer icon

Fix Information:

N/A

Keyword: Performance

One-line Description:

Waters Alliance LC: Waters 2475 FLR Does Not Contain Spectra for the First Few Seconds

Problem:

Data recorded with a Waters 2475 FLR detector does not contain spectra for the first part of (ca. 0.1 min) of a run.

Temporary Solution:

There is no fix

Fix Information:

This is a firmware issue.

Keyword: Performance

One-line Description:

Waters Alliance LC:  2475 FLR and 2487 UV Signals in DA Shifted Compared to the Online Plot

Problem:

The time axis of Waters 2475 FLR and Waters 2487 UV detector signals in the DA chromatogram is shifted compared to the online plot. As a consequence, the peaks have a lower retention time in the online plot compared to the one in the final chromatogram.

Temporary Solution:

The Data Analysis chromatogram has the real retention time.

Fix Information:

To be addressed in the future revision of the driver.

Keyword: Performance

One-line Description:

ACQUITY LC: Poor Resolution of PDA 2D Signals in Online Plot

Problem:

For PDA and 2998PDA, if 3D Data is not enabled, the Online Plot comes in a poor resolution (1 point per second) for the 2D signals.
The Data Analysis shows the correct traces with full resolution.
The issue does not occur if 3D Data is enabled.

Temporary Solution:

n/a

Fix Information:

Fixed in ACQUITY driver v2.4.

Keyword: Performance

One-line Description:

Alliance 2489 UV/VIS: Stepwise Online Signal

Problem:

The online plot does not look smooth and has steps. However, the signal is not affected when looked at from the Data Analysis.

Temporary Solution:

Use Data Analysis to review the data instead of Online signal.

Fix Information:

Fixed in Waters SL for Agilent CDS driver 3.0.

Keyword: Report Templates

One-line Description:

Alliance LC: RID 2414 Runtime is Missing in the Method Report

Problem:

In OpenLab CDS, the runtime for RI detector 2414 is missing.

Temporary Solution:

n/a

Fix Information:

This is fixed in Waters Alliance driver v6.3.0 

Keyword: Report Templates

One-line Description:

ACQUITY LC: ELSD Analog Out "Gas Pressure" Incorrectly Displayed as "Column Heater Temperature" in Method Report

Problem:

In the ELSD method, in the "Analog Out" tap, there are three selections for the auxiliary output: Nebulizer Temperature, Drift Tube Temperature, and Gas Pressure.

If "Gas Pressure" is selected, a printed method report incorrectly displays "Column Heater Temperature" as Auxiliary Output Source.

Temporary Solution:

None

Fix Information:

To be addressed in the future Waters DP.

Keyword: User Interface

One-line Description:

ACQUITY LC: The Instrument Status UI Displays Single Wavelength in Dual Mode

Problem:

The Instrument Status UI displays only one wavelength in dual mode.

Temporary Solution:

Use Waters Console, it shows the information for both channels.

Fix Information:

To be addressed in future Waters DP