C500

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • JSC
    Gimp

    500+ Posts
    • Dec 2006
    • 618

    #1

    C500

    Anyone seen a C500 do this before? Only from a print job using a fiery, it will start off fine then it will go nuts, it does not do it all the time but when it does go wrong the only way cure it is to delete the job and start again.
    The customer only use Mac's and is printing from Quark.
    Attached Files
    The gene pool could use a little chlorine.
  • WaveyDavey
    Technician

    50+ Posts
    • Sep 2008
    • 60

    #2
    looks like faulty video interface/card or cable seen it on other fiery's before

    Comment

    • JSC
      Gimp

      500+ Posts
      • Dec 2006
      • 618

      #3
      Originally posted by WaveyDavey
      looks like faulty video interface/card or cable seen it on other fiery's before
      Thanks, i'll try that next time.
      The gene pool could use a little chlorine.

      Comment

      • bigmark
        Technician
        • Sep 2008
        • 39

        #4
        it could also be the image processing board. negative images are a big issue with both the C500 and the C6500 fiery's and Creo's. try securing the cable so it doesnt move, use duct tape if necessary.

        Comment

        • Haroldbfix
          Trusted Tech

          100+ Posts
          • Feb 2008
          • 212

          #5
          Originally posted by JSC
          Anyone seen a C500 do this before? Only from a print job using a fiery, it will start off fine then it will go nuts, it does not do it all the time but when it does go wrong the only way cure it is to delete the job and start again.
          The customer only use Mac's and is printing from Quark.
          Yes its communication issue between the fiery and the copier, usually the interface cable is the corporate, however as it was suggested the IMPB can cause it as well also the card inside the Fiery that the cable connects, On the Creos they call it the CIC. Im not sure what fiery calls it.

          Comment

          • JSC
            Gimp

            500+ Posts
            • Dec 2006
            • 618

            #6
            Thanks for the input everyone. i'll let you all know the fix when i go back..... its working fine at the minute.
            The gene pool could use a little chlorine.

            Comment

            • ni311
              Senior Tech

              Site Contributor
              500+ Posts
              • May 2008
              • 658

              #7
              http://www.copytechnet.com/forums/ko...orruption.html
              Konica Minolta Error Codes - Explanations and Solutions

              Comment

              Working...