Jump to content

All Activity

This stream auto-updates     

  1. Last week
  2. I can't point you to a known issue, but there's a good chance we've fixed the issue you're mentioning.
  3. Thanks for your response. I am using VIPM 2016 SP1. Is that a known issue in VIPM 2016?
  4. Earlier
  5. Which version of VIPM are you using? I think we made some improvements to VIPM 2018 (and the f1 release) that improve support for PPLs.
  6. Bruce, Can you try to run VIPM as root user using pseudo commands? If that does not help, send us VIPM Error Logs. Refer this article on how to do that: https://support.jki.net/hc/en-us/articles/214135523-How-to-submit-VIPM-Troubleshooting-Logs
  7. I have a .vipb and .vipc files for my project. It was building the packages earlier, but recently I have changed all my project files and reusables to packed library. Now I am getting Error 10 while building the package. But I am able to build the package successfully, If I rename/delete the .vipc it it is building properly. Thanks in advance.
  8. K. Ludlow

    Issue with text encoding

    The flatten to JSON string.vi appears to be using CP-1252 encoding instead of UTF-8. This is causing the character - to be cast as – in my application. This is generating an error in the application. Is there a way to correct this?
  9. I got it. Thanks for confirming this, Jim.
  10. Bruce Diesel

    2017 VIPM Not Connecting to 2018 Labview Linux

    Hi Ashish, thanks for the pointer to the article. Unfortunately it has not solved the problem. VIPM does initially connect to Labview and restart it. But then it sits trying to connect to Labview and eventually times out. Bruce
  11. Hi Tianbin, The VIPM package URL handler only works on Windows, currently. Jim
  12. Ashish

    error code 10

    Ben, Thanks for reporting the issue. We have forward this to our team to take a look at. We cannot promise on when the fix will be released.
  13. Bruce, The issue is likely related to permissions. Have you referred this article: https://support.jki.net/hc/en-us/articles/214135683-Resolving-issues-with-VIPM-connecting-to-LabVIEW
  14. Hi All, I am having difficulty connection VIPM 2017 to Labview 2018 on Linux. I am running 64bit Fedora, with latest Labview 2018. I have installed the required libraries for 32bit VIPM, and it is running fine. When I try to install a package, I don't get a connection to labview. Even though it does recognise that 2018 is installed, and Labview get's restarted by VIPM. After that, it sits trying to connect and eventually times out. Any suggestions? Bruce
  15. smidsy

    Real Time Unit Testing

    HI, I have the same question regarding RT support. I've tried running Test Suites and Test Caseson my RT target with no success: When running Test Suites - always 0 test cases run and no error When running Test Cases - error 7 is generated when discovering class methods I have a feeling that RT is not supported by JKI VI Tester, so there is a room for improvement. All the best, Nikita.
  16. Ben Barrett

    error code 10

    And one last update, sorry about the three posts in a row. I noticed that the malleable VI common to all the VIs failing the build also called malleable VIs within itself (part of the same set). Apparently it doesn't mind building malleable VIs, as long those malleable VIs don't contain other malleable VIs. Luckily for me, in this case, I only had one level of embedded malleable VIs. I solved the issue by replacing the embedded malleable VI its contents (it was a pretty small VI so this wasn't disruptive on the BD). I imagine it this could be a larger issue for someone who built a highly embedded malleable structure and wanted to try and build a package. Is this a bug or is there something about malleable VIs that make them incapable of being built into packages?
  17. Ben Barrett

    error code 10

    Some additional information: The VI's causing the problem all seem to be ones containing the same malleable VI
  18. Hi, Greetings from National Instruments Shanghai R&D. We have a link vipm://jdp_science_jsontext, we can use this link to launch VIPM to the jsontext toolkit install page, we uses System Exec.vi and pass a command line parameter to it(e.g, “cmd /c start vipm://jdp_science_jsontext”), this works perfect on Windows(put this vipm:// link into a web-browser also works). However, on Mac/Linux, we can not do this successfully, we can only launch vipm but cannot open to jsontext toolkit installation page. Is the vipm:// link recognized/supported by VIPM for Mac/Linux? Is there a way to launch VIPM 2017 for Mac/Linux to show a specific toolkit via command line parameter? If yes, how to do that? Thanks! Regards, Tianbin Xu
  19. Great! Glad that you got it working.
  20. Hi Ashish, I have and thank you so much for sending the link. I am happy to say that the problem is fixed and I am able to use VIPM without any issues at this moment. We use Kaspersky Endpoint Security 10 and added VIPM as an exception within Kaspersky and that is why I was unable to achieve a connection with LabVIEW.
  21. Hi, Have to referred this article: https://support.jki.net/hc/en-us/articles/214135683-Resolving-issues-with-VIPM-connecting-to-LabVIEW
  22. Jim Kring

    Support for LVLIBP?

    Hi Steen, Thanks for the well thought out question/proposal. We've considered this at several points, yet there have always been very many considerations that make supporting LVLIBPs problematic. Unfortunately, NI did not have LabVIEW developers in mind when they designed LVLIBPs -- they were focused mostly on addressing internal use cases such as streamlining deployment to embedded targets.
  23. I have been trying to make a connection from VIPM to LabVIEW 2017 but keep getting the same error that states it was unable to connect and to allow access to VIPM by specifying "localhost" in the allowed list in LabVIEW. I have checked settings in LabVIEW and all is allowed. I have also checked for firewalls blocking the connection and there aren't any. I have also reinstalled both LabVIEW 2017 and VIPM but still have not had any luck. Any input that you are able to provide would be greatly appreciated. I am trying to install a third party program into LabVIEW that uses VIPM to download it. Here is what the error is for this issue:
  24. Ben Barrett

    error code 10

    Hi, this topic is 11 years old, but I'm having a similar problem with a package I'm trying to build. I'm getting the same error (10), and if i exclude two particular files from the build it goes away and builds successfully. I tried to find the ./errors directory but can't locate it, has its location changed in the intervening versions between the original post and now? I should note I'm running LV2017 on Windows 7 instead of Mac. Error Details: Code: 10 Source: Error 10 occurred at New VI Library.vi Possible reason(s): LabVIEW: Duplicate path. Error Conditions: Create Target File error: File Path: <Not A Path>
  25. Steen Schmidt

    Support for LVLIBP?

    Upon further investigation I can see that it's not possible to add components from a packed project library directly to a palette (LabVIEW itself does not support this). Palettes containing LVLIBP methods/VIs has to be created in the original LVLIB. First you have an LVLIB, which you build an mnu-file for. This mnu-file you add to the LVLIB, and the entire thing can now be built into an LVLIBP with LabVIEW. Then it's possible to point LabVIEW at the mnu-file now embedded in the LVLIBP. For this process to be entirely handled by VIPB, you'd have to add "build LVLIBP" into VIPB as well (since that part occurs inbetween defining the mnu-file and building the output vip-file).
  26. Steen Schmidt

    Support for LVLIBP?

    Hi, Are there any plans for including support for LVLIBP in VIPB? Currently VIPB does not recognize LVLIBP as a LabVIEW file. A package containing only a LVLIBP requires SYSTEM instead of a LabVIEW version as build target. Even worse is that you cannot create palettes in VIPB with LVLIBP entries in them. The proposed workaround to create wrapper VIs to include in the palettes, that place their content, is no use: For proper documentation in the palettes such wrapper VIs must echo the conpane, terminal configuration, and VI Description as the LVLIBP VI it contains on its BD. But if you set this wrapper VI to place its content, all the wrapper VI's terminals will be placed in the caller as well. That won't work. Why LVLIBP? To do proper components in LabVIEW you need to use packed project libraries (PPL/LVLIBP). This is the only LabVIEW app build output that can be excluded from an executable, and thus the only component type that will alow patching of applications piece by piece. Source distributions cannot be excluded from executables for instance. Cheers, Steen
  27. Jim Kring

    Problem converting back from JSON

    Hi There. Yes, it looks like you may have found a bug. I think that "[]" characters are allowed in JSON data names. Perhaps they were removed because they are also special characters.
  1. Load more activity
×

Important Information

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