Alarms 400 - 562 - Siemens Maxum II Manual

Pd pa ap. general maintenance
Hide thumbs Also See for Maxum II:
Table of Contents

Advertisement

#
Text
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
%3
398
!
Invalid Number of Temper‐
ature or Pressure Program
Segments
399
+ Results not calculated for
Channel %3
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
400
!
Sync Bus Failure %3
401
!
No detector present for
configured detector %3
402
+ SNE reset requested
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001
4.6 Alarm Codes, Descriptions, and Suggested Actions
Description
Start and stop acquisition times for a de‐
tector exceeded the method cycle length.
Invalid event downloaded with method.
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.
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.
System error
The number of temperature program set‐
points was different from the number
sent.
System error
Description
Sync Bus Test failed.
On Advance Plus unit, configured detec‐
tor is invalid.
SYSCON requested a reset from the
SNE. Usually means that the communi‐
cations between the SNE and SYSCON
timed out.  This is can happen when
SYSCON is overloaded.
General Maintenance and Troubleshooting
Action
Decrease acquisition time or increase
cycle method time.
Check for proper SNE version. Rebuild
method.
Correct the method using EZChrom.
Reset the device.
Check the method.
Verify the detector hardware to ensure
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.
Reduce SNE workload. Report to Cus‐
tomer Support.
Contact Customer Support.
Rebuild temperature events for method.
Contact Customer Support.
Action
Replace SNE.
Check sys_detector_cfg configuration.
Reset SNE.
Reduce processing demands on SY‐
SCON.
37

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents