Greetings Luc
its interesting you are seeing the speed spikes. I
am running a CVS version from around Nov 4. I see these spikes as well using
stepper drive. As you mention, the spike seems to come at the end of a move...
its almost like the motion blending has a problem. I have been trying to track
it down as it can be a real problem for steppers. It only happens at the end of
some of the moves and where an x move blends into a radius. I have been using
the cds.ngc demo program to test with and there are at least 10 places in the
code where the x axis drive seems to take off with no regard to the programmed
max speed or accel. I'm not sure if anyone else sees this problem. It may be
happening on other axis, but my test setup only has 1 stepper on
the
x drive. I see the problem with both the old and the g
code interpreter, so I dont think it is a g code related problem. In my test
setup, I have the feed speed at 45ipm. I thought for a while that one of the
real-time tasks was getting behind and playing catch-up, but I rearranged some
of the task intervals to make sure there was some available CPU time with no
effect. The resulting accel is way beyond the programmed max, which I have at
1.0. Does anyone see this problem in the aug11 release? or in older releases?
=======================================================
Lawrence Glaister VE7IT email: lg-at-jfm.bc.ca 1462 Madrona Drive http://jfm.bc.ca Nanoose Bay BC Canada V9P 9C9 =======================================================
|