Messages

211

Mach4 General Discussion / Re: Mach4 Arc OK THCON signal programming

« on: December 19, 2018, 11:11:00 AM »

There will be a new build very soon that has a plasma screen, profile (including macros) etc., THC support........ pretty much everything you need for plasma.

212

G-Code, CAD, and CAM discussions / Re: Help! I need gcode to respond to an input.

« on: October 12, 2018, 10:25:48 AM »

We have developed a surface mapping wizard for Mach4 that I think will be out in the next release. It will do exactly what your looking for (compensate for differences in Z height). I know this doesn't help with Mach3 but development of Mach3 ended years ago.

The MapSurface wizard is pretty slick. You can set the min and max positions to map in X and Y, set the resolution of the units and mapping grid, select the one of 4 possible probes you want to use, etc. You should also be able to lay a map on top of another map. In other words you could do a coarse mape of a big table (say 5' X 10') at something reasonable like a 6 inch grid. Then when you want to do a highly accurate area (say 3" X 3" for a PCB) you could map just that area at some insane resolution grid (like every .010 inch) and enable that map to route your PCB. Here are some screenies of what it looks like.

Since the map points are dependent on knowing where the X, Y and Z are you get a warning it any enabled axis hasn't been homed (referenced). You can ignore it (but i wouldn't) or leave, reference the machine then run it.

213

Mach4 General Discussion / Re: Can I Lockout Mach 4 unless correct post processor is used?

« on: October 12, 2018, 10:02:38 AM »

You can test for the correct file in PLC script. You can't put it in a buttons script because all of it's events would have already ran (pretty sure but didn't test to be honest). If there is a Gcoded loaded signal you might be able to make it a function and run it when that singlas state changes. Would be a better place than the PLC script but I didn't take time to look for or test that either.

Below is a script to do what you want. It looks for the string "Test" beginning at the second and ending at the 5 position on line 0 (Very first line of Gcode). The reason it starts a the second position is the first will be a ; or (.

Anyway, place the script in the PLC script after the inst variable is defined. Add the line "(Test)" (minus quotes) as the very first line of your Gcode and play with it. Once you are comfortable with it you can comment out the line writing to the error label and uncomment the line that pops up a message box.

Code: [Select]

local curGcode, rc = mc.mcCntlGetGcodeFileName(inst)
if  (curGcode ~= lastGcode) then -- Gcode files changed
lastGcode = curGcode
if (curGcode ~= "") then --A gcode file is loaded
--mc.mcCntlSetLastError(inst, "curGcode (" .. curGcode .. ")")
local buff, rc = mc.mcCntlGetGcodeLine(inst, 0)
local s,e = string.find (buff, "Test")
if (s ~= 2) or (e ~= 5) then --The start and/or end of the unique identifier is not in the right place or it doesn't exist
local rc = mc.mcCntlCloseGCodeFile(inst)
mc.mcCntlSetLastError(inst, "File closed due to incorrect format " .. buff)
--wx.wxMessageBox("File closed due to incorrect format " .. buff)
end
end
end

214

Mach4 General Discussion / Re: Can I Lockout Mach 4 unless correct post processor is used?

« on: October 11, 2018, 07:45:24 AM »

You could do what Gary said then when you load the Gcode look at the whatever line number and if it doesn't equal the unique string close the Gcode and pop up a message box saying why it closed. All of the API calls needed to do it exist.

buff, rc = mc.mcCntlGetGcodeLine(number mInst, number LineNumber)
rc = mc.mcCntlCloseGCodeFile(number mInst)

Or, save the unique files with a unique identifier in the name or to a unique location for each machine. You can get the name including the location with.......

buf, rc = mc.mcCntlGetGcodeFileName(number mInst)

Lots of ways to do it. Just think about how you want it to work and do it.

215

Tangent Corner / Re: Always check the deals.

« on: July 12, 2018, 10:57:18 AM »

Not sure if I pay closer attention now or if it really has changed that much over the last 20 years but it sure seems most are in a race to the bottom.

216

Mach4 General Discussion / Re: Exchange settings

« on: July 03, 2018, 04:57:45 PM »

 

217

Mach4 General Discussion / Re: Exchange settings

« on: July 03, 2018, 08:27:30 AM »

All true Craig. Packing your profile (is the short answer) will get the ini, macros, screen and all. But like I said, this is covered in the manual. As well as setting up a custom profile and some other bits that you will likely find helpful.

I usually copy a default profile giving it a unique name then save one of the default screens with the same name as the profile.

218

Mach4 General Discussion / Re: Exchange settings

« on: July 03, 2018, 05:19:47 AM »

That information is covered in the Mach 4 CNC Controller Config manual in the docs folder. In particular the "Setting up the Profile" section.

219

Mach4 General Discussion / Re: Anybody have a working M6 ATC Macro for Mach 4 ?

« on: July 01, 2018, 04:55:08 PM »

Here are 2 m6s I have done. Neither of these are for ATC though. Both are for manual/manumatic. Descriptions are in the comments in the code.

This one is the current default m6 that comes with Mach4. It was recently updated. It is meant for those doing manual tool changes. It does not stop the spindle, coolant, update any offsets, etc. It just stops running the Gcode. Gcode is resumed with a press of cycle start.

Code: [Select]

function m6()

local inst = mc.mcGetInstance()
local selectedTool = mc.mcToolGetSelected(inst)
local currentTool = mc.mcToolGetCurrent(inst)

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 continue") --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.mcCntlSetLastError(inst, "Current tool == " .. tostring(selectedTool) .. "   Previous Tool == " .. tostring(currentTool)) --Message that shows after Cycle Start
mc.mcToolSetCurrent(inst, selectedTool)
end
end

if (mc.mcInEditor() == 1) then
m6()
end
The code below is very similar to the default above. Only instead of just pausing the Gcode it allows you to jog to a probing position and once over the probe, click cycle start. This will begin a probing move. If that probe move is successful it will update the tools height in the tool table. It is very important to have the default move after the probing in the Gcode....... or you could add this default move to the m6 itself but it is not in it as is.

Code: [Select]

function m6()

local inst = mc.mcGetInstance()
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
--mc.mcCntlGcodeExecuteWait(inst, "G90 G53 G0 Z0.0") --Uncomment this line if you would like to move the Z axis to machine coords 0
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))) --Probe move
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, mc.SV_PROBE_POS_Z)
--value, rc = mc.mcCntlGetPoundVar(inst, 5063) --Same as line above but line above uses the Mach constant instead of the #var
mc.mcToolSetData(inst, mc.MTOOL_MILL_HEIGHT, selectedTool, value) --Set the tool height to what was determined by probe move
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
end

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

220

General Mach Discussion / MOVED: WHATS THIS ERROR..??? Clearing a spurious limit hit latch event,

« on: June 24, 2018, 09:05:54 PM »

This topic has been moved to Mach4 General Discussion.

http://www.machsupport.com/forum/index.php?topic=37598.0