Hello Guest it is September 21, 2019, 03:34:48 AM

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

131
Mach4 General Discussion / Re: Mach4 Lock
« on: November 20, 2018, 06:18:06 PM »
CoreConf.dll may be missing from the installation directory.  It is designed to be removed to disable editing the configuration via the GUI.  Just copy a CoreConf.dll from the same build into the installation directory, make the changes to the config, then delete the CoreConf.dll.

Steve

132
Try updating your video driver.

Steve

133
Mach4 Plugins / Re: Mach4 Galil Question
« on: November 06, 2018, 03:46:59 AM »
There is no need to have Mach do anything higher up the chain.  You can set "off on error" on the Galil and do it totally on the Galil.  The error will be seen as a following error.

Steve

134
Mach4 General Discussion / Re: Screen Set Ideas
« on: October 28, 2018, 04:03:40 PM »
Joyous?  I made you life more joyous, right?  :)

135
Mach4 General Discussion / Re: Mach 4 Goto Work Zero
« on: October 22, 2018, 05:05:02 PM »
This isn't so much about customization as it is trying to get a stock (out of the box) system.  The stock Mill profiles are either 4 or 6 axes.  So on the 4 axis profile, we expect all for axes to be enabled.  Simply enabling the 4th axis is all that is required even if it will not be used. 

Maybe we should have a 3 axis only screen set.  But we could do (and have to maintain) screen sets until the cows come home and not cover all possible scenarios.  So we compromised on two Mill profiles. 

Steve

136
Mach4 General Discussion / Re: homing 2 axis
« on: October 22, 2018, 04:46:15 PM »
Gecko is not a motion controller.  A motion controller drives the gecko.  Usually the PC's parallel port or some motion controller like the ESS or a PoKeys. 

If the two motors are mapped to one axis (a gantry type setup), then the homing SHOULD work as I described above.  So I would talk to your motion controller provider and get them to fix that. 

Failing that, you could use the LUA script API to "unmap" one of the motors from the axis in question and "map" that motor to an OOB axis.  Then you can home the original axis (that now only has one motor) and then home the OOB axis (that now has a motor mapped to it).  Then, once all of the homing is done, unmap the motor from the OOB and map if back to the original axis. 

You will probably want to read the API manual to see what functions are available.  In the Axis category. 

Again, the default homing action SHOULD be sufficient for you.  And if it worked, no scripting would be required.  That is why I suggest asking the motion controller provider to clear this up. 

Steve

137
Mach4 General Discussion / Re: homing 2 axis
« on: October 21, 2018, 02:56:03 PM »
This would all depend on how the motion plugin handles homing, meaning homing is a motion controller function.  The correct behavior would be where motor 1 hits its' home switch first, stops, and motor 3 continues to its' home switch. 

So the question now becomes what motion controller are you using?

Steve

138
-30 is MERROR_NOT_COMPILED.  This means that there is a macro with a syntax error that could not compile.  The system tries to compile all of the macros that have changed since the last compile when the control is reset.  Loading a file does an implicit reset on the control.

Steve

139
Make sure your the settings in the config dialog are correct.  e.g. T on M6 line is too to use. 

Steve

140
Mach4 General Discussion / Re: Calling one G-Code file from another
« on: September 28, 2018, 11:58:30 PM »
In a word, subprograms.  :)  Watch this video and see the magic.  https://www.youtube.com/watch?v=fT0wjbO4NpE

The idea would be that each of your different functions would be a a subprogram.  Then any main part program could call them. 

Steve