Re: gEDA-user: pcb prevents overlapping vias

2010-10-16 Thread Ineiev
Hi, kai-martin knaak wrote: When creating a multiple purpose HF connector footprint pcb refused to place vias close to each other. The trigger for refusal seems to be overlapping annulus. Reported three years ago: http://sourceforge.net/tracker/?func=detail&aid=1687692&group_id=73743&atid=5388

Re: gEDA-user: help with gwave svn-REV2444

2010-10-16 Thread Dan White
On Fri, Aug 13, 2010 at 12:14 PM, Stefan Salewski wrote: > On Fri, 2010-08-13 at 12:19 +0100, sibu xolo wrote: >> I have been trying to compile the program gwave (from svn ) > > gwave is one of the most demanding tools of geda suite, for building > from sources. In my opinion, if your goal is to c

Re: gEDA-user: pcb prevents overlapping vias

2010-10-16 Thread Mark Rages
On Sat, Oct 16, 2010 at 5:59 PM, kai-martin knaak wrote: > Moin. > > When creating a multiple purpose HF connector footprint pcb refused > to place vias close to each other. The trigger for refusal seems > to be overlapping annulus. However, I see no strong hardware reason > to second guess me whe

Re: gEDA-user: pcb-20100929 released

2010-10-16 Thread Stefan Salewski
On Wed, 2010-09-29 at 22:58 -0400, DJ Delorie wrote: > It's in the usual place :-) > Fine work, many bugs from 2009 snapshot seems to be removed. While preparing the gentoo ebuild there is still one strange thing: When I test the toporouter I get files like surface0.gts surface1.gts surface2.gt

gEDA-user: pcb prevents overlapping vias

2010-10-16 Thread kai-martin knaak
Moin. When creating a multiple purpose HF connector footprint pcb refused to place vias close to each other. The trigger for refusal seems to be overlapping annulus. However, I see no strong hardware reason to second guess me where I want to put a via. As long as the holes themselves don't overlap

Re: gEDA-user: Unresolved rat lines, zero-ohm resistor, wire bridge

2010-10-16 Thread kai-martin knaak
Jan Martinek wrote: > 4) Use #1 but do some manual post-processing. >disadvantage: At any change in the schematics the manual work >must be done again. You don't need to restart routing all over if the changes in the schematic are only gradual. In fact, I never do. With my hand routed l

Re: gEDA-user: Unresolved rat lines, zero-ohm resistor, wire bridge

2010-10-16 Thread Andrew Poelstra
On Sat, Oct 16, 2010 at 01:49:57PM -0400, Rick Collins wrote: > No, I am not suggesting #2. You don't want to reroute the design > after you add the jumpers. Once you have a routed design, add the > jumper pads to the layout so that wires can be added to the bottom > of the board to complete the

Re: gEDA-user: Unresolved rat lines, zero-ohm resistor, wire bridge

2010-10-16 Thread Rick Collins
No, I am not suggesting #2. You don't want to reroute the design after you add the jumpers. Once you have a routed design, add the jumper pads to the layout so that wires can be added to the bottom of the board to complete the unrouted connections. Then use back annotation to update the sche

Re: gEDA-user: Unresolved rat lines, zero-ohm resistor, wire bridge

2010-10-16 Thread Jan Martinek
Hi, no, it really does not work. I think you are suggesting #2. The autorouter is unpredictable. If I change anything in the schematics, the autorouter comes with different design, often worse than before with more unresolved rat lines. Adding a jumper in schematics does not result into reduc

Re: gEDA-user: Unresolved rat lines, zero-ohm resistor, wire bridge

2010-10-16 Thread Rick Collins
I'm not sure I understand the problem with #1. Can't you take the mostly routed design and back annotate the jumpers so that they are parts in the original schematic? Then you get what you are looking for in #3 which you think is the best approach. Rick At 12:17 PM 10/16/2010, you wrote: H

gEDA-user: Unresolved rat lines, zero-ohm resistor, wire bridge

2010-10-16 Thread Jan Martinek
Hello, I am trying to design a single-sided board with SMD components only (no drilling). The toporouter (which is absolutely awesome, btw.) routes almost all rat lines with only several left unresolved. But, what now? I can do several things: 1) Make the PCB and connect suitable places with

Re: gEDA-user: pcb: Some code-cleanup-patches

2010-10-16 Thread Felix Ruoff
Am 10.10.2010 10:03, schrieb Felix Ruoff: Am 10.10.2010 02:55, schrieb Peter Clifton: On Sat, 2010-10-09 at 23:29 +0200, Felix Ruoff wrote: (...) The first one (0002...) removes some unused functions from the gtk-gui-code. How is removing APIs required by the HID interface and replacing th