Re: [Emc-users] Making emc's backtrace show a line as wide as the (small) bit is cutting.

2011-12-25 Thread Andy Pugh
On 25 Dec 2011, at 03:46, gene heskett ghesk...@wdtv.com wrote: y current .ini base_period values are in the 35-40 u- second range. Is there enough processing time on a 1400mhz athlon to process that w/o any skips? Or would this be a case where a longer base period would actually give

Re: [Emc-users] Making emc's backtrace show a line as wide as the (small) bit is cutting.

2011-12-25 Thread gene heskett
On Sunday, December 25, 2011 11:09:41 AM Andy Pugh did opine: On 25 Dec 2011, at 03:46, gene heskett ghesk...@wdtv.com wrote: y current .ini base_period values are in the 35-40 u- second range. Is there enough processing time on a 1400mhz athlon to process that w/o any skips? Or would

Re: [Emc-users] Making emc's backtrace show a line as wide as the (small) bit is cutting.

2011-12-25 Thread Andy Pugh
On 25 Dec 2011, at 16:49, gene heskett ghesk...@wdtv.com wrote: The DIR column assignment seems backwards. It does always look that way, but is because the value of a parport pin is an output from the driver in to HAL. And vice-versa. Tracking the encoder counts should take very little

[Emc-users] Making emc's backtrace show a line as wide as the (small) bit is cutting.

2011-12-24 Thread gene heskett
Greetings; Yes, I suppose this should be a function of loading a full described tool. I'm trying to visualize, with emc running without motor power, what the encoder wheel I am playing with will actually look like by making it use a path line in the backplot for the metal being cut away, so