Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 09/20/2019 in Posts

  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. 2 points
    Got same error from time to time. Have to restart LabVIEW. LabVIEW 2019 32bit Windows 7 Pro.
  8. 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.
  9. 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?
  10. 1 point
    I was surprised to hear in the state machine course the best practice of adding states at the front of the state queue. I've always added them at the back under the theory that I'm "queuing up" states to be run, but I don't want to hijak the order of exectution if there's already seme states enqueued. The only time I add to the front is in an interrupt type situation. Can someone explain why adding to the front would be considered best practice?
  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
    This is not the case in LV19
  13. 1 point
    Is there any way by which we can perform some operation before / after installing a VI Package configuration? Or is there a way to restrict the installation of a VIPC file based on few conditions? Or is there a way to restart LV before / after applying VIPC?
  14. 1 point
    I found a method that works by using Darren's quick drop shortcut method. https://forums.ni.com/t5/Quick-Drop-Enthusiasts/Quick-Drop-Keyboard-Shortcut-Create-Place-VI-Contents-VI/gpm-p/3520372?profile.language=en I just put the JKI down in a new VI and edited it as I would normally for every new SM and then saved it as a quick drop.
  15. 1 point
    It works... Thanks a lot. Best regards Markus
  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
    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
  18. 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
  19. 1 point
    I have the same problem now, irritating as hell. Having paying customers is of course the optimal for JKI, but it still seems silly to chase everyone over to alternative solutions. It is the adoption rate after all that makes the platform interesting for package publishers. And now that we are all forced to register to download even the open source projects proper logon functionality has become critical. Please support every user, and fix the connection issues.
  20. 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.
  21. 1 point
    I don't see the way to "ignore dependency". Still looking through help.
  22. 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
  23. 1 point
    And it works perfectly now, thanks!
  24. 1 point
    Simply removed the case structure and it seemed to work fine.
  25. 1 point
    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.
  26. 1 point
    Hi There! Glad you like the JKI HTTP REST client. For the base URI, I would use: http://192.168.0.100/restapi and then for the path when you call GET or POST, use: /relay/outlets/0/state/ Here's how you could add the X-CSRF header. Note that you can type (or copy-paste) new items into the drop-down selector for the header -- it works like a string control, but with some pre-defined options to make life easier for common headers. The JKI HTTP REST Client passes the username and password into the HTTP VI used by built-in HTTP Open Handle.vi, which I believe doesn't support digest authentication. Under the hood... Digest authentication is something that could be added -- here's the specification and here's a demo server, if you're interested in trying.
  27. 1 point
    We just released a new build with 2020 support https://www.vipm.io/package/jki_design_palette/
  28. 1 point
    There’s a new build of the JKI design palette that supports LabVIEW 2020! https://www.vipm.io/package/jki_design_palette/
  29. 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!
  30. 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.
  31. 1 point
    In terms of design, it looks quite harmonious
  32. 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
  33. 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.
  34. 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
  35. 1 point
    Thanks, I'll do that. Option 2 would be nice, but I've wished a few times that the Add Control or VI option allowed multiple selections as well. That seems like the more versatile option if only implementing one of the two is feasible. Side question: Any idea why Chrome freezes will VIPM is processing a (very) large package? Background: This package I'm working on is actually a message dictionary for one of my company's products that has 27 different communication nodes and over 1200 defined messages. Since LabVIEW does not support sparse enums, the best strategy I've found to convert this into a LabVIEW library so far is using VI scripting to convert all the #DEFINES into individual VIs that are simply numeric constants wired to an indicator. Essentially, these are "constant" VIs. The end result is the library ends up having ~1450 files in it by the time all is said and done. LabVIEW has generally handled this library fine as a local library I've copied into my projects, but I wanted to package it to make it more easily distributed and easier to keep up to date when our R&D engineers release new product software. Understandably, it takes a while for VIPM to process all these files and build a package, and after installing it takes a while to update the package list. I suppose all of that is to be expected, but what's interesting is that Chrome freezes while a few of these steps are occurring. Every other application on my computer is responsive.
  36. 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.
  37. 1 point
    I've reproduced the issue and it should be fixed in VIPM 2020.
  38. 1 point
    Hi, in our company we changed the Parse State Queue VI, so that we get the previous state in case we had an error. With this it was so much easier to debug the JKI-SM, because we were able to display the state, where the error occurred. Maybe this this an idea for the original Parse State Queue?? Here is an snippet based on the "old" Parse State Queue VI.
  39. 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
  40. 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!
  41. 1 point
  42. 1 point
    Ok, thanks for this, no less than what I was expecting from JKI 🙂 I don't really use NXG yet, I installed NXG 4.0 and had a quick look around, nothing more for now. Not sure yet when I'll start migrating my customer project, probably around end of 2020. At the moment I'm listing all the NI modules/drivers and "community modules" that I use in CurrentGen and start checking if and when they'll be available in NXG.
  43. 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?
  44. 1 point
    I missed the part where you are using a VM for this. Are you accesing from a remote X session? If so, the root user will require some additoinal authorization to run GUI based applications in remote sessions.
  45. 1 point
    Hey Sam. This should be fixed in VIPM 2020. If you're interested in helping beta test it, please sign up for the LabVIEW 2020 beta.
  46. 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
  47. 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.
  48. 1 point
  49. 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
  50. 1 point
    Hi Ton, That's a great idea -- we've noticed that we need that feature, too. It's on our roadmap. Thanks, -Jim
×
×
  • Create New...

Important Information

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