Steve and Daz, Back in 2016 I was helped with the same issue of how to set up an Mcode in Mach4. Steve has listed the steps again but it does not work for me.  I am not sure where I am failing but back in 2016, Daz listed putting the require line into a module load file in the profile/macros directory which Steve did not mentioned this time.  Is this an omission or a change in the version of Mach4? I think I have done everything else correctly but the Mcode programmed M100 never does anything.  I have stepped away from Mach4 and Lua for several years and am back trying to get proficient again, sorry.

I updated to the newest version today since I was running on a version from 2016 but that has not helped.  The post dealing with the topic was topic=33849.20  This time, we are taking about a toolbox which I would like to implement.  Should I start a new topic or continue here. I also am working on Steve's last help for machine state, but not successful yet.

Thanks

I did mention the module load file. 

In a file called MyToolbox.mcs in your profile's macros directory:

Code: [Select]

mt = require("MyToolboxModule") -- mt is the namespace by which you access the functions in the module.  Short for "My Toolbox". :)


There are several examples out here on the forum that use one file to load/require all modules that you want in the macro script environment.  But I like to put each require into their own separate file, named appropriately of course.  To me, it is a little more clear when you go looking at the stuff months from now.   

Steve

How about using register flags like switches on the old machines before CNC

have reg1, reg2, reg3.  0=off 1=on

reg1 on and reg2 and reg3 off means automatic testing started go ahead and do G code move

reg1on and reg2 on and reg3 off means G code move finished so ok to record from analog inputs then when finished recording turn reg3 on

reg1,2,3 on means done and now save data and switch reg2 and 3 off indicating back to G code move

function WaitForIdle()
    local state = mc.mcCntlGetState()
    if (state == mc.MC_STATE_IDLE) then
         return true
    end
    return false
end

cant get this to work  tried lots of stuff but it will not compile

thanks

You are missing the 'inst' from mcCntlGetState.. see below

function WaitForIdle()
    local inst = mc.mcGetInstance()
    local state = mc.mcCntlGetState(inst)
    if (state == mc.MC_STATE_IDLE) then
         return true
    end
    return false
end


function WaitForIdle()
    local inst = mc.mcGetInstance()
    local state = mc.mcCntlGetState(inst)
    if (state == mc.MC_STATE_IDLE) then
         return true
    end
    return false
end

I think I tried the inst without success, but will try again   thanks

function WaitForIdle()
    local inst = mc.mcGetInstance()
    local state = mc.mcCntlGetState(inst)
    if (state == mc.MC_STATE_IDLE) then
         return true
    else
    return false
   end --added end here
end

is this better but I think it still fails I will try both

This is the proper script!

function WaitForIdle()
   local inst = mc.mcGetInstance()
   local state = mc.mcCntlGetPoundVar(inst, mc.SV_MSTATE)--Returns the Machine State
   --Idle will return 0
      if (state == 0) then
      return true
   else
      return false
   end
end

I would use mc.mcCntlGetState(inst) over the #var.  The G code variables can be stale depending on what the interpreter is doing. 

This compiles fine:
function WaitForIdle()
    local inst = mc.mcGetInstance()
    local state = mc.mcCntlGetState(inst)
    if (state == mc.MC_STATE_IDLE) then
return true
    end
    return false
end

Steve

Thanks Steve