Ok, it turned out to be a stupid mistake, and the latest commit fixes it. On Mar 9, 2014 3:52 AM, "Robert Ellenberg" <rwe...@gmail.com> wrote:
> Just a head's up, I think the fix I pushed recently isn't quite perfect. I > noticed a small acceleration overage on one of the blend tests, but it > shouldn't be hard to bisect since all the tests passed so recently. I'll > keep you posted when I find the issue. > > > On Sat, Mar 8, 2014 at 10:15 PM, <sa...@empirescreen.com> wrote: > >> Have to add... It still keeps the velocity up and steadier than the >> current tp. Again - awesome work! >> >> >> On Sat, 08 Mar 2014 20:28:13 -0600 >> sam sokolik <sa...@empirescreen.com> wrote: >> > ran the experimental3 branch on real hardware tonight. The LHchips4 >> > sounded real good. Now it peaks across the belly at close to the y axis >> > velocity. Very nice! >> > >> > Now running steve.ngc you can really see the arc issue. >> > X is >> > MAX_VELOCITY = 2.33 >> > MAX_ACCELERATION = 10 >> > Y is >> > MAX_VELOCITY = 1.33 >> > MAX_ACCELERATION = 15 >> > >> > http://imagebin.org/298016 >> > >> > notice the whole profile runs mostly at 1.33in/sec - with a few peaks. >> > Now this profile has a great portion of the motion in the x axis. >> > >> > sam >> > >> > On 03/08/2014 11:50 AM, Robert Ellenberg wrote: >> > > It would be really nice to have consistent behavior between lines and >> arcs >> > > that way, though I think the limitation is not in the blend arcs >> > > themselves. Currently, maximum speed and acceleration are calculated >> in >> > > canon with conservative assumptions. For short arc segments, it >> should be >> > > possible to squeeze a bit more speed / acceleration out. >> Unfortunately, >> > > there isn't a good way to do the same thing with a large arc (like >90 >> > > deg). Since the velocity changes direction so much, the overall >> maximum >> > > velocity is more likely to be constrained by axis limits. >> > > >> > > One way around this could be to have CAM break up segments into short >> (20 >> > > deg or less) arcs. Unfortunately, to prevent slowdowns, you'd have to >> keep >> > > the segments longer than the minimum length for your feed >> (approximately 2 >> > > * v_max / servo_period). It might be possible to do something like >> this in >> > > canon too, though I'm not sure how hard it would be. >> > > >> ------------------------------------------------------------------------------ >> > > Subversion Kills Productivity. Get off Subversion & Make the Move to >> Perforce. >> > > With Perforce, you get hassle-free workflows. Merge that actually >> works. >> > > Faster operations. Version large binaries. Built-in WAN optimization >> and the >> > > freedom to use Git, Perforce or both. Make the move to Perforce. >> > > >> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk >> > > _______________________________________________ >> > > Emc-developers mailing list >> > > Emc-developers@lists.sourceforge.net >> > > https://lists.sourceforge.net/lists/listinfo/emc-developers >> > > >> > >> > >> > >> ------------------------------------------------------------------------------ >> > Subversion Kills Productivity. Get off Subversion & Make the Move to >> Perforce. >> > With Perforce, you get hassle-free workflows. Merge that actually works. >> > Faster operations. Version large binaries. Built-in WAN optimization >> and the >> > freedom to use Git, Perforce or both. Make the move to Perforce. >> > >> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk >> > _______________________________________________ >> > Emc-developers mailing list >> > Emc-developers@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/emc-developers >> >> >> >> ------------------------------------------------------------------------------ >> Subversion Kills Productivity. Get off Subversion & Make the Move to >> Perforce. >> With Perforce, you get hassle-free workflows. Merge that actually works. >> Faster operations. Version large binaries. Built-in WAN optimization and >> the >> freedom to use Git, Perforce or both. Make the move to Perforce. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk >> _______________________________________________ >> Emc-developers mailing list >> Emc-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/emc-developers >> > > ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
