NI does not actively maintain this document.
This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.
You can contact us by phone, email, or the discussion forums. Visit the NI Website to contact us. If you are contacting NI in regards to a specific issue, be sure to reference the ID.
The following items are known issues in LabVIEW 2013 MathScript Module sorted by Date.
ID | Known Issue | |||||
---|---|---|---|---|---|---|
52985 4DJFLU00 Return | Save for Previous on a VI with MathScript results in broken VI If you select File»Save for Previous Version and save a VI that contains a MathScript Node for LabVIEW 8.0, the VI is broken when you load it in LabVIEW 8.0. Workaround: To correct this problem, load the VI in LabVIEW 8.0 and then modify the script in the MathScript Node. For example, add and remove a space. Then click the block diagram outside of the MathScript Node. When you click the Run button, the VI runs correctly.
| |||||
114532 Return | MathScript cannot create a subplot with multiple 3D graphs on it MathScript always creates a new plot window for 3D graphs, such as surf and mesh. Workaround: N/A
| |||||
99061 Return | MathScript Probe on a reentrant clone attaches to the original If you try to probe a MathScript node on a clone of a reentrant VI, the probe will actually attach to the original VI instead. Workaround: Turn off reentrant execution on the VI that contains the MathScript node before you attach the MathScript probe.
| |||||
194964 Return | RT Target may crash when closing the block diagram of a running VI with the MathScript Probe If you are running a VI on a Real-Time target with a MathScript Probe attached to a MathScript node, closing the block diagram may cause the target to crash. Workaround: Close the MathScript Probe before closing the block diagram.
| |||||
195525 Return | MathScript search path incorrectly shows one of the paths to be invalid When the project is moved, one of the paths in the search path wrongly shows up as invalid. Workaround: After saving the project, open the search path page and click ok.
| |||||
174668 Return | Removing inner function in .m file breaks VI When a referenced .m file contains two functions, one of which calls the other, removing the bottom function (and changing the top function to not depend on it) breaks the caller VI. Workaround: This is just an extraneous error appearing in the error list window. If all the other errors in the caller VI are fixed, the VI becomes good.
| |||||
232284 Return | Attaching a probe to large MathScript Node while running on RT can cause connection loss If a large MathScript Node is running on a RT target and you try to attach a probe, you occasionally lose connection to the target. If you then reconnect, the probe will work normally. Workaround: N/A
| |||||
234580 Return | Running 'clc' clears the output of some commands executed after calling it If 'clc' is used, it should clear the output window then run the script that follows it. The output window should populate with the output of the rest of the script. Instead, 'clc' ' clearis the output of some of the later commands in the same script. Workaround: N/A
| |||||
127425 Return | Filled Contour Plot does not recognize hold command When using a filled contour plot, one cannot then "hold" the plot in order to plot more on top of it. Plotting additional data will clear the plot. Workaround: N/A
| |||||
138460 Return | Title function does not work with 3D plot The title function has no effect on a 3D plot. Workaround: N/A
| |||||
187387 Return | MathScript Probe can become unresponsive When probing a MathScript node that writes to large matrices repeatedly the probe can become unresponsive. Workaround: N/A
| |||||
223370 Return | Opening a VI with a MathScript node on a machine with invalid MathScript license may cause a error dialog box to show up When you open a VI with a MathScript node on a machine that does not have valid MathScript license, you may see a error dialog pop up reporting an 'insanity' error. Workaround: It is cosmetic error and can be safely ignored
| |||||
290936 Return | The fread function returns variant data type even when type is specified The fread function returns variant data even when the parameter specifying the type of data you are reading is used. Workaround: Use data type conversion after the function to cast to the appropriate type.
|
Document last updated on 7/22/2013