Jump to content

2020 not a valid LabVersion for applying vipc file?


Recommended Posts

  • 3 months later...
  • 1 month later...
  • 5 weeks later...

@Sam Taggart, @StefanLemmens.

We just published a new build of the VIPM API which should address this issue.

https://www.vipm.io/package/jki_lib_vipm_api/#2020.0.0.65

2020.0.0.65 (Nov 17, 2020)

This release adds support for VIPM 2020 (including Community Edition) and LabVIEW 2020, and also adds a few new features, changes and fixes:

- [NEW] VIPM 2020 and Community Edition support (Community Edition can use API calls, just like Pro)
- [NEW] LabVIEW 2020 support (fixes an issue where passing version 20.0 was failing a version check)
- [CHANGE] Now compatible with LabVIEW 2013 and greater on Windows (was 2009 previously).
- [NEW] API VI "Check is VIPM Running" will check if VIPM app (process) is running
- [NEW] API VI "Open VIPM" will open the VIPM Main UI (and launch VIPM if needed)
- [CHANGE] "Exit VIPM.vi" to run synchronously. It has a new "Timeout in seconds (0: no timeout)" input and waits on VIPM process to be fully exited. Also, has a "synchronous? (T)" input which can be set to FALSE if asynchronous behavior is desired.
- [CHANGE] Separated compiled code from source code (All VIs)
- [FIX] API will now return an error if VIPM process terminates (crashes) before a timeout occurs when calling a synchronous command.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.