8/1/2005 1

MetaDAQ

A Networked Meta Data Acquisition System

Jason P. Hanley

SEESL

University at Buffalo

8/1/2005 SEESL - University at Buffalo 2

Requirements

• Provide a common interface to setup and control multiple data acquisition devices

• Require only one person to operate all the data acquisition devices during a test

• Provide real-time viewing and analysis capabilities of test data from any data acquisition device– Allow any networked workstation to access this data

• Produce one integrated file with data from all channels regardless of what data acquisition system was used to collect them– Have all test data immediately available over network for

researchers after the test concludes• Reduce the occurrence of human error leading to loss of

non-reproducible experimental data

8/1/2005 SEESL - University at Buffalo 3

Development

• Develop a software program to control any data acquisition device– Provide a common user interface– Only require a networked workstation

• Addition drivers for DAQ devices may be needed

• Interface major data acquisition systems in the lab to this software

8/1/2005 SEESL - University at Buffalo 4

Scope of Work

• Develop a generic interface for data acquisition system

• Develop a module for each data acquisition system to implement this interface

• Build a GUI to configure and control these data acquisition devices through this interface

8/1/2005 SEESL - University at Buffalo 5

Software Components

MetaDAQ

DMM Online

Krypton PC

DVR PC

Capture Core

DVR Online

GPIB-ENET

PacificMainframe

Master Controller

Data Acquisition Device Interface

Cepoint DVR 9000Krypton K600Pacific 6000

Data Archivingand Streaming

Acquisition ControlDevice

Configuration

Graphical User Interface

8/1/2005 SEESL - University at Buffalo 6

MetaDAQ

• This is the META data acquisition program that will control all the others

• It will be a GUI application with three major tasks– Discover devices and configure them– Control the acquisition– Archive and preview the data

• Each data acquisition device will be accessed through a standard interface– There will be standard dialogs for configuration,

control, and data viewing/archiving– A device can extend or override these dialogs for

device specific configuration

8/1/2005 SEESL - University at Buffalo 7

Pacific 6000 Interface

• Use the Pacific CMD DLL– A library for interfacing with the device– Provides common configuration dialogs that

will be reused– Control and data handling will be fully

integrated at the application level and use the common UI elements

• Networking will be transparent with the use of the GPIB-ENET interface

8/1/2005 SEESL - University at Buffalo 8

Krypton K600 Interface

• DMM Online system for accessing the Krypton over the network– Use the Geoloc software as a standalone

application for device configuration– Load this configuration into the interface– Control and data handling will be fully

integrated at the application level and use the common UI elements

8/1/2005 SEESL - University at Buffalo 9

DVR Interface

• Extend the current DVR software to be accessible over the network– Provide full integration of configuration and

control– Data archiving and streaming may be handled

locally on the device because of the huge bandwidth requirements

• Low resolution previews may be implemented

8/1/2005 SEESL - University at Buffalo 10

Implementation Schedule

• Complete Design• Implement General

DAQ interface• Interface Pacific• Interface Krypton• Interface and extend

DVR• Develop GUI• Test System

• 1 week• 1 weeks

• 2 weeks• 2 weeks• 2 weeks

• 2 weeks• 1 week

Total Time

3 months

8/1/2005 SEESL - University at Buffalo 11

Work Distribution

• Jason– Design– DAQ Interface– Pacific– Krypton– Testing

• Goran

– DVR– GUI– Testing

Total Time: 2 months

8/1/2005 SEESL - University at Buffalo 12

Work Plan and Needs

• Start development the beginning of August and complete by the beginning of October

• Will need access to DAQ systems during development– In between tests in the lab

• Use in real lab test as soon as possible to catch bugs and validate operation