Hello Guest it is December 06, 2019, 09:04:16 PM

Author Topic: Mach4 de-referencing all axis when loading gcode  (Read 1585 times)

0 Members and 1 Guest are viewing this topic.

Mach4 de-referencing all axis when loading gcode
« on: December 07, 2016, 08:30:39 PM »
I noticed that Mach4 de-references all axis when loading a new G-code file.  This forces me to do a new "Reference All Axis (Home)" when doing 2 different G-code routines on the same part.

Is there a way to prevent de-referencing when loading a new G-code file?
Re: Mach4 de-referencing all axis when loading gcode
« Reply #1 on: January 07, 2017, 01:28:47 PM »
I am experiencing the same issue. Did you find a way to fix it?
Re: Mach4 de-referencing all axis when loading gcode
« Reply #2 on: January 11, 2017, 09:12:34 PM »
Sorry but I have not heard of a solution yet.

Offline smurph

*
  • *
  •  1,153 1,153
  • "That there... that's an RV."
    • View Profile
Re: Mach4 de-referencing all axis when loading gcode
« Reply #3 on: January 11, 2017, 10:20:43 PM »
I have never heard of Mach doing this.  Why don't you tell us about your hardware and stuff (motion controller, OS, Mach build, etc...)?  Because the more information, the more everyone might be able to find a solution. 

Steve
Re: Mach4 de-referencing all axis when loading gcode
« Reply #4 on: January 12, 2017, 03:50:50 AM »
Using Mach4 version 4.2.0.2803 with CSMIO IP-M controller. CS-labs are releasing a new plugin in a few weeks, letting me use a newer version of Mach - so hopefully it will work then..
Re: Mach4 de-referencing all axis when loading gcode
« Reply #5 on: February 23, 2017, 07:08:22 PM »
SOLVED: Looks like loading a g-code is considered a reset. There is a setting in the CSMIO plugin, "Set Axes to "0" on RESET", just uncheck it and problem is solved.

Offline smurph

*
  • *
  •  1,153 1,153
  • "That there... that's an RV."
    • View Profile
Re: Mach4 de-referencing all axis when loading gcode
« Reply #6 on: February 23, 2017, 08:05:27 PM »
Ahh...  good to know.

Loading G code is an assumed reset.  Because you really want the control in a known state.  Say you had a file that was loaded previously that used G68 rotation.  If the control wasn't reset before loading the new file, it would gank the tool path (and the part!) when the new file is loaded. 

Steve