ProfileDepth Problem
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
ProfileDepth Problem
When I set up a new profile the depths are correct but when I change the stepdown it changes the start depth and finish depth.
OS: Windows 10 (10.0)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.23683 (Git)
Build type: Release
Branch: master
Hash: af4de262e326452fd79f036253cf7cac6a7e7e00
Python version: 3.6.8
Qt version: 5.12.1
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/United Kingdom (en_GB)
3.2 was the original stepdown I changed it to .5OS: Windows 10 (10.0)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.23683 (Git)
Build type: Release
Branch: master
Hash: af4de262e326452fd79f036253cf7cac6a7e7e00
Python version: 3.6.8
Qt version: 5.12.1
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/United Kingdom (en_GB)
Re: ProfileDepth Problem
No problems with current pre0.19
Start is always 1mm, Final always 0mm
OS: Windows 10 (10.0)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.23756 (Git)
Build type: Release
Branch: master
Hash: 9c6e9184930a52b165a0b7274e3a45d1006bfe67
Python version: 3.6.8
Qt version: 5.12.1
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: German/Germany (de_DE)
Start is always 1mm, Final always 0mm
OS: Windows 10 (10.0)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.23756 (Git)
Build type: Release
Branch: master
Hash: 9c6e9184930a52b165a0b7274e3a45d1006bfe67
Python version: 3.6.8
Qt version: 5.12.1
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: German/Germany (de_DE)
Re: ProfileDepth Problem
The problem only occurs when you change the stepdown
Re: ProfileDepth Problem
I changed it to 0,5mm. Still no problem
Re: ProfileDepth Problem
The problem only occurs the first time you try the profile operation, only just found that out just uploaded latest still the same.
Note Z0 at bottom need to create a new a new drawing for this to work I have changed the stepdown from 3.2 to .5 OS: Windows 10 (10.0)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.23756 (Git)
Build type: Release
Branch: master
Hash: 9c6e9184930a52b165a0b7274e3a45d1006bfe67
Python version: 3.8.6
Qt version: 5.12.5
Coin version: 4.0.0
OCC version: 7.4.0
Locale: English/United Kingdom (en_GB)
Note Z0 at bottom need to create a new a new drawing for this to work I have changed the stepdown from 3.2 to .5 OS: Windows 10 (10.0)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.23756 (Git)
Build type: Release
Branch: master
Hash: 9c6e9184930a52b165a0b7274e3a45d1006bfe67
Python version: 3.8.6
Qt version: 5.12.5
Coin version: 4.0.0
OCC version: 7.4.0
Locale: English/United Kingdom (en_GB)
- Attachments
-
- test.FCStd
- (30.6 KiB) Downloaded 35 times
Re: ProfileDepth Problem
HI,
i get an error ( if i use toolbits only, if i use legacy tolls it works ) if i make the Step Down bigger as the distance Start Depth - Final Depth is, but it works if the Step Down is smaller.
The additional path apers after recalculate the path, not directly after changing the value
i get an error ( if i use toolbits only, if i use legacy tolls it works ) if i make the Step Down bigger as the distance Start Depth - Final Depth is, but it works if the Step Down is smaller.
The additional path apers after recalculate the path, not directly after changing the value
Gruß Herbert
Re: ProfileDepth Problem
Should I do a bug report on this depth problem or is it just my setup that is at fault. I construct a simple rectangle and pad it , the origin is bottom LH corner Z at the bottom . I go to path workbench setup a job origin already set by sketch. Create a profile operation cut correct on depth box change depth step down. The last cut now moves to the top of the stock this also happens if you press recalculate. I tried redoing the test with setting the origin at the top of the stock set in the job panel. Still the same problem it just cuts above the stock.
OS: Windows 10 (10.0)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.23756 (Git)
Build type: Release
Branch: master
Hash: 9c6e9184930a52b165a0b7274e3a45d1006bfe67
Python version: 3.8.6
Qt version: 5.12.5
Coin version: 4.0.0
OCC version: 7.4.0
Locale: English/United Kingdom (en_GB)
OS: Windows 10 (10.0)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.23756 (Git)
Build type: Release
Branch: master
Hash: 9c6e9184930a52b165a0b7274e3a45d1006bfe67
Python version: 3.8.6
Qt version: 5.12.5
Coin version: 4.0.0
OCC version: 7.4.0
Locale: English/United Kingdom (en_GB)
- Attachments
-
- tes2t.FCStd
- (32.66 KiB) Downloaded 55 times
-
- Posts: 328
- Joined: Tue May 28, 2019 10:51 am
Re: ProfileDepth Problem
No!
It seems likely from your descriptions that you are a fairly new user to Path Workbench, so there are some things for you to learn.
Firstly as Herbk mentioned, the auto calculate of expressions {edit: usually do not occur} until you "after recalculate the path, not directly after changing the value". This can be triggered by the refresh, or OK to the operation, or even by tabbing out of that field. You should also be aware that there is other builtin functionality that automaticaly calculates, for example the final depth. This is be triggered changes to other fields, such as changes to step down as you have observed. However it is NOT pre-calculated when you first open the operation dialog, so it can appear wrong, and if you are not aware of when it is calculated, you may miss the calculated value appear in the field. If you search or browse the forum, you find other posts describing how these changes work and how they are triggered.
In your last file test2t.FCstd, the stock top surface has height z=0, and the operation has final cut depth of z=0. So the operation is cutting as per the parameters that have been set. That file also does not have rapids speeds set in setup sheet.
Additionaly, be aware that FreeCAD does not know the current position of your CNC, and so the first rapid move in the job, will often appear to start inside your stock. But reality is that you position your CNC/tool somewhere safe (ie not inside your stock) and then the CNC mill move from position you set to the end of the read path you seen in FreeCAD. Tool changes will add other moves if present in the job. Again FC cannot know how your machine is setup for toolchanges, so it can't display those moves in the path. These are thing you need to visualise in your CNC control software.
Your earlier posts also some some errors and warnings in the report window. For example, if those "Please select features from a single solid" errors are from the path WB, then these need to be looked at, or yes your path job is likely not to do what you desire!
Please keep in mind that FreeCAD is very powerful and has been around for many years, so it is very capable. Also it is undergoing a lot of changes, so yes sometimes there are bugs, other times the documentation has not been updated, but from my own stumblings, I would say mostly I have not understood the good documentation and often it is me as a user who has not taken enough time to learn the basics. So it is much better to ask for help in understanding a situation. If there is a bug, it will get confirmed in the discussion and you will get prompted to post a report.
Do have faith in FreeCAD, it is a (many!) great tool, but like any powerful tool, it takes a serious learning investment to get up to speed. Again look at the forum, you will find amazing models and real world things people have done with FreeCAD.