# MCM-216/218

Standalone Ethernet DAQ for Distributed Machine Condition Monitoring

User’s Manual

![Exterior view of a ADLINK MCM-216 industrial control unit with visible ports and connectors (no readable text beyond branding)](.mcm-216-218-50m-00024-1000-10/13d64891be557ff670f26300839fd79ba153aad47e2e5759aef255f23b2f136a.jpg)

Manual Rev.: 1.0

Revision Date: May 10, 2021

Part No: 50M-00024-1000

Revision History

<table><tr><td>Revision</td><td>Release Date</td><td>Description of Change(s)</td></tr><tr><td>1.0</td><td>2021-05-10</td><td>Initial Release</td></tr></table>

# Preface

# Copyright © 2021 ADLINK Technology Inc.

This document contains proprietary information protected by copyright. All rights are reserved. No part of this manual may be reproduced by any mechanical, electronic, or other means in any form without prior written permission of the manufacturer.

# Disclaimer

The information in this document is subject to change without prior notice in order to improve reliability, design, and function and does not represent a commitment on the part of the manufacturer.

In no event will the manufacturer be liable for direct, indirect, special, incidental, or consequential damages arising out of the use or inability to use the product or documentation, even if advised of the possibility of such damages.

ADLINK is committed to fulfill its social responsibility to global environmental preservation through compliance with the European Union's Restriction of Hazardous Substances (RoHS) directive and Waste Electrical and Electronic Equipment (WEEE) directive. Environmental protection is a top priority for ADLINK. We have enforced measures to ensure that our products, manufacturing processes, components, and raw materials have as little impact on the environment as possible. When products are at their end of life, our customers are encouraged to dispose of them in accordance with the product disposal and/or recovery programs prescribed by their nation or company.

![Symbol of a trash bin crossed with a diagonal line, no text or labels present](.mcm-216-218-50m-00024-1000-10/7fd5ed63208bb71a8980a60ba4a637bd8b5a75f1df5b1bfbe56d78c7e27f964f.jpg)

Battery Labels (for products with battery)
![Symbol of a trash bin crossed out by two diagonal lines (no text or numbers present)](.mcm-216-218-50m-00024-1000-10/d87f32f6eacdefe0954dcce8a1f0c992c664bfe0a068d380a08660d5b4b2eb36.jpg)

![Recycling symbol icon with three chasing arrows inside a square frame (no text or labels)](.mcm-216-218-50m-00024-1000-10/3e8caa007f8cb6893c05699292aabbe8a88924c2275d0ad5d32666225f285276.jpg)

Li-ion

![RECYCLE\nRBRC\nLi-ion\n7.800.822.8837](.mcm-216-218-50m-00024-1000-10/eff6db4ffb0afd0f78cc7744de0482ee70005c02fa6faecbbd0b2a4aae3f09cd.jpg)

![Abstract geometric pattern with interlocking X and Y shapes (no text or symbols)](.mcm-216-218-50m-00024-1000-10/c63a35e3ea689e585e6ecf6b45747848d58312de9b5d3034d059ead39e7fa702.jpg)

ᘄ㟁ụㄳᅇᨲ

# California Proposition 65 Warning

![The image shows a standard warning sign: a yellow equilateral triangle with a thick black border. In the center of the triangle is a large black exclamation point.](.mcm-216-218-50m-00024-1000-10/02524d20415dee9ba529ceb553de3c3ed470f95f81204aa2863141ba385af5f1.jpg)

WARNING: This product can expose you to chemicals including acrylamide, arsenic, benzene, cadmium, Tris(1,3-dichloro-2-propyl)phosphate (TDCPP), 1,4-Dioxane, formaldehyde, lead, DEHP, styrene, DINP, BBP, PVC, and vinyl materials, which are known to the State of California to cause cancer, and acrylamide, benzene, cadmium, lead, mercury, phthalates, toluene, DEHP, DIDP, DnHP, DBP, BBP, PVC, and vinyl materials, which are known to the State of California to cause birth defects or other reproductive harm. For more information go to www.P65Warnings.ca.gov.

# Trademarks

Product names mentioned herein are used for identification purposes only and may be trademarks and/or registered trademarks of their respective companies.

# Conventions

Take note of the following conventions used throughout this manual to make sure that users perform certain tasks and instructions properly.

![The image displays a white icon of a document or piece of paper with its top-right corner folded down. Faint grey horizontal lines run across the surface of the paper. A large, bold red checkmark is superimposed over the center of the document.](.mcm-216-218-50m-00024-1000-10/222083fd7f3e7a30e74d0fc36a238627312afcaf9fdd5adeffcb99aee3b6dee3.jpg)
NOTE:

Additional information, aids, and tips that help users perform tasks.

![The image displays a yellow triangular warning sign with a thick black border. In the center, there is a large black exclamation mark.](.mcm-216-218-50m-00024-1000-10/63304fba8e7b02bf9f78fea0f1d4cc5126cd2b7fb05b6427c914f3a48e7ecf84.jpg)
CAUTION:

Information to prevent minor physical injury, component damage, data loss, and/or program corruption when trying to complete a task.

![The image displays a red, upward-pointing triangle containing a large white exclamation point in its center. A black horizontal line runs across the very top edge of the image, intersecting the upper tip of the red triangle. The background is white.](.mcm-216-218-50m-00024-1000-10/68dcb59093808f8c4b16341b4675d62a0fb250df04ecec03034c876f834a4d89.jpg)
WARNING:

Information to prevent serious physical injury, component damage, data loss, and/or program corruption when trying to complete a specific task.

# Table of Contents

# Preface ...... iii

# List of Figures ......... ..... vii

# 1 Introduction ....

1.1 Features...... 2
1.2 Applications .... 2
1.3 Specifications... 3

1.3.1 General Specifications.. 3
1.3.2 Analog Input .. 3
1.3.3 Isolated Digital I/O ... 4
1.3.4 Analog Ouptut Specifications .... 5
1.3.5 Mechanical .. 5
1.3.6 Environmental.. 6

1.4 Mechanical Drawings... 7

1.4.1 Dimensions.....
1.4.2 DIN Rail Mount .. ... 11
1.4.3 Wall Mount.... .. 12

1.5 I/O Connectors..... 14

1.5.1 Analog Input and Analog Output . .. 14
1.5.2 Digital Input and Output. .. 15
1.5.3 Temperature Sensor Input. .. 15
1.5.4 Reset Pin for Factory Default . . 16
1.5.5 Ethernet Ports... . 17
1.5.6 LED Indicators .. .. 17
1.5.7 USB Ports ...... ... 17

# 2 Getting Started ........ 19

2.1 Unpacking the MCM-216/218 . 19
2.2 Connecting to I/O ..... 19
2.3 Connecting/Disconnecting Power..... . 20

2.4 Checking Device Status..... . 20
2.5 Usage Scenarios... . 20

2.5.1 First-Time Configuration / Portable DAQ .................. 21
2.5.2 Periodic Polling (REST API) . .. 21
2.5.3 TCP Socket for Streaming ...... .. 21
2.5.4 Passive Data (TCP Socket)..... .. 21

# 3 Web Console ......... ... 23

3.1 Web Console Login...... 23
3.2 Web Console Menu .. 25

3.2.1 Information/System Information.. . 27
3.2.2 Mission Manager/Peripheral. .. 28
3.2.3 Data Manager/Data History ..... .. 29
3.2.4 Mission Manager/Mission Management .. . 29
3.2.5 System Manager/Change Password .. .. 30
3.2.6 System Manager/Account Management.. .. 30
3.2.7 System Manager/Network Setting ......... .. 31
3.2.8 System Manager/System Setting ...... .. 32
3.2.9 Data Manger/TCP Socket (for one-shut query mode)34
3.2.10 Device Manager/Modbus TCP Server.... .. 35

3.3 DAQ Mission ..... 40

# 4 DAQ Missions......... ... 53

4.1 Usage Behaviors... 53

4.1.1 Web Console .. . 54
4.1.2 Periodic Polling ....... .. 55
4.1.3 Passive Data... .. 55

4.2 Custom Filtering Algorithms..... 5 6

# Important Safety Instructions......... .. 59

# Getting Service ...... ...... 61

# List of Figures

Figure 1-1: Front View . 7

Figure 1-2: Top View.... . 8

Figure 1-3: Left Side View... . 9

Figure 1-4: Right Side View .. . 10

Figure 1-5: DIN Rail Mount Dimensions .. .. 11

Figure 1-6: Wall Mount Dimensions... .. 12

Figure 1-7: Wall Mount Assembly ..... .. 13

Figure 1-8: Analog Input/Output Connector .. . 14

Figure 1-9: Digital Input/Output Connector . . 15

Figure 3-1: Web Console Login Page... . 24

Figure 3-2: Web Console Welcome Page..... .. 26

Figure 3-3: Menu Icon.. . 26

Figure 3-4: System Information.... .. 27

Figure 3-5: Peripheral Devices .. .. 28

Figure 3-6: Data History ..... .. 29

Figure 3-7: Mission Management . . 29

Figure 3-8: Change Password .. .. 30

Figure 3-9: Account Management.. .. 30

Figure 3-10: Network Settings . .. 31

Figure 3-11: System Settings.... . 32

Figure 3-12: Upload Customization/Firmware Files.... . 33

Figure 3-13: TCP Socket .. . 34

Figure 3-14: Modbus TCP Server ... .. 35

Figure 3-15: Data Types for Modbus TCP . .. 36

Figure 3-16: Modbus TCP Created Data Types .. 37

Figure 3-17: Data Value Starting Address Allocation...... .. 38

Figure 3-18: Modbus Function Codes.. . 39

Figure 3-19: Device Configuration ... .. 40

Figure 3-20: Post Trigger without Retrigger.. ... 41

Figure 3-21: Pre-trigger Mode Operation (valid trigger only) ........ 42

Figure 3-22: Pre-trigger Mode Operation (w/ invalid trigger) ........ 42

Figure 3-23: Delay-Trigger Mode Operation .. .. 43

Figure 3-24: Middle-Trigger Acquisition ... .. 43

Figure 3-25: Gated Trigger . .. 44

Figure 3-26: DataType .... ... 46

Figure 3-27: Add Condition.. .. 48

Figure 3-28: Data Capture .. .. 50

Figure 3-29: Device Settings.... .. 50

Figure 3-30: Apply a New Mission .. .. 51

Figure 4-1: Operational Modes . . 54

Figure 4-2: RESTful API... . 55

# 1 Introduction

With the advent of IoT, more field devices are connecting to the Internet. Instead of being distributed at each field site, systems can be monitored and managed from a central control room. In this scenario, machine condition monitoring systems play a crucial role. Monitoring devices are typically deployed at the OT site, but by using an Ethernet-based data acquisition system (DAQ), machine conditions can be monitored remotely by IT staff.

The ADLINK MCM-216/218 is a standalone Ethernet DAQ that acquires voltage and current signals from a monitored machine which represent the machine status, with a threshold setting mechanism reporting important results to the backend server. This in turn dramatically reduces network bandwidth traffic as well as the backend server’s computing burden.

The MCM-216/218 is designed for on-site process automation in the field. When recovering from a power failure, the system will automatically resume its previous running state. The MCM-216/218's compact size also makes it easy to install in the limited confines of an electrical control cabinet.

# 1.1 Features

X Standalone Ethernet DAQ for edge computing
X RESTful API reports machine conditions to IT system
X TCP socket client mode for continuous data acquisition
X Built-in web console for easy configuration and to facilitate use as a portable DAQ
X Supports Modbus TCP server mode to upload data to SCADA system
X Supports custom filtering algorithms for edge data
X 8- or 16-channel, 16-bit analog input up to 250 kS/s
X System automatically resumes its previous running state upon power recovery
X 1x RS-485 port for serial communication with Modbus RTU protocol
X 8-channel isolated digital input/output
X Two 1 Gb Ethernet ports for cascading

# 1.2 Applications

X Distributed machine condition monitoring
X Machine status detection through voltage and current signal

# 1.3 Specifications

# 1.3.1 General Specifications

<table><tr><td colspan="2">System Specifications</td></tr><tr><td>Ethernet (1 Gb)</td><td>2x RJ-45 Ethernet ports(1 IP, Ethernet cascade when powered on)</td></tr><tr><td>MCU</td><td>ARM Cortex A9 1.0 GHz</td></tr><tr><td>NAND Flash (eMMC)</td><td>4 GB</td></tr><tr><td>Memory</td><td>DDR3 RAM 1 GB</td></tr><tr><td>USB</td><td>2x USB 2.0 (for Wi-Fi dongle only)</td></tr><tr><td>Power Supply</td><td>9 to 30 VDC power input(optional: 40W AC-DC adapter, P/N 31-62138-0000)</td></tr><tr><td>Power Consumption</td><td>MCM-216: 5.5 W max.MCM-218: 6.7 W max.</td></tr><tr><td>Communication Interfaces</td><td>Web console, RESTful API, TCP socket(client mode)</td></tr><tr><td>Digital Temperature Sensor (TI LMT01)</td><td>-50°C to 150°C (with 3 meter cable)</td></tr></table>

# 1.3.2 Analog Input

<table><tr><td colspan="2">Analog Input Specifications</td></tr><tr><td>Number of Channels</td><td>8 for MCM-218, 16 for MCM-216</td></tr><tr><td>Resolution</td><td>16-bit</td></tr><tr><td>Maximum Sampling Rate</td><td>250 kS/s and can be shared by selected channels.100 KHz for multi-channel gain queue</td></tr><tr><td>Input Range (voltage)</td><td>±10V, ±2.5V, ±1.25V, ±312.5mV</td></tr><tr><td>Input Range (current)</td><td>0 to 20mA</td></tr><tr><td>Input Configuration</td><td>16 single-ended, or 8 pseudo-differential</td></tr><tr><td>Input Coupling</td><td>DC</td></tr><tr><td>Input Impedance</td><td>1 GΩ, 249.0 Ω (input resistor) for current mode</td></tr><tr><td>Sensor Type</td><td>Voltage: 0.5 to 4.5V DC, 1 to 5V DC, 0 to 5V DC,0 to 10V DCCurrent: 4 to 20mA</td></tr><tr><td>Offset Error</td><td>Voltage mode: ±1 mV (± 10 V)Current mode: ±0.01 mA (typical)</td></tr><tr><td>Gain Error</td><td>Voltage mode: ±0.05% of FSR (± 10 V)Current mode: ±0.13% of FSR (typical)</td></tr><tr><td>-3dB Bandwidth</td><td>&gt;100 Hz</td></tr><tr><td>Flatness</td><td>±0.1dB (20 Hz to 30 KHz)</td></tr><tr><td>Trigger Sources</td><td>Software, digital trigger, analog trigger, built-in button</td></tr><tr><td>Overvoltage Protection</td><td>±15 V</td></tr><tr><td>Input Impedance</td><td>MCM-216: &gt;1G ohmMCM-218: ±249 ohms</td></tr><tr><td>CMRR</td><td>105 dB for ±1.25 V &amp; ±0.3125 V95 dB for ±2.5 V85 dB for ±10 V</td></tr><tr><td>SFDR</td><td>100 dB for ±10 V, Diff</td></tr><tr><td>THD</td><td>103 dB for ±10 V, Diff</td></tr><tr><td>SINAD</td><td>86 dB for ±10 V, Diff</td></tr><tr><td>SNR</td><td>87 dB for ±10 V, Diff</td></tr><tr><td>ENOB</td><td>14-bit for ±10 V, Diff</td></tr></table>

# 1.3.3 Isolated Digital I/O

<table><tr><td colspan="2">Isolated Digital I/O Specifications</td></tr><tr><td>Number of I/O</td><td>4-ch digital input and 4-ch digital output</td></tr><tr><td>Digital Type</td><td>TTL input: 0-5 V for DI / Open drain for DO</td></tr><tr><td>Input Logic Level</td><td>Logic low:  $VIL = 0.8$  V max.,  $IIL = 0.2$  mA max.Logic high:  $VIH = 2.0$  V min.,  $IIH = 0.2$  mA max.</td></tr><tr><td>Supplied Voltage</td><td>5 to 35V DC (for DO open drain)</td></tr><tr><td>Input Frequency Range</td><td>500 KHz for 1 μs pulse</td></tr><tr><td>Max. Sink Current</td><td>250 mA @ 100% duty (per channel)</td></tr><tr><td>Overvoltage Protection</td><td>DO: -50V to +50V; DI: 0V to +5V</td></tr><tr><td>Supported Modes</td><td>Static digital input/outputTachometer support (DI 0 only; range: 0.6 Hz to 500 kHz; 500 kHz for 1 microsecond)External digital trigger in</td></tr></table>

# 1.3.4 Analog Ouptut Specifications

<table><tr><td colspan="2">Analog Ouptut Specifications</td></tr><tr><td>Resolution</td><td>16-bit</td></tr><tr><td>Number of Channels</td><td>2 channels for voltage and current</td></tr><tr><td>Maximum Update Rate</td><td>100 Ksps and settling time 10 μs</td></tr><tr><td>Output Range</td><td>AO Current output: Maximum Load: 600 ohmAO Voltage Output Range: ±10 VAO Current Output Range: 0 to 20mA, No waveform generator support</td></tr><tr><td>AO Accuracy: Offset Error</td><td>Voltage mode: ±0.6mV, 2LSBCurrent mode: ±1μA, 3LSB</td></tr><tr><td>AO Accuracy: Gain Error</td><td>Voltage mode: ±0.05% FSRCurrent mode: ±0.05% FSR</td></tr><tr><td>INL</td><td>≤1LSB</td></tr><tr><td>DNL</td><td>≤1LSB</td></tr><tr><td>Output Driving Capacity</td><td>±5 mA</td></tr><tr><td>Slew Rate</td><td>2.0 V/μs</td></tr><tr><td>Settling Time(0.1% of Full Scale)</td><td>10 μs for 100 Ksps</td></tr><tr><td>Rising Time</td><td>10 μs</td></tr><tr><td>Falling Time</td><td>10 μs</td></tr></table>

# 1.3.5 Mechanical

<table><tr><td colspan="2">Mechanical Specifications</td></tr><tr><td>Dimensions</td><td>110.5 (L) x 40 (W) x 126.5 (H) mm</td></tr><tr><td>Connectors</td><td>2x 6-pin and 2x 14-pin spring-type terminal block</td></tr><tr><td>Front Panel LEDs</td><td>4</td></tr><tr><td>Housing</td><td>Metal, IP30</td></tr><tr><td>Mounting</td><td>DIN rail mount kit(optional: wall mount kit, P/N 34-51112-0000)</td></tr></table>

# 1.3.6 Environmental

<table><tr><td colspan="2">Environmental Specifications</td></tr><tr><td>Operating Temperature</td><td>0°C to 70°C (32°F to 158°F)</td></tr><tr><td>Storage Temperature</td><td>-20°C to 85°C (-4°F to 185°F)</td></tr><tr><td>Humidity</td><td>Approx. 95% @ 40°C (non-condensing)</td></tr><tr><td>Vibration</td><td>Operating: 5 Grms, 5-500 Hz, 3 axes</td></tr><tr><td>Shock</td><td>Operating: 100 G, half sine 11 ms duration</td></tr><tr><td>EMC</td><td>EN61000-6-4/EN61000-6-2</td></tr><tr><td>EMI</td><td>FCC Part 15B Class A, CISPR 32</td></tr><tr><td>EMS</td><td>IEC 61000-4-2 ESD: Contact: 4 kV; Air: 8 kVIEC 61000-4-3 RS: 80 MHz to 1.0 GHz, 10 V/mIEC 61000-4-4 EFT: Power: 2 kV; Signal 2 kVIEC 61000-4-5 Surge: Power 0.5 kV; Signal 1 kVIEC 61000-4-6 CS: 0.15 MHz to 80 MHz, 10 VIEC 61000-4-8 PFMF</td></tr><tr><td>Safety</td><td>IEC 61010-1, IEC 61010-2-201 (pending)</td></tr></table>

# 1.4 Mechanical Drawings

# 1.4.1 Dimensions

![40\nADLINK\nPWR\nSYS\nI/O\nUSB\n126.50\nGND\nD-/B\nD-/A\nGND\nMCM-216\n+ -](.mcm-216-218-50m-00024-1000-10/16d772aa218779b65343a41eb72ff590658079ebb5ac38d28b7d71ce6e46a7d7.jpg)

Units: mm

Figure 1-1: Front View

Units: mm

![40\n111.65\n9-30 V+\nVDC V-\n2 1\nRESET\nFn](.mcm-216-218-50m-00024-1000-10/cbabd506652efe2633e8fc439a54757e1b34bd74f1a511359d3ea71c277ff7ed.jpg)

Figure 1-2: Top View

![Units: mm\n111.65\n126.50\nAO 1\nA.GND\n8 (0-)\n9 (1-)\n10 (2-)\n11 (3-)\n12 (4-)\n13 (5-)\n14 (6-)\n15 (7-)\nA.GND\nA.GND\nA.GND](.mcm-216-218-50m-00024-1000-10/ee7ce2cf2863506f454b9f4c36321f18a15feac2bf4ba12ff30d60e3e9e02549.jpg)

Figure 1-3: Left Side View

![Units: mm\n111.65\n126.50\n0 AO\n0 AGND\n0 (0+)\n1 (1+)\n2 (2+)\n3 (3+)\n4 (4+)\n5 (5+)\n6 (6+)\n7 (7+)\nSENSE\nAGND\nAGND](.mcm-216-218-50m-00024-1000-10/7c5d88acd0a93dd12897049980039e02d1e312bd22d321884f691960b3d4afec.jpg)

Figure 1-4: Right Side View

# 1.4.2 DIN Rail Mount

The DIN rail mount may be attached to the MCM-216/218 using two flat head screws (included).

![15\n89.18\n80.43\n78.38\n70.75\n41.1](.mcm-216-218-50m-00024-1000-10/1362e7e2debc072d782a9049241ebd248bab985944d5622b98a02b42a82c6543.jpg)

Figure 1-5: DIN Rail Mount Dimensions

# 1.4.3 Wall Mount

The optional wall mount bracket may be attached to the MCM-216/218 via four pan head screws (included with wall mount kit, P/N 34-51112-0000; see Figure 1-7 on page 13).

![80.0\n61.6\n20.0\n5.0\n70 100 106\nR5\nØ 5.2\nØ 4.5\nUnits: mm](.mcm-216-218-50m-00024-1000-10/185d6bef061ce7c353383eb4690f0113c5f264e765b33ac633c1575a7c13155b.jpg)

Figure 1-6: Wall Mount Dimensions

![Technical line drawing of an electronic device chassis with mounting brackets and internal components (no text or symbols)](.mcm-216-218-50m-00024-1000-10/ce8157505488fd92c4133efdb3329122e581a1dcbf1a4259106f656dbe028c51.jpg)

Figure 1-7: Wall Mount Assembly

# 1.5 I/O Connectors

The MCM-216/218 provides rich peripherals, including:

X 8 or 16 analog inputs
X 4 digital input and 4 digital output connections
X 1 RS-485 port
X 1 temperature sensor input
X 2 USB hosts (for Wi-Fi dongle only)
X 1 hotkey for triggering
X 1 reset pin for restoring the device to factory default settings
X 2 Ethernet ports for host connection and cascading
X 4 LED indicator lights

# 1.5.1 Analog Input and Analog Output

The MCM-216/218 module is equipped with a 2x14-pin terminal block for analog output and analog input. There are 2 analog output channels and 16 channels for analog input. The A.GND pin is for grounding.

![AO 1\nA.GND\n8 (0-)\n9 (1-)\n10 (2-)\n11 (3-)\nAI\n12 (4-)\n13 (5-)\n14 (6-)\n15 (7-)\nA.GND\nA.GND\nA.GND\n0 AO\nA.GND\n0 (0+)\n1 (1+)\n2 (2+)\n3 (3+)\n4 (4+)\n5 (5+)\n6 (6+)\n7 (7+)\nSENSE\nA.GND\nA.GND](.mcm-216-218-50m-00024-1000-10/f957cc50c52190b2da87a9b44968ddfbe344d04578240b11f45ab132650c3f25.jpg)

Figure 1-8: Analog Input/Output Connector

# 1.5.2 Digital Input and Output

The MCM-216/218 provides 4 digital input and 4 digital output channels labeled DI and DO 0, 1, 2, and 3. Use D.GND for signal grounding with digital input/output. Use A.GND for signal grounding with analog input.

![D.GND\nDO 2\nDO 3\nD.GND\nDI 2\nDI 3\nD.GND\nDO 0\nDO 1\nD.GND\nDI 0\nDI 1](.mcm-216-218-50m-00024-1000-10/7a1bae343e49c50879fa3d3fe85b9c29af79652c29d337e448870478f24ec803.jpg)

Figure 1-9: Digital Input/Output Connector

# 1.5.3 Temperature Sensor Input

The MCM-216/218 allows you to monitor the temperature of a target device or environment between -50 to $1 5 0 ^ { \circ } \mathrm { C }$ using the temperature sensor provided. Connect the temperature sensor leads to the connector as shown.

![D-/A\nGND\nTemp. Sensor Input\nMCM-216](.mcm-216-218-50m-00024-1000-10/240bc1141b9f50c5093f8772f84552ce2cb34b1bba37a416dba5a2b8e519de73.jpg)

# 1.5.4 Reset Pin for Factory Default

Restore the MCM-216/218 to its factory default settings using a paper clip or similar item inserted into the reset pin hole button and pressing the reset button for three seconds until the device reboots.

![The image depicts a white piece of paper with faint horizontal lines running across it. A large, bold red checkmark is superimposed diagonally over the document, slanting upwards from the bottom left to the top right.](.mcm-216-218-50m-00024-1000-10/3a934da6eee0fd9544e398e1bf696ac09fa3644d3f34dfc33a0e1148f2517cde.jpg)
NOTE:

Users can optionally configure the MCM-216/218 to retain its current network settings rather than restoring the factory defaults. See “Web Console” on page 23.

![9-30 V+\nVDC V-\n2 1\nFN\nRESET Reset Pin](.mcm-216-218-50m-00024-1000-10/cf1c06a7f0b8047a5d803643ea8c40669adfc128629aa5c62e57176aa0a33990.jpg)

# 1.5.5 Ethernet Ports

The MCM-216/218 has two GbE ports with one MAC address. Either port can be used for connecting to a host PC, leaving the second port available for cascading. The default static IP address is 169.254.1.1.

<table><tr><td>LED1 (Amber)</td><td>LED2 (Green)</td><td>Link/Activity</td></tr><tr><td>OFF</td><td>OFF</td><td>Link off</td></tr><tr><td>OFF</td><td>ON</td><td>1000 Link/Activity (Tx, Rx)</td></tr><tr><td>ON</td><td>OFF</td><td>100 Link/Activity (Tx, Rx)</td></tr><tr><td>ON</td><td>ON</td><td>10 Link/Activity (Tx, Rx)</td></tr></table>

# 1.5.6 LED Indicators

The MCM-216/218 has four LEDs located on the front panel.

<table><tr><td>LED</td><td>Function</td><td>Description</td></tr><tr><td>PWR</td><td>Power input</td><td>▸ OFF: Device is not powered▸ Steady red: Device is powered</td></tr><tr><td>SYS</td><td>Boot up and system status</td><td>▸ OFF: Powered off▸ Flashing red, then steady red for about 35 seconds: Booting up▸ Steady green: System ready▸ Steady red: System errorNote: Connect the MCM-216/218 to a host PC via Ethernet cable before powering it on to bypass the three minute boot up process.</td></tr><tr><td>I/O</td><td>Analog input</td><td>▸ Flashing: Analog data is being captured▸ OFF: No data is being captured from FPGA</td></tr><tr><td>USB</td><td>USB Device</td><td>▸ Slow flashing green: A USB device is detected and ready to use.▸ Fast flashing green: Data read/write activity</td></tr></table>

# 1.5.7 USB Ports

USB ports can be used to add a Wi-Fi dongle. Contact your ADLINK sales representative for more information.

This page intentionally left blank.

# 2 Getting Started

# 2.1 Unpacking the MCM-216/218

Ensure that the following items are included in the package. If any items are missing, contact your sales representative for assistance.

X MCM-216/218
X DIN rail mount kit with 2x flat head screws
X Temperature sensor with 3 meter cable
X Quick Start Guide
X Optional accessories (if applicable):
Z Wall mount kit with 4x pan head screws
Z 40W AC-DC adapter

![The image displays a standard warning sign featuring a red triangle with a white border containing a large white exclamation point. Below the triangle, the word 'WARNING' is printed in black capital letters.](.mcm-216-218-50m-00024-1000-10/9d7fc0ce27a12668dcb8a06c166a2f7567c7cd547c79ad24731a1f6e5d3dbb70.jpg)

Before unpacking, check the shipping carton for any damage. If the shipping carton and/or contents are damaged, inform your dealer immediately. Retain the shipping carton and packing materials for inspection. Obtain authorization from your dealer before returning any product to ADLINK.

# 2.2 Connecting to I/O

1 For analog input, insert the signal wires into the terminal block.
2. For digital input or output, insert the signal wires into the terminal block.
3. Use a CAT 5 type Ethernet cable to connect a host PC to one of the Ethernet ports on the top panel. To create a daisy chain of multiple MCM-216/218 devices, use the second Ethernet port to cascade them together. Cascading reduces the number of ports needed to connect devices.

![The image shows a yellow triangular warning sign with a black border featuring a large black exclamation point in the center. Below the triangle, the text 'CAUTION:' is printed in black capital letters.](.mcm-216-218-50m-00024-1000-10/321eb004ebc79801fa0809b564999b5ec67371051fdd7cd779f96d0541e6b15d.jpg)

If connecting MCM-216/218 devices in a daisy chain, only use a sequence configuration: do not use a ring configuration. A ring configuration will cause network communications to fail.

4. For temperature measurement, plug a two-pin temperature sensor connector into the front panel ports before attaching the temperature sensor to the target area to be measured.

# 2.3 Connecting/Disconnecting Power

1 Before turning on the power source, connect the positive and negative wires from a 9 to 30 VDC power source to the terminal block.
2. Turn on the power source. If the power was connected correctly, the front panel red PWR LED will light up.

If the MCM-216/218 needs to be shut down, turn off the power source.

To remove the power wires, use a flat head screwdriver to push the orange slots on the terminal block and then pull out the wires.

![The image shows a yellow triangular warning sign featuring a black exclamation point in the center. Below the triangle, the text 'CAUTION:' appears in black capital letters.](.mcm-216-218-50m-00024-1000-10/bcb231d5e4a23673a9bcabe5963073b568ad237d6c23998c3426c5c74b69d26f.jpg)

Ensure the power source is turned off before connecting or removing the power wires.

# 2.4 Checking Device Status

1 When power is supplied, the PWR LED will be red. The SYS LED will initially blink red, then turn to a steady red for about 35 seconds, then change to a steady green indicating the device has successfully booted up.
2. Log into the device’s web console for additional status information and configuration options. See “Web Console Login” on page 23.

# 2.5 Usage Scenarios

The MCM-216/218 is designed for distributed machine condition monitoring and can be used in many kinds of scenarios. Choose the most suitable scenario depending on the system infrastructure, data type, and frequency of data retrieval.

# 2.5.1 First-Time Configuration / Portable DAQ

Use the web console to configure device information, system settings, network settings, and test measurement analog input settings. For portable DAQ usage, the MCM-216/218 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 23.

# 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-216/218 retains captured data in the REST data format. Especially in IT systems, user applications frequently adopt REST APIs because they are intuitive. The MCM-216/218 emulates all functions supported by REST APIs, and the MCM-216/218 embedded middleware executes related operations and transfers the filtered data in JSON format. All queries from a REST command are handled by the MCM-216/218 and reply accordingly. See “DAQ Missions” on page 53.

# 2.5.3 TCP Socket for Streaming

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 get raw or voltage data directly, apply TCP socket client mode (no SDK installation necessary). By using the streaming mode, all queried raw data may bypass the MCM-216/218’s middleware and route directly to the host PC via Ethernet. See “Passive Data” on page 55.

# 2.5.4 Passive Data (TCP Socket)

Similar to the Continuous Data user scenario, for passively retrieving data by each query, it is suitable to use a TCP socket with the MCM-216/218 in client mode. Whenever data is generated, the MCM-216/218 will be triggered to establish a TCP connection with the host PC and actively transmit the data. See “Web Console” on page 23.

This page intentionally left blank.

# 3 Web Console

This chapter describes how to use the built-in web console to configure the MCM-216/218 and view captured data.

# 3.1 Web Console Login

After the MCM-216/218 has been successfully powered on and a host PC has been connected to it, do one of the following: (1) set the PC’s network setting to either DHCP mode or link local mode; or (2) modify the PC’s IP address to be on the same network segment as the device (169.254.x.x). Next, open a web browser on the PC (Google Chrome is recommended) to access the web console via one of the following options.

# Option 1: IP Address

In the web browser’s address bar, enter the MCM-216/218’s IP address (e.g., http://169.254.1.1). The default network setting of the MCM-216/218 is Static IP mode with an IP address of 169.254.1.1.

# Option 2: Hostname

Connect the MCM-216/218 to a network component (switch/router) with DNS functionality, then enter the MCM-216/218’s hostname in the address bar of the host PC’s web browser, prefaced by http:// (e.g., http://mcm216-j801ns1001). A unique default hostname is generated for each MCM-216/218 device and can be found on the label of the box it was shipped in. The hostname can be changed within the web console.

After using either method, the web console will display within roughly 30 seconds, presenting the user with a login screen (see Figure 3-1 on the next page).

The default username is administrator and the default password is Adlink6166.

![ADLINK\nMenu\nLogin\nPlease login first.\nUsername *\nPassword *\nLOGIN\nCopyright © 2019 ADLINK Technology Inc. All Rights Reserved.](.mcm-216-218-50m-00024-1000-10/1a4b79c4c34b557b5f8f3f3a80dc53fb16905101fde4042622ec9dcb45c4dc5d.jpg)

Figure 3-1: Web Console Login Page

# 3.2 Web Console Menu

The web console menu bar includes the following items.

X Mission Manager
Z Device Setting
Z Mission Management
Z Peripheral

X Data Manager

Z Data Capture
Z Data History
Z Data Condition
Z TCP Socket
Z USB Storage
Z Modbus TCP Server
Z Modbus RTU Mater

X Information

Z System information

X System Manager

Z System Setting
Z Network Setting
Z Account Management
Z Change Password

![The image features a blurry, red, upward-pointing triangle centered on a plain white background. There is no text present.](.mcm-216-218-50m-00024-1000-10/73c464999d23159bdddfc7f2a0806cb22e3ce47fab23913872978ba272353022.jpg)

# ADLINK

# Menu

![A blurry, gray wrench is shown on a white background.](.mcm-216-218-50m-00024-1000-10/af8fcddef08d977bafa2083620754f2a308c2754dff9d691ff562aa501dfcafe.jpg)

![目目](.mcm-216-218-50m-00024-1000-10/f511aff5a415dad216faf8967489f71113568d3acecc6bd664ae6768dadc2fdc.jpg)

![The image displays three identical black zig-zag lines, resembling the letter 'W', arranged horizontally in a row against a white background. There is no text present.](.mcm-216-218-50m-00024-1000-10/c17e6b989c3c08ce12a7e07744bff7e686872a97a4d58e85d57ef9a607d76a31.jpg)

![The image displays a blurry, vertical crop of a small icon featuring two curved arrows arranged in a circle, resembling a refresh or reload symbol. There is no text present.](.mcm-216-218-50m-00024-1000-10/cb3a5106fe68b2aa25e0414bba6455d158e7e3d44a3ae03baa94bc8b017a4f1e.jpg)

![The image displays a low-resolution, pixelated black icon on a white background, depicting a circular arrow pointing counter-clockwise, resembling a refresh or reload symbol.](.mcm-216-218-50m-00024-1000-10/d4c82c1ca5929589557f3e7ef622cae29f530a55795f7cf7a957f3306f9089a9.jpg)

![The image displays a low-resolution, grayscale crop of a symbol. It features a dark grey triangle pointing to the right, which is the standard icon for 'Play.' A vertical line is visible along the left edge of the triangle, likely representing the symbol's base. The image is blurry and pixelated.](.mcm-216-218-50m-00024-1000-10/59a3fa24c965bd54176c8a524bc92c96b26ccfa9eca42dc49ce5f2361577b428.jpg)

![The image displays a blurry, dark, horizontal squiggle or line against a plain white background. It resembles a handwritten signature or a smudge. There is no legible text visible.](.mcm-216-218-50m-00024-1000-10/b00364381eff5b25224dc6988245e8ff8d25bf3f3ec3d857ab80c7afd27df995.jpg)

![The image features a blurry, grey cross centered vertically against a background that is split vertically, with a white area on the left and a grey area on the right. There is no text visible in the image.](.mcm-216-218-50m-00024-1000-10/3b4b37ac21d99147ea640f264db68a7f56cf138a8472a8774bfffe1653bde9ac.jpg)

![The image displays a blurry, low-resolution section of a digital interface, likely a webpage or application. It features rectangular blocks, resembling buttons or cards, set against a white background. On the right side, two identical rectangular blocks are stacked vertically. On the left side, a partial view of a similar block is visible. Inside each block, there are two horizontal, dark, blurry shapes that appear to be lines of text, but the text is completely illegible due to the image quality.](.mcm-216-218-50m-00024-1000-10/bd5f559942facad8fa01affc239af1d41830f354f5754ab58b9e4867a9a6a992.jpg)

![The image displays a pair of metal eyeglass frames isolated against a white background. The frames feature a rectangular design with two large, square-shaped rims connected by a central bridge. Small metal nose pads extend inward from the bridge area, and small cylindrical hinge mounts are visible on the outer edges of the rims. The metal has a thin, wire-like construction and a reflective, silvery finish.](.mcm-216-218-50m-00024-1000-10/035af06db7ac1eafc58da834e4156779fd8cfe05087bc220760a626d0990d52c.jpg)

![The image displays a blurry, low-resolution graphic centered on a white background. It features a square icon that resembles a picture frame or window, consisting of a lighter grey outer square containing a darker, inner square shape. A thin, horizontal line is visible at the very top edge of the image. There is no text present.](.mcm-216-218-50m-00024-1000-10/3d58fcde3255afcf34ba07e5d252bb3b80ad0e89e4e97770d7f6ca5a859d2c14.jpg)

![The image displays a small, gray, pixelated gear or cogwheel icon centered on a plain white background. There is no text present.](.mcm-216-218-50m-00024-1000-10/85db6b45a6212d89696300cfd4dbcfa8a5c011985bb7e03b3a0385c3232aa860.jpg)

![The image displays four identical, grey, line-drawn shapes arranged in a horizontal row against a white background. Each shape resembles the letter 'Y' or a stick figure with arms raised and no head.](.mcm-216-218-50m-00024-1000-10/5e9e2b450233eba8930ed881bf7abb6147cc919c8b2c8a3488beca21224acf44.jpg)

![The image displays six identical dark grey shapes arranged in two rows of three against a white background. Each shape resembles a stylized figure with arms raised or a 'Y' shape, consisting of a central vertical stem with two arms extending upwards and outwards.](.mcm-216-218-50m-00024-1000-10/2efb73abefc445174f2e91c3ca988bbdcc9ac1f26f57ca000810d914f72ec394.jpg)

![The image displays a blurry, low-resolution grayscale version of the BMW logo (the roundel), featuring its characteristic four quadrants.](.mcm-216-218-50m-00024-1000-10/6b4307c79fbd7714cb56dde253615caed237f71edfc888638c9c84140e2d5a7a.jpg)

Figure 3-2: Web Console Welcome Page

Depending on the host PC screen size and resolution, the menu list might be collapsed. Click the menu icon to expand the menu.

![The image displays a red logo in the shape of an upward-pointing triangle with a curved base. Inside the red shape, there are horizontal white lines that curve slightly, resembling stylized clouds.](.mcm-216-218-50m-00024-1000-10/f9672f5b8a16fcb30a3317739959996b3e14e750de6d4c3b17b00876271bc376.jpg)

# ADLINK

![The image displays a solid red background featuring three horizontal white bars stacked vertically in the center, resembling a 'hamburger' menu icon.](.mcm-216-218-50m-00024-1000-10/128be319957d3609b1eb1c027b65779ffa304ab8f252a1e8e6aaa0dd5a627e45.jpg)

![The image shows a large, solid black arrow pointing to the left, centered against a red rectangular background.](.mcm-216-218-50m-00024-1000-10/1f8c88d7842dc46eb74388ce0d4751f3729aa6b10a8f3527a9fa998b88c2ecc2.jpg)

Welcome

Figure 3-3: Menu Icon

# 3.2.1 Information/System Information

The System Information page shows the device software version, general information, I/O channel status, and network status.

System Information

Software Version

Firmware Version : 20.10.1225

Device Information

Model: MCM-216-A

Hostname:MCM204

Serial Number: \*nwwaes

Channel Status

Channel Status : Al: ready Log Count:0

Network Status

Ethernet

IP Addre55 : 169.254.1.1

MACAddress:10:0s:2c:bt01:a7

Subnet Mask:16

Gateway:0.0.0.0

Type:static

DNS:8.8.8.8.

Figure 3-4: System Information

# 3.2.2 Mission Manager/Peripheral

Peripheral digital input/output and temperature sensor information is shown on this page. The Status area shows the current status of the peripherals. Select REFRESH to update the status.

Four digital input/output devices can be used. Each can be adjusted for either input or output mode. To enable/disable digital input/output, mark the appropriate check boxes as necessary.

![Peripheral\nAuto-Refresh per 5 seconds\nStatus\nA06 Closed (0.0) A01 Closed (0.0)\nD01 Input (High) D11 Input (High) D12 Input (High) D13 Input (High)\nD06 Output (Low) D01 Output (Low) D02 Output (Low) D03 Output (Low)\nTemperature N/A\nREFRESH\nDigital I/O Setting\nValue\nEnable D00 Output Low\nValue\nEnable D01 Output Low\nValue\nEnable D02 Output Low\nValue\nEnable D03 Output Low](.mcm-216-218-50m-00024-1000-10/b447b89530ec72332f8ecc6c2f18500c5ec20d131c93c445640446ae1963aa1f.jpg)

Figure 3-5: Peripheral Devices

# 3.2.3 Data Manager/Data History

Historical data can be retrieved in this page. Choosing a specific time period will speed up the data search.

![History Data\nClear\nCLEAN ALL DATA\n*This will delete all data history.\n\nSearch Filter :\nAll User\nAll Time\nUser:\nFrom:\nYear Month Day Hour Min Sec\n2020 11 28 15 18 55\nTo:\nYear Month Day Hour Min Sec\n2020 12 25 15 18 55\n'Use the '*' and '-' keys on the keyboard to modify the value.\nSEARCH](.mcm-216-218-50m-00024-1000-10/d6f4967d0aa8081e7cfe53af217586a769f8c386249fce14e51144d57fe03c76.jpg)

Figure 3-6: Data History

# 3.2.4 Mission Manager/Mission Management

A mission is a setting of I/O parameters with an intended output method. The MCM-216/218 will execute the same settings even after a reboot, so if Repeat Times is set to 0 (endless data capture), the MCM-216/218 will run its previous mission after reboot. To configure the I/O parameters for another mission, delete the current mission.

Channel Status shows if the AI and DI/O are running a mission or are ready to be assigned a new mission.

![Mission Management\nDelete Mission\nClick the DELETE button to stop the current mission.\nDELETE\nChannel Status: Atready AOready Log Count:0\nREFRESH](.mcm-216-218-50m-00024-1000-10/92ddb1c9bcbd08e23c474950057eb0e82cc2f391ab08dc9e6135c5dd791e02e9.jpg)

Figure 3-7: Mission Management

# 3.2.5 System Manager/Change Password

This page is used to change the password of each MCM-216/218, whether there is a single device or multiple daisy chained devices. It is recommended that each device have a unique password since the default password for every MCM-216/218 is identical.

![Change Password\nStep 1:Enter current password\nOriginal Password\nCHECK](.mcm-216-218-50m-00024-1000-10/342d24256d005b1d30649131ab2f4a3036cea4b42833b93d9cf353600af4cf81.jpg)

Figure 3-8: Change Password

# 3.2.6 System Manager/Account Management

This page manages user accounts and access privileges.

![Account Management\nCreate New Account\nUsername Password Password Confirm Permission Guest\n*The password must be at least 8 characters, have at least one uppercase character, at least one lowercase character and at least one number.\nCREATE\nAccount List\nNo. Username Permission Action\n1 administrator admin](.mcm-216-218-50m-00024-1000-10/3a6fb760b96939fdbb3d28576bfb7485cc556739a07ec2e4a3e92383812dbdd4.jpg)

Figure 3-9: Account Management

# 3.2.7 System Manager/Network Setting

This page manages various system settings.

Hostname: The device’s hostname can be modified by entering a new hostname here and clicking the APPLY button. A hostname can be used instead of an IP address to access a specific device’s web console. See “Web Console Login” on page 23 for details.

Keep Network Setting: Select Enable to retain network settings even after the device has been reset to factory defaults.

![Network Settings\nETHERNET\nWi-Fi\nNetwork Settings\nHostname\nMCM204\nEthernet\nType\nStatic\nAddress\n169.254 1.1\nGateway\n0 0 0.0\nMask\n16 - 255.255 0.0\nDNS 1\n8.8.8.8\nDNS 2\nAPPLY\nKeep Network Settings : ○ Enable ● Disable\n('Enable' to keep the network settings after restoring factory settings, 'Disable' to restore all settings.)\nAPPLY](.mcm-216-218-50m-00024-1000-10/5a29746650597cfa3dd5c801d15f59b317aad0ef67bd0a17edf555842abb6e32.jpg)

Figure 3-10: Network Settings

# 3.2.8 System Manager/System Setting

![System Settings\nTime Setting\nTime: Year Month Day Hour Min Sec.\n2020 12 25 15 22 07\n'Use the '+' and '-' keys on the keyboard to modify the value:\nTime Zone NTP Server\nAsia/Taipei 0 us pool ntp.org\nAPPLY\nSystem Restart\nClick RESTART to reboot the device.\nRESTART\nData Keep\nData Keep: Enable Disable\n('Enable' to store history data in DISK and RAM, 'Disable' to only store it in RAM.)\nAPPLY\nDDS Setting\nDDS Setting: Enable Disable\nAPPLY](.mcm-216-218-50m-00024-1000-10/8f5c4a3398bbeb48d4e046a153fd0ff9cd30cbdd2a0295ec42850a465e33d677.jpg)

Figure 3-11: System Settings

System Restart: Since the device may be deployed in at a remote site, if it is necessary to reboot the device, click RESTART to soft reboot the device.

Data Keep: By default, the MCM-216/218 stores history data only in RAM and the data is lost when the system reboots. Select Enable to also save history data to internal storage. The amount of disk space allocated for this purpose is 300MB. When that limit is reached, data that has gone for the longest period of time without being accessed will be overwritten first, thus preserving the data that has been accessed most recently.

Device Calibration: The MCM-216/218 can be recalibrated if necessary. Though the MCM-216/218 is factory-calibrated before shipment and associated calibration constants are written to the on-board EEPROM, it is possible that, over time or depending on temperature conditions, recalibration may become necessary.

Customization Library Upload: This function runs custom formulas on the MCM-216/218 according to a given file. See “Custom Filtering Algorithms” on page 56.

Firmware Upgrade: A firmware upgrade file can be uploaded to the MCM-216/218 through this feature. These files will periodically be provided through the product web page:

www.adlinktech.com/Products/IoT\_solutions/Smart\_Factory/ MCM-210\_Series

![DDS Setting\nDDS Setting ○ Enable ● Disable\nAPPLY\nDevice Calibration\nClick APPLY to calibrate the device.\nAPPLY\nCustomization library Upload\nLibrary Upload: 选择檔案 未選擇任何檔案\n(Select a .so file.)\nUPLOAD\nFirmware Upgrade\nFirmware Upgrade: 選擇檔案 未選擇任何檔案\n(Select a .bin file with the correct content.)\nUPLOAD\nFile not selected or invalid.](.mcm-216-218-50m-00024-1000-10/28200a4770d92e55831bfed7dbf9a6f123710d233928518cafee9d744ec68d46.jpg)

Figure 3-12: Upload Customization/Firmware Files

# 3.2.9 Data Manger/TCP Socket (for one-shut query mode)

The MCM-216/218 supports TCP socket communication as a socket client. Enter the IP address and port number of the remote TCP socket server. Different analog input channels can be mapped to different ports. Select ADD RULE to add the TCP server to the Socket Connection List.

The Status column shows the communications status with the corresponding TCP socket server. If the socket is disconnected, select RE-CONNECT ALL to re-establish the connection.

![TCP Socket\nAdd socket connection\nAddress	Port	Channel\n192.168.1.1	6666	ALL\nADD RULE\nSocket Connection List\nRE-CONNECT ALL\nSocket No.	Status	Address	Port	Channel	Action\n1	○	192.168.1.1	6666	ALL	Delete](.mcm-216-218-50m-00024-1000-10/abd2beb5d5b0f120e31b63c2b80a2378a83573269b2938001e9996534dcaf3f4.jpg)

Figure 3-13: TCP Socket

After setting the TCP socket connection and creating a DAQ mission, data generated by the MCM-216/218 will immediately begin transmitting to the TCP server side.

# 3.2.10 Device Manager/Modbus TCP Server

In addition to the REST API, the Modbus TCP protocol can be used to access data generated from the MCM-216/218. The MCM-216/218 acts as a Modbus TCP server, and a remote Modbus TCP client can actively query the MCM-216/218.

![Modbus TCP Server\nServer Setting\nModbus TCP Slave	Port	Slave ID\nEnable	502	1\n\nAI Setting and information\nFunction Code:4\nAddress:30001. The length is 2.\nDescription:Save the AI data in the register. Supported data types: OA, Voltage, Raw Data, G and Custom.\nSelectable Data Values depend on the device settings.\nStarting Address	Data Value	Action\n0	Reserve	INSERT	DELETE\nADD\nAPPLY](.mcm-216-218-50m-00024-1000-10/99305ab9d16c87be640383bd355319057cbc91dbe1bd0465c479e606fb4d6bb4.jpg)

Figure 3-14: Modbus TCP Server

Enable the Modbus TCP function, set a Modbus port number and assign a Slave ID to the MCM-216/218.

Before creating the Modbus register list, be sure to add a data type in each channel. Otherwise, the data value in the Modbus setting will only have Reserve and temperature as default. See “DAQ Mission” on page 40.

Once the device setting page has been set and applied, all the created device types for each channel will be shown in a list under Data Value.

The following examples show channels AI0 with two data types, AI1 with one data type, and AI2 with one data type.

![Channel Config\nAI0 Config\nEnable the Channel\nCoupling Input Range\nDC ±10\nData Type\nVoltage\nADD CONDITION\nData Type\nRawData\nADD CONDITION\nADD DATATYPE\nAI1 Config\nEnable the Channel\nCoupling Input Range\nDC ±10\nData Type\nVoltage\nADD CONDITION\nADD DATATYPE\nAI2 Config\nEnable the Channel\nCoupling Input Range\nDC ±10\nData Type\nVoltage\nADD CONDITION\nADD DATATYPE](.mcm-216-218-50m-00024-1000-10/a019a0a8a34a384910f8980d749245642efb756bc83a1f39766e408e8f51365d.jpg)

Figure 3-15: Data Types for Modbus TCP

In the Modbus TCP settings page, the data value column will show the created data types. Each data type in an analog input channel occupies 2 modbus registers read by modbus function code 4, starting from address 30001.

![Modbus TCP Server\nServer Setting\nModbus TCP Slave	Port	Slave ID\nEnable	502	1\nAI Setting and information\nFunction Code:4\nAddress:30001. The length is 2.\nDescription:Save the AI data in the register. Supported data types: OA, Voltage, Raw Data, G and Custom.\nSelectable Data Values depend on the device settings.\nStarting Address	Data Value	Action\n0	Reserve	INSERT	DELETE\nTemperature\nAI0-Voltage\nAI0-RawData\nAI1-Voltage\nAI2-Voltage\nADD\nAPPLY\nMore Modbus information:\nFunction Code:1 - DO Read](.mcm-216-218-50m-00024-1000-10/5ba196c54cd780d8b5440e15f27bc709a652f579efb91732e021c32c73304530.jpg)

Figure 3-16: Modbus TCP Created Data Types

Now, you can allocate the register sequence accordingly.

Modbus TCP Server

Server Setting

Al Setting and information

Function Code:4

Address:30001. The length is 2

Figure 3-17: Data Value Starting Address Allocation

Other peripherals, such as digital input, digital output, and analog output can be operated by different Modbus function codes and addresses.

![More Modbus information:\nFunction Code:1 - DO Read\nDescription:Read DO modbus register. Each starting address indicates a channel.\nStarting Address Channel\n0 D00\n1 D01\n2 D02\n3 D03\nFunction Code:2 - DI Read\nFunction Code:3 - AO Read\nFunction Code:15 - DO Write\nFunction Code:16 - AO Write](.mcm-216-218-50m-00024-1000-10/365b654cb00e754c521159da82f053e3c8a2f1bdcedfd4c5256f9967fc30f53b.jpg)

Figure 3-18: Modbus Function Codes

# 3.3 DAQ Mission

The MCM-216/218 performs signal detection. Related parameters can be set via the Mission Manger/Device Setting page.

Device Settings
![Analog Input\nAnalog Output\nAI Mission Profile Management\nSave ProfileLoad DefaultSelect Mission Profile\nSAVE PROFILELOAD DEFAULT選擇檔案未選擇任何檔案\nLOAD SETTING\nAI Data Mode\nOne Shot (default)Stream Mode with TCP Socket\n'You can set TCP Socket in 'Menu' - 'Data Manager' - 'TCP Socket' in one shot mode.\nAI Device Configuration\nInput TypeTrigger SourceTrigger DirectionTrigger Value\nSingle-Ended (RSE)NoWaitRising1\nTrigger ModeTrigger StartPos\nPOST0\nRepeat IntervalRepeat TimesSample RateData Count\n3000125000010240\nMax:250000 Min:1\nData Count Boundary\nChannel Gain Queue\nQueue Content:\nAI0 , AI1 , AI2\nDefault AI0 , AI1 , AI2,\nBACKSPACE\nClick and Add:\nAI0AI1AI2AI3AI4AI5AI6](.mcm-216-218-50m-00024-1000-10/1f54f5c82c0aba5818a926f92b5e7e30b86e59d8837241a00f389a91636f8bf2.jpg)

![Channel Gain Queue\nQueue Content:\nA10\nDefault: A10.\nBACKSPACE\nClick and Add:\nA10\nA11\nA12\nA13\nA14\nA15\nA16\nA17\nA18\nA19\nA110\nA111\nA112\nA113\nA114\nA115\nOnly enabled channels can be added.](.mcm-216-218-50m-00024-1000-10/e1746ccdc3c86627e42eaad3f5b34e4a94611e3647b7fefa89d4230a8324ff3b.jpg)

Figure 3-19: Device Configuration

AI Data Mode: There are two kinds of data query modes.

One Shut Mode queries data by time interval. By configuring all the settings, including repeat interval, repeat times, and sample rate, the device will query data accordingly.

Streaming Mode, with a TCP socket, queries data continuously. Hence, the repeat interval and repeat time settings are unavailable. Once the data has been queried from FPGA, the data will then be transmitted to the host PC via TCP socket. Set the IP and port number of the TCP socket server accordingly.

Input Type selects the wiring method, either single-end or pseudo-differential.

# Trigger Modes

Analog input supports post, delay, middle, gate, post trigger with retrigger, and delay trigger with retrigger modes.

# Post-Trigger Acquisition Mode (no retrigger)

Post-trigger acquisition is indicated in applications where data is to be collected after a trigger event, as shown.

![This image is a timing diagram illustrating a sequence of events over time.\n\n**Top Section (Timeline):**\nA horizontal arrow pointing to the right represents the timeline, labeled **'Time'** at the far right. Three vertical arrows point downward from text labels to specific moments on this line:\n*   The first arrow points to **'Operation start'**.\n*   The second arrow points to a moment labeled **'Trigger Event Occurs'** and **'Acquisition start'**.\n*   The third arrow points to a later moment labeled **'Acquisition stop'** and **'Begin to transfer data to system'**.\n\n**Bottom Section (Signals):**\nBelow the timeline are two signal tracks:\n*   The middle track is labeled **'Trigger'** and displays a waveform with a single, short rectangular pulse. The start of this pulse aligns vertically with the 'Trigger Event Occurs' arrow.\n*   The bottom track is labeled **'Data'** and features a hexagonal block containing the text **'N samples'**.](.mcm-216-218-50m-00024-1000-10/20935f97461f8d4df3dee5baf46f78bd537c1ab9f7aac620684d72c5b069f773.jpg)

Figure 3-20: Post Trigger without Retrigger

# Pre-trigger Acquisition (no retrigger)

Collects data before the trigger event, with acquisition starting once specified function calls are executed to begin the pre-trigger operation, and stopping when the trigger event occurs. If the trigger event occurs after the specified amount of data has been acquired, the system stores only data preceding the trigger event by a specified amount, as shown. Note that N must be equal to or less than 8k samples for all analog input channels.

![The diagram illustrates a timeline of data acquisition relative to a trigger event.\n\n**Labeled Blocks and Connections:**\n\n*   **Timeline:** A horizontal arrow pointing right is labeled **'Time'**.\n*   **Start Event:** Text reading **'•Operation start'** and **'•Acquisition start'** has an arrow pointing down to the timeline on the left side.\n*   **Trigger Event:** Text reading **'•Trigger Event Occurs'**, **'•Acquisition stop'**, and **'•Begin to transfer data to system'** has an arrow pointing down to the timeline on the right side.\n*   **Trigger Signal:** A horizontal line labeled **'Trigger'** features a square pulse aligned vertically with the right-hand arrow from the Trigger Event.\n*   **Data Signal:** A horizontal line labeled **'Data'** contains a long rectangular bar divided into two sections:\n    *   A left section hatched with diagonal lines.\n    *   A right section labeled **'N samples'**.\n*   **Annotations:**\n    *   A curly bracket under the hatched section connects to the text: **'This data is discarded.'**\n    *   A curly bracket under the 'N samples' section connects to the text: **'Only acquired N samples will be transferred back to system.'**](.mcm-216-218-50m-00024-1000-10/ab56bfa4f00cc3b3cae49bdac05df7796a3a7f939d1133529501ad31efda8d9d.jpg)

Figure 3-21: Pre-trigger Mode Operation (valid trigger only)

The trigger event occurs after the specified amount of data has been acquired. However, if the trigger event occurs before the specified amount of data has been acquired, the acquisition engine ignores the trigger signal until the specified amount of data has been acquired, as shown.

![This diagram illustrates a timing sequence with three horizontal tracks aligned against a timeline.\n\n**Labeled Blocks and Connections:**\n\n*   **Time Axis (Top Row):** A horizontal arrow pointing right is labeled **'Time'**. Three events mark this axis:\n    *   **Start:** An arrow points to the beginning, labeled with bullet points: **'•Operation start'** and **'•Acquisition start'**.\n    *   **Ignored Signal:** A dotted arrow points to a middle marker, labeled: **'•Trigger signals that occur before the specified amount of data has been acquired are ignored'**.\n    *   **End/Transfer:** An arrow points to a right-side marker, labeled with bullet points: **'•Trigger Event Occurs'**, **'•Acquisition stop'**, and **'•Begin to transfer data to system'**.\n\n*   **Trigger Row:** Labeled **'Trigger'**, this row displays a waveform with two pulses. The first pulse aligns vertically with the middle 'Ignored Signal' marker. The second pulse aligns vertically with the right-side 'End/Transfer' marker.\n\n*   **Data Row:** Labeled **'Data'**, this row shows a long horizontal bar representing the data buffer:\n    *   **Pre-trigger Section:** A hatched (diagonal stripes) section on the left. Below it is a dimension line with text reading: **'X samples have been acquired before trigger occurs, where X(N'**.\n    *   **Post-trigger Section:** A long white rectangular block immediately following the hatched section, labeled **'N samples'**.](.mcm-216-218-50m-00024-1000-10/c06febb78ed1b80bd1b667cfcbf8654952fcdba00c81cd10a47b8541b66ca074.jpg)

Figure 3-22: Pre-trigger Mode Operation (w/ invalid trigger)

# Delay-Trigger Acquisition (no retrigger)

Delays data collection after the trigger event, as shown. The delay count is specified by a 32-bit counter value, such that the maximum delay count is $( 2 ^ { 3 2 } - 1 )$ when the minimum delay count is 1.

![This diagram illustrates a timing sequence across three synchronized rows:\n\n**1. Timeline (Top Row)**\nA horizontal axis labeled **'Time'** with an arrow pointing right features four events marked by downward arrows:\n*   **'•Operation start'**\n*   **'•Trigger Event Occurs'**\n*   **'•Acquisition start'**\n*   **'•Acquisition stop'** and **'•Begin to transfer data to system'**\n\nA horizontal arrow labeled **'Delay Time'** connects the vertical arrow for 'Trigger Event Occurs' to the vertical arrow for 'Acquisition start'.\n\n**2. Trigger Signal (Middle Row)**\nA signal line labeled **'Trigger'** displays a single rectangular pulse that aligns vertically with the 'Trigger Event Occurs' point on the timeline.\n\n**3. Data Signal (Bottom Row)**\nA signal line labeled **'Data'** displays a long pulse labeled **'N samples'**. This pulse begins shortly after the 'Acquisition start' point and extends until it aligns with the 'Acquisition stop' point.](.mcm-216-218-50m-00024-1000-10/ab916e08076b3d82f71fa3d31b5e791a6496174563b4bc30abba8cc23f43eced.jpg)

Figure 3-23: Delay-Trigger Mode Operation

# Middle-Trigger Acquisition

Middle-trigger acquisition is indicated when data is to be collected before and after the trigger event. The amount of stored data before and after trigger event can be set individually (M and N samples), as shown. Please note that M+N must be equal to or less than 8k samples for all analog input channels, and that the trigger event can only be accepted when the specified amount of data has been acquired (M samples), otherwise the trigger event will be ignored.

![The diagram illustrates a timing sequence relative to a timeline.\n\n**Timeline and Events:**\n*   A horizontal line with an arrow pointing right is labeled **'Time'**.\n*   An arrow points to the left side of the timeline with the text:\n    *   **'Operation start'**\n    *   **'Acquisition start'**\n*   An arrow points to a specific point on the timeline (aligned with a pulse) with the text:\n    *   **'Trigger Event Occurs'**\n    *   **'Acquisition stop'**\n    *   **'Begin to transfer data to system'**\n\n**Signals and Data:**\n*   Below the timeline is a signal line labeled **'Trigger'** which shows a brief high pulse.\n*   Below that is a signal line labeled **'Data'** consisting of two segments:\n    *   A left segment shaded with diagonal hatching.\n    *   A right segment labeled **'N samples'**.\n\n**Annotations:**\n*   A curly brace connects the hatched segment to the text: **'This data is discarded.'**\n*   A curly brace connects the 'N samples' segment to the text: **'Only acquired N samples will be transferred back to system.'**](.mcm-216-218-50m-00024-1000-10/1f32216b054c5af1140d74ff6b119d68152af01a802f57df521a8ebbc39449cc.jpg)

Figure 3-24: Middle-Trigger Acquisition

# Gated Trigger

Gated-trigger acquisition is indicated in applications where data is to be collected when trigger events are set to level high/low, and acquisition suspended when trigger events are set to the opposite level. The process repeats until the specified amount of data is acquired.

![The diagram illustrates a data acquisition sequence over time, showing the relationship between trigger events and data samples.\n\n**Labeled Blocks and Text:**\n*   **Top Events:**\n    *   'Operation start'\n    *   'Acquisition start'\n    *   'Trigger event occurs (high active)' (appears twice)\n*   **Signals:**\n    *   'Time' (label for the horizontal arrow)\n    *   'Trigger' (label for the square wave signal)\n    *   'Data' (label for the bottom signal track)\n*   **Data Labels:**\n    *   'M samples'\n    *   'N samples'\n    *   '....' (ellipsis)\n\n**Connections and Flow:**\n1.  **Initiation:** An arrow labeled with 'Operation start' and 'Acquisition start' points to the beginning of the timeline.\n2.  **Triggering:** Two arrows labeled 'Trigger event occurs (high active)' point to the rising edges of the high pulses in the 'Trigger' signal.\n3.  **Data Acquisition:**\n    *   Below the 'Trigger' signal, the 'Data' signal shows a sequence of blocks.\n    *   The high pulses in the 'Trigger' signal align with blocks labeled '**M samples**' (visualized as hatched blocks next to a white label box).\n    *   The low gaps in the 'Trigger' signal align with blocks labeled '**N samples**'.\n    *   This pattern of 'M samples' followed by 'N samples' repeats, indicated by the ellipsis '....' at the end of the row.](.mcm-216-218-50m-00024-1000-10/24aced352b0fc9d444b7fde32ce8a5d481ebc9bfeec7882e588f6258806ddf3a.jpg)

Figure 3-25: Gated Trigger

# Post-Trigger or Delay-Trigger Acquisition with Re-Trigger

Post-trigger or delay-trigger acquisition with re-trigger function is indicated in applications where data is to be collected after several trigger events. The number of scans after each trigger and the re-trigger number are valid from 1 to the buffer size allocated in kernel space. The process repeats until the specified amount of re-trigger signals is detected.

Repeat Interval is the interval between each data capture, in milliseconds. Each data query consists of data capture via FPGA plus data filtering via MCU. The time required for data filtering may vary according to the complexity of the filtering algorithm. If the time required for handling data exceeds the repeat interval, the next time query will be started immediately. It is recommended that this value be set.

Repeat Times is the total number of times the data is to be captured. For endlessly repeating data capture, set to 0.

![This image displays a safety warning sign featuring a maroon triangle with a thin white border. Inside the triangle is a large white exclamation point. Below the triangle, the word 'WARNING:' appears in black capital letters.](.mcm-216-218-50m-00024-1000-10/be31e4aebf5fe0ee068c7819578d4217d610b32f3a0591b92767d349d46a4f75.jpg)

Warning! If you are using a customized algorithm as your Data Type, it is strongly recommended to set Repeat Times to 1 for the first attempt, then to 10 for a limited data capture test. Once you have confirmed the algorithm is running as intended, you can set Repeat Times to 0 for repeated data capture.

Set Sample Rate and Data Count accordingly. Selecting the pen icon to display a convenient sliding tool with fine-tuned (+/-) adjustments.

![Channel Gain Queue\nQueue Content:\nAI0\nDefault: AI0, AI1, AI2,\nBACKSPACE\nClick and Add:\nAI0 ✓ AI1 ✓ AI2 ✓ AI3 ✓ AI4 ✓ AI5 ✓ AI6\nAI7 ✓ AI8 ✓ AI9 ✓ AI10 ✓ AI11 ✓ AI12 ✓ AI13\nAI14 ✓ AI15 ✓\nOnly enabled channels can be added.](.mcm-216-218-50m-00024-1000-10/6f793431754efc097ff16f16bdc446b3f9f58f77f48ddc8eb8eb8e149e201b2f.jpg)

The MCM-216/218 provides the Channel Gain Queue function to dynamically allocate sampling size. By default, the selected channels will equally share the maximized sample rate. However, sampling rates can be allocated as necessary between channels. For example, when choosing 16 channels with a 250 kS/s sample rate, each channel will use 15.625 (250/16) as its sample rate. If a channel needs a higher sample rate, set the value accordingly.

To set the sample rate. first check the desired channels, then select the checkbox for each channel to include them in Queue Content. The sequence in Queue Content represents the allocated unit that each channel requires. Click as many times on the channel as needed. The sample rate will be shared according to the Queue Content.

As the figure below shows, channels 0, 1, 2, and 3 are selected. The sequence is AI0, AI0, AI1, AI3, AI2, AI2, AI2, AI2, AI2, and AI2. Hence, channel 0 will occupy 2/10 of the maximum sample rate. Channel 1 and 3 will occupy 1/10 of the maximum sample rate. Channel 2 will occupy 6/10 of the maximum sample rate. You can manually set the sample rate according to the device each channel connects to.

![Channel Gain Queue\nQueue Content:\nA10 , A10 , A11 , A13 , A12 , A12 , A12 , A12\n\nDefault A10, A11, A12, A13,\nBACKSPACE\n\nClick and Add:\nA10 ✓ A11 ✓ A12 ✓ A13 ✓ A14 A15 A16\nA17 ✓ A18 ✓ A19 ✓ A10 ✓ A11 ✓ A12 ✓ A13\nA14 ✓ A15 ✓\nOnly enabled channels can be added.](.mcm-216-218-50m-00024-1000-10/5fcbda70b45a99d1c7cc3608102962d9095626c41e8026e62cb10544352e6831.jpg)

For each analog input channel, click DataType to choose which data type to use for the output.

![Channel Config\nAdd Config\nEnable the Channel\nCoupling\nInput Range\nDC\nRawData\nVoltage\nFFT_PowerSpec\nCustomization\n±10\nADD DATATYPE](.mcm-216-218-50m-00024-1000-10/250243f5b8cd60814ce4b6e266706c26b38f53ead1167adb6135f269a40e332d.jpg)

Figure 3-26: DataType

An input range can be selected, as below.

![Channel Config\nAdd Config\nEnable the Channel\nCoupling\nDC\n±10\nData Type\nVoltage\n±2.5\n±1.25\n±0.3125\nADD CONDITION\nADD DATATYPE](.mcm-216-218-50m-00024-1000-10/81297ae06cf034e8a36e74c778e2d3e5ee799da0f9c621ce11b7be36b35fd9b0.jpg)

Depending on the channels selected, the Channel Config properties of each channel will be shown.

![**Title:** Click and Add\n\n**Labeled Blocks:**\n*   AI0\n*   AI1\n*   AI2\n*   AI3\n*   AI4\n*   AI5\n*   AI6\n*   AI7\n*   AI8\n*   AI9\n*   AI10\n*   AI11\n*   AI12\n*   AI13\n*   AI14\n*   AI15\n\n**Connections:**\nThere are no connecting lines or arrows between the blocks. They are arranged in a grid layout.\n\n**Footer Text:**\nOnly enabled channels can be added.](.mcm-216-218-50m-00024-1000-10/ac2e48872b8ac896fdedc1d8a2c40000163bf0566f9156794b411c21826cf545.jpg)

![Channel Config\nAI0 Config\nAI1 Config\nAI2 Config\nAI8 Config\nAI11 Config\nAI15 Config](.mcm-216-218-50m-00024-1000-10/d261e42205846585f891e65e164e7c0df082d79a61866dc130fde86c36aa6f9f.jpg)

The MCM-216/218 has built-in functionality for several common data types and also supports user-customized data types, as detailed in the table below. If two or more data types are required for an analog input channel, select ADD DATATYPE for each additional data type.

<table><tr><td>Data Type</td><td>Description</td></tr><tr><td>Raw Data</td><td>The raw data generated by ADC (16-bit, 2&#x27;s complement)</td></tr><tr><td>Voltage</td><td>Transferred from raw data</td></tr><tr><td>FFT_PowerSpec</td><td>Power spectrum transferred by fast Fourier transform (FFT)</td></tr><tr><td>Customization</td><td>Customized data type set by user</td></tr></table>

ADD CONDITION provides an event warning mechanism. When a given condition is triggered, a warning message will display on the Data Condition page.

![Channel Config\nAIO Config\nEnable the Channel\nCoupling Input Range\nDC ±10\nData Type\nVoltage\nADD CONDITION\nName Severity Direction Value\nRule Warning Above 1\nADD DATATYPE](.mcm-216-218-50m-00024-1000-10/31b8cc91f74d56e274be0635b8e64b3eba34505eda64714f52b115aae4ec641f.jpg)

Figure 3-27: Add Condition

After the desired settings have been configured, click APPLY to activate your changes.

# Analog Output

![Device Settings\nAnalog Input	Analog Output\nAO Channel Config\nAO0 Config\nConfig the Channel\nAO Output Type\nClosed\nAO1 G\nVoltage\nCurrent\nClosed\nAPPLY](.mcm-216-218-50m-00024-1000-10/2f155e8d30c20f9a4ff9e63ec2b541b62d7b3f6ee09d2558a186f2acaff1ae6b.jpg)

The MCM-216/218 has two analog output channels: output voltage, or current with a predefined value.

![AO1 Config\n✓ Config the Channel\nAO Output Type	Current Value\nCurrent	20\nRange 0 - 20](.mcm-216-218-50m-00024-1000-10/c2636938b6d28f534d36587190d49165ac1d0a6557c2165b34c60a5c66bb1937.jpg)

The Data Manager/Data Capture page displays DAQ results in real time. You can use the data capture function in lab testing or as a portable DAQ device. Raw data and Voltage can be converted to charts for troubleshooting.

![Capture Data\nData In JSON\n{ 2 items\n  'Data' : ( 2 items\n    0 : { 1 item\n      'AI0' : { 1 item\n        'OA_g(RMS)' : (...) 1 item\n        }\n    }\n    1 : { 1 item\n    'AI1' : { 1 item\n      'Voltage' : 10240 items\n        ( 0 - 1000 )\n        ( 1000 - 2000 )\n        ( 2000 - 3000 )\n        ( 3000 - 4000 )\n        ( 4000 - 5000 )\n        ( 5000 - 6000 )\n        ( 6000 - 7000 )\n        ( 7000 - 8000 )\n        ( 8000 - 9000 )\n        ( 9000 - 10000 )\n        ( 10000 - 10240 )\n    }\n    }\n    )\n    'Date' : '2019-10-25 11:06:07.972'\n}](.mcm-216-218-50m-00024-1000-10/6adbb971be4958c271be8d2cde88401c7d199ed9ad78299774bb55e3173107f4.jpg)

Figure 3-28: Data Capture

![AI Mission Profile Management\nSave Profile	Load Default	Select Mission Profile\nSAVE PROFILE	LOAD DEFAULT	選擇檔案	未選擇任何檔案\n		LOAD SETTING\nAI Data Mode\nOne Shot (default) Stream Mode with TCP Socket\n'You can set TCP Socket in 'Menu' - 'Data Manager' - 'TCP Socket' in one shot mode.](.mcm-216-218-50m-00024-1000-10/f9b1aae0a20a93d6436d5859d5c4748349852215ac1ad55128a253aeb0371259.jpg)

Figure 3-29: Device Settings

Settings may be saved as a Mission Profile (JSON file) for backup or for convenient duplication on other MCM-216/218 devices. Click SAVE PROFILE to download the file to your PC. To import a Mission Profile to an MCM-216/218 device, click Choose File under Select Mission Profile and select the desired configuration file. All settings will change according to that file. Alternatively, clicking LOAD DEFAULT will restore all settings to their default values. After any change to device settings, the APPLY button must be clicked in order to activate the changes.

If a mission is already running while attempting to apply new changes, a confirmation window will appear. If you’re ready for the MCM-216/218 to cancel its previous mission and start running the new mission, click YES.

![Device Settings\nAI/DI Mission Profile Management\nApply New Mission ?\nA previous mission is still running. Do you want to cancel the existing mission\nand apply new mission?\nYES	NO\nAiring Input	Rising Output	Digital Input	Digital Output\nDevice Config\nInputType	Trig Source	Trig Direction	Trig Value\nPseudoDifferential	NoWait	Rising	1](.mcm-216-218-50m-00024-1000-10/39354eca85e70ef527c9804942a1911e14b6a1d31f31a31158f6518d95de365a.jpg)

Figure 3-30: Apply a New Mission

This page intentionally left blank.

# 4 DAQ Missions

The MCM-216/218 supports various modes of operation that users can choose from to quickly integrate into their systems.

# 4.1 Usage Behaviors

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, Continuous Data, and Passive Data. Choosing between them depends on how frequently data must be retrieved. Figure 4-1 on page 54 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-216/218 provides a REST API and sample code in C#, Python, and JavaScript. Alternatively, for continuous data mode, MCM-216/218 provides a Streaming SDK and associated C/C++ sample code.

# 4.1.1 Web Console

The MCM-216/218 has a built-in, easy-to-use web console that implements all device functionalities. By logging into the web console through a connected host PC, users can see all of the device’s current settings, each feature it provides, and any vibration data it has collected. See “Web Console” on page 23.

![**Labeled Blocks:**\n\n*   Configuration / See data in web\n*   Periodically Polling Data\n*   Passively get data\n*   Continuous Data\n*   Web browser\n*   REST API\n*   TCP socket - server mode\n*   Streaming SDK\n*   Web Console\n*   REST Server\n*   TCP Socket - client mode\n*   Data in JSON format\n*   Filtered Data\n*   Raw Data\n\n**Connections:**\n\n*   **Web browser** connects to **Web Console** (downward arrow)\n*   **REST API** connects to **REST Server** (downward arrow)\n*   **Streaming SDK** connects to **Raw Data** (long downward arrow)\n*   **Web Console** connects to **REST Server** (rightward arrow)\n*   **Raw Data** connects to **Filtered Data** (upward arrow)\n*   **Filtered Data** connects to **Data in JSON format** (upward arrow)\n*   **Data in JSON format** connects to **REST Server** (upward arrow)\n*   **Data in JSON format** connects to **TCP Socket - client mode** (upward arrow)\n*   **TCP Socket - client mode** connects to **TCP socket - server mode** (upward arrow)](.mcm-216-218-50m-00024-1000-10/4355ed58c709928ba82d18065b7166318ab8ef9a1645d8d659d05a0b4a2fed6b.jpg)

Figure 4-1: Operational Modes

# 4.1.2 Periodic Polling

A RESTful API is provided to facilitate periodic data polling. The REST document can be found on the web console’s menu bar.

![ADLINK\nMenu\nDevice: MCM-204 Account: administrator Role: admin\nSystem Information\nRestful API Doc](.mcm-216-218-50m-00024-1000-10/8370a607b0b339fc0db1e5513a10f064fc75a5b0d656c3644f81c3c20749d838.jpg)

Figure 4-2: RESTful API

Using this API, functionalities shown in the web console can be implemented in your own custom software. Function references and sample code in Python, JavaScript, and C# are available for download on the MCM-216/218 product web page:

www.adlinktech.com/Products/IoT\_solutions/Smart\_Factory/ MCM-210\_Series

# 4.1.3 Passive Data

The conventional message exchange pattern of the MCM-216/218 for Periodic Polling and Continuous Data modes is request-response, with the MCM-216/218 serving as responder. After receiving a query from the host, the MCM-216/218 responds with the requested data. However, for some applications it’s desirable for the host server to passively wait for data from the client. In such cases, a TCP socket function can instruct the MCM-216/218 to automatically send data to the host server whenever data is generated. See “Data Manger/TCP Socket (for one-shut query mode)” on page 34.

# 4.2 Custom Filtering Algorithms

The MCM-216/218 offers flexible support options for custom filtering algorithms. Users can easily import their own domain-knowledge algorithms to the MCM-216/218. Custom filtering algorithms must be written in C or C++ and compiled under Linux.

Use the following steps to create a custom filtering algorithm.

1. Download and extract the Linux toolchain:

https://releases.linaro.org/components/toolchain/binaries/6.2-2016.11/arm-linux-gnueabihf/gcc-linaro-6.2.1-2016.11-x86\_64\_arm-linux-gnueabihf.tar.xz

2. Download CustomizedAlgo.zip from the MCM-216/218 web page and extract the CalStatistic (C++) and CalRMS (C) sample program folders.

www.adlinktech.com/Products/IoT\_solutions/Smart\_Factory/ MCM-210\_Series

3. Place the extracted CalRMS and Linux toolchain folders in the same file path.

![gcc-linaro-6.2.1-\n2016.11-x86_64_\narm-linux-\ngnueabihf](.mcm-216-218-50m-00024-1000-10/d2e2a9bfc73037070217f14cb9c8337953e06b9a1ccb83f14f361997175c7641.jpg)

![The image features an orange folder icon with a white tab on its upper left corner. Centered below the icon is the text 'CalRMS' in black, sans-serif lettering.](.mcm-216-218-50m-00024-1000-10/db3fc8c5854ff493cc712608d4b2620e17f9e0cb1f83ccac4a4edb6b469e8ee4.jpg)

4. Run the “make” command from within the CalRMS folder to generate a customAlgo.so file.

![The image displays a white document icon with a folded top-right corner. Inside the icon, the text reads:\n\n'customAlgo\nCustom Algorithm - Description\nThis document describes the custom algorithm used in the system. It\nincludes details about the algorithm's purpose, functionality, and\nimplementation. The algorithm is designed to optimize the process\nby analyzing input data and generating output based on specific\ncriteria. The algorithm uses a combination of mathematical\nformulas and logical operations to achieve the desired results.\nThe input parameters are validated before processing to ensure\ndata integrity and accuracy. The output is formatted according to\nthe specified requirements.\nThe algorithm is modular, allowing for easy updates and\nmaintenance. It is written in a high-level programming language\nto ensure readability and portability. Performance optimization is a key consideration, with efforts made\nto minimize resource usage and processing time.\nThe algorithm has been tested extensively to ensure reliability and\nrobustness under various conditions.\nThis documentation serves as a reference for developers and\nusers who need to understand the inner workings of the algorithm.'\n\nBelow the icon, the text 'customAlgo.so' appears in black.](.mcm-216-218-50m-00024-1000-10/956339d1dd50e19717dfc02bd46008a0d6d247027723d8dd330eaa41be7aff85.jpg)

5. Upload customAlgo.so to the MCM-216/218 from the web console System Setting page.

![Customization library Upload\nLibrary Upload: Choose File No file chosen\n(Please Select a. so file.)\nUPLOAD](.mcm-216-218-50m-00024-1000-10/1cce99d6d3ab24dba487f4312fc09512ed53b35388b0f830147f8a7caa58339c.jpg)

6. After it uploads, log back into the web console.

![You have to re-login .\nRe-login](.mcm-216-218-50m-00024-1000-10/cc76e99b8dedc0026f67320c1c8ed80d22aeee2ea08fb0047771f1b580893c6e.jpg)

7. After logging in, choose Customization as the data type, set parameters as needed, then click APPLY to apply the task to the MCM-216/218.

![AI0 Config\nEnable the Channel\nCoupling Input Range\nAC ±10\nData Type Customization Parameter\nCustomization 'rms'\nADD DATATYPE\nSensor Type Sensor Sensitivity (mV/g) IEPE\nAccelerometer 100 Enable\nAI1 Config\nAI2 Config\nAI3 Config](.mcm-216-218-50m-00024-1000-10/f7cfe8ff5ec81333cd820bfaae52768bc8c40f0bb26a203eb6b24d0e9d5422ac.jpg)

![A white rectangular button with a thin reddish-brown border containing the centered text 'APPLY' in red, uppercase letters.](.mcm-216-218-50m-00024-1000-10/fada5276cf4480d6b0db48d08daeb761430612005dbd734eae8f8b1096dd0a3a.jpg)

8. Check the results on the data capture page.

![1 item\n'Data': ( 2 items\n0 : { 1 item\n'AI0': { 1 item\n'Customization': ( 1 item\n0 : 1.0328374\n)\n}\n}\n1 : { 1 item\n'Date': '2019-10-23 16:47:21.967'\n}](.mcm-216-218-50m-00024-1000-10/e8fb736fa4c22380493c2350b6b1b47395df0e4e925ca4ba911131f658350070.jpg)

# Important Safety Instructions

For user safety, please read and follow all instructions, Warnings, Cautions, and Notes marked in this manual and on the associated device before handling/operating the device, to avoid injury or damage.

S'il vous plaît prêter attention stricte à tous les avertissements et mises en garde figurant sur l'appareil , pour éviter des blessures ou des dommages.

X Read these safety instructions carefully.
X Keep the User’s Manual for future reference.
X Read the Specifications section of this manual for detailed information on the recommended operating environment.
X The device can be operated at an ambient temperature of 50ºC.

When installing/mounting or uninstalling/removing device, or when removal of a chassis cover is required for user servicing:

Z Turn off power and unplug any power cords/cables.
Z Reinstall all chassis covers before restoring power.

X To avoid electrical shock and/or damage to device:

Z Keep device away from water or liquid sources.
Z Keep device away from high heat or humidity.
Z Keep device properly ventilated (do not block or cover ventilation openings).
Z Always use recommended voltage and power source settings.
Z Always install and operate device near an easily accessible electrical outlet.
Z Secure the power cord (do not place any object on/over the power cord).
Z Only install/attach and operate device on stable surfaces and/or recommended mountings.

X If the device will not be used for long periods of time, turn off and unplug it from its power source
Never attempt to repair the device, which should only be serviced by qualified technical personnel using suitable tools

X A Lithium-type battery may be provided for uninterrupted backup or emergency power.

![The image displays a yellow triangular warning sign with a black border containing a black exclamation point. Below the triangle, the text 'CAUTION:' is printed in black capital letters.](.mcm-216-218-50m-00024-1000-10/9173ee630286abd67f248812cb0c250a35dd37199557071b5a13e456d71a7a13.jpg)

Risk of explosion if battery is replaced with one of an incorrect type; please dispose of used batteries appropriately.

Risque d’explosion si la pile est remplacée par une autre de type incorrect. Veuillez jeter les piles usagées de façon appropriée.

X The device must be serviced by authorized technicians when:

Z The power cord or plug is damaged.
Z Liquid has entered the device interior.
Z The device has been exposed to high humidity and/or moisture.
Z The device is not functioning or does not function according to the User’s Manual.
Z The device has been dropped and/or damaged and/or shows obvious signs of breakage.

Disconnect the power supply cord before loosening the thumbscrews and always fasten the thumbscrews with a screwdriver before starting the system up.

X It is recommended that the device be installed only in a server room or computer room where access is:

Z Restricted to qualified service personnel or users familiar with restrictions applied to the location, reasons therefor, and any precautions required.

Z Only afforded by the use of a tool or lock and key, or other means of security, and controlled by the authority responsible for the location.

<table><tr><td>&lt;img src="images/a56dbb1261911b4a93608057a3aa1b5518b03b03d0412f1767786ba606ca18a1.jpg"/&gt;</td><td>BURN HAZARDTouching this surface could result in bodily injury.To reduce risk, allow the surface to cool before touching.RISQUE DE BRÛLURESNe touchez pas cette surface, cela pourrait entraîner des blessures.Pour éviter tout danger, laissez la surface refroidir avant de la toucher.</td></tr></table>

# Getting Service

Ask an Expert: http://askanexpert.adlinktech.com

# ADLINK Technology, Inc.

9F, No.166 Jian Yi Road, Zhonghe District

New Taipei City 235, Taiwan

Tel: +886-2-8226-5877

Fax: +886-2-8226-5717

Email: service@adlinktech.com

# Ampro ADLINK Technology, Inc.

5215 Hellyer Avenue, #110

San Jose, CA 95138, USA

Tel: +1-408-360-0200

Toll Free: +1-800-966-5200 (USA only)

+1-408-360-0222

Email: info@adlinktech.com

# ADLINK Technology (China) Co., Ltd.

300 Fang Chun Rd., Zhangjiang Hi-Tech Park

Pudong New Area, Shanghai, 201203 China

Tel: +86-21-5132-8988

Fax: +86-21-5132-3588

Email: market@adlinktech.com

# ADLINK Technology GmbH

Hans-Thoma-Straße 11

D-68163 Mannheim, Germany

Tel: +49-621-43214-0

Fax: +49-621 43214-30

Email: emea@adlinktech.com

Please visit the Contact page at www.adlinktech.com for information on how to contact the ADLINK regional office nearest you:
[🔗 Link to the original document](.mcm-216-218-50m-00024-1000-10/mcm-216-218-50m-00024-1000-10.pdf)