I'm pretty sure that only works on newly created operations.

I just exported an operation to my ops library and I got the following message (see image at the bottom of the posting): I clicked Yes to remove the corrupted tools and the following report popped up. Since I removed the corrupt tools, I assume I now have ops in my ops library that have no tool assigned to them. Looking through the library, that doesn't appear to be the case, unless I overlooked it. In the above report, I also assumed that the numbers 230, 231, 232 and 240 would be operation numbers in my library that had corrupt tools. But those numbers don't all match up with operations that use those tools and the ones that do, appear to have a valid tool assigned to them. So I guess I don't know what to do with all of this. None of this makes any sense. Can anyone shed some light on what's going on here? Using X9.

Perhaps it's in the changing of names, but mill level one ABSOLUTELY did the wireframe 2.5D toolpaths. I don't even know what "entry" level mill does. Maybe I'm the one out of the loop on this, but we used to have mill level 1 seats and we did swept 2D toolpaths like there was no tommorow.

I wish I could be of further help. We never did any probing, and we used Format 1. I will say though, the Fadal manuals are quite good. Perhaps it gives you the answer.

You could save an operation to your ops library that has the comp set to Computer. Then when you want a new contour toolpath, import it from your library. Done deal!

Thanks for the link, Pete, because the search feature at this forum is next to worthless.

Oct. 2002, when this topic started, I was a member here for 5 months. I'm pretty sure that Bernie answered my first question on why Mask on Arc wasn't finding all the specified diameters...Screen-Combine Views!!! Just doing some math in my head, I gotta say that Bernie is around 85 these days.

Even Bernie replied to the original question. Bernie has been around so long, his journeyman's card was carved in a stone tablet.

WorkNC has a dental module.

Fissed.

Agreed, it was a nice video. Great job mwearne! Thanks to Josh for his great video as well. I was just looking to get a laugh out of you guys, that's all.

This sounds really familiar, but I can't quite put my finger on it.

I can't say for certain, since I'm still using X9, but I have a feeling you're going to be disappointed. Not that it can't be done (create a circle/arc that is tangent and translate the solid between points), but I don't believe there's an easy button for that in MC. AFAIK, MC doesn't have mating features like other design packages have.

Thanks for that info, Ron. I wasn't aware of the 2021 solids issue. I requested to have 2021 installed 7 weeks ago. Still waiting.

Ron, are you saying that in later versions that when all toolpath display is turned off, then stock model display is turned off also?

Since it's controlled by the view toolpath controls, I wish it would not show up if all the other toolpaths are toggled off.

Thanks guys!

Can someone tell me how to hide the stock model? After the first rouging toolpath, it's in the way and I want it gone from the graphics view.

@skyking01x @carryinwood I'm curious to know how this works out for you. Way back when, we used Fadal Assist to send programs to/from the machines. The Emulator was fun to goof around with at home. It was like having a Fadal control on your home PC. It was a good way to learn your way around all the different features of the control...the various geometry tools, etc. Today, I guess you'd either need a really old computer to use it (which would probably be hard to maintain) or maybe rig something up with DOSBox.

Of course! lol

PM me your email address and I'll get it to you in the next day or so.

I have the Fadal probe macros.

Please tell us what "Fadal Digitizing Software" is and does. I'm not familiar with that name but I ran Fadal's in the 90s and I was able to "backup" some Fadal software. I just may have it.

That's because it is antiquated.

Lots of good info here.