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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Power Supply Record? |
From: | Geoff Savage <[email protected]> |
To: | EPICS Tech Talk <[email protected]> |
Date: | Thu, 15 Nov 2007 12:24:27 -0600 |
I strongly agree.
Creating templates for different power supply types are probably a good way to go in most cases.
We even broke up our power supply templates into smaller units, most of which are only consisting of a single record. (Templates for "status word", "status bit", "command word", "command bit", ...)
The only exception - maybe - being a case where you have a large number of very similar, very complex power supplies that need a complex state machine to be operated. The only example that I know of: high voltage power supplies in large detectors.
Even in such a case I would consider putting only the complex state machine into a separate custom (or generic subroutine) record.
Good luck! Ralph
Luedeke Andreas wrote:Susanna Jacobson wrote:[...] we are considering writing a custom Power Supply record. [...]Hi Susanna,
I would also welcome any advice or cautions you have, based on your experience in this area. [...]
I had a similar idea 8 years ago for some in-house developed power supply at PSI.
Luckily I got some advice not to do it that way (Thanks Bob!).
If you use one record per power supply, your application will suffer from a lack of expandability, flexibility and usability.
[...]