Experimental Physics and Industrial Control System
Hi,
Would it make sense to use MRES to limit the smallest step size (was it originally like that)? On Diamond beamlines they tend to set RDBD to MRES anyway, as retires are not often used. And I suspect where retries are used this change in behavior wouldn't have any consequences, apart from perhaps some step scanning scripts behaving differently. However, it may affect the insertion device systems, which do use retries extensively.
As an aside, I think if a client attempts to do a move smaller than MRES nothing will happen apart from a change in VAL and a flicker of DMOV (1->0->1).
Cheers,
Matt
Pearson, Matthew R.
Data Acquisition and Control Engineer
Spallation Neutron Source
Oak Ridge National Lab
On May 27, 2013, at 11:46 PM, Tim Mooney <[email protected]<mailto:[email protected]>> wrote:
Hi Emma,
I agree. The original purpose of RDBD was specifically about retries,
and not also about whether or not to make an initial move. I would
like to explore the consequences of going back to that purpose.
Tim
----- Original Message -----
From: "Emma Shepherd" <[email protected]<mailto:[email protected]>>
To: [email protected]<mailto:[email protected]>
Sent: Monday, May 27, 2013 5:57:25 PM
Subject: Motor record .RDBD field
Hi all,
I've stumbled into this issue a couple of times now so I thought it
was worth a message to tech-talk.
The .RDBD field of the motor record limits the smallest allowed move
- quite often we want to set this very low so that we can do small
step moves. However, in a few cases we also want to use the motor
record's retry mechanism by setting .UEIP to 'Yes' and feeding the
encoder into .REP (I'm using the tpmac driver which allows you to do
this when the encoder is on a different channel). Because .RDBD is
now used as the retry deadband, we need to make it larger since it
is not capable of attaining such an accurate position.
It would be better if we could somehow decouple the use of .RDBD in
the retry sense from the smallest allowed move. Have other people
run into this and found a solution? In the meantime I need to keep
switching between modes (toggling .UEIP and changing .RDBD
appropriately) to allow me to do scans in very small steps followed
by a wind-back which uses retries to ensure I'm not losing steps.
It's a bit messy and not ideal.
Of course if we had perfect mechanics we wouldn't need to be doing
retries at all, but c'est la vie!
Thanks,
Emma
P.S. I hope I haven't missed a thread on this already, the APS
website seems to be down at the moment so I can't check
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
- References:
- Re: Motor record .RDBD field Tim Mooney
- Navigate by Date:
- Prev:
Re: streamdevice Dirk Zimoch
- Next:
RE: National Instruments PCI DAQmx Gomella, Andrew (NIH/NHLBI) [F]
- 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
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Motor record .RDBD field Tim Mooney
- 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
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024