Jump to content


Popular Content

Showing content with the highest reputation since 07/14/2020 in all areas

  1. 1 point
    Is there any way by which we can perform some operation before / after installing a VI Package configuration? Or is there a way to restrict the installation of a VIPC file based on few conditions? Or is there a way to restart LV before / after applying VIPC?
  2. 1 point
    I found a method that works by using Darren's quick drop shortcut method. https://forums.ni.com/t5/Quick-Drop-Enthusiasts/Quick-Drop-Keyboard-Shortcut-Create-Place-VI-Contents-VI/gpm-p/3520372?profile.language=en I just put the JKI down in a new VI and edited it as I would normally for every new SM and then saved it as a quick drop.
  3. 1 point
    Yes this 2020.1 version seems to circumvent the problem. With this experience I will try to stay at this version as long as I can...
  4. 1 point
    Some advanced users are asking for support to install VIPM for Windows onto a Docker container. This would allow creating fully automated build processes that spin up virtual machines that have LabVIEW and VIPM installed on them, so that VI Packages can be created automatically.
  5. 1 point
    John, check out "Test Runner Pre-build action.vi" in the 1.0 release. I'm not sure what the current version is on LVTN, but you can find 1.0 on GitHub: https://github.com/JKISoftware/Caraya/tree/release/1.0.0/src The first snippet below is the Pre-Build action itself, the second is the actual guts of where the test gets invoked. Let me know if that doesn't get you started in the right direction or you have more questions.
  6. 1 point
    Hi all, I am using VI tester to run unit tests in my project. When I run unit tests for the VIs which are using NI XML APIs. The LabVIEW crashes/hangs randomly at the VI - "..\vi.lib\xml\XPath\Get All Matched Nodes.vi" at the DLL Node. I am not sure about the reason why I am facing this. In the below image, highlighted is the node where execution waits and makes LabVIEW hangs/crashes. Please answer the below Questions which helps me to understand the problem better: 1. In any case does VI Tester runs all the Test VIs Parallelly? 2. The DLL is set to run in UI Thread Could that be a problem? I have tried to change it to run in any thread but that didn't help. Please help me to understand this issue Thanks, Bhargavi Gowri.
  • Create New...

Important Information

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