Messages

291

Mach4 General Discussion / Re: pay for help

« on: March 06, 2019, 05:00:56 PM »

Very cool machine!
So you're looking for Mach4 to move the metal through the machine, bend the material, and notch the material?
From what I can tell, you would have Mach4 do the following:
Move ### Units (inches/mm) --> Notch1 -->  Move ### --> Bend1 XDegrees --> Move ### --> Notch2... Move ### --> Notch1 --> Move### Bend2  --> etc..
Series of Notching and bending whether it be Notcher 1, 2, 3, etc... Bend Position 1, 2, 3, etc so many degrees.

What are you thinking as far as getting the information to Mach4 to move?
Do you have separate software that generates notched positions and bend positions?

292

Mach4 General Discussion / Re: macro problem

« on: March 06, 2019, 12:18:33 PM »

Craig, I agree with you, I would much prefer having the logic in the button script as well.  May be a little redundant on the work, but it makes it bulletproof.

293

Mach4 General Discussion / Re: macro problem

« on: March 06, 2019, 11:39:36 AM »

Running the m22 macro, I am able to debug it and run it on MDI.
I'm not sure what issue you are having with the Macro, it runs fine for me.

The button press however, instead of using GCodeExecuteWait, use MdiExecute
Also, for best practice, keep the "m" lower case, you had it upper case. 
--New button script.
local inst = mc.mcGetInstance()
local N2Ac = "m22"
--mc.mcCntlGcodeExecuteWait(inst, N2Ac)
mc.mcCntlMdiExecute(inst, N2Ac)

294

Mach4 General Discussion / Re: touch probeing

« on: March 01, 2019, 09:45:07 AM »

Its an air nozzle.  You can hook up an airline to blast the chips off of the top of the tool setter.  Pretty cool idea really, just hook up a solenoid to it.

295

Mach4 General Discussion / Re: touch probeing

« on: March 01, 2019, 12:17:04 AM »

These are pretty good.
eBay item:  143067989514

296

Mach4 General Discussion / Re: Mach 4 and fusion 360

« on: February 18, 2019, 05:30:33 PM »

I'm with TommyG, I use Fusion 360 with Mach4 all the time.  I would check the post processor like he has suggested.

297

Mach4 General Discussion / Re: Mach4 M8 and M62 is not disabled when program is stopped

« on: February 17, 2019, 11:51:14 AM »

You can put it in the Signal Library in the screen load script.

[mc.ISIG_EMERGENCY] = function(state)
    if (state == 1) then
       local inst = mc.mcGetInstance()
       local Output1 = mc.mcSignalGetHandle(inst, mc.OSIG_OUTPUT1)
       mc.mcSignalSetState(Output1, 0)
    end
end,
 
The same with disable, there is an Machine Enabled signal you can use.  Just check for the state to be 0 instead of 1.

298

Mach4 General Discussion / Re: Mach4 M8 and M62 is not disabled when program is stopped

« on: February 17, 2019, 10:51:51 AM »

jorgenbli,
If you want outputs to turn off with E Stop, Cycle Stop, Feedhold, or Reset, you have to add that functionality to the buttons/functions in the screen editor.   
I have several outputs that I want to turn off with Reset, E Stop, and Cycle Stop, so I have no issues with adding those to the screen script.
Everyone has different ideas of how machines are "supposed" to operate, the joy of Mach4 is that you can make it operate just the way you want it to.

299

Mach4 General Discussion / Re: Mach4 LED's

« on: February 06, 2019, 09:19:23 AM »

Glad you got it working! =)

300

Mach4 General Discussion / Re: LUA, repeat until

« on: February 05, 2019, 08:18:59 AM »

If you need it to wait for the axis to get to position before continuing with your script, you may as well turn that motor into A, B, or C axis.   The point of the OB axis is to be moved independently of the normal axis. 

If you do, however, use the OB axis outside of synced movement, then I'm not sure what the solution would be.   Maybe check the OB position requested position with the current position and use a wx. Millisleep until it reaches that point.   
while CurrentPosition~= RequestedPosition do
Wx. Millislepp (100)
end

I wonder if that would work?