Leandro, I just checked, if you right click in the operations manager select "edit selected operations" then select "edit common parameters", "batch" is in the upper right hand corner

You might be able to use the edit selected operations, edit common parameters in the operations manager

Dwain, Currently the 5axis circmill toolpaths output in linear code, to get the helical output you will need create a custom toolplane normal to the hole vector and use a standard circmill toolpath.

Pete, If you loaded an older code in the hasp utility with an expired maint date, then no you will not necessarily be able to run the latest version/s of the software. If you had an old enough code loaded that would say set your maint back to Jan 2005, you would only be running Mcam V9.

There's no reason to uninstall McamX5 from the work station , all you're changing is the location of the nethasp. You don't have Mcam loaded on the server, do you?

Pete, If you're using Mcam in a inch configuration the volume will register in cubic inches then multiply by 16.39 to find CC's. Like Greg said the model will need to be made watertight then create solid from surfaces. I have a question, 01:40 AM? Couldn't you sleep?

CB, In McamX4 when you switched the multiaxis interface to advanced there was no going back to the basic interface. In the McamX5 the only way to switch the toolpath strategy is to start another multiaxis toolpath.

sir Cam, The information concerning the NetHasp setup can be found in the Administrator Guide pdf. http://www.mastercam.com/Support/Documentation/Default.aspx#x5list This pdf is also in the documentation folder in your Mcam install.

I get some of my information from the help utility in the lower right of the toolpath utilities, experimenting, taken a couple of multiaxis classes with Karlo at CNC and teaching multiaxis. InHouse has an advanced multiaxis book that has a couple 5axis projects, one of the files I use frequently is tutorial 6 Gouge Strategies. It shows how you can change a basic curve 5x toolpath by setting up multiple gouge strategies in collision control. I put the file I use up on the ftp, "04_Gouge Check Strategies_TP.MCX-5"

That's a cool solution Keith

OK, ignorant question where's the portal to the ftp?

Which documentation do you speak of?

What about using a surface project then convert to 5axis?

CB, You could setup depth cuts in the multiaxis curve toolpath but it is going reposition to the start of the chain for each pass.

You could use control lines for your tool axis control that will limit the movement.

If you're wanting to have the A&B rotate into position only, then you could use a custom toolplane and associate it with a 2d pocket toolpath.

Smit, You could config one of the computers in McamX5 then share the config within the McamX5 program, you would probably need to config the Win7 and XP separately because the default file locations are mapped slightly different. Check out page 17 of the McamX5 Transition Guide in the documentation pdf. Something that some users seem to forget is that all the Mcam users will need to be mapped into the sever using the same network drive address. Yes, you can bring over the McamX4 config file and use it in the McamX5 install ***However*** due to the differences in file mapping between the two installs there is some back end work that needs to be done. The merging process of the config files starts on page 21 of the McamX5 Transition Guide. The problem is most folks are trying to use the McamX4 config file as is and get extremely frustrated when it doesn't work, then blame it on the software.

The guys in the post dept could explain the tokenization issue better than I can, but I did have an issue with a set of lathe machine & control def files. I keep all my custom files in another location other than the default CNC_Machines folder in the root install. The issue I was having was linked to the control def. It was explained to me that even though I had setup a dummy directory that matched the root install, by moving that file into the dummy directory it had disrupted the token and had become an absolute. To fix the issue I put the Machine def and post back in the default locations and made a copy & renamed a default control def, reassociated the files and the issue was gone.

One thing to be aware of is that when you send the posts, machine & control defs to the server all of the file mapping is absolute. I found out recently that these files are tokenized, when you change the default location that tokenization is broken.

Radial vectors Hot Dang that worked

GCode are you using the front toolplane to force a B rotation?

"vertical tool detected" Yes, I got the same error using a 5x drill toolpath it's basically canceling it self out I'm guessing that the post is detecting an instability type issue

Short of having a custom post setup like your MpMaster (modified) I can't think of a toolpath that will output the format you're looking for.

Keith, Which toolpath are you using to output 2 axis rotary positioning code?

I'm hoping for an edit that can also calculate the feed in relation to the rpm. That functionality isn't controlled by the post, the post only spits out what the NCI file tells it to. You could setup a custom tool library that is specific to that machine. Then program your feeds/speeds from tool as GCode said or if you prefer to take a longer way around the barn you could create a custom material library that is specific to your machine. Like I said in my previous post, the post block edit overrides the programed spindle speed if it is set higher than the max rpm.