Messages

81

Mach4 General Discussion / Re: Mach4 (4.2.0.4284) Status Bar .... confused (wxLathe.set) ?

« on: August 12, 2019, 03:48:50 PM »

You can use the ModalWizard to see which modal groups those are coming from.

82

Mach4 General Discussion / Re: touch probe function question

« on: July 14, 2019, 05:25:13 PM »

Hi Charlie,

Looking at the last error history (click the "history" button) is a good way to see what is happening when using mcTouchOff. The guys at Mach have been very helpful by sending messages there when things are happening in that script, such as a probing move, setting offsets, retract moves, etc.

The command that Craig mentioned, G91 F5 followed by mcCntlEstop, looks like it is from the CheckProbe() function in the script. Look for the "CheckProbe failed" comment. It's also sending a message to the error log so it will be telling you something in that last error history.

83

Mach4 General Discussion / Re: Mach closing randomly 4162

« on: July 10, 2019, 04:00:20 PM »

I believe you'll need a comma or semicolon after each value in that table.

Steve - When something like the mcTouchOff module is loaded from a button, does that remain a separate lua chuck and have it's own 200 count limit on local variables?

84

Mach4 General Discussion / Re: New PC and after restore "mcLua.mcc no such file" error

« on: May 11, 2019, 05:35:18 PM »

In your profile's macro folder, delete all the files with ".mcc" extension. These will be recompiled when you open Mach.

Mach4 is now using Lua 5.3 so if your profile macros were compiled using an earlier version of Mach4 (that used Lua 5.2), you'll get that error.

85

Mach4 General Discussion / Re: Switching tabs

« on: April 23, 2019, 11:49:10 AM »

I've never tried it using an input to trigger the tab change, but in the screen editor the notebook containing those tabs has a property called "Current Tab"...that will work to swap tabs using the scr.SetProperty screen API call Craig listed above. It should call the On Enter and On Exit scripts doing it that way too.

86

Mach4 General Discussion / Re: edit Cyclestop in screen

« on: April 22, 2019, 11:39:29 AM »

C:\Mach4Hobby\ScreenScript.lua:689: wxLua: Expected a 'string' or 'wxString' for parameter 2, but got a 'no value'.
Function called: 'mcCntlSetLastError(string)'
01. mcCntlSetLastError(number, string)

From this part of the error message, you have an mc.mcCntlSetLastError API call but are only use a single parameter (string). It requires two (number, string). These are all listed in the API docs. For mc.mcCntlSetLastError it needs the instance for 'number' and your desired error message for 'string'.

As Craig said, you can use the line number to find where the error is in the screen script.

87

Mach4 General Discussion / Re: Is a short blocking delay in PLC script acceptable?

« on: April 12, 2019, 04:31:01 PM »

That command line switch is great to know!

You can edit the PLC script in the screen.xml, but going straight to the screen editor seems a lot easier.

88

Mach4 General Discussion / Re: How to show spindel RPM?

« on: April 10, 2019, 11:10:40 AM »

Chad-

I believe there is a DRO Code built into Mach for spindle speed override.

I've had issues setting DRO values with scr.SetProperty in the past. Ended up using using mc API calls for most of them.

-jacob

89

Mach4 General Discussion / Re: hold all axis also on jog

« on: April 02, 2019, 07:31:37 PM »

That's great info Steve. I've been learning (sometimes the hard way) the advantages of using return codes! It definitely makes debugging / logging easier.

90

Mach4 General Discussion / Re: hold all axis also on jog

« on: April 02, 2019, 11:19:15 AM »

Thanks!