When you select Tools�Compare�Compare VIs and use the Compare VIs dialog box, LabVIEW does not display differences between values of cluster constants.If you wire a hex value greater than x7FFFFFFF as an unsigned, 32-bit integer to a Formula Node, LabVIEW coerces the value to 0.If you configure the Call Library Function Node to call a DLL written in C with these same settings, LabVIEW works correctly. If you configure a Call Library Function Node to call a LabVIEW DLL, LabVIEW hangs if you place a checkmark in the Specify path on diagram checkbox on the Function page of the Call Library Function dialog box and you select Run in UI thread in the Thread control.Remove the String To Path function wired to the vi path input of the Open VI Reference function to correct the error. x or earlier opens another VI by specifying the example VI name as a path in the Open VI Reference function, you receive an error when you run that example in LabVIEW 8. The Read From Measurement File Express VI returns an error if you call it on the same file multiple times, which makes using this Express VI in a subVI problematic.To correct this problem, use the File I/O VIs to write to text files. You cannot use the DataSocket Write function to write to a text file.You cannot use the http protocol with the DataSocket VI and functions in LabVIEW-built shared libraries. If automatic saving for recovery is enabled, LabVIEW notifies you the first time the VI you are modifying cannot be saved.
0 Comments
Leave a Reply. |