How iDaq is structured

 

iDaq is designed to allow easy implementation and good manageability of any of its parts. In order to get the maximum of flexibility and to make it as dynamic and customizable as possible, iDaq is based on a module-based architecture structured on mainly two levels. It is divided in fact into two programs: iDaq Device Manager and iDaq Dock.

iDaq Device Manager is the application that acquires data from hardware, like DAQmx boards, CompactDAQ, ModBus, Siemens S7 PLC, Ethernet IP devices.

iDaq Dock is a container of Addons. An Addon is an application that processes, stores and visualizes signals and any other type of data acquired with iDaq Device Manager. The following image is a schematic representation of iDaq working principle.

 

Diagram of iDaq Structure

 

The elements in the diagram are three different kinds of modules:

  1. Addons are installable functional utilities that allow you to monitor, save and process acquired signals in many different ways. They are conceived to make iDaq able to combine independent, interchangeable tools at any time.
    Every Addon has two versions: a standalone version, that requires only iDaq Device Manager to receive data, and an iDaq Dock version, that needs iDaq Dock to run.
    Examples of iDaq Addons are Easy Datalogger and 3D Sensor Mapping.
    T4SM provides you with a wide set of ready-to-use Addons, but you could also implement your own Addons using iDaq Developer Toolkit.
    Explore Addons >
  2. Extensions are additional functionality for processing of data acquired by iDaq drivers. Examples of iDaq extensions are virtual channels and WPU (waveform processing units).  
    Explore Extensions >
  3. Drivers communicate with hardware (like DAQmx boards) and acquire data from them. They are distributed as iDaq-Driver files and must be installed in iDaq Device Manager. Examples of iDaq Drivers are S7 Driver for iDaq, Modbus Driver for iDaq, Fanuc CNC Driver for iDaq (soon on the website). 
    Explore Existing Drivers > 

iDaq Device Manager

 iDaq Device Manager handles hardware by using the Drivers, i.e. a special set of items created to acquire data from different data sources and process them in different ways. Drivers extend the number of device types supported by iDaq Device Manager. 

Components: Drivers and Extensions

COMPONENTS are modules that deal directly with signals and hardware: they are thought to increase the number of possible devices with which iDaq Device Manager can interface. Their primary purpose is to extend the capacity of acquiring, generating and elaborating signals of iDaq Device Manager according to your needs. Moreover, the module-based architecture of iDaq Device Manager allows a continuous renewal of its potentialities, so that enables it to be always up-to-date and makes it very suitable for single customers’ requests. There are different categories of components:

  1. DRIVERS enable data acquisition from several different data sources and allow you to connect a wide set of devices. Drivers can also contain CAPABILITIES that are components dedicated to performing particular functions such as acquisition, generation, and computation of different types of signals.
  2. EXTENSIONS that can be:
  • CHANNELS are components focused on the analysis of single types of signals and enable you to take advantage of many different types of signal calibration.
  • WAVEFORM PROCESSING UNITS (WPU) are components dedicated to the elaboration of data extracted from signals.

 

iDaq Dock

iDaq Dock enables you to install useful Addons, additional plug-ins that extend iDaq features, such as different ways of data processing and visualization. The opportunity of introducing new tools and increasing iDaq potentialities in such an easy way makes it a flexible and customizable solution.  Thanks to iDaq Addons, you have unlimited access to your devices, even remotely, without programming efforts. 
There are two types of Addons: 

  • EMBEDDED Addons are built-in Addons. Embedded Addons are Addons integrated into iDaq Dock; you can access them through the Addons tab in iDaq Dock main window. 
  • STANDALONE Addons are independent applications, external to iDaq and don’t need iDaq Dock. Like embedded Addons, standalone Addons communicate with iDaq Device Manager and receive data acquired by iDaq Device Manager itself.

Unlike the embedded Addons, standalone applications can be used whether iDaq Dock is installed or not. Both versions require iDaq Device Manager.
Embedded and standalone Addons can be downloaded from the following link: https://www.idaq-datalogger.com/en/products/addons.

 

How users interact with iDaq

How users interact with iDaq

 

From the diagram shown above you can see how the various parts of iDaq lend themselves to being used by more types of users. The first part, made by iDaq Device Manager with Drivers and Extensions is mainly used by engineers and technicians. Drivers and Extensions can be developed by third-party providers.

The second section composed of iDaq Dock and Addon can instead be used by the machine operator, engineer or manager in the office, depending on which Addon you choose. The Addons can also be developed by third-party providers.

 

<< Go back to iDaq Features