Bob Schor Posted September 16, 2014 Report Share Posted September 16, 2014 I recently installed LabVIEW 2014 (32-bit) on a Windows 7 Pro (x64) machine that had VIPM 2014 already installed. I also have LabVIEW 2010 through 2013 installed on this same machine. I set up all of my LabVIEW versions with the same TCP/IP port, 3363, and "force" VIPM to accept this (so far, this has not been a problem). I just (for the first time) tried to install some packages (such as OpenG) on my 2014 system. To my surprise, on several installations, it would start, get about half-way done, then start the 2-minute Timer, apparently trying to connect to LabVIEW. When the timer expired, instead of an error message, I got a message "Successfully installed". And, indeed, if I stop LabVIEW and restart it, my packages show up in the palette. Why is VIPM "wasting my time" by making me wait two minutes per installation when the installation succeeds? Is this a Bug or a Feature? Bob Schor P.S. -- I'm running the Pro version of VIPM, if that makes a difference. Link to comment Share on other sites More sharing options...
Jim Kring Posted September 16, 2014 Report Share Posted September 16, 2014 Hi Bob, In this case, it seems the connection timeout was not a fatal error, since it only needed to connect to LabVIEW to refresh the palettes. I would focus on figuring out how to get VIPM to successfully connect to LabVIEW. Is there a reason you're using the same TCP-IP port for VI Server on all your instances of LabVIEW? Note that there are a variety of reasons VIPM might not be able to connect to LabVIEW, including windows firewall, LabVIEW VI Server settings, etc. -Jim Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.