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=simple; d=mail.ud03.udmedia.de; h=
	subject:to:references:from:message-id:date:mime-version
	:in-reply-to:content-type:content-transfer-encoding; s=beta; bh=
	8Gel7845X8RcKBJw9fCjhQmQLbn/cfxI9RlfDjS/1ow=; b=fMoFFs9DQP9mFHHf
	jFac5WxGpU/bjYUJqXtN9vA8gl5/lOLXxtPnnLtLEGVDSE/VgrPOswUxII4pLZsn
	wIsbSGieTDh6lrvnygIwvAknTwGW0hh+SpaYNtcunuDU/LZ9s+Jx4Dhlfu2oRXQS
	Tb/tsFHW7Zll8+U1lFarj9NS9jI=
Subject:	Re: [geda-user] gCode output
To:	geda-user AT delorie DOT com
References:	<alpine DOT DEB DOT 2 DOT 00 DOT 1509010447310 DOT 6924 AT igor2priv>
	<CAM2RGhRxevpXzeQpOV-OMtRhofjeSQxMkr0iFsutZ0a2EX9rcQ AT mail DOT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1509010743560 DOT 6924 AT igor2priv>
	<CAM2RGhSs=o0OT9AcWp9rfd=MRRxT3r5uyDa6VBcT66fXkEituw AT mail DOT gmail DOT com>
	<55E5A6BA DOT 4030606 AT jump-ing DOT de> <201509011657 DOT t81Gve9d017777 AT envy DOT delorie DOT com>
	<1441151947 DOT 12067 DOT 57 DOT camel AT benjamin-hp-g70>
From:	"Markus Hitter (mah AT jump-ing DOT de) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID:	<55E64B10.1060007@jump-ing.de>
Date:	Wed, 2 Sep 2015 03:04:16 +0200
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
	Thunderbird/38.2.0
MIME-Version:	1.0
In-Reply-To:	<1441151947.12067.57.camel@benjamin-hp-g70>
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

Am 02.09.2015 um 01:59 schrieb Benjamin L. Naber:
> So I'm curious, under what standard was the gCode generator built?

To the standard of a LinuxCNC controlled machine as well as to a Teacup Firmware driven one. There's a checkbox at the bottom of the dialog to switch between these two. These two choices cover a wide range of milling machines.

> Having experimented with a handful of EDA gcode generators, every single
> one outputs a different style of gcode. And, too add to this mess, every
> single CAM and machine controller responds differently to gcode styles.
> 
> This is very annoying.
> 
> I also notice that no one sticks to a standard of something such as
> turning on a spindle, specifying speed, and so on.

The trick is to read a machine's manual and to adjust a given G-code program to match what's written there. If you find this annoying, such a machine and this software is not for you.

> ... yet another damn program in the toolchain to generate a PCB
> from a pretty picture on the screen?

When you're positive to stop yelling and whining and invest some time to find a solution for your case you can try again. I won't defend software which is the result of hundreds of hours of my work and which I provide for free. Maybe you had more respect if I'd ask for $ 5'000 for your download.


Markus

-- 
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. (FH) Markus Hitter
http://www.jump-ing.de/

- Raw text -