Site Search:

Data Acquisition Using LabVIEW and DATAQ Instruments’ ActiveX Controls

FacebooktwitterredditlinkedinmailFacebooktwitterredditlinkedinmail

LabVIEW is a popular programming environment for many data acquisition applications. DATAQ Instruments hardware products may be programmed under LabVIEW by applying our ActiveX software tools. This application note describes a step-by-step procedure you can use to access any DATAQ Instruments ActiveX control from LabVIEW. This procedure uses the WinDaq control which allows data acquired by WINDAQ® Acquisition software to be simultaneously made available to LabVIEW.

  1. Open a new LabVIEW project (this is usually the default when LabVIEW starts up).
  2. Select the Sequence Structure:
    LabView Sequence Structure
    The sequence structure forces the diagrams to execute in a particular order and separate the diagram into logical execution blocks. In this example, the sequence structure will be used to “start” the WinDaq control before it is used.
  3. Insert the selected sequence structure into the Diagram window:
    Labview Diagram Window
    The Diagram window is the source code of the project. The diagram drawn in this window will determine what gets executed, in what order, etc. This is the “behind-the-scenes” work that runs the Front Panel.
  4. Insert an ActiveX Container into the Front Panel
    LabView Front Panel
    The Front Panel is what will become the User Interface. The ActiveX container is necessary to insert an ActiveX control into LabVIEW. ActiveX controls work on the basis of server-client relationships. Refer to the “Introduction to ActiveX” secondary topic in the LabVIEW online help documentation for a description of how LabVIEW works with ActiveX controls. This section can be found by searching for “ActiveX, introduction” in the index.
  5. Right-click the container and select Insert ActiveX Object….
    LabView - Insert ActiveX Object
  6. Scroll to find WinDaq Control select it, and click OK.
    LabView WinDaq Control
    This will give you a list of all currently available ActiveX controls on the system.
  7. In the Diagram window, right-click the newly created control, select Show then Label to display what it is.
    Labview Diagram Window - Show - Label
    This will make it easier to identify what the object/picture represents.
  8. Click the Wiring tool in the Tools toolbox.
    Labview - Wiring tool in Tools Toolbox
    The wiring tool can be used to create “paths” that are to be followed during the execution of the program. These paths tell LabVIEW to take information from one object and send it to another object.
  9. Connect the WinDaq Control to the Sequence.
    Connect WinDaq control to the Sequence
    This will make the WinDaq control available to all frames within the sequence.
  10. In the Front Panel, insert a Horizontal Slide from the Controls toolbox.
    Insert horizontal slide from controls
    The horizontal slide will be used to select the channel to “watch” (i.e., the channel from which data will be read and displayed onscreen).
  11. In the Tools toolbox, click on the Operate Value tool.
    LabView Operate Value
    This tool allows you to change some of the object’s properties. This tool is used at runtime to operate the controls in the Front Panel.
  12. Now change the slider’s values from 1 to 2. Then, right-click and change the Representation to I16 (Word).
    Labview Representation Word
    To change the values, click on them and type in new values. The representation is changed to I16(Word) because that is the underlying integer type that most closely matches the WinDaq control’s property that will be used to determine the channel. The data types used by a specific property or method can be found in the ActiveX Controls Help file provided on the DATAQ website.
  13. Insert a Digital Indicator.
    Labview Digital Indicator
    This indicator will only display information to the user, not allow them to change it. This indicator will display the total number of channels.
  14. Insert another Digital Indicator. This indicator will display the actual data coming from the WinDaq control.
  15. Right-click on each control and label them as follows:
    Label each control
    After clicking Label, start typing to set the label.
  16. In the Diagram window on the Functions toolbox, click Communication then ActiveX then Invoke Node.
    LabView Invoke Node
    An Invoke Node is an object that calls a method from an ActiveX control. It allows you to give it any data it may need to pass to the method as well as return the results of the method call.
  17. Insert the object inside the sequence and connect a wire from the WinDaq Control (connected to the sequence using the black square on the sequence) to the Reference point of the Invoke Node.
    Connect a wire from WinDaq control to the reference point of the invoke node
    This will allow the Invoke Node to “know” what methods are available, what data needs to be sent, and what data will be returned.
  18. Right-click the Invoke Node and select the Start method.
    LabView Start Method
    The Start method tells the WinDaq control to start acquiring data.
  19. Right-click the Sequence, then click Add Frame After.
    Add frame after
    This will add a separate “block” to draw diagrams which will execute after the previous frame.
  20. Insert a Property Node inside the Sequence and connect it to the WinDaq Control with a wire.
    Insert property node inside the sequence
  21. Use the Arrow tool to move the Channel Count object inside the Sequence frame.
    Labview Arrow Tool
  22. Right-click the Property Node and select the ChannelCount property.
    Labview ChannelCount Property
    The ChannelCount property returns the total number of channels available to read data from.
  23. Right-click the Channel Count object and change its Representation to I16.
    Change Representation to I16
  24. Right-click the Channel Selected object and create an Attribute Node.
    Create an Attribute Node
    An Attribute Node is “connected” to its parent object and allows you to change the parent’s properties when the program is running.
  25. Move this node inside the sequence. Right-click it and change its property to Maximum.
    Move Node inside the Sequence
  26. Using the Wiring tool, create wires to connect the objects inside the sequence as follows:
    Create wires to connect objects inside the sequence.
    The Attribute Node sets the maximum value of the Channel Selected object. This in turn will prevent the user from trying to read data from a channel that is out-of-bounds. The Channel Count indicator will also display the total number of channels.
  27. Add another frame after this one to the sequence.
  28. Insert a While Loop inside the sequence.
    While Loop
    Since events are not supported in the version of LabVIEW this example was created with, a while loop will be used to continuously ask for data from the WinDaq ActiveX control.
  29. Insert an Invoke Node object into the while loop. Move the Channel Selected object and Data object into the while loop.
    Move Channel Selected object and Data object into While Loop
    By moving the objects inside the while loop, they will be executed (along with any other steps inside) with every “round” of the while loop.
  30. Create a wire to connect the Invoke Node to the WinDaq Control. Then, right-click it and select the GetScaledData method.
    GetScaledData Method
    The GetScaledData method will be used to get the data from WinDaq in calibrated engineering units as specified in the software. Refer to the ActiveX Controls Help file for further information on properties and methods of the ActiveX controls.
  31. Insert a Decrement object to decrement the signal from the Channel Selected object to the Data object and connect it as follows:
    LabView Decrement Object
    The Channel Selected object will allow the user to select a channel (1 through Maximum). The object will return the user’s selection, but the actual channel is one less because the WinDaq control enumerates the channels zero-based (starting with zero rather than 1).
  32. Connect the Channel Selected object and the Data object as follows:
    Connect Channel Selected Object and Data Object
    This will allow the Channel Selected to select which channel to get data from and the data returned by GetScaledData will be displayed in the Data indicator.
  33. Insert a Boolean Constant, set it to true using the Operate Value tool by clicking on the object after it is inserted, and connect it to the Conditional Terminal of the while loop.
    Insert Boolean Constant
    This will cause the while loop to run forever or until the program is forcefully stopped by clicking the Stop button. Normally, a Boolean control is used here so that the program may finish properly.
  34. Add another frame, after this one, to the Sequence.
  35. Insert an Invoke Node object in the sequence and connect it to the WinDaq Control. Change its method to Stop.
    Change method to Stop
    This method tells the WinDaq control to stop acquiring data. This will not be executed as it should because the while loop will never terminate to get to this step. When the program is forcefully stopped, it doesn’t go on to this frame.
  36. Start WinDaq as usual, then go back to LabVIEW, in the Front Panel, and run the project.
    Run Project
    You should see the Data indicator displaying the same data as the WinDaq acquisition software. Changing the channel using the Channel Selected object will show the data for that channel.
 

Follow Us
FacebooktwitterlinkedinyoutubeFacebooktwitterlinkedinyoutube

 Categories: Programming

 Tags: , ,

 Bookmark the permalink

 RSS Feed (comments for this post)

 Post a comment

 Trackback URL

2 Comments

  1. Avatar
    Jueun
    Posted August 31, 2016 at 3:02 am Permalink

    I followed upper indication using Labview.
    But, it doesn’t run the program.

    Can I get some example file for Labview?

  2. Avatar
    Enrique Arroyo
    Posted April 13, 2018 at 3:50 pm Permalink

    Dear Sirs,

    I have followed the indications of the application, Labviwe run fine the VI, but I seen don´t work, I mean the VI don’t shown the WinDaq data as suppose to be.

    Any comment or advice is welcome.

    Best regards,

Post a Comment

You must be logged in to post a comment.