Envipco U48DFF, Service Manual

Page: 79 / 100

6-1
Chapter 6
Troubleshooting & Repairs
6.1. Introduction
This chapter details the steps to troubleshoot and repair the
ULTRA
.
6.2. ULTRA’s Error Messages
Table 6-1 lists all of the error messages, their causes, and troubleshooting steps for each.
TABLE 6-1.
ULTRA Error Messages
Error# Error Message Cause Troubleshooting
9000 No Response to Hardware-Init
RVM not operational
Contact Envipco Support
The
RVM
initialization timed
out after 30 seconds.
Check harnesses and connections. If that
fails, replace the
RVM
controller.
9001 Bus-Electronic is not responding
RVM not operational
Contact Envipco Support
No micro controllers were
found on the system bus. Check harnesses and connections. If that
fails, replace the
RVM
controller.
9002 Bus-Electronic differs from
Configuration
RVM not operational
Contact Envipco Support
One or more clients are miss-
ing from the system bus. Check harnesses and connections. If that
fails, replace the
RVM
controller.
9005 Hardware Init
-> Cabinet not closed
RVM not operational
Close all Doors!
The
RVM
will not operate
because the safety interlock is
activated. A door is open or the
magnetic door sensors are mal-
functioning.
Make sure that all doors are closed. If the
doors are closed, check the Diagnostic Pro-
gram (Main / Safety Loop) to see what is
causing this message.
9006 No Hardware Layer
RVM not operational
Contact Envipco Support
The Hardware Process is not
running on the
PC
board.
Check harnesses and connections. If that
fails, replace the
RVM
controller.
9007 Service Mode
is active
>> Service Mode <<
not permitted at Systemstart
Contact Envipco Support
The
RVM
will not operate
while it is in Service Mode.
Exit Service Mode, and remove your override
key.
9008 Cabinet Door open
Safety breach!
RVM not operational
Close all Doors!
The
RVM
will not operate if
one of the doors is open. This
is a catch-all error message.
Make sure that all doors are closed. If the
doors are closed, check the Diagnostic Pro-
gram (Main / Safety Loop) to see what is
causing this message.