Linuxcnc - s-curve acceleration? (7176e)
05 Aug 2018 23:23 #115654
by grijalvap
Replied by grijalvap on topic Linuxcnc - s-curve acceleration? (7176e)
Is anybody we can pay for, if yes maybe we can start a donation campaign or even a Kickstarter campaign to get money to pay for this development.
what do you think?
what do you think?
Please Log in or Create an account to join the conversation.
17 Aug 2018 00:06 #116189
by grijalvap
Replied by grijalvap on topic Linuxcnc - s-curve acceleration? (7176e)
No comments?
Please Log in or Create an account to join the conversation.
15 Apr 2019 23:53 #130949
by warreng
Replied by warreng on topic Linuxcnc - s-curve acceleration? (7176e)
Sorry, my post is not any kind of update. But instead a question. I'm curious about how many of the "advantages" of limited jerk acceleration processing can be compensated with G-code. I'm sure my naivety is showing...
When I first started using Fusion360 to write toolpaths for an older commercial CNC router (instead of ArtCam) I immediately noticed a different personality to the motion. I would think that if your G-code is coarse then your only hope for smooth motion and optimized acceleration is for your controller to manipulate the situation. But if the G-code is more data dense then I can imagine that the bigger acceleration booboos can be handled right at the start. Any comments that might help me understand this more completely?
When I first started using Fusion360 to write toolpaths for an older commercial CNC router (instead of ArtCam) I immediately noticed a different personality to the motion. I would think that if your G-code is coarse then your only hope for smooth motion and optimized acceleration is for your controller to manipulate the situation. But if the G-code is more data dense then I can imagine that the bigger acceleration booboos can be handled right at the start. Any comments that might help me understand this more completely?
Please Log in or Create an account to join the conversation.
16 Apr 2019 16:09 #130985
by PCW
Replied by PCW on topic Linuxcnc - s-curve acceleration? (7176e)
CAM and the actual chosen shape of machined surfaces can have a direct effect on the acceleration and jerk profiles.
If you consider constant surface speed machining, the actual curve you are machining
entirely determines the acceleration and jerk , as long as you don't exceed machine
constraints, the CNC's trajectory planners jerk/acceleration limits have no real effect.
If you consider constant surface speed machining, the actual curve you are machining
entirely determines the acceleration and jerk , as long as you don't exceed machine
constraints, the CNC's trajectory planners jerk/acceleration limits have no real effect.
Please Log in or Create an account to join the conversation.
16 Apr 2019 17:13 #130989
by cmorley
Replied by cmorley on topic Linuxcnc - s-curve acceleration? (7176e)
That is the whole point of the planner... you can ask for impossible profiles and it makes them possible by clipping them to as close as the machine is capable.
The better it is at this, then the more aggressive you can be with speed, acceleration and jerk.
Whether your machine needs/can use this performance is a good question.
Chris M
The better it is at this, then the more aggressive you can be with speed, acceleration and jerk.
Whether your machine needs/can use this performance is a good question.
Chris M
Please Log in or Create an account to join the conversation.
16 Apr 2019 19:21 - 16 Apr 2019 19:21 #130999
by PCW
Replied by PCW on topic Linuxcnc - s-curve acceleration? (7176e)
Sure, just pointing out that many time the profile determine these values, not the machine,
though of course the machine determines the tangential acceleration when changing velocity.
though of course the machine determines the tangential acceleration when changing velocity.
Last edit: 16 Apr 2019 19:21 by PCW.
Please Log in or Create an account to join the conversation.
- ihavenofish
- Offline
- Platinum Member
Less
More
- Posts: 686
- Thank you received: 124
07 Jun 2019 22:26 #136257
by ihavenofish
Replied by ihavenofish on topic Linuxcnc - s-curve acceleration? (7176e)
The only time jerk is meaningful i find is in exact stop linear moves. Many arcs and constant velocity moves have what is effectively built in jerk control as mentioned above. Machining a square at high speed and high acceleration with G64 on is smooth as butter. With it off, the floor shakes
So... how hard is it to do jerk control ONLY for G0 and G1 exact stop moves as a starting point? This would cover most real life cases of bad jerk, and only leave a handful of special cases to be dealt with later. It sounds to me many of the previous tries got hung up on trying to cover all motion. I think we should be more incremental about it.
I have a 2000ipm machine with 0.5G acceleration, so jerk control is an important topic for me as the machine endures a lot of stress.
The cases where we will still have significant jerk ( the start and end of some g64 mode moves, shallow arcs in exact stop, etc) are a fair compromise to leave off.
You will still have to tune your aces for the worst case motion situations, but having smooth rapids and linear moves would be at least for me a vast improvement.
Yes, no, maybe?
So... how hard is it to do jerk control ONLY for G0 and G1 exact stop moves as a starting point? This would cover most real life cases of bad jerk, and only leave a handful of special cases to be dealt with later. It sounds to me many of the previous tries got hung up on trying to cover all motion. I think we should be more incremental about it.
I have a 2000ipm machine with 0.5G acceleration, so jerk control is an important topic for me as the machine endures a lot of stress.
The cases where we will still have significant jerk ( the start and end of some g64 mode moves, shallow arcs in exact stop, etc) are a fair compromise to leave off.
You will still have to tune your aces for the worst case motion situations, but having smooth rapids and linear moves would be at least for me a vast improvement.
Yes, no, maybe?
Please Log in or Create an account to join the conversation.
Time to create page: 0.082 seconds