Trajectory Planner using Ruckig Lib

Sorry. for clarity:
There are instances where you need some "buffer" for acceleration and velocity. Backlash compensation is one. When I got that error recently it was because I had lowered my stepper timing settings to the point my rapids could not be met.

Specifically when you use an S curve acceleration, to get an "average" of say 1m/s/s the middle of the move will be higher. I don't know how this is being set up, so maybe this is not the issue, but it is something to look at.

SOLVED - VPN to the rescue.  While my fixed IP is still blocked (pushing 4 days now) I can use a VPN (lucky I have a subscription) to get in.  And since that is a floating IP I can just shift servers if there are anymore silly blocking issues.

---

Team - my IP address has been blocked by the forum for several days. The only way I can access things is via my mobile phone which is very awkward and annoying.

While I will periodically check access, I am sad to say that until the situation resolves I will be, for all intents and purposes, absent.

If an administrator sees this and can remedy the problem that would be greatly appreciated.

Regards - Joco (James)

@ihavenofish
IIRC the backlash and screw compensation work by increasing the max acceleration *above* the limits in the ini ... I've seen it while documenting but did a quick search and didn't find it, I will get back to you with the details another day.

Small update, this time of year is (as I mentioned) terrible for forward progress on my end but I've been slowly working my way through Doxygen-ating everything we've changed so it's a bit easier to see how it all fits together.

I don't think the outputs from Doxygen are easy to upload to the GitHub wiki though, so I will probably host it on my website and include a script for self-generating the documentation as well.

Just checking in. Are things paused due to holiday season? Or has a wall been hit?  Or lots of beavering away just not posted any updates? Just wondering is all, given the activity then pause.

cheers - J. 

Holiday season pause on my end certainly

Hey together,
I was just curious if the development of this is going on and if there is any way to support it outside of being able to contribute to the code?

I am more of an end user, but due my machines are limited from not having S-Curve Accelerations I would really love to implement and test it. Running at 1700mm/s^2 currently, but I am sure I could easly ramp it up to two-four times that and getting cutting performances close to a Datron Neo. S-Curves seems to be litlerally THE difference between any low-end and DIY machine nowadays and the industry standard controls.
Would be happy to arrange some funding etc. for this feature, I am sure many out there are with more rigid mineral casting machines or retrofits are keen to get their hands on it!

Greetings Fritz