Actions
Forum Thread Details
  • Replies 8 replies
  • Subscribers 177 subscribers
  • Views 558 views
  • Users 0 members are here
Related

symbol with multiple package variations

autodeskguest

Is there a way to allow, for instance any logic device that uses a DIL14

package to be able to use a variation on that package that has been created

without having to go through the entire logic family individually with the

variation device table linking the symbol with the package? For instance,

with Protel one can double click the symbol in a schematic and specify the

package that is used.

Thanks in anticipation of a reply.

Don

 

 

 

Parents

  • "Gary Gofstein" <ggofstein@lbl_nospam.gov> wrote in message

    news:g2cc83$us5$1@cheetah.cadsoft.de...

    Not sure I understand your question, Change.Package in v4.16 will let you

    change the package on board with just a click. But only if that package

    has been previously linked to the part in the library. Otherwise, how

    would EAGLE know which pins to connect to which signals in the new

    package?

    Hope this helps...

     

    "Don Owen" <dono2@tpg.com.au> schrieb im Newsbeitrag

    news:g2cmib$omk$1@cheetah.cadsoft.de...

    The symbol connection diagram in a logic family for a 14 pin DIL package

    is already linked for each device in the family, i.e. pin 2 on the symbol

    diagram goes to pin 2 of the package. Now a package variation  which may

    only be a pad dimension change or a drill hole variation means that pin 2

    symbol is still going to go to pin 2 package and the connection diagram

    would remain the same. Unfortunately with Eagle, this new package

    variation has to be linked in the library to every part in a family and

    requires a fair bit of work. This can be made easier by the copy command

    in the library device editing procedure but is still tedious. A generic 14

    pin footprint of the package variation substitution would be in my view, a

    lot easier where as in Protel, the schematic symbol on the users schematic

    diagram is double clicked and the package variation is specified. In that

    way, package variations can be changed on the fly. However, Eagle is great

    s/w and I can live with minor inconveniences such as this.

     

     

    Eagle V3.5 REPLACE did not need a fully specified library device to operate.

    "REPLACE" a SO14 by a TSSOP14? No problem, you picked the target package out

    of a library of your choice and voilà, all done. Guess how often I was on my

    knees to get this one back. V4 / V5 forces you into useless and time wasting

    component library management. That's one of the points where Eagle outsmarts

    the user, as A.Sterian pointed out elsewhere.

     

    T.

     

     

     

Reply

  • "Gary Gofstein" <ggofstein@lbl_nospam.gov> wrote in message

    news:g2cc83$us5$1@cheetah.cadsoft.de...

    Not sure I understand your question, Change.Package in v4.16 will let you

    change the package on board with just a click. But only if that package

    has been previously linked to the part in the library. Otherwise, how

    would EAGLE know which pins to connect to which signals in the new

    package?

    Hope this helps...

     

    "Don Owen" <dono2@tpg.com.au> schrieb im Newsbeitrag

    news:g2cmib$omk$1@cheetah.cadsoft.de...

    The symbol connection diagram in a logic family for a 14 pin DIL package

    is already linked for each device in the family, i.e. pin 2 on the symbol

    diagram goes to pin 2 of the package. Now a package variation  which may

    only be a pad dimension change or a drill hole variation means that pin 2

    symbol is still going to go to pin 2 package and the connection diagram

    would remain the same. Unfortunately with Eagle, this new package

    variation has to be linked in the library to every part in a family and

    requires a fair bit of work. This can be made easier by the copy command

    in the library device editing procedure but is still tedious. A generic 14

    pin footprint of the package variation substitution would be in my view, a

    lot easier where as in Protel, the schematic symbol on the users schematic

    diagram is double clicked and the package variation is specified. In that

    way, package variations can be changed on the fly. However, Eagle is great

    s/w and I can live with minor inconveniences such as this.

     

     

    Eagle V3.5 REPLACE did not need a fully specified library device to operate.

    "REPLACE" a SO14 by a TSSOP14? No problem, you picked the target package out

    of a library of your choice and voilà, all done. Guess how often I was on my

    knees to get this one back. V4 / V5 forces you into useless and time wasting

    component library management. That's one of the points where Eagle outsmarts

    the user, as A.Sterian pointed out elsewhere.

     

    T.

     

     

     

Children
No Data