Jump to content

All Activity

This stream auto-updates

  1. Yesterday
  2. We're excited to announce the VIPM 2021 beta! You can Download VIPM 2021 Beta Software Here. Note: If you are a JKI Dragon Beta Tester, installing VIPM 2021 beta will remove JKI Dragon. Please do not install VIPM 2021 beta on the same machine on which you wish to continue testing JKI Dragon. What's New: Supports LabVIEW 2021 beta Main UI layout and usability improvements [build 2732] Fix - Installing packages with deep recursion (e.g. A>B>C>A) was getting stuck and hanging VIPM (e.g. SQLite toolkit). This has been fixed. [build 2732] Fix - Detect
  3. Hello, I am installing LabVIEW and EasyXML on a new PC. This PC needs to have both LabVIEW 2017 and 2019 installed for our purposes. I’ve been encountering issues while trying to install the EasyXML package with VIPM 2017 and 2019. In particular I am getting the error VIPM could not connect to LabVIEW 2017 – please see the first image. The error pops-up after I hit Install and LabVIEW finishes loading. So I think that it is not a timeout issue as suggested on the various forums about this topic, because actually LabVIEW opens up. My guess is that there is some sort of communication betwee
  4. Last week
  5. User Stories: As a user of VI Package Manager on a system that is not connected to the internet, I want to output a list of dependencies for a package so I can go download them. As a developer I would like to get a list of packages and dependencies to add to my software's documentation.
  6. Earlier
  7. Dear community, To keep my report clean😀 here are my statements Goal Move code which contains (Boolean) references of controls to another frame by cut and paste. When pasting a copy of the controls are made, the references now reference to the newly created controls. Result I only cut the highlighted section, pasting results in a copy even using shortcuts (Crtl - V or menu Edit - Paste) Note the "2" behind the pasted references. Workaround Create a new reference and place this reference directly in the desired frame. Question Is it a bug o
  8. Hello, as we are moving to LV for Linux 2020, is there an ETA for having VIPM 2020? I am currently using the workaround above of manually copying the packages from Windows to Linux but it is not easy to maintain.
  9. I can confirm the same issue. JKI Design Pallete 1.0.5.196 can not be installed with LabVIEW 2018 SP1, Windows 10 64 bit. Fortunately JKI Design Pallete 1.0.5.193 and JKI Flat UI Controls 2.0.1.28 install and function on my system.
  10. So I'm doing this as the last resource because I have tried everything. I've read a lot of forums. Put commands in the terminal. Like the ones in the photo. And the same thing appear. Over and over again error code 07. The apps have total access to the disks, have permission in the firewall. I have a MacBook Pro with macOS Big Sur. So when I install any packages, it's starts. But always reach a point and stops. I literally tried everything. I need this for a project at my college. Please help. Thank you, Andres Esguerra. prueba.mov
  11. @felipefoz is aware of this, but for other folks out there, this is set to be part of Caraya 1.2 when released. https://github.com/JKISoftware/Caraya/issues/121
  12. @Mathilde (I just saw this thread today) Caraya is not well suited for automated code coverage calculation as it executes at the VI level, not the application level. There is no inspection performed and the framework is all geared towards individual assertions. An application could be developed, on top of Caraya, to inspect code and report on the minimum number of assertion tests to be performed to cover all conditions, but it would probably still be opened to interpretation since different assertions can be done on the same case to test all the limit conditions. As an examp
  13. I'd love to be able to filter out the vipm.io content with labels such as "open source" to only list the projects that have a public repository that I can fork and/or contribute to. This would filter out any package that do not accept contributions. Free does not mean opened. I know that "tags" could be useful filters, but tags do not mean that the information is verified. If there are multiple packages that provide solutions to similar functionality, I'd like to further filter down the list. On the other hand, some users might want to filter out the open source projects in favor of com
  14. Hi, For my build servers I would like to avoid having to call Labview to run a vi that uses VIPM API to apply a vipc. Instead I would like to execute a command that does the same thing. I keep reading about the VIPM (File Handler) command line API but I can't find any documentation about it? Where is it? Cheers
  15. I tried to do the update to 2020.3 from the help menu and it errored out. See attached. I ran the installer .exe for 2020.3 and now I the handler won't open. I get the icon in my system tray but nothing happens. See pic. This is a new computer with windows 10 and LabVIEW 2019 and 2020 freshly installed. My company has very high security protocols for downloading and installing any software. I'm one of the few outside IT that has admin rights to install programs and that is just for my computer. I will now uninstall VIPM 2020.3 and reinstall 2020.2 so I can continue using yo
  16. Hi Jason, I'm glad you got it working. I'm curious if the problem re-appears if you upgrade back to 2020.3, but I'll let you decide when you have the time do that experiment. Thanks again for posting about this issue -- it's helpful to us and other users. Regards,
  17. Update: I uninstalled 2020.3 and installed 2020.2 and now the handler loads and I was able to install the JKI state machine. Hope all of this helps. Thanks,
  18. Update: I was able to uninstall 2020 version and install 2019 and it worked fine. Then I updated to 2020 and now the handler will not load. Thanks,
  19. Yes I can't get the handler to open at all. My company is using SentinelOne for security. Not sure if that is the issue. Thanks,
  20. Hi @Jason Herington. Thanks for reporting this. I haven't seen this specific error before. Does it happen every time? -Jim
  21. This is the event log I get when I try to open VIPM file handler: Log Name: Application Source: Application Hang Date: 4/16/2021 11:22:05 AM Event ID: 1002 Task Category: (101) Level: Error Keywords: Classic User: N/A Computer: Description: The program VIPM File Handler.exe version 2020.3.0.2540 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: 1664 Start Time: 0
  22. Can you verify if you have followed instructions mentioned in this Knowledgebase? The issue in this KB is not relevant to yours but the steps involves should help solve you issue as well. https://support.vipm.io/hc/en-us/articles/214135663-VIPM-fails-to-launch-after-splash-screen-on-Windows
  23. I have the same issue. New computer and fresh installation of the Windows OS. After installing LabVIEW 2020 and restarting the computer, the same information (VIPM service with dashed arrow) as at the beginning of this post appears . I did try also earlier versions of VIPM. It works well up to v. 2019. Problems started after upgrade to 2020.1 ol later versions. BTW. I have Cybereason installed too.
  24. Can you try typing this into a terminal? cd ~/Library/PreferencePanes/ This will navigate you into the PreferencePanes folder then type the following: ls This should list the contents of the folder. Do you see something like the following? VI Package Manager.prefPane If so, then typing the following may fix the issue (as described here) by removing the "quarantine" flag in the OS security settings: sudo xattr -d -r -s com.apple.quarantine "~/Library/PreferencePanes/VI Package Manager.prefPane"
  25. Hi Glen, Sorry for the frustration. Mac support has been challenging for VIPM, but we try. It looks from your post that you tried all the tips mentioned on the knowledge base entry here: File Permission Errors running VIPM on macOS The "AppTranslocation" thing in the file path ("/private/var/folders/w7/rtz9k1m114390vq0fxc21bv00000gn/T/AppTranslocation/54274253-33FC-46D0-A566-B7 F86CC7D1F7/d/VI Package Manager.app/support/callbacks.llb/Refresh Menus 2013.vi") makes me curious if this is some new kind of file system thing that we're not handling. I did some googling of "AppTrans
  26. When I attempt to install packages, I keep getting errors (please see below). It happens if I attempt to install ANY package with my package manager. I went into my System Preferences on my Mac and made sure that LabVIEW and VIPM has access to the disk (r/w) I'm still getting the errors - this doesn't make much sense to me. The VIPM error is as follows: Main Package Name: MakerHub Toolbox v2.0.0.35 Package Name with Error: MakerHub Toolbox v2.0.0.35 Error Message: VIPM could not install the package lvh_toolbox-2.0.0.35 . Error Code: 7 Error
  27. Oh no! I’m sorry to hear the installers and security challenges are such a pain. I wonder if there’s a way to have a VIPM installer that does not include the runtime engine stuff — can you install VIPM and the skip over the runtime installer part, I wonder.
  28. We are also having issues with VIPM not running on our development computers due to Cybereason ActiveProbe. But it's even worse for us... We have LabVIEW 2019 Runtime in our Software Center, which allows anyone in the company to install it without admin rights. This has been done so we can give small executables to people to use, ones that don't need VISA, DAQmx, etc. Runtimes. Well, everything was fine a couple weeks ago but now ALL of those small programs load up with the same message, "The VI is not executable..." Since VIPM 2020 uses LV19 Runtime, this makes sense. But wow is it
  1. Load more activity
×
×
  • Create New...

Important Information

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