Jump to content

Jim Kring

JKI Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Jim Kring

  1. I don't know if there's any way to do this programmatically, at this time.
  2. Hi, Paul. Yes, VI Package Configuration is the way to go!
  3. Hi There. Please email support@jki.net and we'll point you in the right direction.
  4. 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...
  5. 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 ?
  6. 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,
  7. 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 :-)
  8. 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.
  9. 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).
  10. 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.
  11. Have you tried using the JKI HTTP REST Client?
  12. 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
  13. 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.
  14. 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.
  15. @Thoric any chance you could share the contents of your error log file? (C:\ProgramData\JKI\VIPM\error\*.txt)
  16. Thanks for reporting this, Richard! We’ll take a look under the hood.
  17. @Jim C you may want to tell your coworkers to sit down when the hear about this new release... We've made another great round of improvements to the JKI State Machine Editor that we're excited to tell you about. Integrated Event Structure and Case Structure Viewer The biggest thing you'll notice is that we've integrated the Event Structure and Case Structure into a single tree view -- all of the Event Structure frames have been added under the "Idle" ("Event Structure") item at the top of the tree (as shown in the screenshot below). You can now easily navigate all the Event Structure frames and Case Structure frames from this single tree view. Drag & drop to reorder the Event frames -- it works just as you'd expect! Context Help Shows Documentation for Frames of the JKI SM If you show the Context Help window (<Ctrl+H> or Help >> Show Context Help) and then hover over a frame name in the JKI State Machine Explorer's tree view, the Context Help window will update to show the documentation string for that frame. Explore States Dialog Another cool feature we added is the ability to Explore States on a state string constant. Simply right-click on a state string constant and choose Explore States (as shown below). This will open a dialog (shown below) that looks a lot like your string constant, and allows you to click on individual lines/states of the string constant, which will navigate the JKI State Machine to that frame. This allows you to quickly jump between frames if you'd like to navigate through the sequence of states in the string constant. Grouped Right-click Options on States Finally, we added a small usability improvement where we now group all of the right-click options for a state, under a single submenu (as shown below) -- previously, these were all at the root level and started to get unwieldy. I hope you enjoy this latest round of improvements to the JKI State Machine Editor and it helps your write great code even faster.
  18. Hey @BrianW Thanks for posting details of the issue you're experiencing. I found this thread on the NI Forums that addresses a similar issue. The solution post seemed to resolve it for the user in that thread. Any chance that might be of help?
  19. Hi @Tomas Can you explain what, in particular, your "dealing with"? I'm curious about the challenge your experiencing. Also, the timer is interesting. What do you use it for? It looks like it's a shift register with the time the JKI SM started running? Any reason not to put this into the main data (cluster) shift register? -Jim
  • Create New...

Important Information

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