1 Reply Latest reply on Feb 4, 2016 7:41 AM by chuckt

    How do I prevent components from being unrouted in Pads Layout during library update

    larry.gronmeyer

      Hi,

       

      This may be an easy question, but it is causing us fits.  We are using DxDesigner VX.1 and Pads Layout VX.1.

       

      Scenario:

      We recently had a board almost completely finished and ready for a final review.  As librarian, I modified the silkscreen on an IC so that the Pin1 marker was a label and not a graphic (so we can move it in the layout).  When my board designer did a forward annotation to update the library, the IC was ripped up along with all the routed tracks and was left with a rat's nest.

       

      Why?  Nothing changed in the part that would require a reroute.  We've tried gluing the part and protecting all routes.  Neither works.  There has got to be a way to do this without losing a day's work everytime.

       

      BTW, we are new to PADS.

       

      Thanks,

       

      LarryG

        • 1. Re: How do I prevent components from being unrouted in Pads Layout during library update
          chuckt

          Using the forward annotate ECO process to update parts can cause this kind of disconnect, though if only the silkscreen was changed I don't see why you would get a rip up.

           

          If you were say... changing from a bunch of 0805 components to 0402s you would get rats where the traces ended on the 0805s and went to the 0402s.

           

          If you make the change manually, in the ECO tool bar by using the "Change Component" tool (check "Update from Library"), PADS will just stretch the traces to the 0402s without leaving any rats behind.

           

          If your board designer can make the change manually first, then do the annotation to verify everything else is in sync, I don't think you will see any rip ups.

           

          c