Markus,
I will add the patch and give it a try.
How and when do your latest gcode patches get merged into the main branch?
Thanks,
Dave
On 11/29/2010 09:25 AM, Markus Hitter wrote:
Am 16.11.2010 um 22:51 schrieb d...@umich.edu:
However, the gcode export always crashes if I try to define
Am 16.11.2010 um 22:51 schrieb d...@umich.edu:
However, the gcode export always crashes if I try to define the
outline with a rectangle.
It crashed also when the outline layer contains only a single
vertical or horizontal line. Fixed in a new patchset:
Markus,
The outline layer is working fine now, when I draw a rectangle with
lines - even a sloppy rectangle where the lines have kinks, or an
unclosed rectangle. The exporter adds the tool offset as well. Very
nice! However, the gcode export always crashes if I try to define the
outline with
Am 15.11.2010 um 06:55 schrieb d...@umich.edu:
I tried to draw an outline in an 'outline' layer and 'pcb' just
turned the trace lines into an isolation routing outline.
Ouch. This shouldn't happen. Did you apply all 24 patches? If yes,
could you send me (not to the list) the .pcb file
Markus Hitter m...@jump-ing.de writes:
Exactly. A rectangle, or any number of lines drawing another
area. Milled is always a rectangle, though.
Hmm, why? The outline layer is especially useful for boards that are
not rectangular shaped.
--
Stephan
Am 15.11.2010 um 18:06 schrieb Stephan Boettcher:
Markus Hitter m...@jump-ing.de writes:
Exactly. A rectangle, or any number of lines drawing another
area. Milled is always a rectangle, though.
Hmm, why? The outline layer is especially useful for boards that are
not rectangular shaped.
Markus,
I have figured out how to add your 24 patches with git, I recompiled
'pcb', and I am trying out the new version.
The grouping of the drill operation for different drill sizes is great.
Adding a tool table might be cool. There could be a field in the
Preferences window, where the
Am 13.11.2010 um 11:43 schrieb d...@umich.edu:
I will keep R-ing the F-ing M's to try and figure out what git
am 00xxx.patch means.
It's a command to be typed in the command line. Replace the xxx
with the corresponding name of the actual patch file, of course.
To apply all patches
Am 14.11.2010 um 10:38 schrieb d...@umich.edu:
I have figured out how to add your 24 patches with git, I
recompiled 'pcb', and I am trying out the new version.
That's great. Just a second before I sent further comments :-)
Adding a tool table might be cool.
As far as I understand, this
Markus,
Thanks for the note.
On 11/14/2010 05:55 AM, Markus Hitter wrote:
Am 14.11.2010 um 10:38 schrieb d...@umich.edu:
I have figured out how to add your 24 patches with git, I recompiled
'pcb', and I am trying out the new version.
That's great. Just a second before I sent further
Markus,
I cloned and compiled the latest pcb.git version. The program runs, but
I don't think the latest g-code patches are in there. Could you
elaborate a little more on what I have to do to get the latest g-code
patches in my pcb source file? I will keep R-ing the F-ing M's to try
and
Am 11.11.2010 um 05:11 schrieb d...@umich.edu:
I like that the gound plane outline is machined. The circular pads
could use some more lines to round them out. Have you thought about
programming g-code arcs (G02, G03) for them? HeeksCAD/CNC does this
(see below).
Using G02/G03 isn't
Markus,
Thanks for the reply. I tried the 'gEDA - Inkscape - pstoedit - dxf'
route and was not happy with the round-off errors that Inkscape
introduced into the image.
In 'pcb', I tried a dpi of 2000 in the g-code exporter and the resulting
pcb image is beautiful! FOSS pcb milling has
All this algorithm was done by Alberto Maccioni and some research brought up
the statement, this is the only reliable way for offseting all the traces.
Actually the algorithm is not mine, it comes from potrace, a tracing
program by Peter Selinger (as you can see in the source code copyright
Alberto,
Thanks for the comments.
On 11/11/2010 04:24 PM, Alberto Maccioni wrote:
All this algorithm was done by Alberto Maccioni and some research brought up
the statement, this is the only reliable way for offseting all the traces.
Actually the algorithm is not mine, it comes from potrace,
On Fri, Nov 12, 2010 at 9:31 AM, d...@umich.edu wrote:
I think the 2000 dpi output is great!
You coding wizards can do in a minute what would take me a month, but I
would like to try writing a g-code to dxf conversion program in C. Thanks,
Stephen Ecob for the jump start!
Stephen,
Some
Am 11.11.2010 um 20:28 schrieb d...@umich.edu:
The drill xxx.gcode.drill.cnc file goes through the board drilling
all of the holes without differentiating the different drill sizes
(found in the xxx.fab.gbr file). And, there are no tool change g-
codes for changing between drill sizes.
Markus,
That is good news.
Could someone tell be how to add these files to the current pcb-20100929
source download and recompile? Otherwise, I will have to wait on the
next source snapshot, which is fine. I would love to see the latest
patches, though.
I do not know how your '0023-board
At 05:31 PM 11/11/2010, you wrote:
Alberto,
Thanks for the comments.
On 11/11/2010 04:24 PM, Alberto Maccioni wrote:
With a dxf file, in a CAM program, you can program your fine line
cutting with a tiny v bit, then program apocket operation with a
larger bit to remove the remaining copper.
At 2000 dpi the curved traces look great on EMC2/Axis!
On 11/10/2010 11:11 PM, d...@umich.edu wrote:
The g-code exporter looks great! Right now I am looking at EMC2 simulate
the milling of a pcb design!!
I like that the gound plane outline is machined. The circular pads could
use some more
20 matches
Mail list logo
