Whether you’re new to LabVIEW or have been around the block the topic of VI reentrancy is an important one especially when dealing with stateful VI’s. In this post we’re going to briefly define the different reentrancy settings and then talk about the dangers of stateful VI’s who have the wrong reentrancy settings or are used in the wrong context. We define a stateful VI as one that stores data within itself from one call to the next. This is done in LabVIEW using shift registers and feedback nodes.
Once upon a time there was a quack named <your name>. Everyday <your name> arrived to work to solve complicated technical problems with their mighty intellect and LabVIEW development skills. These skills, wielded like a sharp sword helped <your name> slay even the toughest of challenging problems. One day, <your name> faced a looming dreadline that threatened impending doom if <your name> could not dispatch of it quickly enough.
How many times have you looked for an instrument driver, and find that it doesn’t exist? It happens, and that overwhelming feeling of doom looms overhead. Don’t let that feeling overcome you until you have verified that there is not a SCPI interface. SCPI stands for “Standard Commands for Programmable Instruments.” As the name says there could possibly be a set of standard commands that will help you still be able to control your instrument. Most instruments support SCPI as their protocol, which is lucky for us developers.
What is better than having the two-time World's Fastest LabVIEW Programmer? Having the three-time fastest programmer and top six fastest programmers this year!
This year Endigit set a goal to take the top five spots in the competition. We went the extra mile and took the top six spots in the competition. Robert Mortensen beat out fellow Endigit employee Bryan Heslop in 2017 so he had a bye this year through the first two rounds and ended up defending his title in the final round against Blake Ewton.
If you have ever thought "Man, I am so sick of pushing these buttons on this instrument I could punch someone!", or your instrument is strategically placed on the opposite side of the lab from your computer, then you are in luck. The everyday mundane tasks of using instrumentation for your projects is inevitable. Sometimes it requires pushing buttons every hour or so, and sometimes it requires pushing those buttons 30+ times a minute. In short, doing this for days on end can lead to mental breakdown. Science proves it.
Every once in a while we have the opportunity to learn a programming language. With each new language comes the challenges of learning new “vocabulary” as well as the various things that make each language unique. As with any new language, habits from our “native” language carry over. For example as someone who learned to program in Java and C++, leaving types off variables is still hard in Python!
"Sorting this material by hand will take two guys about six months and cost us around $60,000," said my client.
Our team is using BitBucket for source code control and the SourceTree app for Windows to interface with our repositories. We've had a couple of small hurdles getting SourceTree to integrate with the LabVIEW diff tool, but here's a solution that's worked for us. (Credit to Paul Lotz on Atlassian's forum, https://community.atlassian.com/t5/Questions/SourceTree-external-diff-path-issue-on-Windows/qaq-p/394740)
Here is a quick story about some software that became awesome due in a large part to good communication. Our client, AccuPower Solutions, records HD video at 120 frames per second from multiple cameras and force data from a force plate while people jump on it. The data can then be used to draw force arrows on the video and help coaches characterize athletic performance.