Building the S3DK w/ VIPM
To add, remove, or edit any files within a labview package( for our case the S3DK) you must use the VI package manager developed by JKL. In order to use the VIPM the user must have the build file downloaded as well as any VIs/supporting files and have uninstalled the current version of he S3DK. However before doing this the any additions or edits of any VIs must be saved in an accessible place for retrieval later on.
To build a package you must also have the source file taken from the S3DK folder under Labview. Below are the necessary files:
After locating all the files group the above files and any new additions/edits to the source file.
To first build a package is to open VIPM, then click the “build a package” button which is the box with a hammer icon.
After words a new window will appear with the names of different packages and options to open new or already existing builds. Click “Smart grid Synchrophasor SDK (S3DK)” choice, if not available click on the open existing option and search for the package.
Once opening the package will give display a menu:
Build information: Used to find files used for building the package, Version update, and adds release notes for keeping track of changes.
Display information: Displays information to the user about general information regarding the company producing it.
Description: The gives details about the product as a whole and offers a chance for in depth detail depending on who is using the build
Palettes: The palette editor is used to customize the location and display of the VIs. It is in this menu that the layout for the VIs and which VIs appear and don’t appear can be customized. The function palette option can be edited by right clicking and clicking edit palette. Any VI or sub folder not needed by the end user can be moved to the control palette.
Destination: Controls where the files are sent to for the end user.
Source settings: Used to customize the files used to build the package. For example, if any unnecessary files are used for a VI that don’t need to be transferred over can be omitted with this option.
After going through the options click the box and hammer icon and the package should build. Common error:
Cross-Linking: Happens if there is another VI with the same name, can be the result of still having the original files under labview. A package cannot be built if there is a previous file downloaded or located in labview.