On Fri, May 24, 2013 at 10:43:16AM +0100, andy pugh wrote:
> I don't see any reason for this to be a parameter. And I can think of
> a use for it as a pin. (see users list, gantry thread)
> 
> A parameter-to-pin switch should never break any configs, so I suggest
> changing it to an output pin, and pushing that to the 2.5 branch.
> 
> Any objections?

I thought it was a pin already.  I had always thought (in my "it
shouldn't be too hard..." way) that keying off that would be a way
to make an external component that slaves two motors and fakes all
the home signals etc.  It'd be pretty horrible but possible.

I'm VERY gun-shy about changing parameters to pins in the release
version since we screwed up pid so badly doing that previously.  I
think what made pid so bad was some of them were exported
conditionally (but used internally always), and I don't think that's
the case with home-state.  But still, like seb, I'd just rather
avoid it.

To maintain this separately, it'd be great if you want to make a new
branch off v2.5_branch with this change.  Buildbot will even build
and package it for you (seb pointed me to "Sorting of..." on
http://buildbot.linuxcnc.org/dev.html when I asked about this)

I still hope to work on joint slaving at fest next month - I have
the test hardware built and with jepler's help (a loaner 7i30 and
5i20) I should have the hardware to run it.  I think that is the
real and permanent answer.  It's easy to hook two steppers together
but to get index homing we really need to sort out how it should
work and add it to motion's homing state machine.  I don't think you
can easily patch it up outside of motion.

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to