New Trajectory Planner - Testers/programs wanted

Based on feedback from the dev list, it may be difficult to fully optimize the last segment, since the TP doesn't know when a program is done, vs. just waiting on more commands. However, one workaround to this is to make your last move of the program a rapid retract away from the part. Since the last step in the part is no longer the last step in the program, you'll still get a smooth cut.

As for the homing issue, I don't think I've seen any violations myself, but I haven't been specifically looking for them during homing. My simulation configs have the homing process cut short, because I got tired of waiting 5-10 seconds every time I loaded the GUI. Nothing that I've changed in this branch should directly affect homing, but it's always possible there are unintended consequences.

As a side note auto homing seems to ignore the acceleration settings on some moves in both cases.

That may not have been clear, I meant with the original TP and the new TP the results are the same.

I added another arc to the end, but did not see an improvement.

Rick G

You are still not clear...

The homing should be exactly the same as they are simple moves (no blending...)

sam

I posted this on the list - but what the heck - I like redundancy...

This is the above program with a lead-in, out path..



Current TP strait G64 - peaks at 159ipm


New TP strait G64 - peaks at 222ipm


Current TP G64P.001Q.001


New TP G64P.001Q.001

I haven't done that much milling lately and then only simple, non-short-segment stuff, but so far I haven't noticed strange issues with the new TP. Where the old TP would do an audible slow down/accelerate on segment to segment boundaries the new TP just continues.

Can I switch TP behaviour between old/new while running a program by setting a HAL pin/parameter or so?

I don't think so - they are ini settings...

DaBit wrote: I haven't done that much milling lately and then only simple, non-short-segment stuff, but so far I haven't noticed strange issues with the new TP. Where the old TP would do an audible slow down/accelerate on segment to segment boundaries the new TP just continues.

Can I switch TP behaviour between old/new while running a program by setting a HAL pin/parameter or so?