Messages

201

Mach4 General Discussion / Re: Keep track of OB axis

« on: February 01, 2019, 01:00:37 AM »

if I have to resort to using Incremental moves, but that would absolutely require me to be able to update the current position of the OB1 axis.

Why? Incremental means you do not care where it is or where it is going. You only care that it goes the distance you tell it to.

The only time you need to go to an abs position is after referencing to line up with whatever slot you want. After that, incremental is all you need.

That previous line is not right. You could go to an ABS position after referencing but even that would still be better being an incremental move. I'm not sure the OB position is updated even after referencing. If not, it's still no problem. The first move will always be the same distance assuming of course it can reference with a reasonable degree of repeatability. If it can't reference with that reasonable degree of repeatability that's the first thing that needs to be fixed. 

You know what tool number it is at. You know what tool number you want to go to. Just do the math. Determine how many slots to go and what direction. Now do an incremental move of that distance in that direction.

202

Mach4 General Discussion / Re: A Aixs Brake

« on: January 29, 2019, 06:39:28 PM »

 

No problem, glad it helped.

203

Mach4 General Discussion / Re: Stop a macro and go to the end.

« on: January 29, 2019, 06:38:22 PM »

 

Yeah, it is handy.

204

Mach4 General Discussion / Re: A Aixs Brake

« on: January 29, 2019, 11:32:30 AM »

If you want to know if an axis is moving or not get its velocity.

velocity, rc = mc.mcAxisGetVel(
   number mInst,
   number axisId)

Description:
Get the velocity of an axis in user units per min.

205

Mach4 General Discussion / Re: Stop a macro and go to the end.

« on: January 29, 2019, 11:18:32 AM »

Yup, all goes in the macro. Get rid of the m6. at the beginning of the errorOut function name and where it is called.

Code: [Select]

function m6()

local inst = mc.mcGetInstance()
local rc = -40
--local selectedTool = mc.mcToolGetSelected(inst)
--local currentTool = mc.mcToolGetCurrent(inst)
--local maxDown = -4.0000 --Max distance Z will go down in the touch routine
--local rate = 30 --Feed rate the Z will go down in the touch routine
--local safeZ = 0 --Machine coordinates the Z will rapid to after touch move
--
--if selectedTool == currentTool then
-- mc.mcCntlSetLastError(inst, "Current tool == Selected tool so there is nothing to do")
--else
-- --Remove this line if you would not like the Z axis to move
-- --mc.mcCntlGcodeExecute(inst, "G90 G53 G0 Z0.0");--Move the Z axis all the way up
-- mc.mcCntlSetLastError(inst, "Change to tool " .. tostring(selectedTool) .. " and press start to touch off") --Message at beginning of tool change
-- mc.mcCntlToolChangeManual(inst, true) --This will pause the tool change here and wait for a press of cycle start to continue
-- mc.mcToolSetCurrent(inst, selectedTool)
-- mc.mcCntlSetLastError(inst, "Performing touch routine")
-- mc.mcCntlGcodeExecuteWait(inst, string.format("G31 Z%0.4f F%0.4f\nG0 G53 Z%0.4f", tostring(maxDown), tostring(rate), tostring(safeZ)))
-- mc.mcCntlSetLastError(inst, "Touch move complete")
-- mc.mcCntlSetLastError(inst, "Current tool == " .. tostring(selectedTool) .. "   Previous Tool == " .. tostring(currentTool)) --Message that shows after Cycle Start
-- local didStrike, rc = mc.mcCntlProbeGetStrikeStatus(inst)
-- if (didStrike == 1) then
-- --5063 = User position 5073 = Machine position
-- value, rc = mc.mcCntlGetPoundVar(inst, 5063)
-- mc.mcToolSetData(inst, mc.MTOOL_MILL_HEIGHT, selectedTool, value)
-- mc.mcCntlGcodeExecute(inst, string.format("G43 H" .. tostring(selectedTool)))
-- mc.mcCntlSetLastError(inst, string.format("Tool " .. tostring(selectedTool) .. " H offset set to %0.4f", value))
-- else
-- mc.mcCntlSetLastError(inst, "The touch move did not touch so we did not set a tool offset.") --Message that shows after Cycle Start
-- end
--end
--Put this in your macros function
if (rc ~= 0) then
msg = mc.mcCntlGetErrorString(inst, rc) --Get the returned error string
errorOut(msg) --Run the m6.errorOut function passing it the msg parameter
return --Exit the function this is in
end

end

--Add this function
function errorOut(msg)
local inst = mc.mcGetInstance()
mc.mcCntlMacroAlarm(inst, 3, msg)
end

if (mc.mcInEditor() == 1) then
m6()
end

206

Mach4 General Discussion / Re: Stop a macro and go to the end.

« on: January 29, 2019, 10:12:39 AM »

Something like this should be pretty close.

Code: [Select]

--Put this in your macros function
if (rc ~= 0) then
msg = mc.mcCntlGetErrorString(inst, rc) --Get the returned error string
m6.errorOut(msg) --Run the m6.errorOut function passing it the msg parameter
return --Exit the function this is in
end

--Add this function
function m6.errorOut(msg)
local inst = mc.mcGetInstance()
mc.mcCntlMacroAlarm(inst, 3, msg)
end

207

Mach4 General Discussion / Re: Can't set machine position in script

« on: January 25, 2019, 09:30:07 AM »

With any sort of luck smurph will read this post and he may be able to confirm my interpretation.

Craig is right. No way to set machine coordinates via script (on purpose). Well, unless you get very creative and just want the practice.

208

Mach4 General Discussion / Re: New CV Wizards

« on: January 10, 2019, 01:59:58 PM »

Yeah Mauri, that was a bug in the wizard introduced with Lua 5.3. It's fixed in 4026.

209

Mach4 General Discussion / Re: How do you read User Fields in the Tool Table?

« on: December 22, 2018, 10:13:49 AM »

 

210

Mach4 General Discussion / Re: How do you read User Fields in the Tool Table?

« on: December 21, 2018, 11:14:54 PM »

Depends on what kind of data is in the custom field you created. A integer, double or string. Looking at the API doc I think it would be this one for a double ........

value, rc = mc.mcToolGetDataExDbl(number mInst, number toolNumber, string fieldName) --This is the explanation of the 3 parameters from the doc

The API call should make you think....... mc.mc Tool Get Data Extended as a double

value, rc = mc.mcToolGetDataExDbl(inst, 2, "Heavy") --This is how it might look in actual use.

Then the 3 parameters are

inst = instance and the manual says its expecting a type number for this parameter
2 = Tool number and its expecting a type number for this parameter
"Heavy" = field Name and it is expecting a type string for this parameter ("" make it a string). 0 = number "0" = string