Jump to content


Popular Content

Showing content with the highest reputation since 12/16/2010 in all areas

  1. 3 points
    It would also be nice to have the shell menu option "Add to VIPM Library." on *.vip files and not only on *.vipc files. This way *.vip files can be added to the VIPM library from the windows explorer without having to install them.
  2. 3 points
    I'd love to see these three License-related improvements to VIPM: 1) First, a main window column showing the package license, so it becomes very easy to see whether a package is open source, freeware, proprietary/custom, or something else. It'd be nice if the column title could be clicked to sort sort packages by license type: 2) To complement this, a change to the filter box with options to filter by license type, or maybe a second filtering box for this specific purpose. This would further help those searching for packages to focus on finding one they can afford and actually use for new open source projects, which is particularly relevant now that LabVIEW Community Edition is going to bring in lots of new users who definitely aren't going to purchase proprietary add-ons: 3) Finally, it be interesting for the VIPM Community Edition, specifically, to only allow the creation of open source packages, what would create a clear barrier to those who might be thinking of using VIPM Community Edition for proprietary package creation. This could be done by changing the "License Agreement Name" (in VIMP Community Edition only) from a free form text field to a combo box listing only OSI-Approved licenses' SPDX codes, therefore making the intended purpose extremely clear. The default option could be BSD, with other popular OSI-Approved licenses listed below it, and less common ones (if requested) on a submenu: What do you think? 😊 PS: Re-posted with changes from the original in the VIPM 2020 Beta board.
  3. 3 points
    I have installed LABVIEW 2019, and I followed the procedures to make sure VIPM can communicate with VIPM 2018.0.0f2: https://support.jki.net/hc/en-us/articles/214135683-Resolving-issues-with-VIPM-connecting-to-LabVIEW But, still I do not see LABVIEW 2019 listed within the VIPM window: Any clue on how o solve this? Thanks
  4. 2 points
    In any validation setting, the tolerances around measured and reported values is critical, and so is tracking the tolerances for any given parameter being measured, with any measurement device or sensor. To automate the calculation of these ranges and limits within our overall application, we must track the specifications of any of these parameters. This used to be done using a peer reviewed excel table, and was loaded into LabVIEW using the Report Generation Toolkit. This had several drawbacks, but that's not the point of this post. The point is that using Excel means that any text becomes free text and if data isn't entered correctly then it can cause issues with parsing. So I created something I call the Specification Manager. It's a small utility that is intended to only be used by validation test case developers to add new specifications to the database of available specifications that can be tested, or to add new hardware for use in the validation tool. I built this tool in about 2-3 days as a way of trying out the JKI Flat UI 2.0 and the Design Palette. Here's the home screen of the tool: Some things that I think make this a nice UI: Dark background (76, 76, 76) and a nice pop of vibrant color, the icon for the tool uses the same two colors to provide consistency All native windows elements are hidden as this tool is very small and simple, there's no need for a toolbar, etc. Our company uses Century Gothic as a common font in many places, so I used that for some of my UI elements (title bar, specifically) System Chiselled Line separating workflow components of the tool. That horizontal line doesn't look like much, but it's a visual separation of the two things you're supposed to do with this tool. 1) select a file path, 2) manipulate the individual .spec files Listbox to store data - I hate working with listboxes, but I think they are the best UI element for storing continuous data. They look way better than any array I've seen when the data is simple. To add a new specification to the library, you press 'add' and get a dialog window that's a sort of wizard: I used the JKI built-in buttons here to give some sort of icon to the various specifications that can be created. I also changed the color scheme of this wizard to 'light' to signal to the user that this is a dialog/configuration type window and not really part of the core functionality of the utility. If this were a project for a wider audience, I would have customized them a bit more, but as-is, I think it's okay. The symbols are kind of meaningless as the library isn't as vast as I'd like it to be. After selecting the type of specification, you enter the name of it: This screen continues to use consistent fonts, and buttons from the previous screen. Pressing 'Continue' gets you to the heart of what this application is intended to do, modify specifications. (*I typed in random data, please don't double check these against the actual specifications of the 6218 - I will not be using this data in production) I used an array of customized clusters containing the JKI Flat UI 2.0 numerics and enums, then used some more of their pre-built buttons at the bottom for continued navigation. I used the same pop of color on the cancel button, mostly for fun, but also as a way of drawing immediate contrast between the other two operations that the buttons provide. That's about it! This is an internal-only tool, but I think that editing specifications using this small purpose-built utility will be easier than us using Excel to do the same thing. Overall impressions of the Flat UI 2.0 library: Pros: good selection of commonly used buttons and controls, consistent theme across numerics, strings, enums, file paths, and buttons - makes a consistent UI easy to build Color customization of buttons is easy, including customization of the hover-state (which I did to the 'X' button on the home screen of the utility) Wishlist: As with any library of icons and UI elements - a wider selection. I had a hard time finding icons for my 'Add Specification' wizard screen and had to reach pretty far Design palette only launches when using the left ctrl+shift buttons, it'd be nice for it to work with either left or right Cons: Working with the String controls and indicators was a little strange. There are actually two resizable elements in a single control, one for the frame/background and one for the actual text field. I had to be careful when resizing the control to make sure that both fields were resized correctly. Also the front panel snapping meant that the border around the text area was easy to lose if the text field itself was resized incorrectly. I will probably continue to use the UI library for the internal only developer tools, but for the main applications that I'm working on there is still heavy customization specific to my company that I will continue to have to do. Thanks for reading - feel free to ask any questions about the design choices or other elements of the UI for this tool.
  5. 2 points
    Got same error from time to time. Have to restart LabVIEW. LabVIEW 2019 32bit Windows 7 Pro.
  6. 2 points
    This may be due to the Wayland X server. If you are using Wayland, try switching to the Xorg X server and see if the command works.
  7. 2 points
    For the fact that one could use a 3rd party additional software for $ 499 only one year meaningfully is pure rip-off. JKI, never again !!
  8. 2 points
    In version 1.0.3 we've added System Arrays to the "System" theme of the JKI Design Palette. There are two different System Arrays arrays. 1) There's one with a "System Spin Control" for the Index Display (with increment and decrement buttons), which is nice because it's similar to the other array controls (Classic, etc.) 2) There's another one with a "System Numeric" for the Index Display (without increment and decrement buttons), which is nice because sometimes you don't want/need the increment and decrement buttons. These are really useful for creating nice System themed UIs with controls like the ones shown below. Have fun!
  9. 2 points
    Nice. The empty clusters and arrays now work without issues! Here is a suggestion for the existing clusters/arrays that contain a delete me button (in case you need to keep it after the latest upgrade): why not make the text hidden and the color transparent so it won't even appear (since it is going to be deleted anyway) And for the decorations, I suggest that you put the decoration on top of an transparent empty cluster that will get deleted after being placed on the FP (in a similar approach to the above).
  10. 2 points
    Yeah I was able to replicate the issues that you described. Creating and empty array/cluster caused all the controls to disappear on the palette. That is why the existing clusters in the palette contains a dummy "Delete Me" control :). You can do the same with a decoration to add it to the palette: AA
  11. 2 points
    Show Labels of All Controls in the JKI SDP (Ctrl+L) You can show or hide the labels of all the controls in the JKI SDP by pressing Ctrl+L. Press Ctrl+L to show labels on all the controls: Press Ctrl+L again to hide the labels
  12. 2 points
    Ideas and Features: Add other commonly used controls that aren't supported Clusters, arrays, subpanels, decorations, etc. Add more advanced controls Animated Menu Toggled controls (such as one button that does start + stop function) Custom Radio Selectors (paging/tabbing) Draggable Navbar UI templates Merge VIs Other commonly used modern UI building blocks Let us know if you have any others! Post an Idea or Feature Request Now.
  13. 2 points
    Hello Jim, It used to be that older versions of VIPM could connect to the newest versions of LABVIEW. Is there any particular reason why this changed? This issue seems to have happened from the VIPM 2018 Version because it was a major update. Is this going to happen for all versions of VIPMs in the future? The problem is that I have a licence for VIPM 2018, and now I can't use VIPM 2018 with LABVIEW 2019 (I won't be able to generate VIPC files without the licence). thanks Helcio
  14. 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:
  15. 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.
  16. 1 point
    I wanted to try JKI Flat UI Control 2.0 with LabVIEW 2020 Community Edition. However, the installation of JKI Design Palette always fails as it seems not supporting LV2020 (at least LabVIEW version 2020 is not listed). Any ideas?
  17. 1 point
    Curious if there is any plan to ad LV2020 support?
  18. 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.
  19. 1 point
    Hey Ruslan, Thanks - I was able to take that dialog window out of my project pretty easily. Not sure what version of LabVIEW you're using, so I saved it back for 2013 just in case. The one dialog window is effectively two clusters stacked on top of each other. First I make the selection cluster visible, then when a user selects which option they want, I hide that cluster and the Name and Apply buttons are visible beneath it. Happy to answer any questions you've got on it. -Nate Add New Specification.vi
  20. 1 point
    In terms of design, it looks quite harmonious
  21. 1 point
    Yes, I use the in-line execution mode on all the "constant" VIs that I generate as well. I tried out a quick POC performance test... There doesn't seem to be any real difference when using constants. I also tried the same LUT VI with the in-line execution switched off... that does make a HUGE difference. The in-line version is ~11x faster than the same VI with it turned off, and the VI that only contains a constant gets hit just as hard. Call overhead on such a tiny operation = ouch. I'm thinking the improved maintainability makes the LUT concept a winner. Thanks so much for the suggestion... now to rework my code conversion scripts and delete a lot of VIs I don't need anymore. 😅
  22. 1 point
    @Voklaif We dug into it and it turns out to be a LabVIEW bug. The solution is for the user (you) put a To Variant function before the call to Flatten to JSON String, since the bug seems to be inside the coercion dot (and the To Variant function doesn't seem to have that problem). Note: here's the bug (and fix) reduced to a very simple example (example VI also attached for anyone who wants to play with it)... Coerce to Variant Fail (LV2019).vi
  23. 1 point
    It would be interesting and useful for developers as well as users to see some statistics on downloads of packages. This way users can judge how actively certain packages are used. These statistics could include total downloads, downloads last month/year, etc.
  24. 1 point
    I've reproduced the issue and it should be fixed in VIPM 2020.
  25. 1 point
    All- Here is the link to the NI forum concerning this thread. At this time, I have been successful in launching VIPM in openSUSE Leap 15.1. Respectfully, David Johnson
  26. 1 point
    Reading the above thread, does this mean that the Linux VIPM 2017 will only work on LabVIEW 2017 and not 2018 or 2019? If so, when does JKI anticipate a release of VIPM for Linux that supports newer versions of LabVIEW? Respectfully, David
  27. 1 point
    Hello, I am trying to determine if this would be suitable for Continuous Integration, i.e. run Test suites after each commit. Ideally Jenkins would call the executable which calls the JUnit plugin (https://github.com/JKISoftware/JKI-VI-Tester-JUnit-XML-Test-Results) After testing Jenkins could evaluate the output file generated by the exe. I can create a Test Case and can use the JUnit plugin to load it and generate a report. However if I try to replicate this in an executable I get error 1448 even though the library is not broken. I tried including my Test case into a PPL but there was no difference. More compactly my question is as follows: Is it possible to integrate this with Jenkins and run a set of tests for each commit automatically?
  28. 1 point
    Hello! Is it possible to download a file jki flat ui controls 2.0.1 with the vip extension somewhere?
  29. 1 point
    I am having similar issue. I cannot activate design palette offline. I used both my gmail and hotmail, but I received nothing for days. Checked all the mail folders in both mail addresses, but nothing happens. I receive JKI update mails by the way.
  30. 1 point
  31. 1 point
    Thank you very much for that super fast reply and supported download link!!!!!! I will keep an eye on that release. Now I am happy again 😁😍!!!!!! Cheers Gregor
  32. 1 point
    Looks like the newest version fixed it. Thanks!
  33. 1 point
    That's to protect privacy... But seriously, thanks for letting us know. Font sizings can get a little wonky in LabVIEW. We'll see if we can fix this.
  34. 1 point
    Right-clicking on the button also doesn't provide the menu option 'Browse Options.' You have to right-click in the path area itself to select that.
  35. 1 point
  36. 1 point
    A mouse over hover effect has become standard in most major software UIs. This effect allows users to interact with controls in a more intuitive way and gives users confidence that they are making the selection that they intend. However there is a long standing NI bug that renders the hover effect inconsistent (see the discussion here: https://forums.ni.com/t5/LabVIEW/Button-Boolean-mouse-hover-not-working-on-64-Bit-LabVIEW/m-p/3944252#M1121887) Until NI makes a fix one 'solution' that I will employ is to disable the hover effect with the controls that I am using so that users do not get confused by a control stuck in a hover state.
  37. 1 point
    I used the previous "light" themed Flat UI Controls in my application and was excited about the update. There is no "light" theme in Flat UI 2.0 (or I'm missing something)? Regards Christoph
  38. 1 point
    First of all: Thanks for another great LabVIEW tool - highly appreciated! It seems that the ports you are using to activate the design palette and/or download the content is blocked by our corporate network. Using my private internet I could activate it properly, but back again in the company network I get an error message again when I am starting the palette the first time. Would it be possible for you to use other, usually open ports? Or at least let us know which ports need to be opened?! Is there any plan when we can expect the palette for the 64 bit version of LabVIEW? Thanks, Ingo
  39. 1 point
    DP.mp4 it also shows up at unexpected moments, e.g when doing a save all from the lvproj window see video
  40. 1 point
    Can i Link this case structure viewer to my existing case structure. i already created one VI using Enum based state machine.Now i want to convert it to JKI state machine.is there any possibility to convert with minimum changes instead of re-implementing.
  41. 1 point
    Hi JKI team, Firstly I want to thank you for generating the REST toolkit for LabVIEW, it seems pretty easy to connect the IoT cloud. I do, have some glitches when using it. I came across to this youtube demo ( Are you able to make an example to show how to use the tool? If that takes a while, would you please comment on 1. What's the input of Base URL? I used "api.favoriot.com" in my case. 2. Do you define the apiKey in one of the Default Headers? I did this but didn't seem to get anywhere. Your help is appreciated.
  42. 1 point
  43. 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.
  44. 1 point
  45. 1 point
    Yep, the new version works well. Many thanks!
  46. 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- 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
  47. 1 point
    On my MacOS machine, VIPM can't find JKI VI Tester and all of the weblinks are vipm:// links and don't seem to work on MacOS. Is there a plan old download link for vi tester .vip file?
  48. 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?
  49. 1 point
    Confirmed this error on LabVIEW 2017 (no SP1 yet), and VIPM 2017.0.0f1. I'll try it on LabVIEW 2017 SP1 in a few days.
  50. 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!
  • Create New...

Important Information

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