After a tool change, the speeds specified by the Gcode seem to be ignored and the rapid feed speed specified in mach 3 are used instead. Before the tool change everything works as planned.
Some decent replies on mach3 support regarding the problem:
http://www.machsupport.com/forum/index. ... 207.0.html
This is my current tool change macro:
[SEQ_PRECHAR][SEQNUM][DELIMITER]G00 Z[TOOL_CHG_PT_Z]
[SEQ_PRECHAR][SEQNUM][DELIMITER]G00 X[TOOL_CHG_PT_X] Y[TOOL_CHG_PT_Y]
[SEQ_PRECHAR][SEQNUM][DELIMITER]M6[DELIMITER]T[TOOL_NUM]
[SEQ_PRECHAR][SEQNUM][DELIMITER][SPINDLE_BLK]
This is my first load tool macro:
[SEQ_PRECHAR][SEQNUM][DELIMITER]M6[DELIMITER]T[TOOL_NUM]
[SEQ_PRECHAR][SEQNUM][DELIMITER][SPINDLE_BLK]
Do I need a G1 instruction in there so the F speed isn't ignored?
Improper feed rates after tool change
-
- Posts: 2405
- Joined: Wed Aug 01, 2007 4:15 pm
- Location: Irvine, CA, USA
- Contact:
-
- Posts: 488
- Joined: Wed Aug 01, 2007 4:15 pm
- Location: Switzerland
- Contact:
Well, I don't have a Mach 3, but I think the G1 is supposed to be given by the in the "Motion" section of the PP...
The variable [G_CODE] outputs the current active motion code, G0 or G1.
In my Haas tool change macro, I have a couple of more lines than you after the [SPINDLE_BLK] line:
[SEQ_PRECHAR] [SEQNUM] G54 [G_CODE] X [NEXT_NONMDL_X] Y[NEXT_NONMDL_Y]
[SEQ_PRECHAR] [SEQNUM] G43 Z[NEXT_NONMDL_Z]
Note the [G_CODE] in there. This will output a G0, however, because at this point in time, RhinoCAM tells the machine that it needs to rapid over to the G54 XY point, then rapid down to the G43 Z clearance point.
After that, the motion section should take over - that outputs the G1, because it sees a feed move from the programmed toolpath.
[G_CODE][NEXT_X][NEXT_Y][NEXT_Z]
So, check your motion section to be sure it's outputting the correct G1. If that fails, you might experiment in putting in a [G_CODE] instruction at the end of the tool change macro and see if that outputs your G1... It might still output a G0, I don't know. Otherwise, you can manually insert a G1 in the postprocessor on any line, it will output it where you insert it.
Don't know if any of this helps... --Mitch
The variable [G_CODE] outputs the current active motion code, G0 or G1.
In my Haas tool change macro, I have a couple of more lines than you after the [SPINDLE_BLK] line:
[SEQ_PRECHAR] [SEQNUM] G54 [G_CODE] X [NEXT_NONMDL_X] Y[NEXT_NONMDL_Y]
[SEQ_PRECHAR] [SEQNUM] G43 Z[NEXT_NONMDL_Z]
Note the [G_CODE] in there. This will output a G0, however, because at this point in time, RhinoCAM tells the machine that it needs to rapid over to the G54 XY point, then rapid down to the G43 Z clearance point.
After that, the motion section should take over - that outputs the G1, because it sees a feed move from the programmed toolpath.
[G_CODE][NEXT_X][NEXT_Y][NEXT_Z]
So, check your motion section to be sure it's outputting the correct G1. If that fails, you might experiment in putting in a [G_CODE] instruction at the end of the tool change macro and see if that outputs your G1... It might still output a G0, I don't know. Otherwise, you can manually insert a G1 in the postprocessor on any line, it will output it where you insert it.
Don't know if any of this helps... --Mitch
-
- Posts: 2405
- Joined: Wed Aug 01, 2007 4:15 pm
- Location: Irvine, CA, USA
- Contact:
Hoop,
Mitch had mentioned using
[G_CODE][NEXT_X][NEXT_Y][NEXT_Z]
in your tool change macros. Have you tried this?
Also you might want to specify the Feedrate as well to see if this does not affect the feedrates.
[G_CODE][NEXT_X][NEXT_Y][NEXT_Z] F [FEEDRATE]
If your G_CODE is still a G0 you might want to try
G1 [NEXT_X][NEXT_Y][NEXT_Z] F [FEEDRATE]
Mitch had mentioned using
[G_CODE][NEXT_X][NEXT_Y][NEXT_Z]
in your tool change macros. Have you tried this?
Also you might want to specify the Feedrate as well to see if this does not affect the feedrates.
[G_CODE][NEXT_X][NEXT_Y][NEXT_Z] F [FEEDRATE]
If your G_CODE is still a G0 you might want to try
G1 [NEXT_X][NEXT_Y][NEXT_Z] F [FEEDRATE]
This worked well for me.
But how can I make the tool rise to .125 during the transfer for a tool change going to 0,0,0? Not unlike "safe z" of mach3? (which doesn't seem to work during tool changes)
I would like to avoid this shaving of several thousandths upon tool change:
Do I need to set a clearance plane or does this require a macro?
But how can I make the tool rise to .125 during the transfer for a tool change going to 0,0,0? Not unlike "safe z" of mach3? (which doesn't seem to work during tool changes)
I would like to avoid this shaving of several thousandths upon tool change:
Do I need to set a clearance plane or does this require a macro?
-
- Posts: 2405
- Joined: Wed Aug 01, 2007 4:15 pm
- Location: Irvine, CA, USA
- Contact:
You can set up the tool change point and have the tool go to this too l change point at every tool change. You will have to insert the code in the tool change macro in the post-processor to do this. If you are having trouble with this please contact us at [email protected]