New Trajectory Planner - Testers/programs wanted

Awesome!

Thanks Rob

rellenberg wrote: Nice work! I have a fix in the works for this. The code that checks for the maximum axis accelerations didn't properly handle the case of having fewer than 3 axes. It seems to be a simple enough fix on the TP side, though I still have to look canon. I'll have it pushed to a test branch off of 2.7 in another day or two.

Hi guys,

Thanks for everyones' help with getting my 3-axis router running. I've milled a couple small .jpg files so far but haven't had much time to play too much. However, I have a 300 sheet order of different shapes cut from plywood coming and 3d molds for a concept car body after that. So I'm going to be doing a hell of alot machining in the months coming up. I'm hoping during this period you guys can help me get this machine screaming fast. It looks like the new trajectory planner is the way to go. Just looking for some input. Using 2.6.5 on 10.04 now. I've read a little on this thread and it looks like the tp I have now is good for only 100 ipm....is this still the case? I'll definitely need more speed than that for all this work. I think this is a good machine to test if you guys agree. thanks.

cmtunnel wrote: It looks like the new trajectory planner is the way to go. Just looking for some input. Using 2.6.5 on 10.04 now. I've read a little on this thread and it looks like the tp I have now is good for only 100 ipm.

The "classic" TP is not limited to 100ipm except by the acceleration limits of the specific machine.

Anyway, the new TP is in 2.7, and I believe that 2.7 is available from the Buildbot, even though the buildbot instructions don't mention it:

buildbot.linuxcnc.org/

Copy the 2.6 instructions but change to be 2.7 and see what happens

Ok I'll experiment with the accelerations tomorrow & see what happens. I wrote a couple of spiral programs that are point to point with a curve tolerance of .001". One of them is a regular 2d spiral and the other moves down in the z direction as it spirals out. Though this might be useful after reading through the thread. They are attached.

When I download the new 2.7 version with the updated tp will I be able to easily go back and use my current 2.6.5?

If you change the 2.7 back to 2.6 and run an update, you will receive 2.6 again.

The option I use is to run the regular LinuxCNC as 'installed' and the master (latest bleeding edge code) as 'Run In Place' build, compiled from sources. This allows a seamless switch between multiple versions of LinuxCNC.

But in reality all I use 2.6 for is to verify that strange behaviour is indeed a stupid user error instead of a bug. So far I have no stability or other problems running the development releases so I doubt you want to go back to 2.6 once you have 2.7 installed.

And yes, the new TP is a HUGE step forward. I am amost exclusively using curvy HSM-toolpaths, and with the new TP it is absolutely no problems to push 100Kbytes of awful CAM-generated short-segment G-code through the interpreter/motion controller in 5 minutes of milling.

Ok, that sounds good. I have no idea how to set up 2.7 as 'run in place'. Will the info. earlier in this thread get me there? If not could you point me in the right direction? I hate to be so needy here but my time is limited right now and if I can get it running at 100ipm that will do for a little while. I'll get back to the 2.7 issue tonight though. Thanks for the help.