I said to use integer or float for angle type properties. A better idea is to just use the 'Angle' type property. I can't believe I overlooked that. Please forgive the brain-fart.
I have been learning FreeCAD for about 6 months and always find you video's to be excellent. Your teaching style is easy to follow. Keep up the good work.
So glad you're doing more videos on FreeCAD Path. This is an awesome feature that is needed by many but FreeCAD simply needs more good tutorials so idiots like me can follow them to figure out how to use it. I am looking forward to a point a couple years in the future when FreeCAD will be more polished and ready for prime time. It's pretty awesome so far, but I tend to hit a brick wall a little too often, so I keep falling back into tools I'm a bit more familiar with. I really want to get to the point where I am good enough at FreeCAD that I can just count on using it all the time. Thanks a TON for your contribution to the software and big thanks for your videos too, which are very well done.
Yeah a great video from the Guru Master. One small problem - The icons and pointer are so small you loose track many times of what is going on. With bigger icons and bigger and bright red pointer you will have the best CAD videos. Thanks for your help.
Biggest danger in using FreeCAD's Path Workbench is the lack of tool holder geometry setup/identification, especially with regards to collisions. That's an area that needs a lot of development still. Having said that, I'm amazed at all the wonderful features packed into the Path Workbench. Thank you so much for all the work being done on this CAM workbench.
Thank's for a great video. I've watched it 5 times and thought I followed your every instruction, but when I go to add the tool to a path job I get error messages. I'm running Freecad 20 on a MacBook Pro 2020 with Monterey. Is the process different for FreeCad 20?
I just went through doing this to create a tiny vcarve bit. I kept getting an error until I placed the fcstd file in the tool library shape folder. Then I could save the fctb anywhere. Not sure if I'm doing something wrong here. .20 version. Actually still can save it. Now I can get to attributes but when I close it disappears.
Hi Vitus, I think I just replied to you via email. I'm afraid I'm not in a position to take a job at this time but a conversation might be in order anyway. Hope to hear from you.
i see you are a freecad path specialist - so did you ever worked with freecad and a 5 Axis milling machine - means is freecad capable to generte the gcode for 5 Axis
It's something I've been working on (slowly). The problem is difficult for several reasons. First, I need a machine that I can learn and test on. I've never used 5 axis in production so I need to understand the workflow and assumptions of 5 axis machining. For example, I spent the last couple weeks learning about Tool Center Point (TCP) kinematics and tilted work planes. There's a lot to learn and I need to understand it pretty well before I can do anything interesting in Path. The actual work to be done in Path is very large. All the existing operations in Path have to be refactored to remove the 2.5D assumptions. New toolpath generation functionality has to be written. The GUI has to be changed to support it without breaking the current functionality. The postprocessors have to be rewritten to support the new gcode. Visualization and simulation need to be written. Unit tests have to be written for all the new logic. All that is just to get to 3+2 milling. Continuous 5 axis machine paths are still a long way in the future. I have a Patreon account. Those people are actively helping me to work on Path and I'm grateful. With that money I was able to buy a small 4th/5th axis rotary table for my mill. I'm still working to get it to do TCP kins but I'm close. I would like to work on multi-axis features more. Unfortunately, I also have to earn a living.
I said to use integer or float for angle type properties. A better idea is to just use the 'Angle' type property. I can't believe I overlooked that. Please forgive the brain-fart.
I have been learning FreeCAD for about 6 months and always find you video's to be excellent. Your teaching style is easy to follow. Keep up the good work.
So glad you're doing more videos on FreeCAD Path. This is an awesome feature that is needed by many but FreeCAD simply needs more good tutorials so idiots like me can follow them to figure out how to use it.
I am looking forward to a point a couple years in the future when FreeCAD will be more polished and ready for prime time. It's pretty awesome so far, but I tend to hit a brick wall a little too often, so I keep falling back into tools I'm a bit more familiar with. I really want to get to the point where I am good enough at FreeCAD that I can just count on using it all the time.
Thanks a TON for your contribution to the software and big thanks for your videos too, which are very well done.
Yeah a great video from the Guru Master. One small problem - The icons and pointer are so small you loose track many times of what is going on. With bigger icons and bigger and bright red pointer you will have the best CAD videos.
Thanks for your help.
Good point! I'll work on that.
I think your videos are going to be indispensable to me in the future.
thank you for your time to teach..
Biggest danger in using FreeCAD's Path Workbench is the lack of tool holder geometry setup/identification, especially with regards to collisions. That's an area that needs a lot of development still. Having said that, I'm amazed at all the wonderful features packed into the Path Workbench. Thank you so much for all the work being done on this CAM workbench.
Nice tutorial! Thank you!
Thank you for your excellent work!
Thank's for a great video. I've watched it 5 times and thought I followed your every instruction, but when I go to add the tool to a path job I get error messages. I'm running Freecad 20 on a MacBook Pro 2020 with Monterey. Is the process different for FreeCad 20?
I just went through doing this to create a tiny vcarve bit. I kept getting an error until I placed the fcstd file in the tool library shape folder. Then I could save the fctb anywhere. Not sure if I'm doing something wrong here. .20 version. Actually still can save it. Now I can get to attributes but when I close it disappears.
Thank you for the video. This is just what I was looking for.
It would be great if you share a link to the file with the result :)
Great video as always. Does the simulator in Path "recognize" the tool shape too?
In theory it could but that level of simulation isn't supported yet.
@sliptonic great explanation! you are truly a freeCad path specialist would you be open to be hired ?
Hi Vitus, I think I just replied to you via email. I'm afraid I'm not in a position to take a job at this time but a conversation might be in order anyway. Hope to hear from you.
i see you are a freecad path specialist - so did you ever worked with freecad and a 5 Axis milling machine - means is freecad capable to generte the gcode for 5 Axis
It's something I've been working on (slowly). The problem is difficult for several reasons.
First, I need a machine that I can learn and test on. I've never used 5 axis in production so I need to understand the workflow and assumptions of 5 axis machining. For example, I spent the last couple weeks learning about Tool Center Point (TCP) kinematics and tilted work planes. There's a lot to learn and I need to understand it pretty well before I can do anything interesting in Path.
The actual work to be done in Path is very large. All the existing operations in Path have to be refactored to remove the 2.5D assumptions. New toolpath generation functionality has to be written. The GUI has to be changed to support it without breaking the current functionality. The postprocessors have to be rewritten to support the new gcode. Visualization and simulation need to be written. Unit tests have to be written for all the new logic.
All that is just to get to 3+2 milling. Continuous 5 axis machine paths are still a long way in the future.
I have a Patreon account. Those people are actively helping me to work on Path and I'm grateful. With that money I was able to buy a small 4th/5th axis rotary table for my mill. I'm still working to get it to do TCP kins but I'm close.
I would like to work on multi-axis features more. Unfortunately, I also have to earn a living.
Thanks you good 🤩🤩🤩🤩
👌 ρɾσɱσʂɱ