Messages

1981

Mach4 General Discussion / Re: MACH4 Mcode testing

« on: May 26, 2014, 05:08:55 PM »

Steve here is another example of a SIMPLE Mcode to do a simple tap operation. It will not run from the MDI or a Gcode program call.

It will TRY to cycle the first line of code as you can SEE the TOOL CHANGE LED blink but will run the Tap cycle IF you run it from the editor. BUT same as the other example ONLY the first time you run it. After that it is a nogo until you restart Mach4.

function m111()
    inst=mc.mcGetInstance()

    mc.mcCntlGcodeExecuteWait(inst, "T111 \n M6  ");

    mc.mcCntlGcodeExecuteWait(inst, "  M3 S500 M8 \n G4P3 \n G84 Z-0.5000 R.1 G98 F10 \n M5 M9");

end

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


(;-) TP

1982

General Mach Discussion / Re: reference the machine without limit switches?

« on: May 26, 2014, 04:24:59 PM »

Plasma is EASY to recover as the cut tolerances are fairly large. Move to a point in the program you want to restart in. MOVE the machine torch tip to THAT spot on the material you have already started cutting on. Set the DROs to the same as in the Program line and restart.

There are several OTHER methods as well.

(;-) TP

1983

Mach4 General Discussion / Re: Mach 4 Feature Request

« on: May 26, 2014, 04:05:44 PM »

A short example of one of the features of Tool Life Management on a Haas.

http://atyourservice.haascnc.com/whats_new/haas-advanced-tool-management/

1984

Mach4 General Discussion / Re: Mach 4 Feature Request

« on: May 26, 2014, 03:51:59 PM »

HIYA Simpson, in the field machines normally run specific tooling for each material cut. Aluminum runs specific tooling, stainless runs specific tooling. If you abide by the Manf's specs as to chip loading the tool has a specific life at that load. The tool Life indicators ASSUME that you are running at that spec all the time you are cutting so the tool life is based on INCH of cut or can be cut time.  IF you are not running fully loaded you can rate YOUR tool life longer as experinece dictates.

It is normally a good "INDICATOR" of when to change out tools in production. COnditions can vary so can actual tool life

HAAS has a decent TLI. I think they have a manual on it as well

1985

G-Code, CAD, and CAM discussions / Re: Loading 2.5D gcode into M3, but tool path only 2D?

« on: May 26, 2014, 03:05:58 PM »

no problem , always a big help to get a fresh set of eyes to look at it.

(;-)TP

1986

Mach4 General Discussion / Re: MACH4 Mcode testing

« on: May 26, 2014, 02:56:51 PM »

OOPS, sorry here is the script I am trying to run it as a Mcode.

function m100()
    inst=mc.mcGetInstance()
local SNv = mc.mcCntlGetPoundVar(inst , 590)
local str = string.sub(SNv,1,6)
 wx.wxMessageBox(tostring(str))
local SN = {}
for i = 1, #str do
    SN = str:sub(i, i)
end


  for _,v in ipairs(SN) do
    if     v == "1" then
            mc.mcCntlGcodeExecuteWait(inst, "G0 X1.0");
    elseif v == "2" then
            mc.mcCntlGcodeExecuteWait(inst, "G0 X2.0");
    elseif v == "3" then
            mc.mcCntlGcodeExecuteWait(inst, "G0 X3.0");
    elseif v == "4" then
            mc.mcCntlGcodeExecuteWait(inst, "G0 X4.0");
    elseif v == "5" then
            mc.mcCntlGcodeExecuteWait(inst, "G0 X5.0");
    elseif v == "6" then
            mc.mcCntlGcodeExecuteWait(inst, "G0 X6.0");
    elseif v == "7" then
            mc.mcCntlGcodeExecute(inst, "G0 X7.0");
    elseif v == "8" then
            mc.mcCntlGcodeExecuteWait(inst, "G0 X8.0");
    elseif v == "9" then
            mc.mcCntlGcodeExecuteWait(inst, "G0 X9.0");
    elseif v == "0" then
            mc.mcCntlGcodeExecuteWait(inst, "G0 X0.0");

    end
  end


--SN = (SN +1)
mc.mcCntlSetPoundVar(inst , 590,(str +1))
 
end

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

1987

G-Code, CAD, and CAM discussions / Re: Loading 2.5D gcode into M3, but tool path only 2D?

« on: May 26, 2014, 12:28:54 PM »

Runs fine here 4 passes to the bottom. WHEN you say it quits does it return to the top of the program or just STOPS at the line it is on?

(;-) TP

1988

Mach4 General Discussion / Re: MACH4 Mcode testing

« on: May 26, 2014, 12:04:19 PM »

Steve IF you get a chance could you test this script . HERE it will try to run the very first time your try it after staring Mach4. It stalls out in the Gcode somewhere randomly.

after the first run it will never run again untill you restart MAch4.

What happens IS on line 3 where it is to get the #var value it stalls for about 20 seconds and return the WRONG value(Looks like it is trying to find it but cannot) it returns "0" when it should return the #var value(it does it correctly the first time it runs)

I cannot tell if it is the PC ,Mach4 or me so I would appreciate a 2nd set of eyes on this one.

Thanks (;-) TP

1989

Mach4 General Discussion / Re: Mach 4 Bug Reports

« on: May 26, 2014, 11:08:56 AM »

Single block mode needs a little attention. The turning ON works fine as to WHEN and WERE you can turn it on.

 BUT the TURN OFF you should be able to do that ANYTIME. As is it seems to follow the turnON rules.

(;-) TP

1990

Mach4 General Discussion / Re: MACH4 Mcode testing

« on: May 26, 2014, 10:45:09 AM »

Using

mc.mcCntlGcodeExecuteWait(inst, "G65 P9020 A10 B1.125");

Should help with large Mcodes with lots of Gcode lines IF it would run the G65 or M98 as a SUB.

IS there a limit to the nesting of a sub ?? Maybe that is the problem.

 I'll test some more,(;-) TP