EPICS Home

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  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: mrfioc2 release 2.2.0 (Supports VME-EVM-300 & VME-EVR-300 or not?)
From: Michael Davidsaver <[email protected]>
To: "Wang, Lin" <[email protected]>
Cc: EPICS Tech-Talk <[email protected]>
Date: Mon, 16 Oct 2017 10:48:10 -0500
On 10/16/2017 09:24 AM, Wang, Lin wrote:
> 
>> Do you have some specific requirement driving the use of vxWorks/VME, or
>> is this a matter of familiarity and experience?  
> 
> We are familiar with VxWorks, but Linux is also acceptable. At this moment, We do not have any real-time performance requirement yet.

I should note that in recommending Linux, I'm implicitly recommending
PCI variants over VME.  While I have some experience w/ VME+Linux, this
pre-dates my working with EPICS.

VME+Linux can be made to work, just be aware that (last I checked) the
default Linux interface for VME devices isn't enough to fulfill the
EPICS devLibVME interface.  So everyone who uses this combination has a
custom, usually vendor provided, OS driver.

>> To me, Linux is a much
>> more forgiving environment than RTEMS/vxWorks.  I've found non-RT Linux
>> to be more than capable of meeting the 10ms cycle deadline of FRIB.  PSI
>> reported a similar experience with RT Linux at the last week.
> 
> If we choose Linux, which Linux distribution would you recommend for running mrfioc2? Which Linux distribution do you and PSI use for running or testing mrfioc2?

Choice of Linux distribution shouldn't make much difference (both Debian
and Redhat derivatives work).  I've only tested with x86 32 and 64-bit,
though I expect that arm or ppc should work as well.

There is a stronger dependency on Linux kernel version as a small OS
driver is needed.  I do build tests against 3.2.1, 3.16.1, and 4.9.1
(aka default kernel for Debian 7, 8, and 9).  Let me know if you find
that later versions cause build/run failures.

References:
mrfioc2 release 2.2.0 Michael Davidsaver
Re: mrfioc2 release 2.2.0 (Supports VME-EVM-300 & VME-EVR-300 or not?) Wang, Lin
Re: mrfioc2 release 2.2.0 (Supports VME-EVM-300 & VME-EVR-300 or not?) Michael Davidsaver
Re: mrfioc2 release 2.2.0 (Supports VME-EVM-300 & VME-EVR-300 or not?) Wang, Lin

Navigate by Date:
Prev: Asyn GPIB proto file exception @writetimeout, @replytimeout James Larsson
Next: CSDataQuick beta 2 Wang Xiaoqiang (PSI)
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: mrfioc2 release 2.2.0 (Supports VME-EVM-300 & VME-EVR-300 or not?) Wang, Lin
Next: RE: mrfioc2 release 2.2.0 (Supports VME-EVM-300 & VME-EVR-300 or not?) Kalantari Babak (PSI)
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024