Hello Guest it is February 28, 2020, 07:11:50 PM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - smurph


If it works for you then "Good luck!"

Once i needed help and i asked here at the time /year 2015/ still no answer. http://www.machsupport.com/forum/index.php/topic,30436.msg211370.html#msg211370

What money? The money a Galil  controller costs even second hand. And that for sth without official support, on a problematic Mach3...No thanks.

I am using now Chinese offline controller, no PC, No Mach3, No windows. Thanks God. At last all works 100%

Please don't take offense at this, as I'm just trying to explain why some posts go unanswered.  

None of your questions had any relation to the Galil plugin at all.  They were all questions about the Galil and how to hook it up.  I would assume most people that read that post, including myself, decided that if you didn't get the needed information from the Galil manual, no amount of our typing was going to clear it up.  I certainly can't think of a better way or words to answer them than what Galil had to say about it.  A lot of times, that is why posts go unanswered.  Just because people don't think they have anything to add.  Those type of questions would be better served if asked on Galil forum.  

Also, a lot of Galil users were also probably scratching their heads as to why you were using a Galil to drive a Step/Dir interface in the first place when, as you say, there are much better solutions for the money (ESS comes to mind).  People tend to use a Galil to drive analog servo motors in Mach 3 as it is one of a very few plugins that can do that.  If you don't want to drive analog servos, then there is really no reason to run a Galil other than just wanting to.  Most people are not going to post that for fear of offending the OP.  


Mach4 General Discussion / Re: lua script require() question
« on: April 20, 2017, 04:41:28 PM »
This is a path issue.  If lua can't "find" your module, it will ask you where it is via the file dialog.  Make sure the module's path is in the package.path.


Mach4 General Discussion / Re: Mach4 M6 Macro problem
« on: April 20, 2017, 04:33:06 PM »
Mach Config->Tools Tab.  Make sure "T on M6 line is tool to use" is selected.


Mach4 General Discussion / Re: Ignore M Calls While Loading
« on: April 20, 2017, 03:21:52 PM »
You could use mc.mcmcToolPathGetGenerating().


Mach4 General Discussion / Re: mc.mcToolPathGenerate()
« on: April 20, 2017, 03:17:25 PM »
It will only work in the idle machine state.  :(  Why, because it uses the interpreter to generate the tool path.  So running the interpreter to run a file and generate a tool path is definitely mutually exclusive. 


There is no support for unsolicited messages in the Mach3/Galil plugin.  The Galil software will allow you to turn them on, but we don't have an interface to accept them in the plugin. 


These are not definitive.  :)

1. Only the 40x0, 41x3 and 18x6 controllers are "officially" supported by the Mach 4 Galil plugin.  There is code in the plugin to run a 21x3, but no testing has been done on them what so ever. 
2. The Galil will perform the same no matter what is running it.  Mach 4 has more features than Mach 3 in some areas while Mach 3 has more in others.  To give a definitive answer, I would need to know what functionality you are looking for. 

To be safe with that 21x3, I would suggest sticking with Mach 3.  I would keep a lookout for a 41x3 controller.  They really are a better fit for a machine motion controller because we can use contour mode with them.  The 21x3 only supports linear interpolation and while it works, it is not optimum for the task at hand. 


Mach4 General Discussion / Re: probing with do loop
« on: April 02, 2017, 12:17:32 AM »
The probing routines are using LUA co-routines (a cooperative multi-tasking scheme that emulates threads), if I remember correctly.  This is so calling the probe routine from a buttons doesn't lock up the GUI for the duration of the probe operation.  So I don't think you can use it in a loop like that because the probing function actually returns before the probing is complete!  You might want to wait on the control to go to an idle state before looping.  But you might also have to wait on the control to NOT be in the idle state before waiting on the idle state.  It will be tricky.  And if you call it from a button, the GUI will be unresponsive until the loops are done.  So... 

In my opinion, it would be easier to write a G code generator wizard to generate G code to digitize the surface. 

Mach4 General Discussion / Re: Touch button Hobby vs Industrial
« on: March 27, 2017, 12:06:18 PM »
If you paid $1400 for industrial, you will get support.  The kind of support that almost anything in the industrial world gets.  Because time is money in that world.  Now, this doesn't mean Artsoft is going to wire the machine up for you.  Or help you make a VFD from vendor x work.  Or retrofit the control at all.  We expect that has already been done by some OEM.  What it means is if a working machine suddenly has a problem, Artsoft will help diagnose the problem so that a resolution can be affected as quickly as possible.  That is where the majority of cost is born.  Otherwise, you just get the industrial features.  

Industrial also has the "capability" of running multiple planners to run things such as screw machines and mill/turn machines.  The GUI for these machines will be different and will most likely be developed by the OEM.  

Industrial, being for the industrial market, will not have the hobby touch modules installed by default.  The industrial world uses Macro B routines for probing which are supplied by the industrial probe manufacturer (Renishaw, Blum, etc...).  So to "hobby-ize" industrial, one would have to copy the hobby screen sets AND modules to the industrial installation.  

Most machines running industrial are definitely from an OEM.  The OEM would then be the first line of support to the customer.  And Artsoft would support the OEM.

For the hobbyist, Mach Industrial doesn't have any advantages over Hobby unless your hobby machine is a screw machine or you want to play with Macro B or make a prettier screen set.  I have Industrial on my machine because I have Renishaw probes (that cost MORE than Mach Industrial!!!) and want to use them with the Renishaw Macro B routines.  


Mach4 General Discussion / Re: M code Error calling a macro
« on: March 22, 2017, 12:00:06 AM »
If you want a M code macro and a screen button to have the same functionality, put the code in a module and load the module in both the screen load script and the M code macro. 

Make sure the m720 macro script filename is lower case.  As in "m720.mcs".  Also, you have functions within the m720 function.  While this works in LUA, it can be confusing.  The Write/GetRegister functions would be better suited in a file all by themselves.  Say "utility.mcs" and drop that file into the macros directory.  Or, as mentioned above, put in a global module.