vipm opens with labview. necessary?

[rrd2]

With the latest VIPM update, VIPM opens whenever I start LabVIEW 2019.  Is this really necessary? How do I stop this annoyance?

[Jim Kring]

Hi there.

A couple things:

1) There is a way to disable this in the settings file.

2) We just released 2020.3 (SP3) that disables the system tray by default, which will also prevent automatic start when LabVIEW starts.

My suggestion would be to go with #2 so you're running the latest and greatest version of VIPM, since it has some other improvements, too.

Please let us know how that works for you.

-Jim

 

[rrd2]

I did update to 2020.3.  VIPM opens when I run LabVIEW 2019 but not when I open LabVIEW 2020.

Also, I couldn't find any version info in the options menu of VIPM to make sure it did update to 2020.3 after restarting.  However, when I run VIPM by itself, it shows 2020.3 in the opening screen.

This is no VIPM system tray on my Windows 10 computer.

 

Edited December 12, 2020 by rrd2
more info

[Jim Kring]

After you Disable System Tray in the VIPM Options, please reboot your computer and see if that fixes it.

[rrd2]

I just edited the settings.ini with "Start VIPM when LabVIEW starts?="FALSE"".  Thanks.

[Jim Kring]

Great. Yes, that should work too. I think you discovered a bug.

When the System Tray is disabled, VIPM should not start up automatically when LabVIEW starts, even if Start VIPM when LabVIEW starts? is set to TRUE.

We'll fix that in the next release. Glad you figured out a good solution.

[rrd2]

It's odd that VIPM opened only with LV2019 and not with LV2020.

Edited December 12, 2020 by rrd2

[Jim Kring]

Yes, that *is* odd. Question: Are LV2019 and LV2020 32-bit or 64-bit?

[rrd2]

Both 32-bit

[Jim Kring]

Oh, I think I know what it is. The service that auto-starts VIPM looks for the transition from NO LabVIEW versions running to ANY LabVIEW version running.

Here's what I think happened:

1. LV2019 started, which auto-started VIPM.
2. VIPM was closed and LV2019 was left running.
3. Then, LV2020 was opened (while LV2019 was still running)
4. VIPM did not auto-start because the transition from NO LabVIEW running to ANY LabVIEW running did not occur.

Anyhow, it's not super important, since we'll fix this, but I hope it's helpful to make sense of what was happening.

[rrd2]

I understand and I don't mind helping improve great products like yours.

When I started the day yesterday, I opened LV2020 to work on one project.  Upon completion, I closed LV2020.  A few hours later, I had to work on another project that used LV2019.  That's when VIPM opened and I closed immediately closed it.  Finished my work in LV2019 and closed it.  Later I had to open it again and VIPM opened along with it again.

This morning during our initial messages.  I opened LV2019 to make sure I was correct in my replies.  I then close it and opened LV2020.  That's when I noticed no VIPM.  Closed LV2020, opened LV2019, and ... TA-DA ... VIPM.

Hope this helps.

[Jim Kring]

Hmmm, OK. Thanks for that info and the kind words. It’s helpful. 
 

Fix coming soon.

[Jim Kring]

Here's a pre-release of a build you can test.

vipm-20.3.2540-windows-setup.exe

PS - this link may stop working after a day or two, as we're working on the official release.

[rrd2]

Thank you, Jim.  I'll put it through its paces and let you know if I find anything noteworthy.

[whoistheotheraustinman]

I am seeing this behavior with LV 2022Q3. LabVIEW opens only to be followed by VIPM a few seconds later. 

[Jim Kring]

You should be able to change this from the right click menu of the system tray icon. You can also disable that completely in the VIPM options dialog.

Let us know if that works for you, or if it’s still misbehaving or unintuitive.

[Jim Kring]

See also: https://support.vipm.io/hc/en-us/articles/360045406692-Disabling-VIPM-service-System-Tray-startup-when-LabVIEW-starts-up