pcb2gcode-devel

[Pcb2gcode-devel] Some minor fixes to pcb2gcode

[Spencer R. <sf...@me...>]

I noticed that when I was generating paths with multiple paths, the
paths on the very outside of the design were getting put right on top of
each other (see attached pic pcb2gcode_orig.png). It looks like the
bounding box being calculated wasn't taking into account the
"extra_passes" parameter.

I made a minor tweak so it looks at the tool from the "front" layer and
the extra_passes parameter and makes sure the bounding box is large
enough to contain the extra passes. See the result in the other attached
pic (openscam_board.png)

I forked the repo and made my changes in my GitHub repo here:
https://github.com/ssfrr/pcb2gcode

Does my approach seem reasonable? Is there a process for getting this
change merged into the main repository?

Thanks,
-s

[Pcb2gcode-devel] Some minor fixes to pcb2gcode

[Nicola C. <ni...@co...>]

Hi
I've merged your repo (https://github.com/ssfrr/pcb2gcode) into the master
Thanks

Nicola Corna

Re: [Pcb2gcode-devel] Some minor fixes to pcb2gcode

[Lionel S. C. <lio...@gm...>]

Dear all

I made some improvements to pcb2gcode, but it is far too ugly, I have to
rework it. It was on an earlier version.

The improvements included :

   - Factorisation of lines in 3 directions : vertical, horizontal 45
   degrees. This is quite quick and reduces the number of points in the
   toolpath easily
   - I was never successfull to implement a Douglas Peucker algo. Is this
   implemented now?
   - Grow by zero mill on the image to extract the exact outline. Then I
   use my usual cam software to do an external cut (or internal cut when I do
   a stencil)
   - "Grow by amount" on the vectorial data, not the image.
   - Export as a gerber of the toolpath. This is necessary to run visual
   check on gerbv.


Need to check if this is still compatible to the new code. If someone want
to react (give advices, propose adjustments or tell what seems unusefull)
please do it this week, before I work on that again.

Thanks


Lionel SAINTE CLUQUE
adresse:
1, rue Paul de KOCK
92500 Rueil Malmaison
Téléphone +33 (0)6 18 04 20 75

2015-01-25 12:09 GMT+01:00 Nicola Corna <ni...@co...>:

> Hi
> I've merged your repo (https://github.com/ssfrr/pcb2gcode) into the master
> Thanks
>
> Nicola Corna
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Pcb2gcode-devel mailing list
> Pcb...@li...
> https://lists.sourceforge.net/lists/listinfo/pcb2gcode-devel
>

Re: [Pcb2gcode-devel] Some minor fixes to pcb2gcode

[Lionel S. C. <lio...@gm...>]

Dear all

I find very restrictive that pcb2gcode outputs gcode directly. If gcode syntax has to change or language has to change (dxf, gerber, …) it needs to be compiled again.

Do you think that it may be more suitable to output (let’s say) a m4 file and then convert it to gcode using a M4 template.

It is just an idea perhaps m4 is not the good language, or this idea is bad, but I think that it may be the best solution. 
Template may be different for drilling, milling, milling stencils, …

Any ideas ? 

Lionel SAINTE CLUQUE
+33(0)6 18 04 20 75

www.dipole-electronique.fr

> Le 25 janv. 2015 à 20:39, Lionel Sainte Cluque <lio...@gm...> a écrit :
> 
> Dear all
> 
> I made some improvements to pcb2gcode, but it is far too ugly, I have to rework it. It was on an earlier version.
> 
> The improvements included : 
> Factorisation of lines in 3 directions : vertical, horizontal 45 degrees. This is quite quick and reduces the number of points in the toolpath easily
> I was never successfull to implement a Douglas Peucker algo. Is this implemented now?
> Grow by zero mill on the image to extract the exact outline. Then I use my usual cam software to do an external cut (or internal cut when I do a stencil)
> "Grow by amount" on the vectorial data, not the image.
> Export as a gerber of the toolpath. This is necessary to run visual check on gerbv.
> 
> Need to check if this is still compatible to the new code. If someone want to react (give advices, propose adjustments or tell what seems unusefull) please do it this week, before I work on that again. 
> 
> Thanks
> 
> 
> Lionel SAINTE CLUQUE
> adresse:
> 1, rue Paul de KOCK
> 92500 Rueil Malmaison
> Téléphone +33 (0)6 18 04 20 75
> 
> 2015-01-25 12:09 GMT+01:00 Nicola Corna <ni...@co... <mailto:ni...@co...>>:
> Hi
> I've merged your repo (https://github.com/ssfrr/pcb2gcode <https://github.com/ssfrr/pcb2gcode>) into the master
> Thanks
> 
> Nicola Corna
> 
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet <http://p.sf.net/sfu/gigenet>
> _______________________________________________
> Pcb2gcode-devel mailing list
> Pcb...@li... <mailto:Pcb...@li...>
> https://lists.sourceforge.net/lists/listinfo/pcb2gcode-devel <https://lists.sourceforge.net/lists/listinfo/pcb2gcode-devel>
> 

Re: [Pcb2gcode-devel] Some minor fixes to pcb2gcode

[Patrick B. <pat...@gm...>]

I think it should be pretty very to write a different exporter. If I remember correctly, the program was designed to easily allow this. You can probably just start with the gcode exporter class and rewrite it as an m4 exporter, then add a "-m4" flag or something that selects the new exporter in main.cpp

-- Patrick


On Mon, 26 Jan 2015 10:05:15 +0100
Lionel SAINTE CLUQUE <lio...@gm...> wrote:

> Dear all
> 
> I find very restrictive that pcb2gcode outputs gcode directly. If gcode syntax has to change or language has to change (dxf, gerber, …) it needs to be compiled again.
> 
> Do you think that it may be more suitable to output (let’s say) a m4 file and then convert it to gcode using a M4 template.
> 
> It is just an idea perhaps m4 is not the good language, or this idea is bad, but I think that it may be the best solution. 
> Template may be different for drilling, milling, milling stencils, …
> 
> Any ideas ? 
> 
> Lionel SAINTE CLUQUE
> +33(0)6 18 04 20 75
> 
> www.dipole-electronique.fr
> 
> > Le 25 janv. 2015 à 20:39, Lionel Sainte Cluque <lio...@gm...> a écrit :
> > 
> > Dear all
> > 
> > I made some improvements to pcb2gcode, but it is far too ugly, I have to rework it. It was on an earlier version.
> > 
> > The improvements included : 
> > Factorisation of lines in 3 directions : vertical, horizontal 45 degrees. This is quite quick and reduces the number of points in the toolpath easily
> > I was never successfull to implement a Douglas Peucker algo. Is this implemented now?
> > Grow by zero mill on the image to extract the exact outline. Then I use my usual cam software to do an external cut (or internal cut when I do a stencil)
> > "Grow by amount" on the vectorial data, not the image.
> > Export as a gerber of the toolpath. This is necessary to run visual check on gerbv.
> > 
> > Need to check if this is still compatible to the new code. If someone want to react (give advices, propose adjustments or tell what seems unusefull) please do it this week, before I work on that again. 
> > 
> > Thanks
> > 
> > 
> > Lionel SAINTE CLUQUE
> > adresse:
> > 1, rue Paul de KOCK
> > 92500 Rueil Malmaison
> > Téléphone +33 (0)6 18 04 20 75
> > 
> > 2015-01-25 12:09 GMT+01:00 Nicola Corna <ni...@co... <mailto:ni...@co...>>:
> > Hi
> > I've merged your repo (https://github.com/ssfrr/pcb2gcode <https://github.com/ssfrr/pcb2gcode>) into the master
> > Thanks
> > 
> > Nicola Corna
> > 
> > ------------------------------------------------------------------------------
> > New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> > GigeNET is offering a free month of service with a new server in Ashburn.
> > Choose from 2 high performing configs, both with 100TB of bandwidth.
> > Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> > http://p.sf.net/sfu/gigenet <http://p.sf.net/sfu/gigenet>
> > _______________________________________________
> > Pcb2gcode-devel mailing list
> > Pcb...@li... <mailto:Pcb...@li...>
> > https://lists.sourceforge.net/lists/listinfo/pcb2gcode-devel <https://lists.sourceforge.net/lists/listinfo/pcb2gcode-devel>
> > 
>