注册登陆后可查看附件和大图,以及购买相关内容
您需要 登录 才可以下载或查看,没有账号?注册会员
x
Windows系统下(Linux和MAC系统下请自行了解清楚)NI的各种软件、模块、工具包、驱动程序,使用NI许可证管理器来激活的,绝大部分的都可以使用NI Lincense Activator来激活:NI序列号Serial Number生成激活工具NI License Activator,LabVIEW/VBAI/VDM/VAS等软件模块工具包破解工具不限版本http://visionbbs.com/thread-490-1-1.html
视觉论坛的各种NI资源,除了视觉相关的模块有使用外,大部分的都不会使用,仅提供资源不提供技术支持。资源的下载地址一般会同时提供NI官方和百度网盘的地址。某些工具包NI地址失效或没有NI地址,只能使用百度网盘地址;如果百度网盘地址失效过期,可联系论坛客服更新。NI的服务器在美国,有时候速度很慢或下载容易出错,这样会造成安装时各种错误而无法安装。建议在下载完成后,对下载资源做校验和(NI一般会提供MD5或SHA256等)验证,与官方或视觉论坛提供的校验和对比,一致就可以安装;如不一致,则需要重新下载。视觉论坛早期下载上传的资源,基本上都是正常下载的资源;2019后下载的资源,都与NI的正确校验和对比过,保证是正确的资源才上传到百度网盘。校验和工具下载地址:文件Hash计算器FHash,文件校验和验证下载文件正确性验证,MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算http://visionbbs.com/thread-26524-1-1.html
LabVIEW 2010 MathScript Real-Time Module Win32ENG LV2010文本数学脚本实时模块MSRT2010 Win32位英文版下载
LabVIEW MathScript模块帮助您将自定义的文本数学代码部署到LabVIEW应用程序中和NI实时硬件上。
LabVIEW MathScript模块是LabVIEW编程环境的一个附加软件,包含750多种用于信号处理、分析和数学运算的内置文本函数。该模块还提供了一个交互式可编程界面。专为脚本编程而设计的MathScript交互式窗口提供命令行界面,方便用户下载、保存、设计和执行文本文件脚本。MathScript节点专为脚本部署而设计,作为LabVIEW的一项嵌入式功能,可将基于文本的变量与图形化LabVIEW代码的输入与输出连接起来。该模块适用于LabVIEW以及所有LabVIEW Real-Time硬件终端。
百度网盘下载地址:
链接: 请注册视觉论坛会员登录后购买附件下载查看
提取码: 请购买附件下载查看
NI官方下载地址:
请购买附件下载查看
NI下载器下载:
请购买附件下载查看
MSRT2010.txt
(1.09 KB, 下载次数: 0, 售价: 10 元)
LabVIEW 2010 MathScript RT Module ReadmeVersion 10.0 June 2010 This file contains important last-minute information about the LabVIEW 2010 MathScript RT Module, including installation instructions, new features, and known issues. Overview
System Requirements
Installation Instructions
Windows
Mac OS X
Linux
Upgrading from the LabVIEW 2009 MathScript RT Module
Accessing the Help
Finding Examples
New Features
Behavior Changes
Known Issues
Bug Fixes
OverviewLabVIEW MathScript is a text-based language you can use to write functions and scripts. You can process scripts using LabVIEW MathScript in the LabVIEW MathScript Window or a MathScript Node. Use the LabVIEW MathScript Window to edit and execute mathematical commands, create mathematical scripts, and view numerical and graphical representations of variables. Select Tools»MathScript Window to display this window. Use the MathScript Node to execute your LabVIEW MathScripts and other text-based scripts on the block diagram using the MathScript RT Module engine. You can save scripts that you create in the LabVIEW MathScript Window and load them in the MathScript Node and vice versa. System RequirementsIn addition to the system requirements for the LabVIEW Development System, the MathScript RT Module has the following requirements: - LabVIEW 2010 Full or Professional Development System
- At least 500 MB of disk space
Refer to the LabVIEW Release Notes, which are available in your LabVIEW software kit or on the National Instruments Web site, for additional system requirements and supported operating systems for LabVIEW 2010. (LabVIEW 64-bit) The MathScript RT Module is not supported in LabVIEW (64-bit). Installation InstructionsComplete the following steps to install the MathScript RT Module. WindowsYou can install all of your LabVIEW products—including the MathScript RT Module—using the LabVIEW Platform DVDs. You can find installation instructions for the module along with activation instructions in the following locations: - LabVIEW Release Notes, which are available in your LabVIEW software kit.
- LabVIEW Platform DVDs Readme, which is available on the top-level of LabVIEW Platform DVD 1.
To request additional LabVIEW Platform DVDs, refer to the National Instruments Web site. Note: If you purchased this product with an NI Software Suite or NI Product Bundle, use the installation media that shipped with your purchase to install this product. Mac OS XComplete the following steps to install the LabVIEW MathScript RT Module on Mac OS X. - Insert the LabVIEW MathScript RT Module installation CD and open LabVIEW MathScript 2010.mpkg from the Mac OS X subdirectory.
- Follow the instructions that appear on the screen.
Delete the following files or directories on the computer to manually uninstall the LabVIEW MathScript RT Module on Mac OS X: - /Applications/National Instruments/LabVIEW 2010/resource/mathscript.rsc
- /Applications/National Instruments/LabVIEW 2010/examples/MathScript/
- /Applications/National Instruments/LabVIEW 2010/vi.lib/imath/
- /Documents/LabVIEW Data/InstCache/
- /Documents/LabVIEW Data/MathScriptVIs/
LinuxComplete the following steps to install the LabVIEW MathScript RT Module on Linux. - Log into the system as root.
- Insert the LabVIEW MathScript RT Module installation CD. Use mount /mnt/cdrom to mount the CD. On some systems, the CD mounts automatically.
- To change the current directory to the mounted CD, enter the following command:
cd /mnt/cdrom/Linux - To run the installation script, enter the following command:
sh ./INSTALL
If you encounter the message bad interpreter: Permission denied, the CD might not have mounted with executable permissions. To correct this issue, enter the following command:
/bin/sh ./INSTALL
To run a script that uninstalls the MathScript RT Module on Linux, enter the following command:
sh ./UNINSTALL Upgrading from the LabVIEW 2009 MathScript RT ModuleThe following sections describe issues to be aware of when you upgrade to the MathScript RT Module 2010. Opening Applications Saved in LabVIEW 2009Due to enhancements to the LabVIEW compiler, LabVIEW 2010 requires more memory than previous LabVIEW versions when compiling VIs, particularly large VI applications. In LabVIEW 2010, when you open the top-level VI of a large application saved in LabVIEW 2009 or earlier that calls many .m files, LabVIEW might run out of memory and exit. (Windows 64-bit) If you encounter this situation, National Instruments recommends you open the VI on a computer with at least 4 GB of memory. (Windows 32-bit) Refer to the Fundamentals»Managing Performance and Memory»How-To»Extending Virtual Memory Usage for 32-bit Windows topic on the Contents tab of the LabVIEW Help for information about enabling LabVIEW to access more virtual memory. Disallowing Sharing of MathScript Cache Files on Computers with Multiple UsersThe MathScript RT Module 2010 installs VIs that improve the performance of the module. These VIs install to a public directory that is writable for all users of the computer so that LabVIEW can compile the VIs. However, if you want to prevent multiple users from sharing this directory, you can complete the following steps to make LabVIEW use a local directory for each user rather than the public directory. - Delete the InstCache directory from the <;Public Cache>\ directory. (Windows, Mac OS X) The directory is located at <;Public Cache>\National Instruments. (Linux) The directory is located at <;Public Cache>\natinst.
Note: Use the Get System Directory VI, available on the File Constants palette in LabVIEW, to return the location of the <;Public Cache> directory. - Create an empty file named UseLocalInstCacheForAllUsers.ini in the directory.
- Make the directory read-only. Ensure that non-administrator users have only read access to the directory.
This procedure causes LabVIEW to generate VIs in the \LabVIEW Data\InstCache directory instead of the public directory. You can use the Get System Directory VI to return the location of the directory. Accessing the HelpRefer to the MathScript RT Module book on the Contents tab of the LabVIEW Help for more information about the MathScript RT Module. Finding ExamplesRefer to the labview\examples\MathScript directory for LabVIEW examples for the MathScript RT Module. You can modify an example VI to fit an application, or you can copy and paste from one or more examples into a VI that you create. New FeaturesThe LabVIEW 2010 MathScript RT Module introduces the following enhancements and changes. LabVIEW MathScript Window EnhancementsThe LabVIEW MathScript Window includes the following enhancements: - (Windows) The Script Editor in the LabVIEW MathScript Window includes improved script-editing features, such as syntax highlighting, line numbers, a dialog box for finding and replacing text, and bookmarks with which you can mark lines of your script.
- The menu items in the Script Editor are reorganized to include new options. (Windows) The Edit menu in the Script Editor also includes items for finding and replacing text, navigating between bookmarks, and so on.
- On the Variables page, the Dimension column is renamed to Data. The Data column in the LabVIEW MathScript Window displays the value of the corresponding variable, or, if the value is too long to display, LabVIEW displays the dimension of the variable. This feature also exists in the LabVIEW MathScript Probe window.
Adding Output Terminals to MathScript NodesIn the MathScript RT Module 2009 and earlier, after you add an output terminal to a MathScript Node you must manually type the variable name with which you want to configure the output. In the MathScript RT Module 2010, after you enter your script in a MathScript Node, you can right-click the right side of the MathScript Node frame, move the cursor over the Add Output item in the shortcut menu, and select the variable for which you want to create an output from a list of variables detected in your script. New MathScript FunctionsThe MathScript RT Module 2010 includes the following new MathScript functions. You can use these functions in the LabVIEW MathScript Window or the MathScript Node: - The support class contains the rgb_to_grayscale function.
- The transforms class contains the realifft and realifft2d functions.
Refer to MathScript RT Module»MathScript RT Module Functions book on the Contents tab of the LabVIEW Help for more information about built-in MathScript functions. Performance ImprovementsThe LabVIEW MathScript Window executes code with performance similar to the MathScript Node due to performance improvements. Behavior ChangesThe LabVIEW 2010 MathScript RT Module introduces the following behavior changes to LabVIEW MathScript: - In the MathScript RT Module 2009, the default data type of MathScript Node input terminals you create is void. In the MathScript RT Module 2010, the default data type of input terminals you create is double-precision, floating-point numeric.
- In previous versions, the LabVIEW MathScript Probe window does not display variables you define but do not reuse in your script. In the MathScript RT Module 2010, the LabVIEW MathScript Probe window displays all variables you define in your script.
- When you specify indexes of matrix elements in previous versions, LabVIEW ignores indexes for any dimensions higher than 2. For example, when indexing an element of matrix a, LabVIEW treats a(1, 2, 3, 4); the same as a(1, 2); and does not return an error or warning. In the MathScript RT Module 2010, LabVIEW returns an error when you specify a value for a dimension greater than 2.
MathScript Function ChangesThe MathScript RT Module 2010 includes the following changes to built-in MathScript functions: - The bin_to_dec function does not accept letters or digits other than 0, 1, or white space.
- In the MathScript RT Module 2009 SP1, National Instruments recommends you use the fft and sort functions in a time-critical VI or timed structure only if you specify a vector for the a input. In the MathScript RT Module 2010, you also can use these functions in time-critical code with matrices as inputs.
- In the MathScript RT Module 2010, the format function modifies the display format of numbers differently than in previous versions, as described in the following table.
Syntax | MathScript RT Module 2009 Format | MathScript RT Module 2010 | Format | Example: 100 * pi = | format short | Scaled fixed-point format with 5 digits | Scaled fixed-point format with 4 digits after the decimal point | 314.1593 | format short e | Floating-point format with 5 digits | Floating-point format with 4 digits after the decimal point | 3.1416e+002 | format long | Scaled fixed-point format with 15 digits | Scaled fixed-point format with 15 digits after the decimal point | 314.159265358979326 | format long e | Floating-point format with 15 digits | Floating-point format with 15 digits after the decimal point | 3.141592653589793e+002 |
- The fread and fwrite functions include a byte input you can use to specify the byte order, or endian form, to use when reading and writing data, respectively.
- In the MathScript RT Module 2009, you can specify attributes for only 2D plots. In the MathScript RT Module 2010, you can specify attributes for 3D plots you generate with the line and plot3d functions.
- The b input of the linearsolve function accepts matrices.
- The a input of the lu function accepts non-square matrices.
- The median and meshgrid2d functions are suitable for use in deterministic applications when used according to certain guidelines.
Refer to the MathScript RT Module»Guidelines for Using LabVIEW MathScript in Real-Time Applications book on the Contents tab of the LabVIEW Help for more information about using MathScript with RT targets. - The sort function includes an optional order input you can use to sort the input elements in ascending or descending order.
- The std and var functions include a d input you can use to specify the dimension of x across which to calculate the standard deviation or variance, respectively, if x is a matrix.
- The str_to_double and str_to_num functions are no longer supported on RT targets.
- In the MathScript RT Module 2009, when you use the following functions to generate multiple plots, you must specify attributes for all plots or no plots. In the MathScript RT Module 2010, you can specify attributes for only the last plot, and LabVIEW uses the default attributes for previous plots.
- loglog
- plot
- semilog_x
- semilog_y
- Inputs that accept signals for the following functions now accept complex values. For example, the x and y inputs of the crosspsd function accept complex values in addition to real values.
- buffermx
- coherence_ms
- corrmx
- crosspsd
- psd_burg
- psd_covar
- psd_mcovar
- psd_periodogram
- psd_welch
- psd_yule
- pspec_eign
- pspec_music
- root_eign
- root_music
- spectrogram
- tf_estimateplot
Known IssuesYou can access the software and documentation known issues list online. Refer to the National Instruments Web site for an up-to-date list of known issues in the MathScript RT Module. Bug FixesThe following items are the IDs and titles of a subset of issues fixed in the LabVIEW 2010 MathScript RT Module. This is not an exhaustive list of issues fixed in the current version of the MathScript RT Module. If you have a CAR ID, you can search this list to validate the issue has been fixed. ID | Fixed Issue | 221496 | The index output of the 'sortrows' function should be one-based, not zero-based. | 213325 | Loading 2D plots should not take as long as loading 3D plots | 212439 | 'any', 'all', 'and', 'or', and 'xor' functions unnecessarily upcast Boolean inputs | 210616 | 'global' function should accept variable input strings | 208621 | Saved .m filename persists in the MathScript Script Editor even after creating a new script | 208615 | Documentation for some MathScript function not supported in the Run-Time Engine is confusing | 208395 | 'sort' function should allow sorting elements in either ascending and descending order | 206150 | Graph legends and palettes cannot be used in MathScript plot windows | 205801 | 'load' function fails to open read-only .mat files | 205136 | Legacy names need explanation in MathScript function documentation | 204405 | MathScript should return errors for unsupported ND array indexing | 203852 | Changing a .m file while in use by LabVIEW produces empty code | 202693 | Documentation about RT support of 'load' function should list supported syntax a = load(file) | 202249 | Changing a .m file from a script to a function does not recompile the calling script | 201119 | Context help for rt functions is missing | 200816 | MathScript Window and MathScript probe's "Swap X-Y" option does not work | 200735 | Saving a pie plot as BMP does not include percentage number labels | 200723 | Plot generated by 'bar3' function does not have first bar outlined with black lines | 199534 | Growing an empty array in a loop does not work | 197580 | Opening a MathScript VI created on a different machine results in a search dialog for MCStatic_ VIs | 196706 | VIs that call certain functions load with 'Failed to compile' error | 195487 | Indexing a constant variable, such as 'i' in a = i(1,:) using a colon does not work if code contains a warning glyph | 194745 | 'mod' and 'rem' functions with integer inputs should not upcast the values | 194665 | MathScript Nodes return automatic error handling dialog box even if 'error out' cluster on node is wired | 194138 | 'psd_welch' and other functions in the spectral analysis class do not accept complex input signals | 194037 | MathScript probe should show values of variables rather than dimension, display 'String' view for strings by default, and allow resizing much smaller | 193324 | MathScript search path is corrupted in unsaved LabVIEW projects | 191788 | 'interpolate1d' function output dimension behavior change when upgrading from 8.6 to 2009 | 190836 | VI with a MathScript Node that calls .m files can sometimes be broken even if there is no error | 189608 | 'median' function should return a vector when possible instead of an array | 187850 | Documentation correction: 'bin_to_dec' function does not consider letters or digits other than 0 and 1 in 'a' to be zeros in 2009 release | 187299 | Documentation addition: Behavior of numeric conversion functions 'int8', 'int16', etc. when input is of complex data type | 186041 | Script in MathScript Node appears to execute out of order with execution highlighting on | 185013 | Execution highlighting in MathScript Node appears to skip lines | 184237 | MathScript Node returns an error code but no error source description when a plot object is invalid | 183304 | Creating a new subplot removes the title of the first subplot | 183244 | Using unwired user-defined function inputs with short circuit operators can cause errors | 181131 | The title & X-Y labels are not correct for plot from function 'crosspsd' when no output arguments are specified | 180281 | Documentation correction: 'repeatmx' function help refers to 'c' as output when 'd' is the output | 177781 | "An error occurred in a SubVI call" path error not descriptive | 176786 | MathScript Node inputs with void data types cause brief unresponsiveness | 176211 | Attributes don't work unless specified for all plots | 176135 | The 'resample' function does not return a "memory full" error | 175691 | Changing the contents of a .m file while calling VI is running causes crash | 175388 | A conditionally defined variable from a user-defined function should not break VI if it will never execute | 174790 | Using the 'cd' in a MathScript Node displays a warning glyph even if no input arguments are specified | 174206 | Return meaningful errors for 'sound', 'soundscaled', 'wavplay', and 'wavrecord' functions | 173756 | Calling 'path' function with an integer input, such as 'path(1)', gives unhelpful error and clears path list in MathScript Window | 172387 | fwrite_xls and fread_xls needs to give meaningful error if computer does not have appropriate software installed | 171509 | 'updatechol' function returns less accurate results for CDB downdated case | 171353 | 'nchoosek' function should not accept inputs of Control Design and Simulation Module data types | 171022 | Tools>>Option>>MathScript page in French version of LabVIEW has overlapping text | 168379 | When plotting multiple vectors or matrices, cannot specify attributes for just one vector or matrix | 164712 | Documentation correction: List of functions not supported on RT does not denote functions installed with Control Design and Simulation Module | 158848 | Dragging a variable from 'Local' to 'Global' section in the MathScript Window 'Variables' list doesn't work | 158061 | Returning help for some legacy function names fails to return help for corresponding function name | 155368 | Variables you define but do not use later in a script don't appear in the MathScript probe | 154867 | Returning help for some legacy function names fails to return help for corresponding function name | 153539 | Output on MathScript Node with void data types gives confusing error message | 151999 | Indexing a variable using Boolean indices does not work as expected in the MathScript Window | 148323 | MathScript 'help' function should map incomplete legacy names to new names | 147028 | German string in LV German (Vista) cut off in Tools>>Options>>MathScript dialog box | 144739 | Tools>>Option>>MathScript page in German version of LabVIEW has overlapping text | 142972 | Replace indexing needs to support multiple assignments | 137913 | 'std' and 'var' functions should allow specifying the dimension of an input matrix across which to calculate the standard deviation/variance |
Important InformationCopyright © 2009–2010 National Instruments Corporation. All rights reserved. Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical, including photocopying, recording, storing in an information retrieval system, or translating, in whole or in part, without the prior written consent of National Instruments Corporation. National Instruments respects the intellectual property of others, and we ask our users to do the same. NI software is protected by copyright and other intellectual property laws. Where NI software may be used to reproduce software or other materials belonging to others, you may use NI software only to reproduce materials that you may reproduce in accordance with the terms of any applicable license or other legal restriction. For copyright notices, conditions, and disclaimers, including information regarding certain third-party components used in the MathScript RT Module, refer to the Copyright topic of the LabVIEW Help. Trademarks LabVIEW, National Instruments, NI, ni.com, the National Instruments corporate logo, and the Eagle logo are trademarks of National Instruments Corporation. Refer to the Trademark Information at ni.com/trademarks for other National Instruments trademarks. Other product and company names mentioned herein are trademarks or trade names of their respective companies. Patents For patents covering the National Instruments products/technology, refer to the appropriate location: Help» Patents in your software, the patents.txt file on your media, or the National Instruments Patent Notice at ni.com/patents. |