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  2013  2014  2015  2016  2017  2018  2019  <20202021  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  <20202021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: SoftIOC and Labview
From: "Baily, Scott A via Tech-talk" <tech-talk at aps.anl.gov>
To: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Cc: "Mostafa, Jalal \(IPE\)" <jalal.mostafa at kit.edu>
Date: Wed, 27 May 2020 17:04:30 +0000
If you’re writing a LabVIEW client application CALab sounds like the way to go.

If the goal is to serve data via EPICS, then you should consider running an EPICS IOC on the machine running LabVIEW.
lvPortDriver  ( https://github.com/sbaily/lvPortDriver ) will let you do this on any OS that can run EPICS and LabVIEW.
Your LabVIEW program starts the EPICS IOC, and lvPortDriver (an asynPortDriver class with LabVIEW wrappers) handles the communication between the IOC and LabVIEW.
For more information see:  https://conference.sns.gov/event/11/contributions/33/attachments/77/236/EPICSSept2016.pdf

------------
From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Ralph Lange via Tech-talk
Sent: Wednesday, May 27, 2020 1:36 AM
To: EPICS Tech Talk <tech-talk at aps.anl.gov>
Subject: Re: SoftIOC and Labview

My 2cts - your mileage may vary:

The NI implementations of CA (client and server) were indeed getting better over time, but they started at a very low level of compatibility.
Their newest versions are pretty much working (at least for scalars), but - especially for their CA server - you are always in for some surprises, and your clients might need special configuration when talking to an NI Channel Access server.

I can just underline what Gabriel wrote: In my experience (which is obviously biased as I was working at BESSY for a long time), CALab is the most reliable, robust and stable CA client for LabVIEW.
(Doesn't just look better - it works better, too!)

Cheers,
~Ralph

-----------------
On Wed, 27 May 2020 at 08:27, Gabriel Fedel via Tech-talk <mailto:tech-talk at aps.anl.gov> wrote:

I had the same problem with older versions of Labview. As soon I know 
the waveform implementation on Labview is wrong, so you shouldn't trust 
on it.

An alternative is CALab 
(https://www.helmholtz-berlin.de/zentrum/locations/it/software/exsteuer/calab/index_en.html), 
I've tried once and it looks much better than NI solution.
 

Navigate by Date:
Prev: Re: Unpredictable behaviour with PyEpics Matt Newville via Tech-talk
Next: Re: Strange problem with areaDetector driver Jörn Dreyer via Tech-talk
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  <20202021  2022  2023  2024 
Navigate by Thread:
Prev: Re: SoftIOC and Labview Mostafa, Jalal (IPE) via Tech-talk
Next: Strange problem with areaDetector driver Jörn Dreyer via Tech-talk
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  <20202021  2022  2023  2024 
ANJ, 31 May 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·