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  <20132014  2015  2016  2017  2018  2019  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  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: Motor record .RDBD field
From: Emma Shepherd <[email protected]>
To: Ron Sluiter <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Wed, 29 May 2013 08:27:34 +1000
Hi Ron,

> On the other hand, all of the above may be off base and what you are
> asking for (as Tim alluded to) is to have RDBD ignored on the initial
> move (on a change in VAL/DVAL/RVAL). In other words, RDBD only applies
> to retries.

Yes, that's what I meant!  I just want to be able to demand moves that are smaller than .RDBD (but they will still be >= MRES).

Cheers,
Emma

> -----Original Message-----
> From: Ron Sluiter [mailto:[email protected]]
> Sent: Wednesday, 29 May 2013 1:48 AM
> To: Emma Shepherd
> Cc: [email protected]
> Subject: Re: Motor record .RDBD field
>
> Hello Emma,
>
> On 5/27/2013 5:57 PM, Emma Shepherd wrote:
> > The .RDBD field of the motor record limits the smallest allowed move
> I would describe this slightly differently...
> The motor resolution field (MRES) defines the smallest allowed move.
> The motor record limits the retry deadband (RDBD) to be >= motor
> resolution (MRES).
> This prevents the record from attempting to do retry moves that are
> smaller than MRES.
>
> >   - quite often we want to set this very low so that we can do small
> step moves.
>
> By "this", I presume you are referring to the retry deadband (RDBD) and
> that you want to set RDBD less than the motor resolution.
>
> How does the Delta Tau handle a relative move that is less than MRES?
>
> The only motor controller I have investigated for this scenario (i.e.,
> relative moves < MRES) is the OMS VME58.
> Rather than accumulating "too small" relative moves, the OMS VME58
> ignores them.
> For example, if I set MRES=0.1, Max retry count (RTRY)  = 100 and the
> position error at the end of a move is 0.09, the OMS VME58 will be
> command to do 100 retries, but nothing moves (I am referring here to a
> hypothetical motor record where RDBD is not limited by MRES).
>
> > It would be better if we could somehow decouple the use of .RDBD in
> the retry sense from the smallest allowed move.
>
> On the other hand, all of the above may be off base and what you are
> asking for (as Tim alluded to) is to have RDBD ignored on the initial
> move (on a change in VAL/DVAL/RVAL). In other words, RDBD only applies
> to retries.
>
> Which is it?
>
> Ron

SUPPLIERS: As of 1 January 2013, the Australian Synchrotron Company Ltd has changed its business name. However, the trading name will remain Australian Synchrotron.
Please address all quotations and invoices to: Synchrotron Light Source Australia Pty Ltd (SLSA), ABN: 18 159 468 256


Replies:
Re: Motor record .RDBD field Ron Sluiter
References:
Motor record .RDBD field Emma Shepherd
Re: Motor record .RDBD field Ron Sluiter

Navigate by Date:
Prev: Re: Relative time in XY graph Bruce Hill
Next: parsing dbr types pthomas
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Motor record .RDBD field Ron Sluiter
Next: Re: Motor record .RDBD field Ron Sluiter
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 20 Apr 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·