I just found an error I overlooked that may be causing those spikes. I'm seeing similar issues with the straight-line case, which I'm also seeing on my sherline mill on the straight line example. Hopefully it will be a quick fix.
-Rob On Tue, Dec 3, 2013 at 9:08 PM, sam sokolik <[email protected]> wrote: > I will try that tomorrow. One thought - there is no following errror - > so I motion is doing what the tp is telling it to do... > > cool. > > thanks again - I didn't notice that many arcs in the stellabee - but > that could be... I will look for some more line segment programs that > are long in length. > > sam > On 12/03/2013 03:20 PM, Robert Ellenberg wrote: > > On Dec 3, 2013 2:42 PM, "sam sokolik" <[email protected]> wrote: > >> I have not seen the blip.. (but surprisingly I may have found a blip in > >> master...) > >> Ok - spiral - wow. Running at almost 400ipm at the largest diameter. > >> Damn impressive. > >> > >> I am a bit perplexed though.. If I run stellabee1.ngc ( > >> http://electronicsam.com/images/KandT/testing/stellabee1.ngc ) with > >> g64P.005 - it actually runs faster with parabolic blends (master). > >> (40min vs 50 minutes about) I was expecting a 2 fold at least > > improvement. > > > > The reason for that might be the arcs in the program. I reduced the > > acceleration of arcs to fix the overage in arc-arc.ngc, but the tradeoff > is > > lower performance when there is a lot of acceleration and deceleration. > > > >> While the penguin - (metric so .1 is about .004") > >> parabolic blend P.1=2:21 Strait G64=4:12 > >> circular blend P.1=1:41 Strait G64=2:27 > >> > >> So - I don't know if that is correct - or there is some issue. Is the > >> stellabee file just too wacky for the readahead to help? > >> > >> I could not run the stellabee file with strait g64 because it fails. I > >> will try to get more info. (large jump in position/acc) > >> Ok - I did a halscope with program line as part of it.. With stellabee > >> and strait G64 - looks like line 32142. > > Could you build the program with my debug flags enabled? It will spit > out a > > log that will be useful to diagnose what's happening. Run this command: > > > > make EXTRA_DEBUG = '-DTP_DEBUG -DTC_DEBUG' > > > > then run Linuxcnc like this: > > > > linuxcnc > test.log > > > > This works in simulation mode to dump a log of what's happening in tp. > I'd > > like to see if these spikes are visible in the planned motion. > > > > Thanks! > > Rob > > > ------------------------------------------------------------------------------ > > Sponsored by Intel(R) XDK > > Develop, test and display web and hybrid apps with a single code base. > > Download it for free now! > > > http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk > > _______________________________________________ > > Emc-developers mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/emc-developers > > > > > > ------------------------------------------------------------------------------ > Sponsored by Intel(R) XDK > Develop, test and display web and hybrid apps with a single code base. > Download it for free now! > > http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers > ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
