
DIAGNOSING PROBLEMS
There is considerable diagnostic support built in to the MC³ controller that can be used to
troubleshoot the installation. There is also the possibility of an MC³ malfunction that
prevents the firmware from continuing. This is called a Crash.
THE CRASH SCREEN
The Crash Screen is the firmware’s last attempt to communicate a fatal error to you. The
information displayed should always be recorded. The background image looks like this:
Crash Background Image
The available space is then used to display additional information.
Start-Up Crash
If the crash screen occurs during controller boot-up, the two most likely problems are
parameter corruption and controller firmware upgrade.
Parameter Corruption
The non-volatile memory in the MC³ that holds controller parameters is corrupt. The
crash screen will look like this
Checksum Error Crash Screen
You will then be given the opportunity to either reset all parameters (
Reset Ram
) to their
factory default values or continue operation (
Cont.
) with the current, possibly corrupt
parameters. None of these alternatives are attractive. Resetting to factory default will
require you to enter your parameters again, either by hand from the spec sheet, or if you
are using WinMerik, to download them from a previously uploaded file. Continuing with
the existing parameters is risky – you may end up with a fatal error, or with unreliable or
inaccurate operation.
Controller Firmware Upgrade
If the controller firmware has been changed or upgraded, the parameters in the non-
volatile memory will typically not be compatible with the new firmware. The crash screen
will look like this, if you upgraded from 35.00.B to 35.00.C:
35.00.EX O&M Manual
54
Summary of Contents for MC3 35.00.EX
Page 5: ......