EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Delta Tau motor control problem
From: "J. Lewis Muir" <[email protected]>
To: Mark Davis <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Fri, 3 Aug 2018 10:15:33 -0500
On 08/02, Mark Davis wrote:
> On 8/1/2018 3:45 PM, J. Lewis Muir wrote:
>> On 08/01, Mark Davis wrote:
>>> I assume that the driver SHOULD still work with the default Yes
>>> value.  Using the No value is not only less efficient, but could be
>>> a real problem.  If someone makes a typo when entering a new
>>> setpoint, it wouldn't matter if they realized their mistake and
>>> quickly entered the correct setpoint before the device has moved
>>> very much - It would still go all the way to the incorrect setting
>>> before starting to move to the correct position.
>>
>> Couldn't you just stop the move?
>
> Interesting question.
>
> I just tried giving it a new setpoint and then setting STOP to 1
> before it finished moving.  But the same problem occurs:  It stops,
> the done moving bit is till clear, and it won't take any new
> setpoints.

My main point here was just about the user scenario you described where
the user makes a mistake and then tries to quickly enter the correct
setpoint, but the motor goes all the way to the incorrect setpoint
before starting the move to the correct setpoint.  I was just suggesting
that the user could quickly stop the move rather than quickly entering
a new setpoint.  That works, right?  The motor doesn't continue moving
to the incorrect setpoint after the user has commanded a stop, right?  I
understand your bigger issue with the behavior, but just from a safety
point of view for the user scenario you described, stopping the move is
no less safe than entering the correct setpoint.  If anything, stopping
is probably a little safer just because the user wouldn't have to think
about the correct setpoint and enter it; they could just stop the move.

But then you're saying that after commanding a stop, you can no longer
command a move to a new setpoint, ever?  That seems broken.

Lewis

Replies:
Re: Delta Tau motor control problem Mark Davis
References:
Fwd: Re: Delta Tau motor control problem Mark Davis

Navigate by Date:
Prev: Re: Delta Tau motor control problem J. Lewis Muir
Next: Fw: Delta Tau motor control problem [email protected]
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Delta Tau motor control problem J. Lewis Muir
Next: Re: Delta Tau motor control problem Mark Davis
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
ANJ, 06 Aug 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·