Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. @ThomasGutzler @jamesmc86 @TomMcQ @hooovahh @drjdpowell We've been able to reproduce and fix this issue (ID 18605). It'll be fixed in VIPM 2020.
  3. Not a good sign that there were no replies here, but it's worth a shot. After successfully building my application for months, I am also now getting this same error on the same VI. Were you ever able to find a resolution to the problem?
  4. Hi. I just took a look in the latest version of VIPM and it's having some trouble building your package. Note: installing and calling VIs installed outside of LabVIEW is somewhat non-standard, so that's probably why it's not working too well. We'll need to do further debugging.
  5. Last week
  6. This is the right place to ask VIPM related questions for getting community contribution. FYI, we (JKI) do have a dedicated support for VIPM Pro subscribers.
  7. It also looks like VIPM keeps on trying to execute this unknown command because I noticed that the error logfile keeps on growing every 100ms until I close the VI Package Manager. The error logfile than contains this error message about 10 times per second. Even restarting the VIPM doesn't stop the error logfile from growing. It just keeps adding the same message over and over. Even restarting the PC doesn't seem to help. Whenever VIPM is open the error logfile keeps on growing. It only stops when I select "Apply Configuration" in the context menu because then VIPM can execute a known command and stops reporting this error.
  8. When I right-click on a vipc file in the windows explorer the context menu shows the option "Add Contents to VIPM Library". Selecting this opens the VI Package Manager but the contents of the vipc file are not added to the VIPM Library. The vipc file definitely contains the vip itself. The error file (located at C:\ProgramData\JKI\VIPM\error) contains the following error : It looks as if the add-command is not supported (anymore)??? Best Regards, Stefan
  9. Here is what I have done so far to reproduce the issue (I can reproduce on multiple packages, I used a simpler example for the post): Build my FGV Package. Shown below is the file locations on disk in the LabVIEW Project. I then built the package, and installed the package. After installation, the files are all in the FGV folder, with no extra files. Now I want to build my File Path package, which depends on the FGV Package I just installed. NOTE the FGV - Test Mode located in the FGV folder on disk. VIPM correctly identifies that the BMI FGV package is required. Save the configuration and build the package. Install the package. When the package is installed, the file that was in the FGV Package has been added to the directory File Path, instead of using the FGV - Test Mode located in the FGV folder with the FGV Package.
  10. Earlier
  11. I am creating some packages for our internal reuse code. I create Package "Config Files". This package does not have any other package dependencies, and installs as expected (using custom directory, not under LabVIEW). I create a second package, "File Paths", which calls a vi in the Config Files package. Since the Config Files package is installed, VIPM correctly says that the Config Files is a dependency. When I go to build and install (using custom directory, not under LabVIEW) the File Path package, I see a copy of the vi from Config Files under the directory of File path, instead of the file that should have been used under the Config File path. What I Expect: C:\Config Files\test.vi When Installed: C:\File Paths\test.vi I saw some older forum posts about Internal and external dependencies, but I do not see that option in LV 2019. Has this option been removed?
  12. Hi, I am trying to instal LINX for LabVIEW 2013 and I encountered a problem (see attachment). I am using Win 10 and VIPM 2019. TCP/IP port is 3363 and is checked. Under Win XP and earlier version of VIPM it was working. Any help is welcome. Thx.
  13. Hi! I wanted to know where can I ask a question about my problem with VI Package Manager so I get a fast reply? I am sorry if this is an off-topic, but I really urgently need to solve my problem and it just seems that people do not have the same problem as me. But the issue still must be solvable, right? I hope maybe you have an experience of where to turn to in a similar situation. Please let me know, I would be really grateful! I tried to post on LabVIEW forum, but I could not find help there either. This forum just seemed as the right fit, but I am supersized that it is not that active. Thank you in advance!
  14. Just to complete this - in case someone else sees this issue - we've made some server changes on our end which are the root cause of this problem. The server changes have changed permissions on users. Running VIPM as an administrator solved this problem. While we're working on the permissions settings, I've set the shortcut to VIPM to run as Administrator and all works just fine.
  15. Ok, thanks for letting us know, Tim. Hope you got it working.
  16. Hi! I have an issue with not being able to run the LINX example for my Arduino MEGA in LabVIEW. I am using LabVIEW 2019 (32-bit), 2019 JKI VI Package Manage, Diligent LINX (version 3.0.1.192) on Windows 7 (64-bit). So the issue here is that I am not able to run the program and when I click on the broken arrow, it says I have no errors (photo 1). It seems that the error is with the Loop Frequency as I show in the second photo below. I was following this link and tried to force a recompile - did not work. I ran the mass compile and there are indeed a problem with the Loop Frequency (photo 3), but what can I do about it? How can I fix it? Please tell whatever you think, I will try out anything to make this work. Photo 1: Photo 2: Photo 3:
  17. I have an activation problem with Labview. This is most likely the cause of the above issue. No need to respond. Thanks
  18. Below is the error Details from the failed installation. Any help is greatly appreciated. Tim Main Package Name: JKI Serialization v1.0.1.14 Package Name with Error: JKI Serialization v1.0.1.14 Error Message: VIPM could not install the package jki_lib_serialization-1.0.1.14 . Error Code: 8 Error Source: Open/Create/Replace File in C67C17A61D892A779727551BEF09A84E->43105161E3ECC5D5EE650DF274C1CB11->0ED5338B9A29C49A512F6049C2CCAE99->1DBEABF39FB76470575E756F0E9DB3AC->87355405EFC0DDB6ACE0A96175E31D86->OGPM Class.lvlib:89AC7BADF759B8183E200C1F7AFA7855->OGPM Class.lvlib:3617A98EB64CF6012064A2A881466B07->579BE417495B7ADCD1FF111EE165D832->VIPM Main Window.vi<APPEND> C:\ProgramData\JKI\VIPM\cache\jki_lib_serialization-1.0.1.14.spec =============== Main Package Name: JKI Unicode v1.0.0.7 Package Name with Error: JKI Unicode v1.0.0.7 Error Message: VIPM could not install the package jki_lib_unicode-1.0.0.7 . Error Code: 8 Error Source: Open/Create/Replace File in C67C17A61D892A779727551BEF09A84E->43105161E3ECC5D5EE650DF274C1CB11->0ED5338B9A29C49A512F6049C2CCAE99->1DBEABF39FB76470575E756F0E9DB3AC->87355405EFC0DDB6ACE0A96175E31D86->OGPM Class.lvlib:89AC7BADF759B8183E200C1F7AFA7855->OGPM Class.lvlib:3617A98EB64CF6012064A2A881466B07->579BE417495B7ADCD1FF111EE165D832->VIPM Main Window.vi<APPEND> C:\ProgramData\JKI\VIPM\cache\jki_lib_unicode-1.0.0.7.spec =============== Main Package Name: JKI JSON v1.1.10.37 Package Name with Error: JKI JSON v1.1.10.37 Error Message: VIPM could not download the package jki_lib_json_serialization-1.1.10.37 from the remote server. Error Code: 1 Error Source: (No Package Info found for "jki_lib_json_serialization-1.1.10.37") OGPM Class.lvlib:A49D5A837FB8B8AA12AB7AF4D6183704 in 8287055C6AB423A5B8472CDE8E59DC22->VIPM Main Window.vi ===============
  19. I can't understand why that's not working. Can you try restarting VIPM, refreshing the package list, and see if you get the same error?
  20. Hi there. Thanks for your question. Yes, VIPM users need Pro to subscribe to a custom repository.
  21. I am using the trial version of VIPM to evaluate whether our company wants to utilize VIPM Pro for our process. I have been happy with it so far, and have been able to create a number of packages. Now I want to start having other team members use the packages I created. So I have published to a repo on a network drive. When the other team members (who have the free version of VIPM) try to go to the Tools > Options, then click on "Network" to add a subscription to the local repo, they get a dialog that says "Subscribing to a VI Package Repository, requires upgrading your Free version of VIPM to Pro". This is the method described in the tutorial video on the JKI website. https://support.jki.net/hc/en-us/articles/214136483-Getting-Started-with-VIPM Do all team members now need VIPM Pro to subscribe to a local feed? I tried using VIPM 2018 and 2019, got the same error in both.
  22. I have a *.lvlib file which has some VIs and non LabVIEW file.(say *.txt). Now I have the package built. (No much of configurations in the VIPB). After the installation of the package, the lvlib file is corrupted and the says the TXT file is missing but the file is present in the folder location. Looks like the lvlib file still points to the file in the temporary location which was created during package build process. I have attached a sample library with this thread. Thank in advance for any help on this. Regards, Bhaghyaraj. Sample Package.zip
  23. Hello! I need to install the vi package manager 2014 and I cant find it. Im only finding the 2013 version and it doesnt include the biomedical toolkit. Can you please provide me with any link where I can find the 2014 version? thank you
  24. Hello! I need to install the vi package manager 2014 and I cant find it. Im only finding the 2013 version and it doesnt include the biomedical toolkit. Can you please provide me with any link where I can find the 2014 version? thank you
  25. Elmar, At our lab, I did exactly the same for the same reason. To me a very obvious improvement, extremely helpful to find from what part the error originated. I changed the colour of the Parse State Queue VI to distinguish it from the original. See the yellow coloured vi icon in the screenshot below. Now a wire "previous" state is available for error processing, which in my case is done in the white coloured subvi "ERROR". Would love to see this in the next update of the JKI SM :-) @Jim Kring I find it cumbersome to have multiple logins for multiple platforms. This is the JKI forum and you ask for feedback on GitHub? >> We've posted a related idea and request for feedback, here: https://github.com/JKISoftware/JKI-State-Machine/issues/11 >> [..] Should we, instead, make the Previous State available to all frames of the JKI State Machine (e.g. as an additional output to the Parse State Queue), [..] Yes, this is sufficient for me. Oh, and I should mention that I use the very helpful GPower error toolset (https://gpower.io/?lang=en) which allows for creating (and extracting)multiple errors on the "standard error wire". So then the JKI Error Handler frame can handle multiple errors, originating from a single frame.
  26. Is it possible to allow for a user to turn off the warning dialog that pops up every time Reload is pressed? I am currently developing tests one at a time, making sure they fail, then modifying and making sure they pass. It is kind of annoying to have to click the pop up away so often as I am reloading frequently. Thanks for this product, it is changing the way I program! Ryan
  27. Hi, I am using JKI SM for a project. I need a vlaue generated in JKI SM to another loop to generate a user event. The value is timestring and will trigger a state in JKI SM. I a able to generate the timestring user event to stop the executin after 60 seconds. The (time+60) seconds timestring is generated in JKI and this value comes back in the JKI to trigger a state. I have attached a vi which generates an event after 60 seconds from execution and stops the VI. Please convey how can I get the time+60 second value out from JKI. Or Can i achieve this within JKi itself? User Event Example (3).vi
  28. Recently installed LabVIEW 2017 (have other versions already installed), VIPM Pro 2019 fails to install Hidden Gems for LabVIEW 2017 (but installs OpenG just fine).  I also tried running VIPM as Admin, made no difference.  

    Oops, spoke too soon -- Got Error Code 7 with OpenG LabVIEW ZIP Library.  Had gotten Error Code 8 with Hidden Gems.  Did reboot on first seeing this error, and still error persists.

    One other Gripe -- I logged in to JKI Community, saw my old messages, but couldn't Post.  I was identified on the Forum as Bob Schor (Members), but it still insisted that I "Sign In" again to post.  I did, got back to the same place, and now I can post.  This is an annoying "Feature" of the site!

    Bob Schor

    1. Bob Schor

      Bob Schor

      OK.  Second Reboot, uninstalled then reinstalled OpenG Toolkit, on reinstallation, only the LabVIEW Zip Library seemed to be installed, without error.

      Hidden Gems in vi.lib (from the 2017 menu) still gives me the error, message attached below.

      This time, when I log in to the Forum, I get here without trouble (i.e. it not only takes me to my "page", but it lets me enter this message without needing to "Sign In" again).  Weird.

      Bob Schor

      VIPM Hidden Gems Bug.txt

  1. Load more activity
×
×
  • Create New...

Important Information

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