trouble with wires in Eagle ?

The Grid settings are wrong. You need to set the grid to the default 50thou Then place the components. Currently the components are off grid and you cannot snap the wire to them. You can salvage what you have by setting the grid to 1 thou.

Cheers

wire to them.

thanks martin i'll give that a try robb

(with

the

Lots of schematic programs can do the near-miss thing, and most can leave dangling wire segments. PADS can do neither. The only type of schematic wire is a connection.

John

This trapped me badly also. Wires are *not* what you think they are. They don't join to pads in Eagle. You need to use "signal", not "wire".

In addition, Eagle will, if you muck up the grid, create minuscule connections when you join a signal to a pad, unless you drop exactly on the centre grid point of the pad. The extra segment runs between where you dropped (on the grid) and the active point on the pad - even though you can't see the extra connection. Then when you drag the component, it'll be those extra signals that get stretched, which is very ugly. They should have been annotated internally as "extra", and the drag should drag the intended signal to the nearest grid point, before creating any necessary extra segments.

Bottom line is that you really should use a grid that will match the exact pad locations of your component footprints. G*d help you if you want to mix metric (say 1mm spacing) with imperial, say 1.27mm. If you want that, you should first redraw the component footprint of whichever chip is the odd one, using the grid you're going to use for the rest of the board... or just make sure that you never need to move it around once it's placed.

Hope this helps!

Clifford Heath.

the

are.

"wire".

yes that was the problem exactly, i suppose i should have read the instructions/manual

i guess i will read manual to find out what a wire is :)

minuscule

exactly

between

pad - even

the

which is

"extra", and

point,

I think have seen that ? little tails of signals

match

you

1.27mm.

footprint of

use for

to move

yes, very helpful. thanks for the help robb

(with

can

type of

thanks John, looks good but do they have an HE suite ? (hobby edition) one that does not involve loans or leans :)

robb

Yup. "Poorly named".

*-*-*-*-*-*-*-not-*-*-*-conductive+Kevin.Bolding+Use-Net-*-*-*+a-cheat+the.command.is.poorly.named+Use.Bus+avoid+zz+*-*-should-have-been-called-Line

No, sorry, I think a package starts at about $5K.

John

Eagle sounds a bit poor, but what can you expect for nothing ?

Most CAD programs will capture the nearest pin to the net if it is within say 100 thou.

No, Eagle is excellent, and will capture to the pin just fine, as long as you don't use the ill-named wire feature, which isn't meant to.

The "capture to the the pin" is done by adding extra segments, which aren't torn out and redone when you move the chip, and that's another weakness. I wouldn't call it a bug, but it's certainly an inconvenience.

Lousy Spammer!

Stay on the grid. I forget the exact units, but Eagle's schematic capture uses something like a 1/1000th mil internal unit. Wires only connect if they exactly touch. It's very hard to do that if you've got any components off a grid. Back when I used Eagle I had figured out some CLI command to rescue off-grid items (once I orphaned the entire power supply of a project by moving it all with the grid disabled before I knew how to recover it).

--
Ben Jackson AD7GD

http://www.ben.com/

Eagle sounds like a real mess.

It's far better developed and supported than your piece of software, Marra.

The claim that you're using ".Net 3.0 windows graphics interface" only applies to your first image ("Click on a button to select a module..."), doesn't it? The actual applications still run in DOS boxes, don't they?

You are completely wrong.

The software is a windows application using .net framework v3.0 and Windows programming foundation.

The software is fully supported by email and phone.

If you find a bug I fix it and send you an update. I cant think of any other company that does this ! And all for less than =A320 !

This software was converted to windows in around 1997 !

Your comments are only 10 years out of date lol

So why don't your screenshots *look* like regular Windows... windows? You have a non-standard menu bar, no scroll bars, no resize "handle" widget in the lower-right corner, etc. I don't know of any other payware schematic capture/PCB layout tool today for Windows that looks that way... perhaps you've come up with what you think is an even better GUI than what Windows provides? (You wouldn't be the first -- back around 1992 or 93 I used EDA software -- ProNet/ProBoard -- on Commodore Amiga computers that completely ignored the standard Amiga windows menus and controls, substituting their own...)

Why don't you place your users manuals on your web site? If your software really is any good, I'm sure it'll increase your sales.

---Joel

That's certanily commendable; companies' responsiveness to fixing bugs certainly varies a lot these days... Eagle seems to be pretty good, as Pulsonix ...mostly... is (and it's written using .Net as well) -- Cadence and Mentor are pretty much the pits, of course.

..skip list of perceived faults, which I won't bother to dispute...

Did you actually look at the website

The download area has a 248-page pdf "manual-eng.pdf" and a 71-page "tutorial-eng.pdf" right there with the software in rpm and tgz formats. There are also German versions. Over in the User Download area, there's a 418-page "eagle416r2_help_en.pdf", besides a number of other freely downloadable documents in various languages.

As it happens, I use and like Eagle. My previous experience has been with pcad, autocad, and a couple of hobbyist-type programs. I like the freeware Eagle best of them all. I hope someday to be able to be able to pay for a pro-level version.

John Perry

On Tue, 23 Oct 2007 18:46:54 -0500 in sci.electronics.cad, Ben Jackson wrote,

Type a command like "move IC1" (or whatever your part name is) then move it with the mouse. When you drop it, it'll be back on the grid.

>