Archived: LabVIEW 2013 MathScript RT Module Known Issues

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.

Overview



This document contains known issues for the LabVIEW 2013 MathScript RT Module. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.

Contacting NI

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.

Known Issues by Date

The following items are known issues in LabVIEW 2013 MathScript Module sorted by Date.

52985 4DJFLU00Save for Previous on a VI with MathScript results in broken VI
114532MathScript cannot create a subplot with multiple 3D graphs on it
99061MathScript Probe on a reentrant clone attaches to the original
194964RT Target may crash when closing the block diagram of a running VI with the MathScript Probe
195525MathScript search path incorrectly shows one of the paths to be invalid
174668Removing inner function in .m file breaks VI
232284Attaching a probe to large MathScript Node while running on RT can cause connection loss
234580Running 'clc' clears the output of some commands executed after calling it
127425Filled Contour Plot does not recognize hold command
138460Title function does not work with 3D plot
187387MathScript Probe can become unresponsive
223370Opening a VI with a MathScript node on a machine with invalid MathScript license may cause a error dialog box to show up
290936The fread function returns variant data type even when type is specified



IDKnown 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.

Reported Version: 8.5  Resolved Version: N/A  Added: 09/01/2007
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

Reported Version: 8.6  Resolved Version: N/A  Added: 08/01/2008
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.

Reported Version: 8.6  Resolved Version: N/A  Added: 08/01/2008
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.

Reported Version: 2009 SP1  Resolved Version: N/A  Added: 06/17/2010
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.

Reported Version: 2009  Resolved Version: N/A  Added: 06/17/2010
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.

Reported Version: 2009  Resolved Version: N/A  Added: 07/29/2010
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

Reported Version: 2009 SP1  Resolved Version: N/A  Added: 06/20/2011
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

Reported Version: 2010  Resolved Version: N/A  Added: 07/21/2011
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

Reported Version: 8.6  Resolved Version: N/A  Added: 07/18/2012
138460

Return
Title function does not work with 3D plot
The title function has no effect on a 3D plot.

Workaround: N/A

Reported Version: 8.6  Resolved Version: N/A  Added: 07/18/2012
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

Reported Version: 2009 SP1  Resolved Version: N/A  Added: 07/18/2012
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

Reported Version: 2010  Resolved Version: N/A  Added: 07/18/2012
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.

Reported Version: 2010  Resolved Version: N/A  Added: 07/18/2012

Document last updated on 7/22/2013

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).