Dude, You are exactly on the correct tract with G52. Your request is exactly the functionally that I ended up adding. Look at the comments for "mi1$": # -------------------------------------------------------------------------- # Misc. Values: # -------------------------------------------------------------------------- # Integers: # # mi1 - Work coordinate system # 0 = Reference return is generated and G92 with the # X, Y and Z home positions at file head. # 1 = Reference return is generated and G92 with the # X, Y and Z home positions at each tool. # 2 = WCS of G54, G55.... based on Mastercam settings. # 3 = G52 Work Shift, (Current Work Offset still remains) # 4 = Both Work Offset (G54's) and Work Shift (G52) # NOTE: G52 Work Shift uses Home Position Values. # G52 X0. Y0. Z0. Resets Work Shift I literally set this up to use the "Coordinate" method in the Transform Subroutine output. It is setup so you can call up the Active Work Offset (G54), then do a bunch of "G52 Shifts", all while calling the subroutine to repeat the cut, at the new location. It even outputs the G52 XYZ Zero at the end... G52 G52 is a "Global Work Shift". It is simply a + or - move, in XYZ, from wherever the current "Active Work Offset" is set. It is true that we can use "G52 Work Shift" to move the "active zero position", then repeat the same subroutine call (G65 P1001). I would still recommend that you include the "M99" at the end of the Subroutine that you are writing, because you still want it to "return" after the call to make the cut. Fortunately, an active "G52 Shift", is cancelled simply by calling "G52 X0. Y0." after you completed all of the parts where you wanted your Subroutine to cut. Remember that G52 is essentially an "Incremental Shift" to the active Zero Point. On newer machines, this should always be the "multi-offset" type; G54-G59, with or without the "extended series" of offsets. The cool thing about the shift, is if you properly setup the "first offset" location, and your fixture is well built, then each time you "shift", it is always relative to just the single zero point. G92 G92 is a very "old school" method of setting a Zero Point location. It is typically used on older machines, that didn't have a lot of memory or capability. The purpose of G92 is to "assign the current spindle position" to a location, relative to a Program Zero Point. This sounds really complex, but is simpler than it sounds at first. G92 is typically used by a machinist/operator/programmer in the NC Code, to tell the machine's control unit, "where is the position of the tool, relative to Program Zero". The usage can widely vary. The question is, "are you setting 'zero', with G92, or a position relative to zero. What do I mean by "Relative to Zero"? With G92, in almost 100% of the use cases, the Operator of the machine is required to drive the tool to a "known location". Either the Zero Point, or some position "relative" to a known feature on the part. G92 always tells the machine "Zero is wherever you are currently at. Full Stop. If, you are using Zero values." G92 X0. Y0. Z0. <-- This line tells the control, "The Spindle is at Zero." G92 X10. Y0. Z-3. <-- This says "The spindle is 10 inches negative from Program Zero in X, Spindle is on Center-line for Program Zero in Y, and Spindle is 3 inches above Program Zero for Z. So, any positive value for XYZ after G92 "shifts" the Program Zero Point, relative to the current Spindle Location, in a positive direction from the Spindle Gauge Line. The negative coordinates shift it the opposite direction. For X (+ = Right, - = Left). For Y (+ = Back, - = Front), For Z (+ = Up, - = Down). T1 M06 G92 X0. Y0. Z-10. <--- This tells the Control, the spindle is centered on the Program Zero, and it is 10 inches above the Program Zero Point. I would recommend against using G92, unless there is a specific reason why it would make a good addition to your shop. You'll never see me recommending that people use G92. G52 work shifts, relative to an Active Work Offset? This is supported in the Haas Post I mentioned...

That is, indeed, the answer. There is a ".mcam-defaults" file. This file contains the "Operation Defaults" you are looking to edit. It is possible to create "machine specific" default settings files, and link those to a specific Machine Definition, so that each MD-CD-PST combination also references its own '.mcam-defaults' file.

The 'switch' is in the Machine Definition > General Machine Parameters Dialog Box > Coolant Tab. Here the 'support Coolant using coolant variable in Post' switch (checkbox), is the switch that disables "X-Style" coolant. (Disabling X Coolant, enables V9 Coolant.)

I don't know the answer to your question, but you will have a better response if you post your thread in the "sub forum" for Chook, Nethook, and VBScript development. The guys that write the API check in there, and will know what methods are available for writing the data.

Hi RyszardW, We haven't been running live courses for a few years. I've had a lot of changes with my family situation, but much of the strain I was under has been eliminated with my move back to Washington State this past October. What courses would be of most interest to you? I'm finally in a situation where I can get new live classes going again. I started a different thread on here, about offering "live help" on Saturday afternoons, but didn't get much interest in that idea. The hardest part of the courses is not the teaching. It is the promotion and marketing, and getting enough people signed up for each course to make it work for me financially.

Look at the Generic Haas 4X Mill Post. I added some logic several years ago to allow G52 work shift output. Try running it through the debugger, and you'll see the section of code. I'm sure it can be tweaked for whatever your needs are.

Good. Spend some time learning how to use those tools first, including the CAD side of Mastercam. You can do quite a bit of Lathe work, including 3-Axis and 4-Axis Milling, with just those two modules. Once you know how to use those licenses, the next step for you really should be Mill 3D. After you can do 3-Axis Roughing and Finishing, then it is time to step up to full 5-Axis. The one "5 Axis First" situation I can think of, would be if you said this to me; "Our shop wants to start machining impellers for building turbochargers". Then I would tell you to get the Blade Expert module, and with about 8 hours of training, I'd have you making impellers from start-to-finish.

Are you using Mastercam 2018 or 2019?

The type of work you intend to put on your 5 Axis Machines, and your personal Mastercam knowledge have a lot to do with what you should get. Without Mill 3D, you will be very limited in what kind of toolpaths you can easily create. With "Curve and Drill 5X", you must create wireframe to drive every 5 Axis cut. If you have any kind of slightly complex geometry, you'll quicky find that it takes you hours and hours to drive even simple stuff. Here is the thing you should also understand: you can do "5 Axis machining" (really, 3 + 2), without having the "5-Axis" module. You use Toolplanes to position the rotary axes, and perform 3X machining. Reposition, then repeat to get the part done. How much do you know about Mastercam and the Toolpath options available to you? Are you new to Mastercam or are you a seasoned programmer? The complexity of the parts you make will have a huge impact on what kind of licenses are needed and the approach you take in machining your parts. Are you hogging out blocks of metal, or are you doing 5 Axis trimming of composite panels? Or machining parts out of wood? If you were just doing 5 Axis trimming, I'd say get the Curve Drill 5X. My recommendation if you don't know the software that well yet, is to start with Mill and Mill 3D first. (And Lathe.) Spend some money and time on training and learning the software. Wait until you buy a 5X machine (place the order), then upgrade and buy the 5X module. You don't need Curve 5X or Drill 5X, if you don't know how to do 3D machining yet. How many people will be programming? The reason I ask is that you can install a Nethasp, where you can share licenses. So you might have 1 Lathe, a couple Mill and Mill 3D licenses, and 1 5 Axis license, which can be shared among several users. If you are just starting with a Lathe that you want to program, then Lathe and Mill licenses will get you that. You can machine a ton of lathe Toolpaths, and do a lot of Milling with those 2 licenses. The regular Mill license supports single surface machining, so you can do chamfers, or radius features, but you'll quickly find that any serious 3D cutting will require Mill 3D.

Those "Strings" (text labels), are stored as text information at the bottom of your Post Processor. Depending on how your Post was built, and who set it up, there are different "groups" of settings. There are "Default" text strings, and "strings linked to a specific Control Definition name". When you update to a new version of Mastercam, there is often a discrepancy between the "default strings" and the "linked strings". I always make it a point to set the 'default' strings to match the 'linked strings', so updating to a new version of Mastercam goes smoothly. The process involves: 1. Setting the Control Definition Default values, to match your current 'linked Post' values. (See stickied thread here on the Forum.) 2. Using the Control Definition "text strings" to customize the "Post Text", for your linked Post. 3. Opening the Post in a Text Editor, and copying/replacing the 'default strings', with the 'Linked strings'. Doing all of that will ensure that you never have any issues when updating Mastercam to a new version. All your settings from the previous version of Mastercam will be copied correctly to the new version, but only if your default CD settings and Post Text Strings are properly configured.

G00 G91 G28 U0. W0.

Yes?

Don't forget to use the "Direction" button, so you can have lead in/out on the surface...

Another great option.

I would create 2 finish ops, for the ability to regenerate. 1st Op - leave. 005 stock. 2nd Op - final finish pass. The Toolpath Editor is a great tool, especially when you are in a hurry. But the changes are made manually, and it locks the operation after you make the edits.