Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 11/06/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 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
  3. 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.
  4. 2 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.
  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
    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
  17. 1 point
    I always defaulted to using the renaming, and only turned it off in rare cases when renaming broke things. So for me on those rare occasions where I didn't rename, things did work fine. I've been pretty mindful of cross linking and avoiding it between source and install. Given that the only major reason to use rename is to avoid cross-linking I'm going to try to undertake a change to have everything non-renamed. I want to be consistent one way or the other and it seems there are cases when renaming breaks things, but I'm unaware of any case when not renaming breaks things (other than cross linking which can be avoided). My major development woes with this is going to be having a VI that used to call something like: <user.lib>\_Hooovahh\<Package>\Name_hooovahh.vi is now going to have to be updated to point to the Name.vi instead. I have some scripting code to help with this which can return the expected missing VI path, but this doesn't seem to work for VIMs. I already posted over on NI's forums here. Until I get a solution it will be lots of manually fixing VIs and rebuilding...then fixing all the active projects.
  18. 1 point
    I try to use the toolkit when it does not crash 😉 and enjoy it a lot, but I've just found that there is no buttons with icons for such often used actions as Read, Write, Send, Receive. Also, there could be more "specialized", like Query, Execute, Init, DeInit, etc. Are there plans to expand the toolkit, or there is some specific reasons why those (at least more common Read/Write, etc.) are not implemented in the toolkit? Thanks a lot, Sincerely, Ivan.
  19. 1 point
    This is covered in part in various places but I thought it might be useful to have it in one. I've got VIPM running on CentOS 8 but you have to jump through some hoops due to 64 bit, wayland and rpm signing! 1. Install support for the 32 bit RTE on 64 bit by installing the following packages: glibc.i686 libstdc++.i686 libXinerama.i686 libGL.so.1 2. To install the run time engine - you need to remove the digest checks since these have got more strict. In the run time engine folder edit INSTALL so the line that starts RPMOPT includes --nodigest at the end of the string. 3. Now follow the standard install instructions. 4. Before running VIPM run the command "xhost si:localuser:root" to allow the root user to launch a window process. I believe this is due to wayland. Hope that helps someone!
  20. 1 point
    I ran across a problem in a project where, after creating and initializing the class under test in the setUp VI, unbundling it in the test VI returns a default object rather than the one I instantiated. setUp.vi testCount.vi I've attached a project with the class under test (ListImp) and two test cases. Both test cases have (as near as I can tell) identical setUp code and identical code in the test method (testCount). However, one test passes while the other test fails. Any idea what's causing this? [Edit - The about box reports "version 3.0.1.294 (Feb 11 2019)".] [Edit 2 - Another piece of potentially relevant information is the Test_ListImp..._2 test class was brought forward from an older version of VI Tester. I don't know what version, but according to my repository it was sometime before Feb. 2013. The other test class (the one that passed) was created with the current version of VI Tester.] VI Tester Error.zip
  21. 1 point
    I'm in no rush to move project to NXG, but I am curious, I saw on GitHub that JKI is has worked on a JKI State Machine for NXG and I was wondering if there was any similar project for EasyXML. I'm assuming the transition of this toolkit is not going to be a huge problem, am I right? I'm also assuming some NXG early birds have already tried the transition of EasyXML, anyone?
  22. 1 point
    I have a library with some VIMs and regular VIs. On the Display information Screen in the package builder I have Edit All VI Descriptions checked. My regular VIs get the copyright notice added, no problem. The VIMs don't. I am using VIPM PRO 2019.0.0.0. Checked for an update. It says I have the latest. Source Code is in LV19.0f2 if that helps. I suspect the vim file extension may be causing the issue. I attached a simple reproduction. thanks for creating such a great product! Sam VIM Descr Issue.zip
  23. 1 point
    Hi Sam. Thanks for reporting this. Yes, I'm guessing you're right that it's an issue with the *.vim file extension. I'll have our team look into it.
  24. 1 point
    JKI Flat UI Controls 2.0.1 is now available with New Controls and Various Improvements (functional, cosmetic, and search)... This builds on the 2.0 release and all users are encouraged to upgrade. Release Notes New Controls - Text Only Button (“Blank” Button with no Icon -- just text) - File Open Button (120x40 button with File Icon and "Open" text) - File Path Control with folder icon for browse button (in addition to one with a plus “+” icon) - Borderless Cluster (with very small border/edge, which is nice for making arrays of items where extra visual space between elements is not desired) - System Cluster (uses a system recessed frame as cluster border) - System Array (uses a system recessed frame as the array border and a system numeric as the index display) - VISA Resource (looks similar to the existing Flat UI Controls 2.0 Combo Box) Functional Improvements - Mechanical actions of all buttons set to “Latch When Released” (since it tends to be the most commonly used) - String control is now resizable (Removed extra string controls) - Numeric control is now resizable (removed extra string controls) Cosmetic Improvements - Fixed text size and font of combo box control’s display and drop-down list - Improved drop shadows of buttons (it’s a little sharper looking now) - Set all label colors to be consistent across the theme (122,122,127) - Fixed inconsistencies in font size in various controls Search Improvements - Added some some tags to controls for improved search-ability - Added “Flat” tag to all Flat UI Controls - Added “button” tag to all buttons - Fixed typo on “Transparent Boolean” control Download and Installation: Option A - Download and install with VIPM Option B - Run the JKI Design Palette (Tools >> JKI Design Palette) and click the Updates button on the navbar.
  25. 1 point
    I hope for you that others which bought VIPM in 2018 see it the same like you. I bet they don't!!!! 🤣😆 I bet NI is also not amused, if people stay with LV2018 for ever. But hey! I don't care anymore, i found a work around.
  26. 1 point
    Well, that is not good!!!😠 In this case, a free update for those who paid for VIPM PRO would only be fair!!!
  27. 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
  28. 1 point
    Hi guys, @Christoph, you can press Ctrl+R to re-initialize the Palette. That will exit the interactive and color modes. I just noticed another bug using these easter eggs (see video attached). Here is what I did: I first changed the colors of the controls (works well, very cool feature 😊) and then I "allowed interaction" to have a better idea of how these controls would behave on the front panel. After doing that, I selected the JKI Flat UI 2.0 theme inside the Palette and noticed the controls did change color, but I couldn't click on them. I then tried the same thing with my own controls (that I previously added to the Palette) and same problem, I couldn't click on them. In this case, they also wouldn't change color when I moved my mouse pointer over them. Best, Benoit JKI Design Palette.mp4
  29. 1 point
    Hi all, First, thank you JKI for your great tool that makes the design of my UIs so much easier! I successfully added my own themes and controls to the JKI Design Palette but I noticed some controls are not supported. Arrays and clusters with no elements: data structures like arrays and clusters require to have elements to be added to the Palette. Adding arrays or clusters that don't have elements make all the controls in the JKI Design Palette disappear as shown below. In the future, I think it would be great to be able to add our own arrays and clusters that don't have a type to the Palette. Decorations: decorations can't be added to the Palette. I tried to add my own decorations to the Palette and it looks like they are not supported. It didn't make the other controls disappear like above but I think it would be a great improvement to have access to decorations (classic or our own) via the JKI Design Palette. Best, Benoit
  30. 1 point
    My welcome screen looks ugly. Why is the font way too large for the allocated space, see picture? (LV 2019, Windows 10)?
  31. 1 point
    You're really making me think harder now about my cons and wishlists! Thanks to you and the team for the continued refinement of the tool!
  32. 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.
  33. 1 point
    I think I might be able to share this specific utility I'm working on. It's a very small piece in the big picture of what I'm working on, and I use little utilities like this to try out new toolkits, modules, or LabVIEW components to see what might be worth bringing into our more mainstream code. In this case, the utility I'm working on is an accuracy specification management tool. I can probably post a few screenshots and thoughts on the UI development once I finish it up.
  34. 1 point
    So far it looks like issue is not existing anymore. Thanks
  35. 1 point
    Hi Helcio, Yes, this happened in 2018. Our official statement about this is included in the release notes: "In order to best support our customers and ensure LabVIEW compatibility, VIPM supports new versions of LabVIEW as they are released. There are many instances where older versions of VIPM do not work well with newer versions of LabVIEW, due to changes in where/how LabVIEW and its files get installed." JKI has to provide support for each new version of LabVIEW as it's released, so we needed to align our support and releases with LabVIEW.
  36. 1 point
    I had a separate QD plugin for this, but I can't find evidence that I ever shared it with the community. You've just given "ctrl+space ctrl+q" back to me. Thank you. However, mine puts it exactly eight pixels from the output tunnel and pre-wires an empty String constant... Another feature to add might be my JKI State Machine Follower. It activates the current Case Structure case while the VI is running. Maybe? You'll save me "ctrl+space ctrl+f"... Thanks for all your work on this, Jim
  37. 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)
  38. 1 point
  39. 1 point
    Hello. I am trying to make a measurement program. Since this measurement takes a long time, it is necessary to be interrupted by the user's operation so that it can return to the measurement standby state. Is there a smarter way than inserting lots of checking the local variable of the break button during the measurement sequence?
  40. 1 point
  41. 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.
  42. 1 point
    Hello, I am having trouble loading tests. When VI tester starts it doesn't find my tests. I can manually load 1 test by File/Open File or test class. I can't load multiple tests. I have my classes in folders. Do the test classes need to be in the top level of my project? I have them in a auto populating folder called "Unit tests? Thanks Dan
  43. 1 point
    Yep, the new version works well. Many thanks!
  44. 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
  45. 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
  46. 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
  47. 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..
  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
    Yes, were in the process of making some design decisions -- I'm also in Roma for the CLA Summit and am presenting tomorrow... One thing that we're evaluating is the impact of changing the process VI to be Dynamic Dispatch (with the ability to call or override the parent). This changes slightly the mechanics of process registration and synchronization. Additionally, we're working on a full scripting API to allow programmatic creating, editing, and inspection of JKI SMO classes. This aims to enable creating user interface tools that simplify development. We've been doing this experimental development outside of GitHub to avoid a lot of noise. I'd be happy to loop you into what we're working toward and some of the open design questions.
  50. 1 point
    It would be nice if we could re-install a specific package. I had some crosslinking between 8.6 and 8.5 (my fault) so I wanted to revert a package. This couldn't be done, so I had to install an older version of the package and sequentially install the newest version. Ton
×
×
  • Create New...

Important Information

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