I got it :) I had to add an *sgplane in the string pcan1, pbld, n$, [if gcode$, *sgfeed], *sgcode, *sgplane, *sgabsinc, pwcs, pfxout, pfyout, pfcout, *speed, *spindle, pgear, [if gcode$, *feed], strcantext, e$ Now I get a plane callout on every toolchange line

Yeah, all that did was add a G17 in the code before every retract. I just need it called out right after the toolchange. Like G0 G90 G17 G54 X0. Y0. M3 Etc Etc.

I got bit by the sideways drilling spotdrill yesterday lol. After running an engraving path on the rotary the next tool up was a spot drill using G81. Well, turns out still having G19 active is really eye opening. I used to run MPmaster post witch would call out the sgplane at every toolchange. I'm using another one that works with CIMCO probing now that doesn't post out a G17 at every toolchange. I've looked at the Mpmaster and can kinda see how it works, but I thought I would ask here. I can go back to my reseller for the update, but I always like to learn more about posts myself. Thanks in advance for any of ya'lls time

I knew there was something I was missing. Thanks again man

This *Should* be Very common, how else would you tackle multiple parts in a VMC? Two vises, two parts. I'll get this sent off to QC at mastercam

Thanks for checking it out. Btw, it also does this behavior on two other toolpaths. What is my usage of transform that you've never seen before?

Toolpath #4 is the problem child PIF35232_03.mcam Btw this is MC 2023 update1

Well, I have one for QC.... Two parts, g54 g55. I hear the finishing 3/4 endmill making more noise than it should be. I go through the code and found the issue. On one operation (simple contour) it runs that path Twice on the G55 and never even calls out G54. I have checked everything I know twice. Does anyone here wanna check it out??

Man, all I know is I used the option to disable paths/ghost and create separate (or whatever it's called). I've used it many times before, but I'm unsure of what could have happened?? Now I'm scared to use it. It left off a 3d horizontal floor finish path and simple contour. It may very well have been my fault, but I'm unsure of how or what...

Toolpath transform bit me today.... All seemed to post out correctly, But two paths failed to end up in the code Didn't realize this until after the parts were off the machine. This was just for g54 and g55 in two separate vises. Could have been BAD.

I had to make some parts recently like the garbage above out of SS on a 3axis. I window framed the part out of plate so I could "index" it in the vise and have a reference point. Worked great, except was Slow. Unless there's something I'm not seeing, there's no need for a lollipop tool?

Mitsubishi WSX 445 with one wiper insert installed. 16 finish no problem

Dude, it's a Bow frame.... If everything is relatively flat and true I would Assume ±.02 would be fine lol. But then again I don't machine archery products....

Ron, could you elaborate a lil more? I understand the misc int are customizable, but how exactly would that work? I may would like to incorporate something like that in our post.

When that posts out it's not calling up the spindle after the M00, some machines may not work like that. You can fix this by checking "force tool change" in the first op. This will send Z home though...