,,,,,,,,,,,,, ,,,,,,,,,,,,,
Last Updated: 05/19/1999
| 1- Introduction
The Horizon LX Extended Error Log provides additional service information for 8645/GRAM and SGD Hi Slew Gradient Driver hardware, as well as the SRFD 1.0T subsystem error messages that appear in the Release 8.x Error Message Log. 2- Using the Extended Error Log When an error occurs, and there is not enough information in the error log to help solve the problem, look at the end of the error message. If there is an arrow (®) as the last character, there is extended service relevant information available. The first page screen has three soft keys: [Exit] allows you to close the file. [?] provides author information. [Extended Error Log] takes you to the EEL database. Once in the EEL, there are three major fields: The upper field is the Enter Error Number field, the middle field is the Standard Error Message: field, and the lowest field is the Additional Information: field. The Enter Error Number is an active field so that error numbers can be typed in as needed. Type in the error number and click on [Search]. If there is no additional information, the message: 'No Additional Information for error # 223XXXX' shows in the Additional Information: field. If the number has been incorrectly typed, the message: 'XXXXX is an invalid error number, must be 7 numbers' appears in the Standard Error Message: field. If there is additional information, it appears in the field called Additional Information. 3- Keeping the Error Information Up-to-Date One of the best ways to keep this extended error log up-to-date is to submit a CQA with accurate troubleshooting information. As CQAs are received, they are reviewed, and entered, allowing this new tool to be useful, up to date, and relevant. |
"IPG tried to write an undefined RF Amplifier Register. Register: 0x%02X"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_RF_AMP_WRITE_REG
"IPG tried to write an undefined RF Amplifier Register. Register: 0x%02X"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_RF_AMP_WRITE_DATA
"IPG tried to write an undefined command to the RF Control Register. Data: 0x%02X"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_RF_AMP_TYPE_INCORRECT
"RFampType in Mrconfig.cfg file does not match RF Amplifier Type determined by SPI. Please Update Mrconfig.cfg file with correct RFampType. Actual RF Amplifier Type: %01d.%01dT %b."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_ERBTEC_STRING
"Erbtec"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_STRING
"Solid State TELI"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_20
"RFI Interface (RFI) General Overheating Fault. Possible causes: restricted air flow, improper calibration, or defective RFI.->"
Extended Error: The internal heat sensor in the RFI detected fault. Check fan, may be blocked or defective.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_21
"RF Interface (RFI) Mismatch Fault. The Dump Resistor in the RFI has overheated. Possible causes: improper calibration, missing or improper cables between RFI and amplifier(s) or defective RFI. ->"
Extended Error: Improper cables expand on input and output stages of Amp Cables in and out of RF Amps. Small and large cables open or missing. Check RFI Phase Balance Calibration.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_22
"TELI RF Amplifier 1 Cable Fault. The RF Interface (RFI) is reporting the cable is disconnected or defective between the RFI and the TELI RF Amplifier 1."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_23
"TELI RF Amplifier 2 Cable Fault. The RF Interface (RFI) is reporting the cable is disconnected or defective between the RFI and the RF Amplifier 2."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_30
"Power Monitor 1 Fault. RF Transmit power has reached safety limit allowed for scan parameters and patient weight. Check patient weight entered.
Amplitude: %02d
Pulse Width: %02d
Duty Cycle: %02d"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_31
"Power Monitor 2 Fault. RF Transmit power has reached safety limit allowed for scan parameters and patient weight. Check patient weight entered.
Amplitude: %02d
Pulse Width: %02d
Duty Cycle: %02d"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_32
"RF Interface (RFI) High Voltage Relay Fault. Possible causes: RF Monitor cable to System Support Module (SSM) is bad or defective.
Note: This fault may occur in conjunction with a Power Monitor Fault. ->"
Extended Error: High voltage (is really emulated for Erbtec Amp) relay fault will occur with Power Monitor Faults.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_41
"TELI RF Amplifier 1 Power Supply Fault. Teli Amplifier 1 indicates the main power supply is out of specification. Possible causes: bad capacitor, power amplifier stages, or power supply failure. Follow RF Amplifier Functional Checks procedure.->"
Extended Error: VDD faults on measure/output of (54V) power supply shorted capacitors.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_48
"TELI RF Amplifier 1 Excessive Input Drive Fault. TELI Amplifier 1 detects input greater than 2.5dBm. Possible causes: RF Interface (RFI) improper calibration, defective exciter, or defective RF Amplifier 1. ->"
Extended Error: Check exciters signal level. If exciter levels are within specification, check gain adjustment on RFI is correct (within specifications). Refer to RF/PDU Functional Check procedures.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_49
"TELI RF Amplifier 1 Overheat Fault. TELI Amplifier 1 reports the thermal switch has exceeded 80 degrees C. Possible causes: restricted air flow, blown fan fuse, defective fan, room environment out of specification or defective RF Amplifier 1.->"
Extended Error: Check Fan Fuses on Amps.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_4A
"TELI RF Amplifier 1 Peak Power Fault. TELI Amplifier 1 reports its peak power has exceeded 4.5kW. Possible causes: RF Interface (RFI) calibration, defective RFI output stage, defective Exciter or defective RF Amplifier1.->"
Extended Error: Check exciters signal level/gain adjustment on RFI is correct (within specs). Refer to procedure.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_4B
"TELI RF Amplifier 1 Average Power Fault. TELI RF Amplifier 1 reports its average power has exceeded 450W. Possible causes: the PSD is exceeding the limits of the system, defective RF Interface (RFI) output stage, or defective RF Amplifier 1.->"
Extended Error: Check exciters signal level. If exciter levels are within specification, check gain adjustment on RFI is correct (within specifications). Refer to RF/PDU Functional Check procedures.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_4C
"TELI RF Amplifier 1 Voltage Standing Wave Ratio (VSWR) Fault. TELI RF Amplifier 1 reports a greater than 4:1 ratio. Possible causes: disconnected or defective output cable from RF Amplifier 1 to RF Interface (RFI), defective RFI or RF Amplifier 1.->"
Extended Error: Improper cables expand on output stages of Amp cables out of RF Amps.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_4D
"TELI RF Amplifier 1 Gate Fault. TELI RF Amplifier 1 reports an unblank pulse width greater than 30ms. Possible causes: the PSD is exceeding the limits of the system, defective RF Interface (RFI) or defective RF Amplifier 1.->"
Extended Error: Look to ensure proper PSD is being used. If PSD is not problem, perform RF Amplifier Functional Check procedure for RF/PDU Cabinet. If RF Amplifier is operating with in specification then perform RFI Functional Checks for RF/PDU Cabinet.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_61
"TELI RF Amplifier 2 Power Supply Fault. TELI Amplifier 2 indicates the main power supply is out of specification. Possible causes: bad capacitor, power amplifier stages , or power supply failure. Follow RF Amplifier Functional Checks procedure.->"
Extended Error: VDD faults on measure/output of (54V) Power Supply shorted capacitors.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_68
"TELI RF Amplifier 2 Excessive Input Drive Fault. TELI Amplifier 2 detects input greater than 2.5dBm. Possible causes: RF Interface (RFI) miscalibration, defective exciter, or defective RF Amplifier 2.->"
Extended Error: Check exciters signal level. If exciter levels are within specification, check gain adjustment on RFI is correct (within specifications). Refer to RF/PDU Functional Check procedures.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_69
"TELI RF Amplifier 2 Overheat Fault. TELI Amplifier 2 reports the thermal switch has exceeded 80 degrees C. Possible causes: restricted sir flow, blown fan fuse, defective fan, room environment out of specification or defective RF Amplifier 2.->"
Extended Error: Check Fan Fuses on Amps.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_6A
"TELI RF Amplifier 2 Peak Power Fault. TELI RF Amplifier 2 reports its peak power has exceeded 4.5kW. Possible causes: RF Interface (RFI) calibration, defective RFI output stage, defective Exciter or defective RF Amplifier 2.->"
Extended Error: Check exciters signal level/gain adjustment on RFI is correct(within specs). Refer to procedure.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_6B
"TELI RF Amplifier 2 Average Power Fault. TELI RF Amplifier 2 reports its average power has exceeded 450W. Possible causes: the PSD is exceeding the limits of the system, defective RF Interface (RFI) output stage, or defective RF Amplifier 2.->"
Extended Error: Check exciters signal level. If exciter levels are within specification, check gain adjustment on RFI is correct (within specifications). Refer to RF/PDU Functional Check procedures.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_6C
"TELI RF Amplifier 2 Voltage Standing Wave Ratio (VSWR) Fault. TELI RF Amplifier 2 reports a greater than 4:1 ratio. Possible causes: disconnected or defective output cable from RF Amplifier 2 to RF Interface (RFI), defective RFI or RF Amplifier 2.->"
Extended Error: Improper cables expand on output stages of Amp cables out of RF Amps.
Return To Top ---------------------------------------------------------
ERROR: EM_SPI_TELI_ERROR_6D
"TELI RF Amplifier 2 Gate Fault. TELI RF Amplifier 2 reports an unblank pulse width greater than 30ms. Possible causes: the PSD is exceeding the limits of the system, defective RF Interface (RFI) or defective RF Amplifier 2.->"
Extended Error: Look to ensure proper PSD is being used. If PSD is not problem, perform RF Amplifier Functional Check procedure for RF/PDU Cabinet. If RF Amplifier is operating with in specification then perform RFI Functional Checks for RF/PDU Cabinet.
Return To Top ---------------------------------------------------------
2225732
ERROR: EM_SPI_ANALOGIC_STRING
"Solid State ANALOGIC"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
2225733
ERROR: EM_SPI_AN_ERROR_20
"RFI Interface (RFI) General Overheating Fault. Possible causes: restricted air flow, improper calibration, or defective RFI. ->"
Extended Error: The internal heat sensor in the RFI detected fault. Check fan, may be blocked or defective.
Return To Top ---------------------------------------------------------
2225734
ERROR: EM_SPI_AN_ERROR_21
"RF Interface (RFI) Mismatch Fault. The Dump Resistor in the RFI has overheated. Possible causes: improper calibration, missing or improper cables between RFI and amplifier(s) or defective RFI. ->"
Extended Error: Improper cables expand on input and output stages of Amp Cables in and out of RF Amps. Small and large cables open or missing. Check RFI Phase Balance Calibration.
Return To Top ---------------------------------------------------------
2225735
ERROR: EM_SPI_AN_ERROR_22
"ANALOGIC RF Amplifier 1 Cable Fault. The RF Interface (RFI) is reporting the cable is disconnected or defective between the RFI and the ANALOGIC RF Amplifier 1."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
2225736
ERROR: EM_SPI_AN_ERROR_23
"ANALOGIC RF Amplifier 2 Cable Fault. The RF Interface (RFI) is reporting the cable is disconnected or defective between the RFI and the RF Amplifier 2."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
2225737
ERROR: EM_SPI_AN_ERROR_30
"Power Monitor 1 Fault. RF Transmit power has reached safety limit allowed for scan parameters and patient weight. Check patient weight entered.
Amplitude: %02d
Pulse Width: %02d
Duty Cycle: %02d"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
2225738
ERROR: EM_SPI_TELI_ERROR_31
"Power Monitor 2 Fault. RF Transmit power has reached safety limit allowed for scan parameters and patient weight. Check patient weight entered.
Amplitude: %02d
Pulse Width: %02d
Duty Cycle: %02d"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
2225739
ERROR: EM_SPI_AN_ERROR_32
"RF Interface (RFI) High Voltage Relay Fault. Possible causes: RF Monitor cable to System Support Module (SSM) is bad or defective.
Note: This fault may occur in conjunction with a Power Monitor Fault. ->"
Extended Error: High voltage (is really emulated for Erbtec Amp) relay fault will occur with Power Monitor Faults.
Return To Top ---------------------------------------------------------
2225740
ERROR: EM_SPI_AN_ERROR_40
"ANALOGIC RF Amplifier 1 Power Loss Fault. RF Interface (RFI) detects no power to ANALOGIC RF Amplifier 1. Possible cause: the breaker on the front of the RFI is turned off. ->"
Extended Error: RF Amplifier 1 breaker could be OFF or AC switch at rear of RF Amplifier may be in OFF position.
Return To Top ---------------------------------------------------------
2225741
ERROR: EM_SPI_AN_ERROR_41
"ANALOGIC RF Amplifier 1 Power Supply Fault. ANALOGIC Amplifier 1 indicates the main power supply is out of specification. Possible causes: Supply feedback loop exceeds 2.5v, PS heat sink is overheated, Power supply FETS are shorted. ->"
Extended Error: Check fans, may be blocked or defective, Cabinet Filters need to be changed, or RF Amplifier 1 may be operating out of specification.
Return To Top ---------------------------------------------------------
2225742
ERROR: EM_SPI_AN_ERROR_42
"ANALOGIC RF Amplifier 1 Duty Cycle Fault. Unblank duty cycle exceeds 63\%.->"
Extended Error: Verify proper PSD is being used. If PSD is not problem perform RF Amplifier Functional Check procedure for RF/PDU Cabinet. UNBLANK Pulse corrupted, check Tyme Board.
Return To Top ---------------------------------------------------------
2225743
ERROR: EM_SPI_AN_ERROR_43
"ANALOGIC RF Amplifier 1 I Peak Overloaded Fault. Instantaneous peak drain current of RF devices exceeds 120 amps. ->"
Extended Error: Verify proper PSD is being used. If PSD is not problem perform RF Amplifier Functional Check procedure for RF/PDU Cabinet. RF Amplifier 1 may be operating out of specification.
Return To Top ---------------------------------------------------------
2225744
ERROR: EM_SPI_AN_ERROR_44
"ANALOGIC RF Amplifier Device Fault. RF FET device is shorted. ->"
Extended Error: Replace Amplifier.
Return To Top ---------------------------------------------------------
2225745
ERROR: EM_SPI_AN_ERROR_45
"ANALOGIC RF Amplifier HV Low Voltage Fault. ANALOGIC Amplifier 1 power supply voltage dropped below 120 VDC. (150 V nominal). ->"
Extended Error: Verify proper PSD is being used. If PSD is not problem perform RF Amplifier Functional Check procedure for RF/PDU Cabinet.
Return To Top ---------------------------------------------------------
2225746
ERROR: EM_SPI_AN_ERROR_46
"ANALOGIC RF Amplifier HV High Voltage Fault. ANALOGIC Amplifier 1 power supply voltage went above 170 VDC.->"
Extended Error: Verify proper PSD is being used. If PSD is not problem perform RF Amplifier Functional Check procedure for RF/PDU Cabinet.
Return To Top ---------------------------------------------------------
2225747
ERROR: EM_SPI_AN_ERROR_49
"ANALOGIC RF Amplifier 1 Overheat Fault. ANALOGIC Amplifier 1 reports the thermal switch has exceeded 80 degrees C. Possible causes: restricted air flow, defective fan, room environment out of specification or defective RF Amplifier 1.->"
Extended Error: Check fans, may be blocked or defective, Cabinet Filters need to be changed, or RF Amplifier 1 may be operating out of specification.
Return To Top ---------------------------------------------------------
2225748
ERROR: EM_SPI_AN_ERROR_4A
"ANALOGIC RF Amplifier 1 Peak Power Fault. Peak power from ANALOGIC RF Amplifier 1 exceeds specification (69,5 - 69.8 dBm).->"
Extended Error: Check exciter signal Level/gain adjustment on RFI is within specification. Refer to procedure for RFI and RF Amplifier Functional Checks.
Return To Top ---------------------------------------------------------
2225749
ERROR: EM_SPI_AN_ERROR_4B
"ANALOGIC RF Amplifier 1 Average Power Fault. ANALOGIC RF Amplifier 1 reports its average power has exceeded 1000 W. Possible causes: the PSD is exceeding the limits of the system, defective RF Interface (RFI), defective RFI or RF Amplifier 1.->"
Extended Error: Check exciter signal Level/gain adjustment on RFI is within specification. Refer to procedure for RFI and RF Amplifier Functional Checks.
Return To Top ---------------------------------------------------------
2225750
ERROR: EM_SPI_AN_ERROR_4C
"ANALOGIC RF Amplifier 1 Voltage Standing Wave Ratio (VSWR) Fault. ANALOGIC RF Amplifier 1 reflected power exceeds 2250 W. Possible causes: disconnected or defective output cable from RF Amplifier 1 to RF Interface (RFI), defective RFI or RF Amplifier 1.->"
Extended Error: Check RF Out (J4) cable is not disconnected or defective. Check cable lengths. Check connectors on RF Out (J4) cable.
Return To Top ---------------------------------------------------------
2225751
ERROR: EM_SPI_AN_ERROR_4D
"ANALOGIC RF Amplifier 1Gate Fault. ANALOGIC RF Amplifier 1 reports an unblank pulse width exceeding specification (62 - 68 msec).->"
Extended Error: Verify proper PSD is being used. If PSD is not problem perform RF Amplifier Functional Check procedure for RF/PDU Cabinet. UNBLANK Pulse corrupted.
Return To Top ---------------------------------------------------------
2225752
ERROR: EM_SPI_AN_ERROR_4E
"ANALOGIC RF Amplifier 1 Junction Temp Fault. ANALOGIC RF Amplifier 1 device junction temperature > 130 deg C.->"
Extended Error: RFI balance is out of specification, refer to the RF/PDU Maximum Power RF Output Setup And Calibration procedure.
Return To Top ---------------------------------------------------------
2225753
ERROR: EM_SPI_AN_ERROR_60
"ANALOGIC RF Amplifier 2 Power Loss Fault. RF Interface (RFI) detects no power to ANALOGIC RF Amplifier 2. Possible cause: the breaker on the front of the RFI is turned off. ->"
Extended Error: RF Amplifier 2 breaker could be OFF or AC switch at rear of RF Amplifier may be in OFF position.
Return To Top ---------------------------------------------------------
2225754
ERROR: EM_SPI_AN_ERROR_61
"ANALOGIC RF Amplifier 2 Power Supply Fault. ANALOGIC Amplifier 2 indicates the main power supply is out of specification. Possible causes: Supply feedback loop exceeds 2.5v, PS heat sink is overheated, Power supply FETS are shorted. ->"
Extended Error: Check fans, may be blocked or defective, Cabinet Filters need to be changed, or RF Amplifier 1 may be operating out of specification.
Return To Top ---------------------------------------------------------
2225755
ERROR: EM_SPI_AN_ERROR_62
"ANALOGIC RF Amplifier 2 Duty Cycle Fault. Unblank duty cycle exceeds 63\%.->"
Extended Error: Verify proper PSD is being used. If PSD is not problem perform RF Amplifier Functional Check procedure for RF/PDU Cabinet. UNBLANK Pulse corrupted, check Tyme Board.
Return To Top ---------------------------------------------------------
2225756
ERROR: EM_SPI_AN_ERROR_63
"ANALOGIC RF Amplifier 2 I Peak Overloaded Fault. Instantaneous peak drain current of RF devices exceeds 120 amps. ->"
Extended Error: Verify proper PSD is being used. If PSD is not problem perform RF Amplifier Functional Check procedure for RF/PDU Cabinet. RF Amplifier 2 may be operating out of specification.
Return To Top ---------------------------------------------------------
2225757
ERROR: EM_SPI_AN_ERROR_64
"ANALOGIC RF Amplifier Device Fault. RF FET device is shorted. ->"
Extended Error: Replace Amplifier.
Return To Top ---------------------------------------------------------
2225758
ERROR: EM_SPI_AN_ERROR_65
"ANALOGIC RF Amplifier HV Low Voltage Fault. ANALOGIC Amplifier 2 power supply voltage dropped below 120 VDC. (150 V nominal). ->"
Extended Error: Verify proper PSD is being used. If PSD is not problem perform RF Amplifier Functional Check procedure for RF/PDU Cabinet.
Return To Top ---------------------------------------------------------
2225759
ERROR: EM_SPI_AN_ERROR_66
"ANALOGIC RF Amplifier HV High Voltage Fault. ANALOGIC Amplifier 2 power supply voltage went above 170 VDC.->"
Extended Error: Verify proper PSD is being used. If PSD is not problem perform RF Amplifier Functional Check procedure for RF/PDU Cabinet.
Return To Top ---------------------------------------------------------
2225760
ERROR: EM_SPI_AN_ERROR_69
"ANALOGIC RF Amplifier 2 Overheat Fault. ANALOGIC Amplifier 2 reports the thermal switch has exceeded 80 degrees C. Possible causes: restricted air flow, defective fan, room environment out of specification or defective RF Amplifier 2.->"
Extended Error: Check fans, may be blocked or defective, Cabinet Filters need to be changed, or RF Amplifier 2 may be operating out of specification.
Return To Top ---------------------------------------------------------
2225761
ERROR: EM_SPI_AN_ERROR_6A
"ANALOGIC RF Amplifier 2 Peak Power Fault. Peak power from ANALOGIC RF Amplifier 1 exceeds specification (69,5 - 69.8 dBm).->"
Extended Error: Check exciter signal Level/gain adjustment on RFI is within specification. Refer to procedure for RFI and RF Amplifier Functional Checks.
Return To Top ---------------------------------------------------------
2225762
ERROR: EM_SPI_AN_ERROR_6B
"ANALOGIC RF Amplifier 2 Average Power Fault. ANALOGIC RF Amplifier 2 reports its average power has exceeded 1000 W. Possible causes: the PSD is exceeding the limits of the system, defective RF Interface (RFI), defective RFI or RF Amplifier 2.->"
Extended Error: Check exciter signal Level/gain adjustment on RFI is within specification. Refer to procedure for RFI and RF Amplifier Functional Checks.
Return To Top ---------------------------------------------------------
2225763
ERROR: EM_SPI_AN_ERROR_6C
"ANALOGIC RF Amplifier 2 Voltage Standing Wave Ratio (VSWR) Fault. ANALOGIC RF Amplifier 2 reflected power exceeds 2250 W. Possible causes: disconnected or defective output cable from RF Amplifier 2 to RF Interface (RFI), defective RFI or RF Amplifier 2.->"
Extended Error: Check RF Out (J4) cable is not disconnected or defective. Check cable lengths. Check connectors on RF Out (J4) cable.
Return To Top ---------------------------------------------------------
2225764
ERROR: EM_SPI_AN_ERROR_6D
"ANALOGIC RF Amplifier 2 Gate Fault. ANALOGIC RF Amplifier 2 reports an unblank pulse width exceeding specification (62 - 68 msec).->"
Extended Error: Verify proper PSD is being used. If PSD is not problem perform RF Amplifier Functional Check procedure for RF/PDU Cabinet. UNBLANK Pulse corrupted.
Return To Top ---------------------------------------------------------
2225765
ERROR: EM_SPI_AN_ERROR_6E
"ANALOGIC RF Amplifier 2 Junction Temp Fault. ANALOGIC RF Amplifier 2 device junction temperature > 130 deg C.->"
Extended Error: RFI balance is out of specification, refer to the RF/PDU Maximum Power RF Output Setup And Calibration procedure.
Return To Top ---------------------------------------------------------
ERROR: "Internal GAP" software error. Invalid 5 bit address. Address Selected: 0x%08X
If you are using a tool like SHMOD or a debugger, you requested invalid information. If no tools were being run, there is a bug in the software; write a CQA."
Extended Error: To check the MDS link, use the Fiber Optic Light Meter and run the MDS Fiber Optic Diagnostics.
Return To Top ---------------------------------------------------------
ERROR: Internal GAP software error. Number of axis is not between %d and %d.
Axis Selected: %d
If you are using a tool like SHMOD or a debugger, you requested invalid information. If no tools were being run, there is a bug in the software; write a CQA
Extended Error: To check the MDS link, use the Fiber Optic Light Meter and run the MDS Fiber Optic Diagnostics.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_INVALID_DATA
"Internal GAP software error. Invalid 4 bit data. Data to Write: 0x%08X
If you are using a tool like SHMOD or a debugger, you requested invalid information. If no tools were being run, there is a bug in the software; write a CQA
Extended Error: To check the MDS link, use the Fiber Optic Light Meter and run the MDS Fiber Optic Diagnostics.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_INVALID_TP
"Internal GAP software error. Invalid selection for a test point.
Test Point Selected: %d
If the GAP software is running okay ( the GAP Board LED is blinking with a period of 5 seconds ), then this is a software bug; write a CQA."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_INVALID_UPDATE_MODE
"Internal GAP software error. Invalid selection for an update mode.
Update Mode Selected: %d
SPI software specified an undefined mode in a MDS packet. If the MDS link connection is good, this is a software bug; write a CQA."
Extended Error: To check the MDS link, use the Fiber Optic Light Meter and run the MDS Fiber Optic Diagnostics.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_UNDEF_INTERRUPT
"Internal GAP software error. Invalid interrupt.
Interrupt: %d
If the GAP software is running okay ( the GAP Board LED is blinking with a period of 5 seconds ), then this is a software bug; write a CQA."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_UNDEF_MDS_OPCODE
"Internal GAP software error. Invalid MDS opcode.
Undefined Opcode: %d
The GAP received an undefined opcode from a SPI MDS packet. If GAP and SPI software are from the same tape build and the MDS link is good, this is a software bug; write a CQA."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_X_NO_ERROR_FOUND
"X Axis gradient error detected.
A spurious error occurred on the X Axis. Common causes are loose or noisy status signals: Check connections between gradient driver hardware."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Y_NO_ERROR_FOUND
"Y Axis gradient error detected.
A spurious error occurred on the Y Axis. Common causes are loose or noisy status signals: Check connections between gradient driver hardware."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Z_NO_ERROR_FOUND
"Z Axis gradient error detected.
A spurious error occurred on the Z Axis. Common causes are loose or noisy status signals: Check connections between gradient driver hardware."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_X_READY_INTERRUPT
"X Axis gradient ready error detected.
A ready interrupt occurred on the X Axis while the axis was ready. This will not stop the scan, but indicates a communication problem between the GAP and the MIF."
Extended Error: If this problem occurs, it is probably intermittent. This will be a difficult problem to diagnose.
If this error occurs, then the GAP, MIF, and cables between the two are suspect. Swapping MIF Modules is a possibility so that the error can be tracked to see if it moves. If the problem moves, then the MIF Module is the problem. Cables can also be swapped. However, the GAP is a single item in the system, and cannot be swapped. Currently, there are no diagnostics or tests to find this problem.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Y_READY_INTERRUPT
"Y Axis gradient ready error detected.
A ready interrupt occurred on the Y Axis while the axis was ready. This will not stop the scan, but indicates a communication problem between the GAP and the MIF."
Extended Error: If this problem occurs, it is probably intermittent. This will be a difficult problem to diagnose.
If this error occurs, then the GAP, MIF, and cables between the two are suspect. Swapping MIF Modules is a possibility so that the error can be tracked to see if it moves. If the problem moves, then the MIF Module is the problem. Cables can also be swapped. However, the GAP is a single item in the system, and cannot be swapped. Currently, there are no diagnostics or tests to find this problem.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Z_READY_INTERRUPT
"Z Axis gradient ready error detected.
A ready interrupt occurred on the Z Axis while the axis was ready. This will not stop the scan, but indicates a communication problem between the GAP and the MIF."
Extended Error: If this problem occurs, it is probably intermittent. This will be a difficult problem to diagnose.
If this error occurs, then the GAP, MIF, and cables between the two are suspect. Swapping MIF Modules is a possibility so that the error can be tracked to see if it moves. If the problem moves, then the MIF Module is the problem. Cables can also be swapped. However, the GAP is a single item in the system, and cannot be swapped. Currently, there are no diagnostics or tests to find this problem.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_READY_INTERRUPT
"X Axis GRAM ready error detected.
A GRAM ready interrupt occurred on the X Axis while the axis was ready. This will not stop the scan, but indicates a communication problem between the GAP and the GRAM."
Extended Error: If this problem occurs, it is probably intermittent. This will be a difficult problem to diagnose.
If this error occurs, then the GAP, MIF, GRAM and cables between the them are suspect. Swapping MIF Modules is a possibility so that the error can be tracked to see if it moves. If the problem moves, then the MIF Module is the problem. Cables can also be swapped.
The GRAM Modules can be swapped by using the GRAM Troubleshooting Harness (2144094).This harness cannot be used for system operation. It is only used for short term troubleshooting.
The GAP is a single item in the system, and cannot be swapped. Currently, there are no diagnostics or tests to find this problem. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_READY_INTERRUPT
"Y Axis GRAM ready error detected.
A GRAM ready interrupt occurred on the Y Axis while the axis was ready. This will not stop the scan, but indicates a communication problem between the GAP and the GRAM."
Extended Error: If this problem occurs, it is probably intermittent. This will be a difficult problem to diagnose.
If this error occurs, then the GAP, MIF, GRAM and cables between the them are suspect. Swapping MIF Modules is a possibility so that the error can be tracked to see if it moves. If the problem moves, then the MIF Module is the problem. Cables can also be swapped. The GRAM Modules can be swapped by using the GRAM Troubleshooting Harness (2144094). This harness cannot be used for system operation. It is only used for short term troubleshooting.
The GAP is a single item in the system, and cannot be swapped. Currently, there are no diagnostics or tests to find this problem. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_READY_INTERRUPT
"Z Axis GRAM ready error detected.
A GRAM ready interrupt occurred on the Z Axis while the axis was ready. This will not stop the scan, but indicates a communication problem between the GAP and the GRAM."
Extended Error: If this problem occurs, it is probably intermittent. This will be a difficult problem to diagnose.
If this error occurs, then the GAP, MIF, GRAM and cables between the them are suspect. Swapping MIF Modules is a possibility so that the error can be tracked to see if it moves. If the problem moves, then the MIF Module is the problem. Cables can also be swapped. The GRAM Modules can be swapped by using the GRAM Troubleshooting Harness (2144094). This harness cannot be used for system operation. It is only used for short term troubleshooting.
The GAP is a single item in the system and cannot be swapped. Currently, there are no diagnostics or tests to find this problem. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_ERASE_FAIL
"GAP flash memory error. Memory erase failed.
Address Given to Erase: 0x%06X
Contents of Address Location: 0x%08X
Please Reset TPS again. If error is persistent, the flash memory on the GAP Board might be bad."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_ERASE_FAIL_SEQ
"GAP flash memory error. Improper command sequence for erase.
Address Given to Erase: 0x%06X
Contents of Address Location: 0x%08X
Please Reset TPS again. If error is persistent, the flash memory on the GAP Board might be bad."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_ERASE_FAIL_TIMEOUT
"GAP flash memory error. Memory erase took too long and timed out.
Address Given to Erase: 0x%06X
Please Reset TPS again. If error is persistent, the flash memory on the GAP Board might be bad."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_ERASE_FAIL_VPP
"GAP flash memory error. Vpp not present to erase successfully.
Address Given to Erase: 0x%06X
Contents of Address Location: 0x%08X
Please Reset TPS again. If error is persistent, the flash memory on the GAP Board might be bad."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_PROGRAM_FAIL_SEQ
"GAP flash memory error. Improper command sequence for byte programming.
Address Given to Program: 0x%06X
Contents of Address Location: 0x%08X
Please Reset TPS again. If error is persistent, the flash memory on the GAP Board might be bad."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_PROGRAM_FAIL_TIMEOUT
"GAP flash memory error. Memory programming took too long and timed out.
Address Given to Program: 0x%06X
Please Reset TPS again. If error is persistent, the flash memory on
the GAP Board might be bad."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_PROGRAM_FAIL_VPP
"GAP flash memory error. Vpp not present to byte write successfully.
Address Given to Program: 0x%06X
Contents of Address Location: 0x%08X
Please Reset TPS again. If error is persistent, the flash memory on the GAP Board might be bad."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_NO_CLEAR
"Internal GAP software error. Invalid selection for clearing a MIF error bit.
MIF Selected to Clear: %d
If the GAP software is running okay ( the GAP Board LED is blinking within a period of 5 seconds ), then this is a software bug; write a CQA."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_NO_MASK
"Internal GAP software error. Invalid selection for setting or clearing a MIF mask bit.
MIF MASK Selected: %d
If the GAP software is running okay ( the GAP Board LED is blinking within a period of 5 seconds ), then this is a software bug; write a CQA."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_CLK_STOP
"Hardware Error - Gradients timed out.
A gradient clock stop occurred. The GAP stopped receiving the gradient clock from the IPG. Check the connection between the TYME Board and the GAP Board, then run fiber optic diagnostics."
Extended Error: This error condition can also be caused by the Gradient Data Clock Fiber Optic Cables or HSSD Cables being located in the wrong position . In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready either.
Also, if this error seems to be intermittent, and you are getting many other errors, and you have been Resetting TPS, or running Gradient Driver Tests, then, it is possible that IPG could not report all of the tests that have been generated. If this is the case, check the Gradient Data Cable connections to ensure that all, including the Gradient Clock, are in the correct location. When the errors come back from these tests, then check the last line in the error message that reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX" Notice that if all the error messages that read values are coming back with a value of 0v, or 0mV, then this is an indication the Gradient Clock may be missing.This could also indicate a power problem somewhere in this subsystem. check for things that are common to the axis that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_X_CLK_STOP
"X Axis MIF - Gradients timed out.
A gradient clock stop occurred. The MIF X axis stopped receiving the gradient clock. Check the HSSD connection between the GAP and the X Axis MIF."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Y_CLK_STOP
"Y Axis MIF - Gradients timed out.
A gradient clock stop occurred. The MIF Y axis stopped receiving the gradient clock. Check the HSSD connection between the GAP and the Y Axis MIF."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Z_CLK_STOP
"Z Axis MIF - Gradients timed out.
A gradient clock stop occurred. The MIF Z axis stopped receiving the gradient clock. Check the HSSD connection between the GAP and the Z Axis MIF."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_DATA_FRAMING
"Hardware Error - Gradient data framing error.
The GAP reported a data framing error. Check the connections between the TYME Board and the GAP Board."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_X_DATA_FRAMING
"X Axis MIF - Gradient data framing error.
The MIF X axis reported a power module data framing error. Check the HSSD connection between the GAP and the X Axis MIF."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Y_DATA_FRAMING
"Y Axis MIF - Gradient data framing error.
The MIF Y axis reported a power module data framing error. Check the HSSD connection between the GAP and the Y Axis MIF."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Z_DATA_FRAMING
"Z Axis MIF - Gradient data framing error.
The MIF Z axis reported a power module data framing error. Check the HSSD connection between the GAP and the Z Axis MIF."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_X_H_OVERLOAD
"X Axis Gradient Overload Occurred.
The X axis HIGH 8645 Power Module has reported an overload. An overload is the result of the power module output voltage not following the input command."
Extended Error: To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. If the ASM's are OK, and this is a system with a GRAM, then there is probably a GRAM current distortion error and/or an analog saturation error. If this error occurs during GRAM Tuning, then the VBUS (Bus Voltage Regulator) may not be set up correctly.(This calibration is in the GRAM Tuning procedure.) Adjust this parameter per the GRAM Tuning Calibration, and try again.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Y_H_OVERLOAD
"Y Axis Gradient Overload Occurred.
The Y axis HIGH 8645 Power Module has reported an overload. An overload is the result of the power module output voltage not following the input command."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Z_H_OVERLOAD
"Z Axis Gradient Overload Occurred.
The Z axis HIGH 8645 Power Module has reported an overload. An overload is the result of the power module output voltage not following the input command."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_X_L_OVERLOAD
"X Axis Gradient Overload Occurred.
The X axis LOW 8645 Power Module has reported an overload. An overload is the result of the power module output voltage not following the input command."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Y_L_OVERLOAD
"Y Axis Gradient Overload Occurred.
The Y axis LOW 8645 Power Module has reported an overload. An overload is the result of the power module output voltage not following the input command."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Z_L_OVERLOAD
"Z Axis Gradient Overload Occurred.
The Z axis LOW 8645 Power Module has reported an overload. An overload is the result of the power module output voltage not following the input command."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_X_FAILED_RECOVERY
"X Axis gradient error detected."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Y_FAILED_RECOVERY
"Y Axis gradient error detected."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Z_FAILED_RECOVERY
"Z Axis gradient error detected."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_X_FAILED_READY
"One or both of the X axis 8645 Power Modules failed to go to ready when commanded. Check the LED status on the X axis 8645s for a fault, the cable connections between the X axis MIF and the GAP, and power to the MIF and X axis power modules."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: M_GAP_AMP_Y_FAILED_READY
"One or both of the Y axis 8645 Power Modules failed to go to ready when commanded. Check the LED status on the Y axis 8645s for a fault, the cable connections between the Y axis MIF and the GAP, and power to the MIF and Y axis power modules."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: M_GAP_AMP_Z_FAILED_READY
"One or both of the Z axis 8645 Power Modules failed to go to ready when commanded. Check the LED status on the Z axis 8645s for a fault, the cable connections between the Z axis MIF and the GAP, and power to the MIF and Y axis power modules."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_X_H_FAILED_READY
"The X axis 8645 Power Module failed to go to ready when commanded. Check the LED status on the X axis 8645 for a fault, the cable connections between the X axis MIF and the GAP, and power to the MIF and X axis 8645."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Y_H_FAILED_READY
"The Y axis 8645 Power Module failed to go to ready when commanded. Check the LED status on the Y axis 8645 for a fault, the cable connections between the Y axis MIF and the GAP, and power to the MIF and Y axis 8645."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Z_H_FAILED_READY
"The Z axis 8645 Power Module failed to go to ready when commanded. Check the LED status on the Z axis 8645 for a fault, the cable connections between the Z axis MIF and the GAP, and power to the MIF and Z axis 8645."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_X_FAILED_STANDBY
"A X axis 8645 Power Module(s) failed to go to standby when commanded. Check the cable connections between the X axis MIF and the GAP, and power to the MIF and 8645s.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Y_FAILED_STANDBY
"A Y axis 8645 Power Module(s) failed to go to standby when commanded. Check the cable connections between the Y axis MIF and the GAP, and power to the MIF and 8645s.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Z_FAILED_STANDBY
"A Z axis 8645 Power Module(s) failed to go to standby when commanded. Check the cable connections between the Z axis MIF and the GAP, and power to the MIF and 8645s.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_X_H_FAILED_STANDBY
"The X axis 8645 Power Module failed to go to standby when commanded. Check the cable connections between the X axis MIF and the GAP, and power to the MIF and 8645.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Y_H_FAILED_STANDBY
"The Y axis 8645 Power Module failed to go to standby when commanded. Check the cable connections between the Y axis MIF and the GAP, and power to the MIF and 8645.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Z_H_FAILED_STANDBY
"The Z axis 8645 Power Module failed to go to standby when commanded. Check the cable connections between the Z axis MIF and the GAP, and power to the MIF and 8645.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_H_FAULT_SHLF_OVR_TMP
"The MIF is reporting a shelf over temperature fault on the X axis HIGH 8645 Power Module. Wait for the temperature to cool before trying to scan. Cooling time may be in excess of 5 minutes."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Y_H_FAULT_SHLF_OVR_TMP
"The MIF is reporting a shelf over temperature fault on the Y axis HIGH 8645 Power Module. Wait for the temperature to cool before trying to scan. Cooling time may be in excess of 5 minutes."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_H_FAULT_SHLF_OVR_TMP
"The MIF is reporting a shelf over temperature fault on the Z axis HIGH 8645 Power Module. Wait for the temperature to cool before trying to scan. Cooling time may be in excess of 5 minutes."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_L_FAULT_SHLF_OVR_TMP
"The MIF is reporting a shelf over temperature fault on the X axis LOW 8645 Power Module. Wait for the temperature to cool before trying to scan. Cooling time may be in excess of 5 minutes."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Y_L_FAULT_SHLF_OVR_TMP
"The MIF is reporting a shelf over temperature fault on the Y axis LOW 8645 Power Module. Wait for the temperature to cool before trying to scan. Cooling time may be in excess of 5 minutes."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_L_FAULT_SHLF_OVR_TMP
"The MIF is reporting a shelf over temperature fault on the Z axis LOW 8645 Power Module. Wait for the temperature to cool before trying to scan. Cooling time may be in excess of 5 minutes."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_H_FAULT_XFMR_OVR_TMP
"The MIF is reporting a transformer over temperature fault on the X axis HIGH 8645 Power Module. Wait for the temperature to cool before trying to scan. Cooling time may be in excess of 10 minutes."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Y_H_FAULT_XFMR_OVR_TMP
"The MIF is reporting a transformer over temperature fault on the Y axis HIGH 8645 Power Module. Wait for the temperature to cool before trying to scan. Cooling time may be in excess of 10 minutes."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_H_FAULT_XFMR_OVR_TMP
"The MIF is reporting a transformer over temperature fault on the Z axis HIGH 8645 Power Module. Wait for the temperature to cool before trying to scan. Cooling time may be in excess of 10 minutes."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_L_FAULT_XFMR_OVR_TMP
"The MIF is reporting a transformer over temperature fault on the X axis LOW 8645 Power Module. Wait for the temperature to cool before trying to scan. Cooling time may be in excess of 10 minutes."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Y_L_FAULT_XFMR_OVR_TMP
"The MIF is reporting a transformer over temperature fault on the Y axis LOW 8645 Power Module. Wait for the temperature to cool before trying to scan. Cooling time may be in excess of 10 minutes."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_L_FAULT_XFMR_OVR_TMP
"The MIF is reporting a transformer over temperature fault on the Z axis LOW 8645 Power Module. Wait for the temperature to cool before trying to scan. Cooling time may be in excess of 10 minutes."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_H_FAULT_XISTOR_FAULT
"The MIF is reporting a transistor fault on the X axis HIGH 8645 HIGH 8645 Power Module and try to scan.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Y_H_FAULT_XISTOR_FAULT
"The MIF is reporting a transistor fault on the Y axis HIGH 8645 Power Module. To clear the fault, power cycle the Y axis HIGH 8645 Power Module and try to scan.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_H_FAULT_XISTOR_FAULT
"The MIF is reporting a transistor fault on the Z axis HIGH 8645 Power Module. To clear the fault, power cycle the Z axis HIGH 8645 Power Module and try to scan.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_L_FAULT_XISTOR_FAULT
"The MIF is reporting a transistor fault on the X axis LOW 8645 Power Module. To clear the fault, power cycle the X axis LOW 8645 Power Module and try to scan.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Y_L_FAULT_XISTOR_FAULT
"The MIF is reporting a transistor fault on the Y axis LOW 8645 Power Module. To clear the fault, power cycle the Y axis LOW 8645 Power Module and try to scan.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_L_FAULT_XISTOR_FAULT
"The MIF is reporting a transistor fault on the Z axis LOW 8645 Power Module. To clear the fault, power cycle the Z axis LOW 8645 Power Module and try to scan.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_H_FAULT_HI_LINE_VOLT
"X axis HIGH 8645 Power Module Poly Phase Buck Module fault occurred. Possible causes: high line volt. or overtemp. Wait a few minutes for cooling, then power cycle 8645 to clear fault.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Y_H_FAULT_HI_LINE_VOLT
"Y axis HIGH 8645 Power Module Poly Phase Buck Module fault occurred. Possible causes: high line volt. or overtemp. Wait a few minutes for cooling, then power cycle 8645 to clear fault.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_H_FAULT_HI_LINE_VOLT
"Z axis HIGH 8645 Power Module Poly Phase Buck Module fault occurred. Possible causes: high line volt. or over temp. Wait a few minutes for cooling, then power cycle 8645 to clear fault.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_L_FAULT_HI_LINE_VOLT
"X axis LOW 8645 Power Module Poly Phase Buck Module fault occurred. Possible causes: high line volt. or over temp. Wait a few minutes for cooling, then power cycle 8645 to clear fault.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Y_L_FAULT_HI_LINE_VOLT
"Y axis LOW 8645 Power Module Poly Phase Buck Module fault occurred. Possible causes: high line volt. or overtemp. Wait a few minutes for cooling, then power cycle 8645 to clear fault.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_L_FAULT_HI_LINE_VOLT
"Z axis LOW 8645 Power Module Poly Phase Buck Module fault occurred. Possible causes: high line volt. or overtemp. Wait a few minutes for cooling, then power cycle 8645 to clear fault.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_H_FAULT_DIE_OVR_TMP_NOL
"The MIF is reporting a die over temperature fault on the X axis HIGH 8645 Power Module. A die over temperature is an indication that the power module output shelf is too hot and has momentarily shutdown to cool."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Y_H_FAULT_DIE_OVR_TMP_NOL
"The MIF is reporting a die over temperature fault on the Y axis HIGH 8645 Power Module. A die over temperature is an indication that the power module output shelf is too hot and has momentarily shutdown to cool."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_H_FAULT_DIE_OVR_TMP_NOL
"The MIF is reporting a die over temperature fault on the Z axis HIGH 8645 Power Module. A die over temperature is an indication that the power module output shelf is too hot and has momentarily shutdown to cool."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_L_FAULT_DIE_OVR_TMP_NOL
"The MIF is reporting a die over temperature fault on the X axis LOW 8645 Power Module. A die over temperature is an indication that the power module output shelf is too hot and has momentarily shutdown to cool."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Y_L_FAULT_DIE_OVR_TMP_NOL
"The MIF is reporting a die over temperature fault on the Y axis LOW 8645 Power Module. A die over temperature is an indication that the power module output shelf is too hot and has momentarily shutdown to cool."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_L_FAULT_DIE_OVR_TMP_NOL
"The MIF is reporting a die over temperature fault on the Z axis LOW 8645 Power Module. A die over temperature is an indication that the power module output shelf is too hot and has momentarily shutdown to cool."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_SERVICE_MODE
"The GAP couldn't command X axis 8645(s) ready because MIF is in SERVICE MODE. Move MIF slider switch S3 to GAP CONTROL and MIF switch S4, bits 1-5, up to disable SERVICE MODE. If SERVICE MODE is desired, put a `G' in the ipg_stage file and reset TPS."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Y_SERVICE_MODE
"The GAP couldn't command Y axis 8645(s) ready because MIF is in SERVICE MODE. Move MIF slider switch S3 to GAP CONTROL and MIF switch S4, bits 1-5, up to disable SERVICE MODE. If SERVICE MODE is desired, put a `G' in the ipg_stage file and reset TPS."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_SERVICE_MODE
"The GAP couldn't command Z axis 8645(s) ready because MIF is in SERVICE MODE. Move MIF slider switch S3 to GAP CONTROL and MIF switch S4, bits 1-5, up to disable SERVICE MODE. If SERVICE MODE is desired, put a `G' in the ipg_stage file and reset TPS."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_CURRENT_SUMMING
"The GAP could not command the X axis 8645(s) to ready. The X axis MIF indicates that current sense summing is on. Move the slider switch on the MIF Board to CURRENT SENSE SUMMING OFF before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Y_CURRENT_SUMMING
"The GAP could not command the Y axis 8645(s) to ready. The Y axis MIF indicates that current sense summing is on. Move the slider switch on the MIF Board to CURRENT SENSE SUMMING OFF before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_CURRENT_SUMMING
"The GAP could not command the Z axis 8645(s) to ready. The Z axis MIF indicates that current sense summing is on. Move the slider switch on the MIF Board to CURRENT SENSE SUMMING OFF before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_LOW_INVERTED
"The GAP could not command the X axis 8645(s) to ready. The X axis MIF indicates the drive signal to the LOW 8645 is not inverted. Move the slider switch on the MIF Board to CURRENT SENSE SUMMING OFF before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Y_LOW_INVERTED
"The GAP could not command the Y axis 8645(s) to ready. The Y axis MIF indicates the drive signal to the LOW 8645 is not inverted. Move the slider switch on the MIF Board to CURRENT SENSE SUMMING OFF before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_LOW_INVERTED
"The GAP could not command the Z axis 8645(s) to ready. The Z axis MIF indicates the drive signal to the LOW 8645 is not inverted. Move the slider switch on the MIF Board to CURRENT SENSE SUMMING OFF before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_LOAD_COMP
"The GAP could not command the X axis 8645(s) to ready. The X axis MIF indicates the load compensation is not 0. Change the LD CMP3 switch on the MIF before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Y_LOAD_COMP
"The GAP could not command the Y axis 8645(s) to ready. The Y axis MIF indicates the load compensation is not 0. Change the LD CMP3 switch on the MIF before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_LOAD_COMP
"The GAP could not command the Z axis 8645(s) to ready. The Z axis MIF indicates the load compensation is not 0. Change the LD CMP3 switch on the MIF before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_FULL_SCALE
"The GAP could not command the X axis 8645(s) to ready. The X axis MIF indicates the full scale output is not 200A. Change the FS 200 switch on the MIF before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Y_FULL_SCALE
"The GAP could not command the Y axis 8645(s) to ready. The Y axis MIF indicates the full scale output is not 200A. Change theFS 200 switch on the MIF before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_FULL_SCALE
"The GAP could not command the Z axis 8645(s) to ready. The Z axis MIF indicates the full scale output is not 200A. Change the FS 200 switch on the MIF before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_VOLTAGE_CTRL
"The GAP could not command the X axis 8645(s) to ready. The X axis MIF indicates a GRAM is not present and in VOLTAGE CONTROL mode. Change the CTRL V switch on the MIF to disable VOLTAGE CONTROL mode before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Y_VOLTAGE_CTRL
"The GAP could not command the Y axis 8645(s) to ready. The Y axis MIF indicates a GRAM is not present and in VOLTAGE CONTROL mode. Change the CTRL V switch on the MIF to disable VOLTAGE CONTROL mode before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_VOLTAGE_CTRL
"The GAP could not command the Z axis 8645(s) to ready. The Z axis MIF indicates a GRAM is not present and in VOLTAGE CONTROL mode. Change the CTRL V switch on the MIF to disable VOLTAGE CONTROL mode before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: M_GAP_MIF_X_ANALOG_VIN
"The GAP could not command the X axis 8645(s) to ready. The X axis MIF indicates a GRAM is not present and in ANALOG VIN mode. Change the ANALOG switch on the MIF to disable ANALOG VIN mode before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Y_ANALOG_VIN
"The GAP could not command the Y axis 8645(s) to ready. The Y axis MIF indicates a GRAM is not present and in ANALOG VIN mode. Change the ANALOG switch on the MIF to disable ANALOG VIN mode before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_ANALOG_VIN
"The GAP could not command the Z axis 8645(s) to ready. The Z axis MIF indicates a GRAM is not present and in ANALOG VIN mode. Change the ANALOG switch on the MIF to disable ANALOG VIN mode before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_MANUAL_ENABLE
"The GAP could not control the X axis 8645(s) because the MIF is in MANUAL READY. Move the MIF slider switch S3 to GAP CONTROL for software control of the 8645(s) or put a `G' in the ipg_stage file and reset TPS to avoid this and other messages."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_MANUAL_ENABLE
"The GAP could not control the Z axis 8645(s) because the MIF is in MANUAL READY. Move the MIF slider switch S3 to GAP CONTROL for software control of the 8645(s) or put a `G' in the ipg_stage file and reset TPS to avoid this and other messages."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_MANUAL_ENABLE
"The GAP could not control the Z axis 8645(s) because the MIF is in MANUAL READY. Move the MIF slider switch S3 to GAP CONTROL for software control of the 8645(s) or put a `G' in the ipg_stage file and reset TPS to avoid this and other messages."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_MANUAL_STANDBY
"The GAP could not control the X axis 8645(s) because the MIF is in MANUAL Control. Move the MIF slider switch S3 to GAP CONTROL for software control of the 8645(s) or put a `G' in the ipg_stage file and reset TPS to avoid this and other messages."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: M_GAP_MIF_Y_MANUAL_STANDBY
"The GAP could not control the Y axis 8645(s) because the MIF is in MANUAL Control. Move the MIF slider switch S3 to GAP CONTROL for software control of the 8645(s) or put a `G' in the ipg_stage file and reset TPS to avoid this and other messages."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_MANUAL_STANDBY
"The GAP could not control the Z axis 8645(s) because the MIF is in MANUAL Control. Move the MIF slider switch S3 to GAP CONTROL for software control of the 8645(s) or put a `G' in the ipg_stage file and reset TPS to avoid this and other messages."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_X_H_LONG_OVERLOAD
"The MIF is reporting a long overload on the X axis HIGH 8645 PowerModule. The LED on the 8645 for this fault should be lit. If the LED is not lit, check power and cable connections. To clear the fault, power cycle the X axis HIGH 8645 Power Module."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Y_H_LONG_OVERLOAD
"The MIF is reporting a long overload on the Y axis HIGH 8645 Power Module. The LED on the 8645 for this fault should be lit. If the LED is not lit, check power and cable connections. To clear the fault, power cycle the X axis HIGH 8645 Power Module."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Z_H_LONG_OVERLOAD
"The MIF is reporting a long overload on the Z axis HIGH 8645 Power Module. The LED on the 8645 for this fault should be lit. If the LED is not lit, check power and cable connections. To clear the fault, power cycle the X axis HIGH 8645 Power Module."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: M_GAP_AMP_X_L_LONG_OVERLOAD
"The MIF is reporting a long overload on the X axis LOW 8645 Power Module. The LED on the 8645 for this fault should be lit. If the LED is not lit, check power and cable connections. To clear the fault, power cycle the X axis HIGH 8645 Power Module."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Y_L_LONG_OVERLOAD
"The MIF is reporting a long overload on the Y axis LOW 8645 Power Module. The LED on the 8645 for this fault should be lit. If the LED is not lit, check power and cable connections. To clear the fault, power cycle the X axis HIGH 8645 Power Module."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Z_L_LONG_OVERLOAD
"The MIF is reporting a long overload on the Z axis LOW 8645 Power Module. The LED on the 8645 for this fault should be lit. If the LED is not lit, check power and cable connections. To clear the fault, power cycle the X axis HIGH 8645 Power Module."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_X_RECOVERY_DONE
"The gradient system on the X axis recovered successfully.
There are no faults at the present time."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Y_RECOVERY_DONE
"The gradient system on the Y axis recovered successfully.
There are no faults at the present time."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Z_RECOVERY_DONE
"The gradient system on the Z axis recovered successfully.
There are no faults at the present time."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_X_H_POWER
"Check X Axis HIGH 8645 Power Module Power
The X Axis HIGH 8645 Power Module is reporting all its faults to the MIF.
This is most likely caused by power loss to the power module."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Y_H_POWER
"Check Y Axis HIGH 8645 Power Module Power.
The Y Axis HIGH 8645 Power Module is reporting all its faults to the MIF.
This is most likely caused by power loss to the power module."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Z_H_POWER
"Check Z Axis HIGH 8645 Power Module Power.
The Z Axis HIGH 8645 Power Module is reporting all its faults to the MIF.
This is most likely caused by power loss to the power module."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_X_L_POWER
"Check X Axis Low 8645 Power Module Power.
The X Axis Low 8645 Power Module is reporting all its faults to the MIF.
This is most likely caused by power loss to the power module."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Y_L_POWER
"Check Y Axis Low 8645 Power Module Power.
The Y Axis Low 8645 Power Module is reporting all its faults to the MIF.
This is most likely caused by power loss to the power module."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_Z_L_POWER
"Check Z Axis Low 8645 Power Module Power.
The Z Axis Low 8645 Power Module is reporting all its faults to the MIF.
This is most likely caused by power loss to the power module."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_X_POWER
"Check X Axis MIF Power.
All the X Axis MIF registers are zero.
This is most likely caused by power loss to the MIF."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Y_POWER
"Check Y Axis MIF Power.
All the Y Axis MIF registers are zero.
This is most likely caused by power loss to the MIF."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_Z_POWER
"Check Z Axis MIF Power.
All the Z Axis MIF registers are zero.
This is most likely caused by power loss to the MIF."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_MIF_FAULT_HI_LINE_VOLT
"Possible causes: high line volt. or overtemp. Wait a few minutes for cooling, then turn 8645 power off for 30 seconds to clear error. After 30 seconds, turn 8645 power back on. Try to scan. If Main Control Board LED is lit again, replace PPBM."
<srv,myhost,log>
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_AMP_CLK_STOP_MORE_INFO
"If another error message appears in log indicating a clock stop occurred because the GAP stopped receiving the clock from IPG, check the connection between the TYME Board and the GAP Board first."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_ASM_SET_CHANNEL_A_CONFLICT
"Internal GAP software error. Selecting the ADC channel A conflicts with the current selection for channel B. If this error is seen in the field, please write a CQA. Desired Channel A Signal: %d
Current Channel B Signal: %d"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_ASM_SET_CHANNEL_A_CONFLICT
"Internal GAP software error. Selecting the ADC channel A conflicts with the current selection for channel B. If this error is seen in the field, please write a CQA.
Desired Channel A Signal: %d
Current Channel B Signal: %d"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_ASM_SET_CHANNEL_A_CONFLICT
"Internal GAP software error. Unavailable signal for selection on
channel A. If this error is seen in the field, please write a CQA.
Desired Channel A Signal: %d"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_ASM_NO_SET_CHANNEL_B
"Internal GAP software error. Unavailable signal for selection on channel B. If this error is seen in the field, please write a CQA.
Desired Channel B Signal: %d"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_IOUT_H_ERROR
"ASM IOUT_H Monitoring Error.
Output Current on High Side 8645 Power Module has exceeded the maximum range allowed. Low: %6da High: %6da Value: %6da axis: %c Standby/Ready State: %c"
Extended Error: To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_PXTEMP_H_ERROR
"ASM PXTEMP_H Monitoring Error.
The temperature of the positive transistors wells on the High Side 8645 Power Module is out of range. Check fan, blocked air flow or try different PSD. Low: %6dC High: %6dC Value: %6dC axis: %c Standby/Ready State: %c"
Extended Error: To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_NXTEMP_H_ERROR
"ASM NXTEMP_H Monitoring Error.
The temperature of the negative transistors wells on the High Side 8645 Power Module is out of range. Check fan, blocked air flow or try different PSD. Low: %6dC High: %6dC Value: %6dC axis: %c Standby/Ready State: %c"
Extended Error: To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_XFTEMP_H_ERROR
"ASM XFTEMP_H Monitoring Error.
Transformer temperature on the High Side 8645 Power Module is out of range Check for operational fan, blocked air flow or try different PSD. Low: %6dC High: %6dC Value: %6dC axis: %c Standby/Ready State: %c"
Extended Error: To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_VOUT_H_ERROR
"ASM VOUT_H Monitoring Error. The output voltage has exceeded the allowed range on the High Side 8645 Power Module. Low: %6dv High: %6dv Value: %6dv axis: %c Standby/Ready State: %c"
Extended Error: To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_VCC_H_ERROR
"ASM VCC_H Error.
The ASM is reporting that the PPBM voltage has exceeded the allowed range on the High Side 8645 Power Module. Possible causes: PPBM, main board, output shelf, or ASM. Low: %6dv High: %6dv Value: %6dv axis: %c Standby/Ready State: %c"
Extended Error: This is a Hardware only fault. To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_ITOT_ERROR
"ASM ITOT Monitoring Error.
Output Current has exceeded the maximum range allowed.
Low: %6da High: %6da Value: %6da axis: %c Standby/Ready State: %c"
Extended Error: This is a Hardware only fault. To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_VMIF_ERROR
"ASM VMIF Monitoring Error.
The Commanded voltage to the power module(s) has exceeded the maximum allowed range.
Low: %6dv High: %6dv Value: %6dv axis: %c Standby/Ready State: %c"
Extended Error: This is a Hardware only fault. To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_AGND_ERROR
"ASM AGND is out of range.
Re-seat the ASM, if problem persists swap ASM axis. If problem moves to new axis, replace ASM, else replace MIF chassis on faulted axis.
Low: %6dmv High: %6dmv Value: %6dmv axis: %c"
Extended Error: This is a Hardware only fault. To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_V_1_235_ERROR
"ASM V_1_235 is out of range.
Re-seat the ASM, if problem persists swap ASM axis. If problem moves to new axis, replace ASM, else replace MIF chassis on faulted axis.
Low: %6dmv High: %6dmv Value: %6dmv axis: %c"
Extended Error: This is a Hardware only fault. To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_DIG_5V_REF_ERROR
"ASM DIG_5V_REF is out of range. Re-seat the ASM, if problem persists swap ASM axis. If problem moves to new axis, replace ASM, else replace MIF chassis on faulted axis.
Low: %6dmv High: %6dmv Value: %6dmv axis: %c"
Extended Error: This is a Hardware only fault. To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_REF_15V_ERROR
"ASM REF_15V is out of range.
Re-seat the ASM, if problem persists swap ASM axis. If problem moves to new axis, replace ASM, else replace MIF chassis on faulted axis.
Low: %6dmv High: %6dmv Value: %6dmv axis: %c"
Extended Error: This is a Hardware only fault. To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_REF_5V_ERROR
"ASM REF_5V is out of range.
Re-seat the ASM, if problem persists swap ASM axis. If problem moves to new axis, replace ASM, else replace MIF chassis on faulted axis.
Low: %6dmv High: %6dmv Value: %6dmv axis: %c"
Extended Error: This is a Hardware only fault. To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_IOUT_L_ERROR
"ASM IOUT_H Monitoring Error.
Output Current on Low Side 8645 Power Module has exceeded the maximum range allowed.
Low: %6da High: %6da Value: %6da axis: %c Standby/Ready State: %c"
Extended Error: This is a Hardware only fault. To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_PXTEMP_L_ERROR
"ASM PXTEMP_H Monitoring Error.
The temperature of the positive transistors wells on the Low Side 8645 Power Module is out of range. Check fan, blocked air flow or try different PSD. Low: %6dC High: %6dC Value: %6dC axis: %c Standby/Ready State: %c"
Extended Error: This is a Hardware only fault. To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_NXTEMP_L_ERROR
"ASM NXTEMP_L Monitoring Error.
The temperature of the negative transistors wells on the Low Side 8645 Power Module is out of range. Check fan, blocked air flow or try different PSD. Low: %6dC High: %6dC Value: %6dC axis: %c Standby/Ready State: %c"
Extended Error: This is a Hardware only fault. To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_XFTEMP_L_ERROR
"ASM XFTEMP_L Monitoring Error.
Transformer temperature on the Low Side 8645 Power Module is out of range. Check for operational fan, blocked air flow or try a different PSD. Low: %6dC High: %6dC Value: %6dC axis: %c Standby/Ready State: %c"
Extended Error: This is a Hardware only fault. To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_VOUT_L_ERROR
"ASM VOUT_L Monitoring Error.
The output voltage has exceeded the allowed range on the Low Side 8645 Power Module.
Low: %6dv High: %6dv Value: %6dv axis: %c Standby/Ready State: %c"
Extended Error: This is a Hardware only fault. To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_RTM_VCC_L_ERROR
"ASM VCC_L Error.
The ASM is reporting that the PPBM voltage has exceeded the allowed range on the High Side 8645 Power Module. Possible causes: PPBM, main board, output shelf, or ASM. Low: %6dv High: %6dv Value: %6dv axis: %c Standby/Ready State: %c"
Extended Error: This is a Hardware only fault. To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_NO_MASK
"Internal GAP software error. Invalid selection for setting or clearing a GRAM mask bit. GRAM Mask Selected: %d. If the GAP software is running okay ( the GAP Board LED is blinking within a period of 5 seconds ), then this is a software bug; write a CQA."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_CLK_STOP
"X Axis GRAM - Gradients timed out.
A gradient clock stop occurred. The GRAM X axis stopped receiving the gradient clock. Check MIF to GRAM communication cable and GAP to MIF HSSD cable. If another error message appears in log indicating a clock stop occurred because the GAP stopped receiving the clock from IPG, check the connection between the TYME Board and the GAP Board first"
Extended Error: It is possible for the MIF cable to pick up noise from adjoining circuitry or cables. This noise can cause the gradient clock stop error to occur. Check for MIF to GRAM and GAP to MIF cabling touching or near circuitry that could be a source of noise. It is possible for the MIF cable to pick up noise from adjoining circuitry or cables. This noise can cause the gradient clock stop error to occur. Check for MIF to GRAM and GAP to MIF cabling touching or near circuitry that could be a source of noise. Using a scope and scoping these signals can be useful in determining if propagation delay is being built up over this circuit. Possible causes can be the cables themselves. For details on troubleshooting this Gradient Bits problem, use the functional block diagrams to trace the gradient bits data path.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_CLK_STOP
"Y Axis GRAM - Gradients timed out.
A gradient clock stop occurred. The GRAM Y axis stopped receiving the gradient clock. Check MIF to GRAM communication cable and GAP to MIF HSSD cable. If another error message appears in log indicating a clock stop occurred because the GAP stopped receiving the clock from IPG, check the connection between the TYME Board and the GAP Board first"
Extended Error: It is possible for the MIF cable to pick up noise from adjoining circuitry or cables. This noise can cause the gradient clock stop error to occur. Check for MIF to GRAM and GAP to MIF cabling touching or near circuitry that could be a source of noise. Also, it is possible to generate this problem if the circuitry is causing enough of a delay so that the gradient clock signal is reduced in width. A delay can propagate through the cabling and MIF Board to cause this problem. Using a scope and scoping these signals can be useful in determining if propagation delay is being built up over this circuit. Possible causes can be the cables themselves. For details on troubleshooting this Gradient Bits problem, use the functional block diagrams to trace the gradient bits data path.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_CLK_STOP
"Z Axis GRAM - Gradients timed out.
A gradient clock stop occurred. The GRAM Z axis stopped receiving the gradient clock. Check MIF to GRAM communication cable and GAP to MIF HSSD cable. If another error message appears in log indicating a clock stop occurred because the GAP stopped receiving the clock from IPG, check the connection between the TYME Board and the GAP Board first"
Extended Error: It is possible for the MIF cable to pick up noise from adjoining circuitry or cables. This noise can cause the gradient clock stop error to occur. Check for MIF to GRAM and GAP to MIF cabling touching or near circuitry that could be a source of noise. Also, it is possible to generate this problem if the circuitry is causing enough of a delay so that the gradient clock signal is reduced in width. A delay can propagate through the cabling and MIF Board to cause this problem. Using a scope and scoping these signals can be useful in determining if propagation delay is being built up over this circuit. Possible causes can be the cables themselves. For details on troubleshooting this Gradient Bits problem, use the functional block diagrams to trace the gradient bits data path.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_DATA_FRAMING
"X Axis GRAM - Gradient data framing error.
The GRAM X axis reported a GRAM data framing error. Check MIF to GRAM communication cable and GAP to MIF HSSD cable. If another error message appears in log indicating a clock stop occurred because the GAP stopped receiving the clock from IPG, check the connection between the TYME Board and the GAP Board first"
Extended Error: It is possible for the MIF cable to pick up noise from adjoining circuitry or cables. This noise can cause the gradient clock stop error to occur. Check for MIF to GRAM and GAP to MIF cabling touching or near circuitry that could be a source of noise. Also, it is possible to generate this problem if the circuitry is causing enough of a delay so that the gradient clock signal is reduced in width. A delay can propagate through the cabling and MIF Board to cause this problem. Using a scope and scoping these signals can be useful in determining if propagation delay is being built up over this circuit. Possible causes can be the cables themselves. For details on troubleshooting this Gradient Bits problem, use the functional block diagrams to trace the gradient bits data path.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_DATA_FRAMING
"Y Axis GRAM - Gradient data framing error.
The GRAM Y axis reported a GRAM data framing error. Check MIF to GRAM communication cable and GAP to MIF HSSD cable. If another error message appears in log indicating a clock stop occurred because the GAP stopped receiving the clock from IPG, check the connection between the TYME Board and the GAP Board first"
Extended Error: It is possible for the MIF cable to pick up noise from adjoining circuitry or cables. This noise can cause the gradient clock stop error to occur. Check for MIF to GRAM and GAP to MIF cabling touching or near circuitry that could be a source of noise. Also, it is possible to generate this problem if the circuitry is causing enough of a delay so that the gradient clock signal is reduced in width. A delay can propagate through the cabling and MIF Board to cause this problem. Using a scope and scoping these signals can be useful in determining if propagation delay is being built up over this circuit. Possible causes can be the cables themselves. For details on troubleshooting this Gradient Bits problem, use the functional block diagrams to trace the gradient bits data path.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_DATA_FRAMING
"Z Axis GRAM - Gradient data framing error.
The GRAM Z axis reported a GRAM data framing error. Check MIF to GRAM communication cable and GAP to MIF HSSD cable. If another error message appears in log indicating a clock stop occurred because the GAP stopped receiving the clock from IPG, check the connection between the TYME Board and the GAP Board first"
Extended Error: It is possible for the MIF cable to pick up noise from adjoining circuitry or cables. This noise can cause the gradient clock stop error to occur. Check for MIF to GRAM and GAP to MIF cabling touching or near circuitry that could be a source of noise. Also, it is possible to generate this problem if the circuitry is causing enough of a delay so that the gradient clock signal is reduced in width. A delay can propagate through the cabling and MIF Board to cause this problem. Using a scope and scoping these signals can be useful in determining if propagation delay is being built up over this circuit. Possible causes can be the cables themselves. For details on troubleshooting this Gradient Bits problem, use the functional block diagrams to trace the gradient bits data path.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_ANALOG_SATURATION
"X Axis GRAM Overload Occurred.
Image may contain artifacts. The X axis GRAM has reported an overload from analog saturation. The PSD may have violated ampere transitions per second rating."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_ANALOG_SATURATION
"Y Axis GRAM Overload Occurred.
Image may contain artifacts.
The Y axis GRAM has reported an overload from analog saturation. The PSD may have violated ampere transitions per second rating."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_ANALOG_SATURATION
"Z Axis GRAM Overload Occurred.
Image may contain artifacts.
The Z axis GRAM has reported an overload from analog saturation. The PSD may have violated ampere transitions per second rating."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_OVERFLOW
"X Axis GRAM Overload Occurred.
Image may contain artifacts.
The X axis GRAM has reported an overload from overflow. The PSD may have violated slew rate limits or the X GRAM Control Board has been reset by noise."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_OVERFLOW
"Y Axis GRAM Overload Occurred.
Image may contain artifacts.
The Y axis GRAM has reported an overload from overflow. The PSD may have violated slew rate limits or the Y GRAM Control Board has been reset by noise."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_OVERFLOW
"Z Axis GRAM Overload Occurred.
Image may contain artifacts.
The Z axis GRAM has reported an overload from overflow. The PSD may have violated slew rate limits or the Z GRAM Control Board has been reset by noise."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_UNDERFLOW
"X Axis GRAM Overload Occurred.
Image may contain artifacts.
The X axis GRAM has reported an overload from underflow. The PSD may have violated slew rate limits or the X GRAM Control Board has been reset by noise."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_UNDERFLOW
"Y Axis GRAM Overload Occurred.
Image may contain artifacts.
The Y axis GRAM has reported an overload from underflow. The PSD may have violated slew rate limits or the Y GRAM Control Board has been reset by noise."
Extended Error: If you have been using an oscilloscope, or performing GRAM Tuning, it may be possible that you did not use power from the Filtered Service Outlet. It is critical to use this filtered outlet because noise from other sources of power can feed from the scope back into the GRAM Control Board causing calibrations and measurements to be extremely inaccurate. It is possible to get this error if this kind of noise has been introduced into the GRAM. If your oscilloscope uses a voltage other than the 120VAC from the Service Outlet, then try using a step up transformer plugged into this filtered service outlet. In this way, you have the advantage of the filtered service outlet at the correct voltage for your oscilloscope.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_UNDERFLOW
"Z Axis GRAM Overload Occurred.
Image may contain artifacts.
The Z axis GRAM has reported an overload from underflow. The PSD may have violated slew rate limits or the Z GRAM Control Board has been reset by noise."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_FAILED_READY
"The X axis GRAM or 8645 Power Modules failed to go to ready when commanded. Check the LED status on the 8645s and GRAM for a fault, and power and cables for the MIF, GRAM, and 8645s. Verify that the switch on the X axis GRAM is set to ENABLE."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_FAILED_READY
"The Y axis GRAM or 8645 Power Modules failed to go to ready when commanded. Check the LED status on the 8645s and GRAM for a fault, and power and cables for the MIF, GRAM, and 8645s. Verify that the switch on the Y axis GRAM is set to ENABLE."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_FAILED_READY
"The Z axis GRAM or 8645 Power Modules failed to go to ready when commanded. Check the LED status on the 8645s and GRAM for a fault, and power and cables for the MIF, GRAM, and 8645s. Verify that the switch on the Z axis GRAM is set to ENABLE."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_H_FAILED_READY
"The X axis GRAM or 8645 Power Module failed to go to ready when commanded. Check the LED status on the 8645 and GRAM for a fault, and power and cables for the MIF, GRAM, and 8645. Verify that the switch on the X axis GRAM is set to ENABLE."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_H_FAILED_READY
"The Y axis GRAM or 8645 Power Module failed to go to ready when commanded. Check the LED status on the 8645 and GRAM for a fault, and power and cables for the MIF, GRAM, and 8645. Verify that the switch on the Y axis GRAM is set to ENABLE."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_H_FAILED_READY
"The Z axis GRAM or 8645 Power Module failed to go to ready when commanded. Check the LED status on the 8645 and GRAM for a fault, and power and cables for the MIF, GRAM, and 8645. Verify that the switch on the Z axis GRAM is set to ENABLE."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_FAILED_STANDBY
"The X axis GRAM or 8645 Power Modules failed to go to standby when commanded. Check the cables and power for the X axis MIF, GRAM, and 8645s. The switch on the front of the X axis MIF should be in GAP CTRL. The GRAM MAN switch must be disabled."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_FAILED_STANDBY
"The Y axis GRAM or 8645 Power Modules failed to go to standby when commanded. Check the cables and power for the Y axis MIF, GRAM, and 8645s. The switch on the front of the Y axis MIF should be in GAP CTRL. The GRAM MAN switch must be disabled."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_FAILED_STANDBY
"The Z axis GRAM or 8645 Power Modules failed to go to standby when commanded. Check the cables and power for the Z axis MIF, GRAM, and 8645s. The switch on the front of the Z axis MIF should be in GAP CTRL. The GRAM MAN switch must be disabled."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_H_FAILED_STANDBY
"The X axis GRAM or 8645 Power Module failed to go to standby when commanded. Check the cables and power for the X axis MIF, GRAM, and 8645. The switch on the front of the X axis MIF should be in GAP CTRL. The GRAM MAN switch must be disabled."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_H_FAILED_STANDBY
"The Y axis GRAM or 8645 Power Module failed to go to standby when commanded. Check the cables and power for the Y axis MIF, GRAM, and 8645. The switch on the front of the Y axis MIF should be in GAP CTRL. The GRAM MAN switch must be disabled."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_H_FAILED_STANDBY
"The Z axis GRAM or 8645 Power Module failed to go to standby when commanded. Check the cables and power for the Z axis MIF, GRAM, and 8645. The switch on the front of the Z axis MIF should be in GAP CTRL. The GRAM MAN switch must be disabled."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_FAULT_AMPLIFIER_OVR_CURRNT
"The X axis GRAM is reporting an amplifier over current fault.
Try scan again once.
If error occurs again, try a standard spin echo with a larger FOV. If error persists, possible gradient driver fault."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_FAULT_AMPLIFIER_OVR_CURRNT
"The Y axis GRAM is reporting an amplifier over current fault.
Try scan again once.
If error occurs again, try a standard spin echo with a larger FOV. If error persists, possible gradient driver fault."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_FAULT_AMPLIFIER_OVR_CURRNT
"The Z axis GRAM is reporting an amplifier over current fault.
Try scan again once.
If error occurs again, try a standard spin echo with a larger FOV. If error persists, possible gradient driver fault."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_FAULT_MONITOR_OVR_CURRNT
"The X axis GRAM is reporting a coil over current fault.
Try scan again once.
If error occurs again, try a standard spin echo with a larger FOV. If error persists, possible gradient driver fault."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_FAULT_MONITOR_OVR_CURRNT
"The Y axis GRAM is reporting a coil over current fault.
Try scan again once.
If error occurs again, try a standard spin echo with a larger FOV. If error persists, possible gradient driver fault."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_FAULT_MONITOR_OVR_CURRNT
"The Z axis GRAM is reporting a coil over current fault.
Try scan again once.
If error occurs again, try a standard spin echo with a larger FOV. If error persists, possible gradient driver fault."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_FAULT_SHOOT_THRU
"The X axis GRAM is reporting a shoot thru fault.
If under voltage fault also occurred for this axis, possible fatal GRAM fault."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_FAULT_SHOOT_THRU
"The Y axis GRAM is reporting a shoot thru fault.
If under voltage fault also occurred for this axis, possible fatal GRAM fault."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_FAULT_SHOOT_THRU
"The Z axis GRAM is reporting a shoot thru fault.
If under voltage fault also occurred for this axis, possible fatal GRAM fault."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_FAULT_DC_OVR_CURRNT
"The X axis GRAM is reporting a DC current fault.
Please reset TPS. If problem persists, the PSD may be asking for more than 50 amperes for more than 1 second."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_FAULT_DC_OVR_CURRNT
"The Y axis GRAM is reporting a DC current fault.
Please reset TPS. If problem persists, the PSD may be asking for more than 50 amperes for more than 1 second."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_FAULT_DC_OVR_CURRNT
"The Z axis GRAM is reporting a DC current fault.
Please reset TPS. If problem persists, the PSD may be asking for more than 50 amperes for more than 1 second."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_FAULT_OVER_VOLTAGE
"The X axis GRAM is reporting an over voltage fault.
Try another PSD. Most likely cause is a slew rate violation. If problem persists, possible gradient driver fault."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_FAULT_OVER_VOLTAGE
"The Y axis GRAM is reporting an over voltage fault.
Try another PSD. Most likely cause is a slew rate violation. If problem persists, possible gradient driver fault."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_FAULT_OVER_VOLTAGE
"The Z axis GRAM is reporting an over voltage fault.
Try another PSD. Most likely cause is a slew rate violation. If problem persists, possible gradient driver fault."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_FAULT_UNDER_VOLTAGE
"The X axis GRAM is reporting an under voltage fault.
Most likely cause is PSD prescription with demanding parameters or GRAM Hardware Fault."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_FAULT_UNDER_VOLTAGE
"The Y axis GRAM is reporting an under voltage fault.
Most likely cause is PSD prescription with demanding parameters or GRAM Hardware Fault."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_FAULT_UNDER_VOLTAGE
"The Z axis GRAM is reporting an under voltage fault.
Most likely cause is PSD prescription with demanding parameters or GRAM Hardware Fault."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_FAULT_GRAM_WIRING_FAULT
"The X axis GRAM is reporting a wiring fault.
A cable internal or external to the GRAM is loose or disconnected. Check connections to the X GRAM Control Board."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_FAULT_GRAM_WIRING_FAULT
"The Y axis GRAM is reporting a wiring fault.
A cable internal or external to the GRAM is loose or disconnected. Check connections to the Y GRAM Control Board."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_FAULT_GRAM_WIRING_FAULT
"The Z axis GRAM is reporting a wiring fault.
A cable internal or external to the GRAM is loose or disconnected. Check connections to the Z GRAM Control Board."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_FAULT_IGBT_OVR_TMP
"The X axis GRAM is reporting an over temperature fault.
Possible causes: poor ventilation or PSD is exceeding the 100 ampere RMS rating of the GRAM."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_FAULT_IGBT_OVR_TMP
"The Y axis GRAM is reporting an over temperature fault.
Possible causes: poor ventilation or PSD is exceeding the 100 ampere RMS rating of the GRAM."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_FAULT_IGBT_OVR_TMP
"The Z axis GRAM is reporting an over temperature fault.
Possible causes: poor ventilation or PSD is exceeding the 100 ampere RMS rating of the GRAM."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_FAULT_AVG_OVR_CURRNT
"The X axis GRAM is reporting average over current fault.
Possible causes: PSD is requesting an average current of 80 amps for a few seconds, the percent PWM is above 25%%, the amp transitions/second is above 100,000 or a GRAM hardware fault exists."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_FAULT_AVG_OVR_CURRNT
"The Y axis GRAM is reporting average over current fault.
Possible causes: PSD is requesting an average current of 80 amps for a few seconds, the percent PWM is above 25%%, the amp transitions/second is above 100,000 or a GRAM hardware fault exists."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_FAULT_AVG_OVR_CURRNT
"The Z axis GRAM is reporting average over current fault.
Possible causes: PSD is requesting an average current of 80 amps for a few seconds, the percent PWM is above 25%%, the amp transitions/second is above 100,000 or a GRAM hardware fault exists."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_VOLTAGE_CTRL
"The GAP could not command the X axis 8645(s) to ready.
The X axis MIF indicates a GRAM is present and in CURRENT CONTROL mode. Change the CTRL V switch on the MIF to enable VOLTAGE CONTROL mode before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_VOLTAGE_CTRL
"The GAP could not command the Y axis 8645(s) to ready.
The Y axis MIF indicates a GRAM is present and in CURRENT CONTROL mode. Change the CTRL V switch on the MIF to enable VOLTAGE CONTROL mode before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_VOLTAGE_CTRL
"The GAP could not command the Z axis 8645(s) to ready.
The Z axis MIF indicates a GRAM is present and in CURRENT CONTROL mode. Change the CTRL V switch on the MIF to enable VOLTAGE CONTROL mode before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_ANALOG_VIN
"The GAP could not command the X axis 8645(s) to ready.
The X axis MIF indicates a GRAM is present and not in ANALOG VIN mode. Change the ANALOG switch on the MIF to enable ANALOG VIN mode before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_ANALOG_VIN
"The GAP could not command the Y axis 8645(s) to ready.
The Y axis MIF indicates a GRAM is present and not in ANALOG VIN mode. Change the ANALOG switch on the MIF to enable ANALOG VIN mode before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_ANALOG_VIN
"The GAP could not command the Z axis 8645(s) to ready.
The Z axis MIF indicates a GRAM is present and not in ANALOG VIN mode. Change the ANALOG switch on the MIF to enable ANALOG VIN mode before trying to command the 8645(s) to ready."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_FAULT_CURRENT_DISTORTED
"The X axis GRAM is reporting the current is distorted over a period of time. The current is not what the DAC is requesting. Possible gradient driver failure. Another GRAM fault reported in the log could be the cause of this fault."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_FAULT_CURRENT_DISTORTED
"The Y axis GRAM is reporting the current is distorted over a period of time.
The current is not what the DAC is requesting. Possible gradient driver failure. Another GRAM fault reported in the log could be the cause of this fault."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_FAULT_CURRENT_DISTORTED
"The Z axis GRAM is reporting the current is distorted over a period of time.
The current is not what the DAC is requesting. Possible gradient driver failure. Another GRAM fault reported in the log could be the cause of this fault."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_FAULT_POWER_SUPPLY
"The X axis GRAM is reporting a GRAM power supply failure."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_FAULT_POWER_SUPPLY
"The Y axis GRAM is reporting a GRAM power supply failure."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_FAULT_POWER_SUPPLY
"The Z axis GRAM is reporting a GRAM power supply failure."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_FAULT_GROUND_LOSS
"The X axis GRAM is reporting system ground loss. Check power cable between 8645 Gradient Cabinet and GRAM."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_FAULT_GROUND_LOSS
"The Y axis GRAM is reporting system ground loss. Check power cable between 8645 Gradient Cabinet and GRAM."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_FAULT_GROUND_LOSS
"The Z axis GRAM is reporting system ground loss. Check power cable between 8645 Gradient Cabinet and GRAM."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_READY_SERVICE_MODE
"The GAP couldn't control X axis 8645(s) and GRAM because the X axis GRAM is in MANUAL READY. For GAP control, move GRAM MAN dip switch on GRAM down to disable manual control. If manual control is desired put a `G' the ipg_stage file and reset TPS."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_READY_SERVICE_MODE
"The GAP couldn't control Y axis 8645(s) and GRAM because the Y axis GRAM is in MANUAL READY. For GAP control, move GRAM MAN dip switch on GRAM down to disable manual control. If manual control is desired put a `G' the ipg_stage file and reset TPS."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_READY_SERVICE_MODE
"The GAP couldn't control Z axis 8645(s) and GRAM because the Z axis GRAM is in MANUAL READY. For GAP control, move GRAM MAN dip switch on GRAM down to disable manual control. If manual control is desired put a `G' the ipg_stage file and reset TPS."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_STANDBY_SERVICE_MODE
"The GAP could not control X axis 8645(s) and GRAM because X axis GRAM is in MANUAL control. For GAP control, move GRAM ENABLE switch up and GRAM HVE, FW, and MAN switches down. If manual control is desired, put a `G' the ipg_stage file and reset TPS."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_STANDBY_SERVICE_MODE
"The GAP could not control Y axis 8645(s) and GRAM because Y axis GRAM is in MANUAL control. For GAP control, move GRAM ENABLE switch up and GRAM HVE, FW, and MAN switches down. If manual control is desired, put a `G' the ipg_stage file and reset TPS."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_STANDBY_SERVICE_MODE
"The GAP could not control Z axis 8645(s) and GRAM because Z axis GRAM is in MANUAL control. For GAP control, move GRAM ENABLE switch up and GRAM HVE, FW, and MAN switches down. If manual control is desired, put a `G' the ipg_stage file and reset TPS."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_HIGH_VOLTAGE
"The X Axis GRAM has not reached its operating level.
Check the data cable between the GAP and GRAM Control Board."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_HIGH_VOLTAGE
"The Y Axis GRAM has not reached its operating level.
Check the data cable between the GAP and GRAM Control Board."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_HIGH_VOLTAGE
"The Z Axis GRAM has not reached its operating level.
Check the data cable between the GAP and GRAM Control Board."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_POWER
"Check X Axis GRAM Power.
All the X Axis GRAM registers are floating high.
This is most likely caused by power loss to the GRAM.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_POWER
"Check Y Axis GRAM Power.
All the Y Axis GRAM registers are floating high.
This is most likely caused by power loss to the GRAM."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_POWER
"Check Z Axis GRAM Power.
All the Z Axis GRAM registers are floating high.
This is most likely caused by power loss to the GRAM."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_FREEWHEEL
"X Axis GRAM is in Freewheel Mode.
The DIP switch labeled FW on the X Axis GRAM Control Board has been set."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_FREEWHEEL
"Y Axis GRAM is in Freewheel Mode.
The DIP switch labeled FW on the Y Axis GRAM Control Board has been set."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_FREEWHEEL
"Z Axis GRAM is in Freewheel Mode.
The DIP switch labeled FW on the Z Axis GRAM Control Board has been set."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_NO_DIGITAL_TUNE
"GAP was unsuccessful accessing X Axis GRAM Digital Tuning Board.
Check connections to X Axis GRAM Digital Tuning Board. If there is no GRAM, or all GRAMs have Analog Tuning Boards, change digiTuningBoard to `no' in the MRconfig.cfg file and reset TPS."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_NO_DIGITAL_TUNE
"GAP was unsuccessful accessing Y Axis GRAM Digital Tuning Board.
Check connections to Y Axis GRAM Digital Tuning Board. If there is no GRAM, or all GRAMs have Analog Tuning Boards, change digiTuningBoard to `no' in the MRconfig.cfg file and reset TPS."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_NO_DIGITAL_TUNE
"GAP was unsuccessful accessing Z Axis GRAM Digital Tuning Board.
Check connections to Z Axis GRAM Digital Tuning Board. If there is no GRAM, or all GRAMs have Analog Tuning Boards, change digiTuningBoard to `no' in the MRconfig.cfg file and reset TPS."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_TUNE_VERIFY
"The GAP was unsuccessful communicating with the X Axis GRAM Digital Tuning Board. Possible causes are failed Digital Tuning Board, GRAM Control Board or Connectors. After checking connections, please reset TPS and try to scan."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_TUNE_VERIFY
"The GAP was unsuccessful communicating with the Y Axis GRAM Digital Tuning Board. Possible causes are failed Digital Tuning Board, GRAM Control Board or Connectors. After checking connections, please reset TPS and try to scan."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_TUNE_VERIFY
"The GAP was unsuccessful communicating with the Z Axis GRAM Digital Tuning Board. Possible causes are failed Digital Tuning Board, GRAM Control Board or Connectors. After checking connections, please reset TPS and try to scan."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_X_NO_FREEWHEEL
"X Axis GRAM is no longer in Freewheel Mode.
The DIP switch labeled FW on the X Axis GRAM Control Board has been disabled."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Y_NO_FREEWHEEL
"Y Axis GRAM is no longer in Freewheel Mode.
The DIP switch labeled FW on the Y Axis GRAM Control Board has been disabled."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_Z_NO_FREEWHEEL
"Z Axis GRAM is no longer in Freewheel Mode.
The DIP switch labeled FW on the Z Axis GRAM Control Board has been disabled."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GASM_SET_CHANNEL_A_CONFLICT
"Internal GAP software error. Selecting the GASM ADC channel A conflicts with the current selection for channel B. If this error is seen in the field, please write a CQA. Desired Channel A Signal: %d Current Channel B Signal: %d"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GASM_SET_CHANNEL_B_CONFLICT
"Internal GAP software error. Selecting the GASM ADC channel B conflicts with the current selection for channel A. If this error is seen in the field, please write a CQA. Desired Channel A Signal: %d Current Channel B Signal: %d"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GASM_NO_SET_CHANNEL_A
"Internal GAP software error. Unavailable signal for selection on GASM channel A. If this error is seen in the field, please write a CQA. Desired Channel A Signal: %d"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GASM_NO_SET_CHANNEL_B
"Internal GAP software error. Unavailable signal for selection on GASM channel B. If this error is seen in the field, please write a CQA. Desired Channel B Signal: %d"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRTM_V_BUS_0_ERROR
"GASM V_BUS +HI Monitoring Error.
The GRAM VBUS +HI voltage is not within the allowed range.
Low: %6dv High: %6dv Value: %6dv axis: %c Standby/Ready State: %c"
Extended Error: To make sure that you are not looking at faulty sensing from the GASM Board, try swapping the GASM Board for the axis with the fault with an GASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the GASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRTM_V_BUS_1_ERROR
"GASM V_BUS +LO Monitoring Error.
The GRAM VBUS +LO voltage is not within the allowed range.
Low: %6dv High: %6dv Value: %6dv axis: %c Standby/Ready State: %c"
Extended Error: To make sure that you are not looking at faulty sensing from the GASM Board, try swapping the GASM Board for the axis with the fault with an GASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the GASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRTM_V_BUS_2_ERROR
"GASM V_BUS -HI Monitoring Error.
The GRAM VBUS -HI voltage is not within the allowed range.
Low: %6dv High: %6dv Value: %6dv axis: %c Standby/Ready State: %c"
Extended Error: To make sure that you are not looking at faulty sensing from the GASM Board, try swapping the GASM Board for the axis with the fault with an GASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the GASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRTM_V_BUS_3_ERROR
"GASM V_BUS -LO Monitoring Error.
The GRAM VBUS -LO voltage is not within the allowed range.
Low: %6dv High: %6dv Value: %6dv axis: %c Standby/Ready State: %c"
Extended Error: To make sure that you are not looking at faulty sensing from the GASM Board, try swapping the GASM Board for the axis with the fault with an GASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the GASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRTM_V_FILT_ERROR
"GASM V_FILT Monitoring Error.
The GASM has reported that the V_FILT voltage is out of range. Possible causes are: GASM, Tuning Board, Tuning Board Adjustment or GRAM. Low: %6dv High: %6dv Value: %6dv axis: %c Standby/Ready State: %c"
Extended Error: To make sure that you are not looking at faulty sensing from the GASM Board, try swapping the GASM Board for the axis with the fault with an GASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the GASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRTM_V_REG_F_ERROR
"GASM V_REG_F Monitoring Error.
The GASM has reported that the V_REG voltage is out of range. Possible causes are GASM or GRAM. Low: %6dmv High: %6dmv Value: %6dmv axis: %c Standby/Ready State: %c"
Extended Error: To make sure that you are not looking at faulty sensing from the GASM Board, try swapping the GASM Board for the axis with the fault with an GASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the GASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRTM_I_COIL_ERROR
"GASM I_COIL Monitoring Error.
The GASM has reported that the I_COIL current is out of range. Possible causes are: GASM, Tuning Board, Tuning Board adjustment or GRAM. Low: %6da High: %6da Value: %6da axis: %c Standby/Ready State: %c"
Extended Error: To make sure that you are not looking at faulty sensing from the GASM Board, try swapping the GASM Board for the axis with the fault with an GASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the GASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRTM_AGND_ERROR
"GASM AGND is out of range. Re-seat the cables on the GASM, if problem persists swap GASM axis. If problem moves to new axis, replace GASM, else replace GRAM. Low: %6dmv High: %6dv Value: %6dmv axis: %c"
Extended Error: To make sure that you are not looking at faulty sensing from the GASM Board, try swapping the GASM Board for the axis with the fault with an GASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the GASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRTM_V_1_235_ERROR
"GASM 1.235 volt reference is out of range.
Re-seat the cables on the GASM, if problem persists swap GRAM axis. If problem moves to new axis, replace GASM, else replace GRAM. Low: %6dmv High: %6dmv Value: %6dmv axis: %c"
Extended Error: To make sure that you are not looking at faulty sensing from the GASM Board, try swapping the GASM Board for the axis with the fault with an GASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the GASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRTM_VCC_REF_ERROR
"GASM VCC_REF is out of range.
Re-seat the cables on the GASM, if problem persists swap GASM axis. If problem moves to new axis, replace GASM, else replace GRAM. Low: %6dmv High: %6dmv Value: %6dmv axis: %c"
Extended Error: To make sure that you are not looking at faulty sensing from the GASM Board, try swapping the GASM Board for the axis with the fault with an GASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the GASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRTM_REF_15V_ERROR
"GASM REF_15V is out of range.
Re-seat the cables on the GASM, if problem persists swap GASM axis. If problem moves to new axis, replace GASM, else replace GRAM. Low: %6dmv High: %6dmv Value: %6dmv axis: %c"
Extended Error: To make sure that you are not looking at faulty sensing from the GASM Board, try swapping the GASM Board for the axis with the fault with an GASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the GASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRTM_5V_REF_ERROR
"GASM 5V_REF is out of range.
Re-seat the cables on the GASM, if problem persists swap GASM axis. If problem moves to new axis, replace GASM, else replace GRAM. Low: %6dmv High: %6dmv Value: %6dmv axis: %c"
Extended Error: To make sure that you are not looking at faulty sensing from the GASM Board, try swapping the GASM Board for the axis with the fault with an GASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the GASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRTM_NOT_USED_ERROR
"Not used, if seen in the field, please write a CQA."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_X_GRAM_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates a X axis GRAM is present, but the DIP switch on the front of the MIF is not set. The GAP software is not controlling the GRAM, but analog Vin and voltage control are set in GRAM mode."
Extended Error: If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. Swap the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. If the problem stays on the same axis, try swapping the GASM Board for the axis with the fault with a GASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the GASM Board is bad. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_X_NO_GRAM_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates a X axis GRAM is not present, but the DIP switch on the front of the MIF is set. If there is a X axis GRAM, change the MRconfig.cfg file. If there is not a GRAM, change the DIP switch."
Extended Error: If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. Swap the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. If the problem stays on the same axis, try swapping the GASM Board for the axis with the fault with a GASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the GASM Board is bad. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Y_GRAM_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR.
The MRconfig.cfg file indicates a Y axis GRAM is present, but the DIP switch on the front of the MIF is not set. The GAP software is not controlling the GRAM, but analog Vin and voltage control are set in GRAM mode."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. Swap the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. If the problem stays on the same axis, try swapping the GASM Board for the axis with the fault with a GASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the GASM Board is bad. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Y_NO_GRAM_CONFIG_ERROR
GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates a Y axis GRAM is not present, but the DIP switch on the front of the MIF is set. If there is a Y axis GRAM, change the MRconfig.cfg file. If there is not a GRAM, change the DIP switch."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. Swap the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. If the problem stays on the same axis, try swapping the GASM Board for the axis with the fault with a GASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the GASM Board is bad. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Z_GRAM_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates a Z axis GRAM is present, but the DIP switch on the front of the MIF is not set. The GAP software is not controlling the GRAM, but analog Vin and voltage control are set in GRAM mode."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. Swap the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. If the problem stays on the same axis, try swapping the GASM Board for the axis with the fault with a GASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the GASM Board is bad. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Z_NO_GRAM_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates a Z axis GRAM is not present, but the DIP switch on the front of the MIF is set. If there is a Z axis GRAM, change the MRconfig.cfg file. If there is not a GRAM, change the DIP switch."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. Swap the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. If the problem stays on the same axis, try swapping the GASM Board for the axis with the fault with a GASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the GASM Board is bad. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_X_ASM_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates a X axis ASM is present, but the MIF hardware register reads no ASM is present. If an ASM is present, check the connections between the X axis MIF and ASM."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. If an ASM Board is present, and the configuration file is correct, check the functionality of the ASM Board by swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_X_NO_ASM_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates a X axis ASM is not present, but the MIF hardware register reads a ASM is present. Change the MRconfig.cfg file to indicate the presence of a X axis ASM."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. If an ASM Board is present, and the configuration file is correct, check the functionality of the ASM Board by swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Y_ASM_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates a Y axis ASM is present, but the MIF hardware register reads no ASM is present. If an ASM is present, check the connections between the Y axis MIF and ASM."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. If an ASM Board is present, and the configuration file is correct, check the functionality of the ASM Board by swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Y_NO_ASM_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates a Y axis ASM is not present, but the MIF hardware register reads a ASM is present. Change the MRconfig.cfg file to indicate the presence of a Y axis ASM."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. If an ASM Board is present, and the configuration file is correct, check the functionality of the ASM Board by swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Z_ASM_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates a Z axis ASM is present, but the MIF hardware register reads no ASM is present. If an ASM is present, check the connections between the Z axis MIF and ASM."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. If an ASM Board is present, and the configuration file is correct, check the functionality of the ASM Board by swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Z_NO_ASM_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates a Z axis ASM is not present, but the MIF hardware register reads a ASM is present. Change the MRconfig.cfg file to indicate the presence of a Z axis ASM."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. If an ASM Board is present, and the configuration file is correct, check the functionality of the ASM Board by swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_X_GASM_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates a X axis GASM is present, but the GRAM hardware register reads no GASM is present. If an GASM is present, check the connections between the X axis GRAM and GASM."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. If an ASM Board is present, and the configuration file is correct, check the functionality of the ASM Board by swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_X_NO_GASM_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates a X axis GASM is not present, but the GRAM hardware register reads a GASM is present. Change the MRconfig.cfg file to indicate the presence of a X axis GASM."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. If an ASM Board is present, and the configuration file is correct, check the functionality of the ASM Board by swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Y_GASM_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates a Y axis GASM is present, but the GRAM hardware register reads no GASM is present. If an GASM is present, check the connections between the Y axis GRAM and GASM."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. If an ASM Board is present, and the configuration file is correct, check the functionality of the ASM Board by swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Y_NO_GASM_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates a Y axis GASM is present, but the GRAM hardware register reads no GASM is present. If an GASM is present, check the connections between the Y axis GRAM and GASM."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. If an ASM Board is present, and the configuration file is correct, check the functionality of the ASM Board by swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Z_GASM_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates a Z axis GASM is present, but the GRAM hardware register reads no GASM is present. If an GASM is present, check the connections between the Z axis GRAM and GASM."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. If an ASM Board is present, and the configuration file is correct, check the functionality of the ASM Board by swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Z_NO_GASM_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates a Z axis GASM is not present, but the GRAM hardware register reads a GASM is present. Change the MRconfig.cfg file to indicate the presence of a Z axis GASM."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. If an ASM Board is present, and the configuration file is correct, check the functionality of the ASM Board by swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_X_SERIES_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates the X axis is in series mode, but the DIP switch on the front of the MIF is not set. Change the DIP switch on the front of the X axis MIF for series mode."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_X_NO_SERIES_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates the X axis is not in series mode, and conflicts with the hardware configuration. Change the MRconfig.cfg file to indicate X axis series mode."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Y_SERIES_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates the Y axis is in series mode, but the DIP switch on the front of the MIF is not set. Change the DIP switch on the front of the Y axis MIF for series mode."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Y_NO_SERIES_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates the Y axis is not in series mode, and conflicts with the hardware configuration. Change the MRconfig.cfg file to indicate Y axis series mode."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Z_SERIES_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates the Z axis is in series mode, but the DIP switch on the front of the MIF is not set. Change the DIP switch on the front of the Z axis MIF for series mode."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Z_NO_SERIES_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR.
The MRconfig.cfg file indicates the Z axis is not in series mode, and conflicts with the hardware configuration. Change the MRconfig.cfg file to indicate Z axis series mode."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_X_DUAL_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates the X axis has two power modules, but the DIP switch on the front of the MIF is set for one power module. Change the MRconfig.cfg or DIP switch for the correct number of power modules."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_X_NO_DUAL_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates the X axis has one power module, but the DIP switch on the front of the MIF is set for two power modules. Change the MRconfig.cfg or DIP switch for the correct number of power modules."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Y_DUAL_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates the Y axis has two power modules, but the DIP switch on the front of the MIF is set for one power module. Change the MRconfig.cfg or DIP switch for the correct number of power modules."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Y_NO_DUAL_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates the Y axis has one power module, but the DIP switch on the front of the MIF is set for two power modules. Change the MRconfig.cfg or DIP switch for the correct number of power modules."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Z_DUAL_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates the Z axis has two power modules, but the DIP switch on the front of the MIF is set for one power module. Change the MRconfig.cfg or DIP switch for the correct number of power modules."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Z_NO_DUAL_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates the Z axis has one power module, but the DIP switch on the front of the MIF is set for two power modules. Change the MRconfig.cfg or DIP switch for the correct number of power modules."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_REAL_TIME_CONFIG_ERROR
"The MRconfig.cfg file indicates real time monitoring is desired, but the
GAP Software does not detect the presence of any ASMs or GASMs to perform
real time monitoring. Change the MRconfig.cfg file to avoid this message."
Extended Error: The system will not go Ready if a Configuration error is present. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_NO_REAL_TIME_CONFIG_ERROR
"The MRconfig.cfg file indicates real time monitoring is not enabled, but
the GAP Software detects the presence of ASM(s) and/or GASM(s). If real
time monitoring is desired, change the MRconfig.cfg file and reset TPS."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_X_GRAM_REV_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates the X axis GRAM is revision %d, but the GRAM Control Board indicates the revision is %d. Change the value for `xGram' in the MRconfig.cfg file to gram-%d and reset TPS."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Y_GRAM_REV_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates the Y axis GRAM is revision %d, but the GRAM Control Board indicates the revision is %d. Change the value for `yGram' in the MRconfig.cfg file to gram-%d and reset TPS."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_Z_GRAM_REV_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR. The MRconfig.cfg file indicates the Z axis GRAM is revision %d, but the GRAM Control Board indicates the revision is %d. Change the value for `zGram' in the MRconfig.cfg file to gram-%d and reset TPS."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GAP_GRAM_REV_CONFIG_ERROR
"GRADIENT CONFIGURATION ERROR.
The GRAM revision for all three GRAMs must be the same in order to scan. The GAP indicates the following revisions:
X GRAM Revision %d
Y GRAM Revision %d
Z GRAM Revision %d."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_MIF_POWER_OFF
"GRADIENT DRIVER TESTS - Power Up MIF %c Axis Register Pattern Test Failed. Power appears to be off. Possible causes: Cable between MIF & GAP, MIF board, or GAP board."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_ASM_POWER_OFF
"GRADIENT DRIVER TESTS - Power Up ASM %c Axis Register Pattern Test Failed. Power appears to be off. Re-seat the ASM, or check the MIF board, GAP board, and cable between MIF & GAP."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_GRAM_POWER_OFF
"GRADIENT DRIVER TESTS - Power Up GRAM %c Axis Register Pattern Test Failed. Power appears to be off. Possible causes: GRAM Power Supply, cable between GAP & GRAM, GRAM control board, GAP board, or the MIF DIP switch is set improperly."
Extended Error: Verify that the front MIF DIP switch that is marked "GRAM" is set properly. This DIP switch defines if a GRAM is present or if a GRAM is not present. If you do not have a GRAM and the switch is set improperly, Power Up Tests will try to execute on the non-existent GRAM and will produce many errors in the log. In this case, these errors will have no meaning.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_GASM_POWER_OFF
"GRADIENT DRIVER TESTS - Power Up GASM %c Axis Register Pattern Test Failed. Power appears to be off. Possible causes: GASM cable connections, the GASM board, the cable between the GAP & GRAM, the GAP board, or the MIF DIP switch is set improperly."
Extended Error: Verify that the front MIF DIP switch that is marked "GRAM" is set properly. This DIP switch defines if a GRAM is present or if a GRAM is not present. If you do not have a GRAM and the switch is set improperly, Power Up Tests will try to execute on the non-existent GRAM and will produce many errors in the log. In this case, these errors will have no meaning.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_MIF_DISCONNECTED
"GRADIENT DRIVER TESTS - Power Up Register Pattern Test Failed. The MIF appears to be disconnected or there is a cable problem on the %c Axis. Check the cables within the GAP module, or the cable between GAP & MIF."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_ASM_DISCONNECTED
"GRADIENT DRIVER TESTS - Power Up Register Pattern Test Failed. The ASM appears to be disconnected or there is a cable problem on the %c Axis. Check the cables within the GAP module, or the cable between GAP & MIF."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_GRAM_DISCONNECTED
"GRADIENT DRIVER TESTS - Power Up Register Pattern Test Failed. The GRAM appears to be disconnected or there is a cable problem on the %c Axis. Check the cables within the GAP module, or the cable between GAP & MIF. Verify the MIF DIP switch settings."
Extended Error: Verify that the front MIF DIP switch that is marked "GRAM" is set properly. This DIP switch defines if a GRAM is present or if a GRAM is not present. If you do not have a GRAM and the switch is set improperly, Power Up Tests will try to execute on the non-existent GRAM and will produce many errors in the log. In this case, these errors will have no meaning.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_GASM_DISCONNECTED
"GRADIENT DRIVER TESTS - Power Up Register Pattern Test Failed. GASM appears to be disconnected or there is a cable problem on the %c Axis. Check GASM cable connections, cable between GAP & GRAM, cables within GAP module, and MIF DIP switch settings."
Extended Error: Verify that the front MIF DIP switch that is marked "GRAM" is set properly. This DIP switch defines if a GRAM is present or if a GRAM is not present. If you do not have a GRAM and the switch is set improperly, Power Up Tests will try to execute on the non-existent GRAM and will produce many errors in the log. In this case, these errors will have no meaning.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_MIF_COMMON_GAP
"GRADIENT DRIVER TESTS - Power Up Register Pattern Test Failed. Each MIF board has several errors. Possible causes: GAP board or GAP +12V Supply."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_ASM_COMMON_GAP
"GRADIENT DRIVER TESTS - Power Up Register Pattern Test Failed. Each ASM board has several errors. Possible causes: GAP board or GAP +12V Supply."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_GRAM_COMMON_GAP
"GRADIENT DRIVER TESTS - Power Up Register Pattern Test Failed. Each GRAM has several errors. Possible causes: GAP board, GAP +12V Supply, or the DIP switch on the front of the MIF indicates that a GRAM is present when it is not."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_GASM_COMMON_GAP
"GRADIENT DRIVER TESTS - Power Up Register Pattern Test Failed. Each GASM board has several errors. Possible causes: GAP board, GAP +12V Supply, or the DIP switch on the front of the MIF indicates that a GRAM is present when it is not."
Extended Error: Verify that the front MIF DIP switch that is marked "GRAM" is set properly. This DIP switch defines if a GRAM is present or if a GRAM is not present. If you do not have a GRAM and the switch is set improperly, Power Up Tests will try to execute on the non-existent GRAM and will produce many errors in the log. In this case, these errors will have no meaning.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_MIF_PATTERN
"GRADIENT DRIVER TESTS - Power Up Register Pattern Test Failed. The MIF %c Axis has %d errors out of 16. Possible causes: cables within the GAP module, cable between MIF & GAP, the MIF board, or the GAP board."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_ASM_PATTERN
"GRADIENT DRIVER TESTS - Power Up Register Pattern Test Failed. The ASM %c Axis has %d errors out of 16. Possible causes: cables within the GAP module, cable between MIF & GAP, the MIF board, the ASM board, or the GAP board."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_GRAM_PATTERN
"GRADIENT DRIVER TESTS - Power Up Register Pattern Test Failed. The GRAM %c Axis has %d errors out of 16. Possible causes: cables within the GAP module, cable between GAP & GRAM, the GRAM, GAP board, or the MIF DIP switches are not properly set."
Extended Error: Verify that the front MIF DIP switch that is marked "GRAM" is set properly. This DIP switch defines if a GRAM is present or if a GRAM is not present. If you do not have a GRAM and the switch is set improperly, Power Up Tests will try to execute on the non-existent GRAM and will produce many errors in the log. In this case, these errors will have no meaning.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_GASM_PATTERN
"GRADIENT DRIVER TESTS - Power Up Register Pattern Test Failed. The GASM %c Axis has %d errors out of 16. Possible causes: cables within GAP module, cable between GAP & GRAM, GRAM, GAP, GASM cable connections, GASM, or MIF DIP switch settings."
Extended Error: Verify that the front MIF DIP switch that is marked "GRAM" is set properly. This DIP switch defines if a GRAM is present or if a GRAM is not present. If you do not have a GRAM and the switch is set improperly, Power Up Tests will try to execute on the non-existent GRAM and will produce many errors in the log. In this case, these errors will have no meaning.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_MIF_ADDRESS
"GRADIENT DRIVER TESTS - Power Up MIF %c Axis Register Addressing Test Failed. Possible causes: cables within the GAP module, cable between MIF & GAP, the MIF board, the GAP board, or the MIF DIP switches are improperly set."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_ASM_ADDRESS
"GRADIENT DRIVER TESTS - Power Up ASM %c Axis Register Addressing Test Failed. Possible causes: cables within the GAP module, cable between MIF & GAP, the MIF board, the ASM board, or the GAP board."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_GRAM_ADDRESS
"GRADIENT DRIVER TESTS - Power Up GRAM %c Axis Register Addressing Test Failed. Possible causes: MIF DIP switches are improperly set, cables within the GAP module, cable between the GAP & GRAM, GRAM, GAP, or GRAM board DIP switches are enabled."
Extended Error: Verify that the front MIF DIP switch that is marked "GRAM" is set properly. This DIP switch defines if a GRAM is present or if a GRAM is not present. If you do not have a GRAM and the switch is set improperly, Power Up Tests will try to execute on the non-existent GRAM and will produce many errors in the log. In this case, these errors will have no meaning.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_REG_GASM_ADDRESS
"GRADIENT DRIVER TESTS - Power Up GASM %c Axis Register Addressing Test Failed. Possible causes: MIF DIP switches are improperly set, cables within the GAP module, cable between GAP & GRAM, GRAM, GAP, GASM cable connections, or GASM."
Extended Error: Verify that the front MIF DIP switch that is marked "GRAM" is set properly. This DIP switch defines if a GRAM is present or if a GRAM is not present. If you do not have a GRAM and the switch is set improperly, Power Up Tests will try to execute on the non-existent GRAM and will produce many errors in the log. In this case, these errors will have no meaning.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_LOC_POWERUP_STATUS
"GRADIENT DRIVER TESTS - %c Axis Power Up Test failures. ASM and GASM Local Voltage Test will not be executed on %c Axis. Check previous error messages."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_LOC_ASM_COMMON
"GRADIENT DRIVER TESTS - ASM Local Voltage Check Failed.
The ASM %c Axis local voltage signals: AGND, DIG_5V_REF, REF_15V, REF_5V, and V_1_235 all measure 0 Volts. Re-seat the ASM board or check the MIF board."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_LOC_GASM_COMMON
"GRADIENT DRIVER TESTS - GASM Local Voltage Check Failed. The GASM %c Axis local voltage signals: AGND, VCC_REF, REF_15V, REF_5V, and V_1_235 all measure 0 Volts. Check the GASM cable connections or the GRAM Control board."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_LOC_ASM_AGND_RANGE
"GRADIENT DRIVER TESTS - ASM %c Axis AGND voltage out of range. Re-seat the ASM, if problem persists swap ASM. If problem moves, replace ASM, else replace MIF. Low: %10.3fV High: %10.3fV Value: %10.3fV"
Extended Error: To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_LOC_ASM_DIG5VREF_RANGE
"GRADIENT DRIVER TESTS - ASM %c Axis DIG_5V_REF voltage out of range. Re-seat the ASM, if problem persists swap ASM. If problem moves, replace ASM, else replace MIF. Low: %10.3fV High: %10.3fV Value: %10.3fV"
Extended Error: To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_LOC_ASM_REF15V_RANGE
"GRADIENT DRIVER TESTS - ASM %c Axis REF_15V voltage out of range. Re-seat the ASM, if problem persists swap ASM. If problem moves, replace ASM, else replace MIF. Low: %10.3fV High: %10.3fV Value: %10.3fV"
Extended Error: To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_LOC_ASM_REF5V_RANGE
"GRADIENT DRIVER TESTS - ASM %c Axis REF_5V voltage out of range. Re-seat the ASM, if problem persists swap ASM. If problem moves, replace ASM, else replace MIF. Low: %10.3fV High: %10.3fV Value: %10.3fV"
Extended Error: To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_LOC_ASM_V1235_RANGE
"GRADIENT DRIVER TESTS - ASM %c Axis V_1_235 voltage out of range. Re-seat the ASM, if problem persists swap ASM. If problem moves, replace ASM, else replace MIF. Low: %10.3fV High: %10.3fV Value: %10.3fV"
Extended Error: To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_LOC_GASM_AGND_RANGE
"GRADIENT DRIVER TESTS - GASM %c Axis AGND voltage out of range. Check the GASM cable connections; if problem persists swap GASM. If problem moves, replace GASM, else replace GRAM. Low: %10.3fV High: %10.3fV Value: %10.3fV"
Extended Error: To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_LOC_GASM_VCCREF_RANGE
"GRADIENT DRIVER TESTS - GASM %c Axis VCC_REF voltage out of range. Check the GASM cable connections; if problem persists swap GASM. If problem moves, replace GASM, else replace GRAM. Low: %10.3fV High: %10.3fV Value: %10.3fV"
Extended Error: To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_LOC_GASM_REF15V_RANGE
"GRADIENT DRIVER TESTS - GASM %c Axis REF_15V voltage out of range. Check the GASM cable connections; if problem persists swap GASM. If problem moves, replace GASM, else replace GRAM. Low: %10.3fV High: %10.3fV Value: %10.3fV"
Extended Error: To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_LOC_GASM_REF5V_RANGE
"GRADIENT DRIVER TESTS - GASM %c Axis REF_5V voltage out of range. Check the GASM cable connections; if problem persists swap GASM. If problem moves, replace GASM, else replace GRAM. Low: %10.3fV High: %10.3fV Value: %10.3fV"
Extended Error: To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_LOC_GASM_V1235_RANGE
"GRADIENT DRIVER TESTS - GASM %c Axis V_1_235 voltage out of range. Check the GASM cable connections; if problem persists swap GASM. If problem moves, replace GASM, else replace GRAM. Low: %10.3fV High: %10.3fV Value: %10.3fV"
Extended Error: To make sure that you are not looking at faulty sensing from the ASM Board, try swapping the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. Remember to use proper ESD practices when changing these boards. This error condition can also be caused by the Gradient HSSD Cables being located in the wrong position. In addition to generating this error, if the Gradient Data Clock is not correctly connected, then the system will not go Ready. One way to check the Gradient Data Clock connections is to check the last line of the error messages. If it reads " Low: XXXv High: XXXv Value: 0V axis: XXXXXXX", then this is an indication the Gradient Clock may be missing. This could also indicate a power problem somewhere in the subsystem. Check for things that are common to the axes that are failing.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_MSG_HEADER
"GRADIENT DRIVER TESTS"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_APPS_HOLDER
"%b
%b ->
%b"
Extended Error: If you get this error message and the text in this error message says Current Distortion Error and the last line in the error message reads Ready Vctrl=1 AVin=1,then check all data cables and all 1/0 cables between the GRAM Cabinet and the 8645 Cabinet. It may be possible that one of these cables is crossed.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_NO_TESTS_SELECTED
"GRADIENT DRIVER TESTS - Internal GAP Software Error. The Gradient Driver Tests command word was empty. SPI software specified an empty command word in a MDS packet. If the MDS link connection is good, this is a software bug; write a CQA.->"
Extended Error: Any time a GAP programming error occurs, a Reset TPS should be done to reset the GAP software. If this error does not go away, then it is necessary to reload software via a load from warm.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_POWERUP_STATUS
"GRADIENT DRIVER TESTS - %c Axis Power Up Test failures. Gradient Driver %b Tests will not be executed on %c Axis. Check previous error messages."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STDBY_VCC_MODE
"Standby Vctrl=1 AVin=0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_RDY_VCC_MODE
"Ready Vctrl=1 AVin=0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_RDY_CUR_MODE
"Ready Vctrl=0 AVin=0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_RDY_GRAM_MODE
"Ready Vctrl=1 AVin=1"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_SETTLING_MODE
"Dynamic Settling Test"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STATIC_LABEL
"Static"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYNAMIC_LABEL
"Dynamic"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DTUNE_MODE
"Digital Tuning Bd Test"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DIGTUNE_LABEL
"Digital Tune"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_MIF_REG_A_CFG
"GRADIENT DRIVER TESTS - Static Test MIF %c Axis Configuration Error. Required: Current Sum=0, Low-side Invert=1, Serv Mode=0, Manual Ena=0. Current: Current Sum=%d, Low-side Invert=%d, Serv Mode=%d, Manual Ena=%d. No tests will be run on this axis.->"
Extended Error: Current Sum configuration error could cause this fault. Move the DIP switch (S1) on the MIF Circuit Board to the Current Sum true position. Low side inverter configuration error could also cause this fault. Move the DIP switch (S2) on the MIF Circuit Board to the Low Side Polarity true position. Service mode is the logic OR of switches S4-1 through S4-5 (these are the DIP switches on the MIF front panel)...the first five dip switches must be set in the up configuration. Your system should not be in the Manual Enable mode...it must be in GAP control...S3, the three position slide switch should be all the way to the right (series switch can be down) After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. If all switches are correct, and the problem still exists, then swap the MIF chassis of the axis with the fault with a MIF chassis of another axis, and re-run this test.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_ASM_CFG
"GRADIENT DRIVER TESTS - %b Test ASM %c Axis Configuration Error. An ASM must be present to perform this test. This Axis does not have an ASM. To test this axis, install an ASM and run test again.->"
Extended Error: Swap the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. If the problem stays on the same axis, then swap the MIF Module for the axis with the fault with a MIF Module from another axis. If the problem moves, then change the MIF Module. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_SERIES_CFG
"GRADIENT DRIVER TESTS - %b Test %c Axis Configuration Error. Power Modules must be set in Series Mode. To test this axis, set the Series switch on the front of the MIF to 1 and run test again.->"
Extended Error: Swap the ASM Board for the axis with the fault with an ASM Board from another axis to see if the problem changes axis. If the problem changes axis, then the ASM Board is bad. If the problem stays on the same axis, then swap the MIF Module for the axis with the fault with a MIF Module from another axis. If the problem moves, then change the MIF Module. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_GRAD_CFG
"GRADIENT DRIVER TESTS - %b Test %c Axis Configuration Error. Single Power Module without a GRAM is not a valid configuration for this test. To test this axis, reconfigure in a valid product configuration and run test again.->"
Extended Error: To check if hardware is in a valid product configuration, ensure that the single power module DIP switch on the front of the MIF is in the correct position, and that the GRAM present DIP switch on the front of the MIF is in the correct position. The following Table defines the DIP Switch (S4) positions for each product configuration system.
Switch (S4) Number
1 2 3 4 5 6 7 8
Signa Horizon Product Configuration
OFF OFF OFF OFF OFF ON ON OFF
Signa Horizon HiSpeed Prod Conf.
OFF OFF OFF OFF OFF OFF ON ON
Signa Horizon EchoSpeed Prod. Conf.
OFF OFF OFF OFF OFF ON ON ON
After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of S4-6 through S4-8 with the hardware settings of these switches. If the switches differ from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready. Using cfe, ensure that the MRconfig.cfg file is configured correctly.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_GASM_CFG
"GRADIENT DRIVER TESTS - %b Test GASM %c Axis Configuration Error. A GASM must be present to perform this test. This Axis does not have a GASM. To test this axis, install a GASM and run test again.->"
Extended Error: Swap the GASM Board of the axis with the fault with a GASM Board of another axis. If the problem moves, then replace the GASM Board. If the problem remains on the same axis, use the GRAM Troubleshooting Harness, 2141174, to swap the GRAM Module to confirm the functionality of the GRAM Module or Status and Control Cables. If the problem changes axis, then the GRAM Module or Status and Control Cables internal to the GRAM Cabinet are bad for that axis. If the problem remains on the same axis, then the cables external to the GRAM Cabinet are bad. Use the Simplified Block diagrams in Direction 2117724 to check the Cables from the GAP to the GRAM Module. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_GRAM_REG_9_CFG
"GRADIENT DRIVER TESTS - %b Test GRAM %c Axis Configuration Error. Required: Serv Mode=0, Inverter Ready=1, Control Ready=1. Current: Serv Mode=%d, Inverter Ready=%d, Control Ready=%d. No tests will be run on this axis.->"
Extended Error: For GRAM Service Mode, Inverter Ready should be a 1 and displayed as green on DS, within 15 seconds of a power cycle. Control Ready should be a 1 and displayed as green at all times, unless power is turned off. If Inverter Ready and Control Ready conditions are not correct, replace the GRAM for that axis. The four position dip switch on the GRAM Control Board should all be in the inactive, or 0, position.S1 should be in the Enable (Up) position. If Inverter Ready and Control Ready conditions are not correct, replace the GRAM for that axis. If the MRConfig.cfg file has been changed, a Reset TPS MUST be performed. After a Reset TPS, SPI will check the MRconfig.cfg file to compare the software configuration of with the hardware settings. If the hardware differs from the MRconfig.cfg file, SPI will log an error, and will not allow the Gradient Driver Subsystem to go Ready.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_MIF_FS_CFG
"GRADIENT DRIVER TESTS - %b Test MIF %c Axis Full Scale Setup Error. Software failed to set Full Scale to 200A. To test this axis, replace the MIF module and run test again.->"
Extended Error: Images with geometric distortion will generate this error message. running gradient calibration to adjust cfxfull, cfyfull, and cfzfull will not fix this problem. The MIF module must be replaced.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_MIF_LC_CFG
"GRADIENT DRIVER TESTS - %b Test MIF %c Axis Load Comp Setup Error.
Software failed to set Load Compensation to 0. To test this axis, replace the MIF module and run test again."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_GRAM_FW_CFG
"GRADIENT DRIVER TESTS - %b Test GRAM %c Axis Freewheel Setup Error. Software failed to set the GRAM to Freewheel. To test this axis, replace the GRAM and run test again."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_GRAM_HIVOLT_CFG
"GRADIENT DRIVER TESTS - %b Test GRAM %c Axis High Volt Enable Setup Error. Software failed to set GRAM High Voltage Enable. To test this axis, replace the GRAM and run test again."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_MIF_AVIN_CFG
"GRADIENT DRIVER TESTS - %b Test MIF %c Axis Analog VIN Setup Error. Software failed to set the MIF Analog VIN to %d. To test this axis, replace the MIF module and run test again.->"
Extended Error: If the system is a Signa Horizon, there would be no current output. The image would look like a flat image. If the system has a GRAM, then an error message would have indicated a fault, and the scanner would not be permitted to go to Ready. If there was a G in the ipg_stage file, and you performed a scan, the output voltage would be proportional to the DAC signal. This will generate too much voltage and an I Overcurrent and I Distorition fault will occur. If too much current is generated, then there will be an overload condition. In either case, replace the MIF Module.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_MIF_VCTRL_CFG
"GRADIENT DRIVER TESTS - %b Test MIF %c Axis Voltage Control Setup Error. Software failed to set the MIF Voltage Control Mode to %d. To test this axis, replace the MIF module and run test again.->"
Extended Error: If the system is a Signa Horizon, the system should have been in Current Control Mode but was actually in Voltage Control Mode. Overloads would have occurred. This test result indicates that the MIF Module must be replaced. If the system has a GRAM, the system would have generated Power Module overloads. The MIF Module must be replaced.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_NO_AXIS_STATUS
"GRADIENT DRIVER TESTS - %b Tests will not be executed on the %c Axis. To test this axis, check power to the %c Axis and run test again."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_FAULT_NO_TESTS
"GRADIENT DRIVER TESTS - %b Tests will not be executed on the %c Axis since a fault was detected. Check previous error messages. To test this axis, clear the fault and run test again.->"
Extended Error: If after attempting to clear the fault, and faults still occur, and the system can not be controlled to standby, then turn power OFF to the slide switch on the MIF, and power OFF to the GRAM (if present) for this axis. Perform Gradient Driver Tests on the other axes. To run Gradient Driver Tests, Select [TPS Peripheral], then [MDS], then [Gradient Tests] from the Diagnostics menu. These are proprietary diagnostics.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_HIGH_PM_CFG
"GRADIENT DRIVER TESTS - %b Tests %c Axis High Power Module Config Error. Software does not detect a High Power Module on this axis. To test this axis, check power and cables to the High Power Module and run test again.
Extended Error: MIF Module, Main Board and Cables from the MIF to the Main Board could be the problem.
To isolate further, check for power to the Main Board from the Toroid power supply, in the base of the Power Module. There is a cable on the front of the Main Board from this Toroid power supply which is a FRU-2. There are also test points for the Power Module Toroids (L1, L2, and L3. These Toroids are FRU-1's).Also, check the test points on the Main Board to test power to the Transistor Shelf and the PPBM. Check fuses F1, and F2 located on the back of the Power Module.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_LOW_PM_CFG
"GRADIENT DRIVER TESTS - %b Tests %c Axis Low Power Module Config Error. The DUAL DIP switch on the MIF is set, but software does not detect a Low Power Module. To test this axis, check power and cables to Low Module and run test again.->"
Extended Error: The DIP switch indicates that the system is either a Signa Horizon or a Signa Horizon EchoSpeed. If this system is a Signa Horizon HiSpeed, then this dip switch needs to be changed to indicate a single Power Module per axis. If the DIP switch is set, then the MIF is not reading it. It is possible that the MIF Module is not functioning properly. Swap the MIF Module for the failed axis with a MIF Module for a working axis, and run the test again. If the problem moved, then the MIF Module for the failed axis needs to be replaced. Other possible causes are the Main Board or cables from the MIF to the Main Board. To isolate further, check for power to the Main Board from the Toroid power supply, in the base of the Power Module, to the Main Board. There is a cable on the front of the Main Board from this Toroid power supply which is a FRU-2. There are also test points for the Power Module Toroids (L1, L2, and L3. These Toroids are FRU-1's). Also, check the test points on the Main Board to test power to the Transistor Shelf and the PPBM. Check fuses F1, and F2 located on the back of the Power Module.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_NO_LOW_PM_CFG
"GRADIENT DRIVER TESTS - %b Tests %c Axis Dual Power Module Config Error. The DUAL DIP switch on the MIF is not set, but software detects Dual Power Modules. To test this axis, change the DUAL DIP switch and run test again.->"
Extended Error: It is important that the hardware configuration matches the MR Config file. If the hardware matches the MR Config file, then check the configuration switches on the front of the MIF Module. If the switches seem to be in the correct position, perform a RESET TPS. If the problem persists, swap the MIF Modules and re run this test. If the problem moves, then replace the MIF Module on the failed axis. If the problem stays the same, then check the cables from the MIF Module to the Main Board of the Power Module.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_NO_GRAM_CFG
"GRADIENT DRIVER TESTS - %b Tests %c Axis GRAM Configuration Error. The GRAM DIP switch on the MIF is not set, but software detects a GRAM present. To test this axis, change the GRAM DIP switch and run test again.->"
Extended Error: If power is applied to the GRAM, and the DIP switch is in the no GRAM position, and you are trying to troubleshoot by bypassing the GRAM, then, the GRAM has to be taken out of the circuit. The GRAM has to be wired out of the circuit, not just turned off when bypassing the GRAM. If there is no GRAM, but software detects that there is a GRAM, then the DIP switch is not being read properly, this is probably a bad MIF Module. Try toggling the dip switch and re-run this test. If the problem goes away, then the dip switch is probably failing intermittently. Replace the MIF Module. If the problem does not go away, then try swapping the MIF Module and re- running the test. If the problem moves, replace the MIF Module. If the problem stays on the same axis, then there is probably a cable problem. Re-check the cable connections and run numbers.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_GRAM_CFG
"GRADIENT DRIVER TESTS - %b Tests %c Axis GRAM Configuration Error. The GRAM DIP switch on the MIF is set, but software does not detect a GRAM present. To test this axis, check GRAM DIP switch or power and cables to the GRAM, and run test again.->"
Extended Error: Always check to make sure the hardware configuration, switch configuration and MRConfig.cfg file configuration information are the same. A Reset TPS must be performed in order for the changes to the configuration file to take effect.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_NO_TESTS_STDBY
"GRADIENT DRIVER TESTS - %b Tests will not be executed on ALL axes. %c Axis would not go to Standby. Check previous error messages."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_X_OVERLOAD
"X Axis Gradient Overload Occurred. X axis 8645 Power Module has reported an overload. An overload is the result of the power module output voltage not following the input command."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_Y_OVERLOAD
"Y Axis Gradient Overload Occurred. Y axis 8645 Power Module has reported an overload. An overload is the result of the power module output voltage not following the input command."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_Z_OVERLOAD
"Z Axis Gradient Overload Occurred. Z axis 8645 Power Module has reported an overload. An overload is the result of the power module output voltage not following the input command."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VDAC_STDBY_GAP
"GRADIENT DRIVER TESTS - Static Test Failed on ALL Axes. VDAC had %d failures out of %d. Most likely related to a GAP board problem. Other possible causes: HSSD cable from GAP to MIFs, or the MIF board. Standby Vctrl=1 AVin=0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VDAC_STDBY_OTHER
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VDAC had %d failures out of %d. Possible causes: HSSD cable from GAP to MIF, the MIF Board, or the GAP Board.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VDAC_RDYGRAM_GAP
"No text. Message removed."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VDAC_RDYGRAM_OTHER
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VDAC had %d failures out of %d. Possible causes: Cable between the MIF & GRAM, the MIF Module, or the GRAM Module. Ready Vctrl=1 AVin=1"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VMIF_STDBY
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VMIF had %d failures out of %d. Possible causes: MIF Module, cable from MIF to HIGH or LOW Power Module, or the HIGH or LOW 8645 Main Board.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VCCH_STDBY
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VCC_H had %d failures out of %d. Possible causes: 8645 HIGH Main Board, the PPBM, or the MIF Module.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. The suggested swapping strategy is to swap the 8645 HIGH Main Board, if the problem moves, then replace this Main Board. If the problem stays on the same axis, then swap the PPBM for this axis with another axis. Re-run this test. If the problem moves, then replace the PPBM. If the problem stays on the same axis, then it is probably the MIF Module for this axis. Swap the MIF Module for this axis with another axis and re-run the test. If the problem moves, replace the MIF Module. If the problem stays on the same axis, then there is probably a cable problem.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VCCH_RDYVCC
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VCC_H had %d failures out of %d. Possible causes: 8645 HIGH Main Board, PPBM, or MIF Module.-> Ready Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VCCL_STDBY
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VCC_L had %d failures out of %d. Possible causes: 8645 LOW Main Board, the PPBM, or the MIF Module.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. The suggested swapping strategy is to swap the 8645 LOW Main Board, if the problem moves, then replace this Main Board. If the problem stays on the same axis, then swap the PPBM for this axis with another axis. Re-run this test. If the problem moves, then replace the PPBM. If the problem stays on the same axis, then it is probably the MIF Module for this axis. Swap the MIF Module for this axis with another axis and re-run the test. If the problem moves, replace the MIF Module. If the problem stays on the same axis, then there is probably a cable problem.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VCCL_RDYVCC
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VCC_L had %d failures out of %d. Possible causes: 8645 LOW Main Board, PPBM, or the MIF Module.-> Ready Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VOUTH_STDBY
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VOUT_H had %d failures out of %d. Possible causes: Cables between MIF & HIGH Power Module, the GRAM, the MIF Module, or the 8645 HIGH Main Board.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. The suggested swapping strategy is to swap the GRAM, first. Use the GRAM Troubleshooting Harness to swap the GRAM. Remember to swap the appropriate status and control cables. If the status and control cables from the MIF to the GRAM are not swapped, and you continue to run the tests, the GRAM will be damaged which will require a new GRAM for that axis. The PPBM is not feeding voltage into the Power Module at this point. Something is feeding voltage into the Power Module. Try running the Standby Voltage Control Mode Test in the Manual Diagnostics section.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VOUTH_RDYVCC
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VOUT_H had %d failures out of %d. Possible causes: 8645 HIGH Main Board, Output Shelf, PPBM, MIF Module, GRAM Module (if present), or Load.-> Ready Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. The suggested swapping strategy is to swap the GRAM, first. Use the GRAM Troubleshooting Harness to swap the GRAM. Remember to swap the appropriate status and control cables. If the status and control cables from the MIF to the GRAM are not swapped, and you continue to run the tests, the GRAM will be damaged which will require a new GRAM for that axis. The PPBM is not feeding voltage into the Power Module at this point. Something is feeding voltage into the Power Module. Try running the Standby Voltage Control Mode Test in the Manual Diagnostics section.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VOUTL_STDBY
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VOUT_L had %d failures out of %d. Possible causes: Cables between MIF & LOW Power Module, the GRAM, the MIF Module, or the 8645 LOW Main Board.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. The suggested swapping strategy is to swap the GRAM, first. Use the GRAM Troubleshooting Harness to swap the GRAM. Remember to swap the appropriate status and control cables. If the status and control cables from the MIF to the GRAM are not swapped, and you continue to run the tests, the GRAM will be damaged which will require a new GRAM for that axis. The PPBM is not feeding voltage into the Power Module at this point. Something is feeding voltage into the Power Module. Try running the Standby Voltage Control Mode Test in the Manual Diagnostics section.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VOUTL_RDYVCC
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VOUT_L had %d failures out of %d. Possible causes: 8645 LOW Main Board, Output Shelf, PPBM, MIF Module, GRAM Module (if present), or Load.-> Ready Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. If the system has previously reported an Amp Overcurrent or Current Distortion error, and it fails this test, then just about everything in the Power Module and the Load is in the category where it could be suspected as bad. There is probably only one FRU that is bad. A suggested Service Method is to disconnect the Load from the output of the Power Module and run this test again. If the test passes this time, then there is a problem with the Load. The Load test, which is the next test run, will fail generating an error message.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_IOUTH_RDYVCC
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. IOUT_H had %d failures out of %d. Possible causes: 8645 HI Main Board, Current Shunt, Output Shelf, MIF, Epoxy-filled Gradient Coil, Output cables, or Gradient Filter Box.-> Ready Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. This is an indication that there is a problem outside of this Power Module. However, if the tests stop at this point again, then the problem is inside of the affected Power Module or the MIF Module. This is the first error message that will come up after current is applied during the Gradient Driver Tests. Try performing the Load Continuity Test procedure to ensure the load is not open.
To swap the GRAM Module, use the GRAM Troubleshooting Harness. Remember to swap the appropriate status and control cables at the bottom of the rear of the GRAM Cabinet.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_ITOT_RDYVCC
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. ITOT had %d failures out of %d. Possible causes: MIF Module or 8645 HIGH Main Board.-> Ready Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. This problem could be the Main Board on the High Power Module. Since it is easy to swap this with the Main Board of a functioning Power Module, this should be attempted first. If this is not the problem, the next most likely FRU is the 140A Current Shunt. Try swapping this shunt with a shunt from a functioning Power Module. If the problem moves, then the 140A Current Shunt is the problem, if the problem stayed on that axis, try the MIF Module, if that is not the problem, then try the Output shelf. Other possibilities are the I/O Cables for the Gradient Driver Subsystem. These are the single O power signal cables. Another problem could be the Gradient Filter on the Penetration Panel. If your system has a GRAM, try using the GRAM Troubleshooting Harness (2144094) to swap GRAMs from one axis to the other.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_ITOT_RDYCUR
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. ITOT had %d failures out of %d. Possible cause: MIF Module.-> Ready Vctrl=0 AVin=0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_PXTEMPH_STDBY_RANGE
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. PXTEMP_H had %d failures out of %d. Possible causes: 8645 HIGH Main Board, Output Shelf, blocked airflow, or MIF Module.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. This point has either exceeded its highest spec or lowest spec. Additionally, this test checks to see that all of the values are within a specified range. Measure the +LTj test point on TJ201- 4, or pin 4 of TJ201, on the Main Board for the High Power Module per the Transistor Junction Temperature Test procedure. To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. if the problem stays on the same axis, follow troubleshooting advice in the error message from the error log or extended error log when appropriate. This includes the cables from the MIF to the MIF Module. Try swapping the Main Board for this axis with the Main Board of another axis. Try swapping the Output Shelf for this axis with the Output Shelf of another axis. Check the cables between the MIF Module and the 8645 Main Board. Try swapping the MIF Module.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_PXTEMPH_RDYCUR_RANGE
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. PXTEMP_H had %d failures out of %d. Possible causes: 8645 HIGH Main Board, Output Shelf, PPBM, or MIF Module.-> Ready Vctrl=0 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. If this system has only one Power Module per axis, then it is very unlikely that the MIF is the problem. The Power Modules are current monitoring correctly, however, they are not balancing the voltage. This point has either exceeded its highest spec or lowest spec. Additionally, this test checks to see that all of the values are within a specified range. Measure the +LTj test point on TJ201- 4, or pin 4 of TJ201, on the Main Board for the High Power Module per the Transistor Junction Temperature Test procedure.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_PXTEMPH_STDBY_DELTA
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. PXTEMP_H exceeded Max Temp change. Measured Delta=%6.3fC, Maximum Delta=%6.3fC. Possible causes: 8645 HIGH Main Board, Output Shelf, or MIF Module.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. There has been a large temperature delta sensed during this test. This delta exceeds the specified limits. Measure the +LTj test point on TJ201- 4, or pin 4 of TJ201,on the Main Board for the High Power Module per the Transistor Junction Temperature Test procedure. Check the cables from the MIF to the MIF Module. Try swapping the Main Board for this axis with the Main Board of another axis. Try swapping the Output Shelf for this axis with the Output Shelf of another axis. Check the cables between the MIF Module and the 8645 Main Board. Try swapping the MIF Module.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_PXTEMPH_RDYCUR_DELTA
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. PXTEMP_H exceeded Max Temp change. Measured Delta=%6.3fC, Maximum Delta=%6.3fC. Possible causes: 8645 HIGH Main Board, Output Shelf, PPBM, or MIF Module.-> Ready Vctrl=0 AVin=0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_PXTEMPL_STDBY_RANGE
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. PXTEMP_L had %d failures out of %d. Possible causes: 8645 LOW Main Board, Output Shelf, blocked airflow, or MIF Module.-> Standby Vctrl=1 AVin=0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_PXTEMPL_RDYCUR_RANGE
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. PXTEMP_L had %d failures out of %d. Possible causes: 8645 LOW Main Board, Output Shelf, PPBM, or MIF Module.-> Ready Vctrl=0 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_PXTEMPL_STDBY_DELTA
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. PXTEMP_L exceeded Max Temp change. Measured Delta=%6.3fC, Maximum Delta=%6.3fC. Possible causes: 8645 LOW Main Board, Output Shelf, or MIF Module.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. There has been a large temperature delta sensed during this test. This delta exceeds the specified limits. Measure the +LTj test point on TJ201- 4, or pin 4 of TJ201,on the Main Board for the Low Power Module per the Transistor Junction Temperature Test procedure. Check the cables from the MIF to the MIF Module. Try swapping the Main Board for this axis with the Main Board of another axis. Try swapping the Output Shelf for this axis with the Output Shelf of another axis. Check the cables between the MIF Module and the 8645 Main Board. Try swapping the MIF Module.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_PXTEMPL_RDYCUR_DELTA
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. PXTEMP_L exceeded Max Temp change. Measured Delta=%6.3fC, Maximum Delta=%6.3fC. Possible causes: 8645 LOW Main Board, Output Shelf, PPBM, or MIF Module.-> Ready Vctrl=0 AVin=0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_NXTEMPH_STDBY_RANGE
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. NXTEMP_H had %d failures out of %d. Possible causes: 8645 HIGH Main Board, Output Shelf, blocked airflow, or MIF Module.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. This point has either exceeded its highest spec or lowest spec. Additionally, this test checks to see that all of the values are within a specified range. Measure the -LTj test point on TJ201- 5, or pin 5 of TJ201, on the Main Board for the High Power Module per the Transistor Junction Temperature Test procedure. Check the cables from the MIF to the MIF Module. Try swapping the Main Board for this axis with the Main Board of another axis. Try swapping the Output Shelf for this axis with the Output Shelf of another axis. Check the cables between the MIF Module and the 8645 Main Board. Try swapping the MIF Module.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_NXTEMPH_RDYCUR_RANGE
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. NXTEMP_H had %d failures out of %d. Possible causes: 8645 HIGH Main Board, Output Shelf, PPBM, or MIF Module.-> Ready Vctrl=0 AVin=0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_NXTEMPH_STDBY_DELTA
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. NXTEMP_H exceeded Max Temp change. Measured Delta=%6.3fC, Maximum Delta=%6.3fC. Possible causes: 8645 HIGH Main Board, Output Shelf, or MIF Module.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. This point has either exceeded its highest spec or lowest spec. Additionally, this test checks to see that all of the values are within a specified range. Measure the -LTj test point on TJ201- 5, or pin 5 of TJ201, on the Main Board for the High Power Module per the Transistor Junction Temperature Test procedure. Check the cables from the MIF to the MIF Module. Try swapping the Main Board for this axis with the Main Board of another axis. Try swapping the Output Shelf for this axis with the Output Shelf of another axis. Check the cables between the MIF Module and the 8645 Main Board. Try swapping the MIF Module.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_NXTEMPH_RDYCUR_DELTA
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. NXTEMP_H exceeded Max Temp change. Measured Delta=%6.3fC, Maximum Delta=%6.3fC. Possible causes: 8645 HIGH Main Board, Output Shelf, PPBM, or MIF Module.-> Ready Vctrl=0 AVin=0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_NXTEMPL_STDBY_RANGE
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. NXTEMP_L had %d failures out of %d. Possible causes: 8645 LOW Main Board, Output Shelf, blocked airflow, or MIF Module.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. This point has either exceeded its highest spec or lowest spec. Additionally, this test checks to see that all of the values are within a specified range. Measure the -LTj test point on TJ201- 5, or pin 5 of TJ201, on the Main Board for the High Power Module per the Transistor Junction Temperature Test procedure. Check the cables from the MIF to the MIF Module. Try swapping the Main Board for this axis with the Main Board of another axis. Try swapping the Output Shelf for this axis with the Output Shelf of another axis. Check the cables between the MIF Module and the 8645 Main Board. Try swapping the MIF Module.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_NXTEMPL_RDYCUR_RANGE
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. NXTEMP_L had %d failures out of %d. Possible causes: 8645 LOW Main Board, Output Shelf, PPBM, or MIF Module.-> Ready Vctrl=0 AVin=0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_NXTEMPL_STDBY_DELTA
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. NXTEMP_L exceeded Max Temp change. Measured Delta=%6.3fC, Maximum Delta=%6.3fC. Possible causes: 8645 LOW Main Board, Output Shelf, or MIF Module.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. This point has either exceeded its highest spec or lowest spec. Additionally, this test checks to see that all of the values are within a specified range. Measure the -LTj test point on TJ201- 5, or pin 5 of TJ201, on the Main Board for the High Power Module per the Transistor Junction Temperature Test procedure. Check the cables from the MIF to the MIF Module. Try swapping the Main Board for this axis with the Main Board of another axis. Try swapping the Output Shelf for this axis with the Output Shelf of another axis. Check the cables between the MIF Module and the 8645 Main Board. Try swapping the MIF Module.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_NXTEMPL_RDYCUR_DELTA
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. NXTEMP_L exceeded Max Temp change. Measured Delta=%6.3fC, Maximum Delta=%6.3fC. Possible causes: 8645 LOW Main Board, Output Shelf, PPBM, or MIF Module.-> Ready Vctrl=0 AVin=0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_XFTEMPH_STDBY_RANGE
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. XFTEMP_H had %d failures out of %d. Possible causes: 8645 HIGH Main Board, blocked airflow, MIF Module, PPBM, or Toroid Power Supply.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. This point has either exceeded its highest spec or lowest spec. Additionally, this test checks to see that all of the values are within a specified range. Measure the+TJ300-1, TJ300-2, TJ30-3 test points, or pin 1, 2, and 3 of TJ300, on the Main Board for the High Power Module per the Transformer Core Temperature Test procedure. If one test point is out of spec, the Main Board, MIF, Cables or the Toroid may be bad. This includes the cables from the MIF to the MIF Module. Try swapping the Main Board for this axis with the Main Board of another axis. Check the cables between the MIF Module and the 8645 Main Board. Try swapping the MIF Module. If all three test points are bad, there may be blocked air flow or a bad PPBM. Check for air flow problems or try swapping the PPBM for this axis with the PPBM of another axis.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_XFTEMPH_RDYCUR_RANGE
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. XFTEMP_H had %d failures out of %d. Possible causes: 8645 HIGH Main Board, MIF Module, PPBM, or Toroid Power Supply.-> Ready Vctrl=0 AVin=0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_XFTEMPH_STDBY_DELTA
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. XFTEMP_H exceeded Max Temp change. Measured Delta=%6.3fC, Maximum Delta=%6.3fC. Possible causes: 8645 HIGH Main Board, MIF Module, PPBM, or Toroid Power Supply.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. There has been a large temperature delta sensed during this test. This delta exceeds the specified limits. Measure the TJ300-1, TJ300-2, TJ30-3test points, or pin 1, 2, and 3 of TJ300, on the Main Board for the High Power Module per the Transformer Core Temperature Test procedure. If one test point is not tracking like the other test points, the Main Board, Cables internal to the Power Module (J401, J402, J403 for the different transformers) or the Toroid may be bad. This includes the cables from the MIF to the MIF Module. Try swapping the Main Board for this axis with the Main Board of another axis. Check the cables between the MIF Module and the 8645 Main Board. Try swapping the MIF Module.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_XFTEMPH_RDYCUR_DELTA
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. XFTEMP_H exceeded Max Temp change. Measured Delta=%6.3fC, Maximum Delta=%6.3fC. Possible causes: 8645 HIGH Main Board, MIF Module, PPBM, or Toroid Power Supply.-> Ready Vctrl=0 AVin=0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_XFTEMPL_STDBY_RANGE
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. XFTEMP_L had %d failures out of %d. Possible causes: 8645 LOW Main Board, blocked airflow, MIF Module, PPBM, or Toroid Power Supply.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. This point has either exceeded its highest spec or lowest spec. Additionally, this test checks to see that all of the values are within a specified range. Measure the +TJ300-1, TJ300-2, TJ30-3 test points, or pin 1, 2, and 3 of TJ300, on the Main Board for the Low Power Module per the Transformer Core Temperature Test procedure. If one test point is out of spec, the Main Board, MIF, Cables or the Toroid may be bad. This includes the cables from the MIF to the MIF Module. Try swapping the Main Board for this axis with the Main Board of another axis. Check the cables between the MIF Module and the 8645 Main Board. Try swapping the MIF Module.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_XFTEMPL_RDYCUR_RANGE
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. XFTEMP_L had %d failures out of %d. Possible causes: 8645 LOW Main Board, MIF Module, PPBM, or Toroid Power Supply.-> Ready Vctrl=0 AVin=0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_XFTEMPL_STDBY_DELTA
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. XFTEMP_L exceeded Max Temp change. Measured Delta=%6.3fC, Maximum Delta=%6.3fC. Possible causes: 8645 LOW Main Board, MIF Module, PPBM, or Toroid Power Supply.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. There has been a large temperature delta sensed during this test. This delta exceeds the specified limits.
Measure the TJ300-1, TJ300-2, TJ30-3test points, or pin 1, 2, and 3 of TJ300, on the Main Board for the Low Power Module per the Transformer Core Temperature Test procedure. If one test point is not tracking like the other test points, the Main Board, Cables internal to the Power Module (J401, J402, J403 for the different transformers) or the Toroid may be bad. This includes the cables from the MIF to the MIF Module. Try swapping the Main Board for this axis with the Main Board of another axis. Check the cables between the MIF Module and the 8645 Main Board. Try swapping the MIF Module.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_XFTEMPL_RDYCUR_DELTA
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. XFTEMP_L exceeded Max Temp change. Measured Delta=%6.3fC, Maximum Delta=%6.3fC. Possible causes: 8645 LOW Main Board, MIF Module, PPBM, or Toroid Power Supply.-> Ready Vctrl=0 AVin=0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VFILT_STDBY
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. V_FILT had %d failures out of %d. Possible causes: GRAM Module or the cables between the 8645 Power Modules and the GRAM.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the GASM Board, swap the GASM Board for this axis with the GASM Board of another axis and re-test. If the error moves, change the GASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. To swap the GRAM Module, use the GRAM Troubleshooting Harness (2144094). Remember to swap the appropriate status and control cables at the bottom of the rear of the GRAM Cabinet. An open cable or connection between the Power Module and the GRAM could cause this error, as well.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VFILT_RDYGRAM
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. V_FILT had %d failures out of %d. Possible causes: GASM Board or the GRAM Module.-> Ready Vctrl=1 AVin=1"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VREGF_STDBY
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VREG_F had %d failures out of %d. Possible cause: GRAM Module.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the GASM Board, swap the GASM Board for this axis with the GASM Board of another axis and re-test. If the error moves, change the GASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. To swap the GRAM Module, use the GRAM Troubleshooting Harness (2144094). Remember to swap the appropriate status and control cables at the bottom of the rear of the GRAM Cabinet.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VCTRL_STDBY
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. V_CTRL had %d failures out of %d. Possible cause: GRAM Module.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the GASM Board, swap the GASM Board for this axis with the GASM Board of another axis and re-test. If the error moves, change the GASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. To swap the GRAM Module, use the GRAM Troubleshooting Harness (2144094). Remember to swap the appropriate status and control cables at the bottom of the rear of the GRAM Cabinet.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VCTRL_RDYGRAM
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. V_CTRL had %d failures out of %d. Possible causes: MIF Module, GRAM Module, GASM Board, cable between MIF & GRAM, GRAM Tuning Board, or the GRAM Tuning Board connector.-> Ready Vctrl=1 AVin=1"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_DACDI_STDBY
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. DAC_DI had %d failures out of %d. DAC_DI out of adjustment. Perform the DAC_DI Offset Adjustment Procedure, or replace the GRAM Tuning Board or GRAM Module.-> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the GASM Board, swap the GASM Board for this axis with the GASM Board of another axis and re-test. If the error moves, change the GASM Board. If the problem stays on the same axis, follow the suggested service method in these error messages. To swap the GRAM Module, use the GRAM Troubleshooting Harness (2144094). Remember to swap the appropriate status and control cables at the bottom of the rear of the GRAM Cabinet.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_IERROR_RDYGRAM
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. I_ERROR had %d failures out of %d. Possible causes: GRAM Module or the GASM Board.-> Ready Vctrl=1 AVin=1"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_IGRAD_STDBY
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. I_GRAD had %d failures out of %d. Possible causes: Cable between MIF & GRAM, HSSD cable between GAP & MIF, GRAM Module, MIF Module, or GAP Module.--> Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the GASM, swap the GASM Board for this axis with a GASM Board of another axis and re-test. If the error moves, change the GASM Board. If the problem stays on the same axis, follow troubleshooting advice in the error message from the error log or extended error log when appropriate. To swap the GRAM Module, use the GRAM Troubleshooting Harness (2144094). Remember to swap the appropriate status and control cables at the bottom of the rear of the GRAM Cabinet.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_IGRAD_RDYGRAM
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. I_GRAD had %d failures out of %d. Possible causes: Cable between MIF & GRAM, HSSD cable between GAP & MIF, GRAM Module, MIF Module, or GAP Module.-> Ready Vctrl=1 AVin=1"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_ICOIL_RDYVCC_LOAD
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. I_COIL had %d failures out of %d. Possible causes: GRAM Module, Epoxy Filled Gradient Coil, Gradient Filter Box, or Output Cables.-> Ready Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. if the problem stays on the same axis, follow troubleshooting advice in the error message from the error log or extended error log when appropriate. To ensure functionality of the GASM, swap the GASM Board for this axis with a GASM Board of another axis and re-test. If the error moves, change the GASM Board. If the problem stays on the same axis, follow troubleshooting advice in the error message from the error log or extended error log when appropriate. The test that produces this error message is trying to measure the resistance or conductance of the load. One of the failures could be an open or a short. A very hot Gradient Coil could be the source of this error as well. To check the continuity of the Gradient Coil and the rest of the Gradient Driver Subsystem, follow procedure for Continuity Test. To swap the GRAM Module, use the GRAM Troubleshooting Harness. Remember to swap the appropriate status and control cables at the bottom of the rear of the GRAM Cabinet.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_ICOIL_RDYVCC_ALL
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. I_COIL had %d failures out of %d. Possible causes: HI Current Shunt, 8645 HI Main Board, Output Shelf, GRAM, MIF, Epoxy Filled Grad Coil, Grad Filter Box, or Output Cables.-> Ready Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. If the problem stays on the same axis, follow troubleshooting advice in the error message from the error log or extended error log when appropriate. The test that produces this error message is trying to measure the resistance or conductance of the load. One of the failures could be an open or a short. A very hot Gradient Coil could be the source of this error as well. To check the continuity of the Gradient Coil and the rest of the Gradient Driver Subsystem, follow procedure for Continuity Test. Unfortunately, this error could be caused by any of the FRUs in this closed loop analog circuit. The best method to troubleshoot this is to run Manual Diagnostics to try to isolate the problem FRU.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_ICOIL_RDYVCC_PM
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. I_COIL had %d failures out of %d. Possible causes: HIGH Power Module Current Shunt, 8645 HIGH Main Board, Output Shelf, or MIF Module.-> Ready Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the ASM Board, swap the ASM Board for this axis with the ASM Board of another axis and re-test. If the error moves, change the ASM Board. if the problem stays on the same axis, follow troubleshooting advice in the error message from the error log or extended error log when appropriate. The test that produces this error message is trying to measure the resistance or conductance of the load. One of the failures could be an open or a short. A very hot Gradient Coil could be the source of this error as well. To check the continuity of the Gradient Coil and the rest of the Gradient Driver Subsystem, follow procedure for Continuity Test.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_ICOIL_RDYGRAM
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. I_COIL had %d failures out of %d. Possible causes: GRAM Module or the GASM Board.-> Ready Vctrl=1 AVin=1"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VBUS0_STDBY
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VBUS +HI had %d failures out of %d. Possible cause: GRAM Module. Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the GASM, swap the GASM Board for this axis with a GASM Board of another axis and re-test. If the error moves, change the GASM Board. If the problem stays on the same axis, follow troubleshooting advice in the error message from the error log or extended error log when appropriate. To swap the GRAM Module, use the GRAM Troubleshooting Harness (2144094). Remember to swap the appropriate status and control cables at the bottom of the rear of the GRAM Cabinet.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VBUS1_STDBY
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VBUS +LO had %d failures out of %d. Possible cause: GRAM Module. Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the GASM, swap the GASM Board for this axis with a GASM Board of another axis and re-test. If the error moves, change the GASM Board. If the problem stays on the same axis, follow troubleshooting advice in the error message from the error log or extended error log when appropriate. To swap the GRAM Module, use the GRAM Troubleshooting Harness (2144094). Remember to swap the appropriate status and control cables at the bottom of the rear of the GRAM Cabinet.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VBUS2_STDBY
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VBUS -HI had %d failures out of %d. Possible cause: GRAM Module. Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the GASM, swap the GASM Board for this axis with a GASM Board of another axis and re-test. If the error moves, change the GASM Board. If the problem stays on the same axis, follow troubleshooting advice in the error message from the error log or extended error log when appropriate. To swap the GRAM Module, use the GRAM Troubleshooting Harness (2144094). Remember to swap the appropriate status and control cables at the bottom of the rear of the GRAM Cabinet.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VBUS3_STDBY
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VBUS -LO had %d failures out of %d. Possible cause: GRAM Module. Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the GASM, swap the GASM Board for this axis with a GASM Board of another axis and re-test. If the error moves, change the GASM Board. If the problem stays on the same axis, follow troubleshooting advice in the error message from the error log or extended error log when appropriate. To swap the GRAM Module, use the GRAM Troubleshooting Harness (2144094). Remember to swap the appropriate status and control cables at the bottom of the rear of the GRAM Cabinet.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VBUSDIAG_STDBY
"GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VBUS_DIAG had %d failures out of %d. Possible cause: GRAM Module. Standby Vctrl=1 AVin=0"
Extended Error: To ensure functionality of the GASM, swap the GASM Board for this axis with a GASM Board of another axis and re-test. If the error moves, change the GASM Board. If the problem stays on the same axis, follow troubleshooting advice in the error message from the error log or extended error log when appropriate. To swap the GRAM Module, use the GRAM Troubleshooting Harness (2144094). Remember to swap the appropriate status and control cables at the bottom of the rear of the GRAM Cabinet.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_IOUTH_TOLERANCE
"GRADIENT DRIVER TESTS - Static Test Failed. An associated IOUT_H tolerance is set to 0.0 and will cause a Divide-by-Zero Error in the software. Please reset this value in /w/config/gdt_tolerances.cfg and run test again.-> Ready Vctrl=1 AVin=0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_STAT_VFILT_TOLERANCE
"GRADIENT DRIVER TESTS - Static Test Failed. An associated V_FILT tolerance is set to 0.0 and will cause a Divide-by-Zero Error in the software. Please reset this value in /w/config/gdt_tolerances.cfg and run test again.-> Ready Vctrl=1 AVin=1"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_NO_TESTS_STAT
"GRADIENT DRIVER TESTS - Dynamic Tests will not be executed on the %c Axis. Check previous error messages."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_MIF_REG_A_CFG
"GRADIENT DRIVER TESTS - Dynamic Test MIF %c Axis Configuration Error. Required: Current Sum=0, Low-side Invert=1, Serv Mode=0, Manual Ena=0. Current: Current Sum=%d, Low-side Invert=%d, Serv Mode=%d, Manual Ena=%d. No tests will be run on this axis.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_GRAM_NO_FW_CFG
"GRADIENT DRIVER TESTS - %b Test GRAM %c Axis Freewheel Setup Error. Software failed to take the GRAM out of Freewheel Mode. To test this axis, replace the GRAM and run test again.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_INVALID_NPTS_SAMPLE
"GRADIENT DRIVER TESTS - Internal GAP software error. Invalid selection for sample points. Number Pts Selected: %d SPI software specified an undefined mode in a MDS packet. If the MDS link connection is good, this is a software bug; write a CQA.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_INVALID_NPTS_RISE
"GRADIENT DRIVER TESTS - Internal GAP software error. Invalid selection for number of rise points. Rise Pts Selected: %d SPI software specified an undefined mode in a MDS packet. If MDS link connection is good, this is a software bug; write a CQA.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_INVALID_NPTS_PLATEAU
"GRADIENT DRIVER TESTS - Internal GAP software error. Invalid selection for plateau points. Plateau Pts Selected: %d SPI software specified an undefined mode in a MDS packet. If the MDS link connection is good, this is a software bug; write a CQA.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_INVALID_OFFSET_VBUS
"GRADIENT DRIVER TESTS - Internal GAP software error. Invalid selection for offset VBUS points. VBUS Offset Selected: %d SPI software specified an undefined mode in a MDS packet. If MDS link connection is good, this is a software bug; write a CQA.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_INVALID_OFFSET_START
"GRADIENT DRIVER TESTS - Internal GAP software error. Invalid selection for start offset. Offset Start Selected: %d SPI software specified an undefined mode in a MDS packet. If MDS link connection is good, this is a software bug; write a CQA.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_PEAK_0
"0 to positive plateau"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_PEAK_1
"positive plateau to negative plateau"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_PEAK_2
"negative plateau to positive plateau"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_PEAK_3
"positive plateau to 0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_PEAK_4
"0 to negative plateau"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_PEAK_5
"negative plateau to 0"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_OFFSET_INDEX_DATAERR
"No text. Message removed."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_VDAC_FLATLINE
"GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. VDAC data does not follow the input waveform. Possible causes: GRAM to MIF Cable, MIF Module, or the GRAM Module."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_VOUTH_FLATLINE
"GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. VOUT_H data does not follow the input waveform. Possible causes: MIF Module, or HI Power Module FRUs (Main Bd, Output Shelf, or PPBM)."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_ICOIL_FLATLINE
"GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. ICOIL data does not follow the input waveform. Possible causes: GRAM Module."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_IGRAD_FLATLINE
"GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. IGRAD_DEL data does not follow the input waveform. Possible causes: GASM, IPG, HSSD Fiber Optic Links, or GAP Module."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_ITOT_FLATLINE
"GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. ITOT data does not follow the input waveform. Possible causes: MIF Module, HI Main Board, or HI Output Shelf."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_VDACDEL_FLATLINE
"GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. VDAC_DEL data does not follow input waveform. Possible causes: ASM, IPG, HSSD Fiber Optic Links, GAP Module, or MIF Module."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_VDAC_VOUTH_SETTLE
"GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. VDAC & VOUT_H did not match within tolerances %d out of %d samples. Worst case delta=%6.3fV Possible causes: HI Main Board, MIF Module, Output Shelf, PPBM, or GRAM Module."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_GRAM_DIVIDE_ZERO
"GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. IGRAD_DEL data would cause a Divide By Zero error if analyzed. The positive and negative peaks are the same value. Possible causes: GASM, IPG, HSSD Fiber Optic Links, or GAP."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_ICOIL_IGRAD_SETTLE
"GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. ICOIL & IGRAD_DEL did not settle to +/-%6.3fA in %6.3fusec on the %b transition. Actual=%6.3fusec. Possible causes: GRAM or Tuning Bd, GRAM Tuning, Power Module FRUs, MIF, or Load.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_MIF_DIVIDE_ZERO
"GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. VDAC_DEL data would cause a Divide By Zero error if analyzed. The positive and negative peaks are the same value. Possible causes: ASM, MIF Module, IPG, HSSD Fiber Optic Links, or GAP."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_ITOT_VDACDEL_SETTLE
"GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. ITOT & VDAC_DEL did not settle to +/-%6.3fA in %6.3fusec on the %b transition. Actual=%6.3fusec. Possible causes: Power Module FRUs, MIF Module, or Load.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_ICOIL_IGRAD_TOLERANCE
"GRADIENT DRIVER TESTS - Dynamic Test Failed. The ICOIL_IGRADDEL_SETTLE_TIME tolerance is set to zero or a negative value in /w/config/gdt_tolerances.cfg. Please reset this value and run test again."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DYN_ITOT_VDAC_TOLERANCE
"GRADIENT DRIVER TESTS - Dynamic Test Failed. The ITOT_VDACDEL_SETTLE_TIME tolerance is set to zero or a negative value in /w/config/gdt_tolerances.cfg. Please reset this value and run test again."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DTUNE_MIF_REG_A_CFG
"GRADIENT DRIVER TESTS - Digital Tune Test MIF %c Axis Config Error. Required: Current Sum=0, Low-side Invert=1, Serv Mode=0, Manual Ena=0. Current: Current Sum=%d, Low-side Invert=%d, Serv Mode=%d, Manual Ena=%d. No tests will be run on this axis.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DTUNE_IGRAD_FLATLINE
"GRADIENT DRIVER TESTS - Digital Tune Test failed on %c Axis. IGRAD data does not follow the input waveform. Possible causes: GASM, GRAM Module, GAP Module, or cables between GAP and GRAM.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_GRAM_X_NO_DIGITAL_TUNE
"GRADIENT DRIVER TESTS GAP was unsuccessful accessing X Axis Digital Tuning Bd. Check X Axis Digital Tune Bd cables. If there is no GRAM, or all GRAMs have Analog Tune Bds, change digiTuningBoard to `no' in the MRconfig.cfg file and reset TPS.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_GRAM_Y_NO_DIGITAL_TUNE
"GRADIENT DRIVER TESTS GAP was unsuccessful accessing Y Axis Digital Tuning Bd. Check Y Axis Digital Tune Bd cables. If there is no GRAM, or all GRAMs have Analog Tune Bds, change digiTuningBoard to `no' in the MRconfig.cfg file and reset TPS.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_GRAM_Z_NO_DIGITAL_TUNE
"GRADIENT DRIVER TESTS GAP was unsuccessful accessing Z Axis Digital Tuning Bd. N Check Z Axis Digital Tune Bd cables. If there is no GRAM, or all GRAMs have Analog Tune Bds, change digiTuningBoard to `no' in the MRconfig.cfg file and reset TPS.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_GRAM_X_TUNE_VERIFY
"GRADIENT DRIVER TESTS GAP was unsuccessful accessing Z Axis Digital Tuning Bd. Check Z Axis Digital Tune Bd cables. If there is no GRAM, or all GRAMs have Analog Tune Bds, change digiTuningBoard to `no' in the MRconfig.cfg file and reset TPS.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_GRAM_Y_TUNE_VERIFY
"GRADIENT DRIVER TESTS GAP was unsuccessful communicating with the Y Axis Digital Tuning Board. Possible causes are failed Digital Tuning Board, GRAM Control Board or Connectors. After checking connections, please reset TPS.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_GRAM_Z_TUNE_VERIFY
"GRADIENT DRIVER TESTS GAP was unsuccessful communicating with the Z Axis Digital Tuning Board. Possible causes are failed Digital Tuning Board, GRAM Control Board or Connectors. After checking connections, please reset TPS.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DTUNE_ONE_CASE_FAILED
"GRADIENT DRIVER TESTS - Digital Tune Test failed on %c Axis. 1 case out of %d failed: time constant=Tau_%d. Possible causes: Digital Tuning Board.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DTUNE_MULTIPLE_CASES_FAILED "GRADIENT DRIVER TESTS - Digital Tune Test failed on %c Axis. %d cases out of %d failed. Largest time constant=Tau_%d. Possible causes: GRAM to Digital Tuning Board cables, GRAM Module, GASM, or Digital Tuning Board.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DTUNE_INVALID_TESTCASE
"Internal GAP software error. Test case number is not between %d and %d. Case Selected: %d. If the GAP software is running okay ( the GAP Board LED is blinking with a period of 5 seconds ), then this is a software bug; write a CQA."
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DTUNE_OFFSET_RANGE
"GRADIENT DRIVER TESTS - Digital Tune Test failed on %c Axis. I_GRAD Offset out of range. Actual=%5.3fA; Limits=+/-%5.3fA. Possible causes: GRAM or Digital Tuning Bd.->"
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GDT_DTUNE_GAIN_RANGE
"GRADIENT DRIVER TESTS - Digital Tune Test failed on %c Axis. I_GRAD Gain out of range. Actual=%5.3fA; Limits=%4.2f to %4.2fA. Causes: GRAM or Digital Tuning Bd.->"
Extended Error: No Additional Information Is Available For This Error Code
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_MGRAM_LVPS_UV_FAULT
The GIP reported a %c Axis miniGRAM Low Voltage Power Supply Undervoltage Fault. Try swapping the miniGRAM Control Board or the entire miniGRAM axis to isolate the problem.-> .->"
Extended Error: Suspect the ± 15V power supply on the miniGRAM Control Board.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_MGRAM_OC_FAULT
The GIP reported a %c Axis miniGRAM OverCurrent Fault. Try swapping the miniGRAM Control Board, or the entire miniGRAM axis, or the miniGRAM Gate Driver Board, or the GPM, or the GIP to isolate the problem.-> .->"
Extended Error: The following conditions can cause this ERROR:
a) >140A average current (OCAVG LED DS7)
b) >275A peak current (OCINST LED DS8)
c) >80% Pulse Width Modulation (OCDUTY LED DS6)
d) >800,000 Amp transitions/sec (OCDUTY LED DS6) If this condition, suspect the PSD. Remove the JP1 located on miniGRAM control Board to latch the appropriate LED. If this error occurs 4 more times, 2241548 will be reported and you will have to cycle power to the GRAM Power Supply to reset it.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_MGRAM_OC_FAULT
The GIP reported a %c Axis miniGRAM OverCurrent Fault. Try swapping the miniGRAM Control Board, or the entire miniGRAM axis, or the miniGRAM Gate Driver Board, or the GPM, or the GIP to isolate the problem.->
Extended Error: This occurs if miniGRAM Power Supply voltage is > 850 VDC. Measure the voltage at J2 on the front of the miniGRAM Control Board; pin 8(Vbus+), pin 20(Vbus-) should be 7.5V + 0.3V. Swap miniGRAM cables to isolate between miniGRAM and miniGRAM Power Supply. If error follows miniGRAM, swap miniGRAM Control Boards to further isolate cause and replace the defective component. If this error occurs 4 more times, 2241547 will be reported and you will have to cycle power to the GRAM Power Supply to reset it.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_MGRAM_UV_FAULT
The GIP reported a %c Axis miniGRAM UnderVoltage Fault. Try swapping the miniGRAM Control Board, or the entire miniGRAM axis, or the miniGRAM Power Supply to isolate the problem. ->
Extended Error: This error occurs if the miniGRAM Power Supply voltage is < 300VDC. Measure the voltage at J2 on the front of the miniGRAM Control Board; pins 8(Vbus+), 20(Vbus-) should be 7.5V + 0.3V. Swap miniGRAM cables to isolate between miniGRAM and miniGRAM Power Supply. If error follows miniGRAM, swap miniGRAM Control Boards to further isolate cause and replace the defective component.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_GPM_XSISTOR_FAULT
The GIP reported a Transistor Fault on the %c Axis of the GPM. This fault could be related to noise. Possible causes: Cable between the GIP and GPM,%c Axis GPM Main Board or Output Shelf. ->
Extended Error: If the transistor fault happens immediately when the scanner goes to Ready, this indicates a shorted transistor and the Output Shelf for this axis will have to be replaced. If this error occurs 4 more times, 2241546 will be reported and you will have to cycle power to the GPM Power Supply to reset it. If the fault is intermittent, swap the GPM Main Board for the failing axis with another Main Board to isolate the cause of the fault to the Main Board or the Output Shelf. Replace the component that reproduces the fault.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_GPMPS_FAULT
The GIP reported a GPM Power Supply Fault. Check the GPM or the GPM Power Supply. ->
Extended Error: This error can be caused by Overtemp, Overcurrent, or Overvoltage conditions on GPM Power Supply. If the error occurs 4 more times, error 2241550 will be generated and power to the GPM Power Supply will need to be cycled to reset it. If error sequence reoccurs then remove output cables from the back of the GPM one at a time to isolate to GPM axis (you must always have at least one output connected or a Power Supply fault will occur.). Note: while running with an output disconnected from an axis, you can ignore error 2241522 or 2242045 for that axis.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_MGRAMPS_FAULT
The GIP reported a miniGRAM Power Supply Fault. Check GRAM Tuning, the miniGRAM, or the miniGRAM Power Supply. ->
Extended Error: This error can be caused by Overtemp, Overcurrent, or Overvoltage conditions on GRAM Power Supply. If this error occurs 4 more times, error 2241549 will be generated and then power to the GRAM Power Supply will need to be cycled to reset it. If the error sequence reoccurs then remove output cables from miniGRAM's one at a time to isolate to an axis (you must always have at least one output connected or an Overload error will stop the diagnostics). Note: while running with an output disconnected from an axis, you can ignore error 2241516 or 2242039 for that axis.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_MGRAM_IDIST_FAULT
The GIP reported a %c Axis Current Distortion Fault. Another fault reported in the log could be the cause of this fault. Possible causes: GRAM Tuning, miniGRAM, components of the %c Axis GPM, GIP, or cables. ->
Extended Error: The output current did not follow the commanded current. If this error is reported following another fault that shuts don the axis, focus on troubleshooting the previous error reported. Other causes: If this is a new installation, check output cabling to the gradient coil. Connect scope to DAC_I for appropriate axis on 37 sub-D connector on front GIP panel. Connect scope ground to gnd. on GIP front panel. Signal at ICOIL BNC for appropriate axis on 37 sub-D connector on front of GIP panel should be identical but inverted.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_GPM_SHELF_OT_FAULT
The GIP reported a Shelf Over Temp Fault on the %c Axis of the GPM. Wait for the temperature to cool before trying to scan.Cooling time may be in excess of 5 minutes. Make sure back door of Gradient Cabinet is closed. ->
Extended Error: The Shelf Overtemp Fault is sensed on the GPM. Check for the following:
a) Verify backdoor of gradient cabinet is closed
b) Excessive output current 9>100A RMS)
c) PPBM Vrail output malfuntion. Vrail could be stuck at high voltage ~190V.
d) If the scanner was using a custom PSD, suspect the PSD
e) If none of the above causes are the problem, then isolate between Main Board and Output Shelf for the failing axis by swapping with another axis.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_GPM_SUPPLY_FAULT
GPM. The GPM will recover when the Supply voltage changes to a safe range. Possible causes: %c Axis GPM PPBM, Main Board, Output Shelf, or the GPM Power Supply. ->
Extended Error: This error is generated by the PPBM and would occur under the following conditions
a) PPBM was Overtemp
b) Input voltage from GPM Power Supply (in Ready) was <80V or >210V
c) Average output current >100A.
If these are not the problem, then replace the PPBM. If the error is intermittent, swap PPBM's.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_GPM_LONG_OVERLOAD_FAULT
The GIP reported a Long Overload Fault on the %c Axis of the GPM. Possible causes: %c Axis GPM. Try swapping the GPM Axis connections to isolate the problem. ->
Extended Error: Long overload (overload that is >50 msec in duration) is sensed on the GPM when the output voltage does not follow the commanded voltage. Use a scope to verify the input signal VCNTRL for appropriate axis on front panel of GIP and the output signal on GPM BNC (Vout) are the same. Connect scope ground to gnd on GIP. Long Overloads will shutdown scan and could be indicative of image quality or stability problems.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_MGRAM_HS_OT_FAULT
The GIP reported a %c Axis miniGRAM Heatsink OverTemp Fault
Wait for the temperature to cool before trying to scan. Cooling time may be in excess of 5 minutes. Make sure back door of Gradient Cabinet is closed. Check miniGRAM Control Bd & min
Extended Error: The heatsink has exceeded 70 degrees Celsius. GIP receive circuitry could be suspect. Try swapping cables to miniGRAMs if this error reoccurs to isolate fault.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_GPMPS_READY_FAULT
The GPM Power Supply failed to go to Ready when commanded, orcame out of Ready. Possible causes: cable between GIP & GPMPower Supply, the GPM Power Supply, or the GIP.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_MGRAMPS_READY_FAULT
The miniGRAM Power Supply failed to go to Ready when commanded, or came out of Ready. Possible causes: cable between GIP & miniGRAM Power Supply, the miniGRAM Power Supply, or the GIP.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_AMP_DATA_FRAMING
Hardware Error - Gradient data framing error. The GIP reported a data framing error. Check the fiber optic clock cable between the Systems Cabinet and GIP. Check the IPG, TYME, and GIP Boards. Run fiber optic diagnostics. ->
Extended Error: Run fiberoptic diagnostics and gradient data link test.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_X_SHORT_OVERLOAD_FAULT
X Axis Gradient Overload Occurred. The X Axis of the GPM has reported an overload. An overload is the result of the GPM output voltage not following the input command. ->
Extended Error: Short overload (overload is <50 msec in duration) is sensed on the GPM when the output voltage does not follow the commanded voltage. Use a scope to verify the input signal VCNTRL on GIP (Test pt TBD) and the output signal on GPM BNC (Vout) are the same. Short Overloads will not shut down scan, but could be indicative of image quality or stability problems.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_Y_SHORT_OVERLOAD_FAULT
Y Axis Gradient Overload Occurred. The Y Axis of the GPM has reported an overload. An overload is the result of the GPM output voltage not following the input command. ->
Extended Error: Short overload (overload is <50 msec in duration) is sensed on the GPM when the output voltage does not follow the commanded voltage. Use a scope to verify the input signal VCNTRL on GIP (Test pt TBD) and the output signal on GPM BNC (Vout) are the same. Short Overloads will not shut down scan, but could be indicative of image quality or stability problems.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_Z_SHORT_OVERLOAD_FAULT
Z Axis Gradient Overload Occurred. The Z Axis of the GPM has reported an overload. An overload isthe result of the GPM output voltage not following the input command. ->
Extended Error: Short overload (overload is <50 msec in duration) is sensed on the GPM when the output voltage does not follow the commanded voltage. Use a scope to verify the input signal VCNTRL on GIP (Test pt TBD) and the output signal on GPM BNC (Vout) are the same. Short Overloads will not shut down scan, but could be indicative of image quality or stability problems.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_X_GPM_TJ_OT_FAULT
X Axis of the GPM reported a Transistor Junction OverTemp Fault. Wait for temp to cool before trying to scan. Cooling time may be in excess of 5 minutes. Gradient back door must be closed. Check GRAM Tuning, GPM X Axis Main Bd, PPBM, Output Sh
Extended Error: Transistor junction is hitting 200 degrees Celcius. The power module momentarily shutoff which can result in an overload or I-distortion fault. Long term reliability will be degraded on the output shelf if operation continues at these high temperatures.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_Y_GPM_TJ_OT_FAULT
Y Axis of the GPM reported a Transistor Junction OverTemp Fault. Wait for temp to cool before trying to scan. Cooling time may be in excess of 5 minutes. Gradient back door must be closed. Check GRAM Tuning, GPM Y Axis Main Bd, PPBM, Output Sh
Extended Error: Transistor junction is hitting 200 degrees Celcius. The power module momentarily shutoff which can result in an overload or I-distortion fault. Long term reliability will be degraded on the output shelf if operation continues at these high temperatures.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_Z_GPM_TJ_OT_FAULT
Z Axis of the GPM reported a Transistor Junction OverTemp Fault. Wait for temp to cool before trying to scan. Cooling time may be in excess of 5 minutes. Gradient back door must be closed. Check GRAM Tuning, GPM Z Axis Main Bd, PPBM, Output Sh
Extended Error: Transistor junction is hitting 200 degrees Celcius. The power module momentarily shutoff which can result in an overload or I-distortion fault. Long term reliability will be degraded on the output shelf if operation continues at these high temperatures.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_X_MGRAM_OVRANGE_FAULT
X Axis Gradient Data Overrange Occurred. The GIP detected an error in the incoming High Speed Data from the IPG. Swap fiber optics at the Systems Cabinet. Run fiber optic diagnostics.
Extended Error: If simultaneously reported framing error, then you should troubleshoot the framing error not this overrange error. If no framing error, this error could be caused by faulty data generation hardware on the IPG, or faulty data receive hardware on the GIP. If swapping data lines at the Systems Cabinet causes the fault to change axes then suspect the IPG. Run gradient data link diagnostic to confirm overrange error.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_Y_MGRAM_OVRANGE_FAULT
Y Axis Gradient Data Overrange Occurred. The GIP detected an error in the incoming High Speed Data from the IPG. Swap fiber optics at the Systems Cabinet. Run fiber optic diagnostics.
Extended Error: If simultaneously reported framing error, then you should troubleshoot the framing error not this overrange error. If no framing error, this error could be caused by faulty data generation hardware on the IPG, or faulty data receive hardware on the GIP. If swapping data lines at the Systems Cabinet causes the fault to change axes then suspect the IPG. Run gradient data link diagnostic to confirm overrange error.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_Z_MGRAM_OVRANGE_FAULT
Z Axis Gradient Data Overrange Occurred. The GIP detected an error in the incoming High Speed Data from the IPG. Swap fiber optics at the Systems Cabinet. Run fiber optic diagnostics.
Extended Error: If simultaneously reported framing error, then you should troubleshoot the framing error not this overrange error. If no framing error, this error could be caused by faulty data generation hardware on the IPG, or faulty data receive hardware on the GIP. If swapping data lines at the Systems Cabinet causes the fault to change axes then suspect the IPG. Run gradient data link diagnostic to confirm overrange error.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_GPM_FAILED_READY
The %c Axis of the GPM failed to go to Ready when commanded. Check the cable between the GIP & GPM, and the LED status on the %c Axis of the GPM. Guarantee that the switch on the GPM is set to GIP Control. Swap axis GPM Main Bd.
Extended Error: If the GPM failed to go to Ready when commanded, the GPM to GIP cable is suspect. Or there could be a fault on the GPM that is not being reported to the GIP. The faults can be seen by viewing the LED's through the Main Board Tray by pulling the GPM out momentarily (Remember, do not scan with the GPM pulled out of the cabinet, because the GPM needs the air flow from the cabinet). Note: it is normal for the Standby LED or the Ready LED on the GPM to be lit when the GPM PS is not enabled.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_MGRAM_FAILED_READY
The %c axis miniGRAM failed to go to Ready when commanded. Check the cable between the GIP & miniGRAM, miniGRAM Ctrl Bd, GIP, and the LED status on the %c Axis miniGRAM.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_GPM_FAILED_STANDBY
The %c axis GPM failed to go to Standby when commanded. Check the cable between the GIP & GPM, and the LED status on the %c Axis of the GPM. Guarantee that the switch on the GPM is set toGIP Control.
Extended Error: The GPM failed to go to Standby when commanded. Check the status of the GPM by observing the Standby/Ready LED's on front of GPM. If the GPM is in Standby, then the status of GPM is not being reported properly, suspect GPM to GIP cable.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_MGRAM_FAILED_STANDBY
The %c axis miniGRAM failed to go to Standby when commanded. Check the cable between the GIP & miniGRAM, miniGRAM, GIP, and the LED status on the %c Axis miniGRAM.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_X_FAILED_RECOVERY
X Axis gradient error detected; recovery in progress.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_Y_FAILED_RECOVERY
Y Axis gradient error detected; recovery in progress.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_Z_FAILED_RECOVERY
Z Axis gradient error detected; recovery in progress.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_RECOVERY_DONE
The gradient system on the %c axis recovered successfully. There are no faults at the present time.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_GPM_OV_SPECIAL_RECV
The GIP reported a second Long Overload on the %c Axis of the GPM. Power cycle the main breaker on GPM Power Supply to recover from this condition. If this fault occurs again, swap the GPM axis. Run diagnostics.
Extended Error: Long Overload (overload that is >50 msec in duration) is sensed on the GPM when output voltage does not follow the commanded voltage. Use a scope to verify the input signal VCNTRL on GIP (Test pt TBD) and the output signal on GPM BNC (Vout) are the same. Long Overloads will shutdown a scan and could be indicative of image quality or stability problems.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_GPM_TR_SPECIAL_RECV
The GIP reported a second Transistor Fault on the %c Axis of the GPM. Power cycle the main breaker on GPM Power Supply to recover from this condition. If this fault occurs again, replace the GPM %c Axis Output Shelf.
Extended Error: If a transistor fault happens immediately upon going to Ready, this indicates a shorted transistor; in this case replace Output Shelf. If this fault is intermittent, swap Main Boards to isolate between it and Output Shelf. Replace the component that reproduces the fault.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_MGRAM_OV_SPECIAL_RECV
The GIP reported several %c Axis miniGRAM OverVoltage Faults. Power cycle the main breaker on the miniGRAM Power Supply to recover from this condition. If this fault occurs again, check the miniGRAM Control Bd, miniGRAM, or miniGRAM Power Supply
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_MGRAM_OC_SPECIAL_RECV
The GIP reported several %c Axis miniGRAM OverCurrent Faults. Power cycle main breaker on miniGRAM Power Supply to recover from this condition. If this fault occurs again, check miniGRAM Control Bd, miniGRAM, miniGRAM Gate Driver Bd, GPM, or GIP
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_MGRAM_PS_SPECIAL_RECV
The GIP reported several miniGRAM Power Supply Faults. After the miniGRAM Power Supply fault LED turns off, power cycle main breaker on Power Supply to recover. If this fault occurs again, check GRAM Tuning, the miniGRAM, miniGRAM Power Supply
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_GPM_PS_SPECIAL_RECV
The GIP reported several GPM Power Supply Faults. After the GPM Power Supply fault LED turns off, power cycle the main breaker on Power Supply to recover. If this fault occurs again, check the GPM & the GPM Power Supply. Run Diagnostics.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_LATCHED_GPM_SPLY_FAULT
The GIP reported a PPBM Fault on the %c Axis of the GPM. The GPM will recover when the Supply voltage changes to a safe range.
Possible causes: %c Axis GPM PPBM, Main Board, Output Shelf, or the GPM Power Supply.
Extended Error: This fault occurs when the GPM initially goes to Ready when commanded, but then gets an error while in Ready. This fault is generated by the PPBM and will occur with any of the following conditions:
a) Overtemp
b) Input voltage from GPM Power Supply (in Ready) was < 80V or > 210 V
c) Average output current >100A.
If these are not the problem, then replace the PPBM. If the fault is intermittent, swap PPBM's to verify the failure. If swapping does not confirm a bad PPBM the error could be due to the GPM main board, output shelf, or the GIP.
Return To Top ---------------------------------------------------------
ERROR: EM_GIP_LATCHED_GPM_SPLY_SPECIAL_RECV
The GIP reported several PPBM Faults on the %c Axis of the GPM. Power cycle the main breaker on the GPM Power Supply to recover from this condition. If this fault occurs again, check the GPM & the GPM Power Supply.
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_MGRAM_LVPS_UV_FAULT
GRADIENT DRIVER TESTS - %c Axis Fault Occurred. The GIP reported a %c Axis miniGRAM Low Voltage Power Supply Undervoltage Fault. Try swapping the miniGRAM Control Board or the entire miniGRAM axis to isolate the problem. %b
Extended Error: Suspect the + 15V power supply on the miniGRAM Control Board
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_MGRAM_OC_FAULT
GRADIENT DRIVER TESTS - %c Axis Fault Occurred. The GIP reported a %c Axis miniGRAM OverCurrent Fault. Try swapping the miniGRAM Control Board, or entire miniGRAM axis, or miniGRAM Gate Driver Bd, or GPM, or GIP to isolate problem. %b
Extended Error: The following conditions can cause this ERROR:
a) >140A average current (OCAVG LED DS7)
b) >275A peak current (OCINST LED DS8)
c) >80% Pulse Width Modulation (OCDUTY LED DS6)
d) >800,000 Amp transitions/sec (OCDUTY LED DS6) If this
condition, suspect the PSD.
Remove the JP1 located on miniGRAM control Board to latch the appropriate LED. If this error occurs 4 more times, 2241548 will be reported and you will have to cycle power to the GRAM Power Supply to reset it.
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_MGRAM_OV_FAULT
GRADIENT DRIVER TESTS - %c Axis Fault Occurred. The GIP reported a %c Axis miniGRAM OverVoltage Fault. Try swapping the miniGRAM Control Board, or the entire miniGRAM axis, or the miniGRAM Power Supply to isolate the problem. %b
Extended Error: This occurs if miniGRAM Power Supply voltage is > 850 VDC. Measure the voltage at J2 on the front of the miniGRAM Control Board; pins 8(Vbus+), 20(Vbus-) should be 7.5V + 0.3V. Swap miniGRAM cables to isolate between miniGRAM and miniGRAM Power Supply. If error follows miniGRAM, swap miniGRAM Control Boards to further isolate cause and replace the defective component. If this error occurs 4 more times, 2241547 will be reported and you will have to cycle power to the GRAM Power Supply to reset it.
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_MGRAM_UV_FAULT
GRADIENT DRIVER TESTS - %c Axis Fault Occurred. The GIP reported a %c Axis miniGRAM UnderVoltage Fault. Try swapping the miniGRAM Control Board, or the entire miniGRAM axis, or the miniGRAM Power Supply to isolate the problem. %b
Extended Error: This error occurs if the miniGRAM Power Supply voltage is < 300VDC. Measure the voltage at J2 on the front of the miniGRAM Control Board; pins 8(Vbus+), 20(Vbus-) should be 7.5V + 0.3V. Swap miniGRAM cables to isolate between miniGRAM and miniGRAM Power Supply. If error follows miniGRAM, swap miniGRAM Control Boards to further isolate cause and replace the defective component
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_GPM_XSISTOR_FAULT
GRADIENT DRIVER TESTS - %c Axis Fault Occurred. The GIP reported a Transistor Fault on the %c Axis of the GPM. This fault could be related to noise. Possible causes: Cable between the GIP and GPM, Axis GPM Main Board or Output Shelf. %b
Extended Error: If the transistor fault happens immediately when the scanner goes to Ready, this indicates a shorted transistor and the Output Shelf for this axis will have to be replaced. If this error occurs 4 more times, 2241546 will be reported and you will have to cycle power to the GPM Power Supply to reset it. If the fault is intermittent, swap the GPM Main Board for the failing axis with another Main Board to isolate the cause of the fault to the Main Board or the Output Shelf. Replace the component that reproduces the fault.
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_GPMPS_FAULT
GRADIENT DRIVER TESTS - Fault Occurred. The GIP reported a GPM Power Supply Fault. Check the GPM or the GPM Power Supply. %b
Extended Error: This error can be caused by Overtemp, Overcurrent, or Overvoltage conditions on GPM Power Supply. If the error occurs 4 more times, error 2241550 will be generated and power to the GPM Power Supply will need to be cycled to reset it. If error sequence reoccurs then remove output cables from the back of the GPM one at a time to isolate to GPM axis (you must always have at least one output connected or a Power Supply fault will occur.) Note: while running with an output disconnected from an axis, you can ignore error 2241522 or 2242045 for that axis.
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_MGRAMPS_FAULT
GRADIENT DRIVER TESTS - Fault Occurred. The GIP reported a miniGRAM Power Supply Fault. Check GRAM Tuning, the miniGRAM, or the miniGRAM Power Supply. %b
Extended Error: This error can be caused by Overtemp, Overcurrent, or Overvoltage conditions on GRAM Power Supply. This error is reported for the first occurrence only; then if the error occurs 4 more times, error 2241549 will be generated. Power to the GRAM Power Supply will need to be cycled to reset it. If the error sequence reoccurs then remove output cables from miniGRAM's one at a time to isolate to an axis (you must always have at least one output connected or a Power Supply fault will occur.) Note: while running with an output disconnected from an axis, you can ignore error 2241516 or 2242039 for that axis.
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_VLO_GPM_GIP
GRADIENT DRIVER TESTS - Static Test Failed. VLO_GPM had %d failures out of %d. Most likely related to a GPM Power Supply, GIP Board, or GPM problem.%b
Extended Error: Try isolating to single axis by putting other axes in StandBy; configure switch on front of GPM to determine if loading down and disconnect associated power cable at GPM PS. And check voltage at Power supply input at back of GPM; should be 188 + 8VDC. If no loading down replace GPM PS.
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_VLO_GRAM_GIP
GRADIENT DRIVER TESTS - Static Test Failed. VLO_GRAM had %d failures out of %d. Most likely related to a miniGRAM, miniGRAM Power Supply, or GIP Board problem. %b
Extended Error: Try isolating to single axis by putting other axes in StandBy; configure switch on front of GPM to determine if loading down and disconnect associated power to that miniGRAM. And check voltage at Power supply input of GRAM; Vbus+ and Vbus- at front of minigram should be 5.5 + 0.2VDC (HiSpeed). 7.6 + 0.2 (EchoSpeed)If no loading down replace GRAM PS.
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_VRAIL_ALL_GIP
GRADIENT DRIVER TESTS - Static Test Failed on ALL Axes. VRAIL had %d failures out of %d. Most likely due to noisy signals between the GIP & GPM. %b
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_VRAIL_GIP
GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VRAIL had %d failures out of %d. Possible causes: This axis of the GPM, the GPM Power Supply, or the GIP. %b
Extended Error: Suspect the PPBM is in Ready when it is not expected to be. Swap data cables from GIP to GPM and GRAM's with another axis. Then Swap main bd then PPBM to isolate.
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_LDIDT_GIP
GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. LDIDT had %d failures out of %d. Possible causes: the GIP Board. %b
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_VFILT_GIP
GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VFILT had %d failures out of %d. Possible causes: the miniGRAM, miniGRAM Ctrl Bd, GIP Board, or cables between miniGRAM & GIP. %b
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_VOUT_GIP
GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VOUT had %d failures out of %d. Possible causes: This axis of the GPM, cables, or the GIP Board. %b
Extended Error: Swap Main Bd first; most likely that or swap cables to eliminate the Output Shelf; if didn't follow the GPM swapping, then suspect GIP or cables between
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_PXTEMP_STDBY_RANGE
GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. PXTEMP had %d failures out of %d. Possible causes: this axis of the GPM, cables, or the GIP board. Static Standby Mode
Extended Error: Swap Main Bd first; most likely that or swap cables to eliminate the Output Shelf; if didn't follow the GPM swapping, then suspect GIP or cables between
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_PXTEMP_STDBY_DELTA
GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. PXTEMP exceeded Max Temp change. Possible causes: this axis of the GPM, cables, or the GIP board. Measured Delta=%6.3fC, Maximum Delta=%6.3fC. %b
Extended Error: Swap Main Bd first; most likely that or swap cables to eliminate the Output Shelf; if didn't follow the GPM swapping, then suspect GIP or cables between
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_NXTEMP_STDBY_RANGE
GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. NXTEMP had %d failures out of %d. Possible causes: this axis of the GPM, cables, or the GIP board. Static Standby Mode
Extended Error: Swap Main Bd first; most likely that or swap cables to eliminate the Output Shelf; if didn't follow the GPM swapping, then suspect GIP or cables between
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_NXTEMP_STDBY_DELTA
GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. NXTEMP exceeded Max Temp change. Possible causes: this axis of the GPM, cables, or the GIP board. Measured Delta=%6.3fC, Maximum Delta=%6.3fC. %b
Extended Error: Swap Main Bd first; most likely that or swap cables to eliminate the Output Shelf; if didn't follow the GPM swapping, then suspect GIP or cables between
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_VOUT_RDYVCC
GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VOUT had %d failures out of %d. Possible causes: this axis of the GPM, cables, or the GIP board. Static Ready Mode
Extended Error: Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP. Else swap Main Bd first, then PPBM, then swap cables to eliminate the Output Shelf.
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_VFILT_RDYVCC
GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VFILT had %d failures out of %d. Possible causes: the miniGRAM, cables to the GIP, the GIP board, or this axis of the GPM. Static Ready Mode
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: GRADIENT DRIVER TESTS
Static Test Failed on %c Axis. VRAIL had %d failures out of %d. Possible causes: this axis of the GPM, cables, or the GIP board.-> Static Ready Mode
Extended Error: Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP. Else swap Main Bd first, then PPBM, then swap cables to eliminate the Output Shelf.
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_VRAIL_RDYGRAM
GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VRAIL had %d failures out of %d. Possible causes: GIP Bd, the load, miniGRAM, this axis of the GPM, or GPM Power Supply.-> Static Ready GRAM Mode
Extended Error: Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP. If not then swap load cables at the back of miniGRAM's. If problem followed axes next isolate between miniGRAM and GPM (in main bd, PPBM and output shelf order). Then turn off power to gradient cabinet and disconnect GRAM output cables. Then check load resistance across terminals of the BRM (0.2 ohms); from terminal of load to ground (>1K ohms); and terminal of each axis to other axes (>1K ohms). Lastly GPM Power Supply. Note: use the disconnection and drive one axis at a time information in previous message
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_VFILT_RDYGRAM
GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VFILT had %d failures out of %d. Possible causes: GIP Bd, the load, miniGRAM, this axis of the GPM, or GPM Power Supply.-> Static Ready GRAM Mode
Extended Error: Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP. If not then swap load cables at the back of miniGRAM's. If problem followed axes next isolate between miniGRAM and GPM (in main bd, PPBM and output shelf order). Then turn off power to gradient cabinet and disconnect GRAM output cables. Then check load resistance across terminals of the BRM (0.2 ohms); from terminal of load to ground (>1K ohms); and terminal of each axis to other axes (>1K ohms). Lastly GPM Power Supply. Note: use the disconnection and drive one axis at a time information in previous message
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_VOUT_RDYGRAM
GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VOUT had %d failures out of %d. Possible causes: GIP Bd, the load, miniGRAM, this axis of the GPM, or GPM Power Supply.-> Static Ready GRAM Mode
Extended Error: Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP. If not then swap load cables at the back of miniGRAM's. If problem followed axes next isolate between miniGRAM and GPM (in main bd, PPBM and output shelf order). Then turn off power to gradient cabinet and disconnect GRAM output cables. Then check load resistance across terminals of the BRM (0.2 ohms); from terminal of load to ground (>1K ohms); and terminal of each axis to other axes (>1K ohms). Lastly GPM Power Supply. Note: use the disconnection and drive one axis at a time information in previous message
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_IERROR_RDYGRAM
GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. IERROR had %d failures out of %d. Possible causes: GIP Bd, the load, miniGRAM, this axis of the GPM, or GPM Power Supply.-> Static Ready GRAM Mode
Extended Error: Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP. If not then swap load cables at the back of miniGRAM's. If problem followed axes next isolate between miniGRAM and GPM (in main bd, PPBM and output shelf order). Then turn off power to gradient cabinet and disconnect GRAM output cables. Then check load resistance across terminals of the BRM (0.2 ohms); from terminal of load to ground (>1K ohms); and terminal of each axis to other axes (>1K ohms). Lastly GPM Power Supply. Note: use the disconnection and drive one axis at a time information in previous message
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_ICOIL_RDYGRAM
GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. ICOIL had %d failures out of %d. Possible causes: miniGRAM, this axis of the GPM, GPM Power Supply, the load, cables, or GIP.-> Static Ready GRAM Mode
Extended Error: Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP. If not then swap load cables at the back of miniGRAM's. If problem followed axes next isolate between miniGRAM and GPM (in main bd, PPBM and output shelf order). Then turn off power to gradient cabinet and disconnect GRAM output cables. Then check load resistance across terminals of the BRM (0.2 ohms); from terminal of load to ground (>1K ohms); and terminal of each axis to other axes (>1K ohms). Lastly GPM Power Supply. Note: use the disconnection and drive one axis at a time information in previous message
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_PXTEMP_RDYGRAM_RANGE
GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. PXTEMP had %d failures out of %d. Possible causes: components in the GPM (Main Board, PPBM, Output Shelf), or Gradient Cabinet Back Door is open. Static Ready GRAM Mode
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_NXTEMP_RDYGRAM_RANGE
GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. NXTEMP had %d failures out of %d. Possible causes: components in the GPM (Main Board, PPBM, Output Shelf), or Gradient Cabinet Back Door is open. Static Ready GRAM Mode
Extended Error: No Additional Information Is Available For This Error Code.
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_STAT_VLO_GPM_RDYGRAM_GIP
GRADIENT DRIVER TESTS - Static Test Failed on %c Axis. VLO_GPM had %d failures out of %d. Most likely related to a GPM Power Supply, GPM, or GIP Board problem.-> Static Ready GRAM Mode
Extended Error: Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP. If not then swap load cables at the back of miniGRAM's. If problem followed axes next isolate between miniGRAM and GPM (in main bd, PPBM and output shelf order). Then turn off power to gradient cabinet and disconnect GRAM output cables. Then check load resistance across terminals of the BRM (0.2 ohms); from terminal of load to ground (>1K ohms); and terminal of each axis to other axes (>1K ohms). Lastly GPM Power Supply. Note: use the disconnection and drive one axis at a time information in previous message
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_DYN_VCNTRL_FLATLINE
GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. VCNTRL data does not follow the input waveform. Possible causes: Fiber Optic cable between GIP and IPG, or the GIP Board.->
Extended Error: Check GRAM Tuning first, if it fails then suspect gradient hardware and troubleshoot after putting defaults in for short time constant eddy currents. Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP. If not then swap load cables at the back of miniGRAM's. If problem followed axes next isolate between miniGRAM and GPM (in main bd, PPBM and output shelf order). Then turn off power to gradient cabinet and disconnect GRAM output cables. Then check load resistance across terminals of the BRM (0.2 ohms); from terminal of load to ground (>1K ohms); and terminal of each axis to other axes (>1K ohms). Lastly GPM Power Supply. Note: use the disconnection and drive one axis at a time information in previous message
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_DYN_VOUT_FLATLINE
GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. VOUT data does not follow the input waveform. Most likely caused by this axis GPM or GIP Board.->
Extended Error: Check GRAM Tuning first, if it fails then suspect gradient hardware and troubleshoot after putting defaults in for short time constant eddy currents. Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP. If not then swap load cables at the back of miniGRAM's. If problem followed axes next isolate between miniGRAM and GPM (in main bd, PPBM and output shelf order). Then turn off power to gradient cabinet and disconnect GRAM output cables. Then check load resistance across terminals of the BRM (0.2 ohms); from terminal of load to ground (>1K ohms); and terminal of each axis to other axes (>1K ohms). Lastly GPM Power Supply. Note: use the disconnection and drive one axis at a time information in previous message
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_DYN_IERROR_FLATLINE
GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. IERROR data does not follow the input waveform. Possible causes: Fiber Optic cable between GIP and IPG, or the GIP Board.->
Extended Error: Check GRAM Tuning first, if it fails then suspect gradient hardware and troubleshoot after putting defaults in for short time constant eddy currents. Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP. If not then swap load cables at the back of miniGRAM's. If problem followed axes next isolate between miniGRAM and GPM (in main bd, PPBM and output shelf order). Then turn off power to gradient cabinet and disconnect GRAM output cables. Then check load resistance across terminals of the BRM (0.2 ohms); from terminal of load to ground (>1K ohms); and terminal of each axis to other axes (>1K ohms). Lastly GPM Power Supply. Note: use the disconnection and drive one axis at a time information in previous message
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_DYN_VFILT_FLATLINE
GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. FILT data does not follow the input waveform. Possible causes: miniGRAM, cable between GIP and miniGRAM, or the GIP Board.->
Extended Error: Check GRAM Tuning first, if it fails then suspect gradient hardware and troubleshoot after putting defaults in for short time constant eddy currents. Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP. If not then swap load cables at the back of miniGRAM's. If problem followed axes next isolate between miniGRAM and GPM (in main bd, PPBM and output shelf order). Then turn off power to gradient cabinet and disconnect GRAM output cables. Then check load resistance across terminals of the BRM (0.2 ohms); from terminal of load to ground (>1K ohms); and terminal of each axis to other axes (>1K ohms). Note: use the disconnection and drive one axis at a time information in previous message
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_DYN_VCNTRL_VOUT_SETTLE
GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. VCNTRL & VOUT did not match within tolerances %d out of %d samples. Worst case delta=%6.3fV. Check GRAM Tuning, axis GPM, GIP, Power Supplies, miniGRAM, cables.->
Extended Error: Check GRAM Tuning first, if it fails then suspect gradient hardware and troubleshoot after putting defaults in for short time constant eddy currents. Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP. If not then swap load cables at the back of miniGRAM's. If problem followed axes next isolate between miniGRAM and GPM (in main bd, PPBM and output shelf order). Then turn off power to gradient cabinet and disconnect GRAM output cables. Then check load resistance across terminals of the BRM (0.2 ohms); from terminal of load to ground (>1K ohms); and terminal of each axis to other axes (>1K ohms). Lastly GPM Power Supply. Note: use the disconnection and drive one axis at a time information in previous message
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_DYN_IERROR_SETTLE
GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. ERROR did not settle to +/-%6.3fA in %6.3fusec on the %b transition. Actual=%6.3fusec. Check GRAM Tuning, GIP, miniGRAM, axis GPM FRUs, or Power Supplies.->
Extended Error: Check GRAM Tuning first, if it fails then suspect gradient hardware and troubleshoot after putting defaults in for short time constant eddy currents. Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP. If not then swap load cables at the back of miniGRAM's. If problem followed axes next isolate between miniGRAM and GPM (in main bd, PPBM and output shelf order). Then turn off power to gradient cabinet and disconnect GRAM output cables. Then check load resistance across terminals of the BRM (0.2 ohms); from terminal of load to ground (>1K ohms); and terminal of each axis to other axes (>1K ohms). Lastly GPM Power Supply. Note: use the disconnection and drive one axis at a time information in previous message
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_DYN_VFILT_AVE_RANGE1
GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. VFILT Average was out of range on the Max to Min Transition. Actual=%6.3fV. Check GRAM Tuning, GIP, miniGRAM, and cables.->
Extended Error: Check GRAM Tuning first, if it fails then suspect gradient hardware and troubleshoot after putting defaults in for short time constant eddy currents. Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP.. Note: use the disconnection and drive one axis at a time information in previous message
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_DYN_VFILT_AVE_RANGE2
GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. VFILT Average was out of range on the Min to Max Transition. Actual=%6.3fV. Check GRAM Tuning, GIP, miniGRAM, and cables.->
Extended Error: Check GRAM Tuning first, if it fails then suspect gradient hardware and troubleshoot after putting defaults in for short time constant eddy currents. Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP.. Note: use the disconnection and drive one axis at a time information in previous message
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_DYN_VFILT_MAX_RIPPLE1
GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. VFILT Maximum ripple exceeded on the Max to Min Transition. Actual Maximum=%6.3fV. Average=%6.3fV. Check the miniGRAM, GIP, and cables.->
Extended Error: Check GRAM Tuning first, if it fails then suspect gradient hardware and troubleshoot after putting defaults in for short time constant eddy currents. Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP.. Note: use the disconnection and drive one axis at a time information in previous message
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_DYN_VFILT_MAX_RIPPLE2
GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. VFILT Maximum ripple exceeded on the Min to Max Transition. Actual Maximum=%6.3fV. Average=%6.3fV. Check the miniGRAM, GIP, and cables.->
Extended Error: Check GRAM Tuning first, if it fails then suspect gradient hardware and troubleshoot after putting defaults in for short time constant eddy currents. Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP.. Note: use the disconnection and drive one axis at a time information in previous message
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_DYN_VFILT_MIN_RIPPLE1
GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. VFILT Minimum ripple too small on the Max to Min Transition. Actual Minimum=%6.3fV. Average=%6.3fV. Check the miniGRAM, GIP, and cables.->
Extended Error: Check GRAM Tuning first, if it fails then suspect gradient hardware and troubleshoot after putting defaults in for short time constant eddy currents. Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP.. Note: use the disconnection and drive one axis at a time information in previous message
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_DYN_VFILT_MIN_RIPPLE2
GRADIENT DRIVER TESTS - Dynamic Test failed on %c Axis. VFILT Minimum ripple too small on the Min to Max Transition. Actual Minimum=%6.3fV. Average=%6.3fV. Check the miniGRAM, GIP, and cables.->
Extended Error: Check GRAM Tuning first, if it fails then suspect gradient hardware and troubleshoot after putting defaults in for short time constant eddy currents. Swap miniGRAM and GPM data cables at GIP reports problem on same axis, replace the GIP.. Note: use the disconnection and drive one axis at a time information in previous message
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_LCOIL_ICOIL_FLATLINE
LCoil Adjustment failed on %c Axis. ICOIL data does not follow the input waveform.
Possible causes: check cables, this axis GPM, miniGRAM or GIP. Run Diagnostics.->
Extended Error: If static test failure troubleshoot per message text. If dynamic test fails on one axis, swap fiberoptic at Systems Cabinet and rerun dynamic tests. If dynamic test fails on all axes, verify the following signals while running a typical scan: DAC_I signals on J15 on front of GIP (X= pin 4; Y = pin 3; Z = pin2) compare to the ICOIL signals on BNC's on front of GIP (X=J16; Y =J17; Z =J18). These signals for each axis should be identical but inverted.
Return To Top ---------------------------------------------------------
ERROR: EM_SGDT_LCOIL_VCTRL_FLATLINE
LCoil Adjustment failed on %c Axis. VCTRL data does not follow the input waveform.
Possible causes: check cables, this axis GPM, miniGRAM or GIP. Run Diagnostics.->
Extended Error: If static test failure troubleshoot per message text. If dynamic test fails on one axis, swap fiberoptic at Systems Cabinet and rerun dynamic tests. If dynamic test fails on all axes, verify the following signals while running a typical scan: DAC_I signals on J15 on front of GIP (X= pin 4; Y = pin 3; Z = pin2) compare to the ICOIL signals on BNC's on front of GIP (X=J16; Y =J17; Z =J18). These signals for each axis should be identical but inverted.
Return To Top ---------------------------------------------------------