Bizhub C250 Hour glass

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • darkdjproject

    #1

    [Dead] Bizhub C250 Hour glass

    Hello all,

    I have a Develop Ineo+ 250 which is the same as the KM Bizhub C250.
    My machine stuck on the hour glass when power on.
    After contact with a company, they advised me to unplug the Hard Disk Drive, and Change the Memory, this didn't had any impact .

    Now i read often that this is a firmware error or NVRam problem.

    Is here someone who could help me with this problem or getting the firmware for this machine to fix the problem?

    I read the old topic: http://www.copytechnet.com/forums/ko...r-failure.html
    Which is outdated yet, and the download doesn't work anymore.

    To not bump a old thread i started a new one.

    Thanks in advance.
  • EarthKmTech
    Step aside, noob

    1,000+ Posts
    • May 2009
    • 2139

    #2
    Re: Bizhub C250 Hour glass

    is the lcd backlight lit or off ?

    i've had this caused by the pwb-m board (no backlight) and the NVRam (backlight on)

    You will know if its the pwb-m board as fw reloading will either never start at all or never complete the printer stage

    Comment

    • darkdjproject

      #3
      Re: Bizhub C250 Hour glass

      First of all Thanks for the reply,

      The LCD backlight is ON, and turns off after 6 minutes.

      Comment

      • copier tech
        Field Supervisor

        5,000+ Posts
        • Jan 2014
        • 8144

        #4
        Re: Bizhub C250 Hour glass

        Just sent you the C250 firmware, try that you might be lucky, let me know.
        Let us eat, drink, and be merry, because tomorrow we may die!

        For all your firmware & service manual needs please visit us at:

        www.copierfirmware.co.uk - www.printerfirmware.co.uk

        Comment

        • EarthKmTech
          Step aside, noob

          1,000+ Posts
          • May 2009
          • 2139

          #5
          Re: Bizhub C250 Hour glass

          yep, its not your pwb-m board.

          you may be lucky with a firmware reload.

          Failing this try the nic initialize first before the nvram initialize as i've had nic corruption cause this before too.

          Comment

          Working...