Migrate from Fiery to Postscript - Color 550

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • XEROX_1111_TEC
    Technician
    • Aug 2019
    • 67

    [Error Code] Migrate from Fiery to Postscript - Color 550

  • xcopytech
    Service Manager

    1,000+ Posts
    • Aug 2006
    • 1728

    #2
    Re: Migrate from Fiery to Postscript - Color 550

    If you removed VSEL pwb from machine then you should replace it with jumper pwb.
    You can not copy or print on c550 without jumper or vsel pwb

    Comment

    • Caffeine
      Trusted Tech

      Site Contributor
      250+ Posts
      • Feb 2008
      • 380

      #3
      Re: Migrate from Fiery to Postscript - Color 550

      Originally posted by XEROX_1111_TEC
      I really need this printer only with postscript
      As xcopytech said, just leave the VSEL pwb in there, assuming you don't have the jumper pwb, which can be hard to get. It can run without a Fiery attached, using Postscript on the built in green controller, even while the VSEL is still installed.

      Comment

      • XEROX_1111_TEC
        Technician
        • Aug 2019
        • 67

        #4
        Re: Migrate from Fiery to Postscript - Color 550

        Originally posted by Caffeine
        As xcopytech said, just leave the VSEL pwb in there, assuming you don't have the jumper pwb, which can be hard to get. It can run without a Fiery attached, using Postscript on the built in green controller, even while the VSEL is still installed.
        Thanks

        I will try that and post what result do I get

        Comment

        • XEROX_1111_TEC
          Technician
          • Aug 2019
          • 67

          #5
          Re: Migrate from Fiery to Postscript - Color 550

          UPDATE

          Your tips were follow and the problem was detected. The postscript pwa contacts were not totally clean so that was generating that error. After cleaning the contacts and reinstalled the the VSEL pwb it worked fine.

          Thanks a lot for your help.

          Keep safe and thanks once more.

          Comment

          Working...