Thanks Keith, I will definitely use that information. Have a good day! Jeramiah

I think that would work. I would just have to set the correct misc int in every toolpath. I was hoping I could do it in the post so it would not have to be done for each toolpath in mcam. I appreciate your thoughts on this subject and I will try it out if I can't figure another way. Thanks

In my machine G95 is feed per revolution.. hth

I also use the force toolchange for other things like checking parts / tools, blowing parts out, and measuring features etc... this is done with misc integers. I have been manually editing these duplicate tool staging calls out, and would like to get rid of them thru my post. I have used ref point in the past, but I have found using the tool change to work better for me.. thanks for the suggestions

Exactly, I think I have to create a variable of some sort, and check to it when it tries to stage a tool. Just not sure how to code it either...

Let me elaborate a bit... I am using force tool change to go to a safe position for rotating my B-axis. So when it rotates it is still using the same tool, and the next tool is still the same. If the operation on the first side is quicker than the tool staging, when the controller reads the duplicate tool staging call, it won't do anything until that tool gets into it's pot. If the program did not duplicate the tool staging, the machine would continue to run. Hope this makes sense..

GENERIC FANUC 4X MILL X2 MR2 I have made some edits to this post in the past, so it is not 'out of the box' anymore thanks

I am having trouble understanding what "ttblend" does in my post. I am thinking it means it is at the last toolchange, for staging the 1st tool, but it is only in one place in my post... thanks

Can anyone tell me an easy way to get the post to see which tool is already staged, and if that is the one it wants to stage next, to not post the tool call for it. This is basically for when I do a force tool change, my post wants to stage the tool that has already been staged. In some cases when a tool runs faster than the next tool gets staged, the machine will sit there and wait until the tool is staged before it continues on with the program. Sorry for the long post. Thanks in advance.

Bryan, I would be interested in taking a look at that if you don't mind. Thanks,

i just had it happen X2 MR2...

I know this is an old post, but does anyone know if this has been reported or not?

Greg, Yeah, that is how I figured that out, too. Had my boring tool score a couple bores and then figured out that MCX didn't puy the 'Q' in. That's usually how we learn in this trade, we get forced too. Have a good day,

Greg, About the 'Q' value in the boring cycle... That value is modal, so MCAM won't post it in successive operations in which that value remains the same. You have force the output in the post. For example, in the drilling section of my post the asterisk in front of shftdrl$ is what forces that value each time, no matter if it changed or not. Hope this helps, code: pmisc1$ #Canned Fine Bore (shift) Cycle pdrlcommonb pcan1, pbld, n$, *sgdrlref, *sgdrill, pxout, pyout, pfzout, pcout, prdrlout, *shftdrl$, dwell$, *feed, strcantext, e$ pcom_movea

This way I can just use the tools and holders that I have already defined in MC and not have to worry about any of it. The reason I didn't see that before is because I have just been using some generic solid blocks for stock on my screen when I go to simulate. Now I see if I would just use a finished model of the part it should work flawlessly. I want to thank you again. I can't believe how simple of a solution this is, and how I kept trying to make it some big complex, post edit, and everything else. Thanks again Dave, Have a great day

Yeah, I think you're saying to check against the model of the finished part instead of 'stock' like I would in verify. That is a fine idea, and I am sure that will work. Then I wouldn't have to worry about it showing a collision when it's actually supposed to be cutting.

Could I have it define my new holder stl file using the holder dimensions that are in mastercam? Pretty much the same way it defines each different tool? Because each tool I use will have a different size holder.

Wow, that is crazy. I kind of struggled with how to do that at first also, but I found this way to be much easier and even more operator friendly. I really don't have any other experience on this subject so hopefully someone will have some better ideas for you to think about. Good Luck

I just do a force tool change between ops that work on different axes. This makes the tool go to home in Z before it rotates. I found this to be better than using reference points for my application.

Hey Everyone, I am wondering if anybody has their machine setup using the moduleworks machsim c-hook. I have finally got mine setup, and I am kind of bummed out about the way the collision detection works. When it brings in your tool settings from MC it knows what the 'holder' diameter is from what you defined it as in MC, but at the same time it is defined as part of the tool. This allows the 'holder' to crash into the part as if it was part of the cutting tool. I am just curious if anyone has this process figured out or if there are any work-arounds that any one has figured out. Thanks

Actually, now that you mention it, I remember having some circle mill paths that wouldn't post arc moves. I changed the diameter of the circle by .0001" and it would work, so it must be something in the math somehow. Have a good one!

Nevermind, that doesn't make sense either. The best bet is probably let one of these gurus look at it if you are still curious. I thought I could help but it sounds like something I never heard of. Good Luck

Are you using control comp?

on the lead in page there is a box for ramp height, that is the only thing I am coming up with that would make it helix in. Is the actual cut circular interpolation, or is the whole thing helical?

By 'Z' value, I mean ramp height...