Jump to content

Jim Kring

JKI Team
  • Posts

    2,199
  • Joined

  • Last visited

  • Days Won

    105

Everything posted by Jim Kring

  1. 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.
  2. @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.
  3. 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
  4. That's great to hear. Thanks for letting us know. If you come up with a good solution, maybe you can share some details, so that other's can see how you did it. Thanks!
  5. You may need to do some googling and research to figure out how to run 32 bit applications on your linux installation. there’s a discussion thread here with some tips: https://stackoverflow.com/questions/23182765/how-to-install-ia32-libs-in-ubuntu-14-04-lts-trusty-tahr Specifically, it talks about how to add another package repository for apt yet to find the missing package. Please keep in mind that I’m not sure exactly if this is the best solution for you, so please be sure to do some research.
  6. Some googling shows that this error can occur when you're running 64-bit and in order to run 32-bit executables, you'll need to install the ia32-libs package (and make sure you have multi-architecture support enabled). You can try installing the ia32-libs package using the following command: apt-get ia32-libs Some googling will help you figure out all the details for your platform. Disclaimer: I'm not a Linux expert, but I sometimes play one on TV.
  7. thanks for posting that. It looks like you are in the right folder, the permissions are correct on the vipm file, and you tried to execute it. I'm no Linux expert, but that looks like it should work. What happens if you type the following? ls -al /usr/local/JKI/VIPM/vipm This should output something that looks like: -rwxr-xr-x. 1 root root 35218160 Mar 8 21:22 vipm
  8. You need to run the executable: sudo /user/local/JKI/VIPM/vipm or change directories into the VIPM folder first and then run the executable cd /user/local/JKI/VIPM sudo ./vipm The directions could be a little more clear. Does that work for you?
  9. Yes and no. Yes, it's possible. You will need to write to the http request header a "Authorization: Negotiate [token]" instead of "Authorization: Basic" (for basic password authentication). However (this is the "no" part), you probably will need to implement the security token handshaking protocol yourself -- I don't see (via googling) that anyone has done that. See here for a high level overview. There's a more detailed, technical explanation of the process here.
  10. We're pleased to announce the release of VI Package Manager 2017 for Linux! Our team has worked hard to address several issues that were making Linux support difficult. Click here for more details.
  11. Good catch @wyzromek! We've fixed this issue (I hope) and released a new version. Also, we added support for In Place Element Structure cluster (un)bundlers, while we were at it.
  12. We're pleased to announce the release of VI Package Manager 2017 for Mac! Our team has worked hard to address several issues that were making Mac support difficult. Click here for more details.
  13. A very simple LabVIEW toolkit for localizing VI front panels, based on a dictionary translation file. This toolkit makes use of the "Language for non-Unicode programs" setting in Windows (located in the "Region and Language" settings). The toolkit uses a JSON dictionary file (can be in Unicode format) to store phrases in several different languages. The toolkit will translate from the default language (typically English) to the target language specified as the "Language for non-Unicode programs" in Windows. It does all this by making calls into the Windows API to translate the Unicode 16-bit characters from the dictionary into 8-bit non-unicode characters that can be displayed by non-Unicode program (assuming the "Language for non-Unicode programs" has been properly set in Windows). In this way, LabVIEW developers have a simple way to localize their applications, even though LabVIEW does not support Unicode, out-of-the-box. JKI Simple Localization Homepage Get JKI Simple Localization
  14. Get the JKI State Machine Editor (just check VIPM for package updates) Version 2013.4.0.186 This new release adds a right-click option called "Find Data Accessors" to Bundle by Name and Unbundle by Name nodes in a JKI State Machine. Using this feature will open a dialog showing all the frames of the JKI State Machine that access the data, as shown below:
  15. Hi All, There have been reports of issues downloading OpenG packages using VIPM, due to an outage at SourceForge.net (get status updates here). In the meantime, you can install all the latest OpenG Toolkit packages using this VI Package Configuration file: OpenG Toolkit - 2018-02-28.vipc
  16. Hi Norm (@Viper). Great question and you're not the first one to want this feature -- I'd like it, too. No, right now that's the only way to do it -- by unbundling and building a cluster of data yourself. EasyXML doesn't look at the data inside of classes, unfortunately.
  17. The JKI State Machine for LabVIEW is an easy-to-use yet powerful state machine template. It is the very same template that is used by the JKI team, nearly every day, and is the result of years of refinement by our team of LabVIEW™ experts. JKI State Machine Project Homepage Get JKI State Machine Watch Video Tutorials Learn Best Practices JKI State Machine Editor
  18. JKI REST Client is a HTTP client library for connecting LabVIEW applications with RESTful web services. JKI REST Client provides a client implementation of HTTP protocol that is specifically designed for integrating LabVIEW applications with web services. JKI REST Client augments the LabVIEW native implementation of HTTP by adding several features that make it better fit for connecting with RESTful web services than LabVIEW native HTTP client. HTTP REST Client Homepage Get HTTP REST Client
  19. VI Package Manager (VIPM), JKI's flagship toolkit ships with LabVIEW and allows you to discover, create, and share LabVIEW add-ons. VIPM gives you instant access to the add-ons on the LabVIEW Tools Network. Get VIPM, Learn More Release Notes, Knowledge Base, Idea Exchange
  20. Caraya is an assertion and unit test framework for LabVIEW that is simple and fast. It takes a whole new approach to unit testing; your VI is your test. Caraya allows you to convert your manual test VIs you use to debug your code into unit test cases with nearly no effort. This significantly lowers the barrier to systematicaly write unit tests for your project leading into improved overall code quality for real-world projects where developers don't always have the luxury to write unit test cases first. Caraya Project Homepage Get Caraya
  21. The RSS Feed URL changed. Try this one: https://lavag.org/rss/forums/1-lava-forums/
  22. Michael is a VIPM super-star!

  23. Hoping there are no major issues with the JKI forum upgrades :)

  24. You're welcome. No, I don't think there is any way to do this in 2.x. You'll have to ask Santa for VIPM 3.0
×
×
  • Create New...

Important Information

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