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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: LabView interface to EPICS |
From: | Emmanuel Mayssat <[email protected]> |
To: | "Faucett, John A" <[email protected]>, tech-talk <[email protected]>, "[email protected]" <[email protected]> |
Cc: | Emmanuel Mayssat <[email protected]>, "[email protected]" <[email protected]> |
Date: | Thu, 19 Sep 2013 15:05:26 -0700 |
John,
Let me see if I understand correctly. You use a device like the cRIO ( http://www.ni.com/compactrio/ ) that include a FPGA. That FPGA is running code (VHDL +) generated and downloaded through LabView. The FPGA is programmed for 2 functions: (1) interface with the hardware (2) run an embedded EPICS IOC. Once the FPGA is programmed, you can interface with its process variable (PV) to change (let's say) a digital output. Is LabVIew only only to configure the FPGA? Or is LabVIew also used to control the FPGA (I/O), i.e. interact with PVs ? If that's the case, do you use Labview GUIs that interact with multiple EPICS devices or IOCs? (That is can labview GUI be used as a replacement for edm/BOY/etc?) -- Emmanuel From: [email protected] To: [email protected] Subject: Re: LabView interface to EPICS Date: Thu, 19 Sep 2013 21:20:06 +0000 Emmanuel Mayssat wrote:
LANSCE is using this for all future generic analog and binary devices. We have 45 such production IOCs now (compared to 26 VME-based IOCs).
Fairly good cost per channel. We can use very similar setups for most IOCs. We will convert most Camac and our home-grown RICE systems to these.
John Faucett
LANSCE
LANL
Correspondence |