Messages

161

Mach4 General Discussion / Re: How do I stop the pauses in motion while setting output signals?

« on: June 26, 2020, 02:26:27 PM »

You could try the following. M64 P1 will turn on output 1. It might reduce the delay a bit

Code: [Select]

mc.mcCntlGcodeExecuteWait(inst, "G00 G91 X2\nM64 P1\nG00 G91 Z.5")


162

Mach4 General Discussion / Re: reference all problem

« on: June 21, 2020, 04:30:59 AM »

Set the axis direction so that it is correct when running g-code, and then in the 'Homing/Soft Limits' settings you can reverse the direction of the axis when homing

163

Mach4 General Discussion / Re: adding delay to signal script

« on: June 08, 2020, 10:23:29 AM »

You should avoid using wxMilliSleep as you will freeze the whole GUI especially for delays that long. Instead you should use wxTimer or the PMC

164

Mach4 General Discussion / Re: mc.OSIG_SPINDLEON - how does this signal get turned on?

« on: May 18, 2020, 10:02:34 AM »

The API call mc.mcSpindleSetDirection probably turns on the output

165

Mach4 General Discussion / Re: Tool change Problem.

« on: May 11, 2020, 12:56:16 PM »

If you go into Configure>Control and go into the 'Tools' tab, what do you have selected in the 'Tool change type' box?

There are two options: 'T on M6 line is next tool' or 'T on M6 line is current tool'. It might be that you need to select 'T on M6 line is current tool' if the other option is selected

166

Mach4 General Discussion / Re: How to read/write Analog Inputs and Analog Outputs

« on: May 11, 2020, 08:30:36 AM »

Try putting a 1 in the denominator and numerator column for each of the inputs

167

Mach4 General Discussion / Re: Set propperties from button within a function

« on: May 05, 2020, 03:27:09 AM »

You should learn to use the debugging features inside ZeroBrane to help identify reasons why code doesn't work

If its code from a module or screen load script I will normally copy the code and paste it into a script of temporary button that I created. First hit F7 to compile the code, this will highlight any initial errors in the Output window at the bottom.

After compilation is successful use F5 to start debugging and then F11 to step through the code line by line. You can right click on variables and add them to the Watch list so that you can see the values update as you step through the code. Any errors will be shown in the Output window at the bottom along with the line number that the error occurred on.

168

Mach4 General Discussion / Re: Default MouseOver color

« on: April 28, 2020, 01:03:57 PM »

I don't think it is possible to change it. You can turn if off by putting scr.EnableButtonHover(0) in the screen load script

169

Mach4 General Discussion / Re: T## Oddities

« on: April 28, 2020, 01:01:03 PM »

Try replacing the parameters.ini file in your profile with a backup

170

Mach4 General Discussion / Re: Trying Mach 4 for the first time, Gcode won't load, fine in Mach 3

« on: April 17, 2020, 02:30:31 AM »

If you are using build 4300 I believe there is a bug with ‘M0’ which causes Mach to lockup when loading g-code as you described. You can try a newer build from the ftp site