Messages

571

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..
G80
...
Mach 4 requires:
G83 X.. Y.. Z.. R.. Q..
X.. Y
X.. Y
G80

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

Steve

572

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_CONTROL_NOT_FOUND   -2
SERROR_PROPERTY_NOT_FOUND  -3
SERROR_PAGE_NOT_FOUND         -4
SERROR_INVALID_PARAM             -5
SERROR_FUNCTION_NOT_FOUND  -6
SERROR_IPC_NOT_READY            -99

Steve

573

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. 

Steve

574

Mach4 General Discussion / Re: Calibration issue (I think)

« on: July 10, 2018, 05:49:37 PM »

What is the Mach build number?

575

Mach4 General Discussion / Re: Are #100 thru #199 #vars safe for user functions?

« on: June 25, 2018, 01:15:30 PM »

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

Steve 

576

Mach4 General Discussion / Re: Can't seem to get load_modules.mcs working

« on: June 21, 2018, 06:42:01 PM »

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. 

Steve

577

Mach4 General Discussion / Re: Pass word protect Mach4 menu selections

« on: June 21, 2018, 06:38:41 PM »

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. 

Steve

578

Mach4 General Discussion / Re: Need the answer to this question "Is Mach4 a "MACHINE CONTROLLER"

« on: June 21, 2018, 12:18:38 AM »

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. 

Steve

579

Mach4 General Discussion / Re: Using a button script to set jog increments etc

« on: May 29, 2018, 04:08:20 PM »

The obvious question is why do the axis jog planners  not use the default units set by the user? Surely that overcomes the problem?

I don't know  why the Reset button is even there, it didn't exist in my Mach3 screen that I use. The only time I've pressed it was when Mach4 became unresponsive for any reason and I thought that might get back in control. I intend to remove it because I have no idea what it's supposed to be used for.

Mach 4 is not Mach 3.  About the only thing they have in common is that they are windows programs that run G code.  If you want to make a comparison, Mach 4 is probably a lot more like a Fanuc than it is like Mach 3.  The reset button is normally on all machine controls (Fanuc, Ysanac, Fidia, etc...), Mach 3 being an exception.  It is there to put the machine into a known state.  For instance, what if you were running a program with cutter comp and stopped it.  And you wanted to restart it from the beginning.  Well...  comp is still in effect!  Or what if you ganked the machine state running MDI commands?  Reset ensures that the machine is put back into its' know state (no comp) before you run the file again.  Reset is all about safety.  You can spot the reset button on a Fanuc quickly because it one of the most used buttons and is probably worn more than others.  

Steve

580

Mach4 General Discussion / Re: Using a button script to set jog increments etc

« on: May 29, 2018, 03:59:07 AM »

I see what is happening now.  It is not changing on its' own.  The config process destroys the axis jog planners and recreates them with the default of inches.  Nothing, at this point, will set the jog units other than a reset.  Pressing Reset will put the control in the proper mode.  

Ok, I'll call that a bug.  But you don't press reset after a config?!?

Steve