CLX9201 Tint on white

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Allante666
    Junior Member
    • Oct 2024
    • 9

    #1

    CLX9201 Tint on white

    HI, CLX9201 has suddenly started printing a faint cyan background (evenly) on all colour prints and copies where it should be white (doesnt happen if in monotone). Changed Cyan toner cart (which was almost empty despite the machine saying 83% full- suspect may have been swapped prior to me seeing it) but has made no difference. Have run all the auto tone settings etc I can find (normally a canon guy so still finding my way round this one) but the tint still remains. Apparently started quite suddenly. transfer rollers etc all nice and clean as is the machine in general although it only does it in colour so Im ruling those out. Any ideas much appreciated!
  • crm-informatica.it
    Technician
    • Dec 2017
    • 13

    #2
    Originally posted by Allante666
    HI, CLX9201 has suddenly started printing a faint cyan background (evenly) (cut)
    Check the cleaning blade of the belt.

    Comment

    • Allante666
      Junior Member
      • Oct 2024
      • 9

      #3
      Originally posted by crm-informatica.it
      Check the cleaning blade of the belt.
      I havent checked that but if it was the cleaning blade then surely it would do it with all colours not just the cyan?

      Comment

      • crm-informatica.it
        Technician
        • Dec 2017
        • 13

        #4
        Originally posted by Allante666

        I havent checked that but if it was the cleaning blade then surely it would do it with all colours not just the cyan?
        It is not always true.
        The 1.st step is to test the drum simply shifting it with another color. If the color of the background changes, you must replace the cyan drum after the repositioning.
        The 2.nd step is to try to clean the cleaning blade group. You should see a quality improvement immediately after the cleaning. If it is the case you find the solution or one solution.

        Comment

        • Allante666
          Junior Member
          • Oct 2024
          • 9

          #5
          Originally posted by crm-informatica.it

          It is not always true.
          The 1.st step is to test the drum simply shifting it with another color. If the color of the background changes, you must replace the cyan drum after the repositioning.
          The 2.nd step is to try to clean the cleaning blade group. You should see a quality improvement immediately after the cleaning. If it is the case you find the solution or one solution.
          I already tried swapping the drum around but it still stayed the same colour background.
          Also, it doesnt do it when it prints in black/white if that helps?

          I will try cleaning the wiper blade though and see what happens. I seem to think the itb cleaner just slides out on this.

          Comment

          • crm-informatica.it
            Technician
            • Dec 2017
            • 13

            #6
            Originally posted by Allante666

            I already tried swapping the drum around but it still stayed the same colour background.
            ...it is the reason because I suggested you the check the cleaning blade of the belt.
            I did have the same cases but not on this Multifunction: the problem was on the rollers of the developer group.

            Comment

            • Allante666
              Junior Member
              • Oct 2024
              • 9

              #7
              Originally posted by crm-informatica.it
              ...it is the reason because I suggested you the check the cleaning blade of the belt.
              I did have the same cases but not on this Multifunction: the problem was on the rollers of the developer group.
              Cleaned the wiper blade but has made no difference unfortunately, all colour prints still have a light blue caste.

              Comment

              • crm-informatica.it
                Technician
                • Dec 2017
                • 13

                #8
                Originally posted by Allante666

                Cleaned the wiper blade but has made no difference unfortunately, all colour prints still have a light blue caste.
                You have to empy from toner the ITB cleaning blade group, not simply "clean". Can you post a sample?

                Comment

                • Allante666
                  Junior Member
                  • Oct 2024
                  • 9

                  #9
                  Originally posted by crm-informatica.it

                  You have to empy from toner the ITB cleaning blade group, not simply "clean". Can you post a sample?
                  Yes sorry I should have made that clearer, I emptied and cleaned the whole blade assembly, the blade, the hopper, the screw.

                  Comment

                  • Allante666
                    Junior Member
                    • Oct 2024
                    • 9

                    #10
                    Also, is there any way of checking the developer unit? Just spoke to a local tech who says it sounds liek the charge wire/roller. I can get one but dont want ot spend money on it if its not that.

                    Comment

                    • Crowfeather
                      Printer firmware is !&$!

                      100+ Posts
                      • Mar 2021
                      • 130

                      #11
                      I'm not sure if this is solved or not, but what you are describing is a fault produced on the imaging unit.
                      I can see you swapped the drum to check if its the imaging unit itself and issue persisted.
                      But the fact it doesn't happen when doing mono prints, basically confirms that this is the only cause, because the drums are not engaged in mono prints, everything else is.

                      So what you need to do is do a jam test to confirm the state of the imaging unit. Print a colour page with a small coverage and then before the paper reaches the transfer belt, open the side door. This will cause a jam and prevent the printer completing the rest of the printing process. Remove the imaging drum, and you should see a blue image marking out what you were trying to print. If the drum is faulty, you will see that the drum is covered in toner. This is an indicator that it is overcharging.

                      Now as you've already swapped the drum, the only thing left would be to replace the HVPS or if you are using compatible cartridges the toner cartridge.



                      Anything else in the machine is a red herring, because if you had issues at those parts, it would appear on mono prints as well as blank pages if its an issue of residue or the ITB not cleaning for example. The fact it only occurs on 1 colour, and that it doesn't show in mono prints, means its a production issue not a transfer issue.


                      If the magnetic roller on the developer fails you will get a V pattern. You can check the developer by swapping it with another colour as they're interchangeable. But you will need to pump toner through it for it to print the correct colour, as the developer will always have some amount of toner in it.
                      You may be able to tell by physically inspecting the magnetic roller on the developer itself.

                      Comment

                      • Allante666
                        Junior Member
                        • Oct 2024
                        • 9

                        #12
                        Originally posted by Crowfeather
                        I'm not sure if this is solved or not,

                        If the magnetic roller on the developer fails you will get a V pattern. You can check the developer by swapping it with another colour as they're interchangeable. But you will need to pump toner through it for it to print the correct colour, as the developer will always have some amount of toner in it.
                        You may be able to tell by physically inspecting the magnetic roller on the developer itself.
                        Hi. So Im thinking along the same lines. I think, like you, that the fact its fine in mono rules out the actual transfer parts i.e. the ITB and onwards. The drum I have ruled out as swapping it made no difference. I have visually compared the developer roller on the cyan unit to one of the others and it doesnt appear to be any more covered in toner than the other was.

                        I wasnt aware they were interchangeable. When you say pump toner through it to get the correct colour I assume you mean just keep printing colour until it comes right?

                        So Im thinking likely cuprit is something on the HVPS board resulting in a wrong charge voltage to the drum. To this end i have, as we speak, a new (well, new to me) HVPS board on its way so hopefully that will either cure it or at least narrow it down to the developer unit.
                        I have tried to check the wiring and connectors between the HVPS board and the socket where the drum etc plugs in. Its not very accessible but does appear to be all ok.

                        The only other thing is in the service manual, there is a part regarding HV faults that says 'Check if T1–roller spring in ITB is connected correctly.' I cant really work out where they mean regarding that but im guessing anything on the ITB unit is already past the cause of the fault.

                        Just have to see what the new HVPS does.

                        Comment

                        • Allante666
                          Junior Member
                          • Oct 2024
                          • 9

                          #13
                          Well I give up with this! So I put a complete new HVPS board in. Still blue tint on backgrounds. So going by what Crowfeather said, I swapped over the cyan developer unit with the Magenta one. Printed off a load of purge sheets until they both came out the correct colours. Still blue tint!!!

                          Comment

                          Working...