Jump to content


JKI Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Ashish

  1. Not sure if it is related but yes....VIPM connects to LabVIEW via VI Server. I wonder if LabVIEW reinstall/repair will help. Keep me posted on what solution NI provides for Desktop Execution Trace Toolkit.
  2. Hmm....thats odd. We want you to try to re-install VIPM. To do this you will have to uninstall VIPM using the VIPM uninstall and then delete the following folders manually: C:\ProgramData\JKI\VIPM C:\Program Files (x86)\JKI\VI Package Manager Then re-install VIPM.
  3. aputman, Thanks for summarizing your observations and the solution that helped leverage JKI State Machine architecture to meet your needs. As drjdpowell pointed out, there are certain tradeoffs as well. So, it all depends on the use case. Certainly, your suggestions will be useful for many JKI State Machine users in similar situation.
  4. `Are there any popup dialogs at LabVIEW launch? You must disable them (by selecting the checkbox "Do not show again").
  5. Refer this article: http://support.jki.net/entries/21447601-Resolving-issues-with-VIPM-connecting-to-LabVIEW
  6. Hi, I was able to successfully install MakerHub Link v2.0.0.93. Chances are that VIPM was not able to download the package successfully. Else, try to contact the package provider for any similar issues reported.
  7. Hi, You will have to manually tweak VIPM Settings file by following the below instructions. Let me know how it goes. FYI, our experience suggests that editing the file in Notepad gives good results. Locate Settings.ini file located at: /Library/Application Support/JKI/VIPM/Settings.ini Backup this file (copy at a different location) Open Settings.ini in notepad Locate "Targets" section and update as shown below. (The example is for one version of LabVIEW installed on the system) [Targets] Names.="1" Names 0="LabVIEW" Versions.="1" Versions 0="13.0" Locations.="1" Locations 0="/Macintosh HD/Applications/National Instruments/LabVIEW 2013/LabVIEW.app" Ports=" 3364" Tested.="1" Tested 0="TRUE" Disabled.="1" Disabled 0="FALSE" Connection Timeout="120" Active Target.Name="LabVIEW" Active Target.Version="13.0" PingDelay(ms)="-1" PingTimeout(ms)="60000"
  8. Where did you get the VIPM installer from?
  9. You can think of adding a dummy subVI in the package that you will replace later.
  10. James, There are no reports of VIPM update checker. The JKI Update checker should have notified you of the build 1967. Chances are that the update checker might have been blocked possibly by firewall resulting in this behavior. Sorry for the inconvenience.
  11. Anders, The error image seems to be missing. Can you send it again? Also, send the error description, image to support@jki.net.
  12. If you add other packages as dependencies, then you will get all the necessary subVI components installed. Also, the order of installation should not matter since VIPM performs mass comipile after package installation.
  13. Well....sorry to say that we are not able to recover the missing attachment. We will keep an eye on the error occurrence in future and let you know how it goes.
  14. Hi, There seems to be no easy way to find the missing attachment. Do you remember the name of the attachment? I can check on my local machine, if I had ever downloaded it.
  15. Ok. Let me check with our team about the missing attachment.
  16. Hi, Is the issue resolved? If not, can you share the code to help reproduce the behavior?
  17. Steen, Just trying to catch up on open items. Have you ever resolved the issue? Do you happen to have any dynamic libraries?
  18. Manikandan, This thread is not relevant for licensing related discussions.
  19. Sara, This article will provide appropriate reasoning: http://support.jki.net/entries/66745297-VIPM-2013-cannot-install-packages-built-in-VIPM-2014
  20. Sara, So, as suggested in the message, did you try building with System target? We introduced "System" as a target in order for users like you to create packages without VIs in it.
  21. Good catch! I did not pay attention to the error and certainly recommend the way you did. Thanks for the updates.
  22. Jason, Thanks for the updates and clarification. Glad to know that you were able to sort it out.
  23. Attached is the screenshot showing updated VI that should work. Let me know how it goes.
  • Create New...

Important Information

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