EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: PV name changes and epics extensions
From: Emmanuel Mayssat <[email protected]>
To: Don Dohan <[email protected]>
Cc: epics <[email protected]>
Date: Fri, 24 Aug 2007 16:48:13 -0700
IRMIS is definitely one of the solution I am looking for.
But how difficult is it to implement?
is IRMIS for Oracle databases only?
Are simple crawlers easy to program?
is there any other solution out there?

Is anybody on this list at SLAC and using IRMIS?
I definitely would like to have a short demo in the near future.

Thanks,
--
Emmanuel


On Fri, 2007-08-24 at 14:08 -0500, Don Dohan wrote:
> Emmanuel
> 
> This is one of the features of the IRMIS relational database. 
> 
> IRMIS consists of, in part, all of the PVs in your system.  A pv crawler 
> (a perl program) detects when an IOC reboots, then scans and expands 
> that IOC's st.cmd file to load the IRMIS database with that IOCs PVs.  
> This scanning is unobtrusive to the IOC.
> 
> Other crawlers have been written to scan CA clients.  At the APS, we 
> crawl for MEDM, ALH, and SDDS clients, and we are testing the SNL 
> crawler written at SLAC.  We intend to crawl save/restore files as well 
> (future).  For each CA client instance, a list of resolved PVs is 
> generated, and inserted into the IRMIS database.
> 
> Taking the MEDM client as an example, the crawler resolves the macro 
> substitutions for nested MEDM screens, so that it tells you which .adl 
> file in the chain needs to be fixed if a given PV is removed.
> 
> Crawlers for other CA clients have been written at other facilities - 
> EDM, DM/2K for example.
> 
> Don Dohan
> 
> Emmanuel Mayssat wrote:
> > Another question about software upgrade...
> >
> > Let's say that I change the name of PV in my epics database.
> > Potentially with this change, I could break epics extensions.
> > Medm of course, but also feedback system, PV backup, etc.
> >
> > Is there a way to know which extensions will break if I change a PV
> > name? (may keeping track for each extension of the used PVs in a flat
> > file is the solution, but is there any other, smarter ones?)
> >
> > --
> > Emmanuel
> >
> >   


Replies:
Re: PV name changes and epics extensions Don Dohan
References:
PV name changes and epics extensions Emmanuel Mayssat
Re: PV name changes and epics extensions Don Dohan

Navigate by Date:
Prev: RE: Network plug and play epics devices Emmanuel Mayssat
Next: Re: ethernet IP John Dobbins
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: PV name changes and epics extensions Don Dohan
Next: Re: PV name changes and epics extensions Don Dohan
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Nov 2011 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·