Tag Archives: LabVIEW

Announcing the New “Magic Delay Fairy” Tool for LabVIEW

JKI is pleased to announce the release of the new Magic Delay Fairy Tool for LabVIEW,  a revolutionary new tool for LabVIEW developers working to solve some of the toughest system timing and synchronization challenges. Here’s how this tool can help… Some Bugs … Continue reading

Posted in Company News | Tagged , , , | 2 Comments

JKI State Machine 3.0 Released (Open Source)

We are happy to announce that JKI State Machine v3.0 has been released as a JKI Open Source Project (BSD license) and is available for download using VIPM. Additionally, we’ve upgraded the sources to LabVIEW 2013 and made a few minor cosmetic tweaks: – Built … Continue reading

Posted in JKI State Machine | Tagged , , , , , , | Leave a comment

JKI Open Source Projects

We are excited to announce that JKI has officially launched its open source software projects on GitHub. JKI strongly believes in contributing to the open source movement and has made several of its LabVIEW libraries and tools available under the BSD … Continue reading

Posted in Company News | Tagged , , , , , | Leave a comment

CLA Summit 2013 Europe: “Public Events for Modules” Video & Slides Now Available

I had the pleasure of being invited to speak at the CLA Summit Europe 2013, at NI France in Nanterre (just outside Paris).  This was a fantastic event and it was a lot of fun to meet CLAs from around … Continue reading

Posted in Events, LabVIEW | Tagged , , , , , | Leave a comment

#4 Best Practice for using the JKI State Machine: Use macros instead of “chaining” together sequential states

In my last post on JKI State Machine Best Practices, I explained the #3 Best Practice: Keep the Original Size (i.e. don’t grow the structures).  In this post, I’ll tell you which best practice came in fourth place. The #4 Best Practice: Use macros … Continue reading

Posted in JKI State Machine, LabVIEW | Tagged , , , , | 5 Comments

#3 Best Practice for using the JKI State Machine: Keep the Original Size (i.e. don’t grow the structures)

In my last post on JKI State Machine Best Practices, I explained the #2 Best Practice: Don’t add code and logic inside the Event Structure.  In this post, I’ll tell you which best practice came in third place. The #3 Best Practice: Keep the … Continue reading

Posted in JKI State Machine, LabVIEW | Tagged , , , , | 3 Comments

Bay Area LabVIEW User Group (Feb 10, 2015) – Come learn about JKI State Machine Objects

If you’re in the Bay Area, come to the NI offices this evening, Feb 10, 2015, for a LabVIEW User Group presentation on JKI State Machine Objects, an easy and scalable way to manage and reuse multiple JKI State Machines … Continue reading

Posted in Bay Area LabVIEW User Group, Community, Events, JKI State Machine, LabVIEW | Tagged , , , , , , , | Leave a comment

#2 Best Practice for using the JKI State Machine: Don’t add code and logic inside the Event Structure

In my last post on JKI State Machine Best Practices, I explained the #1 Best Practice: Don’t hide your state strings in subVIs.  In this post, I’ll tell you which best practice came in second place. The #2 Best Practice: Put code and … Continue reading

Posted in JKI State Machine, LabVIEW | Tagged , , , , | 1 Comment

#1 Best Practice for using the JKI State Machine: Don’t hide your state strings in subVIs.

At a recent JKI Team “LabVIEW Lunch” (where the team gets together to eat and talk shop), we were discussing JKI State Machine Best Practices. Note: the JKI State Machine, an easy-to-use yet powerful state machine template we created to help LabVIEW developers … Continue reading

Posted in JKI State Machine, LabVIEW | Tagged , , , , | Leave a comment

JKI State Machine Best Practices

At a recent JKI Team “LabVIEW Lunch” (where the team gets together to eat and talk shop), we were discussing best practices for using the JKI State Machine, an easy-to-use yet powerful state machine template we created to help LabVIEW developers write code … Continue reading

Posted in JKI State Machine, LabVIEW | Tagged , , , , | Leave a comment