Academic Company Events Community Support Solutions Products & Services Contact NI MyNI
3 ratings:
 3 out of 5   

Why is My Write File VI from LabVIEW 7 Replaced with a Write Binary File VI in LabVIEW 8?

Primary Software:
Primary Software Version: 8.0
Primary Software Fixed Version: N/A
Secondary Software: N/A

I've written code in LabVIEW 7 that outputs my data to a text file. However, when I upgrade my code to LabVIEW 8, I notice that all of the Write are replaced with Write to Binary Why did this happen and how will it affect my code?

LabVIEW 8 replaces the Write with a Write Binary because various enhancements have been made to the VIs for ease of use. The replacement of the Write with the Write Binary will not influence the readability of the file.

In LabVIEW 7, the Write is often used to write both text and numerical data to a file. If you try to read these files in Windows Notepad, you'll notice that text is readable, but numerical values are represented by gibberish. The reason has to do with how LabVIEW writes information to files. At the core of all of the File I\O VIs (Write to, Write Character to, Write to I16, etc.) is the Write This VI always writes information in binary format. Strings are written as ASCII numbers in binary format and numeric data types are written in binary format.

Notepad was designed to interpret ASCII characters written in binary, which is why text is readable in Notepad. However, Notepad assumes that all information in a file is ASCII. Therefore if a binary byte appears in the file for which there is no corresponding ASCII character, Notepad represents the byte with an empty box or it may be translated into gibberish.

Related Links:
LabVIEW 8.6 Help: Write to Binary File Function


Report Date: 11/22/2005
Last Updated: 05/07/2013
Document ID: 3RLAEPMY

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
  1 2 3 4 5
Please Contact NI for all product and support inquiries.submit