Messages

151

Mach4 General Discussion / Re: Setting to millimeters

« on: December 28, 2017, 03:57:25 PM »

It would be nice if an event (e.g. a Signal) was raised when this happens so that scripts could react accordingly if required.

Allan

152

Mach4 General Discussion / Re: Setting to millimeters

« on: December 28, 2017, 11:06:10 AM »

I also find that going to Mach configuration causes the jog units, type, and distance to be reset. The safest practice seems to be to restart Mach4 after configuration changes.

Allan

153

Mach4 General Discussion / Re: Toolpath Regen

« on: December 27, 2017, 11:43:22 AM »

Went out to the garage and re-tested with 3481 and CS Labs. Again everything worked without issue, so sorry I am unable to reproduce your issue.

Allan

154

Mach4 General Discussion / Re: Setting to millimeters

« on: December 27, 2017, 10:22:02 AM »

Another funny thing.  My setup units are all metric, which is all I ordinarily use.

If I home the machine, and assuming G54 offset is zero, the work coordinates DROs read 0. If I issue a G20 MDI command, then jog X 1 unit, then issue G21, the X DRO reads 25.4 afterwards. If, however, I First switch the display to machine coordinates and then follow the above sequence, the DRO reads 1 afterwards. This doesn’t make sense to me. I can understand that Mach4 may, by design, change the jog units to imperial when the current units are so changed by a G20 command, but why would this depend on which coordinates are on display?
Above with 3485 and SIM. Sounds like another bug to me.

Allan

155

Mach4 General Discussion / Re: Toolpath Regen

« on: December 27, 2017, 07:51:26 AM »

Not exactly earlier as you request, but I have no such issue with version 3485. I can open files freely, whether or not the program is run in between. I do not need to close one file before opening another.

This is on my office machine using SIM.

Allan

156

Mach4 General Discussion / Re: Setting to millimeters

« on: December 23, 2017, 09:52:06 AM »

Another user has suggested that this is a bug in version 3481, and that a resolution is to revert to version 3390. I have not tested this, but have seen intermittent cases of my mill jogging 25.4mm when 1mm was expected, USING 3481. Scarey.

Another thing that you might try if you are into LUA is to execute the following to explicitly set the jog units prior to jogging:

    local inst = mc.mcGetInstance()
    local rc = mc.mcJogSetUnitsMode(inst, mc.X_AXIS, 21)

(Repeat line 2 for all axes.)  You might try placing such code in the jog tab On Enter script and open this tab prior to jogging.

In case it has a bearing, which controller do you use? Mine is CS Labs.

Allan

157

Mach4 General Discussion / Re: HELP!: Mach4 3481 jogs in inches when "set"(?) to mm

« on: December 12, 2017, 05:00:29 AM »

Excellent work. I will go back to 3390 and see if that fixes the issue. As it is intermittent, it's impossible to guarantee that it will never happen, so it's just a matter of building confidence over time..

I have seen similar effects with 3481 to those you describe if I have metric setup units but issue a G20 command.

Allan

158

Mach4 General Discussion / Re: HELP!: Mach4 3481 jogs in inches when "set"(?) to mm

« on: December 11, 2017, 04:47:05 AM »

I too have seen this with 3481, though in my case it happens intermittently. I can confirm that both config settings are at metric, and I have also checked that both default units and current units are metric immediately prior to the API call for jogging.

This is a serious error and I have no idea whether Mach4 or the plugin (CSMIO-IP/A in my case) is responsible.

Allan

159

Mach4 General Discussion / Re: Creating your own homing script

« on: December 04, 2017, 07:04:27 AM »

Here is a button script I use to home the Z axis. You should be able to adapt this to suit your needs:

--Move Z axis to home position
local inst = mc.mcGetInstance()
-- Check  homed indicator
local hSig = mc.mcSignalGetHandle(inst, mc.OSIG_HOMED_Z)
local zHomed = mc.mcSignalGetState(hSig)
if (zHomed == 1) then
    mc.mcCntlMdiExecute(inst, "G00 G90 G53 Z0")
else
    local rc = mc.mcAxisHome(inst, mc.Z_AXIS)
    if (rc == mc.MERROR_NOERROR) then
        -- Set homed indicator
        local rc = mc.mcSignalSetState(hSig, 1)
    end
end

Allan

160

Mach4 General Discussion / Re: How do I get to the center of 2 edges?

« on: October 10, 2017, 06:18:51 AM »

If you want to try my ready made solution, here is an export of my Offsets tab.  After backing up your current screen set, import the revised tab into the screen tree. As i have also modified the 6 offset buttons, which in some circumstances might not have indicated the current offset, you will also need to add the function ShowFixedOffset() to the screen load script.

Allan