Any way to prevent implicit power connections?

On 05/11/12 06:56, Tilmann Reh wrote:

Asher Hoskins schrieb:

 

>> Is there any way to prevent Eagle making implicit power connections?

However, in this case it's pretty obvious that your library is badly

defined. If that pin is allowed to be left open (or connected

elsewhere), its direction should not be PWR or SUP, but simply PAS.

Then, it also wouldn't connect automatically.

Thank you, that sounds like the thing to fix. I created the library so I

have only myself to blame!

Two thoughts:

1. I suggest to upgrade to the latest V5 version (5.12.0) that is

covered by your current license. Many issues have been fixed.

2. Take the time to have a closer look at V6 before buying the upgrade.

Personally, I didn't get the upgrade - many long standing issues have

not been addressed, most of the new features are of no use for me, many

new bugs and flaws have been introduced... For the time being, I stick

with 5.12.

I've not spent any time playing with Eagle 6 yet. My main reason for

thinking about upgrading is the "design reuse" feature, being able to

design a schematic+board section once and then copy it multiple times

into a design. A lot of the design work I've been doing recently (over

the course of a PhD) has been on multi-channel devices so this feature

appeals to me. I shall have a proper play with Eagle 6 before I decide

to pay for an upgrade.

Asher.

Asher Hoskins schrieb:

Is there any way to prevent Eagle making implicit power connections?

 

I've just been bitten in a design which has both 5V (from a USB

interface module) and 3.3V power levels and didn't notice a connection

made by the autorouter between the main "VCC" net (at 3.3V) and a pin

named "VCC", which should have been left unconnected, on a 5V USB module.

If you want that pin to be connected to any other net, simply draw that

in the schematic. In this case, you'd draw a net stub to that second

"VCC" pin and give it another name. You'll get a DRC warning, which you

can "acknowledge".

The same applies to the different supply nets, in case you use logic

devices at different voltages. INVOKE the power gates and connect them

to the correct supply nets, then acknowledge the DRC complaints.

However, in this case it's pretty obvious that your library is badly

defined. If that pin is allowed to be left open (or connected

elsewhere), its direction should not be PWR or SUP, but simply PAS.

Then, it also wouldn't connect automatically.

I'm using Eagle 5.7.0 (Linux) at the moment but will be upgrading to 6.X

once my current design project's finished.

Two thoughts:

1. I suggest to upgrade to the latest V5 version (5.12.0) that is

covered by your current license. Many issues have been fixed.

2. Take the time to have a closer look at V6 before buying the upgrade.

Personally, I didn't get the upgrade - many long standing issues have

not been addressed, most of the new features are of no use for me, many

new bugs and flaws have been introduced... For the time being, I stick

with 5.12.

Tilmann