Tools, old Tool, new ToolBit and other fun stuff

[memfis]

IMHO, letters (names of sizes, their explanations) in the tool sketch file are secondary, the more important is the task file of fctb tool, and there the less letters = the better.
And given the fact that the Earth is round and there are many languages, a large number of letters can complicate perception (language barrier) - the ability to see a sketch of each tool and directly in it to compare the terms and their understanding by the author = a big deal. And translations can be quite bizarre - sometimes you even need to take a sip of wine to understand correctly.

It is not difficult to create a tool - it is just a file of the tool model, the rules are clear and without words. That's how to make a program slip this created tool (in the appimage version) - this is a question I haven't managed to solve yet.

Also for now, since only endmill is included in the appimage, I didn't understand if I could see the real result of material processing in "Visualization".

In the meantime, apparently, the only way is to edit the appimage -
https://www.freecadweb.org/wiki/AppImag ... _AppImages

[roerich_64]

Hi @mlampert,

i play also with an appimage on Linux Mint... see above

My preferences are now:

preferences_II.jpg (63.8 KiB) Viewed 1297 times

The experimentals are on:

eperimental.jpg (101.01 KiB) Viewed 1297 times

Take the tools from Github to here:

Tools.jpg (60.57 KiB) Viewed 1297 times

But when i will create a new tool with the toolmanager:

NewTool.jpg (122.04 KiB) Viewed 1297 times

I can not select a shape...

How can i activate them?

[memfis]

Hi, @roerich_64 -

How can i activate them? -

maybe it's here? -

[memfis]

Yay, I was able to see the tool that was created. But next = trouble.
You should also learn how to launch it in the mode that uses all the processor cores.
I made a sketch, pressed the button "create a task". I set the workpiece. Then on the Tool tab I load the library, there I choose my new tool - it rustles and loads as a separate object, the defaults tool remains unchanged. The path along the edge line creates only with default tools, the new tool is not visible there.
It allows you to drag the 'new tool' object into def-tools place with the mouse, and at the same time it replaces it (d-t in this case leaves the task, see the file), is automatically replaced in the created path and everything breaks down - produces the error 'FeaturePython' object has no attribute 'ToolNumber'. The history is repeated with the standard (not mine) tool as well.
What am I doing wrong?

[memfis]

and I think it would be wise to set zero in the z-axis of the tool model at the tip of the cutter, not at the tip of the shank. I'll remake it at my place tomorrow.

[roerich_64]

Puh...
It's really complicated to follow them...

Now, will add the 'Last Path'- stuff... to the 'Parameters'... hope that activate anything...

[roerich_64]

Now the newest:

Code: Select all

OS: Linux Mint 19.2 (X-Cinnamon/cinnamon)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.19107 (Git) AppImage
Build type: Release
Branch: master
Hash: ad952191297fe53593c4d4b0ac80b43fd6664b22
Python version: 3.7.6
Qt version: 5.12.5
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: German/Germany (de_DE)

The 'Parameters':

parameter.jpg (139.4 KiB) Viewed 1267 times

But still nothing:

NewTool_II.jpg (137.06 KiB) Viewed 1267 times

One man around the world play with it... The others not... sorry, but i am very frustrated...

Will help for testing...
but when it was so complicatet to activate anything...
So what should i say???

Walter

[mlampert]

Will help for testing...
but when it was so complicatet to activate anything...
So what should i say???

Thanks, it looks like you enabled the new tools, so the only way to get to the old tools and tool libraries (I am aware off) is by editing an existing job, or creating a job from a template which references old tools. In cause you do neither one of them, could you describe step by step how you got to the legacy tool editor? (and I see the legacy tool library manager in the background - very concerning)

[mlampert]

What am I doing wrong?

AFAICT you're trying to use the ToolBit directly in the job. You still need to create a ToolController to wrap the ToolBit so it can be used in a job. This is where the ToolBit gets a number for the tool changer (if you have one) and where the feeds and speeds are set.

[chrisb]

and I think it would be wise to set zero in the z-axis of the tool model at the tip of the cutter, not at the tip of the shank.

I don't think so at all. When you have different tools, they would have different zeros .