Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 11/06/2010 in all areas

  1. 4 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
    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.
  3. 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.
  4. 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
  5. 2 points
    I do not know what I am doing wrong: I have an account on https://www.vipm.io/ where I can log in. I have VIPM installed and it was just recently automatically updated. I am able to install i2 JSON for 2018-64 I am not able to log in for "community" or "free" status. When I choose in the new window "Use existing JKI account" I get an error message, when using the account data for www.vipm.io. I also get an error when choosing "Sing up for a new JKI account". When pressing "Forgot your password?" an new tab in the browser opens where I can write my mail address and it tells me that an email was sent. However, I nether get the mail, nor is it gone to my spam folder. What can I do to solve this. I rely in my largest project on the OpenG lib and the MGI lib, which was not a problem to install in previous time. Best regards Wolfgang Kilian
  6. 2 points
    Hi, I am having an issue with functions palette I generate in VIPM. The palette is generated and behaves correctly in LabVIEW, however, when I click "show in palettes" in VIPM after installing toolkit, instead of my functions palette, Agilent 34401 palette is displayed. Any idea what might be wrong?
  7. 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.
  8. 2 points
    Got same error from time to time. Have to restart LabVIEW. LabVIEW 2019 32bit Windows 7 Pro.
  9. 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.
  10. 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 !!
  11. 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!
  12. 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).
  13. 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
  14. 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
  15. 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.
  16. 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
  17. 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:
  18. 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.
  19. 1 point
    And it works perfectly now, thanks!
  20. 1 point
    Hi Sam. VIPM 2020 works a little bit differently. It hangs around in memory for a little bit in case someone uses it again -- this way, it's much more responsive. Yet, it's changed the observed behavior around exactly when the package list refreshes. This is something we're working on and should be improved in the next release.
  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
    I was able to fix this by setting vip files to open with VIPM File Handler.exe by default.
  23. 1 point
    I can't get the Design Palette to launch using keyboard shortcuts. I know it used to work, so I'm not sure what's going on. Launching from the Tools menu does still work. I might try removing and reinstalling the Design Palette, but has anyone else run into this?
  24. 1 point
    Hi Thanks for creating Flat UI! My customer requested me to change the blue color of the combo box. They want it to be green instead so that it matches the rest of the UI. I have not been able to figure out how to do that. Is it possible? Thanks /Sebastian Bengtsson
  25. 1 point
    Hi Jim Thanks for the quick reply. Based on this information we decided to keep the current blue color. Again, thanks. Sebastian
  26. 1 point
  27. 1 point
    My welcome screen looks ugly. Why is the font way too large for the allocated space, see picture? (LV 2019, Windows 10)?
  28. 1 point
    Hello JKI Team & Community, I'm having trouble activating the JKI Design Palette, specifically requesting the activation code. Labview throws an Network Time Limit Error when submitting the mail adress (see attached image). The error is consistent within the corporate network (proxy/firewall) and on the unrestricted mobile hotspot. Using Windows 10, Labview 2015 (32bit) Looking forward to trying the new controls, Cheers
  29. 1 point
    Ah - yep, that worked! I usually try and keep my styles separate from the data types, rather than have my type defs styled a certain way, too. But I think for the convenience of not having to recreate my enum and still have it linked to the typedef then this is worth it. Thanks again Jim Edit: I opened my classic enum typdef, replaced it with the jki one, then to avoid replacing all instances of the type def with the JKI one, I went back to my front panel that I wanted to change, used the quick drop shortcut ctrl + p and selected my typedef. That replaced just the instances with the JKI enum, then I went back to my typedef and reverted it to the boring classic style.
  30. 1 point
    Story of my life when dealing with LabVIEW UI elements... Thanks for the explanation - I'll keep that in mind when placing buttons on my UI. I tend to put icon-only buttons in the horizontal mode for space saving, or I'll put the text underneath an icon similar to the ribbon in Microsoft Applications, or the left-bar in their newer applications (Teams). Combination of icon and text center aligned in a Laid Out Horizontally layout, and stacked vertically in the same space: Icons and Text all center aligned: Of course, this all heavily depends on how the user plans on interacting with the UI. In my case, the applications I'm working on a very document centric and have lots of configurations and menus, similar to Office applications. To keep the layout familiar to the user, I mimicked the Ribbon and File Menu ideas. Thanks for being so receptive to the feedback. I can tell just how much painstaking pixel pushing work went into these UI elements and am really loving the look and feel (and built-in color customization!) of the new controls.
  31. 1 point
    Yes, I meant Quick Drop, but couldn't remember its proper name. I'm using the latest version of JKI Design Palette. However, the problem disappeared. It seems that it disappeared after I first tried Ctrl+Alt+Space to pop up the Design Palette. After that Ctrl+Space correctly opens Quick Drop window.
  32. 1 point
    Yes, when the DP shows up as I open a project it is pinned. See attached video : I have a small project already open with the main.vi running Then open a DQMH project >> DP shows up pinned Untitled.mp4
  33. 1 point
    I suspected that but could not pinpoint which one could be causing the issue. I monitored the memory consumption to see if it is spiking during scrolling but it is not. I am not able to scroll all the way in neither classic nor Flat... And out of no where, i am sometimes getting the error below (even when the design palette is not open). I guess the palette continuously check for communication with the server in the background for some reason. Ali
  34. 1 point
    Never mind. It appears my JKI state machine was a older version after the upgrade I was able to access explorer option.
  35. 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.
  36. 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.
  37. 1 point
    Hi all, I have faced an issue with JKI VI Tester. Here are the details.. I am creating a DOM reference in "Setup.vi" and bundling it into my TestCase Object. DOM reference can be created by using "Load.vi" from XML Parser palette(attached image-> XML Parser palette and DOM Ref.png). When I unbundle it in the test VI, the DOM is reset to '0'. It is getting lost. We digged into the VI Tester and found out that some deprecated property nodes are used in "_JKI Toolkits\VI Tester\TestCase.llb\CallTestMethod.vi" in order to pass data from one VI (Setup VI) to another VI (Test VI).Refer to attached images -> VI Tester_Set Control.png, VI Tester_Get All.png. When the DOM reference is flattened it is getting lost, because LabVIEW doesn't know how to convert DOM reference into flattened data type. We have done a quick internal fix by replacing the property nodes and using variant to data after getting the control value. These changes are shown in "VI Tester_Set Changed.png" and "VI Tester_Get_Changed.png". Also, in "_JKI Toolkits\VI Tester\TestCase.llb\WaitOnTestComplete.vi", we have replaced the property node when parent data is written to child class indicator. This change is shown in "WaitOnTestComplete.png". I am getting my DOM reference in test VI correctly after doing this change. As I said this is a quick fix done for internal purpose. If this is the right change to make it work, can you please make this change and distribute the package so that my customers can also use it. If this is not the right change to be made, please suggest us how to fix this. Also, let me know if you can fix this issue and and release the fixed version. Please let me know if any other information is needed regarding this. Thanks, Bhargavi Gowri.
  38. 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.
  39. 1 point
    Yep, the new version works well. Many thanks!
  40. 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)
  41. 1 point
    The issue is because I renamed the event case to "Idle" from "" (empty string). Renaming the case name will resolve this issue.
  42. 1 point
    Hi Jim, THANK YOU! That link did help! Looks like all I needed was to install libXinerama.so.1 WHICH I thought I had already but not for 32 bit! Installed, as a result: Installed: libXinerama.i686 0:1.1.3-2.1.el7 nvidia-x11-drv-32bit.x86_64 0:384.111-1.el7.elrepo Dependency Installed: libX11.i686 0:1.6.5-1.el7 libXau.i686 0:1.0.8-2.1.el7 libXext.i686 0:1.3.3-3.el7 libxcb.i686 0:1.12-1.el7 Didn't require the 2015 run-time install since 2017 pro dev is installed. VIPM is happily doing its package cache download stuff as I am typing this! What a lovely sight!!!! Thank you again! Cheers, Brian
  43. 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
  44. 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
  45. 1 point
    I really like this template. It works great, is easy to use, easy to debug, keeps things well organized, etc, etc, etc. The one issue that I have with it is how it processes events. I do not like the event structure being inside the idle case. This one particular app I wrote runs test sequences consisting of multiple states back to back (essentially a macro). If the user presses the ESC key, they can interrupt the test sequence and skip to the end. To implement this, I had to poll the IDLE case in every one of the states of the test sequence to see if this event had happened. I didn't like doing that so I removed it and I thought I would share how I did it. I like this method much better because it will process the events as they happen but can also, in a way, prioritize the events. So obviously, I had to pull out the event structure and place it in its own process loop. You'll notice the UI Event queue for passing states to the state machine. Next, I create a VI that reads from the queue, with a very small timeout, and adds the event state to the front of the JKI state queue. This VI goes in front of the Parse State Queue VI so that the event is added to the font of the state queue. And within the state machine, I added a UI: Process Event state that accepts two arguments: first is the control and the second is the value associated with the control action. This works for my application but may need to be changed for other needs. Within the state, I can now determine whether to process the event immediately (as in the case of the ESC button scenario that I mentioned above) or I can choose to add another state to the end of the queue to be processed after the current queue is empty. I think this method keeps the UI responsive and doesn't require the additional requests to the IDLE states scattered throughout your program. I would definitely suggest enabling and disabling controls to only allow events to happen that make sense at that point in time. This would prevent a flood of events being added to the front of the queue if the user decides to go on a clicking spree.
  46. 1 point
    I've been tasked with trying to build packages on MacOS, but so far I have not been able to successfully build anything. The builds complete without error, but when I try to open the packages I just built they do not contain any files. I'm running MacOS High Sierra which is not explicitly supported by any version of LabVIEW at the moment, but I'm using LabVIEW 2016. Has anyone successfully built packages on High Sierra?
  47. 1 point
    Yes I can see the JKI packages. I noticed there appears to now be a "MacOS JKI VI Tester" package
  48. 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
  49. 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
  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.