MX-PEX2 booting

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Dustin(WOP)
    Trusted Tech

    100+ Posts
    • Apr 2009
    • 223

    #1

    MX-PEX2 booting

    Hello all,
    I am having an issue with an MX-7001N with a MX-PEX2 fiery controller attached. When machine is turned on, copier display says initializing print controller. It sits there for a little bit then clears. Then goes to "Booting Print Controller. Please Wait." message. This message stays on the screen for hours on end. The service display screen on the display shows "00". I took the fiery off the machine and made sure the machine will come ready without it and machine worked fine. Called tech support and they said to replace the IF harness from the fiery to the IF board on the MFP board. No change. Replaced the IF board mounted on the MFP board and still no go. Not sure what else to try.
    Anyone have any ideas?
    Sharp said the next step would be to replace the Main Board in the Feiry, but that is over $300 that I do not want to spend unless I know that will fix my issue. Thanks for the help!!!
  • mojorolla
    The Wolf

    2,500+ Posts
    • Jan 2010
    • 2583

    #2
    Re: MX-PEX2 booting

    Do you have all 7 software patches installed on the Fiery?

    Failing to plan is planning to fail!!!

    Comment

    • Dustin(WOP)
      Trusted Tech

      100+ Posts
      • Apr 2009
      • 223

      #3
      Re: MX-PEX2 booting

      all of the patches have been loaded as I had to reload system software about 6 months ago for a different issue.

      Comment

      • mojorolla
        The Wolf

        2,500+ Posts
        • Jan 2010
        • 2583

        #4
        Re: MX-PEX2 booting

        Does it have an LCT? There is a known issue with an LCT attached if the files are installed in the wrong order. I would try reloading the system software from Command Workstation. I also seem to remember Sharp no longer officially supporting Fiery so some of their answers I would take with a grain of salt.

        Failing to plan is planning to fail!!!

        Comment

        • blackcat4866
          Master Of The Obvious

          Site Contributor
          10,000+ Posts
          • Jul 2007
          • 22996

          #5
          Re: MX-PEX2 booting

          There are a few things that can cause this issue.

          1. Check the CPU fan clips are correctly in place. The PEX1 & PEX2 Fierys had many issues with the CPU fan clips breaking on one side, and not holding the fan onto the CPU correctly. This quickly leads to an overheating of the CPU, then lockup of the unit during bootup.

          2. Perform a clone of the engine & engine HDD, then run a NIC reset & NVRAM clear in 67-17 (with the Fiery controller removed from the machine). Reattach the Fiery controller, and run the full setup & network configuration/setup again through the Fiery menu. Make the clone just as a precaution, as its a backup of all settings.

          3. On both the older Bear Fierys (ARPE1 - ARPE3) and the Whale standard print controller, a faulty HDD will cause the same symptom (very long or locked bootup, usually followed by a F9-00 code). Check the HDD is installed correctly. A good tip is to check the HDD temperature just by touching it. I have seen a few faulty HDDs over the years be so hot that you couldn't touch them. They were obviously faulty and causing the issue.

          4. Re-flash the firmware on the engine. Many weird issues over the years have been sorted out with a Firmware reload.

          5. On the old ARPE2's, a constant bootup could also be caused by a problem with the power supply. Look for a constant LED on the motherboard.

          I've also seen this in the field, just by chance found that if the Fiery is powered on by its own power switch first, then allowed to perform its bootup sequence FIRST, then several minutes later power on the engine. The machine always come up to ready quite quickly.

          =^..^=
          If you'd like a serious answer to your request:
          1) demonstrate that you've read the manual
          2) demonstrate that you made some attempt to fix it.
          3) if you're going to ask about jams include the jam code.
          4) if you're going to ask about an error code include the error code.
          5) You are the person onsite. Only you can make observations.

          blackcat: Master Of The Obvious =^..^=

          Comment

          Working...