Is there a way to set the minimum distance that the autorouter leaves between tracks and pins? I've
looked in the manual, tried setting DRC Minimum copper spacing, tried enabling
Settings-Enforce DRC clearances but the autorouter still runs tracks closer to pins
than I would like. Any
Hi Kai-Martin,
Could you please test this patch and see if it does what you had in
mind?
Thanks,
Peter
--
Peter Brett pe...@peter-b.co.uk
Remote Sensing Research Group
Surrey Space Centre
From 69c00410599bbd1580e2c353553c4d63a99f0f3d Mon Sep 17 00:00:00 2001
From:
On Tue, 2011-01-04 at 16:22 -0800, Matthew Wilkins wrote:
[snip]
I have added a combo box to
the name column, so you you can choose attribute names there from the same
list
as in the Add Attribute portion of the dialog.
[snip]
While I was at it, I added a help button to the dialog,
Hi,
-Original Message-
From: geda-user-boun...@moria.seul.org
[mailto:geda-user-boun...@moria.seul.org] On Behalf Of Mark Rages
Sent: Wednesday, January 05, 2011 5:03 AM
To: gEDA user mailing list
Subject: Re: gEDA-user: Wiki cleanup?
On Tue, Jan 4, 2011 at 8:06 PM, DJ Delorie
Matthew Wilkins wrote:
Hm, Peter C is right that this complicates things a lot.
Well, you asked for potential use cases. Not all conceivable uses
may warrant the effort to code. In addition, there may be better
ways to achieve the same goal. Symbols in gschem are a bit overloaded.
The data
Den 2011-01-04 21:47:59 skrev Stefan Salewski m...@ssalewski.de:
On Tue, 2011-01-04 at 21:14 +0100, Johnny Rosenberg wrote:
comment=Use 74_pwr.sym for supply
I wrote it some months ago...
A single 74_pwr.sym can not work for 14 and 16 pin parts, so I really
recommend to do not use a
Johnny Rosenberg wrote:
Maybe this is in the wiki somewhere and I just missed it, but
what are the possible text strings for pintype?
http://geda.seul.org/wiki/geda:master_attributes_list?s[]=pintype#pintype
So far I've seen in, out, oc, pas. Are there more? Do the gEDA
software use them
Peter TB Brett wrote:
Could you please test this patch and see if it does what you had in
mind?
Surprise: Layer 3 was already defined as outline layer defined in
gaf-head. With your patch I got two such layers ;-)
While at it, I note, that the first two layers are still component
and
Matthew Wilkins matthew_m_wilk...@yahoo.ca writes:
There _is_ a meaning to the order if a netlister expects only one
attribute, but the symbol has several of the same name. In that case,
the netlister could find either the first attribute of that name or
the last, depending on how the
On Wed, 2011-01-05 at 14:32 +0100, Johnny Rosenberg wrote:
A single 74_pwr.sym can not work for 14 and 16 pin parts, so I really
recommend to do not use a 74_pwr.sym at all, but one for 14, and one for
16 pins devices. I think I called my one at gedasymbols
74xx-14N-Pwr-1.sym.
But the
On Jan 5, 2011, at 8:49 AM, Stephan Boettcher wrote:
Matthew Wilkins matthew_m_wilk...@yahoo.ca writes:
There _is_ a meaning to the order if a netlister expects only one
attribute, but the symbol has several of the same name. In that case,
the netlister could find either the first
Bert Timmerman wrote:
http://www.xs4all.nl/~ljh4timm/gaf/dox.html
IMHO, this resource should be linked to in a prominent way on gpleda.
Currently, there is just a link hidden in the section Doxygen Comments
and Styles of the devel-tips
Hi,
-Original Message-
From: geda-user-boun...@moria.seul.org
[mailto:geda-user-boun...@moria.seul.org] On Behalf Of Stefan Salewski
Sent: Wednesday, January 05, 2011 5:23 PM
To: gEDA user mailing list
Subject: Re: gEDA-user: Symbol question - suggestions?
On Wed, 2011-01-05 at
Hi Kai-Martin ,
-Original Message-
From: geda-user-boun...@moria.seul.org
[mailto:geda-user-boun...@moria.seul.org] On Behalf Of
Kai-Martin Knaak
Sent: Wednesday, January 05, 2011 5:30 PM
To: geda-u...@seul.org
Subject: Re: gEDA-user: Wiki cleanup?
Bert Timmerman wrote:
Peter TB Brett wrote:
Well, no, because you will now get a BIG FAT WARNING every time you run
gnetlist.
You mean, I will receive this big fat warning for every symbol I attach
more than one comment to?
---)kaimartin(---
--
Kai-Martin Knaak tel:
On Wednesday 05 January 2011 16:32:48 Kai-Martin Knaak wrote:
Peter TB Brett wrote:
Well, no, because you will now get a BIG FAT WARNING every time you run
gnetlist.
You mean, I will receive this big fat warning for every symbol I attach
more than one comment to?
Why not try it and find
On Monday 03 January 2011, Dan White wrote:
The Analog Rails tweaks to gnucap make parallel simulations
with hspice feasible from a common *.sch set. Their repo is
at
http://redmine.gnucapplus.org/
I could use some help with gnucap development.
I have asked Analog Rails to officially
I'd prefer a spice-prototype attribute, which would allow us to avoid many of
the difficulties without a confusing proliferation of attributes. For the
symbol nmos-3.sym, a suitable prototype might be:
M? #D #G #S #S $model-name L= W= AS= AD= PS= PD= M=
Yes, if we're willing to reinvent
John Doty j...@noqsi.com writes:
I'd prefer a spice-prototype attribute, which would allow us to avoid many of
the difficulties without a confusing proliferation of attributes. For the
symbol nmos-3.sym, a suitable prototype might be:
M? #D #G #S #S $model-name L= W= AS= AD= PS= PD= M=
Den 2011-01-05 16:17:57 skrev Karl Hammar k...@aspodata.se:
Johnny Rosenberg:
Maybe this is in the wiki somewhere and I just missed it, but what are
the
possible text strings for pintype?
Since it is just a text field there is no limitation for what you
could type in there.
So far I've
Den 2011-01-05 17:22:39 skrev Stefan Salewski m...@ssalewski.de:
On Wed, 2011-01-05 at 14:32 +0100, Johnny Rosenberg wrote:
A single 74_pwr.sym can not work for 14 and 16 pin parts, so I really
recommend to do not use a 74_pwr.sym at all, but one for 14, and one
for
16 pins devices. I
On Jan 5, 2011, at 10:07 AM, Johnny Rosenberg wrote:
So the bottom line is that I should keep to those above and don't make my own…
Only if drc2 (which is a severely troubled tool) rule your flow. If your flow
needs something different, and you're willing to do the scripting to make a
On Jan 5, 2011, at 9:56 AM, Stephan Boettcher wrote:
John Doty j...@noqsi.com writes:
I'd prefer a spice-prototype attribute, which would allow us to avoid many
of the difficulties without a confusing proliferation of attributes. For the
symbol nmos-3.sym, a suitable prototype might be:
On Jan 5, 2011, at 10:56 AM, Stephan Boettcher wrote:
John Doty j...@noqsi.com writes:
On Jan 5, 2011, at 9:56 AM, Stephan Boettcher wrote:
Is this too verbose?
M? #{pinlabel=D} #{pinlabel=G} #{pinlabel=S} #{pinlabel=S} ${model-name}
L={length} W={width} AS= AD= PS= PD= M=
Yes,
On Wednesday 05 January 2011 17:49:50 John Doty wrote:
WARNING: Trying to rename something twice:
X2/GND and X2/GND
are both a src and dest name
This warning is okay if you have multiple levels of hierarchy!
I've never known this warning to actually indicate a problem with a design.
I'm creating a footprint according to the datasheet, and it has 3
different prohibited areas on the footprint. I'm not sure of the exact
meaning of these areas. Can someone explain?
1) Prohibited Area
2) Pattern Prohibition Area
2) Solder Prohibition Area
On Jan 5, 2011, at 11:15 AM, Peter TB Brett wrote:
On Wednesday 05 January 2011 17:49:50 John Doty wrote:
WARNING: Trying to rename something twice:
X2/GND and X2/GND
are both a src and dest name
This warning is okay if you have multiple levels of hierarchy!
I've never known this
On Wednesday 05 January 2011 18:38:04 John Doty wrote:
They're not especially bad. In that project make clean; make generates
2074 lines of chatter, only about 1/3 of them from gschem and gnetlist.
The worst offender is pdflatex.
You can see how a warning could easily be lost.
That
On Jan 5, 2011, at 11:49 AM, Peter TB Brett wrote:
On Wednesday 05 January 2011 18:38:04 John Doty wrote:
They're not especially bad. In that project make clean; make generates
2074 lines of chatter, only about 1/3 of them from gschem and gnetlist.
The worst offender is pdflatex.
You
On Wed, 5 Jan 2011 10:00:24 -0800
Colin D Bennett co...@gibibit.com wrote:
[...]
Actually, I am impressed with the flexibility of your footgen.py
script. It looks like you've created many different types of
footprints using it.
I think we miss-understood each other. Or let me say I
DJ Delorie d...@delorie.com writes:
I had that problem with silk. I've not seen it for pads.
Fixed in git head, not including any subtleties with elements with pads
on both sides. I did the obvious thing for those, anyone who *has* one
of those (edge connectors?) can complain if it doesn't do
And that is the way forward for the problematic overloading we have
right now, e.g., the pinseq attribute:
The spice netlist shall learn to use a (spice-)port-order
attribute, or however that shall be named, and fall back to pinseq,
with an obsolescence warning.
The operation is select. PCB doens't know *why* you're selecting,
it's just selecting everything in a region. If you select the *element*
should it select the *whole* element, or just part of the element?
___
geda-user mailing list
On Wednesday 05 January 2011 19:04:37 John Doty wrote:
On Jan 5, 2011, at 11:49 AM, Peter TB Brett wrote:
On Wednesday 05 January 2011 18:38:04 John Doty wrote:
They're not especially bad. In that project make clean; make generates
2074 lines of chatter, only about 1/3 of them from gschem
On Wed, Jan 05, 2011 at 11:05:06PM +0100, Stephan Boettcher wrote:
DJ Delorie d...@delorie.com writes:
If an element is on the front side, but has pads on both sides, and the
back side is hidden, when you select the element, should the hidden pads
be selected too?
No. Not for
I didn't change the de-selection logic; invisible stuff is still
de-selected when you're selecting a new region.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
DJ Delorie d...@delorie.com writes:
The operation is select. PCB doens't know *why* you're selecting,
it's just selecting everything in a region. If you select the *element*
should it select the *whole* element, or just part of the element?
It is possible to make parts of an element
Bert Timmerman wrote:
Would it be possible to
provide the pages on gpleda.org itself?
That can be done, it's just a couple of MB to upload.
Question to the maintainers of gpleda.org(*):
Would it be possible to give upload permissions to Bert?
---)kaimartin(---
(*) Anyone else beyond Ales?
Hi Kai-Martin, maintainers and all,
-Original Message-
From: geda-user-boun...@moria.seul.org
[mailto:geda-user-boun...@moria.seul.org] On Behalf Of
Kai-Martin Knaak
Sent: Thursday, January 06, 2011 12:25 AM
To: geda-u...@seul.org
Subject: Re: gEDA-user: Wiki cleanup?
Bert
On Jan 5, 2011, at 3:19 PM, Peter TB Brett wrote:
On Wednesday 05 January 2011 19:04:37 John Doty wrote:
On Jan 5, 2011, at 11:49 AM, Peter TB Brett wrote:
On Wednesday 05 January 2011 18:38:04 John Doty wrote:
They're not especially bad. In that project make clean; make generates
2074
Bert Timmerman wrote:
I will see if I can create a wiki like format and paste that into the
doxygen output as to mimick the current style of the webpages on
gpleda.org.
Hmm, I think, the current style of the web pages are less than
optimum. Dokuwiki can definitely look and feel better. The
Frank wrote:
I'm creating a footprint according to the datasheet, and it has 3
different prohibited areas on the footprint. I'm not sure of the
exact meaning of these areas. Can someone explain?
Can you give a link to the data sheet?
---)kaimartin(---
--
Kai-Martin Knaak
Email:
On Jan 5, 2011, at 5:51 PM, Kai-Martin Knaak wrote:
Frank wrote:
I'm creating a footprint according to the datasheet, and it has 3
different prohibited areas on the footprint. I'm not sure of the
exact meaning of these areas. Can someone explain?
Can you give a link to the data sheet?
On Thu, 06 Jan 2011 01:51:27 +0100
Kai-Martin Knaak k...@lilalaser.de wrote:
Frank wrote:
I'm creating a footprint according to the datasheet, and it has 3
different prohibited areas on the footprint. I'm not sure of the
exact meaning of these areas. Can someone explain?
Generally this
44 matches
Mail list logo
