• Who should use DAQPilot?
• Is DAQPilot free to use?
• What is the difference between the ADLINK DASK libraries and DAQPilot?
• Can I use DAQPilot with my existing ADLINK DAQ card? Does it support future DAQ products?
• I can't find the DAQPilot Task Manager after installation?
• How do I modify a pre-defined DAQPilot task?
• What is a DAQPilot task?
• How easy is it to use DAQPilot Wizard to build various DAQ applications?
• Does DAQPilot support Visual Studio .NET?
• Where can I find DAQPilot sample programs?
• How can I find additional resources for DAQPilot?
• What is the functional difference between ADLINK DAQ-LVIEW and ADLINK DAQPilot for LabVIEW?
• What is the major benefit of DAQPilot SDKs compared with competing software solutions?
• How many VI types are in LabVIEW and what are ADLINK's corresponding solutions?
• What is Express VI?
• What is a Polymorphic VI?

DAQPilot is designed for the novice to the most experienced programmer. Because DAQPilot can finish a DAQ task in minutes, it is suitable for programmers that aim to immediately program their premium ADLINK DAQ modules and integrate these tasks in their own DAQ applications.

Yes. DAQPilot is free and is the most cost-effective DAQ development tool available. DAQPilot is part of ADLINK's commitment to full support for its comprehensive line of data acquisition products.

While the ADLINK DASK libraries come in three packages (PCIS-DASK for PCI/PCIe/cPCI Series DAQ cards, D2K-DASK for DAQ/DAQe/PXI-2000 Series DAQ cards, and WD-DASK for PCI/PXI-9820 digitizer cards), DAQPilot offers a single SDK interface for all ADLINK DAQ cards. The unified DAQPilot interface offers a convenient way for programmers to develop their DAQ applications. The ADLINK DASK libraries is driver with low level API, DAQPilot is SDKs for ADLINK DAQ cards. While the ADLINK DASK libraries come in three packages (PCIS-DASK for PCI/PCIe/cPCI Series DAQ cards, D2K-DASK for DAQ/DAQe/PXI-2000 Series DAQ cards, and WD-DASK for PCI/PXI-9820 digitizer cards), DAQPilot offers a universal programming interface for all ADLINK DAQ cards. The unified DAQPilot interface offers programmers convenient development of DAQ applications.

DAQPilot's task-oriented universal APIs also provide a quicker way to finish DAQ applications without the need to understand complex programming details such as in conventional API-based development. For advanced programming, you may still refer to the DASK function reference for detailed function configurations for various hardware devices.

Yes. DAQPilot supports task-oriented universal API for a complete line of PCI, CompactPCI, and PXI data acquisition modules and will support future DAQ offerings. DAQPilot's strength lies in the fact that programming methods stay the same no matter what DAQ card/module you use.

The DAQPilot Task Manager is integrated with the ADLINK DAQMaster to form a unified and integrated interface for more efficient DAQ programming. You can launch the DAQPilot Task Manager from DAQMaster's main function bar.

To modify a pre-defined DAQPilot task:

• 1.Load a pre-defined DAQ task to the DAQPilot wizard by clicking on Start > ADLINK > DAQPilot > Open DAQPilot Task from the Windows desktop.
• 2.Use the DAQPilot wizard to modify the task parameters. You may also use the DAQMaster Task Manager to manage all created tasks.

A DAQPilot task is a DAQ task with a complete set of parameters including channels, timing, and trigger properties. A DAQPilot task represents the type of measurement to be performed. All task configuration information can be set up for use in an application. DAQPilot brings you a task-oriented programming approach with universal APIs with two ways to create a task: DAQPilot Wizard and DAQPilot API.

Very easy. With DAQPilot Wizard, you can quickly create 19 types of DAQ tasks. After creating the task, simply load the DAQPilot Task file into your DAQ application, then use the Start() function to execute the Task. For example:

HANDLE hDAQPilotTask = NULL;
hDAQPilotTask=DAQPilot_LoadTask("AOSingleShot",TRUE);
DAQPilot_Start(hDAQPilotTask);
// user can easily use DAQPilot_LoadTask to load different TASK file to
// finish different DAQ Task
printf("Wait for AO output finish.");
while(DP_STATUS_DEVICE_RUNING & DAQPilot_GetTaskStatus(hDAQPilotTask)); DAQPilot_EndTask(hDAQPilotTask);

Note:
The return values under v1.3 of DAQPilot_GetTaskStatus(hDAQPilotTask) is as follows.

v1.3:

• DP_STATUS_DEVICE_STOP (1)
  The device has stopped. You may call the Start() method to restart the task; Start() method will not automatically call Config() method before running. This is the default return value.

• DP_STATUS_DEVICE_RUNING (2)
  The device is running.

• DP_STATUS_DEVICE_DIRTY (4)
  You can use the device dirty flag to determine whether the current property has been modified since it was last saved. If the Start() method is called when the device dirty flag is true, Start() method will automatically call Config() method before running.

• DP_STATUS_DEVICE_EVENT (8)
  According to different tasks, this flag has different meanings. In AI/AO/DI/DO single shot task, it means that the AI/AO/DI/DO task is complete. In AI/AO/DI/DO continuous task, it means that the buffer is half ready. In timer interrupt task, it means that an interrupt has occurred.

In the past, to directly call ADLINK DASK DLL libraries (Native Library) with callback function, ADLINK provided all related function declarations for C#.NET and VB.NET, including complete example programs. Taking advantage of .NET, the DAQPilot Assembly (Component) comes with well-tested managed components and complete example programs for C# .NET and VB.NET. Based on .NET framework, many benefits are available, including robust exception handling mechanism to deal with both expected and unexpected errors, safety and security, garbage memory collection, type safety, array bounds, index checking, and code reuse.

From the DAQMaster Software Manager, select DAQPilot, then click on the Sample DIR button. The command opens the ActiveX, API, and .NET sample directory. You may also go direct to the sample folder using this path: C:\ADLINK\DAQPilot\Sample.

For late-breaking updates and product information, visit: http://www.adlinktech.com/MAPS/DAQPilot.html. An online demo is available to assist you when using and maximizing the DAQPilot features.

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.

For Microsoft Visual Studio users, ADLINK's DAQPilot provides a task-oriented SDK for API, ActiveX controls, and .NET Assembly equipped with an interactive setting dialog replacing the conventional properties pages. ADLINK is the only provider of an interactive setting dialog for developing DAQ application with component technology. For LabVIEW users, programmers can interactively configure ADLINK DAQ products through DAQPilot Express VI and Polymorphic VI libraries. ADLINK is the second company in the world providing the Express VI and Polymorphic solution.

• Standard VIs: => ADLINK DAQ-LVIEW PnP
  Modularized VIs customized by wiring VIs for performing: Analog Input, Analog Output, Digital I/O and Counter operations
• Express VIs: => ADLINK DAQPilot version 2
  Interactive VIs with configurable dialog page VIs for performing a task one set of VIs for all measurement types
• Polymorphic VIs: : => ADLINK DAQPilot version 2
  Polymorphic VIs accepts different data types for a single input or output terminal. 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.

Express VI provides 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 encapsulates the functionality of related standard VIs, providing developers with easy access to powerful measurement technologies through point-and-click interfaces, requiring 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 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.

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 polymorphistic 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.