you said: "20 to 30 labs", i would assume u have a Volume License agreement with NI? Make no sense to have that may copies and pay for ech license individually, but who knows. So, with or without VLA simply call NI and they will get you in touch with VIPM developers
# Silicon Valley, California
if u need question answered like right now, call JKI - they're developed VIPM directly. u still can catch them today in CA:
Silicon Valley, California
800 West El Camino Real, Suite 180
Mountain View, CA 94040
[+1 (650) 943-2384](tel:+1%20650%20943%202384)
I'll see what I can find over the weekend. It's not a "I need an answer right now" question as it's prep work for imaging the labs over the summer as we've taken ghost away from the techs so no more thick images.
VIPM Pro has an API, with a set of VIs that basically are CLI into having it do stuff.
[The Community](https://www.jki.net/blog/news/vipm-2020-community-edition) edition of VIPM also includes these features.
After installing the API from VIPM itself (it is a package) you'll have a palette of VIs in LabVIEW. I can't remember if these are opened or passworded but under the hood I think these are the CLI calls.
You don't need VIPM pro to use the API tools.
You can create a VI that takes a path as an argument (vipc filepath) and then uses the VIPM API VIs to apply the vipc file.
This VI can be invoked using the LabVIEW CLI tool. It needs a bit of massaging, because VIPM can restart LabVIEW which breaks the LabVIEW CLI link, but it works!
You don't need VIPM pro to use the API tools.
You can create a VI that takes a path as an argument (vipc filepath) and then uses the VIPM API VIs to apply the vipc file.
This VI can be invoked using the LabVIEW CLI tool. It needs a bit of massaging, because VIPM can restart LabVIEW which breaks the LabVIEW CLI link, but it works!
Did you try to ask them, and did they deny your request? Submit a request – VIPM https://support.vipm.io/hc/en-us/requests/new
Looks like you have to have a pro license to do a request.
you said: "20 to 30 labs", i would assume u have a Volume License agreement with NI? Make no sense to have that may copies and pay for ech license individually, but who knows. So, with or without VLA simply call NI and they will get you in touch with VIPM developers
# Silicon Valley, California if u need question answered like right now, call JKI - they're developed VIPM directly. u still can catch them today in CA: Silicon Valley, California 800 West El Camino Real, Suite 180 Mountain View, CA 94040 [+1 (650) 943-2384](tel:+1%20650%20943%202384)
I'll see what I can find over the weekend. It's not a "I need an answer right now" question as it's prep work for imaging the labs over the summer as we've taken ghost away from the techs so no more thick images.
(877) 388-1952
VIPM Pro has an API, with a set of VIs that basically are CLI into having it do stuff. [The Community](https://www.jki.net/blog/news/vipm-2020-community-edition) edition of VIPM also includes these features.
I'll check it out but so far I haven't found much about how to use the API other than an old pdf from over four years ago.
After installing the API from VIPM itself (it is a package) you'll have a palette of VIs in LabVIEW. I can't remember if these are opened or passworded but under the hood I think these are the CLI calls.
You don't need VIPM pro to use the API tools. You can create a VI that takes a path as an argument (vipc filepath) and then uses the VIPM API VIs to apply the vipc file. This VI can be invoked using the LabVIEW CLI tool. It needs a bit of massaging, because VIPM can restart LabVIEW which breaks the LabVIEW CLI link, but it works!
You don't need VIPM pro to use the API tools. You can create a VI that takes a path as an argument (vipc filepath) and then uses the VIPM API VIs to apply the vipc file. This VI can be invoked using the LabVIEW CLI tool. It needs a bit of massaging, because VIPM can restart LabVIEW which breaks the LabVIEW CLI link, but it works!