Yeah Byte, that's the one. You should know that I use your chook every day, and have been for about a year: I think it's great. I've even expanded its usage by adding folders and scripts with command combos. The customization and expandability of your chook has made it the best add on tool I’ve used.

Byte, can you please post the source code (visual studio solution) for the " C-Sharp & Iron Python Scripts". I'd like to learn from it.

Simon, thank you for the link. I seem to keep forgetting about that corner of the forum.

Any updates on this topic? I have a question that's sort of related to this subject. I want to programmingly request tool data from Mastercam. Could someone please elaborate on the API methods utilized by tools like the VERICUT chook to requisition cutter data from a specified toolpath group within the toolpath manager. The encompassed tool data comprises vital attributes: tool ID, descriptive information, classification (turning or milling), gauge length, CAD profile coordinates of the cutter, gage length, rotational aspects, and orientation. From within the tool data retrieval methods are their GET functions I can use to control the format/structure of the data I've requested?

Hey there, Anyone having success with rotating and flashing 3D lathe tools and chooking them out to Vericut? If so, I'd love to learn more about your technique, tips, and any gotchas you might have. I mostly use stick tools when programming 2-Axis and 5-axis VTLs, and it usually gets the job done. But it would be awesome if I could build turning tools in Mastercam with the ability to flash, flip, and rotate them without running into those ridiculous error messages that leave me clueless about what went wrong or the tool's orientation. Also, the MCAM to VERICUT chook often fails to deliver the desired results when exporting 3D lathe tools, and that's quite frustrating. Currently, my VTL programming strategy goes like this: I create my toolpath ops using stick tools in Mastercam. While working on the part in Mastercam, I also run Vericut to use 3D lathe tool builds for verifying and tuning the NC file. Finally, I set up the information using Mastercam and some Vericut data. My tool list always includes visuals of the turning tool builds. I find Mastercam to be the quickest tool for creating annotated tool visuals. I just wish I could use those 3D tool models I'm importing into Mastercam for more than just screenshot models. If you've got any insights or suggestions, I'd really appreciate it! Thanks!

I don't seem to get any additional planes when I import models for creating 3D lathe tools. I'm also not using the mill-turn environment. I'm using lathe machine definitions with milling. Maybe that's why I don't see any additional planes being created.

Can you upload a MCAM file? That would help us solve your issue, like crazy fast! When you run these toolpaths through Mastercam’s verify, do you see gouging or large scallops?

What am I doing wrong that’s stopping me from using 3D lathe tools to its full potential? What’s the deal with 3D Lathe tools and 5-Axis vertical turning centers. It seems that most of the time 3D lathe tools have issues with flashing and rotating causing the toolpath to fail. The failure of the toolpath is indicated by a popup saying something like, “There were one or more errors…”. The popup’s scant message leaves the programmer with no explanation of why the toolpath failed or what orientation the tool was at when this happened, Bummer. Then it’s back to using 2D stick tools as those can be flashed, flipped, and rotated as much as one would like to.

Wow, "tilt relative to reference surface" is a great function! It's almost to easy to do.

Ken, here you go. I used tool axis control lines rather than the gray surface. Also, If you're planning on running this code on a trunnion you will most likely get extreme c axis rotations. You could use the transform rotate function to skew the part a bit or instead of using tool axis control lines use the "from point" or "to a point". One of those to functions should help you control the trunnion. Let me know If I was wrong, thanks test unite tool path.mcam

Thank you Colin!

Happy I could help. The number of passes and the amount to drop was backward. morph-depth-cuts.mcam

Colin, count me in on these "Post Processing online classes". I looked a few weeks ago on eapprentice and saw nothing concerning these classes; that's what lead me here. So, you'll let us know if or not these classes will happen? One last thing, when will we see new content on eapprentice and if some are in the works can you give us a written preview of what to expect? Machining here in the Aurburn Vallley is always evolving. I trust and depend on your training courses to stay as close to the leading edge as possible. Thank You CNC Programmer in

Gents, are any of you aware of any educational tutorials on machining strategy's and Technics. Let me explain in more detail; an ALU hogout which has pockets, thin walls, holes, clevis, tight tolerance flatness call outs and tight true position call outs on holes ect.. The tutorials would cover different roughing methods and what tools work best based on the type of Matl and shape of the part. And the order in which one should rough away Matl and or leave some till the end for rigidity. I have seen many tutorials that can be purchased teach the in and outs of Mastercam but none on which part Features should be machined first and which ones you should save for last. Thank you, John

Has anyone used this "ICE-VISE" successfully?

Subject should be " Surface Finish Blend stray toolpath x7" Hi, Surface Finish Blend is one of my favorite toolpaths. I feel I understand it well, but sometimes these stray wall climbing paths form. They don't actually touch the surface but are out in space. Takes me a lot of tweaking to get rid of them sometimes. I start with simple setting; .002 or .005 Total Tolerance/ .01 Step, Zig zag, Gap is 800 and No Arc Filtering on a 3/8 Ball milling .270 typ fillets. Anyone have an answer to this? Thank you

Thanks for responding and welcoming me to the site Foghorn, Machine Rotary Zero Position is what we call it or Center of Rotation ( COR) . I usually put MRZP on setup sheets. Yeah I also use the "Current WCS" too, but forget form time to time when I'm rushed or getting interrupted which happens everyday. I don't have any programmers outside my company to discuses machining with. I'm not complaining though. I am one of 3 programmers here and one of them is my lead, he is very skilled and seems to be able to program anything. I have never taken a programming course or had anyone other than my lead school me on programming techniques. I know everything I need to know to make parts, I think. I would feel more confident knowing what else is out there as far as new ways of seeing parts and how to mill them. That is why I join this site.

Hello, I briefly would like to point out that I use the machining terminology of my shop which may be elementary to some. I have never posted a question in a forum before. Please feel free to correct me. At our shop we draw and or import our customers models at MC's origin adjusting for MRZP if needed and leave them there. We then program the part to totality from there using the WCS/View like anyone else. So, for example If my part is on a trunnion and requires the part to flip 180 about Y axis I simply make a WCS to cut the other side while the part stays put. This makes programming easy for me. One issue with this method is that when I out put files from my second op to Vericut or MC machine sim the models are upside down. Its not a big issue, but a innovative having make rotated models in MC or rotating them in Vericut. Its this method the normal or is there different way of handling this? Screen shot of one of my projects below.