Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019 
<== Date ==> <== Thread ==>

Subject: Re: EPICS fsmRecord question
From: Michael Davidsaver <mdavidsaver@bnl.gov>
To: Jiro Fujita <jiro.fujita@gmail.com>
Cc: Michael Cherney <mcherney@creighton.edu>, CharlesCostello@creighton.edu, EPICS tech-talk <tech-talk@aps.anl.gov>
Date: Mon, 15 Jul 2013 10:28:49 -0400
On 07/13/2013 01:06 AM, Jiro Fujita wrote:
...what is the minimum version of EPICS Base should we be using? 

I developed fsmRecord against 3.14.10 and it should build against newer versions.  Also, it isn't doing anything special, the only part of OSI it uses is epicsMutex, so it will likely build against earlier 3.14 releases.

This is something we probably should have thought about before we started, but for a number of reasons, we didn't. 

And I didn't think to ask...


The subdetector system in question is mostly running EPICS base 3.13 or 3.12 (yes, we still have them around).  For a number of technical reasons it is not all that easy for us to recompile EPICS base 3.12 IOCs (although not impossible, I suppose). 

I wouldn't dream of discourage you from upgrading :)  However, I suspect it would be less work to port fsmRecord back.  If you were considering this you might have a look at StreamDevice which supports 3.13 (specifically the file StreamEpics.cc).  It might be as simple as replacing use of epicsMutex with a vxWorks semaphore.

My thought is we can always edit the database of those IOCs to add flnk to send the PV values to another PVs running on soft IOC somewhere to get the job done (not very elegant, but should work). 

This is possible, but some care is needed.  fsmRecord uses the normal db linking calls, so puts to output CA links queue a request and return immediately.  So the FSM might have to include extra states to check (and wait) until this has happened.


Michael


Replies:
Re: EPICS fsmRecord question Jiro Fujita
References:
EPICS fsmRecord question Jiro Fujita

Navigate by Date:
Prev: Re: StreamDevice send/recevie bit array problem Dirk Zimoch
Next: Re: Looking for STRUCK SIS3302 device driver Michael Davidsaver
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019 
Navigate by Thread:
Prev: EPICS fsmRecord question Jiro Fujita
Next: Re: EPICS fsmRecord question Jiro Fujita
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019 
ANJ, 20 Apr 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·