Page 1
Maxum II
PD PA AP
Maxum edition II Analyzer General
Maintenance
General Analyzer Functions, Troubleshooting, and
Maintenance for Maxum II Gas Chromatographs. The
information in this manual supercedes the applicable
topics in previous manuals.
Introduction
1
Manual
Safety notes
System Functions
General Maintenance and
Troubleshooting
Appendix A - Contact
Information
2
3
4
A
August 2018
A5E42019842001
Page 2
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will be
used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property
damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified
personnel are those who, based on their training and experience, are capable of identifying risks and avoiding
potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described.
Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in
this publication is reviewed regularly and any necessary corrections are included in subsequent editions.
Siemens AG
Division Process Industries and Drives
Postfach 48 48
90026 NÜRNBERG
GERMANY
A5E42019842001
Ⓟ 08/2018 Subject to change
Copyright © Siemens AG 2018.
All rights reserved
Page 3
Table of contents
1 Introduction...................................................................................................................................................5
1.1 Analyzer Specific Documents..................................................................................................5
2 Safety notes..................................................................................................................................................7
2.1 Approved Use..........................................................................................................................7
2.2 Qualified Personnel..................................................................................................................8
3 System Functions.........................................................................................................................................9
3.1 Chromatography Overview......................................................................................................9
3.2 Functions................................................................................................................................10
3.3 Analyzer Operation................................................................................................................13
3.4 Data Communication..............................................................................................................17
4 General Maintenance and Troubleshooting...............................................................................................19
4.1 Analyzer Status Indicators.....................................................................................................19
4.1.1 Operator Controls...................................................................................................................19
4.1.2 LED States Inside the Electronics Cabinet............................................................................21
4.1.2.1 Base3DPM Status Indicator LEDs.........................................................................................21
4.1.2.2 SIB3 LEDs..............................................................................................................................22
4.1.2.3 PECM LEDs...........................................................................................................................25
4.1.2.4 Modular Oven Model PECM-DC LED Locations....................................................................26
4.2 Leak Testing...........................................................................................................................26
4.3 General Analyzer Shutdown Procedure.................................................................................27
4.4 General Analyzer Startup Procedure.....................................................................................27
4.4.1 Procedure...............................................................................................................................28
4.5 Accessing the Bootloader......................................................................................................30
4.6 Alarm Codes, Descriptions, and Suggested Actions..............................................................31
4.6.1 Alarms 301 - 324....................................................................................................................31
4.6.2 Alarms 330 through 359 SNE Communication......................................................................33
4.6.3 Alarms 360 - 399....................................................................................................................35
4.6.4 Alarms 400 - 562....................................................................................................................37
4.6.5 Alarms 671 - 699....................................................................................................................41
4.6.6 Alarms 700 - 737....................................................................................................................43
4.6.7 Alarms 801 - 999....................................................................................................................45
4.6.8 Alarms 1002 - 1128................................................................................................................47
4.6.9 Alarms 1317 - 1319................................................................................................................52
4.6.10 Alarms 1617 - 1697 Pecm Errors...........................................................................................53
4.6.11 Alarms 1917 - 2005 DPM TCD..............................................................................................55
4.6.12 Alarms 2217 - 2306 DPM FID................................................................................................58
4.6.13 Alarms 2500 - 2577 Access Bus Driver Errors.......................................................................62
4.6.14 Alarms 2817 - 2904 DPM Temperature.................................................................................67
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 3
Page 4
Table of contents
4.6.15 Alarms 3117 - 3204 EPC.......................................................................................................69
4.6.16 Alarms 3401 - 3454 TFTP......................................................................................................70
4.6.17 Alarms 3500 - 3528 Advance.................................................................................................71
4.6.18 Alarms 3718 - 3804 SNE I/O..................................................................................................72
4.6.19 Alarms 4001 - 4124 EZChrom...............................................................................................75
4.6.20 Alarms 4217 - 4320 CAN Bridge............................................................................................77
4.6.21 Alarms 4525 - 5220 Advance TC...........................................................................................79
4.6.22 Alarms 10000 - 11536 MicroSAM..........................................................................................81
A Appendix A - Contact Information...............................................................................................................83
Index...........................................................................................................................................................85
Figures
Figure 3-1 Example Applet...........................................................................................................................10
Figure 3-2 Operational Block Diagram (Maxum II Airless Airbath model shown).........................................14
Figure 3-3 Data Communication Paths.........................................................................................................17
Figure 3-4 Identification Number..................................................................................................................18
Figure 4-1 Base3DPM Status LEDs.............................................................................................................21
Figure 4-2 SIB3 LEDs and Switches............................................................................................................22
Maxum edition II Analyzer General Maintenance
4 Manual, August 2018, A5E42019842001
Page 5
Introduction
This manual provides maintenance information common to various Maxum Edition II Gas
Chromatograph models.
1.1 Analyzer Specific Documents
Included with each analyzer is a custom documentation-drawing package. This package
provides drawings and information pertinent only to a specific analyzer. Contents of this
package are application-dependent and vary for each analyzer. Typical drawings included are:
1
● System Block and Utility Requirements
● System Outline and Dimensional Drawings
● Sampling System - Plumbing and Spare
Parts List
● Sampling System Dimensional Diagram
● Sampling Probe
● Electronics Compartment - Internal Layout
● Applicable Wiring Diagrams
● Oven Plumbing Diagram - Sensor Near
Electronics
● Recommended Spare Parts - Analyzer
● Manufacturing Test Charts
● Stream Composition Data
● Database
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 5
Page 6
Introduction
1.1 Analyzer Specific Documents
Maxum edition II Analyzer General Maintenance
6 Manual, August 2018, A5E42019842001
Page 7
Safety notes
Maxum II Analyzers have varying levels of certification for operating in hazardous
environments. See the
(A5E02220442001), and the
information.
The Maxum edition II Process Gas Chromatograph, also called the Maxum II, employs several
design and construction features which conform to various international safety standards.
These standards are to ensure that the Maxum II and related products can be safely installed
and operated in hazardous areas. Each individual detail and component of these safety
systems is important to help ensure that the chromatograph does not ignite flammable vapors
and gases which may be present in the environment surrounding the analyzer. Therefore, it
is important that any personnel that come in contact with the analyzer be familiar with the
operation of the safety systems so that they do not compromise safe operation while performing
routine maintenance, operation, or other tasks.
Explosion risk
Do not install, operate, or service this equipment without reading and understanding all
documentation for the equipment and the Safety Data Sheets for all chemicals used in the
installation and operation. Failure to follow safe procedures with chemicals commonly used
in gas chromatography greatly increases the risk of severe injury or death, and destruction
of equipment.
DANGER
Maxum II Explosion Protection Safety Standards Manual
Maxum edition II Installation Manual
(2000595) for complete
2
2.1 Approved Use
The Maxum edition II gas chromatograph is primarily used in all branches of the fine chemicals,
refining, and hydrocarbon processing industries. It performs chemical composition analysis of
gases and liquids that are present in all phases of production. The application flexibility of the
Maxum II allows it to analyze a wide variety of samples including feedstock, partially processed
streams, final products, and process byproducts including wastes and environmental hazards.
The Maxum II product is intended to be used only in conjunction with other devices and
components which have been recommended and approved by Siemens. Appropriate safety
standards were used in the development, manufacture, testing, and documentation of the
Maxum II. Under normal operation, this product is safe for use providing that all safety and
handling guidelines are observed with respect to configuration, assembly, approved use, and
maintenance.
This device has been designed with safe isolation between high and low voltage circuits. Low
voltages which are connected must also be generated using safe isolation. If any part of the
Maxum II is opened, certain parts of the device are accessible which may carry dangerous
voltages. Therefore, only suitably qualified personnel may work on this device as indicated in
the next section which is titled "Qualified Personnel".
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 7
Page 8
Safety notes
2.2 Qualified Personnel
2.2 Qualified Personnel
Only suitably qualified personnel may operate or perform maintenance on the Maxum II. For
the purposes of safety, qualified personnel are defined as follows:
● Those who have been appropriately trained for the tasks which they are performing (for
example, commissioning, maintenance, or operation).
● Those who have been appropriately trained in the operation of the Maxum II process gas
chromatograph and are sufficiently acquainted with Maxum II documentation.
● Those who are familiar with the safety concepts of the Maxum II process gas
chromatograph and are sufficiently acquainted with Maxum II documentation.
● Those who are authorized to energize, ground, and tag circuits and devices in accordance
with established safety practices may perform those tasks for which they are trained.
WARNING
Avoid injury and property damage
Operation or Maintenance of the Maxum II by unqualified personnel or failure to observe the
warnings in this manual or on the device may lead to severe personal injury and/or extensive
property damage.
WARNING
Do not connect analyzer to the internet.
This equipment must not be connected to the internet except by a secure connection using
a network security appliance administered by qualified IT personnel.
Failure to implement robust network security may expose your company to internet hacking
attacks that could result in theft or loss of sensitive data, equipment damage, serious injury
or death.
For more information see the Maxum II Explosion Protection Safety Standards Manual
(A5E02220442001) at Maxum II Explosion Protection Safety Standards Manual (https://
support.industry.siemens.com/cs/document/42017542/maxum-edition-ii%3A-explosionprotection-safety-standards?dti=0&pnid=17741).
Maxum edition II Analyzer General Maintenance
8 Manual, August 2018, A5E42019842001
Page 9
System Functions
3.1 Chromatography Overview
Gas Chromatograph Terminology
The following are some of the terms that are used in this manual.
Application: The supporting hardware and software required to perform the analysis.
Supporting hardware consists of hardware channels: detector channel, Solenoid Valve Control
Module channel, Electronic Pressure Control channel, Temperature Controller. Streams are
defined to applications. If there are 3 or 4 simultaneous streams, they are defined as a single
group called a Method. Applications can run only one Method at a time. Two applications can
run if there are two cycle clocks in the Maxum II.
Method is the part of the application that contains the parameters for controlling the hardware.
Methods control the hardware associated with an Application. The method controls the
hardware, including all cycle-clock timed events. Methods are defined to streams. That is,
several stream sequences can make up one Method. Methods also control the integration and
calculations of the chromatogram. There is one cycle clock per method.
Applet refers to pre-engineered chromatographic segments of common applications, which
have been optimized and standardized.
3
Applet Module refers to a complete assembly including Model 50 valve(s), detector and
interconnecting tubing all mounted as a single module. The module includes columns and
restrictors
Parallel Chromatography
With the Maxum II hardware and software, a complex single-train chromatograph analysis can
be broken it into multiple simple trains. Each simple train then runs simultaneously – in parallel.
This parallel chromatography procedure simplifyies the overall analysis and increases
reliability.
Redundant Measurements
Using parallel chromatography can reduce calibration requirements by running two identical
modules in parallel on the same stream to obtain redundant measurements. As long as the
results remain the same within a predefined error limit, the analysis is known to be accurate.
Deviations outside the error limit can trigger notification or activate analyzer calibration.
Overall, the Maxum II calibration requirements are significantly lower because of the parallel
measurement configurations and standard modular applications.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 9
Page 10
System Functions
3.2 Functions
Figure 3-1 Example Applet
3.2 Functions
Overview
Startup Tasks
This section provides an operational overview of the real-time functional tasks of the Maxum
II.
● Startup Tasks
– Applying Power
– Valid Database
– Oven Temperature
– Cycle Control Flag
● Timed Event Scheduling
– Time-Of-Day Clock
– Schedule of Events • Frequency Events
On start-up, when primary AC power is applied to the analyzer, the analyzer first processes
whatever electronic self-tests and diagnostics are required such as PROM, RAM, A/D, and
communication ports. This processing occurs within 5 seconds.
System-related initial messages are generated and output to the network ports. Appropriate
initial messages are then displayed on the Maintenance Panel and completed within 20 to 25
seconds. If the analyzer cycle clock is in RUN or CAL mode, an appropriate alarm may be
generated during this internal test and the following startup period.
● Analysis Cycle Clock
– Accessing System Controller
– Analysis Cycle Clock
– SYSCON Cycle Clock
– Valve Events
● Manual Operations via User Interface
Maxum edition II Analyzer General Maintenance
10 Manual, August 2018, A5E42019842001
Page 11
Self Test
Oven Temperature
System Functions
3.2 Functions
After the self-test, the following conditions occur:
● Installed hardware is initialized.
● Interrupts are enabled.
● Oven temperatures and carrier pressure default set points are output.
● Analog input system(s), associated with detector inputs, are initialized and begin scanning.
The System Controller (SYSCON) verifies that a valid database is resident, then ouputs the
appropriate temperature and carrier set points. If a valid database is not verified, default set
points are left in place.
The analyzer monitors the oven temperature to ensure that it has stabilized at the set point
before automatically proceeding. Depending on how long primary AC power has been off, this
may take from 2 seconds to 45 minutes.
Cycle Control Flag
Cycle Control Flags can be used to run optional diagnostic cycles to validate analytical
hardware including solenoid valves, detectors, or carrier regulators. This option is typically
based on a custom application being initiated by a power-fail alarm.
Cycle Ccontrol Flags indicate if any analyzer cycle clocks are to be in RUN mode. If they are
not, the analyzer remains in the HOLD mode until operator intervention. If the cycle clock is in
RUN mode, based on having been in RUN mode prior to powering down, then RUN mode
starts in progress without waiting for intervention.
Program Event Scheduling
The Time of Day (TOD) clock schedules events on a second, minute, hourly, daily or weekly
basis. The clock is maintained on the system controller and schedules events from the residing
SYSCON database.
The TOD clock has one-second resolution that is maintained and generated by a hardware
device that maintains accurate time independent of analyzer power. This allows a power
recovery event to determine duration of power down state.
Certain events are scheduled on a frequency basis, which are independent of the TOD or
analysis cycle clocks. The frequency clock has a resolution of 1 second, which is used to
schedule repetitive events, such as reading DI and AI signals for alarm purposes. Scheduling
of frequency events can be set to 5 seconds or greater. They occur regardless of whether the
analyzer is in Run or Hold.
Description
A schedule event can be for instrument calibration and special calibrations. Special calibrations
include daily or shift averages, report logging to a printer or Host computer. When these tasks
are scheduled by the TOD clock, they are put into queue. This allows them to be performed
at the next appropriate time. Typically, this is after completion of current analysis cycle.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 11
Page 12
System Functions
3.2 Functions
If a calibration is scheduled, it is put in queue. The calibration then initiates after completion
of the current cycle, and when the appropriate time has passed for the calibration blend to flow
through the sampling valve. If shift average reports are to be calculated and printed, the report
should include all cycles, which started, or sampled, during the specified shift. To have data
available for calculation, a wait period may occur for completion of the current sample analysis.
Analysis Cycle Clock
The Analysis Cycle Clock (ACC) is another clock that provides the timebase for all events
associated with the actual chromatograph analysis cycle. SYSCON cycle clocks can be
configured to provide timed event resolutions of 0.1 second, 0.01 second, 0.01 minute, or 0.001
minute. This is the Sensor Near Electronics software module (SNE) Event Table Scan Rate,
which is independent of detector scan rates.
All SYSCON cycle clocks and associated SNE MUST BE of the same second or minute time
units. This clock works in conjunction with the Stream Sequence Table and associated sample
stream enable and skip flags. This controls sampling order and analysis of process streams
connected to the analyzer.
Accessing SYSCON
The clock cycle RUN mode is controlled by the SYSCON upon command from SNE. When a
clock cycle is started, the associated SNEs, for that method, initiate a mirror of the cycle clock.
SNE Cycle Clock
The SNE clock is the true basis of timed events relating to the Gas Chromatograph oven valve
timing, detector digitization and peak integration.
The SNE cycle clock is used to schedule the following events.
● Analysis valve timing
● Detector balances
● Temperature set points start and stop for
PTGC
Note
Scheduled solenoid valve events cause Solenoid Valve Control Module (SVCM) hardware to
be activated within 5 milliseconds of stated cycle time. Any scheduled pressure set-point
adjustments are transferred to the actual Electronic Pressure Control Module (EPCM)
hardware within 5 milliseconds.
● Cycle Reset
● Pressure set point timing for pressure
programming
● Analysis result calculations and reporting
Maxum edition II Analyzer General Maintenance
12 Manual, August 2018, A5E42019842001
Page 13
Manual Operations
System Functions
3.3 Analyzer Operation
Manually controlled functions can be initiated through the color touchscreen. A manuallycontrolled event can occur asynchronously with any event and control some of the analyzer
operations. Controlled items include:
● Activation of solenoid valves
● Balancing detectors
● Changing a pressure or temperature set
point
● Initiating a calculation
3.3 Analyzer Operation
This section provides an overview of the operation of the Maxum II analyzer. The examples
show a Maxum II Airless/Airbath model in order to include many optional features. Most
analyzers will have only some of these features; for example, the Modular Oven model has
no detector compartment.
The operational block diagram shows how a sample is processed within the analyzer. The
SNE functions are performed in software in new systems; older systems still have hardware
versions.
● Report logging event
● Change the cycle time of an event
● Initiate a calibration
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 13
Page 14
FPD
DPM
(A/D)
SYSCON
SNE Software Moule
GCP
I2C
Network
DPM
(A/D)
Electronic
Pressure
Control
Module
Solenoid
Valve
Control
Module
Temperature
Control
Oven
Heater
Control
Electronics Enclosure
DPM
(A/D)
FID
Detector Compartment
(Mezannine)
Oven
Sample
Conditioning
Atmosphere Vents
Feedthroughs
Sample In
TCD
Columns
Sample
Valve
Columns
Columns
Regulated Carrier Gas
I2C from SYSCON
System Functions
3.3 Analyzer Operation
Power On
Sample Conditioning
Figure 3-2 Operational Block Diagram (Maxum II Airless Airbath model shown)
The Power Entry Control Module (PECM), in response to commands on internal bus, accepts
system primary power and provides switching and control of AC power for oven heaters and
other AC powered devices.
Before being piped to the analyzer, the sample from the process is sent to a sample conditioner
system. The sample conditioner ensures that the process sample is compatible with the
requirements of the analyzer. That is, it assures that the phase, pressure, temperature and
flow rate to the analyzer are suitable, that the sample is filtered, that condensates are removed
and other treatments are carried out. The resultant conditioned sample is typically piped via
1/8-inch stainless steel tubing to the sample valve(s) located in the oven of the Maxum II.
Maxum edition II Analyzer General Maintenance
14 Manual, August 2018, A5E42019842001
Page 15
Sample Valve
The type of sample valve used in a Maxum II is application dependent. Five primary types of
sample valves are available.
● The first is the 10-port Model 50 valve that is designed for vapor sample only.
● The second is the Model 11 valve for vapor or liquid samples.
● Third is the Model 20 valve for liquid high-pressure samples.
● The fourth type is the set of Valco valves that are designed for high temperatures and very
low sample volumes.
● The fifth is the independently-heated Siemens Liquid Injection Valve.
The sample valve(s) and any column valves are controlled by a Solenoid Valve Control Module
located in the Maxum II’s electronics compartment. There can be up to three SVCMs installed
in an electronics compartment (EC).
Solenoid Valve Control Module
The Solenoid Valve Control Module (SVCM) provides pneumatic on/off control for both
sampling and oven systems functions. The SVCM manifolds are connected as a group of four
4-way and four 3-way solenoids. The (SVCM) receives commands from the I2C bus. Solenoid
commands are received from the SNE software module. Solenoid relay status is read back to
the SNE software module to indicate whether a selected solenoid is to be deactivated or
activated. Timing is controlled by SNE software module timing. There is no timebase in the
SVCM.
System Functions
3.3 Analyzer Operation
Columns
Column Valves
Commands from I2C bus control the deactivation or activation of solenoid valves. If fault or
warning conditions have occurred, pressure control and SVCM status information is returned
to the SYSCON database.
Samples are injected by the sample valves into the chromatograph columns where the samples
are separated into individual components. Many different types of columns may be used
including 1/16-inch micro-packed, 1/8-inch packed and fused silica or metal capillaries. The
columns used are dependent on the requirements of the application.
In most applications, there are multiple columns in use that are typically switched by column
valves located in between them. These column valves are not shown in the illustration, but like
the sample valves described above they are also controlled by the Solenoid Valve Control
Module and SNE software module.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 15
Page 16
System Functions
3.3 Analyzer Operation
Electronic Pressure Control
The carrier gas pressure that is used to push the sample through the columns is controlled by
an Electronic Pressure Control Module (EPCM) or in some applications by mechanical
regulators. The EPCM is mounted on manifolds located on the EC right-side wall. The EPCM
pneumatics are digitally controlled by the Sensor Near Electronics (SNE) software module. Up
to four EPCMs can be mounted in an EC. Each EPCM contains two channels, and each
channel can use a different gas at a different pressure. EPCMs are also used to control the
fuels for some of the detector modules. Each Electronic Pressure Control Module (EPCM)
communicates the actual pressure back to the SNE software module. Information may then
be displayed on the Maintenance Panel. Depending on model and application, up to 3 or 4
EPCMs may be installed
Oven Heaters
For the columns and detectors to work correctly, they must usually be operated at elevated
temperatures. The Maxum II uses electrical heater(s) to elevate the temperature. These
heaters (not shown in block diagram) are connected to relays in the electronics compartment
and, like the valves and the Electronic Pressure Control Modules, are controlled by the SNE
software module.
Detector
The sample eluted from the columns is transported to the associated detector that senses the
presence of the sample and converts it to an electrical signal. Depending upon the application,
the Maxum II can include up to three detector modules. Each detector module can have
multiple detector sensor elements. Several detector module types are available including
Thermistor, Filament, Flame Ionization, Flame Photometric, and Pulsed Discharge. The
resulting electrical signal from the detector is then connected to the Detector Personality
Module (DPM) located in the EC.
Sensor Near Electronics (SNE) Software Module
The detector signal(s) is routed to the Detector Personality Module (DPM). The DPM (unique
for each detector type) amplifies the analog signal and converts it to a digital signal. The digital
signal output from the DPM is processed by the SNE software module. The DPM is interfaced
to installed peripherals connected to the I2C bus through a set of digital and analog I/O signal
commands. All accessible I/O's are uniquely addressable through the module type, enclosure
ID, SNE, location ID and module channel number.
In earlier analyzers, the SNE control and processing functions were performed by a separate
processor board, called the SNE controller (SNECON) mounted in the DPM cage assembly
and connected to the SYSCON by an Ethernet cable.
System Controller (SYSCON)
The System Controller (SYSCON) resides in a pullout drop-down assembly located in the EC
and controls all external communications and internal communication. The SYSCON houses
the primary processor, plug-in I/O boards (for external signal control), communication
interfaces, and an interface to the maintenance panel display. All internal communication
between modules and SYSCON is via the internal I2C signal bus.
Maxum edition II Analyzer General Maintenance
16 Manual, August 2018, A5E42019842001
Page 17
Software SNE
DPM 3
Software SNE
DPM 2
I2C I2C I2C
Sampling
System
I2C
CAC3
CAN
RS485
RS232
Analyzers
GCP
Ethernet
Ethernet
Switch
(optional)
I/O
Boards
I2C
I2C
EPCs
SVCMs
Ethernet
I2C
I2C
GCP
Color
Touch
Display
SYSCON
(SIB3)
PECM
Controller
Board
Software SNE
DPM 1
System Functions
3.4 Data Communication
The original SYSCON consists of a single controller board. The newest version of SYSCON,
called SYSCON2, is a base SIB (SYSCON Interface Board) with an attached CAC3
(Communication and Control board). The SYSCON combines all data results and performs
additional high level data processing and calculations. The SYSCON connects to a color
touchscreen display, strip chart recorder, other analyzers, printers, the Advance
Communication System (ACS), or other connected networks.
The SYSCON is the analyzer control system in addition to containing the application database.
The application database also contains analytical hardware database definitions that are used
to perform the following functions:
● Obtain desired sampling measurements
● I/O and SNE schedule of timing events
● Sequence of sampling streams
3.4 Data Communication
Internal Communication
An I2C Internal Bus provides communication between the SYSCON, SVCM, EPC, PECM and
to the I/O bus. External communication is through an Ethernet link. The interface for each type
of module is described in the Component Descriptions and Maintenance Procedures section.
● Calculations of reported values
● Formatting of results and location and
outputting results
● How to report or correct error conditions
Figure 3-3 Data Communication Paths
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 17
Page 18
.
129.1 - 1.: 11 - 111
SNE ID
Module Type
Channel Type
Channel Number
PIC Index
Module Number (Location ID)
Sub Module Type & Description
System Functions
3.4 Data Communication
Module Addressing
The Maxum II modules located in the electronic compartment have their own physical address
and communicate via the I2C Internal Bus, shown in the diagram below. Address information
is contained in the SYSCON database and identifies modules by their location. Each DPM is
associated with a software SNE module that appears in the list as a separate device.
Identification Number
All modules within the Maxum II electronic compartment have a unique identification number
as related to the software SNE module which controls them. The identification relationship
between the SNE and the modules it controls is referred to as the SNE ID String.
Figure 3-4 Identification Number
Address information is located in the analyzer local I/O Table. The I/O points are identified by
module type, mounting location within the electronic compartment and channel number. This
allows module addressing from either the SYSCON database, SNE Tables or from Advance
Database.
18 Manual, August 2018, A5E42019842001
Maxum edition II Analyzer General Maintenance
Page 19
General Maintenance and Troubleshooting
4.1 Analyzer Status Indicators
4.1.1 Operator Controls
Color Touchscreen
4
Status LEDs
The color touchscreen displays all mainte‐
nance functions and data in a graphical dis‐
play. In addition it can also display both realtime and stored chromatograms. The stored
chromatograms include voltages and cycle
times for future comparison as well as zoom
and pan features. Operational and routine
maintenance tasks for the analyzer can be
performed from the color touchscreen interac‐
tive display screens and menus. System se‐
curity is assured with multiple levels of pass‐
word protection for all analyzer-operating
functions.
A color touchscreen emulator (also called a Human Machine Interface, or HMI, emulator) is
available from the Maxum Gas Chromatograph Portal (GCP) software. This emulator allows
a user to perform color touchscreen tasks without being located at the unit.
Purge (Flashing Red) Purge pressure lost
Fault (Red)
Warning (Yellow) "Maintenance request" status signal is active
"Failure" status is active
Power (Green) 24 V power supply is on
All LEDs are on during power-up boot.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 19
Page 20
General Maintenance and Troubleshooting
4.1 Analyzer Status Indicators
Workstation
The Maxum II uses a PC based network
workstation for programming and data
processing. Analyzers can be program‐
med and monitored from a single location,
and, like the color touchscreen, the work‐
station includes graphical displays for op‐
eration, maintenance, and diagnostics. It
also supports PC printers to print chroma‐
tograms and alarm logs in order to meet
record keeping requirements.
The Maxum II workstation software, Gas Chromatograph Portal (GCP), is designed for PCs
with Microsoft® Windows operating systems. PC workstations can be connected through
existing LANs for wide access to monitoring or maintenance tasks. The graphical interface
recognizes and displays all network hardware. The system monitors the alarm status of all
analyzers connected to the network to centralize system maintenance. More information can
be found in the Gas Chromatograph Portal User Manual (A5E03944542001) at https://
support.industry.siemens.com/cs/document/109745485/gas-chromatograph-portal-usermanual-maxum-microsam?lc=en-WW&pnid=17741 (https://support.industry.siemens.com/cs/
document/109745485/gas-chromatograph-portal-user-manual-maxum-microsam?lc=enWW&pnid=17741).
Chromatography Software
Using GCP, it is possible to set up methods and component peak identification.
GCP allows a user to choose the best peak gating and basing methods automatically. It is also
possible to:
● Re-process captured chromatograms with different methods
● Measure unknown component peaks automatically
● Record multiple detector measurements simultaneously.
Maxum edition II Analyzer General Maintenance
20 Manual, August 2018, A5E42019842001
Page 21
4.1.2 LED States Inside the Electronics Cabinet
Normal
Fault
Warning
Power Active
Heater 2
Temp Limit
Overtemp
Flameout
Ignite
Alternate Range
Power Active
Heater 1
Temp Limit
Overtemp
4.1.2.1 Base3DPM Status Indicator LEDs
General Maintenance and Troubleshooting
4.1 Analyzer Status Indicators
Figure 4-1 Base3DPM Status LEDs
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 21
Page 22
I2C-Pullup
Active LEDs
3
2
1
0
PCI Slot LEDs
Reset
I/O Connector
DI Mode
Switch
(Set to Mode 2)
CAN
Bridge
LEDs
Power LEDs
Internal
Ethernet
to SNECON
LEDs
CAC3
I2C LEDs
General Maintenance and Troubleshooting
4.1 Analyzer Status Indicators
4.1.2.2 SIB3 LEDs
LED Locations
The SIB3 has several LEDs that indicate useful information about the operating status of
various interfaces.
Figure 4-2 SIB3 LEDs and Switches
22 Manual, August 2018, A5E42019842001
Maxum edition II Analyzer General Maintenance
Page 23
General Maintenance and Troubleshooting
4.1 Analyzer Status Indicators
Power LEDs
Located at the back of the board near the RJ 45 connector
Description Color and Meaning
Power Green – 3.3V power is available. Should be on at all times
Power Bad Red – Power is faulty or SYSCON hardware reset switch is being pressed
CAC Conn Bad Red – Connection from the SIB3 to the CAC3 is faulty or incomplete. After power up, this
LED should turn off once CAC3 to SIB3 connection is completely initialized.
I2C Bus LEDs, Buses A and B
Located next to I2C Bus connectors
Description Color and Meaning
LED2/5 Norm/Comm Dim Green – I2C Bus is normal
Bright Green - I2C Bus is communicating
LED3/6 Warning Yellow – Warning on the I2C Bus
LED4/7 Fault Red –I2C Bus fault
I2C Bus Pullup-Active LEDs
Located next to battery holder
Description Color and Meaning
LED19, 20 The Auto-pullup feature is supplying pullup current on the I2C Bus.
Can Bridge LEDs
Located to the left of the far left PCI slot
Description Color and Meaning
LED16 Ready/Comm Dim Green – Can Bridge is normal
Bright Green – Can Bridge is communicating
LED17 Warning Yellow – Warning on the Can Bridge
LED15 Fault Red – Can Bridge fault
Can I/O LEDs
Located next to far left CAN direct connector, CAN direct 5
Description Color and Meaning
LED8 TX Green – On when a valid CAN I/O message (other than a heartbeat reply) has been received
and queued for processing
LED9 RX Green – On when a CAN message (other than a heartbeat transmission) has been queued
for sending to the CAN hardware
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 23
Page 24
General Maintenance and Troubleshooting
4.1 Analyzer Status Indicators
Description Color and Meaning
LED10 Heartbeat Green – Flashes once for each heartbeat message transmitted. This LED will flash once
every 1.5 seconds for each active CAN card
LED11 Fault Red – On when an error state is detected on the CAN bus hardware
PCI Slot LEDs
Located between PCI slots
Description Color and Meaning
LED14 Slot 0 Fault Red – Overcurrent or thermal shutdown on PCI slot 0
LED13 Slot 1 Fault Red – Overcurrent or thermal shutdown on PCI slot 1
LED18 Slot 2 Fault Red – Overcurrent or thermal shutdown on PCI slot 2
LED12 Slot 3 Fault Red – Overcurrent or thermal shutdown on PCI slot 3
Internal Ethernet LEDs
Located next to and on SIB3 RJ-45 connector
Description Color and Meaning
Green LED on RJ-45 Green – LED is green when link is in full duplex mode
Yellow LED on RJ-45 Yellow – LED is on when link is active. Will flash off for transmit or receive activity.
LED1 Speed Green –
On – Speed is 100 Mb/sec (or auto-negotiating)
Off – Speed is 10 Mb/sec (or disconnected)
Maxum edition II Analyzer General Maintenance
24 Manual, August 2018, A5E42019842001
Page 25
4.1.2.3 PECM LEDs
State 1 - Power off
State 2 - Self test
State 3 - Address assignment
State 4 - Normal operation
State 5 - Warning condition; data good temporarily
State 6 - Fault condition; data invalid
Normal
Fault
Warning
PECM-CTRL PCB
LEFT Heater Status RIGHT Heater status
Heater 1 Air Pressure
Heater 1 Power Activate
Heater 1 Temp Limit
Heater 1 Overtemp
Heater 2 Air Pressure
Heater 2 Power Activate
Heater 2 Temp Limit
Heater 2 Overtemp
Normal
Fault
Warning
Normal
Fault
Warning
PECM Status
Temperature
Controller
Status
The LEDs on the PECM board can help with troubleshooting problems. There are two sets of
LEDs: one on each side of the front board as shown in the diagram to the right. The bottom
set of three LEDs is the same as used on other boards. The left set is for the PECM software
and the right set is for the temperature controller software. Each will go through a separate
display on power up and normal operation. The top two sets of four LEDs each are for the
operation of each of the two temperature controllers on the front board. Heater 1 is on the left
and heater 2 is on the right side of the board.
General Maintenance and Troubleshooting
4.1 Analyzer Status Indicators
PECM LED Interpretation
PECM LEDs
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 25
Page 26
1RUPDO
)DXOW
:DUQLQJ
+HDWHU2Q
2YHUWHPS
+HDWHU6KRUW
General Maintenance and Troubleshooting
4.2 Leak Testing
4.1.2.4 Modular Oven Model PECM-DC LED Locations
LED Status Indicators
The PECM-DC LED locations are shown below.
4.2 Leak Testing
A gas chromatograph is a complex device with many gas fittings. Under normal thermal and
vibration stresses, these can develop leaks. Therefore, periodic leak testing must be performed
in accordance with local safety ordinances and rules.
General Overview of Leak Test Methods
An overall static pressure test of the analyzer installation can detect if a leak exists somewhere
in the system.
1. Install caps on all vents.
2. Make sure the system is properly purged.
3. Increase EPC settings to maximum, or to pressures specified by safety rules.
4. Open the gas supply valves and allow the entire system to be pressurized.
5. Close gas supply valves and watch for a pressure drop over a minimum time period. This
time period will be application specific and may be specified in local safety rules.
6. Operate the column and sample valves to ensure all parts of the system are pressurized.
Some pressure drop may be seen upon valve operation; shortly afterward the pressure
should stabilize and hold the current pressure.
7. If no pressure drop is observed, then the test can be ended, the vent caps removed, and
the analyzer safely placed into service.
8. If a pressure drop is observed, a leak exists. Leaks can affect the application reliability and
the safe operation of the analyzer. The leak must be isolated and repaired.
26 Manual, August 2018, A5E42019842001
Maxum edition II Analyzer General Maintenance
Page 27
4.3 General Analyzer Shutdown Procedure
Back Up the Database
If a current database has not been saved, first save a database to a remote device to provide
a potential method of reloading if a CAC3 has been replaced or an earlier database needs to
be restored to the analyzer. Generally, a database reload will not be needed, though in some
cases this may be required.
1. Put the Maxum II in Hold and wait for the cycle to complete. This will provide the quickest
restart of the application when power is restored.
2. After the cycle has completed and the analyzer is in Hold:
– Turn off carrier gas, valve gas, instrument air, and sample flows.
– Remove power from the unit.
WARNING
General Maintenance and Troubleshooting
4.4 General Analyzer Startup Procedure
Voltage dangerous to life exists. Failure to follow appropriate safety procedures may result
in severe injury or death.
Before beginning to work inside the electronics compartment, the power must be externally
removed from the GC. AC power comes directly into the electronics enclosure, so power must
be removed and secured/tagged to prevent inadvertent application while work is being
performed.
4.4 General Analyzer Startup Procedure
The startup procedure described in this section explains the principle steps necessary to power
the Maxum II in a manner that does not compromise the safety systems of the analyzer.
Note
The specific application and the facility in which this equipment is installed will impose
additional requirements for startup and shutdown.
This section does not explain the startup procedures required that relate to software functions
or the analytical application of the analyzer. Please see other documentation and manuals for
information and startup steps that relate to these other aspects of startup.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 27
Page 28
General Maintenance and Troubleshooting
4.4 General Analyzer Startup Procedure
4.4.1 Procedure
Following is the procedure for safe startup of the Maxum II.
1. Verify that AC power is turned off at main power feed lines. All indicator lights should
be off.
2. Verify that the analyzer has been mounted and installed correctly.
3. (If APU is used) Verify that all power and signal lines have been connected correctly
through the APU power-disconnect relay and signal-disconnect relays.
NOTICE
APU Considerations
When an APU is used, there must not be any wiring entering the Maxum II EC that is powered
from any outside source without connecting through the APU signal-disconnect relays. This
warning includes the Advance Data Hiway, Ethernet, and any other input or output signal
lines that are connected to other equipment which may source power onto the signal lines.
4. Verify that clean (free of particulates and flammable gases and vapors), dry instrument
air has been attached correctly to the analyzer air lines. Refer to separate installation
documentation for instructions on making required attachments. Air flow should be
set to off at this time.
All air, gas supply and sample lines should be blown down and cleared of any partic‐
ulates or chemicals prior to pressurizing these lines to the Maxum II gas chromato‐
graph.
5. Make a physical inspection of all analyzer safety systems to verify that there is no
mechanical damage and that all systems are in good repair. This inspection must
include the Methanator (if in use), the Air Treater (if in use), the oven heater systems,
and all detector assemblies. Refer to the "Maintenance Considerations" sections pro‐
vided throughout this manual for specific inspection tasks for different components.
6. Inspect the EC door gasket. Verify it is clean and will seal all the way around the door.
Check all ports both gas and electrical to verify they are sealed to the cabinet and any
electrical wiring external connections have a proper wire seal.
7. (If APU is equipped) Verify that the maintenance switch for the APU is set for normal
operation.
8. (If APU is not equipped) Verify that fast purge valve is set to off.
9. Close the EC door and oven door. Turn on instrument air and verify that cable access
points and other openings in the EC are properly sealed or closed off.
Note
The remainder of the startup process is dependent on whether an APU is installed.
If py (not equipped with APU)
10. Set the air pressure to the value stated on the purge tag.
Maxum edition II Analyzer General Maintenance
28 Manual, August 2018, A5E42019842001
Page 29
General Maintenance and Troubleshooting
4.4 General Analyzer Startup Procedure
11. Turn on the fast purge switch and allow fast purge air to flow for at least 8 minutes.
Flow of fast purge air can be verified because of the louder sound of the air flow. The
fast purge relief valve opens slightly and the air can be heard as it leaves the EC.
12. Turn off the fast purge switch. Flow of normal purge air should continue.
13. Turn on electrical power to the system.
If px (equipped with APU)
14. Turn on electrical power to the system. The remainder of the startup process is auto‐
matic and is described as follows.
15. APU power comes on. The Purge LED next to the maintenance switch begins to blink.
16. The APU activates the fast purge function. Activation of fast purge can be verified by
the louder sound of air flow. Fast purge continues for approximately 8 to 20 minutes.
During this time the Purge LED next to the maintenance switch should blink intermit‐
tently. Allow at least 30 minutes before interrupting the startup purge to diagnose a
delay.
17. Once the APU determines that the analyzer is properly purged, it activates power to
the analyzer. At this point the Purge LED next to the maintenance switch should stay
on constantly.
Note
If the fast purge process does not complete correctly ending in the Purge LED light remaining
on, then turn off power and repair any leaks that may exist.
(For all systems)
18. Once power has been applied to the main analyzer, complete startup of the system
(refer to startup procedures available in installation documentation). For systems with
APU, the Purge light next to the maintenance switch should remain on. For systems
without APU, the purge light on the Maintenance Panel or CIM display should remain
off.
Note
(For systems without APU) If there is ever a loss of purge, the Purge alarm LED on the display
will light and a software purge alarm is logged.
(For systems with an APU) If there is ever a loss of purge, the APU will turn off power to the
analyzer.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 29
Page 30
General Maintenance and Troubleshooting
4.5 Accessing the Bootloader
4.5 Accessing the Bootloader
Accessing the Bootloader to Set the Network Address
This procedure is needed when a CAC3 is replaced, when the memory backup battery is
removed, or when the CAC3 is removed from a CIM or SIB3. In this procedure, the term
"SYSCON" can mean either a SYSCON assembly in a Maxum Airless/Airbath model or a CIM
in a MAxum Modular Oven model analyzer. To prepare, disconnect the analyzer from the
network by unlugging the Ethernet cable.
From the color touchscreen in the door of the analyzer, use this set of steps to set the IP
addresses. This allows the GCP software to communicate with the device so that a database
may be loaded.
1. Push the reset button through the opening on the SYSCON cage. This provides access to
the bootloader.
2. Press the Home key when the message “To enter the bootloader menu, press the Home
key now…” appears.
3. Press the 5 key to select the “Configuration” menu.
4. Press the 4 key to select “Choose Device Mode”.
5. Press the 2 key to select “Standalone SysCon”.
6. The SYSCON reboots into standalone mode.
7. Press the Home key to re-enter the boot loader
8. Press the 5 key to select the “Configuration” menu again.
9. Press the 2 key to select “Primary Ethernet IP Configuration”.
10.The question “Do you want to change this configuration?” appears: Press the 9 key to select
“Yes”.
11.Press the 0 key to disable DHCP.
12.Press the 9 key to change the IP address.
13.Enter the desired IP address. Press the “Home” key to return to the menu.
14.Press the 9 key to change the subnet mask.
15.Enter the correct subnet mask. Press the “Home” key to return to the menu.
16.Press the 9 key to change the Default Gateway address.
17.Enter the Default Gateway address. Press the “Home” key to return to the menu.
18.Press the 0 key to select “No” to the question “Change the DNS?”
19.Press any key to continue.
20.Press the Back key to return to the bootloader menu.
21.Press the 9 key to reset the device.
The external Ethernet cable may now be reconnected to the network, and the analyzer should
be visible in the GCP Network list.
Maxum edition II Analyzer General Maintenance
30 Manual, August 2018, A5E42019842001
Page 31
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
4.6 Alarm Codes, Descriptions, and Suggested Actions
4.6.1 Alarms 301 - 324
GCP Alarm Descriptions 301 - 324
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# Text Description Action
301 ? External Message: send
failure %3
302 ? External Message: server
lost
303 + External Message: Rec'd
invalid communication
from unit %3
304 + External Message: Orphan
message received from %3
305 ? External Message: Invalid
Message Length for %3
306 + External Message: Send in‐
valid communication to unit
%3
307 ? External Message: Dupli‐
cate anlz_id %3 detected ;
setting to zero
308 ? External Message: Dupli‐
cate UNIT %3 detected;
setting loop/unit to zero
309 ? External Message:
RUD:Unit does not re‐
spond; loop/unit %3
A message was received by the device
from itself; or source of message can't be
identified; or Gateway is too busy or com‐
munication was disrupted between the
GC and the message handler.
System Error Contact Customer Support.
Message was received from Advance
DataHiway unit that had previously
broadcast with no slots or slot is out of
range.
An Advance DataHiway external
PANDSP message was received with no
matching PANKEY; or an ATTACH was
received with no matching RATCH; or an
internal timeout was generated for nonexistent message.
Advance DataHiway Results, print, HAE,
or Service Panel messages received
from GC that have no length.
Message from GC is directed to an Ad‐
vance DataHiway unit that has no slots,
an invalid range of slots, or no UID has
ever been received.
An Advance DataHiway ZIP message
was received from another Advance Da‐
taHiway unit, or another GC has broad‐
cast with the same analyzer num‐
ber.Check other units on network.
An Advance DataHiway SLEEP mes‐
sage has been received. Another Ad‐
vance DataHiway unit has broadcast
with the same loop/unit.
Occurs when Advance DataHiway loop/
unit does not respond to a RUD message
- originates from I/O, Host, or Printer ta‐
ble in GC.
Reset Gateway or SYSCON.
Reset Advance DataHiway unit.
Ignore or reset SYSCON.
Check database set up for these mes‐
sages.
Check Advance DataHiway unit.
Check other units on network.
Check other units on Advance DataHi‐
way and correct loop/unit of GC.
Remove extraneous references to nonexistent units. Check Advance Data‐
Hiway connection.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 31
Page 32
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
310 ? External Message: Unit not
known for %3
311 ? External Message: Error
for Activation of EVT on %3
312 ? External Message: Send
error for %3
313 ? External Message: Invalid
TOR sequence on %
314 ? External Message: Anlz:
%3 & Anlz: %4 have loop/
unit conflict
315 ? External Message: Anlz id
exceeds allowable limit for
ADH
316 ? External Message: Host:
Anlz 1 to 50 config conflict
317 ? External Message: Host:
for anlz 51-254 stream>1
or # of components>9
318 ? External Message: Host: in‐
valid data received from
anlz
319 ? External Message: no re‐
sults marked to transmit for
stream %3
320 ? External Message: %3
Timeout for %4
321 + External Message connec‐
tion opened on: %3
322 ? No ADH connection detec‐
ted %3 failed
323 ? External Message: Invalid
LOOP %3 detected ; set‐
ting loop/unit to zero
324 ! Error processing database
command %3
GC is trying to communicate with an un‐
known unit on the Advance DataHiway.
Bad Advance DataHiway Host Activation
Event message was sent by GC to mes‐
sage handler.
Send failure for UDP outgoing message
sequences.
An Advance DataHiway SEND message
was received from external unit when
there are no results to send.
Two Advance GCs have duplicate Ad‐
vance DataHiway addresses (loop,unit).
FUNCT 88 Advance DataHiway Alarm
message received from HCI-H; or GC
attempted a broadcast with an ana‐
lyzer_id greater than 255.
FUNCT 89 Advance DataHiway Alarm
message received from HCI-H.
FUNCT 90 Advance DataHiway Alarm
message received from HCI-H.
Advance DataHiway H card is sending
alarm back to GC.
No results are marked for transmission.
Comes from GC prior to transmission.
Advance DataHiway message timeout
for ADREQ, REXD, results, HAE, Print,
FUNCT.
Normal message from reset. No action necessary.
No message handler. This means that
that certain software components are not
working.
An Advance DataHiway WRLP message
has been received.
An error has occured in SQL messaging
to a remote or local database table for
Modbus or remote I/O.
Wait 10 minutes to see if this condition
will correct itself. If it does not, verify
that the Gateway is communicating with
the GC.
Check MaxBasic programs for invalid
setting of attributes on the analyzer ta‐
ble.
This is a general failure that indicates a
network fault.
Check result transmit, # of results.
Check for duplicate loop,unit addresses
on the two analyzers and correct the
duplication.
Check analyzer ID.
Check # results and # streams against
HCI-H limitations.
Check # results and # streams against
HCI-H limitations.
Check trtval in result table.
Check trtval in result table.
Reset SYSCON. If the alarm occurs
again, contact Customer Support.
Contact Customer Support.
Check Loop of GC.
Check network communication and
contact Customer Support.
Maxum edition II Analyzer General Maintenance
32 Manual, August 2018, A5E42019842001
Page 33
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
4.6.2 Alarms 330 through 359 SNE Communication
GCP Alarm Descriptions 330 - 359
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# Text Description Action
331 ! Run Method: No SNE
found or bad status on mod‐
ule: %3
332 ! Run Method: No module
found for detr: %3
333 ! Run Method: No Detr found
or bad status for meth‐
od.channel: %3
334 ! Run Method: No Channel
found for method: %3
335 + SNE connection opened
on %3
336 ! SNE connection closed on
%3 error: %4
337 ! SNE connection replaced
on %3
338 ? SNE %3 Method %4 Can‐
not Store Chrom
339 ? SNE %3 Method %4 Appli‐
cation %5 not found
340 ! SNE %3 Method %4 Load
- Invalid Method
341 ! SNE %3 Method %4 Inac‐
tive
342 ! SNE %3 Method %4 Load
- Max Method exceeded
The connection between the GC and the
SNE is invalid.
The SNE has not reported the detector,
pressure controller, or temperature con‐
troller.
Realtime chromatogram attempt on inva‐
lid detector, or bad status on detector.
No channels are present or can't find de‐
tector for channel.
System error Contact Customer Support.
SNE connection closed due to timeout or
error.
System error Contact Customer Support.
Results received from SNE for unknown
stream.
Can't find application or method to match
SNE results. This indicates that messag‐
es between the SNE and SYSCON are
corrupted.
SNE has sent a status message that the
method is invalid. No other information is
available.
SNE sent message that method is inac‐
tive. No other information is available.
SNE sent message that maximum meth‐
ods has been exceeded.
Check cable between the SNE and SY‐
SCON.
Check the LEDs on the SNE to see if it
is running.
Check hardware connections to SNE.
The GC can contain references to inva‐
lid hardware channels.
Check the pressure, temperature, and
detector channels defined in the appli‐
cation for correct assignments.
Check hrdwr_id, module for app_detec‐
tor. The GC can contain references to
invalid hardware channels.
Check the detector channels defined in
the application for correct assignments.
Check app_detector, EZChrom method
for proper hardware channel assign‐
ments.
If IP address specified is not a
192.168.144.# network address, check
for appropriate grounding of system.
Otherwise check SNE for appropriate
connections and software versions.
Check stream table. It is possible to de‐
lete streams during the run of a cycle.
If that is done, then this alarm may oc‐
cur.
Reset SNE to sychronize messages. It
is possible to delete applications during
the run of a cycle. If that is attempted,
then this alarm may occur.
Download method from EZChrom
again.
Restart the application.
Reduce number of methods, reset SY‐
SCON.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 33
Page 34
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
343 ! SNE %3 Method %4 Load
- Invalid Mode
344 ! SNE %3 Method %4 status
- unknown error %5
345 ! Stream Valve does not ex‐
ist
346 ! SNE %3 Write IO %4 does
not exist %5
347 ! SNE %3 Read IO %4
does not exist
348 ? SNE %3 RT chrom %4
does not exist
349 ? SNE %3 Method %4 - Write
attempted on active meth‐
od
350 ! SNE Module I/O error 0x
%3 on %4
351 ! SNE pSOS error 0x %3 on %4System Software Failure. Report the error number and the mod‐
352 ! SNE pSOS Driver error 0x
%3 on %4
353 ! SNE AAI Driver error 0x %3
on %4
354 ? SNE TFTP load Error on
%3 : %4
355 ? SNE FLASH Driver Error
on %3 : %4
356 ! SNE %3 Stream/Method
%4 / %5 does not exist
357 ! SNE Method %3 - Invalid
message argument
Invalid run/hold sent to SNE. Reset SYSCON or try placing applica‐
tion in run.
Unknown error from SNE method status. Reset SNE/SYSCON.
Can't find appdo or sys_do for DO set in
cycle_events. Digital Output on cy‐
cle_event may not be valid.
IO write was sent to SNE, where I/O does
not exist.
IO read was sent to SNE where the I/O
does not exist.
Realtime chromatogram request to nonexistent SNE.
Ignore: Alarm was removed from Ver‐
An operation attempted on an attached
SNE module failed.
Driver Software Failure. Report the error number and the mod‐
AAI custom driver failure. Report the error number and the mod‐
TFTP load failure during download of
SNE software.
Flash Memory Failure. If persistent, replace SNE.
Results received from SNE: Can't locate
stream/method. Deleting streams and
methods or downloading methods while
a cycle is running can cause this error.
This indicates that the SNE has an obso‐
lete software version or the messages
between the SNE and SYSCON have
been corrupted.
Check DO on application I/O tables to
see if the DO exists for this application
and has a normal status.
Reset SNE/SYSCON.
Check the sys_hardware table for nor‐
mal I/O status.
If any I/O is not normal, investigate the
cause.
Reset SNE/SYSCON
Check the sys_hardware table for nor‐
mal I/O status.
If any I/O is not normal, investigate the
cause.
Reset SNE/SYSCON
Check the sys_hardware table for nor‐
mal I/O status.
If any I/O is not normal, investigate the
cause.
sions 4.3 and later.
Report the error number and the mod‐
ule to Customer Support.
ule to Customer Support.
ule to Customer Support.
ule to Customer Support.
Verify that TFTP server is running
Verify correct IP address
Verify correct file location
Retry TFTP load
Check sequence. Place application in
hold and then run again.
Check the SNE and SYSCON software
versions with the upgrade tool.
Reset the SYSCON and SNE.
Maxum edition II Analyzer General Maintenance
34 Manual, August 2018, A5E42019842001
Page 35
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
358 ! SNE Invalid I/O Write from
SNE on %4 , command %5
359 ! SNE I/O not found on I/O
Write from SNE: %4
This should only occur if the SNE has an
old software version or the messages be‐
tween the SNE and SYSCON have been
corrupted.
This should only occur if the SNE has an
old software version or the messages be‐
tween the SNE and SYSCON have been
corrupted.
Check the SNE and SYSCON software
versions with the upgrade tool.
Reset the SYSCON and SNE.
Check the SNE and SYSCON software
versions with the upgrade tool.
Reset the SYSCON and SNE.
4.6.3 Alarms 360 - 399
GCP Alarm Descriptions 360 - 399
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# Text Description Action
360 ! %!3 %4 General SNE Fault. Contact Customer Support.
361 ? %3 %4 General SNE warning. Contact Customer Support.
362 + %3 %4 General SNE note. Contact Customer Support.
363 ! Invalid function request %3
from SYSCON
364 ? No real-time buffer exists
for detector %3 on DPM %4
365 ! Incomplete Analysis on
channel %3
366 ! Data Corruption Error Major Data corruption on SNE Reset SNE
367 ! System Error %3 in File %4
line %5
368 ! Unable to find %3 number %4Hardware specified in method is not in
369 ! Unsupported channel type %3Hardware channel operation requested
370 ? No channel %3 on DPM
%4 for realtime display
This indicates that the SNE has an obso‐
lete software version, or that the messag‐
es between the SNE and SYSCON have
been corrupted.
Detector data is being collected for a de‐
tector that wasn't properly enabled.
EZChrom analysis was not completed on
channel.
System Software Failure. Record sequence of events leading to
analyzer.
for an invalid channel type.
Realtime display requested for a detector
channel that doesn't exist. Indicates da‐
tabase corruption.
Check the SNE and SYSCON software
versions with the upgrade tool.
Reset the SYSCON and SNE.
If received during a load sequence, it is
an artifact of the shutdown sequence.
Otherwise, record occurrence and
DPM information and report to Custom‐
er Support.
Modify integration events in method.
Send method to Customer Support.
Report error to Customer Support.
occurrence and report error, along with
the complete contents of the alarm mes‐
sage, to Customer Support.
Verify that the method is correct.
Inspect for current version of SNE soft‐
ware. May require a reload or rebuild of
corrupted SYSCON database.
Restore an older version of the data‐
base.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 35
Page 36
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
371 ! Invalid channel acquisition
overlap on %3
372 ! Scheduling error %3 scan‐
ning %4 # %5 channel %6
373 ! Module I/O error %3 on %4
# %5 channel %6
374 ! Internal communication er‐
ror %3
375 ! End of cycle missed; stop‐
ping cycle
376 + Adjusting cycle clock mas‐
ter
377 ! Error %3 scheduling cycle
clock master adjustment
378 + %3 samples adjusted on
chrom from channel %4
379 ! Error %3 preparing analy‐
sis for channel %4
380 ! Error %3 finding chrom
peaks for channel %4
381 ! Error %3 generating re‐
sults for channel %4
382 ! EZChrom server failed er‐
ror %3 on channel %4
383 ? Software Watchdog Time‐
out
384 ! Method Modification Failed An attempt to modify a running method
385 ? Event occurred before
modification request
386 ! Invalid Cycle Length %3 A cycle length larger than the maximum
387 ! Invalid Sample Rate %3 on
channel %4
Two channels referencing the same
hardware detector are scheduled to ac‐
quire at the same time.
Unable to schedule all event and polling
routines. May indicate a memory or hard‐
ware failure.
Error between module and channel. Indi‐
cates obsolete anayler.
Software modules inside SNE are failing
to communicate. Usually happens with
out of memory condition resulting from
SYSCON timeout.
The message that coordinates the end of
a method around the SNE tasks was lost.
Obsolete software version. Contact Customer Support.
Resource not found for scheduling ad‐
justment of event clock. SNE may be
overloaded.
An excessive number of samples re‐
quired adjustment on chromatogram. Oc‐
curs in conjunction with DPM alarms.
EZChrom processing error. Check integration events; modify
EZChrom processing error. Check integration events and peak ta‐
EZChrom processing error. Example er‐
ror: Setting the threshold value too low,
causing many peaks to be detected in
the noise of the chromatogram.
Resource problem on SNE. Reduce SNE workload.
SNE is running out of processing capaci‐
ty.
failed, most likely due to invalid data.
Before a modification of a running meth‐
od was completed, the event occurred.
size was specified in a method. Usually
caused by a corrupt method. Maximum
cycle length is approximately 2 days.
Invalid sample rate value chosen for
channel in method.
If multiple application detector channels
are assigned to the same hardware de‐
tector, do not allow their times to over‐
lap.
If method schedules many events as
well as all 18 detectors, try removing
some of the events or deleting some of
the detectors, then resetting the SNE.
Consider upgrading analyzer.
Reduce processing requirements on
SYSCON.
Reset SNE.
Reduce the complexity of the SNE set‐
up.
Replace SNE.
Reduce complexity of tasks for
SNE.Reset SNE to prevent event clock
overflow.
Replace affected DPM.
events that may cause problems.
ble; modify events that may cause prob‐
lems.
Check method for problems that could
affect results.
Replace SNE.
Reduce SNE workload.
Replace SNE.
Verify that modification was valid.
Contact Customer Support.
Verify correct values in method.
Verify the methods and use only a sup‐
ported detector sample rate.
Maxum edition II Analyzer General Maintenance
36 Manual, August 2018, A5E42019842001
Page 37
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
388 ! Acquisition time greater
than cycle length on chan‐
nel %3
389 ! Invalid Event Type %3 for
event %4
390 ! Invalid Start Time %3 for
event %4
391 ? %3 messages not sent to
SYSCON from SNE
392 ? %3 Detector underflows
detected on channel %4 of
module %5
393 ? %3 Detector opens detec‐
ted on channel %4 of mod‐
ule %5
394 ? %3 Unexpected Calibra‐
tion points on channel %4
of module %5
395 ? %3 Detector overflows on
channel %4 of module %5
396 ! SNE out of memory at %3
line %4
397 ! Invalid Trace from channel %3System error Contact Customer Support.
Start and stop acquisition times for a de‐
tector exceeded the method cycle length.
Invalid event downloaded with method. Check for proper SNE version. Rebuild
Event time specified that is outside the
cycle start and stop times.
Some messages that the SNE attempted
to send to SYSCON were lost. Results
may be unpredictable.
Detector is reading a raw value of 0. It
is potentially clipping the signal at the low
value.
Detector channel is not connected. Verify the detector hardware to ensure
Detector channel unexpectedly went into
calibration mode.
Detector is reading above its maximum
value and the signal is being clipped.
SNE is out of memory. Reduce SNE workload. Report to Cus‐
Decrease acquisition time or increase
cycle method time.
method.
Correct the method using EZChrom.
Reset the device.
Check the method.
that it is properly connected and that the
detector is not damaged.
Replace DPM if persistent.
Reduce the amount of sample or, if pos‐
sible, the detector gain.
tomer Support.
398 ! Invalid Number of Temper‐
ature or Pressure Program
Segments
399 + Results not calculated for
Channel %3
The number of temperature program set‐
points was different from the number
sent.
System error Contact Customer Support.
Rebuild temperature events for method.
4.6.4 Alarms 400 - 562
GCP Alarm Descriptions 400 - 478
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# Text Description Action
400 ! Sync Bus Failure %3 Sync Bus Test failed. Replace SNE.
401 ! No detector present for
configured detector %3
402 + SNE reset requested SYSCON requested a reset from the
On Advance Plus unit, configured detec‐
tor is invalid.
SNE. Usually means that the communi‐
cations between the SNE and SYSCON
timed out. This is can happen when
SYSCON is overloaded.
Check sys_detector_cfg configuration.
Reset SNE.
Reduce processing demands on SY‐
SCON.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 37
Page 38
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
403 ! Configured Detector %3
Balance Failure
404 ? All Methods must be in
Hold before Configuring
Detectors
405 ! Method not on tracking list:
Count = %3 Track ID = %4
406 ! Error %3 Monitoring Purge
Signal
407 ? SYSCON-SNE Communi‐
cations Overload Detected
408 ? Spurious detector acquisi‐
tion
409 ? SNE low on Memory SNE error. Reduce the memory consumption.
420 ! Heartbeat timeout MicroSAM: error Contact MicroSAM support for assis‐
421 ! Heartbeat lost MicroSAM: error Contact MicroSAM support for assis‐
422 ! Cannot connect to RSP MicroSAM: error Contact MicroSAM support for assis‐
423 ! Method %3 has more than
8 simultaneous events
424 ! Method %3 has more than
255 events
Balance Failure from an Advance+ de‐
tector.
All methods must be in hold while chang‐
ing the configuration of any configured
detectors.
SNE processing error. Contact Customer Support.
SNE or I2C error. Reset unit.
SNE or I2C messaging error. Contact Customer Support.
SNE error. Contact Customer Support.
MicroSAM: error Contact MicroSAM support for assis‐
MicroSAM: error Contact MicroSAM support for assis‐
Check sys_detector_cfg configuration.
Set all application in hold and wait for
cycles to complete. Then reconfigure
Advance Plus configured detector.
Some examples of how to do this in‐
clude:
Reduce the number of peaks detected
by increasing the threshold.
Reduce the length of cycles.
Reduce the detector sampling rate.
tance.
tance.
tance.
tance.
tance.
Maxum edition II Analyzer General Maintenance
38 Manual, August 2018, A5E42019842001
Page 39
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
425 ! EZChrom Method Verifica‐
tion failed, code %3
426 ! SIMDIS not supported The EZChrom method contains the simu‐
The method was successfully downloa‐
ded from the SYSCON to the EMSNE but
failed an integrity verification test. The
method is likely corrupted or may contain
a feature which is not supported. Code
values are listed below:
0: Unknown error, the method is likely
corrupt.
1: Invalid Method Binary, the method is
likely corrupt.
10: Invalid Cycle Lag time. The Cycle
Start value must be <= 0 sec.
11: Invalid Cycle Length. The Cycle Stop
value must be greater than the Cycle
Start.
20: Invalid Event List Binary. The method
is likely corrupt.
21: Invalid Event List Binary. The method
is likely corrupt.
22: Pulse DO duration too short for a
pulse DO event started at the time indi‐
cated by alarm Cycle Time.
23: Pulse DO extends beyond the end of
cycle, for a pulse DO event started at the
time indicated by alarm Cycle Time.
24: Invalid Pulse Polarity for a Pulse DO
event started at the time indicated by
alarm Cycle Time.
25: Pulse DO overlapping another DO
event, on the same channel, started at
the time indicated by alarm Cycle Time.
26: Multiple DO events at the same time
and on the same channel, at the time in‐
dicated by alarm Cycle Time.
40: The start time of a detector channel
is invalid.
41: Invalid Run Duration for a detector
channel.
50: Invalid Temperature Program seg‐
ment. The start time of the segment is
not within the cycle and was requested
to start at the time indicated by alarm Cy‐
cle Time.
51: Invalid Pressure Program segment.
The start time of the segment is not within
the cycle and was requested to start at
the time indicated by alarm Cycle Time.
lated distillation analysis option which is
not supported by the EMSNE.
The action to be taken is determined by
the code value in the alarm message,
as follow:
0: Replace the method.
1: Replace the method.
10: Change the Cycle Start value to be
smaller or equal to 0 sec.
11: Change the Cycle Stop value to be
greater than the Cycle Start.
20: Replace the method.
21: Replace the method.
22: Extend the pulse DO duration to at
least 1 ms.
23: The Cycle Stop value must be in‐
creased or the pulse duration must be
reduced to fit within the cycle.
24: The pulse polarity must be set to
positive or negative.
25: One affected event must be deleted
or moved to another time in the cycle,
in order to eliminate the overlap.
26: One affected event must be deleted
or moved to another time in the cycle.
40: The detector start time must be
changed to be within the cycle (be‐
tween Cycle Start and Cycle Stop).
41: The detector stop time must be
changed to be greater than the detector
start time.
50: The start time of the temperature
segment must be changed to be within
the cycle.
51: The start time of the pressure seg‐
ment must be changed to be within the
cycle.
Remove the SIMDIS option from the
method or use a separate SNECON if
SIMDIS is needed for this application.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 39
Page 40
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
427 + Detector simulation activa‐
ted
428 ! Invalid configuration for
smoothing noise measure‐
ment
460 ! Invalid Method Write System error Not applicable
461 ! Argument %3 , Invalid
Type %4
462 ! Invalid Method Section %3 System error Not applicable
463 ! Unable to Run Method,
Hardware Initializing
464 ! Unable to Run Method, In‐
strument Busy
465 ! Error Running Method An I/O error was detected while execut‐
466 ! Error Installing Method System error Not applicable
467 ! Error Retrieving Method System error Not applicable
468 ! Unable to Run Method, Not
on Method List
469 ! Invalid component results System error Not applicable
470 ! Invalid Spectrum results System error Not applicable
471 ! Invalid calibration file %3
line %4
472 ? Unknown method status %3System error Not applicable
The detector data reported by the DPM
is from a simulation chromatogram read
from the EZChrom trace binary and not
from actual data acquired by the DPM.
This is normal when running a simulation.
The method contains a channel with
smoothing noise measurement and the
time range used for noise measurement
is outside of the time range of the chro‐
matogram. The analysis was aborted
and the results for this channel could not
be calculated.
System error Not applicable
System error Not applicable
System error Not applicable
ing a cycle event associated with a run‐
ning method. This is probably caused by
a missing or invalid I/O module or by re‐
using the same detector channel in more
than one application.
System error Not applicable
System error Not applicable
If simulation is not desired, the trace
(TRC) binary must be removed from the
EZChrom method for non-simulated
chromatogram data to be collected.
Correct the method (on the workstation)
so that the time range used for noise
measurement falls within the time
range of the chromatogram.
Verify the status of all I/O modules and
correct as needed. To identify the I/O
module associated with this alarm, read
the alarm cycle time information and
use while looking up the list of cycle
events in the method. The problematic
I/O is one of the events with the cycle
time matching the cycle time reported
with the alarm.
473 ? Multiple component sets
not allowed
474 ? Multiple component scans
not allowed
475 ! Component report invalid System error Not applicable
476 ! Arguments do not match
script
477 ! Component report with no
associated method
478 ! Internal reset commanded System error Not applicable
System error Not applicable
System error Not applicable
System error Not applicable
System error Not applicable
Maxum edition II Analyzer General Maintenance
40 Manual, August 2018, A5E42019842001
Page 41
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
511 ! Program Failed event # %3 %4Error running MaxBasic program. Check message and program. If this
program was written by Siemens, con‐
tact Customer Support.
512 ? Program execution cancel‐
led: event # %3
513 ! Program Failed: Run re‐
quested on running event #
%3
514 ! Program Invalid frequency;
disabling event # %3
515 ? Program Overrun for event
# %3
516 ! Formula Failure: %3 The condition given in the alarm text pre‐
561 + EZChrom download Informational message. No action necessary.
562 + EZChrom upload for app
%1 method %3
Cancellation requested from HMI or CIM
Display.
Occurs when overrun_option is set to 2
and event is run while event is still run‐
ning from a previous request.
Invalid program frequency. Check program_schedule setup.
Occurs when overrun_option is set to 1
and warns that a program is running
when a previous run of the same pro‐
gram has not finished.
vented the formula from returning a re‐
sult.
Informational message. No action necessary.
Informational. No action necessary.
Check event timing or change overrun
option.
Check cycle event timing or frequency
of program or ignore.
Investigate the condition given in the
alarm text.
4.6.5 Alarms 671 - 699
GCP Alarm Descriptions 671 - 699
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# Text Description Action
671 ! Database: Failure: %3 1. Cannot find method;
2. Cannot find MaxBasic program;
3. Invalid stream for program;
4. Bad status on external result.
672 ! Database: Remote Service
lost on %3
673 ! Database:value > limit: %3 Limit exceeded. See Alarm Text.
674 ! Database value < limit: %3 Limit exceeded. See Alarm Text.
675 ! Database: No Stream at cy‐
cle start on applicaton %1
A connection for remote I/O or result
transmission has been closed. This
alarm is normal when the remote unit be‐
comes unavailable.
Cannot locate stream to start. Check sequence to make sure that the
Check methods and sequences.
Check program table.
Check program streamcontext.
Verify extresult table entries.
Check the status of the remote unit.
See the Limits and Alarm Handlers ta‐
bles under the GCP Application View.
See the Limits and Alarm Handlers ta‐
bles under the GCP Application View.
entries are enabled.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 41
Page 42
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
676 ! Database: delay limit ex‐
ceeded on stream %3
677 ? Next Stream Error Cannot locate next stream in sequence
678 ! End of Cycle occurred be‐
fore events completed
679 ! Application is out of service Attempt was made to move (approve) re‐
680 ? Print job failed: %3 for Print‐
er: %4
681 ! Application is disabled Attempt was made to set disabled appli‐
682 ! Database: I/O failure: %3 Bad status on AO, DO write. Check I/O channels.
683 ? Database: no normal se‐
quence for application: %3
684 ? Database: no enabled en‐
tries in sequence
685 ? Printer: TCP connection or
queue failed
686 ? Printer: TCP Print failed Communication failure with TCP printer. Try printing again.
687 ! Results for cycle %3 lost
due to SNE reset
688 ! Method is corrupt: %3 re‐
load from EZChrom
689 ! Database: Fault on Slave
Application %3
690 ! Database: Slave Applica‐
tion not Complete %3
691 ? Database: Warning: %3 System error Contact Customer Support.
692 ! Database: Divide by zero in %3Peak measured value is zero during cal‐
693 ? Database: I/O warning: %3 System error Contact Customer Support.
694 ? Database:value > limit: %3 Limit exceeded. Message should contain
695 ? Database value < limit: %3 Limit exceeded. Message should contain
696 ? DB: Screen access denied System error Contact Customer Support.
697 ! DB: Run requested on dis‐
abled program: %3
Temperature or pressure wait set in the
method has been exceeded.
after a stream step.
System error Contact Customer Support.
sults for an out-of-service application.
Print failure. Check printer.
cation to run.
No active sequence. Check sequences.
Cannot find enabled entry in sequence. Check sequence.
Printer connection failed. Check address in printer table.
This alarm marks results as uncertain un‐
til a cycle has been completed after re‐
setting unit.
Method is corrupt. Download method from EZChrom.
A fault is being transferred from the slave
to the master to invalidate the master's
results.
Master application is trying to run when
slave is not in hold. The slave must com‐
plete before the master.
ibration for an autocalibration, so marginchecking cannot occur.
sufficient information.
sufficient information.
System error Contact Customer Support.
Check temp or press controller.
Check wait_delta and maxwait in tem‐
perature or pressure controller table.
Check sequence to ensure that there is
an enabled stream.
Put application in service.
Enable application.
Automatic repair: No action necessary.
Check fault in slave application.
Check cycle length of slave application;
should be shorter than master. Also
could occur if autocalibration sequence
for master is shorter than for the slave.
Check method.
See the Limits and Alarm Handlers ta‐
bles under the GCP Application View.
See the Limits and Alarm Handlers ta‐
bles under the GCP Application View.
Maxum edition II Analyzer General Maintenance
42 Manual, August 2018, A5E42019842001
Page 43
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
698 ? NAU %3 not available for
communication
699 ? MODBUS: result is not in
address map %3
1. No analyzer reference in host table for
Maxum Modbus
2. Cannot open connection to remote an‐
alyzer for Maxum Modbus or remote I/O.
This is a sometimes-temporary error that
indicates a problem in the host table or a
network problem.
Cannot find address in map for result or
analyzerstatus that came from an ana‐
lyzer.
4.6.6 Alarms 700 - 737
GCP Alarm Descriptions 700 - 736
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
Check the cables at the sending and
receiving ends.
Check modbus_addmap for an incor‐
rect anlz attribute.
# Text Description Action
700 ? Network: Analyzer %3 not
available
701 ? MODBUS: scale factor or
euhi absent for %3
702 ? MODBUS: host command
for %3 invalid; undefined
database location
703 ? MODBUS: host command
for undefined address: %3
704 ? MODBUS: host cannot
write to this address: %3
705 ? MODBUS: mod‐
bus_msg_buffer cannot be
processed: %3
706 ? MODBUS: cannot locate
euhi %3
707 ? Calibration rejected: mar‐
gin exceeded for %3
708 ? MODBUS: Data type fail‐
ure for address: %3
709 ! DB: AI averaging %3 Averaging is occurring on an AI with no
710 ? DB: AI averaging %3 Averaging is occurring on an AI with no
Analyzer cannot be opened from NAU to
receive message from the DCS.
Scale factor or EUHI is absent for scaled
results.
A DCS command has been received for
an undefined address.
DCS message received that is for an un‐
known address.
The address written to by the DCS is not
defined with a value_type that the host
can send messages to.
1. Invalid DCS command was sent to an
Optichrom or
2. EUHI, calibrate, stream select, skip
stream, run/hold, doset set from host that
cannot be located in analyzer table.
Cannot find EUHI for result. Check EUHI address in modbus_add‐
Peak or group margins exceeded on auto
calibration.
Data_type mismatch with value_type. Check modbus_addmap. This is usu‐
result designated to receive the average.
result designated to receive the average.
Check network.
Reset SYSCON.
Check contents of modbus_addmap.
Check contents of modbus_addmap.
Check contents of modbus_addmap.
Check value_type of address in mod‐
bus_addmap.
1. Cannot clear alarms on optichrom or
2. Check analyzer table to see if entry
occurs or wait until analyzer broadcasts.
map_result table.
Check peak or group margins in EZ‐
Chrom.
ally self-correcting, but changes should
be checked.
Check configuration of AI averaging.
Check configuration of AI averaging.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 43
Page 44
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
711 + Database: %3 System error Contact Customer Support.
712 ! %6 Start Ver: %3 - %4 on %5SYSCON has been reset.
Informational message.
713 + System backed up System error Contact Customer Support.
714 + All alarms cleared System error Contact Customer Support.
715 + Database Build System error Contact Customer Support.
716 ? DB: Invalid Sourcekey or
SourceAttribute for Stat‐
Mon table: ID %3
717 ? DB: Calibration : margin
check/reports are invalid
for curve type
718 ? Validation failed for %3 Validation has failed. Check report or validation results
719 + Database: SNE reset re‐
quested
720 ? Database: Reprocess dur‐
ing Run not allowed
721 + Application is in service Informational message. No action is necessary.
722 ? Reference Component not
found; Component %3 ,
Reference %4
723 ! Database: Method ID %3
not found
724 ? Calibration or Validation
failed; application in hold
725 ? DB: Method %3 halted Application was halted from the HMI,
726 ! DB: Slave application
stream is invalid %3
727 ? DB: Master app autocali‐
bration completed before
Slave app %3
728 ? DB: application cannot au‐
tocalibrate
729 ! DB: message processing
timeout for message %3;
attempting recovery
730 ! DB: Unnamed peak pro‐
cessing exceeded (2000)
for channel %3
731 ! CAN initialization failure for
application %3
Occurs when StatMon table is not prop‐
erly configured.
Occurs when a margin is set in EZChrom
for a curve type that does not support
margin checking.
SNE is indicating that it has been reset
from a database request.
Reprocess button pushed while applica‐
tion in run.
Quantra alarm. Contact Customer Support
Method ID is in sequence, but not in
method table.
Calibration or validation was requested
while one was already running.
CIM display, or a MaxBasic program. In‐
formational message.
A stream ID in slave does not line up with
master application stream ID (new re‐
quirement for version 4.0).
Master autocalibration sequence is fin‐
ishing before slave autocalibration.
Autocalibration was requested on appli‐
cation that is not defined for autocalibra‐
tion.
System error Contact Customer Support.
Processing for unnamed peaks must not
exceed 2000 peaks for a channel. Ex‐
cess peaks were discarded.
Application does not start until CAN
cards required by the application are ini‐
tialized. The application starts regardless
of the error after 30 seconds.
No action necessary.
Consult documentation.
Remove margin or change curve type.
screen on the HMI or CIM Display.
May indicate a communication over‐
load.
Only push reprocess button when ap‐
plication is in hold.
Check method table.
Check timing of calibration or validation
events.
No action necessary.
Check master and slave sequences.
Check length of sequences. Master au‐
tocalibration sequence must finish after
slave autocalibration.
Check autocal attribute in application
table.
Increase the EZChrom threshold value
to reduce the number of peaks.
Verify that all application I/Os are prop‐
erly initialized. Remove any I/O that de‐
pends on a CAN card that is not present.
Maxum edition II Analyzer General Maintenance
44 Manual, August 2018, A5E42019842001
Page 45
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
732 ! IO: underflow or lower fail‐
safe condition detected for
%3
733 ! IO: overflow or upper fail‐
safe condition detected for
%3
734 ! %3 Process not communi‐
cating
735 ? IO: AO value was clamped
for %3 to %4
736 ? Untrusted Connection Re‐
fused from %3
737 ? System Time is Incorrect System Time is Incorrect Set Analyzer Time or set TimeServer IP
The firmware is reporting an under-range
error for analog NAMUR data types 6 or
8.
The firmware is reporting an under-range
error for analog NAMUR data types 7 or
8.
Occurs when ADHMaxumD or I2CDB
connection is not present.
Indicates clamping of AO value. Informa‐
tional message.
A connection was refused from an exter‐
nal client due to the trusted-connection
function.
Check the wiring for the secondary de‐
vice being used. Verify proper ranges
for the I/O.
Check the wiring for the secondary de‐
vice being used. Verify proper ranges
for the I/O.
Contact Customer Support.
No action necessary.
Trusted Connections are defined on the
HMI. Please contact your site's admin‐
istrator or Siemens Customer Service.
Address as described in “Regional Set‐
tings” Help in GCP.
4.6.7 Alarms 801 - 999
GCP Alarm Descriptions 801 - 999
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# Text Description Action
801 ? System Error %3 in File %4
line %5
802 ? Error %3 opening Flash
File %4
803 ? Error %3 closing Flash File System Error Reset the device. If the error persists,
804 ? Error %3 reading Flash File System Error Reset the device. If the error persists,
805 ? Error %3 writing Flash File System Error Reset the device. If the error persists,
System Error Contact Customer Support.
System Error Reset the device. If the error persists,
replace the Flash/SRAM module.
replace the Flash/SRAM module.
replace the Flash/SRAM module.
replace the Flash/SRAM module.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 45
Page 46
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
806 ? Memory Corruption Error
from Task %3
807 + Region 0 Memory Low: %3 The amount of free memory in the SY‐
808 + Excessive Network Com‐
munications
809 + System is excessively busy This is an overload situation, the process‐
810 ? Invalid dbdat file The db.dat file, containing the 'cold' da‐
811 + Excessive Maxum broad‐
casts were dropped
812 ? Network communication
overload
813 + SYSCON-SNE Comm De‐
bug: %3
814 ? Invalid CMOS time, check
the battery
An attempt to free a block of memory was
unsuccessful because the header was
overwritten. The block of memory was
not returned to the free pool.
SCON is low.
The internal network communication buf‐
fers (PNA buffers) are abnormally low.
This indicates that the network traffic to
the analyzer is abnormally high.
or cannot keep up with the requests.
tabase on a Compact flash system, is
missing or invalid. This may happen if
the system was reset or powered down
during a user initiated save to flash (initi‐
ated from the HMI, CIM display, or the
workstation).
Other analyzers on the network are gen‐
erating network broadcast messages at
an abnormal rate (greater than 200/min).
The excessive traffic is ignored. As a re‐
sult, the status of the analyzers in the an‐
alyzer table may not be up to date.
The internal network communication buf‐
fers (PNA buffers) are full; the system
may not function normally.
Debugging information, for internal use. No action necessary.
The built-in SYSCON clock has an inva‐
lid time.
1. Save a fresh copy of the database to
your Maxum Workstation.
2. Connect to the SYSCON Debug port
with hyperterminal or equivalent with
‘save to file’ turned on.
3. Type the login and password individ‐
ually when prompted (maxum, maxum)
4. Type each of the diagnostic com‐
mands one at a time from the following
list: ps, id, fr, st a, ck netstat, ifstatus,
uptime.
5. Send the debug file and the .amd file
to Customer Support.
Verify the amount of memory installed
in the SYSCON. Contact Customer
Support.
Investigate the cause of the high net‐
work traffic.
To reduce processor load:
● Reduce the size of the Modbus
table.
● Reduce the number and poll rate of
AIs and DIs.
● Reduce the number of concurrent
applications running.
● Reduce the communication burden
with Optichrom analyzers.
Perform a manual save to flash as soon
as possible in order to have a valid
db.dat file.
Investigate the network traffic. Contact
Customer Support for assistance.
Reset the device. Contact Customer
Support.
Check SYSCON clock battery and re‐
place if needed.
Maxum edition II Analyzer General Maintenance
46 Manual, August 2018, A5E42019842001
Page 47
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
997 + %3 General alarm used for information.
Used most often by MaxBasic programs.
998 ? %3 General warning alarm used for informa‐
tion. Used most often by MaxBasic pro‐
grams.
999 ! %3 General fault alarm used for information.
Used most often by MaxBasic programs.
4.6.8 Alarms 1002 - 1128
GCP Alarm Descriptions 1002 - 1128 SNE Common Module Errors
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
No action necessary.
Immediately report runtime errors to
Customer Support (please make care‐
ful note of the alarm message).
Immediately report runtime errors to
Customer Support (please make care‐
ful note of the alarm message).
# Text Description Action
1002 ! ID Key Not Connected on %4All PICs: The module location ID connec‐
tor is disconnected or set to 0. This is an
abnormal condition; the module may not
be operational.
1003 ! ID Key Change on %4 All PICs: The module location ID value
was changed while the module was op‐
erating. This is a transient error that cau‐
ses the module to automatically reset.
The module can then be addressed and
operated at the new location ID.
1004 ! EEPROM Bad Checksum
on %4
1005 ? Temp Diag Error on %4 All PICs: The on-board temperature sen‐
All PICs: A checksum error was detected
in the module EEPROM. The firmware
will still use all the information that it can
read from the EEPROM. However, the
module may not operate normally.
sor (LM-75) diagnostic failed. This alarm
indicates that the ability of the board to
detect a module overheat (alarm #1044)
may be compromised. This alarm is may
happen occasionally following a board
reset.
This alarm is in no way related to and
should not be confused with the Over‐
temp Shutdown related to heater temper‐
ature controls.
Verify that the location ID connector is
in good condition and connected prop‐
erly.
Verify that the location ID connector is
in good condition and connected prop‐
erly.
Check for intermittent connection.
Cycle power.
If the error repeats, replace the module.
No action is required unless the error
happens every time the board is reset.
For these repetitive errors replace the
module.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 47
Page 48
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
1007 ! Firmware Fault on %4 All PICs: A 'run-time' error was detected
in the PIC firmware. For example, a timer
is turned off at a point where the firmware
expects it to be on. The firmware will at‐
tempt to recover. Usually an additional
specific flag will be set to provide more
information about the cause of the fault.
1008 ! EEPROM Bad Value on %4 All PICs: A value read from EEPROM is
out of range or invalid. This may happen
if a board’s EEPROM was incorrectly in‐
itialized during manufacturing.
1009 ! Local I2C error on %4 All PICs: A fatal error was detected while
accessing the internal, on-board I2C bus
(not the private bus between a SNE and
a DPM). The communication with the onboard EEPROM or the LM75 (on board
temperature sensor) is not working nor‐
mally.
1010 ! Fatal error on %4 All PICs: An error or an invalid operation‐
al condition was detected by the PIC firm‐
ware. The board is shut down to a failsafe
mode.
1041 ? AO Out Of Range on %4 All PICs: An AO was set to a value out‐
side of the allowed range. The value was
clipped to the allowed range.
For example, an EPC has a 0 to 100 psi
nominal range for the pressure setpoint.
An attempt to set the setpoint to 150 psi
results in an "AO out of range" and the
setpoint is clipped to remain within the
allowed range (100 psi).
1042 ? Invalid Group Channel on %4All PICs: The hardware I/O channel(s)
requested does not exist on the module.
1043 ? Invalid EEPROM Address
on %4
All PICs: The on-board EEPROM ad‐
dresses requested do not exist or cannot
be accessed within a single command.
Contact Customer Support.
Cycle power.
If the error repeats, replace the module.
Cycle power.
If the error repeats, replace the module.
Contact Customer Support.
Locate the problematic AO and change
the AO value to a value within the prop‐
er range.
Check the 'Sys Hardware' table for in‐
valid entries.
Check that only detector channels are
specified in the detector I/O table.
Check that only EPC are defined in the
pressure controller table.
Check that only temperature controllers
are defined in the temperature control‐
ler table.
Report to Customer Support for further
investigation.
Maxum edition II Analyzer General Maintenance
48 Manual, August 2018, A5E42019842001
Page 49
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
1044 ? Board overheating on %4 All PICs: A module temperature greater
than the defined maximum operating
temperature (default 65°C) has been de‐
tected.Overheating must be corrected as
soon as possible to avoid permanent
damage to the analyzer electronics, in‐
cluding reduced module life expectancy
or other board failures.
Note: This alarm can occur together with
alarm 1005 (Temp Diag Error) in which
case the board may not actually be over‐
heating.
This alarm concerns the temperature in
the electronics enclosure. This alarm is
not related to the Overtemp Shutdown
related to heater temperature controls.
1045 ? Output Locked on %4 All PICs: The state of the DO or the value
of the AO are locked and cannot be
changed. The AO or DO command was
ignored. Some DO and AO are locked
during a board self-test.
1047 ? PIC firmware diagnostic 47
on %4
1048 ? PIC firmware diagnostic 48
on %4
1049 ? PIC firmware diagnostic 49
on %4
1050 ? PIC firmware diagnostic 50
on %4
1051 ? PIC firmware diagnostic 51
on %4
1052 ? PIC firmware diagnostic 52
on %4
1053 ? PIC firmware diagnostic 53
on %4
1054 ? PIC firmware diagnostic 54
on %4
1055 ? PIC firmware diagnostic 55
on %4
1056 ? PIC firmware diagnostic 56
on %4
1081 + Data Not Ready on %4 All PICs: The data requested is not avail‐
1082 + Reset Detect on %4 %5 All PICs: A reset was detected. Normal
1083 + Power Up on %4 %5 All PICs: A power-up cycle was detected.
System error Contact Customer Support.
System error Contact Customer Support.
System error Contact Customer Support.
System error Contact Customer Support.
System error Contact Customer Support.
System error Contact Customer Support.
System error Contact Customer Support.
System error Contact Customer Support.
System error Contact Customer Support.
System error Contact Customer Support.
able.
indication that the PIC was reset.
Normal indication that the PIC was pow‐
ered up.
If the overheating condition is real, de‐
termine and correct the cause of high
operating temperature.
Possible causes include ambient tem‐
perature higher than specification or an
inoperative fan in the electronics enclo‐
sure (restricted air flow inside the EC).
When performing a board self-test, sus‐
pend all other operations affecting the
board.
Contact Customer Support.
No action necessary.
No action necessary.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 49
Page 50
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
1084 + I2C Timeout on %4 All PICs: An I2C communication timeout
timer has expired. The timer is reset after
each successful character processed.
Only an addressed module may gener‐
ate a timeout. The timeout can occur on
incoming and outgoing characters.
1085 + I2C Read Past End on %4 All PICs: The I2C communication master
did not stop reading after the complete
response had been sent.
1086 + I2C Buffer Overflow on %4 All PICs: The combination of the transmit
and receive I2C message was too large,
causing a buffer overflow. (With kernel
revision 1: SSP_READ_UNEXPEC‐
TED_STOP, a stop condition occurred
before the end of the response).
1087 + I2C Write Past End on %4 All PICs: In an I2C message, more than
the number of bytes specified by the
length was written. The extra bytes are
ignored.
1088 + I2C Resync Error on %4 All PICs: Severe I2C error, causing the
current message to be dropped. Commu‐
nication will re-synchronize after the next
START or STOP condition. Usually as‐
sociated with alarm 1092.
1089 + I2C Write Unexpected Stop
on %4
1090 + I2C Write Unexpected
Start on %4
All PICs: A new I2C message was re‐
ceived in the middle of a write. The old
message was discarded and the new
message is served (this message may
be out of sequence and therefore cause
other flags to be set).[With kernel revi‐
sion 1: SSP_WRITE_UNEXPEC‐
TED_STOP, during a slave write a stop
condition occurred before the message
was completed. The message is ignor‐
ed.]
All PICs: A new I2C message was re‐
ceived in the middle of a read. The old
message was discarded and the new
message is served (this message may
be out of sequence and therefore cause
other flags to be set). [With kernel revi‐
sion 1: SSP_WRITE_UNEXPEC‐
TED_START, during a slave write a Start
or Repeat Start (RS) condition was de‐
tected before the entire message was re‐
ceived (according to the length field). The
message is ignored and processing re‐
sumes following the Start or Repeat
Start.]
Contact Customer Support.
Contact Customer Support.
Contact Customer Support.
Contact Customer Support.
Contact Customer Support.
Contact Customer Support.
Contact Customer Support.
Maxum edition II Analyzer General Maintenance
50 Manual, August 2018, A5E42019842001
Page 51
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
1091 + I2C Write Before Read on %4All PICs: An attempt was made to write
an I2C message before reading the re‐
sponse from a previous message. This
indicates that an attempt was made to do
a Slave Write - RepeatStart - Slave
Write combination.
1092 + I2C Read Unexpected on %4All PICs: An I2C read from the peripheral
was attempted before a slave write loa‐
ded a command.
1093 + I2C Invalid Checksum on %4All PICs: An I2C message with an invalid
checksum was received. The mes‐
sage was ignored.
1094 ! Data not available on %4 All PICs: Some data was lost and is no
longer available. For a detector channel
it means that a 'Detector Read' command
was received with an invalid index. This
can happen when a request to retransmit
detector data came too late when the da‐
ta was already gone from the buffer.
This situation may also happen while ac‐
cessing the I/O related to the LM75
(BOARD_TEMPERATURE and OVER‐
TEMP_SETPOINT). It indicates that the
local I2C bus was not available to per‐
form the desired action.
1095 + Invalid Message on %4 All PICs: An I2C message with a valid
checksum was not recognized or had an
invalid op-code.
1096 + Diagnostic mode enabled
on %4
1121 ! Firmware Math error on %4 All PICs: An unexpected math operation
1122 ! Firmware Mem error on %4 All PICs: A jump or a call was made to an
1123 ! Firmware Table error on %4All PICs: An error was detected when ad‐
Informational message. No action Necessary.
error was detected by the PIC. It can be
an un-handled overflow, underflow, etc.
This flag is always associated with a
FIRMWARE_FAULT flag.
invalid PIC memory location causing the
PIC to be reset. This flag is always as‐
sociated with a FIRMWARE_FAULT flag.
dressing an internal PIC firmware table.
The index in the table is likely to be inva‐
lid. This flag is always associated with a
FIRMWARE_FAULT flag.
Contact Customer Support.
Contact Customer Support.
Contact Customer Support.
Cycle power.
If the error repeats, replace the module
or the SNECON.
Cycle power.
If the error repeats, replace the module
or the SNECON.
Cycle power.
If the error repeats, replace the module.
Cycle power.
If the error repeats, replace the module.
Cycle power.
If the error repeats, replace the module.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 51
Page 52
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
1124 ! Firmware Watchdog on %4 All PICs: The PIC watch dog timer has
expired causing a module reset. This flag
is always associated with a FIRM‐
WARE_FAULT flag. It can be an indica‐
tion that the I2C clock or data line was
held low for more than the timeout dura‐
tion (nominally 30 ms). It can also indi‐
cate that the PIC oscillator is not working
normally.
1125 ! Firmware System Monitor
on %4
1126 ! Firmware Application on %4All PICs: A general PIC firmware error
1127 ! Firmware Stack Overflow
on %4
1128 ! Firmware Unknown Reset
on %4
All PICs: The background system moni‐
toring task has discovered a problem
causing the PIC to be reset. It can be that
the interrupt or timer were disabled when
they should have been enabled, or some
similar error. This flag is always asso‐
ciated with a FIRMWARE_FAULT flag.
was encountered causing a board reset.
An abnormal condition was detected in
the firmware of a specified module.
An abnormal condition was detected in
the firmware of a specified module.
Cycle power.
If the error repeats, replace the module.
Cycle power.
If the error repeats, replace the module.
Cycle power.
If the error repeats, replace the module.
Reset the device. If the condition per‐
sists, replace the affected module.
Reset the device. If the condition per‐
sists, replace the affected module.
4.6.9 Alarms 1317 - 1319
GCP Alarm Descriptions 1317 - 1319
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# ! Text Description Action
1317! Valve Switch Error on %4SVCM PIC: The SVCM firmware
1318! J10 Disconnected on %4SVCM PIC: The SVCM J10 con‐
1319! J11 Disconnected on %4SVCM PIC: The SVCM J11 con‐
Replace the module.
has detected an invalid condition
in the circuit driving the solenoid
valves. One or more valves is
likely to be malfunctioning.
Check the J10 connection.
nector is not properly connected
and the corresponding bank of
solenoids may not work.
Check the J11 connection.
nector is not properly connected
and the corresponding bank of
solenoids may not work.
Maxum edition II Analyzer General Maintenance
52 Manual, August 2018, A5E42019842001
Page 53
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
4.6.10 Alarms 1617 - 1697 Pecm Errors
GCP Alarm Descriptions 1617 - 1697 PECM Errors
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# Text Description Action
1617
- 1624
1625,
1626
1627 ! ABH Ctrl Plug Missing on %4PECM PIC: The air bath heater control
1628 ! ABH Air Plug Missing on %4PECM PIC: The air-bath heater air-sen‐
1629 ! Purge Indicator not availa‐
1630 ! The low wattage relay
! [LWH1; LWH2; LWH3;
LWH4; LWH5a; LWH5b;
LWH6a; LWH6b] Output
Fault on %4
! ABH [1 - 2] Output Fault on %4PECM PIC: On-board diagnostic indicat‐
ble on %4
board is missing
PECM PIC: On-board diagnostic indicat‐
ing that a LWH is not working correctly.
This diagnostic is active only when a
SSR output is configured for PECM selfcontrol, when the loop-back connector is
present. The diagnostic is not active
when the control is from a temperature
controller. If this happens when the out‐
put is controlled by a temperature con‐
troller, it indicates a defective harness
between the DPM and the PECM. (The
PLUG_DETECT pin (#5) is not grounded
and the output is turned on).
ing that an ABH is not working correctly.
This diagnostic is active only when a
SSR output is configured for PECM selfcontrol, when the loop-back connector is
present. The diagnostic is not active
when the control is from a temperature
controller. If this happens when the out‐
put is controlled by a temperature con‐
troller, it indicates a defective harness
between the DPM and the PECM. (The
PLUG_DETECT pin (#5) is not grounded
and the output is turned on).
cable is missing in J9 and at least one of
the air-bath heaters is non-disabled. If
the cable is missing, the NO_AIR_ABH_x
flag will also be set on the non-disabled
air-bath heater channels.
sor connector is missing and at least one
of the air bath heaters is non-disabled.
PECM PIC: Neither the SYSCON nor the
HMI level 1 LED panel is connected. It
indicates that there is no purge indicator
connected, the PECM has nowhere to
report the purge information.
PECM PIC: The low wattage relay board
is not connected properly to the PECM
electronics.
If associated with an 'Invalid configura‐
tion alarm' (1659), then check the J con‐
nector on the PECM associated with
the specified LWH.
Otherwise, replace the PECM or the ca‐
ble between the DPM and PECM.
If associated with an 'Invalid configura‐
tion alarm' (1659), then check the J con‐
nector on the PECM associated with
the specificed ABH.
Otherwise, replace the PECM or the ca‐
ble between the DPM and PECM.
If the air bath heater is not used, then
disconnect J91 and J92 on PECM in or‐
der to eliminate the alarm.
Otherwise check J9.
Check J10 on PECM.
Check J1302 and J101 on PECM. Ver‐
ify the cable connected into J1302.
Confirm that the relay board is connec‐
ted properly.
Replace the relay board and/or the
PECM electronics.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 53
Page 54
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
1633
- 1638
1657
- 1658
1659 ? Invalid Configuration on %4 PECM PIC: An attempt was made to con‐
1665
- 1670
1697 ? Purge Loss on %4 PECM PIC: Purge failure in the EC en‐
! Output error on solenoid
valve, [left location, left
group; left location, right
group; right location, left
group; right location, right
group; upper location, left
group; upper location, right
group]
? ABH[1 - 2] No Air on %4 PECM PIC: The air bath heater #n is
? Solenoid valve disconnec‐
ted, [left location, left
group; left location, right
group; right location, left
group; right location, right
group; upper location, left
group; upper location, right
group]
PECM PIC: The solenoid output status
read-back value is incorrect for at least
one valve in the group. This can happen
when a solenoid cable is disconnected,
even momentarily. Note that the readback check can only be accomplished
when the state of the output to a solenoid
is OFF (no verification can be done on an
output when it is ON).
turned off, as the air pressure is too low
for a safe operation of the heater. This
flag is set only if the corresponding air
bath heater is in use. The PECM con‐
siders the air bath heater in use if a loop‐
back connector or a cable from a temper‐
ature controller is connected.
trol a heater output with a DO command
while the corresponding loopback is not
installed.
This alarm can be generated as a result
of either of the following:
1. The cable to the corresponding valve
group was disconnected since the last
time the PECM board was reset. As a
result, all valves in that group may not
work properly.
2 A digital output was invoked to a dis‐
connected valve group. The output can‐
not be controlled.
closure. The pressure differential be‐
tween the interior and exterior of the EC
is not high enough. Depending on the
environment classification where the an‐
alyzer is installed, this alarm may indi‐
cate an unsafe condition that requires
immediate action to correct.Check sup‐
ply-air pressure.
Verify the cable connections.
Replace the solenoid group cable.
Replace the solenoid group.
Replace the PECM board.
If the channel is not in use, disconnect
the loopback connector or temperature
controller cable.
Check the air pressure on the corre‐
sponding air bath heater. Make sure
that it is 10 psi or above.
Electrically disconnect the pressure
switch:
1. Verify that it operates normally by
measuring the contact resistance with
a multimeter at 0 and 10 psi.
2. Verify with a multimeter that there is
no continuity to ground.
Verify the harness with a multimeter.
Replace the PECM.
Install or verify the corresponding
PECM loopback plug.
Verify that the solenoid valve cable is
properly seated in the connector and
reset the device.
Verify the configuration of the DOs in all
applications to ensure that no DO is ref‐
erencing a valve in a non-connected
group.
Verify that door is closed.
Check for damaged door gaskets.
Verify that all cables and tubes entering
the EC are sealed properly.
Maxum edition II Analyzer General Maintenance
54 Manual, August 2018, A5E42019842001
Page 55
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
4.6.11 Alarms 1917 - 2005 DPM TCD
GCP Alarm Descriptions 1917 - 1999 DPM Errors
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# Text Description Action
1917 ! Balance Hardware Failure
TCD L %5 on %4
1918 ! Balance Hardware Failure
TCD U %5 on %4
1919,
1920
1921 ! PIC Timeout on %4 System error Contact Customer Support.
1922 ! Incompatible Hardware on %4TCD DPM Detector PIC: The PIC firm‐
1925 ? Glow Plug bad FID DPM Detector PIC: The glow plug is
1926 ! Invalid PIC index DPM Detector PIC: The PIC index is not
1927 ! Mezzanine module discon‐
1928 ! Mezzanine-module ID
! A/D Failure TCD [L; U] %5
on %4
nected
changed
System error Contact Customer Support.
System error Contact Customer Support.
TCD DPM Detector PIC: Set when the
corresponding Analog to Digital Convert‐
er hardware does not work properly. The
flag will be set if the A/D internal calibra‐
tion cycle is not completed within a predetermined period of time or the A/D
does not report any valid data within a
pre-defined timeout period.
Note: A firmware problem affecting the
version 1.000 of the TCD detector PIC
may cause an A/D failure flag to show-up
occasionally following a PIC reset. This
is not a sign of a defective A/D converter.
ware is not compatible with the DPM
board.
not working correctly. The diagnostic is
performed when the board is reset or
when an attempt is made to light the
flame. The hardware diagnostic verifies
that a minimum current and voltage is
present, checking for a short and open
glow plug. This may also indicate that a
spark igniter that is not connected prop‐
erly.
valid, the DPM board is not working nor‐
mally.
FID DPM Detector PIC: The mezzaninemodule ID value is 0 or 15 indicating that
no module is present or is malfunctioning.
FID DPM Detector PIC: The mezzaninemodule ID value has changed since the
last time the board was reset. Indicates
a bad contact or a bad component.
Cycle power. If the error repeats con‐
sistently, replace the module.
Replace the module.
Confirm that the glow plug or spark ig‐
niter cable is securely inserted in the
corresponding connector. Replace the
glow plug. Replace the DPM.
Replace the module.
Verify that the mezzanine module is
properly connected.
Replace the module on the DPM.
Replace the DPM.
Verify that the mezzanine module is
properly connected.
Replace the module on the DPM.
Replace the DPM.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 55
Page 56
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
1929 ! Mezzanine-module ID inva‐
lid
1930 ! Mezzanine-module ID re‐
served
1957,
1958
1959,
1960
1961,
1962
! Balance Failure TCD [L; U]
%5 on %4
? Balance Out Of Limit TCD
[L; U] %5 on %4
! The ADC missed a sample
on channel [1 - 2] on %4
FID DPM Detector PIC: The mezzaninemodule ID value is not supported by this
DPM board. More specifically, the
module value is pointing to a non-initial‐
ized EEPROM region on the DPM.
This may indicate an invalid mezzanine
module or an older revision of the DPM
that was manufactured before the mez‐
zanine module was defined.
FID DPM Detector PIC: The mezzaninemodule ID value is set to a value re‐
served for future expansion.
TCD DPM Detector PIC: For Rev 1
TCD DPM: A detector balance sequence
failed because of a hardware failure, an
improper configuration, or sequence of
events. Some possible causes include:
The detector beads are too unbalanced
to be 'balance-able'. The detector signal
is not stable enough and proper balance
could not be obtained before the maxi‐
mum number of iterations was reached.
The A/D or D/A do not work properly. The
detector is not configured for acquisition
or turned off. SIMULATE_TCD_x is set
to ‘1’ (the detector cannot be balanced in
detector simulation mode).The balance
is disabled (DISABLE_BAL‐
ANCE_TCD_x is set to ‘1’). The sampling
period was changed during the balance
sequence.
TCD DPM Detector PIC: For Rev 1 TCD
DPM: A detector balance value is
above the normal limits. The balance
may still work as this is an early warning.
A transient error was detected by the An‐
alog-to-Digital Converter of the DPM,
channel #n. The missing or invalid data
point was replaced by a point with a value
of zero.
Verify the DPM revision level and re‐
place as needed.
Replace the mezzanine module on the
DPM.
Verify the DPM revision level and re‐
place as needed.
Replace the mezzanine module on the
DPM.
Contact Customer Support.
If associated with a balance failure
(alarm 1957), then the source of the
balance failure must be corrected.
If not associated with a balance failure
and the balance limits are normal
(greater than 9 Volts or 90%) then
schedule maintenance to replace the
detector beads.
If using Rev 2 TCD DPM or FID DPM,
contact Customer Support.
Reset the DPM. If the error repeats, re‐
place the DPM.
Maxum edition II Analyzer General Maintenance
56 Manual, August 2018, A5E42019842001
Page 57
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
1965 ? Flame ignition failure TCD DPM Detector PIC: The FID flame
could not be lit within the predefined de‐
lay (25 or 60 sec). No other attempt will
be made to automatically light the flame
until the MANUAL IGNITION DO is acti‐
vated.
1966 ? Gain override TCD DPM Detector PIC: An external sig‐
nal is applied to the DPM, overriding the
DPM gain control. This is a normal situa‐
tion if a signal is connected to the exter‐
nal gain-select connector.
1967 ? Gain select not supported TCD DPM Detector PIC: An attempt was
made to change the gain on a configura‐
tion that does not support the dual gain
feature. The request was ignored.
1968 ? Igniter type changed TCD DPM Detector PIC: The spark ignit‐
er was connected or disconnected during
an ignition sequence, causing the igni‐
tion sequence to be aborted.
1997,
1998
2005 ! Firmware error Firmware error Contact Customer Support.
2006 ! Bias off FID DPM Detector PIC: The detector is
! Buffer Overflow TCD [L; U]
%5 on %4
DPM Detector PIC: The PIC detector da‐
ta buffer filled up before an I2C command
was received to retrieve the data.
Some data was lost. The SNECON was
not fast enough to retrieve the points or
the SNECON stopped polling without
turning off the corresponding detector
channel. This may happen with a combi‐
nation of a very high speed detector with
a large burst of I/O commands.
used while the 300 Volts bias is disabled.
The data validity is unknown.
If associated with an alarm 2225 (Glow
plug failure), then diagnose and fix this
other alarm first. If a BASIC program is
used to control the electronic pressure
controller (EPC) to adjust the gas mix‐
ture for proper ignition, confirm that the
poll rate of the 'IGNITE' DI is set to 2
sec. Check that the gas supply pres‐
sure is adequate. Verify the proper op‐
eration of the EPC.
If no external signal is connected, re‐
place the DPM.
Remove access to the GAIN_ALT_SE‐
LECT DO.
Verify that the igniter is properly con‐
nected. Replace the igniter. Replace
the DPM.
Stagger the balance events and valve
switching events by approximately
10-20 ms to distribute the load on the
I2C bus.
Disconnect the SNECON debug cable
(if connected) and reset.
Reload the SNECON OS and APP soft‐
ware.
Set the 'disable bias' DO to ‘0’.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 57
Page 58
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
4.6.12 Alarms 2217 - 2306 DPM FID
GCP Alarm Descriptions 2217 - 2306 DPM Errors
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# Text Description Action
2217 ! Balance Hardware Failure
FID L %5 on %4
2218 ! Balance Hardware Failure
FID U %5 on %4
2219,
2220
2221 ! PIC Timeout on %4 System error Contact Customer Support.
2222 ! Incompatible Hardware on %4The firmware has detected an invalid
2225 ? Glow Plug Bad on %4 FID DPM Detector PIC: The glow plug is
2226 ! Invalid PIC index DPM Detector PIC: The PIC index is not
2227 ! Mezzanine module discon‐
2228 ! Mezzanine-module ID
! A/D Failure [FID; TCD] %5
on %4
nected
changed
System error Contact Customer Support.
System error Contact Customer Support.
DPM Detector PIC: Set when the corre‐
sponding Analog to Digital Converter
hardware does not work properly. The
flag will be set if the A/D internal calibra‐
tion cycle is not completed within a predetermined period of time or the A/D
does not report any valid data within a
pre-defined timeout period.
condition indicating that the hardware is
not compatible with the firmware.
not working correctly. The diagnostic
is performed when the board is reset or
when an attempt is made to ignite the
flame. The hardware diagnostic veri‐
fies that a minimum current and voltage
is present, checking for a short and open
glow plug. This may also indicate that a
spark igniter is not connected properly.
valid; the DPM board is not working nor‐
mally.
FID DPM Detector PIC: The mezzaninemodule ID value is 0 or 15 indicating that
no module is present or is malfunctioning.
FID DPM Detector PIC: The mezzaninemodule ID value has changed since the
last time the board was reset. Indicates
a bad contact or a bad component.
Cycle power. If the error repeats con‐
sistently, replace the module.
Replace the module.
Confirm that the glow plug or spark ig‐
niter cable is securely inserted in the
connector.
Replace the glow plug.
Replace the DPM.
Replace the module.
Verify that the mezzanine module is
properly connected.
Replace the module on the DPM.
Replace the DPM.
Verify that the mezzanine module is
properly connected.
Replace the module on the DPM.
Replace the DPM.
Maxum edition II Analyzer General Maintenance
58 Manual, August 2018, A5E42019842001
Page 59
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
2229 ! Mezzanine-module ID inva‐
lid
2230 ! Mezzanine-module ID re‐
served
2257 ! Balance Failure FID on %4 FID DPM Detector PIC: A detector bal‐
FID DPM Detector PIC: The mezzaninemodule ID value is not supported by this
DPM board. More specifically, the mod‐
ule value is pointing to a non-initialized
EEPROM region on the DPM. This may
indicate an invalid mezzanine module or
an older revision of the DPM that was
manufactured before the mezzanine
module was defined.
FID DPM Detector PIC: The mezzaninemodule ID value is set to a value re‐
served for future expansion.
ance sequence failed because of a hard‐
ware failure or because of an improper
configuration or sequence of events.
Some possible causes are:
The detector signal is not stable enough
and proper balance could not be ob‐
tained before the maximum number of
iterations was reached.
The A/D or D/A do not work properly.
The detector is not configured for acquis‐
ition or turned off.
SIMULATE_FID is set to 1 (the balance
cannot be done in detector simulation
mode).
The balance is disabled (DISABLE_BAL‐
ANCE_FID is set to 1).
The sampling period was changed dur‐
ing the balance sequence.
Verify the DPM revision level and re‐
place as needed.
Replace the mezzanine module on the
DPM.
Verify the DPM revision level and re‐
place as needed.
Replace the mezzanine module on the
DPM.
Contact Customer Support.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 59
Page 60
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
2258 ! Balance Failure TCD %5
on %4
2259 ? Balance Out Of Limit FID
on %4
2260 ? Balance Out Of Limit TCD
%5 on %4
2261,
2622
2265 ? Flame Ignition Failure on %4FID DPM Detector PIC: The FID flame
! The ADC missed a sample
on channel [1 - 2] on %4
FID DPM Detector PIC: A detector bal‐
ance sequence failed because of a hard‐
ware failure or because of an improper
configuration or sequence of events.
Some possible causes are:
The detector beads are too mismatched
to be balance corrected.
The detector signal is not stable enough
and proper balance could not be ob‐
tained before the maximum number of
iterations was reached.
The A/D or D/A do not work properly.
The detector is not configured for acquis‐
ition or turned off.
SIMULATE_TCD is set to ‘1’ (the bal‐
ance cannot be done in detector simula‐
tion mode).
The balance is disabled (DISABLE_BAL‐
ANCE_TCD is set to ‘1’).
The sampling period was changed dur‐
ing the balance sequence.
FID DPM Detector PIC: A detector bal‐
ance value is above the normal limits.
The balance may still work as this is an
early warning.
TCD DPM Detector PIC: A detector bal‐
ance value is above the normal limits.
The balance may still work as this is an
early warning.
A transient error was detected by the An‐
alog-to-Digital Converter of the DPM,
channel #n. The missing or invalid data
point was replaced by a point with a value
of zero.
could not be ignited within the predefined
delay (25 or 60 sec). No other attempt
will be made to automatically ignite the
flame until the MANUAL IGNITION DO
is activated.
Contact Customer Support.
If associated with a balance failure
(alarm 2257), then the source of the
balance failure must be corrected.
If not associated with a balance failure
and the balance limits are normal
(greater than 9 Volts or 90%), schedule
maintenance to clean or replace the
FID detector.
If associated with a balance failure
(alarm 2258), then the source of the
balance failure must be corrected. If not
associated with a balance failure and
the balance limits are normal (greater
than 9 Volts or 90%) then maintenance
should be scheduled to replace the de‐
tector beads.
Reset the DPM. If the error repeats, re‐
place the DPM.
If associated with an alarm 2225 (Glow
plug failure), then diagnose and fix that
alarm first. If a BASIC program is used
to control the electronic pressure con‐
troller (EPC) to adjust the gas mixture
for proper ignition, confirm that the poll
rate of the 'IGNITE' DI is set to 2 sec.
Verify adequate gas-supply pressure.
Verify the proper operation of the EPC.
Maxum edition II Analyzer General Maintenance
60 Manual, August 2018, A5E42019842001
Page 61
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
2266 ? Gain override FID DPM Detector PIC: An external sig‐
nal is applied to the DPM, overriding the
DPM gain control. This is a normal situa‐
tion if a signal is connected to the exter‐
nal gain-select connector.
2267 ? Gain select not supported FID DPM Detector PIC: An attempt was
made to change the gain on a configura‐
tion that does not support the dual gain
feature. The request was ignored.
2268 ? Igniter type changed FID DPM Detector PIC: The spark igniter
was connected or disconnected during
an ignition sequence, causing the igni‐
tion sequence to be aborted.
2297,
2298
2299 ! Detector Disabled on %4 FID DPM Detector PIC: An attempt was
2305 ! Flame Out on %4 FID DPM Detector PIC: The flame is out;
2306 ! FID Bias off on %4 FID DPM Detector PIC: The detector is
! Buffer Overflow [FID; TCD]
on %4
FID DPM Detector PIC: The PIC detector
data buffer filled up before an I2C com‐
mand was received to retrieve the data.
Some data was lost. The SNECON
was not fast enough to retrieve the points
or the SNECON stopped polling without
turning off the corresponding detector
channel. This may happen with a combi‐
nation of a very high speed detector with
a large burst of I/O commands.
made to read detector information from
a disabled detector.
the data generated on the FID channel is
invalid.
used while the 300 Volts bias is disabled.
The data validity is unknown.
If no external signal is connected, re‐
place the DPM.
Remove access to the GAIN_ALT_SE‐
LECT DO.
Verify that the igniter is properly con‐
nected.
Replace the igniter.
Replace the DPM.
Stagger the balance events and valve
switching events by approximately
10-20 ms to distribute the load on the
I2C bus.
Disconnect the SNECON debug cable
(if connected) and reset.
Reload SNECON OS and APP soft‐
ware.
Cycle power. If the error repeats re‐
place the module.
Verify adequate flame gas supply.
Verify the operation of any associated
EPC.
Set the 'disable bias' DO to ‘0’.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 61
Page 62
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
4.6.13 Alarms 2500 - 2577 Access Bus Driver Errors
GCP Alarm Descriptions 2500 - 2577 Access Bus Driver Errors
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# Text Description Action
2500 ? I2C Premature Stop on %4 SNECON I2C driver: A stop condition
was detected in the middle of a transfer
(SNECON hardware revision 2.x).
2501 ? I2C No Acknowledge (Mod‐
ule Disconnected?) on %4
2502 ? I2C NS486 Timeout Over‐
flow on %4
2503 ? I2C Address is Odd on %4 SNECON I2C driver: Illegal I2C address. Reset the analyzer. Reload SNE‐
2505 ? I2C Driver Not Initialized SNECON I2C driver: An attempt was
2508 ? I2C Improper Acknowl‐
edge on %4
2509 ? I2C Invalid Message
Checksum Received on %4
2510 ? I2C Module Not Found: %4 SNECON I2C driver: No module of this
2511 ? I2C Invalid Opcode Re‐
ceived from %4
2512 ? I2C Error Reading ISR
Queue
2513 ? I2C Message Too Big on %4SNECON I2C driver: The I2C message
2515 ! I2C Address Table Full SNECON I2C driver: No free addresses
SNECON I2C driver: No module re‐
sponding to the I2C address. A module
was disconnected or is no longer re‐
sponding. This can also happen if the
PIC-index is erroneously set to 0 as this
is a way to bypass the I2C address reso‐
lution table and directly address the I2C
bus.
SNECON I2C driver: An I2C commu‐
nication timeout condition was detected
(SNECON hardware revision 2.x).
made to communicate to the I2C driver
before it was initialized.
SNECON I2C driver: No module re‐
sponding to the I2C address. A module
was disconnected or is no longer re‐
sponding (SNECON hardware revision
2.x).
SNECON I2C driver: A message was re‐
ceived with an invalid checksum.
'module type' and 'location id' is listed in
the address table.
SNECON I2C driver: The message re‐
ceived corresponds to an unrecognized
opcode.
SNECON I2C driver: An error was detec‐
ted reading a communication queue
(SNECON hardware revision 2.x).
received is too large and is not valid.
on the I2C bus. There is a limit of 120
addresses per bus (each PIC occupies
one address).
Contact Customer Support.
Reset the analyzer.
Contact Customer Support.
CON OS software.
Reset the analyzer.
Reload SNECON OS and APP soft‐
ware.
Contact Customer Support.
(SNECON hardware revision 2.x): Ver‐
ify that the application does not use a
hardware address that does not exist.
Reset the analyzer.
Verify that the application does not use
a hardware address that does not exist.
Reset the analyzer.
Reload SNECON OS and APP soft‐
ware. Replace the SNECON.
Reset the analyzer.
Contact Customer Support.
Reset the analyzer.
Maxum edition II Analyzer General Maintenance
62 Manual, August 2018, A5E42019842001
Page 63
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
2516 ? I2C Invalid Bus on %4 SNECON I2C driver: Invalid I2C bus
identification number.
2518 ? I2C Unknown Address Re‐
ceived on %4
2519 ? I2C Invalid Data Type on %4SNECON I2C driver: SNECON firmware
2520 ? I2C Invalid Number of I/O
Channels on %4
2521 ? I2C Bus Conflict; Lost Arbi‐
tration on %4
2522 ? I2C Using a Free Message
Buffer on %4
2523 ? I2C NS486SXF-C0 Patch
Timeout on %4
2525 ? I2C Invalid Driver Control
Command on %4
2526 ? I2C Capability Information
Too Big on %4
2527 ? I2C Message Lost in a Con‐
troller Reset: %4
2529 ? I2C Invalid Capability Ver‐
sion; Incompatible Firm‐
ware on %4
2530 ? I2C Internal Error; Invalid
Daemon Function on %4
2531 ? I2C Internal Error; Invalid
Info on %4
2532 ? I2C Invalid Device ID Ver‐
sion; Incompatible Firm‐
ware on %4
2534 ? I2C Internal Error; Bus
Manager Invalid Command
on %4
2537 ? I2C Address Table not ini‐
tialized on %4
2538 ? I2C ISR Lockup SNECON I2C driver: The SNECON
2539 ? I2C Invalid Message Sta‐
tus Size on %4
SNECON I2C driver: SNECON firmware
internal error.
internal error.
SNECON I2C driver: SNECON firmware
internal error.
SNECON I2C driver: An I2C communica‐
tion error was detected (SNECON hard‐
ware revision 2.x).
SNECON I2C driver: SNECON firmware
internal error.
SNECON I2C driver: SNECON firmware
internal error.
SNECON I2C driver: SNECON firmware
internal error.
SNECON I2C driver: SNECON firmware
internal error.
SNECON I2C driver: A pending I2C mes‐
sage could not be sent and was lost as a
result of a reset of the I2C interface. The
cause of the reset is usually a recurring
communication error.
SNECON I2C driver: An I2C module has
provided an invalid device capability in‐
formation message. The associated
'Sys_Hardware' table may be invalid.
System error Contact Customer Support.
SNECON I2C driver: SNECON firm‐
ware internal error.
SNECON I2C driver: An I2C module has
provided an invalid device ID information
message. The module type and loca‐
tion ID information may be invalid.
System error Contact Customer Support.
SNECON I2C driver: SNECON firmware
internal error.
message receive indicator is stuck
(SNECON revision 3.0 hardware only).
SNECON I2C driver: SNECON firmware
internal error.
Reset the analyzer.
Reset the analyzer.
Reset the analyzer.
Reset the analyzer.
Confirm that only one SNECON is
present on the bus; a revision 2 SNE‐
CON cannot share the I2C bus.
Reset the analyzer.
Reset the analyzer.
Replace the SNECON.
Reset the analyzer
Reload the SNECON OS and APP soft‐
ware.
Replace the SNECON.
Reset the analyzer.
Contact Customer Support.
Replace the module
Reload newer SNECON OS and APP
software.
Reset the analyzer.
Replace the module.
Reload SNECON OS and APP soft‐
ware.
Reset the analyzer.
Reset the analyzer.
Replace the SNECON.
Reset the analyzer.
Replace the SNECON.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 63
Page 64
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
2540 ? I2C Message Too Short on %4SNECON I2C driver: An I2C message
received by the SNECON is too short to
be valid.
2541 + I2C FPGA Queue Full on %4SNECON I2C driver: SNECON firmware
internal error (SNECON revision 3.0
hardware only).
2542 ? I2C FPGA Write Before
End on %4
2543 ? I2C FPGA Write After End
on %4
2544 ? I2C FPGA Message Too
Short on %4
2545 ? I2C FPGA Invalid Check‐
sum on %4
2546 ? I2C FPGA Invalid Size on %4SNECON I2C driver: SNECON firmware
2547 ! I2C Heartbeat Timeout Ex‐
pired; Resetting Controller
2549 ? I2C Heartbeat Counter Mis‐
match on %4
2550 ? I2C Invalid Message Sta‐
tus on %4
2551 ? I2C Internal Error; Invalid
Block Structure ID on %4
2552 ? I2C Internal Error; Invalid
Block Offset on %4
2553 ? I2C Internal Error; Invalid
Block ID on %4
2554 ? I2C Internal Error; New
Block Offset Non-Zero on
%4
SNECON I2C driver: SNECON firmware
internal error (SNECON revision 3.0
hardware only).
SNECON I2C driver: SNECON firmware
internal error (SNECON revision 3.0
hardware only).
SNECON I2C driver: SNECON firmware
internal error (SNECON revision 3.0
hardware only).
SNECON I2C driver: SNECON on-board
communication error. Known to hap‐
pen very infrequently with SNECON I2C
FPGA rev 23 or lower (SNECON revision
3.0 hardware only).
internal error (SNECON revision 3.0
hardware only).
SNECON I2C driver: A SNECON PIC
was not responding and was reset (SNE‐
CON revision 3.0 hardware only).
SNECON I2C driver: One or more mes‐
sages were lost on the on-board commu‐
nication (SNECON rev 3.0 hardware on‐
ly).
SNECON I2C driver: SNECON firmware
internal error (SNECON revision 3.0
hardware only).
SNECON I2C driver: SNECON firmware
internal error (SNECON revision 3.0
hardware only).
SNECON I2C driver: SNECON firmware
internal error (SNECON revision 3.0
hardware only).
SNECON I2C driver: SNECON firmware
internal error (SNECON revision 3.0
hardware only).
SNECON I2C driver: SNECON firmware
internal error (SNECON revision 3.0
hardware only).
Contact Customer Support.
Reset the analyzer.
Replace the SNECON.
Reset the analyzer.
Replace the SNECON.
Reset the analyzer.
Replace the SNECON.
Reset the analyzer.
Replace the SNECON.
Ignore the alarm. If occurring frequent‐
ly, replace the SNECON.
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
Maxum edition II Analyzer General Maintenance
64 Manual, August 2018, A5E42019842001
Page 65
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
2555 ? I2C Internal Error; Block
Table full
2556 ? I2C Not Enough Memory SNECON I2C driver: SNECON firmware
2557 ? I2C Internal Error; Block
Too Large on %4
2558 ? I2C Internal Error; Block
Not Found on %4
2559 ? I2C Internal Error; Invalid
Block Size on %4
2560 ! I2C Driver OS and Applica‐
tion version mismatch
2562 ? I2C Internal Error; Bad
state on %4
2563 ! I2C FPGA bad version SNECON I2C driver: The SNECON I2C
2564 ! I2C Temperature Block
Version Invalid
2565 ? I2C Opcode not expected
in current state on %4
2566 ! I2C Modules were reset fol‐
lowing multiple errors
2567 ! I2C Header Index Mis‐
match; Message Lost
2568 ? I2C Internal Error; Invalid
Block Index on %4
2569 ? I2C FPGA Queue Full on %4SNECON I2C driver: The SNECON I2C
2570 ? I2C FPGA Packet Too Big
on %4
SNECON I2C driver: SNECON firmware
internal error (SNECON revision 3.0
hardware only).
internal error.
SNECON I2C driver: SNECON firmware
internal error (SNECON revision 3.0
hardware only).
SNECON I2C driver: SNECON firmware
internal error (SNECON revision 3.0
hardware only).
SNECON I2C driver: SNECON firmware
internal error (SNECON revision 3.0
hardware only).
SNECON I2C driver: The version num‐
ber of the SNECON OS is incompatible
with the SNECON APP version.
SNECON I2C driver: SNECON firmware
internal error.
FPGA is incompatible or broken.
SNECON I2C driver: The temperature
controller PID parameter data block sup‐
plied by the SYSCON is incompatible.
SNECON I2C driver: Unexpected I2C
message opcode received by the SNE‐
CON from a module.I2C communication
error.
SNECON I2C driver: A fatal error or mul‐
tiple consecutive retries have forced the
I2C controller to reset.
System error Contact Customer Support.
SNECON I2C driver: SNECON firmware
internal error (SNECON revision 3.0
hardware only).
FPGA queue is full, the PIC is no longer
processing I2C messages.
SNECON I2C driver: SNECON firmware
internal error (SNECON revision 3.0
hardware only).
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
Reload the SNECON OS with the new‐
est version.
Replace the SNECON.
Reload the SNECON OS and APP soft‐
ware to the corresponding SYSCON
version.
Contact Customer Support.
Contact Customer Support.
Reset the analyzer.
Reload the SNECON OS software.
Reset the analyzer.
Reload the SNECON OS software.
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 65
Page 66
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
2571 ? I2C FPGA Recovery Failed
on %4
2572 ? I2C FPGA Read in pro‐
gress not set after header
on %4
2573 ? I2C Not enough memory in
ISR on %4
2574 ! I2C PIC Reset Detected on %4SNECON I2C driver: A problem was de‐
2575 ? I2C General AO error on %4SNECON I2C driver: A channel specific
2576 ? I2C General DO error on %4SNECON I2C driver: A channel specific
2577 ? I2C bus configuration
changed
SNECON I2C driver: SNECON firmware
internal error (SNECON revision 3.0
hardware only).
SNECON I2C driver: SNECON firmware
internal error (SNECON revision 3.0
hardware only).
SNECON I2C driver: SNECON firmware
internal error (SNECON revision 3.0
hardware only).
tected by a SNECON PIC and it went
through a reset. Can also be caused by
an I2C communication error.
error was detected while an AO com‐
mand was processed (Example AO out
of range) . A more specific alarm will be
reported by the module on the next poll.
error was detected while an DO com‐
mand was processed (Example DO out
of range) . A more specific alarm will be
reported by the module on the next poll.
The configuration between internal I2C
(5V I2C) and external, SSSI (10V I2C)
was changed. The configuration change
is ignored until the next reset.
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
Reset the analyzer.
Reload the SNECON OS software.
Replace the SNECON.
If occurring frequently, replace the SNE‐
CON.
Provides the channel information for an
alarm reported on the same module.
Provides the channel information for an
alarm reported on the same module.
If the configuration was changed inten‐
tionally, simply reset the device. Other‐
wise, verify that the cable in J3 and J13
on SNECON V4 or J1 and J3 on the SIB
are properly inserted.
Maxum edition II Analyzer General Maintenance
66 Manual, August 2018, A5E42019842001
Page 67
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
4.6.14 Alarms 2817 - 2904 DPM Temperature
GCP Alarm Descriptions 2817 - 2904 - DPM Temperature
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# ! Text Description Action
2817 ! 12V Error on %4 Temperature controller PIC: The 12 volt
supply is not working normally.
2818 ! Setpoint Board Missing on %4Temperature controller PIC: The OTS
and temperature limit configuration
board (t-rating configurator) is not detec‐
ted on J10. The temperature controller
is non-functional.
2819,
2820
2823,
2824
2825 ! A/D Failure on %4 Temperature controller PIC: An Analog
2899,
2900
! RTD Failure [1 - 2] on %4 Temperature controller PIC: An attempt
was made use a temperature channel
that has an invalid RTD signal. The RTD
is shorted or open circuit. The tempera‐
ture controller cannot function.
! SSR Cable [1 - 2] Missing
on %4
! Over Temp Shutdown [1 -
2] on %4
System error Contact Customer Support.
to Digital Converter chip does not work
properly. The flag will be set if the A/D
internal calibration cycle is not completed
within a pre-determined period of time or
the A/D does not report any valid data
within a pre-defined timeout period.
Note: A firmware problem affecting the
version 1.002 of the Temperature con‐
troller PIC may cause an A/D failure flag
to show-up occasionally following a PIC
reset. This is not a sign of a defective
A/D converter.
Temperature controller PIC: The OverTemp Shutdown function is active on
channel #1. The heater cannot be turned
on. The overtemp shutdown condition in‐
dicates that the temperature reached the
absolute limit..
Disconnect the RTDs and feedthrough
connector. If the error does not go
away, replace the DPM.
If the error goes away, confirm that
there is no continuity between any RTD
lead and ground.
Install or replace the TLIM-OTS T-rat‐
ing configuration board.
Verify the 4-wire temperature sense
RTD on channel #1. The RTD resist‐
ance must be between 81 and 269
ohms. Confirm that none of the leads
have any continuity with ground.
Cycle power.
If the error repeats consistently, replace
the module.
Check for:
A disconnected TLIM-OTS configura‐
tion board.
A temperature setpoint too high for the
allowed T-rating.
A defective OTS or T-limit temperature
probe.
A defective DPM
A defective (shorted) SSR.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 67
Page 68
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# ! Text Description Action
2901,
2902
2903,
2904
? Deviation [1 - 2] Exceeded
on %4
? Ramp has no origin [1 - 2]
on %4
Temperature controller PIC: The meas‐
ured temperature deviation (TEMP_DE‐
VIATION) has exceeded the correspond‐
ing MAX_DEVIATION value. The PID
control was not successful to control the
heater with the desired precision on
channel #1. A large deviation is normal
on power-up and immediately following
a change in the temperature setpoint.
Temperature controller PIC: A ramp rate
was set without a prior temperature set‐
point on channel #1. A ramp must have
an initial temperature defined by the pre‐
vious setpoint value.
Check for:
Improper controller type 'temptype' se‐
lected in the 'App_tempctl' table.
The PID parameters are not optimal.
Fast variation in the ambient tempera‐
ture, airflow or line voltage.Insufficient
air flow. For an air bath heater with 1/8
inch spargers, 3 cfm is adequate for up
to 100 DegC and then 4 cfm should be
used.
A temperature setpoint too high for the
allowed T-rating.
An Air pressure switch that works inter‐
mittently.
A defective DPM.
A defective PECM.
A defective Solid State relay.
Set the power-up default ramp value to
0.
Maxum edition II Analyzer General Maintenance
68 Manual, August 2018, A5E42019842001
Page 69
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
4.6.15 Alarms 3117 - 3204 EPC
GCP Alarm Descriptions 3117 - 3204 EPC
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# Text Description Action
3117,
3118
3119,
3120
3157,
3158
3159,
3160
3161,
3162
! Pressure [1 - 2] Out-Of-
Control on %4
! A/D [1 - 2] Failure on %4 EPC (Electronic Pressure Controller)
? Low Supply Pressure [1 - 2]
on %4
! Deviation [1 - 2] Exceeded
on %4
? Setpoint [1 - 2] changed fol‐
lowing a change in Max
Pressure
EPC (Electronic Pressure Controller)
PIC: The measured pressure, on chan‐
nel #n, has exceeded the absolute maxi‐
mum allowed pressure and the corre‐
sponding channel was shutdown. The
pressure controller is no longer working.
PIC: The Analog to Digital Converter chip
does not work properly. The flag will be
set if the A/D internal calibration cycle is
not completed within a pre-determined
period of time or the A/D does not report
any valid data within a pre-defined time‐
out period.
Note: A firmware problem affecting the
version 0.250 of the EPC PIC may cause
an A/D failure flag to show-up occasion‐
ally following a PIC reset. This is not a
sign of a defective A/D converter.
EPC (Electronic Pressure Controller)
PIC: Set when the contact on the optional
supply pressure sensor on [J5 or J6] is
closed indicating that the supply pres‐
sure is getting low and that the bottle
must be changed soon.
EPC (Electronic Pressure Controller)
PIC: The measured pressure deviation
has exceeded the corresponding
MAX_DEVIATION value. The PID con‐
trol was not successful in controlling the
pressure with the desired precision on
channel #n.
EPC (Electronic Pressure Controller)
PIC: The SETPOINT_[n] AO value was
modified internally as a result of the SET‐
POINT_MAX_[n] AO value set to a value
lower than the SETPOINT_[n] value.
Confirm that the flow is greater than the
minimum specification. Replace the
EPC.
Cycle power. If the error repeats con‐
sistently, replace the module.
Check air supply. Replace supply bottle.
MAX_DEVIATION_x that is too small.
An improper setting of TIME_LIM‐
IT_DEVIATION_UP_x or TIME_LIM‐
IT_DEVIATION_DN_x.
Insufficient supply pressure.
Flow too small or too large.
Defective EPC.
Set the SETPOINT_MAX_[n] value first
and then set the setpoint.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 69
Page 70
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
3163,
3164
3203,
3204
! EPC Shutdown on %4,
Channel [1 - 2]
! EPC ramp has no origin on
%4, Channel [1 - 2]
The [n] channel of the Electronic Pres‐
sure Control (EPC) was temporarily shut
down. This happens when the EPC
control valve is fully opened for more
than 5s and is meant to prevent over‐
heating of the valve. This situation typ‐
ically happens when the input pressure
is too low, as from an empty cylinder.
The starting point of the pressure ramp
was set to the current measured pres‐
sure as the setpoint value was not previ‐
ously set. When no prior setpoint is
available, this alarm is issued and the
current measured pressure is used as a
substitute for setpoint #1.
4.6.16 Alarms 3401 - 3454 TFTP
No action required. The shutdown is
temporary and the operation will auto‐
matically resume after 15s.
Set a static setpoint first, and then set
the ramp rate, followed by a new set‐
point. With this sequence, the starting
point of the ramp will be setpoint #1 and
the ending point will be setpoint #2.
GCP Alarm Descriptions 3401 - 3454 TFTP
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# Text Description Action
3401 ? TFTP Protocol Error Protocol error detected, such as receipt
of a non-DATA packet or lack of an ex‐
pected message acknowledgment. Most
likely the gateway settings on the SNE
are wrong.
3402 ? TFTP Timeout The TFTP client didn't receive a re‐
sponse from the server.
3403 ? TFTP Server out of Sync The data packets requested by the TFTP
client to not match those sent by the
TFTP server. Either the TFTP client or
TFTP server is not working properly.
3404 ? TFTP Server out of Sockets TFTP server cannot create a portal from
which to communicate. SNE or host com‐
puter is low on resources.
3405 ? TFTP Max Channels ex‐
ceeded
3406 ? TFTP Driver Not Initialized TFTP driver was not successfully initial‐
3450 ? TFTP Client Out of Memory Client ran out of memory loading file. Verify that the SNE has 16Mb SIMM.
Too many TFTP load requests have
been commanded.
ized. Usually a problem of resource.
Power up the SNE connected to a serial
terminal and change the settings in the
startup dialog.
Verify that the TFTP server is running
on the host computer, and that the host
computer is connected to the SNE
through the network.
Reset the SNE.
Restart the TFTP server on the host
computer.
Wait for problem to clear.
Contact Customer Support.
Only request one TFTP load at a time.
Verify that the SNE has sufficient mem‐
ory.
Upgrade SNE.
Reset SNE.
Reset SNE.
Maxum edition II Analyzer General Maintenance
70 Manual, August 2018, A5E42019842001
Page 71
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
3451 ? TFTP Client Checksum Er‐
ror
3452 ? TFTP Client Missing End of
File
3453 ? TFTP Client Invalid OS File Attempt to load OS with invalid address
3454 ? TFTP Client Invalid App
File
File loaded had invalid checksum. Verify that loadfile is correct and uncor‐
Attempt to load truncated file. Verify that loadfile is correct and uncor‐
range.
Attempt to load App with invalid address
range. Loadfile may be OS file or corrupt.
4.6.17 Alarms 3500 - 3528 Advance
GCP Alarm Descriptions 3500 - 3528 Advance
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
rupted.
rupted.
Verify that loadfile is correct and uncor‐
rupted.
Verify that loadfile is correct and uncor‐
rupted.
# Text Description Action
3500 ? Reserved System error Contact Customer Support.
3501 ! Advance Adapter Initializa‐
tion Failure
3502 ? Invalid Channel for Ad‐
vance Adapter %4
3503 ? Advance Adapter Back‐
plane Timeout on %4
3504 ? Advance Adapter Back‐
plane Error on %4
3505 ? Resource for %4 not avail‐
able on Advance Adapter
3516 ! No Advance Adapter detec‐
ted
3517 ! Advance Adapter Driver
Out of Memory
3518 ! Invalid Advance Adapter
Driver Command
Advance Adapter detected, but respond‐
ing improperly.
Reference to invalid channel on Advance
Adapter.
The referenced I/O on backplane board
did not respond.
The referenced I/O on backplane respon‐
ded improperly.
Memory or operating system object not
available for hardware access.
System error Contact Customer Support.
Driver initialization failure due to lack of
memory.
Application requested invalid command
from Adapter Driver. Most likely a mis‐
match between the SNECON OS and
application.
Repair or replace adapter.
Check reference to I/O channels in ap‐
plication tables.
Reseat or replace board corresponding
to hardware ID.
Reseat or replace board corresponding
to hardware ID.
Verify that SNE has sufficient memory.
Upgrade SNE.
Reset SNE.
Verify that SNE has sufficient memory.
Upgrade SNE. Reset SNE.
Reload SNECON software.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 71
Page 72
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
4.6.18 Alarms 3718 - 3804 SNE I/O
GCP Alarm Descriptions 3718 - 3804 SNE I/O
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# Text Description Action
3718 ! FPGA Error Full on %4 SNECON PICs: The FPGA queue to the
NS486 was full and a packet could not
be sent. A best attempt is made to con‐
tinue but one or more packets were lost.
3719 ? FPGA error reset_W on %4 SNECON PICs: A FPGA reset was de‐
tected during a packet write from the PIC.
The packet and any packet still in the
FPGA queues were lost.
3720 ? FPGA error reset_R on %4 SNECON PICs: A FPGA reset was de‐
tected during a packet read by the PIC.
The packet and any packet still in the
FPGA queues were lost.
3721 ? FPGA error_W on %4 SNECON PICs: An error was detected
while writing the packet header or data
to the FPGA. A best attempt is made to
continue but one or more packets may
be lost.
3722 ? FPGA error_R on %4 SNECON PICs: An error was detected
when reading the packet header or data
from the FPGA. A best attempt is made
to continue but one or more packets may
be lost.
3725 ! Error SCL on %4 SNECON PICs: An abnormal situation
was detected on the I2C 'Serial Clock'
line. This is an indication that the WDB is
broken, a cable harness is broken or one
board connected to the I2C bus is mal‐
functioning, pulling the I2C data signal to
a logical low.
3726 ! Error SDA on %4 SNECON PICs: An abnormal situation
was detected on the I2C 'Serial Data'
line. This is an indication that the WDB is
broken, a cable harness is broken or one
board connected to the I2C bus is mal‐
functioning, pulling the I2C data signal to
a logical low.
3727 ! I2C will not align on %4 SNECON PICs: I2C communication er‐
ror.
3728 ? I2C msg not allowed on %4 SNECON PICs: A packet containing an
I2C message was received by the PIC
(from the NS486 through the FPGA) at a
time when it is not allowed but after a val‐
id configuration message was received.
The message was discarded.
Reset the SNECON.
Replace the SNECON.
Reset the SNECON.
Replace the SNECON.
Reset the SNECON.
Replace the SNECON.
Reset the SNECON.
Replace the SNECON.
Reset the SNECON.
Replace the SNECON.
Contact Customer Support.
Contact Customer Support.
Contact Customer Support.
Reset the SNECON.
Reload the OS for the SNECON.
Replace the SNECON.
Maxum edition II Analyzer General Maintenance
72 Manual, August 2018, A5E42019842001
Page 73
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
3757 ? NACK address on %4 SNECON PICs: An I2C message trans‐
action failed after the required number of
retries. A cause of this failure was a
unacknowledged destination address
byte (first byte in the message). This
may happen if a module was disconnec‐
ted from the bus after its address has
been reassigned.
3758 ? NACK Byte on %4 SNECON PICs: An I2C message trans‐
action failed after the required number of
retries. A cause of this failure was a un‐
acknowledged byte that is not the first
byte in the message (any byte other than
the destination address was not acknowl‐
edged). This may happen if a module is
seriously corrupted or the I2C signal in‐
tegrity is a problem (noise, etc…).
3759 ? NACK Message on %4 SNECON PICs: An I2C message trans‐
action failed after the required number of
retries. A cause of this failure was a
NACK message with a non-zero flag.
This may happen if the firmware of the
peripheral module is not responding
properly.Reset the analyzer.
3760 ? Invalid Checksum on %4 SNECON PICs: An I2C message trans‐
action failed after the required number of
retries. A cause of this failure was an
invalid checksum in the reply message.
This may happen if the firmware of the
peripheral module is not working proper‐
ly or the electrical properties of the I2C
signals are marginal.
3761 ? Invalid Opcode on %4 SNECON PICs: An invalid private op‐
code was received from the NS486. The
message was ignored. This may happen
if the PIC firmware is out-of-date relative
to the SNE software.
3762 ? Invalid Message on %4 SNECON PICs: An I2C message trans‐
action failed after the required number of
retries. A cause of this failure was a reply
message that had a valid checksum and
valid opcode but was invalid in any other
way. This may happen if the firmware of
the peripheral module is not working
properly or the SNECON software is too
old.
3763 ! Arbitration Loss on %4 SNECON PICs: An I2C message trans‐
action failed after the required number of
retries and a cause of this failure was that
the PIC could not successfully arbitrate
its way to the bus. Other bus-master de‐
vices are using all the I2C bus bandwidth.
Reset the analyzer.
Contact Customer Support.
Replace the module being addressed.
Contact Customer Support.
Reload the OS and APP software for
the SNECON.
Replace the SNECON.
Reload the OS and APP software for
the SNECON. Replace the module be‐
ing addressed. Replace the SNECON.
Contact Customer Support.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 73
Page 74
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
3764 ? Timeout SCL on %4 SNECON PICs: An I2C message trans‐
action failed because the I2C clock was
stretched beyond the allowed timeout pe‐
riod specified in the configuration. A mod‐
ule may be malfunctioning.
3765 ? Timeout SDA on %4 SNECON PICs: An I2C message trans‐
action failed because the I2C data line
was held beyond the allowed timeout pe‐
riod specified in the configuration. A mod‐
ule may be malfunctioning.
3766 ? Bus Not Sync on %4 SNECON PICs: The master-mode oper‐
ation generated a start condition that was
not detected by the FPGA.
3767 ? Timeout Buffer on %4 SNECON PICs: A master-mode mes‐
sage has not been processed within a
timeout period. This is a broad alarm with
multiple possible causes. The PIC will
discard the message and attempt to re‐
cover.
3768 ? Invalid Handle on %4 SNECON PICs: The received header
handle was not sequential. One or more
I2C messages were lost.
3769 ? High I2C traffic on %4 The amount of traffic on the I2C bus has
exceeded a configurable threshold. A
heavy traffic may delay the I/O activity
which ultimately can affect the operation
(accuracy, repeatability) of the analyzer.
3797 + Invalid Checksum Slave on %4SNECON PICs: An unsolicited I2C mes‐
sage was received with a bad checksum.
The message was discarded and it is ex‐
pected that the master will retry the mes‐
sage. This is a communication error that
can be ignored if not frequent.
3798 + Invalid Message Slave on %4SNECON PICs: An unsolicited I2C mes‐
sage was received with an invalid mes‐
sage size, invalid opcode or invalid data.
The message was discarded. There may
be a firmware version conflict.
3799 ? Invalid Status Summary on %4SNECON PICs: A packet was received
by the PIC from the NS486 and the pack‐
et had an undefined bit set in the Sta‐
tus_summary field of the packet. The
packet was processed normally.
3800 ? Module Not Ready on %4 SNECON PICs: An I2C message trans‐
action failed after the required number of
retries and the cause of the failure was a
series of consecutive message NACKs,
all with a 0 flag. This may happen if the
firmware of the peripheral module is not
responding properly.
Contact Customer Support.
Contact Customer Support.
Reset the SNECON. Replace the SNE‐
CON.
Contact Customer Support.
Reset the SNECON.
Replace the SNECON.
Check the methods to ensure that the I/
O activity is distributed in time and not
all at the same exact cycle time (Detec‐
tor balance event, valve events, tem‐
perature and pressure setpoint, etc).
Reset the SNECON.
Replace the SNECON.
Reload the OS and APP software to all
SNECONs.
Reload the OS and APP software for
the SNECON.
Replace the SNECON.
Reload the OS and APP software for
the SNECON.
Replace the module being addressed.
Replace the SNECON.
Maxum edition II Analyzer General Maintenance
74 Manual, August 2018, A5E42019842001
Page 75
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
3801 ? Invalid Status Data on %4 SNECON PICs: The content of the status
buffer, 'Status_data', was invalid and not
recognized by the PIC. This may happen
if the PIC firmware is out of date relative
to the NS486 software.
3802 ? Invalid Status Type on %4 SNECON PICs: The value of the sta‐
tus_type was invalid and not recognized
by the PIC. This may happen if the PIC
firmware is out of date relative to the
NS486 software.
3803 + Invalid Msg Size on %4 SNECON PICs: A packet was received
with an invalid I2C message size or no
I2C message at all. The packet was dis‐
carded.
3804 + Arbitration Loss Slave on %4SNECON PICs: The PIC lost a slave
read arbitration. It indicates that at least
one other module responded to the same
message request.
Reload the OS and APP software for
the SNECON.
Replace the SNECON.
Reload the OS and APP software for
the SNECON.
Replace the SNECON.
Reload the OS and APP software to all
SNECONs.
If sporadic, no action is necessary.
If repeating frequently, reset the ana‐
lyzer.
4.6.19 Alarms 4001 - 4124 EZChrom
GCP Alarm Descriptions 4001 - 4124 EZChrom
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# Text Description Action
4001 ? TFTP cannot load with ac‐
tive method %3
4003 ! Zero Correction Out of Lim‐
its on %4
4022 ? I/O channel not found on %4Hardware resource requested not
4024 ? Slope check failure on
channel %4
4025 ? Detector channel under‐
flow occurred on %4
4026 ? Detector channel open oc‐
curred on %4
4027 ? Detector channel overflow
occurred on %4
Method currently running when software
load was commanded.
System error. Contact Customer Support.
present.
Slope check commanded with invalid pa‐
rameters.
A/D converter for detector reading lowest
possible value. This error may also be a
secondary error caused by an overflow
on an FID DPM.
Open connection detected on A/D detec‐
tor input. This error may also be a secon‐
dary error caused by an overflow on an
FID DPM.
A/D converter for detector reading maxi‐
mum value possible.
Put method on hold and wait for it to
complete before loading SNE software.
Reload and or repair SYSCON data‐
base.
Check method for slope check events
and review data.
Check A/D inputs, potentially replace
referenced DPM.
Verify proper operation of the DPM.
Check A/D inputs, potentially replace
referenced DPM.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 75
Page 76
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
4028 ? Detector channel unknown
error occurred on %4
4029,
4030
4031 ! Flame out on %4 Flame out detected on an Advance+ FID
4032 ? Purge Loss on %4 Loss of purge pressure has been detec‐
4033 ! Zero Correction Out of Lim‐
4120 ? Pulse DO Within a Pulse
4121 + Pulse DO Aborted on %4 A pulse DO was aborted as a result of a
4122 ! Method Conflict: Concur‐
4123 ! Unsupported detector sam‐
4124 ! Run-time Operational Con‐
? Zero Correction failure on
[first/lower/right; second/
lower/left] channel of %4
its on %4
DO is Not Allowed on %4
rent Chromatogram Chan‐
nel Acquisition on %4
pling rate on %4
flict on %4
Undeterminable error occurred on detec‐
tor channel circuit. This error may also be
a secondary error caused by an overflow
on an FID DPM.
Should occur only with a revision 2 TCD
DPM or revision 3 baseboard (PIC firm‐
ware revision 2.006 and up ). Or, the zero
correction value exceeded the maximum
allowed value for that particular board.
This is a balance failure situation.
or FPD Board.
ted. Possible causes include low pres‐
sure for supply air, open door, and failed
gaskets. Depending on the environment
classification where the analyzer is instal‐
led, this alarm may indicate an unsafe
condition that requires immediate action
to correct.
The value of the zero correction (soft‐
ware balance of the detector) has excee‐
ded the balance limits.
A pulse DO was requested by the SY‐
SCON while a pulse DO was already in
progress. The latest requested pulse
DO was ignored.
standard (non-pulsed) DO command.
The non-pulsed DO command has
precedence.
It is not allowed to use the same detector
channel for more than one chromato‐
gram acquisition at a time, whether within
a method or across methods. The new‐
est request was cancelled.
A request was made to run the specified
detector channel at a standard rate but
the DPM hardware does not support that
rate. The method file is likely corrupt. It
may be necessary to rebuild the method.
An operation was requested at a time
when it is not allowed. e.g.: GainSelect
VDO: A gain select was initiated before
the previous GainSelect sequence was
completed.
Reset. If error repeats, replace DPM.
Eliminate the cause of the balance fail‐
ure:
On TCD detector, replace the detector
bead or filament.
On FID detector, clean or replace the
FID.
Ignite flame on unit. If flame is burning,
board may be defective.
Investigate and correct cause of pres‐
sure loss.
Confirm that the corresponding balance
limit values are not too small. See the
maintenance instructions for the specif‐
ic detector type.
Wait until the on-going pulse has com‐
pleted before requesting another pulse
DO.
Informational message. No action nec‐
essary.
Verify that the method does not contain
2 concurrent uses of the same detector
channel hardware. Verify that the meth‐
ods running in separate applications
are not erroneously reusing the same
detector channels.
Contact Customer Support for assis‐
tance.
Revise the method to remove the con‐
flicting events.
Maxum edition II Analyzer General Maintenance
76 Manual, August 2018, A5E42019842001
Page 77
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
4.6.20 Alarms 4217 - 4320 CAN Bridge
GCP Alarm Descriptions 4217 - 4320 CAN Bridge
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# Text Description Action
4217 ! CAN:Underflow %4 System error Contact Customer Support.
4218 ! CAN: Overflow %4 System error Contact Customer Support.
4220 ! CAN: External AO uncali‐
brated
4257 ? CAN: Underflow System error Contact Customer Support.
4258 ? CAN: Overflow System error Contact Customer Support.
4259 ? CAN: Node init failure Indicates that at least one CAN node
4260 ? CAN: Node failure Indicates that at least one CAN node
4261 ? CAN: Bus HW init failure Indicates a failure of the CAN bus detec‐
4262 ? CAN: Bus HW Failure Indicates a fatal failure of the CAN bus
4263 ? CAN: Invalid channel %4 A read or a write was attempted to a
4264 ? CAN: Node changed Indicates that at least one serial number
The EEPROM does not contain valid fac‐
tory calibration information for a local AO
channel. Default calibration values are
used. The module is operational.
failed during the initialization process. No
I/O operations are allowed on the node.
failed during normal operation. This flag
is generated only if the node worked
properly during initialization but failed at
a later time. No further I/O operations
are allowed on the node. The communi‐
cation with the card will be stopped and
the card will set itself to failsafe output.
ted during the CAN bus initialization.
No communication is possible with any
node. This can be as a result of either:
a) No CAN card is present, but yet at
least one card is defined in the database
b) The CAN hardware cannot communi‐
cate with a CAN device as a result of a
hardware error (e.g. broken or shorted
cable) and the PIC CAN module is re‐
porting a transmitter error.
detected during the normal operation.
This flag is generated only if the CAN
system worked properly during initializa‐
tion but failed at a later time. No commu‐
nication is possible with any node.
channel that does not exist.
has changed and that, as a result, the
CAN bridge PIC will soon reset. This is
normal as a result of a CAN node list
configuration change.
Replace the SIB to eliminate the alarm.
Reset the device.
If the problem persists, replace the CAN
card.
Reset the device.
If the problem persists, replace the CAN
card.
Check the Database CAN node list for
a stray card.
Check data cable and power to CAN
Extension Unit (CEU).
Check power to CAN Extension Unit
(CEU).
Verify the hardware ID of the I/O for val‐
id addresses.
No action necessary.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 77
Page 78
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
4265 ? CAN: Receive Init Buffer
Overflow
4266 ? CAN: Receive Heartbeat
Buffer Overflow
4267 ? CAN: Receive I/O Buffer
Overflow
4268 ? CAN: Transmit Buffer Over‐
flow
4269 ? CAN: Channel not respond‐
ing
4270 ? CAN: Hardware FIFO
Overflow
4297 + CAN: init complete The initialization of the CAN card has
The CAN bus receive buffer that process‐
es messages from uninitialized CAN
cards has overflowed. Initialization will
likely fail.
CAN card heartbeat replies have over‐
flowed the heartbeat buffer. The heart‐
beat buffer is large enough to hold replies
from all 20 cards. Overflow would indi‐
cate a serious loading problem.
CAN card I/O replies/updates are not
processing fast enough. This indicates
that some received CAN messages have
been lost because the CAN bridge can‐
not process them fast enough. Since
CAN messages take longer to transmit
on the CAN bus than it takes to process
them this flag is unlikely to occur. If it ever
occurs, the likely cause is very heavy I2C
traffic combined with a large number of
ADIO boards which add considerable
CAN traffic to the bus.
There are too many pending CAN mes‐
sages and the transmit buffer is full. This
indicates that the SYSCON is performing
I/O operations faster than they can be
transmitted on the CAN bus. The most
likely cause would be heavy DO traffic
since the I2C protocol can update many
DO bits per transaction but it takes one
CAN message for EACH DO bit.
Indicates that one or more channels have
not properly communicated and recovery
efforts have failed. For outputs, this flag
is set after several retries writing to a
channel without proper confirmation from
the CAN card that the message was re‐
ceived and handled. For inputs, this flag
is set after enough time passes without
getting an update from the channel.
The PICs hardware CAN message buffer
has overflowed.
completed. Informational message.
Contact Customer Support.
Contact Customer Support.
Reset the device. If the problem per‐
sists, the I2C traffic to the CAN bridge
or the number of ADIO boards in the
system must be reduced.
Contact Customer Support.
Reset the device. If the problem per‐
sists, replace the CAN card.
Contact Customer Support.
No action necessary.
Maxum edition II Analyzer General Maintenance
78 Manual, August 2018, A5E42019842001
Page 79
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
4300 + CAN: Unrecognized card This flag is set when an uninitialized card
is detected on the bus after the init se‐
quence is complete. The most com‐
mon cause of this condition is a Node/SN
list that does not precisely match the card
mix on the bus either due to missing en‐
tries or typographical errors.
4301
- 4320
+ CAN: Node [1 - 20] abnor‐
mal
CAN card I/O malfunction that causes in‐
itialization failure, loss of heartbeat re‐
sponses from a CAN card or loss of com‐
munication with one or more channels of
the node.
4.6.21 Alarms 4525 - 5220 Advance TC
GCP Alarm Descriptions 4525 - 5220 Advance TC
Verify the node list in the database for
an exact match of all serial numbers.
Make sure that no unused CAN card is
present in the system.
If this is associated with a 'CAN: Node
x abnormal' error, replace the corre‐
sponding card.
Verify the node list in the database for
an exact match of all serial numbers.
If this is associated with a 'CAN: Node
x abnormal' error, replace the corre‐
sponding card.
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# Text Description Action
4525 ! AD Failure on %4 Advance Adapter Temperature Control‐
ler PIC: The Advance Adapter tempera‐
ture A/D converter is not generating data
points within the prescribed time interval.
4526 ! Over Temp Shutdown Pow‐
er Supply Failure on %4
4557 ? Setpoint Changed follow‐
ing a change of Max Temp
%4
4599 ! Over Temp Shutdown on %4Advance Adapter Temperature Control‐
Advance Adapter Temperature Control‐
ler PIC: The power supply used for over‐
temp shutdown is not working properly.
Advance Adapter Temperature Control‐
ler PIC: The SETPOINT AO value was
modified internally as a result of the SET‐
POINT_MAX AO value set to a value low‐
er than the SETPOINT value.
ler PIC: The Over-Temp Shutdown func‐
tion is active, the heater cannot be turned
on. The overtemp shutdown condition in‐
dicates that the temperature reached the
absolute limit.
Reset the analyzer.
Replace the Advance Adapter.
Replace the Advance Adapter.
Set the SETPOINT_MAX value first,
then set the setpoint value.
Check for:
A temperature setpoint too high for the
allowed T-rating.
A defective temperature probe.
A defective Advance Adapter.
A defective (shorted) SSR.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 79
Page 80
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text Description Action
4601 ? Temperature Deviation Ex‐
ceeded on %4
4817 ! AI Underflow Fault on %4 One or more AIs on the module has en‐
4818 ! AI Overflow Fault on %4 One or more AIs on the module has en‐
4819 ! External ADC HW is not re‐
sponding on %4
4820 ! External AO is not calibra‐
ted on %4
4821 ! External AI is not calibrated
on %4
4857 ? External AI underflow on %4One or more AIs on the module has en‐
4858 ? External AI overflow on %4 One or more AIs on the module has en‐
5117
- 5140
5157
- 5199
5200
- 5220
! Alarm [5117 - 5140] on %4 A fault alarm was generated on an un‐
? Warning [5157 - 5199] on %4A warning alarm was generated on an
+ Note [5200 - 5220] on %4 A note alarm was generated on an un‐
Advance Adapter Temperature Control‐
ler PIC: The measured temperature de‐
viation (TEMP_DEVIATION) has excee‐
ded the corresponding MAX_DEVIA‐
TION value. The PID control did not suc‐
cessfully control the heater with the de‐
sired precision. A large deviation is nor‐
mal on power-up and immediately follow‐
ing a change in the temperature setpoint.
Only small deviations are expected dur‐
ing normal operation.
countered a voltage or current underflow
situation.
countered a voltage or current underflow
situation.
Timeout or communication error with an
Analog to Digital Converter.
One or more AO channel has an invalid
calibration record in the EEPROM of the
module.
One or more AI channel has an invalid
calibration record in the EEPROM of the
module.
countered a voltage or current underflow
situation.
countered a voltage or current overflow
situation.
recognized I2C module.
unrecognized I2C module.
recognized I2C
Check for these causes of temperature
instability:
Fast variation in the ambient tempera‐
ture, airflow or line voltage. Insufficient
air flow.
A temperature setpoint too high for the
allowed T-rating.
A defective DPM.
A defective Solid State relay.
Make sure that the signal going to all
AIs is within the range of the inputs.
Make sure that the signal going to all
AIs is within the range of the inputs.
Reset the device.
If the problem recurs, replace the mod‐
ule.
Reset the device.
If the problem recurs, replace the mod‐
ule.
Reset the device.
If the problem recurs, replace the mod‐
ule.
Make sure that the signal going to all
AIs is within the range of the inputs.
Make sure that the signal going to all
AIs is within the range of the inputs.
Update to the latest software version.
Make sure that the latest text files are
loaded.
Update to the latest software version.
Make sure that the latest text files are
loaded.
Update to the latest software version.
Make sure that the latest text files are
loaded.
Maxum edition II Analyzer General Maintenance
80 Manual, August 2018, A5E42019842001
Page 81
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
4.6.22 Alarms 10000 - 11536 MicroSAM
GCP Alarm Descriptions - 10000 - 11536 MicroSAM
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# Text Description Action
10000 ! Temperature control failure
on %4
10001 ! Temperature sensor (RTD)
of %4 defective
10002 ! Temperature deviation on
%4 exceeds limits
10003 ! Temperature controller %4
disabled
10004 ! Carrier gas pressure low
on %4
10256 ! Detector %4 disabled MicroSAM alarm Contact MicroSAM Support.
10257 ! Detector %4 shorted MicroSAM alarm Contact MicroSAM Support.
10258 ! Detector %4 not connected MicroSAM alarm Contact MicroSAM Support.
10259 ! Carrier gas pressure low
on %4
10512 ! Pressure controller %4 dis‐
abled
10513 ! A/D converter failure on %4 MicroSAM alarm Contact MicroSAM Support.
10514 ? Operating pressure low on %4MicroSAM alarm Contact MicroSAM Support.
MicroSAM alarm Contact MicroSAM Support.
MicroSAM alarm Contact MicroSAM Support.
MicroSAM alarm Contact MicroSAM Support.
MicroSAM alarm Contact MicroSAM Support.
MicroSAM alarm Contact MicroSAM Support.
MicroSAM alarm Contact MicroSAM Support.
MicroSAM alarm Contact MicroSAM Support.
10515 ! Pressure exceeds limits on %4MicroSAM alarm Contact MicroSAM Support.
10516 ! Setpoint exceeds limits on %4MicroSAM alarm Contact MicroSAM Support.
10517 ! Pressure out of control on %4MicroSAM alarm Contact MicroSAM Support.
10518 ! Voltage exceeds limits on %4MicroSAM alarm Contact MicroSAM Support.
10519 ! Operating pressure low MicroSAM alarm Contact MicroSAM Support.
10768
10775
11536 ! General RSP communica‐
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 81
! Valve [1 – 8] operation fail‐
-
ure on %4
tion error on %4
MicroSAM alarm Contact MicroSAM Support.
MicroSAM alarm Contact MicroSAM Support.
Page 82
General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
Maxum edition II Analyzer General Maintenance
82 Manual, August 2018, A5E42019842001
Page 83
Appendix A - Contact Information
Register at the Siemens Industry Online Support (SIOS) website:
https://support.industry.siemens.com
International USA
Siemens AG
I IA SC PA PM Process Analytics
Oestliche Rheinbrueckenstrasse 50
76187 Karlsruhe
Germany
Web site: www.siemens.com/processanalytics
Support Information: https://support.industry.siemens.com
Spares
Contact your local Siemens sales representative
Support Requests
www.siemens.com/automation/support-request
Siemens Industry, Inc.
5980 West Sam Houston Parkway North
Suite 500
Houston, TX 77041
USA
Tel: +1 713 939 7400
Fax: +1 713 939 9050
Email: saasales.industry@siemens.com
Web site: www.usa.siemens.com/pa
Training
Tel: +1 800 448 8224 (USA)
Email: saatraining.industry@siemens.com
Spares
Tel: +1 800 448 8224 (USA)
Email: PAspareparts.industry@siemens.com
Support Requests
www.siemens.com/automation/support-request
Tel: +1 800 448 8224 (USA)
Email: GCsupport.industry@siemens.com
A
Singapore Online Support Request
Siemens Pte. Limited
I IA SC Process Analytics
9 Woodlands Terrace
Singapore 738434
Web Site: http://www.siemens.com.sg
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 83
Web site:
www.siemens.com/automation/support-request
Page 84
Appendix A - Contact Information
Maxum edition II Analyzer General Maintenance
84 Manual, August 2018, A5E42019842001
Page 85
Index
A
Applet, 9
Applet Module, 9
Application, 9
C
Columns, 15
D
DHCP, 30
E
EC, 15
Ethernet IP, 30
F
Filament, 16
Flame Ionization, 16
Flame Photometric, 16
T
Thermistor, 16
I
IP address, 30
M
Method, 9
P
Pulsed Discharge, 16
S
Sensor Near Electronics, 12
Sensor Near Electronics software module, 12
SNE, 12
SNE functions, 13
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001 85
Page 86
Index
Maxum edition II Analyzer General Maintenance
86 Manual, August 2018, A5E42019842001
Loading...