Hello Guest it is October 21, 2019, 09:27:50 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

Mach4 General Discussion / Re: Run in parallel 2 Gcode files
« on: July 30, 2018, 07:56:58 PM »
It looks like two machines to me.  Two G code interpreters that are linked together with inputs/outputs.  Two PCs with Mach each would be required.  Or wait for our muilt-path version of Mach which can run as many as 6 paths (interpreters).  And possibly one Mach machine and a PLC may be able to do the labeling? 


You only need to re-generate the tool path if the work offsets have been changed.  Otherwise, Mach doesn't redraw the whole tool path.  It only draws the entire tool path when you load a file or hit re-gen.  All it draws is the cross hairs and changes the color of the cut path after that.  I fear that there is something wrong with your graphics driver if you think it is trying to re-draw the tool path all of the time. The build on the website (3804) has all of the optimizations I was talking about the you quoted. 

I would:

1. see if there is an updated video driver.
2. make sure you are not swaping to disk (low memory).


Mach4 General Discussion / Re: G-Code for Mach4 vs. Mach3
« on: July 17, 2018, 11:46:31 PM »
For a post processor, the main differences will be in the canned cycles.  You cannot repeat the cycle G code on every line like you could in Mach3.

Mach3 would allow:
G83 X.. Y.. Z.. R.. Q..
G83 X.. Y.. Z.. R.. Q..
G83 X.. Y.. Z.. R.. Q..
Mach 4 requires:
G83 X.. Y.. Z.. R.. Q..
X.. Y
X.. Y

Threading on the lathe (G76) is Fanuc compat and Mach3 threading code will just not run in Mach4. 


Mach4 General Discussion / Re: mcMasterModule question
« on: July 10, 2018, 06:17:40 PM »
Try checing the return code of the scr API call. 

val, rc = scr.GetProperty("droToolChangePosZ", "Value")

What is the value of rc?  It will be one of:

SERROR_NOERROR                       0
SERROR_API_INIT                       -1
SERROR_IPC_NOT_READY            -99


Mach4 General Discussion / Re: G 05
« on: July 10, 2018, 06:08:29 PM »
The default motion mode is determined by the general tab of the configuration dialog.  Exact Stop (G61) or Constant Velocity (G64), CV for short.  G64 is the semi-equivalent of you motion smoothing.  Most of the time, G64 (CV) is the default motion mode.  G64 it is primarily characterized by the acceleration capabilities of your machine.  The higher the accel settings/capabilities, the closer CV cuts to the true path.  There is a way to tailor the CV settings by angle.  But there isn't a way to blend with a number in a range like your G5 command. 


Mach4 General Discussion / Re: Calibration issue (I think)
« on: July 10, 2018, 05:49:37 PM »
What is the Mach build number?

The system variables are also described in the Mill G code programming manual in the Docs folder.  Chapter 6.


This is the way to share code between LUA states.  But it will not let you share global variables between the states!  Just throwing that out to clarify.  If you want to share data between the states, use Mach registers. 


No, there isn't a way to lock more menu items. 

Once the machine is configured, you can remove CoreConf.dll.  That will make it impossible to configure the machine.  It will remove some config related menu items as well. 


It is just semantics.  The human controls Mach which controls the motion controller that controls the machine (maybe not even all of it) or just a stepper driver (or servo drive) that controls the stepper (or servo) motor which controls the screw which controls the table position for a plane of motion.  I/O boards may be different from the motion controller, but does that mean they don't control parts of the machine?  The machine control is really the sum of the parts that make up the system. 

Which one controls the machine again?  Seems like it is really the human that kicks it all off.  And this human thinks your buddy may be overthinking it a bit.  :)