Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 05/21/2015 in all areas

  1. 2 points
    Get the JKI State Machine Editor (just check VIPM for package updates) Version 2013.4.0.186 This new release adds a right-click option called "Find Data Accessors" to Bundle by Name and Unbundle by Name nodes in a JKI State Machine. Using this feature will open a dialog showing all the frames of the JKI State Machine that access the data, as shown below:
  2. 2 points
    I found one problem that occurs to me. "Find Data Accessors" is available in any VI (not only JKI State Machine) for the Unbudle by Name function, but its call does not cause the appropriate list to be displayed in the dialog box, although the application is started and consumes processor resources. Calling it several times on a notebook with an i5-4210M processor results in 100% CPU load. I've attached a screenshot for the FMSM example from LabVIEW example projects. As you can see, also Add Dynamic Events and JKI State Machine Editor... are visible - only when pop-up on Bundle/Unbundle by Name.
  3. 1 point
    @Jim C you may want to tell your coworkers to sit down when the hear about this new release... We've made another great round of improvements to the JKI State Machine Editor that we're excited to tell you about. Integrated Event Structure and Case Structure Viewer The biggest thing you'll notice is that we've integrated the Event Structure and Case Structure into a single tree view -- all of the Event Structure frames have been added under the "Idle" ("Event Structure") item at the top of the tree (as shown in the screenshot below). You can now easily navigate all the Event Structure frames and Case Structure frames from this single tree view. Drag & drop to reorder the Event frames -- it works just as you'd expect! Context Help Shows Documentation for Frames of the JKI SM If you show the Context Help window (<Ctrl+H> or Help >> Show Context Help) and then hover over a frame name in the JKI State Machine Explorer's tree view, the Context Help window will update to show the documentation string for that frame. Explore States Dialog Another cool feature we added is the ability to Explore States on a state string constant. Simply right-click on a state string constant and choose Explore States (as shown below). This will open a dialog (shown below) that looks a lot like your string constant, and allows you to click on individual lines/states of the string constant, which will navigate the JKI State Machine to that frame. This allows you to quickly jump between frames if you'd like to navigate through the sequence of states in the string constant. Grouped Right-click Options on States Finally, we added a small usability improvement where we now group all of the right-click options for a state, under a single submenu (as shown below) -- previously, these were all at the root level and started to get unwieldy. I hope you enjoy this latest round of improvements to the JKI State Machine Editor and it helps your write great code even faster.
  4. 1 point
    Never mind. It appears my JKI state machine was a older version after the upgrade I was able to access explorer option.
  5. 1 point
    I am using a class that I want to generate an xml to archive as final data. I can't just wire the class to the easy generate xml_jki Easy.vi. so I have to use a constant cluster and unbundle and rebundle. Is there an easier way to do this. Thanx Norm
  6. 1 point
    Hi, in our company we changed the Parse State Queue VI, so that we get the previous state in case we had an error. With this it was so much easier to debug the JKI-SM, because we were able to display the state, where the error occurred. Maybe this this an idea for the original Parse State Queue?? Here is an snippet based on the "old" Parse State Queue VI.
  7. 1 point
    Hello everyone, Fist of all thank you for your Tools that are very helpfull. I'm trying to use the HTTP JKI REST drivers with an HTTPS website but I need to go trough a Proxy. How is it possible to desribe the PROXY settings with this driver? Thank you by advance.
  8. 1 point
    Hi @Antoine Chalons. Yes, I can see how layers of nested array/cluster containers can be tricky 🙂 I'm glad you were able to figure it out, and get it working! Hope all is going well for you in general and on your LV projects.
  9. 1 point
    Open "Compare to Constant.xnode" with a text editor. Near the bottom, delete the two items "Untitled 4 (SubVI)" and "Untitled 5 (SubVI)" Then it will build.
  10. 1 point
    single step sounds good - and should work in both direction Last/Next Step dynamic state generation - maybe JSON imported State"Objects" (export fct would be nice 2)
  11. 1 point
  12. 1 point
  13. 1 point
    Hi @JimKring, I have moved to the approach of creating the DOM reference in setUp.vi of Test Suite. I will let you know if I face any problem. For now, Thanks, Bhargavi Gowri.
  14. 1 point
    Hi @JimKring I have attached the sample project, which demonstrates the issue that I am facing. I have also attached the image, which shows the DOM ref values in New.vi of test suite and setUp.vi of the test case. Please let me know if you need any details. Thanks, Bhargavi Gowri. Sample Code.zip
  15. 1 point
    @Robert Smith I know this is four years later and probably not very helpful, but I just used VI Tester for the first time and found that my tests would not appear in the UI if the test classes were in auto-populating folders. This may have been your problem. Hopefully this helps someone else who might come across this thread.
  16. 1 point
  17. 1 point
    Ruslan, I will suggest to leverage VIPM's capability. Refer this link: https://support.jki.net/hc/en-us/articles/214135803-How-do-I-transfer-packages-with-VIPM-to-a-non-networked-computer-
  18. 1 point
    It would be great if there is a preview window along with the description editor. Right now, after formatting the description with various tags (like bold/italics etc.,) I would need to build the package in order to see the formatting. If there is a preview pane along with the description, it would easy to see the final formatting. Thanks, Ajay.
  19. 1 point
    Yep, the new version works well. Many thanks!
  20. 1 point
    No, CPU usage is high all of the time. Yes, Mass Compile is enabled (always). I reinstalled JKI State Machine, but still nothing. So, I have to remember to close the Block Diagram first or JKI SM Editor (Explorer in fact...). Maybe it is important or not... my LabVIEW version is 2018 (18.0f2)
  21. 1 point
    The issue is because I renamed the event case to "Idle" from "" (empty string). Renaming the case name will resolve this issue.
  22. 1 point
    Hi, Please help... I am trying to create a .vip that will install my LabVIEW project as a LabVIEW project template (note: I have done this process a few time before with no issues) I have my project that I want to make into a template, everything works perfectly. I configure the .vipb, I build and install the .vip. I check the destination to see if my files have installed to the correct location, they have. Here's where the problem kicks in...... I open my LabVIEW project that has installed in the destination, and notice that the .png files in my project some are missing and some are saying missing. In my project I have .png files in various .lvlibs. The first .lvlib in the project has the .png's showing, however showing as missing and the expected location is saying C:\ which is incorrect, it should be in the location where my .lvlib is in the destination. The other .lvlib's don't even show the .pngs in the LabVIEW project explorer. Now checking on disk all the png's are there and in the correct location. In summary it looks as if as part of the vip install it is removing the link the .lvproj has to my .png files VI Package Manager Version : 2018.0.0f1 Jul 21 2018 LabVIEW Version : 2016 (32 bit) OS : Windows 10 Pro Version 1803 Any help is greatly appreciated Thanks in advance. Kev
  23. 1 point
    Jim, Here is a simple example. Note it appears that also text files (and perhaps any non-LV files) are affected. The .vipb file is from 2017. Sam Simple Example.zip
  24. 1 point
    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.
  25. 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
  26. 1 point
    Tell me where to download the latest version state machine
  27. 1 point
    I believe that you are referring to this article already to Transfer Packages to Non-Network Computer Here are the options Get VIPM on the network PC with help from IT folks OR Get temporary internet connection to the non-network PC OR Download in personal PC and then transfer to non-network PC
  28. 1 point
    Update from JKI: This issue is planned to been fixed in VIPM 2018. So I can successfully build packages with VIMs in them. But I found that if I need to make a package, that depends on a package, which contains a VIM, the build will fail. First install the hooovahh_array_vims-1.0.0.6 package. Then try to build the File IO package, which at the moment only contains one VI. If it is like my setup the build will fail with this error. If I remove the VIM dependency by replacing it with the OpenG one the build is successful. Build Fail VIM Dependency.zip
  29. 1 point
    Thank you for giving me hope and help! Kindest Regards, Brian
  30. 1 point
    Thanks, Jim. That's great news. I'm not sure whether it addresses Fab's concerns, but it does address mine. I'll let you know if I encounter any issues with VIPM 2017 for Linux. -Chris
  31. 1 point
    @Jim Kring Ahaaaa- in my case, that folder already existed from a previous install; and the jki.conf it contained was owned (755) by the previous user of my machine... I recursively gave myself permissions through the whole folder, which cured the error 8; however, VIPM would then launch, and die silently while still at the splash screen.. So I blow away the whole JKI folder, and everything went fine from a clean start ;-) -Thanks for your help! ~Tom
  32. 1 point
    The OpenG Array Library 4.1.1.14 is not listed in VIPM from the JKI Package Network. I even tried refreshing, but it did not find the required library. Other observations: 1. I am able to see an older version 4.1.0.13 of that library in VIPM 2. I checked the website and was able to find the latest version But I want to understand why my VIPM is not listing it
  33. 1 point
  34. 1 point
    Thanks team. I have achieved the authentication using .NET. But it is little slow. Let me try some other methods and post the updates..
  35. 1 point
    I tried installing the new VIPM2017 for Linux in a clean Fedora 27 virtual machine just to give it a try but I can't get it to do anything. I followed the two basic steps: 1) install LVRTE 2015SP1 which installs without any problems or errors 2) copy JKI folder to /usr/local as described in the instruction.txt When launching vipm I just get the blunt error: No such file or directory as shown below sudo ./vipm sudo: unable to execute ./vipm: No such file or directory What could be the problem and how could it be resolved?
  36. 1 point
  37. 1 point
    One of my colleagues almost fell down; he was so happy when I showed him this new feature. Excellent idea & implementation.
  38. 1 point
    I've looked into the LabVIEW based API for VIPM, and was wondering if there is an equivalent for MacOS? In general, is there anyway to automate applying vipc files on MacOS? I'm looking to use VIPM as dependency management for a large application that supports windows and mac and I'd like to make applying a vipc part of the automated build process. I understand that the current VIPM API vi package is not compatible with MacOS. But on a low level it seems to just call an executable with key-value pairs as command line arguments, so I'm hopeful that VIPM on Mac is capable of similar functionality.
  39. 1 point
    I installed VIPM (2014 because that's the latest build for Mac) on MacOS. It's showing plenty of packages such as ones from NI, MGI, etc... But oddly, no JKI packages. So I can't find VI tester in the list. Any idea what could be causing that?
  40. 1 point
    Thanks @Jim Kring for the quick response! Glad I wasn't crazy for thinking it could be done "in theory". My team is definitely in need of VIPM pro but in the near future we would need a way to automate applying vipc files during our build process. Using command line is actually great for our purposes.
  41. 1 point
    Yes I can see the JKI packages. I noticed there appears to now be a "MacOS JKI VI Tester" package
  42. 1 point
    It worked. Only issue is when opening the visual tester it looks for some stuff from registry.llb (or dll I can't remember) and I have to ignore it, but the tester ran fine after ignoring those files.
  43. 1 point
    I understand cleaning up references is generally a good thing, but is there a reason the JKI State Machine attempts to close the This VI reference of a VI that is in memory? This in my mind is basically a no-op and can be removed because the close can't remove the VI from memory since that is the VI that is running. Which brings me to question why we even get a copy of the This VI reference and put it in the shift register. If you have a property or invoke node set to the VI Server class "VI" then you can leave the reference unwired and it assumes "This VI", which is actually seen in the "Initialize Core Data" case. Is there a good reason to keep a copy of This VI in the cluster? And if so is there a good reason to have a Close Reference in cleanup?
  44. 1 point
    I have a colleague that is interested in learning LabVIEW and I want to get him started on the JKI SM (and SMOs) right out of the gate. Are there any ready-made presentations that demonstrate the common pitfalls facing a new developer, and how the JKI SM handles them? Thank you, Jim
  45. 1 point
    Perfect Jim, thanks. I'll try the workaround and keep an eye out for the fix. I'm not permitted to follow that link, is the workaround the same as Jens Gräwe suggests here?: https://support.jki.net/hc/en-us/community/posts/360000027103-Error-in-Deactivation-Infos-in-VIPM-Pro Cheers, Steen
  46. 1 point
    Hello JKI, I wanted to follow up on this issue as it seems that Deactivation still does not work when Binding a license in VIPM Pro. When a product uses this feature in VIPM, and a customer tries to deactivate, they are given an error "Unknown Error". This error is not given if a developer uses the "add-on Licensing Tool" inside LabVIEW and doesn't bind a license during build time. Here is how to reproduce the problem: Install TPLAT from VIPM: vipm://ni_lib_tplat License an LVLIB using TPLAT Standard Mode (Tools > Add-on Licensing Tool) Delete the licensed source code, but keep the .lf file that was created Create a VIPM build spec with the unlicensed lvlib Enable "Bind License to Library at Build Time" in "Licensing and Activation tab. Enable deactivation and use the credentials as described in your help document (http://jkisoft.com/vipm/docs/2014/index.html?turl=licensingactivation.htm) Build package Install Package on test machine Create a test license in SOLO server for the product Activate the product in LabVIEW with test license Deactivate the product in LabVIEW and receive an "UNKNOWN ERROR!" Has there been any investigation into this issue and is there any timeline for resolving it? Please let me know if you need any information from our side. Thanks for your help, David
  47. 1 point
    Note that if you do this you are committed to making sure that any sequence of “states” you call must be able to handle any possible external interruption at any point. In other words, you must be super vigilant against race conditions. With the “idle” method, one can choose where in a sequence of steps one will accept outside input. For example, if you had the macro: Take Data Analysis Data Save Analysis and also a “Set Parameter” event that changes a parameter used in Analysis and Save, then you have a race condition where the analysis may be saved with a different parameter value, if the “Set Parameter” happens between Analysis and Save.
  48. 1 point
    Hello, I've been trying to implement an application using the state machine template. Using Javier Ruiz's excellent webinar as a guide, I configured the template using a 9022 RT with a 9116 chassis. The FPGA code runs well but I get this message when executing the RT: Error 53 occurred at Property Node (arg 1) in RT Main.vi Possible reason(s): LabVIEW: Manager call not supported. I am using LV 2014sp1. I've tried this using the 9024 RT and a sbRIO9641 - both issue the same error. Any ideas as to my (obvious) incompetence? Thanks!
  49. 1 point
    Hello Javier, Ah yes, that solved my problem. You are a giant among LabVIEW developers! Thank you so much. Regards, Kurt
  50. 1 point
    In this example, we show how you can refactor existing code. We have taken the 3 button dialog that ships with the base version of LabVIEW and upgraded it to use the JKI State Machine template. We have not added or changed any functionality. Also, we have not changed the way the functionality is implemented. Here is a screenshot showing how the VI looked before the refactoring: Here is a screenshot showing how the VI looked after applying the JKI State Machine template: We've attached the the refactored VI that has been written in LabVIEW 8.2. Remember that you need to have the JKI State Machine package installed in your version of LabVIEW. Click here for information on how to install the JKI State Machine. Three_Button_Dialog_CORE___JKI.vi The original VI is located at: \Utility\error.llb\Three Button Dialog CORE.vi Click here to watch a video that describes some of the design thought process used in the re-factoring: Video: Refactoring the LabVIEW three button dialog
×
×
  • Create New...

Important Information

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