EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  <19961997  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  Index 1994  1995  <19961997  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 
<== Date ==> <== Thread ==>

Subject: Re: epics driver & device support for IRM
From: [email protected] (Bill Brown)
To: [email protected], [email protected], [email protected]
Cc: [email protected]
Date: Wed, 21 Aug 96 09:47:52 PDT
We've done some work with the IRM using the code supplied by desy.  It all
seems to work without a great deal of trouble, but then that was expected,
wasn't it.

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?


Disclaimer:  Any opinions are my own and have	    |  -bill
    nothing to do with the official policy or the   |   [email protected]
    management of L.B.L, who probably couldn't      |   Berkeley, CA
    care less about employees who play with trains. |   aka [email protected]
    

PS - Many thanks to all who responded to my recent question about "edge
triggered" record processing.  I started out using one of the suggested
approaches and it turned out, once I understood the _REAL_ problem, to be
very simple.  All it took was a dfanout record to drive the .DISA fields
of the two bo records, and setting the .DISV field of one record to "0"
and the other one to "1".  Of course, I didn't see that until I'd gotten
"edge detection" working with a calc record.  Yet another learning experience!
(YALE? - I think that one's taken!)


Navigate by Date:
Prev: subscribe Stathis Stiliaris
Next: Re: epics driver & device support for IP modules Andrew Johnson
Index: 1994  1995  <19961997  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: tclCa package (was et_wish) Claude Saunders
Next: Re: epics driver & device support for IRM Gabor Csuka
Index: 1994  1995  <19961997  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 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·