Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by sth

  1. I don't see the way to "ignore dependency". Still looking through help.
  2. In installing the JKI Flat UI Controls with LabVIEW 2020 on Mac OS, the package claims requirement to install JKI Design Palette. However this Package is not listed as available on the Mac. Not sure if there is something fundamentally not allowed on the Mac OS or if it was an oversight in packaging the JKI Design Palette. Furthermore, VIPM reports that there is also a missing dependency on OpenG Port IO which is a very old package that has never been compatible with the Mac OS. And is not part of most windows machines that haven't had a "Printer Port" in years. However that is a dependency in the OpenG toolkit which I use despite that missing dependency. However it now blocks in stallion of the JKI Flat UI Controls. (Note I believe that this issue is also in earlier versions of LabVIEW (does not work in LV 2019) as well, I just decided to update my controls UI using a modern looking set with a change to 2020)
  3. Any progress on that? Catalina has been out for awhile now and 64 bit apps have been the default since LabVIEW 16! Running a LabVIEW 15-32 build is a bit old! I am starting to test Catalina and VIPM is part of that since there is zero chance that NI-Package Manager will ever be available for the Mac. Possible Beta to test?? As a second point, on the Mac system if you initially run VI Package Manager under one user, it fails if you switch to another user account. There is some file permissions problem (the old error 7!) that I have not been able to work around. Either setting the permissions when the file is first created or changing the file open to read only might fix this.
  4. I seem to be getting a whole host of issues…. I am installing a clean reference system for LV. I can use VIPM if I carefully only use the admin account I installed VIPM from and not other admin accounts. BUT, after the install, it should do a Mass Compile of the packages since I have set that option. I get a message at the bottom "Connecting to LabVIEW 2014 (64 Bit) Timeout NNN" where NNN counts down from 120 seconds. I have verified the connection to LabVIEW 2014 (64 bit) (on Port 3370) and it seems to be correct. Is the Mass compile command connecting on a default port? I will do the manual mass compile since it does install the packages. It would be very very nice if VIPM used a LabVIEW 2014 run time. LV 13 and previous have a scrolling bug where if the window is scrolled to the bottom if you go 1 pixel too far the window jumps to the top. This has been fixed in both 32 and 64 bit LabVIEW 14. -Scott
  5. Jim, Thanks for looking at this. I spent some time re-installing and testing over the weekend. It seems to be a permissions issue with /Library/Application Support/JKI. If I install as one admin user, I cannot use VIPM as another admin user. Setting the group writable access on the files in /Library/Application Support/JKI does not help nor setting their group to admin. Then you get a message about cannot access the lab view updates. Not sure which file access triggers this. I even tried making things world writable but still no joy. I did notice that the preference for "Network" does not default to "direct access" on the Mac but to "Use System Proxy Settings (Windows Only)" which is probably not what is needed. However it should use the system proxy settings in the network setup anyway. Thanks for looking into this. I will just have to make sure that I use the same admin account for configuring VIPM. -Scott
  6. I am having trouble with VIPM 2014(1955) on Mac OS X. The SourceForgeMirrors.txt file is updated when it updates the package list. However this always seems to zero out the SourceForgeMirrors.txt file. This becomes an empty file and then VIPM tells me that I can't load from the OpenG or LV tools network. The file should have the contents from the initial install listed at the end of this message. This is with "Mac" line endings or \r. If I go to the preferences and ask VIPM to update the source forge repository list the file then becomes a zero length empty file. -Scott easynews: Phoenix, AZ (North America) superb-west: Seattle, Washington (North America) internap: San Jose, CA (North America) superb-east: McLean, Virginia (North America) voxel: New York, New York (North America) puzzle: Bern, Switzerland (Europe) mesh: Duesseldorf, Germany (Europe) ovh: Paris, France (Europe) dfn: Berlin, Germany (Europe) heanet: Dublin, Ireland (Europe) garr: Bologna, Italy (Europe) surfnet: Amsterdam, The Netherlands (Europe) kent: Kent, UK (Europe) transact: Canberra, Australia (Australia) internode: Adelaide, Australia (Australia) waix: Perth, Australia (Australia) jaist: Ishikawa, Japan (Asia) nchc: Tainan, Taiwan (Asia) ufpr: Curitiba, Brazil (South America)
  7. Michael, Thanks for the response. I have tried both versions of VIPM 2013. They seem to behave the same. The 2010 version works and remembers the multiple versions between restarts. The system does not auto find all my LV versions but every time reverts to only LV 8.5. Now since I have renamed the executables this is expected. I renamed them for two reasons. The first was to keep the preferences straight which is no longer necessary but the second is to identify them in the dock since the dock badging feature is not on all versions. The "sizes" setting is reset to 1 on all the preferences even though the data is all there. The data is all there for all the LV versions except the port numbers which is just the 8.5 version. The active target is still 12.0 but but that version has been cut out by setting the size to 1. I think that the number 0 target was LV version 13 but it was reset to 8.5 when I quit. The package I was originally trying to load and get an error 7 is downloaded from https://decibel.ni.com/content/docs/DOC-12813 -Scott [Targets] Connection Timeout="15" Active Target.Name="LabVIEW" Active Target.Version="12.0" PingDelay(ms)="-1" PingTimeout(ms)="60000" Names.<size(s)>="1" Names 0="LabVIEW" Names 1="LabVIEW" Names 2="LabVIEW" Names 3="LabVIEW" Names 4="LabVIEW" Names 5="LabVIEW" Names 6="LabVIEW" Names 7="LabVIEW" Versions.<size(s)>="1" Versions 0="8.5" Versions 1="12.0" Versions 2="11.0" Versions 3="10.0" Versions 4="9.0" Versions 5="8.6" Versions 6="8.5" Versions 7="8.2" Locations.<size(s)>="1" Locations 0="/sthMac/Applications/National Instruments/LabVIEW 8.5/LabVIEW.app" Locations 1="/sthMac/Applications/National Instruments/LabVIEW 2012/LabVIEW 12.app" Locations 2="/sthMac/Applications/National Instruments/LabVIEW 2011/LabVIEW 11.app" Locations 3="/sthMac/Applications/National Instruments/LabVIEW 2010/LabVIEW 10.app" Locations 4="/sthMac/Applications/National Instruments/LabVIEW 2009/LabVIEW 9.0.app" Locations 5="/sthMac/Applications/National Instruments/LabVIEW 8.6/LabVIEW 8.6.app" Locations 6="/sthMac/Applications/National Instruments/LabVIEW 8.5/LabVIEW.app" Locations 7="/sthMac/Applications/National Instruments/LabVIEW 8.2/LabVIEW 8.2.app" Tested.<size(s)>="1" Tested 0="TRUE" Tested 1="TRUE" Tested 2="TRUE" Tested 3="TRUE" Tested 4="TRUE" Tested 5="TRUE" Tested 6="TRUE" Tested 7="TRUE" Disabled.<size(s)>="1" Disabled 0="FALSE" Disabled 1="FALSE" Disabled 2="FALSE" Disabled 3="FALSE" Disabled 4="FALSE" Disabled 5="FALSE" Disabled 6="FALSE" Disabled 7="FALSE" Ports="<size(s)=1> 3363"
  8. Ashish, I am way beyond that point. I can concurrently connect to all 9 versions of LV on my system on different ports. VIPM reports that all the connections are verified and working. I can install somethings on LV 2012. But only if I don't quit and restart VIPM! If I quit and restart VIPM all the connections I entered vanish. This does not happen with VIPM 2010 but with both released versions of VIPM 2013. I should not have to re-enter all the connection data every time I start VIPM this is why settings files were invented. I can install OpenG packages if I open VIPM, create the connection to LV 2012 and then immediately install without quitting VIPM. But when I install ESF (from Norm Kirchner's) package I get the error 7. This is a second error. The settings error has just made it much harder to find the second error.
  9. Reverting to VIPM 2010 seems to work but is a limited. At least I can connect to multiple versions of LabVIEW. However going back to 2013 immediately limits me to a single version of LV upon restarting VIPM. I just removed ALL preference files and re-installed VIPM 2013.0.1 and added 3 versions of LV. Upon quitting VIPM and restarting I am back to a single version. If this isn't a settings corruption then there needs to be another explanation. I removed the entire directory /Library/Application Support/JKI where all the new 2013 version info goes and is a lot more compatible with OS X instead of putting all those files in either the home directory or the application directory. -Scott
  10. Ashish, That did not resolve the issue. That is very weird settings given how VIPM manages all the rest of the settings. I did reconnect all the versions. In fact, if I just open it and connect 1 more version (it opens with only 8.5 connected) and I add 2012. Then I quit and restart VIPM and I am back to only 1 connected version of LV. If I take my older settings file that had multiple versions of LV in it and open it with either VIPM 13.0.1(1906) or VIPM 13.0.0(1866) the number of connected versions of LV is reset to 1. It is odd that ports are handled in such a different way than all the other settings. For example, the "Names" have a separate "size" setting that gives the number of entries. Names.<size(s)>="9" and then followed by settings for "Names 0", "Names 1" etc. However Ports are given all in the same string Ports="<size(s)=1> 3363" There is no setting "Ports.<sizes(s)>" as there is for "Tested.<size(s)>" Either way, I cannot add a LV version without it disappearing upon restart. Lastly, there is no right click to run as administrator. I think you are taking me for a windows person. There is obviously access to the settings file since VIPM is modifying it. -Scott
  11. In poking around a bit more. The /Library/Applications/JKI/VIPM/settings.ini file has a corrupt entry. Ports="<size(s)=3> 3365 3364 3363" This seems very very wrong given the structure of the rest of the file. ----- If I blow away the settings file, it is recreated with just a reference to LV 8.5 in the TARGETS section, but still has the bad ports entry. [Targets] Names.<size(s)>="1" Names 0="LabVIEW" Versions.<size(s)>="1" Versions 0="8.5" Locations.<size(s)>="1" Locations 0="/sthMac/Applications/National Instruments/LabVIEW 8.5/LabVIEW.app" Ports="<size(s)=1> 3363" Tested.<size(s)>="1" Tested 0="FALSE" Disabled.<size(s)>="1" Disabled 0="FALSE" Connection Timeout="120" Active Target.Name="LabVIEW" Active Target.Version="8.5" PingDelay(ms)="-1" PingTimeout(ms)="60000"
  12. I updated my VIPM to the latest build (2013.0.1 build 1906) and now I get errors on installing? I am installing into LV 2012 (but I have links to the other LV versions on my system) which is my primary development system. I was trying to install Norm's ESF (Extensible Session Framework) and I get the following error. "Main Package Name: ESF - Extensible Session Framework v2.4.0.25 Package Name with Error: ESF - Extensible Session Framework v2.4.0.25 Error Message: VIPM could not install the package ni_tool_esf- . Error Code: 7 Error Source: ===============" The mysterious error 7 is a file permissions error. I am logged in as an admin and should be able to write to the LV directory. I have write permissions to vi.lib/addons. -------------------------------------------------------------- If I try to refresh my packages by looking for updates, I get Error accessing the following subscriptions: 1. LabVIEW Tools Network 2. VI Package Network This not a network problem since I am accessing the web to write this message and the firewall is open for all outgoing connections. -------------------------------------------------------------- And it does not seem to remember my configuration of various LV versions after restarting? I have write access to /Library/Application\ Support/JKI/jki.conf Attached is error file
  • Create New...

Important Information

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