Am ordering an MR-1 next week and am preparing F360 in my free time. I’ve imported the tool library and post. Are there any particular sections of the machine configuration I should pay attention?
Thanks,
Corey
Others may have different approaches, but I dont use machine configuration.
Save the tool library as a cloud library (if you use F360 on multiple computers), but build a second library. Copy / Paste tools out of online sources into your “owned” tools so you dont have to look at tools that you dont have access too. After testing YOUR tools in YOUR machine on YOUR materials, save the cut parameters.
This will make finding what you want much faster.
I’ve also found saving common toolpaths as templates a huge time saver, especially for things like tapping holes. the template will have everything saved (tool, cut parameters, heights, etc.) and you can add it as a tool path, then just select the appropriate geometry.
I actually run 2 cloud libraries - one is for testing tools, and once they have been tested I move them to a production library. Being cloud libraries allows me (and my coworkers) to all use the same set of tool parameters, and if an error is found in one (and fixed) it will be available everywhere.
Having a basic model you can insert of your vice / work holding can be useful if you are running close tolerances and need to check for collision avoidance.
This Post Processor (by another forum member here) is a tad better for starting out, it fixes a bug with units when splitting a file. It is also the basis of my post processor that is slowly under development.
1 Like
Thank you for the reply.