Sam Taggart Posted May 24, 2020 Report Share Posted May 24, 2020 I was trying to apply a vipc using the API and it tells me 20.0 isn't a valid LabVIEW version. Digging into I found this: see attached image. Maybe you guys were a little too optimistic about the switch to NXG and figured wed never see 20.0? 1 Quote Link to comment Share on other sites More sharing options...
Sam Taggart Posted May 24, 2020 Author Report Share Posted May 24, 2020 Simply removed the case structure and it seemed to work fine. 1 Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted May 24, 2020 Report Share Posted May 24, 2020 Thanks Sam! We’ll fix this in the shipping API. Quote Link to comment Share on other sites More sharing options...
Sam Taggart Posted May 24, 2020 Author Report Share Posted May 24, 2020 I was trying to understand the logic behind this and now that I take a step back, I see. You were trying to prevent people from putting in 2012 instead of 12.0. Makes perfect sense now. Quote Link to comment Share on other sites More sharing options...
StefanLemmens Posted September 8, 2020 Report Share Posted September 8, 2020 Is the new VIPM API package available? Has this been fixed already? Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted October 17, 2020 Report Share Posted October 17, 2020 We have an official bug ID for this 18825 - VIPM API doesn't handle LabVIEW 2020 We're working on a fix. Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted November 17, 2020 Report Share Posted November 17, 2020 @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. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.