Jump to content

Wire Warrior

Members
  • Posts

    226
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Wire Warrior

  1. Hoovah, Okay that makes sense. 

     

    I suppose extending on that idea you could have a "planned" communication graph and an "actual" communication graph as well.  Doing that lets the tool be used as a verification piece also. 

     

    I wonder....does the state machine tool kit have features/functions that could be co-opted to assist with this?

  2. I guess maybe I am missing something but what exactly does this information tell you?  I can see the graph as representative of the relationships but how does that help?

     

    Do you have like a use case example that you could walk me through to show how the data is used?

     

    Wire Warrior

  3. Hello all,

     

    After trying to find an answer to a issue I was having with Requirements Gateway last week and not finding a users group, I have created a Requirements Gateway User Group on the communities and I invite you all to join.  There isn't much content at the moment since it's still a bit of a fledgling.  Please join and add your content, questions, and tips.

     

    You can join by going to https://decibel.ni.com/content/groups/requirements-gateway-users-group

     

    See you there.

     

    Wire Warrior

  4. That depends on the mechanism being used to transfer the data.  Is it serial? TCP/IP? FTP?  Once you answer that use the Example Finder to look up the protocol type along with log to file and you should see some examples you can use as guides for building your own program.

  5. Okay that makes me want to ask a question.  I was using a class in a dialog subVI.  The class value is passed into the subVI to be modified by the user in the pop-up.  I had based my dialog on the JKI string based state machine which has a data initialize state in the while loop.  When I placed my input class control inside the loop and my output class control outside the loop, the VI broke and the error was that re-entrant class couldnot be used that way.  When I got to looking my data accessors which were programmatically created by the IDE were set to re-entrant.  I didn't expect that to be the default behavior.

     

    This is with a less than 2 week old install of LV2012 (not sp1) on a virgin machine.  Thoughts?

  6. NI offers this 16-port serial card to plugin to your computer. http://sine.ni.com/nips/cds/view/p/lang/en/nid/207740

    Probably be your best solution. Details below.

    NI PCIe-8430/16 (RS232) High-Performance, 16-Port RS232 Interface for PCI Express
    • Compatible with Windows and LabVIEW Real-Time OSs
    • Flexible standard and nonstandard baud rates from 2 baud to 1,000,000 baud
    • Better than 0.015 percent accuracy for standard baud rates and 0.5 percent for nonstandard rates
    • High-speed DMA interface and 128 B transmit and receive FIFOs minimize CPU overhead
    • Includes two 8-port breakout cables (68-pin VHDCI to eight D-Sub 9-pin male ports)
    • NI-Serial driver includes free NI-VISA API for easy programming

  7. The node you want to use is the Call Library Function Node.  If you look up DLLs in the Find Examples utilty (accessed via the help menu) you will get some examples.

     

    The LV2012 help file can be found at http://zone.ni.com/reference/en-XX/help/371361J-01/glang/call_library_function/.  It should also be installed with your LabVIEW installation.

     

    This page tells how to configure it:  http://zone.ni.com/reference/fr-XX/help/371361J-0114/lvexcodeconcepts/configuring_the_clf_node/

     

    There is also more information on ni.com.  You can search there as well.

  8. For our re-usable code we like to have a separate project for the "library" where maintainance is performed. These are put in source code control and we never link directly to the VIs in the project area. When use VI Package Manager (VIPM) to build VI packages to place the VI's in a custom location in the user.lib folder. This has worked well for us with multiple developers through two LabVIEW upgrades. We are still working with the community version of VIPM since I can convince the boss man to spring for the pay version(s) that would let us manage distribution easier.

    • Like 2
×
×
  • Create New...

Important Information

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