• Topic ID: id_15667659
  • Version: 1.11
  • Date: Jul 4, 2019 7:12:13 PM

Doing the coil ID stress diagnostic (DPP)

Depending on your service agreement, not all service tools, diagnostics, and utilities referenced in this document may be accessible. Contact your sales person for information on available service license packages.

Diagnostic path

Diagnostics > System Function > RF > Coil ID Stress Diagnostic

Diagnostics > Hardware Location > Magnet Room > Coil ID Stress Diagnostic

Figure 1. Coil ID stress diagnostic

Purpose

This diagnostic tests the communication path for retrieving and displaying coil ID information. It is intended to be used to troubleshoot intermittent coil detection or ID problems.

Components tested

  • RRxPPort
  • Cable track 25-pin DC interface
  • RxDist
  • ICE
  • Host

Requirements

One or more coils plugged into the system

Block diagrams

Test sequence

  1. Navigate to Coil ID Stress Diagnostic.
  2. To perform something other than the number of test iterations shown, enter a different value in the Total iterations (1-100) field.
  3. Click Run.
When the Coil ID Stress Diagnostic runs, the following operations are performed:
  • The SCP in ICE re-reads all coils connected to the RRxPPorts.
  • The SCP checks the coil present pins on the coil port cables (RRxPPort J3, J4).
  • For each coil port cable with the coil present pins shorted, the SCP starts a 1-wire read of the coil ID information from the 1-wire coil ID chip(s) in the coil.
  • When the 1-wire operations complete, the SCP communicates with the host to get the coil information from the coil database.
  • After all the coil connectors with a coil have been read, the sequence is run again until it reaches the number of iterations given.
  • After the host responds with the coil information or if the host communication is down, the SCP displays the coil ID information to the diagnostic screen.

Results

To be able to run the stress test, one or more coils must be detected. If no coils are detected, the diagnostic fails.

For each iteration, the stress test prints out the coil information read and error indications. Check the display for any differences in coil information between iterations. If any differences are noted between iterations, this could indicate an intermittent system problem.
notice: when checking or reseating cables, always turn the system power off, otherwise it may cause a system problem.
Table 1 Diagnostic results
Result Description GE field action
ERROR: This diagnostic cannot run due to HW emulation. Required hardware (IRF, Receiver, and coil ID) are emulated. Remove emulation from /w/config/mgd_stage, TPS reset, and retry diagnostic.
Bootup processing still running. Wait a minute and try again. TPS reset has failed, but hardware and firmware initialization required by this diagnostic is not complete yet. Wait a minute for initialization to complete, then retry the diagnostic.
ERROR: No DVMR fiber link to the RxDist module found. The SCP and RxDist are not communicating over the fiber link. Check subsequent error messages to determine possible cause for communication failure and next action. Possible causes include RxDist input power failure, internal RxDist power regulation failure, RxDist clock cable not attached or clock signal failure, bad RxDist SFP module. This error could also be caused by a bad or disconnected fiber cable between ICE and RxDist. Try running the DVMR Link Status Diagnostic.
ERROR: the ICE to RxDist cable is not connected. The ICE to RxDist 25-pin cable is required to be connected.
  1. Connect the ICE to RxDist 25-pin cable.
  2. Check and reseat the cable.
RRxPPort is communicating to the SCP over its fiber link, but RxDist does not detect that the RRxPPort 44-pin cable is connected. Check RxDist to RRxPPort 44-pin cable and try reseating it.
The RxDist detects a RRxPPort cable connection, but that RRxPPort does not have good digital power.
  1. Check RxDist to RRxPPort 44-pin cable and try reseating it.
  2. Replace the RRxPPort and/or RxDist.
The RxDist detects a RRxPPort cable connection, but that RRxPPort does not have a good clock signal.
  1. Check RxDist to RRxPPort 44-pin cable and try reseating it.
  2. Replace the RRxPPort and/or RxDist.
The RxDist detects a RRxPPort cable connection, but that RRxPPort does not have a good SFP module.
  1. Check RxDist to RRxPPort 44-pin cable and try reseating it.
  2. Try running the DVMR Link Status Diagnostic to measure SFP signal levels.
  3. If there were no power errors logged, replace the SFP modules in the RRxPPort.
The RxDist detects a RRxPPort cable connection, but that RRxPPort does not have DVMR link communication with ICE.
  1. Check RxDist to RRxPPort 44-pin cable and try reseating it.
  2. Try running the DVMR Link Status Diagnostic.
  3. If there were no SFP errors logged, replace the fiber cables between the RRxPPort and ICE according to the following error that states whether the low side or high side link is bad.
ERROR: RxDist analog power fault. RxDistribution analog power is bad.
RRxPPort 5V or 3.3V power is bad. Replace the RRxPPort.
RRxPPort -10V power is bad. Replace the RRxPPort.
note: This error can occur if cables are swapped when running the Coil Datapath Diagnostic. Make sure that the errors were logged during the Coil ID Diagnostic before replacing the RRxPPort.
RRxPPort +10V power is bad. Replace the RRxPPort.
note: This error can occur if cables are swapped when running the Coil Datapath Diagnostic. Make sure that the errors were logged during the Coil ID Diagnostic before replacing the RRxPPort.
RRxPPort has an intermittent power fault. Replace the RRxPPort.
ERROR: Not enough receiver fiber links found. ICE cannot communicate with enough receiver modules for this system configuration.
  1. Verify that enough receiver modules are connected to RxDist.
  2. Try running the DVMR Link Status Diagnostic.
  3. Check RxDist to RRxPPort 44-pin cabling.
ERROR: Not all receivers are in applications mode. Some receivers’ FPGA(s) are not running the application code yet.
  1. Look for the reason for code check failure in the error log.
  2. Wait and retry diagnostic.
  3. Replace receiver module with code check error.
ERROR: The DVMR links are not ready. Some DVMR link nodes are not ready.
  1. Look for the reason that the DVMR link is not ready in the error log.
  2. Try running the DVMR Link Status Diagnostic.
  3. Wait and retry diagnostic.
ERROR: Internal receiver diags have failed. Check error log for details. DPP runtime initial checks failed.
  1. Look for the reason that the startup checks failed in the error log.
  2. Run the receive chain BLD, receive chain DP.
(Error log) An RRX module did not echo a command value sent to it from ICE over its dual fiber cable. A DVMR link command from ICE to a receiver module failed. Look for DVMR link errors in the log and troubleshoot the device that caused the link to go down. Try running the DVMR Link Status Diagnostic.
Diagnostic aborted due to DVMR fiber link fault. DVMR link communication failed. Look for DVMR link errors in the log and troubleshoot the device that caused the link to go down. Try running the DVMR Link Status Diagnostic.
Diagnostic aborted due to a failed attempt to read a coil ID from port X. Could not read coil ID from port X.
  1. Check RRxPPort cable track connection for Port X.
  2. Run the receive chain DP.
  3. Look for DVMR link errors in the log and troubleshoot any device or link that caused the link to go down.
  4. Try running the DVMR Link Status Diagnostic.
A coil ID error has occurred. The SCP reports a failure to read the coil ID information over the 1-wire line to the coil ID chip.
  1. Check the coil ID 1-wire pins on the coil to make sure they are not bent.
  2. Try plugging in a different coil to the same port to check if the problem is internal to the coil. Or, use the Coil Datapath Diagnostic to troubleshoot the failure.
  3. Check the coil ID 1-wire line in the cabling between the coil port and the RRxPPort.
  4. If every item checks out successfully, try replacing the RRxPPort.
Coil is invalid. There is a problem with the information in the coil ID chip or coil database. Check that the coil is installed in the coil database.
No coils detected with coils connected. The RRxPport is not reporting that a coil is connected. This means that the coil present lines are broken between the coil and the RRxPPort.
  1. Check the coil present pins on the coil to make sure they are shorted, or plug in a different coil to the same port. Use the Coil Datapath Diagnostic to troubleshoot the failure.
  2. Check the coil present lines in the cabling between the coil connector and the RRxPPort.
  3. If every item checks out successfully, try replacing the RRxPport.
Coil ID reads timed out. Coil ID response from the host was not received.
  1. Check Ethernet communication between ICE and host.
  2. TPS reset and retry diagnostic.
  3. Reboot system and retry diagnostic.
The MCRv tool was detected. The MCRv tool is not allowed in this diagnostic. This diagnostic does not support the MCRv tool connected directly to the RRxPPort.
  1. Use the Coil Datapath Diagnostic to read the MCRv tool’s coil ID.
  2. Connect the MCRv tool to the coil connector and run this diagnostic.