Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.
Use your display name or email address to sign in:
It is possible to have Mastercam post output macro variable codes like T#1 T#2 T#3, very easy actually. But this could cause some issues depending on how your program runs. For example what if you have more than 21 tools in a program? What if you use the same tool twice in different locations?
"Better" is a difficult thing to answer. I generally recommend creating a tool library per material rather than driving by the material. Reason being it is possible to get much more specific about the speeds and feeds for your tools if they are defined in the tool library. Driving a tool by material will give general speeds and feeds for each tool. For example, a given 1/2" carbide endmill. The speeds and feeds can easily be calculated based on the number of flutes and desired SFM and feed/tooth, but it does not take into account the cutting length. If you have a short cutting length, 1/2" that could be driven much harder than a long cutter length 2".
If you have a Nethasp then you can certainly access the license over a VPN.
First make sure that the Nethasp license server is installed and actively serving the license to your local network. If you are using the Nethasp connected to you current computer then you may need to install the Nethasp license manager.
Second, setup a VPN on your network. You may be able to do this through the router or through your server. If you have an IT department/company contact them, they will know exactly what you need.
From your remote location (house, hotel room, coffee shop) you will connect to the VPN through that locations internet service. Once you are connected, it is like your computer is actually in the office and Mastercam should be able to find the license.
One more thing, if Mastercam does not locate the license, modify the nethasp.ini in c:\program files\mcamx9\, and specify the server IP address.
There are many customers who access Mastercam licenses via VPN but if it doesn't work for your company your reseller will not be able to help.
There is no issues importing SWX 2016 files into Mastercam, if you have the update that JParis recommends. Also I would never recommend using an IGES file if anything else is available. IGES will give you a surface body instead of a solid.
Go to Mastercam's download page
http://www.mastercam.com/en-us/Support/Downloads/Mastercam
Except for many dynamic toolpaths. Choosing solid faces for machining and avoidance regions is usually pretty easy and efficient, depending on the model of course. Edge chaining still leaves some to be desired.
Finish Contour will jump on the first couple of passes, especially with a very small step over. You can eliminate some of these by setting Advanced Settings > Only between surfaces. Also change your ramp length to a much smaller value, between .1 and .01.
For rouging the part you might try a large tool that can overlap all of the material left, and just use the same toolpath for roughing as finishing, just leave stock on the roughing one. If you can upgrade to X9 I would recommend using Optirough with a Stock Model.
M00006033-1-3.MCX-7
Yes a very clean way of getting short code from the program. I have been trying to get the surface toolpath to output the same way, it just doesn't want to see the surface as a series of helix's.
Another option would be to use Surface Finish Contour with the Ramp option turned on. A short ramp between passes will usually eliminate the "zipper" line, depending on setup.
eMastercam - your online source for all things Mastercam.
Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.