Siemens Maxum II Manual page 51

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

Advertisement

#
Text
1091
+ I2C Write Before Read on
%4
1092
+ I2C Read Unexpected on
%4
1093
+ I2C Invalid Checksum on
%4
1094
!
Data not available on %4
1095
+ Invalid Message on %4
1096
+ Diagnostic mode enabled
on %4
1121
!
Firmware Math error on %4 All PICs: An unexpected math operation
1122
!
Firmware Mem error on %4 All PICs: A jump or a call was made to an
1123
!
Firmware Table error on
%4
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001
4.6 Alarm Codes, Descriptions, and Suggested Actions
Description
All PICs: An attempt was made to write
an I2C message before reading the re‐
sponse from a previous message.  This
indicates that an attempt was made to do
a  Slave Write - RepeatStart - Slave
Write combination.
All PICs: An I2C read from the peripheral
was attempted before a slave write loa‐
ded a command.
All PICs: An I2C message with an invalid
checksum was received.  The mes‐
sage was ignored.
All PICs: Some data was lost and is no
longer available. For a detector channel
it means that a 'Detector Read' command
was received with an invalid index. This
can happen when a request to retransmit
detector data came too late when the da‐
ta was already gone from the buffer.
This situation may also happen while ac‐
cessing the I/O related to the LM75
(BOARD_TEMPERATURE and OVER‐
TEMP_SETPOINT). It indicates that the
local I2C bus was not available to per‐
form the desired action.
All PICs: An I2C message with a valid
checksum was not recognized or had an
invalid op-code.
Informational message.
error was detected by the PIC. It can be
an un-handled overflow, underflow, etc.
This flag is always associated with a
FIRMWARE_FAULT flag.
invalid PIC memory location causing the
PIC to be reset.  This flag is always as‐
sociated with a FIRMWARE_FAULT flag.
All PICs: An error was detected when ad‐
dressing an internal PIC firmware table.
The index in the table is likely to be inva‐
lid. This flag is always associated with a
FIRMWARE_FAULT flag.
General Maintenance and Troubleshooting
Action
Contact Customer Support.
Contact Customer Support.
Contact Customer Support.
Cycle power.
If the error repeats, replace the module
or the SNECON.
Cycle power.
If the error repeats, replace the module
or the SNECON.
No action Necessary.
Cycle power.
If the error repeats, replace the module.
Cycle power.
If the error repeats, replace the module.
Cycle power.
If the error repeats, replace the module.
51

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents