IMHO being an input pin makes perfect sense - when there is hardware switch
for enable/disable, so such an input pin is needed to inform EMC about it. I
even think that it is meant to be input pin for "motion enabled", because
there are amplifier enable output pins.
I agree, that it would great to clean up any inconsistency.
Viesturs
On 2011. gada 31. Jūl. 09:50, "Chris Morley" <[email protected]>
wrote:
>
> Hi guys
>
> Was working with someone on the forum when this came up.
>
> motion.motion-enabled is reported as an output in the manual.
> which makes sense
>
> everywhere else its an input (man pages, HALCMD)
>
> Looking in motion.c it is written to be an input but seems pretty
> clear that it's supposed to be an output.
> <snip>
>
> /* export machine wide hal parameters */
> retval =
> hal_pin_bit_new("motion.motion-enabled", HAL_IN,
&(emcmot_hal_data->motion_enabled),
>
> <snip>
>
> /*! \todo FIXME - these don't really need initialized, since they are
written
> with data from the emcmotStatus struct */
> *(emcmot_hal_data->motion_enabled) = 0;
> *(emcmot_hal_data->in_position) = 0;
> *(emcmot_hal_data->coord_mode) = 0;
> *(emcmot_hal_data->teleop_mode) = 0;
> <snip>
>
> This is backed up be the fact that writing to it does nothing.
> where do I find info on emcmotStatus struct?
> I would fix it but I don't want to mess with something I don't totally
understand.
> Could someone confirm my conclusion?
> If I'm right I would imagine it wasn't found cause it works properly
anyways.
>
> Chris M
>
>
------------------------------------------------------------------------------
Got Input? Slashdot Needs You.
Take our quick survey online. Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
