[go: up one dir, main page]

0% found this document useful (0 votes)
64 views20 pages

Pages From 914731 - R6

This document provides troubleshooting steps for communication problems between a 3800 GC and a Star Workstation. It lists symptoms, potential causes, and recommended actions to resolve issues like the GC's Ethernet address not appearing in the BOOTP table or the GC not appearing in the list of available instruments. Causes could include the GC not being powered on, incorrect network configuration, or cabling/wiring problems. Suggested actions range from checking cabling and IP addresses to allowing more time for the GC to initialize.

Uploaded by

sabo6181
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
64 views20 pages

Pages From 914731 - R6

This document provides troubleshooting steps for communication problems between a 3800 GC and a Star Workstation. It lists symptoms, potential causes, and recommended actions to resolve issues like the GC's Ethernet address not appearing in the BOOTP table or the GC not appearing in the list of available instruments. Causes could include the GC not being powered on, incorrect network configuration, or cabling/wiring problems. Suggested actions range from checking cabling and IP addresses to allowing more time for the GC to initialize.

Uploaded by

sabo6181
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

Diagnostics/Troubleshooting

Communication Problems
When encountering communication problems between the 3800 GC and
your Star Workstation, refer to the following list of symptoms, causes and
recommended actions.
Symptom: When IP addresses are managed from the BOOTP Server table,
the 3800 GC Ethernet address does not show up in the BOOTP table.
Cause Action
The 3800 GC is not Power on all 3800 GCs that you expect to see in
powered on. the BOOTP Server table.
Did not wait long enough It may take up to one minute for the Ethernet entry
for 3800 GCs to broadcast to appear in the BOOTP Server table for any
their Ethernet addresses. given 3800 GC. Either wait for one minute, or
power off and on the GCs.
Cable and wiring a) Check to see if the 3800 GC and PC cabling
problems. network has been terminated at both ends with
50 ohm resistors.
b) Check to see if both network card and 3800 GC
COM boards are connected to the cable with a
tee. (See the 3800 GC communication kit
instructions for proper wiring configurations).
c) Check the cable resistance with tees and
terminators attached (but with no connections
to the PC or 3800). Resistance should be ~25
ohms when the resistance is measured from
the center pin of the cable to the outer
connector.
d) Check to make sure the cable is a minimum of
5 feet long.
f

Data Acquisition with 3800 GC Control 163


Symptom: When IP addresses are managed from the BOOTP Server table,
the 3800 GC Ethernet address does not show up in the BOOTP table.
Cause Action
The PC TCP/IP protocol a) Verify that TCP/IP protocol has been added
has not been configured and properly configured. Run WINIPCFG.EXE
correctly. (shipped with Windows 95 in the windows/
system directory) to see if the TCP/IP protocol
is functioning properly. The Ethernet Adapter
Name, Adapter Address, IP Address, Subnet
Mask, Default Gateway, and Host Name should
all be shown by WINIPCFG with correct values
for the intended type of network installation.
b) Using the IP Address shown in WINIPCFG, run
PING (shipped with Windows 95 in the
windows\system directory) in an MS-DOS
window to test the ability of the Ethernet
Adapter to echo a packet (PING <IP
address>). If PING succeeds, the problem is
most likely in the cabling and/or the 3800.
Otherwise verify that the TCP/IP protocol has
been setup correctly for the type of network
connection.
PC TCP/IP DNS and Disable DNS and WINS in the TCP/IP protocol if a
WINS enabled for a private network configuration is being used.
private network Private IP addresses start with a 10.
configuration.
PC Ethernet adapter Most network cards support multiple network
configured incorrectly for cable types. Make sure that the network card has
wrong cable type or been configured for the BNC wire type. Consult
adapter is not working. the documentation that comes with your network
adapter. If you suspect the network card is not
working run the diagnostic programs that ship with
your network card.
Network card has an Check for Resource Conflicts using the Device
interrupt conflict with Manager in System from the Control Panel. Run
another device installed on WINIPCFG and PING to verify that everything is
the PC. set up properly and works.
COM board absence or If the Ethernet address still does not appear in the
failure. BOOTP table after checking the items listed
above, the 3800 communication board (03-
925804-01) or other GC components may need to
be replaced. Contact Varian Service.

164 03-914731-00:6
DIAGNOSTICS/TROUBLESHOOTING
Communication Problems

Symptom: The 3800 GC Ethernet address shows up in the BOOTP table but
the 3800 does not show up in the list of available 3800s.
Cause Action
The host name for the GC In the BOOTP table you must enter a Host Name
was not entered in the for the 3800 on the line which contains the
BOOTP table. Ethernet address and IP address. <Unnamed> is
not a valid host name.
The 3800 GC was started When the 3800 GC is powered on and a
in local mode. communication board is installed, the GC will wait
for a network connection before starting. You are
prompted to press any key to start in local mode,
at which point the GC will no longer attempt to
connect to a Workstation. Turn the power to the
3800 GC off and on again. Allow the Workstation
to connect to the GC (do not press any key on the
GC front panel).
Operator not giving 3800 It takes several minutes for the GC to initialize.
GC enough time to boot. Wait at least 5 minutes before attempting to
continue troubleshooting.
The startup.ins file in the Close System Control, delete the startup.ins file in
Star directory is corrupt. the directory where Star is installed, and restart
System Control. You will need to reconfigure
your instrument settings in the Configuration
window.
The network configuration Reinstall the network adapter and associated
has been corrupted. software by doing the following.
a) Go to the network icon in Control Panel.
Highlight the network adapter currently being
used for 3800 control. Select remove.
b) Exit from the Control Panel without restarting
windows.
c) Shut down the PC and remove the adapter
card.
d) Restart Windows and then Shut down the
computer. Reinstall the network card and
reload the adapter software and protocols.

Data Acquisition with 3800 GC Control 165


Symptom: After switching from an isolated network configuration to a company
network configuration, the GC fails to communicate.
Cause Action
The IP address on the PC Make sure that the IP addresses of all
is inappropriate for the Workstations and 3800s connected to the network
type of network have IP addresses provided by the Network
connection. Administrator.
The network repeater box Change the terminator switch position to ON if the
(if used) connecting the network cable is attached directly to the repeater
3800 to the network does box without a Tee or Tee and terminator.
not have the terminator
switch in the correct
position.

Symptom: After switching from a company network configuration to an isolated


network configuration, the GC fails to communicate.
Cause Action
The network configuration In the Network Settings accessed from the
on the PC is not Windows 95 Control Panel, verify that no gateway
compatible with an is specified, that DNS and WINS are disabled and
isolated network. that the subnet mask is 255.0.0.0. Also make
sure that the IP address is in the range
10.2.128.1 to 10.255.255.254.

Symptom: The 3800 GC intermittently loses communication and logs error


message “Module 3800 disconnecting…” in the Message Log.
Cause Action
PC power management Check to make sure that the power management
enabled. has been disabled on the PC.
Network latency is causing If running on a company network, make sure that
communication timeouts. network packets are not delayed by more than 20
seconds.

166 03-914731-00:6
DIAGNOSTICS/TROUBLESHOOTING
Communication Problems

Symptom: The Workstation warns that duplicate TCP/IP entries exist in the
registry and the 3800 does not communicate with the Workstation.
Cause Action
An error exists in the Run REGEDIT.EXE and look under
Windows registry. HKEY_LOCAL_MACHINE\System\CurrentControlSet\
Services\Class\NetTrans. There should be a list
of one or more numerical entries. Click on each
entry and check the DriverDesc to see if it is
TCP/IP. There should only be one for each
Ethernet Card. Most Workstations should have
only one. If there are more, delete the
unnecessary ones.

Symptom: The 3800 is assigned an IP address but this IP address is not in the
BOOTP table.
Cause Action
There are multiple To avoid confusion, only have one PC designated
BOOTP servers on the as the BOOTP server.
network.

Symptom: The BOOTP table has an entry of 0.0.0.0 for the 3800.
Cause Action
The Workstation is waiting Manually enter an IP address for the GC into the
for the operator to enter BOOTP table.
an IP address for the GC.

Symptom: 3800 GCs on a company network simultaneously disconnect from


Workstations.
Cause Action

The network is being Contact the Network Administrator and locate and
flooded with broadcast remove the source of the broadcast packets.
packets. This may be due
to an improperly
configured isolated
network IP address
(starting with 10) running
on a company network.

Data Acquisition with 3800 GC Control 167


Setup Ethernet Ports Message Boxes
The following errors may appear in messages boxes generated by the
Setup Ethernet window. The messages are listed in alphabetical order.

Message Box Text Cause


Clients with IP Addresses but no The BOOTP Server will not reply to
Host Names will not connect to unnamed clients. Name each client in
the Star Workstation! Do you the BOOTP Server spreadsheet that you
want to name the unnamed wish to boot from your BOOTP Server.
Clients before closing this Dialog
Box?
DNS should be disabled and its The Star Workstation is configured with
Servers deleted for Private Class DNS enabled even though it is running
A Operation! Private Class A. Disable DNS.
Each Ethernet Address must be Each Ethernet hardware address entry in
unique! the BOOTP Server spreadsheet must be
unique; no duplicate entries are allowed.
Otherwise there would be multiple IP
address and Host Name assignments for
a single client.
Each Host Name must be Each Host Name entry in the BOOTP
unique! Server spreadsheet must be unique; no
duplicate entries are allowed. Otherwise
clients might have the same Host Name
and be mistaken for one another.
Each IP Address must be unique! Each IP address entry in the BOOTP
Server spreadsheet must be unique; no
duplicate entries are allowed. Otherwise
clients might attempt to use the same IP
address.
Ethernet Driver Cannot Allocate There is not enough memory to load the
BOOTP Records! BOOTP database from STARTUP.INS.
Gateway nnn.nnn.nnn.nnn should The Star Workstation is configured with a
be 0.0.0.0 for Private Class A non-zero Gateway (Router) address
Operation! even though it is running Private Class
A. Change the Gateway to 0.0.0.0.
Module 'nn', Name 'zzzz', and There are duplicate Host Names and/or
Module 'mm', Name 'yyyy', IP addresses in the 'Setup Ethernet
cannot have the same Domain Ports' Dialog Box. Eliminate all
Name or IP Address! duplicates before closing the Dialog Box.

168 03-914731-00:6
DIAGNOSTICS/TROUBLESHOOTING
Setup Ethernet Ports Message Boxes

Message Box Text Cause


Module 'nn''s name is 'zzzz', but The Setup Ethernet Ports Dialog Box
its domain name is specified as has detected a mismatch between the
'yyyy'! Either rename the Module Host Name you specified for the IP
to 'yyyy', or update your HOSTS address, and the name that it got from
File or DNS Server with the name the HOSTS file or DNS/WINS server for
'zzzz' for the IP Address that IP address. Either enter the correct
nnn.nnn.nnn.nnn. Host Name, or update the
HOSTS/DNS/WINS database to contain
the correct Host Name.
Not Enough Memory to Setup There is not enough memory to run the
BOOTP Server! BOOTP Server.
Please enter a Host Name! Enter an alphanumeric host name
containing no dot or space characters.
Please enter a Valid Ethernet Enter the hardware address of an
Address; format Ethernet Adapter in dotted hexadecimal
00.00.00.00.00.00! format.
Please enter a Valid IP Address; Enter an IP address in dotted decimal
format 000.000.000.000! format.
Private Class A IP Address is The Star Workstation has a Private
nnn.nnn.nnn.nnn; Must exceed Class A IP address that is in the range
10.2.128.0 reserved for use by Varian Analytical
Instruments. Change the IP address to
one that is at least 10.2.128.1.
Sorry, TCP/IP allows no spaces TCP/IP specifications reserve spaces
or dots in Host Names! Use '_' and dots for use as delimiters of fields,
instead. so they cannot be used in host names.
Subnet Mask nnn.nnn.nnn.nnn The Star Workstation is configured with a
should be 255.0.0.0 for Private Subnet Mask that is incorrect for use in
Class A Operation! Private Class A mode. Change the
Subnet Mask to 255.0.0.0.
There are Multiple TCP/IP The Windows Registry contains multiple
Drivers in the Registry! entries for TCP/IP under
HKEY_LOCAL_MACHINE/System/Curre
ntControlSet/Services/Class/NetTrans.
System Control will use the first one in
the list.
This Workstation has no IP The Star Workstation has no valid IP
Address assigned! address. Configure a valid IP address
using the Network TCP/IP tab in the
Control Panel Applet.

Data Acquisition with 3800 GC Control 169


Message Box Text Cause
Unable to locate IP Address for The Star Workstation was unable to find
Module 'nn', Name 'zzzzz'! an IP address corresponding to the
Module's specified Host Name. Update
your HOSTS file in your WINDOWS
directory, or ask your administrator to
update your DNS/WINS server with the
Host Name and IP Address.
Unable to start WINSOCK; Error WINSOCK.DLL failed with the indicated
'n'! error when System Control attempted to
initialize it.
WINS Resolution should be The Star Workstation is configured with
disabled for Private Class A WINS enabled even though it is running
Operation! Private Class A. Disable WINS.
Your new password was not re- When changing the BOOTP Server
entered correctly! Please try password, you must enter the new
again! password twice before the new password
is accepted.
'zzzz' resolves to The Setup Ethernet Ports Dialog Box
ooo.ooo.ooo.ooo instead of has detected a mismatch between the IP
nnn.nnn.nnn.nnn! Update your address you specified for the Host
HOSTS File or DNS Server to Name, and the IP address that it got
resolve 'zzzz' to the IP Address from the HOSTS file or DNS/WINS
nnn.nnn.nnn.nnn! (Remember to server for that Host Name. Either enter
restart Windows after updating the correct IP Address, or update the
the HOSTS File!) HOSTS/DNS/WINS database to contain
the correct IP address.

170 03-914731-00:6
DIAGNOSTICS/TROUBLESHOOTING
System Control Messages

System Control Messages


The following messages may appear in the Message Log in
System Control. Several categories of these messages are
listed.

The most recent entry in


the Message Log is
visible at the bottom of
the Instrument window
in system Control.
Double-click on this line
to view the entire log.

BOOTP Server Messages

The following messages appear in the Configuration Log (the log


accessed from the bottom of the Configuration screen in System
Control). The messages describe problems with and status of operation
of the BOOTP Server on the Workstation. The messages are listed in
alphabetical order.
Message Cause
BOOTP Adding Client to Table The BOOTP Server is adding the client's
Line 'n'! Ethernet Address to a new row number
'n' in the spreadsheet.
BOOTP Client already has IP: The BOOTP Client that sent the BOOTP
nnn.nnn.nnn.nnn! Request Broadcast is indicating that it
already has an IP address.

Data Acquisition with 3800 GC Control 171


Message Cause
BOOTP Client has No IP The BOOTP Server has determined that
Address in Table! the Ethernet address entered in the
spreadsheet for the client does not have
an entry for the IP address in the
spreadsheet. It will not send a BOOTP
Reply Broadcast to the client until the
operator enters an IP address and a
Host Name for the client.
BOOTP Client IP The BOOTP Server has determined that
nnn.nnn.nnn.nnn already in use! the IP address entered in the
spreadsheet for the client is already in
use by another 3800 GC. There is
probably another BOOTP Server
assigning that IP address to that 3800.
BOOTP Client nnn.nnn.nnn.nnn: The BOOTP Server has determined that
No Host Name! the IP address entered in the
spreadsheet for the client does not have
an entry for the Host Name in the
spreadsheet. It will not send a BOOTP
Reply Broadcast to the client until the
operator enters a Host Name for the
client.
BOOTP Client not found in Table! The BOOTP Server just received a
BOOTP Request Broadcast from a client
that has no entry of its Ethernet Address
in the spreadsheet.
BOOTP got Request from Client The BOOTP Server just received a
xx.xx.xx.xx.xx.xx! BOOTP Request Broadcast from the
client with the specified Ethernet
Address.
BOOTP ignoring non-Varian The BOOTP Server just received a
Client! BOOTP Request Broadcast from the
client that has an Ethernet Address
outside of the range allocated to Varian
Analytical Instruments.
BOOTP Request has bad The BOOTP Server just received a
Header! BOOTP Request Broadcast from the
client that contains incorrect BOOTP
Header information.

172 03-914731-00:6
DIAGNOSTICS/TROUBLESHOOTING
System Control Messages

Message Cause
BOOTP Sending IP The BOOTP Server is broadcasting a
nnn.nnn.nnn.nnn, Name BOOTP Reply packet to the client
'xxxxxxxxxxx' to Client! containing the specified IP address and
Host Name.
BOOTP Server Bad Request The BOOTP Server just received a
Size 'n'! BOOTP Request Broadcast from the
client that does not have the correct
BOOTP Request packet size.
BOOTP Server Cannot Transmit The BOOTP Server's attempt to
Reply! broadcast a BOOTP Reply packet to the
client failed due to a socket error.
BOOTP Server Disabled; The BOOTP Server has been turned off
Ignoring Request! and is ignoring the BOOTP Request
Broadcast that it just received.
BOOTP Server has been The BOOTP Server has been turned off
Disabled! by unchecking the checkbox in the
BOOTP Server Dialog Box.
BOOTP Server has been The BOOTP Server has been turned on
Enabled! by checking the checkbox in the BOOTP
Server Dialog Box.
BOOTP Server is Waiting for a The BOOTP Server is waiting to receive
Request! a BOOTP Request Broadcast from a
client needing an IP address and Host
Name.
BOOTP Server Socket Error 'n'! The BOOTP Server detected the
indicated WINSOCK socket error while
waiting for a BOOTP Request Broadcast.
BOOTP Server Timed Out! The BOOTP Server timed out while
waiting for a BOOTP Request Broadcast.
BOOTP Table Full; Cannot Add The BOOTP Server cannot add the
Client! client's Ethernet Address to a new row in
the spreadsheet because the
spreadsheet already contains its limit of
100 rows. Delete some unused rows to
make more room.
Microsoft Windows Sockets This is the Vendor Version Identification
Version 1.1 for WINSOCK.DLL. Any version other
than Microsoft Version 1.1 is unqualified
and may not be reliable with the Star
Workstation.

Data Acquisition with 3800 GC Control 173


Module Communication Messages

The following messages describe problems encountered while


communicating with the 3800 GC. The messages are listed in
alphabetical order.

Message Cause
3800 Has Disconnected from A 3800 Module has completed its
System Control! disconnection process and is no longer
communicating with the Star
Workstation.
3800 Has Reconnected to A 3800 Module has completed its
System Control! reconnection process and is now
communicating with the Star
Workstation.
3800 Sent BEGINMON Packet The 3800 sent a BEGINMON raw data
Out of Sequence packet in the wrong sequence of
packets.
3800 Sent BEGINRUN Packet The 3800 sent a BEGINRUN raw data
Out of Sequence packet in the wrong sequence of
packets.
3800 Sent ENDMON Packet Out The 3800 sent an ENDMON raw data
of Sequence packet in the wrong sequence of
packets.
3800 Sent ENDRUN Packet Out The 3800 sent an ENDRUN raw data
of Sequence packet in the wrong sequence of
packets.
3800 Sent INMON Packet Out of The 3800 sent an INMON raw data
Sequence packet in the wrong sequence of
packets.
3800 Sent INRUN Packet Out of The 3800 sent an INRUN raw data
Sequence packet in the wrong sequence of
packets.
3800 Sent Invalid Data Count 'n'; The 3800 sent an invalid data count in a
Ignoring Run! raw data packet.
3800 Sent RUNHEADER Packet The 3800 sent a RUNHEADER raw data
Out of Sequence packet in the wrong sequence of
packets.
3800 Sent RUNTRAILER Packet The 3800 sent a RUNTRAILER raw data
Out of Sequence packet in the wrong sequence of
packets.

174 03-914731-00:6
DIAGNOSTICS/TROUBLESHOOTING
System Control Messages

Message Cause
3800 Sent SHORTMONITOR The 3800 sent a SHORTMONITOR raw
Packet Out of Sequence data packet in the wrong sequence of
packets.
3800 Sent SHORTRUN Packet The 3800 sent a SHORTRUN raw data
Out of Sequence packet in the wrong sequence of
packets.
Cannot Download; Method does The specified method cannot be
not match Setup! downloaded to the 3800 GC because the
method contents do not exactly match
the hardware setup in the 3800 GC.
Module 3800.'nn': Method A 3800 module is inhibiting Method
Download Inhibited while 3800 Download because it cannot receive a
Running! method while it is in a run.
Module 'nn' Completing Delayed A delayed disconnect is now being
Disconnect! completed.
Module 'nn' Delaying Disconnect; An attempt to disconnect the module was
Connect in Progress! initiated while the module was in the
process of connecting. The disconnect
will not be started until the connection
process either completes or fails.
Module 'nn' Disconnected by A module is disconnecting because the
Address Change! operator changed its IP Address in the
'Setup Ethernet Ports' Dialog Box.
Module 'nn' Disconnected by A module is disconnecting because the
Operator! operator removed it from the 'Setup
Ethernet Ports' Dialog Box.
Module 'nn' Disconnecting; A module's control connection is
Command Failed! disconnecting because it detected a
socket error while sending a command.
Module 'nn' Disconnecting; A module's control connection is
Command Keepalive Failed! disconnecting because it detected a
socket error while sending a KEEPALIVE
packet.
Module 'nn' Disconnecting; A module's control connection is
Control Timed Out! disconnecting because no activity was
detected for the specified period of time.
Module 'nn' Disconnecting; A module's file transfer connection is
Download Failed! disconnecting because a download
operation failed due to a socket error.

Data Acquisition with 3800 GC Control 175


Message Cause
Module 'nn' Disconnecting; Raw A module's raw data connection is
Data Failed! disconnecting because it detected a
socket error.
Module 'nn' Disconnecting; A module's status connection is
Status Failed! disconnecting because it detected a
socket error.
Module 'nn' Disconnecting; A module's status connection is
Status Timed Out! disconnecting because no activity was
detected for the specified period of time.
Module 'nn' Disconnecting; A module's file transfer connection is
Transfer Keepalive Failed! disconnecting because it detected a
socket error while sending a KEEPALIVE
packet.
Module 'nn' Disconnecting; A module's file transfer connection is
Transfer Timed Out! disconnecting because no activity was
detected for the specified period of time.
Module 'nn' Disconnecting; A module's file transfer connection is
Upload Failed! disconnecting because an upload
operation failed due to a socket error.

176 03-914731-00:6
DIAGNOSTICS/TROUBLESHOOTING
System Control Messages

Constant Flow Mode Messages

The following messages describe errors generated when performing


constant flow mode with the 1079 Injector and Type 1 EFC. The
messages are listed in alphabetical order.

Message Cause
EFC Constant Flow: above max Constant Flow Mode has generated a
pressure rate! pressure ramp that requires a rate above
the maximum rate that the EFC is
capable of sustaining.
EFC Constant Flow: above max Constant Flow Mode has generated a
pressure! pressure ramp that requires a pressure
above the maximum pressure that the
EFC is capable of sustaining.
EFC Constant Flow: below min Constant Flow Mode has generated a
pressure rate! pressure ramp that requires a rate below
the minimum rate that the EFC is
capable of sustaining.
EFC Constant Flow: below min Constant Flow Mode has generated a
pressure! pressure ramp that requires a pressure
below the minimum pressure that the
EFC is capable of sustaining.
EFC Constant Flow: no carrier Constant Flow Mode cannot generate a
gas in setup! pressure ramp because the carrier gas is
set to 'none'.
EFC Constant Flow: zero column Constant Flow Mode cannot generate a
diameter in setup! pressure ramp because the column
diameter is set to zero.
EFC Constant Flow: zero column Constant Flow Mode cannot generate a
length in setup! pressure ramp because the column
length is set to zero.

Data Acquisition with 3800 GC Control 177


Hardware Setup Error Messages

The following messages describe errors generated when obtaining the


hardware setup from the 3800 GC. The messages are listed in
alphabetical order.

Message Cause
Setup: Bad Carrier Gas: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Carrier
Gas identifier.
Setup: Bad Column Diameter: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Column
Diameter.
Setup: Bad Column ID: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Column
identifier.
Setup: Bad Column Length: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Column
Length.
Setup: Bad Column Oven ID: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Column
Oven identifier.
Setup: Bad Column Oven Zone: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Column
Oven Temperature Zone identifier.
Setup: Bad Column SIS ID: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Column
sample introduction system identifier.
Setup: Bad Column Zone: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Column
Temperature Zone identifier.
Setup: Bad Coolant: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Coolant
identifier.
Setup: Bad Detector Column ID: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Detector
Column Tap identifier.
Setup: Bad Detector ID: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Detector
identifier.

178 03-914731-00:6
DIAGNOSTICS/TROUBLESHOOTING
System Control Messages

Message Cause
Setup: Bad Detector Zone: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Detector
Temperature Zone identifier.
Setup: Bad EFC ID: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Injector
EFC identifier.
Setup: Bad EFC PDU: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Injector
EFC pressure display unit setting.
Setup: Bad EFC SIS ID: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Injector
EFC sample introduction system
identifier.
Setup: Bad Injector ID: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Injector
identifier.
Setup: Bad Injector SIS ID: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Injector
sample introduction system identifier.
Setup: Bad Injector Zone: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Injector
Temperature Zone identifier.
Setup: Bad Methanizer Detector ID: The 3800 GC sent a Hardware Setup
'n' update containing an incorrect
Methanizer Detector identifier.
Setup: Bad Methanizer ID: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect
Methanizer identifier.
Setup: Bad Methanizer Zone: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect
Methanizer Temperature Zone identifier.
Setup: Bad Minimum Flow: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Injector
EFC minimum flow rate.
Setup: Bad Model Number: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect 3800 GC
model number.
Setup: Bad Outlet Pressure: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Injector
EFC outlet pressure setting.

Data Acquisition with 3800 GC Control 179


Message Cause
Setup: Bad Output Port ID: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Output
Port identifier.
Setup: Bad SW Version: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect software
version number.
Setup: Bad Temp Limit: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect
Temperature Limit.
Setup: Bad Valve Bank ID: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect valve
bank identifier.
Setup: Bad Valve ID: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect valve
identifier.
Setup: Bad Valve Oven ID: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Valve
Oven identifier.
Setup: Bad Valve Oven Zone: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect Valve
Oven Temperature Zone identifier.
Setup: Bad Valve SIS ID: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect valve
sample introduction system identifier.
Setup: Bad Valve Temp Zone: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect valve
temperature zone identifier.
Setup: Bad Zone ID: 'n' The 3800 GC sent a Hardware Setup
update containing an incorrect
Temperature Zone identifier.

180 03-914731-00:6
DIAGNOSTICS/TROUBLESHOOTING
System Control Messages

3800 GC Runlog Error Messages

The following messages describe errors obtained from the 3800 GC and
documented in the Runlog. The messages are listed in alphabetical
order.
Message Cause
Air Leak Fault The 3800 just detected that the
specified TCD has a disabling air leak.
Board Failure The 3800 just detected that the
specified PFPD has a failed electronics
board.
Coolant Timed Out The 3800 just detected that the
specified component's Temperature
Zone Coolant has timed out.
Data Loss due to Workstation The 3800 just detected that its raw
Disconnect data buffer has overflowed because it
was unable to transmit its contents to
the Star Workstation quickly enough.
Flame-out The 3800 just detected that the
specified FID has a flame-out.
Large Air Leak The 3800 just detected that the
specified TCD has a large air leak.
Lower than Minimum Temp The 3800 just detected that the
specified component's Temperature
Zone has gone below its minimum
temperature.
Max Setup Temperature Limit The 3800 just detected that the
Exceeded specified component's Temperature
Zone has exceeded its maximum
Setup temperature limit.
Maximum Temp has been The 3800 just detected that the
exceeded specified component's Temperature
Zone has exceeded its maximum
temperature.
No Response from Temp Probe The 3800 just detected that the
specified component's Temperature
Zone Probe is not responding.
Temp Probe is Open The 3800 just detected that the
specified component's Temperature
Zone Probe has an open circuit.

Data Acquisition with 3800 GC Control 181


Message Cause
Temp Probe is Shorted The 3800 just detected that the
specified component's Temperature
Zone Probe has a short circuit.
Temp Probe Response is Too Fast The 3800 just detected that the
specified component's Temperature
Zone Probe is responding too fast.
Temp Probe Response is Too The 3800 just detected that the
Slow specified component's Temperature
Zone Probe is responding too slowly.
Thermal Runaway The 3800 just detected that the
specified component's Temperature
Zone has begun thermal runaway.
Workstation Connected The 3800 just detected that the Star
Workstation has connected its
Ethernet communications.
Workstation Disconnected The 3800 just detected that the Star
Workstation has disconnected its
Ethernet communications.

Recovering a Lost Password for BOOTP Server Access


If you have enabled password protection for the BOOTP Server
dialog box in System Control, you can reset or recover the
password if it has been forgotten or inadvertently changed. To
do so, find the BootpPassword entry in the [System Control]
section of the file STAR.INI in your Windows directory. This entry
contains the password required to enter the BOOTP Server
dialog box. Deleting this line resets the password to blank (no
password).

182 03-914731-00:6

You might also like