注册登陆后可查看附件和大图,以及购买相关内容
您需要 登录 才可以下载或查看,没有账号?注册会员
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
NI LabVIEW 2013 Win32ENG 32位LV2013英文版下载
文件大小: 1404691232 字节 (1.31 GB)
修改日期: 2013-08-08 10:50
MD5: 0b0b5ef75faa918b06a6314246863173
SHA1: 740fa62e93c395f7d3bf4e470565fddce24beb96
SHA256: e9cbebb9748dc0f54ea3d37400ae825647659dee63ed490f70b33ef9b8bd2f3a
CRC32: 3d6cb5c1
百度云盘下载:
链接: 请注册视觉论坛会员登录后购买附件下载查看
提取码: 请购买附件下载查看
NI官方下载地址(可能无效或无法下载完成):
请购买附件下载查看
下载器:
请购买附件下载查看
LV2013ENG.txt
(891 Bytes, 下载次数: 53, 售价: 10 元)
LabVIEW 2013 Readme for WindowsVersion 13.0.0 June 2013 This file contains important information about LabVIEW 2013 for Windows, including installation instructions, a partial list of bugs fixed for LabVIEW 2013, and known issues. Refer to the National Instruments website for the latest information about LabVIEW 2013. Refer to the labview\readme directory for readme files about LabVIEW add-ons, such as modules and toolkits. System Requirements Installation Instructions Known Issues LabVIEW 2013 (64-bit) Additions to the LabVIEW Help Bug Fixes Accessing the Help Finding Examples Automating the Installation of NI Products How to Use NI Software with Microsoft Windows 8 NI Software Support for Microsoft Windows Vista, Windows XP, and Windows Server 2003 System RequirementsWindows | Run-Time Engine | Development Environment | Processor | Pentium III/Celeron 866 MHz or equivalent | Pentium 4M or equivalent | RAM | 256 MB | 1 GB | Screen Resolution | 1024 x 768 Pixels | 1024 x 768 Pixels | Operating System | Windows 8/7/Vista (32-bit and 64-bit)
Windows XP SP3 (32-bit)
Windows Server 2008 R2 (64-bit)
Windows Server 2003 R2 (32-bit) | Windows 8/7/Vista (32-bit and 64-bit)
Windows XP SP3 (32-bit)
Windows Server 2008 R2 (64-bit)
Windows Server 2003 R2 (32-bit) | Disk Space | 382 MB | 3.5 GB (includes default drivers from the NI Device Drivers DVD) | Color Palette | N/A | LabVIEW and the LabVIEW Help contain 16-bit color graphics. LabVIEW requires a minimum color palette setting of 16-bit color. | Temporary Files Directory | N/A | LabVIEW uses a directory for storing temporary files. National Instruments recommends that you have several megabytes of disk space available for this temporary directory. | Adobe Reader | N/A | You must have Adobe Reader installed to search PDF versions of all LabVIEW manuals. | Note The following list describes restrictions for using LabVIEW on Windows:- LabVIEW does not support Windows 2000/NT/Me/98/95 or Windows XP x64.
- You cannot access LabVIEW using a Guest account on Windows.
| Installation InstructionsDepending on whether you are installing LabVIEW for the first time or upgrading from a previous version, refer to one of the following documents for information about installing LabVIEW: - LabVIEW Installation Guide—Includes information about installing LabVIEW, modules and toolkits, drivers, and hardware.
- LabVIEW Upgrade Notes—Includes information about protecting existing VIs and projects before you install a new version of LabVIEW, as well as upgrade and compatibility issues and a complete list of new features in LabVIEW 2013.
You can access the LabVIEW Installation Guide and the LabVIEW Upgrade Notes at ni.com as well as on the installation media. 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. LabVIEW Updates and NotificationsNational Instruments posts information about critical updates and security notifications on ni.com. Visit ni.com/info and enter Info Code updates to access this information. Known IssuesYou can access the software and documentation known issues list online. Refer to the National Instruments website for an up-to-date list of known issues in LabVIEW 2013. LabVIEW 2013 (64-bit)When run on Windows (64-bit), LabVIEW 2013 (64-bit) provides access to more memory than a 32-bit operating system or a 32-bit application can provide. LabVIEW 2013 (64-bit) includes nearly all of the development environment features of LabVIEW 2013 (32-bit). Refer to the National Instruments website for information about obtaining a copy of LabVIEW 2013 (64-bit). Supported HardwareLabVIEW 2013 (64-bit) supports many hardware devices. Refer to the National Instruments website for information about drivers compatible with LabVIEW 2013 (64-bit). For GPIB devices, you must use at least NI-488.2 2.6 for Windows. Refer to the specific hardware documentation for more information about compatibility with LabVIEW 2013 (64-bit). Supported ModulesLabVIEW 2013 (64-bit) supports only the NI Vision Development Module. Refer to the Vision Development Module documentation for more information. No additional modules support LabVIEW 2013 (64-bit). Additions to the LabVIEW HelpThe following list contains additional changes to LabVIEW that are not included in the LabVIEW Help, the LabVIEW Upgrade Notes, or both: - Because LabVIEW 2013 may apply different compiler optimizations on different machines, you may need to perform additional steps to guarantee that a built application contains the same binary contents when built on different machines. Refer to the National Instruments website for more information about reproducing builds in LabVIEW 2013.
- If you create a VI that overrides a property accessor VI in a parent LabVIEW class, you must provide the same name and folder path in the property definition folders for both the child and parent classes.
Bug FixesThe following items are the IDs and titles of a subset of issues fixed in LabVIEW 2013. This is not an exhaustive list of issues fixed in the current version of LabVIEW. If you have a CAR ID, you can search this list to validate the issue has been fixed. ID | Legacy ID | Fixed Issue | 39604 | 49UBP4LE | Write to Clipboard Method consumes 100% of CPU for several minutes | 43931 | 4GPF7QYE | Save Report to File.vi copies images from Temp rather than moving them | 91672 | 477M7K00 | Large amounts of data in combo box can appear to hang LabVIEW | 136939 | — | Dragging an unsaved VI from one project to another, and then closing the original project without saving corrupts the VI | 138552 | — | Load VRML File.vi missing "error in" terminal | 148149 | — | Event Structure cases can incorrectly remap to other dynamic events | 214989 | — | Dropping a System OK button silently removes any existing key binding for the key | 221251 | — | Shared Variable values discarded after system restart | 233963 | — | Service Locator does not work when installed to a path containing stress characters | 240362 | — | Image in Header or Footer.vi created HTML-files with one additional unwanted '<' character | 242214 | — | LabVIEW does not marshal .NET objects, so you cannot make a LabVIEW .NET assembly with a usable .NET refnum in the connector pane | 248755 | — | Zoom, pan, and rotate sometimes cause 3D objects to move in 3D Scene Displays | 253088 | — | Programmatic tab view changes sometimes fail if front panel controls are being updated with property nodes | 256978 | — | Custom Font Setting tokens in LabVIEW.ini file are overwritten when you modify any other part of the INI file | 279047 | — | Coercing a cluster containing a cluster to a variant can cause the inner cluster to have its labels change | 280941 | — | DWarn: ProjectItem.cpp line 8914 sometimes thrown when using auto-populating folders | 287984 | — | lvanlys.dll fails to load on an 8 core processor | 288741 | — | Non-handled, registered dynamic events reset the Event structure timeout | 294464 | — | Connected PSP property returns error on Shared Variables that have write only access | 300375 | — | Scan From String returns error when using %y%m formatting with 2 digit years | 301753 | — | SMTP Email Send Message VI: Subject line with more than 45 connected characters causes error | 303503 | — | When a LVM file is read by the Read from Measurement File Express VI, the Y Unit attribute is ignored | 306025 | — | Changing the front properties of a front panel object affects all objects created after it | 309897 | — | Scan from String incorrectly parses a string containing SI notation | 312458 | — | Fatal Internal Error: "proptype.cpp" sometimes displayed when programmatically exiting LabVIEW | 312533 | — | Private member VIs of a library can be exported in .NET interop assemblies | 315663 | — | Files inside a NIER Report have the incorrect date | 317314 | — | LabVIEW "Terminal" based web services don't display more than 6 digits of precision | 318263 | — | Changing a type def text ring control to a constant causes the display format to change to floating point | 319888 | — | Using NaN in Y array of XY Graph causes line not to plot | 321518 | — | Nested source-only type-defined clusters may not propagate changes to calling VIs | 322705 | — | Find and Replace text sometimes does not find all instances of text | 323078 | — | Silver XY Graph's legend does not snap to upper-right corner of graph when control is set to fit to pane | 325150 | — | The tip strips for the Variant To/From Element nodes on the In Place Element structure are missing | 330806 | — | Incorrect time stamp plotted when using Express VIs | 331293 | — | Font changes to XY Graph affect non-selected controls | 334314 | — | Creating an Override VI for a child class that has a parent in a Packed Project Library gives error 1035 | 334661 | — | Pane setting "Scale Objects While Resizing" is disabled after programmatically disabling scaling and then reenabling it for a single object | 339553 | — | Under certain conditions, wiring a mismatching data type to a Property Node input does not cause a broken run arrow | 339661 | — | Using the Export to CSlipboard method with a Mixed Signal Graph causes LabVIEW to crash | 342148 | — | Using a Boolean reference as the first item in a cluster can cause LabVIEW to crash | 346295 | — | Cannot create negative user-defined error codes in the Edit Error Code Assistant | 347249 | — | Keeping the mouse over the drop-down menu for a combo box causes high CPU usage | 352625 | — | Creating patches for an installer leaves multiple entries in Add/Remove Programs | 354737 | — | Running eight remote front panel executables on the same port on the same computer causes significant performance degradation | 354827 | — | Polymorphic VIs break the wires connected to their outputs when switching between a specific type and Automatic | 354829 | — | MathScript Node hangs using certain data sets for linear and cubic 2D interpolation | 355198 | — | The Revision History dialog always appears when building an executable containing LabVIEW classes even if they are saved | 355966 | — | Changes to typedef enum sometimes do not prompt affected open VIs to save | 356466 | — | Stopping VIs and immediately closing project may crash LabVIEW | 357219 | — | Pasting into the Icon Editor stretches the clipboard image in the x and y directions | 358049 | — | When a specific VI is opened and closed, LabVIEW remains in the task bar, with no windows open | 359369 | — | Application Font change not applied correctly when pasting text | 360520 | — | Crash when dropping a cluster with a disabled table into an empty array control | 360757 | — | Deploying a project created with the Actor Framework template makes LabVIEW unresponsive | 361635 | — | Importing strings to a cluster containing two or more tables throws an error | 361636 | — | Ignore Timestamp property does not work for Mixed Signal Graphs | 361793 | — | I/O tags with names that are identical except for case behave differently in a built application | 362742 | — | Updating multiple shared variables' Networking Published: Binding Project Path crashes LabVIEW | 362812 | — | Quit LabVIEW primitive does not work in subVIs called by an Asynchronous Call by Reference function | 363363 | — | Undo does not work for the VI Properties dialog Reentrancy setting | 364154 | — | Cross-linking can occur if you use a sample project that contains an FPGA target before installing the LabVIEW FPGA Module | 364607 | — | Invalid Network VISA reference causes DAQmx calls to slow in different loop | 364643 | — | Cursor does not associate with correct plot when using Cursor.Plot property with waveforms of different scales | 365087 | — | Register Event Callback crashes LabVIEW when wired to front panel object | 366427 | — | .NET property exceptions are not propagated by the error wire if called with a LabVIEW Property Node | 367445 | — | Source distribution of a class that uses dynamic dispatch can become broken looking for a missing subVI | 369125 | — | Shortcut menu does not allow the user to select items using the right mouse button | 369472 | — | Polymorphic VIs lose their icons when built into packed libraries | 369537 | — | Trying to set the "Active Bus" property on a Digital Waveform Graph crashes LabVIEW | 369691 | — | LabVIEW crashes if a Plot Visibility Checkbox of a Silver Waveform Graph is customized | 369833 | — | Draw VIs sometimes create corrupt PNG images when used with the LV Image to PNG Data VI | 369872 | — | Polymorphic VIs are not password-protected when built into source distributions | 371030 | — | A Waveform Graph incorrectly shows more peak plots when doing peak detection in combination with certain bar plot styles | 372390 | — | Hermite Interpolation 1D VI does not correctly interpolate certain data sets | 373396 | — | Sub-diagram labels that have been resized do not maintain their size when you edit them | 373399 | — | Resizing a sub-diagram label and bolding text within it bolds other text on the block diagram | 374196 | — | A Call Library Function Node referencing a function that does not exist within an existing DLL attempts to load despite being in a Diagram Disable structure | 375002 | — | Old library icon template persists on lower layer of VI icon after making library icon changes | 375760 | — | Displaying transposed array data on a Waveform Chart typedef causes crash during execution | 375872 | — | Crash when setting a floating-point numeric control to Inf, -Inf, or NaN when the control is configured for relative time display format | 376574 | — | Launching the Getting Started Window repeatedly can launch a blank VI instead of the Getting Started Window | 376714 | — | Using the Merge VIs utility with VIs that contain a tab control causes LabVIEW to hang | 377021 | — | Primitives are not correctly overloaded for Silver Matrix controls | 378888 | — | The Mixed Signal Graph does not correctly label plots in LabVIEW 2012 | 378947 | — | MD5Checksum File VI returns the wrong value for files larger than 4GB | 379023 | — | Items with colons in their localized names do not drop with Quick Drop in LabVIEW German | 379095 | — | Changing display format on an EXT indicator produces an "End of file encountered" dialog | 379444 | — | Register Event Callback does not work in LabVIEW 2012 Base Development System | 380475 | — | Data returned from a LabVIEW built .NET Assembly that unbundles a cluster is incorrect | 380741 | — | Array Subset function can add an extra value to the output array when used on a fixed-sized array | 381638 | — | Waveform chart x-axis scales incorrectly when Plot Area scrolls for new data | 381707 | — | The Render to Image method for 3D picture controls demonstrates slow performance | 382333 | — | The Match Regular Expression VI in LabVIEW 2012 on Linux crashes when the screen color depth is set to 16-bit | 382668 | — | Silver Multicolumn Listbox has six blank cells when placed from palette | 383351 | — | LabVIEW crashes if a subVI front panel is continually open and closed while its graphs are updated | 383525 | — | The "auto-detect the storage format" option of the Open Data Storage Express VI only works the first time you wire the VI | 384576 | — | NI SSL Libraries not installed for LabVIEW Runtime Engine on OS X | 384767 | — | Performance of Error Cluster From Error Code VI is hurt by VI Server calls | 385212 | — | Adding and removing a registry key from a build specification can cause the build specification to become corrupt | 385247 | — | Custom Waveform Graphs display NaN values incorrectly | 385317 | — | LabVIEW crashes when a Value Change user event is registered on a Panel GOjbect | 385324 | — | The Max&Min VI incorrectly compares NaN values in arrays of 16 or more | 386813 | — | Changing an Error Cluster constant to a control, then undoing the change, causes the front panel to hang | 387768 | — | SubVI execution speed is reduced if SubVI contains a Case structure with an unwired 2D string array tunnel | 388083 | — | LabVIEW crashes when you open Profile Performance and Memory window from a library | 388419 | — | Registering a cluster containing an array of user-defined events crashes LabVIEW 64-bit | 389295 | — | LabVIEW 2012 SP1 breaks custom prototypes in DLLs that contain LabVIEW classes | 389991 | — | Memory leak when calling LabVIEW DLLs from C with new threads | 390386 | — | LabVIEW HTTP Client does not implement Curl Rewind, causing authentication errors for auth-basic | 390673 | — | Crash when you open a VI containing a Time Domain Math Express VI in LabVIEW 2012 after saving the VI for 2011 | 390908 | — | Crash on Windows 64-bit when X input of the Cubic Spline Fit VI is empty | 391285 | — | NI Variable Engine tagsrv.exe cannot handle illegal characters in OPC Tag names | 391783 | — | Compiler error: "copy cvt str/pict/tag, csrc=0x21" on conditional auto-indexing tunnel | 394001 | — | Timestamp data exported to DIAdem from graphs is incorrect | 395404 | — | Reading MixedSignalGraph.PlotClassName causes Access Violation crash | 395901 | — | Compiler error: "maxmin only minip?" when LabVIEW 2011 VI is compiled in LabVIEW 2012 | 396062 | — | After upgrading VI to 2012 SP1 the Round to Nearest function sometimes produces incorrect value if debugging is not allowed | 396305 | — | Conversion from EXT to U64 is incorrect for integers greater than 53 bits, when the top 53 bits are set | 396603 | — | The X-axis tick marks on strip charts move further than data points when updating | 396984 | — | Sequential For Loops sometimes execute incorrectly when VI property "Allow Debugging" is disabled | 403235 | — | DAbort 0xF50EFD7B in MemoryManager.cpp when auto-indexing a 2D waveform | 403284 | — | Execution speed does not return to normal after removing debug probes | 403386 | — | Using a property node to rapidly read the references to the variables deployed on a target introduces memory leak | 404117 | — | Cannot create Shared Variable if properties are copied from a Shared Variable inside a virtual folder | Accessing the HelpRefer to the LabVIEW Help, accessible by selecting Help»LabVIEW Help from LabVIEW, for more information about LabVIEW 2013. Finding ExamplesSelect Help»Find Examples from LabVIEW to launch the NI Example Finder. Automating the Installation of NI ProductsYou can automate the installation of most NI products using command-line arguments to suppress some or all of the installer user interface and dialog boxes. However, starting with the August 2012 releases (products using NI Installers version 3.1 or later), you may need to perform additional steps before or during a silent installation of NI software. If the NI product you are installing uses Microsoft .NET 4.0, the .NET installer may run before any NI software installs and may require a reboot before the installation of NI software begins. To avoid a .NET reboot, install .NET 4.0 separately before you install NI software. For more information, refer to the following KnowledgeBase articles: - For more information on silent installations of individual NI products, refer to KB 4CJDP38M, Automating the Installation of a Single Installer.
- For more information on silent installations of suited NI products, such as NI Developer Suite, refer to KB 4GGGDQH0, Automating the Installation of a Suited Installer.
- To determine what version of NI Installers your product contains, refer to KB 4CJDR18M, How Can I Determine the Type and Version of My National Instruments Installer?.
How to Use NI Software with Microsoft Windows 8When you install National Instruments software on Microsoft Windows 8, you will notice a few additional tiles on the Start screen, including shortcuts to NI application software products such as NI LabVIEW, Measurement & Automation Explorer (MAX), and the new NI Launcher. Using NI LauncherNI Launcher helps you find and launch installed NI products. It provides you with a method of finding NI products similar to the Start menu in previous versions of Microsoft Windows. To use NI Launcher, click the NI Launcher tile on the Start screen. NI Launcher launches the desktop and opens a menu containing a list of NI products. Click any NI product to launch it. Note MAX does not appear as a desktop shortcut when installed on Microsoft Windows 8. You can launch MAX either from the Start screen or from within NI Launcher.
Pinning Frequently Used ApplicationsFor convenience, you can pin your most-used NI applications, such as MAX, to either the Start screen or the Taskbar on the desktop, as necessary: Current Application | Icon Location | Pin to Action | Windows 8 Desktop | Desktop Taskbar | Right-click application and select Pin to Taskbar | Windows 8 Desktop | Start screen | Right-click application and select Pin to Start | Windows 8 Start screen | Desktop Taskbar | Right-click application and select Pin to taskbar from the menu bar on the bottom of the screen | Finding All ProgramsIf you want to find a particular application or related files, such as documentation files, from the Start screen, you can access all installed files by right-clicking anywhere on the Start screen and selecting All apps. A list of all installed software and related files appears, in alphabetical order by creator or type. For more information about NI support for Windows 8, visit ni.com/windows8. LabVIEW Drops Support for Microsoft Windows Vista, Windows XP, and Windows Server 2003 in 2016National Instruments LabVIEW will drop support for Microsoft Windows Vista, Windows XP, and Windows Server 2003 as of July 1, 2016. Versions of LabVIEW that ship after July 1, 2016 will not install or run on Windows Vista, Windows XP, or Windows Server 2003. For detailed information about NI application software product life cycles, visit ni.com/info and enter one of the following Info Codes: Product | Info Code | NI LabVIEW | lifecycle | NI LabWindows™/CVI™ | cvi_lifecycle | NI Measurement Studio | mstudiolifecycle | NI TestStand | tslcp | NI DIAdem | ddlcp | NI SignalExpress | selcp | NI VeriStand | nivslifecycle |
Important InformationCopyright © 2004–2013 National Instruments. 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. End-User License Agreements and Third-Party Legal Notices You can find end-user license agreements (EULAs) and third-party legal notices in the following locations after installation: - Notices are located in the directories.
- EULAs are located in the \Shared\MDF\Legal\license directory.
- Review \_Legal Information.txt for information on including legal information in installers built with NI products.
Trademarks Refer to the NI Trademarks and Logo Guidelines at ni.com/trademarks for information on 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. |