Manage Instrument Drivers with VI Package Manager (VIPM)

[chris.b]

This is something a few power users have asked me about. There's no Instrument Driver or VIPM Idea Exchange, so I thought I would post it here.

What if VIPM could manage Instrument Drivers from IDNet?
There are a few key benefits this would offer us...

• download IDNet drivers directly from VIPM 
• track which version of a driver you are using for different projects and revert when necessary 
• wrap up ID dependencies in a VIPC file for use at a customer site

 

[SamoraJ]

I like this idea a lot.

Still i agree with Minty and ibbergers objections, so i posted another idea.

Not sure if it's supplementary of contradicting but, it's there.

Cheers,

/MArcus

[MichaelAivaliotis]

Just want to let everyone know that JKI now has a VIPM Idea Exchange. More information can be found here:

http://blog.jki.net/news/we-want-your-vi-package-manager-ideas/

Click here to vote on or submit your ideas.

[MichaelAivaliotis]

We have some news on this topic. We've added a new feature in VIPM 2012 SP1, that allows you to import zip files downloaded from IDNet into VIPM and quickly build them as packages. Click on the following link for a short video tutorial on this:

http://support.jki.net/entries/22443418-how-to-import-a-labview-idnet-driver-into-vi-package-builder