Create Awesome LabVIEW

Don't waste time re-inventing code that's already been written. Leverage the power of our community maintained packages to deliver bug free code faster.

With a registry containing 106 packages, you're sure to find some help.

Checkout These Cool Packages

Popular
New

@cs/event-logger: Composed Event Logger is an extendable, ready to use LabVIEW event logger. Injectable event destinations, referred to as 'sinks', log entry formats, and application wide error processing allow extension and customization
@cs/lookup-table: A malleable, by-reference, lookup table API with in-placeness optimization and type abilities
@cs/actor-framework-messages: Messaging extensions to the LabVIEW Actor Framework
@cs/variant: Extensions to LabVIEW variant functionality for everyday use
@cs/transport: Q: How did the chicken cross the LabVIEW application? (A: Transport)

twincat-strict: The TwinCAT LabVIEW library uses variants to deal with typing. This library adds wrappers to provide a strictly typed interface.
@cs/session: A session framework for abstraction of business logic through a by reference API
@cs/task: An implementation of Futures-Promises-Continuations all wrapped up in asynchronous Task objects.
@mgi/panel-manager: A framework to manage VI front panels
@cs/event-logger: Composed Event Logger is an extendable, ready to use LabVIEW event logger. Injectable event destinations, referred to as 'sinks', log entry formats, and application wide error processing allow extension and customization

Why GPM rules

GPM takes a project based approach to package installation.

Packages installed into the project folder: The contents of the package file live right next to your application's code. This means you can easily see what version of what packages the current project is executing. You can also add the package contents in to source code control so other developers just have to get the latest version from source code control and they're ready to go.
Designed with multi developer teams and Continuous Integration in mind: Information about what packages your project uses is stored as the packages are installed. This along with a rich command line interface means other developers (or your CI server) just need to run a simple command to reconstruct the exact package configuration.
Multiple versions of the same package on one computer: Since the packages are installed in the project folder, each project can have its own unique version of the package file. This means that updating the package for one project won't introduce untested code into another.

Getting GPM

Follow these instructions to install GPM onto your system.

GPM is installed using NI Package Manager. Please download and install NIPM before installing GPM.

Install GPM's package feed to your system then start the interactive installation process.

"C:\Program Files\National Instruments\NI Package Manager\nipkg.exe" feed-add --system --name=mgi-gpm https://s3-us-west-1.amazonaws.com/gpm-dist/master/ && "C:\Program Files\National Instruments\NI Package Manager\NIPackageManager.exe" install gpm-windows --update-feeds

Install GPM's package feed to your system then silently install it.

"C:\Program Files\National Instruments\NI Package Manager\nipkg.exe" feed-add --system --name=mgi-gpm https://s3-us-west-1.amazonaws.com/gpm-dist/master/ && "C:\Program Files\National Instruments\NI Package Manager\nipkg.exe" install gpm-windows --update-feeds -y

Note: This command must be run from an elevated command prompt!