Messages

181

Mach4 General Discussion / Re: DRO Properties

« on: March 13, 2019, 01:44:22 PM »

Under DRO Properties and Editor there are 4 choices;
In Place
Keypad
Keypad Extended
Read Only

What exactly do each of those do?

In Place = Click in the dro and enter values directly into the dro.

KeyPad and Keypad extended requires you to enable Operator/DRO auto Calc to take advantage of them.
Keypad = Gives an on screen basic calculator layout when you click in the dro.
Keypad Extended = gives an on screen scientific calculator layout when you click in the dro.

Read only = You cannot click in the DRO and enter data……. it is read only.

182

Mach4 General Discussion / Re: Various Issues I have run across with Mach 4

« on: March 13, 2019, 09:16:49 AM »

The onscreen mode only applies to on screen buttons (if referring to one of the default screens). Keyboard jog requires you to hold down the control key while jogging for incremental (if the keyboard plugin is configured as default).

183

Mach4 General Discussion / Re: 2 simple lines

« on: March 12, 2019, 09:23:19 PM »

Used it in a lathe m6 this week. Works a treat (in the last dev. version I know).

184

Mach4 General Discussion / Re: ATC help

« on: March 12, 2019, 08:33:56 PM »

I usually put a helper function in my m6 script. I use it to check all return calls and then do what I want if it fails. This is what it could look like and example of using it.

Code: [Select]

function m6ErrorOut(msg)
mc.mcCntlMacroAlarm(inst, 6, msg)
end

Code: [Select]

rc = mc.mcCntlGcodeExecuteWait(inst, string.format("G1 G53 F%0.4f Z%0.4f\nG1 G53 Y%0.4f\n", changeFeedRate, zAtCar, yAtCar))
if (rc ~= 0) then
msg = mc.mcCntlGetErrorString(inst, rc) --Get the returned error string
m6ErrorOut(msg)
return
end

185

Mach4 General Discussion / Re: Hold button for enable?

« on: March 12, 2019, 08:27:45 PM »

Absolutely. Most of the default screens have this in their sigLib in the screen load script already, it's just commented out.

Code: [Select]

[mc.ISIG_INPUT1] = function (state)
   -- if (state == 1) then   
--        CycleStart()
--    --else
--        --mc.mcCntlFeedHold (0)
--    end

end,

186

Mach4 General Discussion / MOVED: Crashing !

« on: March 12, 2019, 01:21:59 PM »

This topic has been moved to General Mach Discussion.

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

187

Mach4 General Discussion / Re: Notepad ++ Add M4 API

« on: March 12, 2019, 01:19:06 PM »

To the best of my knowledge, yes. The APIs integration into ZeroBrain that comes with Mach is a much more automated process.

188

Mach4 General Discussion / Re: Notepad ++ Add M4 API

« on: March 12, 2019, 09:38:26 AM »

Fair warning, I have not updated it in a while so some new API calls won't be built in. This is not automatically generated on build as the zerobrain editor does. I just did this to help me and figured I'd share it. But I will update it one weekend (but that will likely be a while).

189

Mach4 General Discussion / Re: M6 script does not seem to take changes

« on: March 12, 2019, 08:31:39 AM »

And if you rename the macro file but leave it in the macros folder, it still gets compiled into the Lua.mcc chunk. So, name the files what ever you want but if you have multipul m6 functions rolled into the Lua.mcc......... guess which one runs each time you call it.

So, don't have anything you don't want as a macro in the macros folder. Also delete all .mcc files (assuming you have the source code of course) in the macros folder after editing any macro. This will force a new compile insuring any changes you made show up.

190

Mach4 General Discussion / Re: ATC help

« on: March 12, 2019, 08:25:28 AM »

Check out the mcSignalWait API call in the Mach4CoreAPI.chm help file.