Alarms 360 - 399 - Siemens Maxum II Manual

# Text
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
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
360 ! %!3 %4
361 ? %3 %4
362 + %3 %4
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
367 ! System Error %3 in File %4
line %5
368 ! Unable to find %3 number
%4
369 ! Unsupported channel type
%3
370 ? No channel %3 on DPM
%4 for realtime display
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001
4.6 Alarm Codes, Descriptions, and Suggested Actions
Description
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.
Description
General SNE Fault.
General SNE warning.
General SNE note.
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.
Major Data corruption on SNE
System Software Failure.
Hardware specified in method is not in
analyzer.
Hardware channel operation requested
for an invalid channel type.
Realtime display requested for a detector
channel that doesn't exist. Indicates da‐
tabase corruption.
General Maintenance and Troubleshooting
Action
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.
Action
Contact Customer Support.
Contact Customer Support.
Contact Customer Support.
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.
Reset SNE
Report error to Customer Support.
Record sequence of events leading to
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.
35