Experimental Physics and
Industrial Control System

Hi Mark,

I started to edit the requirements document, but the premise seems to be that we would like to get rid of the motor record if only we could.  I don't feel this way.  I think it's a very valuable implementation of the behavior needed for nearly all the motors on APS beamlines.  An important but small number of motors need a better model to do complicated motions, and I'd like to focus my effort on those needs, without also pursuing the goal of reimplementing stuff that works.

However, I also agree that at least some of the state-machine aspects of the algorithm the motor record mplements would be much easier to code and maintain in a driver, because a driver can block and a record can't.  On the other hand, a record has a special() routine and a driver doesn't.

In any case, I would like to retain at least one behavior of the motor record: the ability to set a speed, start a motion, and then immediately return the speed to its previous value without affecting the motor motion in progress.  The table and monochromator software expect this behavior. It's certainly possible for software to wait until the motor has finished moving to reset the speed, but it's more complicated and error prone to do this.

Tim Mooney ([email protected]) (630)252-5417
Software Services Group (www.aps.anl.gov)
Advanced Photon Source, Argonne National Lab


________________________________________
From: [email protected] [[email protected]] on behalf of Mark Rivers [[email protected]]
Sent: Monday, May 25, 2015 3:03 PM
To: [email protected]; EPICS Tech-Talk
Subject: Draft requirements document for enhanced EPICS motor support

Folks,

I have created a straw-man requirements document for enhanced EPICS motor control in the new EPICS-motor-wg project on github.

https://github.com/EPICS-motor-wg/discussions/blob/master/documents/Requirements.md

If interested please take a look.  You can make contributions via the pull request mechanism on github.

Mark

Replies:

RE: Draft requirements document for enhanced EPICS motor support nick.rees

Re: Draft requirements document for enhanced EPICS motor support Kevin Peterson

RE: Draft requirements document for enhanced EPICS motor support Mark Rivers

References:

Draft requirements document for enhanced EPICS motor support Mark Rivers

Navigate by Date:

Prev: Re: releases of devlib2 and mrfioc2 Michael Davidsaver

Next: Re: CA client broadcast brings down galil which is not running EPICS Henrique Almeida

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: Draft requirements document for enhanced EPICS motor support Mark Rivers

Next: RE: Draft requirements document for enhanced EPICS motor support nick.rees

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