XFD Power-Up Diagnostics

The GP4 board has two status LEDs located on the front panel. One, labeled POWER, is always on when the GP board has power. The second one labeled HEARTBEAT LED flashes on and off with a period of five seconds and a 50 percent duty cycle, to indicate that the GP4 is executing application code. During boot mode, when there is a checksum failure (that is when the checksum in the flash for DSP1 application code does not match the checksum in the header), the HEARTBEAT LED flashes ON and OFF rapidly three times in a row. The boot code does not use any other blink code other than three blinks for checksum failure. See Table 1.

The CAN Status LED will indicate the CANOpen software state. The CAN status LED will blink two times during normal DSP1 application code execution. During boot mode when the boot code is downloading application code through CAN the CAN status LED will blink only once since the CAN will be in Pre-operational state. See Table 2.

The CAN Error LED will indicate any CAN network or hardware error. CAN Power Off error is a special case. CAN Power Off will not be indicated if CAN power was never detected since the last reset. More information on CAN States can be found in the USSS Communication Core SDD. See Table 3.

This test performs the checksum test of the DSP1 application code present in flash memory. The checksum is computed for the DSP1 application code and is compared with the checksum field present in the header. If the checksum test passes the application code is started, otherwise the HEARTBEAT LED starts flashing three times and the boot code starts downloading DSP1 application code through CAN. It should take about a minute to complete the downloading. After the download the GP4 board gets reset and the HEARTBEAT LED should flash on and off with a period of five seconds and a 50 percent duty cycle, to indicate that the GP4 is executing application code.

If the HEARTBEAT LED continues to have three blinks for more than a minute then the boot code flashing failed. In that case, verify that the CAN cabling is in place including the terminators and the CAN Power supply on the Drive Module is ON. If it keeps blinking three times even after verifying that the cables are in place, make sure the SCP is up in running and that the rest of the CAN link diagnostics pass. If none of these solve the issue, replace the GP4 board.

The CAN Error LED should remain OFF during the flash download. If it blinks with any of the above-mentioned sequence wait for at least a minute and then power cycle the GP4. This will force another download. If the CAN Error LED still remains ON for a minute even after the power cycle check that the CAN cable is connected including the terminator and make sure the CAN Power supply in the driver module is ON. Also verify that the rest of the CAN link diagnostics pass. Else, replace the GP4 board.

At power-up DSP1 application code checks if the FPGA has valid code in it. If it does not have valid code an error message is reported to the message log and the application code does not go to ready. In this case replace the GP4.

The Power-up Register Test checks several registers on the GP4 board. At the start of the register test, the contents of all registers used during the test are saved. Likewise, these registers are restored at the conclusion of the test. The register test begins with a rigorous pattern test. Each register is tested with all possible patterns in a counting sequence:0000,0001, … 1111. Because some registers on each board have bits that are read only, only read/write registers are tested. Bits that are read only or should not be altered are not changed via this test. Errors discovered through this test are logged to the message log. If any error is found, the Power-up Tests will abort and the application code will not go to ready. If an error message is logged, power cycle the GP4 once and if the problem persists replace the GP4.