Jump to content

Jim Kring

JKI Team
  • Content Count

    1,688
  • Joined

  • Last visited

  • Days Won

    40

Jim Kring last won the day on May 26

Jim Kring had the most liked content!

Community Reputation

74 Excellent

6 Followers

About Jim Kring

Recent Profile Visitors

26,358 profile views
  1. Hi Thomas. That’s super cool! Thanks for showing the screenshots. I’m glad to hear how easy that was for you and hope it’s helpful to you and your team. -Jim
  2. I’m glad to hear it’s working for you!
  3. Great. For what it's worth, a couple things we're considering: 1) Disable/configure the hotkey -- sometimes it pops up with just Ctrl+Space for some reason. 2) Allow pointing to other folders of custom controls.
  4. @Sam Taggart. There are error logs here: C:\ProgramData\JKI\VIPM\error
  5. Thank you for posting this! I'll forward it along to NI to take a look into it. Well, only NI can fix LVInternal errors 🤷‍♂️ Still, I'll ping them, since I'm sure they care to know what the issue is.
  6. You're welcome. Any requests to make it more awesome?
  7. 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.
  8. I think the issue is that you need to "Check Network for Package Updates" (Refresh) in the main VIPM package list. Can you try that? Then, I think it'll find the new version. LMK if that works. PS - you're welcome!
  9. 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.
  10. We just released a new build with 2020 support https://www.vipm.io/package/jki_design_palette/
  11. There’s a new build of the JKI design palette that supports LabVIEW 2020! https://www.vipm.io/package/jki_design_palette/
  12. Hey @John Hoehner and @ChrisStrykesAgain. Caraya 1.0 is officially released and in the wild! https://www.vipm.io/package/jki_lib_caraya/
  13. Yes! Thanks for the ping about this Sam. We will update this, very soon.
×
×
  • Create New...

Important Information

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