HAMPEL SOFTWARE ENGINEERING

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== VI Package Manager ======

//VI Package Manager (VIPM) is a community and tool that helps you find, download, create, share, & manage LabVIEW Add-ons.// 

<WRAP center round tip 100%>
HSE Internal: [[organization:internal-kb:sw-dev:vips|How to create a new package]]
</WRAP>


===== Resources =====

  * https://vipm.io
  * https://vipm.io/desktop/versions/
  * https://forums.vipm.io

---- 

===== FAQ =====

=== Package Cache ===

The downloaded VI packages can be found at

    <ProgramData>\JKI\VIPM\cache

=== Custom Actions ===

You can define VIs to be called during install/uninstall, so-called custom actions. I've tried to copy zip files to ''C:\ProgramData\Hampel Software Engineering\PPLs'' instead of installing them into vi.lib and it turned out, that the Post-Install Custom Action is executed before the files were extracted!

=== Connecting to LabVIEW ===

VIPM connects to LabVIEW via the VI-Server TCP port (default: 3363). If experiencing problems, make sure to adhere to the settings as described on [[https://support.vipm.io/hc/en-us/articles/214135683-Resolving-issues-with-VIPM-connecting-to-LabVIEW|this KB page]].

{{:kb:labview:tools:vipm-lv-viserver.png?600|}}


=== internal_deps ===

When VIP Builder thinks he needs to add dependencies, a folder in vi.lib next to the installation folder will be created like this:

{{:kb:labview:tools:pasted:20240815-094406.png}}

I was able to solve it, be opening the .vipb file and refreshing the dependency list.

Looking at the .vipb with notepad++ showed changes in this entries, but I couldn't follow the logic.

   <Advanced_Settings>
     <Package_Dependencies>
       <External_Dependencies>...</External_Dependencies>
       ...
       <Direct_Dependencies>...</Direct_Dependencies>
     </Package_Dependencies>


---- 

===== Linux =====

==== Download ====

  * [[https://www.vipm.io/desktop/|Latest Official Release]]
  * [[https://forums.vipm.io/topic/7513-vipm-2023-q3-release-candidate-for-linux/#comment-14353|VIPM 2023 Q3 Release Candidate for Linux]]
 


==== Installation ====

[[https://support.vipm.io/hc/en-us/articles/8746083021460-Error-11-Too-many-files-open-on-VIPM-for-Linux|To prevent the too many files open issue]]

    $ sudo nano /etc/sysctl.conf
    $ fs.file-max = 2000000
    $ sudo sysctl -p

Restart your system or re-login.

Create two folders
    $ sudo mkdir -p /usr/local/JKI/VIPM
    $ sudo mkdir /etc/JKI

Change the owner of the folders to your current user, to gain write access (not needed, if sudo is used later)
    $ sudo chown $USER -R /usr/local/JKI/VIPM
    $ sudo chown $USER /etc/JKI

Unzip to the new folder
    $ unzip vipm-22.1.2354-linux.zip -d /usr/local/JKI/VIPM/


==== Usage ====

VIPM needs write permission to the LabVIW installation. Because LabVIEW is usually installed under ''/usr/local/natinst/'' the normal user has no write access and VIPM needs to be executed as user "root". To do this on modern linux systems, it is remommended to use the command ''sudo'' or ''pkexec''. Examples

    $ sudo /usr/local/JKI/VIPM/vipm

If this command returns an error "Unable to open x display", it is necessary to provide the environment variables to access the x display.

    $ pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY /usr/local/JKI/VIPM/vipm

To start vipm with ''sudo vipm'', you can create a symbolic link with this command
    $ sudo ln -s /usr/local/JKI/VIPM/vipm /usr/bin/vipm

//Alternative//: Change the owner of the LabVIEW folder to your current user, to gain write access and don't need sudo.
    $ sudo chown $USER -R /usr/local/natinst/