Jump to content

Johannes

Members
  • Posts

    2
  • Joined

  • Last visited

Johannes's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. I have VIPM connecting to LabVIEW 2021 community on Debian 11.5 now but it will not connect to 2022 the 2022 Qtr3 version at all but which will run as root and complain about not being activated if running as normal user from the application menu in the Ffce desktop. This gives two methods for running Labview but causes what I think is a problem it that both can set its own LabVIEW port numbers. Thus depending on how LabVIEW is run it creates a problem that VIPM cannot compensate for. This appears to be caused by the Labview installer links to the labviewcommunity versions at /usr/local/natinst/LabVIEW-2022-64/labview and also at /usr/local/natinst/LabVIEW-2021-64/labview. To me this appears to be an attempt to convert from 'labview' to actual names of labviewcommunity or labviewprofull and potentially change restrictions as set by license. I think all this likely induces nothing but problems..
  2. I have installed both the 2021 and 2022 labview-2021-community and labview-2022-community editions on Debian. Both are working and the 2022 vipm appears to be working fine when running as root. The problem is that vipm will not connect to the assigned ports of Labview 3362 or 3363 in vipm and Labview versions. It will start the proper version of Labview but not connect. It just complains that there is a another version Labview version is running at the specified port or path. Since the individual ports are properly configured I think that this could potentially be due to a Labview naming issue. Possibly due to the addition of community to the name of Labview. As an example in: /usr/local/natinst/LabVIEW-2022-64/labviewcommunity In vipm it will show the Labview folder names 2021 -64 and 2022-64 but may just be expecting labview instead of labviewcommunity. Is this a possibility?
×
×
  • Create New...

Important Information

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