Quoted from frobozz:Someone else recently found that the other end of the USB cable for this board, the end plugged in to the PC cage in the head, was only plugged in about halfway. Check that end. If the board isn't recognized at all (based on the error message you reported) it's likely to be a USB cable problem, which usually means one end or the other isn't plugged in properly.
Quoted from frobozz:And you still get the "Check PFD board" message on startup? And in sensor calibration test they all appear red? So now see if anything on that board works. The hotrails (you can see in attract mode if they are working)? The spotlights (they have their own device test, do they move?) The two little status LEDs on that board, do they both blink at a fairly fast rate? (If you pull the USB cable while everything is powered up, you can see the slow default blink rate that they both should have... does plugging the USB cable back in make them both blink faster like they should?)
Next try pulling the "ethernet cable" type connections from the boards with the sensor, one by one while in sensor test. The shooter lane board and keyboard board are both easy, but for the upper playfield board you're going to have to follow the cables down and unplug them at the PFD board - just unplug both since it will be impossible to tell in place which one goes to the sensors. Unplug one, wait a moment, check screen, then on to the next. Do the remaining sensors come alive on the test screen at some point, i.e. is a bad board somehow stomping on all the sensors? If you unplug them all with no change, try plugging them back in one by one slowly in a different order, in case it was the last one you unplugged that was bad.
The way you try to identify a problem , and the cause , and go through it step by step , is the best I've seen .
You explain yourself so well , even a simpleton like me is able to understand