-
Try out the new Jake: AI Coding Assistant for LabVIEW (beta)!
Get answers to questions about LabVIEW and discuss your code.
VIPM API by JKI - Toolkit for LabVIEW Download
| Version | 2020.0.3.80 |
| Released | Oct 08, 2022 |
| Publisher | JKI |
| License | JKI SLA |
| LabVIEW Version | LabVIEW>=13.0 |
| Operating System | Windows |
| Used By | sas_workshops_lib_vipb_builder_for_g_cli sas_workshops_lib_vipc_applier_for_g_cli felipefoz_lib_venv_tools sas_workshops_lib_vip_installer_for_g_cli |
| Project links | Homepage |
Description
The VIPM VI-based API is a collection of VIs that allow you to command and control VIPM (VI Package Manager). The VIs have been compiled in LabVIEW 2013 and can be used for automation code written in LabVIEW 2013 or newer.
The VIPM 2020 API VIs only work with VIPM 2020 Pro or Community Edition (or newer). It will not work with VIPM Free Edition. Also, In order for the API to work, you must have the main VIPM application running. It can be minimized, but it must be running.
For help with the VIPM API, please visit: support.vipm.io
List of Functions:
Main (Root Palette)
- Install VI Packages by Name.vi
- Uninstall VI Packages by Name.vi
Library Subpalette
- Add VI Packages to VIPM Package Library.vi
- Remove VI Package from VIPM Package Library.vi
- Download VI Packages.vi
- Network Update and Sync VIPM Package Library.vi
- List VIPM Package Library Contents.vi
Package Building Subpalette
- Build VI package.vi
- Write VI Package Build Spec.vi
- Read VI Package Build Spec.vi
VI Package Configuration (VIPC) Subpalette
- Apply VIPC File.vi
- Test VIPC Apply Needed.vi
- Scan Project.vi
- Create New VIPC File.vi
Repository Subpalette
- Publish VI Packages to Repository.vi
- Unpublish VI Packages from Repository.vi
- List Repository Contents.vi
- List VIPM Managed Repositories.vi
Utility Subpalette
- List VIPM LabVIEW Target Version.vi
- Switch Target.vi
- Open VIPM.vi
- Check is VIPM Running.vi
- Minimize VIPM.vi
- Exit VIPM.vi
Release Notes
- [FIX] Passing 0 (zero) as the major version number to "Write VI Package Build Spec.vi" was causing an error
- [FIX] Passing four-digit LabVIEW version (year) to Test VIPC Apply Needed was causing an error (was only supporting two digit LV version)
- [FIX] Test VIPC Apply Needed was returning an error for LabVIEW versions where packages have never yet been installed (when the package installation database is empty).
- [ADD] VIPC File LabVIEW Version now passed out of Test VIPC Apply Needed (and can be passed to other API calls like Apply VIPC, etc.)
Post a Resource
Recent Posts
|
Missing option "Store package in file on save"
It would be great to have this optional flag in the Scan Project.vi to be able to share a vipc file… by Michal Kozminski, 1 month, 1 week ago, 0  ,
0
|
|
|
Error 42 seems to strike again
There is a release note: 2020.0.1.69 (Nov 20, 2020) - [FIX] Was raising Error 42 (The LabVIEW ver… by Michał Bieńkowski, 1 year, 7 months ago, 1 ,
0
|
|