Part Design: Multiple Chassis Grounds

On 30/10/16 01:33, Richard Hornbaker wrote:

While designing a part recently (a MicroUSB jack, FWIW), I ended up with 6 pads for the chassis ground (4 PTH and 2 SMT pads).

 

Connecting them all to the same signal in the device definition isn't a problem - that's done.  But how do I get Eagle to realize only one needs to be routed (i.e., the pads are already connected to each other within the part)?

 

Right now, Eagle presents 6 airwires - which is fine if the other 5 would clear once the first one gets routed.  I'm hoping not to define just one pad as the routing point, because that'll vary by application (and I'd like them all connected to a plane if it's there).  I suppose I could present 6 swappable chassis pins in the schematic instead of 1.

 

Is there a cleaner solution?

 

Yes, as of V7.something - earlier versions don't have it, but the

current version allows you to specify in the library whether a group of

common pins are to be connected as any or all. Unfortunately the machine

I'm at has only V5.12 so I can't easily look up the details.

On 30/10/16 01:33, Richard Hornbaker wrote:

While designing a part recently (a MicroUSB jack, FWIW), I ended up with 6 pads for the chassis ground (4 PTH and 2 SMT pads).

 

Connecting them all to the same signal in the device definition isn't a problem - that's done.  But how do I get Eagle to realize only one needs to be routed (i.e., the pads are already connected to each other within the part)?

 

Right now, Eagle presents 6 airwires - which is fine if the other 5 would clear once the first one gets routed.  I'm hoping not to define just one pad as the routing point, because that'll vary by application (and I'd like them all connected to a plane if it's there).  I suppose I could present 6 swappable chassis pins in the schematic instead of 1.

 

Is there a cleaner solution?

 

Yes, as of V7.something - earlier versions don't have it, but the

current version allows you to specify in the library whether a group of

common pins are to be connected as any or all. Unfortunately the machine

I'm at has only V5.12 so I can't easily look up the details.

Rob Pearce wrote:

On 30/10/16 01:33, Richard Hornbaker wrote:

While designing a part recently (a MicroUSB jack, FWIW), I ended up with 6 pads for the chassis ground (4 PTH and 2 SMT pads).

 

Connecting them all to the same signal in the device definition isn't a problem - that's done.  But how do I get Eagle to realize only one needs to be routed (i.e., the pads are already connected to each other within the part)?

 

Right now, Eagle presents 6 airwires - which is fine if the other 5 would clear once the first one gets routed.  I'm hoping not to define just one pad as the routing point, because that'll vary by application (and I'd like them all connected to a plane if it's there).  I suppose I could present 6 swappable chassis pins in the schematic instead of 1.

 

Is there a cleaner solution?

 

Yes, as of V7.something - earlier versions don't have it, but the

current version allows you to specify in the library whether a group of

common pins are to be connected as any or all. Unfortunately the machine

I'm at has only V5.12 so I can't easily look up the details.

that feature is available with 6.x already (what x I'm not sure of)

--

Lorenz

Rob Pearce wrote:

On 30/10/16 01:33, Richard Hornbaker wrote:

While designing a part recently (a MicroUSB jack, FWIW), I ended up with 6 pads for the chassis ground (4 PTH and 2 SMT pads).

 

Connecting them all to the same signal in the device definition isn't a problem - that's done.  But how do I get Eagle to realize only one needs to be routed (i.e., the pads are already connected to each other within the part)?

 

Right now, Eagle presents 6 airwires - which is fine if the other 5 would clear once the first one gets routed.  I'm hoping not to define just one pad as the routing point, because that'll vary by application (and I'd like them all connected to a plane if it's there).  I suppose I could present 6 swappable chassis pins in the schematic instead of 1.

 

Is there a cleaner solution?

 

Yes, as of V7.something - earlier versions don't have it, but the

current version allows you to specify in the library whether a group of

common pins are to be connected as any or all. Unfortunately the machine

I'm at has only V5.12 so I can't easily look up the details.

that feature is available with 6.x already (what x I'm not sure of)

--

Lorenz

On 30.10.2016 02:33, Richard Hornbaker wrote:

While designing a part recently (a MicroUSB jack, FWIW), I ended up with 6 pads for the chassis ground (4 PTH and 2 SMT pads).

 

Connecting them all to the same signal in the device definition isn't a problem - that's done.  But how do I get Eagle to realize only one needs to be routed (i.e., the pads are already connected to each other within the part)?

 

Right now, Eagle presents 6 airwires - which is fine if the other 5 would clear once the first one gets routed.  I'm hoping not to define just one pad as the routing point, because that'll vary by application (and I'd like them all connected to a plane if it's there).  I suppose I could present 6 swappable chassis pins in the schematic instead of 1.

 

Is there a cleaner solution?

 

Thanks,

Richard

In the pin connection list there is a symbol in the normally empty

column between pin and pad. If that symbol shows two pads connected, all

needs to be connected. If you click it, it will change to disconnected

pads, meaning only one will be needed.

On 30.10.2016 02:33, Richard Hornbaker wrote:

While designing a part recently (a MicroUSB jack, FWIW), I ended up with 6 pads for the chassis ground (4 PTH and 2 SMT pads).

 

Connecting them all to the same signal in the device definition isn't a problem - that's done.  But how do I get Eagle to realize only one needs to be routed (i.e., the pads are already connected to each other within the part)?

 

Right now, Eagle presents 6 airwires - which is fine if the other 5 would clear once the first one gets routed.  I'm hoping not to define just one pad as the routing point, because that'll vary by application (and I'd like them all connected to a plane if it's there).  I suppose I could present 6 swappable chassis pins in the schematic instead of 1.

 

Is there a cleaner solution?

 

Thanks,

Richard

In the pin connection list there is a symbol in the normally empty

column between pin and pad. If that symbol shows two pads connected, all

needs to be connected. If you click it, it will change to disconnected

pads, meaning only one will be needed.

Perfect, thanks.

It's very subtle, but works as desired.