Jump to content

Leaderboard

Popular Content

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

  1. 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.
    6 points
  2. 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.
    4 points
  3. 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 points
  4. 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.
    3 points
  5. 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 points
  6. Found a solution : https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019Ru8SAE&l=fr-FR Luckily, my colleague has the same laptop with similar NI softs installed so he sent me his tdtable.tdr file and then it all works fine again.
    2 points
  7. User Stories: As a user of VI Package Manager on a system that is not connected to the internet, I want to output a list of dependencies for a package so I can go download them. As a developer I would like to get a list of packages and dependencies to add to my software's documentation.
    2 points
  8. As an update, I have been applying the file directly to the unicodeStringtoASCIIJKI_Simple_Localization.vi. Arabic gets translated to ASCII correctly as shown in the screenshots. Maybe a kernel32.dll function needs to be updated. Hopefully I find something and I will post it on this thread.
    2 points
  9. With VIPM 2020.3 (build 2540) and VIPM API 2020.0.2.73, it's not possible to supply a major number of 0 via the API, the API returns an error 42: Seeing as we also build projects that are in a pre-v1.0 state, I don't see a reason to not allow the major build number to be 0. I was actually tempted to file a bug report... 😉
    2 points
  10. Release notes are written in the build specification. When, for example, developer realizes that some note should be added - package has to be rebuilt. But sometimes build of the package could take a lot of time (for example, build of our DBT toolkit takes approx. 1 hour with licensing, password protecting and further build). It would be great if there will be option to update just release notes, or another information which should not be compiled (authors list, etc.). That would help to save some time... But on the other side, developer should pay some more attention to build configuration before actually building the toolkit...
    2 points
  11. Currently at our company we are building internal toolkits which we use for projects, but do not put it to LVTN. Toolkits are published via OneDrive, everyone has mapped same local folder as repository in VI Package Manager. Different toolkits are handled by different developers. And sometimes there is a situation, when new version of toolkit is built, installed locally and tested, but it is not published to our local repository. It would be nice (I understand that on the other hand it is not such a common case) to have it in such a way, that: - developer installs new version of the toolkit; - VIPM detects that actually such a toolkit (based on name and version) has been previously installed from a locally configured (custom) repository; - if so, VIPM checks that this toolkit has not yet been published to that local repository; - it will display some icon similar to those which are in "VIPM Legend" list. In that case, developer would see that he has some toolkit which is not published - so either he will publish it, or leave it as it is. Also there could be warning similar to the one which is shown when VIPM is opened, and there are updates for the toolkit. And, when toolkit is published - icon is set as usually.
    2 points
  12. I think I see what you're saying -- if an older version of the package is published in a repository, but the installed/latest (i.e. displayed) version is not published, it would be helpful to know that it's a development version that's not yet "officially" published to the repo. This is different, perhaps, than a package where no versions are published. Idea: Maybe VIPM should display "Local" as the Repository name if no versions of the package are published. This deserves some more thought, for sure. I'm glad you have a workable solution, for now. Thanks for sharing these ideas. P.S. Yes, there have been some dragon signings lately
    2 points
  13. Just the idea - not sure whether it is possible to implement. There are some packages, which are used as dependencies in other packages. And, we can find dependencies of the packages by sending package to configuration; but we can not find packages which are dependent on some particular packages. If we could do something like right click on the package in the list -> Find dependent packages, and it would show us list of packages (ideally even not installed) which use that package as dependency, that could be sometimes useful. Now, for example, we use some package as dependency, and I was wondering whether there are some other toolkits which use it as dependency. But, there is no way to find it out - unless to check information for each of the package or trying to install them. Thank you very much, Sincerely, Ivan.
    2 points
  14. Hi, I would like to ask for a help with the following issue: I am trying to distribute VIP file with some dependencies, which are not published on VIPM. Hence, I added them to VIPC and would like to distribute this VIPC with VIP file. Is this somehow possible?
    2 points
  15. Howdy V, I have not previously done exactly what you are asking, but have done some similar tasks. We use VIPM Pro and a local repository to distribute packages not found in the public repositories; not only our internally developed packages. First, using VI Package Builder's Destinations and Source File Settings pages you can easily include the file and specify where it is installed. Second, using the Custom Actions you can specify a VI to run Before or After the package install. Use the Generate VI button to create a template VI and save into your package project; I create a Custom Actions folder when needed. Edit this template VI to launch your package configuration file; I typically rename so I know its purpose without viewing. You can use the System Exec.vi and create a constant for the command line that will include the exact install path to the .vipc file location. And, if you're not comfortable with command lines, using Open a Document on Disk.vi is another option. I'm uncertain of whether VIPM will have any issues launching a package configuration before or after a package install. However, testing this will be simple and you can include instructions for the end-users if the automation is unsuccessful. NOTE: My suggestions are based upon a Windows OS install and will need modifications for MAC or Linux Best wishes with finding a solution. James
    2 points
  16. 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
    2 points
  17. 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?
    2 points
  18. 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.
    2 points
  19. Got same error from time to time. Have to restart LabVIEW. LabVIEW 2019 32bit Windows 7 Pro.
    2 points
  20. 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.
    2 points
  21. 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 !!
    2 points
  22. 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!
    2 points
  23. 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).
    2 points
  24. 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
    2 points
  25. 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
    2 points
  26. 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.
    2 points
  27. 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
    2 points
  28. 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 points
  29. 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.
    2 points
  30. VIPM 2020.3 (build 2540) I'm getting a bizarre error. I get a build failure where VIPM claims that the following source library is missing C:\Common\Generator Interface\Message Interfaces\Gen11 Message Interface\Gen11 Message Interface\Gen11 Message Interface.lvlib When the library actually is located here. C:\Common\Generator Interface\Message Interfaces\Gen11 Message Interface\Gen11 Message Interface.lvlib This library is a collection is actor message interface classes if that makes a difference. I'm also been able to do a mass compile of the entire directory without any errors. This might not be related, or a quirk of the builder that I don't know about: The other weird thing is if I open the project while VIPM is in the failed state, the error list contains a bunch of failed VIs that couldn't find a .NET library located within my project. (This project is pretty big and contains some proprietary information so I can't upload it. Sorry, that makes it hard to troubleshoot.)
    1 point
  31. This is the event log I get when I try to open VIPM file handler: Log Name: Application Source: Application Hang Date: 4/16/2021 11:22:05 AM Event ID: 1002 Task Category: (101) Level: Error Keywords: Classic User: N/A Computer: Description: The program VIPM File Handler.exe version 2020.3.0.2540 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: 1664 Start Time: 01d732d32dab9048 Termination Time: 4294967295 Application Path: C:\Program Files (x86)\JKI\VI Package Manager\support\VIPM File Handler.exe Report Id: dbea6963-a249-4035-8a67-b3b236e62947 Faulting package full name: Faulting package-relative application ID: Hang type: Top level window is idle Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Hang" /> <EventID Qualifiers="0">1002</EventID> <Level>2</Level> <Task>101</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2021-04-16T15:22:05.172829700Z" /> <EventRecordID>16829</EventRecordID> <Channel>Application</Channel> <Computer> <Security /> </System> <EventData> <Data>VIPM File Handler.exe</Data> <Data>2020.3.0.2540</Data> <Data>1664</Data> <Data>01d732d32dab9048</Data> <Data>4294967295</Data> <Data>C:\Program Files (x86)\JKI\VI Package Manager\support\VIPM File Handler.exe</Data> <Data>dbea6963-a249-4035-8a67-b3b236e62947</Data> <Data> </Data> <Data> </Data> <Data>Top level window is idle</Data> <Binary>54006F00700020006C006500760065006C002000770069006E0064006F0077002000690073002000690064006C00650000000000</Binary> </EventData> </Event>
    1 point
  32. Hello @Sam Grayson and @Jim Kring, the IT departement tried to whitelist any folders but it didn't work finally. it was working few time if VIPM start before Cyberreason. Anyway IT solved the issue with puting my computer in a special group to only use antivirus of cyberreason. Now it works correctly. I try to get more information from IT departement and let you know when I have news.
    1 point
  33. I believe that is what I was looking for. https://github.com/JKISoftware/Caraya/issues/112 It is coming in 1.2
    1 point
  34. @Vollinger: Great question! First, I was going to suggest the possibility of distributing a VIPC file (instead of a package) that includes your package and all it's dependencies inside of it. You can then name this VIPC file to convey that it's your package+dependencies. However, this approach doesn't fully look like an installer for your package -- it appears like a multi-package installer to your users. However, it's a pretty clean approach that involves distributing only a single file. And, you can name this VIPC file to convey that it's the installer for your product. Another approach is to build the dependencies into the package file (if you remove the dependencies, then the package builder will pull in copies of those VIs and namespace them such that they are internalized inside the package). This makes your package file larger, since it now includes the dependencies and you also have to consider the licensing terms of your dependencies. @James@Work: That's a very clever idea to putt a VIPC file inside the package as a support file. I'd love to hear how this works in practice. Some considerations with this approach that come to mind: - Dependencies are typically installed by VIPM before the package that depends upon them, and the package's installed contents are only available after the package is installed. So, the VIPC would need to be invoked *after* the package is installed (in a post install custom action). - This approach makes the package file larger (since the package contains its dependencies). - Some consideration may be needed about whether to install the bundled packages, if newer versions are already installed or happen to be cached/available. - Deadlock issues may occur if a post-install tries to invoke the VIPM API to install packages, synchronously (since a package would try to install packages, which require VIPM to be idle, but it's not idle, because it's installing a package).
    1 point
  35. Hy, the large Settings button has a small visual bug. If the button is off it shows the gear as symbol, but if it is on in shows a black rectangle. Greets Martin
    1 point
  36. Hi Everyone @Mads Toppe, @szymsciupak, @wolfkil, This is a known issue that affects some people behind corporate firewalls. In VIPM 2020.1 (still in beta), you will be able to download packages without a sign-in and hopefully this will resolve the pain point. Thanks for your patience. -Jim
    1 point
  37. Alin, Thanks for the detailed description of the bug. It helped me to reproduce it. I have recorded this issue as Case 18752 for consideration. I can't promise when this will be fixed but we will inform you when that happens. Since JKI State Machine Editor is open source, you can post any issues in GitHub: https://github.com/JKISoftware/JKI-State-Machine-Editor/issues Take care and stay safe.
    1 point
  38. I don't see the way to "ignore dependency". Still looking through help.
    1 point
  39. I would mark this as an improvement since in the past it could sometimes take a while for VIPM to refresh everything. I am quite happy with the design palette at the moment, but if I think of anything I will let you know.
    1 point
  40. 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!
    1 point
  41. 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
    1 point
  42. Dear JKI community, let me, please, share the following - button "Boolean--Add-Plus-Transparent-Button-(flat).ctl" has label "Wrench" (although, there is real wrench in transparent buttons set). Thank you very much, Sincerely, kosist.
    1 point
  43. version 2.0.1.24 requires JDP version 1.0.4.93 but the latest available version is 1.0.4.92 See image :
    1 point
  44. 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.
    1 point
  45. Hi Jim Yes i am able to use the palette if not scrolling. It is not freezing after a period of time. Below are also some observations: The palette will freeze if I: Select "System theme" from the combo box (the classic and flat works fine) Maximize the palette The palette will NOT freeze if a I scroll with a limited number of controls shown (for example when filtering to show only boolean controls)
    1 point
  46. 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.
    1 point
  47. 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.
    1 point
  48. 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
    1 point
  49. 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?
    1 point
×
×
  • Create New...

Important Information

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