ADLINK MCM-216/218 Edge DAQ Deployment Configuration Guide

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.