Messages

81

Mach4 General Discussion / Re: Button script

« on: August 07, 2019, 06:15:10 PM »

If it can all be done in Gcode do it all as one string of gcode and do not use wait. It will be executed in order.

If you have to use api calls you might want to consider using a coroutine. See the ref all home button, function in screen load script and PLC of wx6.set.

I would get rid of those sleeps too. Rule of thumb is if you have to use sleep you need to rethink your code.

Maybe you can do it all in a macro (say 127). Then when you want it to run from a button the buttons clicked script looks something like this.

local inst = mc.mcGetInstance()
mc.mcCntlMdiExecute(inst, "M127")

82

Mach4 General Discussion / Re: Mach4 y coordinates are wrong when machining

« on: August 07, 2019, 11:01:18 AM »

If your steps per are not right the further you go the worse it gets out. Check you backlash and calibrate your motor tuning. These 3 links will help. They are very short and very relevant.

https://www.machsupport.com/forum/index.php?topic=12513.0

https://www.machsupport.com/forum/index.php?topic=12512.0

https://www.machsupport.com/forum/index.php?topic=16315.0

83

Mach4 General Discussion / Re: Creating M-Code to activate Outputs

« on: August 07, 2019, 01:38:40 AM »

Think you could do them all with a single macro and just set the output number using a p var. Something like M201P1, M201P2, etc. Will have to look. I know I did it before.

84

Mach4 General Discussion / Re: Programming Mach4 setup on one computer, but running it on another? Licensing.

« on: August 05, 2019, 07:02:18 AM »

Why not get and set the VFD over Modbus?

85

Mach4 General Discussion / Re: Help with first easy script or macro (which term?) for automatic oiler

« on: August 03, 2019, 06:47:49 PM »

Something like this should work. Make sure you set the right output in the script. I would have a function in the screen load script that is ran each cycle through the PLC script.

Code: [Select]

--PLC script
TogWayOil()

--Screen load script
function TogWayOil()
local hSig, rc = mc.mcSignalGetHandle(inst, mc.OSIG_OUTPUT1)
local sigState, rc = mc.mcSignalGetState(hSig)
local vX, rc = mc.mcAxisGetVel(inst, mc.X_AXIS)
local vY, rc = mc.mcAxisGetVel(inst, mc.Y_AXIS)
local xyVel = math.sqrt((vX * vX) + (vY * vY))

if (sigState == 0) and (xyVel > 0) then --turn the output on
rc = mc.mcSignalSetState(hSig, 1)
elseif  (sigState ~= 0) and (xyVel == 0) then --turn the output off
rc = mc.mcSignalSetState(hSig, 0)
end
end

86

Mach4 General Discussion / Re: How to make the Mist Coolant button & M07 M09 actually turn on an output?

« on: August 03, 2019, 06:29:53 PM »

OK, yeah let's talk about that other thread in that other thread. I will clean this one up.

87

Mach4 General Discussion / Re: How to turn off an output when the machine is Not Enabled (Disabled)?

« on: August 03, 2019, 06:22:37 PM »

Do I even need those inst = mc.mcGetInstance() in there since at the begging of the screen load script it says this already.

Nope. As long as the inst variable is within the scope of the script you are working with and is already properly defined there is no reason to redefine it or create a local copy of it.

But, if there is ever a chance the script may be called for different instances of Mach4 you should write the script with provisions to define the inst from whatever is calling it.

88

Mach4 General Discussion / Re: How to make the Mist Coolant button & M07 M09 actually turn on an output?

« on: August 03, 2019, 06:01:32 PM »

Do I need to modify the start screen code and the sig library and create M code scripts to just make a button that already exists and has predefined M Code action work?

For example I just want to make the Mist button work and give it an output to turn on. Where do I do this? Is there a tutorial for this exact thing where you just want to make an existing button and Mcode work?

 I can make a new button that does this and I could make a new M code script that does this, but I would think they intend for you to use the built in action for this? mc.OSIG_MISTON? I will keep reading and reading and reading to figure it out, but hopefully someone can just give a quick link with a good simple to understand way of how it should be done for best performance.

Thanks. I looked for a couple hours so far and have not figured it out yet. Too tired from a long day I guess. I am reading through a bunch of information, but there is just so much to look at and no straight to the point of the best way and the exact code and where to put it etc. The only variable from what pretty much everyone is doing for this simple task is which output they are using. In my mnd this simple thing should not require a programmer to get working...

Not sure what the problem is. The mist toggle button toggles the state of the mist output (as it should) in the default screens. Even has an LED beside it to indicate its status. Executing a M07 and M09 turns the mist on and off as well. Not sure how much simpler it could be. There is even a dedicated output labeled "Mist On" (the only way you can control any output is to know what output your controlling). You aren't trying to control your mist with a general purpose output are you?

89

Mach4 General Discussion / Re: Coroutine or executewait

« on: August 02, 2019, 06:03:17 PM »

It all depends on what your doing. If it can be done with mc.mcCntlGcodeExecuteWait() then no reason not to use it. Technically I guess it would be the safest. But using a coroutine is perfectly fine too as long as it is implemented correctly.

90

Mach4 General Discussion / Re: mach 4 plasma

« on: August 02, 2019, 12:44:39 PM »

Have a look in your C:\Mach4Hobby\Docs folder, Plasma_Configuration.pdf. That is covered on page 2 and 3.