Hello Guest it is May 28, 2026, 04:56:40 PM
Profile Guest

Recent Posts

Pages: « 1 2 3 4 5 6 7 8 9 10 »
11
MachPro General Discussion / Re: RC ATC Dustboot
« Last post by cd_edwards on May 20, 2026, 12:54:33 PM »

-- Dustshoe Entry Settings
local inst = mc.mcGetInstance()

local DustBootX = 45.85   
local DustBootY = 36.4
local DustBootZ = -4.3513
local DustBootRateY = 100
local DustBootRateZ = 50
local DustBootYSlide = 5   
local DustBootSafeZ = -0.1

--  ============================================================ PICKUP DUST SHOE ==========================================================================   
   
function m2223()
   local toolnum, rc = mc.mcToolGetCurrent(inst)
    if (toolnum == 0 or rc ~= 0) then
      do return end
   end
   
   GCode = string.format("G00 G90 G53 Z%.4f\n", DustBootSafeZ)                                       ------ Z UP
   mc.mcCntlGcodeExecuteWait(inst, GCode)                                       ------ Z UP
   
   GCode =  string.format("G00 G90 G53 X%.4f Y%.4f\n", DustBootX, DustBootY-DustBootYSlide)                                  ------ To DustShoe Entry X
   mc.mcCntlGcodeExecuteWait(inst, GCode)
   
   GCode = string.format("G00 G90 G53 Z%.4f\n", DustBootZ+0.75)                                 ------ G00 Quick down to 20mm above DustShoe Pick Up
   mc.mcCntlGcodeExecuteWait(inst, GCode)
   
   GCode = string.format("G00 G90 G53 Z%.4f F%.4f\n", DustBootZ,DustBootRateZ/2)                     ------ DustShoe Pick Up
   mc.mcCntlGcodeExecuteWait(inst, GCode)
            
   GCode = string.format("G00 G90 G53 Y%.4f F%.4f\n", DustBootY,DustBootRateY)      ------ DustShoe SlideOutY
   mc.mcCntlGcodeExecuteWait(inst, GCode)

   GCode = string.format("G00 G90 G53 Z%.4f\n", DustBootSafeZ)                                                             ------ PICK UP Z --- DROP SHOE IN HOLDER --
   mc.mcCntlGcodeExecuteWait(inst, GCode)
end   

I need to move to a specific location in XYZ,  then slide forward 5 inches and finally raise Z up to remove my dust boot. To pick it up, I need to go to a specific XYZ, drop Z down ontop of the boot, and slide backwards. It's magnetically attached to the spindle shoe and can not be on the spindle when doing a tool change. is it hicky? maybe, but it's what I've got on my home built machine.

 
12
MachPro General Discussion / Re: Spindle reverse
« Last post by paul.stephens on May 20, 2026, 12:52:52 PM »
What do you have set to Spindle Forward and Spindle Reverse?
https://prnt.sc/vZgG7ANe2w00

Are you using any custom logic that overwrites the original M3 or M4?
13
MachPro General Discussion / Re: RC ATC Dustboot
« Last post by paul.stephens on May 20, 2026, 12:49:21 PM »
I believe we currently have dust shoe/cover logic built into the core now and can be setup through settings.
Example image of setup:
https://prnt.sc/1oNqaz78JPfj

I believe the logic is called for every tool change regardless if the settings are defined or not.
Alternatively, we have built in Mcodes for dust cover, m112 dust cover open and m113 for dust cover closed.

We do have additional hooks for open dust cover and close dust cover. We have Pre open logic and post open logic as well as Pre close and post closed logic.
These functions will still be used for the m112 and m113 Mcodes.

Code: [Select]
function UserMCodeModule.TC_PreOpenDustCover()
------------------ Add user code below this line ------------------

------------------ Don't Edit below this line -----------------------
return nil, true, w.FunctionCompleted()
end
function UserMCodeModule.TC_PostOpenDustCover()
------------------ Add user code below this line ------------------

------------------ Don't Edit below this line -----------------------
return nil, true, w.FunctionCompleted()
end
function UserMCodeModule.TC_PreCloseDustCover()
------------------ Add user code below this line ------------------

------------------ Don't Edit below this line -----------------------
return nil, true, w.FunctionCompleted()
end
function UserMCodeModule.TC_PostCloseDustCover()
------------------ Add user code below this line ------------------

------------------ Don't Edit below this line -----------------------
return nil, true, w.FunctionCompleted()
end

In short, if you just need I/O to fire and a delay, just use the settings. This will handle your logic on tool changes automagically. If you need to ever manually fire your Dust cover, you can use m112 and m113. If you need custom pre and post logic applied, you will need to use the functions provided above. This method will ensure that everything works well together. These functions will be called in the UserMCodeModule.

In terms of Tool Change hooks... We have over 500 different hooks that can be called. Could I get a little more of a description of what you're trying to accomplish?

If you want to ignore the Dust cover operation in special cases, you can modify the setting that applies the logic.
https://prnt.sc/AW2WiikpoSyF
Use the example code below to modify it.

w.SetOEMParamValueString(RegName, val, inst)

Code: [Select]
local inst = mc.mcGetInstance("Function Name")
w.SetOEMParamValueString("AutoToolChangerDCBehavior", "Do Nothing", inst) -- Turns Dust cover behavior to do nothing when function is called.
w.SetOEMParamValueString("AutoToolChangerDCBehavior", "Open", inst) -- Turns Dust cover behavior to Open when function is called.
w.SetOEMParamValueString("AutoToolChangerDCBehavior", "Open-Return To Prev State", inst) -- Turns Dust cover behavior to do Open, and then return to the previous state when finished, when function is called.
w.SetOEMParamValueString("AutoToolChangerDCBehavior", "Open-Close", inst) -- Turns Dust cover behavior to Open and then later close, when function is called.

You can use this same logic for running a Tool Setter as well.
Code: [Select]
w.SetOEMParamValueString("AutoToolSetterDCBehavior", "Do Nothing", inst)

Set this logic to apply on a dashboard button when selected. You can also use w.GetOEMParamValueString(RegName, inst   ) to check its current state.
14
MachPro General Discussion / Re: Change Log
« Last post by paul.stephens on May 20, 2026, 09:52:22 AM »
We are currently in the process of making a changelog for software updates. This is not something that has been released yet. As of right now, any changelogs are going to be a higher level overview of the changes made for each normal release. The current Log for the new release is awaiting approval.
15
MachPro General Discussion / Spindle reverse
« Last post by cd_edwards on May 19, 2026, 02:03:58 PM »
What includes MachPro and m4 reverse spindle?  I am unable to use m4 to reverse spindle.  mc command will work. RCATC works in reverse but m4 does not?
16
Mach4 General Discussion / Re: How to set up automatic reporting of machine run-times
« Last post by Bill_O on May 18, 2026, 12:42:10 PM »
I would like this also.
If anyone has this already or something close it would be helpful.
If not I can put it on my list of want to do and code it myself.

Bill
17
Vistacnc Control Pendants / Uncommanded rapid movement P1A-S
« Last post by Trebleplink on May 18, 2026, 11:31:14 AM »
Yesterday I installed the pendant and I like the features BUT it is dangerous to use.  I'm running Mach3 v 3.********* on Windows XP.  The plugin is 3.3.0 (I updated firmware today - Monday - same results)

2 problems:

When in step mode, as I am turning the mpg, stepping 0.001 at a time, it will reverse direction and move at full rapid speed back. I'm not sure if it is returning to where I started or not, but it is something like an inch or so. It does not seem to matter what the increment is set on. It's un-commanded movement at rapid speed. So I cannot use it.

Sometimes the mpg goes to sleep. The lcd shows the dro value OK, but the mpg does nothing, and there is no way to fix it until I restart Mach3.

Anyone seen this problem?  I'm hoping to hear back from VistaCNC soon ...

Chris Scott
Bowling Green, KY
18
Mach4 General Discussion / How to set up automatic reporting of machine run-times
« Last post by Letra-Tek on May 18, 2026, 11:29:04 AM »
Does someone know an easy way to record machine start & stop times each time it runs a file?
Is this something that I could add to a post processor, maybe a macro???
Or is it something that can be done in Mach4, maybe a plug-in???
Or is it something else???
Years ago, I always used MultiCam machines with their controller and EnRoute Pro.  It kept a running log of every file run with name, date, start/stop times, total machine run-time, whether the file finished normally or was canceled, etc.  I'm pretty sure these logs were generated by the MultiCam interface, what they called their DNC.
I would love to find out how I can get that for my current CNC router using Mach4.
Thank you in advance for any help/advice you can give me!
19
MachPro General Discussion / Re: Assign Button to Call M132
« Last post by cd_edwards on May 18, 2026, 09:55:45 AM »
and of course there's the problem that we never run the mcode script. I'm loathe to add it into the UserMCodeModule.

Also, what's the differance between these two functions? Other than the _

function UserMCodeModule.m222(hVars)
   return true, true, w.FunctionCompleted()
end

function UserMCodeModule._m225(hVars)
   return true, true, w.FunctionCompleted()
end

function UserMCodeModule.LubeSystem()
   return true, true, w.FunctionCompleted()
end
There is already a script for this. Do these cascade? one after another or would this replace LubeSystem.mcs?
20
MachPro General Discussion / Re: Assign Button to Call M132
« Last post by cd_edwards on May 18, 2026, 09:47:16 AM »
my problem was the color code. It would be nice if the color picker would specify the hex color code. Might make it easiler than doing a screen shot, putting into paint and using the color picker edit to find the hex value. :)
Pages: « 1 2 3 4 5 6 7 8 9 10 »