Topics

1

General Mach Discussion / G17

« on: February 13, 2019, 01:23:24 AM »

Is it ok for mach3 to have a G17 on a line by itself as it is at the end of the Gcode below?

Code: [Select]

(1001)
(SPOONS X 2 ORIGIN ON FROUNT SET)
(POST PROG )
(GENERATED ON WEDNESDAY, FEBRUARY 13, 2019 192159)
(T3  D=12.7 CR=0. - ZMIN=0. - FLAT END MILL)
G90 G94 G91.1 G40 G49 G17
G21
G28 G91 Z0.
G90

(FACE1)
M5
M9
T3 M6
S18000 M3
G54
G0 X375. Y-38.857
G43 Z11. H3
Z6.
G1 Z1.27 F700.
G18 G3 X373.73 Z0. I-1.27 K0.
G1 X366.75
X126.75 F1250.
X119.75
X-120.25
X-127.25
X-367.25
G17 G2 Y-27.968 I0. J5.444
G1 X-127.25
X-120.25
X119.75
X126.75
X366.75
G3 Y-17.08 I0. J5.444
G1 X126.75
X119.75
X-120.25
X-127.25
X-367.25
G2 Y-6.191 I0. J5.444
G1 X-360.063
X-127.25
G3 Y4.697 I0. J5.444
G1 X-131.796
X-366.733
X-366.75
G2 Y15.586 I0. J5.444
G1 X-126.872
G18 G2 X-125.602 Z1.27 I0. K1.27 F900.
G0 Z6.
X-117.266 Y-6.191
G1 Z1.27 F700.
G2 X-115.996 Z0. I1.27 K0.
G1 X-113.063
X119.75 F1250.
G17 G3 Y4.697 I0. J5.444
G1 X115.204
X-119.733
X-119.75
G2 Y15.586 I0. J5.444
G1 X120.128
G18 G2 X121.398 Z1.27 I0. K1.27 F900.
G0 Z6.
X129.734 Y-6.191
G1 Z1.27 F700.
G2 X131.004 Z0. I1.27 K0.
G1 X133.937
X366.75 F1250.
G17 G3 Y4.697 I0. J5.444
G1 X362.204
X127.267
X127.25
G2 Y15.586 I0. J5.444
G1 X367.128
X367.25
G3 Y26.474 I0. J5.444
G1 X127.25
X120.25
X-119.75
X-126.75
X-366.75
G2 Y37.363 I0. J5.444
G1 X-126.75
X-119.75
X120.25
X127.25
X367.25
G18 G2 X368.52 Z1.27 I0. K1.27 F900.
G0 Z11.
G17

G28 G91 Z0.
G90
G28 G91 X0. Y0.
G90
M30

2

General Mach Discussion / 4th axis continuous movment

« on: November 05, 2017, 01:14:17 AM »

Does anyone know of a way to get the A axis to just spin at a set speed and be controlled from Mach3 for on and off and setting the speed. I know just connecting it up to a stepper driver with a arduino it can be done, It's for a non technical person on the other side of the planet from me.

He wants to knock 30 mins of a tool path. doing a traces op in fusion 360 along the X then stepping in closer in the Y axis it will work, if I can get a simple way to get the A axis to just spin.

3

General Mach Discussion / Pokeys 57cnc pwm setup

« on: December 08, 2016, 06:05:28 PM »

I need a bit of help with setting up the pwm on the 57cnc.
I have it sort of working I can turn the spindle on and off but have no control over the speed putting in a M3 S what ever will just turn it on

I am useing a super pid

the pwm is on pwm 2 pin 20 the on and off is with oc1 as output 1.

I have spent 2 days trying to work out what to do but cant find anything saying do this or that I have read all the manuals.

Mach3 profile attached

4

Mach4 General Discussion / Mach4 CV

« on: June 13, 2016, 01:58:37 AM »

is the CV working in the latest version of M4 and how do you go about setting the CV wizard.

I like the router screen could we get a 4 axis version Please

5

General Mach Discussion / pokeys and G540

« on: February 20, 2016, 03:29:32 AM »

has anyone got a G540 working with a Pokeys 57CNC v1.2 and a superpid I am having a hell of a time getting the 57CNC to control the superpid

6

General Mach Discussion / fusion 360 wrapping fuction

« on: December 05, 2015, 09:13:32 PM »

here are a couple of vid on doing 4th axis wrapping with fusion 360
 part2 https://www.youtube.com/watch?v=kL65HSxBquI
part 1 https://www.youtube.com/watch?v=y7NtJKP8YJQ

the post processor and parameters are here. https://drive.google.com/folderview?id=0B1KN_0ll_6soUUV6bmRFcWJYMVU&usp=sharing

part one is a bit buggy it will be redone when the bug is fixed

7

General Mach Discussion / fusion 360 wrapping function

« on: November 20, 2015, 04:01:17 AM »

Here is a new tool for everyone (Mach3 so far) this was done by @HughesTooling He did the post processor changes and the .f3d file I just asked for it, all credit for this goes to Mark he the Man with the getup and go to do this.
 
attached is the post processor and demo file is here http://a360.co/217rTWk this is for wrapping Y axis to A this post processor can be used to convert X or Y axis to A you just need to make sure radius correction is set to half diameter in the file the diameter is 50 so the correction is 25, and make sure the axis of rotation is set in tool paths under config in Mach3.
 
I have not tested this on a machine yet also your X, Y, Z and A axis zero's have to be set first before running it there are some small changes still to be done it will be reposted when done but it works and is useable.
 
any question ask here.

8

Mach4 General Discussion / tool height probing

« on: June 29, 2015, 07:03:06 PM »

can some one test the attached code I am not sure if it`s working properly it look`s to be working but keeps come up with no probe signal found.

I am run M4 with no license on a ESS

this is the code use from the zip not here

Code: [Select]

-----------------------------------------------------------------------------
-- Auto Tool Setting Macro
-----------------------------------------------------------------------------
--[[
 Requires the following instance registers to be defined
 TS_XPos-----------X position of probe (machine position)
 TS_YPos-----------Y position of probe (machine position)
 TS_Type-----------Offset type (1 or 2)
 TS_TouchPos-------Z position of touch off surface (machine position)
 TS_ProbeH---------Height of probe above touch off surface
 TS_DefaultL-------Default tool length guess
 TS_Retract--------Retract distance after probe touch
 Offset Type 1-----Length of tool from gauge line to tip
 Offset Type 2-----Distance from tip of tool to the touch position
]]
--The function GetRegister() must be defined for use by macros


 function m1005()
 local inst = mc.mcGetInstance()

function GetRegister(regname)
      local rc;
      local inst = mc.mcGetInstance();
      local hreg = mc.mcRegGetHandle(inst, string.format("iRegs0/%s", regname));
      return mc.mcRegGetValueString(hreg);
   end

 ------------- Define Vars -------------
 local ProbeSignal = mc.ISIG_DIGITIZE
 ------------- Get current state -------------
 local CurTool = mc.mcToolGetCurrent(inst)
 local CurHNum = mc.mcCntlGetPoundVar(inst, 2032)
 local CurFeed = mc.mcCntlGetPoundVar(inst, 2134)
 local CurZOffset = mc.mcCntlGetPoundVar(inst, 4102)
 local CurFeedMode = mc.mcCntlGetPoundVar(inst, 4001)
 local CurAbsMode = mc.mcCntlGetPoundVar(inst, 4003)
 ------------- Get touch off parameters -------------

 local XPos = GetRegister("TS_XPos", 1)
 local YPos = GetRegister("TS_YPos", 1)
 local OffsetType = GetRegister("TS_Type", 1)
 local TouchPos = GetRegister("TS_TouchPos", 1)
 local ProbeHeight = GetRegister("TS_ProbeH", 1)
 local RetractDistance = GetRegister("TS_Retract", 1)
 local ToolLengthGuess = GetRegister("TS_DefaultL", 1)
 ------------- Check Probe -------------
 local hsig = mc.mcSignalGetHandle(1,inst, ProbeSignal,mc.ISIG_INPUT11)
 local ProbeState = mc.mcSignalGetState(hsig)
 if (ProbeState == true) then
 mc.mcCntlSetLastError(inst, "ERROR: Probe signal is activated")
 do return end
 end

 ------------- Calculations for Gcode -------------
 local StartHeight = TouchPos + ProbeHeight + ToolLengthGuess + .5

 ------------- Generate GCode -------------
 AutoToolSetGCode = ""
 AutoToolSetGCode = AutoToolSetGCode .. "G00 G80 G40 G49 G90\n"
 AutoToolSetGCode = AutoToolSetGCode .. "G00 G53 Z0.0\n"
 AutoToolSetGCode = AutoToolSetGCode .. string.format("G00 G53 X%.4f Y%.4f\n", XPos, YPos)
 AutoToolSetGCode = AutoToolSetGCode .. string.format("G00 G53 Z%.4f\n", StartHeight)
 AutoToolSetGCode = AutoToolSetGCode .. "G91 G31 Z-2.0 F25.\n"

 mc.mcCntlGcodeExecuteWait(inst, AutoToolSetGCode)
 --Check probe contact
 ProbeState = mc.mcSignalGetState(hsig)
 if (ProbeState ~= 1) then
 mc.mcCntlSetLastError(inst, "ERROR: No contact with probe")
 mc.mcCntlGcodeExecuteWait(inst, "G0 G90 G53 Z0.0\n")
 do return end
 end

 AutoToolSetGCode = ""
 AutoToolSetGCode = AutoToolSetGCode .. string.format("G91 G00 Z%.4f\n", RetractDistance)
 AutoToolSetGCode = AutoToolSetGCode .. "G91 G31 Z-1.0 F10.\n"

 mc.mcCntlGcodeExecuteWait(inst, AutoToolSetGCode)
 --Check probe contact
 ProbeState = mc.mcSignalGetState(hsig)
 if (ProbeState ~= 1) then
 mc.mcCntlSetLastError(inst, "ERROR: No contact with probe")
 mc.mcCntlGcodeExecuteWait(inst, "G0 G90 G53 Z0.0\n")
 do return end
 end

 AutoToolSetGCode = ""
 AutoToolSetGCode = AutoToolSetGCode .. "G90 G00 G53 Z0.0\n"
 mc.mcCntlGcodeExecuteWait(inst, AutoToolSetGCode)
 ------------- Get touch position and set offset -------------
 local ZProbed = mc.mcCntlGetPoundVar(inst, 5063)
 local ZOffset = ZProbed - ProbeHeight + CurZOffset
 if (OffsetType == 1) then
 ZOffset = math.abs(TouchPos - ZOffset)
 end

 mc.mcToolSetData(inst, mc.MTOOL_MILL_HEIGHT, CurTool, ZOffset)
 mc.mcCntlSetLastError(inst, string.format("Auto tool setting complete, Offset = %.4f",
ZOffset))
 
 ------------- Set previous state -------------
 mc.mcCntlSetPoundVar(inst, 2134, CurFeed)
 mc.mcCntlSetPoundVar(inst, 4001, CurFeedMode)
 mc.mcCntlSetPoundVar(inst, 4003, CurAbsMode)

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

9

Mach4 General Discussion / need a little bit of help

« on: May 31, 2015, 04:04:40 AM »

I am trying to get my code for Laser Zero working properly I have it so it turn the output on/off (will have a Laser on button that's easy) then move to require position.

then what I would like is for it to zero out the axis`s it does not do it in the correct order it zero`s the axis first before the required move.

I am using

mc.mcAxisSetPos(inst, 0, 0.000)
mc.mcAxisSetPos(inst, 1, 0.000)

to zero the axis`s

this is the code
--Laser Zero

local inst = mc.mcGetInstance();  --Get the instance of the controller
local out5= mc.mcSignalGetHandle(inst, mc.OSIG_OUTPUT5);  --Get the out5 handle
local outstate = mc.mcSignalGetState(out5); --Output TOGGLE
   if (outstate == 1) then
       mc.mcSignalSetState(out5, false);
     else
       mc.mcSignalSetState(out5, true);
    end

local inst = 0;
local rc = 0;
local Xmove = "X2";
local Ymove = "Y3";
    rc = mc.mcCntlGcodeExecute(inst, "G91 G0 \n" .. Xmove .. " G91 G0 \n" .. Ymove);

    mc.mcAxisSetPos(inst, 0, 0.000)
    mc.mcAxisSetPos(inst, 1, 0.000)

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

can some one point me to what I should use or what am I doing wrong

thank

pain in the a

10

Mach4 General Discussion / Lua Signal Table

« on: May 18, 2015, 02:55:20 AM »

I have run into a problem with signal tables from the scripting manual in it it has the sig table like this

SignalTable = { -------sig table number goes here I think without {
     [mc.ISIG_INPUT0] = function (on_off)
        if (on_off == 1) then
            mc.mcCntlCycleStart(inst)
        end
    end

I keep get a error this

Compilation error on line number: 54
Lua: Syntax error during pre-compilation
[string "C:\Users\Daniel\AppData\Local\Temp\le6115.mcc..."]:54: unexpected symbol near '['



I have searched but cant find anything to help I used this and it work`s

if (sig == mc.ISIG_INPUT1) and (state == 1) then
local inst = mc.mcGetInstance()
mc.mcCntlCycleStart(inst)
end