Jump to content

Jim Kring

JKI Team
  • Content Count

    1,717
  • Joined

  • Last visited

  • Days Won

    42

Everything posted by Jim Kring

  1. Hi Thomas. Thanks for reporting this. Can you explain a little bit about how this missing .rtm file is impacting your work? Does it cause any specific problems, or is it just an observation that it's missing? Thanks.
  2. Looks like your IT department is probably blocking the download URL.
  3. Thank you. We'll take a look at reproducing this and if there's a future fix for the issue. We can't commit to a timeline, but we certainly would love to see this issue addressed in a future release, if there's a solution to be found.
  4. Hi. Thanks for reporting this. Would you be willing to spend a small amount of time to create a super simple VI Package project that demonstrates this issue and share that with us (as a zip file)? We'd love to be able to reproduce this issue and see if there's a work-around or fix.
  5. I can't point you to a known issue, but there's a good chance we've fixed the issue you're mentioning.
  6. Which version of VIPM are you using? I think we made some improvements to VIPM 2018 (and the f1 release) that improve support for PPLs.
  7. Hi Tianbin, The VIPM package URL handler only works on Windows, currently. Jim
  8. Hi Steen, Thanks for the well thought out question/proposal. We've considered this at several points, yet there have always been very many considerations that make supporting LVLIBPs problematic. Unfortunately, NI did not have LabVIEW developers in mind when they designed LVLIBPs -- they were focused mostly on addressing internal use cases such as streamlining deployment to embedded targets.
  9. Hi There. Yes, it looks like you may have found a bug. I think that "[]" characters are allowed in JSON data names. Perhaps they were removed because they are also special characters.
  10. Hi Kev, Can you try setting VIPM to use "No Proxy" and see if that helps.
  11. I don't know if there's any way to do this programmatically, at this time.
  12. Hi, Paul. Yes, VI Package Configuration is the way to go!
  13. Hi There. Please email support@jki.net and we'll point you in the right direction.
  14. Not totally sure what the issue is. Have you tried running both VIPM and LabVIEW as the root user? Also, might be because LabVIEW is running in Evaluation mode. Linux is a bit tricky, since it's so configurable and quirky...
  15. Thanks for the update @wyzromek. Yes, there's still a lot to do -- NXG 2.1 still isn't totally ready for upgrading existing projects and there is still a little work to do on the JKI SM side of things, too. We're hoping that NXG 3.0 will provide a bit more features and improvements to the process ?
  16. Hi @Jim C I split this discussion into a separate discussion thread. I like you're idea about the JKI State Machine Follower. I've been collecting some ideas about possible run-time and debugging tools: https://github.com/JKISoftware/JKI-State-Machine-Editor/wiki/Roadmap#run-time-tools Here are a few ideas: State logging - Show which states executed in which order Data logging - Show what data was changed between execution of frames Single stepping - Execute one frame at a time and pause between execution Breakpoints on individual states - Pause when a state is executed, so that highlight execution can then be enabled (and maybe we could turn execution highlighting ON, but I'm not sure how to do that programmatically) These tools would probably require temporarily swapping the Parse State Queue function in the user's instance of a JKI State Machine with a special one that has debugging features under the hood (there could be a debugging and non-debugging version of Parse State Queue that we could script in/out of the VI to enable/disable the debugging features). Anyhow, I wanted to let you know that this is a direction we're looking into, in case you have any ideas you've already been thinking about or working on :-) Thanks,
  17. Thanks for the feedback @Jim C. I'm glad you like this new feature. I also like the idea of allowing the JKI SM Editor to help with debugging and have it highlight the actively executing frame. I've been toying with some similar thoughts :-)
  18. We've made another great round of improvements to the JKI State Machine Editor that we're excited to tell you about. This release adds a pretty cool new little feature that we've heard several people ask for... Now, you can right-click on a state string wire and select Insert "Add State(s) to Queue" to automatically insert this VI.
  19. Hi again @wyzromek. Have you tried clicking 'Next' and continuing with the conversion? The resulting project should be relatively unbroken: the missing methods/property nodes are replaced with placeholder nodes and the NXG 2.0 library calls to both JKI & OpenG are mapped correctly (see below).
  20. Hi @wyzromek. Thanks for reporting this. We're currently looking into the issue, with the help of NI and will get back to you with information, as soon as we know more.
  21. Have you tried using the JKI HTTP REST Client?
  22. Hi @Ruslan. Yes, if a Case Structure frame is doing work, the Event Structure frames will not execute (until the Case Structure is done and there is no more “work” on the state string shift register / queue (unless the “Idle” state is called explicitly by adding it to the state string queue). However, Events (that the Event Structure is registered for) will still be queued up for the Event Structure to handle once the work is done in the Case Structure. hope that helps, Jim
  23. I have to confess that I don't speak Russian I think you said (according to Google Translate), "How could it be the case that a frame works for a long time, and then the whole program does not respond to events?" I'm not sure without looking at your specific code/example.
  24. Just a quick update that there have been some minor fixes and improvements over the past couple weeks (since the last big release). Fixed issue where tree fully expands after any edit of JKI SM frame names Fixed issue where sometimes state strings were not recognized correctly if they were inside or wired through structures Fixed some quick search/filtering bugs Added right-click option JKI SM Explorer tree view to Expand All and Collapse All items You can download and install the latest version using VIPM.
×
×
  • Create New...

Important Information

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