Messages

4601

General Mach Discussion / Re: Plasma Z floating head

« on: May 10, 2018, 12:31:44 AM »

Hi,

the lua script in the post processor

Lua is the scripting language of Mach4. A post processor is software associated with your CAM program.

There is no such thing as a Mach4 post processor, but rather a post processor that works with your CAM
program to produce Gcode. The Gcode to be of use must be Mach compatible.

To my knowledge no CAM manufacturer uses Lua to write their post's therefore there is no Lua script in a post
processor.

i just want the damn auto touch off feature reference which utilizes the g28.1 z0 code to work so i can cut bigge

To my knowledge G28.1 has no role in Auto Touch Off......are you confusing G31?.....G31 is used for probing
which is very much related to Auto Touch Off.

Craig

4602

Mach4 General Discussion / Re: Spindle at Speed

« on: May 09, 2018, 08:02:24 PM »

HI Steve,
kool, as I say the mc.SignalWait() restriction tripped me up back then, sounds like that limitation has
been addressed, good stuff.

If you want more control over the spindle waits using signals, and don't want to wait up to 20 seconds for a timeout, then using the mcSignalWait() API function on ISIG_SPINDLE_AT_SPEED and AT_ZERO may be what you need.

Yes, that was the exact reason that Hakan wished to pursue that idea and we did get it to work.

Craig

4603

Mach4 General Discussion / Re: Spindle at Speed

« on: May 09, 2018, 05:02:06 PM »

Hi Allan,
if I understand Steve's suggestion has a fixed delay whereas the mc.SignalWait() solution delays
ONLY until a signal from the VFD comes good. That was the intent and desire of Hakan, the bloke
I was helping at the time. Current OP, Helmut, needs the same solution.

Both Helmut and Hakan were bemused, even annoyed, that ISIG_SPINDLE_AT_SPEED and ISIG_SPINDLE_AT_ZERO
have no action despite the signal being defined within Mach's core.
Secondly they were annoyed, with some justification, that the documentation lags the reality.
I confess some exasperation that a very simple one line addition to the API.chm which would rectify
the matter has been ignored.

Craig

4604

Mach4 General Discussion / Re: Spindle at Speed

« on: May 09, 2018, 02:45:29 PM »

Hi,
the API which is subject to the signal range restriction is mc.SignalWait(). If the input signal is not  in the range ISIG_INPUT1 to ISIG_INPUT64 then you will get MERROR_INVALID_ARG.

Steve introduced mc.SpindleSetDirectionWait(), but that introduction to the conversation is recent.

Craig

4605

Mach4 General Discussion / Re: Spindle at Speed

« on: May 09, 2018, 01:58:12 PM »

Hi Allen,
and  the API was mc.SignaWait()

Craig

4606

Mach4 General Discussion / Re: Spindle at Speed

« on: May 09, 2018, 01:56:12 PM »

Hi Allen,
no there was a test for 'timed out'. The rc was MERROR_INVALID_ARG.

Craig

4607

Mach4 General Discussion / Re: Mach4/Uc100 problem with jogging

« on: May 09, 2018, 10:42:45 AM »

Hi,
a quick email to CNCDrive will clear it up.

Craig

4608

Mach4 General Discussion / Re: Mach4/Uc100 problem with jogging

« on: May 09, 2018, 10:24:55 AM »

Hi,
yes I also interpreted that as a supported Mach3 function not necessarily Mach4.

Craig

4609

Mach4 General Discussion / Re: Mach4/Uc100 problem with jogging

« on: May 09, 2018, 09:45:50 AM »

Hi,
yes I agree with ger21, I can certainly find that the UC100 supports backlash compensation with Mach3 but cannot find anything
specific about Mach4.

Given that the UC100 Mach4 plugin is so new, probably less than a year, it would not surprise me that its not yet available.

Craig

4610

Mach4 General Discussion / Re: Mach4/Uc100 problem with jogging

« on: May 09, 2018, 09:17:01 AM »

Hi,
I wasn't aware that the UC100 supported backlash. Backlash compensation is a controller enacted feature, not really Mach at all.

Craig