Maybe way out of left field, but how long is this long-run job? At 500 lbs/week (upper end of your estimate), that is 26,000 lbs of magnesium chips a year. Even if you're at the low end of your estimate, that is 13,000 lbs. just of swarf. Have you considered a small onsite furnace to melt the chips and pour your own ingots? I know that may seem crazy on the surface, but it is chips and dust that are the fire hazard. Bulk magnesium does not burn unless heated above its melting point (1198F for pure magnesium). It is also suitable for transport once you've condensed it back into a solid. This may make it easier to find a recycler, or maybe even a metals supplier/foundry who would pay you for ingots to use as feedstock, since it would come already alloyed, and likely only require minor adjustments to the elements/ratios. The ingots could also be stored outside. What about a racing wheel manufacturer like Litespeed or Dymag?

When I was in my early 20's, maybe 23, I took a hike up to Rattlesnake Ridge, near the town of North Bend in Washington State. I brought along a woman I was dating and really liked was madly in love with. She was gorgeous and I wanted to impress her. I had a friend who was former EOD in the Air Force, and he made some spectacular fireworks. I took a very large, uh, let's say, "firecracker" with me on this hike. It is about a mile to the top of this ledge, about a thousand feet above rattlesnake lake, with the cascade mountains all around. Imagine the most beautiful scenery you've ever laid eyes on, and it was about ten times more beautiful than that. So I waited until there were no other hikers around at the top of this ridge, maybe 30-40 minutes until the coast was clear. I (very carefully) lit the fuse and waited until the wick was uncomfortably short, and chucked this thing off the edge, but behind the ledge, where the view is obscured and close to the 'mountain wall' behind the ledge, because this was likely the safest place to perform this stunt. The initial boom was loud, very loud. Let's call it unreasonably loud and very impressive for me, and my date. What I did not expect was the sound after the initial boom. We stood in awe as the wave front of the boom propagated along the walls of the valley. The mountains on either side reflected some of the sound back to us on the ledge, so we could hear the boom as it both travelled away from us, and echoed its passage back to us. The sound swept up the valley and continued for at least 20-30 seconds, the roar gradually fading into silence. We shared a private moment, and passed a bunch of sheriff deputies heading up the trail when we were almost to the parking lot. Was it foolhardy, dangerous, and illegal? Yes. It was also a magical adventure and a memory I'll treasure forever. I think a Mag. fire on a mountain in winter might also be a magical experience, provided you take the right precautions, and accept the risk & accountability which accompanies such an endeavor. Lighting the fire and "running", I wouldn't recommend. Stand in the shadows and slip away into the night instead after admiring the fruits of your labor.

Kirkland, WA. Big Okuma shop. Tier-1 Boing Subcontractor for many years... If you know it, please don't say it. Lol. Let's just say, it can be very easy to underestimate the amount of Mag. chips in a 55-gallon drum. Ours was maybe 20% full. Maybe. And that was good for 20 minutes of burn. Good thing the ignition was determined to be accidental, from an untrained employee putting hot chips in the wrong barrel...

If you do this > you'll want to alert the Fire Department beforehand, and DO NOT do this at night. Ask me how I know. Something, something, 2nd shift, something, something, bored machinists, I think you get the picture. And, I would not do this in California, Massachusetts, and/or any states with strict environmental protection laws, because if the wrong agencies catch wind (maybe literally, lol), that could be bad. Also, if you should happen to be playing around, and lighting Ti or Mag chips on fire, the light is as bright as a welding arc. Save your sight! Don't look unless you've got the proper welding glasses/shield to protect your eyes. And again, doing this at night will absolutely alert the entire neighborhood to a bright white fiery light source, and this will attract all the wrong attention.

One of the great things about the Halocarbon MWF is the performance in improving surface finish. Improvements of 200-500% are possible in Tungsten, Tantalum and Niobium. I've heard serious boosts in tool life for Ti and Inco 718 as well.

If you machine refractory metals, or Mag, Ti, Inconel, etc., I'd recommend looking into these guys. Their Metal Working Fluid (oil) has shown great performance in some very difficult materials for our government customers. I have no commercial affiliation or business interests with these guys, Phillips does not represent them or warranty their products, and these statements are my own. I just like their products and have heard good things from some guys I trust. But if you do call, tell Dave I gave you his contact! https://halocarbon.com/ Dave Antonuccio | Business Development Director Mobile: (828) 384-6541

You can easily start a fire which burns through the bottom of your machine, and continues burning through the concrete, until all the magnesium is consumed in the fire. Fire suppression is a good hedge against risk, but fire prevention is much more important. A Class "D" extinguisher may save the fire from spreading to your entire shop, but it may not save the machine. I worked at a shop which occasionally would build parts from large magnesium casting. These are machined on open-bed Deckel CNC machines (before the merger), and the orders were to "sweep up all the chips/swarf after each and every cut, and transfer the chips to the chip barrel outside, at the far end of the parking lot". Letting the magnesium chips build up and/or moving on to other operations/work before cleaning up the fire hazard, was a terminable offense. When I was young, I thought this was overkill. With the benefit of experience comes wisdom, and now I completely understand and agree with the need for these rules!

I would posit that he hasn't learned a thing since joining...

Beat me to it...

Oh, that burns! Lol. Thanks JP!!!

This was my discovery as well.

Exactly. The whole "auto-increment the work offset" function was created and intended for Horizontal work. It allows you to program Front > Right > Back > Left planes, and get B0 G54, B90 G55, B180 G56, and B270 G57 > automagically. But this behavior does a terrible job at "advanced horizontal programming", where you may be cutting at B0, but on the left or right part, held on the B90 or B270 face, where you want a separate work offset, so you can make adjustments to each part/feature independently.

Start over? Not to sound glib, but Mastercam V8 was last supported before the turn of the century, running on Windows 95, or XP, or maybe Windows 2000. To have any shot at a real answer, I'd suggest proving our community with more information about the problem.

Yep, the "Taper" is the primary attachment point to the machine, hence it is the Primary Holder. Everything between the primary holder and the tool is just another adapter/attachment. This would also apply for a "stackup", such as the Capto system, where you can mount additional extensions/adapters between the primary holder and the tool component.

I was able to use the Operations file (not Operation Defaults) to assign Tool Assemblies. This does create more work in your workflow though, as you now must "import" an Operation, instead of just clicking on a new Operation.

I did some experimentation with the Defaults File. Looks like you can save a "Default Tool" to an operation, but not a "Default Tool Assembly". I went through and replaced the Machine Definition and Tool Library inside the Defaults File, which will cause any "new Operation" you create to use the default tool assigned, but it will just grab the "Default Holder", which you can't really change. I don't think this is a "bug" per se, but just an enhancement which needs to be made where if a Tool Assembly is assigned to a Default Operation Type in the Defaults File, that it actually pulls the Tool Assembly, not just the default tool. Just to confirm > it isn't you!

Sweet! Looking at February 3rd, at my place. Start around 9:30-10:00 AM, I'm hosting lunch (we'll break around 12:30 PM), and we'll wrap around 3:00-4:00 PM, based on how everyone is feeling. Of course, everyone is welcome to attend as much, or as little, as they wish. I've also decided to do a limited Teams Meeting for those who are outside the New England area. First Come, First Served, for those who wish to join. I'm somewhat limiting attendance to no more than 10-15 people. My main intent in hosting was to meet more actual flesh-and-blood people, and not just host an online meeting, but I also don't want to let distance be a barrier to learning.

Date changed to Saturday, February 3rd... Not sure if that changes anything? Either way, you're welcome to join or just watch the videos when you can.

I completely understand @JParis! Much of my home life is dedicated to taking care of my wife as well. I missed your post as well about working with Dave on this issue. It sounds like one of the big "missing pieces" is the ability to pass strings as parameters along with the operations, and perhaps only having 10 misc. integers and decimals as well. That said, I've done some unique things with Manual Entry toolpaths, using 'strstr' function to pass "intent" for the data and use this as a form of "flow control" within the Post. That, coupled with the new 'opinfo' function, gives us some very cool tools to play with. I can read forwards or backwards with opinfo in some unique ways. Truthfully, I don't even mess with Mastercam Posts much these days anymore. I'm getting rusty. That's why I want to do some of these Mastercam meetup sessions before I forget it all. Lol.

Will certainly record whatever we do and post it to YouTube afterwards. Trying to do "YouTube Live" takes a lot of production, but we may end up doing a Teams meeting invite, and just recording that. Teams is a bit easier to manage than a broadcast stream. @Jake L, you're welcome to join as well!

"every time we upgrade and make a new program something is always out of whack and could potentially harm the machines". Could it be this > you haven't set the Control Definition Defaults properly, so the Control Definition Settings change, every time you update Mastercam? I wrote a whole thread about this. It is 'stickied' at the top of the Forum. Do yourself a favor (when you have time) and read through that thread. I think you'll learn how to setup your Mastercam, so an upgrade can be done flawlessly, in about 5-minutes, not including the install time. When I upgrade Mastercam, I run the Migration Wizard, and I'm done. No fuss, no muss, no changing Control Definition Settings. My Mastercam 2024 outputs the exact same NC code as all the previous versions, after a fresh install/upgrade.

Hey John, I'm planning a Mastercam Meetup at my house in Connecticut. Not sure if that would be too far of a drive to be of interest, but I'll extend the invitation if you'd like to come. I'd be curious to see if we could engineer a process using Manual Entry Paths, to input the hand-edited data you're adding to your NC Programs, directly from Mastercam. Where there is a will, there is a way! I've done some crazy things to develop solutions for Mastercam Posts before, so if you're up for the challenge, I'd love to help solve this for you. We could always do this over Teams, since I would bet you live 2+ hours from me in East Hartford, and that is a lot of driving for one day. So far, I've got three other guys who all happen to live in Connecticut or reasonably close, who would be joining me. We are looking at a Saturday, possibly the 6th or the 13th, to host this event at my place. @Aaron Eberhard, if you've got any interest in this, you're welcome to join us as well. Nothing fancy, just a bunch of guys with laptops and possibly a larger screen, hanging out and learning about Posts and/or toolpath techniques.

This is like saying you "just want to load up the pallet pool with material, and take a nap". Can it be done, absolutely! But there is no getting around all the investment in time and labor required to get to the point where you can just "print money". There is no cheap/free lunch in manufacturing. Metal Powder is expensive. So is the engineering required to get from idea to printed part, let alone all the way through "finished and delivered part to the customer". What competitive advantage can you apply, consistently, to make the 3D Printing process profitable in metal or plastic? I have yet to see a "job shop" enter the world of 3D printing (especially metal), and be instantaneously successful. You've got to find customers who are willing to pay for a technology to produce parts which "can't be made through traditional manufacturing technologies" (think engineered geometry like 'ntopology'), where the goal is to create periodic repeating geometric structures, for either "light weighting" purposes (lattice or generative design), or to find more efficient methods of heat transfer (like gyroid or diamond TMPS - triply periodic minimal surface). Most of the 3D Printed Metal Parts I've seen still require some sort of post-process step. Heat Treating or hot isostatic pressing (HIP) treatments help change the density and porosity characteristics of the part. Many 3D printed metal parts still require traditional post-process machining steps (flanges, O-ring grooves, bores, seals, ports, etc.) to make a finished component, ready to be installed on a product or assembly. One of the biggest hurdles to overcome are the materials and testing standards, and inspection processes, to qualify parts for any process which is safety critical. Phillips has sold additive machines since 2000, and distributes for Markforged, EOS, and AML3D. We also build our own Phillips Hybrid machine, by integrating Meltio DED Print Heads onto Haas machines. These print heads feed a commercial welding wire down through the center of the nozzle, and hit the wire with 6 lasers (1,200 watts, 200 each) to form the melt pool. Our machines are an affordable entry point for additive, both new build and component repair processes, but you still need to make the business case for parts to be printed (to make the raw pre-form), and then finished machined. We also sell a standalone Meltio M450 machine, which only prints, but this way you and have one machine printing, while the CNC just handles the machining duties. If you'd like to talk one-on-one, I can share more information and details which I wouldn't want to publicly disclose. For example, Phillips is building and running the Additive Manufacturing Center of Excellence for the US Navy, in Danville VA, for 3D printing additive parts for the Columbia-class Submarine. https://www.linkedin.com/posts/fastechengineering_usnavy-dod-usmanufacturing-activity-7118217521836486658-mO7H?

t$ = t$ + 10000 tloffno$ = 1 tllngno$ = 1

I would recommend forcing the tolerance in Mastercam to 8 decimal places for Inch. You always want the "input" data to be more accurate and granular than the output data. Keep in mind > more precise tolerances require more mathematical calculations and time to process. What is the 'least increment input' for the machine? Will you be running in Inch or Metric? Often, with Japanese machines (and most machines in general), you'll be able to hold tighter tolerances in Metric mode. Keep in mind > your NC Code is an approximation of a path to follow. Translation of complex curved shapes into point-to-point, or line/arc motion, is always an approximation of a complex shape. Is your machine's control capable of NURBS Interpolation (G06)? This would be the best and most accurate form of curve control at the machine, but good-luck supporting that output in Mastercam. The "NCI Data Format" (Mastercam's Raw Toolpath) is not capable of feeding "NURBS Curve Data" into the Post. Every Toolpath will linearize the input curve, and the output will be point-to-point motion. Trying to take those point-to-point moves and then derive an accurate NURBS curve output from that input, is a recipe for failure. There may be some advanced tools in MP where you could literally capture the starting NCI Block where the curve starts, and then scan forward through the blocks to determine the end of the curve, but there is a whole lot of math involved in just capturing the start/end blocks of the curve, let alone using that input to generate accurate NURBS output. Could you do this with Point-to-Point, using Mastercam? Sure. Will it be accurate enough to give you what you need? Only one way to find out! There are other CAM software packages with a deeper bench of engineering tools that may better support what you are trying to accomplish specifically for machining optics. The "rounding issue" that Aaron is referring to, has to do with how Floating Point numbers are stored in your computer (and how the windows kernel reads and writes values. For example, if your input is "4.5", that number is likely stored as a very close approximation: 4.499999999999 (or similar). It is through Rounding, that we are seeing nice, round, numbers. There is a Command Variable in the Mastercam Post: 'round_opt$', which "changes the internal windows library which fetches the data, and performs the rounding. The 'round_opt$' variable is only needed in cases where you notice "bouncing" of the final digit of a rounded value. (For example, a Z value that bounces from Z-.6605 to -.6604, where only that 4th decimal place digit is bouncing between 4/5, or 5/6.) This could be a result of an input value of 0.660455, for example.) The round_opt$ variable can fix these instabilities in floating point conversions to rounded values. 'round_opt$' only has a couple of valid values, I recommend trying them all! NOTE: you should only initialize this variable near the top of the Post, and only one time. (Set the value, Post your code, examine the output, change the initialization value, save the Post again, and re-test the output. Do this for each of the following values.) round_opt$ : 1 round_opt$ : 10 round_opt$ : 11 round_opt$ : 21