Messages

191

Mach4 General Discussion / Re: pay for help

« on: March 06, 2019, 10:49:25 PM »

Yup, it's just I/O and motion.

1) Figure out what needs to happen.
2) Figure out how the user interacts with.
3) Marry those 2 things.

192

Mach4 General Discussion / Re: pay for help

« on: March 06, 2019, 07:05:23 PM »

I don't see any reason Mach4 can't do it. It will take a bit of work which == time but certainly doable unless I'm missing something.

193

Mach4 General Discussion / Re: Lathe Turn Cycle with Threading (Prog hangs at end)

« on: March 03, 2019, 05:56:20 PM »

ini file types should be allowed now.

194

Mach4 General Discussion / Re: write to a register

« on: February 28, 2019, 04:36:55 PM »

No problem.

195

Mach4 General Discussion / Re: write to a register

« on: February 28, 2019, 08:44:03 AM »

which for safety sake:
local mc.mcRegSetValue(hreg,asnumber(EncScale'))

Did you mean

local mc.mcRegSetValue(hreg,tonumber(EncScale))

?

196

Mach4 General Discussion / Re: Mach4 Output Config. gets lost with shutdown

« on: February 26, 2019, 02:19:42 AM »

You don't have a failing cmos battery in your PC allowing the system time to get off do you?

197

Mach4 General Discussion / Re: Is it possible to call an M code from a different M code?

« on: February 19, 2019, 11:30:46 AM »

Code: [Select]

The M1000 function is in a different file.
This is true but all macros get compiled into the single mcLua.mcc file (chunk). So functions in one macro are available to other macros unless they are made local within the macro they are created in. So MN300's suggestion is spot on. Use m1000() in other macros. Call the m1000 as gcode from buttons.

Another way you could do it is to put your depth setting function in a module and call it from various macros, screen buttons, etc. but the above solution is simpler.

198

Mach4 General Discussion / Re: LUA, repeat until

« on: February 05, 2019, 08:15:44 AM »

Once you send the jog command loop until you get motion. Right after that loop until motion stops. In each of the loops use a var to increment during the loop and set it to something reasonable so that you can exit the loops if the counter reaches some value.

Code: [Select]

local atcAxis = mc.AXIS6
local loopCount = 0
local loops = 200000

repeat --Until we start moving or time out
loopCount = (loopCount +1)
local ob1info = mc.mcAxisGetInfoStruct(inst, atcAxis)
local OB1Jogging = ob1info.Jogging
until --Jogging starts or we time out
(OB1Jogging == 1) or (loopCount >= loops)

if (loopCount >= loops) then
m6ErrorOut("Carousel took too long to start moving")
return
end

loopCount = 0

repeat --Until we stop moving or time out
loopCount = (loopCount +1)
local ob1info = mc.mcAxisGetInfoStruct(inst, atcAxis)
local OB1Jogging = ob1info.Jogging
until --Jogging stops or we time out
(OB1Jogging == 0) or (loopCount >= loops)

if (loopCount >= loops) then
m6ErrorOut("Carousel took too long to get into position")
return
end

199

Mach4 General Discussion / Re: Keep track of OB axis

« on: February 01, 2019, 09:07:42 AM »

Pieces are falling into place.
About setting Pod var, is this somehow going into a register or will Mach remember this var when promting it during next tool change?
Would it possible to set pod var to 1, during the home/reference action so that the variable always have a number during the first tool change?

Well, lots of ways it could be done. You could just create a register and write to it when you move and read it to determine how far to move. Or, one of the slicker ways to do it would be to have the plc script monitor the position of the OB axis. For every so many steps in this direction add one to the current pod #, for every so many steps in the other direction subtract one pod from the current pod #. In between positions it could read pod 0 or "No Pod". This way if say an estop was activated while the pods are rotating you still know where it is or you know you need to reference it to continue. Endless ways to make it work. Even more ways to make it work very well.

It's a logic puzzle. Enjoy solving it. Map out every single step and all the possible ways to do each, what could go wrong during that step to make it fail and what happens if it does fail. Do you throw an estop and pop up a message box? Does it just automagicly reference and start over from there. Endless possibilities. It makes you think but that is the fun part.   

200

*****VIDEOS***** / Re: Open Build CNC machine

« on: February 01, 2019, 01:29:43 AM »

Welcome to the forum.

I like. 

I'm interested in seeing how you get on and what you make.

Are you using Mach3 or Mach4 to control the router?