Messages

111

Mach4 General Discussion / Re: activate script on button from script

« on: September 28, 2021, 11:15:45 AM »

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

Code: [Select]

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


112

Mach4 General Discussion / Re: Lua Error

« on: September 18, 2021, 05:24:13 AM »

Try deleting all .mcc files in the macros folder for the profile you are using and restart Mach. It should then recompile everything and give you mcLua.mcc

113

Mach4 General Discussion / Re: Tool changing to wrong number

« on: September 10, 2021, 04:45:10 PM »

You need to replace the parameters.ini file in your profile folder. For some reason this can get corrupted and causing this setting to always revert to next tool to use

114

Mach4 General Discussion / Re: Macro or script for A axis

« on: September 09, 2021, 03:16:34 AM »

Could an OB axis be used for this? Just set it to jog and then run a gcode?

115

Mach4 General Discussion / Re: Turn Backlash OFF in a script?

« on: September 09, 2021, 03:12:16 AM »

Backlash compensation is handled by the motion controller so you will probably have to speak to the manufacturer of the one you use to see if there is a register or something that turns it on/off

116

Mach4 General Discussion / Re: Display Work Envelop button in the Tool Path Ops tab

« on: August 20, 2021, 09:23:31 AM »

If you go into Mach4Hobby>ZeroBraneStudio>api>lua and open scr.lua you will see a list of all the scr. calls. Some of them are applicable to only Industrial such as the Editor ones. The ones you will be most interested in will just be scr.GetProperty and scr.SetProperty. Whatever you see in the Properties window within the screen editor for each of the controls you can get/set the values. 

117

Mach4 General Discussion / Re: Doing deadly unexplained rapid moves after Manual Tool Change

« on: August 11, 2021, 06:39:32 AM »

At the bottom of the screen it lists all the modal g-codes that are active. I have circled 'G1' in the image below. Check to see if 'G0' is active before resuming, this would mean the next move would be a rapid unless something other than G0 is on the next line of gcode.

Are there additional scripts that are run to move the machine to tool change position and zero the z?

118

Mach4 General Discussion / Re: Doing deadly unexplained rapid moves after Manual Tool Change

« on: August 10, 2021, 03:21:00 AM »

I would check your modals and see which gcode is active after the toolchange. Maybe it's staying in G00?

119

Mach4 General Discussion / Re: Jog Rate lost each shutdown

« on: July 31, 2021, 04:41:28 AM »

I think it depends on how Avid have set this up.. When you update the ini file manually which parameter are you changing? If you can upload the screenset I could have a look at it. Which mach4 build are using also?

120

Mach4 General Discussion / Re: Mach3 to Mach4 migration "#"

« on: July 31, 2021, 04:37:59 AM »

It says 'Axis 1 commanded while disabled'. This means exactly that. You need to check your motor configuration and that you have the correct motors mapped to the axes you are using.

If you have not set up your motors and axes yet, usually the manufacture of your motion controller will have a guide on how to do this.