Curious...just tried it and yeah, ok I see it now... Not sure it's a big issue as I see it, so long as you have your correct post defaulted but yeah, this is definitely something "newer" and should be cleaned up

Ron, As I found the original post this is James' work O9201(REDUCING PECK MACRO) (THIS PROGRAM IS DESIGNED TO RUN FROM A PRE-DRILLED HOLE) (USED FOR A DEEP HOLE WHERE TWO DIFFERENT DRILL LENGTHS ARE NEEDED) (#18 "R" RAPID PLANE) (#4 "I" 1ST PECK) (#17 "Q" MINIMUM PECK) (#26 "Z" FINAL DEPTH) (#5 "J" REDUCTION MULTIPLIER) (#9 "F" FEEDRATE) (#3 "C" PECK RETRACT COUNT) (#100 INITIAL PLANE STORAGE) (#101 REMAINING DISTANCE CHECK) (#102 "Z" TARGET VALUE) (#103 "Z" FEED/RAPID VALUE) (#8 "E" SUB RAPID PLANE) #10=#4 (ERROR CHECKS) IF[#3EQ#0]GOTO5 #3=FIX[#3] GOTO6 N5#3=1 N6IF[#26EQ#0]GOTO50 IF[#18EQ#0]GOTO51 IF[#9EQ#0]GOTO52 IF[#4EQ#0]GOTO53 IF[#18LT#26]GOTO54 IF[#5NE#0]GOTO7 #5=1 N7IF[#5GT1]GOTO55 IF[#17GE.2]GOTO8 #17=.2 N8#100=#5003(STORE CURRENT Z POSITION) G0Z#18(RAPID TO R PLANE) #101=ABS[#5003-#26](CHECK FOR REMAINING DISTANCE #101=FINAL DEPTH) #103=#18(SET 103 TO R PLANE, #103=NEW "R" IN PART) WHILE[#101GT[#4+.02]]DO1(TEST 101 FOR FINAL DEPTH) #149=0 WHILE[#3NE#149]DO2(CHECK FOR RETURN TO "R") G0Z#103(RAPID INTO NEW "R" PLANE) IF[#101LE[#4+.02]]GOTO2 #103=[#5003-#4](NEW DEPTH) G1Z#103F#9(FEED TO "Z") #101=ABS[#5003-#26](RECALIBRATE DISTANCE TO GO) #103=#103+.1(RETURN PECK IN "R" PLANE) G0Z#103(RAPID TO NEW "R") #4=[#4*#5](RECALCULATE FEED DISTANCE) #149=#149+1(INCREMENT COUNTER) IF[#4GT#17]GOTO1(CHECK FOR MINIMUM PECK) #4=#17(SET TO MINIMUM PECK) N1END2 G0Z#18(RAPID TO ORIGIONAL "R" PLANE) END1 G0Z#103(RAPID TO PECK RETURN PLANE) N2G1Z#26(FEED TO FINAL Z) GOZ#18 N3G0Z#100 #4=#10 GOTO4 (ERROR STATEMENTS) N50#3000=1(NO VALUE IN Z) N51#3000=2(NO VALUE IN R) N52#3000=3(NO VALUE IN F) N53#3000=4(NO VALUE IN I) N54#3000=5(R IS DEEPER THAN Z) N55#3000=6(J VALUE MUST BE LE 1.) N4M99 Though as a relook at that one, I don't think it's one of mine but I probably used it to create something else..so I don't want to credit for someone else's work on this....

How about a z2g? I am not saying it's not happening but that is something I Have never seen.

Yup and these are generally single work order releases...there will be follow ons. We have parts that we make 100k+/yr and these are not small little lathe parts but milled parts that run on a tombstone 2 ops, 40 complete each cycle....so yeah, keeping that smaller qty stuff in our vertical area helps keep the HMC area humming https://imgur.com/dxe7Gga

I will also note a bit more...the HMC's tooling gets set up and left, we may run several thousand parts, then turn the job off but as an OEM things get turned off/on all year long and from year to year. On our VMC's that do short run protoypes & short qty <2000 usually, tooling is always moved in & out as the machines only have 30 tool capacity....tools get setup and broken down for each as they go.

I do not....I have my tool libraries, I have my holder libraries.... Times are I use what already exists, I am just importing tools from a similar job...otherwise I pick a tool, add an appropriate holder and move on... In my case, even though all(27) of my HMC spindles are the same, each machine having 160 tool carousel, there are so many different jobs running in these machines that I cannot always be sure the tool assembly I have already exists in that machine....jobs do occasionally get moved from machine to machine for scheduling purpose and needs. I have actually done a count of just trying to standardize taps in one machine, between cut, sprial & rollform taps, pre-plate & post plate, inch and metric I could use up a chunk of the tooling capacity for a machine.

The simple answer is no....and it's not very Applie'ish....most software titles are not fully backwards compatible.. You of course can save the part geometry in a format that he can open but the tool path information does not go backwards...

The above will REMOVE the reference to that post in the control def....after you make the change you will have to reload the control def into the file.

First thing I am going to say is make a backup of your post..... Second thing I'll say, if you don't do this VERY CAREFULLY you WILL hose your post, be certain not to change the formatting... Third thing is if you don't need to do this, DO NOT DO THIS...... If you have a Control Def that has multiple posts in it and you want them gone, it "can" be done inside the post....see my 3 warnings to start..... Open the post, go down to the bottom where the control section begins.. # -------------------------------------------------------------------------- # POST TEXT # -------------------------------------------------------------------------- [CTRL_TEXT_XML_BEGIN] # All post text edits must be made through Control Definition Manager <?xml version="1.0" encoding="UTF-8"?> <mp_xml_post_text xml:space="preserve"> Every control def is defined with the tags <control> </control> Everything between a single set of those control codes is a control definition..... In this example I'll use the CTRL_MILL|DEFAULT as the example.... Find everything between the control codes <control> <control_label>CTRL_MILL|DEFAULT</control_label> <language>en-US</language> <misc_integers> <misc_1> <text>Work Coordinates [0-1=G92, 2=G54's]</text> <value>2</value> </misc_1> <misc_2> <text>Absolute/Incremental, top level [0=ABS, 1=INC]</text> </misc_2> <misc_3> <text>Reference Return [0=G28, 1=G30]</text> </misc_3> </misc_integers> <simple_drill> <first_peck> <text>""</text> </first_peck> <subsequent_peck> <text>""</text> </subsequent_peck> <peck_clearance> <text>""</text> </peck_clearance> <retract_amount> <text>""</text> </retract_amount> <shift> <text>""</text> </shift> </simple_drill> <peck_drill> <dwell> <text>""</text> </dwell> <first_peck> <text>Peck</text> </first_peck> <subsequent_peck> <text>""</text> </subsequent_peck> <peck_clearance> <text>""</text> </peck_clearance> <retract_amount> <text>""</text> </retract_amount> <shift> <text>""</text> </shift> </peck_drill> <chip_break> <dwell> <text>""</text> </dwell> <first_peck> <text>Peck</text> </first_peck> <subsequent_peck> <text>""</text> </subsequent_peck> <peck_clearance> <text>""</text> </peck_clearance> <retract_amount> <text>""</text> </retract_amount> <shift> <text>""</text> </shift> </chip_break> <tap> <dwell> <text>""</text> </dwell> <first_peck> <text>""</text> </first_peck> <subsequent_peck> <text>""</text> </subsequent_peck> <peck_clearance> <text>""</text> </peck_clearance> <retract_amount> <text>""</text> </retract_amount> <shift> <text>""</text> </shift> </tap> <bore1> <description> <text>Bore #1 (feed-out)</text> </description> <first_peck> <text>""</text> </first_peck> <subsequent_peck> <text>""</text> </subsequent_peck> <peck_clearance> <text>""</text> </peck_clearance> <retract_amount> <text>""</text> </retract_amount> <shift> <text>""</text> </shift> </bore1> <bore2> <description> <text>Bore #2 (stop spindle, rapid out)</text> </description> <dwell> <text>""</text> </dwell> <first_peck> <text>""</text> </first_peck> <subsequent_peck> <text>""</text> </subsequent_peck> <peck_clearance> <text>""</text> </peck_clearance> <retract_amount> <text>""</text> </retract_amount> <shift> <text>""</text> </shift> </bore2> <misc1> <description> <text>Fine Bore (shift)</text> </description> <first_peck> <text>""</text> </first_peck> <subsequent_peck> <text>""</text> </subsequent_peck> <peck_clearance> <text>""</text> </peck_clearance> <retract_amount> <text>""</text> </retract_amount> </misc1> <misc2> <description> <text>Rigid Tapping Cycle</text> </description> <dwell> <text>""</text> </dwell> <first_peck> <text>""</text> </first_peck> <subsequent_peck> <text>""</text> </subsequent_peck> <peck_clearance> <text>""</text> </peck_clearance> <retract_amount> <text>""</text> </retract_amount> <shift> <text>""</text> </shift> </misc2> <drill_cycle_descriptions> <misc_drill_1> <text>Fine bore (shift)</text> </misc_drill_1> <misc_drill_2> <text>Rigid Tapping Cycle</text> </misc_drill_2> </drill_cycle_descriptions> <canned_text> <canned_text_1> <text>Stop</text> </canned_text_1> <canned_text_2> <text>Ostop</text> </canned_text_2> <canned_text_3> <text>Bld on</text> </canned_text_3> <canned_text_4> <text>bLd off</text> </canned_text_4> <canned_text_5> <text>M5</text> </canned_text_5> <canned_text_6> <text>M6</text> </canned_text_6> <canned_text_7> <text>M7</text> </canned_text_7> <canned_text_8> <text>M8</text> </canned_text_8> <canned_text_9> <text>M9</text> </canned_text_9> <canned_text_10> <text>M10</text> </canned_text_10> </canned_text> </control> and delete it.... DO NOT, I REPEAT DO NOT DELETE THE NEXT <control> as that is the beginning of the next control definition with which that post is associated. Again, reread my 3 missives at the top and proceed at YOUR OWN CAUTION!!!!!

To the best of my knowledge, no. Only way I know how to do it is load the assembly into Mastercam, delete the holder and save the tool back. This is why I create my tools individually and save them and pick them for assemblies as I need to...

The system resources that a thread uses is amazing....you can dig back on this forum and my general answer when someone wants to generate a thread, "so they can show it" my typical answer is don't...others and myself over the years have shown people how to do it but no one really suggests to do it... Would be better if that engineer used the lighter weight version that only produces and hole but in the CAD shows a thread.

Sight unseen, I can only speculate here but I would be looking for ways to trim that initial solid down in size....defeature things that were unimportant, finding and deleting any extraneous solids or surface fragments that might be coming in on import....if it has threaded holes that I don't need to process, I would remove them....hell, I'd trim out sections of the model completely that I didn't have to touch.....I would simplify it as much as I could prior to any tool path creating to help keep that file size down. I view it as time spent upfront saves me time on the backend trying to wrestle and manage large files.

Just curious, is there anything you do like?

A lot of what I do, I end up with files that are in the 4-500 meg range....on these systems I spec'd we do well with them. There are days where around lunch time things get a bit wonky, that's when I and tell my guys, to save the file, shut down Mastercam and restart it...sometimes you just need to flush out the system.

It's actually very easy.... Orient the holder so the centerline lies along the X axis......the face of the holder should be at the origin.... Clean up all of the geometry so that you have a wireframe outline in the X- / Y+ quadrant....make sure it is ALL neatly trimmed together and all on a level named NOCUT Save that as a .dxf file....you can them import the dxf into the standalone tool manager and name it as you would like... Once you've done a few, the process is really straight forward If you start out with a solid model for a holder, position it as noted and Create >> Curve >> Slice to get the wireframe.

Because when you have large, complicated models it can and does tax the available system(computer) resources causing system performance slow downs. A solid model is at its root a large complex math formula, surfaces are a lighter system weight. You need to remember, a large model is not dictated so much by the physical size of it in the real world. It is more about how many faces the computer graphics have to render....I have had small, lens size files with 10k+ small rendered faces that bring the system to a slowdown.

Flip your Y+ direction 180° In doing so you'll stay with the Cartesian coordinates system...

Sounds like it is programmed for a product that you don't have access to use. You can open a lathe file but if you don't have a lathe license it will grey out

You can set your tools up in your library for different materials. It's a bit of work but it is achievable

You need different geometry for a solid sweep...ideally, outer rails that touch the circles on both ends...in this case, use surface, flat boundary the ends, then create solid from surfaces...

Yup, with these op heavy I parts I do in multiple positions on a tombstone, I carry a stock model all the way through each position, the save that result as a PMesh, position that for the next rotation position and build on that carry all the next ops til the end, then rinse & repeat.

If you are trying to start Mastercam remotely, it won't work. Assuming you have a license on the remote computer, you cannot start it from a remote location, the license reads the wrong computer...however if you leave it running, you can log in and use it, though it will be a bit sluggish. If you have Mastercam installed on the computer in front of you, you need a network license and a VPN connection to pull the license. If you have a software license, you can borrow it onto the traveling computer and use it that way.

In that respect yeah...I don't know if I have good trigger finger discipline or what but I've been very lucky in that respect. I've had it happen, I have been lucky it's been minimal

How would you lock "live" backplot lines....from that standpoint, you'd have to lock every operation, which you can already do...

Hard pass thank you... One guys explained Gibbs Cam to me this way..."forget everything you already know about any other CAM system, Gibbs doesn't work that way" I cannot say if that is accurate or not but after that, no desire