Yahoo Groups archive

Homebrew PCBs

Index last updated: 2026-04-28 23:05 UTC

Message

Re: DeskPCB question

2002-11-24 by Dave Mucha

I am not sure about the errors, but it may be that you have a tool 
bit size in the program that it too large for the traces.  for 
instance, if your bit size is listed as 0.1", and you have 0.1" 
between chip pads, you cannot cut two lines around a pad and still 
have any pad left.  you certainly cannot put 2 or 3 traces between 
pads either.  if your bit was listed as 0.01", you could easily put a 
trace between pads.

as for lineing up the boards.  make a template, use the board 
mounting holes, drill them exactly to size, put pins in the holes 
that are a tight fit

use or put 4 more holes for verifying. one in each side, near the 
edges, these could be actual thru holes for traces, or just alignment 
holes.  These should be done with the software controlling the 
drill.  Since you know their exact locations, when you flip the 
board, you can posistion the drill over the holes and verify the 
exact alignment.

There may be other ways, but this works for me.

Dave




--- In Homebrew_PCBs@y..., "dougfennell2000" <dfennell@m...> wrote:
> Hi all. I downloaded the deskpcb software and it seems to do a good 
> job. I was wondering if anyone else has given it a spin. If you 
have, 
> here are a few questions that maybe you can help me with. In the 
> create g-code section there are a few parameters that I can't 
figure 
> out: Tool # - what are the definitions of these tools? I'm also 
> getting an error on that says 6 traces could not be routed. Is this 
> because there is something I'm doing wrong with the initial layout, 
> or perhaps my trace size? I'm using a 60deg. bit from think & 
tinker 
> and some 2 sided board I got from them as well. As a final 
question, 
> what is the best way to line up the board after you flip it over to 
> cut the back side?
> 
> Thanx,
> 
> Doug

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.