ADLINK Technology MCM-204, User Manual

Page: 47 / 55

DAQ Missions 39
MCM-204
4 DAQ Missions
The MCM-204 supports various modes of operation that users can
choose from to quickly integrate into their systems.
4.1 Usage Behaviors
IEPE sensors transmit raw data to the MCM-204 which can then
be filtered to other kinds of data types that are more application
appropriate, such as overall vibration values (ISO 10816) for
mechanical vibration data. The overall vibration value data size is
greatly reduced in comparison to raw data, so the backend server
receives much less data for analysis. Data filtering is best suited to
applications requiring continual information updates at a given
time interval, such as every minute, which the user can then
review periodically.
In contrast to data filtering, some applications, such as lab testing,
require continuous raw data for analysis. However, continuous
transmission of large amounts of raw data places a heavy burden
on the backend server and takes up more network bandwidth.
Evaluate your bandwidth and application requirements carefully in
order to adopt the most suitable programming method for your
needs.
There are three major usage behaviors: Periodic Polling, Continu-
ous Data, and Passive Data. Choosing between them depends on
how frequently data must be retrieved. Figure 4-1 on page 40 can
serve as a guide for selecting the appropriate usage behavior for
system integration based on polling data frequency.
For the periodic polling mode, MCM-204 provides a REST API
and sample code in C#, Python, and JavaScript. Alternatively, for
continuous data mode, MCM-204 provides a Streaming SDK and
associated C/C++ sample code.