A-9
Driver is not installed [E_NOT_INSTALLED_I]
Comment: Returned in response to the ON_LINE command to indicate that the MAPI
driver is not installed in the system.
Action: Verify that the line DEVICE=C:\MENU\MAPIDEV.SYS is in the system
CONFIG.SYS file, that the correct interrupt level (IRQ) and I/O base address are
specified and that the file C:\MENU\MAPIDEV.SYS is installed on the system.
Driver is off line [E_OFF_LINE_I]
Comment: Returned by any driver whenever a command is written to the driver and the
system is OFF_LINE.
Action: Put the driver back on line.
Driver missed a hardware interrupt [E_MISSED_INTERRUPT_I]
Comment: The filter drum or the X-ray hi/lo monitor is enabled in the C-arm driver
and the driver detected a dropped message from the C-arm microprocessor (indicated
by a mismatch in the message sequence field).
Action: Verify that no other software, TSR or operating system is running while you do
a scan (e.g., do not run a scan with while connected to a network or attempt to run a
scan under Windows). This may also be due to a communications error between the AT
and the C-arm. Follow the procedure under "BAD CHECKSUM IN MESSAGE." to
diagnose I/O errors.
Emergency stop active [E_EMERGENCY_STOP_I]
Comment: The system emergency stop is active, either because the operator has
pressed the emergency stop button, one of the emergency stop strips has been touched,
or because the C/C has calculated that the C-arm and the table are within 1/10" of each
other.
Action: If the emergency stop button on the operator panel is down (on), pull it up.
Verify that nothing is touching the emergency stop strips on the table. If the C-arm and
table are within 1/10", the problem is with the application (or operator) that moved
them so close. If they are not, see the discussion about
E_COLLISION_IMMINENT_I. If both E_COLLISION_IMMINENT_I and
E_EMERGENCY_STOP_I are active, the only way to recover is to manually push the
table and C-arm away from each other and then follow the recovery procedure under
E_COLLISION_IMMINENT_I.
End of file
Action: This could occur at the start of a lateral scan if the currently selected scan is not
an analyzed companion AP scan.
ERROR MESSAGE
HARDWARE
/SOFTWARE
ERROR
LOCUS
COMMENT/ACTION
Summary of Contents for DISCOVERY A
Page 52: ...Discovery QDR Series Technical Manual 2 30...
Page 55: ...Discovery QDR Series Technical Manual 3 3 Figure 3 2 System Dimensions for Discovery C...
Page 56: ...Discovery QDR Series Technical Manual 3 4 Figure 3 3 System Dimensions for Discovery SL...
Page 144: ...Discovery QDR Series Technical Manual 4 22...
Page 188: ...Discovery QDR Series Technical Manual 5 22...
Page 228: ...Discovery QDR Series Technical Manual 6 16...
Page 248: ......