Recent Posts

1

Mach4 General Discussion / How to call tabPositionsExtens "On enter script" when mach 4 starts up

« Last post by TTalma on May 18, 2024, 01:04:54 PM »

I've added some buttons for my ATC to the 'tabPositionsExtens' tab (the first one shown on startup). It populates the button labels with the tool number. The script works, but when I start mach 4 the script is not called. I need to select a different tab, then go back go back to 'tabPositionsExtens' tab and everything is correct.

Is there a way to make mach 4 call the script when it starts up?

2

Mach4 General Discussion / Re: Mach 4 and 2 vfd Spindles setup

« Last post by c.r.conception@free.fr on May 18, 2024, 06:34:49 AM »

Hello DAAD, can you help with the api's please? Do you have an example? Thanks in advance

3

Mach4 General Discussion / Re: issue with m62/m63 triggering the plc script

« Last post by grsfldflyer on May 17, 2024, 10:41:53 AM »

M62 requires a small move on the next like or motion won't start. I have had problems with motion not starting with M62 even with G0 or G1 move immediatly after. I'm still investigating the cause. M64 does not need a move.

M62: Synchronized Output On
Turns on an output synchronized with the start of the next motion command. If no motion is commanded, the output will not turn on. It is best to specify motion immediately following the M62 command.

Format: M62 P_

P specifies the output number to turn on. For example: Output0 = 0, Output3 = 3, Output10 = 10, etc.

M63: Synchronized Output Off
Turns off an output synchronized with the start of the next motion command. If no motion is commanded, the output will not turn off. It is best to specify motion immediately following the M63 command.

Format: M63 P_

P specifies the output number to turn off. For example: Output0 = 0, Output3 = 3, Output10 = 10, etc.

M64: Immediate Output On
The specified output is turned on immediately. Format: M64 P_

P specifies the output number to turn on. For example: Output0 = 0, Output3 = 3, Output10 = 10, etc.

M65: Immediate Output Off
The specified output is turned off immediately. Format: M65 P_

4

Works in progress / MOVED: WaterJet

« Last post by Tweakie.CNC on May 17, 2024, 03:00:25 AM »

This topic has been moved to Promote and discuss your product.

https://www.machsupport.com/forum/index.php?topic=48623.0

5

Mach4 General Discussion / Re: mc.mcToolGetSelected not tracking tool setting(e.g. T1 M6, T2 M4, ...) !!!!

« Last post by pmageau on May 16, 2024, 12:19:00 PM »

Thanks, that fixed it !

6

Promote and discuss your product / Re: WaterJet

« Last post by smoedano on May 16, 2024, 11:03:18 AM »

Hello Birillo, the development KIT is for sale, includes PLC, Control card, MPG and a small computer windows 11, Licenses for mach3 and sheet Cam. Ready to connect in any languish. The price is 3500 USD. smoedano@moetooling.com

7

Mach4 General Discussion / Re: mc.mcToolGetSelected not tracking tool setting(e.g. T1 M6, T2 M4, ...) !!!!

« Last post by SwiftyJ on May 16, 2024, 05:07:10 AM »

That means your parameters.ini file in C:\Mach4hobby\profiles\<your profile> folder is corrupt. You can normally copy the file from another profile e.g the router or mill profile, and it will be ok

8

Mach4 General Discussion / Re: mc.mcToolGetSelected not tracking tool setting(e.g. T1 M6, T2 M4, ...) !!!!

« Last post by pmageau on May 15, 2024, 03:21:01 PM »

Thanks Swifty. I found the setting but for some reason it won't stick. When I set it, close the config dialog. Open it again, the setting is stuck on "Tool is the Next Tool". Any thoughts ?

9

Mach4 General Discussion / Re: mc.mcToolGetSelected not tracking tool setting(e.g. T1 M6, T2 M4, ...) !!!!

« Last post by SwiftyJ on May 15, 2024, 06:59:33 AM »

Go to Configure>Control and on the Tools tab make sure “T on m6 line is tool to use”

10

Mach4 General Discussion / mc.mcToolGetSelected not tracking tool setting(e.g. T1 M6, T2 M4, ...) !!!!

« Last post by pmageau on May 14, 2024, 04:24:53 PM »

I have written a M6 manual tool change macro. All the probing operations work as expected. The problem occurs when I run the M6 script more than once. I wrote a test gcode file that does this :

T1 M6
T2 M6
T3 M6
M30


On the first M6 call, the current tool is initially 99, selected tool is 1, then the current tool is set to 1(selected tool)
On the second M6 call, the current tool is initially 1 AND the selected tool is ALSO 1 !!!current tool is set again to 1!
On the third M6 call, the current tool is initially 1 AGAIN !!  and the selected tool is 2

T3 is never "selected"

Any ideas why the selected tool does not track the program T* setting ??


---------
This is the simple m6 test

function m6()
   local inst = mc.mcGetInstance();
   
    --get current state
    mc.mcCntlSetLastError(inst, "M6 Tool Change Test Started!")
      local selectedTool = mc.mcToolGetSelected(inst)
   selectedTool = math.tointeger(selectedTool)
   local currentTool = mc.mcToolGetCurrent(inst)
   currentTool = math.tointeger(currentTool)
    mc.mcCntlSetLastError(inst, "Starting Current Tool "..tostring(currentTool).." Selected Tool "..tostring(selectedTool))
 
    
   -- set current tool to new(selected) tool number
    mc.mcToolSetCurrent(inst, selectedTool)

   currentTool = mc.mcToolGetCurrent(inst)
   currentTool = math.tointeger(currentTool)
   
   mc.mcCntlSetLastError(inst, "Ending Current Tool "..tostring(currentTool).." Selected Tool "..tostring(selectedTool))
     selectedTool = 0
    mc.mcCntlSetLastError(inst, "Tool Change Test Finished\n")

end

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