Jump to content

JLMommy

Members
  • Posts

    22
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by JLMommy

  1. That depends on what LabVIEW modules/toolkits you have installed...

     

    NI Example Finder

    Toolkits and Modules >> PID and Fuzzy Logic Control >> PID >> 25 examples

    Toolkits and Modules >> Control Design and Simulation >> Control Design >> Analytical PID Design >> 5 examples

    Toolkits and Modules >> Control Design and Simulation >> Control Design >> Classical Control Design >> 3 examples

    Toolkits and Modules >> Control Design and Simulation >> Simulation >> Optimal Control Design >> 2 examples

     

    Figure 7 of the PID Theory white paper shows a DAQmx implementation using the PID toolkit.

  2. Wirebird Labs will sponsor two (2) Leap Motion Controllers.

     

    Announced yesterday, a new marketplace for Leap Motion software has opened at airspace.leapmotion.com, featuring 75+ applications.

     

    See you at the BBQ!

     

    attachicon.gifScreen Shot 2013-07-23 at 9.52.30 AM.png

    Screenshot from https://www.leapmotion.com/product

    Hopefully my preordered Leap will come in the mail today..stupid rural post office is behind as usual!

     

    And there is a LabVIEW LEAP API!  Now if only they would publish it...

    • Like 1
  3. The collector block returns a cluster with two arrays: Time and Signal.  Use Unbundle by Name or Unbundle to extract the arrays. You can then use Array Max/Min on the Signal array to find the maximum value - the value and index will be returned.  Use Index Array on the Time array to extract the corresponding time:

    post-19194-0-83133800-1357146087.png


    Repeat for settling time.  You'll need to figure out how you want to determine the settling time of your system.  You may want to find where the value stops changing or doesn't change by more than a percentage or maybe you know an exact value.  The idea is the same - search the array for a certain value, use the index of this value to retrieve the corresponding time.

  4. Attached is a VI that searches recursively and returns all objects in the block diagram of the specified VI. I only handled the flat sequence, stacked sequence, while loop, for loop, event structure, disable structure, timed loop, timed sequence and in place element structure - if any more are needed they could be easily added. Figured it would at least be a starting point for someone trying to accomplish this.

    - Becky

    GetAllBDObjectsLV2011.vi

  5. I'm probably biased since I used to work at NI (former Michigan DSM), but I think it works great - IF you already have a requirements document.

    The overhead to create/update requirements documents is what actually defers me from using it - the company I work with would rather I spend my time programming. Most of the projects I have worked on do not have a strict set of "written" requirements and things change regularly as the project progresses. My customer typically tells me what they want and then see that I met the requirements when they "test" my code. I know this is not the best way and I wish I could change it, but for now that's what I'm stuck with.

    It is actually a really useful tool if the industries you work with are highly regulated. It is a quick and easy way to prove that your code has met every single requirement of a project after the intial learning curve. It also helps point out what requirements may be missing - if you have a lot of extra code that doesn't map to a requirement - was it really necessary? Or does your requirements document need updated?

    One last note - make sure you are a good speller and/or double check when you type your tags. RG will pick up your tags from multiple places in LabVIEW (FP, BD, VI Prop documentation, etc), but if you mistype something - it will look like you didn't meet the requirement. On that note, if you decide to use it, do not wait until the end to run RG - run it every few days so you can find these problems early and often.

    Hope that helps!

    - Becky

×
×
  • Create New...

Important Information

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