>
> 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.
>
> 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.
>
> Any ideas? Is this worth spending some time on during the next epics meeting?
>
My opinion is the following:
----------------------------
Must be separate the 'epics' and 'vwWorks' configuration. (Of course
this two must be fit together)
The Epics run-time configuration on version 3.13 is much more better
then the 3.12. features. This is needed, and the Epics is on this way.
(We in DESY useing some envinroment variable foe enable/disable device/driver
support moduls on version 3.12.2.D (DESY add owns). This env. variable
settings are in STARTUP script yet.)
The VxWorks configuration part can be done on that case when the IP module
drivers are independen from EPICS. At DESY we can do this useing our
CDI interface and adding this configuration possibility to CDI. (Which is
not in CDI V4.0, and a part is implemented in CDI V4.2 and plan to add more)
In case of IRM the connection between Epics and IP module has been
made by Epics driver support routine. So in thet case the proble
is same as any IO card (pre)configured by Epics and not depend on IP module.
At firs must be solve it in Epics. (hopefully it has been done in
next release (?) or at least we get more flexible configuration possibility)
I like the 'module' system, thats meaning yet: I use the same VxWorks
image (per board type) and download different moduls or same moduls with
different parameters, adding more feature for VxWorks kernel. After this
download the same EPICS and configure from startup useing different
values for the envinroment variablas.
As long as is possible I prefer this way to manage our IOC-s.
Regards,
Gabor Csuka
-----------
DESY, Germany
- Navigate by Date:
- Prev:
Re: rec/devSup advise needed Gabor Csuka
- Next:
Re: epics driver & device support for IRM Matthias Clausen DESY -MKV2/KRYK-
- 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 Bill Brown
- Next:
Re: epics driver & device support for IRM Matthias Clausen DESY -MKV2/KRYK-
- 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
|