ADLINK MCM-204 Edge DAQ Deployment Configuration Guide

3.4 Mission Management

Mission is the core concept of MCM-204, which includes parameter sets such as sampling rate, trigger source, repetition rate, and data type. The device automatically executes the previous task after each startup (if the number of repetitions is set to 0, it means an infinite loop). You can create, delete, or switch tasks here.

3.5 System Setting

Host name modification: facilitates network recognition.

Retain network settings: Even if reset from the factory, the current IP can still be retained to avoid remote device loss.

Data persistence: By default, historical data only exists in RAM and is lost during power outages. After activation, it can be saved to a 300MB dedicated area of 4GB eMMC internally (using LRU elimination strategy).

Equipment calibration: Although calibrated at the factory, software self calibration can be performed after long-term use or temperature drift (without the need for an external signal source).

Firmware upgrade: You can upload the upgrade package (. bin file) downloaded from the official website.

Custom Algorithm Upload: Used to import user written signal processing algorithms (see Section 6 for details).

3.6 TCP Socket Configuration

MCM-204 can act as a TCP client and actively send data to remote servers. Configure server IP and ports, and map different ports for different channels. The connection status can be monitored on the interface and supports reconnecting all.

3.7 Account Management

Supports multi-user accounts and allows for the modification of default passwords (it is strongly recommended to set a separate password for each device).

DAQ task configuration and data types

4.1 Basic parameter settings

On the "Device Setting" page, users configure:

Trigger source: software trigger, analog trigger (level), digital trigger (from DI0), or front panel button.

Repetition interval: The interval (in milliseconds) between two acquisitions. Note that the complexity of the filtering algorithm may affect the actual interval.

Repetition count: 0 represents infinite loop; Warning: When using a custom algorithm for the first time, it is recommended to set it to 1 and try again to 10. After confirming that there are no errors, change it to 0.

Sampling rate and number of data points: Both determine the duration of the collection window (data points/sampling rate=time length).

4.2 Data Type (DataType)

Each analog input channel can simultaneously output multiple data types (supporting the addition of multiple DataTypes). The built-in types include:

Data type description

Raw Data ADC raw 24 bit binary complement code

Convert Voltage to Voltage Value (Unit: V)

FFT_PowerSpec power spectrum (FFT amplitude squared)

OA_g (RMS) Direct value, unit g (RMS)

OA_g (Peak) Direct value, unit g (peak value)

OA_mm/s (RMS) velocity direct frequency value (mm/s effective value)

OA_mm/s (Peak) Speed Direct Value (mm/s Peak)

OA_um (P-P) displacement frequency value (micron peak to peak)

G acceleration (requires sensor sensitivity conversion)

Customization User defined Algorithm Output

These predefined OA values strictly follow the ISO 10816 standard and can be directly used for evaluating the vibration intensity of rotating machinery.

4.3 Condition Alarm (Add Condition)

Threshold judgment can be set, and when the data exceeds the set upper and lower limits, an alarm message will be generated on the "Data Condition" page for quick identification of anomalies on site.

4.4 Mission Profile

All settings can be exported as JSON files for batch cloning to other MCM-204 devices or as backup and recovery.

Four working modes and API selection

MCM-204 provides four typical usage scenarios based on data acquisition frequency and interaction methods:

5.1 Portable DAQ/Initial Configuration (Web Console)

Directly accessing the console through a browser, manually triggering data collection and real-time viewing of waveform charts, suitable for laboratory debugging or temporary inspections.

5.2 Periodic Polling (REST API)

Suitable for routine monitoring that obtains status values every minute or hour. MCM-204 provides complete RESTful API documentation (available in the console menu), along with Python, C #, and JavaScript example code. IT engineers can easily integrate device status into enterprise monitoring systems and return data in JSON format.

5.3 Continuous Streaming SDK

If continuous collection of raw data is required (such as transient analysis or fault diagnosis), the Streaming SDK written in C/C++can be used for real-time transmission through DDS (Data Distribution Service). Note:

DDS functionality needs to be enabled in the web console.

The host and MCM-204 must be on the same network segment.

Do not use REST API to query continuous data simultaneously to avoid conflicts.

The SDK download and examples are located on the product page, and the installation path is C: ADLINK MCM MCM200 (Windows host).

5.4 Passive Data Push (TCP Socket Client)

For backend servers that do not wish to actively poll, MCM-204 can be configured as a TCP client. Once new data is generated, it will immediately establish a connection and push the data. This approach is suitable for event driven alarm or low bandwidth scenarios.