Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/23/2016 in all areas

  1. A bit late, but this table can probably help: You're apparently in the Waiting to run state, which happens with statically linked VIs which are inside VIs which are in Run mode. I didn't remember whether this applies to static VI references, but apparently it does. Another option which hasn't been mentioned here is to store the VI reference in the caller (e.g. using a feedback node) and always start by opening its FP. If that works (no error), you carry on. If it doesn't, you launch a new VI and store its reference.
    2 points
  2. Alright, thanks for the info. I knew of the AF group but generally try to avoid anything on ni.com (at least till all other resources are exhausted) since the knowledge might be there, but the page is a navigational atrocity and things are usually fragmented and hard to find.
    1 point
  3. You're welcome to do what you want with your contribution to the community, but I generally recommend code be posted in the Code Repository here on LAVA. This has version tracking, it generates a new thread for submitted code, so user discussion can be linked to the code posted, and a few other benefits like download number tracking, etc. Generally you post it as uncertified then if interest level (and time) permit it is updated to certified. Here's another link on how to submit code. https://lavag.org/topic/10351-how-to-submit-code-to-the-code-repository/ https://lavag.org/topic/10350-how-does-the-code-repository-work/
    1 point
×
×
  • Create New...

Important Information

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