Ray Henry wrote:
> Unless I'm doing something very wrong, the INI file variable for
> location of part programs is completely broken. This seems to be true
> for even the most recent stuff.
Yes, I think this has been the case for some time. You mean the
default directory when you open the browse
You can use M66 as described here:
http://www.linuxcnc.org/docview/2.2/html/gcode_main.html#sec:M66:
In TRUNK (latest CVS) analog inputs also work, in the 2.2.x version only
digital inputs.
(maybe this counts as a bugfix, as the code doesn't match the docs.. if
jeff's ok with this, I could bac
Is there a mechanism to obtain return values from user defined M codes?
For example, if M101 could obtain information about something that is
not easily incorporated into the EMC system, but is readily obtained via
something like a shell script, the execution of the ngc program could be
controlled
Ah okay. I have been copying the config. But I have also been changing
PROGRAM_PREFIX to something other than ~/emc2/nc_files. It would seem
after a bit more testing that I must be typing stuff into PROGRAM_PREFIX
wrong. Thanks Alex.
Ray
On Fri, 2007-11-16 at 19:51 +0200, Alex Joni wrote:
>
The only thing I can think of that you're doing wrong is using a sample
config :)
If you select to create a copy of the config, and it gets copied to your
homedir, the PROGRAM_PREFIX variable will be fixed to point to
~/emc2/nc_files
Maybe it would be better if releases have a predefined PROGRA
Unless I'm doing something very wrong, the INI file variable for
location of part programs is completely broken. This seems to be true
for even the most recent stuff.
Ray
-
This SF.net email is sponsored by: Microsoft
De
Bloat or not, those are the whole libraries you should be grateful
for. Completely pre-fabricated ;-) ... you wouldn't want to make them
manually from gates on your own.
On 11/13/07, John Kasunich <[EMAIL PROTECTED]> wrote:
> Jeff Epler wrote:
> > On Tue, Nov 13, 2007 at 01:48:21PM -0700, Sebasti
