Thanks to Seb's help, circular-blend-arc-rc3 is now available as a debian package in the scratch/rt and scratch/sim folders. The suffix is RC3 instead of RC1 because I rebased a few times until we found a master commit that passed all the tests.
Since I made a bit of a mess pushing these branches, I'd like to clean up a bit by deleting circular-blend-arc-rc1. It's been supersede by RC3, so leaving it in the repo will just cause confusion. My plan is to delete it by this Friday unless someone objects. In the meantime, for anyone who was holding out for the debian packages, you should be able to test the new TP. For safety, please run any programs in a simulation build before risking your expensive hardware :) Setting up is pretty straightforward: 1) Download and install the .deb file for your system. 10.04 32 bit RT: http://buildbot.linuxcnc.org/dists/lucid/scratch-rt/binary-i386/linuxcnc_2.6.0~pre~circular.blend.arc.rc3~12a6c8b_i386.deb 10.04 32 bit sim: http://buildbot.linuxcnc.org/dists/lucid/scratch-sim/binary-i386/linuxcnc-sim_2.6.0~pre~circular.blend.arc.rc3~12a6c8b_i386.deb For other builds, go here and find your distribution / architecture: http://buildbot.linuxcnc.org/dists/ 2) Update your machine configuration (ini file) with the following settings under [TRAJ]: ARC_BLEND_ENABLE = 1 ARC_BLEND_FALLBACK_ENABLE = 0 ARC_BLEND_OPTIMIZATION_DEPTH = 50 ARC_BLEND_GAP_CYCLES = 4 ARC_BLEND_RAMP_FREQ = 20 For more detail on what these settings mean, look here: http://www.linuxcnc.org/index.php/english/forum/10-advanced-configuration/27368-new-trajectory-planner-testersprograms-wanted?start=120#44419 http://www.linuxcnc.org/index.php/english/forum/10-advanced-configuration/27368-new-trajectory-planner-testersprograms-wanted?start=130#44474 On Wed, Mar 5, 2014 at 9:42 PM, sam sokolik <sa...@empirescreen.com> wrote: > Ok - I finally got a chance to test some more real hardware. This is a > bastard router that has 3 different steppers/drive (it was a converted > step/repeat machine.) I built robs latest (RC3) from the linuxcnc git > and ran some of the test programs. some good news one bad. > > Good news. The motion is very smooth. The program I was testing was > the LHchips4.ngc. It sounds very nice. > > http://electronicsam.com/images/KandT/testing/LHchips4.ngc > > I found one issue. A cutting profile containing more than 1 axis will > only go as fast as the slowest axis. This machine has 3 different axis > velocities > > X 150ipm > Y 78IPM > Z 50IPM > > On the 'belly' of chips - there are long x-z profiles (mostly X moves). > The profiles would peak at 50ipm. (they should peak at something > between X and Z. The current TP actually runs that profile faster > (closer to 100ipm) There are long XY profiles also - they peak at 78ipm > but should peak pretty close to 150ipm in some areas.. > > I talked to Rob about this - he said I should post here in case others > have seen this issue and didn't know what was happening. He has some > Ideas on solutions and will keep us posted. > > sam > > On 03/03/2014 05:12 PM, Robert Ellenberg wrote: > > Hi All, > > > > I just created a "release candidate" branch for circular arc blending: > > > > > http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=shortlog;h=refs/heads/circular-blend-arc-rc1 > > > > It's identical to my github branch that Sam and others have been testing. > > There was one small hiccup in pushing the new branch: > > > > remote: fatal: bad object 0000000000000000000000000000000000000000 > > > > However, it looks like the build failed here: > > > > > http://buildbot.linuxcnc.org/buildbot/builders/1400.rip-wheezy-rtpreempt-amd64/builds/193 > > > > I'm not sure how to interpret this error, but I suspect that since I > forked > > from master back in October, there have been fixes that my branch is > > missing. > > > > As a possible solution, I've been able to rebase the RC branch onto the > > lastest master with minimal changes. If there is a recent build that we > > know is solid, I can rebase my branch onto that and push it. If I go down > > this route, should I increment the branch's name, or just overwrite the > > "bad" branch? > > > > -Rob > > > ------------------------------------------------------------------------------ > > 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
