Messages

151

Mach4 General Discussion / Re: Touch Module - Using Darwin, a wire and a plate

« on: November 25, 2017, 02:17:37 AM »

If the black box works ok via the parallel port then you can assume that this box already contains stepper drivers and possibly the easiest and cost effective step is to go with an ESS which emulates 3 parallel ports giving you plenty of expansion for the future.

DazTheGas

152

Mach4 General Discussion / Re: Touch Module - Using Darwin, a wire and a plate

« on: November 24, 2017, 05:14:05 PM »

The Touch Module will work with Mach4 in demo mode and will work with Darwin as it consists of G31 moves and a bit of maths, I have answered another thread that might explain why yours is not working.

http://www.machsupport.com/forum/index.php/topic,36039.msg246828.html#msg246828

DazTheGas

153

Mach4 General Discussion / Re: Lua: Error while running chunk - on closing MACH4

« on: November 24, 2017, 05:10:48 PM »

This can happen if Mach4 has crashed for any reason and has`nt saved the profile correctly. The T Frame is part of the Touuch Panel, to rectify the fault you will need to edit your profile.ini file that is in your profile directory. Look for the lines that will prob look like this

Code: [Select]

[TOffParams]
ToffDialog=1
ToffProbeRate=5
and change to this whilst Mach4 is not running

Code: [Select]

[TOffParams]
ToffDialog=0
ToffProbeRate=5
If yours looks like the first one then this will prevent the Touch Panel from working correct as when you press the button Mach4 thinks the panel is already open when not, so it gives you the impression that it doesnt work.

DazTheGas

154

Mach4 General Discussion / Re: ESS- Spurious Limit-hit ???

« on: November 24, 2017, 04:20:53 PM »

You need to look on the forum for latest dev versions

https://warp9td.com/index.php/kunena/plugin-releases

DazTheGas

155

Mach4 General Discussion / Re: ESS- Spurious Limit-hit ???

« on: November 24, 2017, 04:16:27 PM »

What version of the ESS plugin are you using, there was a bug found to do with --Limits and was reported fixed in version 211 and above.

DazTheGas

156

Mach4 General Discussion / Re: Mach4 lathe threading with UC100

« on: November 19, 2017, 03:01:59 PM »

Heres a post from march of this year, I could not tell you if there plugin or controller has been updated since

http://www.machsupport.com/forum/index.php/topic,34338.msg237514.html#msg237514

DazTheGas

157

Mach4 General Discussion / Re: Mach 4 variables

« on: November 16, 2017, 03:02:12 PM »

2035 is the current tool length register but you can pull any data from the tooltable using the commands such as mc.mcToolGetDataExDbl, take a look in the API Docs under tools.

DazTheGas

158

Mach4 General Discussion / Re: werid script debug problems

« on: November 13, 2017, 09:50:49 AM »

Have another problem have a check in code for cycle start

I have been all over the script and cannot find anything to do with cycle start??? the script confuses me in that it looks like its part of the dialog example from github and you are trying to do an axis steps optimizer but yet there are comments about G31 which is for probeing. If it is a steps calculator there is a basic one within the wizards.

DazTheGas

159

Mach4 General Discussion / Re: Setting Auto Zero button help

« on: November 12, 2017, 05:55:50 AM »

If you are just wanting to probe to get your Z height then you could just execute some gcode from the Left Up Script

IE

Code: [Select]

local inst = mc.mcGetInstance()
mc.mcCntlGcodeExecute(inst,"G91 G31 Z-15 F10")
DazTheGas

160

Mach4 General Discussion / Re: werid script debug problems

« on: November 12, 2017, 05:48:43 AM »

The problem you have is as you say is the mc.mcCntlGcodeExecuteWait, there is no bug in the command. one thing you have to remember is when using mc.mcCntlGcodeExecuteWait within the gui you are also making the gui wait so it then becomes unresponsive. mc.mcCntlGcodeExecute runs the script fine as it doesnt block the gui. If you change your FeedRate of F4 to say F500 then set your travel distance to say just 1 and select X using the mc.mcCntlGcodeExecuteWait

Code: [Select]

mc.mcCntlGcodeExecuteWait(inst, 'G01 '.. AxisLetter .. AxisEnteredDistance..'F500')
you will find this will run the script fast enough that it doesnt make the gui unresponsive proving the mc.mcCntlGcodeExecuteWait is working.

DazTheGas