> -
> /* define how far the cursor could be to activate magnetic */
> #define MAGNETIC_PIN_REACH 50
> #define MAGNETIC_NET_REACH 20
> #define MAGNETIC_BUS_REACH 30
What do the values actually mean? Is it 50 grid units, 50 pixels, 50 what?
I've also experience some frustration with this fe
Hi Kai-Martin,
On Dienstag, 22. September 2009, Kai-Martin Knaak wrote:
> Sometimes, gschem nets shows an annoying tendency to snap to a not so
> near node. Is there a way to tune the distance at which the gschem
> net snaps?
This is a hardcoded feature ;-)
It's not possible to change this with c
There is a new development snapshot available ...
http://gnucap.org/devel/gnucap-2009-09-22.tar.gz
Optional plugin files:
http://gnucap.org/devel/gnucap-2009-09-22-models-bsim.tar.gz
http://gnucap.org/devel/gnucap-2009-09-22-models-
jspice3-2.5.tar.gz
http://gnucap.org/devel/gnucap-2009-09-22-mo
DJ Delorie wrote:
> I talked with Dan about it, we seem to think it's better to not use
> the ground plane for the return signal,
Just for clarity sake, in this particular area there is not ground
plane. Just the ground plane layer. If I had zoomed out, you'd see
lots of copper in other areas.
I talked with Dan about it, we seem to think it's better to not use
the ground plane for the return signal, and route the return the same
way you route the audio. Think of it like a differential pair. That
way, you get current balancing without breaking up your ground plane.
Also, avoiding vias
DJ Delorie wrote:
> You want an audio-frequency microstrip then. Sounds like a Dan
> question, he's probably hit that already.
>
>
> ___
> geda-user mailing list
> geda-user@moria.seul.org
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>
Yep
You want an audio-frequency microstrip then. Sounds like a Dan
question, he's probably hit that already.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>
> Perhaps if you explained *why* you're using a trace that way, we could
> help you figure out how PCB would prefer to handle that situation.
I figured that question was coming next :)
Those particular traces you see are low frequency audio. There's
several channels of it. In order to redu
Right, that's a fundamental difference between a trace and a polygon -
traces always connect two points together, polygons are for area
coverage and need to be more flexible.
Perhaps if you explained *why* you're using a trace that way, we could
help you figure out how PCB would prefer to handle
Maybe you could post a small picture of what's happening to
> help us understand what you're trying to accomplish?
>
Sure.
This picture shows a polygon on the ground layer. The via has a
clearance around it, as expected.
http://www.geocities.com/fazool1_2000/geda/route-with-polygon.png
Here'
> If I route a trace, not polygon, on the ground layer, and it passes
> by a via, the via connects to the trace. I don't want this to
> happen. Anyway to make it so ("make it so, number one")?
I don't understand - that's the whole point of traces and vias - they
connect. Maybe you could post a
If I route a trace, not polygon, on the ground layer, and it passes by a
via, the via connects to the trace. I don't want this to happen.
Anyway to make it so ("make it so, number one")?
___
geda-user mailing list
geda-user@moria.seul.org
http://www.
On Tue, 2009-09-22 at 15:34 +, Kai-Martin Knaak wrote:
>
> This description looks like an instance of the problem I tried to resolve
> in my failed coding effort this summer. With composite components the
> output of gnetlist depends on the order of symbols in the *.sch file. If
> you delet
On Sep 22, 2009, at 11:05 AM, Stefan Salewski wrote:
> On Tue, 2009-09-22 at 15:34 +, Kai-Martin Knaak wrote:
>> On Tue, 22 Sep 2009 16:58:08 +0200, Stefan Salewski wrote:
>>
>>> If I
>>> delete in this schematic the Power symbols 502 and 503 and
>>> replace them
>>> with a copy of 501 and
On Tue, 2009-09-22 at 15:34 +, Kai-Martin Knaak wrote:
> On Tue, 22 Sep 2009 16:58:08 +0200, Stefan Salewski wrote:
>
> > If I
> > delete in this schematic the Power symbols 502 and 503 and replace them
> > with a copy of 501 and renumber manually again to 502 and 503 all works
> > fine
>
> T
Sometimes, gschem nets shows an annoying tendency to snap to a not so
near node. Is there a way to tune the distance at which the gschem net
snaps?
---<(kaimartin)>---
--
Kai-Martin Knaak tel: +49-511-762-2895
Universität Hannover, Inst. für Quantenoptik fa
On Tue, 22 Sep 2009 16:32:02 +0100, andrew whyte wrote:
> This is much better than my current method of copying the dxf to an
> image and tracing it! I'll be sure to use it on the next project.
This flow works for me:
*.dxf
some CAD app --> *.ps
ps2edit --> *.pcb
---<(kaimartin)>---
--
On Tue, 22 Sep 2009 16:58:08 +0200, Stefan Salewski wrote:
> If I
> delete in this schematic the Power symbols 502 and 503 and replace them
> with a copy of 501 and renumber manually again to 502 and 503 all works
> fine
This description looks like an instance of the problem I tried to resolve
i
Great, I have been searching for a way to do this for ages.
This is much better than my current method of copying the dxf to an
image and tracing it! I'll be sure to use it on the next project.
Andrew
On Tue, Sep 22, 2009 at 3:56 PM, Kovacs Levente wrote:
> Hi,
>
>
> I wrote a small program
This is a not too serious, but strange error -- maybe solved in 1.5.x?
I tried to generate a BOM for my DSO board. This has some Dual OpAmps
(slotted) with separate power symbols.
I have reduced the problem to a minimal schematic, called test5.sch. If
I delete in this schematic the Power symbols
Hi,
I wrote a small program that reads *.dxf files, and converts it into a
PCB file.
Before you start throwing tomatoes, please note that this is my first c+
+ program, so be gentle.
It reads a dxf file, and a PCB file. It searches for layers in both
file, and if there is a match, it'll write a
The gschem gui seems to append new items to the bottom of the file. As a
consequence, symbols done with the GUI are a pain to edit in a text
editor. Pins mix with comments and attributes in no particular order. It
would be nice, if the internals were sorted by type, by value, and/or by
position
Another snippet from the device attribute in the master attribute list:
/-
Do not put spaces into the device name;
(...)
Examples: device=7400 device=CONNECTOR 10 device=NPN TRANSISTOR
\-^ ^
Why do the examples contain spaces, when th
Cite from the master attribute list:
/--
device= is the device name of the symbol and is required by gnetlist.
\--
However, I forgot the device attribute in some of my symbols and gnetlist
did not seem to care at all. Netlist generation was just fine. What is
the purpose
24 matches
Mail list logo
