Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 10/30/2019 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. 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
  5. 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?
  6. 2 points
    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.
  7. 1 point
    I was trying to apply a vipc using the API and it tells me 20.0 isn't a valid LabVIEW version. Digging into I found this: see attached image. Maybe you guys were a little too optimistic about the switch to NXG and figured wed never see 20.0?
  8. 1 point
    In case when new (custom) destination's name starts the same as already existing one, then both destinations are treated as the same (not possible to edit name of custom destination, and when path is changed in one of them - it is reflected in another one). As the example, there is standard destination "Help Menu", then I've added "Help Menu Test" - both of them were treated as the same destinations. And then 3rd destination "Menu Test Help" was fine.
  9. 1 point
    Thanks Jim. That was exactly what I was looking for.
  10. 1 point
    Suppose you have an architecture where states calls sub states to do the details of the action then you have to queue to the front. Example of a motor stage with a break: Top level commands queued are 1) Move_To_Pos >> A 2) Move_To_Pos >> B where state Move_To_Pos (PosArg) issues the actual string of commands or states: Break >> Off Goto >> PosArg Break >> On The initial queue after 1), 2) are queued will be: (Front) Move_To_Pos >> A; Move_To_Pos >> B (tail) which if you use add to front of queue gets expanded to (Front) Break >> Off; Goto >> A; Break >> On; Move_To_Pos >> B (tail) and if using add to tail: (Front) Move_To_Pos >> B; Break >> Off; Goto >> A; Break >> On; (tail) And this gets replaced with (Front) Break >> Off; Goto >> B; Break >> On; Break >> Off; Goto >> A; Break >> On; (tail) As you see the sequence of positions will be B then A and not as the example presumes A then B So for the concept of subroutine-like states to work you have to add to front.
  11. 1 point
    Hi everyone, I'd like to change the description of the VIs contained in my package during the build process (to add BSD licence text). I created a pre build action and used the path array to add description to VI. It seems that the action vi is not called. What am I doing wrong ? Thank in advance for any help. Note: I'm using VIMP 2020 community edition
  12. 1 point
    Yes this 2020.1 version seems to circumvent the problem. With this experience I will try to stay at this version as long as I can...
  13. 1 point
    Hi Jim, That was the setting I knew that exists and didn't find last night (I was probably too tired 😇). Anyway, I gave it a try this morning without success. I got no error, but text wasn't appended to vi description. Any idea ?
  14. 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.
  15. 1 point
    Hi @Vollinger. The issue is that LabVIEW addresses items in the palette by their display name. So, if two items have the name "Connect.vi" then LabVIEW will show the first one it finds, even if it's for a different toolkit. The solution/work-around is to change the palette display name of your "Connect.vi" to something like "Connect (MyComponent)". Here's where you would change that name in the palettes, via the palette editor. Does that work for you?
  16. 1 point
    A recent conversation on LAVA: https://lavag.org/topic/21631-anybody-having-problems-with-vipm-2020-and-how-can-i-get-vipm-2019/?tab=comments#comment-132642 Suggest multiple LabVIEW developers are unhappy with the 2020 version of VIPM. I think you have been a bit aggressive in the number of changes, and you need to quickly get on top of some of the issues. You need a 2020.1 version soon.
  17. 1 point
    A little more info I found when playing around: I located .mnu file responsible for my palette in LabVIEW directory and deleted it. Now, as expected, show in palettes does not work. Also, my palette disappeared from LabVIEW funtions palette. When I restore .mnu file, palette is available once more, however, show in palettes displays Agilent 34401 palette after clicking again.
  18. 1 point
    Similar issue, im not able to activate this via email. I send out the email request and never receive an Activation code. Is there an alternate method of activation available? Fixed now, looks like my account was not setup to receive emails from JKI
  19. 1 point
    Please tell me when it is ready. I would be happy to be a tester. I only need to download the Arduino code?
  20. 1 point
    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
  21. 1 point
    Always forward, Jim I don't want to bring up the "increased performance" argument. I mean, we're using LabVIEW after all. Nobody who's using LabVIEW can seriously play the performance card. I regularly see VIPM using over 1GB of memory and sometimes crashing with an "out of memory" error - although that might be due to the ridiculous 4GB of total memory available on that machine. How long before that goes to 2GB, 3GB? We've had 64bit on windows for 15 years now. I think it's time to move on. At least give us the option. Surely VIPM isn't depending on modules that don't exist in 64bit land
  22. 1 point
    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.
  23. 1 point
    Hello, I have exactly the same problem. When trying to sign in or create new account, I get the message as in the screenshot attached.
  24. 1 point
    In installing the JKI Flat UI Controls with LabVIEW 2020 on Mac OS, the package claims requirement to install JKI Design Palette. However this Package is not listed as available on the Mac. Not sure if there is something fundamentally not allowed on the Mac OS or if it was an oversight in packaging the JKI Design Palette. Furthermore, VIPM reports that there is also a missing dependency on OpenG Port IO which is a very old package that has never been compatible with the Mac OS. And is not part of most windows machines that haven't had a "Printer Port" in years. However that is a dependency in the OpenG toolkit which I use despite that missing dependency. However it now blocks in stallion of the JKI Flat UI Controls. (Note I believe that this issue is also in earlier versions of LabVIEW (does not work in LV 2019) as well, I just decided to update my controls UI using a modern looking set with a change to 2020)
  25. 1 point
    I don't see the way to "ignore dependency". Still looking through help.
  26. 1 point
    Hi, This is not a problem report but more a success story. Well done crew! I heard about caraya when I looked through the talks of VI Week (and I'm still watching videos) and I wanted to give it a go. I've been wanting to try unit testing for a while but the built-in stuff just wasn't doing it for me. We (work) do all our building, releasing and deployment via Azure pipelines so when I heard that caraya can generate JUnit format test results, I jumped straight in and made myself a test pipeline for a new feature we just added to one of our libraries. I downloaded the TDD template, copied the Pre-Build-Action.vi into my project (it needed a bit of fixing) and defined some tests. Once I had the pre-build vi working I looked at the Azure part. I wanted the pipeline to be aware of the test results. All I had to do is to call the Publish Test Results task which takes the results and publishes them to the Azure test repository and bang! Unit testing done. Here are some screenshots And then I added a broken test
  27. 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?
  28. 1 point
    And it works perfectly now, thanks!
  29. 1 point
    Curious if there is any plan to ad LV2020 support?
  30. 1 point
    That did the trick. Curious - I thought that ran everytime you opened VIPM. Is that true? Does it only automatically do it on some schedule? I swear I had restarted VIPM.
  31. 1 point
    By the may thanks for an awesome toolkit and the quick response!
  32. 1 point
    Hello LV Gurus, I am creating a simple GUI to control a web (specifically RESTful web server) based DLI Web Power Switch Pro I have three problems: What is the "Base URL" Is it just the IP + port (e.g. http://192.168.0.100:80) or the whole URI including the path to the web server (e.g. http://192.168.0.100/restapi/relay/outlets/0/state/) Where and how do I insert the cross-site forgery ignore in the header (e.g. X-CSRF:x) with your REST API? The Default Header list does not include X-CSRF. Do you support Basic and/or Digest authentication? I get "Unauthorized" error messages using your PUT (or GET) methods returned in the Status String. I then proceeded to create a version of this GUI using cURL (via the System Exec node) to enable switch outlet 1 using "digest" authentication and it works: curl --digest -u admin:1234 -X PUT -H "X-CSRF: x" --data "value=true" "http://192.168.0.100/restapi/relay/outlets/0/state/" FYI: This is DLI guideline for using RESTful HTTP on their power switches Thanks in advance guys. You do wonders for us LabVIEW cogs! Relativity1
  33. 1 point
    We just released a new build with 2020 support https://www.vipm.io/package/jki_design_palette/
  34. 1 point
    There’s a new build of the JKI design palette that supports LabVIEW 2020! https://www.vipm.io/package/jki_design_palette/
  35. 1 point
    Hello All! I'm working on integrating the Caraya test framework into our CI process. As of now, we are using a Jenkins server to manage our builds, but I'm looking to add our Caraya unit tests to that equation. I'm relatively new to the CI world, but have a good amount of experience using Carayas built in test reporting functionality (the text report version). Ideally, upon unit test failure I would like to have the full report sent to the user via email showing them which unit tests did not pass. I know some of this is handled on the Jenkins side, but I'm more so curious about how to properly invoke the unit test VI within my project so that the results and report are available to Jenkins so they can then be emailed. Any and all insights here would be much appreciated. Thank you!
  36. 1 point
    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.
  37. 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
  38. 1 point
    Hi guys, Just wondered if there's any way (using VIPM File Handler) to Refresh a VIPC to reference latest versions of listed packages (assuming they're already installed in VI package library) ?. Alternatively, any plans to add the ability to Add Packages to VIPC by package name rather than scanning a Project ? BR. Chris
  39. 1 point
    Hi In the VIPM 2020 beta I tried to install the error logger from CPE. And indeed that worked except that the include ppl was not correct for LV2019 or LV2018 so not useable. I have send a request to CPE to add those versions but only this morning so somewhat early to expect a reaction. Is it possible to check for ppl versions or should we leave that to the developer.
  40. 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. 😅
  41. 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
  42. 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.
  43. 1 point
    Glad you got this working and sorry for the delay in response.
  44. 1 point
    Hi all, I am using VI tester to run unit tests in my project. When I run unit tests for the VIs which are using NI XML APIs. The LabVIEW crashes/hangs randomly at the VI - "..\vi.lib\xml\XPath\Get All Matched Nodes.vi" at the DLL Node. I am not sure about the reason why I am facing this. In the below image, highlighted is the node where execution waits and makes LabVIEW hangs/crashes. Please answer the below Questions which helps me to understand the problem better: 1. In any case does VI Tester runs all the Test VIs Parallelly? 2. The DLL is set to run in UI Thread Could that be a problem? I have tried to change it to run in any thread but that didn't help. Please help me to understand this issue Thanks, Bhargavi Gowri.
  45. 1 point
    I've reproduced the issue and it should be fixed in VIPM 2020.
  46. 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
  47. 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.
  48. 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!
  49. 1 point
    I was able to fix this by setting vip files to open with VIPM File Handler.exe by default.
  50. 1 point
×
×
  • Create New...

Important Information

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