• Registered: 2011-03-04
  • Posts: 1

Topic: FEC Hardware test failure

Hello
I am writing in regard to an issue I am having with an ATL HDI 3000. I am an electronics technician and A+ tech. I am writing on behalf of one of my customers, a physician in the Fayetteville NC area. The issue we are having is as the topic lists a hardware failure on boot. The information provided is at best unclear. I am presented with a prompt after the boot process begins saying that FEC MOP reported a hardware error during bootup and then a code is listed 1902-1990-1306-5B307831
This may also be of some relevance, When the system nearly finishes the boot process I hear the sound of loud clicks like a hard drive thats reading from bad sectors or corrupted areas of the drive. I am assuming that the hard drive has taken it's last call except the system seems to operate normally other than the prompt that I am presented with. The error has been presented on numerous occasions over the last few months and now is appearing nearly every time the machine is booted. I was wondering if your experience with this equipment may be able to confirm my diagnosis or is the code provided pointing to another issue unrelated to the clicks I am hearing from inside the machine after boot?
I read in another post that the software is serialized to only operate on the hard drive that is currently installed. Would flashing the firmware and correcting the serial to match on a replacement drive be sufficient to facilitate a re-install of the ATL software?
There are a few utilities for older IBM or Hitachi SCSI drives that will allow such modifications of the drive data. Perhaps the utilities work with IDE drives as well. Either way before I tear in and start pulling the drive it's good to check upline.  Thanx for your help

  • Registered: 2011-02-18
  • Posts: 5

Re: FEC Hardware test failure

The hard drive is OK. The front-end controller is initializing the Scanhead Select module and that sound comes from a bunch of relays switching states. Those clicks are normal at the end of bootup.

The error, being isolated to the front end, is probably caused by a channel board test failure (since there are several channel boards in there wink). Don't have the specific failure tied to that error code.

You can run the Machine Comprehensive Test to see if that reveals more specifics on the failure.