Software Status Bulletin

ELSD RC.Net Driver     G4260A/G4261A, G4260B/G4261B and G7102A

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

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

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

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

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

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

Keyword Glossary

Keyword Index

Keyword: 

One-line Description:

Files are left in the Windows System32 directory after uninstall

Problem:

The following files are not uninstalled when the ELSD driver is uninstalled:

C:\Windows\System32\CDRVDL32.dll
C:\Windows\System32\CDRVHF32.dll
C:\Windows\System32\CDRVXF32.dll

 

Temporary Solution:

n/a

Fix Information:

Fixed with driver version 1.8

Keyword: 

One-line Description:

HT-ELSD existing serial number is not re-applied after firmware update

Problem:

The ELSD firmware resets all parameters to default, including the serial number, when the firmware is updated. The serial number is only set during this process if the user selects the change serial number checkbox. This results in the existing serial number being cleared if the user does not choose the change the serial number.

Temporary Solution:

None

Fix Information:

N/A

Keyword: 

One-line Description:

ChemStation instrument method not updated with LED Intensity change from ELSD UI Method

Problem:

CDS: ChemStation

When making a change to the LED intensity parameter in the ELSD UI Method window (Status UI Right click method option) the software instrument method is not updated. However, when another parameter is changed then the LED intensity parameter is updated correctly.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Correct StateInfoChanged event logic for ELSD 38X

Problem:

CDS: OpenLab CDS 2.2.

The StateInfoChanged event is being fired when there is no change in the state information. This may have performance implications on the host application. OpenLab CDS 2.2 Acquisition Server currently crashes due to the state information variable not being thread safe. This has been fixed in OpenLab CDS 2.2 Hotfix 04.

Temporary Solution:

n/a

Fix Information:

Apply Hotfix 04 to OpenLab CDS 2.2. Alternatively, upgrade to OpenLab CDS 2.3 or later.

Keyword: 

One-line Description:

ELSD method audit trail not fully reported for ELSD 38X

Problem:

Changes to the ELSD LED Intensity parameter and the Evaporator On option are not reported in the method audit trail.

Temporary Solution:

n/a

Fix Information:

None

Keyword: 

One-line Description:

SVT does not check all registry entries

Problem:

The software verification tool (SVT) does not check all the registry entries created by the ELSD drivers.

Temporary Solution:

n/a

Fix Information:

Fixed in driver release 1.8

Keyword: 

One-line Description:

Not all ELSD driver files are checked by SVT

Problem:

Not all the ELSD driver installed files are checked and verified by the software verification tool (SVT). The unreported files are:

C:\Program Files (x86)\Common Files\Polymer Laboratories\els2100com.dll
C:\Program Files (x86)\Common Files\Polymer Laboratories\nlogc.dll
C:\Program Files (x86)\Common Files\Polymer Laboratories\nlog.config
C:\Program Files (x86)\Common Files\Polymer Laboratories\plsendmail.dll

Temporary Solution:

n/a

Fix Information:

Fixed in driver version 1.8

Keyword: 

One-line Description:

Excessive information logged to ELSD log file

Problem:

The ELSD driver can write an excessive number of log messages to the ELSD log file.

Temporary Solution:

n/a

Fix Information:

Fixed in driver version 1.8

Keyword: 

One-line Description:

OpenLab branding

Problem:

The OpenLab branding is incorrect. Replace OpenLAB with OpenLab.

Temporary Solution:

n/a

Fix Information:

Fixed in driver version 1.8

Keyword: 

One-line Description:

ELSD not switched off when using the OpenLab CDS Shutdown method

Problem:

The ELSD is not switched off and put into Standby mode when completing the shutdown method in OpenLab CDS. The ELSD remains in Run mode.

Temporary Solution:

Use a short, shut-down method with the "Switch off at end of run" box checked.

Fix Information:

n/a

Keyword: 

One-line Description:

Support for Walkup software version 4.1

Problem:

The ELSD driver is incompatible with the Agilent WalkUp software version 4.1 when running with Agilent OpenLab CDS 2.

Temporary Solution:

n/a

Fix Information:

Fixed in driver version 1.8

Keyword: 

One-line Description:

Erroneous method parameters values initially seen on first connection to an ELSD upgraded to version 32.xx firmware.

Problem:

After upgrading to version 32.xx of the ELSD firmware, the parameters that were not stored on the instrument prior to the firmware update (see list below) may contain erroneous values which when uploading the method using version A.01.07 or later of the ELSD driver may not show the expected values.

The most likely parameters that exhibit this issue are ‘Stop Time’ and ‘Post Time’ (the user defined times). and on uploading the method from the ELSD using version A.01.07 or later of the driver will be somewhere in the defined range rather than the expected value of 1.00.

Instrument parameters not stored are as follows:
Acquire Signal (< FW Ver 31.06)
Use Stop Time
Stop Time
Use Post Time
Post Time
Autozero at Start of Run
Switch Off at End of Run
Switch Off on Program Exit

Note: The instrument operational parameters (accessed from the keypad) will be retained on upgrading the firmware.

Temporary Solution:

n/a

Fix Information:

The recommendation is to create and download a method from the CDS. The parameters will be updated to valid values on the detector.

Keyword: 

One-line Description:

The Sub Page of the ELSD front panel will prevent communication with a PC.

Problem:

If the front panel display of the ELSD is set to the sub menu (2nd page), it is not possible to connect to the ELSD. The ELSD UI Status dialogue will display the Offline state.

Temporary Solution:

n/a

Fix Information:

Return the ELSD detector to the main page and retry.

Keyword: 

One-line Description:

Control Actions - Switch ON action is Disabled in the ELSD <Device name> menu when the ELSD is in an Error state

Problem:

The Switch ON action is disabled in the ELSD <Device Name> menu, when the ELSD is in an Error state.

Platforms affected: OpenLab ChemStation and EZChrom.

Temporary Solution:

Use the ON button on the status UI or the ELSD right click menu.

Fix Information:

n/a

Keyword: 

One-line Description:

Loss of communications during a sample run

Problem:

Disconnecting the RS232 cable and/or loss of power during a injection causes the following:
• In "Pre-run" and "Run" - the injection is aborted However the next sequence injection loaded runs to infinity. The sequence must be STOPPED, before subsequent injection runs or sequences can be run to completion or the software closed down.
• In "Postrun" - the injection is already completed. Any further injection runs or sequences run to completion without the need to press STOP or close down the software.

Platform affected: OpenLab ChemStation only.

Temporary Solution:

n/a

Fix Information:

None

Keyword: 

One-line Description:

ELSD 380/385 F/W 24.02.00 showing offline state instead of error state

Problem:

Connecting either system configured for a 385 ELSD to a 385 ELSD configured instrument with firmware 24.02.00 or a system configured for a 380 to a 380 configured instrument with firmware 24.02.00 shows the 38x ELSD in an offline state instead of Error 101 Unsupported ELSD firmware.

Platforms: OpenLab ChemStation or EZChrom

Temporary Solution:

The correct error 101 is shown in the instrument logbook.

Fix Information:

n/a

Keyword: 

One-line Description:

ELSD showing offline status instead off Error state

Problem:

Connecting a system configured for a 1260 ELSD to a 380 ELSD configured instrument displays the 380 ELSD in an offline state, the status tooltip shows: Connection condition command Error instead of Error 100 configuration mismatch.

Platforms: OpenLab ChemStation or EZChrom

Temporary Solution:

The correct error 100 is shown in the instrument logbook

Fix Information:

n/a

Keyword: 

One-line Description:

ELSD remains offline when trying to reconnect

Problem:

An ELSD configured as part of a LC instrument may remain offline after the instrument is disconnected and reconnected within a few seconds. All other LC modules are online, but the ELSD remains offline.

Temporary Solution:

After disconnecting the instrument wait 30 seconds before reconnecting the instrument.

Fix Information:

n/a