Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/31/2010 in all areas

  1. Name: TLB - Top-Level Baseline Submitter: Norm Kirchner Submitted: 19 Apr 2011 File Updated: 19 Apr 2011 Category: *Uncertified* LabVIEW Version: 2010 License Type: BSD (Most common) This is the official release of my LV State Machine template; the TLB - Top-Level Baseline. It was presented at the State Machine vs. State Machine presentation at NI Week 2010. This is worth using because it implements most of the common functionality that you end up creating w/ most / all LV state machines anyway: Error handling Idle cases Interactive event driven execution Shutting down parallel loops gracefully String based queued states Handling the Panel Close? event Some techniques used are not immediately intuitive, but each design decision was made with the idea of scalability and ease of use in mind. Please post your 'Why did you do that?' questions and I'll gladly inform and instruct why the design choices were made (including why did I use colors) Click here to download this file
    2 points
  2. Just a word of warning based on my recent experience... If your RT code has lots of static NSV nodes and you are also programmatically opening NSV references then you need to make sure that the behind-the-scenes init code that comes with each static NSV node has completed before attempting to use the NSV API. If you do not then you may corrupt the SVE and will have to reboot to recover. Currently I just do a dumb wait (30s in my case), it would be nice if there was a way to find out programmatically when it was safe to start executing your RT code.
    1 point
  3. Hi all, having suffered a lot from cleaning code of somebody that had not heard anything about Loops or Clusters, I sat down to study scripting and produce my first Quick Drop plugin. Use of the Plugin: Select the objects you want to wire to a BuildArray or Bundle function and invoke the Plugin ("shift" for Bundle). The Plugin then creates the function with a matching number of input terminals and connects the objects to the function. For sure, there are ample possibilities to improve/expand the Plugins functionality. Herbert Wire to BuildArray_Bundle.vi
    1 point
  4. Thanks, Norm. I can't wait to dig into this, I've been waiting for the finished version. One thing I'd like to see an example and brief explanation of is implementing inter-process communication.
    1 point
×
×
  • Create New...

Important Information

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