Messages

6621

Mach4 General Discussion / Re: M code macros do not run

« on: September 21, 2017, 03:26:55 AM »

Hi,
not really. Sounds rather like the macro m111.mcs is where its supposed to be but the Lua editor is not enabled and therefore the script cant be opened.

The only thing I can think of is that the Gcode editor is not enabled in you QR profile. Go to Configure/Mach/General and upper right hand side is a text box
with the path to the Gcode file editor. Is it populated with a legitimate file editor?

Craig

6622

Mach4 General Discussion / Re: Homing sequence triggering by limit switch possible?

« on: September 21, 2017, 03:15:10 AM »

Hi,
I follow your script and see what your trying to achieve. I don't know what the errors are and the log files don't mean much to me either.

I do have a couple of questions tho...

Code: [Select]

local mInst=0;
local X_AXIS=0;
local Y_AXIS=1;
Did you decide that you were going to ascribe a Mach instance? Whenever I've done any coding I've always set mInst by asking MachCore what the
current instance is:
local mInst=mc.mcGetInstance()

Also I thought X_AXIS and Y_AXIS are C++ constants, part of Mach. Redefining them seems counterproductive to me.

As you can tell I'm very much a LUA newbie but its fascinating none the less.

Craig

6623

Mach4 General Discussion / Re: M code macros do not run

« on: September 21, 2017, 02:51:57 AM »

Hi,
well that's a different problem altogether and I don't think I'm going to be able to help.

It occurred to me after posting my reply to you this morning that if you go Operator/Edit-Debug scripts the list of scripts in your profile will be displayed,
a very simple test to prove that the file has been placed correctly.

As you probably know all the LUA fragments including your scripts get compiled and put together in one big LUA chunk at run time. If for whatever reason the
script didn't compile then it wouldn't end up in the chunk and wouldn't run if you called it. Does that describe whats happening? If so you could probably check
that it does compile without error. How you check whether it gets included in the chunk I don't know...hopefully someone will chime in with an explanation.

Craig

6624

Mach4 General Discussion / Re: cad/cam software that link with mach4 on USB to control

« on: September 21, 2017, 02:40:36 AM »

Hi All,
apologies to OP, I just couldn't pass it up!

Jokes aside I think OP is being just a bit hopeful, there is usually a lot of work that goes in between artwork and a Gcode job ready to cut. I have experimented
with the Art features of Mastercam and is very good. Takes quite some work, its not automatic. Of course Mastercam with all the bells and whistles is over
$20k and 2.5k annually, hardly hobbyist material, shame, it is good.

Craig

6625

Mach4 General Discussion / Re: cad/cam software that link with mach4 on USB to control

« on: September 20, 2017, 08:39:32 PM »

Hi,
from artwork to Mach4 without any intervening steps...try the CNCfairy, last I heard he was flatting with the
Easter Bunny smoking a lot of weed and bonking all the girls!

Craig

6626

Mach4 General Discussion / Re: M code macros do not run

« on: September 20, 2017, 06:02:14 PM »

Hi,
your file should be in the macros folder of YOUR profile.

Craig

6627

General Mach Discussion / Re: Does G28.1 always instantly reset a homed axis to zero? Can it be made not to?

« on: September 20, 2017, 04:52:15 PM »

Hi,
yes, my understanding is that Mach4 will permit one input pin to be assigned to two signals, home X axis
and G31.1 for instance.

Craig

6628

General Mach Discussion / Re: Interference with axis motors

« on: September 20, 2017, 04:49:39 PM »

Hi,
debounce is not going to help you, it applies to inputs to Mach, your problem is noise on the outputs...

Additionally the debounce setting you see on the General Setup screen applies to the parallel port whereas it
may not apply to the motion control you are actually using.

Craig

6629

General Mach Discussion / Re: Does G28.1 always instantly reset a homed axis to zero? Can it be made not to?

« on: September 20, 2017, 03:14:43 PM »

Hi,
multiple probe inputs are a Mach4 feature. Probing is in large part done by the motion control plugin, Warp9 have added multiple probe input
capability to the ESS plugin in the last few months only.

Craig

6630

General Mach Discussion / Re: Interference with axis motors

« on: September 20, 2017, 02:51:38 PM »

Hi,
debounce is a bit like a filter. If you set it Mach will wait until the signal has been constant for a period of time before it will act on it.

Imagine a big noise spike gets induced into one of your limit switches. If Mach responded instantly the machine would stop immediately thinking
that its preventing a crash. The big noise spike however will be over in nano seconds, if Mach waits for several micro seconds before responding
it would realise that the limit signal was false.

It is called debounce because it was originally for a switch. Often as a switch as it either makes or breaks its connection it will jitter and make-break several
times before it settles into its new state. A reasonable debounce setting in Mach prevented a 'bouncing' contact to cause multiple events.

It can be useful for suppressing noise but if the source of noise is quasi-continuous it won't work. As has already been posted its better to prevent the noise
from being 1) generated and 2) transmitted.

Craig