Jump to content


Popular Content

Showing content with the highest reputation since 04/25/2018 in all areas

  1. 1 point
    Is there a way to install all the packages into Labview 2018 that I already had in LV2017 (short of shift-clicking all the OpenG VI packages, then ctrl-clicking all the MGI packages and my favorite other goodies)? If it's part of VI Package Configurations, I might just upgrade.
  2. 1 point
    Sorry for my late answer, I am very bussy at work. Yes, I've tried. There a many placeholders. For examples: So, a lot of work to do. But OK. New technology (LV NXG), new philosophy, new tools... It is better to start the new project directly in NXG. But another problem in NXG 2.1. I have instaled JKI SM 2.0 and there is an option to start the new project with JKI SM. But... if I need to add JKI SM to new, empty VI I'm not able to do it. In new JKI SM project, there is also a lack of Close Reference in "Data: Cleanup" state. I am sorry for so many questions and comments, but I often use JKI SM and recommend it to my students as the next step with programming in LabVIEW (something more then a simple state machine). Regards
  3. 1 point
    There are a number of items that are not adequately covered in the documentation OR (in the case of the video) actually show you the wrong way to do things. This is not intentional on JKI's part but rather the result of improvements to the VI Tester which didn't get added to the pinned getting started stuff. Important things to be aware of (tested with LabVIEW 2014 32 bit): *) Don't copy the testExample.vit as per the video as you won't be able to see your tests EVER! The .vit is a template file and the VI Tester ignores all templates. You need to right click on the testExample.vit and select "New from template" and save your VI starting with the word test and ending with .vi (not.vit) eg. test-anything.vi Rob Calhoun also makes the following important points in this post Test Cases that do not have any test methods do not appear in VI Tester hierarchy. (Maybe this is a feature, but it's not what I would expect.) After creating and saving a new test method the Test Case still does not appear in the VI Tester hierarchy. This is because the Test Case (class) has not been saved, so it still has no test methods from the point of the VI Tester Only test methods that start with the word "test" (at least this appears to be case-insensitive) are considered test methods.

Important Information

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