Siemens Maxum II Manual page 32

General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text
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
32
Description
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 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.
Action
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.
No action necessary.
Contact Customer Support.
Check Loop of GC.
Check network communication and
contact Customer Support.
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001