This is exactly what I was wondering about. I had been told to expect a setup much like this and I just wanted to know if there was a common set of fields from the standard motor record which I could expect in a setup like this where the energy is controlled by a set of motors but is exposed to the user as a single system.
Thank you.
-Richard
-----Original Message-----
From: Peter Jemian [mailto:[email protected]]
Sent: Friday, April 03, 2009 3:51 PM
To: Richard Pastrick
Cc: [email protected]
Subject: Re: Motor Soft Record Client Interface
Richard:
The attached file (kohzuSeqCtl_All.adl.png) is a screen shot of a common GUI used for double crystal monochromator control at APS. Several beam lines have used this screen (or a derivative) for a decade or so. It includes energy controls that appear to the user like a soft motor. The underlying PVs are not a soft motor but a suite of records to provide energy support. DCM-specific controls are also provided on this screen. While there is a more condensed screen (with fewer controls), this one is common.
Another case is a combination DCM and mirror used at one beam line (33BM). Not that this is representative of all cases, but here is an example description of a set of controls providing energy as a soft motor (and some other stuff). I imagine it is close to what you are thinking of providing in terms of energy as a soft motor using the EPICS motor record from synApps.
http://www.aps.anl.gov/Sectors/33_34/controls/docs/mirdcm/
The energy soft motor looks like any other motor (readback value, target value, tweak reverse and forward, engineering units, and some more). It uses the same GUI structure as any other motor record would. The [More] button pulls up the standardized screen for details which are more detailed than the standard operating controls. In fact, there are several panels which show the energy soft motor with a wavelength soft motor, as well as angle soft motors and some real motor axes as well.
Can't tell them apart by looking at the GUI.
But, since the soft motor for energy is based on calculations, it needs additional controls for specification of crystal Bragg spacing and crystal offset (geometry-specific information for this monochromator).
Can supply more details if this takes you in a direction you prefer.
Pete
Mark Rivers wrote:
> If you are addressing a motor that uses the EPICS motor record that is part of synApps, then there is a perfectly well defined set of fields available. If you are addressing a motor that does not use the motor record then things are more difficult. There is a database used by the GMCA and others for the Delta Tau motors, so that is another "standard".
>
> But when you say:
>
>
>> It doesn't matter if it is energy or whatever. My question is more towards motor records in general.
>>
>
> It actually does matter. Typically energy is NOT a "motor record", it is another type of record (e.g. ao) and cannot be addressed using the fields for a motor record senso stricto.
>
> Mark
>
>
>
> ________________________________
>
> From: Richard Pastrick [mailto:[email protected]]
> Sent: Fri 4/3/2009 1:37 PM
> To: Mark Rivers; [email protected]
> Subject: RE: Motor Soft Record Client Interface
>
>
>
> It doesn't matter if it is energy or whatever. My question is more towards motor records in general. If I am expecting to be addressing a motor, is there a minimum set of fields that I should always expect to be implemented?
>
> -Richard
>
>
> -----Original Message-----
> From: Mark Rivers [mailto:[email protected]]
> Sent: Friday, April 03, 2009 10:57 AM
> To: Richard Pastrick; [email protected]
> Subject: RE: Motor Soft Record Client Interface
>
> Energy is usually not actually a "soft motor" per se (e.g. motor record), but another type of PV. There is no standard being used.
>
> Mark
>
>
> ________________________________
>
> From: [email protected] on behalf of Richard Pastrick
> Sent: Fri 4/3/2009 12:20 PM
> To: [email protected]
> Subject: Motor Soft Record Client Interface
>
>
>
> I have implemented a client interface for EPICS motors on windows for an x-ray microscope and one of the key features was the ability to integrate with various soft motor records which control the energy axis at synchrotrons. I was wondering if there was a list of required fields that I could depend on to be implemented at each site or am I partially at the mercy of the controls engineers?
>
>
>
> Thanks.
>
>
>
> Richard Pastrick
>
> Associate Software Engineer
>
> Xradia Inc
>
> 5052 Commercial Cir
>
> Concord CA 94520
>
> 925-288-1228 Ext 1151
>
> 925-771-8051 (direct line)
>
> 925-348-0384 (cell)
>
>
>
>
> ________________________________
>
> The information in this email, including any attachments, is confidential and intended only for the recipient(s) listed. Any use of this email for any other purpose is prohibited. If you have received this email in error, please notify me immediately by reply email, delete this email, and do not disclose its contents to anyone.
>
>
> The information in this email, including any attachments, is confidential and intended only for the recipient(s) listed. Any use of this email for any other purpose is prohibited. If you have received this email in error, please notify me immediately by reply email, delete this email, and do not disclose its contents to anyone.
>
>
>
>
--
----------------------------------------------------------
Pete R. Jemian, Ph.D. <[email protected]>
Beam line Controls and Data Acquisition, Group Leader
Advanced Photon Source, Argonne National Laboratory
Argonne, IL 60439 630 - 252 - 3189
-----------------------------------------------------------
Education is the one thing for which people
are willing to pay yet not receive.
-----------------------------------------------------------
The information in this email, including any attachments, is confidential and intended only for the recipient(s) listed. Any use of this email for any other purpose is prohibited. If you have received this email in error, please notify me immediately by reply email, delete this email, and do not disclose its contents to anyone.
- References:
- Motor Soft Record Client Interface Richard Pastrick
- RE: Motor Soft Record Client Interface Mark Rivers
- RE: Motor Soft Record Client Interface Richard Pastrick
- RE: Motor Soft Record Client Interface Mark Rivers
- Re: Motor Soft Record Client Interface Peter Jemian
- Navigate by Date:
- Prev:
Re: Motor Soft Record Client Interface Peter Jemian
- Next:
Report from the Second Annual EPICS Codeathon Andrew Johnson
- 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 Soft Record Client Interface Peter Jemian
- Next:
Re: Motor Soft Record Client Interface J. Lewis Muir
- 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
|