# SDAQ-204

Standalone Ethernet DAQ for Distributed Machine Condition Monitoring

User's Manual

![Exterior view of a ADLINK SDAQ-204 networking device with multiple ports and connectors (no readable text or symbols beyond branding)](.sdaq-204-50m-00119-1000-10/2e718fa498c270ced014e63705984117e0a3163fdd078399d92a718df0ab30f6.jpg)

Manual Rev.: 1.0

Revision Date: March 14, 2023

Part No: 50M-00119-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>2023-03-14</td><td>Initial Release</td></tr></table>

# Preface

# Copyright © 2023 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](.sdaq-204-50m-00119-1000-10/32da99ccade0f701153a0846c4899668c38b706ce62488190d8a97e0f550ac49.jpg)

Battery Labels (for products with battery)
![Symbol of a trash bin crossed out by two diagonal lines (no text or numbers present)](.sdaq-204-50m-00119-1000-10/06dced15077ea2c52ecce6f0195a892582aac6539f090f1d468046c88f3510ff.jpg)

![Recycling symbol icon with three chasing arrows inside a square frame (no text or labels)](.sdaq-204-50m-00119-1000-10/d72a9a0143463624fe895f6ca92bc60e7c60827ae6974fdf6a0280abd80f2b30.jpg)

Li-ion

![RECYCLE\nRBRC\nLi-ion\n7.800.822.8837](.sdaq-204-50m-00119-1000-10/8987cc2dc2b90c65b7934c160604eb5d68dded9b592e2c6686bf76a8d41c6746.jpg)

![Abstract geometric pattern with interlocking X and Y shapes (no text or symbols)](.sdaq-204-50m-00119-1000-10/2462a34a3a17cab143e87c702ebf1f90609d24ceb52a45513664d9855f7e23e1.jpg)

廢電池請回收

# California Proposition 65 Warning

![A yellow triangular warning sign with a thick black border containing a large black exclamation point in the center.](.sdaq-204-50m-00119-1000-10/c96cfd318cc20fbc1662f2494f27beccf1f26dbcfab8d5f94376844ebf6015d8.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 an icon of a white document page with a folded top-left corner and horizontal lines running across it. A large, thick red checkmark is superimposed over the center of the page.](.sdaq-204-50m-00119-1000-10/7c1f8353c9c3e777caa41d0a81cac14496bab8b8b65d4c905a40631f42333c2d.jpg)
NOTE:

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

![The image displays a standard warning symbol: a yellow equilateral triangle with a thick black border. Centered inside the triangle is a large black exclamation point (!). A thin black vertical line is visible along the right edge of the image.](.sdaq-204-50m-00119-1000-10/1cb084846cc797a4f367f27eb982e281c23fc7f915edb4d72ce172a2a6b46de7.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 dark red triangle with a thin black border. Inside the triangle is a white exclamation mark. The background is white.](.sdaq-204-50m-00119-1000-10/bb6dc3d30932cfaf79d63d032b36c4aa155a6a1b21269ada3dc8cac8f6f53983.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.1 Features.... 2
1.2 Applications 2
1.3 Specifications.... 3
1.4 Mechanical Drawings.... 6
1.5 I/O Connectors.... 13

# 2 Getting Started 17

2.1 Unpacking the SDAQ-204 17
2.2 Connecting to I/O.... 17
2.3 Connecting/Disconnecting Power 18
2.4 Checking Device Status.... 18
2.5 Usage Scenarios 18

# 3 DAQPilot.... 21

3.1 DAQPilot ACE 21
3.2 iApp Development and Device Management 22

# 4 Web Console.... 35

4.1 Web Console Login 35
4.2 Web Console Menu 37
4.3 DAQ Mission.... 47

# 5 DAQ Missions.... 53

5.1 Usage Behaviors 53
5.2 Custom Filtering Algorithms.... 56

# Important Safety Instructions.... 59

# Getting Service 61

# List of Figures

Figure 1-1: Front View 6

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

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

Figure 1-4: Right Side View 9

Figure 1-5: DIN Rail Mount Dimensions 10

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

Figure 1-7: Wall Mount Assembly 12

Figure 1-8: BNC Connector Polarity .... 13

Figure 4-1: Get IP Address from DAQPilot ACE....35

Figure 4-2: Web Console Login Page 36

Figure 4-3: Disabling DAQPilot Setting.... 37

Figure 4-4: Web Console Welcome Page....38

Figure 4-5: Menu Icon....38

Figure 4-6: System Information....39

Figure 4-7: Peripheral Devices 40

Figure 4-8: Data History....41

Figure 4-9: Mission Management 42

Figure 4-10: Change Password 42

Figure 4-11: Account Management....42

Figure 4-12: Network Settings 43

Figure 4-13: System Settings.... 44

Figure 4-14: Upload Customization/Firmware Files....45

Figure 4-15: TCP Socket 46

Figure 4-16: Device Configuration 47

Figure 4-17: DataType....48

Figure 4-18: Add Condition....50

Figure 4-19: Data Capture 51

Figure 4-20: Device Settings....51

Figure 4-21: Apply a New Mission 52

Figure 5-1: Operational Modes 54

Figure 5-2: RESTful API 54

Figure 5-3: DAQPilot Setting....55

This page intentionally left blank.

# 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 SDAQ-204 is a standalone Ethernet DAQ that acquires vibration signals from a monitored machine and transforms this signal from raw data into filtered data. By capturing data such as FFT, power spectrum, overall value (OA), etc., with a standalone DAQ, the SDAQ-204 plays a critical role in pre-processing at the edge. Continuous high-volume data generated in the field can be converted to filtered data, significantly reducing its size. This in turn dramatically reduces network bandwidth traffic as well as the backend server's computing burden.

The SDAQ-204 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 SDAQ-204's compact size also makes it easy to install in the limited confines of an electrical control cabinet.

# 1.1 Features

▶ Standalone Ethernet DAQ for edge computing
▶ RESTful API reports machine conditions to IT system
▶ DAQPilot SDK for continuous data acquisition
▶ Built-in web console for easy configuration and to facilitate its use as a portable DAQ
▶ Supports custom filtering algorithms for edge data
▶ 4-channel, 24-bit simultaneous sampling analog input up to 128 kS/s
▶ System automatically resumes its previous running state upon power recovery
▶ Supports IEPE 4mA excitation current output on each analog input to drive accelerometer
▶ 4-channel programmable isolated digital input/output (software selectable)
▶ Two 1 Gb Ethernet ports for cascading

# 1.2 Applications

▶ Distributed machine condition monitoring
▶ Vibration detection
▶ Acoustic measurement
▶ Environmental noise analysis

# 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>32 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 and USB storage 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>8.8 W max.</td></tr><tr><td>Communication Interfaces</td><td>Web console, RESTful API, DAQPilot SDK,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>4 (simultaneous, BNC type)</td></tr><tr><td>Resolution</td><td>24-bit</td></tr><tr><td>Maximum Sampling Rate</td><td>128 kS/s and can be adjusted to 1 kS, 2 kS, 4 kS, 8 kS, 16 kS, 32 kS, 64 kS</td></tr><tr><td>Input Range (voltage)</td><td>±10 V, ±1.25 V</td></tr><tr><td>Input Configuration</td><td>Pseudo-differential</td></tr><tr><td>Input Coupling</td><td>DC/AC</td></tr><tr><td>IEPE</td><td>4 mA, compliance voltage +24 V</td></tr><tr><td>Sensor Type</td><td>IEPE sensor (vibration detection)</td></tr><tr><td>Offset Error</td><td>±0.1 mV</td></tr><tr><td>Gain Error</td><td>±0.05% of FSR</td></tr><tr><td>-3dB Bandwidth</td><td>0.43 x sampling rate</td></tr><tr><td>Flatness</td><td>±0.01 dB (10 Hz to 10 kHz)</td></tr><tr><td>AC Cut-off Frequency (-3dB)</td><td>0.4 Hz</td></tr><tr><td>AC Cut-off Frequency (-0.1dB)</td><td>2.4 Hz</td></tr><tr><td>Trigger Sources</td><td>Software, digital trigger, analog trigger, built-in button</td></tr><tr><td>Overvoltage Protection</td><td>±50 V</td></tr><tr><td>Input Impedance</td><td>200 kΩ between positive input and negative input115 Ω between negative input and analog ground1.5 kVdc between analog ground and chassis ground</td></tr><tr><td>Crosstalk</td><td>-100 dB</td></tr><tr><td>Dynamic Range</td><td>95 dB</td></tr><tr><td>THD (1kHz)</td><td>-100 dB</td></tr><tr><td>THD+N (1kHz)</td><td>-95 dB</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 DI/O (digital input and output can be configured)</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:  $\text{VIL} = 0.8 \text{ V max.}, \text{IIL} = 0.2 \text{ mA max}.$  $\text{Logic high: VIH} = 2.0 \text{ V min.}, \text{IIH} = 0.2 \text{ mA max.}$ </td></tr><tr><td>Overvoltage Protection</td><td>±50 V</td></tr><tr><td>Supported Modes</td><td>Static digital input/outputTachometer support (DI 0 only; range: 0.6 Hz~500 kHz; 500 kHz for 1 microsecond)External digital trigger in</td></tr></table>

# 1.3.4 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>4x BNC + 2x 6-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.5 Environmental

<table><tr><td colspan="2">Environmental Specifications</td></tr><tr><td>Operating Temperature</td><td>0°C to 50°C (32°F to 122°F)</td></tr><tr><td>Storage Temperature</td><td>-20°C to 70°C (-4°F to 158°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\nDI/O\n0\n2\nD.GND\nA.GND\nDI/O\n1\n3 PWR\nD.GND\nSYS\nA.GND I/O\nUSB\nAI 0\nAI 1\nAI 2\nAI 3\n126.5](.sdaq-204-50m-00119-1000-10/c9fea6427a66d5be9c4758997207319f7f867df383ed1a4055d447f707b6666a.jpg)

Units: mm

Figure 1-1: Front View

![40\n9-30 V+\nVDC\nV.\n111.65\n2 1\nRESET\nFn](.sdaq-204-50m-00119-1000-10/b655dd897916d00dc188f04fb4e9d6a675b7731a3e300dbae1825c936e9bb54a.jpg)

Units: mm
Figure 1-2: Top View

![Units: mm\n126.5\n111.65](.sdaq-204-50m-00119-1000-10/c63d432b2bed117b9b8cb490b35ea1feea001a73cece949e37a7d104f0a8db94.jpg)

Figure 1-3: Left Side View

![111.65\nUnits: mm\n126.5](.sdaq-204-50m-00119-1000-10/1f80f655b1277a7c94dc4e07d95cdbd96604996a525259a74b2dc00a2bcbb12b.jpg)

Figure 1-4: Right Side View

# 1.4.2 DIN Rail Mount

The DIN rail mount may be attached to the SDAQ-204 using two flat head screws (included).

![15\n89.18\n80.43\n78.38\n70.75\n41.1](.sdaq-204-50m-00119-1000-10/0fd8e8b9ee48b31cd8fd4f7daec73330080ab215d5e074e12b76d35848706cdf.jpg)

Figure 1-5: DIN Rail Mount Dimensions

Units: mm

# 1.4.3 Wall Mount

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

![80.0\n61.6\n20.0\n5.0\n70 100 106\nR5\nØ 5.2\nØ 4.5\nUnits: mm](.sdaq-204-50m-00119-1000-10/e7656fa9fda9f62a0461da014efa0e192deecae2dc7089f40239aa0e1a11b95a.jpg)

Figure 1-6: Wall Mount Dimensions

![Technical line drawing of an electronic device housing with mounting brackets and internal components (no text or symbols)](.sdaq-204-50m-00119-1000-10/5add3126257cfbc8e39fc13f00e994aac5eb9117f8432a6d23745381e0117332.jpg)

Figure 1-7: Wall Mount Assembly

# 1.5 I/O Connectors

The SDAQ-204 provides rich peripherals, including:

▶ 4 analog inputs
▶ 4 digital input and output connections
▶ 1 temperature sensor input
▶ 2 USB 2.0 (for Wi-Fi dongle and USB storage only)
▶ 1 hotkey for triggering
▶ 1 reset pin for restoring the device to factory default settings
▶ 2 Ethernet ports for host connection and cascading
▶ 4 LED indicator lights

# 1.5.1 Analog Input BNC Connector

The SDAQ-204 module is equipped with four BNC connectors to receive voltage signals from various sources. For sensors requiring excitation, such as accelerometers or microphones, the IEPE excitation current can be enabled to reduce the wiring effort.

![AI 0\nNegative\nPositive](.sdaq-204-50m-00119-1000-10/c0521b3b57a0a5990da1ff1b311a5e7ae46ebc4fd8da5c36990d35b5aa5eddb1.jpg)

Figure 1-8: BNC Connector Polarity

# 1.5.2 Digital Input and Output

The SDAQ-204 provides 4 digital input/output channels labeled 0, 1, 2, and 3. Each channel can be set for input or output modes independently through the web console. Use D.GND for signal grounding with digital input/output. Use A.GND for signal grounding with analog input.

![DI/O\n0\n2\nD.GND\nA.GND\nDI/O\n1\n3\nD.GND\nA.GND](.sdaq-204-50m-00119-1000-10/d3634b808e17c82f728e7b4848313047f47651a48b4104cb2bfbf24704e9d13a.jpg)

# 1.5.3 Temperature Sensor Input

The SDAQ-204 allows you to monitor the temperature of a target device or environment between -50 to 150°C using the temperature sensor provided. Connect the temperature sensor leads to the connector as shown.

![AI 2\nAI 3\nTemp. Sensor Input](.sdaq-204-50m-00119-1000-10/882bf0c029d28bc526f838329c5ee80d7b234779dffef2c2dcabe722fb016a11.jpg)

# 1.5.4 Reset Pin for Factory Default

Restore the SDAQ-204 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 displays a white document icon with a folded top-left corner and faint horizontal lines running across it. A large, bold red checkmark is superimposed over the center of the document, slanting upwards from left to right.](.sdaq-204-50m-00119-1000-10/b29b84e3b60a136299cb23a2f5b635a5049ba33e7743b4f602c7ae7a0f1933db.jpg)
NOTE:

Users can optionally configure the SDAQ-204 to retain its current network settings rather than restoring the factory defaults. See “Web Console” on page 35.

![40\n9-30 V\nVDC V\n111.65\n2 1\nRESET\nReset Pin\nFn](.sdaq-204-50m-00119-1000-10/6f3535a3756d0525df1beae6f468b5d6d2cdd505ea842c85174a37d8332c5d39.jpg)

Units: mm

# 1.5.5 Ethernet Ports

The SDAQ-204 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 SDAQ-204 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 SDAQ-204 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.

# 2 Getting Started

# 2.1 Unpacking the SDAQ-204

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

▶ SDAQ-204
▶ DIN rail mount kit with 2x flat head screws
▶ Temperature sensor with 3 meter cable
▶ Quick Start Guide
▶ Optional accessories (if applicable):
▷ Wall mount kit with 4x pan head screws
▷ 40W AC-DC adapter

![The image displays a warning sign featuring a red triangle with a white border. Inside the triangle is a black exclamation point. Below the triangle, on a black background, is the word 'WARNING' in white, capital letters.](.sdaq-204-50m-00119-1000-10/4e45339f0cde098ae997a16b090696c7a2b59c142b69fbe021ce9c8f6e758597.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, plug in the accelerometer with a BNC type connector.
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 SDAQ-204 devices, use the second Ethernet port to cascade them together. Cascading reduces the number of ports needed to connect devices.

![This image shows a vertical warning sign. At the top is a yellow triangle with a black border containing a black exclamation point with a dot in the center. Below the triangle, the text 'CAUTION:' appears in black capital letters.](.sdaq-204-50m-00119-1000-10/e3deba06ed20f4796381fe2f52a78a5ff43c2a37db6d9909ef11977dac0289ca.jpg)

If connecting SDAQ-204 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 SDAQ-204 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 with a black border. Inside the triangle is a large black exclamation point. Below the triangle, the text 'CAUTION:' is written in black capital letters.](.sdaq-204-50m-00119-1000-10/2f86a48ca80fbca8d4d5653c1d3591779b3b93b9248254ec754c7182bd75211c.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 35.

# 2.5 Usage Scenarios

The SDAQ-204 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 Deploy User-Developed Analytics Apps

The DAQPilot ACE software allows users to easily manage Smart DAQ devices and deploy user-developed applications on them.

DAQPilot ACE provides the following features:

▶ IDE for Python programming, allowing users to develop and debug iOS app remotely
▶ Provides a dashboard widget to show the data immediately
▶ Auto-discovers all supported devices on the local network
- Tags function allows users to identify or group multiple devices
▶ Deploys iApp to device via one-click function

For more information, see "DAQPilot" on page 21.

# 2.5.2 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 SDAQ-204 has a built-in dashboard to show the results of acquired data. The web-based console is also a convenient tool for users unfamiliar with DAQ behavior or programming. see “Web Console” on page 35.

# 2.5.3 Periodic Polling (REST API)

Many distributed machine condition monitoring applications acquire device status periodically, for example, every minute, or hourly. The SDAQ-204 retains captured data in the REST data format. Especially in IT systems, user applications frequently adopt REST APIs because they are intuitive. The SDAQ-204 emulates all functions supported by REST APIs, and the SDAQ-204 embedded middleware executes related operations and transfers the filtered data in JSON format. All queries from a REST command are handled by the SDAQ-204 and reply accordingly. see “DAQ Missions” on page 53.

# 2.5.4 Continuous Data (DAQPilot SDK)

Some applications need to acquire streaming data continuously. To transmit high volumes without data loss, raw data without any transformation is best. For users needing to access the DAQ library directly, the DAQPilot SDK is the proper method. By using the streaming API, all queried raw data may bypass the SDAQ-204's middleware and route directly to the host PC via Ethernet. see “Continuous Data” on page 55.

# 2.5.5 Passive Data (TCP Socket)

For passively retrieving data, it is suitable to use a TCP socket with the SDAQ-204 in client mode. Whenever data is generated, the SDAQ-204 will be triggered to establish a TCP connection with the host PC and actively transmit the data. see “Web Console” on page 35.

# 3 DAQPilot

DAQPilot is a software package for ADLINK DAQ products. It provides an integrated management utility that includes device management, iApp creation and allows deployment of user-defined data analytics to DAQ devices for enhanced smart capabilities and provides a unified SDK that allows users to stream continuous time-series data. The SDK is task-oriented and optimized for typical DAQ applications.

It available for download on the SDAQ-204 product web page:

https://www.adlinktech.com/Products/Data\_Acquisition/SmartDAQ/SDAQ-204

# 3.1 DAQPilot ACE

DAQPilot ACE is able to auto-discover all supported devices on the local network and features an intuitive user interface for providing device management functionalities including displaying device information, iApp deployment to devices and setting Tags to identify or group multiple devices. Tags are a convenient way for mass iApp deployment to grouped devices.

# 3.1.1 Installation

For optimal performance, make sure that the ACE software is properly installed on a client system computer that is properly linked with all ACE devices on the same LAN.

1. Install ACE devices.
2. Connect each ACE device to the same LAN with an Ethernet cable.
3. Power on each ACE device.

Note: It can take up to 2 minutes for the devices to link-up.

# 3.2 iApp Development and Device Management

ACE contains two major parts, iApp development and device management. This section includes a tutorial on how to create an iApp before deployment. iApps are saved in a repository and can be deployed to devices through the device management function.

# 3.2.1 iApp Development

Follow these steps to create a Python-based iApp.

1. Click iApp Creator from the left sidebar.

![ADLINK Connection Explorer Version: 22.10.1110\nDAQ Pilot\nDevice Manager\niApp Creator\nACE Handbook\nManage iApps\nRefresh iApps\nCreate iApp\niApp name ↑↓\nOperations\nOEE\nEdit iApp\nDelete iApp\nPower_Monitoring\nEdit iApp\nDelete iApp\nVibration\nEdit iApp\nDelete iApp](.sdaq-204-50m-00119-1000-10/a90bf7dd32df5c1c6f0ae7012539ad67278c3c80d124686666c1ca772360de43.jpg)

# 2. Click Create iApp to create a new iApp.

![ADLINK Connection Explorer Version: 22.10.1110\nDAQ Pilot\nDevice Manager\niApp Creator\nACE Handbook\nManage iApps\nRefresh iApps\nCreate iApp\niApp name ↑↓\nOperations\nOEE\nEdit iApp Delete iApp\nPower_Monitoring\nEdit iApp Delete iApp\nVibration\nEdit iApp Delete iApp](.sdaq-204-50m-00119-1000-10/7ac03d1ad7393b521981146a9003f7f868043b0628e167c70d896c7f9b745dd9.jpg)

# 3. Select an iApp template to start from.

![Create iApp\nName: iApp name\nSelect a template: Simpleio AI\nEmpty\nSimpleio AI\nREST server\nREST client\nDASK AI\nDASK AO\n✓ Create](.sdaq-204-50m-00119-1000-10/b8d9cee16347c9f5657eb96328e21f94076dab8e3de780b986831477914be454.jpg)

# 4. Enter a name for the iOS and then click Create.

# Create iApp

![Three dark grey 'X' shapes are evenly spaced in a horizontal row against a plain white background.](.sdaq-204-50m-00119-1000-10/71d84f85993237cecb202ab3a52a22d45d0586896cbfb0e3212ea8f3d8611d33.jpg)

Name:

Vibration

Select a template: Simpleio AI

Empty

Simpleio AI

REST server

REST client

DASK AI

DASK AO

![The image shows a rectangular button with rounded corners set against a white background. The button is a muted grey color and features a white checkmark icon on the left side, followed by the word 'Create' in white text. A thick red border surrounds the entire white area containing the button.](.sdaq-204-50m-00119-1000-10/5374f9a54276be44d8fff7ac599a64dfbc57e5f6d699f0ae190ab916de0ce2db.jpg)

# 5. A new iOS will be automatically loaded into the editor where it can be edited as necessary.

![count_3 = AI_Count(00)\ncount_4 = AI_count(00)\ntime_0 = AI_time(00, 2000)\ntime_1 = AI_time(01, 2000)\ntime_2 = AI_time(02, 2000)\nAHPer = (x * PS for x in (00(x-150))\nms = upstart(ip.max(up.array(D8)**3))\npowerVoltage = ms*15.3\nsimple1 could print('Throughput Product Line1 (K3): 'str(count_3))\nsimple2 could print('Throughput Product Line2 (K3): 'str(count_4))\nsimple3 could print('Run (ms): 'str(Time_0))\nsimple4 could print('File (ms): 'str(Time_1))\nsimple5 could print('Error (ms): 'str(Time_2))\nsimple6 could print('Power (ms): 'str(powerVoltage)))\nsimple7 could plot_graph(00), 'Throughput Product Line1', 'voltage')\nsimple8 could plot_graph(00), 'Throughput Product Line2', 'voltage')\nsimple9 could plot_graph(AHPer, 'APPower', 'voltage')\nsimple10 could plot_graph(00, 'Run', 'voltage')\nsimple11 could plot_graph(01, 'file', 'voltage')\ndata = ()\ndata( (DEX_1 ) = Time_0\ndata( (DEX_2 ) = Time_1\ndata( (DEX_3 ) = Time_2\ndata( (Count_Low ) = count_3\ndata( (Count_Right ) = count_4\ndata( (ADPowerVoltage) ) = powerVoltage\ndata( (APowerVoltage) ) = AHPer](.sdaq-204-50m-00119-1000-10/59473d7042b00cb7530efaa7628461d055802a56e562c8d637961fe47e6e0f59.jpg)

6. Click Save iApp when editing is completed.

![select Device ) Run Stop Console\nmain.py\ncount_3 = AI_Count(OM)\ncount_4 = AI_Count(OM)\ntime_0 = AI_Time(OM, 2000)\ntime_1 = AI_time(OM, 2000)\ntime_2 = AI_time(OM, 2000)\nACPer = ( * PS for x in OM(0:150))\nrun = np.spr(yn.mean(np.array(OM)**2)))\npowerVoltage = np*0.1)\nsimple1 could_print('Throughput Product time1 (953)'; *str((count_1)))\nsimple1 could_print('Throughput Product time1 (953)'; *str((count_2)))\nsimple1 could_print('run (m): 'str((time_0)))\nsimple1 could_print('idle (m): 'str((time_1)))\nsimple1 could_print('error (m): 'str((time_2)))\nsimple1 could_print('power run): *str((powerVoltage))\nsimple1 could_print.graph(OM), 'Throughput Product time1', 'voltage')\nsimple1 could_print.graph(OM), 'Throughput Product time1', 'voltage')\nsimple1 could_print.graph(ACPer, 'ACPer', 'Voltage')\nsimple1 could_print.graph(OM, 'Run', 'voltage')\nsimple1 could_print.graph(OM, 'tile', 'voltage')\ndata = ()\ndata( (OR_1) ) = Time_0\ndata( (OR_2) ) = Time_1\ndata( (OR_3) ) = Time_3\ndata( (Count_low) ) = count_3\ndata( (Count字号) ) = count_4\ndata( ACPer/voltage ) = powerVoltage\ndata( ACPer/Residual) = ACPer](.sdaq-204-50m-00119-1000-10/6b3beab234b637df8098555c5652ef80e72e0386f00ba27d3377ddaa884c1cf1.jpg)

# 3.2.2 iApp Deployment

Follow these steps to deploy an iApp.

1. Click Select Device on the menu bar.

![DAQ Pilot\nDevice Manager\nApp Creator\nACE Handbook\nOEE\nSelect Device\n1.08PC1001 (ADJNK,SDAG-216,Timer-Light)\nK7R5E1C1010 (ADJNK,SDAG-204,Motor)\nMX043NCA21 (ADJNK,SDAG-216,Power-Source)\ncount_3 = AI_Count(CK)\ncount_d = AI_Count(OM)\ntime_0 = AI_time(OK, 2000)\ntime_1 = AI_time(OK, 2000)\ntime_2 = AI_time(OK, 2000)\nACDVar = (e * p for i x in OMS(bit))\nreq = np.iqtr(np.mean(np.array(OK)**2))\npowerVoltage = req*3L...\nsimplel.comscale.print('Throughput Product Line1 (PK3): *str(count_3))\nsimplel.comscale.print('Throughput Product Line2 (PK3): *str(count_4))\nsimplel.comscale.print('new (ms): *str(time_0))\nsimplel.comscale.print('file (ms): *str(time_1))\nsimplel.comscale.print('true (ms): *str(time_2))\nsimplel.comscale.print('power res(v): *str(powerVoltage))\nsimplel.comscale.plot_graph(OK), 'Throughput Product Line1', 'Voltage')\nsimplel.comscale.plot_graph(OK), 'Throughput Product Line2', 'Voltage')\nsimplel.comscale.plot_graph(OK), 'ACDVar', 'Voltage'\nsimplel.comscale.plot_graph(OK, 'Bus', 'Voltage')\nsimplel.comscale.plot_graph(OK, 'Title', 'Voltage')\ndata ( 1)\ndata('IOE_v') = Time_0\ndata('IOE_v') = Time_1\ndata('IOE_v') = Time_2\ndata('count_low') = count_3\ndata('count_nlgm') = count_4\ndata('ACDVar,nlgm') = powerVoltage\ndata('ACDVar,nlgm') = ACDVar](.sdaq-204-50m-00119-1000-10/09433a836e67489138e680d4035b005137aacc3c98abb03718a35c3209744760.jpg)

# 2. Select the target device to be deployed.

![DAQ Pilot\nDevice Manager\nApp Creator\nACE Handbook\nOEE\nSelect Device Run Stop Console\n100PC3091 (DAQLIK.SDAQ-218, Tower-Light)\nK7R5EC100 (DAQLIK.SDAQ-204.Motor)\nM5DHCNCAV (DAQLIK.SDAQ-218, Power-Source)\ncount_3 = AI_count(OM)\ncount_d = AI_count(OM)\ntime_0 = AI_time(OM, 2000)\ntime_1 = AI_time(OM, 2000)\ntime_2 = AI_time(OM, 2000)\nACPw = (x * 21 for x in OM(0:30))\nms = np.sqrt(np.mss(np.array(OM))^{*})\npowerVoltage = ms^21.3\nsimple1A.comable_plot('Throughput Product Line1 (PCS): *str(count_3))\nsimple1A.comable_plot('Throughput Product Line2 (PCS): *str(count_4))\nsimple1A.comable_plotRun(m): *str(Time_8))\nsimple1A.comable_plot('Info(m): *str(Time_1))\nsimple1A.comable_plot('Error(m): *str(Time_2))\nsimple1A.comable_plotPower(m): *str(powerVoltage))\nsimple1A.comable_plot_graph(OM), 'Throughput Product Line', 'Voltage')\nsimple1A.comable_plot_graph(OM), 'Throughput Product Line', 'Voltage'\nsimple1A.comable_plot_graph(ACPw, 'ACPw', 'Voltage')\nsimple1A.comable_plot_graph(OM, 'ACPw', 'Voltage')\nsimple1A.comable_plot_graph(OM, 'ACPw', 'Voltage')\ndata = ()\ndata('OB_0') = time_0\ndata('OB_1') = time_1\ndata('OB_2') = time_2\ndata('count_lm') = count_3\ndata('count_rp#') = count_4\ndata('ACPw_Rp#') = converterage\ndata('ACPw_Rp#data') = ACPw\ntry](.sdaq-204-50m-00119-1000-10/69e37e5f16a888dda4c05ac34ffa03f201a8661265a01382595b1014fa9289d0.jpg)

# 3. Click Run and wait for the deployment to finish.

![Deploying iApp into device...\nOEE\n✓ iApp deployed](.sdaq-204-50m-00119-1000-10/ff1a42aa8e107a6649240a1c420296d39c8474956c0f2fee37365ef2cace1564.jpg)

# 4. Click Console on the menu bar.

![OEE\nL108PC1001(ADLINK.SDAQ-216.Tower-Light) Select Device ▼ Run □ Stop □ Console\nmain.py\n78 count_3 = AI_count(OH)\n79 count_4 = AI_Count(OH)\n80 Time_0 = AI_Time(OH, 2000)\n81 Time_1 = AI_Time(OH, 2000)\n82 Time_2 = AI_Time(OH, 2000)\n83 ACPer = (x * 25 for x in OH(0:150))\n84 rms = np.sqrt(np.mean(np.array(OH)**2))\n85 powerVoltage = rms*35.3\n86 simpleio.console.print('Throughput Product Line1 (PCS): *str(count_3))\n87 simpleio.console.print('Run (ms): *str(Time_0))\n88 simpleio.console.print('Idle (ms): *str(Time_1))\n89 simpleio.console.print('Error (ms): *str(Time_2))\n90 simpleio.console.print('power rms(V): *str(powerVoltage))\n91 simpleio.console.plot_graph(OH, 'Throughput Product Line1', 'Voltage')\n92 simpleio.console.plot_graph(OH, 'Throughput Product Line2', 'Voltage')\n93 simpleio.console.plot_graph(ACPer, 'ACPower', 'Voltage')\n94 simpleio.console.plot_graph(OH, 'Run', 'Voltage')\n95 simpleio.console.plot_graph(OH, 'Idle', 'Voltage')\n96 data = {}\n97 data('OEE_G') = Time_0\n98 data('OEE_V') = Time_1\n99 data('OEE_A') = Time_2\n100 data('Count_Low') = count_3\n101 data('Count_High') = count_4\n102 data('ACPower_Voltage') = powerVoltage\n103 data('ACPower_RawData') = ACPer\n104 tpi](.sdaq-204-50m-00119-1000-10/7f6cc07bec9d9e430dd9fc7ffe23ed7e6000adc93dee78f5e2d8dee3d5068f4c.jpg)

# 5. Console view shows that the iApp deployed to the remote device is running.

```txt
Console
L108PC1001(mcm204): Error (ms): 0.0
L108PC1001(mcm204): power rms(V): 227.17853736703296
L108PC1001(mcm204): requests data
L108PC1001(mcm204): Throughput Product Line1 (PCS): 0
L108PC1001(mcm204): Throughput Product Line2 (PCS): 0
L108PC1001(mcm204): Run (ms): 0.0
L108PC1001(mcm204): Idle (ms): 0.0
L108PC1001(mcm204): Error (ms): 0.0
L108PC1001(mcm204): power rms(V): 227.2169433184742
L108PC1001(mcm204): requests data
```

# 3.2.3 Device Management

Follow these steps to deploy an iApp to a single device.

1. Click Device Manager on the the left sidebar.

![DAQ Pilot\nDevice Manager\nApp Creator\nACE Handbook\nManage Devices\nRefresh devices\nDeploy by tags\nDevice ID 11\nIP/MAC Address\nTags\nCurrent iApps\nL108PC1001\n169.254.1.91\n02:42.47c3.971sd\nADLINK SDAQ-2TB Tower-Light\nOEE\nK785EC1010\n169.254.1.30\n02:42.7c5.6779\nADLINK SDAQ-2TB Motor\nVibration\nM5043NCA01\n169.254.1.506\n02:42.6h09-cc33\nADLINK SDAQ-2TB Power Source\nPower_Monitoring](.sdaq-204-50m-00119-1000-10/60e7669574e5523298f9a0c4021e70b64823d502e55d0bea8c4417a4b288ac8b.jpg)

2. For a targeted device, click Choose iApp.

![Current iApps\niApp Status ↑↓\nDeploy\nOEE\nrunning\nChoose iApp\nVibration\niApp name ↑↓\nOEE\nPower_Monitoring\nVibration](.sdaq-204-50m-00119-1000-10/49553b6ff8b69c18fa841d050fe44b65b653d7e6453cfb5d8658591ccb392454.jpg)

3. Select a target iApp to deploy to start deployment.

![Current iApps\niApp Status ↑↓\nDeploy\nOEE\nrunning\nChoose iApp\nVibration\niApp name ↑↓\nPower_Monitoring\nOEE\nPower_Monitoring\nVibration](.sdaq-204-50m-00119-1000-10/f6b763e62689006e57eeecc4411ca0569cf985f2e921508e3430157ed844e0a1.jpg)

4. The selected iApp is deployed to the target device.

# 3.2.4 Assign Tags to Devices

Tags can be assigned to devices for device naming or mass deployment. Follow these steps to assign a name to a device.

1. Click Device Manager on the left sidebar.

![DAQ.Pilot\nDevice Manager\nApp Creator\nACL Handbook\nManage Devices\nRefresh devices\nDeploy by tags\nDevice ID 11\nIP/MAC Address\nTags\nCurrent Apps\nL108PC1001\n169.254.1.91\n02.42.47c3.97c78\nADLINK\nSDAQ-218\nTower-Light\nDEE\nKT856C1010\n169.254.1.30\n02.42.7c7c8c879\nADLINK\nSDAQ-204\nMotor\nVibration\nM5043NCA01\n169.254.1.106\n02.42.4b9c9c133\nADLINK\nSDAQ-218\nPower Source\nPower_Monitoring](.sdaq-204-50m-00119-1000-10/528aa39d21054819c4b638bd6ec4b083d95b0004ebdc45c2eab1d720152acb2c.jpg)

2. To select a targeted device, click the dropdown menu under Tags.

![Manage Devices\nRefresh devices\nDeploy by tags\nDevice ID ↑↓\nIP/MAC Address\nTags\nCurrent iApps\niApp Status ↑↓\nDeploy\nL108PC1001\n169.254.1.91\n02.42.41c3.97cd\nADLRK SEAQ-218 Tower Light\nOKE\nrunning\nChese App\nK7836C1010\n169.254.1.30\n02.42.70c1.4779\nSelect Tags\nVibration\nrunning\nChese App\nM5043NCA01\n169.254.1.106\n02.42.e8e8b.0c33\nADLRK\nPower_Monitoring\nrunning\nChese App](.sdaq-204-50m-00119-1000-10/4ccaac7e912c2c4a7cb4d4035d3eef241aa52d12cd58205221838149423e9380.jpg)

![DAQ Pilot\nManage Devices\nRefresh Devices\nDisplay by steps\nDevice ID\nIP/MAC Address\nTags\nCurrent type\nIApp Status\nDisplay\n1.000PC7035\n168.254.130\n52.40.41.9.37E7.62\n168.254.130\n52.40.41.9.37E7.62\n168.254.130\n52.40.41.9.37E7.62\n168.254.130\n52.40.41.9.37E7.62\n168.264.130\n52.40.41.9.37E7.62\n168.264.130\n52.40.41.9.37E7.62\n168.264.130\n52.40.41.9.37E7.62\n168.264.130\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip\nLED Chip](.sdaq-204-50m-00119-1000-10/02c9e4e90b63024d9405d1684c842ce5311aa72995c0b03792e15a48ed2fff8d.jpg)

3. Select a tag to list the devices.

![DAQ Pilot\nManage Devices\nSoftware Manager\nDevice ID: 100\nRIMAC Address\nTags\nRIMAC Address\nCurrent Style\nApply Status\nDisplay\n1.000000000\n100 2543.91\n03.42.451.58756\nA100000000\n100 2543.91\n03.42.751.69778\nM0044NCA4X1\n100 2543.91\n03.42.451.58783\nRIMAC Address\nRIMAC Address\nRIMAC Address\nRIMAC Address\nRIMAC Address\nRIMAC Address\nRIMAC Address\nRIMAC Address\nRIMAC Address\nRIMAC Address\nRIMAC Address\nRIMAC Address\nRIMAC Address\nRIMAC Address\nRIMAC Address\nRIMAC Address\nRIMAC Address\nRIMAC Address\nRIMAC Address\nRIMAC Address\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC website\nRIMAC website\nRIMAC website\nRIMAC website\nRIMAC website\nRIMAC website\nRIMAC website\nRIMAC website\nRIMAC website\nRIMAC website\nRIMAC website\nRIMAC website\nRIMAC website\nRIMAC website\nRIMAC website\nRIMAC website\nRIMAC website\nRIMAC website\nRIMAC website\nRIMAC website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Website\nRIMAC Software](.sdaq-204-50m-00119-1000-10/b1bdef581c9cac34b21dbc3517932665bebfbe9a31222276fe36294361212417.jpg)

4. To create new tag, click +, and then save it.

![ADLINK Connection Explorer Version: 22.10.1110\nDAQ Pilot\nDevice Manager\niApp Creator\nACE Handbook\nManage Devices\nRefresh devices\nDevice ID ↑↓\nIP/MAC Address\nL108PC1001\n169.254.1.91\n02-42:a9:c3:97:cd\nK785EC1010\n169.254.1.30\n02-42:7c:fc:d7:79\nM9043NCA01\n169.254.1.106\n02-42:a9:d9:dc:33\nTags\nADLINK SDAQ-218 Tower-Light\nADLINK\nSDAQ-204\nNo results found](.sdaq-204-50m-00119-1000-10/64b7f1b90a98db6875827be155f3214ee21db9973388c161e109783c553b1b8b.jpg)

ADLINK Connection Explorer Version: 22.10.1110

![DAQ Pilot\nDevice Manager\niApp Creator\nACE Handbook\nManage Devices\nRefresh devices\nDevice ID ↑↓\nIP/MAC Address\nTags\nL108PC1001\n169.254.1.91\n02:42:4f:c3:97:cd\nADLINK SDAQ-218 Tower-Light\nK785EC1010\n169.254.1.30\n02:42:7c:fc:d7:79\nADLINK SDAQ-204\nM9043NCA01\n169.254.1.106\n02:42:a9:d9:dc:33\nPower-Light\nSDAQ-218\nPower-Source\n✓ SDAQ-204\nDeploy by tags](.sdaq-204-50m-00119-1000-10/7659a0f29d9d93094dbce20d5987980339e8e6212d5336209459952be25fcde1.jpg)

![Confirm\nSave tags?\n× No ✓ Yes](.sdaq-204-50m-00119-1000-10/9de7935a60792dd54d05a367da56aa6d9914c5ea36130966fe051d0316002241.jpg)

# 3.2.5 Deploy an iApp to Multiple Devices with Tags

Follow these steps to deploy an iapp to multiple devices with tags.

1. Click Device Manager on the left sidebar.

![DAQ Pilot\nDevice Manager\niApp Creator\nACE Handbook\nManage Devices\nRefresh devices\nTag\nDisplay by tags\nDevice ID ↑↓\nIP/MAC Address\nTags\nCurrent Apps\nL108PC1001\n169.254.1.93\n02:42:47:3.87c70\nADLINK  SDAQ-218  Tower-Light\nOEE\nKT856C1010\n169.254.1.30\n02:42:7c7c7c779\nADLINK  SDAQ-204  Motor\nVibration\nM9043NCA01\n169.254.1.06\n02:42:ab:89bc:33\nADLINK  SDAQ-218  Power Static\nPower_Monitoring](.sdaq-204-50m-00119-1000-10/0b948345dcf12e800881fde8f7531c2254b397848a099b803834821d7c2c193e.jpg)

2. Click Deploy by tags.

![DAQ Pilot\nDevice Manager\ni-App Creator\nACE Handbook\nManage Devices\nRefresh devices\nDisplay by tags\nDevice ID: T1\nIP/MAC Address\nTags\nCurrent iApps\nL10MPC1001\n168.254.1.91\n02-42-49:63:87/ind\nADLINK SDAQ-278 Tower-Light\nOEE\nK785EC1010\n168.254.1.30\n02-42-70:07:79\nADLINK SDAQ-204 Motor\nVibration\nM9043NCA01\n168.254.1.06\n02-42-ad:09:0c:33\nADLINK SDAQ-278 Power-Source\nPower_Monitoring](.sdaq-204-50m-00119-1000-10/3c137207d934a041fbf653f94916cca2acb40e2c3cb685f3c0dad19e28fea9f6.jpg)

Select a tag and a target iApp to deploy and click Deploy. The target iApp will be deployed to the target device.

![Tags\nADLINK\nADLINK\nSDAQ-216\nTower-Light\nSDAQ-204\nmotor](.sdaq-204-50m-00119-1000-10/cd6d877f839e07bf918df9254d76826d044e0a3816335e4555bcd46b386080fc.jpg)

![Tags\nADLINK SDAQ-216 Tower-Light\nDeploy by tags\nTags\nADLINK\niApp\nPower_Monitoring\nOEE\nPower_Monitoring\nVibration](.sdaq-204-50m-00119-1000-10/105986ee55845dc3a527ab8d1ab8968919b753c0124293df4acbb7fbc39a85c5.jpg)

This page intentionally left blank.

# 4 Web Console

This chapter describes how to use the built-in web console to configure the SDAQ-204 and view captured data.

# 4.1 Web Console Login

After the SDAQ-204 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

1. Get the IP address from DAQPilot ACE (available for download on the SDAQ-204 product web page: https://www.adlinktech.com/Products/Data\_Acquisition/SmartDAQ/SDAQ-204)

![The image features a small, blurry, red icon on a white background, resembling a stylized chain link or infinity symbol (often used as a 'share' icon). There is no text in the image.](.sdaq-204-50m-00119-1000-10/0d3db2470df8690938260425ff126ef6dd7e8d8b1f412b1c9ece243f017b7546.jpg)

ADLINK Connection Explorer Version: 22.10.1110

![The image displays a logo set against a white background. It features two interlocking, stylized geometric shapes. On the left is a grey shape resembling the letter 'C,' and on the right is a red shape resembling the letter 'D.' The shapes are angled and appear to weave together. There is no text visible in the image.](.sdaq-204-50m-00119-1000-10/0e6d7cd4e9712beb95b3616b6bbf20f42c4607b8f1633bc5a76f2554e5010a27.jpg)

DAQ Pilot ACE

![The image displays a simple icon consisting of four horizontal gray bars stacked vertically. The bars are of equal width and thickness, with rounded ends, and are centered on a white background. This design is commonly used as a 'hamburger' menu icon in user interfaces.](.sdaq-204-50m-00119-1000-10/2ba6d099098bbe37167572380a2c6bba0c64d6db6a7d25632e7c6dbdfbb61745.jpg)

![Device Manager\niApp Creator\nACE Handbook\nManage Devices\nRefresh devices\nDevice ID ↑↓\nIP/MAC Address\nK785EC1010\n169.2541.30\n02:42:9e:84:be:5c](.sdaq-204-50m-00119-1000-10/2208c6abd20b8685f09a0e9db95bada80ebf8ad35f7ba535289142918520fd12.jpg)

Figure 4-1: Get IP Address from DAQPilot ACE

2. In your web browser's address bar, enter the IP address from above (e.g., http://169.254.1.30).

# Option 2: Hostname

Connect the SDAQ-204 to a network component (switch/router) with DNS functionality, then enter the SDAQ-204's hostname in the address bar of the host PC's web browser, prefaced by http:// (e.g., http://mcm204-j801ns1001). A unique default hostname is generated for each SDAQ-204 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 4-2).

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.](.sdaq-204-50m-00119-1000-10/53b188ce815ecb2dc4918d9b1138b283577675e76b518c26b9e95bd9ecc7568a.jpg)

Figure 4-2: Web Console Login Page

After logging into the web console, DAQPilot Setting must be disabled immediately before continuing (see Figure 4-3).

![System Information\nSystem Manager\nSystem Settings\nNetwork Settings\nAccount Management\nChange Password\nData Keep\nData Keep: ○ Enable ● Disable\n('Enable' to store history data in DISK and RAM, 'Disable' to only store it in RAM.)\nAPPLY\nDAQPilot Setting\nDAQPilot Setting: ○ Enable ● Disable\nRESTART\nAPPLY](.sdaq-204-50m-00119-1000-10/2219c91535c08f4e3e2165b6f5e2c18dc3722a5949082da55fee2be41b7c4d1f.jpg)

Figure 4-3: Disabling DAQPilot Setting

# 4.2 Web Console Menu

The web console menu bar includes the following items.

▶ System Information
▶ Device Setting
▶ Data Capture
▶ Peripheral
▶ Data History
▶ Data Condition
▶ Mission Management
▶ Change Password
▶ Account Management
▶ System Setting
▶ TCP Socket

![ADLINK\nLOGOUT\nMenu\nSystem Information\nDevice Setting\nData Capture\nPeripheral\nData History\nData Condition\nMission Management\nChange Password\nAccount Management\nSystem Setting\nTCP Socket\nDevice: MCM-204 Account administrator Role admin Restful API Doc.\nWelcome\nDevice Name : MCM-204\nHostname : MCM204\nIP Address : 192.168.100.5\nMAC Address : 00:30:64:32:5d.5e\nTime : 2019-10-24 17:04:53(Asia/Taipei)\nTurn On : Oct 24 09:32:37\nSerial Number : J7F0EC1003\nCopyright © 2019 ADLINK Technology Inc. All Rights Reserved.](.sdaq-204-50m-00119-1000-10/aef5023273c0267c9368022d79bb4a16383c7fcd1c385ad135d627292d1ad920.jpg)

Figure 4-4: 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 graphic logo on a white background. The shape resembles a stylized capital letter 'A' or a right-angled triangle with the hypotenuse on the left. The top portion is a solid red triangle pointing upwards. Below this, the lower section is composed of three horizontal red bars stacked vertically, separated by thin white horizontal gaps. The left edge of the entire shape forms a continuous straight diagonal line, while the right edge appears to be a straight vertical line.](.sdaq-204-50m-00119-1000-10/eee90c2e2c1c7920c8600978b700f4e42846e36da4c1859bc4d9b57d99af0b05.jpg)

# ADLINK

![≡\nDevice: MCM-204 Account: administrator Role: admin](.sdaq-204-50m-00119-1000-10/c9d55f30de9756e1ab5b7e1aa3e6f940b9d40749bfeebbb2ae0997059a8e5212.jpg)

Welcome

Figure 4-5: Menu Icon

# 4.2.1 System Information

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

![System Information\nDevice Setting\nData Capture\nPeripheral\nData History\nData Condition\nMission Management\nChange Password\nAccount Management\nSystem Setting\nTCP Socket\nSystem Information\nSoftware Version\nFirmware Version : 19.10.1023\nDevice Information\nModel : MCM-204\nHostname : MCM204\nSerial Number : J7F0EC1003\nTime : 2019-10-24 17:09:11(Asia/Taipei)\nTurn On : Oct 24 09:32:37\nChannel Status\nChannel Status : DO : ready AI : ready DI : ready\nREFRESH\nNetwork Status\nIP Address : 192.168.100.5\nMAC Address : 00:30:64:32:5d:5e\nSubnet Mask : 24\nGateway : 192.168.100.1\nType : static\nDNS : 8.8.8.8,](.sdaq-204-50m-00119-1000-10/d9c74bb7e061f741acfba801329a062eb439e11a20103fbb78ff06dfae79846b.jpg)

Figure 4-6: System Information

# 4.2.2 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\nDIO0:High DIO1:High DIO2:High DIO3:High Temperature Sensor:N/A\nREFRESH\nDigital I/O Setting\nEnable DIO0 Digital Type\nInput\nEnable DIO1 Digital Type\nInput\nEnable DIO2 Digital Type\nInput\nEnable DIO3 Digital Type\nInput\nAPPLY\nNo I/O is selected.](.sdaq-204-50m-00119-1000-10/c2eaccf3cddd7adf597fea3707078f6d6d46fa0a3da2e273e61b3efa01ad900d.jpg)

Figure 4-7: Peripheral Devices

# 4.2.3 Data History

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

![Device: MCM-204 Account: administrator Role: admin\nRestful API Doc\nHistory Data\nClear\nCLEAN ALL DATA\n*It will clean all history data.\nSearch Filter :\nAll User All Time\nUser: From:\nYear Month Day Hour Min Sec\n2019 9 28 17 11 48\nTo:\nYear Month Day Hour Min Sec\n2019 10 24 17 11 48\n*Press '*' and '*' keys on the keyboard to modify value.\nChannel Filter\nAll\nSEARCH](.sdaq-204-50m-00119-1000-10/0a6250fb2a96dd0ddd0b721a625eae9839bd957f5df15db78d5af4e2c8dab2e7.jpg)

Figure 4-8: Data History

# 4.2.4 Mission Management

A mission is a setting of I/O parameters with an intended output method. The SDAQ-204 will execute the same settings even after a reboot, so if Repeat Times is set to 0 (endless data capture), the SDAQ-204 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

Delete Mission

Click the DELETE button to stop current mission.

Channel Status : DO:ready AI:ready DI:ready

DELETE

REFRESH

Figure 4-9: Mission Management

# 4.2.5 Change Password

This page is used to change the password of each SDAQ-204, 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 SDAQ-204 is identical.

![Device: MCM-204 Account: administrator Role: admin\nChange Password\nStep 1:Enter original password first.\nOriginal Password\nCHECK](.sdaq-204-50m-00119-1000-10/2aaabf1e2b9f59e408a686e83827a7abf7856a329a23ab2a8c79e2595723c8b0.jpg)

Figure 4-10: Change Password

# 4.2.6 Account Management

This page manages user accounts and access privileges.

Account Management

Create New Account

Username

Password

Password Confirm

Permission

Guest

![The image displays a dark, blurry, inverted triangle pointing downwards, centered against a white background. There is no text present.](.sdaq-204-50m-00119-1000-10/29f9f3d65aa85a6828cd9a7e28cf4f35c39efb38cfb4928d32f21abd7a039c3d.jpg)

\* The password must be at least 8 characters and at least one uppercase characters, at least one lowercase characters and at least one number.

CREATE

Account List

<table><tr><td>No.</td><td>Username</td><td>Permission</td><td>Action</td></tr><tr><td>1</td><td>administrator</td><td>admin</td><td></td></tr></table>

Figure 4-11: Account Management

# 4.2.7 System 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 35 for details.

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

![System Information\nDevice Setting\nData Capture\nPeripheral\nData History\nData Condition\nMission Management\nChange Password\nAccount Management\nSystem Setting\nTCP Socket\nSystem Setting\nNetwork Setting\nHostname\nMCM204\nEthernet\nType\nStatic\nAddress\n192.168.100.5\nGateway\n192.168.100.1\nMask\n24 - 255.255.255.0\nDNS 1\n8.8.8.8        DNS 2\n    APPLY\nKeep Network Setting : ○ Enable ● Disable\n('Enable' to keep the network setting after restore factory setting and 'Disable' will restore the all setting.)\n    APPLY](.sdaq-204-50m-00119-1000-10/c418d3f0818ef49ce1c48b0563002c35a2564816c418c4e1ec75c62f54fa453d.jpg)

Figure 4-12: Network Settings

Data Keep: By default, the SDAQ-204 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 SDAQ-204 can be recalibrated if necessary. Though the SDAQ-204 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.

![Time Setting\nYear Month Day Hour Min Sec\nTime: 2019 10 24 17 48 55\n* Press '+' and '-' keys on the keyboard to modify value.\nTime Zone NTP Server\nAsia/Taipei 0.us.pool.ntp.org\nAPPLY\nSystem Restart\nPress 'RESTART' to reboot: the device.\nRESTART\nData Keep\nData Keep: ○ Enable ● Disable\n('Enable' to keep history data in DISK and RAM and 'Disable' only keep it in RAM.)\nAPPLY\nDevice Calibration\nPress 'Apply' to calibrate the device.\nAPPLY](.sdaq-204-50m-00119-1000-10/5fae76852865a7c430cb46792737285cfd8c5e967894ac79dd65f0d68aff9bb8.jpg)

Figure 4-13: System Settings

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

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

https://www.adlinktech.com/Products/Data\_Acquisition/SmartDAQ/SDAQ-204

![Customization library Upload\nLibrary Upload: Choose File No file chosen\n(Please Select a .so file.)\nUPLOAD\nFirmware Upgrade\nFirmware Upgrade: Choose File No file chosen\n(Please Select a .bin file with correct content.)\nUPLOAD](.sdaq-204-50m-00119-1000-10/69a7222f8723a62d9329626cac00a5fcdaf58bb2ef154021fa70be6896effc27.jpg)

Figure 4-14: Upload Customization/Firmware Files

# 4.2.8 TCP Socket

The SDAQ-204 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

Add Socket Connection

<table><tr><td>Address</td><td>Port</td><td>Channel</td></tr><tr><td>192.168.100.2</td><td>6666</td><td>ALL</td></tr></table>

ADD RULE

Socket Connection List

RE-CONNECT ALL

<table><tr><td>Socket No.</td><td>Status</td><td>Address</td><td>Port</td><td>Channel</td><td>Action</td></tr><tr><td>1</td><td></td><td>192.168.100.2</td><td>6666</td><td>ALL</td><td>Delete</td></tr></table>

Figure 4-15: TCP Socket

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

# 4.3 DAQ Mission

The SDAQ-204 performs excellent vibration detection with an analog IEPE accelerator connected. Related parameters can be set via the Device Setting page.

Device Config

<table><tr><td>Input Type</td><td colspan="2">Trigger Source</td><td colspan="2">Trigger Direction</td><td>Trigger Value</td></tr><tr><td>PseudoDifferential</td><td colspan="2">NoWait</td><td>Rising</td><td>1</td><td></td></tr><tr><td>Repeat Interval</td><td>Repeat Times</td><td>Sample Rate</td><td>Data Count</td><td>Tachometer</td><td></td></tr><tr><td>3000</td><td>1</td><td>128000</td><td>10240</td><td>Disable</td><td></td></tr><tr><td></td><td></td><td>Click the icon to adjust it.</td><td>Click the icon to adjust it.</td><td></td><td></td></tr></table>

Channel Config
![AI0 Config\nEnable the Channel\nCoupling Input Range\nAC ±10\nData Type\nVoltage\nADD CONDITION\nADD DATATYPE\nSensor Type Sensor Sensitivity (mV/g) IEPE\nAccelerometer 1000 Disable](.sdaq-204-50m-00119-1000-10/cd80b732461c339772f55e47b0f253cc11e85b31c5c75395782c1607d66f64d1.jpg)

Figure 4-16: Device Configuration

Trigger Source allows the data capture function to be triggered from a particular source via analog and digital triggers.

Repeat Interval is the interval between data captures, 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.

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

![The image displays a vertical graphic consisting of a red triangle with rounded corners containing a white exclamation point in the center. Directly below the triangle is the text 'WARNING!' printed in black, capital letters.](.sdaq-204-50m-00119-1000-10/3a84adee5c424e608bed3cafcc02cc0ce5cc7dc21a8feb8b130005224dd98b20.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.

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

Channel Config

![AI0 Config\nRawData\nVoltage\nInput Range\n±10\nFFT_PowerSpec\nOA_g(RMS)\nOA_g(Peak)\nOA_mm/s(RMS)\nOA_mm/s(Peak)\nOA_um(P-P)\nSensor Sensitivity (mV/g)	IEPE\nG	Disable\nCustomization](.sdaq-204-50m-00119-1000-10/2a83051d7a1119f0ee851988da34331fd626f5a5139c699027d0abe0cc37ae52.jpg)

Figure 4-17: DataType

The SDAQ-204 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 (24 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>OA_g(RMS)</td><td>Overall value in the format of g(RMS)</td></tr><tr><td>OA_g(Peak)</td><td>Overall value in the format of g(Peak)</td></tr><tr><td>OA_mm/s(RMS)</td><td>Overall value in the format of mm/s(RMS)</td></tr><tr><td>OA_mm/s(Peak)</td><td>Overall value in the format of mm/s(Peak)</td></tr><tr><td>OA_um(P-P)</td><td>Overall value in the format of um(P-P)</td></tr><tr><td>G</td><td>Acceleration transferred from sensor sensitivity</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

![AI0 Config\nEnable the Channel\nCoupling Range\nAC ±10\nDataType\nVoltage\nADD CONDITION\nName Severity Direction Value\nRule Warning Above 1\nADD DATATYPE\nSensor Type Sensor Sensitivity (mV/g) IEPE\nAccelerometer 1000 Disable](.sdaq-204-50m-00119-1000-10/cf327605f8c3da364e23b3f2db9b42097d8765ee67b655f0690641b5fcf1e940.jpg)

Figure 4-18: Add Condition

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

The 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

Data In JSON

![A blurry, dark grey icon of a cloud with a downward-pointing arrow in the center.](.sdaq-204-50m-00119-1000-10/08e7551197f2c5ccd7e6c669bc25a4308a31a705b37cc7edf3eefd485e35878b.jpg)

![{'Data': ( 2 items\n    0 : { 1 item\n        {'AI0': { 1 item\n            {'OA_g(RMS)':(...) 1 item\n        }\n    }\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}](.sdaq-204-50m-00119-1000-10/3665cc536776f2aa0eb5d857cc172d2b5dce686a8b277b51125f366acf477911.jpg)

Figure 4-19: Data Capture

Device Settings

![Mission Profile Management\nSave Profile	Load Default	Select Mission Profile\nSAVE PROFILE	LOAD DEFAULT	Choose File	No file chosen\nDevice Config\nInput Type	Trigger Source	Trigger Direction	Trigger Value\nPseudoDifferential	NoWait	Rising	1\nRepeat Interval	Repeat Times	Sample Rate	Data Count	Tachometer\n3000	1	128000	10240Disable](.sdaq-204-50m-00119-1000-10/43cb886003130177349632c930f83d51347982793a7f6c73bec28eb5777fc64e.jpg)

Figure 4-20: Device Settings

Settings may be saved as a Mission Profile (JSON file) for backup or for convenient duplication on other SDAQ-204 devices. Click SAVE PROFILE to download the file to your PC. To import a Mission Profile to an SDAQ-204 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 SDAQ-204 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\nPseudoDifferential	NoWait	Rising	1](.sdaq-204-50m-00119-1000-10/d4d32b6c53db4f98c4d8550a825effd7df753c23ace412778dffddc28a33e089.jpg)

Figure 4-21: Apply a New Mission

# 5 DAQ Missions

The SDAQ-204 supports various modes of operation that users can choose from to quickly integrate into their systems.

# 5.1 Usage Behaviors

IEPE sensors transmit raw data to the SDAQ-204 which can then be filtered to other kinds of data types that are more application appropriate, such as overall vibration values (ISO 10816) for mechanical vibration data. The overall vibration value data size is greatly reduced in comparison to raw data, so the backend server receives much less data for analysis. Data filtering is best suited to applications requiring continual information updates at a given time interval, such as every minute, which the user can then review periodically.

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 5-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, SDAQ-204 provides a REST API and sample code in C#, Python, and JavaScript. Alternatively, for continuous data mode, SDAQ-204 provides a DAQPilot SDK and associated C/C++ sample code.

# 5.1.1 Web Console

The SDAQ-204 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 35.

![Based on the provided image, here is the description of the flowchart blocks and their connections:\n\n**Labeled Blocks:**\n*   **Top Row (Red):** 'Configuration / See data in web', 'Periodically Polling Data', 'Passively get data', 'Continuous Data'\n*   **Second Row (Yellow):** 'Web browser', 'REST API', 'TCP socket- server mode', 'Streaming SDK'\n*   **Middle Row (Grey/Blue):** 'Web Console', 'REST Server', 'TCP Socket- client mode'\n*   **Bottom Stack (Grey):** 'Data in JSON format', 'Filtered Data', 'Raw Data'\n\n**Connections and Flow:**\n*   **Configuration Path:** 'Configuration / See data in web' leads to 'Web browser', which points down to 'Web Console'. 'Web Console' then points right to 'REST Server'.\n*   **Polling Path:** 'Periodically Polling Data' leads to 'REST API', which points down to 'REST Server'.\n*   **Passive Data Path:** An arrow points up from 'TCP Socket- client mode' to 'TCP socket- server mode'.\n*   **Continuous Data Path:** 'Continuous Data' leads to 'Streaming SDK', which has a long arrow pointing down into 'Data in JSON format'.\n*   **Data Processing Stack:**\n    *   'Raw Data' points up to 'Filtered Data'.\n    *   'Filtered Data' points up to 'Data in JSON format'.\n    *   'Raw Data' also points directly up to 'Data in JSON format' (bypassing the filtered step).\n*   **Data Distribution:** From 'Data in JSON format', arrows point up to both 'REST Server' and 'TCP Socket- client mode'.](.sdaq-204-50m-00119-1000-10/72b5cf822b34840ff529221662721601e9005ff866dea785db273a859af49a41.jpg)

Figure 5-1: Operational Modes

# 5.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](.sdaq-204-50m-00119-1000-10/296c7cb9f70bb9da1b65dade96b029eafabf8560d6ac5f13145a4c52d95201ed.jpg)

Figure 5-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 SDAQ-204 product web page:

https://www.adlinktech.com/Products/Data\_Acquisition/SmartDAQ/SDAQ-204

# 5.1.3 Continuous Data

To use continuous data mode, first install the DAQPilot SDK, available for download on the SDAQ-204 product web page:

https://www.adlinktech.com/Products/Data\_Acquisition/SmartDAQ/SDAQ-204

After installation, sample code and function references can be found in the C:\Program Files\ADLINK\DAQPilot folder.

Before using the DAQPilot SDK, DAQPilot Setting must be enabled via the SDAQ-204 web console.

![System 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\nDAQPilot Setting\nDAQPilot Setting ● Enable ○ Disable\nAPPLY](.sdaq-204-50m-00119-1000-10/26b1acc08470c476b1e5a869a560c920fa23e07f2f0294882f2ee08cebed8b92.jpg)

Figure 5-3: DAQPilot Setting

![The image displays a standard hazard warning sign. It features a red triangle containing a black exclamation point in the center. Directly below the triangle is the text 'WARNING:' printed in black capital letters.](.sdaq-204-50m-00119-1000-10/1183f2eb670d40da3d8062359edbf2e27069e1bb1d554c889a61cdd31f7e0939.jpg)

- When using DAQPilot, the host server and SDAQ-204 must be deployed to the same network segment.
It is strongly recommended not to use the REST API for querying continuous data.

# 5.1.4 Passive Data

The conventional message exchange pattern of the SDAQ-204 for Periodic Polling and Continuous Data modes is request-response, with the SDAQ-204 serving as responder. After receiving a query from the host, the SDAQ-204 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 SDAQ-204 to automatically send data to the host server whenever data is generated. See “TCP Socket” on page 46.

# 5.2 Custom Filtering Algorithms

The SDAQ-204 offers flexible support options for custom filtering algorithms. Users can easily import their own domain-knowledge algorithms to the SDAQ-204. 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 SDAQ-204 web page and extract the CalStatistic (C++) and CalRMS (C) sample program folders.

https://www.adlinktech.com/Products/Data\_Acquisition/SmartDAQ/SDAQ-204

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](.sdaq-204-50m-00119-1000-10/d1b9197a8b735aebec611b6ccceeb4aa74f67a9bd384d52f45a275ed7834abdd.jpg)

![The image features a digital icon of an orange folder with a tab on the upper left side, set against a white background. Below the folder icon is the text 'CalRMS' in a sans-serif font. The 'C' is capitalized and appears slightly larger than the lowercase 'a' and 'l'. The 'RMS' consists of uppercase letters. The text 'Cal' is colored in a light grey, while 'RMS' is in a dark grey or black.](.sdaq-204-50m-00119-1000-10/85166981c7db1e1a83e68878b3303732dadcb69aa21a05f3df8c8aeac4b43b3d.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 gray lines representing text, positioned above the black text 'customAlgo.so'.](.sdaq-204-50m-00119-1000-10/792b611abd1d30f77b6dc8ab58ba608642bc2efaca7a5f7461de3292174c693f.jpg)

5. Upload customAlgo.so to the SDAQ-204 from the web console System Setting page.

![Customization library Upload\nLibrary Upload: Choose File No file chosen\n(Please Select a. so file.)\nUPLOAD](.sdaq-204-50m-00119-1000-10/e3b99a0bf13a5f1a82e97f630e65ca18b490c94170f7b71ca6d94a374fc17d96.jpg)

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

![You have to re-login .\nRe-login](.sdaq-204-50m-00119-1000-10/a48938b840f3252382f0a9ab95ef174f9c814ae42898b2123f1906c8d39e81eb.jpg)

7. After logging in, choose Customization as the data type, set parameters as needed, then click APPLY to apply the task to the SDAQ-204.

![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](.sdaq-204-50m-00119-1000-10/352ebe5467dd77ffa474ad6fb9ff0237409db90ffe2410e80471237aaf9dadd4.jpg)

<table><tr><td>AI1 Config</td><td>✓</td></tr><tr><td>AI2 Config</td><td>✓</td></tr><tr><td>AI3 Config</td><td>✓</td></tr></table>

APPLY

8. Check the results on the data capture page.
```json
{ 1 item
    "Data": [ 2 items
    0 : { 1 item
    "AI0": { 1 item
    "Customization": [ 1 item
    0 : 1.0328374
    ]
    }
    }
    1 : { 1 item
    "Date": "2019-10-23 16:47:21.967"
    }
}
```

# 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.

▶ Read these safety instructions carefully.
- Keep the User’s Manual for future reference.
▶ Read the Specifications section of this manual for detailed information on the recommended operating environment.
▶ The device can be operated at an ambient temperature of $50^{\circ}$ C.

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

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

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

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

▶ 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

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

![The image displays a safety sign featuring a yellow triangle with a black border and a black exclamation point in the center. Below the triangle, the text 'CAUTION:' is printed in black capital letters.](.sdaq-204-50m-00119-1000-10/5fa456f6ca533994b97fb7f272f836c7ec096a604024863c08d6cd9766c9a655.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.

The device must be serviced by authorized technicians when:

The power cord or plug is damaged.
▷ Liquid has entered the device interior.
The device has been exposed to high humidity and/or moisture.
The device is not functioning or does not function according to the User's Manual.
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.

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

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

▶ 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.

No. 66, Huaya 1st Road, Guishan District

Taoyuan City 333, Taiwan

Tel: +886-3-216-5088

Fax: +886-3-328-5723

Email: service@adlinktech.com

# Ampro ADLINK Technology, Inc.

6450 Via Del Oro, San Jose,

CA 95119-1208, USA

Tel: +1-408-360-0200

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

Fax: +1-408-600-1189

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: