You shouldn't need any arc filtering with your geometry so I turned it off but still had the same results you said. I changed my stock to leave to ".0105" and the code posted out correctly. It is caused by the arc error checking in the control def. If you turn off "End point checks" the code will generate fine even with your ".010" stock to leave. Not sure whether this is a bug because the end point checks are there to prevent code being sent to the machine that could result in a crash. You might want to send this to CNC and have them check it out.

In machining, "Know everything, Assume nothing"

Until the issue is resolved, when using the quick input make sure you type both coordinate values (X &Y or D & Z) in the field.

You need to upload a zip2go. Look in the help menu of Mastercam. The NC code is all over the place, maximum Z move is 26.8mm and minimum is -42.5.

I would also recommend mapping a button to lock the space mouse to "pan" only. I was insanely frustrated with my space mouse until I did this, makes using it much easier. IMHO.

Yes, Toolpaths > Material Manager... Right click in the dialog and you can create a new material. Edit any material and you can change the name or its' parameters. A material is defined by a base SFM and FPT with the different operations and tool types set to run as a percentage of the base. Personally I prefer to create a tool library for my different materials. This allows finite control over the speeds and feeds of each tool.

Yes that will work fine. The view is just a specific XYZ orientation with an origin. Using Left or a copy of Left would give you identical code.

What would it do before? That sounds like standard behavior, assuming your toolchanges are programmed to go home in your post.

One way you could do it is to program a 2D Contour Ramp toolpath and save the backplot geometry. Then make a 3D Contour toolpath using that geometry but chain it from the bottom up. I think you would want the 2D contour toolpath to be a conventional cut so that when you selected it going the other direction it would climb mill. Maybe you could let us know what you are trying to do so that we could find the best solution.

propi62 please start a new thread for your issue. Include all error messages and steps you have taken so that you can be best assisted resolving the problem.

You uninstalled CodeMeter. Do not unistall Codemeter. Try doing a repair on Mastercam if this doesn't work uninstall and reinstall the whole program.

+1 I can confirm that this resolved the issue on an install for me as well. It was an Nvidia Quadro card and we installed an older driver. No problems after that. Another option would be to "Disable Hardware Acceleration" in the Configuration Settings > Screen. You could also turn off the prompt for the NC File in the Configuration Settings > Toolpath Manager.

I 2nd getting a hold of your dealer. I would also recommend not installing your def files to the network until you get updated to X7. Previous versions are tricky to get functioning and if you are already having to sort out other problems don't add in unnecessary complications. Setup both machines to work locally and then update to X7. Then move your files using the method I described above.

No problem with the wordiness, a full complete explanation is always preferable. To answer your question you can associate a tool library to a Machine Definition by clicking the "machine parameters" icon, screenshot below. Now to go further....(assuming you are using X7) I recommend you share your machine files, posts and libraries by moving the entire "Shared Mcamx7" folder on the network. Get one computer completely configured with all the correct mappings, Machine/Control/Posts along with Tool Libraries, etc. Create a folder on your network drive called "Shared Mcamx7" then in the Mastercam configuration settings > Files set the "Shared Data Folder" item to the new network directory you just created. Mastercam will automatically copy all of the current machines files to this new directory. Once it is done immediatly close and reopen Mastercam and set the "Machine Type" menu with the network machine locations. Then you can map the other PC's to the network drive the same way. Using this method all of the machines, libraries and defaults will automatically be pulled from the network location. All of the relevant settings in System Configuration will also be mapped to the network location.

My answer would be, "Because it doesn't NEED to". In your example it can enter another way, in my example the only way for it to cut the center feature it fits into is by helixing. NEED here is the key. Just my two cents.

+1 JParis response. Looking at the geometry in your file I wouldn't want to helix into that feature. It just looks like an open slot and the best way to enter and cut these features would be from the outside. If I see it this way then Mastercam should to. My suggestion, if someone asks you that question open the file I created or something similar and demonstrate. It's a great opportunity to show the intelligence and ease of programming with dynamic machining.

It will only helix in where necessary. Dynamic Core will always enter from the outside of the part where possible. If a feature is selected that can be fit into but not entered from the outside Core will helix into the feature like an Area mill. Sample attached. DYNAMIC CORE HELIX SAMPLE.MCX-7

It is configured in Mastercam in the "Number of cuts" fields, screenshot below. If your post is not posting multiple passes for the G92 with this field set you should get with your reseller about modifying it.

I can not say why but I have always noticed that the Xeon processors struggle. I would recommond any of the i core processors, definitly i7 would be the best. Memory and SSD will help with any system, but I think your Xeon is the culprit.

Safenet is the company that makes the hasp keys, google safenet and you will find the site. Codemeter is the new locking mechanism that is not implemented yet. Note: Do not uninstall Codemeter. For your hasp issue make sure you check the Nhaspx program and it is set correctly for your sim type. Hasp and local for purple dongle, Nethasp and network for a network license.

You can also default these setting in the configuration file. In the Converters section check the box "Edge curves". Now every model will open with edge curves already created. However, I personally prefer to not create curve on the entire model, instead I will use the Create > Curve > on one edge where I need it. Just my opinion it makes keeping your file organized easier.

+1

Select all operations right click in the operations manager then "Edit Selected Operations > Renumber Tools..."

Also have a look at the EA Manager, Enitity Attributes manager. It can automatically modify geometry attributes for you.

Delete the drafting lines along the Y axis and create a horizontal line at the end of the tool that terminates at the Y axis. It should work perfectly with those two changes.