kb:labview:tools:nipm
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
kb:labview:tools:nipm [2023/02/15 11:02] – removed - external edit (Unknown date) 127.0.0.1 | kb:labview:tools:nipm [2023/11/22 12:08] (current) – joerg.hampel | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== NI Package Manager ====== | ||
+ | |||
+ | |||
+ | <WRAP left round download 60%> | ||
+ | [[https:// | ||
+ | </ | ||
+ | |||
+ | <WRAP left round tip 60%> | ||
+ | [[https:// | ||
+ | </ | ||
+ | |||
+ | ===== FAQs ===== | ||
+ | |||
+ | ==== Error during installation of packages ==== | ||
+ | |||
+ | Invalid checksum for package < | ||
+ | Please check your internet connection and try again. | ||
+ | |||
+ | * http:// | ||
+ | |||
+ | - Close NI Package Manager | ||
+ | - Go to '' | ||
+ | - Double-click on '' | ||
+ | - Double-click on '' | ||
+ | - Restart NI Package Manager and try installing the package again | ||
+ | |||
+ | |||
+ | ==== Restore space from downloaded packages ==== | ||
+ | |||
+ | The NI Package Manager stores all downloaded packages (*.nipkg) under '' | ||
+ | |||
+ | See also: https:// | ||
+ | |||
+ | |||
+ | ==== Store SystemLink Credentials in .lvproj ==== | ||
+ | |||
+ | By default, LabVIEW does not store user credentials for SystemLink Feeds inside the LabVIEW project file. You can modify the .xml source of the .lvproj file manually to store the credentials persistently. Add the following entries to the corresponding build spec of your LabVIEW project: | ||
+ | |||
+ | < | ||
+ | < | ||
+ | |||
+ | Beware that even only opening and looking at the build spec in the LabVIEW IDE will remove those manual entries! | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== Debugging ===== | ||
+ | |||
+ | ==== Errors ==== | ||
+ | |||
+ | //Courtesy Neil Pate// | ||
+ | |||
+ | Errors are logged to: '' | ||
+ | |||
+ | Under the hood the packages are MSI files, to get more detailed logging information run this command: | ||
+ | |||
+ | " | ||
+ | |||
+ | Additional information is available inside here: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== Command Line Interface ===== | ||
+ | |||
+ | * http:// | ||
+ | |||
+ | You can use Package Manager' | ||
+ | |||
+ | To invoke the CLI, navigate to '' | ||
+ | |||
+ | You can access help for the CLI at any time by typing '' | ||
+ | |||
+ | |||
+ | |||
+ | ==== Downloading a Package with Dependencies ==== | ||
+ | |||
+ | It can be necessary to provide a package for offline installation. In this case, it's important to also provide all dependencies to the package, too. With the following command, a specific package with all needed dependencies can be downloaded. | ||
+ | |||
+ | <code bash> | ||
+ | >> nipkg download --all-deps PKG-NAME | ||
+ | </ | ||
+ | |||
+ | <note important> | ||
+ | The packages will be downloaded into the current working directory. Use the option '' | ||
+ | </ | ||
+ | |||
+ | To find the correct internal name of a package, you can use the Package Manager GUI. Find the package in the list of installed packages and point to the row with the searched package. The context help will display the internal package name. E.g. '' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== LabVIEW Package Builder ===== | ||
+ | |||
+ | * Available from [[https:// | ||
+ | * Last version to support anything but NXG5 and LV2020: NIPB 20.0 | ||
+ | * https:// | ||
+ | |||
+ | {{: | ||
+ | |||