nice, so happy to see these new forums, tied up with work for a few days but i definitely have some interesting topics that i wanted to start on here soon! Love that we have this new forum because its going to be awesome to share some ideas and get others ideas on things, i of course use mastercam for all of my modeling, stl/mesh editing, etc and from there prusa slicer. i have an ender 3, hate this printer and most likely gonna replace it with a Bambu labs printer soon, i also have a prusa mini with upgraded extruder that i get great result with and really like the printer, before the upgrade to the extruder it was so/so but with the upgrade it does spectacular at almost everything ive thrown at it and except for the slowness (comparing it to bambu) and small print volume i think its great. Looking forward to getting my hands on one of a Bambu some day soon. also i hope everyone knows this but you can use the Mastercam HLE to make .stl files and .3mf files for 3d printing without having a full license, thanks to everyone at mastercam for letting this be possible, its a great way to stay sharp with the softwares cad tools and i think its a great thing that they let it be used for that at no cost, great way to get it into students hands as well and thanks Emastercam team and Daniel for starting this forum!

Verify > Collision Checking > Collision (Tiny little button), opens up the Collision Detection Options window

This information is of extremely high value to me. I can't get enough keyboard shortcuts, the unabashed speed vs menu cruising or hover-waiting makes me all tingly.

are the collisions happening on flat surfaces? do you have micro lift enabled? a file was posted here a couple of months ago with collisions using dynamic mill and a ball endmill what was happening was that the ball endmill was leaving cusps on horizontal surfaces and the endmill was rapiding through the crests of the cusps during backfeed motion enabling microlift with a lift value higher than the cusps, eliminated this issue.

^^^this^^^ ..preach it to the people..

In this link, it's "Fix 2": https://www.inhousesolutions.com/resource/cannot-find-parasolid-data-in-solidworks-file/ In case that link or video goes down: Start Menu Mastercam (version) Advanced Configuration Components Browse to C:\Program Files\Mastercam (version)\Mastercam\common\SWORKSDATA\SwDocumentMgr.dll Right-click "Unregister Component" Right-click "Register Component"

Thanks Colin, I got it to work with the following code. Not pretty, but it does the trick. str_testTool : "" #Empty String str_warnTool : "" #Empty String str_testComment : "" #Empty String str_warnComment : "" #Empty String str_CheckComment : "" #Empty String ptoolCharacterCheck str_testTool = no2asc(33) #no2asc(33) #Convert ASCII Code decimal value to ! string representation pstr_testTool str_testTool = no2asc(40) #no2asc(40) #Convert ASCII Code decimal value to ( string representation pstr_testTool str_testTool = no2asc(41) #no2asc(41) #Convert ASCII Code decimal value to ) string representation pstr_testTool str_testTool = no2asc(176) #no2asc(176) #Convert ASCII Code decimal value to ° string representation pstr_testTool str_testTool = no2asc(177) #no2asc(177) #Convert ASCII Code decimal value to ± string representation pstr_testTool pOperationCommentCheck str_testComment = no2asc(33) #no2asc(33) #Convert ASCII Code decimal value to ! string representation pstr_testComment str_testComment = no2asc(40) #no2asc(40) #Convert ASCII Code decimal value to ( string representation pstr_testComment str_testComment = no2asc(41) #no2asc(41) #Convert ASCII Code decimal value to ) string representation pstr_testComment str_testComment = no2asc(176) #no2asc(176) #Convert ASCII Code decimal value to ° string representation pstr_testComment str_testComment = no2asc(177) #no2asc(177) #Convert ASCII Code decimal value to ± string representation pstr_testComment pstr_testTool result = strstr(str_testTool, strtool$) #Test string for character assigned with no2asc if result <> 0, [ str_warnTool = "BAD CHARACTER " + str_testTool + " FOUND IN" + " T#" + no2str(t$) + ", TOOL COMMENT IS " + strtool$ + " NAME." + " PLEASE FIX COMMENT AND REPOST!" result = mprint(str_warnTool) ] pstr_testComment str_CheckComment = scomm$ result = strstr(str_testComment, str_CheckComment) #Test string for character assigned with no2asc if result <> 0, [ str_warnComment = "BAD CHARACTER " + str_testComment + sbubbleinfo + " FOUND IN OPERATION " + drs_str(2,opnumber) + ", COMMENT IS " + str_CheckComment + " PLEASE FIX COMMENT AND REPOST!" result = mprint(str_warnComment) ]

Just a quick post to get us started. I've been printing since 2012, building then purchasing a succession of printers. I currently have a Prusa i3 MKS & a Bambu X1C.

Thanks for the input! After a lot of messing around I got the angle head to work the default mill post and my 5 axis post. The key piece of information I was missing was a setting in the control definition under work offsets called translate NCI coordinates to machine view with aggregate. Once selected Mastercam posted out the proper code.

The box stock setup sheets can give you a good start. I spent way too much time before I found out about the better options out there. The best advise is already been given, but the active reports can get you something that may work.

For a simple tool list, you can select your operations, in the Toolpath manager, right-click (with your cursor in the Toolpath manager) and select Tool List.

I used HSM Advisor yesterday on a project I am working on. I have a 25mm 4 flute Sandvik indexable screwed onto a heavy metal shank that I am using to side mill the cheeks on a crankshaft with. Normally I would run it at .004 a tooth and 475ish sfm. That is where I started at. It worked out to be 40 IPM and 1900 RPM. This particular crank is a 6 cylinder so I had 6 pins to play on. HSM Advisor suggested 76 IPM and 2100 RPM. I took the advice offered here and started at my normal speed and feed and adjusted up each pin. I ended up at 72 IPM and 2100 RPM. The only reason I didn't get to 76 like HSM Advisor suggested was that I ran out of pins. I will try it on the next crank. Of course surface finish suffered as I increased feed rate, as expected, but for what I am doing, it doesn't matter on this op. I was able to take a solid 4 mins of cycle time out, which will work out to over 24 mins a crank from my baseline. Time is money as we all know. 24 mins times 30 cranks and HSM is priceless. This is just one op. It has paid for itself already and stuck money back into the companies pocket. This has really got me thinking about my approach to, well, everything. There are other projects that I want to go back and re-apply this on now. I have a dynamic milling project I am probably going to do today or tomorrow in a horizontal cat 45 mill so I will get the chance to play more on HSM Advisor then. Thank you guys for the info, feed back and help. This place is awesome and I read here everyday. I always seem to pick up something new and it makes me think daily.

I was kidding but this things claims to have 50 buttons. I don't see them all though. https://www.theverge.com/circuitbreaker/2016/7/1/12078740/z-mouse-swiftpoint-kickstarter-pivot-game

opinfo 75003

Why I have a job.

Using Save Some, change the Save-As type to Parasolid (the native kernel Mastercam uses). This removes all Mastercam-specific items such as viewsheets/etc, while leaving the entities intact and untranslated, and the file can be opened directly in Mastercam. When saving out to STEP and reimporting, in the background you're changing the data format from parasolid to STEP then back to parasolid, which can induce translation errors.

No it has been requested and rejected.

Shooting in the dark without a file... Usually I'll see this collision when the tool hits the stock while plunging in preparation for the entry motion. Try increasing z clearance on the entry motion and see if that fixes it.

Some Google and YouTube searching showed me information about a SwDocumentMgr.dll file. I reregistered it and all is well.

I use mine to make stuff for my tool box, chess pieces, broken toy fixes, gun parts, etc... Gun stuff gets Colorfabb XT CF20. I use a hardened steel nozzle when printing for it.

I have a Prusa i3 MKS. We got it in May of 2019. Yes, THAT May.

I have an Amazon ender 3 clone

Found It!!! Not sure how I unchecked this, but it stays modal depending on it's status.

I'm just getting started on my journey here at Vector.. I picked up a pretty heavily modified Creality from a friend that already had all the goodies done to it (rails, upgraded grantry, extruder, bed, etc., etc.). I've been using it for rapid prototyping fixtures to proof concepts for customers. It's been very handy. Also handy to have around the house to fix random bits that break (washing machine knob), or make halloween costume parts

DM me your machine's parameters. When FANUC installs options, they DO NOT configure the parameters for the machine. That is the builder/dealer/end-user's responsibility.

Pressing the Ctrl key, on your keyboard switches between modes.

Hey Tim, Process Hole works by matching Solid Hole forms (and segments of a hole) between the template file and the part file you're using Process Hole in. Because of this, the selections you make in a template file need to be tied to Solid Hole operations, or they're just ignored by Process Hole as invalid processes for a template file. (This helps you use any part file as a valid template file, and filter out any toolpath groups or operations that aren't part of the template process you would want to use.) This solid hole selection distinction can be subtle and it's one of the things we're working to improve in Process Hole. So, simple change to make it all work. Here in your template file, you've single-clicked and selected solid faces (no intelligence) for the features the toolpath is acting upon: Instead, double-click to select the actual solid hole (intelligence, knowledge of the solid operation and all segments of the hole). Take a look at the differences in the Toolpath Hole Definition labels and name. The Type is now signified as (Solid Hole) and the name of the feature is the name of the solid hole operation.

This link will take you to all of In-House Solutions training material https://www.inhousesolutions.com/training/mastercam-2024/

Hello Josh, Good idea! I have created a new 3D printing sub forum that can be found here: https://www.emastercam.com/forums/forum/40-3d-printing/ To navigate to it, it's in the Mastercam Forums, underneath Machining, Tools, Cutting & Probing

Yeah, Eldar is genius behind HSM works. In my opinion-based rating, HSM is world ahead of GWizard, at least it was when I evaluated it a while ago. And the problem with surveys like this is: How did you reach your test audience? Is the survey you're hearing about representative of people who still have a land-line and answer an unknown number's call? Yes? Well, then, I'm questioning the results...

I dont have 2023 loaded anymore, but in 2024 - Dynamic OptiRough for Example on the tool page there is Tool Inspection with distance or time options.

Who supplied the post? What process did they say needed to be used for using the RAH? If the post builder didn't build the post to support a RAH then you are not going to get it to work like you're thinking. Might can lie to it to get it to work, but if you want to go about it the correct way then need to have your post builder add this logic to the post.

We have just posted our updated 2024 training material on our website. See this link to download https://www.inhousesolutions.com/resource/mastercam-2024-training-links/

Pretty rude to post something so outlandish without a link...

Oh, I wasn't being naive enough to think I could get them to buy useful tools, I meant convincing them of the use of proper feeds, speeds, depth of cut, and stepover in dynamic milling operations. Okay, their website gave me a giggle... >>Ideal for more powerful machines such as HAAS In what universe? I work in a shop full of Haas, and it's like driving the plastic barbie jeep in the Baja 1000.