Units for feedrate
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
-
- Posts: 395
- Joined: Fri Oct 07, 2011 8:58 pm
- Location: Beaverton,Oregon, USA
- Contact:
Units for feedrate
I still use imperial units for CAM and would like to bring something up about feedrates- in the property panels it seems that there is only 'mm/s' for feedrates for Path operations.
I submitted a bug report on Mantis about this:
[bug]https://www.freecadweb.org/tracker/view.php?id=2890[/bug]
In the past, I think we ignored the units in the feedrates entries in the property panels for operations, but we really should figure out how to fix it. I know it's probably deep in the units source somewhere in the main FreeCAD App directory, but I did a little grepping and can't seem to find where 'mm/s' is coming from.
I submitted a bug report on Mantis about this:
[bug]https://www.freecadweb.org/tracker/view.php?id=2890[/bug]
In the past, I think we ignored the units in the feedrates entries in the property panels for operations, but we really should figure out how to fix it. I know it's probably deep in the units source somewhere in the main FreeCAD App directory, but I did a little grepping and can't seem to find where 'mm/s' is coming from.
Re: Units for feedrate
I think the feed rate is just a number and whatever unit the post processor sets is what is being used.
-
- Posts: 395
- Joined: Fri Oct 07, 2011 8:58 pm
- Location: Beaverton,Oregon, USA
- Contact:
Re: Units for feedrate
That is true, so maybe the solution is to remove "App::PropertySpeed" from the property panel entry boxes and use "App::PropertyFloat" instead.mlampert wrote:I think the feed rate is just a number and whatever unit the post processor sets is what is being used.
Re: Units for feedrate
Gotcha' - good point.danielfalck wrote:That is true, so maybe the solution is to remove "App::PropertySpeed" from the property panel entry boxes and use "App::PropertyFloat" instead.
Re: Units for feedrate
I updated the bug.
Just for my clarification, do you have the global unit options in FC set to metric or are those also in imperial?
Just for my clarification, do you have the global unit options in FC set to metric or are those also in imperial?
-
- Posts: 395
- Joined: Fri Oct 07, 2011 8:58 pm
- Location: Beaverton,Oregon, USA
- Contact:
Re: Units for feedrate
I have set my global prefs to imperial.mlampert wrote:I updated the bug.
Just for my clarification, do you have the global unit options in FC set to metric or are those also in imperial?
Re: Units for feedrate
Interesting, sounds like a bug in InputField. Maybe an oversight of not handling speed according to the global unit and just assuming the default.
-
- Posts: 395
- Joined: Fri Oct 07, 2011 8:58 pm
- Location: Beaverton,Oregon, USA
- Contact:
Re: Units for feedrate
I can eradicate all instances of "App::PropertySpeed" if no one objects
Re: Units for feedrate
I don't understand the consequences, so how could I object? If it is without units I don't see any problem. If it uses units, can we assure they are conforming to the settings in the post processor? Or is it the other way round: the post processor has to be configured so that it matches the units used in the path?danielfalck wrote:I can eradicate all instances of "App::PropertySpeed" if no one objects
A Sketcher Lecture with in-depth information is available in English, auf Deutsch, en français, en español.
-
- Posts: 395
- Joined: Fri Oct 07, 2011 8:58 pm
- Location: Beaverton,Oregon, USA
- Contact:
Re: Units for feedrate
The only indicator that there are units involved is in the property panel that has 'mm/s' attached to the entry box for the feed rate. I found that I was having to multiply my desired feed rates by 25.4 to get them to come out to the proper output with my centroid post processor. I had created a function to filter/convert feed units in that post.chrisb wrote:I don't understand the consequences, so how could I object? If it is without units I don't see any problem. If it uses units, can we assure they are conforming to the settings in the post processor? Or is it the other way round: the post processor has to be configured so that it matches the units used in the path?danielfalck wrote:I can eradicate all instances of "App::PropertySpeed" if no one objects