![]() That would be pretty kick ass, I think it covers everybody's needs! Now. So you get the starting S&F that came with the tool, and add presets in the assembly itself. And on top of that, each assembly could have their own S&F added, because holder plays a role in that too. ![]() I like the generic S&F attached to the tool. this allows customized speeds for the independent projects, but still could have a solid starting parameter that i have made myself. Then instances of the cutter would be implemented with an option to keep or break the link to the parent entity. Next level would just break down between tool and holder, with all physical data included, along with some sort of generic speeds and feeds for the cutter. So you have many kind of scenarios to deal with, hopefully something can satisfy all/most level would be assembly I hope this clarifies why I would like to keep the link between tool and holders we don't assemble tools every time as per OP. We have duplicates of our machines, so the tools are mirrored between them. Most of our machines hold over 200 tools each, and they pretty much stay in the machines. ![]() If you don't want this behavior, you would simple create a new tool instead of updating an old one.ĮDIT: after reading the previous answer from OP, I need to clarify something: for us, we have machines with permanent tools. So let's say you have a 3/4" rougher with 4 flutes, and one day you decide that you want to get a 7 flutes to replace that 4 flutes one, the assembly referencing the old tool should now all update to the new tool. If a tool and/or holder gets modified, all assemblies in the cribs get updated with the new data, because really, the assembly should just be a link between a tool and a holder, with the stick out value added only in the assembly. A proper assembly would ask you to pick a tool and a holder and keep the link to them. At the moment, you do have tools and holders, but you don't pick the tool when you create an assembly, you have to copy the tool over and pick a holder, and it's a copy, there is no link to that original tool. It would be great if it would work exactly like a physical tool crib, meaning that you have tools, you have holders, and you put them together (assemblies). Sorry to barge in, but since you are talking about tool cribs, if I may: Just hoped to add my 2 cents in case it sparks an idea or sounds solid enough to look into as is! I apologize that i havent looked to see what exactly the wonderful team in charge of the tool library has planned, they potentially already have this figured out, or have even better ideas than my 5 minute rant. maybe even a solid idea to have a global speeds and feeds type of feature, where you want to copy the specified speeds and feeds to any machine that has that particular tool linked. and to take it 1 step further to add the already available speeds and feeds for seperate materials, or finishes for different materials. Got me thinking, that it would be nice to have a master tool library where you just enter all global data, to get a physical representation of the tool, then i should be able to setup a library for a machine with its own speeds and feeds for any tool i pick to add to that machine. we only really have 3 different mills so its not a huge job to convert over. Had the idea to switch from my current setup where i have 1 tool library with all my common tools, numbered 1-199, and swap it with a dedicated library for each machine. Even though PCBN and ceramic inserts make it possible to achieve the highest material removal rate, breakages can be a problem in the most demanding applications.Had some extra time this afternoon to fine tune my tooling libraries. ELIMINATE HOLDER BREAKAGE WHEN ROUGHING WITH PCBN AND CERAMICS Brittle inserts can sometimes break, often taking expensive toolholders with them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |