LabVIEW 7.1.1
ftp://ftp.ni.com/support/labview/updates/windows/7.1.1/
LabVIEW RT 7.1.1
ftp://ftp.ni.com/support/labview/labview_rt/Updates/Windows/7.1.1/
<span = id=text374473>LabVIEW 7.1.1 Readme
November 2004
This file contains important information about LabVIEW 7.1.1, including installation and upgrade issues, compatibility issues, and changes from LabVIEW 7.1.
Refer to the National Instruments Web site for the latest information about LabVIEW 7.1.1.
Changes from LabVIEW 7.1
Known Issues
Changes from LabVIEW 7.1
Fixed an issue where a function in a For Loop produces incorrect results if all inputs wired to the function are constants or computed constants, at least one of the constants is outside the For Loop, and auto-indexing is disabled for the output tunnel.
Fixed issues related to thread synchronization and shared resources associated with the error handler VIs, timing Express VIs, and the Timed Loop VIs. Refer to the KnowledgeBase for more information about this problem.
Fixed an issue where the Max & Min function produces incorrect results when it operates on 2D arrays in Compare Elements mode if you wire both outputs.
Fixed an issue that causes 100% CPU usage and decreased redraw performance on a remote front panel client when you view a VI that contains a graph or chart with dynamic or waveform data wired to it.
Fixed an issue where the Spectral Measurements Express VI always returns results based on the units of the input, even when you set Result to dB.
Fixed an issue where LabVIEW might crash if you wire some types of cluster data to the bottom input of the Subtract function but you do not wire the top input.
Fixed an issue where LabVIEW might crash when you copy an Event structure that has no events defined.
Windows Fixed an issue where the LabVIEW Base Package might crash when you select a Storage VI from the Functions palette. Refer to the KnowledgeBase for more information about this problem.
Windows Fixed an issue where error 1046 occurs when you use the Xmath Script node. Refer to the KnowledgeBase for more information about this problem.
Windows Fixed an issue where error 1047 occurs if you wire string, path, real scalar, real vector, or real matrix data to the MATLAB Script node and you are using MATLAB 7.0 or later. Refer to the KnowledgeBase for more information about this problem.
Windows Fixed an issue where NI-DAQmx error –200088 occurs if the first time you access a MAX-based NI-DAQmx task is through an NI-DAQmx Property Node. Refer to the KnowledgeBase for more information about this problem.
Mac OS Fixed an issue where LabVIEW might hang while you run certain VIs on a dual-processor computer with Mac OS X, particularly on dual-processor G5 systems.
Linux Fixed an issue where LabVIEW might crash on launch on Linux distributions with kernel 2.6 using the ext3 file system and with the dir_index option enabled. Refer to the KnowledgeBase for more information about this problem.
In the Japanese version of LabVIEW, fixed an issue where the dialog box you use to edit the events for an Event structure displays the wrong event.
Known Issues
You must mass compile the LabVIEW 7.1 directory after you install LabVIEW 7.1.1. If you do not mass compile, you will experience unexpected program dialog boxes and degraded performance of LabVIEW. Refer to the following instructions before you mass compile. Note: You must have administrator privileges or root access to mass compile the LabVIEW directory.
If you have the LabVIEW Datalogging and Supervisory Control (DSC) Module installed, you might receive up to four dialog boxes prompting you to mass compile certain directories when you launch LabVIEW after you install LabVIEW 7.1.1. National Instruments recommends that you click the No button in these dialog boxes. Clicking the Yes button does not mass compile all directories that must be mass compiled. Therefore, you would need to mass compile again to mass compile the entire LabVIEW 7.1 directory. If you receive these dialog boxes after you install the LabVIEW DSC Module with LabVIEW 7.1.1 and you already mass compiled the LabVIEW directory after installing LabVIEW 7.1.1, click the Yes button in these dialog boxes.
Complete the following steps if you have the Modulation, Sound and Vibration, or Spectral Measurements toolkits installed.
After you install LabVIEW 7.1.1, launch LabVIEW.
Select Tools»Advanced»Mass Compile.
Navigate to the LabVIEW 7.1\vi.lib\addons\NISML directory and double-click the _nisml.llb.
Double-click the . folder to select that LLB.
Click the Mass Compile button. The mass compile should take only a few minutes.
Complete the following steps to mass compile the LabVIEW 7.1 directory.
If you have VI Logger installed, move the LabVIEW 7.1\vi.lib\addons\VI Logger directory to a location outside of the LabVIEW 7.1 directory, such as to your desktop.
If it is not already open, launch LabVIEW 7.1.1.
Select Tools»Advanced»Mass Compile.
Navigate to the LabVIEW 7.1 directory and click the Select Cur Dir button.
Click the Mass Compile button. The mass compile might take a few hours.
If you have VI Logger installed, move the VI Logger directory you moved in step 1 back to its original location in the LabVIEW 7.1\vi.lib\addons directory.
If you install any toolkits or modules with LabVIEW 7.1.1 in the future, you should mass compile the LabVIEW directory again to make sure all the installed VIs are updated to LabVIEW 7.1.1. Refer to the KnowledgeBase for more information about how LabVIEW 7.1.1 affects other toolkits and modules.
If you install a new version of a toolkit or a driver after you install LabVIEW 7.1.1 and mass compile, you might need to uninstall the old version of the toolkit or driver before you install the new version.
Windows Measurement & Automation Explorer displays a LabVIEW version of 7.1 even after you install LabVIEW 7.1.1. In LabVIEW, select Help»About LabVIEW to display the correct version number.
Windows If you install Application Builder with the LabVIEW Base Package or Full Development System after you install LabVIEW 7.1.1, you must reinstall LabVIEW 7.1.1. You also should reinstall LabVIEW 7.1.1 if you upgrade LabVIEW from the Base Package to the Full or Professional Development Systems or from the Full to the Professional Development System. Complete the following steps to reinstall LabVIEW 7.1.1.
After you download and extract the LabVIEW 7.1.1 update files, navigate to the components\LV711 directory in the LabVIEW 7.1.1 update files and double-click the LabVIEW711.msi file.
When the installation program prompts you to modify, repair, or remove the installation, click the Remove button.
After the uninstallation is complete, double-click the LabVIEW711.msi file again to reinstall LabVIEW 7.1.1.
Windows If the LabVIEW 7.1.1 installation program fails, navigate to each subdirectory of the components directory and run each MSI file individually. Doing so might provide more information about the failure should you need to contact National Instruments technical support.
Windows Use the Add or Remove Programs applet in the Control Panel to uninstall LabVIEW 7.1.1. Do not insert the LabVIEW 7.1 CD and select the remove option from the LabVIEW 7.1 installation program because doing so does not properly remove LabVIEW 7.1.1.
--------------------------------------------------------------------------------
© 2004 National Instruments Corporation. All rights reserved.
是直接把exe檔案開啟設定即可呢?還是…有更方便的方法???
LabVIEW 7.1.1 Maintenance Release Information
Primary Software: LabVIEW Development Systems>>Full Development SystemPrimary Software Version: 7.1
Primary Software Fixed Version: N/A
Secondary Software: N/A
|
Problem: How will the installation of LabVIEW 7.1.1 affect other National Instruments hardware and software products? Where can I get the LabVIEW 7.1.1 Maintenance Release? What issues does it address?
Solution:
Note: Shortly after LabVIEW 7.1.1 releases (December 1, 2004), this web page may be changing frequently. In particular, some of the links in this document may not work immediately. If you are using any of the affected products and its link is not yet functional, National Instruments recommends waiting until updates for all the products you are using are available before installing LabVIEW 7.1.1.
- If you use LabVIEW Real-Time, you must install the LabVIEW RT 7.1.1 Update after installing the LabVIEW 7.1.1 Maintenance Release.
- If you use the Compact Vision System, you must install the Compact Vision System Update after installing the LabVIEW 7.1.1 Maintenance Release.
- If you use LabVIEW FPGA, click here for important information regarding using LabVIEW FPGA after installing the LabVIEW 7.1.1 Maintenance Release.
- Many newer National Instruments drivers and applications install VIs to the
National Instruments\MAX\Assistants\LVCGen\LV71directory. Refer to this document for information about mass compiling this directory if it exists on your system.
When mass compiling LabVIEW, the results window may indicate some "Bad VIs". LabVIEW ships some VIs that for one reason or another are not complete, and generally these mass compile messages do not indicate a problem with the LabVIEW 7.1.1 Update installation.
Note that VIs and built executables created in LabVIEW 7.1 can be opened and run in LabVIEW 7.1.1 and vice versa.
If a non-English version of the LabVIEW 7.1.1 Run-Time Engine is already installed you may encounter problems when updating the Windows English version of LabVIEW 7.1. Refer to this document for more information.
The LabVIEW 7.1.1 Maintenance Release includes the LabVIEW 7.1.1 Run-Time Engine. That is, if you have a LabVIEW Development System installed, you only need to download and install the LabVIEW 7.1.1 Maintenance Release. Similarly, if you have only the LabVIEW 7.1 Run-Time Engine installed, you only need to download and install the LabVIEW 7.1.1 Run-Time Engine package.
Related Links:
LabVIEW 7.1.1 Maintenance Release
LabVIEW 7.1.1 Maintenance Release - Windows English
LabVIEW 7.1.1 Maintenance Release - Windows French
LabVIEW 7.1.1 Maintenance Release - Windows German
LabVIEW 7.1.1 Maintenance Release - Windows Japanese
LabVIEW 7.1.1 Maintenance Release - Mac OS X
LabVIEW 7.1.1 Maintenance Release - Linux
LabVIEW 7.1.1 Maintenance Release - Sun Solaris
LabVIEW 7.1.1 Run-Time Engine
LabVIEW 7.1.1 Run-Time Engine - Windows English
LabVIEW 7.1.1 Run-Time Engine - Windows French
LabVIEW 7.1.1 Run-Time Engine - Windows German
LabVIEW 7.1.1 Run-Time Engine - Windows Japanese
LabVIEW 7.1.1 Run-Time Engine - Mac OS X
LabVIEW 7.1.1 Run-Time Engine - Linux
LabVIEW 7.1.1 Run-Time Engine - Sun Solaris
Attachments:
Report Date: 2004/11/15
Last Updated: 2004/12/03
Document ID: 3FEEM8EWBenjamin38331.3661226852
我已經先衝鋒陷陣了 , 現在正在mass compile
看compile的樣子, 真的是要a few hours
(Pentium 2.4G, 512MB ram)
下午再來報告狀況, 希望不要失敗
-------------------------------------------
大概半個小時 , 不過很多failed to load
yao38331.4218518519我不會Update7.1.1,因為7.1就已經很好用了…
可是7.1.1有修正一些錯誤 , 看起來有些也是常用的元件
剛剛看了一下訊息 , 那些Failed to load的元件都是7.0版的
所以我想應該沒有什麼問題吧, 開了幾個程式都可正常執行
我不會Upload 7.1,因為7.0已經夠了.
[QUOTE=yao]我已經先衝鋒陷陣了 , 現在正在mass compile看compile的樣子, 真的是要a few hours(Pentium 2.4G, 512MB ram)下午再來報告狀況, 希望不要失敗
-------------------------------------------
大概半個小時 , 不過很多failed to load[/QUOTE]
請問 yao 大大，什麼是 "mass compile" ？要怎麼做呢？
在LabVIEW的上方選項, 選 Tools -> Advanced -> Mass compile, 會出現如圖視窗
第一個選擇你安裝LabVIEW的路徑, 如此就會將LabVIEW內所有的vi重新compile一次
建議最好勾選Log Results, 以防有什麼問題可以追查一下
我個人是因為有修正錯誤才升級的, 並不是為了嘗新
而且升級後再安裝的toolkit及module都要重新compile一次, 所以你自己考慮一下喔
把Read me看一下再決定吧
yao38344.9746180556這個 Maintenance Release 還真麻煩哩…
感謝 yao 大大，我已經 Mass compile 好了，不過我仍不大清楚做這個Mass compile 是什麼意義？我只發現VI寫好之後要關掉時，就不會再問SubVI是否要save了…
不错,非常好！
[QUOTE=ARK]感謝 yao 大大，我已經 Mass compile 好了，不過我仍不大清楚做這個Mass compile 是什麼意義？我只發現VI寫好之後要關掉時，就不會再問SubVI是否要save了.....[/QUOTE]
請問是不是：就是把main VI跟subVI做個連結，並且儲存這個連結，這要下次開啟main VI時，就會直接按照連結去找subVI，就省去找尋VI所花的時間了。這樣對嗎?
關於Mass Compile，您可以參考這一篇文章：What Does LabVIEW's Mass Compile Do?
請問大大貼的LV7.1.1 updates 和LV7.1.1 RT分別是做什麼用的~~我看不太懂意思ㄟ~~是將LV更新升級成7.1.1嗎~~還是只做一些軟體bug的修正阿~~
謝謝