This is all well and good, except, that they don't know about the static file path issue.Įvery Control Definition file has a set of "Default Settings" that are used (you might have guessed), by default. But then they go and "link" their CD to that Post Processor, and take the time to configure their CD. When you setup a new post processor, most users typically create (rename, whatever) a new post, and put it in a specific folder, local or network folder location. Those settings are only valid for that exact post processor file name, in the exact folder location you specify. The settings that are stored inside the CD are stored for a specific post in a specific file location. This problem occurs because the settings in the CD refer to a static file path. The main problem that I see people run into comes when they update to the next release of Mastercam. OK, so the CD contains settings that format output from the post.
MASTERCAM 2019 UPDATE CODES CODE
So in a nutshell, the CD contains user-select-able parameters that control some of the formatting of NC code output. The CD allows you to do that, without changing the settings in the Library Copy of your CD. For this individual file, it might make sense to disable Sequence Numbers, remove all the "Space characters", and output all of your Arcs using "R" values instead of IJK, just to save space. You wouldn't want all those modifications to be made to the "library copy" of your files they are project specific.Īnother situation might come up where you are running out of memory for a specific program. You could setup the "stations" with a RAH component, and have all of those options saved inside your individual Mastercam file. So for example, say you had a program that used a Right Angle Head, with a few specific tools. This convention allows you to make "individual" file changes.
To a certain extent, this does make sense. These "file copies" are specific to your individual Mastercam file, and are not "linked" back to the originals (or "library copies") of the files. When you create a new job in Mastercam, and load a "Machine Definition" file into your Ops Manager, Mastercam places a copy of your MD and CD into the Ops Manager. So even though a machine might share all the same settings with another machine in your shop, the "best practice" is to use a single MD/CD/PST name for each unique machine on your shop floor. Every shop that I've worked with uses a single MD, CD, and PST file, all with the same name. In practice however, nobody ever does this. This would give "administrators" the ability to make edits for multiple machines from within a single file. When it was originally conceived, the CD was created with the ability to link and control multiple post processors, and have separate settings for each one. The idea behind the CD is that it gives the programmer the ability to adjust settings by using a Graphic User Interface, instead of having to make edits directly to your post processor. The CD (Control Definition) contains common settings for things like "Arc Formatting", and the settings for Sequence Numbers (N numbers), among other things. What is a Control Definition, and why should you care?:įirst, what is a Control Definition File? A Control Definition is a file that Mastercam uses to store settings for controlling your NC code output. Here is a step-by-step process for setting the Control Definition Defaults. You can setup Mastercam to handle upgrading without causing you frustration, or the loss of any hair/sleep. Ok, so what's going on? -> You didn't set the Control Definition Default Settings. Since many people have asked me to share how this works, I thought I would make a post about setting the Control Definition Default settings.Īre you tired of your NC code changing whenever you update Mastercam? Why do your NC settings seem to get screwed up? You ran the "Migration Wizard", and things are still broken.
0 kommentar(er)
