MSA SUPREMA Touch, Инструкция по установке и обслуживанию, Страница: 98 / 309

MSA AUER
MSA
Maintenance and Service
SUPREMATouch 97
US
6.8 System Failure Messages
No.
Failure Mes-
sage Text
Module
Appears in
case of Disappears
in case of Error
LED Fail
LED Info 1
[BYTE] Info 2
[DWORD]
Remarks/ Remedial action
1 dynamic mem-
ory overflow All Stack overflow
or stack under-
flow detected Restart X X Task ID Memory ad-
dress Generally software problems
[e.g. wrong stack dimensions]
Perhaps sequence error
to No. 2,3 or 6
2 error in work
memory All RAM failure de-
tected [Self-test] Whole RAM
tested fail-
ure-free [af-
ter approx.
24 h] X X Bit pattern
fault bits Memory ad-
dress Hardware defect: exchange
module
3 error in pro-
gram memory All ROM failure de-
tected [Self-test] Whole ROM
tested fail-
ure-free [af-
ter approx.
24 h] X X 1
→
found
during sys-
tem start;
0
→
other-
wise
loWord
→
CRC found;
hiWord
→
CRC should
be
Hardware defect: exchange
module
4 internal time-
out All Life sign of at
least one task is
missing All tasks
gave life
sign in time X X Nominal val-
ue of task
flags [8 low-
est Bits] loWord
→
task flags is;
hiWord
→
task flags
should be
Perhaps sequence error of
CAN bus failure. Check bus.
5 data lost on
bus MDA,
MGO,
MAO CAN controller
detects overflow CAN Con-
troller in nor-
mal mode X X Always 0 Always 0 Perhaps not correctly termi-
nated bus or modules with
wrong bitrate at the bus.
[Green CAN-LED indicates
the status of the bus.]
May also be defect hardware.
6 fatal internal
error All Exception Inter-
rupt [e.g. write
access to ROM,
invalid memory
address...] Restart X X Exception
number Memory ad-
dress Hardware defect: exchange
module
Perhaps sequence error to
No. 1, 2 or 3
7 buffer overflow MCP,
MDO,
MDA,
MBC
Overflow of the
internal process-
ing queues. Restart X X Queue
number Queue Sta-
tus Perhaps in combination with
No. 4 at system overload or
sequence error to CAN bus
failures
8 communica-
tion error on
bus MCP,
MDO Error during
SDO transfer
[transfer of con-
figuration and
parameter data] SDO trans-
fer success-
fully ended X X CAN-I/O er-
ror code Additional
data [error
code de-
pended] Perhaps CAN-bus failure:
check Bus.
Check MCP and MDO for in-
compatible software status.
May occur when hot plugging
modules.
9 system error of
configuration
memory MCP,
MDO,
MBC Error on access-
ing flash memo-
ry which
contains param-
eter and configu-
ration data Restart X X Flash error
code Additional
data [error
code de-
pended] Hardware defect: exchange
module
Perhaps in combination with
No. 10 or 15.
10 error in config-
uration memo-
ry MCP,
MDO,
MBC Flash error de-
tected [Self-test
of the configura-
tion and param-
eter memory] Whole flash
tested error-
free [after
approx.
24 h] X X Always 0 Always 0 Hardware defect: exchange
module
11 data lost at se-
rial communi-
cation MDO Error at serial
communication Restart X X Interface
number loWord
→
number of
characters;
hiWord
→
status
Data lost at PC or printer inter-
face: Check cables
Perhaps hardware defect: ex-
change MDO module
12 node guarding
error detected MCP,
MDO Module does not
respond to
node- guarding,
or does not send
any heartbeat All nodes re-
spond again X X ID of node
that doesn't
respond If the node in
info 1 is an
MDA and info
2 is not 0, this
is the MAI
number CAN-Bus failure, module de-
fect or missing: Check bus
and modules
MGO,
MAO X X Always 0 Time in sys-
tem-ticks no output data was received
for a certain time: check bus
and MCP/MDO modules