Jump to content

Darren

NI
  • Content Count

    579
  • Joined

  • Last visited

  • Days Won

    48

Everything posted by Darren

  1. If you search the LabVIEW Help for "generate report", you should find lots of topics on the Report Generation VIs. These VIs come with LabVIEW and allow you to generate HTML reports and "Standard" reports (a standard report prints directly to your printer). If you purchase the Report Generation Toolkit, these VIs are expanded to include the generation of reports for Word and Excel. You can learn more about the Report Generation Toolkit at http://www.ni.com/toolkits/report_gen.htm . -D
  2. The ".." notation in a Case Structure defines a range of values. For instance, if you have a case defined for "1..5", then any value between 1 and 5 (inclusive) will cause that case to run. If you use the ".." without an upper or lower limit, it will include all values greater or less than that value...for example, "..5" means that case will run if any value less than or including 5 is specified. For the documentation on this, search the LabVIEW Help for "Case Structure". In the "Case Structure" topic, click the link for "enter a single value or lists and ranges of values". Good luck, -D
  3. Search the LabVIEW Help for "Feedback Node" and read the first topic that comes up (it should be called "For Loop and While Loop Structures"). Scroll down almost to the bottom and you'll see a screenshot showing the "feed forward" version of the feedback node. To create one of these, do the following: 1. Drop a function (I used an Increment function because it's easy) in a loop. 2. Wire the output to the input. 3. Branch off the same wire (it should be broken) and wire to the loop border. 4. Right-click anywhere on the broken wire and choose "Insert Feedback Node". Voila...you have
  4. Hi Jim, The word "topic" in the documentation you reference is simply a misprint. Replace "topic" in that sentence with "portion" and you'll have the correct description of the '^' character. Sorry for the anticlimactic response...I'll bet you were all ready with a conspiracy theory. -D P.S. - I have filed a CAR (3VLDERF2) against the LV documentation to get this corrected.
  5. I just checked with some of my colleagues in LabVIEW R&D and this is what I found: Static VI Reference issue: This is expected behavior. A Static VI Reference will not appear in the Callees' Names or Callees' Paths property list. This is because a Static VI Reference allows you to have a VI call itself recursively, and the Callees' properties do not support recursive VI calls. I have filed a CAR (3VJDFQF2) against the LabVIEW documentation so we can indicate this fact in the help for both the Static VI Reference and the Callees' properties. SubVI with Required Input issue: This is a
×
×
  • Create New...

Important Information

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