» Inter-Application Communication » File I/O
LabVIEW can share data with 3rd Party tools using File I/O. Communication using File I/O involves one program creating and saving the file, and the other program opening and accessing the file.
File I/O is an easy way of transferring data between applications. There is a minimal amount of programming to be done in LabVIEW to open and process the data in a file, and likewise to save data to a file. One benefit inherent to this type of communication is that all data is saved before being used, so a backup copy is available if needed. LabVIEW natively supports the following file types for saving and opening data:
The TDMS file format can be used to log data in LabVIEW and then perform post acquisition analysis of the data in DIAdem.
The following screenshot shows how to store simulated data in the TDMS file format from LabVIEW. The subsequent screenshot shows the data loaded in DIAdem for advanced analysis and reporting.
Figure 1: Storing measurement data in LabVIEW to TDMS file format
Figure 2: Reading measurement data in DIAdem
The following examples can be found from the NI Example Finder in LabVIEW, by navigating to Help»Find Examples...
Developer Zone Tutorial: NI TDM/TDMS Data Model
KnowledgeBase 10U39NAQ: Writing Binary Files with LabVIEW That Can Be Read by Other Applications
KnowledgeBase 42AANPH0: Reading and Writing TDM/TDMS Files
Ajayvignesh_MV wrote:
Is File I/O good for streaming the data between two processes?
For steaming? Definately NOT. If different executables, then TCP would be the proper way to stream data. Inside the same application, there are a lot more options (queues, user events, etc).
If you're on Linux (i.e. LVRT), just open a pipe. You can on Windows too, but the native API is clunky and requires a lot of finesse to avoid boundary-condition errors.