scurve trajectory planner

O_o

o_O

Grotius you're a madlad

I'm pretty sure you can just send this to a university and they'll send you back a math degree diploma image missing /media/kunena/emoticons/silly.png

I've been away from the game for quite a while as I was finishing school myself, but I'll put this to work in the near future

For awareness:

The scurve planner has some behaviour changes around:
motion.feed-hold
motion.adaptove-feed

Under the standard planner per documentation the effects of these pins can be enable or disabled through the use of M53 and M52 respectively.  These M codes are not supported under scurve.  The effects of these pins are always active.

If this departure from current behaviour is material and of concern then we would be interested to understand what the "real world" down sides are to this implementation.

Thanks - James.
 

Joco wrote:

For awareness:

The scurve planner has some behaviour changes around:
motion.feed-hold
motion.adaptove-feed

Under the standard planner per documentation the effects of these pins can be enable or disabled through the use of M53 and M52 respectively.  These M codes are not supported under scurve.  The effects of these pins are always active.

If this departure from current behaviour is material and of concern then we would be interested to understand what the "real world" down sides are to this implementation.

Thanks - James.

 

I've never used a feed-hold disable function; I suspect it's a legacy feature intended for machines run by operators who are not 'allowed' to really manipulate the controls.  Or the programmer sees a feature to be cut where feed-hold would lead to issues (drill/tool rubbing and work-hardening the part) and turns off feed hold for that program segment.

Neither have I used adaptive-feed, but I could imagine a situation where the programmer or operator would like to turn it off/on.  Perhaps using block-skip in the program for segments (roughing, maybe?) where adaptive feed is appropriate but not fully proven out.

Adaptive feed and feed hold are core to how plasmac for plasma machines operates.   However it does not use the gcode on/off capabilities that I have seen.

feed-hold issued during a tapping cycle could be catastrophic as it just stops xyz motion and does nothing to spindle.   Feed-inhibit would be appropriate then as it alllows synch motion as used in tapping to complete.

Adaptive feed along with external offsets allows for some cool cut recovery operations on a plasma or probably any jet cutting machine (e.g. Laser or water jet)

tommylight wrote:

At the risk of repeating myself:
Grotius is like a heat seeking missile, he locks on to something and does not stop!
Thank you Grotius.

In this case, the missile orbited earth at least 15 times and probably once around Mars before hitting the Scurve target!

I am in awe with Grotius's tenacity over many years on this!