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 EPICS server and client data types. |
From: | <[email protected]> |
To: | <[email protected]> |
Date: | Tue, 29 Oct 2013 10:06:19 +0000 |
Brian, I’ve never tried using the LabVIEW client/server with anything other than a non-LabVIEW client/server in the setup so have always used the CA supported items only otherwise that would fall over. If you can share
your VIs with me I may be able to help, but at a guess this is the downside of how NI have enacted their I/O servers for EPICS by tying them in to shared variables, in that shared variables in LabVIEW have all those data types available, while the server doesn’t.
You may find that NI have been kind are will cast to a type that CA can use. As far as using the Auto data type, I haven’t looked for this question on the NI fora yet, and I’m very aware of the lack of information regarding the functionalities of LabVIEW and
EPICS integration, so would recommend either asking the question there (you may get a response from the right people fairly quickly, or just me again) if you haven’t already, or just biting the bullet and trying it.
Kathryn From: [email protected] [mailto:[email protected]]
On Behalf Of Vaughn, Brian When configuring a Labview EPICS Server I/O Server, one is able to select from more data types than are available when configuring a Labview EPICS Server I/O Client. For example, you can create a network-published shared
variable with a data type: array of booleans, and link it to an EPICS PV, but when trying to create a corresponding PV in the client, there is no option for the data type: array of booleans. The same situation exists for unsigned integers, etc. Does anyone have experience working around this? There is an “Auto” data type available in the Client configuration, but I am leery of using it, especially since I can’t find detailed documentation regarding it. Any help
would be appreciated. --
|