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: 

One-line Description:

User with restricted permission in CDS can modify in Assist Control Softare

Problem:

A user which can log into a CDS with his user account and log into the Assist Control Software with one of the available roles may be able to modify method parameters (e.g. Flow) in the Assist Control Software, despite not being permitted to in the CDS.

Temporary Solution:

CDS permissions and the Assist Control Software are independent.
If the users role on the Assist Control Software has to many permissions, assign a proper role with less permissions.

Fix Information:

n/a

Keyword: 

One-line Description:

A task on Assist Hub can be started during a monitor run in Empower

Problem:

If a task on Assist Hub is started during a LC monitor run in Empower, the monitoring and task execution run in parallel.

Temporary Solution:

n/a

Fix Information:

System has to be rebooted to get LC instrument idle again. Or a sequence/sample set can be started to abort the monitoring.

Keyword: 

One-line Description:

Search in context help may fail on Assist Control Interface

Problem:

The search in the context help might fail when executed on the Assist Control Interface

Temporary Solution:

n/a

Fix Information:

Fixed in 2.0

Keyword: 

One-line Description:

Run Control shows different run times on Assist Interface and in PC browser

Problem:

When comparing the task (e.g. Make Ready) run times in the Run Control between the Assist Interface at the instrument and in a PC browser window, the run times are not identical.
This happens when the times on the Assist Hub or the time on the PC are not correctly set - most likely because Assist Hub Date & Time Source is set to "Manual"

Temporary Solution:

Ensure:
- PC correctly receives time from a Time Server
Check
- in Assist Control Software - Settings - General - Date & Time: Set Date & Time Source to NTP (Network Time Protocol) when the Assist Hub can reach a time server in the network/internet
- in Assist Control Software - Settings - General - Date & Time: Set Date & Time Source to CDS when LC Driver with revision >= 3.8 is installed in the CDS - the driver will then provide the time from the CDS server PC

Fix Information:

Fixed in 2.0 - Assist Hub web page shows warning on long time difference 

Keyword: 

One-line Description:

Some CDS is not able to connect when HTTPS/TLS active

Problem:

Some CDS (e.g. MassHunter) are not able to connect when HTTPS/TLS active on the Assist Hub.
HTTPS/TLS certificates are bound to hostnames. If the CDS only supports connections via IP addresses instead of hostnames a secure connection cannot be established.

Temporary Solution:

Several possibilities:
- Setup CDS connection to use hostname instead of IP address (if possible)
- Deactivate HTTPS/TLS in Assist Hub
- Create Certificates bound to instrument IP addresses. However, that is not best practices and not recommended

Fix Information:

n/a

Keyword: 

One-line Description:

Page refresh required when turning off HTTPS/TLS

Problem:

When HTTPS/TLS is active in the Assist Control Software and then turned off via Settings - Security - HTTPS/TLS, it is no longer possible to log into the Assist Control in the same browser session from external devices.

The Assist Control Interface not affected.

Temporary Solution:

n/a

Fix Information:

Fixed in 2.0

Keyword: 

One-line Description:

Make Ready task passes despite pump doing auto flow reduction

Problem:

When "Make Ready" task is configured with a high pressure limit less than the back pressure resulting from the configured flow and instrument characteristics, the pump will try to go into "auto flow reduction" to meet the high pressure criteria.
In such cases, the pump will show a not ready, but the "Make Ready" task will continue to execute the equilibration step nevertheless.
Depending on the configured criteria the task might end with a success message, despite the auto flow reduction being active.

Temporary Solution:

Ensure the configured High Pressure Limit for the Equilibration step is high enough for the configured flow and there are no blockages in the system flow path.

Fix Information:

Will be fixed in the next revision.

Keyword: 

One-line Description:

System Pressure test aborts when G7167 Multisampler with Dual Needle option and bypassed needle(bypass capillary)

Problem:

System Pressure Test aborts with "Aborted by System" at the end of the test under following conditions:
G7167A/B Multisampler with Dual needle option is in system and the sampler has a bypassed needle and the bypassed needle(bypass capillary) position is selected in the System Pressure Test configuration step.
If the leak measurement succeeded, a result value is shown and checked against the limit, but while finalizing the error occurs

Temporary Solution:

As workaround, configure the desired path in advance and do not select the Sampler in the System Pressure Test configuration step

Fix Information:

Will be fixed in the next revision

Keyword: 

One-line Description:

Assisted Troubleshooting may fail after rebooting detector module

Problem:

Assisted Troubleshooting of a "Lamp Ignition Failed" error may fail during Verification step when the detector module had been turned off as part of the "Replacing the lamp" procedure. Abort reason is "Attempt to launch a sub procedure..."

Temporary Solution:

Workaround: When Verification step failed, cancel the Assisted Troubleshooting, navigate to Status screen, use the "Switch On Lamp" quick action and navigate to Health - Diagnostics - Intensity test to manually verify the new lamp.

Fix Information:

Fixed in 2.0

Keyword: 

One-line Description:

Task Scheduling Discrepancy While Choosing Days of the Week 

Problem:

When scheduling tasks, the instrument chooses the day of the week based on the UTC time zone. If the user schedules a time of day in their time zone that has a different day of the week in the UTC time zone, the task will run at the time scheduled, but on the wrong day of the week.

Temporary Solution:

When scheduling tasks, compare the time zone of the instrument with the UTC time zone to determine which day of the week the task will run.

Fix Information:

Fixed in 1.1

Keyword: 

One-line Description:

Make Ready / Standby flush steps limiting run time

Problem:

During execution of Make Ready or Standby Task, the steps Pre-Flush, Flush System and Store Column will complete after one hour when configured flush volume and pump flow result in a flush time greater than 1h.
The time limit is not visible in the configuration UI or the generated result.

Temporary Solution:

Ensure the configured run time resulting of flush volume and pump flow do not exceed 1h.

Fix Information:

Fixed in 2.0 by limiting the maximum flush time to 3 h. 
Configuration UI will show a warning when volume and flow result in longer time. Existing tasks will be flagged as invalid and cannot be started - adjusting the configuration and saving the valid task will allow starting again.

Keyword: 

One-line Description:

Assist Hub failing to Update FW of G7158B Sampler

Problem:

Assist Hub fails during FW update (e.g. in finalization after Assist Hub update).

Workaround: 
First: Use Agilent Lab Advisor and connect via mini-USB cable to the G7158B sampler (or other module in stack with mini-USB connector) and update to latest FW.
Next: Then update the Assist Hub to the new version - which will then update the remaining module FW (if required)

Temporary Solution:

n/a

Fix Information:

Will be fixed in next revision

Keyword: 

One-line Description:

Assist Control software shows delayed MS Status for iQ Pro MS

Problem:

Users may observe that the MS status in Assist control software (e.g., Idle or Not Ready) does not immediately match the status shown in CDS, especially during startup or method transitions. 

This behavior is due to differences in how each application determines the MS status:
CDS uses detailed method information to calculate the status.
Assist control software receives a simplified status directly from the instrument, which does not include method-specific context.

As a result, there can be a delay between the two systems. This is a known limitation and does not affect instrument performance.

Temporary Solution:

n/a

Fix Information:

The issue will be addressed in the next releases.

Keyword: 

One-line Description:

iQ Pro Tune status not updated after using Tune Control in MS Drivers

Problem:

When users activate Tune Control or run Autotune from CDS, the MS status in Assist may remain Idle, even though tuning is in progress. This can lead to confusion about whether the instrument is actively tuning.

This issue occurs because Assist and CDS use different systems to determine MS status. CDS uses a detailed driver-based logic, while Assist relies on a simplified status from the instrument. The Tune process includes steps that are only visible to CDS, and not reflected in the status Assist receives.

What this means for users:

The MS is tuning correctly, even if Assist shows Idle.
There may be a delay or mismatch in status updates between CDS and Assist during tuning.
This is a known limitation and does not affect the tuning process or results.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Issue with Exported File Names from Make Ready or Standby Tasks on USB

Problem:

We have identified an issue that affects the export of results from Make Ready or Standby tasks to a USB drive, regardless of whether the export is initiated via Assist or the Assist Interface.

When a task name contains Chinese or Japanese characters, a file exported via USB will show up with unreadable characters in Windows OS.

Temporary Solution:

Workaround: Rename the file when copying from USB stick to OS file system

Fix Information:

Investigating possibilities to ensure consistent file name readability across platforms with next releases.