Xerox Versant 180 error 42-384

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • azehnali
    Senior Tech

    500+ Posts
    • Nov 2009
    • 679

    Xerox Versant 180 error 42-384

    anyone know of a solution for error 42-384
    after start up the error comes up
    IBT belt rotates for a few seconds and then error
  • xcopytech
    Service Manager

    1,000+ Posts
    • Aug 2006
    • 1747

    #2
    Re: Xerox Versant 180 error 42-384

    Have you check ibt drive encoder

    Comment

    • azehnali
      Senior Tech

      500+ Posts
      • Nov 2009
      • 679

      #3
      Re: Xerox Versant 180 error 42-384

      it seams to turn fine

      Comment

      • xcopytech
        Service Manager

        1,000+ Posts
        • Aug 2006
        • 1747

        #4
        Re: Xerox Versant 180 error 42-384

        Clean encoder first

        Comment

        • azehnali
          Senior Tech

          500+ Posts
          • Nov 2009
          • 679

          #5
          Re: Xerox Versant 180 error 42-384

          will do but its super clean and machine only has 80,000 impressions

          Comment

          • jhalfhide
            Trusted Tech

            250+ Posts
            • Apr 2015
            • 450

            #6
            Re: Xerox Versant 180 error 42-384

            Machines built after June 7th 2018, don't have an encoder. It's all in the NVMs. Have you done an NVM initialisation?

            Comment

            • azehnali
              Senior Tech

              500+ Posts
              • Nov 2009
              • 679

              #7
              Re: Xerox Versant 180 error 42-384

              really dont want to do an nvm initialize because I have upgraded the software and the nvms associated with the upgrade a while back related to the BTR

              Comment

              • azehnali
                Senior Tech

                500+ Posts
                • Nov 2009
                • 679

                #8
                Re: Xerox Versant 180 error 42-384

                last set of nvm was the issue
                thanks J

                Comment

                Working...