ADLINK MCM-216/218 is a standalone Ethernet data acquisition (DAQ) module designed for distributed machine condition monitoring. It is equipped with an ARM Cortex-A9 1GHz processor, 1GB DDR3 memory, and 4GB eMMC storage. It supports 8 or 16 channel 16 bit analog inputs (up to 250 kS/s, configurable voltage/current input range), 2-channel analog outputs, 4-channel isolated digital inputs, and 4-channel isolated digital outputs. It also integrates temperature sensor inputs, dual gigabit Ethernet (supports cascading), USB 2.0, and RS-485 interfaces. Its built-in web console supports various data exchange methods such as RESTful API, TCP Socket client, and Modbus TCP server. It can execute custom filtering algorithms on the edge side, upload only key feature values, and significantly reduce network bandwidth and cloud computing pressure. This article is based on the user manual and systematically outlines hardware installation, network configuration, web console operation, DAQ task and trigger mode settings, Modbus integration, custom algorithm import, and common troubleshooting to assist engineers in quickly completing on-site deployment and system integration.
Product positioning and typical applications
MCM-216/218 is designed specifically for OT field automation and is suitable for:
Vibration and temperature monitoring of rotating machinery (motors, pumps, fans)
Process signal (4-20mA sensor) acquisition and threshold alarm
Distributed device status detection (aggregated to SCADA/cloud platform via Ethernet)
Portable data recording (real-time viewing of waveforms through a web dashboard)
Its "breakpoint resume" feature: the system automatically resumes its previous operating state after power failure, without the need for manual intervention, making it suitable for unmanned sites.
Hardware installation and I/O connection
2.1 Unpacking and Mechanical Installation
The standard packaging includes the host, DIN rail installation kit (including two flat head screws), 3-meter temperature sensor, and quick start guide. Optional wall bracket (P/N 34-51112-0000) and 40W AC-DC adapter (P/N 31-62138-0000).
Dimensions: 110.5 (length) x 40 (width) x 126.5 (height) mm, metal casing IP30.
Installation method: DIN rail (standard) or wall mounted (optional). Before installation, ensure that the ambient temperature is between 0 ° C and 70 ° C, and the humidity is less than 95% non condensing.
2.2 Power Connection
Power supply range: 9~30 VDC, connected through 3-pin spring terminals (positive, negative, grounded).
Power consumption: MCM-216 maximum 5.5W, MCM-218 maximum 6.7W.
Key operation: Be sure to connect/disconnect the power cord in the power-off state, and use a Phillips screwdriver to press the orange slot to release the wire.
After power on, if the front panel PWR LED (red) is constantly on, it indicates that the power supply is normal; The SYS LED will flash red first and then turn stable green after about 35 seconds, indicating that the system is ready. If SYS is always red, it indicates a system error.
2.3 I/O Wiring Guide
Analog input (16/8 channels)
Connector: 2 × 14 pin spring terminals (see manual figure 1-8).
Supports single ended or pseudo differential input, which can be selected through the web console.
Voltage range: ± 10V, ± 2.5V, ± 1.25V, ± 312.5mV; Current range: 0~20mA (requires external 249 Ω resistor, integrated inside the module).
Sensor type: 0.5~4.5V, 1~5V, 0~5V, 0~10V voltage output type, or 4~20mA current loop.
Input impedance: voltage mode>1G Ω, current mode 249 Ω.
Digital I/O (4 DI+4 DO)
Connector: Independent 14 pin terminal (Figure 1-9), using D.GND as the common ground.
DI logic level: Low<0.8V, High>2.0V (maximum 5V), input frequency up to 500 kHz (only DI0 supports tachometer speed measurement).
DO is an open drain output that requires an external pull-up power supply (5-35V), with a maximum current of 250mA per channel (100% duty cycle) and overvoltage protection (-50~+50V).
temperature sensor
Comes with TI LMT01 digital temperature sensor (-50~150 ° C), 3-meter cable, plug in dedicated 2-pin terminal to read environmental/device temperature.
Ethernet cascade
Two RJ45 ports share the same IP, either can connect to a host, and the other is used to cascade the next device (only supports chain topology, ring topology is prohibited).
The default static IP is 169.254.1.1, which can also be accessed through DHCP or by setting the host name.
First launch and login to the web console
Set the PC network card to DHCP or link local address (169.254. x.x), and connect the MCM and PC with an Ethernet cable.
Power on and wait for the SYS LED to turn green (approximately 35 seconds).
Browser access http://169.254.1.1 Or the device host name (such as http://mcm216-xxxx See packaging label).
The default username is administrator, and the password is Adlink6166 (it is recommended to change it after the first login).
The web console is the core tool for configuration, monitoring, and debugging, without the need to install any software.

Detailed Explanation of Core Function Configuration
4.1 Network and System Settings (System Manager)
Network Setting: IP mode (static/DHCP) and hostname can be modified. After enabling 'Keep Network Setting', network parameters are retained even if the factory settings are restored to avoid remote device loss.
Change Password&Account Management: Supports multi-user permission management, it is recommended to set a unique password for each device.
System Setting:
System Restart: Soft restart device (remote maintenance).
Data Keep: By default, historical data only exists in RAM and is lost in case of power failure; After activation, save the data to the internal 300MB storage space and overwrite it in a loop.
Firmware Upgrade/Customization Library Upload: Used for firmware upgrade and custom algorithm import (see below).
4.2 DAQ Task Configuration (Mission Management)
Mission "defines a set of collection parameters (channel, sampling rate, triggering method, data type, output method) that automatically resume execution after device restart, achieving unmanned operation.
AI Data Mode
One Shut Mode: Periodically collect data according to the set Repeat Interval (ms) and Repeat Times (0 is infinite).
Streaming Mode: Requires TCP Socket to continuously stream raw data to a specified server, ignoring repetition intervals/times.
Trigger Modes
Supports six triggering methods, flexibly adapting to different measurement scenarios:
Post Trigger: Collection begins after triggering an event.
Pre Trigger: Collect data before triggering (N samples, N≤8k), Suitable for capturing precursors of sudden events.
Delay Trigger: After triggering, delay the specified count before collecting (maximum delay count is 2 Ω² -1).
Middle Tiger: Collect M and N samples before and after triggering (M+N ≤ 8k).
Gated Trigger: Level controlled acquisition (collected during high/low level periods, suspended when stopped).
Post/Delay Trigger with Re trigger: Multiple triggers, fixed length collected each time, repeated a specified number of times.
The trigger source can be selected from software, digital trigger (external DI), analog trigger (level comparison), or front panel button.
Sampling rate and Channel Gain Queue
The maximum total sampling rate is 250 kS/s, which can be allocated between channels as needed.
By setting the weight of each channel through 'Queue Content', such as AI0 weight 2, AI1 weight 1, AI2 weight 6, the actual sampling rate will be proportionally allocated. This is very practical for multiple sensors with different bandwidth requirements.
Data Type (DataType)
Each AI channel can choose to output:
Raw Data: ADC raw 16 bit binary complement.
Voltage: Convert to voltage value (or current value).
FFT_PowerSpec: Power spectrum (FFT operation result).
Customization: User defined algorithm (requires uploading. so library).
At the same time, multiple DataTypes can be added to the same channel (such as simultaneously outputting Raw and Voltage), making it convenient for different applications.
Add Condition Alarm
Set threshold comparisons (greater than, less than, interval) for each data type, and once triggered, record the event on the Data Condition page for subsequent troubleshooting.
4.3 Modbus TCP Server Mode
MCM-216/218 can be used as a Modbus TCP Slave and seamlessly integrated with SCADA systems.
Enable Modbus TCP, set the port number (default 502) and Slave ID.
The data type of each AI channel is automatically mapped to a hold register (Function Code 4) with a starting address of 30001, and each data occupies 2 registers (32-bit floating-point).
DI/DO is accessed through Coil or Discrete Input (Function Code 1/2/5/15).
The configuration page clearly displays the starting address of each data type for easy PLC programming.
4.4 TCP Socket Client (Active Upload)
For scenarios that require active data push (such as cloud reception), TCP Socket connections can be configured:
Set remote server IP and port to map different AI channels to different ports.
Once the DAQ task runs, the data is automatically sent to the server (in JSON or binary format).
Support reconnection after disconnection (Re Connect All).
4.5 Data History and Real time Dashboard
Data Capture: Real time display of waveforms, optional voltage or raw values, suitable for on-site debugging.
Data History: Query stored historical data by time period (Data Keep needs to be enabled).
The configuration can be exported as Mission Profile (. json) for easy backup or bulk deployment.
Custom filtering algorithm import (edge computing)
MCM-216/218 supports users to write C/C++algorithms, compile them into shared libraries, and upload them to achieve edge feature extraction (such as RMS, peak, mean, frequency domain features), only uploading results instead of raw data, saving bandwidth.
Import steps (pages 56-58 of the manual):
Download the Linaro ARM cross compilation toolchain (gcc-linaro-6.2.1).
Download CustomizadAlgo.zip from the official website, which includes sample programs (CalRMS and CalStatistical).
After decompression, place the toolchain and sample folder in the same path, and execute make to generate customAlgo.so.
Upload the file through the web console "System Setting → Customization Library Upload".
After logging in again, select "Customization" in the Data Type of the DAQ task to call the custom function.
If the algorithm requires parameters, parameter items can be configured in the interface.
This feature makes MCM a true edge intelligent node, especially suitable for specialized scenarios such as vibration analysis and bearing fault diagnosis.
Common troubleshooting and solutions
6.1 Unable to access web console
Check if the SYS LED is green (if it is red, the system is incorrect and needs to be restarted).
Confirm that the PC and device IP are in the same network segment (default 169.254.1.1), and disable VPN or other virtual network cards.
Attempt to access using the host name (if there is DNS on the network).
If you forget the IP, you can reset the pinhole (press with a paper clip for 3 seconds) to restore the factory settings (note that if "Keep Network Setting" is enabled, the IP will be retained and can be disabled first).
6.2 Abnormal or deviated analog input readings
Confirm that the input type (voltage/current) and range settings are consistent with the actual sensor.
Check wiring: Single ended mode requires common ground (A.GND), and pseudo differential requires separate connection of signal+and signal -.
If using current mode, confirm that an external 249 Ω resistor (already integrated internally) is connected and the sensor is two-wire active.
Performing device calibration (System Setting → Device Calibration) can eliminate long-term drift.
6.3 Digital output unable to drive load
Check if the external power supply (5-35V) is connected to the DO common terminal and if the load is connected in series between the output and the power supply.
Confirm that the current does not exceed 250mA, overload may trigger protection (power off and restart required).
Measure the voltage of the output pin to ground with a multimeter and confirm that the logic state is correct.
6.4 Modbus TCP communication unresponsive
Confirm that the Modbus TCP service is enabled and the port is not blocked by the firewall.
Check if the Slave ID matches the client request.
Use tools such as Modbus Poll to read the hold register address 30001 and subsequent, and verify the data format (Float or ∝).
6.5 TCP Socket data not actively sent
Check if the remote server IP and port are correct and if the server is listening.
Check the Socket connection status (Status column), if disconnected, manually click Re Connect All.
Confirm that the DAQ task mode is Streaming or One Shu (repeat interval needs to be configured).
6.6 System overheating or frequent restarts
Check if the ambient temperature exceeds 70 ° C, ensure good ventilation, and avoid stacking and installing in enclosed cabinets.
Verify that the power supply voltage is stable and the ripple is less than 5%.
Check the system information of the web console. If the CPU load is over 90% for a long time, consider reducing the sampling rate or decreasing the channels.
Maintenance and backup suggestions
Regularly backup Mission Profile (. json) and custom algorithm library (. so), and store them on PC or cloud.
Read the release instructions before upgrading the firmware and verify compatibility on the testing device.
The temperature sensor cable should avoid excessive bending and the connector should be checked regularly for oxidation.
If the equipment is powered off for a long time, run it on every six months to maintain the activity of the electrolytic capacitor.
