Eagle Software

On 03/13/2014 08:26 PM, Brian Mcclung wrote:

Hi Chuck

 

I'm still having the same problem, but other questions first.

 

How do you change the units.

How do you define the grid in such a way that your measurement steps are

smaller than the area to be measured.

As Doug mentioned, you can use the grid command.  Try "grid mil 5" to

set the snap to every 5 mils, or "grid mil 1" to set it to 1 mil.  You

can go smaller or larger to suit your needs.  You can also append a

second integer to this that affects the display of the grid.  Try "grid

mil 1 5".  This will set your snap to 1 mil, and the grid display to

every 5 snaps (5 mils).  "grid mil 5 5" will set the snap to 5 mils, and

the display to 5 snaps (25 mils).

You can also specify other units, such as mm or in.

Back to my original problem.

 

I checked the parameter I think you specified, and the size is already

set to 10 mils.

Well, that's the source of the DRC problems.  If the pads are on .5mm

spacing, and each pad is .25mm wide, that leaves only .25mm of spacing.

That converts to 9.8 mils.  Try setting the size to 9 mils.

This also means that the wire coming off the pad must be less than 9.8

mils - a 10 mil trace will create a DRC clearance error.

What I want to know is if these errors are caused by a design rule, why

is Eagle not self adjusting to what is a standard part.

That would be making assumptions about the capabilities of the board fab

house, and your design limitations.

Why is Eagle not self adjusting, and is this going to be a persistent

feature when using Eagle.  Is this something that every time I do a

board, I am going to have to go in adjust my design rules?

Basically, yes.  If you are using all PTH components, there's no need

for such tight tolerances.  For SMD designs, obviously the fab

requirements have small tolerances.  I'm sure you can change the default

design rules for new designs, but I don't know where that would be done.

HTH,

    - Chuck

What exactly are you trying to do with the dimensioning tool?  I've never thought of it as anything more than icing on the cake, just a way to put measurements on a page for a human to read...

Here is where I'm having a problem with the design rules.

This particular part that was giving me problems was obsolete 7 years ago.  It has been replaced with the M model, but the spacing is the same.   This particular obsolete part has been around 10 years.

What legitimate board house could not handle that spacing.

So let me retract my question, why are the DRC rules not self adjusting.   I could further debate the point, but I wont.

I never changed the DRC rules.

Now my question is this.

Why would Eagle default to parameters that don't reflect current manufacturing capabilities.

Is that spacing really beyond typical manufacturing capability?

If it isn't, I was caused unnecessary trouble by the parameters it defaulted to.

Thank you for your response.

Maybe to aid placement, a quick check of board or edge-part spacing.

I just don't see how it can be used for a quick a-b measurement.

It seems to pick its own points automatically, or at least one of them.

On 14/03/14 11:23, Brian Mcclung wrote:

Yes Rob, I agree, how stupid of me.

 

Why would I not expect Eagle to impose a limit on me based upon an

action I have never performed: Adjusting the rules you carefully worked

out to suit a component you picked on a whim.

 

Do me a favor!

 

Do yourself a favour and READ THE ADVICE YOU ARE GIVEN.

We are not here to waste our time on your personal whinge-fest. If you

want to know why things are as they are, and somebody answers that

question, rejecting an answer you don't like with sarcasm is incredibly

rude and obnoxious. Please grow up.

Brian Mcclung wrote:

Maybe to aid placement, a quick check of board or edge-part spacing.

 

I just don't see how it can be used for a quick a-b measurement.

When I want to do a quick measurement, I just use the "mark" command.  When you place a mark, you get a display of relative coordinates right next to the cursor location display.  Read: MARK command You can use the "assign" command or the options-assign menu to tie the mark command to a particular key that you like.  For example:

ASSIGN F12 'mark';

If you want, you can even assign a key to stop marking:

ASSIGN F11 'mark;';

(Notice additional semicolon inside quotes.)

It seems to pick its own points automatically, or at least one of them.

If you read the help on dimension DIMENSION command you'll see that if you click on an object, EAGLE will try to guess what to do...

I'm going to make this really simple for you.

The next time anybody refers to anything I'm questioning, wanting to do, or thinking you should be allowed to do as catastrophically stupid, they will get an attitude from me.

You don't have to act like you are the defenders of eagle.

Everything about Eagle is not the greatest.

I may be kind of unique, but I would actually prefer a little less thinking for me.

I want to clarify.

I have been reading the advice given.   I have not rejected anything.   I'm here to learn how to do things.

And I have tried to thank everybody who has helped me.

None of these 4 things requires me to like Eagle.

And I don't have to justify anything I would like to do.

Now that we have that straightened out, if you don't want to help, don't!!!!

Brian Mcclung wrote:

You don't have to act like you are the defenders of eagle.

LOL, but this is the EAGLE forum - we *ARE* the defenders of EAGLE!

 * AnalogNotes dons his EAGLE cape and stands on the roof, hands on hips, gazing into the distance with his hair and cape billowing behind him in the wind while patriotic music plays...

Everything about Eagle is not the greatest.

In some circles, that comment would be worthy of the title "troll"...

Troll (Internet) - Wikipedia, the free encyclopedia

Seriously though, what other EDA products have you used, why are they better than EAGLE, and why aren't you using them?