注册登陆后可查看附件和大图，以及购买相关内容
您需要 登录 才可以下载或查看，没有账号？注册会员
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 2017SP1 Win32ENG/FRE/GER/JPN/KOR 32位LV2017SP1英语/法语/德语/日语/韩语多国语言版下载
2018年1月更新发布LabVIEW2017SP1版。LabVIEW2017SP1共发布了64位英文版、32位英文版、32位中文版、32位日文版、32位韩文版、32位法语版、32位德语版以及MAC系统版本等多个版本。请根据需要选择不同的版本安装。
LabVIEW2017SP1 32位英语版：
百度网盘和NI官方下载地址：
请注册视觉论坛会员登录后购买附件下载查看
LV2017SP1ENG.txt
(675 Bytes, 下载次数: 95, 售价: 10 元)
LabVIEW2017SP1 32位日语版：
百度网盘和NI官方下载地址：
请注册视觉论坛会员登录后购买附件下载查看
LV2017SP1JPN.txt
(604 Bytes, 下载次数: 0, 售价: 10 元)
LabVIEW2017SP1 32位韩文版：
百度网盘和NI官方下载地址：
请注册视觉论坛会员登录后购买附件下载查看
LV2017SP1KOR.txt
(604 Bytes, 下载次数: 0, 售价: 10 元)
LabVIEW2017SP1 32位法语版：
百度网盘和NI官方下载地址：
请注册视觉论坛会员登录后购买附件下载查看
LV2017SP1FRE.txt
(604 Bytes, 下载次数: 0, 售价: 10 元)
LabVIEW2017SP1 32位德语版：
百度网盘和NI官方下载地址：
请注册视觉论坛会员登录后购买附件下载查看
LV2017SP1GER.txt
(604 Bytes, 下载次数: 0, 售价: 10 元)
LabVIEW 2017 Service Pack 1 Readme for WindowsSeptember 2017 This file contains important information about LabVIEW 2017 Service Pack 1 (SP1) for Windows, including system requirements, installation instructions, known issues, and a partial list of bugs fixed for LabVIEW 2017 SP1. Refer to the NI website for the latest information about LabVIEW. Refer to the labview\readme directory for readme files about LabVIEW add-ons, such as modules and toolkits. System Requirements Installation Instructions Product Security and Critical Updates New Features LabVIEW 2017 SP1 (64-bit) Known Issues Bug Fixes Accessing the Help Finding Examples Automating the Installation of NI Products Using NI Software with Microsoft Windows 10 Using NI Software with Microsoft Windows 8.1 Legal Information
System RequirementsLabVIEW 2017 SP1 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 (version 1703)/8.12/7 SP13
Windows Server 2012 R22 (64-bit)
Windows Server 2008 R2 SP13 (64-bit) | Windows 10 (version 1703)/8.12/7 SP13
Windows Server 2012 R22 (64-bit)
Windows Server 2008 R2 SP13 (64-bit) | | 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 SP1 will not install or run on an unsupported OS. You cannot deploy or distribute applications that use LabVIEW 2017 SP1 to an unsupported OS. Additionally, after installing LabVIEW 2017 SP1, 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 InstructionsComplete the following steps to install and activate LabVIEW for Windows. Are 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. Are you upgrading from a previous version of LabVIEW? Refer to the LabVIEW Upgrade Notes for information about protecting existing VIs and projects before installing a new version of LabVIEW, as well as upgrade and compatibility issues and a complete list of new features in LabVIEW 2017. Note Starting from 2017, LabVIEW supports backward compatibility for the LabVIEW Run-Time Engine. Versions of LabVIEW later than 2017 can load binaries and VIs built with LabVIEW 2017 without recompiling. This improvement applies to stand-alone applications (EXEs), shared libraries (DLLs), and packed project libraries. 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 UpdatesVisit ni.com/security to view and subscribe to receive security notifications about NI products. Visit ni.com/critical-updates for information about critical updates from NI. New FeaturesIn LabVIEW 2017 SP1, malleable VIs can adapt to input classes. A malleable VI that calls a method of class A accepts data of unrelated classes as long as the class has a public method with the same name, connector pane pattern, and terminal direction as the method of class A that the malleable VI calls. The malleable VI adapts to the input class by replacing the call to the method of class A with a call to the public method in the input class, if such a method exists. You can think of this adaptability of a malleable VI as defining an interface of method calls with method name, connector pane pattern, and terminal direction. The malleable VI accepts data of any class that fulfills the interface of method calls, which allows you to use one malleable VI to perform operations on data of unrelated classes or implement multiple interfaces defined by different malleable VIs on one class. Refer to the labview\examples\Malleable VIs\Class Adaptation\Malleable VIs - Class Adaptation.lvproj for an example of using malleable VIs to define interfaces of method calls. LabVIEW 2017 SP1 (64-bit)Use the LabVIEW Platform media to install modules and toolkits supported by LabVIEW 2017 SP1 (32-bit) and LabVIEW 2017 SP1 (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 HardwareRefer to the NI website for information about drivers compatible with LabVIEW 2017 SP1 (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 (64-bit). Supported Modules and ToolkitsLabVIEW 2017 SP1 (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 SP1 (32-bit) | LabVIEW 2017 SP1 (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. |
Refer to the readme of each product for more information about 32-bit and 64-bit support, system requirements, installation instructions, and activation. For information about products not listed in the previous table, refer to the user documentation of those products. Known IssuesYou 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 and LabVIEW 2017 SP1. Bug FixesThe following items are the IDs and titles of a subset of issues fixed in LabVIEW 2017 SP1. 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 that the issue has been fixed. | ID | Fixed Issue | | 604133 | LabVIEW can crash when executing a Value (Signaling) property on a generic subpanel reference. | | 607006 | Changed click behavior with Windows 10, version 1607. | | 607329 | Merged signals do not have correct names in output file of Write to Measurement File express VI. | | 608412 | In some cases, attempting to plot multiple large datasets on an XY graph can result in LabVIEW hanging. | | 618044 | In rare cases, updating a type definition file may cause instances of the typedef to revert to default data. | | 620145 | Using a Formula Node with a large number of equations can cause LabVIEW to crash. | | 622429 | On the first execution of LabVIEW, using the Edit Tree Items: Move Item method causes a crash. | | 627910 | Large projects may have extended save times. | | 637096 | LabVIEW-built applications can have DPI scaling issues. | | 639416 | LabVIEW-built assemblies with array parameters cannot be called from Visual Studio. | | 639842 | Occasional crashes on real-time targets, exception code 0x661. | | 640139 | Updating a type definition that is used in dynamic event registration leads to incorrect behavior. | | 640344 | A Stream channel writer can be wired to a Lossy Stream channel writer without breaking the wire. | | 640873 | Callers of malleable VIs will sometimes show a document modification and prompt to save when the VI has not changed. | | 649615 | Dragging a node with a channel wire connection into or out of a structure can rewire incorrectly. | | 649837 | Crash using Actor Framework Message Maker after first message creation fails because of an already-existing file on disk. | | 649952 | In very rare situations, LabVIEW can crash while unflattening data. | | 650556 | Message Channel acks can unblock improperly. | | 651326 | Double-clicking a reentrant subVI in LabVIEW 2017 always opens the master VI, never the clone. | | 653033 | In certain cases, updating a numeric member of a cluster will not update the cluster. | | 653897 | Make LabVIEW more robust when presented with corrupted resource files. | | 654700 | Read-only DVR can occasionally return the wrong value. | | 654714 | Scripted channel endpoint VIs show up on the Recent Files list in the Getting Started Window. | | 656295 | In some cases, using the Alignment tool on wires can cause a LabVIEW crash. | | 656516 | Some VIs that are runnable in LabVIEW 2015 and earlier will report broken in LabVIEW 2016 and later. | | 657776 | Creating a VI for Data Member Access can crash LabVIEW. | | 658033 | In the Rearrange Cases dialog for Event Structure frames, the "Sort" button doesn't sort alphabetically. | | 658387 | Sometimes a terminal with a coercion dot will be displayed as the wrong data type in Context Help. | | 658923 | Custom Probes for LabVIEW classes have erratic block diagram behavior when live drag is enabled. | | 660055 | Comparison primitives with waveform as input in "Compare Aggregate" mode can cause a LabVIEW crash at runtime. |
Accessing the HelpRefer to the LabVIEW Help, accessible by selecting Help»LabVIEW Help from LabVIEW, for information about LabVIEW 2017 SP1. Finding ExamplesSelect Help»Find Examples from LabVIEW to launch the NI Example Finder. 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. 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. If the NI product you are installing uses Microsoft .NET 4.6.2, 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.6.2 separately before you install NI software. 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 10Microsoft Windows 10 is the latest version of the Windows operating system and features significant changes compared to previous versions. Windows 10 introduces several new capabilities and also combines features from both Windows 7 and Windows 8. For more information about NI support for Windows 10, visit ni.com/windows10. Using NI Software with Microsoft Windows 8.1When 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 InformationCopyright © 2004–2017 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. 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. 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.
U.S. Government Restricted Rights 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. IVI Foundation Copyright Notice Content from the IVI specifications reproduced with permission from the IVI Foundation. The IVI Foundation and its member companies make no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The IVI Foundation and its member companies shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. Trademarks Refer to the NI Trademarks and Logo Guidelines at ni.com/trademarks for information on NI trademarks. Other product and company names mentioned herein are trademarks or trade names of their respective companies. Patents For patents covering the NI products/technology, refer to the appropriate location: Help» Patents in your software, the patents.txt file on your media, or the NI Patent Notice at ni.com/patents. 374715H-01
| 
发表于 2018-12-31 16:40:48
