On Sunday, December 25, 2011 11:09:41 AM Andy Pugh did opine:
> On 25 Dec 2011, at 03:46, gene heskett <[email protected]> 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 it more time to keep up?
>
> I don't think you need to worry about it, but you can look at the thread
> execution period in "show hal configuration to check"
When did that toy get added? Sweet! You guys constantly amaze me. A nice
Christmas present, whenever it was.
It looks as if I have a cushion of about 15 more u-secs of fiddling around
before binding it up completely. Current base thread is 40 u-secs, 24 of
which would be the worst case used in the present configuration.
How much time does it take to track an A-B quadrature output + index output
spindle encoder on a per event basis, worst case on a typical setup similar
to this mobo/cpu? Or does this cloud up the crystal ball? :)
Another section of this display seems intuitively wrong, the parport pins
are shown as:
Component Pins:
Owner Type Dir Value Name
7 bit IN TRUE parport.0.pin-01-out <== estop-out
7 bit IN FALSE parport.0.pin-02-out <== xstep
7 bit IN FALSE parport.0.pin-03-out <== xdir
7 bit IN FALSE parport.0.pin-04-out <== ystep
7 bit IN TRUE parport.0.pin-05-out <== ydir
7 bit IN FALSE parport.0.pin-06-out <== zstep
7 bit IN FALSE parport.0.pin-07-out <== zdir
7 bit IN FALSE parport.0.pin-08-out <== astep
7 bit IN FALSE parport.0.pin-09-out <== adir
7 bit OUT FALSE parport.0.pin-10-in
7 bit OUT TRUE parport.0.pin-10-in-not
7 bit OUT FALSE parport.0.pin-11-in
7 bit OUT TRUE parport.0.pin-11-in-not
7 bit OUT FALSE parport.0.pin-12-in
7 bit OUT TRUE parport.0.pin-12-in-not
7 bit OUT FALSE parport.0.pin-13-in
7 bit OUT TRUE parport.0.pin-13-in-not
7 bit IN FALSE parport.0.pin-14-out <== spindle-ccw
7 bit OUT FALSE parport.0.pin-15-in
7 bit OUT TRUE parport.0.pin-15-in-not
7 bit IN FALSE parport.0.pin-16-out <== spindle-pwm
7 bit IN TRUE parport.0.pin-17-out <== xenable
The DIR column assignment seems backwards. But from this I assume I can
use pins 10, 11, & 12 as inputs from the encoder I'm trying to build.
Correct?
Also, I am not currently using the xenable out on pin 17 for anything, but
I would like, come the time, to re-assign that and use that to start a
small 12 volt compressor to pressurize the table prior to issueing a move
command to it, lifting it enough so the a motor can turn it.
I assume this is just some .hal stuff?
Because of backlash, I have it pulled pretty tight against the base to act
as a friction lock and have milled a groove for air injection under the rim
of the table to release it. None of this air compressor or plumbing to
inject the air exists anyplace but in my head ATM though. A work in
progress I think you call that. :)
Thanks Andy
Cheers, Gene
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://coyoteden.dyndns-free.com:85/gene>
It is easy when we are in prosperity to give advice to the afflicted.
-- Aeschylus
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
