Messages

561

Mach4 General Discussion / Re: Arc ok signal in Mach4

« on: February 12, 2016, 01:45:09 PM »

If you already have a way of getting the signal into mach4 then you could add to the m03 at the end mc.SignalWait command to halt all untill the ARC OK signal is recieved.

DazTheGas

562

Mach4 General Discussion / Re: Can I "level" my work piece in software?

« on: February 07, 2016, 05:11:44 PM »

Well if you fortunate enough to get the go ahead from the wife then i would get right on it.

DazTheGas

563

Mach4 Toolbox / Re: Lua scripting manual has been removed, use the Mach4 API help file

« on: February 03, 2016, 02:50:39 AM »

very nice idea to convert to pdf but the whole idea of pushing to use the api docs was that in each release they would be upto date, unfortunately after another release your pdf will be superceeded by a new api docs thus being outdated.

DazTheGas

564

Mach4 General Discussion / Re: Touchprobe

« on: February 02, 2016, 11:07:08 AM »

on the probing screen under bore.

DazTheGas

565

Mach4 General Discussion / Re: Mach4 ESS Homing

« on: February 01, 2016, 05:14:09 PM »

The complete setup for the ess is there and the homing part is https://www.youtube.com/watch?v=cB-B1-SaZ_0&list=PL7IitnI6IOQB0Ws59EFXhBtYsWOgPCKT9&index=3

DazTheGas

566

Mach4 General Discussion / Re: Mach4 ESS Homing

« on: February 01, 2016, 03:47:02 PM »

Have you setup your homing in the ess config, there is a tab for homing.

DazTheGas

567

Mach4 General Discussion / Re: Can someone better explain probing setup?

« on: February 01, 2016, 03:12:48 AM »

If your talking about the probing screen then your dro is showing 1 which is in the plus direction, change to -1

DazTheGas

568

Mach4 General Discussion / Re: Calling an "Action" from a lua script

« on: January 30, 2016, 04:40:43 AM »

To do something like this you would need to script your own function, heres a start for ya.

Code: [Select]

local inst = mc.mcGetInstance() -- declare our instance
local CurInc = mc.mcProfileGetInt(inst,"Preferences","JogIncSet",0) --make a new setting in profile to hold our current inc number

CurInc = CurInc + 1 -- increment our CurInc by 1

if CurInc > 10 then CurInc = 1 end -- if our CurInc is greater than 10 then go back to 1

local SetInc = mc.mcProfileGetDouble(inst,"Preferences","JogInc"..CurInc,0.00) -- fetch our inc value from the profile JogInc + 2 say = [Preferences][JogInc2]

mc.mcJogSetInc(inst, mc.X_AXIS, SetInc) -- set inc for axis
mc.mcJogSetInc(inst, mc.Y_AXIS, SetInc) -- set inc for axis
mc.mcJogSetInc(inst, mc.Z_AXIS, SetInc) -- set inc for axis

mc.mcProfileWriteInt(inst,"Preferences","JogIncSet",CurInc) --set our profile to new CurInc

DazTheGas

569

Mach4 General Discussion / Re: Mach4 Screenset Customisation Question - Sliders

« on: January 27, 2016, 04:37:44 AM »

Unfortunately I never found a way of changing the foreground colour within the screen editor or with any external wxform builders, i may be wrong but I came to the conclusion that wxlua/wxwidgets was using the system colours for sliders and other controls so it could use the windows themes.

Again the leds are a very hit n miss thing - every now and then even during normal running the background of these can turn white, unfortunately this is not a mach4 coding error, it is somewhere between wxwidgets or wxlua Z height control.

DazTheGas

570

Mach4 General Discussion / Re: Mach4 G28.1 Z equivalent?

« on: January 25, 2016, 07:38:39 PM »

I would tend to just do all macros in uppercase ( function M100 and name the file M100 ) as most cam programs output the gcode in upper case anyway, plus windozzzee wont allow 2 files with same name. you may of noticed the confusion lately with the M6 macro not working because the file was named M6 but the function inside was declared as m6.

As for starting the journey, were all onit :-)

DazTheGas