EPICS Controls 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  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  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: LabView interface to EPICS
From: <[email protected]>
To: <[email protected]>
Date: Fri, 20 Sep 2013 09:33:41 +0000
Back on the original question, yes there are actually quite a few people using LabVIEW and EPICS - including us at ISIS at the moment.
Benefits and Drawbacks will vary depending on situation. What are the benefits and drawbacks of using EPICS with a C program? Or with CSS (which is one of many interfaces)? Depends on situation...

I'm a LabVIEW developer primarily moving into EPICS, so have a different bias when it comes to this question than the EPICS developer having to use LabVIEW, or the C developer learning both for example.

John seems to describe one of the best uses for the NI setup which is the integrated hardware version (not what my workplace uses - we interact in a different way), and there are different ways of interacting. The shared memory between VxWorks and LabVIEW is a nice solution if what you have is NI hardware, and programming an FPGA in LabVIEW if you're new to FPGAs and don't like writing thousands of lines of VHDL can be quicker - but it won't suit everyone. G (the language LabVIEW actually programs) is just a language, and it will suit some people and not others, and like the difference between C and C# the language and interface is evolving, and continues to do so.

If you have existing IOCs and just want to look at PVs in LabVIEW then caLab (http://www-csr.bessy.de/control/SoftDist/CA_Lab/) is the way to go. If you want to serve data from LabVIEW and don't have the hardware to use the shared memory option, then you either have to use the DSC module (and there are a couple of downsides to that from an EPICS point of view), or find another solution. If you are writing from scratch, then you can write an IOC to run alongside and caLab is still a good option, if you have existing code, or are using manufacturer code (we had the situation of both) then the solution my colleague came up with for Windows is fine. If you're running LabVIEW on a linux based system, then something different again may be needed, but I'm sure it can be done in other ways that would be of interest.

Kathryn (CLD)

-- 
Scanned by iCritical.


References:
LabView interface to EPICS Emmanuel Mayssat
Re: LabView interface to EPICS Scott Baily

Navigate by Date:
Prev: Re: LabView interface to EPICS Scott Baily
Next: Re: LabView interface to EPICS Dirk Zimoch
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  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: LabView interface to EPICS Scott Baily
Next: Re: LabView interface to EPICS Dirk Zimoch
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  2020  2021  2022  2023  2024 
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 ·