On 9 April 2010 18:00, Dave <[email protected]> wrote: > Just has to be worked out.
This seems to pretty-much work. Note that it doesn't work unless you put the mux and the oneshot into a thread before the motion functions. The axis position on hitting the limit is pretty consistent (enough to show a position loss) and can be seen my looking at xcheck in Hal Meter or linking it to a PyVCP control. loadrt mux2 count=1 loadrt oneshot count=1 addf oneshot.0 servo-thread addf mux2.0 servo-thread <Motion and other threads here> net xcheck axis.0.joint-pos-fb => mux2.0.in1 net xcheckfb mux2.0.in0 <= mux2.0.out net xchecktrig oneshot.0.out => mux2.0.sel setp oneshot.0.width 0.0001 setp oneshot.0.rising 1 setp oneshot.0.falling 0 net both-home-x => axis.0.home-sw-in => oneshot.0.in -- atp ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
