ADLINK Technology MCM-204, User Manual

Page: 27 / 55

Getting Started 19
MCM-204
2.5.1 First-Time Configuration / Portable DAQ
Use the web console to configure device information, system set-
tings, network settings, and test measurement analog input set-
tings. For portable DAQ usage, the MCM-204 has a built-in
dashboard to show the results of acquired data. The web-based
console is also a convenient tool for users unfamiliar with DAQ
behavior or programming. See “Web Console” on page 21.
2.5.2 Periodic Polling (REST API)
Many distributed machine condition monitoring applications
acquire device status periodically, for example, every minute, or
hourly. The MCM-204 retains captured data in the REST data for-
mat. Especially in IT systems, user applications frequently adopt
REST APIs because they are intuitive. The MCM-204 emulates all
functions supported by REST APIs, and the MCM-204 embedded
middleware executes related operations and transfers the filtered
data in JSON format. All queries from a REST command are han-
dled by the MCM-204 and reply accordingly. See “DAQ Missions”
on page 39.
2.5.3 Continuous Data (Streaming SDK)
Some applications need to acquire streaming data continuously.
To transmit high volumes without data loss, raw data without any
transformation is best. For users needing to access the DAQ
library directly, the Streaming SDK is the proper method. By using
the streaming API, all queried raw data may bypass the
MCM-204’s middleware and route directly to the host PC via
Ethernet. See “Continuous Data” on page 41.
2.5.4 Passive Data (TCP Socket)
For passively retrieving data, it is suitable to use a TCP socket
with the MCM-204 in client mode. Whenever data is generated,
the MCM-204 will be triggered to establish a TCP connection with
the host PC and actively transmit the data. See “Web Console” on
page 21.