Siemens Maxum II Manual page 73

# Text
3757 ? NACK address on %4
3758 ? NACK Byte on %4
3759 ? NACK Message on %4
3760 ? Invalid Checksum on %4
3761 ? Invalid Opcode on %4
3762 ? Invalid Message on %4
3763 ! Arbitration Loss on %4
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001
4.6 Alarm Codes, Descriptions, and Suggested Actions
Description
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.
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...).
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.
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.
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.
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.
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.
General Maintenance and Troubleshooting
Action
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.
73