LinuxCNC S-Curve Accelerations

Hi,

For today, a nice day with some progress.

In the video you can see i am playing with the :

• adaptive feed
• velocity overide
• max velocity

The planner is capable of going back until start of gcode file is reached.

In the gremlin screen, the dtg for xyz are present, also current velocity is present.

The change in adaptive feed, has to react a little faster, i will change that in the code.

inline_github_video

Question :
Where can i retrieve the current adaptive feed value? Is it just one motion.c hal pin?
I don't like to open a new nml channel for this. For now it can be set with a parameter pin.

 

Is it going around corners at full speed?

Hi Grotius,

I wanted to ask if this S-curve project is your private project? Or if you plan to release it to the official LCNC Branch?

If I understood correctly, someone else tried the S-curve first and didn't make it to the end. Then you created a HAL component that allowed you to do S-curve movements and now you're making your own interpreter. It is so?

If you are making a new intepreter and at the same time if you plan to release it, I would like to ask you that your new intepreter allows you to use the python command self.execute("G1 X20 Y20 f50") after the "yield INTERP_EXECUTE_FINISH" command. Namely, to be able to use the command "yield INTERP_EXECUTE_FINISH" several times during Remap, not just once.

forum.linuxcnc.org/38-general-linuxcnc-q...xecute-finish#268975

• Code following a yield may not recursively call the interpreter, like with self.execute("<mdi command>"). This is an architectural restriction of the interpreter and is not fixable without a major redesign.

I understand that no one will probably do this modification in the current Interpreter, but it was a shame to repeat this mistake in the new Interpreter.
 

I've read through the entire post history here and it's really impressive both the quality of contribution from the community and also the tenacity of Grotius in solving this problem.

--- Edit

It's taken me a couple of days but I've gotten it to compile and I'm working through getting it up and running to test it out. I have a step-by-step guide that I've been keeping along the way to help me understand how it works, and we'll see if I can refactor this a bit to be easier for others to follow along and more easily improve this in the near future.

zz912 wrote:

If I understood correctly, someone else tried the S-curve first and didn't make it to the end. Then you created a HAL component that allowed you to do S-curve movements and now you're making your own interpreter. It is so?

I think that technically he is working on a modified trajectory planner, and probably keeping the existing interpreter. 

I am curious about the current status. 

Hi all,

Andy is right. i was working on a modified trajectory planner.

It took me a lot of time to figur things out.
Last year i had it partially working, but i was not satisfied. And i stopped with working on it.
Mayor issue was that lcnc is running out of cyclus time. The different algo's take to much.

@ZZ912,
It's not a private project, code is on github.

@Beef,
How is your project status?