KM2550 continuous printing

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

    100+ Posts
    • Oct 2012
    • 147

    KM2550 continuous printing

    Please find attach sample of print from KM2550 copier. Printer option is connected via usb. As usb cable is connected, printer starts printing continuously samples as attached. Please note smiley face in the upper left corner
    Any suggestions?
    Attached Files
    drugstore-onlinecatalog.com
  • kkendric
    Trusted Tech

    250+ Posts
    • Apr 2009
    • 301

    #2
    Re: KM2550 continuous printing

    Could be corrupted print drivers on the computer. Have you checked the computer for even hung print jobs?

    Comment

    • tech.gasm
      Technician
      • Sep 2010
      • 39

      #3
      Re: KM2550 continuous printing

      Originally posted by ldfrepairs
      Please find attach sample of print from KM2550 copier. Printer option is connected via usb. As usb cable is connected, printer starts printing continuously samples as attached. Please note smiley face in the upper left corner
      Any suggestions?
      Corrupt print drivers / faulty usb cable/port.

      Comment

      • blackcat4866
        Master Of The Obvious

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

        #4
        Re: KM2550 continuous printing

        The "garbage" you describe is usually a single line of smiley faces, hearts, or wing-dings on each page, usually hundreds of pages. It's called a PostScript error, but is not limited to the PostScript print emulation. The characters you see are the actual lines of code being sent to the printer, one line per page.

        You can get a PostScript error any time the printer cannot understand the print language emulation being sent to it. Here are a few of many possible causes:
        1) The print driver is selected to PCLXL (or PCL6: same thing), and the printer is selected to KPDL (or PostScript: same thing). Or vice versa. Or line printer, or one of many possible print emulations. The settings must match, or the printer must be set to "Auto" to self determine which emulation to use.
        2) The print emulation data in the header of the print job is corrupt, so the printer cannot determine what language to use. This can be caused by a bad cable, a corrupt print driver, or possibly having multiple versions of the same print driver loaded on the same server.
        3) The hardest one to narrow down is when the data coming to the printer is not really print data at all. It's some other kind of data being sent to the printers IP address, usually from an automated source.

        Start with checking the print emulations, then stripping the print drivers, and loading the latest versions of the print drivers to the servers. =^..^=
        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

        • Jules Winfield
          Senior Tech

          500+ Posts
          • Jul 2009
          • 823

          #5
          Re: KM2550 continuous printing

          I have experiences similar situations to what blackcat is talking about when a large number of printers are installed on the same server (usually a server that is over utilized to begin with). You can move over the offending printer to a different server (or workstation) as a test to see if that is indeed the issue. I had to bring a server, workstation, switch and network cables out to a customer once in order to isolate the printer from their network and prove to them that running all of their printers (50+) from their BDC was a bad idea.
          But I'm trying, Ringo. I'm trying real hard... to be the Shepherd.

          Comment

          Working...