Questions? Call us at 1-800-528-1417

Free gift with purchases over $50. Learn more > 

Cart (0)
Simply smart circuitry since 1971

ADLINK DAQPilot Support Information


DAQPilot

ADLINK Task-oriented DAQ Driver and Wizard for Windows

DAQPilot is ADLINK new generation DAQ driver and SDK for full-line DAQ products. ADLINK's DAQPilot provides task-oriented SDK for API, ActiveX controls, and .NET assembly. For LabVIEW users, ADLINK introduced DAQPilot Express VI and Polymorphic VI libraries in DAQPilot beginning in version 2. Programmers can interactively configure ADLINK DAQ products through DAQPilot Express VI and Polymorphic VI libraries. DAQPilot Express VI and Polymorphic VI libraries allow you to transfer your LabVIEW software knowledge and expertise to whom may be extremely knowledgeable of that specific applications, but not so familiar with LabVIEW.

Previously, LabVIEW™ introduced an Easy I/O and Intermediate I/O layer to traditional library to simplify common DAQ tasks. ADLINK thus provided DAQ-LVIEW PnP VI Library as a plug and play library based on its architecture. Now, with DAQPilot task-oriented VI libraries for LabVIEW, users can "Plug ADLINK, Play LabVIEW" by interactive configuration dialog for ADLINK DAQ products.

No Matter which ADLINK DAQ cards you use, DAQPilot is your start point for quick trial and advanced program development.

What ADLINK DAQPilot Offers
 
DAQPilot Version 2.0 - 2008
  •  
DAQPilot provides one Express VI enables replacement of large portions of a complex DAQ application with an interactive configuration dialog and fourteen Polymorphic VIs to support more flexible function.

DAQPilot Version 1.0 - 2007
  •  
DAQPilot support task-oriented DAQ driver and SDK for ADLINK's full line of DAQ products.
  •  
DAQPilot SDK include APIs, ActiveX controls, .NET assembly for various application development environments, including Microsoft C# .NET, Microsoft Visual Basic .NET, Microsoft Visual Basic, Microsoft Visual C++, Borland Delphi, and Borland C++ Builder.
 
 
Live Demo
    • Programming with DAQPilot .NET Assembly in Visual Studio 2005
      Here are two demonstrations on how to develop a continuous analog input application with an ADLINK DAQ module in Visual Studio 2005 and how you can take advantage of the .NET framework with DAQPilot .NET Assembly:

    • Programming with DAQPilot ActiveX Control in Visual Basic 6 ( 1024*768  7MB )
      ActiveX is a Microsoft technology to develop reusable object-oriented software components. You can use DAQPilot ActiveX control on various ADE environments such as Visual Basic, Visual C++, Borland C++ Builder, etc. This presentation shows you how to develop a single-shot analog input application with an ADLINK DAQ module in Visual Basic 6.


 
Features
    • DAQ driver with graphical interface assistance for programmers
    • Program by three approaches DAQPilot API, DAQPilot ActiveX control and .NET assembly
    • Supports Express VI for LabVIEW
    • Supports Polymorphic VIs for LabVIEW
    • Supports 32-/64-bit editions of Windows Vista/Server 2003/XP and legacy Windows 98/NT/2000
    • Supports a complete line of ADLINK DAQ cards and compatible with all ADLINK DAQ hardware functions
    • Supports various application development environments including:
            • Microsoft Visual C# .NET, Microsoft Visual Basic .NET, Microsoft Visual Basic,
            • Microsoft Visual C++, Borland Delphi, and Borland C++ Builder
    • Task-oriented approach creates your DAQ application in 3 minutes
    • One interface to hundreds of ADLINK data acquisition Cards
 
Benefits
 
 
All-In-One DAQPilot Express VI for quick start of application development
Fourteen DAQPilot Polymorphic VIs for advanced programming
Task-oriented approach to develop a DAQ application
One interface to hundreds of data acquisition Cards
Test panel to real-time check your configuration
. NET support with Managed Component
Friendly User Interface for ActiveX controls configuration and integration
Reference code generation for various programming language in a mouse click
19 DAQ tasks for the common data acquisition applications
 
All-In-One DAQPilot Express VI for quick start of application development

Express VI is designed by interactive configuration dialog boxes. Benefits include reduced wiring, and a dramatically reduced learning curve. Express VI is composed of an Express Source VI and an Express Configuration Dialog Box VI. In fact, Express VI encapsulate the functionality of related standard VIs, providing developers with easy access to powerful measurement technologies through point-and-click interfaces, whereby such interactive VIs simply require little or no programming to configure. Express VI provides an easy-to-use interface for developers who possess in-depth understanding of the application or concepts, but lack in programming experience. With Standard VIs, VIs are modularized via wiring. With Express VI, complicated wiring is already integrated as an single interface. The DAQPilot Express VI is completely compatible with various LabVIEW™ functions and with ADLINK DAQ Products.

Fourteen DAQPilot Polymorphic VIs for advanced programming

A Polymorphic VI is a collection of VIs with the same connector pane patterns. Each VI in the collection is an instance of the Polymorphic VI which provides the polymorphism ability of a node to adjust automatically to data of different representation, type, or structure. For most polymorphic VIs, the data types you wire to the inputs of the Polymorphic VI determine the instance to use. DAQPilot Polymorphic VIs thus provide a better way to perform the same operation on different data types.

 
Task-oriented approach to develop a DAQ application

Leave the complexities to DAQPilot wizard, then Use DAQPilot library to program in task-oriented concept by three approaches includes DAQPilot API, DAQPilot ActiveX control, and DAQPilot .NET Assembly.

One interface to hundreds of data acquisition Cards

The ADLINK DASK and DAQPilot are both drivers and SDKs for ADLINK DAQ cards. DAQPilot offers a single task-oriented driver and SDK interface for all ADLINK DAQ cards instead traditional three packages: PCIS-DASK, D2K-DASK, and WD-DASK. DAQPilot also provides uniform and task-oriented approach ActiveX control/.NET Assembly that supports current and future ADLINK DAQ devices.

Test panel to real-time check your configuration

Users can test their DAQ setting real time before further programming with created DAQ task specification. DAQPilot test panel supports virtual device testing so you can test the application even before you install the DAQ device.

. NET support with Managed Component

Managed code is computer instructions executed by a CLI-compliant virtual machine, such as Microsoft's .NET Framework CLR. DAQPilot .NET Assembly benefits user of .NET self-register mechanism, AUTO exception handling, AUTO garbage memory processing, AUTO type safety, etc.

Friendly User Interface for ActiveX controls configuration and integration

DAQPilot ActiveX Control and .NET Assembly supports component-based DAQ applications, DAQPilot embed wizard in property configuration page to accelerates integration with your programming environment

Reference code generation for various programming language in a mouse click

DAQPilot Task manager which integrated in DAQMaster can dynamically generate the task related C/C++ reference code based on DAQPilot library for advanced programming and integration.

19 DAQ tasks for the common data acquisition applications

DAQPilot supports four task categories and a timer/counter function. These comprise nineteen task items.

Supported products
  • ADLINK PCI/PCIe/cPCI Series DAQ Cards
    • 6202, 6208, 6216, 6308, 7200, 7224, 7230, 7233, 7234, 7248, 7250, 7252, 7256, 7258,
    • 7260, 7296, 7300, 7348, 7350, 7360, 7396, 7432, 7433, 7434, 7442, 7443, 7444, 7452,
    • 8554, 9111, 9112, 9113, 9114, 9118, 9221,9222, 9223, 9524
  • ADLINK DAQ/DAQe/PXI-2000 Series DAQ Cards
    • 2005, 2006, 2010, 2016, 2204, 2205, 2206, 2208, 2213, 2214, 2501, 2502
  • ADLINK PCI/PXI Digitizers
    • 9810, 9812, 9816, 9820, 9826, 9846
* All other photos and company names appearing herein are trademarks or tradenames of their respective companies.