>We've looked at our future requirements, and while the IRM may not be a very
>good fit as it stands, the option of using a '162 with some of the large
>variety of IP cards available looks very interesting.
agreed
>Perhaps some discussion of creating a "standard model" for supporting IP cards
>under EPICS might be in order. As the IP interface (including module
>identification) seems to fairly well specified, perhaps we could take advantage
>of that information in the system configuration and initialization process.
The idea of standardisation is always good - but this only works if the IP-modules can
really be identified by their ID. This rule is already broken by the IP modules designed
for the IRM. You have to manually specify the type which in our case is done through
environment variables in the startup command file.
Maybe we'll find some time during the next EPICS meeting to start the discussion over
coffee!?
Matthias Clausen
- Navigate by Date:
- Prev:
Re: epics driver & device support for IRM Gabor Csuka
- Next:
Re: rec/devSup advise needed Marty Kraimer
- 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: epics driver & device support for IRM Gabor Csuka
- Next:
Re: epics driver & device support for IRM Bill Brown
- 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
|