Third party software and hardware support forums. > Tempest Trajectory Planner

Tempest Planning - Preliminary information and testing

<< < (3/29) > >>

poppabear:
Art,

    On axis 7,8,9 are they another rotary primarily axis that also rotate around x,y,z (with option on making them linear)?
What are you going to call them in G code will they have a primary letter, and then an "alias" letter as well, like the current 6 axis do?

scott

ART:
As attached in MAch3, you have no connection to the 7,8 or 9th axis.
They will be separated to U,V,W in the end. At the moment they are all
simply linear interpolations until such time as kinematics are added.

  Preliminary tests show that Tempest is pretty smooth, does great blending , but
suffers from lower speeds than desired as the segment size gets smaller. Thats whats
currently being worked on, when and if I can speed it up to relative mach3 levels of speed
with small segement concatentation speeds, then Ill be investigating rotational kinemtaics
to make the A,B,C and the U,V,W axis as set rotation vecotr components to the cartesion axis
based on setting tranformational matrix'sfor each rotational axis.

Art

ART:
Well, Preliminary testing shows that version of the tempest test is very smooth, but slower than mach3 by too much in small segment code. THis is because with SCurve planners a lookahead strategy is necessary to see how much speed we can add up to in the stream of gcode.

  This version is Quantum on steroids. It looks ahead and back and precompiles the speed capabilities. On my stress test, which Ill post as well, MAch3 takes 51 seconds on my setup, Tempest takes 56 seconds, not too bad a difference to respect physical motion laws and limit the jerking of the machine, not to mention make the CV blending more controllable by the user.

You only need to unzip this to a mach3 folder to test, and then select "config/set planner type" to turn on the tempest planner , you can swap back and forth between planners as long as your not currently running code. Setting higher Jerk limits will speed up the end result and a number like 12000 or so shoudl work for most of you, lower if your machine is crappy, higher if its a stout solid unit.

 Id be interested in any observations.

Thx
Art
  

ART:
Hi:

   Well, testing on that version shows a few errors in small segement code. This version test very well even in small segement code. I still havent done much
testing with Arcs in the code, but speed is very high with even very tight and small segement testing. This version seems so far to eliminate the errors of Quantum
and is now testing well on any file Ive tried. Work continues on FeedHold actions now to allow it to integrate into a full CNC program.

Thx
Art

chad:
Hi Art,

I have been away for quite some time but I am about to begin on a new project and I am trying to do some ketch up reading.

I am planning a cnc laser cutter. 100w co2 rf-pumped, yaskawa sigma 5 servos, I am leaning towards smooth-stepper or something else that Brian has on the back burner. 

I am planning on flying optics, super rigid really light. But I have been concerned about cv with the laser. I would also like to be able to vary the laser power with velocity.  My goal is REALLY smooth motion for a nice cut edge but I would also like to have decent speed.
Down the road I would also like to do raster engraving.

This is planned for sale and It is not just a hobby machine. I Think I am going to start ordering parts next week and begin the proto.

DO you see any advantages with this type of planner with laser?

chad
 

Navigation

[0] Message Index

[#] Next page

[*] Previous page