On Wed, 2009-11-25 at 17:37 -0500, DJ Delorie wrote:
You know what would be cool? Being able to drag and drop symbols from
gschem into pcb, and have it load the right footprint.
That isn't actually that crazy..
Somewhat impractical due to rubber-banding within gschem, but if a
modifier key
On Wed, 2009-11-25 at 21:56 +, Kai-Martin Knaak wrote:
On Wed, 25 Nov 2009 18:02:23 +, Peter Clifton wrote:
done.
I should have been clear.. don't speak to me.. speak to the GTK
developers ;)
_I_ should have been clear: I did speak to the developers via a comment
to the
Hi
I am using PCB to make footprints and I'm having a problem with PCB
not saving the silkscreen along with the pins. Here is my proceedure
for making the footprints.
1. Draw the silkscreen and pins (drawn with vias in the component layer)
2. Select all objects
3. Copy selection to buffer
4.
On Sun, 22 Nov 2009 18:24:18 -0500, Stuart Brorson wrote:
2. Use as a language one can use to automate various actions in gschem.
This is probably closer to the way Eagle users think about scripting
Eagle.
IMO, Scheme is an excellent language for use 1. Other languages aren't
really
On Wed, 25 Nov 2009 17:39:12 -0500, Dan McMahill wrote:
the code is there today, right now,
Now you are talking!
that lets you launch pcb from a
running instance of gschem and when you select a component in gschem,
then pcb will automatically select it.
Arrgh! I am missing this cross
On Thu, 2009-11-26 at 16:04 -0800, Anthony Shanks wrote:
Hi
I am using PCB to make footprints and I'm having a problem with PCB
not saving the silkscreen along with the pins. Here is my proceedure
for making the footprints.
1. Draw the silkscreen and pins (drawn with vias in the component
On Wed, 25 Nov 2009 16:47:57 -0500, DJ Delorie wrote:
It takes layer GROUP numbers, or layer NAMES. Layer groups are numbered
starting at zero, just for inconsistency.
Lets see:
Layer definition of my current project is:
Groups(1,2,3,c:4,5,6,s:7:8)
I assume, the special groups top
On Tue, 24 Nov 2009 13:07:37 +, Peter Clifton wrote:
The issue which is somewhat tricky is how to place the numbers -
assuming they didn't exist in the symbol to start with. We'd have to get
our auto-placement heuristics out,
I, for one, wouldn't care. Autoplacement has caused me a bit of
On Thu, 26 Nov 2009 16:04:35 -0800, Anthony Shanks wrote:
1. Draw the silkscreen and pins (drawn with vias in the component layer)
2. Select all objects
3. Copy selection to buffer
4. Convert buffer to element
5. Save buffer elements to file
Thats ok.
(I do all my footprints that way)
On Sun, 2009-11-22 at 13:29 +1300, Anthony Blake wrote:
Stefan Salewski wrote:
Is option --enable-toporouter-output only for debugging -- needs cairo,
what does it?
Huh? That is only referring to the debugging output.. if that option is
not enabled, the router will still try and exported
If your layer 2 were top, I'd say it was using layer-1 as the number
to use. Which, to me, would be wrong.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Oh crap, thats it, I made the silk with polygons, not lines... whoops...
On Thu, Nov 26, 2009 at 5:13 PM, Kai-Martin Knaak k...@familieknaak.de wrote:
On Thu, 26 Nov 2009 16:04:35 -0800, Anthony Shanks wrote:
1. Draw the silkscreen and pins (drawn with vias in the component layer)
2. Select
Hi Anthony,
Anthony Shanks wrote:
Finally getting the hang of the footprint file format, here is a
footprint of a dsub 15 high density connector (Analog VGA) if anyone
needs it.
More footprints to come.
- annulus = 11.57 mils, is that large enough for hand soldering ?
Yes, plenty. I use 8-10 mils for the annulus, but grow it after the
board's laid out whenever possible, just to make it easier.
- solder mask hole is 65.06 mils, giving a -2.47 mils overlap with
- the pad.
I set my mask
Sorry about the weird numbers but yes everything is in mm, the diagram
I had used mm as the units so I have to draw everything using mm.
I didn't consider fab requirements, hand soldering requirements, or
pin numbering since just was just my first pass at me learning the
tool. I'll be re-editing
On 11/27/09, Stefan Salewski m...@ssalewski.de wrote:
OK, --enable-toporouter-output is for debugging.
But for PCB20091103 I do see no difference if built with
--enable-toporouter-output or --disable-toporouter-output.
The last time I tried it, the toporouter action resulted in some PNG
16 matches
Mail list logo
