Labview

LabVIEW and ASAM-ODS




This document is designed to give the LabVIEW programmer all the required ASAM-ODS background and all the needed descriptions of the VIs this document comes with to successfully read from and write to an ASAM-ODS server or ATF file.





The VIs described in this document and their subVIs can be found in:


ASAM-ODS Example.llb Example VIs described in thisdocument


ASAM-ODS.llb Core VIs needed for any AOP project





ASAM-ODS Background/Connection/Setup


ASAM-ODS Data Reading


ASAM-ODS Data Writing


ASAM-ODS Object Querying


ASAM-ODS Data Storage Structure



ASAM-ODS Background/Connection/Setup

National Instruments applications LabVIEW and DIAdem both connect to ASAM-ODS servers via a shared data managementlayer called USI (Universal Storage Interface). In fact, ASAM-ODS data bases and ATF files are only some of the many data sources, including other industry standard files and customer legacy files, to which USI can connect LabVIEW and DIAdem. The USI layer abstracts the details of the particular data source and groups together input and output routines common to all data sources. The individualcomponents which plug into USI and contain the data source-specific routines for reading and sometimes writing data from/to the particular data source are called “Plugins” or “DataPlugins”. You must have LabVIEW version 7.1 or later in order to use USI to connect to ASAM-ODS data bases and ATF files.

[pic]





Install the AOP Plugin


Get the AOP Connection String


Query the AOPData Model


Adapt the Storage VIs to the AOP Model



Install the AOP Plugin

You may or may not have the required AOP Plugin to connect to your ASAM-ODS data base and ATF files. You can tell by launching one of the below-listed VIs and checking its run arrow. If the run arrow is white, you have the required AOP Plugin to connect to that ASAM-ODS data base with LabVIEW. If the run arrowis broken, you need to first download the required AOP Plugin before you can connect to that ASAM-ODS data base. Note that there are two VIs because there are two fundamentally different kinds of ASAM-ODS servers.
AOP3 Server ( “…\ASAM-ODS Example.llb\Get AOP3 Connection String.vi”
AOP5 Server ( “…\ASAM-ODS Example.llb\Get AOP5 Connection String.vi”
www.ni.com/diadem/dataplugins
If the“Get AOP# Connection String.vi” opens up with a broken run arrow, you can download and install the required Plugin from the above-linked ni.com/datplugins site. After installation, the next time you launch LabVIEW and load the above VI, it should be ready to run.
Get the AOP Connection String
Open the appropriate “…\ASAM-ODS Example.llb\Get AOP# Connection String.vi” if you don’t already have itopen from the previous (Install the AOP DataPlugin) section. The AOP/AOP5 Plugins both require an XML connection string to specify all the connection parameters (user name, password, server location, port number, etc.). The VI you now have open will pop up a configuration dialog to create this XML connection string.
[pic] [pic]
Note that you will need to use different parameters from thoseshown in the above dialogs, and this will probably require a conversation with your ASAM-ODS server administrator. Once you have the correct connection parameters entered above, clicking the button will result in the creation of the XML connection string, which will look like the following.
[pic] [pic]
Note that connecting to an ATF file requires a particularly simple connection string:C:\Path to Directory\Name of File.atf
In the remainder of this document the “Test ASAM-ODS.atf” file will be used to illustrate the methods of reading from and writing to an AOP server. You will hopefully find this fully functional example file helpful in acquainting yourself with the different topics, but you will no doubt want to try those same methods with your own AOP server. Note that in...