scurve trajectory planner

Ok. Your new code works a lot better.

With the given 9axis sim machine everything works as it should I think.

But, if you use a my 4axis testmachine (very high kinematic values) than you are able to stop the tp and also get trouble with the axis screen. But nevertheless. Under normal circumstances the 4axis testmachine works now also without axis screen problems.

Hi Grotius,

I made a small test nc file for better testing. This is a video with my 4 axis test machine capable of:

- 100m/min velocity
- 1 g acceleration
- 6.000 rpm A axis
- wild acceleration of the A axis

My current project will be capable of 30m/min, 0,5 g and the A axis will be a turning axis (of curse with way less acceleration). So in my opinion the test machine is not sooooo way of.

Video

I try different feed override values and as you can see I set the max jerk nearly to maximum (as if there is no scurve).
The behaviour of the A axis is still strange. And as you can see I am able to stop the tp. but it seems that the planer works on and only the axis gui si stoped. Nevertheless strange.

Please feel free to mention if I am testing to wild! I can live with boundaries so to say.

Last thing I just realised. 2.9.3 need a few percentage of my cpu (i5 4570T), maybe 3 to 10%. 2.10 with your scure tp needs over 40% while in idle and up to 50% while running the program.
 

Oh, forget about the cpu load. Its to late. I forgot that I tested the axis cycle time.

Hi Julian,

Did some updates.

The scurve is now conversed to c code. I think this is easyer for bug solving.
And it can now be used directly in lcnc components.

I forgot to apply the feed overide to the end velocity's of segments.
Now it's running much faster.

I came accross a new bug. When a new buffer was loaded, the velocity was starting from zero when
using feed overides around 300%. Lower than that the bug was not visible.
This now is solved. During a new buffer load and transition the velocity keeps up.

There was also a endvel=0 error, wich halted motion,  is solved by pushing the motion into a new segment,
depending on rundir.

Extreme feed overides:

Hi Grotius.

Really cool! Tomorrow I will have some time to test around. I also wrote a small ncode with some loops to test P and F values. Will test and provide tomorrow.

The conversion I dont get right now. Of course I know how to use components and so on, but have to look how you mean it.

juliankoenig87 wrote:

Hi Grotius.

Really cool! Tomorrow I will have some time to test around. I also wrote a small ncode with some loops to test P and F values. Will test and provide tomorrow.

The conversion I dont get right now. Of course I know how to use components and so on, but have to look how you mean it.

Julian, can you join the qtpyvcp chat room?

matrix.to/#/#qtpyvcp:matrix.org