NEW Tool Library

[veso58S5W]

😫that's first impression.
What was the reason to change?
Why mess up good things?
How you organize tools? If I want list to be by #. Or by diameters?
Renumber Tool, now I must go through several operations.

[Anonymous]

It would save unnecessary steps when creating/duplicating tools with the same surface speed and feed per revolution.

Everything I do in the cutting data tab could be omitted.

[ltomuta]

@christopher.cooperVHK2N 

 Please populate radius field for ball-end mills. Yes, it defaults to D/2 but ...

I was looking for tools with 2mm radius today and in the filter I had selected both ball-end and bull-end mills (no other filter). Looking at the results with sorting done on "Corner radius" there was no tool with 2mm value. Of course I ignored the 4mm ball mill for which the radius value was not shown.

What's worse,  if I specifically filter for "Corner radius = 2" the ball mill is also not shown because the value is not in the database.

[christopher.cooperVHK2N]

@Anonymous Yes I understand now. I think this improvement will be beneficial and  will take a look at it this week.

Thanks

[mattdlr89]

I think it would be good if there were more "Tool Categories" on the filter option at level 1. For example I want to find a tap in my tool library but I have to click Hole making > tap. Why make something 2 clicks when it could be done in a single click. Only minor but would smooth the workflow nicely...

In addition would be nice if that filter was smart based on the library selected. In the screenshot below Turning, cutting, probe and holders are all empty. I'd rather it see finer level detail of the tool categories that are in that library. 

Basically the first filter should probably be "type" and then only the types that are present in the selected library visible. 

[FrodoLoggins]

A: Already suggested, no the replys did not suffice:

https://forums.autodesk.com/t5/fusion-360-manufacture/new-tool-library/m-p/9927187/highlight/true#M9...

https://forums.autodesk.com/t5/fusion-360-manufacture/new-tool-library/m-p/9942049/highlight/true#M9...

B: Libraries STILL do not order alphabetically/numerically. Something that was supposedly fixed (twice) over a year ago. Mostly in order today (never this good), but 99 is still bigger than 9:

C: Still unable to reorder speed/feeds templates. Something also that was apparently going to be fixed. A whole year ago. Surprise surprise. It still isn't. Not looking to delete work, have things out of order:

😧 Accounting for chip thinning makes toolpath templates useful, removes the need for 50 different feed/speed templates, saves me from doing math, etc

E: If chip thinning doesn’t get added, add different ramp fields. A helical ramp at 3 degrees will have a different feed than a straight ramp. A zig zag with corner radii in stainless steel: My tool’s either breaking around the corner because it’s going too fast or it’ll break going too slow during the straight portion.

F: Escape key to close dialogue, escape again to completely close the tool library. Escape key should never close both.

G: It’s a little slow but I get it.

H: Who thought this was a good idea:

Current job should be the current thing I'm looking at.

I: Make it easier to see what line you’re on:

[ltomuta]

The library should really save the cutting data fields as introduced, saving expressions and relationships.

You may prefer to look at surface speed as a function of spindle speed but if I enter it the other way around and the fx flag moves to the spindle speed field then I expect the relationship to be preserved the next time I have to work with these fields (duplicate of current profile, duplicate of current tool, later edit to current tool & profile).

Similarly, if stepover is introduced as .1*tool_diameter then I expect the same expression be used to calculate the stepover for a new tool I creat by duplicating this one and changing its diameter.

Maybe for legacy/search reasons you also have to store actual values in the database but dropping the expressions is not justified. They should be used whenever possible to override and derive new values.

Also, please add autocomplete for expressions. One can only take so much of typing tool_fluteLenght ( or is it Length? 🙂 ) 

[ltomuta]

When a tool has the tool_stepdown defined in the library, this parameter is used to override the maximumStepdown expression from a templated 2D Contour operation for example. This is not cool as I may have some other clever expression there, one that may or may not use tool_stepdown internally.

I wouldn't just replace a non-factory-default value/expression with tool_stepdown. If I want that parameter used there explicitly I could make it the default. But if I don't, then let my content be.

[gtprototype]

Why is it every time I turn around the preview for the new tool library is turned on? 

I'd love to try out the new features however, as I mentioned before, the font is too small and illegible at 125%.  Here is a comparison old and new:

 Old @ 125%New @ 125%

I thought well maybe at 150% I could give it a try; here's what it looks like, see any difference from 125%?  I couldn't either.New @ 150%

Another significant noticeable difference is the scroll slider.  On the new tool library it's so small that if you have the slightest hand tremor you're gonna have one heck of a time unless you turn the resolution down on your mouse.

When I first started with CAD small text and hidden or drop down menus made sense because everything had to fit on a tiny monitor.  Considering the giant monitors and or multiple monitors in use today, why is the development team trying to reclaim workspace by making things smaller and hidden, or what is their goal?  Seeing how eye site and motor skills degrade with age, is AutoDesk fostering discrimination?  I'd really like to know: what is the goal?

[quadfluiddynamics]

I feel my blood start to boil every time I use this "New Tool Library" ! Go back o the old tool library.. This has too much junk on it.. Why  have set drill,end mill, and other tool sizes? This is terrible!

[mattdlr89]

@christopher.cooperVHK2N 

I noticed a small bug yesterday (not sure if this has changed since the update or always been a problem). When renaming the tool libraries you cannot scroll left or right with the arrow key. Present on Windows and Mac. 

Also as been brought up before the sorting/order of cloud libraries keeps going awry. Yesterday they were all in order apart from the one at the to being put at the bottom. I changed it so the one I wanted at the bottom should be at the top and it ordered how I wanted. Got back to it this morning and now they're ordering correctly so the one I wanted at the bottom is back at the top. Not a big problem but would be nice to have reliable alphanumerical sorting. 

[christopher.cooperVHK2N]

@mattdlr89 Thanks for posting. The issue re Cloud libraries and arrow bug on rename has been addressed and you should see these in the next release.

Thanks

Chris

[mattdlr89]

Hi @christopher.cooperVHK2N 

Using arrow keys on rename of a tool library is not working for me. 

I can use arrow keys to go up and down the library tree but if I right click and rename I cannot use left/right to scroll my cursor. Not that the screen shot really shws much below but pasted anyway - The cursor was right of the 's' in library and if I want to move it I can only do it with the mouse. 

This is fine when edit text fields in the tool dialog etc it's only the tool libraries.

Version details:

2.0.9849
Active Plan: Fusion 360, Subscription
Windows 10 (19042)

[christopher.cooperVHK2N]

@mattdlr89 You wont see the change yet. It should be the next release. Sorry if it wasn't clear in my first response.

Thanks

Chris

[mattdlr89]

Yeah I now realise didn't really read your post correctly 🙄! Thanks for the responses. 

[raymus.houston]

@christopher.cooperVHK2N 

I'm running into an issue in the new tool library related to form tools. When I define the profile, tool axis and compensation point, the tool's tip offset is being set to the farthest point away from the intended lowest position. In the old library you could manually type in a tip offset value so it wasn't a big deal. There isn't a field to specify the tool tip offset in the new library despite the parameter still being listed in the tool data. See the image below with the tip offset point circled as well as the tip offset value.

[seth.madore]

@raymus.houston this is a known bug and you will see a fix for it in an upcoming release 🙂

[ltomuta]

---

@ltomuta wrote:

Once I define a shoulder length higher than flute length all the shaft customization is done above the shoulder. See below  the two segments I need to be below the shaft, they are modeled above it.

Here shoulder length = 30, flute length = 4

Only if shoulder length = flute length = 4 the segments are modeled in the correct position

---

Defining a new mill today, I got the same issue as above plus the bonus of a thin disk right above the flutes. A rounding issue somewhere or a new enhancement of the old bug?

[ltomuta]

Nice new improvements released today. Theoretically.
When trying to to as much as a tool copy or even tool select I run into 

[MatthewPBryant]

Hi @ltomuta, 

Thanks for your post and sorry to see you're having issues with the update! I can't reproduce the issue you're seeing here - could you provide a few more details to help us find the issue, please?

• What version of the tool library are you using? The version number is shown in faint text in the bottom left corner.
• What are the steps you're following to get this error? In particular, where are you copying tools from and to, how many tools are you copying, and are you copying using right-click copy/paste or by dragging and dropping?
• Would you be happy to send a copy of the tools/libraries you're copying from/to? You can export them to JSON by right-clicking and selecting 'Export library'.

Thanks, 

Matt

[ltomuta]

I'm sure if you search a bit around you will find other instances of this problem being reported. This is not a new bug. Usually it goes away after a Fusion restart. This time it took two restarts for the problem to go away.

When this happens, usually there's also the "Unable to select tool" error (which I guess is caused by the same "copy to document library" base-64-encoding error although the tool library does not show it as such).

In this particular case I was just trying to copy one tool from our "all tools" library to the "most used" library, for easier selection. Both library files are old, tried and tested. The tool itself added ages ago and used a lot, so not subject to some error in tool definition possibly caused by recent changes. 

Tool library version is 1.15.1. The issued showed up right after the "restart to update" to the most recent Fusion release.

I can send you our tool libraries but I'm afraid it would not help unless we somehow manage to find how to trigger the bug. It only shows-up at random and right now, after the two consecutive restarts, copy/pasting the tools works like a charm.