Messages

1

Mach4 General Discussion / Re: Can someone explain how M43 is supposed to work

« on: March 15, 2022, 11:36:31 AM »

And, I don't think the G43 line matters what order the G43, the H3, or a Z move are in.
[/quote]

Whilst I agree in principle with this statement, I find that if there is a problem, then it's best to follow the format shown in the systems manual, to remove one possible problem source.

As you correctly point out, because the code calls for a drill depth of Z0, it does appear that the OP's tool lengths are incorrect.

2

Mach4 General Discussion / Re: Enforce Ref-All-Home

« on: March 14, 2022, 04:30:55 PM »

This is the script for Auto Soft Limits from here:- https://www.youtube.com/watch?v=IXuuGRACU1I
I can't confirm if it works or not, but worth a try.

Hopefully one of the Mach team will be along to help you with the Ref All .

New script to turn on soft limits after homing:

---------------------------------------------------------------
-- Ref All Home() function.
---------------------------------------------------------------
function RefAllHome()
    mc.mcAxisDerefAll(inst)  --Just to turn off all ref leds
    mc.mcAxisHomeAll(inst)
    coroutine.yield() --yield coroutine so we can do the following after motion stops
    ----See ref all home button and plc script for coroutine.create and coroutine.resume
    wx.wxMessageBox('Referencing is complete.\nSoft Limits Set.')
    SetSoftlimits()
end

-------------------------------------------------------
--  Set Soft Limits
-------------------------------------------------------
function SetSoftlimits()
    for v = 0, 5, 1 do --start, end, increment
        mc.mcSoftLimitSetState(inst, v, mc.MC_ON)
       
    end
    scr.SetProperty("tbtnSoftLimits", "Button State", tostring(1))
    scr.SetProperty("tbSoftLimits", "Button State", tostring(1))
   
end

3

Mach4 General Discussion / Re: Can someone explain how M43 is supposed to work

« on: March 14, 2022, 07:29:38 AM »

Just had a quick read of the manual and if you want to retain the Z move, then add it after the H value,  G43 H3 Z1.3783

4

Mach4 General Discussion / Re: Can someone explain how M43 is supposed to work

« on: March 14, 2022, 06:55:19 AM »

Try removing the Z value after G43.
This is part of some code I've used on my machine without any problems

(Andys Mincer Plate.tap)
N5 G90 G20 G54 G28 G40 G80
(Setup 1)
(Work Zero)
(Spot Drill 2mm Cutouts)
N10 M09
N15 M05
N20 G53 G00 Z-0.1250 (Tool Change Position)
N25 G54
N30 T01 M06 (6mm Spot Drill)
N35 G43 H01
N40 S5000 M03
N45 G00 X-0.1181 Y1.0465
N50 G00 Z0.0400
N55 G81 X-0.1181 Y1.0465 Z-0.0150 R0.0400 F4.
N60 X0.1181 Y1.0465
N65 X0.1181 Y-1.0465
N70 X-0.1181 Y-1.0465
N75 G80
N80 G00 Z0.0400
(Spot Drill 1.5mm Holes)
N85  X-0.6264 Y0.6264
N90 G00 Z0.0400
N95 G81 X-0.6264 Y0.6264 Z-0.0150 R0.0400 F4.
N100 X-0.4921 Y0.7365
N105 X-0.3390 Y0.8184
N110 X-0.1728 Y0.8688
N115 X0.0000 Y0.8858
N120 X0.1729 Y0.8688

5

Mach4 General Discussion / Re: Incremental Jogging Issue

« on: March 08, 2022, 07:13:36 PM »

This is a long standing bug within Mach4 (see the attached screen shot)

6

Mach4 General Discussion / Re: Hazardous Motion - Mach4 Software

« on: July 16, 2021, 06:25:17 PM »

I use a couple of machines at work, that have Centroid controls and with them, if you either spin the MPG hand wheel  or press the INC Jog button too fast, the control just ignores the extra pulses, until the input rate is slowed down. With this, you don't get the continuing movement after you've stopped spinning the hand wheel, whilst all the buffered pulses are used up.

Although I use Mach4 at home , the Centroid handling of MPG and INC inputs, always struck me as to be the most sensible and safest way.

I went with Mach4, well before Centroid Acorn was introduced, otherwise I would also be using Centroid at home.

Nick.

7

Mach4 General Discussion / Re: Ignore Tool Changes setting?

« on: July 16, 2021, 06:01:15 PM »

I had exactly the same problem as you regarding your other posting.
With me it was caused by having the "Wait On Spindle To Stabilize "xx " Percent" Box checked (Under Mach4 Spindle Configuration Tab).
At the time, I didn't have any Spindle feedback to Mach via the ESS, so Mach just sat there waiting for a signal that was never going to appear.

Regards,
Nick.

8

Mach4 General Discussion / Re: Hybrid Stepper Motor Driver Alarm Line Handling

« on: June 29, 2021, 05:24:26 PM »

This is the script I use for my mill. The ESS Inputs will probably not be the same as yours, but it should give you a starting point (The ToolChangeMsg and Keyboard Inputs Toggle at the start and end , are only there to show where I slotted the alarm script into the screen load script):-

            mm.ToolChangeMsg("A tool change has been requested via M6. Change your tool then press Cycle Start to continue!", "Tool Change Active!")
        end
    end
end,

-----------------------------------------------------------
--- Axis Drive Fault Alarm
----------------------------------------------------------
[mc.ISIG_INPUT30] = function (state)
        DriveAlarm()
    end,
    [mc.ISIG_INPUT31] = function (state)
        DriveAlarm()
    end,
    [mc.ISIG_INPUT32] = function (state)
        DriveAlarm()
    end,
    [mc.ISIG_INPUT33] = function (state)
        DriveAlarm()
    end
}


--------------------------------------------------------------
-- Axis Drive Alarm Function
---------------------------------------------------------------
function DriveAlarm()
    local hSig, rc = mc.mcSignalGetHandle(inst, mc.ISIG_INPUT30) -- Is mapped to Port 3 Pin 10 -- X Axis Drive
    local XDriveAlarm, rc = mc.mcSignalGetState(hSig)
    local hSig, rc = mc.mcSignalGetHandle(inst, mc.ISIG_INPUT31) -- Is mapped to Port 3 Pin 11 -- Y Axis Drive
    local YDriveAlarm, rc = mc.mcSignalGetState(hSig)
    local hSig, rc = mc.mcSignalGetHandle(inst, mc.ISIG_INPUT32) -- Is mapped to Port 3 Pin 12 -- Z Axis Drive
    local ZDriveAlarm, rc = mc.mcSignalGetState(hSig)
    local hSig, rc = mc.mcSignalGetHandle(inst, mc.ISIG_INPUT33) -- Is mapped to Port 3 Pin 13 -- 4th Axis Drive
    local ADriveAlarm, rc = mc.mcSignalGetState(hSig)

    if XDriveAlarm == 1 then
        mc.mcCntlEStop(inst)
   wx.wxMessageBox ("X Axis Drive Fault")
    elseif YDriveAlarm == 1 then
        mc.mcCntlEStop(inst)
   wx.wxMessageBox ("Y Axis Drive Fault")
    elseif ZDriveAlarm == 1 then
        mc.mcCntlEStop(inst)
   wx.wxMessageBox ("Z Axis Drive Fault")
    elseif ADriveAlarm == 1 then
        mc.mcCntlEStop(inst)
   wx.wxMessageBox ("4th Axis Drive Fault")
    end
end
---------------------------------------------------------------
-- Keyboard Inputs Toggle() function. Updated 5-16-16
---------------------------------------------------------------

Hope this helps,
Nick.

9

Mach4 General Discussion / Re: Mach4 not running canned cycles or 3d milling operations

« on: May 23, 2021, 10:39:17 AM »

Don't know why there's a problem with your setup, but Mach4 does seem to be quite Flaky recently, in some instances.

There's a useful tip in the last post of this thread if you want to try making a new profile from scratch, or even trying another install of Mach4 :- https://www.machsupport.com/forum/index.php?topic=44501.msg285501#msg285501

10

Mach4 General Discussion / Re: Mach4 not running canned cycles or 3d milling operations

« on: May 23, 2021, 10:02:10 AM »

Loaded without any problems for me.

Edit:- Tried it in both Metric and Inch machine configurations just in case.