New Trajectory Planner - Testers/programs wanted

Rob

I am not having much success getting this to work on the machinekit/beaglebone setup.
It works no problem in Sim mode
But i will take that up with them.
But what i would like to know is:-
What is the correct usage of G64 in a program to utilize your new TP.

Just G64
or G64 P*.*
or G64 P*.* Q*.*

Maybe you could add the answer into your first post aswell?

nothing has changed with G64 vs the current TP

www.linuxcnc.org/docs/2.5/html/gcode/gcode.html#sec:G64

So - as a summary.

G64 Go as fast as you can while touching every segment.

G64 Px.xxx - (No Q assumes Q = P) Combine line segments that are within x.xxx and follow new path within x.xxx

G64 Px.xxx Qy.yyy Combine segments that are within y.yyy - follow new path within x.xxx

G64 Qy.yyy combine segments within y.yyy and go as fast as you can while still touching each segment in the new path.

Clear as mud?

sam

If I use Linux 2.5.4, it take 10 min
If i use new TP, it take 5 min.
I use G64P0.05
I just happy.

Yay!!

sam

I am just using the new TP without constantly comparing to the old one, and so far I haven't noticed problems with toolpath generation.

I really think this is one of the best improvements to LinuxCNC in the 2.6 release.

Not to sound lazy but I've read most of this page and am curious on the best way to test the new planner out (get a build or so forth). All I ever do is 3d profiling and I think I could really be shocked on how much faster things may become.

Any testing is good testing! A good way to get started is just to try running one of your programs, and see what difference the new TP makes. It would also be helpful to know if there are any more subtle effects, like if you notice a change in surface finish, or how the machine sounds when running. Also, if you have a configuration other than the traditional XYZ, it would be great to know how well it works there.

I sort of worded my question wrong there.
I was wondering what the current instructions are to get a working build.
The reason I'm interested is I run a small 3 axis machine that's currently set to 120 IPM, 50 IPS^2 or so, and it runs 50K to 100K line gcode files for 3d profiling. So any speed increase would be great since I never do 2d work.

rellenberg wrote:

Any testing is good testing! A good way to get started is just to try running one of your programs, and see what difference the new TP makes. It would also be helpful to know if there are any more subtle effects, like if you notice a change in surface finish, or how the machine sounds when running.

All improved. The slowing down - speeding up of the regular TP is reduced, which improves surface finish. Machine sounds the same.
Here is a picture of a part made with your TP. Surface finish looks pretty decent to me for a simple BF20/G0704 mill.

I want to give it a shot on my files, it's just I need to get it built, and my knowledge of Linux isn't great.
I'll torture a build I have on virtual box that I use for Gcode testing and see if I can get it working.