600 Series LINK Interface

Operator’s Manual
Release History

Part Number Release Publication Date

N515-6031 A March 2001

Any comments about the documentation for this product should be addressed to:
User Assistance
PerkinElmer Instruments LLC
710 Bridgeport Avenue
Shelton, Connecticut 06484-4794
U.S.A
Or emailed to: AI.UserAssistance@perkinelmer.com

Notices
The information contained in this document is subject to change without notice. PerkinElmer makes no
warranty of any kind with regard to the material, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose. PerkinElmer shall not be liable for errors contained
herein for incidental consequential damages in connection with furnishing, performance or use of this
material.

NOTE: TotalChrom is the updated version of the software previously marketed as Turbochrom. This
product is compatible with TotalChrom and Turbochrom version 6.1.x. The term TotalChrom has been
used throughout this document to denote either system.

Copyright Information
This document contains proprietary information that is protected by copyright.
All rights are reserved. No part of this publication may be reproduced in any form whatsoever or
translated into any language without the prior, written permission of PerkinElmer Instruments LLC.

Copyright © 2001 PerkinElmer Instruments LLC.

Trademarks
Registered names, trademarks, etc. used in this document, even when not specifically marked as such,
are protected by law.
PerkinElmer is a registered trademark of PerkinElmer, Inc.
TotalChrom, TurboScan, AutoSystem XL GC, and 600 Series LINK Interface are trademarks of
PerkinElmer Instruments LLC
 Table of Contents

Chapter 1 Introduction .......................................................................................1

Chapter 2 Installation .........................................................................................3

Safety and Site Data .................................................................................................................... 4
Power Connections and Fusing ................................................................................................... 5
Back Panel Connections.............................................................................................................. 6
Instrument Ports ................................................................................................................... 6
Configuration Switches ........................................................................................................ 8
Host Communications ........................................................................................................ 10
Host GPIB Port .................................................................................................................. 10
Host RS-232 Port ............................................................................................................... 11
Auxiliary Ports ................................................................................................................... 12

Chapter 3 Operation .........................................................................................13

Power-On LED Sequence ......................................................................................................... 13
Status LEDs............................................................................................................................... 15

Chapter 4 Technical Data .................................................................................17

Functional Description .............................................................................................................. 17
CPU.................................................................................................................................... 17
Memory.............................................................................................................................. 17
Firmware ............................................................................................................................ 17
Diagnostics................................................................................................................................ 18
Troubleshooting Guide.............................................................................................................. 19
LINK Error Messages ............................................................................................................... 22
Warranty/Service....................................................................................................................... 28
Specifications ............................................................................................................................ 28

Index

i
 Chapter 1
Introduction

The PerkinElmer 600 Series LINK Interface is used with PerkinElmer software products to
acquire and buffer digital data from laboratory instruments and to control the operating
parameters of such instruments. The LINK Interface is available in two forms. The Models 600
and 610 are standalone modules that connect to both the host computer and to the controlled
instrument. The Integral LINK (Model 680) is a version of LINK that is installed inside the
AutoSystem GC. Each standalone LINK module can simultaneously communicate with up to
four instruments. Each Integral LINK module communicates with the single instrument in
which it is installed. The operation of these various models is otherwise identical from the user
perspective; only the cabling is different. Data acquired from each instrument are buffered
within LINK until the data can be transmitted to the host computer. There is no user interface
for the LINK Interface; all user interaction is with the software running on the host computer.
Internal to the LINK Interface is a HD64180 microprocessor that executes firmware located in
an Instrument Personality Module (IPM). The IPM is copied to the LINK Interface from the
host computer mass storage by a Configuration Utility executed on the host computer. During
execution of the Configuration Utility, the user provides information regarding the type of
instrument connected to each port, allowing the host software to select one or more IPMs to be
down-loaded. Once an IPM is installed in the LINK Interface, the user interacts with the
PerkinElmer software running on the host computer to specify the instrument operating
parameters. LINK then receives instructions from the host computer and formats and transmits
commands to the connected instrument. Data and status information are received from the
instrument by LINK, formatted as necessary, and transmitted to the host. If the host or
intervening network is unavailable, the LINK Interface will buffer the information until it can
be transmitted.

1
Safety and Site Data

Instructions from the host to LINK can be sent as methods or setpoints. Methods include an
entire set of parameters sufficient to initiate and execute an analysis on an instrument. Setpoints
are used to modify a single parameter during an analysis. LINK is capable of storing multiple
methods for each connected instrument, allowing sequences of multiple methods to be
executed, even when the host computer is not available.
The exact set of method parameters that can be controlled for a given instrument are dependent
on the characteristics of that instrument. These parameters are described in the documentation
that accompanies the IPM distribution media for the specific instrument.
Instrument Personality Modules are stored in non-volatile memory in the LINK Interface. Re-
configuration is not required after cycling power on the Interface. However, buffered data will
be lost if power is interrupted, as will method and sequence information stored in LINK for
later analyses.
The amount of data that can be buffered by a LINK Interface is dependent on several factors,
including the LINK model, the instrument(s) connected to the LINK Interface, and the number
of methods stored in the LINK Interface. As an example, a Model 600 LINK or Model 680
Integral LINK connected to a single AutoSystem GC, with a single stored method, has buffer
for approximately 64000 data points. Each stored method reduces the buffer capacity by
approximately 500 data points. Additionally connecting a Hewlett Packard 5890A GC reduces
the buffer capacity by approximately 2500 data points. Using a Model 610 LINK Interface,
with 1 MByte of memory in contrast to the 256 KByte memory of a Model 600, would increase
the capacity by approximately 195,000 data points.

2 Chapter 1
 Chapter 2
Installation

The 600 Series LINK Interface is designed for easy customer installation. Depending on the
host data system, either a GPIB (IEEE-488) cable or an RS-232 cable should be purchased
with the Interface. If a cable was not purchased, refer to “Host Communications” on page 10
for further information. A power cord is provided with each Interface.
There are NO internal settings or adjustments for the user to change.
The installation procedure requires four steps:
1. Select the correct power line voltage (standalone units only).
2. Select host communication parameters using the Configuration Switches.
3. Connect a cable from the LINK Interface to the host computer or terminal server.
4. Connect a cable from the LINK Interface to each instrument to be controlled.
Details on each of these steps are provided in the following sections.

3
Safety and Site Data

Safety and Site Data

The 600 Series LINK Interface contains no user-serviceable parts. Therefore, there is no
reason to remove the top cover in normal usage. Should you remove the top cover for any
reason, disconnect the power cord from the Interface before removing the cover.

FCC Notice
This equipment generates, uses, and can radiate radio frequency energy and if not installed and
used in accordance with the instruction manual, may cause interference to radio
communications. It has been tested and found to comply with the limits for a Class A
computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to
provide reasonable protection against such interference when operated in a commercial
environment. Operation of this equipment in a residential environment is likely to cause
interference in which case the user at their own expense will be required to take whatever
measures may be required to correct the interference.
When installing this equipment, shielded cables must be used on all connections.

EMC Directive (European Union)

This equipment is intended for use in industrial and commercial locations. EN 55022 Class A
ITE radio interference limits may not be suitable in certain situations where the equipment is to
be used on low voltage power supply networks which supply buildings used for domestic
purposes.

Compliance with Canadian Radio Interference Regulations

The following statement is supplied in compliance with Canadian Radio Interference
Regulations (C.R.C., c. 1374):
This device has been tested and found to comply with the limits for a Class A computing
device pursuant to Section 23 of the Canadian Radio Interference regulations, which are
designed to provide reasonable protection against such interference when operated in a
commercial environment.

4 Chapter 2
 Power Connections and Fusing

Power Connections and Fusing

This section applies to standalone LINK Interfaces only.
The 600 Series Link Interface is a Safety Class I apparatus according to IEC Standard 950, that
is, it uses a three-conductor line cord. Before turning the unit on, check that the proper line
voltage has been selected in the fuse module at the back of the interface. Otherwise serious
damage to the Interface may occur. The line cord plug should only be inserted in a receptacle
provided with a protective earth contact. The protective earth ground contact should not be
disconnected for any reason. To do so will interfere with the proper operation of the Interface.
The Interface will operate at any one of five line voltages: 100/120/220/230/240 VAC.
Refer to the fuse module at the lower rear of the Interface (Figure 1). The fuses and voltage
selector may be exposed by unsnapping the plastic cover.

Be sure the power cord is disconnected from the interface before proceeding.

In order to change the voltage, the voltage selector must be removed from the fuse module and
then reinserted into the fuse module with the selected voltage value facing outward. For 230
VAC nominal line voltage, use the 240 VAC position.

Do not attempt to rotate the voltage selector while it is still in the fuse module.

The fuse holders accommodate either two "Normal-Blow" 3AG type (1-1/4" x 1/4") or two
DIN (5 x 20 mm) fuses. The 3AG type are intended for North American installations and the
DIN type for European and other installations. Use 0.25 amp fuses when using 220/230/240
volt line power and 0.5 amp fuses when using 100 or 120 volt line power. The fuse containers
should be inserted with their arrow indicators pointing down.

Caution: The fuse holder incorporates double-pole/neutral fusing.

Caution: For continued protection against risk of fire, replace only with the same type and
rating of fuse.
Avertissement: Pour assurer une protection continue contre les risques d'incendie, remplacer
uniquement par un fusible de même type et de même calibre.

Installation 5
Back Panel Connections

Back Panel Connections

Instrument Ports
Each standalone LINK Interface has four RS-232D Instrument Ports located on the back panel
(Figure 1). These ports (Inst A, Inst B, Inst C, and Inst D) are used to communicate command
parameters, data, and status between the LINK Interface and instruments controlled through the
Interface.
Each Integral LINK in an AutoSystem GC has two instrument ports. A captive cable is
supplied to connect the first port to the AutoSystem’s External Communications Port (RS-232)
under the Electronics Access Panel on the top of the AutoSystem. The second instrument port
is available for use with an associated device such as a PerkinElmer HS-40 Automated
Headspace Sampler.
An instrument system may require connection to one or more Instrument Ports; for example, a
gas chromatographic system may require one connection to the chromatograph and one
connection to the autosampler. In cases where multiple connections are required for a single
system, adjacent ports must be used. Detailed connection requirements are provided in the
instructions that accompany each Instrument Personality Module distribution package.
The communication characteristics (baud rate, parity, handshaking, etc.) of each Instrument
Port are controlled by the IPM installed for that port. Cables should be purchased for each
instrument with the IPM package; if a cable is not purchased one can be constructed based on
the requirements specified in the IPM documentation. The pinouts for the Instrument Ports are
listed in Table 1. A specific instrument may not require the connection of all lines.
Table 1 - Instrument Port Pinouts

Pin Usage Description

1 --- Frame Ground
2 Output Transmit Data
3 Input Receive Data
4 Output Request to Send
5 Input Clear to Send
6 Input Cable Detect (cable to short to pin7)
7 --- Signal Ground
8 Output Data Terminal Ready
9 Input Data Set Ready

6 Chapter 2
 Back Panel Connections

Figure 1 - Back Panel Connections

Installation 7
Back Panel Connections

Figure 2 - AutoSystem GC with Integral LINK — Right Side Panel Connections

Configuration Switches
The Configuration Switches are used to set the GPIB address or RS-232 baud rate and parity
for communication between the LINK Interface and the host computer. These switches can also
be used to select the self-test function.
On standalone LINK Interfaces, the Configuration Switches are located on the back panel
(Figure 1) and are labeled SETUP. For Integral LINK Interfaces, the switches are located on
the AutoSystem right side panel (Figure 2). They are numbered 1 through 8 from left to right
and are OFF when pushed in at the bottom and ON when pushed in at the top. The Interface
reads the state of the switches only as the Interface is powered on. To change the Configuration
Switch settings, switch the Power OFF, reset the switches, and switch the Power ON.
The function of each of the switches is listed in Table 2. Setting all the switches ON causes the
Interface to perform a continuous Self-Test at Power-On. This is used for troubleshooting only.
The factory default for all switches is OFF. Switches 1 through 5 have a dual function. If
switch 6 specifies GPIB operation (OFF position), then 1 through 5 provide the GPIB address;
otherwise 1 through 5 specify the RS-232 parameters.

8 Chapter 2
 Back Panel Connections

Table 2 - Configuration Switch Functions

DIP GPIB Function RS-232 Factory Default

Function (OFF)
1 GPIB Address BAUD Rate GPIB Address =
0/9600 baud
2 GPIB Address BAUD Rate " "
3 GPIB Address BAUD Rate " "
4 GPIB Address Parity " " No parity
5 GPIB Address Stop bits " " 1 stop bit
6 GPIB/RS-232 GPIB
Select
7 GPIB Controller Not Controller
8 Factory OFF
diagnostics

The settings required for specific addresses or baud rates follow in the “Host Communications”
section.

Installation 9
Back Panel Connections

Host Communications
Depending on the type of host computer system, the LINK Interface communicates to the host
using either the GPIB port or the Serial/Host (RS-232) port (Figures 1 and 2).
Host GPIB Port
The GPIB Port is just above the fuse module on the back panel of the Interface (Figure 1) or on
the AutoSystem right side panel (Figure 2). Use a shielded cable to connect this port to the
GPIB port of the host computer. When connecting, do not overtighten screws. Do not put more
than two connectors on the Interface port.
Each Interface (both LINK Interfaces and 700, 800, and 900 Intelligent Interfaces) connected
to the host computer must have a unique GPIB address. Interfaces are shipped with address 0
selected. Refer to the Installation section of your PerkinElmer data system manual for any
GPIB address conflicts. The GPIB address must be set using the Configuration Switches in
accordance with Table 3. In all cases SW6 must be OFF to select GPIB communications.
The host application software will automatically determine the GPIB addresses in use and the
type of interface connected.
Table 3 - GPIB Address Selection

Address SW 1 SW 2 SW 3 SW 4 SW 5
0 OFF OFF OFF OFF OFF
1 ON OFF OFF OFF OFF
2 OFF ON OFF OFF OFF
3 Host Controller Address
4 OFF OFF ON OFF OFF
5 ON OFF ON OFF OFF
6 OFF ON ON OFF OFF
7 ON ON ON OFF OFF
8 OFF OFF OFF ON OFF
9 ON OFF OFF ON OFF
10 OFF ON OFF ON OFF
11 ON ON OFF ON OFF
12 OFF OFF ON ON OFF
13 ON OFF ON ON OFF

10 Chapter 2
 Back Panel Connections

Address SW 1 SW 2 SW 3 SW 4 SW 5
14 OFF ON ON ON OFF
15 ON ON ON ON OFF

Host RS-232 Port

The Serial/Host Port is on the right side of the back panel (Figure 1) or on the AutoSystem
right side panel (Figure 2). An RS-232 cable should be purchased with the Interface. Connect
the cable by inserting one end into the Serial/Host Port connector and tightening the lock posts.
Attach the other end of the cable to a serial port on the host computer or terminal server.
Since the LINK Interface is normally configured at the factory for GPIB operation, it must be
reconfigured for RS-232 operation and the baud rate must be set as described in Table 4.The
normal parameters are 9600 baud, no parity, 1 stop bit. SW6 must be set ON to select RS-232
communication.
Table 4 - Host/Serial RS-232 Configuration

Baud rate SW1 SW2 SW3 SW4 SW5

9600 Baud OFF OFF OFF
4800 Baud ON OFF OFF
2400 Baud OFF ON OFF
1200 Baud ON ON OFF
600 Baud OFF OFF ON
300 Baud ON OFF ON
No Parity OFF
Odd Parity ON
1 Stop Bit OFF
2 Stop Bits ON

Installation 11
Back Panel Connections

If a cable was not purchased with the Interface, one can be constructed using the information in
Table 5.
Table 5 - Host/Serial Port Connections

Interface Pin Host Pin (typical) Description

1 1 Frame Ground (shield)
2 3 Transmit Data (to host)
3 2 Receive Data (from host)
7 7 Signal Ground

Serial communication requires that all active ports be identified to both the terminal server
software (if any) and the host application software. Refer to the installation documentation for
your data system for further instructions.

Auxiliary Ports
Auxiliary Ports E and F are not currently used.

12 Chapter 2
 Chapter 3
Operation

The operation of the LINK Interface is directed via the software executing on the host
computer. The manuals associated with the host software provide detailed instructions on
configuring and operating the LINK interface. The status of the LINK Interface is monitored
through the use of the host software.
Each standalone LINK provides a simple indication of its status using a set of LEDs located on
the front panel (Figure 3). At the time of Power-On, these LEDs provide a visual indication of
the progress of the Self Test. Any failure at this time will be indicated as described in “Power
On LED Sequence” on page 13. During routine operation, these LEDs provide an indication of
the activity on each Instrument Port, as described in “Status LEDs” on page 15.

Power-On LED Sequence

This section applies to standalone LINK Interfaces only.
At Power-On, the LINK Interface performs a self-test, including a partial memory test (a
complete memory test, which requires nearly 1 minute for a Model 610, is performed by the
Continuous Self-Test described in the “Troubleshooting Guide” on page 19). During the test
the front panel LEDs display the status of the test. When the power switch is set ON, the
POWER LED should come on and remain on. The other LEDs should blink in the pattern
described in Table 6, remaining in state 5 at the completion of the test. (For this test, all four
Channel Error LEDs operate together, as do the Channel Active and Channel Ready LEDs). If
the LEDs do not step through the sequence of Table 6, and/or do not stop in state 5, then the
self-test has failed. In this case, refer to “Diagnostics” on page 18.

13
Power-On LED Sequence

Table 6 - LED Power-On Sequence

LED STATE
1 2 3 4 5
Ready (Chan A-D) X X
Active (Chan A-D) X X
Error (Chan A-D) X X
System Ready X X
X = ON, Blank = OFF

Figure 3 - Standalone LINK Interface Front Panel LEDs

14 Chapter 3
 Status LEDs

Status LEDs
This section applies to standalone LINK Interfaces only.
After the completion of the Self-Test, the System Ready LED will remain ON. When
communication between the host computer and the LINK Interface occurs, the System Ready
LED will blink.
The four sets (A, B, C, and D) of Channel LEDs (Ready, Active, and Error) provide status
information for each of the four instruments that can be controlled by a single LINK Interface.
Each set of Channel LEDs is associated with the corresponding Instrument Port.
Each READY LED is set ON when the host software takes control of the corresponding
channel during the installation of the IPM. The READY LED remains ON until a RESET
command is received from the host or the power is cycled to the LINK interface. The ACTIVE
LED blinks whenever communication (data, status, commands, etc.) occurs between the LINK
interface and the instrument. The ERROR LED is set ON whenever the corresponding
instrument reports an error or the LINK interface detects an error in communicating with or
controlling the instrument. The ERROR LED is subsequently set OFF when the host software
requests an error report.

Operation 15
Status LEDs

16 Chapter 3
 Chapter 4
Technical Data

Functional Description
The descriptions in this section are not intended to be a technical definition of the LINK
interface. Rather, they are provided for those situations in which a better understanding of the
interface may aid in its application.

CPU
The system is based on a 64180 8-bit CPU operating at 6.122 Mhz. This highly integrated CPU
includes DRAM refresh control circuitry, an interrupt controller, a memory management unit,
and two UARTs. Two additional dual UARTs are located on the System PCB. Each of the
UART ports may be individually programmed for baud rate and other communication
parameters.

Memory
The memory of the LINK interface is partitioned into four parts: 32 KBytes of Static Random
Access Memory (SRAM), 64 KBytes of Erasable Programmable Read Only Memory
(EPROM), 32 KBytes of Non-Volatile Static Random Access Memory (NVSRAM), and either
256 KBytes (Model 600) or 1 MByte (Model 610) of Dynamic Random Access Memory
(DRAM). The SRAM is used for temporary storage of program data, the EPROM contains the
LINK operating system firmware, the NVSRAM stores the Instrument Personality Module(s)
down-loaded from the host computer, and the DRAM stores the acquired data and instrument
methods and sequences. The non-volatile characteristic of the NVSRAM results from a battery
internal to the integrated circuit package; the life expectancy of the battery is in excess of 10
years.
Firmware
The operation of the LINK interface is controlled by firmware, a set of processor instructions
stored in the memory of the interface. The firmware is partitioned into two sections. The LINK
Operating System (LINK O/S) is permanently stored in the EPROM. This portion of the
firmware provides a variety of low level functions, including diagnostic tests, and provides the
basic start-up functions necessary to communicate with the host computer.

17
Diagnostics

The second portion of the firmware is the Instrument Personality Module, which is down-
loaded (copied) from the host computer into NVSRAM during execution of the instrument
configuration utility on the host computer. The IPM incorporates the processor instructions that
perform operations that are unique for a specific type and model of instrument. A LINK
Interface can store two IPMs, both of which can be active. After an IPM is down-loaded, it is
“installed” on one or more Instrument Ports, at which time the IPM becomes responsible for all
communication through the port. A standalone LINK Interface can support any combination of
up to two IPMs and up to four instruments (subject to the four port limit for instruments that
require more than one port) are permitted. An Integral LINK Interface can support a single
IPM for the instrument on which it is installed.
Since the IPM is stored in NVSRAM, disconnecting power to the LINK Interface will not erase
it. Additionally, sufficient information is stored in the NVSRAM to install the IPM on the
correct ports to restore the configuration that existed prior to the power failure. However,
stored data is not preserved during a power failure; any data not sent to the host before a power
failure will be lost. Any active data acquisition will be terminated by a power failure and can be
restarted only through the host computer.

Diagnostics
All LINK Interfaces perform a self-test whenever power is applied to the Interface, as
described in Chapter 3, “Operation.” Following a successful self-test, the LINK Interface will
begin to communicate with the host computer. If the self-test is not successful, the Interface
will not communicate with the host computer.
In addition to this routine self-test function, an extended self-test is provided in standalone
LINK Interfaces. The extended self-test, including testing each memory address, can be
initiated using the Back Panel Configuration Switches as described below. The progress of the
self-test is indicated by the front panel LEDs. In the event of a failure, the LEDs provide
diagnostic information. It is advisable to perform the complete self-test on a periodic basis, and
prior to contacting the PerkinElmer Service Department if the Interface is not functioning
correctly.
To initiate the extended self-test of a standalone LINK Interface, perform the following steps:
1. Set the Interface Power OFF.
2. Set all eight Back Panel Configuration Switches to the ON position.
3. Set the Interface Power ON.
4. The normal LED pattern is as follows:
a. All LEDs momentarily ON.
b. Power, Channel B Error, and Channel C Ready On; all other LEDs OFF.
c. Power, Channel B Active and Error, and Channel C ON; System Ready,
Channel A Ready, Active, and Error, and Channel B Ready blinking at
varying rates; all other LEDs OFF.

18 Chapter 4
 Troubleshooting Guide

The blinking LEDs cited in 4c (System Ready, Channel A Ready, Active and Error, and
Channel B Ready) indicate the progress of a single self-test cycle. The Channel C and D LEDs
indicate the cycle number currently in progress. The cycle number is represented in octal
notation, with the C LEDs indicating the units digit (Ready = 1, Active = 2, Error = 4) and the
D LEDs indicating the 8's digit. For example, the eleventh cycle would be indicated by the
Channel D Ready LED and the Channel C Ready and Active LED.
Successive self-test cycles proceed at slower rates to fully test the DRAM refresh logic.
If the self-test fails, the System Ready LED and two or more of the Channel C and Channel D
LEDs will flash a repeating S-O-S pattern (3 short blinks, 3 long blinks, 3 short blinks). If this
happens, the Channel A and Channel B LEDs provide an indication of the nature of the failure.
Contact the PerkinElmer Service Department (see “Warranty/Service” on page 28) for further
assistance.

Troubleshooting Guide
If the LINK Interface is not operating correctly, turn it OFF using the back panel Power switch
of a standalone LINK or the AutoSystem power switch for an Integral LINK. Wait a few
seconds and switch the Power ON again. If one or more of the following symptoms occur,
perform the described action.
1. Failure to Communicate With Host Computer
IEEE-488 (GPIB) Communications
GPIB communications failures are often obscure and difficult to pinpoint. The
symptoms are usually an Interface that is not recognized during Configuration or a
communications error reported during the process of taking control of an instrument.
Improper cabling, poor connections, dirty contacts, failing bus drivers or weakened
bus controllers may all contribute to the problem. Check that you are using cables that
are properly shielded with metal shields at the connectors. If the total cable length
exceeds twenty meters or two meters per segment it is very important that the cables
be properly grounded at both ends. Make sure that all contacts are clean and not bent
as a result of improper insertion. Ensure that all connections are snug but DO NOT
OVERTIGHTEN. If these actions do not correct the problem then the symptoms may
be due to current overloading or excessive bus noise. Record the number and type of
components on the bus and the cabling configuration. Then contact the PerkinElmer
Service Department (refer to “Warranty/Service” on page 28) for further assistance.
RS-232 Serial Communications
RS-232 communication to the host computer is generally accomplished through a
terminal server attached to a network, thereby introducing several points for potential
communication problems. A typical problem is inconsistencies in the configuration
information that is provided to the terminal server, to the server software on the host
computer
(e.g., LTLOAD.COM for ACCESS*CHROM), and to the host application (e.g.,
SYSCONFIG for TotalChrom C/S or NELSON.CONF for ACCESS*CHROM).

Technical Data 19
Troubleshooting Guide

Inconsistencies in this data can result in an Interface that does not respond. Problems
can also arise from unexpected sources, such as an inappropriate request for a port
connection from an application running on another network node.
If you are not using a cable supplied by PerkinElmer, refer to “Host RS-232 Port” on
page 11 to ensure that your cable makes the correct pin connections.
Another common problem is an incorrect baud rate. Make sure that the baud rate
specified in the host application configuration and on the Interface Configuration
Switches (refer to “Configuration Switches” on page 8) agree. Also verify that the
server port is configured for 8 data bits, 1 stop bit, no parity.
A useful test to verify that all the configuration information and cabling is correct is to
temporarily replace the Interface with a terminal configured for 9600 baud, 8 data
bits, 1 stop bit, and no parity. Then perform a Channel Reset from the host
application. If no characters are received by the terminal, then either the cabling or the
server hardware is defective, or the server configuration is invalid. If characters are
received and displayed by the terminal, then the Interface is probably malfunctioning.
To obtain additional assistance with problems related to host serial communication in
North America, telephone the PerkinElmer Customer Support Department at 800-762-
4000. In other areas, please contact your local PerkinElmer support office.
2. No Front Panel LEDs ON (standalone LINK only)
a. Check the power cord for proper connection to an operative power receptacle.
b. Check the fuses in the fuse module (refer to “Power Connections and Fusing” on page
5 for further information).
c. Check the line voltage setting on the fuse module (refer to “Power Connections and
Fusing” on page 5 for further information).
3. LEDs Continue to Blink After Self-Test (standalone LINK only)
This indicates an error occurred during the self-test. Refer to “Diagnostics” on page
18 for further information. This usually requires that the Interface be returned for
repair. Refer to “Warranty/Service” on page 28 for further instructions.
4. All LEDs Blinking Rapidly -or- All LEDs Remain ON (standalone LINK only)
If the problem recurs after cycling power, contact the Service Department as described
in “Warranty/Service” on page 28. If the problem does not recur, there are two
possible explanations.
The LINK Interface has extensive shielding against electrostatic discharge (ESD), the
integrity of which may have been compromised or bypassed. Make sure that nothing
has been added to the Interface other than the approved connections.
Check that all connections are properly shielded and grounded. Despite the ESD
protection, sufficiently intense discharges can damage the Interface. While the

20 Chapter 4
 Troubleshooting Guide

Interface can recover from one or more ESD events, multiple events can weaken the
shielding components and lead to permanent failure. If you suspect that ESD is a
problem, ensure that your installation protects both the Interface and other equipment
from large discharges.
A second possibility is that some component is intermittently failing for reasons other
than ESD degradation. Use the Interface only when its operation can be isolated and
observed. If the problem is caused by a component failure, it should quickly become
reproducible.
5. Power LED ON But Self-Test Not Executed (standalone LINK only)
Return the Interface for service as described in “Warranty/Service” on
page 28.
6. All Channel ERROR LEDs ON Within a Few Seconds of Power-Up
(standalone LINK only)
If using serial communication with ACCESS*CHROM, verify that the host port is
correctly configured as an application port. This symptom usually results from the
LINK Interface receiving a LOGIN prompt from the host computer.

Technical Data 21
LINK Error Messages

LINK Error Messages

The following errors may be reported by the host software. Following each error is a
description of potential problems that may result in the error message. Additional IPM-specific
errors are documented in the various IPM Installation Manuals.
0 No error occurred.
ERROR command was given and no error had occurred.
1 File already exists.
A Task tried to create a file, but it already exists.
Probably result of bug in IPM.
Could be result of corrupted IPM.
Could be result of bug in LINK OS EPROM.
2 File does not exist.
A Task tried to access a non-existent file.
Probably result of bug in IPM.
Could be result of corrupted IPM.
Could be result of bug in LINK OS EPROM.
3 PCB is already open.
A Task tried to open a Pipe Control Block that was already being used.
Probably result of bug in IPM.
Could be result of corrupted IPM.
Could be result of bug in LINK OS EPROM.
4 File is already open.
A Task tried to open a file that was already open.
Probably result of bug in IPM.
Could be result of corrupted IPM.
Could be result of bug in LINK OS EPROM.
5 File is protected (read only) !
A Task tried to write to a file that is read only.
Probably result of bug in IPM.
Could be result of corrupted IPM.
Could be result of bug in LINK OS EPROM.
6 PCB has no open file. No file was open.
A Task tried to read from or write to a file that had not been opened yet.
Probably result of bug in IPM.
Could be result of corrupted IPM.
Could be result of bug in LINK OS EPROM.

22 Chapter 4
 LINK Error Messages

7 File not open for write.

A Task tried to write to a file that had not been opened yet.
Probably result of bug in IPM.
Could be result of corrupted IPM.
Could be result of bug in LINK OS EPROM.
8 File not open for read.
A Task tried to write to a file that had not been opened yet.
Probably result of bug in IPM.
Could be result of corrupted IPM.
Could be result of bug in LINK OS EPROM.
9 Illegal calling parameters.
A Task tried to write to a file that had not been opened yet.
Probably result of bug in IPM.
Could be result of corrupted IPM.
Could be result of bug in LINK OS EPROM.
10 Ran out of memory.
LINK is not supposed to begin a run if there would not be enough space to hold all the
data.
Probably result of bug in IPM.
Could be result of corrupted IPM.
Could be result of bug in LINK OS EPROM.
11 Ran out of directory entries.
LINK has a limit of 512 files. This error could result from a lot of very short runs.
Probably result of connecting too many instruments to LINK.
Could be result of bug in IPM.
Could be result of corrupted IPM.
Could be result of bug in LINK OS EPROM.
12 Ran out of Task Control Blocks.
This is probably the result of a task which creates new tasks but fails to return Task
Control Blocks to system when done. May require that the rogue task execute several
times before error occurs.
Probably result of bug in IPM.
Could be result of corrupted IPM.
Could be result of bug in LINK OS EPROM.
13 Memory Pool does not exist for this file.
This error should never occur.

Technical Data 23
LINK Error Messages

14 Unexpected end of file or device timed-out.

Probably result of communications failure via Serial Port.
Could be result of bug in IPM.
Could be result of corrupted IPM.
Could be result of bug in LINK OS EPROM.
15 Ran out of Pipe Control Blocks.
This is probably the result of a task which requests Pipe Control Blocks from System
but fails to return them when done. May require that the rogue task execute several
times before error occurs.
Probably result of bug in IPM.
Could be result of corrupted IPM.
Could be result of bug in LINK OS EPROM.
16 Pipe Control Block not assigned to Task yet.
Probably result of bug in IPM.
Could be result of corrupted IPM.
Could be result of bug in LINK OS EPROM.
17 Illegal filename.
Illegal characters were given in a filename.
Probably result of bug in Host control program.
Could be result of bug in IPM.
Could be result of corrupted IPM.
Could be result of bug in LINK OS EPROM.
18 File is erased.

19 This is a DEVICE not a file.

An operation was attempted on a device that only applies to a file.
20 File is too large.
This error results if you try to download an IPM that is larger than 16K bytes.
Probably result of bug in Host control program.
Could be result of a corrupted IPM file at Host computer.
21 BIN failed verification during write operation.
When you download an IPM, LINK always verifies that it got written correctly. If
verification fails then this error would result.
Probably result of missing SRAM chip(s).
Could be result of defective SRAM chip(s).
Could be result of bug in Host control program.

24 Chapter 4
 LINK Error Messages

22 Syntax error on command line.

Although LINK recognized the command, the parameters on command line do not
make sense.
Probably result of bug in Host control software.
Could be result of bug in IPM.
Could be result of corrupted IPM.
Could be result of bug in LINK OS EPROM.
23 Cable not connected.
Probably result of cable not plugged into LINK port.
Could be result of improperly wired RS-232 cable.
24 STOP command was given.
The STOP command does not apply to instrument control and thus should never be
issued to an IPM.
Probably result of bug in Host control software.
25 Binary data not allowed here.
Probably result of bug in Host control software.
26 Not allowed in an INVOKE file.
Probably result of bug in IPM.
Could be result of corrupted IPM.
Could be result of bug in LINK OS EPROM.
27 BIN library is not compatible.
Probably result of using an out of date LINK EPROM or an out of date IPM.
Could be result of corrupted IPM.
28 BIN library is corrupted or not available.
Probably result of corrupted IPM.
29 Command line parameter is out of range.
Probably result of bug in Host software.
Could be result of bug in IPM or LINK EPROM.
30 BIN module not found in any of the libraries.
LINK could not find the IPM given in the INSTALL command.
Probably result of bug in Host software.
31 Device expected here, not file.
An operation was attempted on a file that is only allowed for a device, such as setting
Baud rate with the MODE command.

Technical Data 25
LINK Error Messages

32 Illegal character found in string.

Probably result of bug in IPM or LINK EPROM.
33 BIN is in use.
This error results if the Host computer tries to erase (BINERASE) or download to
(BINCOPY) an IPM while it is in use (still INSTALLED).
Probably result of bug in Host software.
34 Circular input buffer overflowed.
Probably result of data arriving at port before the IPM was installed.
Could be result of bug in IPM.
35 Instrument does not respond.
Probably result of instrument being turned off.
Could be result of disconnected RS-232 cable.
36 Command is out of sequence.
This error results when certain commands are given before prerequisite commands are
given.
Probably result of bug in Host software.
37 Interrupt not serviced fast enough.
Too much data arrived at instrument port for the CPU to handle.
Probably result of bug in LINK EPROM or bug in IPM.
38 Handle does not exist.
Probably result of bug in Host software.
40 GPIB is not bus controller.
A non-PerkinElmer program has attempted to communicate to the GPIB address of
this LINK.
50 Command not recognized.
Probably result of bug in Host software.
Could be result of corrupted IPM.
51 Record is too long for buffer.
Probably fault of GPIB or RS-232 communications.
52 Ran out of Handles.
This is probably the result of a task that asks for handles from the LINK Operating
System, but neglects to give them back when done with them.
Probably result of bug in IPM.

26 Chapter 4
 LINK Error Messages

53 Ran out of Chores.

This is probably the result of a task that asks for chores from the LINK Operating
System, but neglects to give them back when done with them.
Probably result of bug in IPM.
54 Extra Acknowledgement was received.
Results when LINK receives a packet protocol acknowledgement it was not expecting.
Probably result of bug in Host software.
60 Communications error.
Probably result of incorrect Baud rate.
Could be result of noise on RS-232 line.
61 Instrument reports an error.
Probably result of a problem at the instrument.
Could be result of an improper configuration.
The instrument that LINK is controlling has reported an error.
The error message is instrument specific. Refer to the IPM Installation Manual for
further details.
62 IPM was already installed.
An INSTALL command was issued when an IPM had already been installed at that
port.
Probably result of bug in Host software.
63 Parameter cannot be changed in this mode.
This error typically occurs when the host system attempts to send a non-setpoint
parameter while the chromatograph is in the midst of a run.
64 This is a read only parameter.
This error typically occurs when the host system attempts to change a parameter that
cannot be edited.
65 LINK has not taken control of the instrument yet.
Many instrument commands require that the instrument be seized.
This error results if SEIZE command was not issued first.
Probably result of bug in Host software.
Could be result of someone releasing control of instrument with LINK-TALK and
then restarting the Host software.
66 Autosampler not installed.
Probably result of improper configuration.

Technical Data 27
Warranty/Service

67 Data segment has not been released with OC command.

Probably result of bug in Host software.
99 The subroutine that was called is not finished yet.
Probably result of bug in IPM.
255 Fatal system error.
This error will result on recovery from a Fatal System Error.
A Fatal System Error is signified by LEDs at all four channels appearing to bounce up
and down. Set DIP switch 8 ON and then OFF again to have LINK recover (reset
itself). Afterwards, an error 255 will be obtained. Please write down the register
values reported with this error so factory engineers can trace the cause of the
malfunction.

Warranty/Service
If repair is required please contact your local PerkinElmer service office.

Specifications
Power: 100/120 VAC ± 10%, 50/60 Hz, 400mA max. current
220/230/240 VAC ± 10%, 50/60 Hz, 200mA max. current
Fuse: 500 mA for 100/120 VAC
3AG (quantity 2), Normal Blow (US, Canada, and Japan)
250 mA for 220/240 VAC
Type F DIN (quantity 2) Quick Acting (elsewhere)
Temperature: +10° to +45° C (operating)
-20° to +60° C (non-operating)
Altitude: 0 to 2000 meters (operating)
0 to 12,000 meters (non-operating)
Relative
Humidity: 20% to 80% (non-condensing)

28 Chapter 4
 Index

Auxiliary Ports, 12 Host/Serial port connections, 12

Back Panel Connections, 6 Host/Serial RS-232 configuration, 11
Battery, 17 Installation, cables, 3
Canadian Radio Interference Regulations, 4 Instrument Port Pinouts, 6
Channel LEDs, 15 Instrument Ports, 6
Class A limits, 4 LED power-on sequence, 14
Configuration switch functions, 9 LEDs, 15
Configuration Switches, default, 8 Active, 15
CPU, 17 Channel, 15
Diagnostics, 18 Error, 15
EMC Directive (European Union), 4 Ready, 15
Error System Ready, 15
All Channel ERROR LEDs ON within a few Memory
seconds of power-up, 21 DRAM, 17
All LEDs blinking rapidly, 21 EPROM, 17
All LEDs remain ON, 21 NVSRAM, 17
IEEE-488 (GPIB) communications, 19 RAM, 17
LEDs continue to blink after self-test, 21 SRAM, 17
LINK Error Messages, 22 Memory, 17
No front panel LEDs ON, 20 Operation, 13
Power LED ON but self-test not executed, 21 Power Connections and Fusing, 5
RS-232 Serial Communications, 20 Power On LED Sequence, 13
Error Messages, 22 READY LED, 15
Failure to Communicate With Host Computer, 19 RS-232 Ports, 6
FCC Notice, 4 Safety and Site Data, 4
Firmware, LINK Operating System, 18 Self-test function
Firmware:, 17 extended, 18
Front panel LEDs, 14 memory address, 18
Functional Description, 17 routine, 18
Fuse, 28 Service, 28
Fuse holder, 5 Specifications, 28
Fusing, 5 Status LEDs, 15
GPIB address selection, 10 SYSTEM READY LED, 15
Host Communications, 10 Troubleshooting Guide, 19
Host GPIB Port, 10 Warranty/Service, 28
Host RS-232 Port, 11

i
ii