Application Errors - HEIDENHAIN MSE 1000 Operating Instructions Manual

12
Troubleshooting
12.3

Application errors

12.3 Application errors
Error
Printer is not installed
Lost communication to the
MSE 1000
Timeout while the progress bar
was waiting for a result
MSEsetup was not shutdown
properly
Setting the IP address failed
The module chain needs to be
reconnected
Error programming module
150
Cause
The Log or Error screen failed
to be printed because a printer
is not installed.
Communication between MSE-
setup and MSE 1000 modules
has been lost or failed.
Occurs when a progress bar
times out before a process
has completed. This error may
cause other screens to load in-
correctly.
The workstation was pow-
ered off or the application was
closed through the operating
system instead of the Close
button.
MSEsetup will only need to re-
cover from this error if the Sys-
tem Configuration or Module
Configuration file has been cor-
rupted by the improper shut-
down.
The Set Static operation failed.
The MSE 1000 modules were
powered off while MSEsetup is
connected.
Programming the firmware or
bootloader for a module failed.
The Module label and the Com-
munication error will also be
displayed.
HEIDENHAIN | MSE 1000 | Operating Instructions | 10/2015
Corrective action
Verify a default printer is
installed on the workstation
PC.
Attempt to recover from the
Error screen.
If unable to recover from
the Error screen, see
"Communication errors",
page 156 for additional
information.
Restart MSEsetup.
If the error continues contact
HEIDENHAIN technical
support.
Restore defaults
or
Load previously saved
System Configuration and
Module Configuration files,
see "File options", page 71.
If MSEsetup will not open:
Delete the System
Configuration and Module
Configuration files, see
"Installing MSEsetup",
page 49 for configuration
file locations.
Open MSEsetup.
Power cycle the module
chain, see "Power cycling",
page 48.
Perform a Broadcast.
Perform a Reconnect.
Power cycle the module
chain, see "Power cycling",
page 48.
Perform a Broadcast.
It may be necessary to power
cycle twice in a row to clear
the module's state machine if
programming fails.