Thank you for your helpful comments. After delving further into both National Instruments and EPICS documentation, I’ve decided the expedient thing to do is to write a couple of Labview VI’s to publish and read
all the different Labview data types in EPICS and see what happens. The confusion, at least on my part, seems to come from there being different data types in EPICS database records and record fields, not to mention the many more data types in Labview.
From: firstname.lastname@example.org [mailto:email@example.com]
On Behalf Of firstname.lastname@example.org
Sent: Tuesday, October 29, 2013 6:06 AM
Subject: RE: Labview EPICS server and client data types.
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.
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.
Scanned by iCritical.