New Trajectory Planner - Testers/programs wanted

What are the splines made up of? if they are a bunch of arcs that are not joined at perfect tangents - then yes - short line segments are going to run faster. could you give us a short example of the 2 programs (one as splines and one as polylines?) but I assume the above - splines are made up of arcs - polylines are made up of line sements.

To recap - so far the readahead works with
line-line segments
tangent line-arc segmetns
tangent arc-arc segments

Paul wrote:

DaBit wrote: In my hobby environment 2.6-pre runs flawless, but I don't have a very complicated setup.

Thanks DaBit. Have you seen issues with splines that don't seem to show up with polylines? Maybe this is coming from my CAM program?

No, I haven't. But that must be CAM-related.

90% of my millng is done using handcrafted G-code using a mix of a few O-word calls for standard operations and some logic in G-code. Or just start a milling operation from a GladeVCP panel. Many parts I make are a variation of 'mill to size, make a few holes and pockets, and mill a contour'. As I said before: usually I am not doing complicated things. Although I want to do more 3D-contour milling, which is pretty slow with the current TP and a reasonably accurate G64 Px setting.

The only CAM-software I use is CamBam+, partially because it generates such a nice G-code (for a CAM-program, that is) using it's arc-fitting algorithms etc. and partially because I can afford it. Software like Deskproto generates plain stupid G-code which runs like sh*t on the original TP (my trial has expired, BTW). The code I have seen from Vectric products is even worse. Megabytes and megabytes of short G1 segments. The new TP should really shine on that. Unfortunately I don't own that either.

My spiral was made in Inkscape which was saved with thier version of an AutoCad R14 format. That's where the splines come from. I then converted the spiral to polyines.

Thanks...

PK

What is the problem?
I can open both spiral NGC's and run them. On a sim config at least; cannot run code on the real machine without actually powering it on.

Polyline code seems to be faster on the new TP, circular code on the current 2.5.3.

Simulator here only so far. Both run here, too. On the simulator here, the polyline speed is more consistant. The spline slows down to transistion to the next spline segment. I'm afraid the speed change will show up on the piece. Not a problem to convert to polylines, just wondering if I can change something with the spline version to be more consistant.

PK

Yes - for whatever reason the trasitions are not tangent arc-line or arc-arc. Because they are not - the trajectory planner falls back (slows down) to the original parabolic blending for those segments.

Paul wrote: My spiral was made in Inkscape which was saved with thier version of an AutoCad R14 format. That's where the splines come from. I then converted the spiral to polyines.

Thanks...

PK