Daron Chabot wrote:
Any idea about the effort required to create support for it given
there is synApps support for the Parker 6000 ?
The effort required to create complete EPICS motor record device driver
support for a new controller is about two weeks. The majority of that time
is usually spent trying to understand how to handle abnormal events or minor
aspects of the motor controllers' operations and conditions (e.g., fault
conditions, homing, jogging). Usually you can get a motor to do point to
point moves in a week. It's all the over stuff that drags on.
If the Parker 9000 has exactly same commands as the 6000 and behaves
exactly the same as the 6000; your done. Just use the 6000 device driver
and let me know so that I can document the fact.
If the Parker 9000 is close to the 6000; then follow the example of the
Newport 4000/5/6 device driver; i.e., start with the 6000 driver; have the
driver read the controller's ID at boot-up and set a "model" indicator for
later use. Use the model indicator to select minor differences in the
Parker
6000/9000 device driver.
If either of the above scenarios work out then it can be done in the
mythical uninterrupted week. Otherwise, it's going to take a little
longer.
Hope this helps,
Ron
- References:
- Parker 9000 Daron Chabot
- Navigate by Date:
- Prev:
Parker 9000 Daron Chabot
- Next:
RE: CAJ questions Mark Rivers
- 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:
Parker 9000 Daron Chabot
- Next:
CA reconnection problem Dirk Zimoch
- 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
|