Siemens Maxum II Manual page 74

General Maintenance and Troubleshooting
4.6 Alarm Codes, Descriptions, and Suggested Actions
# Text
3764 ? Timeout SCL on %4
3765 ? Timeout SDA on %4
3766 ? Bus Not Sync on %4
3767 ? Timeout Buffer on %4
3768 ? Invalid Handle on %4
3769 ? High I2C traffic on %4
3797 + Invalid Checksum Slave on
%4
3798 + Invalid Message Slave on
%4
3799 ? Invalid Status Summary on
%4
3800 ? Module Not Ready on %4
74
Description
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.
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.
SNECON PICs: The master-mode oper‐
ation generated a start condition that was
not detected by the FPGA.
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.
SNECON PICs: The received header
handle was not sequential. One or more
I2C messages were lost.
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.
SNECON 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.
SNECON 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.
SNECON 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.
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.
Action
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
Manual, August 2018, A5E42019842001