Printing problems on e-Studio 3511

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

    #1

    Printing problems on e-Studio 3511

    Hi,

    We've got two problems printing to our Toshiba e-Studio 3511. As far as I know, these problems only happen when printing to the machine, not when copying or scanning. We've had two techs come look at the machine but both have poked around and, because the problems are intermittent, they haven't been able to reproduce them at that particular time and have declared the machine fine. I was hoping that maybe some of you might have come across something similar before or may have an idea of what might be wrong.

    1) Sometimes, prints come out split with half the page being offset from the other. I've attached a scan of this problem as it's hard to describe in words. If you look at the attachment, the left side of the page is fine, but the right side of the page has one of the colours offset from everything else. This was from a five duplexed page job. The other pages (including the other side of this page) was fine. The problem is intermittent (maybe happening 5-10% of the time) and reprinting the page is usually the workaround.
    (It's not a great workaround because it means you can't trust the integrity of the print job and you always have to check that nothing needs to be reprinted.)

    2) Sometimes a print out only comes out with part of the job on it and a following page is printed with the text:
    ERROR: rangecheck
    OFFENDING COMMAND: image

    OPERAND STACK:
    --nostringval--
    --nostringval--


    We've been told it might be driver issues, but we've tried both the 1.70 and 1.16.12.0i1 drivers as downloaded from this page:
    copiers.toshiba.com


    Can anyone please help?


    Thanks,

    Shawn
    Attached Files
  • Mr Spock
    Vulcan Inventor of Death

    1,000+ Posts
    • Aug 2006
    • 2064

    #2
    check the transfer drive belts (it is a royal pain to change) the originals were prone to breakage. The new ones feel more like plastic then rubber. Also check the transfer belt registration sensors. What it appears like is a misregistration of color. As to the second issue I would try updating the firmware and reloading the driver. If the above checks are ok then I would look at memory, nvram or logic pwb.
    And Star Trek was just a tv show...yeah right!

    Comment

    • kjc

      #3
      Driver

      How have you updated the drivers?
      We have had simular messeges when drivers are overwritten we found using a driver delete utillity and a fresh install helps.
      BEWARE ON A SERVER, A DRIVER DELETE UTILLITY USUALLY REQUIRES A REBOOT,

      Keith

      Comment

      • foo

        #4
        Thanks Spock, I'll look into the things you mentioned. Isn't it odd for a misregistration to only affect part of the page?

        Keith, when we tried different drivers, we uninstalled the first set via the Add/Remove Programs window and then installed the new one. The first problem I listed occured before any driver update but I'm not sure about the second.

        Comment

        • xcopytech
          Service Manager

          1,000+ Posts
          • Aug 2006
          • 1794

          #5
          3511

          HI,

          Check firmware version and upload newest firmware.

          Also check have you use PCL or PS printer driver.

          It is look like file broke during ripping in controller.

          BR

          Comment

          • ToshiBoy

            #6
            Check the firmware and make sure it is up to the latest version (easiest way is to go into lists and print out a function list. in the upper right hand corner is the firmware version). Here in Oz we're up to v4006, but I don't know what the latest is in other parts of the world.

            Having said that, I have had two machines do similar things. In both cases it had to do with memory. First thing you could try is to reseat the memory chips, and if not, replace them. I guess it could have to do with with the HDD, too, but they tend to error before they play up like this.

            I think you would find that this problem happens on copying as well, in particular with large documents going through the ADF.

            Comment

            Working...