Messages

11

Mach4 General Discussion / Re: Help me troubleshoot the Cycle Timer

« on: November 05, 2019, 09:49:57 AM »

This is a perfect example of why you need to always keep the default screen. Also, I would highly recommend when you start with Mach4 copy the profile and screen you plan to start your actual profile with and save each of them as something custom, screen and profile. I usually make the names match for both screen and profile. This way later on you have a exact copy of what you began with if you need to undo something, use for reference, start over, etc.

The cycle timer uses 2 bits of script. One in the screens PLC script and the other is in the screens screen load script.

PLC

Code: [Select]

-------------------------------------------------------
--  Cycle time label update
-------------------------------------------------------
--Requires a static text box named "CycleTime" on the screen
if (machEnabled == 1) then
local cycletime = mc.mcCntlGetRunTime(inst, time)
scr.SetProperty("CycleTime", "Label", SecondsToTime(cycletime))
end

Screen load

Code: [Select]

-------------------------------------------------------
--  Seconds to time Added 5-9-16
-------------------------------------------------------
--Converts decimal seconds to an HH:MM:SS.xx format
function SecondsToTime(seconds)
if seconds == 0 then
return "00:00:00.00"
else
local hours = string.format("%02.f", math.floor(seconds/3600))
local mins = string.format("%02.f", math.floor((seconds/60) - (hours*60)))
local secs = string.format("%04.2f",(seconds - (hours*3600) - (mins*60)))
return hours .. ":" .. mins .. ":" .. secs
end
end

12

Mach4 General Discussion / Re: Tool Change / Probe

« on: November 04, 2019, 09:28:49 PM »

Macros are in their own chunk and are ran separate from the GUI scripts. From a macro they may not get the correct parent (macros have no GUI). Best to have the macro set a register and monitor that register and launch the message box from the PLC script (which is in the the GUI) if needed.

13

Mach4 General Discussion / Re: Tool Change / Probe

« on: November 04, 2019, 09:17:13 PM »

Haven't studied it all but mc.mcAzisGetPos is not right. Think you meant mc.mcAxisGetPos

Also, you should not call a message box from a macro.

14

Mach4 General Discussion / Re: Mach 4 Screen Editor GCode Help

« on: October 30, 2019, 06:49:27 PM »

 

15

Mach4 General Discussion / Re: Why for sanity sake isn't their an "undo" on the screen editor!

« on: October 30, 2019, 11:01:07 AM »

Using the tree view on the left is a lot of help for seeing what you added where, selecting objects under something else, etc.

16

Mach4 General Discussion / Re: VFD in box or not

« on: October 30, 2019, 08:59:48 AM »

I do a lot of work day to day with VFD drives. You CAN place them in the cabinet with your controls, but you need to be very diligent about following proper grounding and EMI mitigation practices. This includes having a galvanized or SS subpanel in your enclosure (or removing the paint from under your VFD), having a master grounding bar with braided grounding straps going to each subpanel, grounding the enclosure body individually, etc. Physical separation of AC, DC and VFD output wires is a must to prevent noise from coupling onto your control wires.

Even then you do risk having issues with noise. If you do place your VFD in another box, you really should still be following all these practices. Shielded cables are a lifesaver, but can get a bit expensive.

Bravo! EMI can be the biggest pain imaginable. Best to do all you can to mitigate it as building rather than redoing IMO.

I prefer the VFD in it's own metal (ventilated/cooled is important) enclosure. This way if done right it has it's very own personal faraday cage. I have put them in cabinets with other components but never would if I could avoid it.

17

Mach4 General Discussion / Re: Mach4 Macros to enable outputs in an order

« on: October 30, 2019, 06:56:30 AM »

Might be able to do it all with a single string of Gcode. There are Mcodes to set the state of outputs and Gcode for dwell.

18

Tangent Corner / Re: It's a Dog thing.

« on: October 28, 2019, 08:53:31 AM »

  Perfection!

19

Mach4 General Discussion / Re: Mach 4 Screen Editor GCode Help

« on: October 23, 2019, 09:42:38 AM »

OK, below is a pretty simple way to do it. But it may not be as robust as it should be. There might need to be some checks/lockouts that prevent the function from being called again before the previous move is finished. What can happen now is you can click the button or pedal and while it is moving the 10 units let off the pedal or click the button again. This will make it move again in the same direction (like a step jog would) the next time the button or pedal changes states. But it will move another 10 form its current position at that time. You might even find that a bit helpful? But if you press the pedal down and hold until it has moved the 10 it will move in one direction when pressed and the other when released. Same with the button. If you click it one time and wait until it finishes moving before pressing it again up will move it one direction and down will move it in the other.

Add this to the top of the sigLib table in the screen load script.

Code: [Select]

[mc.ISIG_INPUT3] = function (state)
moveYhardStop(state)
end,
Add this function to the screen load script anywhere after the sigLib table.

Code: [Select]

function moveYhardStop(dir)
scr.SetProperty("togBGtest", "Button State", tostring(dir))
local inst, YMach, rc
inst = mc.mcGetInstance()
YMach, rc = mc.mcAxisGetMachinePos(inst, mc.Y_AXIS)
if (dir == 0) then --Up == "0" Down == "1"
rc = mc.mcCntlMdiExecute(inst, string.format("G0 G53 Y%4.4f", (YMach + 10)))
else
rc = mc.mcCntlMdiExecute(inst, string.format("G0 G53 Y%4.4f", (YMach - 10)))
end
end
Now for your toggle button. First clear the Input Signal property you have that input set to. Then in its Up and Down Script events put this code which calls the function you put in the screen load script passing it the direction parameter. The direction parameter (dir) needs to be the number 0 or 1. So, both Up and Down script events will have the same code. the only difference is one will have a 0 and the other will have a 1. I think your up script should have a 0 and down a 1 but that depends on how/when your foot pedal goes low and high and if you want pedal down to == button down or button up.

Code: [Select]

moveYhardStop(0)
Play with that and see if you like it, need to add some checks, etc.

20

Mach4 General Discussion / Re: Mach 4 Screen Editor GCode Help

« on: October 22, 2019, 09:37:30 PM »

Hey  BGEvents, can you tell me what input signal in Mach you are using and the exact name of the toggle button you pasted the code into?