Chromeleon-PA Analyzer User’s Guide€¦ · Chromeleon-PA Analyzer 2 Doc. 031964-01 10/03 •...

Chromeleon-PA AnalyzerUser’s Guide

© 2003 Dionex Corporation

Document No. 031964Revision 01

October 2003

Anuta

New Stamp

©2003 by Dionex CorporationAll rights reserved worldwide.Printed in the United States of America.

This publication is protected by federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system, or transmitted into any human or computer language, in any form or by any means, electronic, mechanical, magnetic, manual, or otherwise, or disclosed to third parties without the express written permission of Dionex Corporation, 1228 Titan Way, Sunnyvale, California 94088-3603 U.S.A.

DISCLAIMER OF WARRANTY AND LIMITED WARRANTYTHIS PUBLICATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND. DIONEX CORPORATION DOES NOT WARRANT, GUARANTEE, OR MAKE ANY EXPRESS OR IMPLIED REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THIS PUBLICATION IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, CURRENTNESS, OR OTHERWISE. FURTHER, DIONEX CORPORATION RESERVES THE RIGHT TO REVISE THIS PUBLICATION AND TO MAKE CHANGES FROM TIME TO TIME IN THE CONTENT HEREINOF WITHOUT OBLIGATION OF DIONEX CORPORATION TO NOTIFY ANY PERSON OR ORGANIZATION OF SUCH REVISION OR CHANGES.

TRADEMARKSChromeleon is a registered trademark of Dionex Corporation.OPC is a trademark of the OPC Foundation.

PRINTING HISTORYRevision 01, October 2003

Doc. 031964-01 10/03 i

Contents

1 • Introducing Chromeleon-PA

1.1 Introducing Chromeleon-PA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.2 About the Chromeleon Datasource . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.2.1 Datasource Folder Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.2.2 Changing the Current Datasource . . . . . . . . . . . . . . . . . . . . . . . 6

1.3 About the Analyzer Program User Interface . . . . . . . . . . . . . . . . . . . . . . 7

1.3.1 Program Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.3.2 Window Panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.3.3 Alert Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.3.4 Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.4 About the Event Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.4.1 Filtering the Event Monitor List . . . . . . . . . . . . . . . . . . . . . . . . 10

1.4.2 Resizing the Event Monitor Window and Column . . . . . . . . . 10

2 • Configuring Analyzers

2.1 About Configuring Analyzers and Systems . . . . . . . . . . . . . . . . . . . . . 11

2.2 About Creating Instrument Control Programs . . . . . . . . . . . . . . . . . . . 12

2.2.1 Example Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.3 About Creating Method (QNT) Files . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.4 Adding Analyzers and Assigning Systems . . . . . . . . . . . . . . . . . . . . . . 14

2.4.1 About the Configuration Tree . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chromeleon-PA Analyzer

ii Doc. 031964-01 10/03

2.4.2 Guidelines for Adding Analyzers . . . . . . . . . . . . . . . . . . . . . . .15

2.4.3 How to Add a New Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . .15

2.5 Removing Analyzers and Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

2.6 Renaming Analyzers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

2.7 Configuring Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

2.8 Configuring Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

2.8.1 How to Configure a Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

2.8.2 How to Override the Default Sample Prep Parameters . . . . . . .21

2.9 Creating and Editing Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

2.9.1 How to Create or Edit a Sequence . . . . . . . . . . . . . . . . . . . . . . .23

2.9.2 How to Override the Current Sample Prep Parameters . . . . . . .24

2.9.3 How to Delete a Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

2.10 Assigning Default Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

2.10.1 How to Assign Default Sequences to an Analyzer . . . . . . . . . .26

2.11 Defining Result-Based Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

2.11.1 How to Define a Result-Based Event . . . . . . . . . . . . . . . . . . . .27

2.12 Configuring Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

2.12.1 About Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

2.12.2 Alarm Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

2.12.3 Alarm Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

2.12.4 How Alarm Lights and Relays are Cleared . . . . . . . . . . . . . . .32

2.12.5 Configuring Hardware Alarms . . . . . . . . . . . . . . . . . . . . . . . . .33

2.12.6 Bypassing Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Contents

Doc. 031964-01 10/03 iii

3 • Analyzing (Running) Sample Streams

3.1 About Analyzing (Running) Sample Streams . . . . . . . . . . . . . . . . . . . . 35

3.2 About Sequence Runs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.3 About Sample Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

3.4 About Sample Preparation Overlap . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.5 Creating Sequence Batches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.6 Running Sample Streams Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.7 Controlling Analyzer Runs (Start, Stop, Standby, and Resume) . . . . . 42

3.8 About Operating Individual Systems Offline . . . . . . . . . . . . . . . . . . . . 44

3.9 Taking Systems Offline and Online . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

3.9.1 How to Take a System Offline if the Analyzer is Stopped . . . 45

3.9.2 How to Take a System Offline if the Analyzer is Running . . . 45

3.9.3 How to Bring a System Back Online (Resume) . . . . . . . . . . . . 46

3.10 Running a System Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

3.11 About Processing Result-Based Events . . . . . . . . . . . . . . . . . . . . . . . . 47

3.11.1 Result-Based Event Flow Diagrams . . . . . . . . . . . . . . . . . . . . . 48

3.12 Viewing Chromatograms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

4 • Reporting

4.1 About Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

4.2 About Report Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

4.3 Enabling and Disabling End-of-Run Reports . . . . . . . . . . . . . . . . . . . . 70

4.4 Scheduling Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

4.5 Suspending a Scheduled Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73


iv Doc. 031964-01 10/03

4.6 Modifying a Scheduled Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

4.7 Printing Reports Immediately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

5 • Trending

5.1 About Trending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

5.2 Defining New Trend Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

5.3 Editing a Trend Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

5.4 Defining the Trend Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

5.5 Working with Trend Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

5.6 About the Trend Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

5.7 Changing the Trend Chart Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

Doc. 031964-01 10/03 1

1 • Introducing Chromeleon-PA

1.1 Introducing Chromeleon-PA

Dionex Chromeleon-PA is a client/server-based chromatography data system that provides software control of the DX-800 Process Analyzer.

Chromeleon-PA is an extended version of the Dionex Chromeleon chromatography data system. Chromeleon-PA adds process monitoring functions to the Chromeleon chromatography functions. These functions include sample stream selection, sample preparation and analysis, configuration of alarms and conditional responses, and component data trending.

The following sections provide an overview of Chromeleon-PA's main features.

Chromeleon-PA ComponentsThese are the Chromeleon-PA main components:

• Chromeleon Server Configuration program: This program contains configuration information about the chromatography instrument systems that are in the DX-800 Process Analyzer. This program is a standard component of the Chromeleon chromatography data system.

• Chromeleon instrument server: The server controls the data exchange between the DX-800 Process Analyzer and the Chromeleon-PA computer.

• Chromeleon Server Monitor program: This program is required for starting and monitoring the chromatography server. This program is a standard component of the Chromeleon chromatography data system.

• Chromeleon program: This program is the Chromeleon client user interface for accessing chromatography data and for controlling individual chromatography instruments. This program is a standard component of the Chromeleon chromatography data system.

• Analyzer program: This program is the user interface for accessing process analytical functions. This includes all analyzer-level configuration, control, results display, and results reporting. This program is unique to Chromeleon-PA.


2 Doc. 031964-01 10/03

• Datasource: This is the database in which Chromeleon-PA data is stored.

• Chromeleon-PA OPC Interface (Optional): The Chromeleon-PA OPC (OLE for Process Control) Server allows access to, and limited control of, one or more DX-800 Process Analyzers by an external OPC-compatible program (the client). The OPC client uses DX-800 data and/or alarm and event information for custom applications. The Chromeleon-PA OPC interface specifications are based on the Axeda FactorySoft OPC™ Toolkit. Refer to Setting Up Chromeleon-PA (Document No. 031970) for details about the Chromeleon-PA OPC interface.

The above programs, as well as the datasource and instrument server can be installed on a single computer or on separate computers, as in the following example:

Introducing Chromeleon-PA

Doc. 031964-01 10/03 3

Instrument ConfigurationBefore Chromeleon-PA can operate the DX-800 Process Analyzer, it needs to know what instruments are to be controlled and how they are connected. The Chromeleon Server Configuration program is used to define the instruments in your analyzer systems. A typical system consists of a CC80 Component Controller, an analytical pump, and a detector.

After the systems are configured, they are assigned to analyzers. A typical analyzer consists of one or more systems combined to operate in parallel. An analyzer is configured to sequentially monitor from 1 to 21 samples. If more than one sample will be monitored, an optional SS80 Sample Selector is installed on one of the systems. Chromeleon-PA can control a total of four systems configured in up to four analyzers. The example in the figure below shows four systems configured into two analyzers.


4 Doc. 031964-01 10/03

Instrument Control and Data AcquisitionThe individual systems handle all low-level instrument control and data acquisition functions. Programs (created in Chromeleon) contain the commands required for controlling instrument functions. Sample analysis sequences (created in the Analyzer program) define the order in which samples are analyzed. Chromeleon-PA coordinates all instrument control, sample selection and preparation, injection, and data acquisition functions, as shown in the figure below:

Data Processing and TrendingAt the end of each analysis, Chromeleon-PA processes the data as specified in the quantification (QNT) method assigned to the system. In addition, Chromeleon-PA allows data trending (monitoring of data over time). Trend data is displayed graphically on the trend plot.

Unlike Chromeleon, which can be connected to multiple datasources, Chromeleon-PA can be attached to only one Chromeleon datasource at a time. All data from the configured analyzers is stored and retrieved from this single datasource. The datasource contains all sample data as well as all other information related to the analyzer: the Chromeleon Audit Trail, Analyzer Event Log, report templates, alarm configurations, and so on. Chromeleon-PA


Doc. 031964-01 10/03 5

determines the folder structure of the datasource where sample data and other types of data is stored.

ReportingChromeleon-PA provides several reporting and printing options. Individual sample reports can be printed after each sample run is completed. Summary reports can also be scheduled to print at specified intervals (for example, daily or weekly). Scheduled summary reports can be created for individual analyzers, streams, and/or systems.

Report definition files that define what information to include in the report and how to organize the report are created in Chromeleon. The schedule for when a report should be printed is specified in the Analyzer program.

1.2 About the Chromeleon Datasource

Chromeleon-PA can be attached to only one datasource at a time. All data (including sample data, the Audit Trail, the Analyzer program Event Log, report templates, alarm configurations, and so on) is stored and retrieved from this datasource. Chromeleon-PA creates the folder structure of the datasource.

1.2.1 Datasource Folder Structure

When timebases (systems) are created in the Server Configuration program, Chromeleon creates a top-level folder in the datasource for each configured system. All programs (PGM files), methods (QNT files), and report templates (RDF files) for a system must be stored in this top-level folder. These files are used as templates during daily operation, as described below.

During daily operation, when the analyzer begins the first sequence of the day, Chromeleon-PA creates a new folder under the system top-level folder and names it with the current year, month, and day. All sequences started on that day are then placed in this subfolder. Each sequence is named with a 6-digit number to ensure uniqueness. Output PGM and QNT files, which are copied from the template versions located in the


6 Doc. 031964-01 10/03

top-level folder, are also stored in the sequence folder. You can view the datasource structure in the Chromeleon Browser.

1.2.2 Changing the Current Datasource

1. To change the current datasource, select Datasource from the Administration menu. This opens the Datasource dialog box.

2. In the Available Datasources box, select the desired datasource and click Make Current.

The Available Datasource box contains all of the datasources currently connected in Chromeleon. If a particular datasource does not appear in the available list, check to see if it is connected in Chromeleon.


Doc. 031964-01 10/03 7

1.3 About the Analyzer Program User Interface

The Analyzer program user interface is designed to let you easily access program functions.

The following sections describe the main features of the user interface.

1.3.1 Program Tabs

Clicking one of the three tabs on the Analyzer program window (Configuration, Run, or Trending) displays a page with controls for the selected program function.

• Use the Configuration page to configure analyzers and systems before starting sample processing.

• Use the Run page to control processing of sample streams on the configured analyzers and systems.

• Use the Trending page to view a graphical display of selected data over time.

1.3.2 Window Panes

Each program page is divided into left and right panes.

• On the Configuration and Run pages, use the left pane to configure analyzers. On the Trending page, use the left pane to define trend lines. The settings selected on the left pane determine the information displayed on the right pane. For example, on the left pane of the Configuration page, select an analyzer name to display configuration properties for the analyzer, or select a system name to display configuration properties for the system.

• The right pane provides access to most Analyzer program functions. Use the right pane of the Configuration page to configure streams, sequences, and result-based events. Use the right pane of the Run page to control analyzer sequence batch and manual sample runs, and to control runs on individual systems. Use the right pane of the Trending page to view plots of the trend lines defined on the left pane.


8 Doc. 031964-01 10/03

1.3.3 Alert Bar

Whenever an event occurs in the Analyzer program (for example, a sequence is started or an error occurs), the information is displayed across the alert bar above the program tabs.

After the event is displayed in the alert bar, it is added to the Event Monitor (see Section 1.4).

1.3.4 Status Bar

Status information for the analyzers and systems is listed across the bottom of the program window. You can allow the status to scroll through the analyzers and systems, pausing at each one to briefly display status information, or you can lock the display to view only a selected analyzer and/or system.

To lock the status bar display, select the analyzer or system that you want to view and then click the unlocked icon . The icon changes to locked

. The status bar will now display status for only the selected (locked) analyzer or system.

In the example status bar shown below, Analyzer 2 is running Sample 1. The system status is locked on System_A, which is currently running a program named CC84.

Notes:• To hide the left pane, click . To show the left pane when it is

hidden, click the vertical bar on the left side of the page.• To change the width of the left pane, point to the right edge of the pane.

The cursor changes to left and right arrows . Drag the pane to the desired size.


Doc. 031964-01 10/03 9

1.4 About the Event Monitor

Whenever an event occurs in the Analyzer program (for example, a sequence is started or a report is printed), the Analyzer program displays the event in the alert bar at the top of the window. The information is displayed across the alert bar and then added to the list of events in the Event Monitor window. A notice next to the Show Event Monitor button displays the number of new items in the list.

Clicking Show Event Monitor opens the Event Monitor window.

The Event Monitor lists all Analyzer program events that have occurred in the past 7 days.

Notes: • If an analyzer or system is removed from the configuration, events

generated for the analyzer or system before it was removed will remain on the list for 7 days after they were generated.

• The items listed in the Event Monitor are separate from and supplemental to the Audit Trail in Chromeleon. Items shown in the Audit Trail do not appear in the Event Monitor and vice versa. For example, when running a sequence, the Event Monitor lists events related to the analyzer (analyzer started, stream in use, analyzer run completed, etc.), while the Audit Trail lists messages related to individual system control (start of sample, inject, autozero, acquisition on, etc.).


10 Doc. 031964-01 10/03

1.4.1 Filtering the Event Monitor List

Each entry in the Event Monitor List indicates the following details:

• The event type ( error, warning, or information)

• The event category (hardware, software, report, or component).

• The analyzer and system that generated the event.

You can filter the list using one or more of these conditions. If filter conditions are not currently displayed in the window, click Show Filter Conditions. Then, select or clear the check boxes to view the desired set of events.

1.4.2 Resizing the Event Monitor Window and Column

To resize the Event Monitor window, position the mouse at the lower right corner of the window and drag. To change the width of a column, position the cursor on the right border of the column and drag.

Doc. 031964-01 10/03 11

2 • Configuring Analyzers

2.1 About Configuring Analyzers and Systems

Use the Configuration page to configure analyzers and systems before starting sample processing.

Analyzer configuration consists of the following basic steps:

• Assigning one or more chromatography instrument systems to the analyzer

The systems assigned to an analyzer configuration operate synchronously to analyze a series of process sample streams.

• Configuring each system

Each system in the analyzer configuration is assigned default control programs, a quantification method, a confidence interval, a report format, and alarm parameters.

• Defining the streams to be analyzed

An analyzer can include definitions for up to 100 streams. These include the SS80 valve positions (either 7, 14, or 21) and one or more non-valve streams (these are typically, calibration and check standards). Each stream is assigned a name and a type (calibration, check standard, sample stream, blank, or matrix). Optionally, each stream can be assigned sample preparation parameters (program, injection volume, and internal standard amount), which override the default parameters assigned to each system.

• Defining sequences

The sequences defined for an analyzer can be used for various functions, such as running sample analyses, calibrating the analyzer, or running check standards. The samples in the sequence can also optionally be assigned sample preparation parameters, which will override parameters assigned to the stream and the system.

• Assigning default sequences to the analyzer

There are four analyzer functions to which you can assign default sequences: (1)routine analyzer runs, (2)startup, (3)calibration, and (4)check standards.


12 Doc. 031964-01 10/03

• Defining result-based events

After each sample is run, the results can be compared against pre-defined conditions. If the results meet at least one of the conditions, an event is triggered. For example, if the amount of chloride in a sample exceeds a pre-defined maximum, the check standard sequence is triggered to run.

2.2 About Creating Instrument Control Programs

Instrument control programs are created in Chromeleon with the Program Wizard. This section provides an overview of the types of programs needed for an analyzer, guidelines for creating the programs, and example programs. For details about how to create a program with the Program Wizard, refer to the Chromeleon Help.

The Analyzer program lets you assign the following four types of programs to a system:

The Chromeleon Program Wizard is designed primarily for creating programs for sample analyses (default). Default programs include commands for injection and data acquisition, which are not used with the Standby, Shutdown, and Overlap Flush programs.

When you use the Program Wizard to create a Standby, Shutdown, or Overlap Flush program, delete the following commands from the program after completing the Wizard:

• Autozero

• ECD_1.AcqOn

• ECD_1.AcqOff

Program Type Used For

Default Running sample analyses.

Standby Placing a system in standby.

Shutdown Shutting down a system.

Overlap Flush Flushing when a sequence is interrupted (for example, if an alarm occurs).

Configuring Analyzers

Doc. 031964-01 10/03 13

2.2.1 Example Programs

Chromeleon-PA provides example program files, which you can refer to when creating programs for your analyzer. Because every program is created for a specific system and application, the examples will not work “as is” with your analyzer, but the principles behind the types of commands included and the order in which they are listed can be applied to many systems.

Refer to Setting Up Chromeleon-PA (Document No. 031970) for printouts and descriptions of the example programs.

The example programs are included in the CM-PA Example datasource on the Chromeleon-PA installation CD. To connect to the datasource and view the examples, insert the CD in the drive, go to the Chromeleon Browser, and select File>Mount Datasource>Browse.

2.3 About Creating Method (QNT) Files

Quantification method files are created in Chromeleon using the QNT Editor and stored in each system's top-level folder in the Chromeleon datasource. These files are used as templates during daily operation as described below.

During daily operation, when the Analyzer program runs a sequence, it copies the template method (QNT) file from the system’s top-level program and saves it with the sequence. If a sequence includes calibration standards, both the sequence copy of the method and the template method are updated. This ensures that the updated calibration information is used for all subsequent sequence runs on that system.

The steps below provide an overview of how to create a method file for Chromeleon-PA. For detailed instructions, refer to Chromeleon Help. In the Chromeleon Help keyword index, select QNT Editor>Actions.

Complete the following steps in the Chromeleon client.

1. Create a new method file (select File>New>Method File) or copy one of the example files included in the Dionex Templates>IC Applications folders and modify it as required for your system.

2. In the QNT Editor, select the General tab page, and select the Fixed Mode under Global calibration settings.


14 Doc. 031964-01 10/03

3. Create a sequence that runs the desired number of levels and replicates of the calibration standards.

4. Run the standards.

5. In the QNT editor, select the Calibration tab and add the standards to the table (right-click and select Insert Standard).

6. On the Amount Table tab page, enter the amounts of the components in the standard.

7. On the General tab page, click the Calibrate button to generate the calibration curve and parameters.

8. Save the calibrated method file in the top-level folder for the system.

2.4 Adding Analyzers and Assigning Systems

Analyzers are added from the configuration tree (the left pane on the Configuration page). To go to the Configuration page, select the Configuration tab. If the configuration tree is hidden, click the vertical bar on the left side of the page.

2.4.1 About the Configuration Tree

The first time the Analyzer program is started, the configuration tree contains a single branch labeled Unassigned Systems. This branch lists systems that were configured in the Chromeleon Server Configuration program and that are not yet assigned to an analyzer.

Note: An analyzer’s configuration cannot be changed while it is running.


Doc. 031964-01 10/03 15

If analyzers have already been created, the configuration tree shows the existing analyzers and the systems assigned to them. Unassigned systems (if any) are listed after the analyzers.

2.4.2 Guidelines for Adding Analyzers

• An analyzer can include up to four systems.

• Only one system with an SS80 Sample Selector can be included per analyzer. If your configuration includes more than one SS80, create a separate analyzer for each one.

• System names cannot be changed from the Analyzer program. These names are assigned in the Chromeleon Server Configuration program.

2.4.3 How to Add a New Analyzer

1. Click Add Analyzer. A new analyzer is added to the tree.

2. Type a name for the analyzer and press the Enter key.

3. Drag a system from the Unassigned Systems list to the new analyzer.

4. Repeat Step 3 to assign additional systems (if any) to this analyzer.

5. Create additional analyzers, if required for your configuration requirements.


16 Doc. 031964-01 10/03

6. For each new analyzer, complete the remaining analyzer configuration tasks:

• Configure Systems (see Section 2.7)

• Name and Configure Streams (see Section 2.8)

• Create and Edit Sequences (see Section 2.9)

• Assign Default Sequences (see Section 2.10)

• Define Result-Based Events (see Section 2.11)

2.5 Removing Analyzers and Systems

1. Select the Configuration tab.

2. If the configuration tree (the left pane on the Configuration page) is hidden, click the vertical bar on the left side of the page.

3. To remove a system from an analyzer, select the system and click Remove. The system now appears in the Unassigned Systems list.

4. To remove an analyzer, first remove all of the systems assigned to the analyzer. Then, select the analyzer name in the configuration tree and click Remove.

2.6 Renaming Analyzers



3. Select the analyzer name in the configuration tree

4. Click again to enable editing.

5. Type the new name and press the Enter key.

Note: • Systems cannot be renamed from the configuration tree. Systems are

assigned names in the Chromeleon Server Configuration program.• You cannot rename a running analyzer.


Doc. 031964-01 10/03 17

2.7 Configuring Systems



3. Select the system name in the configuration tree. Configuration parameters for the selected system appear on the right side of the window.

4. Select the Instrument Control Programs from the drop-down lists. The lists contain all of the programs created in the Chromeleon PGM Editor for the selected system.

• Default: Select the program that will be used for running sample streams, unless a different program is selected in the stream or sequence configuration.

• Standby: (Optional) Select the program to run when the system is placed in standby.

• Shutdown: (Optional) Select the program to run when the system is shut down.

• Overlap Flush: (Optional) Select the program to run that will flush the system of the current sample if a sequence is interrupted. For example, if a result-based event occurs, the overlap flush program is run before the current sample is rerun. This ensures that an overlapped sample is flushed from the system.

5. Select the Quantification Method from the drop-down list. The list contains all of the methods created in the Chromeleon QNT Editor for the selected system.

6. Select a Correction Factor.

7. Select the Print End-of-Run check box to have a report printed after each sample is analyzed. Then, select the report definition file from the drop-down list. The list contains all of the report definitions created in Chromeleon for the selected system.


18 Doc. 031964-01 10/03

8. Under Check Standard, select the Confidence Interval percentage. The Confidence Interval is the range in which the “true” calibration curve will be found with a given probability. You can select the probability at which the values for a check standard should fall within the confidence interval. The following options are available: 90%, 95%, 98%, 99%, 99.7% 99.8%, 99.9%, and 99.99%.

9. In the Hardware Alarms table, specify the system response to each type of alarm.

Alarm Types

Alarm Type Description

Fatal HW An error has occurred that requires the sequence to be aborted. The Analyzer program runs the shutdown program (if possible). If the alarm is caused by a serious system error (for example, the pump pressure exceeds the maximum limit) internal system commands are used to shut down the system.

Non-fatal HW An error has occurred in a CC80 module (for example, a leak is detected or the temperature is not ready), but the sequence is not aborted.

TTL-1 In, TTL-2 In, ... TTL-8 In

An external device connected to a CC80 TTL input has detected a condition or an error and sent a TTL signal (usually an open circuit).


Doc. 031964-01 10/03 19

System Responses

What this icon means. A red exclamation icon next to the name of a control program, quantification method, or report indicates that the program, method, or report selected for the system is unavailable. Pass the mouse over the icon to see a description of the problem.

2.8 Configuring Streams

Streams are configured from the Streams pane on the Configuration page. The Streams pane displays the available streams for the selected analyzer.

• The numbered rows under Valve Position correspond to the number of sample selection valves installed in the SS80 (either 7, 14, or 21).

• In addition to the numbered valves, streams labeled N/A can be configured. These streams are used for samples that enter the analyzer from a source other than the SS80. Calibration and check standards are typically assigned to N/A streams.

System Response Description Available for ...

Relay Out (1-2) Enter 1 to open Relay Out 1 on the CC80. Enter 2 to open Relay Out 2 on the CC80. Enter None to leave a relay closed.

All alarm types

Panel Light (1-4) Enter 1, 2, 3, or 4 to turn on the corresponding light on the CC80 front panel. Enter None to not turn on a light.

All alarm types

Action: Shutdown The system is shut down. All alarm types

Action: Ignore The alarm is ignored. All alarm types

Action: Standby The system is placed in standby. All alarm types

Action: Bypass One or more selected streams are bypassed.

TTL Input alarms only

Streams to Bypass If the selected action is Bypass, click the Streams to Bypass cell and select the streams.

TTL Input alarms only


20 Doc. 031964-01 10/03

2.8.1 How to Configure a Stream



3. Select the Streams tab on the right pane of the window and select the desired analyzer in the configuration tree.

4. Under Stream Name, do one of the following:

• Click the (enter Name) cell next to the valve position of the stream to be configured.

• To configure a non-SS80 stream, click the blank row on the streams table. A new stream, labeled N/A, is added to the table.

5. Type a stream name. When streams are identified elsewhere in the Analyzer program (for example, in the Sequence Editor or Trending window), the name assigned here is displayed.

6. Select a Stream Type (Calibration, Check Standard, Sample Stream, Blank, or Matrix) from the drop-down list.


Doc. 031964-01 10/03 21

2.8.2 How to Override the Default Sample Prep Parameters

When a system is configured, a default program is assigned to it, and the injection volume and internal standard amount are both set to default values (20 and 1, respectively). These default parameters are used for most samples. However, some samples, especially calibration standards, check standards, and samples that differ significantly from the rest, may require different sample preparation steps. If this is the case, follow the steps below to assign different sample prep parameters and override the sample parameters specified in the system configuration. See Section 3.3 for additional information.

1. One or more vertical bars, labeled Sample Prep. (System Name) are located to the right of the Stream Type column. Click a bar to display the sample preparation parameters for that system.

2. Select the Override check box.

3. Select the desired sample preparation parameters:

• Program: Select the instrument control program that will be used to run the stream. The drop-down list contains all of the available programs for the system (created in Chromeleon). In order to appear in this list, the program must be saved in the system's top-level folder in the Chromeleon Browser.

• Inj. Vol: Select the injection volume in microliters (µL).


22 Doc. 031964-01 10/03

• Int. Std: Select the amount of the internal standard added to the sample; this is implemented as a multiplication factor in the amount calculation formula.

What this icon means. A red exclamation icon in the Program or Valve Position column indicates that the program selected for the stream is unavailable. Pass the mouse over the icon to see a description of the problem.

2.9 Creating and Editing Sequences

Use the Sequence Editor to create new sequences, edit existing sequences, or delete sequences.

To go to the Sequence Editor:

• Click the Configuration tab.

• If your configuration consists of multiple analyzers, select the desired analyzer on the configuration tree (the left pane on the Configuration tab). To display the configuration tree if it is hidden, click the vertical bar on the left side of the page.

• Click the Sequence Editor tab on the right pane of the window.


Doc. 031964-01 10/03 23

2.9.1 How to Create or Edit a Sequence

1. In the Sequence field, select New (enter name) and type a name for the new sequence or select the name of an existing sequence from the drop-down list. Press Enter.

2. (Optional) Select an Injection Cycle Time. Select the desired number of hours and minutes between injections.

3. Define or edit the injection parameters for Injection 1:

• Sample Name: Click (select Stream) and select the sample (stream) name from the drop-down list. This list contains the sample streams that are configured on the Streams page for the analyzer.

• Alarm Sequence (Optional): Click (select Sequence) and select the name of the sequence to be run if a result-based event occurs and the selected action is Rerun: Alarm on Failure. See Section 3.11 for details.

• Repeats (Optional): Enter the number of times to repeat the alarm sequence. The alarm sequence runs until the alarm condition clears or until the number of repeats is reached. If the alarm sequence is repeated the specified number of times and the alarm has not cleared, the Analyzer program goes to the next line in the original sequence. If Repeats is set to 0, the alarm sequence is run one time and then the Analyzer restarts the original sequence at the first line.


24 Doc. 031964-01 10/03

4. To add a new injection to the sequence, click the blank row on the injection table. A new injection with default settings is added to the table. Define the injection parameters as described in Step 3 above.

5. To delete an injection, select the injection in the table and press the keyboard Delete key, or right-click and select Delete from the menu.

6. Click Save to save the sequence.

2.9.2 How to Override the Current Sample Prep Parameters

Follow the steps below to override the sample preparation parameters currently assigned to a system. One possible reason for overriding the sample preparation parameters in a sequence is if you want to concentrate different volumes of the same sample as part of an alarm sequence.

1. One or more vertical bars, labeled Sample Prep. (System Name) are located to the right of the Sample Name column. Click a bar to display the sample preparation parameters currently in effect for that system.

2. Select the Override check box.

3. Select the desired sample preparation parameters:

• Program: Select the instrument control program that will be used to run the stream. The drop-down list contains all of the available programs for the system (created in Chromeleon). In order to appear in this list, the program must be saved in the system's top-level folder in the Chromeleon Browser.

• Inj. Vol: Select the injection volume in microliters (µL).

Note: The sample prep. parameters that you select here override the sample prep. parameters selected on the Streams page and in the system configuration. See Section 3.3 for details.


Doc. 031964-01 10/03 25

• Int. Std: Select the amount of the internal standard added to the sample; this is implemented as a multiplication factor in the amount calculation formula.

2.9.3 How to Delete a Sequence

1. In the Sequence field, select the name of the sequence from the drop-down list.

2. Click Delete.

2.10 Assigning Default Sequences

Default sequences are assigned to each analyzer from the Sequences pane on the Configuration page.

You can assign default sequences to four analyzer functions:

• Default: The Default sequence is used for routine analyzer runs.

• Alt. (Alternate) Start: The Alt. Start sequence is typically started from an external command and lets you run a start-up sequence before running the Default sequence.

• Calibration: The Calibration sequence is used for calibration of the analyzer. It is run automatically whenever calibration is selected as the response for a result-based event.

• Check Std. (Standard): The Check Std. sequence is used for running check standards. It is run automatically whenever check standard is selected as the response for a result-based event.


26 Doc. 031964-01 10/03

2.10.1 How to Assign Default Sequences to an Analyzer



3. Select the Sequences tab on the right pane of the window.

4. For each type of default sequence (Default, Alt. Start, Calibration, or Check Std.), select a sequence from the Sequence Name drop-down list. This list contains all of the sequences that have been previously configured for the analyzer using the Sequence Editor.

5. In the Starting Line # field, enter the line in the sequence at which to begin running the sequence.

6. In the Repeats field, enter the number of times to repeat the sequence (0 to 99, or continuous). Note: To enter continuous, type a c (or any portion of the word) or type -1. Then press the Enter key.


Doc. 031964-01 10/03 27

2.11 Defining Result-Based Events

After each injection is processed, the results can be compared against pre-defined conditions. If the condition is met, a response (event) is triggered. Use the Result-Based Events pane on the Configuration page to define one or more conditions (formulas) and to select the response (action) for each condition.

2.11.1 How to Define a Result-Based Event



3. Select the desired analyzer in the configuration tree.

4. Select the Result-Based Events tab on the right pane of the window.

If no events were defined previously, line 1 of the list has default settings in all cells.

5. To define the first event, change the default settings on line 1 as described below. If events are already defined, add a new line by clicking in the blank cell below the last defined event.

6. In the Stream column, select a stream from the drop-down list, or select All Streams.


28 Doc. 031964-01 10/03

7. In the Condition (Formula) column, define a condition.

a. Double-click the icon in the Condition (Formula) cell to open the Define test condition dialog box.

b. From the System drop-down list, select the system on which the stream will be run.

c. Under Evaluation Test Condition, first select the component to include in the condition. The components shown in the list depend on the selected stream and system.

d. Then, select the result variable (Amount, Area, Height, or Retention Time) to include in the condition.

e. To complete the condition, select an operator and then enter a value. Click OK.

Condition Example

The example below defines a condition for checking the retention time of the chloride peak produced on System_A. If the retention time is less than 3.225, then the selected action is triggered.

Note: You can also define a custom formula by selecting the Custom Formula check box and typing the formula directly into the field. Custom formulas can include any Chromeleon report variable. See the Chromeleon online Help for a list and description of the report variables (search the Index for “report variables”).


Doc. 031964-01 10/03 29

8. In the Response (Action) cell, select the desired action from the drop-down list.

9. If you selected the Run Sequence action, select the sequence to run from the Sequence drop-down list.

10. In the Panel Light cell, select 1, 2, 3, or 4 to turn on the corresponding light on the CC80 front panel if the condition occurs. Select None to not turn on a light.

Response (Action) Description

Continue Go on to the next injection in the sequence.

Run Sequence Run a specified sequence.

Calibrate Run the calibration sequence.

Standby Analyzer Place the analyzer in standby.

Rerun: Alarm on failure

Rerun the injection; if the failure recurs, run the alarm sequence specified in the sequence definition.

Rerun: Check Std: Calibrate on failure

Rerun the injection; if the failure recurs, run a check standard. If the check standard fails, run the calibration sequence.

Rerun: Check Std: Standby on failure

Rerun the injection; if the failure recurs, run a check standard. If the check standard fails, place the analyzer in standby.

Rerun: Check Std: Continue on failure

Rerun the injection; if the failure recurs, run a check standard. If the check standard fails, go on to the next injection.

Check Std: Calibrate on failure

Run a check standard; if the check standard fails, run the calibration sequence.

Check Std: Standby on failure

Run a check standard; if the check standard fails, place the analyzer in standby.

Check Std: Continue on failure

Run a check standard; if the check standard fails, go on to the next injection.

Standby System Place the system in standby.

Shutdown System Shut down the system.


30 Doc. 031964-01 10/03

11. In the Relay Out cell, select 1 to open Relay Out 1 on the CC80 if the condition occurs. Select 2 to open Relay Out 2 on the CC80. Select None to keep the relays closed.

2.12 Configuring Alarms

2.12.1 About Alarms

The Analyzer program provides several types of alarms.

• Hardware alarms are triggered when an error occurs in a system module (analytical pump, detector, component controller, etc.). Hardware alarms are classified as either fatal (the sequence is aborted) or non-fatal (the sequence is not aborted).

• TTL input alarms are triggered by an external device connected to a CC80 TTL input. For example, a liquid sensor on a sample pipe triggers a TTL alarm if the sample pipe is dry.

• Result-based event alarms are triggered when the results from a run meet a pre-defined condition. For example, if the amount of chloride in a sample exceeds a pre-defined maximum, the check standard sequence is run.

2.12.2 Alarm Configuration

The configuration properties for each system in an analyzer determine how the analyzer responds when a hardware or TTL alarm occurs. The response to each type of alarm can be different. In addition, multiple responses can be assigned to each alarm. For example, a non-fatal hardware alarm can be configured to turn on a CC80 front panel light and to also place the system in standby.

The properties of the result-based events defined for each stream in an analyzer determine how the analyzer responds when an event occurs. Multiple result-based events can be defined for each stream. A result-based event definition consists of a condition (for example, a component amount over a set limit) and a response (action) (for example, running a

Note: If multiple result-based events occur simultaneously, the event with the highest priority takes precedence.


Doc. 031964-01 10/03 31

check standard or a calibration sequence). Result-based events can also turn on a CC80 front panel light and/or open a relay output.

The following table summarizes the possible responses for each alarm type (fatal hardware, non-fatal hardware, TTL in, and result-based events):

*One action per alarm.

Alarm Response Fatal HW

Non-Fatal HW

TTL in RBE

Open Relay Out 1 or 2 on the CC80 X X X X

Turn on CC80 front panel light 1, 2, 3, or 4 X X X X

Trigger an Action:*

Shutdown the system X X X X

Ignore the alarm X X X X

Place the system in standby X X X X

Bypass one or more sample streams X

Additional actions for RBEs only: run sequence, calibrate, standby (analyzer), re-run: alarm on failure, re-run: check standard: calibrate on failure, re-run: check standard: standby on failure, check standard: calibrate on failure, check standard: continue on failure

X

Note: Multiple alarms (of any type) can be assigned to the same CC80 panel light or relay output. When configuring alarms, it is helpful to assign the same type of alarm to a particular light or relay. For example, you could assign fatal hardware alarms to light 1, non-fatal hardware alarms to light 2, TTL input alarms to light 3, and result-based events to light 4.


32 Doc. 031964-01 10/03

2.12.3 Alarm Priorities

If multiple alarms occur simultaneously, the Analyzer program responds to them according to the action assigned to each. The priority of actions is as follows:

1. Shutdown action

2. Standby

3. Bypass Streams

4. Ignore

If multiple result-based events occur simultaneously, the Analyzer program responds to them in the order in which they are listed on the Result-Based Event tab page in the Analyzer Configuration.

2.12.4 How Alarm Lights and Relays are Cleared

If a hardware alarm occurs that turns on a CC80 front panel light or a relay output, the Analyzer program turns off the light or relay when the cause of the alarm no longer exists. If the alarm caused the system to be shut down or placed in standby, the Analyzer program turns off the light or relay when the system is online again (provided the cause of the alarm no longer exists).

If a result-based event occurs that turns on a CC80 front panel light or activates a relay out, the Analyzer program turns off the light or relay only when the same stream is re-run and the result condition does not recur.

If a light or relay is cleared for one alarm, but another alarm condition exists for the same light (or relay), the light or relay will immediately turn on again. This will continue happening until all alarm conditions are cleared. See Section 3.11 for additional information.


Doc. 031964-01 10/03 33

2.12.5 Configuring Hardware Alarms

The Analyzer program provides several types of alarms, which can be configured for each system in an analyzer. For an overview of the different alarm types, see Section 2.12.1.

1. Select the Configuration tab to go to the Configuration page. Display the configuration tree (click the vertical bar on the left side of the page) if it is hidden.

2. In the configuration tree, click the system name. Configuration parameters for the selected system appear on the right side of the window.

3. In the Hardware Alarms table, specify the following for each type of alarm:

Response (Action):

• Shut Down: The system is shutdown.

• Ignore: The alarm is ignored.

• Standby: The system is placed in standby.

• Bypass Streams (available for TTL alarms only): One or more selected streams are bypassed.

Panel Light (1-4): Enter 1, 2, 3, or 4 to turn on the corresponding light on the CC80 front panel, or enter None if you do not want a light to turn on.


34 Doc. 031964-01 10/03

Relay Out (1-2): Enter a 1 to open Relay Out 1 on the CC80. Enter a 2 to open Relay Out 2, or enter None if you do not want a relay output to open.

2.12.6 Bypassing Streams

You can set up a TTL alarm that will cause injections from one or more streams to be skipped if the alarm occurs. For example, if a liquid sensor on a sample pipe is connected to CC80 TTL-1 and the pipe is dry, the sensor signals the TTL-1 input. Injections from that sample are then bypassed.

1. Select the Configuration tab to go to the Configuration page.


3. In the configuration tree, click the system name on which the streams to be bypassed are processed. Configuration parameters for the selected system appear on the right side of the window.

4. In the Alarms table, under Response (Action), select Bypass streams for the TTL input that will be used to trigger the alarm. For example, if a liquid sensor is connected to TTL-1 on the CC80, select Bypass in the TTL-1 in Response (Action) cell. The Streams to Bypass cell is enabled.

5. Double-click the icon in the (select Streams) cell to open the Please specify streams to bypass dialog box.

6. Select the stream(s) to bypass and then click OK.

Notes:• Multiple alarms (of any type) can be assigned to the same CC80 panel

light or relay out. When configuring alarms, it is helpful to assign the same type of alarm to a particular light or relay. For example, you could assign fatal hardware alarms to light 1, non-fatal hardware alarms to light 2, TTL input alarms to light 3, and result-based events to light 4.

• The alarms are prioritized according to the response they trigger: (1)shutdown, (2)standby, (3)bypass streams, or (4)ignore. If more than one alarm is assigned to a relay output or panel light, the higher priority alarm is given precedence.

Doc. 031964-01 10/03 35

3 • Analyzing (Running) Sample Streams

3.1 About Analyzing (Running) Sample Streams

Use the Run page to control the analysis of sample streams on the configured analyzer(s) and system(s).

Sample streams are typically analyzed in sequences that are grouped into a batch. A separate sequence batch is used for each configured analyzer. When multiple systems are configured in the analyzer, the Analyzer program synchronizes each sample run in a sequence. In addition, sample preparation can be overlapped; that is, the CC80 can perform sample preparation for the next sample while the current sample is still running.

In addition to running sequences, individual sample streams can be manually analyzed.

The Analyzer program allows different sample parameters (program, injection volume, and internal standard amount) to be specified for use at different times. This means that sample preparation for a particular stream can be processed differently, depending on the sample parameters currently in effect.

The controls on the Run page also let you take individual systems offline to perform maintenance or calibration functions while the rest of the analyzer continues to run. Offline systems can be brought online without stopping the analyzer, by clicking the Resume button.

Note:• When a system is offline, Chromeleon is used to control functions, such

as calibration.• When a system with an SS80 goes offline, the analyzer stops after the

current sample completes.


36 Doc. 031964-01 10/03

3.2 About Sequence Runs

The figure below shows the steps the Analyzer program performs when running samples in a sequence. Sample preparation overlap is turned on. See Section 3.4 for details about sample preparation overlap.

Analyzing (Running) Sample Streams

Doc. 031964-01 10/03 37

When samples are analyzed in sequences, all systems configured in the analyzer are synchronized to start at the same time. After analyzing a stream, a system does not inject the next sample until the following events occur:

• All other systems have completed the current stream and sent their results to the Analyzer program

• The Analyzer program has evaluated the results for result-based events (RBEs)

• RBEs (if any) are executed

• The Analyzer program sends the “Analyzer Ready” command to begin the next sample stream

• The Injection Cycle Time expires (if one is specified for the sequence)

3.3 About Sample Parameters

The Analyzer program allows different sample parameters (program, injection volume, and internal standard amount) to be specified for use at different times. This means that an injection from a particular stream can be processed differently, depending on the sample parameters currently in effect.

When each system is configured, a default program is assigned to that system and the injection volume and internal standard amount are both set to default values (20 and 1, respectively). These sample parameters are used for most samples. However, some samples, especially calibration standards, check standards, and samples that differ significantly from the rest, may require different sample preparation steps. If this is the case, you can assign alternate sample parameters. Sample parameters can be specified in the following places within the Analyzer program:

• Configuration tab (system selected) (default): A default program must be assigned in the system configuration. The remaining two sample parameters are always set to default values (injection volume=20, internal standard=1).

• Configuration tab (analyzer selected) Streams page: Sample parameters can be assigned to each stream in the analyzer configuration. If there are multiple systems, different parameters can be used for each system.

• Configuration tab (analyzer selected) Sequence Editor page: Sample parameters can be assigned to each stream in a sequence. If there are multiple systems, different parameters can be used for each system.


38 Doc. 031964-01 10/03

• Run tab (Manual Sample option selected): Sample parameters can be selected at run time (except when the analyzer is running one of the default sequences).

When sample parameters are specified in more than one place, the Analyzer program selects parameters in the following order of priority:

Run: If sample parameters are specified for a manual sample run on the Run page, they are always used. Sample parameters specified elsewhere are ignored.

Sequence: If sample parameters are not specified on the Run page, the sequence sample parameters are used.

Streams: If sample parameters are not specified on the Run page or in the sequence, stream sample parameters are used.

System: If sample parameters are not specified elsewhere (run, sequence, or stream), system sample parameters are used.

3.4 About Sample Preparation Overlap

To reduce the time between injections, the CC80 can perform the sample preparation functions for the next sample in a sequence while the current sample is still running. The overlapped functions are run while data acquisition or other program commands that do not require the CC80 are being executed. When the CC80 finishes the overlapped functions, the program pauses, if necessary, to allow the currently running sample to finish. Then, the remaining commands (inject, data acquisition, etc.) in the overlapped sample’s program are executed. If an RBE


Doc. 031964-01 10/03 39

occurs that requires a different sequence to be run (for example, a calibration), the overlapped sample is flushed from the system before the other sequence is started.

3.5 Creating Sequence Batches

Sample streams are typically processed in sequences that are grouped into a batch list. A separate sequence batch is created for each configured analyzer.

1. To view and edit an analyzer's sequence batch list, click the Run tab.

2. In the configuration tree (the left pane on the Analyzer program window), select the analyzer to be run.

3. On the right side of the window, select Sequence Batch. The table below the Sequence Batch button displays any sequences already in the batch.

4. If the batch is empty, the first line of the table has default settings in all cells. To add the first sequence, change the default settings on line 1 as described below. If the batch already contains sequences, add a new sequence by clicking in the blank cell below the last sequence in the table. Default values for the sequence parameters are filled in.

5. Select the desired values for the sequence you are adding:

Sequence Type

• Default: Selecting Default enters the name of the Default sequence (assigned in the analyzer configuration) into the Sequence Name cell.

• Alt. (Alternate) Start: Selecting Alt. Start enters the name of the default alternate start sequence (assigned in the analyzer configuration) into the Sequence Name cell.

Notes: • Sample preparation overlap occurs only within a sequence (i.e., the first

sample in the next sequence is not prepared until the last sample in the current sequence is complete).

• Sample preparation overlap is enabled or disabled in the Chromeleon Server Configuration program during setup of the analyzer systems. It is enabled by default.


40 Doc. 031964-01 10/03

• Calibration: Selecting Calibration enters the name of the default calibration sequence (assigned in the analyzer configuration) into the Sequence Name cell.

• Check Std. (Standard): Selecting Check Std. enters the name of the default check standard sequence (assigned in the analyzer configuration) into the Sequence Name cell.

• Specify>>: Selecting Specify>> lets you choose to run any sequence available to the analyzer. Choose the sequence to run from the Sequence Name list.

Sequence Name: If you selected Specify>> for the sequence type, select the sequence to run from the list. If you selected one of the default sequence types, the name of the default sequence for that type is automatically filled in and cannot be edited.

Start Line #: If you selected Specify>> for the sequence type, enter the line number at which the analyzer should begin running the sequence. If you selected one of the default sequences, the line number specified in the analyzer configuration is automatically filled in and cannot be edited.

Date/Time Start: Indicates when the sequence will start.

Repeat: If you selected Specify>> for the sequence type, select the number of times to repeat the sequence. enter the number of times to repeat the sequence (0 to 99, or continuous). Note: To enter continuous, type a c (or any portion of the word) or type -1 and then press the Enter key. If you selected one of the default sequences, the repeat number specified on the Sequences tab page in the analyzer configuration is automatically filled in and cannot be edited.

Suspend Printing: Select whether to suspend printing of end-of-run reports. The default setting is no (do not suspend printing). To suspend printouts, type yes and press Enter. Note: In order to have printouts after each run, the Print End-of-Run option must be enabled in each system's configuration (see Enabling and Disabling End-of-Run Reports) and the Suspend Printing option in the sequence batch must be set to no.

6. To start the sequence batch, click the Start button.

The Analyzer program runs the sequences in the order in which they are listed in the batch.


Doc. 031964-01 10/03 41

3.6 Running Sample Streams Manually

Individual sample streams can be manually processed, instead of being processed automatically in sequences. Manual sample runs are only available if a sequence is not currently running.

1. Click the Run tab.

2. In the analyzer configuration tree (the left pane on the Run page), select the analyzer on which the stream is processed.

3. Click Manual Sample and select the stream to be processed from the list. The list shows the available sample streams for the selected analyzer.

4. (Optional) Select sample parameters (program, injection volume, and internal standard) for the run:

The Active Sample table displays the sample parameters currently in effect for the selected stream. For each system, select a program, injection volume, or internal standard amount. These selections will be used only for the selected run of this stream.

5. Click Start.


42 Doc. 031964-01 10/03

3.7 Controlling Analyzer Runs (Start, Stop, Standby, and Resume)

Use the Start, Stop, Standby, and Resume buttons on the Run page to control runs on a selected analyzer.

Starting an Analyzer Run1. Click the Run tab. The alert bar at the top of the Run page indicates the

analyzer currently selected.

2. To start a different analyzer, select it in the configuration tree (the left pane on the page). To display the configuration tree if it is hidden, click the vertical bar on the left side of the page.

3. Select either Sequence Batch or Manual Sample.

4. For sequence batch runs, add, remove, or rearrange sequences in the batch as required (see Section 3.5). In the configuration tree, the analyzer is labeled –(running). Configuration changes, such as adding or deleting systems cannot be made while an analyzer is running.

5. For manual sample runs, select the sample (see Section 3.6).

6. Click the Start button.

The Analyzer program starts the sequence batch or the manual sample run.

Stopping an Analyzer Run1. Click the Run tab. The alert bar at the top of the Run page indicates the


2. To stop a different analyzer, select it in the configuration tree (the left pane on the page). To display the configuration tree if it is hidden, click the vertical bar on the left side of the page.

Notes:• Clicking the Start button starts all of the systems that are currently

online. • The system the SS80 is assigned to must be online in order to start the

analyzer. You can take other systems offline before starting a run by clearing the Online/Offline check box in the Active Sample table.


Doc. 031964-01 10/03 43

3. Click the Stop button and select the desired option.

• Immediately: The current injection is stopped. Data acquired up to that point is saved.

• After current sample: The current injection is completed.

• After current sequence: All injections in the current sequence are completed. This option is not available when a manual sample is running.

Placing an Analyzer in Standby1. Click the Run tab. The alert bar at the top of the Run page indicates the


2. To control a different analyzer, select it in the configuration tree (the left pane on the page). To display the configuration tree if it is hidden, click the vertical bar on the left side of the page.

3. Click the Standby button and select the desired option. The available options depend on whether the analyzer is running a sequence batch or a manual sample:

• Immediately: The current injection is stopped. Data acquired up to that point is saved. All systems in the analyzer then run their overlap flush programs, followed by the Standby programs.

• After current sample: The current injection is completed and then all systems in the analyzer run their overlap flush programs, followed by the Standby programs.

• After current sequence: All injections in the current sequence are completed and then the systems run their overlap flush programs, followed by the Standby programs. This option is not available when a manual sample is running.


44 Doc. 031964-01 10/03

Resuming an Analyzer Run1. Click the Run tab. The alert bar at the top of the Run page indicates the


2. To control a different analyzer, select it in the configuration tree (the left pane on the page). To display the configuration tree if it is hidden, click the vertical bar on the left side of the page.

3. Click the Resume button.

This returns all systems in standby to the running state.

3.8 About Operating Individual Systems Offline

Individual systems can be taken offline and operated separately from the analyzer. When a system is offline, it is not started when an analyzer sequence batch or manual sample run starts.

When a system is offline, you can use Chromeleon to run samples, perform instrument calibration and maintenance procedures, and directly control other instrument functions, while the analyzer continues running.

After operating a system offline, you can click the Resume button to bring the system online with the analyzer.

To check whether a system is currently online, go to the Run page and select the analyzer in the analyzer configuration tree (the left pane on the Run page). The Active Sample table on the right side of the Run page displays the online status of each system in the selected analyzer.


Doc. 031964-01 10/03 45

3.9 Taking Systems Offline and Online

You can take individual systems offline (the system does not start when the sequence batch starts) and leave them offline during a sequence batch run or return them online (resume) during the run.

3.9.1 How to Take a System Offline if the Analyzer is Stopped

1. Click the Run tab.

2. In the Active Sample table, clear the system's check box under On/Off Line. The system with an SS80 cannot be taken offline from the Active Sample table.

3.9.2 How to Take a System Offline if the Analyzer is Running

1. Go to the Run page.

2. If the analyzer configuration tree (the left pane on the Run page) is hidden, click the vertical bar on the left side of the page.

3. Expand the analyzer in the configuration tree and select the system name under the analyzer.

4. To take the system offline and stop it, click Stop and select the desired option.

• Immediately: The selected system stops immediately. Data acquired up to that point is saved.

Notes:• The system that includes an SS80 Sample Selector cannot be taken

offline individually. It is only controlled as part of an analyzer.• In order to start a sequence batch, the system that includes an SS80 must

be online.

Note: The Active Sample table shows only the systems in the currently selected analyzer. To take a system in a different analyzer offline, select the analyzer in the configuration tree (the left pane on the Run page). To display the configuration tree if it is hidden, click the vertical bar on the left side of the page.


46 Doc. 031964-01 10/03

• After current sample: The current injection is completed. The selected system stops.

• After current sequence: All injections in the current sequence are completed. The selected system stops.

5. To take the system offline and place it in standby, click Standby and select the desired option.

• Immediately: The current injection is stopped. Data acquired up to that point is discarded. The selected system then runs its Standby program.

• After current sample: The current injection is completed and the selected system then runs its overlap flush program, followed by the Standby program.

• After current sequence: All injections in the current sequence are completed, and then the selected system runs its overlap flush program, followed by the Standby program.

3.9.3 How to Bring a System Back Online (Resume)

1. Go to the Run page.

2. If the analyzer configuration tree (the left pane on the Run page) is hidden, display it by clicking the vertical bar on the left side of the page.

3. In the configuration tree, select the analyzer in which the system is configured.

4. If the analyzer is not running, select the system's check box under On/Off Line in the Active Sample table.

5. If the analyzer is running, select the system in the analyzer configuration tree. Click Resume.

Note: Selecting Stop or Standby when a system is selected in the analyzer configuration tree affects the selected system only. The remaining systems in the analyzer continue running.

Note: In order to start a sequence batch, the system that includes an SS80 Sample Selector must be online.


Doc. 031964-01 10/03 47

3.10 Running a System Offline

1. Take the system offline. See Section 3.9 for instructions.

2. In the analyzer configuration tree (the left pane on the Run page) on the Run page, select the analyzer in which the system is configured and select the system name under the analyzer.

3. Go to Chromeleon by clicking the Direct Control button on the upper-right side of the page.

4. In Chromeleon, create and run any required sequences or perform any required operations under direct control from a panel.

5. To resume operation with the analyzer, first end any runs being controlled by Chromeleon and disable direct control by selecting Monitor from the Control menu. Then, return to the Analyzer program and click Resume to bring the system back online with the analyzer.

3.11 About Processing Result-Based Events

The Analyzer program performs the following basic steps when a result-based event occurs after running a sample stream:

1. After the systems run a stream in a sequence, they report the results to the Analyzer program.

2. The Analyzer program checks the results against any conditions defined in result-based events.

3. If a sample result meets one of the conditions, the Analyzer program performs the action specified in the result-based event and (if specified) also turns on a CC80 front panel light and/or a CC80 relay output. See the flow diagrams below for details about how the Analyzer program handles each type of result-based event action.

4. After completing the result-based event action (or if no result-based event occurred) the Analyzer program signals the systems to go to the next stream in the sequence.


48 Doc. 031964-01 10/03

3.11.1 Result-Based Event Flow Diagrams

RBE Action=Continue

Summary: Continue

If a result-based event (RBE) occurs when the selected action is Continue, the Analyzer program turns on a panel light and/or a relay output if specified in the RBE definition, and then continues to the next line in the sequence.


Doc. 031964-01 10/03 49

RBE Action=Run Sequence

Summary: Run Sequence

If a result-based event (RBE) occurs and the selected action is Run Sequence, the Analyzer program turns on a panel light and/or a relay output if specified in the RBE definition. The overlap flush program is then run, followed by the specified sequence. When the sequence is complete, the systems continue to the next line in the original sequence.

Note: This action is similar to the Rerun: Alarm on Failure action in that a sequence is run if the RBE occurs. However, with this action, the sequence is always run until completion and it cannot be repeated.


50 Doc. 031964-01 10/03

RBE Action=Calibrate

Summary: Calibrate

If a result-based event (RBE) occurs when the selected action is Calibrate, the Analyzer program turns on a panel light and/or a relay out if specified in the RBE definition. The overlap flush program is then run on all systems, followed by the calibration sequence. After calibration, the QNT files for each system are updated and then each system continues to the next line in the original sequence.


Doc. 031964-01 10/03 51

RBE Action=Standby (Analyzer)

Summary: Standby (Analyzer)

If a result-based event (RBE) occurs when the selected action is Standby (Analyzer), the Analyzer program turns on a panel light and/or a relay out if specified in the RBE definition. The overlap flush program is run on all systems, followed by the standby program. The analyzer remains in standby until you click Resume on the Analyzer program Run page. Then, each system continues to the next line in the sequence.


52 Doc. 031964-01 10/03

RBE Action=Re-Run: Alarm on Failure

Summary:Rerun: Alarm on Failure

If a result-based event (RBE) occurs (1), the Analyzer program turns on a panel light and/or a relay output (2) if specified in the RBE definition. The overlap flush program is run and then the sample is rerun (3).

• If the same RBE does not re-occur when the sample is rerun, the analyzer continues to the next line in the sequence (4).

• If the same RBE re-occurs, the Analyzer program starts running the alarm sequence (5). After each line in the alarm sequence is completed, the Analyzer program checks for RBEs. If no RBEs occurred, the alarm sequence


Doc. 031964-01 10/03 53

is ended, and the analyzer then continues to the next line in the original sequence (6). If an RBE occurs and the alarm sequence has not been completed, the next line in the sequence is run (7).

When all of the lines in the alarm sequence have been run, the Analyzer program checks whether a repeat is requested. If so, the alarm sequence is restarted (8). When there are no more repeats, the analyzer continues to the next line in the original sequence (even if RBEs are still occurring) (9).

Note: This action is different from the Run Sequence action in that the sequence does not continue running if no RBE occurs. Also, if the alarm sequence runs to completion, it can be repeated.


54 Doc. 031964-01 10/03

RBE Action=Re-Run: Check Standard: Calibrate on Failure


Doc. 031964-01 10/03 55

Summary:Rerun: Check Standard: Calibrate on Failure


If the same RBE does not recur when the sample is rerun, the analyzer continues to the next line in the sequence (4).

• If the same RBE recurs, the analyzer runs the check standard sequence (5).

• If the check standard sequence fails (as determined by the QNT file and the confidence interval specified for each system), the calibration sequence is run (6). After calibration, the QNT file for each system is updated and then the analyzer continues to the next line in the sequence (7).

• If the check standard sequence passes, the Analyzer program starts running the alarm sequence (8) (if one exists).

• After each line in the alarm sequence is completed, the Analyzer program checks for RBEs.

• If no RBEs occurred, the alarm sequence is ended, and the analyzer then continues to the next line in the original sequence (9).

• If an RBE occurs and the alarm sequence has not been completed, the next line in the sequence is run (10).

• When all of the lines in the alarm sequence have been run, the Analyzer program checks whether a repeat is requested. If so, the alarm sequence is restarted (11).

• When there are no more repeats, the analyzer continues to the next line in the original sequence (even if RBEs are still occurring) (12).


56 Doc. 031964-01 10/03

RBE Action=Re-Run: Check Standard: Standby on Failure


Doc. 031964-01 10/03 57

Summary:Rerun: Check Standard: Standby on Failure

If a result-based event (RBE) occurs (1), the Analyzer program turns on a panel light and/or a relay out (2) if specified in the RBE definition. The overlap flush program is run and then the sample is rerun (3).

If the same RBE does not re-occur when the sample is rerun, the analyzer continues to the next line in the sequence (4).

If the same RBE re-occurs, the analyzer runs the check standard sequence (5).

• If the check standard sequence fails (as determined by the QNT file and the confidence interval selected for each system), the Standby program for all systems in the analyzer is run (6). The analyzer then idles (runs existing conditions) until you click Resume on the Analyzer program Run page. When Resume is selected, the analyzer continues to the next line in the sequence (7).


• After each line in the alarm sequence is completed, the Analyzer program checks for RBEs.

• If no RBEs occurred, the alarm sequence is ended, and the analyzer then continues to the next line in the original sequence (9).





58 Doc. 031964-01 10/03

RBE Action=Re-Run: Check Standard: Continue on Failure


Doc. 031964-01 10/03 59

Summary: Rerun: Check Standard: Continue on Failure


If the same RBE does not recur when the sample is rerun, the analyzer continues to the next line in the sequence (4).

If the same RBE recurs, the analyzer runs the check standard sequence (5).

• If the check standard sequence fails (as determined by the QNT file and the confidence interval selected for each system), the analyzer continues to the next line in the sequence (6).


• After each line in the alarm sequence is completed, the Analyzer program checks for RBEs. If no RBEs occurred, the alarm sequence is ended, and the analyzer then continues to the next line in the original sequence (8).





60 Doc. 031964-01 10/03

RBE Action=Check Standard: Calibrate on Failure


Doc. 031964-01 10/03 61

Summary:Check Standard: Calibrate on Failure

If a result-based event (RBE) occurs (1), the Analyzer program turns on a panel light and/or a relay output (2) if specified in the RBE definition. The overlap flush program is run, followed by the check standard sequence (3).

• If the check standard sequence fails (as determined by the QNT file for each system), the calibration sequence is run (4). After calibration, the QNT files for each system are updated and then the analyzer continues to the next line in the sequence (5).







62 Doc. 031964-01 10/03

RBE Action=Check Standard: Standby on Failure


Doc. 031964-01 10/03 63

Summary:Check Standard: Standby on Failure


• If the check standard sequence fails (as determined by the QNT file and the confidence interval specified for each system), the program for all systems in the analyzer is run (4). The analyzer then idles (runs existing conditions) until you click Resume on the Analyzer program Run page. When Resume is selected, the analyzer continues to the next line in the sequence (5).

• If the check standard sequence passes, the Analyzer program starts running the alarm sequence (6) (if one exists). If an alarm sequence does not exist, the analyzer continues to the next line in the sequence.






64 Doc. 031964-01 10/03

RBE Action=Check Standard: Continue on Failure


Doc. 031964-01 10/03 65

Summary:Check Standard: Continue on Failure


• If the check standard sequence fails (as determined by the QNT file and the confidence interval specified for each system), the analyzer continues to the next line in the sequence (4).

• If the check standard sequence passes, the Analyzer program starts running the alarm sequence (5) (if one exists). If an alarm sequence does not exist the analyzer continues to the next line in the sequence.






66 Doc. 031964-01 10/03

RBE Action=Standby (System)

Summary: Standby (System)

If a result-based event (RBE) occurs when the selected action is Standby (System), the Analyzer program turns on a panel light and/or a relay out if specified in the RBE definition. The overlap flush program is then run, followed by the Standby program on the system that reported the RBE. The system then goes offline and remains offline until you click Resume on the Analyzer program Run page. While the system with the RBE is offline, the remaining systems in the analyzer continue running the sequence. When you click Resume, the offline system is synchronized with the other online systems.


Doc. 031964-01 10/03 67

RBE Action=Shutdown (System)

Summary: Shutdown (System)

If a result-based event (RBE) occurs when the selected action is Shutdown (System), the Analyzer program turns on a panel light and/or a relay out if specified in the RBE definition. The overlap flush program is run, followed by the shutdown program on the system that reported the RBE. The system then goes offline and remains offline until you click Start on the Analyzer program Run page. While the system with the RBE is offline, the remaining systems in the analyzer continue running the sequence. When you click Start, the offline system is synchronized with the other online systems.


68 Doc. 031964-01 10/03

3.12 Viewing Chromatograms

Chromeleon displays chromatograms of each sample that is run on the analyzer systems.

1. Click the Run tab to go to the Run page.

2. If the analyzer configuration tree (the left pane on the Run page) is hidden, click the vertical bar on the left side of the page.

3. Select the analyzer in which the system is configured and select the system name under the analyzer.

4. Go to Chromeleon by clicking the Direct Control button on the upper-right side of the page.

5. In the Chromeleon Browser, open the control panel for the system:

6. Open the Dionex Templates/Panels/Dionex_IC/DX-800 folder.

7. Double-click the panel that matches the instrument configuration for your system.

8. Connect the system to the panel by selecting Connect to Timebase from the Control menu. A dialog box appears. Select the system from the list and click OK.

9. Select Monitor from the Control menu. This ensures no direct control commands are inadvertently issued while the system is online with the analyzer.

Doc. 031964-01 10/03 69

4 • Reporting

4.1 About Reporting

The Analyzer program provides several reporting and printing options. Individual sample reports can be printed after each sample run is completed. Summary reports can also be scheduled to print at specified intervals, for example, daily or weekly. A scheduled summary report can include information for all analyzers, streams, and systems; or just the analyzer, stream, and/or system of interest.

Report templates define the information to be included in the report and how it is organized. Templates are created in Chromeleon. See Section 4.2 for details. The schedules for when to reports should be printed are created in the Analyzer program.

4.2 About Report Templates

Report templates determine the contents and organization of reports printed from the Analyzer program. The Analyzer program uses two basic types of report templates:

• End-of-run templates: These templates determine the contents of reports printed at the end of each sample run. An end-of-run report template is assigned to each system when it is configured on the Analyzer program Configuration page.

• An end-of-run report typically includes a chromatogram, a table containing information (height, area, amount, etc.) about each peak in the chromatogram, calibration curves and tables, and peak analysis information (height, width, type, resolution, etc.).

• Scheduled summary report templates: These templates determine the contents of reports printed at scheduled intervals. A report template is assigned to each

Note: This topic provides a brief description of report templates and how they are created. For detailed information, refer to the Chromeleon Help. In the Help keyword index, select Printer Layout>Actions.


70 Doc. 031964-01 10/03

scheduled report when it is created in the Analyzer program Manage Reports dialog box.

A scheduled summary report typically includes summary information and trend data plots.

Report templates are part of the report definition files created in Chromeleon. A report definition file has two purposes: it determines the sample information shown on the screen in Chromeleon (the screen report) and it determines the contents and organization of printed reports (the printer layout). For the end-of-run and schedule report templates used in the Analyzer program, the printer layout portion of the report definition file is most relevant.

Chromeleon provides example report definition files, which can be used either without modification or customized for your needs. The examples are available in the Chromeleon Browser in the Dionex Templates>Reports folder. When Chromeleon-PA is set up, report definition files (templates) are created for each system. Refer to Setting Up Chromeleon-PA (Document No. 031970) for details.

4.3 Enabling and Disabling End-of-Run Reports

1. Click the Configuration tab.

2. In the configuration tree (the left pane on the Analyzer program window), select the analyzer and then select the system. To display the configuration tree if it is hidden, click the vertical bar on the left side of the page.

3. On the right side of the window, select or clear the Print End-of-Run Report check box. If you select the check box, select the report template from the drop-down list. See Section 4.2 for more information.

Note: Because you typically do not want a printout of every sample in a scheduled report, the example scheduled report template prints the last sample in the sequence only.

Note: You can temporarily disable (suspend) end-of-run reports on the Run page. See Section 3.5 for more information.

Reporting

Doc. 031964-01 10/03 71

4.4 Scheduling Reports

You can schedule printing of reports at specified intervals. A scheduled report can include information for all analyzers, streams, and systems; or just the analyzer, stream and/or system of interest.

1. Click the Reporting button at the top of the Analyzer program window to open the Manage Reports dialog box.

2. Click the Add button.

3. Under Report # Properties, select how often to print the report, what information to include, and the report format.

• Under Interval, select how often to generate the report (the time between each report). For example, to print a report every 12 hours, select 12 and Hour(s).

• In the Beginning field, enter the starting date and time at which to begin counting the interval. For example, if the interval is 12 hours and you select today's date and the current time, the first report will print 12 hours from now. The Beginning date/time can be either in the future or in the past.

• In the Span field, select the range of data (the number of seconds, hours, days, weeks, or months) to be included in the report. The span begins at the specified number of seconds, minutes, hours, etc., before the first report is scheduled to print. For example, if the first report is scheduled to


72 Doc. 031964-01 10/03

print at 6:00 and the Span is 1 hour, the report will contain data from samples with an injection time between 5:00 and 6:00.

This example schedules a report to print once a week (Interval=1 week). The first report will print on Thursday Jan 08 at 9:00 (1 week from the Beginning date/time). It will contain data from all samples that have an injection time between Thursday Jan 01 and Friday Jan 02 (Span=1 day). The contents and format of the report is determined by the Format named Summary (System_A). Subsequent reports continue the schedule, printing once a week with data collected the previous day.

• Analyzer, Stream, System: Select the analyzers, streams, and systems to be included in the report.

• Format: Select the report template from the drop-down list.

• Description: Enter a description for the report that will appear in the list of reports at the top of the dialog box, or accept the default description.

4. Click Apply.

Reporting

Doc. 031964-01 10/03 73

If you specify a Beginning date/time that is in the past, the Analyzer program generates each separate report as required, and then queues them for printing. For example, to schedule a daily report that includes reports from the previous week, set the Beginning date/time to a week in the past and set the Interval to 1 day. The Analyzer immediately generates seven reports and sends them to the printer. Thereafter, a report will be generated once a day.

4.5 Suspending a Scheduled Report


2. In the list of reports, clear the check box for the report that you want to temporarily disable.

4.6 Modifying a Scheduled Report


2. In the list at the top of the dialog box, select the description of the report to be modified.

3. Click Properties.

Note: When you start the Analyzer program after a shutdown, the Analyzer prints the first report that would have printed had the program continued running, and then skips the remaining reports. The schedule then continues at the current date/time. This prevents a large backlog of reports from being sent to the printer. For example, a report is scheduled to print daily and the Analyzer program is shut down for a week. When the Analyzer program is restarted, the first of the seven queued daily reports is printed and the remaining six are skipped.

Note: To permanently remove a report, select it in the list and click Delete.


74 Doc. 031964-01 10/03

4. The current settings for the selected report appear. Change the settings as required:

• Interval: Select how often to generate the report and the date on which to begin generating reports.

• Analyzer, Stream, System: Select the analyzers, streams, and systems to include in the report.

• Span: Select the range of data (the number of hours, days, weeks, or months) to include in the report.

• Format: Select the report template from the drop-down list.

• Description: Enter a description for the report that will appear in the list of reports at the top of the dialog box, or accept the default description.

5. Click Apply.

4.7 Printing Reports Immediately


2. In the list at the top of the dialog box, select the description of the report to be printed.

3. Click Print Now.

This prints a report containing data from injections with a date/time stamp between the last scheduled report and the current date/time.

Doc. 031964-01 10/03 75

5 • Trending

5.1 About Trending

Trending provides a graphical display of selected data over time (for example, a plot of the peak height obtained for a particular component over the last 24 hours). A particular trend line can show data from all of the configured analyzers, streams, and systems, or can be limited to a single analyzer, stream, or system. In addition to plotting component variables (amount, area, height, retention time, etc.), you can plot instrument-specific variables (the detector's background signal, the pump pressure, etc.) and calculations (for example, the sum of multiple amounts). Multiple trend lines can be defined. They will be displayed simultaneously on the trend chart.

Various time range options are available for displaying data. For example, you can display data starting from a specified date/time in the past until the present and have the chart continuously updated, or you can display data between two fixed dates/times. Another option is to display all the data for a “window” of time (for example, the previous two days).

The combination of the defined trend lines, selected time range, and other viewing options determine the contents of the trend chart, or the trend view. Trend views can be saved and then reopened later. They can also be deleted.


76 Doc. 031964-01 10/03

5.2 Defining New Trend Lines

1. Click the Trending tab to view the Trending page.

2. On the left pane of the page, click Add. Note: If the left pane is hidden, click the vertical bar on the left side of the page.

The Define New Trend Line dialog box opens.

3. Specify the trend line label, color, and trend parameters:

Label: Enter a name for the trend line. The label will appear on the left pane of the Trending page. The default is Line # <edit name>. Line # is the number of defined plots +1.

Color: To change the color, click the button and select a different color from the dialog box, or define a custom color.

Analyzer: To include data from all of the configured analyzers, select All Analyzers. To restrict the trend plot to data from a particular analyzer, select the analyzer from the list.

Stream: To include data from all of the configured streams, select All Streams. To restrict the plot to data from a particular stream, select the stream from the list. If you selected a single analyzer above, the list will include only the streams for that analyzer.

Trending

Doc. 031964-01 10/03 77

Trend: Select this option if you want to plot results (amount, area, height, or retention time) for a component. Select the component from the list and then select the result variable. The list of available components depends on the settings selected for Analyzer and Stream.

Custom Formula: Select this option if you want to use a custom formula to define the data to be plotted. Custom formulas can include any Chromeleon report variable. Refer to the Chromeleon Help for a list and description of the report variables. In the Help keyword index, select Report Variables.

Units: If you are entering a custom formula, enter the formula units in quotes.

4. When the trend line definition is complete, click OK.

The defined trend line is listed on the left pane of the Trending page. The trend line is plotted, in the selected color, on the right pane.

5.3 Editing a Trend Line

1. Click the Trending tab to view the Trending page.

2. On the left pane of the page, select the trend line that you want to edit. Note: If the left pane is hidden, click the vertical bar on the left side of the page

3. Click Properties.

The Edit Trend Line dialog box opens.

4. Edit the trend line definition parameters as needed and then click OK.

Label: Enter a name for the trend line. The label will appear on the left pane of the Trending page. The default is Line # <edit name>. Line # is the number of defined plots +1.

Color: To change the color, click the button and select a different color from the dialog box, or define a custom color.

Analyzer: To include data from all of the configured analyzers, select All Analyzers. To restrict the trend plot to data from a particular analyzer, select the analyzer from the list.

Stream: To include data from all of the configured streams, select All Streams. To restrict the plot to data from a particular stream, select the stream from the list. If you selected a single analyzer above, the list will include only the streams for that analyzer.


78 Doc. 031964-01 10/03

Trend: Select this option if you want to plot results (amount, area, height, or retention time) for a component. Select the component from the list and then select the result variable. The list of available components depends on the settings selected for Analyzer and Stream.

Custom Formula: Select this option if you want to use a custom formula to define the data to be plotted. Custom formulas can include any Chromeleon report variable. Refer to the Chromeleon Help for a list and description of the report variables. In the Help keyword index, select Report Variables.

Units: If you are entering a custom formula, enter the formula's units enclosed in quotes.

5.4 Defining the Trend Range

1. To define the date/time range of the analyzer data that will be available for display on the trend graph, click the Define Range button at the top of the Trending Page.

The Please specify trend range lower/upper limits dialog box appears.

2. Click a Range Type:

Expanding: This option lets you specify a range at a starting date/time that is continually updated to include the current date/time.

Fixed: This option lets you define a range between two specific dates/times, or between a specific date/time and an earlier or later range of data (for example, 1 day).

Moving: This option lets you specify a moving “window” of trend data, for example, the last two months of data.

The controls in the dialog box vary, depending on the range type selected.

3. Define the trend range.

Trending

Doc. 031964-01 10/03 79

• To define an expanding range, select the starting date and time under Trend Start.

• To define a fixed range, choose one of the following methods:

1. Select specific start and end dates. Select the Date option for both the Trend Start and the Trend End.

2. Select a specific start date/time and a range for the end date/time. Select the Date option under Trend Start and select the Range option under Trend End. For example, select a start date of January 1 and select a range of 1 month to view trend data for the month of January.


80 Doc. 031964-01 10/03

3. Select a range for the trend start and select a specific end date/time. For example, select a start range of 24 Hours and an end date of today's date to view trend data for the past 24 hours.

• To define a moving range, select a specific starting date/time in the past or select a range. The Trend End is always the current date/time.

Trending

Doc. 031964-01 10/03 81

5.5 Working with Trend Views

A trend view is the combination of the defined trend lines, selected time range, and other viewing options that determine the contents of the trend chart. Trend views can be saved and then reopened later. They can also be printed or deleted.

Controls for saving, opening, printing, and deleting trend views are on the left pane of the Trending page. If the left pane is hidden, click the vertical bar on the left side of the page.

• To save a trend view, select New (enter name) from the drop-down list at the top of the pane. Type a name and click Save View.

• To open a saved trend view, select the name from the list of saved views.

• To delete a view, click Delete View.

5.6 About the Trend Chart

The trend chart displays plots of the defined trend lines.

The chart has the following basic features:

• The x-axis shows the date/time range of the defined trend data.

• The y-axis shows the data value range and units of the trend line selected in the list on the left pane of the page. The color of the y-axis matches the color of the selected line.

• Multiple trend lines are shown overlaid (each plot shares the same x- and y-axes).

• The chart scale can be changed by dragging the mouse over the desired data area or by right-clicking on the chart background and selecting a command on the shortcut menu.

• The size of the chart can be increased by selecting Hide Borders from the shortcut menu. This expands the chart to the full size of the Analyzer program window (the tabs, menus, and status bar are hidden). To return to the previous view, select Hide Borders again. You can also hide the left page (the Trend View list) to further increase the chart size.


82 Doc. 031964-01 10/03

5.7 Changing the Trend Chart Scale

By default, the trend plot is shown in full-scale view. To change the scale of the plot, use one of the following methods:

• Use the mouse to zoom into a portion of the plot.

a. Point the mouse to the area of the plot that you want to view. Press and drag the mouse. A bounding box appears.

b. Drag until the bounding box encloses the data you want to view and then release.

The selected data fills the chart.

• Right-click on the plot and select a scale command from the shortcut menu.

Auto Scale: Adjusts the plot scale to fit the currently displayed data.

Full Scale: Returns the plot scale to the full-scale view.

Undo: Cancels the last scale command. You can repeat the Undo command to return to any previous scale view until the full-scale view is reached.

Redo: Reinstates the last scale command after an Undo command.

Doc. 031964-01 10/03 83

A • Glossary

AAlternate start sequence: A sequence (typically started from an external command) that

is run at startup.

Analyzer: An analyzer is a group of chromatography instrument systems that operate synchronously to analyze a series of process sample streams. Analyzers are defined on the Analyzer program's Configuration tab.

BBatch: See Sequence batch

CCalibration sequence: The sequence used for routine calibration of the analyzer.

Check standard sequence: The sequence used to run check standards on the analyzer.

Confidence interval: The range in which the “true” calibration curve will be found with a given probability. For each system, you can select the probability at which the values for a check standard should fall within the confidence interval. The following options are available: 90%, 95%, 98%, 99%, 99.7% 99.8%, 99.9%, and 99.99%.

Correction factor: Compensates for any variance in loop volume from the assumed volume when measuring or delivering standards with the metering (ME) valve on theSP80. The correction factor is used to correct the amount values for the components in the calibration standard. To determine the correction factor, compare the results for a standard prepared by the instrument with a standard prepared by hand, or estimate the value by calculating the volume of the tubing.

Cycle time: Sets a uniform time between injections, regardless of differences processing parameters, including those for sample preparation. If the cycle time is set to 0, the time between injections is determined by the commands in the program specified for each injection in a sequence.


84 Doc. 031964-01 10/03

DDatasource: A database where Chromeleon stores and retrieves analysis data.

Default sequence: The sequence used for routine sample runs.

HHardware alarms: Alarms that occur in the analyzer system modules (the analytical

pump, detector, component controller) and are then communicated to the Analyzer program. Hardware alarms are classified as either fatal or non-fatal.

Host computer: The computer on which Chromeleon-PA is installed.

IInjection cycle time: See Cycle Time.

Injection volume: The injection volume, in microliters (µL), is used by Chromeleon to calculate the amount of a component in a sample. The size of the injection loop installed on the LC80 injection valve determines the actual volume injected by the CC80. The default injection volume (and loop size) is 20 µL. In most cases, you can use the default injection volume (even if the installed loop is not 20 µl), provided all of the samples have the same loaded volume and the amount calculation used in the report is not based on an actual volume. However, if the loaded volumes are different for different samples (for example, some samples are concentrated on a pre-column) or if the amount calculation is based on a specific volume, then enter the actual injection volume.

Internal standard amount: The amount of the internal standard added to the sample, which is implemented as a multiplication factor in the amount calculation formula.

PProgram (PGM): A list of instructions that tell a chromatography system how to prepare

a sample for analysis and/or how to analyze a sample. Programs are defined in the Chromeleon PGM Editor.

Glossary

Doc. 031964-01 10/03 85

QQuantification (QNT) method: Defines parameters for identifying the peaks within a

chromatogram and for calculating amount/concentration from the recorded peak areas (calibration). Quantification methods are created in the Chromeleon QNT Editor.

RReport: Defines parameters for reprocessing and displaying your results on the screen and

in printouts.

Result-based event: An event (for example, the start of a calibration sequence) that is triggered when the results from a run meet a pre-defined condition.

SSequence: A list of injections to be analyzed sequentially. The sequence can consist of

any combination of injection types (sample stream, calibration, check standard, blank, or matrix. Sequences are defined on the Analyzer program's Configuration tab.

Sequence batch: A list of sequences to be automatically processed on an analyzer. Sequences in the batch are processed in the order in which they are listed in the batch.

Stream: A sample, standard, blank, or matrix that enters the analyzer from the SS80 or from some other flow inlet. Streams are defined on the Analyzer program's Configuration tab.

System: A group of chromatography instruments configured to perform a specific analysis. Systems are defined in the Chromeleon Server Configuration program.

TTrend line: A plot of selected data (typically a component variable such as amount, area,

or height) over time


86 Doc. 031964-01 10/03

Doc. 031964-01 10/03 Index-1

Index

AAbout

alarms, 30analyzing streams, 35configuring analyzers and systems, 11operating systems offline, 44processing result-based events, 47report templates, 69reporting, 69sample parameters, 37sample preparation overlap, 38sequence runs, 36the Chromeleon datasource, 5the Event Monitor, 9the trend chart, 81the user interface, 7trending, 75

Actionconditional, 27result-based event, 29

Alarm sequence, 23, 47, 49Alarms, 18, 30 – 34, 47

actions, 33bypassing streams, 34CC80 front panel lights, 33conditional, 27configuring, 33hardware alarms, 18, 33ignoring, 33result-based events, 27, 47setting relays, 33, 47shutdown, 33standby, 33

Alert bar, 8Alternate start sequence, 25Analyzers, 11, 14, 16, 19, 35, 37

about configuring, 11about processing sample streams, 35

about sample parameters, 37assigning default sequences, 25configuring streams, 19creating, 14removing, 16renaming, 16

Auto scale, 82

BBatch, 39Blank, 19Bypassing streams, 19, 34

CCalibration, 20, 25, 44, 47

assigning default sequences, 25automatically after an event, 29, 47, 50of system components, 44

CC80 Component Controller, 1, 11, 17about configuring analyzers, 11configuring systems, 17front panel light, 29, 31, 33relay out, 19, 33TTL input, 17, 33

Changing, 82trend plot scale, 82Y-axis, 82

Check standard, 20, 25, 54assigning a default sequence, 25running automatically after an event, 27,

47Chromatogram, 68


Index-2 Doc. 031964-01 10/03

Chromeleon, 1, 5, 47, 68launching from the Analyzer program, 44running a system offline, 47viewing chromatograms, 68

Chromeleon server configuration, 16Chromeleon-PA, 1

components, 1data acquisition, 1datasource, 1, 5instrument configuration, 1instrument control, 1reporting, 1trending, 1

Client/server software, 1Color

changing trend plot colors, 76 – 77Component alarm, 11, 17, 27, 30, 47Conditional event, 27Configuration tree, 14Configuring, 11, 14, 17, 19

alarms, 33analyzers and systems, 1, 11hardware alarms, 33new analyzers, 14removing analyzers and systems, 16renaming analyzers, 16result-based events, 27streams, 19systems, 14, 17, 30

Control program, 11 – 12Controlling, 35

analyzer runs, 35Correction Factor, 17Creating, 12, 14, 22, 35

instrument control programs, 12new analyzers, 14sequence batches, 35sequences, 22

Cycle time, 22

DData acquisition, 1

Data processing, 1, 4Data system, 1Datasource, 1, 5Date/time, 75, 78, 81 – 82

changing the trend plot scale, 82defining the trend range, 78

Default programs, 11 – 12, 17Default sequences, 11, 25

assigning to an analyzer, 25Define Range button, 78Defining, 27, 76, 78

date/time, 78result-based events, 27trend lines, 76trend range, 78

Deleting, 22sequences, 22

Direct control, 47, 68operating systems offline, 44, 47viewing chromatograms, 68

Disablingreports, 73

DX-800 Process Analyzer, 1

EEditing, 22, 77

sequences, 22trend lines, 77

End-of-run report, 17, 70Event Monitor, 9Example programs, 13Example reports, 70Expanding trend, 78

FFatal hardware alarms, 18Fixed trend, 78Folder structure, 5Formula, 27 – 28Full size, 82

Index

Doc. 031964-01 10/03 Index-3

HHardware alarms, 17, 30, 33 – 34

IIgnoring alarms, 33Injection cycle time, 22Injection volume, 21, 37Injections

bypassing, 34Instrument control programs, 12, 17, 37

about sample parameters, 37assigning to systems, 17creating, 12datasource folder, 5examples, 13guidelines for creating, 12overriding the default, 21

Instruments, 1, 11Internal standard, 22, 37Interval, 74

MManually running streams, 41Matrix, 20Method, 1, 17Modifying a scheduled report, 73Moving trend, 78

NNon-fatal hardware alarms, 18

OOffline, 35, 44 – 45, 47OLE for Process Control, 2Online, 35, 44 – 45OPC, 2Operating

systems offline, 35, 44, 47See also Running

Overlap flush program, 12, 17Overlap of sample preparation, 36Override, 21, 24

PPGM

See Instrument control programsPlot, 82

changing the trend plot scale, 82defining new trend lines, 76defining the trend range, 78editing a trend line, 77working with trend views, 81

Preferred end-of-run report, 17assigning to systems, 17

Printing, 40, 69 – 71, 74about report templates, 69about reporting, 69end-of-run reports, 70reports immediately, 74scheduling reports, 71suspending end-of-run reports, 40suspending scheduled reports, 73

Processing, 35 – 36, 47about sample parameters, 37about sequence runs, 36creating sequence batches, 39operating systems offline, 44, 47placing analyzers in standby, 42resuming, 42running sample streams manually, 41starting, 42stopping, 42taking systems offline, 45

ProgramSee Instrument control programs

Properties, 73, 77, 82changing the trend plot scale, 82editing a trend line, 77scheduling reports, 73


Index-4 Doc. 031964-01 10/03

QQuantification method, 1, 17

assigning to systems, 17data processing, 4datasource folder, 5

RRange, 78, 82

changing the trend plot range, 82defining the trend range, 78

Range type, 78Redo, 82Relay out, 19, 30, 33Removing, 16

analyzers and systems, 16Renaming, 16

analyzers, 16Repeating sequences (looping), 40Repeats, 22, 40Reports, 69 – 71, 74

about report templates, 69about reporting, 69end-of-run, 70examples, 70modifying a scheduled report, 73printing immediately, 74scheduling, 71suspending a scheduled report, 73

Response, 27conditional, 27

Result-based events, 11, 27, 30about processing, 47alarm priorities, 32configuring alarms, 30 – 31defining, 27 – 30

Resuming runs, 35, 42, 46Running, 35 – 36, 47

about sample parameters, 37about sequence runs, 36creating sequence batches, 39placing analyzers in standby, 42

running a sequence after an event, 27running a system offline, 47running manual samples, 41running streams manually, 35, 41starting/stopping/resuming, 35, 42taking systems offline, 45

SSample name, 19Sample parameters, 37Sample preparation overlap, 36, 38Sample preparation program, 19, 37Sample streams

about analyzing, 35bypassing, 34configuring, 19running manually, 41

Saving trend views, 81Scheduled reports, 71

modifying, 73scheduling reports, 71suspending, 73

Sequence, 11, 22, 25assigning default sequences, 25creating, 22deleting, 22editing, 22running automatically after an event, 27

Sequence batches, 35, 39Set

trend date/time, 82Shutdown, 47

after an alarm, 47by hardware alarm, 33

Shutdown program, 12, 17Skipping injections, 34SS80 Sample Selector, 1, 11, 19, 45Standby, 33, 42, 47

after an alarm, 47automatically after an event, 27

Standby program, 12, 17

Index

Doc. 031964-01 10/03 Index-5

Start date/timespecifying the trend range, 78

Starting runs, 35, 40, 42at specific line numbers, 39

Status, 7Stopping runs, 42Streams, 11, 19, 35, 41

bypassing, 34configuring, 19running manually, 41

Suspending scheduled reports, 73Synchronized runs, 36Systems, 11, 16 – 17, 45, 47

assigning to an analyzer, 14configuring, 17removing from the configuration, 16running a system offline, 47shutdown in case of alarms, 33standby in case of alarms, 33taking offline, 45

TTemplates, 5Trend chart, 81Trend data, 78Trend end, 78, 82Trend line, 76 – 77

defining, 76editing, 77

Trend plot, 77, 81 – 82changing label fonts, 81changing plot colors, 77changing the scale, 82editing a trend line, 77

Trend range, 75, 78defining, 78

Trend start, 78, 82Trend views, 81Trending, 75, 81TTL input alarms, 30, 34

UUnassigned Systems list, 14, 16Undo, 82User interface, 7

VValve position, 19Viewing chromatograms, 68Volume, 21

WWindows Control Panel, 81

XX-axis, 82

YY-axis, 81 – 82


Index-6 Doc. 031964-01 10/03

Chromeleon-PA Analyzer User’s Guide€¦ · Chromeleon-PA Analyzer 2 Doc. 031964-01 10/03 •...

Documents

Transcript of Chromeleon-PA Analyzer User’s Guide€¦ · Chromeleon-PA Analyzer 2 Doc. 031964-01 10/03 •...