Sharp 6500 with PE 10 Fiery

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • spanky
    Trusted Tech

    250+ Posts
    • Sep 2012
    • 468

    #1

    Sharp 6500 with PE 10 Fiery

    This machine will tell the customer to remove paper from the stapler compiler, but only on the Fiery screen.

    If I go to the copy screen it does not tell me there is paper there and I am able to run copier.

    I go back to the Fiery screen and the message is still there to remove the paper.

    Have installed the Fiery software on the server again and it corrected the problem for a short period of time, had come back.

    I can reboot the Fiery and the message will disappear.
  • igi
    Service Manager

    1,000+ Posts
    • Apr 2009
    • 1507

    #2
    Re: Sharp 6500 with PE 10 Fiery

    hi
    make sure you got
    the latest firmware for the copier
    and latest fiery updates

    Comment

    • blackcat4866
      Master Of The Obvious

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

      #3
      Re: Sharp 6500 with PE 10 Fiery

      I take it on very good authority that the fix for this is installing Service Pack 2, with patch FIT156263 "false misfeed in CWS, no jam in machine".
      Just reloading system software isn't enough. There are a whole heap of patches which need to be also applied (in order) after applying SP2.
      Print out the system updates log to confirm all patches & SP's are installed.

      Personally, I don't see Sharp much any more, but my source is very reliable. =^..^=
      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

      • DavePo
        Trusted Tech

        250+ Posts
        • Jul 2008
        • 303

        #4
        Re: Sharp 6500 with PE 10 Fiery

        Originally posted by blackcat4866
        I take it on very good authority that the fix for this is installing Service Pack 2, with patch FIT156263 "false misfeed in CWS, no jam in machine".
        Just reloading system software isn't enough. There are a whole heap of patches which need to be also applied (in order) after applying SP2.
        Print out the system updates log to confirm all patches & SP's are installed.

        Personally, I don't see Sharp much any more, but my source is very reliable. =^..^=
        I have a similar situation except it is Command Workstation thinks Upper Stacker Door is open. Am in process of reloading system software as two of the patches installed twice.

        Comment

        • mojorolla
          The Wolf

          2,500+ Posts
          • Jan 2010
          • 2583

          #5
          Re: Sharp 6500 with PE 10 Fiery

          The new Fierys are shipping with Fiery version 1.1. This version has the SP1-SP3 patches built into it, if you are going to spend the time reloading, use 1.1. After installed, hook into the internet and it will update itself like Windows updates. I believe with 1.1, the only updates are for banner printing issues and a new version of Command Workstation.
          Over a year after release, still wrought with issues.....ugh.


          Last edited by mojorolla; 02-10-2015, 02:48 AM.
          Failing to plan is planning to fail!!!

          Comment

          • Tonerbomb
            AutoMajical Resolutionist

            Site Contributor
            2,500+ Posts
            • Feb 2005
            • 2589

            #6
            Re: Sharp 6500 with PE 10 Fiery

            Try running the latest version of cws??
            Mystic Crystal Revelations

            Comment

            • spanky
              Trusted Tech

              250+ Posts
              • Sep 2012
              • 468

              #7
              Re: Sharp 6500 with PE 10 Fiery

              Fiery update corrected problem

              Comment

              Working...