X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20210112;
	h=mime-version:references:in-reply-to:from:date:message-id:subject:to
	:cc;
	bh=lTPDrcxuJTf5cG0BWr3NS+dNtruTBpFR9iBmSMJuIsA=;
	b=c5lDbnLDfjZFjtzN3px/MsVqxs5tYCCeo2K7LapU5SvWTk77QS31QAWmDafxiLRZ4m
	ZuI09eohKE1CtwZI4shS/ltAfvfrI4qAPJw1uUpnLfckXKeyXGxlpPrGKNC/uy7IHe63
	TIAOPVGYDlPhtbiLtwe0CD2XyifOmDXx833AGZZ1omOwq4JYYigMm9D83Vf4BpJMx0a+
	MiKb57FwhtHXNh3WdIhBpqfnBZr9pEpXTqAMzaUj6Ix/fdol6szdaLWlgNEjlqcoWhLl
	3kMiOvFP3/YkZbUuUw4enaHW/q/cVr1ObGfSbyLQk12x1VruqhmiIyd3LTpPTiTqGcLX
	FdUQ==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20210112;
	h=x-gm-message-state:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:cc;
	bh=lTPDrcxuJTf5cG0BWr3NS+dNtruTBpFR9iBmSMJuIsA=;
	b=ZuaD/W1o4P+u3JWUGRn1rdvzsWXB5sYZogt654xQQFwC0ZThpalR7NgM5ZtOC08qPh
	4B2I2qsIUvMpk9EKX4KA+5qqFdFolzIBTYdP7yTdER4JD1h639O2hHrf1lUSaeCIjFiv
	HrmrSOglMUu2HNtQ3Jx1VshiJ1iw7Jat/Haz89Vz96YSXeGGfOvhsvYIvQVwnxL7bRa6
	NLP1gawbEajlf32CAd3q2l05fm9cvheqy1uA8f3bqlW81k2ywN2GrkKj5aY7N2NkNGUq
	ZH8paS9PHocrq03Kd5myR5tAje3O5rQRrx5FW10nl1375pRTme5/IF6NoC13KFRKCD1V
	rPIQ==
X-Gm-Message-State:	AJIora8wK8SIClfy+a5e16CDQbQgy3QEL++InReNBEfrxCveDlpkNtAm
	39koAJN4/+NJQDr6cEoWCyhPRt4k735P/upf84gwqwQi
X-Google-Smtp-Source:	AGRyM1syA3arJCa4D+PwchFrW860rGsYKLcFyrCWgpetItB6QeC5uncWmwqpWQ8kxdLhm+04tnLyl8S4reNtdTpYUPY=
X-Received:	by 2002:a05:6830:2016:b0:60c:468:e30 with SMTP id
	e22-20020a056830201600b0060c04680e30mr1884711otp.271.1655382328164; Thu, 16
	Jun 2022 05:25:28 -0700 (PDT)
MIME-Version:	1.0
References:	<c7bdfc66-52cb-3fd6-5a7f-831b9af70901 AT epilitimus DOT com>
In-Reply-To:	<c7bdfc66-52cb-3fd6-5a7f-831b9af70901@epilitimus.com>
From:	"Erich Heinzle (a1039181 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Date:	Thu, 16 Jun 2022 21:55:15 +0930
Message-ID:	<CAHUm0tPJBgrOQSaKQUPVN6Kzr9cuWp+mdtCbOo96TvXftRfSyQ@mail.gmail.com>
Subject:	Re: [geda-user] pcb- gcode export
To:	geda-user <geda-user AT delorie DOT com>
Cc:	miho23 AT igor2 DOT repo DOT hu
Reply-To:	geda-user AT delorie DOT com

--000000000000a3450705e18fbbbb
Content-Type: text/plain; charset="UTF-8"

for some time now pcb-rnd has had user configurable CAM exporters,  to
allow customised exporting for different fabs and workflows.

see also

http://repo.hu/cgi-bin/pool.cgi?cmd=show&node=cam

the lead dev is able to implement support for user configurable pre and
post gcode headers and footers pretty quickly,  but would need someone
willing to build pcb-rnd and the support library librnd from svn head to
test the implementation in production.

The code just needs to be modified to support a header and footer in an
optional, plugin specific config file.

I have included the lead developer in the cc:, so, if you are keen to see
this feature supported and are willing to build and test, let him know.

regards,

Erich

On Thu, 16 Jun 2022 13:55 Glenn (glimrick AT epilitimus DOT com) [via
geda-user AT delorie DOT com], <geda-user AT delorie DOT com> wrote:

> How hard would it be to make the gcode prefix/postfix code optionally
> loaded from a file?
>
> My situation is that my super cheap pcb router doesn't support bits of
> the prefix (G64 & M7) and I would like to have some custom postfix code
> in each gcode file (Moves to a safe location essentially) but the prefix
> and postfix code are hard coded into the binary.
>
> So unless I am missing something my options are:
> 1. hand edit each gcode file (already getting old)
> 2. Hack the source code (hid/gcode/gcode.c) to make it what I want -
> which is what I am probably going to do
> 3. Beg for a feature.
>
> So consider this me begging, low priority, as I said I will probably
> just fix my local copy. But I thought it worth mentioning in case
> someone is feeling bored.
>  I don't know gtk and don't feel motivated enough to learn it just for
> this. My approach would be a check box and text box on the gcode export
> dialog. If the checkbox is checked the text box is a file that contains
> the pre/postfix code.
>
> And since I am begging it would be nice if the export settings were
> saved so they don't have to be reentered every time.
>
> Okay I'm done now.
>
> running 4.2.2
>
>

--000000000000a3450705e18fbbbb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">for some time now pcb-rnd has had user configurable CAM e=
xporters,=C2=A0 to allow customised exporting for different fabs and workfl=
ows.=C2=A0<div dir=3D"auto"><br></div><div dir=3D"auto">see also</div><div =
dir=3D"auto"><br></div><div dir=3D"auto"><a href=3D"http://repo.hu/cgi-bin/=
pool.cgi?cmd=3Dshow&amp;node=3Dcam" target=3D"_blank" rel=3D"noreferrer">ht=
tp://repo.hu/cgi-bin/pool.cgi?cmd=3Dshow&amp;node=3Dcam</a><br></div><div d=
ir=3D"auto"><br></div><div dir=3D"auto">the lead dev is able to implement s=
upport for user configurable pre and post gcode headers and footers pretty =
quickly,=C2=A0 but would need someone willing to build pcb-rnd and the supp=
ort library librnd from svn head to test the implementation in production.<=
/div><div dir=3D"auto"><br></div><div dir=3D"auto">The code just needs to b=
e modified to support a header and footer in an optional, plugin specific c=
onfig file.</div><div dir=3D"auto"><br></div><div dir=3D"auto">I have inclu=
ded the lead developer in the cc:, so, if you are keen to see this feature =
supported and are willing to build and test, let him know.</div><div dir=3D=
"auto"><br></div><div dir=3D"auto">regards,</div><div dir=3D"auto"><br></di=
v><div dir=3D"auto">Erich</div></div><br><div class=3D"gmail_quote"><div di=
r=3D"ltr" class=3D"gmail_attr">On Thu, 16 Jun 2022 13:55 Glenn (<a href=3D"=
mailto:glimrick AT epilitimus DOT com" target=3D"_blank" rel=3D"noreferrer">glimri=
ck AT epilitimus DOT com</a>) [via <a href=3D"mailto:geda-user AT delorie DOT com" target=
=3D"_blank" rel=3D"noreferrer">geda-user AT delorie DOT com</a>], &lt;<a href=3D"m=
ailto:geda-user AT delorie DOT com" target=3D"_blank" rel=3D"noreferrer">geda-user=
@delorie.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">How har=
d would it be to make the gcode prefix/postfix code optionally<br>
loaded from a file?<br>
<br>
My situation is that my super cheap pcb router doesn&#39;t support bits of<=
br>
the prefix (G64 &amp; M7) and I would like to have some custom postfix code=
<br>
in each gcode file (Moves to a safe location essentially) but the prefix<br=
>
and postfix code are hard coded into the binary.<br>
<br>
So unless I am missing something my options are:<br>
1. hand edit each gcode file (already getting old)<br>
2. Hack the source code (hid/gcode/gcode.c) to make it what I want -<br>
which is what I am probably going to do<br>
3. Beg for a feature.<br>
<br>
So consider this me begging, low priority, as I said I will probably<br>
just fix my local copy. But I thought it worth mentioning in case<br>
someone is feeling bored.<br>
=C2=A0I don&#39;t know gtk and don&#39;t feel motivated enough to learn it =
just for<br>
this. My approach would be a check box and text box on the gcode export<br>
dialog. If the checkbox is checked the text box is a file that contains<br>
the pre/postfix code.<br>
<br>
And since I am begging it would be nice if the export settings were<br>
saved so they don&#39;t have to be reentered every time.<br>
<br>
Okay I&#39;m done now.<br>
<br>
running 4.2.2<br>
<br>
</blockquote></div>

--000000000000a3450705e18fbbbb--

- Raw text -