注册登陆后可查看附件和大图,以及购买相关内容
您需要 登录 才可以下载或查看,没有账号?注册会员
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 2017 Win64ENG 64位LV2017英文版下载
2017年5月春季包更新全新LabVIEW2017版,该软件包含了下一代的LabVIEW NXG。LabVIEW2017共发布了64位英文版、32位英文版、32位中文版、32位日文版、32位韩文版、32位法语版、32位德语版以及MAC系统版本等多个版本。请根据需要选择不同的版本安装。
NI发布软件不按套路出牌了,按以前的套路,这个时候应该是出LabVIEW2016SP1版本的,等到下半年8月时,才会出LabVIEW2017了。但是现在将LabVIEW2017直接放到上半年发布了,跳过了LabVIEW2016SP1版本。不管他怎么发布,反正只要性能强劲就好。不过从LV2017版开始,上半年开始发布主版本,下半年则发布SP1版本。调整了一下发布周期。以前是上半年发布上一年的SP1版本,下半年发布当年的主版本。
百度网盘下载地址:
标准下载:
链接:请注册视觉论坛会员登录后购买附件下载查看
提取码: 请购买附件下载查看
NI下载器下载:
链接:请注册视觉论坛会员登录后购买附件下载查看
提取码: 请购买附件下载查看
NI官方下载地址(可能无效或无法下载完成)(EXE版和ZIP版内容一样,EXE版为NI当年发行版,ZIP版为NI后期更新重压制版):
标准下载:
请购买附件下载查看
NI下载器下载:
请购买附件下载查看
LV2017ENG64.txt
(822 Bytes, 下载次数: 56, 售价: 10 元)
LabVIEW 2017 Readme for WindowsThis file contains important information about LabVIEW 2017 for Windows, including system requirements, installation instructions, a partial list of bugs fixed for LabVIEW 2017 for Windows, and known issues. Refer to the labview\readme directory for readme files about LabVIEW add-ons, such as modules and toolkits. Installation Instructions LabVIEW 2017 (64-bit) Bug Fixes Additions to the LabVIEW Help Automating the Installation of NI Products Using NI Software with Microsoft Windows 8.1 LabVIEW 2017 has the following requirements: Windows | Run-Time Engine | Development Environment | Processor1 | Pentium 4M/Celeron 866 MHz (or equivalent) or later (32-bit)
Pentium 4 G1 (or equivalent) or later (64-bit) | Pentium 4M (or equivalent) or later (32-bit)
Pentium 4 G1 (or equivalent) or later (64-bit) | RAM | 256 MB | 1 GB | Screen Resolution | 1024 x 768 pixels | 1024 x 768 pixels | Operating System | Windows 10/8.12/7 SP13
Windows Server 2012 R22
Windows Server 2008 R2 SP13 | Windows 10/8.12/7 SP13
Windows Server 2012 R22
Windows Server 2008 R2 SP13 | Disk Space | 620 MB | 5 GB (includes default drivers) | 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. NI 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. | 1 LabVIEW and LabVIEW Run-Time Engine require processors of the Pentium 4M/G1 generation or later, which are capable of executing SSE2 instructions.
2 NI software installs VC2015 Runtime and .NET 4.6.2. Windows 8.1 and Windows Server 2012 R2 require Microsoft updates to support these items. Refer to Microsoft KB2919442 and KB2919355 for more information about how to install these updates.
3 NI software is signed with a SHA-256 certificate. Windows 7 SP1, Windows Embedded Standard 7 SP1, and Windows Server 2008 R2 SP1 require Microsoft updates to support SHA-256. Refer to Microsoft KB3033929 for more information about how to install this security update.
|
Note- You cannot access LabVIEW using a Guest account on Windows.
- In 2016 LabVIEW dropped support for Windows Vista, Windows XP, Windows Server 2003, and installations of Windows 7 without any service packs. LabVIEW 2017 will not install or run on an unsupported OS. You cannot deploy or distribute applications that use LabVIEW 2017 to an unsupported OS. Additionally, after installing LabVIEW 2017, you cannot use any installers built on this computer with any version of LabVIEW, LabWindows™/CVI™, NI TestStand™, or Measurement Studio on an unsupported OS. For more information about the changes to our OS support for 2016, refer to KB 79UC78LS, Why Does my LabVIEW, LabWindows/CVI, Measurement Studio, or TestStand Built Installer Fail on Windows XP/Vista and Server 2003?.
- Support for Windows 32-bit operating systems may require disabling physical address extension (PAE). To learn how this might affect your system and what actions you might need to take, visit ni.com/info and enter the Info Code PAESupport.
Installation InstructionsAre you installing LabVIEW for the first time? Insert the LabVIEW Platform media and follow the onscreen instructions to install LabVIEW, modules, toolkits, and drivers. When prompted, enter the serial number for each product you want to activate. Your serial number can be found at ni.com/myproducts. If you are managing your license with a volume license server, you should receive your volume license file by email. 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. Product Security and Critical UpdatesUse the LabVIEW Platform media to install modules and toolkits supported by LabVIEW 2017 (32-bit) and LabVIEW 2017 (64-bit). When run on Windows (64-bit), LabVIEW (64-bit) provides access to more memory than a 32-bit operating system or a 32-bit application can provide. LabVIEW (64-bit) is available in English only. Supported HardwareLabVIEW 2017 (64-bit) supports a limited number of modules and toolkits. The following lists compares the modules and toolkits supported by LabVIEW (32-bit) and LabVIEW (64-bit). Product | LabVIEW 2017 (32-bit) | LabVIEW 2017 (64-bit) | Advanced Signal Processing Toolkit | ✓ | — | Control Design and Simulation Module | ✓ | ✓1 | Database Connectivity Toolkit | ✓ | — | DataFinder Toolkit | ✓ | — | Datalogging and Supervisory Control Module | ✓ | — | Desktop Execution Trace Toolkit for Windows | ✓ | ✓ | Digital Filter Design Toolkit | ✓ | — | FPGA Module | ✓ | — | MathScript RT Module | ✓ | ✓2 | Report Generation Toolkit for Microsoft Office | ✓ | ✓ | Real-Time Module | ✓ | — | Robotics Module | ✓ | — | SoftMotion Module | ✓ | — | Statechart Module | ✓ | — | Sound and Vibration Measurement Suite | ✓ | ✓ | Unit Test Framework Toolkit | ✓ | ✓ | VI Analyzer Toolkit | ✓ | ✓ | Vision Development Module | ✓ | ✓ | 1 The Control Design and Simulation Module (64-bit) does not support the System Identification VIs, System Identification Assistant, Control Design Assistant, and real-time targets.
2 The MathScript RT Module (64-bit) does not support the libraries class of MathScript RT Module functions. |
You can access the software and documentation known issues list online. Refer to the NI website for an up-to-date list of known issues in LabVIEW 2017. Bug FixesID | Fixed Issue | 404983 | Dynamic load of LabVIEW Class fails when built into a DLL. | 522606 | Error Ring does not adhere to dataflow in an executable or in a VI with debugging disabled. | 524160 | Updated Timed Loop Mode example VI to better display custom phase and show correct value for period in context help. | 567353 | When an XNode output is wired to the Loop count of a Parallel For Loop the VI breaks. | 571901 | Using the BD Get Image Scaled method crashes LV 2014 and 2015 if the depth of the image is 1. | 572024 | Built applications hang in some instances when calling Quit LabVIEW. | 584378 | LabVIEW has the potential to crash when simultaneously setting multiple variant attributes to empty variant constants. | 588140 | Insert of Compound Arithmetic node on wire can result in undesirable configuration. | 590370 | Levenberg-Marquardt algorithm has poor convergence in some cases. | 591709 | Calling Format Value on improper value can result in crash. | 592088 | Improper updates of library members when using Actor Framework Message Maker. | 594760 | Example "Extract number with match pattern" gives incorrect output. | 595178 | Certain examples show incorrect title bars on the Project Window. | 595814 | The unflatten from String primitive can take several minutes to return when given malformed input strings. | 595815 | DataSocket Read VI crashes LabVIEW when calling certain IP addresses. | 596804 | Re-registering a dynamic event can cause subscribing event frames to behave improperly. | 597858 | File permissions error when saving a LabVIEW file to a Windows Server from Windows 10. | 598986 | Scrollbar does not properly respond to clicks on string constant. | 599478 | LabVIEW may not update classes on Real-Time targets after changing the inplaceness of a connector pane terminal for a VI within those classes. | 601256 | Error message when replacing existing channel endpoint with an invalid configuration is not clear. | 601764 | Local variables can be created from channel wires. | 601807 | Resizing a "Register for Events" Node Crashes LabVIEW. | 602230 | Connecting conflicting channel types does not always break the wire. | 602973 | In some cases, using the Min/Max function on array of single precision floating point numbers can cause a VI to fail to compile. | 603092 | Rearranging tabs in tab control can cause a crash. | 603391 | Incorrect Out of Memory dialog when using "Active Plot" property node in 64-bit LabVIEW. | 603562 | Using dynamically dispatched VIs with unwired input terminals can, in some cases, cause crashes. | 603576 | Channels carrying typedefs/classes create crosslinks when users duplicate projects. | 603854 | QMH project template contains a potential race condition. | 605231 | Attempting to abort a VI may not always cause the VI to abort. | 606365 | Dragging a control or indicator to the edge of the block diagram can cause duplication of the front panel object. | 606847 | Dynamic Dispatch VIs break when the class wire is passed through a shift register in specific cases. | 607685 | Cast Unit Bases does not correctly remove units from output. | 609835 | Actor Framework debug traces do not occur on Real-Time targets. | 611532 | Selecting "Use Default if Unwired" on an output tunnel with a LabVIEW class data type will cause a broken VI with no errors. | 611810 | Saving a VI containing a "Lookup Channel Probe" node for LabVIEW version 2015 and earlier can result in failure to open the saved VI. | 611838 | The abort behavior of the Accumulator Tag channel wire does not match that of other implementations. | 612501 | Interpolate 2D Scattered VI will return an incorrect value for specific size input values. | 615195 | Collapsing "Variant Attribute Get / Replace" border node on In Place Element Structure causes LabVIEW to crash. | 615288 | Previous versions of LabVIEW are unable to open dynamic classes saved using "Save for Previous Version" in 2016. | 616848 | Using Quick Drop to add a Custom Control Template to a VI's Front Panel crashes LabVIEW. | 617119 | Pressing Abort during project creation then creating another project causes LabVIEW to crash in some cases. | 617504 | Dragging the front panel icon of a VI onto the block diagram of another VI will undo the last edit of the dragged VI in some cases. | 617917 | Possible crash when loading particular classes. | 624304 | Actors that return an error from Pre Launch Init also send a Last Ack containing the same error. | 624957 | Possible memory corruption when opening invalid file. | 627716 | Opening a project with "Messenger Channels" causes a search for Wrapper.lvclass. | 627910 | Large projects may have extended save times. |
Accessing the HelpThe following list contains additional changes to LabVIEW that are not included in the LabVIEW Help, the LabVIEW Upgrade Notes, or both: - In LabVIEW 2017, you can insert the contents of a subVI into the calling block diagram at edit time by right-clicking the subVI node and selecting Replace with SubVI Contents. In the Replace with SubVI Contents dialog box that appears, you can configure the following options:
- Make space in calling diagram to fit subVI contents—Specifies whether to adjust the calling block diagram to accommodate the contents of the subVI.
- Wrap subVI contents in a Sequence structure—Specifies whether to place the contents of the subVI in a Stacked Sequence structure.
Finding ExamplesYou 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. For more information about automating the installation of NI products, refer to the following KnowledgeBase articles: - For more information about silent installations of individual NI products, refer to KB 4CJDP38M, Automating the Installation of a Single Installer.
- For more information about silent installations of NI products in a suite, such as NI Developer Suite, refer to KB 4GGGDQH0, How Do I Automate 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 NI Installer?.
Using NI Software with Microsoft Windows 10When you install NI software on Microsoft Windows 8.1, you will notice a few additional tiles in the Apps view, including shortcuts to NI application software products such as NI LabVIEW, Measurement & Automation Explorer (NI MAX), and NI Launcher. For more information about NI support for Windows 8.1, visit ni.com/windows8. Legal Information© 2004–2017 National Instruments. All rights reserved. NI 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. 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.
If you are an agency, department, or other entity of the United States Government ("Government"), the use, duplication, reproduction, release, modification, disclosure or transfer of the technical data included in this manual is governed by the Restricted Rights provisions under Federal Acquisition Regulation 52.227-14 for civilian agencies and Defense Federal Acquisition Regulation Supplement Section 252.227-7014 and 252.227-7015 for military agencies. Content from the IVI specifications reproduced with permission from the IVI Foundation. Trademarks Patents 374715G-01 |