# EMU-210 # IoT Gateway # User’s Manual ![AT&T-MSK\n9\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n0\n1\nS423.1\nS423.1\nS423.1\nS423.1\nS423.1\nS423.1\nS423.1\nS423.1\nS423.1\nS423.1\nS423.1\nS423.1\nS423.1\nS423.1\nS423.1](.emu-210-50m-19701-1000-10/379d8dbbc0334bfe6795a35f6802a4f19561a52a90880fe76a7b24f4fdbe2ec3.jpg) Manual Rev.: 1.0 Revision Date: June 20, 2024 Part No: 50M-19701-1000 Revision History
RevisionRelease DateDescription of Change(s)
1.02024-06-20Initial release
# Preface # Copyright © 2024 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 and a horizontal bar below (no text or labels)](.emu-210-50m-19701-1000-10/2d3bcbfcd837db04e4afacd06e3b7651751c5d84ad42faf16665c33adb6e30d3.jpg) Battery Labels (for products with battery) ![Symbol of a trash bin crossed out by two diagonal lines (no text or numbers present)](.emu-210-50m-19701-1000-10/e01a1110613dbb2148128d7071265029f488ab948e8c0cd89f1a933c80d98973.jpg) ![Recycling symbol icon with three chasing arrows inside a square frame (no text or labels)](.emu-210-50m-19701-1000-10/c85c802c2927583498bf28b7684d4747bf206c9382d56e151f9b2054a8ae3fcd.jpg) Li-ion ![RECYCLE\nRBRC\nLi-ion\n7.800.822.8837](.emu-210-50m-19701-1000-10/a1b95a379de902e6e05ab04ee00c5e5146eb880c6bfb3354bc40c9d230c9a42e.jpg) ![Abstract geometric pattern with interlocking black and white shapes (no text or symbols)](.emu-210-50m-19701-1000-10/b4086dadfb0313467225eec276092a3bd8ec9ad42628372bb8a1519df5293325.jpg) ᘄ㟁ụㄳᅇᨲ # California Proposition 65 Warning ![A yellow triangular warning sign with a thick black border and a black exclamation point in the center.](.emu-210-50m-19701-1000-10/179c8e9947a91fa217dba877cc7206de93874d307781116b181fe1bd7276387c.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 features a white icon resembling a sheet of paper with faint horizontal lines and a folded top-left corner. A large, red checkmark is superimposed over the center of the document.](.emu-210-50m-19701-1000-10/fecd813c1fcb30a7907ac23c4f005dcd0743a3dbfdff8f89d0ef0b396fcd153e.jpg) NOTE: Additional information, aids, and tips that help users perform tasks. ![The image displays a triangular warning sign with a yellow background and a black outline. Inside the triangle, there is a large black exclamation point centered. The sign is set against a white background.](.emu-210-50m-19701-1000-10/871f0785a1543e927214a505f749b0933fd308e2a60daaad4be9e9d84b9d7547.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 standard warning symbol consisting of a red triangle with a white border. Inside the triangle is a large white exclamation point centered vertically and horizontally. The symbol is set against a white background, with a thin black horizontal line visible at the very top edge of the frame.](.emu-210-50m-19701-1000-10/c204af836454a18f3814e84d65f2ad07bd051ac114614e56a443ff247374604f.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..... 1 1.2 Packing List ... 2 1.3 Optional Accessories .... 2 1.4 Specifications..... 3 1.5 Functional Block Diagram... 5 1.6 Mechanical Drawings... 6 1.7 I/O Connectors..... 11 # 2 Getting Started ..... . 17 2.1 Unpacking the EMU-210.... 17 2.2 Connecting DC Power ..... . 18 2.3 Connecting to the EMU-210 .. 2 0 # 3 EGiFlow ......... 21 3.1 EGiFlow Login ..... . 21 3.2 EGiFlow Menu .... . 23 # A Appendix: Debian Linux OS ..... . 59 A.1 Hardware Setup...... 5 9 A.2 Connecting and Logging in via SSH .. 6 0 A.3 LED Function ..... 6 1 A.4 Serial Port Configuration.. 61 A.5 Network Settings.. 6 2 A.6 5G/4G/LTE Module Configuration 6 3 A.7 Wi-Fi Configuration and Connection.. 65 # B Appendix: Accessory Installation ....... .....67 B.1 Wi-Fi Module... 67 B.2 4G Module .... 73 B.3 5G Module .... 78 # Important Safety Instructions....... . 83 # Consignes de Sécurité Importantes ......... .. 85 # Getting Service ....... ..... 89 # List of Figures Figure 1-1: Functional Block Diagram.. 5 Figure 1-2: EMU-210 Dimensions... 6 Figure 1-3: DIN Rail Mount 1 . 7 Figure 1-4: DIN Rail Mount 2 .. .. 8 Figure 1-5: Wall Mount 1.. . 9 Figure 1-6: Wall Mount 2.. . 9 Figure 1-7: Wall Mount 3.. .. 10 Figure 1-8: Front View . .. 11 Figure 1-9: Side View.... .. 11 Figure 1-10: DC Power Input .. .. 13 Figure 1-11: COM Port Pin Definition . . 15 Figure 3-1: EGiFlow Login Page.. .. 22 Figure 3-2: EGiFlow Main Page... . 22 Figure 3-3: Create EGiFlow iApp .. . 24 Figure 3-4: Modbus TCP/RTU to Cloud. . 25 Figure 3-5: Create Modbus TCP. .. 26 Figure 3-6: Configure Modbus TCP. .. 26 Figure 3-7: Create Modbus RTU.. .. 27 Figure 3-8: Configure Modbus RTU.. . 27 Figure 3-9: Create Compute .. .. 28 Figure 3-10: Develop Customized Data Conversion.. . 28 Figure 3-11: Create Azure .. .. 29 Figure 3-12: Configure Azure.. .. 29 Figure 3-13: Create AWS... .. 30 Figure 3-14: Configure AWS.. .. 30 Figure 3-15: Run and Deploy.. .. 31 Figure 3-16: Modbus TCP/RTU to MQTT . . 31 Figure 3-17: Create MQTT Publish.. .. 33 Figure 3-18: Configure MQTT Publish . . 33 Figure 3-19: Modbus TCP/RTU to RESTful.. .. 34 Figure 3-20: Create RESTful . .. 35 Figure 3-21: Configure RESTful... .. 35 Figure 3-22: Modbus RTU to Modbus TCP . .. 36 Figure 3-23: Create Modbus TCP Write . . 37 Figure 3-24: Configure Modbus TCP Write... .. 37 Figure 3-25: OPC UA to AWS... .. 38 Figure 3-26: Create OPC UA .. . 39 Figure 3-27: Configure OPC UA .. .. 39 Figure 3-28: Create Compute .. ... 40 Figure 3-29: Develop Customized Data Conversion.... .. 40 Figure 3-30: Create AWS.. . 41 Figure 3-31: Configure AWS.. ... 41 Figure 3-32: Create Python iApp..... .. 42 Figure 3-33: Select a template and enter a name... .. 42 Figure 3-34: The new iApp can be edited . .. 43 Figure 3-35: Run a new iApp .. ... 43 Figure 3-36: Network Settings... . 44 Figure 3-37: Select LAN Port .. ... 44 Figure 3-38: Configure LAN Port... ... 45 Figure 3-39: Select DHCP or Static .. .. 45 Figure 3-40: Configure Static IP (IPv4) . .. 46 Figure 3-41: Configure Static IP (IPv6) ..... .. 46 Figure 3-42: DNS Settings (IPv4).. . 47 Figure 3-43: Network Settings.. .. 47 Figure 3-44: WiFi Network Information . . 48 Figure 3-45: Select Country Code and SSID Name..... .. 48 Figure 3-46: Cellular Network .. . 49 Figure 3-47: Enable Cellular Network .. . 49 Figure 3-48: Select Time Settings..... .. 50 Figure 3-49: Configure Time Settings . . 50 Figure 3-50: Configure NTP Settings... .51 Figure 3-51: Synchronize Time... . 51 Figure 3-52: Serial Settings.... . 52 Figure 3-53: Configure Serial Port .. . 52 Figure 3-54: Account Management.. . 53 Figure 3-55: Create User Accounts... . 53 Figure 3-56: System Management.. . 54 Figure 3-57: Factory Default and Firmware Upgrade... . 54 Figure 3-58: Event Log . . 55 Figure 3-59: Event Log Information... . 55 Figure 3-60: External Storage.. . 56 Figure 3-61: Manage External Storage. . 56 Figure 3-62: System Information... .57 Figure 3-63: Device Information and Software Version ........... .. 57 # 1 Introduction The EMU-210 IoT Energy Gateway provides communication conversion between different Ethernet or serial-based protocols allowing for wider integration of devices into a network with the ability to send data to the cloud. It is designed to work under a large variety of applications such as monitoring energy consumption, electric vehicle charging control and monitoring, renewable energy monitoring, and smart manufacturing. The EMU-210 is an i.MX8M Plus based high-performance IoT gateway with a Quad Core processor open platform design, two RS-232/422/485 isolated serial ports, two 10/100/1000 Ethernet ports, two USB 3.0 port and an operating temperature range of -20\~70°C. It offers two M.2 slots for integrating Wi-Fi/4G/5G modules. The EMU-210 enables system integrators to develop applications precisely for renewable energy, EV charging, smart cities and factories that require massive data collection, a cloud-based application and video related monitoring solutions. # 1.1 Features  NXP i.MX8M Plus Cortex A53 Quad Core 1.8GHz  LPDDR4 2GB RAM, 32GB eMMC for system storage  2x RS-232/422/485 isolated serial ports  2x 10/100/1000 Ethernet ports  1x M.2 E-key for Wi-Fi  1x M.2 B-key for 5G or 4G/LTE  Operating Temperature: $\mathsf { - } 2 0 ^ { \circ } \mathsf { C }$ to $70 \textdegree$ # 1.2 Packing List 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. Ensure that the following items are included in the package.  1x EMU-210 IoT Gateway  DIN rail mount kit with 2x flat head screws  Wall mount kit with 4x pan head screws  Quick Start Guide # 1.3 Optional Accessories  12V/240W power adaptor (P/N: 31-62164-0010-A0)  24V/90W power adapter (P/N: 31-62187-1000-A0) # 1.4 Specifications
ModelEMU-210
System
Processori.MX8M Plus ARM Cortex A53 Quad Core 1.8GHz
MemoryLPDDR4 2GB
Main Storage32 GB eMMC
Storage Slot1x microSD
TPMTPM2.0
RTCMonthly difference max.180 sec.
WDTSupported
I/O Interfaces
Ethernet2x GbE
Serial Ports2x RS-232/422/485, 4-wire
USB2x USB 3.0 Type-A
Display1x HDMI
Wi-Fi/BT1x M.2 E-key
Expanded I/F1x M.2 B-key (USB 3.0) for 5G or 4G/LTE
Mechanical
Dimensions110.90 (L) x 40 (W) x 131.4 (H) mm
MountingDIN rail kit / wall mount kit
HousingMetal, IP40
CoolingFanless
Power Supply
DC Input12-24V DC
Environmental
Operating Temperature-20°C to 70°C
Storage Temperature-25°C to 80°C
Humidityapprox. 95% @ 40°C (non-condensing)
Vibration Resistance1. Test Standard: Referenced from IEC 60068-2-642. Test Mode: Random wave3. Frequency: 5-500 Hz4. Acceleration: 2 Grms5. Direction: X, Y, Z axis6. Duration: 60 min/axis
Shock Resistance1. Test Standard: Referenced from IEC 60068-2-272. Acceleration: 20G3. Pulse width: 11ms4. System condition: Operation mode5. Test faces: -X,-Y,-Z, X, Y, Z axis6. Test times: 3 times per axis
Certifications
EMCCE / UKCA / RCM / KC / FCCEN/IEC 61000-6-4:2019; EN/IEC 61000-6-2:201947 CFR FCC Part 15 Subpart B, class B
ULIEC 62368-1:2014; EN 62368-1:2014+A11:2017UL 61010-1; CSA C22.2 No.61010-1UL 61010-2-201; CSA C22.2 No.61010-2-201
# 1.5 Functional Block Diagram ![Based on the provided block diagram, here is a concise description of the labeled blocks and their connections:\n\n**Central Processor**\n* A central block labeled '**i.MX8M Plus**' contains the inner block '**ARM CORTEX 4x A53 + M7**'.\n\n**Power and Reset**\n* '**12-24V DC-IN**' connects to '**OVP UVP**'.\n* '**OVP UVP**' connects to '**Buck Converter to 5V**'.\n* '**Buck Converter to 5V**' connects to '**PMIC**'.\n* '**Reset Button**' connects to '**PMIC**'.\n* '**PMIC**' connects via '**I2C**' to '**I2C1_SDA I2C1_SCL**'.\n* '**PMIC**' connects to '**POWER**'.\n\n**Ethernet**\n* Two instances of '**RJ45**' connect to '**Ethernet PHY**'.\n* Each '**Ethernet PHY**' connects via '**RGMII**' to '**RGMII_TXC/RXC RGMII_TD/RD(3:0)**'.\n* Each '**Ethernet PHY**' connects to '**RST/INT**'.\n\n**Serial and UART**\n* '**UART2_TX/RX**' connects to '**SW Debug**'.\n* '**UART3_TX/RX UART3_CTS/RTS**' connects via '**UART**' to '**RS232/RS485/RS422 Serial Transceiver**'.\n* '**RS232/RS485/RS422 Serial Transceiver**' connects to '**Connector**'.\n* '**UART4_TX/RX UART4_CTS/RTS**' connects via '**UART**' to '**RS232/RS485/RS422 Serial Transceiver**'.\n* This second transceiver connects to '**Connector**'.\n* '**UART1_TX/RX UART1_CTS/RTS**' connects via '**UART**' to '**PCIE CLK**'.\n\n**I2C Peripherals**\n* '**I2C2_SCL I2C2_SDA**' connects via '**I2C**' to '**RTC**'.\n* '**I2C3_SCL I2C3_SDA**' connects via '**I2C**' to '**TPM**'.\n\n**Storage and Memory**\n* '**DRAM**' connects to '**LPDDR4 2GB**'.\n* '**SDHC3**' connects to '**eMMC5.1 32GB**'.\n* '**SDHC2**' connects via '**USB 2.0**' to '**Micro SD**'.\n* '**SDHC1**' connects to '**PCIE_REF_CLK_P/N**'.\n\n**USB and PCIe**\n* '**USB1_P/N**' connects via '**USB HS MUX**' to '**Micro USB 2.0**'.\n* '**USB1_RX_P/N USB1_TX_P/N**' connects via '**USB 2.0**' to '**USB30 HUB**'.\n* '**USB30 HUB**' connects via '**USB3.0 Type A**' to '**USB3.0 Type A**'.\n* '**USB1_P/N**' connects via '**USB 3.0**' to '**USB1_RX_P/N USB1_TX_P/N**'.\n* '**USB2_P/N USB2_TX_P/N USB2_RX_P/N**' connects via '**USB 2.0/USB 3.0**' to '**M.2 B Key**'.\n* '**M.2 B Key**' connects to '**USIM Slot**'.\n* '**PCIE_TXP/N PCIE_RXP/N**' connects via '**PCIE**' to '**M2 E Key**'.\n* '**PCIE_CLK GEN**' connects via '**PCIE CLK**' to '**M2 E Key**'.\n* '**PCIE CLK**' connects to '**PCIE_REF_CLK_P/N**'.\n\n**Display and Control**\n* '**HDMI2.0**' connects via '**HDMI**' to '**HDMI Connector**'.\n* '**GPIO**' connects to '**Power Button**'.\n* '**GPIO**' connects to '**LEDs**'.](.emu-210-50m-19701-1000-10/ea2b2440c2d6142a22df30ac964fb0b599d4b4da3100b279b05f5e8edd83f50f.jpg) Figure 1-1: Functional Block Diagram # 1.6 Mechanical Drawings ![The image displays an icon of a white document sheet with a folded top-left corner. Faint horizontal grey lines run across the paper, suggesting text or a form. A large, bold red checkmark is superimposed over the document, indicating approval, completion, or selection.](.emu-210-50m-19701-1000-10/631c705a37118018ebb17c51898c1b491e60df868aa3d4d227f7ae79db381616.jpg) NOTE: All dimensions are in millimeters unless noted. # 1.6.1 Dimensions ![110.90\n40\n131.40](.emu-210-50m-19701-1000-10/1cd4fe944112f65ee6c248ef14c51750ef2c1c4b093921477f17f061158a89ba.jpg) Figure 1-2: EMU-210 Dimensions # 1.6.2 DIN Rail Mounting The DIN rail mount can be attached to the EMU-210 with two screws included in the wall mounting kit. ![Technical diagram of an electronic device with labeled components and mounting points, including a bracket and terminal blocks.](.emu-210-50m-19701-1000-10/407fab58f509891026f605561811ad074a90e25970261eef397f086409a71784.jpg) ![48.27\n43.26](.emu-210-50m-19701-1000-10/00e3d03605d582034fd17c03d520ee382c2b9294bb70b7493ab601e87916e3e4.jpg) Figure 1-3: DIN Rail Mount 1 ![Technical diagram of an electronic device with labeled components and dimensional annotations](.emu-210-50m-19701-1000-10/023ad35e4ba682f5b84ba4fdea70401de6d38e1ffc11ef55a251af7123c534d4.jpg) Figure 1-4: DIN Rail Mount 2 # 1.6.3 Wall Mounting Each wall mount bracket can be attached to the EMU-210 with two screws included in the wall mounting kit. ![5.20\n20\nR5\n9.5W\n1.5WD\n1.5WD\n2.5WD\n3.5WD\n4.5WD\n5.5W\n70\nØ5.20\n40\n50\n40.50](.emu-210-50m-19701-1000-10/339dcb52562d05aeefe935636c48616ec07a4108747f75e61a0ad0c36350fa26.jpg) ![Technical line drawing of an electronic device with mounting holes and internal components (no text or symbols)](.emu-210-50m-19701-1000-10/80eb2f2fe4d6132bbc976b55b9ed1defaab62e488eb208a10dfddb59c49ea401.jpg) Figure 1-5: Wall Mount 1 ![MNT3\n100\nMOM\nMOM\nINT-1\nINT-2\nINT2\nUSB1\nUSB2\nINT1\nINT3\n40\n55\n70\n20\n40\n50\n30.25\n110.9](.emu-210-50m-19701-1000-10/3f20d59c4ea56454adad49f98a85d72835c8a611dae0d7274e580310182c4e23.jpg) ![Technical line drawing of an electronic device with mounting holes and internal components (no text or symbols)](.emu-210-50m-19701-1000-10/9a46177af6a5dd7eda082c507a65096cf720f50d490be174e0828a9de5e00877.jpg) Figure 1-6: Wall Mount 2 ![50\n40\n33.25\n158.95\n173.95\n5.20\n20\nØ5.20\nR5](.emu-210-50m-19701-1000-10/3fc1d533d1a32e2605e15a5493e08243bdddfccb56332f9c3e7e46ef2583d98d.jpg) Figure 1-7: Wall Mount 3 # 1.7 I/O Connectors ![A\nB\nC\nD\nE\n12-24VDC\nV+\nV-\nUSB 1\nPGM WWAN WLAN PWR\nF ANT 1\nUSB 2\n1-LAN-2\nANT 2\nANT 3\nG\nH\nI](.emu-210-50m-19701-1000-10/0367e89f2119a121635783f4c4b5788da6f795975d5c8becd0d2d72b9572b5b8.jpg) Figure 1-8: Front View ![J K L M N\nHDMI 5 4 3 2 1 5 4 3 2 1 SD / SIM\nCOM 2 COM 1\nPit RS-232 RS-422 RS-485\n1 RTS TXD+ DATA+\n2 Rx TXD+ DATA+\n3 Tx RXD+\n4 RTS RXD-\n5 GND GND GND\nANT 4 ANT 5\nANT 6\nO P Q](.emu-210-50m-19701-1000-10/d5a15d269a59eae4902ea59ad42b61608048650ad9397f81bd075e2ad2130d89.jpg) Figure 1-9: Side View
ItemDescription
ADC power input
BUSB 3.0 Type-A
C, DGigabit Ethernet (GbE, RJ45)
EFunction button
FGround screw
G, H, I, O, P, QAntenna connector (optional for Wi-Fi/4G/5G/GPS)
JMicro USB Connector
KHDMI
L, MRS-232/422/485, 4-wire
NmicroSD and SIM slot
Table 1-1: I/O Connector Legend
LEDDescription
PWR LEDThe LED will light up when the system is powered.
WLAN LEDWhen a Wi-Fi module is installed, the LED will light up after the system loads, otherwise the LED will not light up.
WWAN LEDWhen a 5G/4G/LTE module is installed, the LED will light up after the system loads, otherwise the LED will not light up.
PGM LEDThe LED will light up when flashing the BSP to the eMMC via an SD card.
Table 1-2: I/O Connector Legend # 1.7.1 DC Power Input ![Technical line drawing of a mechanical component with three circular ports and two side brackets (no text or symbols)](.emu-210-50m-19701-1000-10/57fcad0fbe5ecbb635a4fa4b1b99973bfbb72dc7b7bc58515bd3a98b0563041b.jpg) Figure 1-10: DC Power Input
PinSignal
1V+ (DC_IN)
2GND
3V-
# 1.7.2 USB 3.0 Ports The USB 3.0 Type-A ports support are compatible with SuperSpeed, Hi-Speed, full-speed and low-speed USB devices, with support for multiple boot devices, including USB flash, USB external HDD, and USB CD-ROM drivers, and boot priority and boot device configured in BIOS. # 1.7.3 Gigabit Ethernet Ports There are two Gigabit Ethernet (GbE) ports on the front panel with two MAC address. Either port can be used for connecting to a host PC  LAN1: The default is DHCP  LAN2: The default static IP address is 192.168.50.2 # 1.7.4 Reboot Button Pressing the reboot button will cause the system to reboot. # 1.7.5 Function Key Restore the EMU-210 to factory default settings by pressing the function button until the device reboots.
ItemDefault Value
usernameroot
passwordadlink
COM Port 1RS-485/9600/N/8/1
COM Port 2RS-485/9600/N/8/1
LAN 1DHCP
LAN 2Static IP:192.168.50.2
WiFi▸ Disconnect WiFi network connection▸ Clean all parameters
Cellular (optional)▸ Disconnect cellular network connection▸ Clean all parameters
# 1.7.6 Antenna Ports Antenna ports ANT1-6 support the functions listed in Appendix B: Accessory Installation on page 67. # 1.7.7 HDMI Connector An HDMI Type-A socket is provided to connect a monitor to the system. # 1.7.8 Micro-SIM Slot Insert a micro-SIM card into the slot. Make sure it is properly aligned and inserted all the way. Once the card is inserted, the EMU-210 can connect to a cellular network and access the Internet. # 1.7.9 COM Port Connectors The EMU-210 provides two COM ports through 5-pin connectors. The COM1 & COM2 ports support RS-232/422/485 modes. ![A black and white line drawing depicts a rectangular mechanical block in perspective. The front face features a top row of five circular holes or bearings aligned horizontally, and a bottom row of five rectangular slots aligned directly beneath them.](.emu-210-50m-19701-1000-10/3f8c5bd1a7c5b60b488b2dd604eb0a729c221e0a89d4feb92197687c23cb1eb2.jpg) 54321 Figure 1-11: COM Port Pin Definition
PinSignal
RS-232RS-422RS-485
1CTSTXD-DATA-
2RxTXD+DATA+
3TxRXD+
4RTSRXD-
5GNDGNDGND
Table 1-3: 5-pin Signal Function of COM Ports # 1.7.10 microSD Slot Insert a microSD card into the slot for additional storage. This page intentionally left blank. # 2 Getting Started # 2.1 Unpacking the EMU-210 Ensure that the following items are included in the package. If any items are missing, contact your sales representative for assistance.  EMU-210  DIN rail mount kit with 2x flat head screws  Wall mount kit with 4x pan head screws  Quick Start Guide ![The image displays a maroon triangular warning sign containing a white exclamation point with a dot at its base. Below the triangle, the text 'WARNING:' is printed in black capital letters.](.emu-210-50m-19701-1000-10/9f613e9f8226d28fd72dd79a04b6b034d9cefd162a579d890f67e3e7067a7121.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. # Déballage de la EMU-210 Assurez-vous que les éléments suivants sont inclus dans le colis. Si des éléments sont manquants, veuillez contacter votre représentant commercial pour obtenir de l'aide.  EMU-210  Kit de montage sur rail DIN avec 2 vis à tête plate  Kit de montage mural avec 4 vis à tête cylindrique  Guide de Démarrage Rapide ![The image displays a red triangular warning sign featuring a white exclamation point in the center. Below the triangle, the text 'WARNING:' is printed in black capital letters.](.emu-210-50m-19701-1000-10/492008238fbf41c18d4e41177f98cc481eea39c26778ed65301b9ebdece45b2d.jpg) AVERTISSEMENT: Avant de déballer, vérifiez l'emballage d'expédition pour tout dommage. Si l'emballage d'expédition et/ou le contenu sont endommagés, informez immédiatement votre revendeur. Conservez l'emballage d'expédition et les matériaux d'emballage pour inspection. Obtenez l'autorisation de votre revendeur avant de retourner tout produit à ADLINK. # 2.2 Connecting DC Power DC power source output rating:  Voltage: 12 to 24 VDC  Current: 5A to 2.5A minimum Follow these steps to connect power to the EMU-210: 1 Before turning on the power source, connect the positive and negative wires from a 12 to 24V DC power source to the terminal block. 2. Turn on the power source. If the power was connected correctly, the front panel green PWR LED will light up. ![A vertical red triangle containing a white exclamation point is positioned above the word 'WARNING' in black capital letters.](.emu-210-50m-19701-1000-10/4df90e84f148b7c3aea879160c111048728c4e064dd09ee54776613055ca54ba.jpg)  Only use an IEC or UL certified power source.  The maximum operating altitude is 5000m whose output meets LPS and SELV (ES1) circuits. If the EMU-210 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. ![This is a standard yellow triangular warning sign with a black border. Inside the triangle is a black exclamation point. Below the triangle, the text 'CAUTION:' is printed in black capital letters.](.emu-210-50m-19701-1000-10/cc92c3f3571cd11f7aaa44d7ce8958f21c453d5b902f41437a607b5f3c93eb14.jpg)  Ensure the power source is turned off before connecting or removing the power wires. Before providing DC power to the apparatus, ensure the voltage and polarity provided are compatible with the DC input. Improper input voltage and/or polarity can be responsible for system damage. # Connexion de l'alimentation CC Valeur nominale de sortie de la source d'alimentation CC:  Tension: 12 à 24 VCC  Courant: 5A à 2,5A minimum Suivez ces étapes pour connecter l'alimentation à l'EMU-210: 1 Avant d'allumer la source d'alimentation, connectez les fils positifs et négatifs d'une source d'alimentation de 12 à 24 V CC au bornier. 2. Allumez la source d’alimentation. Si l'alimentation a été correctement connectée, la LED verte PWR du panneau avant s'allumera. ![The image displays a red triangular warning symbol containing a white exclamation point. Below the triangle, the text 'WARNING:' is written in black capital letters.](.emu-210-50m-19701-1000-10/82d8a43f3502dd9682cd2d679efe71237ddc9d2be5bfffd78853e62684ec4d95.jpg) Utilisez uniquement une source d'alimentation certifiée IEC ou UL.  L'altitude maximale de fonctionnement est de 5 000 m dont la sortie répond aux circuits LPS et SELV (ES1). Si l'EMU-210 doit être arrêté, coupez la source d'alimentation. Pour retirer les fils d'alimentation, utilisez un tournevis à tête plate pour pousser les fentes orange du bornier puis retirez les fils. ![The image displays a standard warning sign featuring a yellow triangle with a black border. Inside the triangle is a large black exclamation point. Below the triangle is a white rectangular section containing the word 'CAUTION' in black capital letters.](.emu-210-50m-19701-1000-10/3e618d227ca8a1f2ec6672060bcb0d74d9f31000fe1ca39b7af484b7e3e6665a.jpg)  Assurez-vous que la source d'alimentation est éteinte avant de connecter ou de retirer les fils d'alimentation.  Avant de fournir une alimentation CC à l'appareil, assurez-vous que la tension et la polarité fournies sont compatibles avec l'entrée CC. Une tension d'entrée et/ou une polarité incorrecte peuvent être responsables d'endommagements du système. # 2.3 Connecting to the EMU-210 1 When power is supplied, the PWR LED will initially blink green while the system boots up, then change to a solid green indicating the device has successfully booted up. 2. Connect LAN2 of the EMU-210 to the host computer. 3. Set the network domain of the host computer to 192.168.50.xx. 4. Open a web browser (Google Chrome is recommended) on the host computer and enter http://192.168.50.2 to access EGiFlow (Figure 3-1). 5. Enter admin as the username and adlink as the password (Figure 3-1). 6. After logging in, EGiFlow displays. (Figure 3-2). # 3 EGiFlow This chapter describes how to use the built-in EGiFlow to configure the EMU-210 and start different kind of applications. # 3.1 EGiFlow Login After the EMU-210 has been successfully powered on, access EGiFlow via one of the default following options. Option 1: With a host PC connected to the EMU-210 LAN2 port, do the following: 1. Set the host PC’s network setting to Static IP mode. 2. Modify the host PC’s IP address to be on the same network segment as the device (192.168.50.x). 3. Open a web browser (Google Chrome is recommended) on the host PC to access EGiFlow: http://192.168.50.2, or enter the EMU-210 hostname in the address bar (e.g., http://emu210-2361100lba.local/) Option 2: With a host PC connected to the EMU-210 LAN1 port, do the following: 1. Set the host PC’s network setting to DHCP mode. 2. Open a web browser (Google Chrome is recommended) on the host PC to access EGiFlow by entering the EMU-210 hostname in the address bar (e.g., http://emu210-2361100lba.local/) Option 3: Connect the LAN1 port of the EMU-210 to a network component (switch/router) with DNS functionality: 1. Set the host PC’s network setting to DHCP mode and connect to network component (switch/router). 2. Open a web browser (Google Chrome is recommended) on the host PC to access EGiFlow by entering the EMU-210 hostname in the address bar (e.g., http://emu210-2361100lba.local/) A unique default hostname is generated for each EMU-210 device and can be found on the label of the chassis it was shipped in. The hostname can be changed from EGiFlow (default username: admin, default password: adlink). ![A red logo resembling the letter 'A' with a curved base, featuring three horizontal white stripes within the upper triangular section, accompanied by a small registered trademark symbol (®) to the bottom right.](.emu-210-50m-19701-1000-10/3f909c9d8e8bebdbb931e0e00f9d524bd0cf179ab6b0453caf29f83960cc6553.jpg) # ADLINK # Username Password # Sign In Figure 3-1: EGiFlow Login Page ![EGIFlow\n不安全 http://192.168.50.2/#/\nADLINK\nEGIFlow\nOverview\niApp Creator\nNetwork Settings\nTime Settings\nSerial Settings\nAccount Management\nSystem Management\nEvent Log\nExternal Storage\nSystem Information\nSystem Information\nDevice Type: EMU200\nHostname: EMU-200\nDevice UID: 44dbcb80-c85e-S18d-9609-\n544816923d6\nSerial Number:\nUptime: 10:33:28 up 30 min\nNetwork Interfaces\nLAN1\nCable unplugged\nLAN2\nIPv4 address: 192.168.50.2\nIPv6 Address: fw80:230:64fffe73:c296\nResource Usages\nCPU: 13.3%\nMemory: 358.18 MB free\nStorage: 23.16 GB free\nCopyright © 2022 - Current, ADLINK Technology Inc. All Rights Reserved.](.emu-210-50m-19701-1000-10/8b5979bca7126eb29e6d56966b5f0f27c4bcdf75ad562da99a09c51c6911c971.jpg) Figure 3-2: EGiFlow Main Page # 3.2 EGiFlow Menu EGiFlow includes the following items for configuration and protocol translation in different field applications. #  EGiFlow iApp  Modbus TCP/RTU to AWS and Azure  Modbus TCP/RTU to MQTT  Modbus TCP/RTU to RESTful  Modbus RTU to Modbus TCP  OPCUA to AWS #  Python iApp  Development  Deploy and Run #  Gateway Configuration & Management  Network Setting (LAN) (IPv4 IPv6)  Network Setting (WiFi) (IPv4 IPv6)"  Network Setting (Cellular) (IPv4 IPv6)"  Time Sync Setting, NTP  Account Management  System Management  Event Log  External Storage  System Information  Serial Settings # 3.2.1 EGiFlow iApp EGiFlow iApp provides an intuitive and straightforward configuration method, allowing the EMU-210 to acquire the required sensor data for measurement through various communication protocols. It then converts and transmits the data to various services, including edge servers, local SCADA, or the cloud, for applications such as energy monitoring in buildings, factories, smart factories, and for energy storage monitoring. Below are a few commonly used scenarios to illustrate how to create and use EGiFlow iApp to complete the conversion and data transmission of various communication protocols. ![ADLINK\nEGiFlow\nOverview\niApp Creator\nNew\nExport\nImport\nKeyword Search\nName ↑↓\nNo iApp found.\nCreate a new project\nEGiFlow iApp\nPython iApp\nLast Modified Date ↑↓](.emu-210-50m-19701-1000-10/5146c5ae1eeed2096601a2d3b4f9b77916a850e617287bdccdb23dec565b199b.jpg) Figure 3-3: Create EGiFlow iApp # Modbus TCP/RTU to AWS and Azure The overall architecture of the application is shown below, aiming to acquire sensor data from the Modbus interface and send it to cloud services such as Azure and AWS. ![This diagram illustrates an IoT architecture labeled 'EMU- 200' involving Modbus protocols and cloud connectivity.\n\n**Bottom Layer (Devices/Sensors):**\n* **Left:** A block labeled '**Modbus TCP Server**' featuring icons for '**Energy**' and '**Sensors**'.\n* **Right:** A block labeled '**Modbus RTU Slave**' featuring icons for '**Energy**' and '**Sensors**'.\n\n**Middle Layer (EMU- 200 Box):**\n* A large dotted box labeled '**EMU- 200**' contains two rows of text.\n * **Top Row:** '**AWS IoT Core**' and '**Azure IoT Hub**'.\n * **Bottom Row:** '**Modbus TCP Client**' and '**Modbus RTU Master**'.\n\n**Top Layer (Cloud/Connectivity):**\n* Icons representing a cloud, the '**aws**' logo, and the '**Microsoft Azure**' logo.\n* Symbols for Wi-Fi, '**4G**', and a network hub are situated between the middle box and the top icons.\n\n**Connections:**\n* A dashed arrow points from '**Modbus TCP Server**' upward to '**Modbus TCP Client**'.\n* A dashed arrow points from '**Modbus RTU Slave**' upward to '**Modbus RTU Master**'.\n* A dashed arrow points from '**Modbus TCP Client**' upward to '**AWS IoT Core**'.\n* A dashed arrow points from the '**EMU- 200**' box upward toward the cloud icons and logos.](.emu-210-50m-19701-1000-10/a8b19e9685358f107c6db91c8da6cbb1ecfe1e6d8871ab21370c202172846840.jpg) Figure 3-4: Modbus TCP/RTU to Cloud To achieve this, you can utilize EGiFlow iApp as a middleware component. 1. Modbus TCP Client (Master): Use EGiFlow iApp's intuitive setup to create and configure the Modbus TCP client (master) functionality. Specify the Modbus server's IP address, port number, and other necessary parameters. EGiFlow iApp provides an interface to define the data registers to be read from the Modbus server. ![ADLINK\nOverview\niApp Creator\nNetwork Settings\nTime Settings\nSerial Settings\nAccount Management\nSystem Management\nEvent Log\nExternal Storage\nSystem Information\nEZiApp_1692446359\nRun Stop\nSource\n+\nCompute\nDestination\nChoose Your Source Component\nOPC UA Read Modbus TCP Read Modbus RTU Read MQTT Sub](.emu-210-50m-19701-1000-10/c13e10da6815a2bc44c6fc1e2eb40447b3a26afb385f13b24ae0d8c735eedeb3.jpg) Figure 3-5: Create Modbus TCP ![Configure Your Source\nModbus TCP\nKey ModbusTCP-9fb73a\nIP Address*\n172.30.70.52 Port* Slave ID*\n502 0\n+ Add\nTag Function Address Quantity Type\nt1 Input Register 1 2 float32 ✓ ✓ ✗\n( Back ✓ Save](.emu-210-50m-19701-1000-10/4bb01178db09806a94570251c197d82e3b33dd0fcc562bd32a367a7ce2d8a76a.jpg) Figure 3-6: Configure Modbus TCP 2. Modbus RTU Master: Use EGiFlow iApp's setup to create and configure the Modbus RTU Master functionality. Determine the serial parameters required for communication, such as baud rate, parity, data bits, and stop bits. EGiFlow iApp provides an interface to define the data registers to be read from the Modbus slave. ![ADLINK\nOverview\nUApp Creator\nNetwork Settings\nTime Settings\nSerial Settings\nAccount Management\nSystem Management\nEvent Log\nExternal Storage\nSystem Information\nEZiApp_1692446359\nRun Stop\nSource\n+\nCompute\nDestination\nChoose Your Source Component\nOPC UA Read Modbus TCP Read Modbus RTU Read MQTT Sub](.emu-210-50m-19701-1000-10/4236a9acb91ad2541ab72b84b58fe07daa7b8670935677c0ea8ce118038e8de7.jpg) Figure 3-7: Create Modbus RTU ![Configure Your Source\nModbus RTU\nKey* ModbusRTU-f132a0\nSerial Port*\nBaudrate*\nSlave ID*\nCOM1 9600 0\nData Bits* Parity* Stop Bits*\n8 None 1\n+ Add\nTag Function Address Quantity Type\nt2 Discrete Input 3 2 float32\n( Back Save](.emu-210-50m-19701-1000-10/f4dbd24437c8f53f91b4de90f81e664c9bf4b1d4cfa91b0aa25efb69bfc690b8.jpg) Figure 3-8: Configure Modbus RTU 3. Data Conversion by Compute: Upon receiving the sensor data from the Modbus server/slave, EGiFlow iApp can perform any required data conversions or formatting as per the specific requirements of Azure and AWS. This may include transforming the data into the appropriate format, applying data preprocessing or aggregation, and ensuring compatibility with the cloud service APIs. ![ADLINK\nOverview\nUapp Creator\nNetwork Settings\nTime Settings\nSerial Settings\nAccount Management\nSystem Management\nEvent Log\nExternal Storage\nSystem Information\nEZiApp_1692446359\nRun Stop\nSource\nCompute\nDestination\n+\n+\nChoose Your Compute Component\nPython\nFunction](.emu-210-50m-19701-1000-10/3de76d8998704d44661e20eeb0a33d32b333533f07bdd9b35732a476cf9c2f24.jpg) Figure 3-9: Create Compute Configure Your Compute ![The image displays two grey icons on a white background. On the left is a square outline with an arrow pointing outward from the top-right corner and a smaller square in the bottom-left corner. To its right is a simple 'X' shape.](.emu-210-50m-19701-1000-10/78d21b3a4160556bda8d6c1773a73a40330065db2c80483940113088fcea0ebd.jpg) Python Function ![ModbusRTU-Test_t1\nRetrieve values from source component by it's tag.\nApply custom logic to these values to compute a new value\nThe most important thing is to return a value at the end\ne.g.\ncomputed_value = values('(source_tag)') + 1\nreturn computed_value\n'''\ncomputed_value = values('ModbusRTU-Test_t1') + 1\nreturn computed_value](.emu-210-50m-19701-1000-10/434fc7774a0dd26e7f8747c5f70fad1b9f363b6b25d1b4ec28b60fe70c75fbff.jpg) Figure 3-10: Develop Customized Data Conversion 4. Data Transmission to Azure: EGiFlow iApp can utilize Azure IoT Hub to securely transmit the converted sensor data. It establishes a connection with Azure and publishes the data to the desired Azure endpoint. ![ADLINK\nOverview\niApp Creator\nNetwork Settings\nTime Settings\nSerial Settings\nAccount Management\nSystem Management\nEvent Log\nExternal Storage\nSystem Information\nEZiApp_1692446359\nRun Stop\nSource Compute Destination\n+ +\n+ +\nChoose Your Destination Component\nMQTT\nPub Azure\nIoT Hub\nPub AWS IoT\nCore Pub RESTful\nWrite OPC UA\nWrite Modbus\nTCP Write](.emu-210-50m-19701-1000-10/b015011fc400c3e10463d9882f21cfe23412deccd8eb0873d301b59f3f173cfd.jpg) Figure 3-11: Create Azure ![Configure Your Target\nAzure IoT Hub Pub\nKey AzurelotHub-1faab8 Select Input Tags\nConnection String*\nHostName=xxxx.azure-devices.net;DeviceId=xxx;SharedAccessKey=(KEY)\nBack Save](.emu-210-50m-19701-1000-10/026dd0c02ae3b9dceda5739ba0bc794604f30287f4c7a38aca9c1b3d19247802.jpg) Figure 3-12: Configure Azure 5. Data Transmission to AWS: Similarly, EGiFlow iApp can leverage AWS IoT Core to securely transmit the converted sensor data. It establishes a connection with AWS and publishes the data to the desired AWS endpoint. ![ADLINK\nOverview\niApp Creator\nNetwork Settings\nTime Settings\nSerial Settings\nAccount Management\nSystem Management\nEvent Log\nExternal Storage\nSystem Information\nEZiApp_1692446359\nRun Stop\nSource\nCompute\nDestination\n+\n+\nChoose Your Destination Component\nMQTT\nPub\nAzure\nIoT Hub\nPub\nAWS IoT\nCore Pub\nRESTful\nWrite\nOPC UA\nWrite\nModbus\nTCP\nWrite](.emu-210-50m-19701-1000-10/18340680b9913b490d10311121f08ebdc85d5271c317ba1f9b7a707b3834e4d2.jpg) Figure 3-13: Create AWS ![Configure Your Target\nAWS IoT Core Pub\nKey AWSIoTCore-8f481e Select Input Tags\nClient ID*\nCLIENT_ID Endpoint*\nxxxx-xxxx.amazonaws.com\nTopic*\nsdk/test/python QoS*\n0\nCertificate*\n+ Choose your certificate\nPrivate Key*\n+ Choose your private key\nRoot CA*\n+ Choose your root CA\n( Back ✓ Save](.emu-210-50m-19701-1000-10/8f00e339a03d2b0d85915cc4b338440178ec19d34220b83eebae5cff845e8e15.jpg) Figure 3-14: Configure AWS 6. Run and Deploy: Click Run and wait for the deployment to finish. ![Test\n✓ Deploy Success\ndeploy done\nRun Stop](.emu-210-50m-19701-1000-10/303cef3b767653adbed0bc5e883d968af8b4297c8187bff93bfc150ab72787c6.jpg) Figure 3-15: Run and Deploy # Modbus TCP/RTU to MQTT The overall architecture of the application is in Figure 3-16, with the objective of acquiring sensor data from the Modbus interface and transmitting it via MQTT to an Edge Server or Local SCADA. ![This diagram illustrates a data flow architecture involving an edge device, sensors, and a central server.\n\n**Labeled Blocks:**\n\n* **Top:** 'Edger Server/Local SCADA' (Note: 'Edger' is spelled as shown) with the text 'MQTT Subscribe' below it. An icon of a computer monitor and server rack is present.\n* **Middle (enclosed in a dotted box):** Labeled 'EMU- 200'. Inside, there are two blocks: 'Modbus TCP Client' (left) and 'Modbus RTU Master' (right). In the center of the box is the text 'MQTT Publish'.\n* **Bottom Left:** 'Modbus TCP Server'. Below it are icons labeled 'Energy' (lightning bolt in circle) and 'Sensors' (server rack, gauge, phone).\n* **Bottom Right:** 'Modbus RTU Slave'. Below it are identical icons labeled 'Energy' and 'Sensors'.\n\n**Connections (Arrows):**\n\n* **Upward from Bottom to Middle:** Dotted arrows point upward from 'Modbus TCP Server' to 'Modbus TCP Client' and from 'Modbus RTU Slave' to 'Modbus RTU Master'.\n* **Upward within EMU-200:** Arrows point upward from 'Modbus TCP Client' and 'Modbus RTU Master' towards the central 'MQTT Publish' label.\n* **Upward to Top:** An arrow points upward from 'MQTT Publish', passing through icons representing Wifi, '4G', and a network switch, connecting to 'Edger Server/Local SCADA'.](.emu-210-50m-19701-1000-10/56e98f73de9d762b69cc4cf913264d8354e310d5692eb3aed3c50b075ea5ccc9.jpg) Figure 3-16: Modbus TCP/RTU to MQTT To accomplish this, you can follow the steps below using EGiFlow iApp: 1. Modbus TCP Client (Master): Use EGiFlow iApp's setup to create and configure the Modbus TCP client (master) functionality. Specify the Modbus server's IP address, port number, and other necessary parameters. EGiFlow iApp provides an interface to define the data registers to be read from the Modbus server. (See Figure 3-5 and Figure 3-6) 2. Modbus RTU Master: Use EGiFlow iApp's setup to create and configure the Modbus RTU Master functionality. Determine the serial parameters required for communication, such as baud rate, parity, data bits, and stop bits. EGiFlow iApp provides an interface to define the data registers to be read from the Modbus slave. (See Figure 3-7 and Figure 3-8) 3. Data Conversion by Compute: Upon receiving the sensor data from the Modbus server/slave, EGiFlow iApp can perform any necessary data conversion or formatting to ensure compatibility with MQTT. This may involve transforming the data into a suitable format, applying any required preprocessing or aggregation, and ensuring adherence to the MQTT payload structure. (See Figure 3-10) 4. MQTT Communication: EGiFlow iApp integrates MQTT functionality to connect to an MQTT broker. It establishes a connection with the broker and publishes the converted sensor data as MQTT messages. The MQTT broker can be located on the Edge Server or within the Local SCADA environment. ![ADLINK\nTest\nRun Stop\nSource\nCompute\nTarget\n+\n+\n+\nChoose Your Target Component\nMQTT Pub\nAzure IoT\nHub Pub\nAWS IoT Core\nPub\nRESTful](.emu-210-50m-19701-1000-10/77aaea154b17bd50096578a19dad59d65d2e34bfb8eb6612a71c3c90dfaa3c31.jpg) Figure 3-17: Create MQTT Publish ![Configure Your Destination\nMQTT Pub\nKey* MqttPub-34c771\nCompute-42798\nBroker Address*\n127.0.0.1\nTopic*\ntest\nUsername\nPassword\nBack\nSave](.emu-210-50m-19701-1000-10/5ab99066b7fa88df5b7a57af53ec5a564e45d827a966375f41a377aa153fdaed.jpg) Figure 3-18: Configure MQTT Publish 5. Run and Deploy: Click Run and wait for the deployment to finish. (See Figure 3-15) # Modbus TCP/RTU to RESTful The overall architecture of the application is in Figure 3-19, with the objective of acquiring sensor data from the Modbus interface and transmitting it via RESTful API to an Edge Server or Local SCADA. ![This diagram illustrates a hierarchical system architecture with communication flowing upwards.\n\n**Labeled Blocks:**\n\n* **Top Level:**\n * 'Edger Server/Local SCADA' (orange text) next to server rack icons.\n * 'Web Server' (text below server icons).\n * A computer monitor icon (to the left of the server icons).\n* **Middle Level (Dashed Box):**\n * 'EMU- 200' (label on the left edge of the box).\n * 'RESTful' (center top inside the box).\n * 'Modbus TCP Client' (left side inside the box).\n * 'Modbus RTU Master' (right side inside the box).\n* **Bottom Level:**\n * 'Modbus TCP Server' (left side).\n * 'Modbus RTU Slave' (right side).\n * 'Energy' (appears twice, next to lightning bolt icons).\n * 'Sensors' (appears twice, below small device icons).\n* **Network Indicators:**\n * '4G' (text between top and middle levels).\n * WiFi and network switch icons (between top and middle levels).\n\n**Connections:**\n\n* **RESTful Connection:** A dashed arrow points upward from 'RESTful' to the computer monitor icon at the top.\n* **Modbus TCP Connection:** A dashed arrow points upward from the 'Modbus TCP Server' area (labeled 'Energy' and 'Sensors') to 'Modbus TCP Client'.\n* **Modbus RTU Connection:** A dashed arrow points upward from the 'Modbus RTU Slave' area (labeled 'Energy' and 'Sensors') to 'Modbus RTU Master'.](.emu-210-50m-19701-1000-10/2cd5f28418de5e782d2b5832ec61ec1952f777bd82f2283b2b78efd99f699f47.jpg) Figure 3-19: Modbus TCP/RTU to RESTful To achieve this, you can follow the steps below using EGiFlow iApp: 1. Modbus TCP Client (Master): Use EGiFlow iApp's setup to create and configure the Modbus TCP client (master) functionality. Specify the Modbus server's IP address, port number, and other necessary parameters. EGiFlow iApp provides an interface to define the data registers to be read from the Modbus server. (See Figure 3-5 and Figure 3-6) 2. Modbus RTU Master: Use EGiFlow iApp's setup to create and configure the Modbus RTU Master functionality. Determine the serial parameters required for communication, such as baud rate, parity, data bits, and stop bits. EGiFlow iApp provides an interface to define the data registers to be read from the Modbus slave. (See Figure 3-7 and Figure 3-8) 3. Data Conversion by Compute: Upon receiving the sensor data from the Modbus server/slave, EGiFlow iApp can perform any required data conversion or formatting to prepare it for RESTful API transmission. This may involve transforming the data into a compatible format, applying preprocessing or aggregation, and organizing it according to the RESTful API payload structure. (See Figure 3-9) 4. RESTful API Communication: EGiFlow iApp integrates RESTful API functionality to connect to the Edge Server or Local SCADA system. It establishes an HTTP/HTTPS connection with the designated API endpoint and sends the converted sensor data as RESTful API requests. The API endpoint should be configured to receive and process the incoming data accordingly. ![ADLINK\nOverview\niApp Creator\nNetwork Settings\nTime Settings\nSerial Settings\nAccount Management\nSystem Management\nEvent Log\nExternal Storage\nSystem Information\nEZiApp_1692446359\nRun Stop\nSource\nCompute\nDestination\n+\n+\nChoose Your Destination Component\nMQTT\nPub\nAzure\nIoT Hub\nPub\nAWS IoT\nCore Pub\nRESTful\nWrite\nOPC UA\nWrite\nModbus\nTCP\nWrite](.emu-210-50m-19701-1000-10/69b56f03962f6a58e33909e85f3319f324e16ab95e23bd89bf73f08cd9903324.jpg) Figure 3-20: Create RESTful ![Configure Your Target\nRESTful\nKey* Rest-848ec4 Select Input Tags\nURL*\nhttp://127.0.0.1:8080 Method*\nPOST\nBack Save](.emu-210-50m-19701-1000-10/72c79362f45b77d8d0876c66e6cdf8893ca1554e2fc4a88bd708a1d50314eb50.jpg) Figure 3-21: Configure RESTful # 5. Run and Deploy: Click Run and wait for the deployment to finish. (See Figure 3-15) # Modbus RTU to Modbus TCP The overall architecture of the application, as shown in Figure 3-22, aims to convert Modbus RTU to Modbus TCP. ![The diagram depicts a data flow from left to right involving the following labeled blocks and connections:\n\n**Blocks:**\n* **Modbus RTU Slave**: Located on the far left, accompanied by icons and labels 'Energy' and 'Sensors'.\n* **EMU- 200**: A dashed box in the center containing two internal blocks: 'Modbus RTU Master' and 'Modbus TCP Server'.\n* **Network Interface**: Inside the EMU-200 box near the right edge, there are icons for a router and Wi-Fi, alongside the text '4G'.\n* **Modbus TCP Client**: Located on the far right, serving as a header for a group of device illustrations (servers, smartphones, monitors). Below these illustrations is the label 'Touch Screen (Panel Computer)'.\n\n**Connections:**\n* A dashed green arrow points from the **Modbus RTU Slave** block into the **EMU- 200** box, directed at the 'Modbus RTU Master' block.\n* Inside the **EMU- 200** box, a dashed green arrow points from 'Modbus RTU Master' to 'Modbus TCP Server'.\n* A dashed green arrow extends from the network icons ('4G') out of the **EMU- 200** box toward the **Modbus TCP Client** section on the right.](.emu-210-50m-19701-1000-10/3d0534a2e17275ac78a59dcc147aa77d5efada081021e13c10a849996586d472.jpg) Figure 3-22: Modbus RTU to Modbus TCP 1. Modbus RTU Master: Use EGiFlow iApp's setup to create and configure the Modbus RTU Master functionality. Determine the serial parameters required for communication, such as baud rate, parity, data bits, and stop bits. EGiFlow iApp provides an interface to define the data registers to be read from the Modbus slave. (See Figure 3-7 and Figure 3-8) 2. Modbus TCP Conversion: Modbus RTU requests are recieved from the RTU devices and converted into Modbus TCP requests. ![ADLINK\nEZiApp_1692446359\nRun Stop\nSource Compute Destination\n+ +\n+ +\nChoose Your Destination Component\nMQTT\nPub Azure\nIoT Hub\nPub AWS IoT\nCore Pub RESTful\nWrite OPC UA\nWrite Modbus\nTCP\nWrite](.emu-210-50m-19701-1000-10/77b4911b7c9307503a6d580c70a1c122600dc6058433f924943dde6c9c744d56.jpg) Figure 3-23: Create Modbus TCP Write ![Configure Your Destination\nModbus TCP Write\nKey ModbusTcpWrite-4c9334\nIP Address*\nPort*\nSlave ID*\n127.0.0.1 502 0\nTest Connection\n+ Add\nTag Function Address Quantity Input Tag\nt1 Holding Registers (HR) 1 1 ModbusRTU-Test_t1\nt2 Holding Registers (HR) 2 1 ModbusRTU-Test_t2\nBack Save](.emu-210-50m-19701-1000-10/21adb0762bc8b012b098ab00419a6424baa99c5349b19b58699ab1622c7af4b1.jpg) Figure 3-24: Configure Modbus TCP Write # OPC UA to AWS The overall architecture of the application is in Figure 3-25. ![Based on the provided image, here is the accurate description of the flowchart:\n\n**Labeled Blocks and Icons:**\n* **Top:** A cloud icon, the 'aws' logo, the text 'EMU- 200', a WiFi symbol, the text '4G', and a network switch icon.\n* **Middle (inside a dashed box):** The text 'AWS IoT Core' and 'OPC UA Client'.\n* **Bottom:** A server rack icon labeled 'OPC UA Server'. Below that, there are icons including a lightning bolt labeled 'Energy' and a group of icons (server rack, gauge, phone) labeled 'Sensors'.\n\n**Connections (Flow):**\n* A dashed arrow points upward from the 'Energy' / 'Sensors' area to the 'OPC UA Server'.\n* A dashed arrow points upward from the 'OPC UA Server' to the 'OPC UA Client'.\n* A dashed arrow points upward from the 'OPC UA Client' to the 'AWS IoT Core'.\n* A dashed arrow points upward from the 'AWS IoT Core' to the cloud icon.](.emu-210-50m-19701-1000-10/166a096f4fab309d54d50a2e30e8a461aa07164cd9a206ab16528048ac9ecd75.jpg) Figure 3-25: OPC UA to AWS To achieve this, you can follow the steps below using EGiFlow iApp: 1. OPC UA Client: Use EGiFlow iApp's intuitive setup to create and configure the OPC UA client functionality. Specify the OPC UA server's IP address, port number, and other necessary parameters. EGiFlow iApp provides an interface to browse node information from the server. ![ADLINK\niApp Creator\nNetwork Settings\nTime Settings\nSerial Settings\nAccount Management\nSystem Management\nEvent Log\nExternal Storage\nSystem Information\nEZiApp_1692446359\nRun Stop\nSource\n+\nCompute\n+\nDestination\nChoose Your Source Component\nOPC UA Read Modbus TCP Read Modbus RTU Read MQTT Sub](.emu-210-50m-19701-1000-10/e2a63b53796ff31806442a9aee75e11738828ac1699b09c36278544be050c4ec.jpg) Figure 3-26: Create OPC UA Configure Your Source ![The image displays two identical circular icons arranged side-by-side horizontally against a white background. Each circle features a faint, thin grey outline and contains a dark grey 'X' symbol in its center.](.emu-210-50m-19701-1000-10/8f294bda622f21576318a1a660529c41402060570659a00724dee674a0151df2.jpg) OPC UA Read ![Key OPCUA-Test\nIP Address*\n192.168.233.131\nPort*\n4841\nPath*\nOPCUA/SimulationServer\nSecurity Mode*\nSign and Encrypt\nSecurity Policy*\nBasic2565ha256\nUser Auth\nTest Connection\nb](.emu-210-50m-19701-1000-10/f04fb27979db9ad1d97094f918ec5c363fda2757b160f82885182cca6dd2b929.jpg) \+ Browse Server
TagNode IdData TypeValue
[ExtensionObject](Typed=NodeId)(Identifier=4, NamespaceIndex=2, NodeType=(NodeId)Type(FourType:1.), Body=bV01/v00/v00/v00/v00/ROCCSCUv02/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00-v). ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=<NodeId)Type(FourType:1), Body=bV1/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v00/v. ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType:1), Body=bV1/v05/v03/v05/v05/v05/v05/v05/v14(v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v 1), ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType:1), Body=bV2/v14(v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v14,v 1), ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType:1), Body=bV3/v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v25-v 1), ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType:1), Body=bV3/v26-v26-v26-v26-v26-v26-v26-v26-v26-v26-v26-v26-v26-v26-v26-v26-v26-v26-v26-v26-v26-v26-v26-v26-v 1), ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType:1), Body=bV3/v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v36-v 1), ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType:1), Body=bV4/v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v38-v 1), ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType:1), Body=bV5/v39-v39-v39-v39-v39-v39-v39-v39-v39-v39-v39-v39-v39-v39-v 1), ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType:1), Body=bV7-gv4-gv4-gv4-gv4-gv4-gv4-gv4-gv4-gv4-gv4-gv4-gv4-gv4-gv4-gv4-gv4-gv4-gv4-gv4-gv4-gv4-gv 1), ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType:1), Body=bV8-gv5-gv5-gv5-gv5-gv5-gv5-gv5-gv5-gv5-gv5-gv5-gv5-gv5-gv5-gv5-gv5-gv5-gv5-gv5-gv5-gv 1), ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType:1), Body=bV9-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7-gv7g v)
Analgorithmsns=2)=5ExtensionObject[ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType:1), Body=bV9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv9/gv 1], ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType:1), Body=bV10/gv10/gv10/gv10/gv10/gv10/gv10/gv10/gv10/gv10/gv10/gv10/gv10/gv10/gv10/gv10/gv10/gv10/gv10/gv10/gv1 1), ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType:1), Body=bV11/gv11/gv11/gv11/gv11/gv11/gv11/gv11/gv11/gv11/gv11/gv11/gv 1), ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType:1), Body=bV12/gv12/gv12/gv12/gv12/gv12/gv12/gv12/gv12/gv12/gv 1), ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType: 1), Body=bV13/gv13/gv13/gv13/gv13/gv13/gv13/gv13/gv 1), ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType: 1), Body=bV14/gv14/gv14/gv14/gv14/gv14/gv14/gv 1), ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType: 1), Body=bV15/gv15/gv15/gv15/gv 1), ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType: 1), Body=bV16/gv16/gv 1), ExtensionObject(TypeId=NodeId)(Identifier=4, NamespaceIndex=2, NodeIdType=(NodeId)Type(FourType: 1), Body=bV17/gg v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 8g v 9]
Figure 3-27: Configure OPC UA 2. Data Conversion by Compute: Use EGiFlow iApp's setup to create python functions, import OPC UA server data from the drop-down menu, reference sample code or write your own algorithms. ![ADLINK\nOverview\niApp Creator\nNetwork Settings\nTime Settings\nSerial Settings\nAccount Management\nSystem Management\nEvent Log\nExternal Storage\nSystem Information\nEZiApp_1692446359\nRun Stop\nSource\nOPCUA-934a3\nOPC UA Read\nIP: 192.168.1.8 port: 53530\nCompute\n+\nDestination\nChoose Your Compute Component\nPython\nFunction](.emu-210-50m-19701-1000-10/663bd6cbd15b8178683515b0468c603b63631acc0824190337df3667420b3be9.jpg) Figure 3-28: Create Compute ![Configure Your Compute\nPython Function\nKey* Compute-e53f6a\nOPCUA-Test_AnalogInputs\n✓\nOPCUA-Test\n✓OPCUA-Test_AnalogInputs\nShow Sar\ncurrent_net_values = {}\nfor i in range(12):\n # Decode Object data\n data_opc_tree = values('OPCUA-Test_AnalogInputs')(i)\n data_opc_tree = data_opc_tree.__dict__\n data_opc_binary = data_opc_tree('Body')\n# Decode binary data\ndata_opc = decode_opcuabinary(binary_data=data_opc_binary)\ncurrent_net_value=float(data_opc(5))\nserver = f'AnalogInput{i}'\ncurrent_net_values(server) = current_net_value\nreturn current_net_values](.emu-210-50m-19701-1000-10/fc08c1f8aee480d359b7c94f49fc00671001c1e918505d02f15ea3d65635e293.jpg) Figure 3-29: Develop Customized Data Conversion # 3. Data Transmission to AWS: Establishes a connection with AWS and publishes data to the desired AWS endpoint. ![ADLINK\nOverview\niApp Creator\nNetwork Settings\nTime Settings\nSerial Settings\nAccount Management\nSystem Management\nEvent Log\nExternal Storage\nSystem Information\nEZiApp_1692446359\nRun Stop\nSource\nCompute\nDestination\n+\n+\nChoose Your Destination Component\nMQTT\nPub\nAzure\nIoT Hub\nPub\nAWS IoT\nCore Pub\nRESTful\nWrite\nOPC UA\nWrite\nModbus\nTCP\nWrite](.emu-210-50m-19701-1000-10/34a886163c64d49795f583c9072039087fe22cd64cab52b2b65dd27b4721dfec.jpg) Figure 3-30: Create AWS ![Configure Your Target\nAWS IoT Core Pub\nKey AWSIoTCore-8f481e Select Input Tags\nClient ID*\nCLIENT_ID Endpoint*\nxxxx-xxxx.amazonaws.com\nTopic*\nsdk/test/python QoS*\n0\nCertificate*\n+ Choose your certificate\nPrivate Key*\n+ Choose your private key\nRoot CA*\n+ Choose your root CA\n( Back Save](.emu-210-50m-19701-1000-10/db7f255a311389f558f8e4ca7ac96b8255a02e4a08432d14e9e129a99f05ac11.jpg) Figure 3-31: Configure AWS # 4. Run and Deploy: Click Run and wait for the deployment to finish. (See Figure 3-15) # 3.2.2 Python iApp 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. 1. Create and Development: Click iApp Creator from the left sidebar and select Python iApp. 2. Select an iApp template and enter a name for it and then click Create. After creation, the a new iApp will be automatically loaded into the editor where it can be edited as necessary. ![ADLINK\nEGiFlow\nOverview\niApp Creator\nNew\nExport\nImport\nKeyword Search\nName ↑↓\nNo iApp found.\nCreate a new project\nEGiFlow iApp\nPython iApp\nLast Modified Date ↑↓](.emu-210-50m-19701-1000-10/1abbdce070cc97f2bd4d7961a5926d99e95dc7830714fe93a7d712db937fa651.jpg) Figure 3-32: Create Python iApp ![Create iApp\nName: Publish Temperature\nSelect a template: MQTT\nEmpty\nSimpleio Modbus\nREST server\nREST client\nMQTT\n✓ Create](.emu-210-50m-19701-1000-10/a3cb5df29919d8208eb1f31b1333c15e55c74e8c800baa218fadbc11c00fd449.jpg) Figure 3-33: Select a template and enter a name ![1 import simpleio\n2 import numpy as np\n3 import paho.mqtt.client as mqtt\n4 import json\n5\n6\n7\n8 client = mqtt.client()\n9 client.connect('192.168.0.100', 1883, 60)\n10 # set loop interval (if not set, the default value is 5)\n11 interval = 1\n12 # execute when start up\n13\n14 def setup(:\n15 simpleio.ai.set_total_channels(4)\n16 simpleio.ai.set_sample_rate(10000)\n17 simpleio.ai.set_sample_count(10040)\n18\n19\n20 # execute every interval\n21\n22 def loop(:\n23 data={\n24 voltages = simpleio.ai.fetch( )\n25 CHO = voltages(0).tolist( )](.emu-210-50m-19701-1000-10/c8ad218352a9e3d20edc39763ee5f46c139e7f25b387b28aca4dce0694152c55.jpg) Figure 3-34: The new iApp can be edited 3. Run and Deploy: Click Run and wait for the deployment to finish. ![1 import simpleio\n2 import numpy as np\n3 import paho.mqtt.client as mqtt\n4 import json\n5\n6\n7\n8 client = mqtt.Client()\n9 client.connect('192.168.0.100', 1883, 60)\n10 # set loop interval (if not set, the default value is 5)\n11 interval = 1\n12 # execute when start up\n13\n14 def setup():\n15 simpleio.ai.set_total_channels(4)\n16 simpleio.ai.set_sample_rate(10000)\n17 simpleio.ai.set_sample_count(10040)\n18\n19\n20 # execute every interval\n21\n22 def loop():\n23 data=()\n24 voltages = simpleio.ai.fetch()\n25 CHO = voltages(0).tolist()\n36 Save iApp\n37 Save File](.emu-210-50m-19701-1000-10/d4704795f84d8e42cd9983ac6560fc9dabddd1a1d5498810638b8b2b04c141ee.jpg) Figure 3-35: Run a new iApp # 3.2.3 Gateway Configuration & Management # LAN Network Settings The EMU-210 has two Ethernet ports that can be configured to support IPv4 and IPv6 network modes. 1. Open the Network Settings page. ![ADLINK\na LEADING EDGE COMPUTING\nOverview\nApp Creator\nNetwork Settings](.emu-210-50m-19701-1000-10/1f003323fae1cb8e2d92142278af900eb422f653e2d9d6a55a5010eb23cd6ac0.jpg) Figure 3-36: Network Settings 2. Select a LAN Port to set the wired network information. Network Settings ![LAN(eth0) LAN(eth1) WiFi Cellular\nIPv4\nIP assignment: Static\naddress: 192.168.50.2\nnetmask: 255.255.255.0\nIPv6\nIP assignment: Automatic\naddress: fe80::5645:38ff.fe51:9f00\nprefix: 64](.emu-210-50m-19701-1000-10/faddabce8c25e453b5285c6f71928f5d30db838f07b861c2026e0771f6736998.jpg) Figure 3-37: Select LAN Port # 3. Configure the DHCP or static IP settings. Network Settings ![LAN(eth0) LAN(eth1) WiFi Cellular\nIPv4\nIP assignment: Static\naddress: 192.168.50.2\nnetmask: 255.255.255.0\nIPv6\nIP assignment: Automatic\naddress: fe80::5645:38ff:fe51:9f00\nprefix: 64](.emu-210-50m-19701-1000-10/d56c67befc528d53a023320c72641abaa9e58a27901ad663138cb07c8e4800a1.jpg) Figure 3-38: Configure LAN Port ![Network Settings\nLAN(eth0) LAN(eth1) WiFi Cellular\nIPv4\nIPv4 Settings\nInterface Name: eth0\nMethod\nSelect method\nAutomatic(DHCP)\nStatic](.emu-210-50m-19701-1000-10/f0acd06b8c5ae42fd2a6cbcea3c3b8141383b7ee7872817a15e37da53b33c709.jpg) Figure 3-39: Select DHCP or Static ![Network Settings\nIPv4 Settings\nInterface Name: eth0\nMethod\nStatic\nIP address\n192.168.50.3\nNetmask\n255.255.255.0\nGateway\nCancel Save](.emu-210-50m-19701-1000-10/05b683662b33ba733dfe3e205dced3297f6a6849c1996870b8de58589d18ca19.jpg) Figure 3-40: Configure Static IP (IPv4) ![Network Settings\nIPv6 Settings\nInterface Name: eth1\nMethod\nStatic\nAddress\nfe80::5645:38ff:fe51:9f00\nPrefix\n64\nGateway\nNone\nCancel ✓ Save\nIPv4\nIP assignment: Sta\naddress: 192.168.5\nnetmask: 255.255.](.emu-210-50m-19701-1000-10/83b7cb42dcda96d8f5e392ff7e9b28b1114c7941c4da94daf7302e9ab311cda6.jpg) Figure 3-41: Configure Static IP (IPv6) 4. For DNS settings, The DNS server will be used first. ![IPv4 Settings\nInterface Name: eth1\nMethod\nStatic\nIP address\n192.168.50.2\nNetmask\n255.255.255.0\nGateway\nDNS Server\nCancel Save](.emu-210-50m-19701-1000-10/9cd8849f611b0ce08df093241dbf031098784cec471f75831dc53156a7f84d66.jpg) Figure 3-42: DNS Settings (IPv4) # WiFi Network Settings Similar to the Ethernet port, the WiFi network client mode also supports IPv4 and IPv6 network mode settings. 1. Open the Network Settings page. ![ADLINK\nLEADING EDGE COMPUTING\nOverview\niApp Creator\nNetwork Settings](.emu-210-50m-19701-1000-10/babdd1b9e89f56b6c38bd0f1505744de14046597c8f183e0fcfbf87fd7228066.jpg) Figure 3-43: Network Settings # 2. Select to set WiFi network information. ![Network Settings\nLAN(eth0) LAN(eth1) WiFi Cellular\nWi-Fi\nCurrent SSID:\nIPv4 Address:\nIPv6 Address:\nMAC Address: 00:30:64:73:77:52](.emu-210-50m-19701-1000-10/27ab8f44539e83e05da9bea46bf628d9ebbaca75f1b803b8fd95a2e54ad8fe5f.jpg) Figure 3-44: WiFi Network Information # 3. Users need to select the Country Code, SSID name and security of the WLAN to join the network. ![Wifi Settings\nInterface Name: wlan0\nAdvanced..\n6-4\nWifi Advanced Settings\nCountry Code\nTaiwan\nNew Zealand\nAustralia\nUnited States of America\nCanada\nTaiwan\nCancel Connect](.emu-210-50m-19701-1000-10/cb573c3f8a2f3ad9186974fa3bc0853ed4c295fad4a94e8171791ad58f566cfe.jpg) ![Wifi Settings\nInterface Name: wlan0 Advanced...\n6-4\nVincent\n\xe4\xbd\xa0\xe9\x80\xa3\xe4\xb8\x8d\xe5\x88\xb0\xe7\nhsu\nIRONPHONE\nLi House\n292Y149267\nPAN-HOUSE1\nhocc\nPassword\n@......\nCancel Connect](.emu-210-50m-19701-1000-10/2c262894016703bacde809639d530c1782668cbb664642aa594822e200b2c83a.jpg) Figure 3-45: Select Country Code and SSID Name # 4. Click Apply to complete the configuration. # Cellular Network Settings (Optional) 1. Open the Network Settings page, and select to set Cellular network information. ![ADLINK\nLEADING CODE COMPUTING\nOverview\niApp Creator\nNetwork Settings\nTime Settings\nSerial Settings\nNetwork Settings\nLAN1 LAN2 WiFi Cellular\nCellular](.emu-210-50m-19701-1000-10/b4bd34405eabe0169e0117b168098a8186cf5618804bff71767f0a76cf63b1f6.jpg) Figure 3-46: Cellular Network 2. Make sure the system has a 5G/4G/LTE module and SIM card installed, and then enable the cellular network. ![Network Settings\nLAN(eth0) LAN(eth1) WiFi Cellular\nCellular](.emu-210-50m-19701-1000-10/0da8f86cf047bc9b88eac1d5071a9b589422e5f210284ce6dea6b5907a272fd5.jpg) Figure 3-47: Enable Cellular Network # Time Sync Setting, NTP Users can adjust the time synchronization settings. 1. Double click Time Settings to enter the configuration page. ![ADLINK\nLEADING EDGE COMPUTING\nOverview\niApp Creator\nNetwork Settings\nTime Settings](.emu-210-50m-19701-1000-10/43f9df06a67fdd5c611a180bca552f6e6095db6f798e69a28041ce3079914d0a.jpg) Figure 3-48: Select Time Settings 2. The selection of synchronization with the NTP server allows the device to synchronize with a source, and the address of the source can be a domain name or an IP address. Time Settings ![19:05\nSunday, June 04, 2023\nTaipei\nAsia/Taipei (CST, +0800)\nNTP: Active\nNTP Server: Sync Now](.emu-210-50m-19701-1000-10/13b1103ebe2568cb99831d8ee0587ea9bff424745be811bc3a52bb18190fd46a.jpg) Figure 3-49: Configure Time Settings ![Time Settings\n19:05\nSunday, June 04, 2023\nNTP Settings\nTimezone\nAsia/Taipei\nNTP Enabled ✓\nNTP Server\nCancel ✓ Save](.emu-210-50m-19701-1000-10/fbf7674c8bb0039844ae3fa4c70bcb250ed1a2d2efdbd05e9484b23002eecffe.jpg) Figure 3-50: Configure NTP Settings ![Taipei\nAsia/Taipei (CST, +0800)\nNTP: Active\nNTP Server:\nSync Now](.emu-210-50m-19701-1000-10/199d2105ba83856b4f8c1a175f6d4d0442f91a1c969d955afa881cf0a08efa73.jpg) Figure 3-51: Synchronize Time 3. Check serve as a NTP server to enable the device to be a time synchronization source for other devices to synchronize their time with this device. # Serial Settings This page manages serial settings. 1. Double click Serial Settings to enter the configuration page. ![Overview\niApp Creator\nNetwork Settings\nTime Settings\nSerial Settings](.emu-210-50m-19701-1000-10/fef0779ee55b641c87ff24e140d60744f7e63666f891aa670dc95aed0ad2c542.jpg) Figure 3-52: Serial Settings 2. Select the serial port to configure it. Serial Settings ![COM1\nMode: 485\nBaudrate: 9600\nData Bits: 8\nParity: N\nStop Bits: 1\nCOM2\nMode: 485\nBaudrate: 9600\nData Bits: 8\nParity: N\nStop Bits: 1\nCOM1 Serial Settings\nMode*\n485\nBaudrate*\n9600\nData Bits*\n8\nParity*\nNone\nStop Bits*\n1\nCancel Save](.emu-210-50m-19701-1000-10/dd296976a20b396528769e71ef6eec4b83a78ae9da2cd7d23b34dab0dfc35b83.jpg) Figure 3-53: Configure Serial Port # Account Management This page manages user accounts. 1. Double click Account Management to enter the configuration page. ![This image displays a rectangular button or menu item with a white background and a thick red border. Inside, there is a small blue icon of a person on the left, followed by the text 'Account Management' in blue font.](.emu-210-50m-19701-1000-10/342a80193dda8090951925d9010431ed70c5c17166bd6129551f80c420182d0b.jpg) Figure 3-54: Account Management 2. Create user accounts and access privileges. ![Account Management\nCreate User\nGlobal Search\nUser Name Email Operations\nadmin admin@email.com](.emu-210-50m-19701-1000-10/0fc11423bd3931c1688506f466e64e0696ba8dc441fa5eb3c973021380945374.jpg) ![Create User\nUser Name*\nEmail*\nPassword*\nCancel Create](.emu-210-50m-19701-1000-10/c8c0ab1428f95e6bf44b7806929c0a440981f4bf059cfa8ad652c3809b8f4df3.jpg) Figure 3-55: Create User Accounts # System Management This page manages restoring to factory defaults and firmware upgrades. 1. Double click System Management to enter the configuration page. MANAGEMENT ![The image displays a simple, black line-art icon of a person against a white background. It consists of a circle representing a head and a curved, U-shaped line below it depicting the shoulders and upper body, resembling a standard user or profile symbol.](.emu-210-50m-19701-1000-10/c0c733bd520e9ac1844c24762b83ae75bc87388cc52905bbdfccefa97d1e18b8.jpg) Account Management ![The image displays a light purple, eight-toothed gear icon with a central circular hole, set against a white background.](.emu-210-50m-19701-1000-10/7984192e2d28e11bf4ff4e5ec9a6f871909f1bcb89ee46daf64aaaebe1eba8c9.jpg) System Management ![A black and white line-art icon of a document or file featuring a folded top-right corner and three horizontal lines representing text.](.emu-210-50m-19701-1000-10/fbe360fd42e8af61a8f8a33d5afcc6ba4a97e42223404e250dbe220b0b15ca11.jpg) Event Log ![The image displays a simple black line drawing on a white background. It depicts a vertical stack of three identical, horizontally-oriented cylinders or disks, arranged one on top of the other. It resembles a standard icon for a database or storage. There is no text in the image.](.emu-210-50m-19701-1000-10/977c8a4616e6e76568ce932db719ecf45d33156984e601aef7353fda39ed9eac.jpg) External Storage Figure 3-56: System Management 2. Factory default: Restores the EMU-210 to factory default settings. 3. Firmware upgrade: A firmware upgrade file can be uploaded to the EMU-210 through this feature. These files will periodically be provided through the product web page: https://www.adlinktech.com/Products/ Industrial\_IoT\_and\_Cloud\_solutions/IoTGateway/ EMU-210\_Series. System Management Factory default ![The image displays a blurry, red, cursive character, resembling a lowercase letter 'e' or a looped 'C', set against a plain white background. There is no legible text present.](.emu-210-50m-19701-1000-10/1ad39e0115432444bef2e299e9bb4b18ba0cccd15b7ea911f052f1afc0043789.jpg) Reset Firmware upgrade ![The image displays a simple, pixelated icon in a light purple or lavender color against a white background. It depicts an upward-pointing arrow emerging from a rectangular container that is open at the top, a universal symbol for 'upload' or 'share.'](.emu-210-50m-19701-1000-10/89d1b12a833e109bb238d3802c39af17d6a5f67ae1a95ef8b9e10c0e334084ca.jpg) Choose ![The image displays a repeating horizontal pattern of stylized, light purple figures against a white background. Each figure resembles a simple abstract shape, possibly a tree or a person, featuring a rounded, cloud-like top and a straight vertical stem. The figures are arranged in a row, with the sequence partially cut off on the left side. The image is slightly blurry.](.emu-210-50m-19701-1000-10/98aa5b0b00ec224d5dbf7f5c7e52b1bfb48291dd96971e6133a317a8d8b5c4a3.jpg) Figure 3-57: Factory Default and Firmware Upgrade # Event Log This page manages the system log. 1. Double click Event Log to enter the page. 目External Storage Figure 3-58: Event Log 2. The log information includes Date Time, Level, Module and Message. Event Log
Date Time ↑↓LevelModuleMessage
2022-12-22 19:59:59SUCCESSAccount Managementadmin authenticated successfully.
2023-07-14 13:54:53SUCCESSAccount Managementadmin authenticated successfully.
2023-07-14 16:23:28ERRORTime SettingsNTP sync status read failed. Command 'timedatectl timesync-status' returned non-zero exit status 1.
2023-07-19 13:49:52WARNINGAccount Managementadmin authenticated failed.
2023-07-19 13:50:00SUCCESSAccount Managementadmin authenticated successfully.
2023-07-19 14:11:21ERRORTime SettingsNTP sync status read failed. Command 'timedatectl timesync-status' returned non-zero exit status 1.
2023-07-21 17:46:01WARNINGAccount Managementadmin authenticated failed.
2023-07-21 17:46:09SUCCESSAccount Managementadmin authenticated successfully.
2023-07-21 18:20:41SUCCESSAccount Managementadmin authenticated successfully.
2023-07-21 18:35:15ERRORTime SettingsNTP sync status read failed. Command 'timedatectl timesync-status' returned non-zero exit status 1.
Figure 3-59: Event Log Information # External Storage This page manages external storage. 1. Double click External Storage to enter the page. ![The image displays a rectangular UI element, likely a button or menu item, enclosed within a red border. Inside, on a white background, there is a blue icon resembling a stack of discs (a database symbol) to the left of the blue text 'External Storage'.](.emu-210-50m-19701-1000-10/933f459022ad3407bfeb2f0ec76e1013789ec846ddfa3569dd35dc6218c10edb.jpg) Figure 3-60: External Storage 2. Manage external storage. External Storage sdcard\_1 ![New\nDelete\nUpload File\nDownload File](.emu-210-50m-19701-1000-10/d5c30cdad67a730d5ba723a0bc7a01b28c536ac9f9232ba440d03ba2bd8e2d1d.jpg) Figure 3-61: Manage External Storage # System Information This page manages system information. 1. Double click System Information to enter the page. ![i System Information](.emu-210-50m-19701-1000-10/319651b481ccde37791543f22e43914e39fa34493de736d058b5fa4b7e953670.jpg) Figure 3-62: System Information 2. System information includes device information and software version. System Information Device Information Device Type: EMU200 Host Name: EMU Device UID: 59acc135-1336-515a-8619-80a697ff07ed Serial Number: Software Versions Web Console Version: 23.07.0713.0 Figure 3-63: Device Information and Software Version This page intentionally left blank. # Appendix A Debian Linux OS Debian Linux is used as the EMU-210 operating system for system integrators to develop customization applications.This appendix includes information on the following items.  Hardware Setup  Connecting and Logging in via SSH  LED Function  Serial Port Configuration  Network Settings  5G/4G/LTE Module Configuration  WiFi Configuration and Connection # A.1 Hardware Setup 1. LAN1 (DHCP) connects to the network. LAN2 (Static IP) connects to the EMU-210 via SSH. 2. Connect the EMU-210 to a 12-24V DC power supply. 3. The EMU-210 will power on automatically. # A.2 Connecting and Logging in via SSH 1. Set the network domain of the host computer that will be connected to the EMU-210 to 192.168.50.xx. 2. Open Putty on the host computer and enter the IP address of the EMU-210: 192.168.50.2. ![PuTTY Configuration\nCategory:\nSession\nLogging\nTerminal\nKeyboard\nBell\nFeatures\nWindow\nAppearance\nBehaviour\nTranslation\nSelection\nColours\nConnection\nData\nProxy\nTelnet\nRlogin\nSSH\nSerial\nBasic options for your PuTTY session\nSpecify the destination you want to connect to\nHost Name (or IP address)\n192.168.50.2\nPort\n22\nConnection type:\nRaw Telnet Rlogin SSH Serial\nLoad, save or delete a stored session\nSaved Sessions\nDefault Settings\nLoad\nSave\nDelete\nClose window on exit:\nAlways Never Only on clean exit\nOpen\nCancel\nAbout Help](.emu-210-50m-19701-1000-10/fb62f46475cfed38092b4b91ea4da7e92b354c259ea9733ca5eb906c8d400b01.jpg) 3. Log in with the username (root) and password (adlink). 4. You have successfully connected to the EMU-210. ![192.168.50.2 - PuTTY\nlogin as: root\nroot@192.168.50.2's password:\nLinux EMU-210 5.15.52-emu-210.1v1.0.0+b11bfb49c45e #1 SMP PREEMPT Wed Mar 20 11:01:01 CST 2024 aarch64\nThe programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright.\nDebian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law.\nLast login: Thu Mar 21 06:46:48 2024 from 192.168.50.100\nroot@EMU-210:~#](.emu-210-50m-19701-1000-10/50456314b943c287bc0615597b2d9b6e87be53e25d52a89db90fa5b99bee3647.jpg) # A.3 LED Function  PWR LED: The LED will light up when powered. WLAN LED: When a Wi-Fi module is installed in the slot, the LED will light up after the system loads. If the hardware does not have a Wi-Fi module installed, the LED will not light up. WWAN LED: When a 5G LTE module is installed in the slot, the LED will light up after the system loads. If the hardware does not have a 5G LTE module installed, the LED will not light up.  PGM LED: The LED will light up when flashing the BSP to the eMMC via an SD card. # A.4 Serial Port Configuration Use the following commands to query the current COM1/COM2 serial settings. \$ cat /sys/class/gpio\_switch/com1Mode \$ cat /sys/class/gpio\_switch/com2Mode Use the following commands to set the COM1/COM2 serial settings to RS-232/422/485. \$ echo RS232 > /sys/class/gpio\_switch/com1Mode \$ echo RS232 > /sys/class/gpio\_switch/com2Mode \$ echo RS422 > /sys/class/gpio\_switch/com1Mode \$ echo RS422 > /sys/class/gpio\_switch/com2Mode \$ echo RS485 > /sys/class/gpio\_switch/com1Mode \$ echo RS485 > /sys/class/gpio\_switch/com2Mode Use the following commands to set the COM1/COM2 serial paths. COM1: /dev/ttymxc2 COM2: /dev/ttymxc3 # A.5 Network Settings Use the following command to Modify LAN1 (eth0). ```txt $ vi /etc/systemd/network/10-eth.network.conf ``` Use the following command to Modify LAN2 (eth1). ```txt $ vi /etc/systemd/network/11-eth1.network.conf ``` # A.6 5G/4G/LTE Module Configuration 1. Enter the following command to check the interface status. \$ nmcli d ```batch root@EMU-210:~# nmcli d DEVICE TYPE STATE CONNECTION wlan0 wifi connected ADLINKTECH cdc-wdm0 gsm disconnected -- p2p-dev-wlan0 wifi-p2p disconnected -- dummy0 dummy unmanaged -- eth0 ethernet unmanaged -- eth1 ethernet unmanaged -- lo loopback unmanaged -- ``` 2. Add a connection. \$ nmcli c add type gsm ifname cdc-wdm0 con-name cellular ```txt root@EMU-210:~# nmcli c add type gsm ifname cdc-wdm0 con-name cellular Warning: There are 3 other connections with the name 'cellular'. Reference the connection by its uuid 'b0456del-8858-4a8a-ae0e-7fdfd7345f86' Connection 'cellular' (b0456del-8858-4a8a-ae0e-7fdfd7345f86) successfully added. ``` 3. Check the connection status. \$ nmcli c show cellular 4. Activate the connection. \$ nmcli c up cellular ```txt root@EMU-210:~# nmcli c up cellular Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/6) root@EMU-210:~# ``` 5. Check if the network interface (wwan0) is present. \$ ifconfig ```txt wwan0: flags=4291<UP,BROADCAST,RUNNING,NOARP,MULTICAST> mtu 1500 inet 10.131.44.140 netmask 255.255.255.248 broadcast 10.131.44.143 inet6 2001:b400:e3db:7b17:909b:f846:edf2:4278 prefixlen 64 scopeid 0x0<global> ether da:ee:52:5e:92:7e txqueuelen 1000 (Ethernet) RX packets 294 bytes 29244 (28.5 KiB) RX errors 46 dropped 0 overruns 0 frame 0 TX packets 494 bytes 54865 (53.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ``` 6. Perform network connectivity test (ping Google DNS). \$ ping -I wwan0 8.8.8.8 ```txt root@EMU-210:~# ping -I wwan0 8.8.8.8 PING 8.8.8.8 (8.8.8.8) from 10.131.44.140 wwan0: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=55 time=1089 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=55 time=144 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=55 time=14.6 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=55 time=22.3 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=55 time=25.3 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=55 time=13.2 ms 64 bytes from 8.8.8.8: icmp_seq=7 ttl=55 time=27.4 ms 64 bytes from 8.8.8.8: icmp_seq=8 ttl=55 time=14.2 ms 64 bytes from 8.8.8.8: icmp_seq=9 ttl=55 time=32.2 ms 64 bytes from 8.8.8.8: icmp_seq=10 ttl=55 time=21.4 ms 64 bytes from 8.8.8.8: icmp_seq=11 ttl=55 time=31.8 ms 64 bytes from 8.8.8.8: icmp_seq=12 ttl=55 time=13.6 ms 64 bytes from 8.8.8.8: icmp_seq=13 ttl=55 time=25.9 ms 64 bytes from 8.8.8.8: icmp_seq=14 ttl=55 time=24.6 ms 64 bytes from 8.8.8.8: icmp_seq=15 ttl=55 time=26.3 ms 64 bytes from 8.8.8.8: icmp_seq=16 ttl=55 time=24.3 ms 64 bytes from 8.8.8.8: icmp_seq=17 ttl=55 time=30.9 ms 64 bytes from 8.8.8.8: icmp_seq=18 ttl=55 time=16.8 ms ``` 7. Close the connection. \$ nmcli c down cellular ```txt root@EMU-210:~# nmcli c down cellular Connection 'cellular' successfully deactivated (D-Bus active path: /org/freedesktop, NetworkManager/ActiveConnection/7) root@EMU-210:~# ``` # A.7 Wi-Fi Configuration and Connection 1. Enter the following to connect to the Wi-Fi AP. ```txt $ nmcli dev wifi connect "Your AP SSID" password "Your Password" ``` ```txt root@EMU-210:~# nmcli dev wifi connect ADLINKTECH password adlink6166 Device 'wlan0' successfully activated with '9d7f20ab-bdf3-4c2d-84e7-41ff89eeee11' root@EMU-210:~# ``` 2. Check if the Wi-Fi network interface (wlan0) is present. ```txt wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.30.202.182 netmask 255.255.252.0 broadcast 172.30.203.255 inet6 fe80::413c:2383:2f98:7fef prefixlen 64 scopeid 0x20<link> ether 2c:33:58:f3:7e:b5 txqueuelen 1000 (Ethernet) RX packets 1183 bytes 75726 (73.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1151 bytes 93612 (91.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ``` 3. Enter the following command to execute a Wi-Fi connectivity function test (ping Google DNS). \$ ping -I wlan0 8.8.8.8 ```txt 192.168.50.2 - PuTTY 64 bytes from 8.8.8.8: icmp_seq=463 ttl=57 time=89.7 ms 64 bytes from 8.8.8.8: icmp_seq=464 ttl=57 time=112 ms 64 bytes from 8.8.8.8: icmp_seq=465 ttl=57 time=135 ms 64 bytes from 8.8.8.8: icmp_seq=481 ttl=57 time=166 ms 64 bytes from 8.8.8.8: icmp_seq=482 ttl=57 time=86.0 ms 64 bytes from 8.8.8.8: icmp_seq=483 ttl=57 time=110 ms 64 bytes from 8.8.8.8: icmp_seq=484 ttl=57 time=132 ms 64 bytes from 8.8.8.8: icmp_seq=504 ttl=57 time=270 ms 64 bytes from 8.8.8.8: icmp_seq=505 ttl=57 time=83.3 ms 64 bytes from 8.8.8.8: icmp_seq=506 ttl=57 time=213 ms 64 bytes from 8.8.8.8: icmp_seq=507 ttl=57 time=132 ms 64 bytes from 8.8.8.8: icmp_seq=509 ttl=57 time=158 ms 64 bytes from 8.8.8.8: icmp_seq=510 ttl=57 time=78.7 ms 64 bytes from 8.8.8.8: icmp_seq=511 ttl=57 time=104 ms 64 bytes from 8.8.8.8: icmp_seq=512 ttl=57 time=48.2 ms 64 bytes from 8.8.8.8: icmp_seq=520 ttl=57 time=156 ms 64 bytes from 8.8.8.8: icmp_seq=522 ttl=57 time=84.3 ms 64 bytes from 8.8.8.8: icmp_seq=523 ttl=57 time=106 ms 64 bytes from 8.8.8.8: icmp_seq=524 ttl=57 time=132 ms 64 bytes from 8.8.8.8: icmp_seq=531 ttl=57 time=970 ms 64 bytes from 8.8.8.8: icmp_seq=532 ttl=57 time=175 ms 64 bytes from 8.8.8.8: icmp_seq=533 ttl=57 time=97.5 ms 64 bytes from 8.8.8.8: icmp_seq=534 ttl=57 time=117 ms ``` This page intentionally left blank. # Appendix B Accessory Installation # B.1 Wi-Fi Module 1. Remove 8 screws from chassis. ![Black electronic device labeled 'ADLINK' on a wooden surface, with red circles highlighting mounting points (no readable text beyond branding)](.emu-210-50m-19701-1000-10/321fcec14c37378e7ebabd03acc3c11acc681c6d21a04bba07fea36b7720cbd6.jpg) 2. Remove the top cover ![Close-up of a hand holding a black electronic device with visible circuit board and screw holes (no text or symbols)](.emu-210-50m-19701-1000-10/488b9c84d2f2c5c1a706c86dd420ec7055dc7096dcbe79dc65abbc8dfae43577.jpg) 3. Remove the appropriate antenna covers based on the Wi-Fi module used. There are two positions to choose from, depending on whether you will upgrade to a 4G module or a 5G module. If you will not upgrade the system, choose the first option. # Antenna covers for 4G modules Sierra EM7421 and Quectel EM05-G ![Interior view of an electronic device casing with visible circuit boards and components, no text or symbols present.](.emu-210-50m-19701-1000-10/b63ce94044acd160f0f0ed7cd9ca8a97669132154a17ab730ccaf522cb3d8ce6.jpg) # Antenna covers for 5G module: TELIT MV32-W-AD ![Interior view of an electronic device casing showing internal components and circuit board (no visible text or symbols)](.emu-210-50m-19701-1000-10/8f886fea4b255b3f2e4bfaafdeab8574631bb4e2ffb7eb0bb989c2ef6f193651.jpg) 4. Install two RF Cables. Thread the SMA connector through the antenna hole. ![Close-up of a hand inserting a gold connector into a green printed circuit board (no visible text or symbols)](.emu-210-50m-19701-1000-10/8497f147be926799b75fd1112c3593bc15bd7ae5a09fdbf59a8e19fc194c90bd.jpg) ![Close-up of a hand holding a small electronic component with visible pins and connectors (no readable text or symbols)](.emu-210-50m-19701-1000-10/3d6fe684e99e74522c72c6e3136cbd9e4ce08493b0294e65a78d00888d768c0e.jpg) 5. Insert the washer and install the hex nut (torque value = 6-8kgf.cm). ![Close-up of a brass-colored mechanical connector with threaded body and mounting flange (no visible text or symbols)](.emu-210-50m-19701-1000-10/bf823614f13ee5303f44b9c9489e0527c4fc900c52b8074a74e8d9b498088fed.jpg) ![Close-up of a brass-colored RF connector with threaded body and hexagonal base (no text or symbols visible)](.emu-210-50m-19701-1000-10/9a7debd9c0c9b33f77e341adc66824dbbb71c9488188c1af339cb2c6934152c8.jpg) 6. Install the Wi-Fi module and secure with a hex standoff (torque value = 4-5kgf.cm). ![Close-up of an electronic circuit board with visible components and a red annotation pointing to a component (no readable text or symbols)](.emu-210-50m-19701-1000-10/354ee473aad380ca82f6a33a13c89f34e152b8a656374156c156935f8e708392.jpg) 7. Attach the RF cable connector to the module. ![Close-up of a green printed circuit board with attached components and red annotations pointing to features (no readable text or symbols)](.emu-210-50m-19701-1000-10/ae5e693f9237ded4bce402b59236a00b8e840a7834de4b0046fab5b8ee3a83eb.jpg) 8. RF Cable routing. There are two positions to choose from. Cable routing for 4G modules Sierra EM7421 and Quectel EM05-G ![ANT 4\nANT 5\nANT 6\nANT 3\nANT 1](.emu-210-50m-19701-1000-10/b12dd5fc3b21adc8cc959b01b1790977dfe681215c064539bacee2df8fe8947f.jpg) Cable routing for 5G module TELIT MV32-W-AD ![ANT 4\nANT 5\nANT 6\nANT 3\nANT 2\nANT 1](.emu-210-50m-19701-1000-10/a1aa2760ef51eb77e67633f353e875b4a3ac261907a4c13217b6d12e7d76ab42.jpg) 9. Install the thermal conductive aluminum block and tighten the M2.5 screw and two M3 screws (torque value = 3.5-4kgf.cm). ![Close-up of an electronic circuit board with three red circular annotations pointing to a component (no readable text or symbols)](.emu-210-50m-19701-1000-10/5a0b0d051f02f229412ce0328440868a157af576bb5bbe9ffdbca5aa96bd3e97.jpg) The thermal conductive aluminum block has release paper on both sides, which needs to be removed before installation. ![Two views of a metal bracket component with blue adhesive, being handled by fingers (no text or symbols visible)](.emu-210-50m-19701-1000-10/dd1b4d6558a47734a6223c5b5e93e16118a9ab394fb26426e371e3d4acdfd4fb.jpg) 10.Replace the top cover and original screws. # B.2 4G Module 1. Remove 8 screws from chassis. ![Black electronic device labeled 'ADLINK' on a wooden surface, with red circles highlighting mounting points (no readable text beyond branding)](.emu-210-50m-19701-1000-10/275d29d8dad9f36e11a8c6e08b01b020f7c74dcb43bc6ca48322b9eed7c6ddd5.jpg) 2. Remove the top cover ![Close-up of a hand holding an open black electronic device with visible circuit board and connectors (no text or symbols)](.emu-210-50m-19701-1000-10/7b12ad9cba4f5e681460b19ad191894e630751231fac66240a199adf738b7f61.jpg) 3. Remove the appropriate antenna covers based on the 4G module used. There are two positions to choose from, depending on the 4G module used. Antenna covers for 4G module Sierra EM7421 ![Interior view of an electronic device casing with visible circuit boards, capacitors, and components (no text or symbols)](.emu-210-50m-19701-1000-10/01fca12b9ab243594d8cadd86e0a805a3af4dcac254fd825bc4635960c103344.jpg) Antenna covers for 4G module Quectel EM05-G ![Interior view of an electronic device casing showing internal components and circuit boards (no visible text or symbols)](.emu-210-50m-19701-1000-10/c04c579c32e809579a252ea4120b81802ba84ce686bd16317e4b04e48d5648bc.jpg) 4. Install the RF Cables. Thread the SMA connector through the antenna hole. ![Close-up of a hand inserting a gold-colored connector into a green electronic device (no visible text or symbols)](.emu-210-50m-19701-1000-10/04ade1a2641acdbc20ae4c20f06367ed30d8cec495d7a65b5db7e99d4e4c6f72.jpg) ![Close-up of a hand holding a small electronic component with visible pins and connectors (no readable text or symbols)](.emu-210-50m-19701-1000-10/cb0e41e127a78435ccd419b99a4cab893b55135c9b8fecc1d8686fb4c74cb046.jpg) 5. Insert the washer and install the hex nut (torque value = 6-8kgf.cm). ![Close-up of a metallic threaded connector with gold casing (no text or symbols visible)](.emu-210-50m-19701-1000-10/d66528c6f19d7ba06ad291db48c31e1182f4680df66557c5575bd240de688de8.jpg) ![Close-up of a brass-colored RF connector with threaded metal body (no text or symbols visible)](.emu-210-50m-19701-1000-10/12a89b0b9eb907470c423ea83359e2ee0ef2739744158c3657343adcc068d74f.jpg) 6. Install the 4G module and secure with a hex standoff (torque value = 4-5kgf.cm). ![2CPO2\nB\n7-212\nNEI 30555146/PTA\nGPT 30555146/PTA\nGPT 30555146/PTA\nGPT 30555146/PTA\nGPT 30555146/PTA\nGPT 30555146/PTA\nGPT 30555146/PTA\nGPT 30555146/\nGPT 30555146/\nGPT 30555146/\nGPT 30555146/\nGPT 30555146/\nGPT 30555146/\nGPT 30555146/\nGPT 30555146/\nGPT 30555146/\nGPT 87334.002\nGPT 87334.002\nGPT 87334.002\nGPT 87334.002\nGPT 87334.002\nGPT 87334.002\nGPT 87334.002\nGPT 87334.002\nGPT 87334.\nGPT 87334.\nGPT 87334.\nGPT 87334.\nGPT 87334.\nGPT 87334.\nGPT 87334.\nGPT 87334.\nGPT 87334.\nGPT 87334.\nGPT 87334.\nGPT 87334.\nH\nS\nO\nP\nR\nT\nN\nO\nP\nR\nT\nN\nO\nP\nR\nT\nN\nO\nP\nR\nT\nN\nO\nP\nR\nT\nN\nO\nP\nR\nT\nN\nO\nP\nR\nT\nN\nO\nP\nR\nT\nN\nO\nP\nR\nT\nN\nO\nP\nR\nT\nN\nO\nP\nR\nT\nO\nP\nR\nT\nN\nO\nP\nR\nT\nN\nO\nP\nR\nT\nN\nO\nP\nR\nT\nN\nO\nP\nR\nT\nN\nO\nP\nR\nT\nN\nO\nP\nR\nT\nN\nO\nP\nR\nT\nN\nO\nP\nR\nT\nN\nO\nP\nR\nT\nNo](.emu-210-50m-19701-1000-10/f71e3aea83e630f15b572ff69f02a6f5db1b6f8af0521580db59b47ae733cacf.jpg) ![The image shows a silver metallic bolt with a hexagonal head and a threaded shaft lying diagonally on a light-colored wooden surface with a visible grain pattern. A small black rectangular block is attached to the top flat face of the hexagonal head. A hexagonal socket hole is visible on the front face of the head. A small red arrow points toward the left side of the bolt head.](.emu-210-50m-19701-1000-10/0f709a51867b82a00f2b679b5453dfd89368416249132439ef0a0f581a45c56e.jpg) 7. Attach the RF cable connectors to the module. ![Close-up of an electronic circuit board with a component highlighted in red, showing wiring and connectors (no readable text or symbols)](.emu-210-50m-19701-1000-10/caa432ebdaccde9ab17e0fa02ce7df144c3d2ac6e358947738214f688783dabf.jpg) 8. RF Cable routing. There are two positions to choose from. Cable routing for 4G module Sierra EM7421 ![ANT 4\nANT 5\nANT 6\nANT 3\nANT 1](.emu-210-50m-19701-1000-10/7aa8d75f52c65cf4eca619af887f62876a99673e383be8db86028672983e3c9a.jpg) Cable routing for 4G module Quectel EM05-G ![ANT 4\nANT 6\nANT 3\nANT 1](.emu-210-50m-19701-1000-10/13592881cbc2489a27c0351202813d7c0a795f2e0e2871c9ac392315d921fb95.jpg) 9. Install the thermal conductive aluminum block and tighten the M2.5 screw and two M3 screws (torque value = 3.5-4kgf.cm). ![Close-up of a mechanical component with red annotations highlighting features, including screws and metal parts (no text or symbols present)](.emu-210-50m-19701-1000-10/f492e4e944a32ca33b220483973e18322acdb8b7bef55087f1e58c0d9d822bc7.jpg) The thermal conductive aluminum block has release paper on both sides, which needs to be removed before installation. ![Two hand-drawn photos showing a blue and silver metal component being handled, with a magnified inset showing a color swatch (no text or symbols visible)](.emu-210-50m-19701-1000-10/16ffa4aabb3922ae3e61f921ae636f8b7a5549e427025f107af4c535c68ef0b8.jpg) 10.Replace the top cover and original screws. # B.3 5G Module 1. Remove 8 screws from chassis. ![Black electronic box with red circular annotations marking points of interest on the surface (no readable text or symbols)](.emu-210-50m-19701-1000-10/84e0e02ef5b088ee7bb6c3ec25921f8eb0649ca79e5526a958d4cefc310d448e.jpg) # 2. Remove the top cover ![Close-up of a hand holding an open black electronic device with visible circuit board and components (no text or symbols)](.emu-210-50m-19701-1000-10/3fae88338dfc174482f6e45e946d6a0030bdc2f1c8ab7d4572c975d0a69d1f55.jpg) # 3. Remove four antenna covers. ![Interior view of an electronic device casing showing internal components and circuit board (no text or symbols visible)](.emu-210-50m-19701-1000-10/38d46f2f21532f404f44661c66d93b9dddb22592cf651408de71c17e6a7ca6f0.jpg) 4. Install the RF Cables. Thread the SMA connector through the antenna hole. ![Close-up of a green electronic circuit board with attached metallic connectors and screws, being handled by a hand (no visible text or symbols)](.emu-210-50m-19701-1000-10/e32e52a2ffd9b3148848aa2d16f71ef16c3e52633b2c1a4f021c6dfcce402acf.jpg) ![Close-up of a hand inserting a small electronic component into a black case (no visible text or symbols)](.emu-210-50m-19701-1000-10/45bf189037016265b81ee6dafa15291c6d36bad665e4326a46af8825ab0f4925.jpg) 5. Insert the washer and install the hex nut (torque value = 6-8kgf.cm). ![Close-up of a metallic threaded connector with flange and mounting holes (no text or symbols visible)](.emu-210-50m-19701-1000-10/25ad97ffccd12fc1dc212517f3bcde5c9179315807c3d9bfb708dc1822a589cb.jpg) ![Close-up of a metallic threaded connector with hexagonal base (no text or symbols visible)](.emu-210-50m-19701-1000-10/e60d5dc02cc7d85ce9211e4ee20ac9b69405772c7cf6c32c3a2bc7e339ff08ec.jpg) 6. Install the 5G module and secure with a hex standoff (torque value = 4-5kgf.cm). ![45552870012369 - RA\nCIC 101 QIPMS30 M\nM23\nCINTECHON\n390-101\nModel 1\nA27-27-0](.emu-210-50m-19701-1000-10/b16e318a2c77072e9d4c7badd6a7db3c3b1ab55ef745be08da8ba5e1453e73c3.jpg) 7. Attach the RF cable connectors to the module. ![SCB02\n1798358 MTR 0.49 P H\n952870012363\nNOV TO: 5618\n100 GB 01WAVE 2-W-4\nMAX: 10 WAVE 2 W-4\n100 GB 01WAVE 2-W-4\n100 GB 01WAVE 2-W-4\n100 GB 01WAVE 2-W-4\n100 GB 01WAVE 2-W-4\n100 GB 01WAVE 2-W-4\n100 GB 01WAVE 2-W-4\n100 GB 01WAVE 2-W-4\n100 GB 00WAVE 2-W-4\n100 GB 00WAVE 2-W-4\n100 GB 00WAVE 2-W-4\n100 GB 00WAVE 2-W-4\n100 GB 00WAVE 2-W-4\n100 GB 00WAVE 2-W-4\n100 GB 00WAVE 2-W-4\n155 MB 01WAVE 2-W-4\n155 MB 01WAVE 2-W-4\n155 MB 01WAVE 2-W-4\n155 MB 01WAVE 2-W-4\n155 MB 01WAVE 2-W-4\n155 MB 01WAVE 2-W-4\n155 MB 01WAVE 2-W-4\n100 GB 01WAVE 2-W-4\n100 GB 01WAVE 2-W-4\n100 GB 01WAVE 2-W-4\n100 GB 01WAVE 2-W-4\n155 MB 01WAVE 2-W-4\n155 MB 01WAVE 2-W-4\n155 MB 01WAVE 2-W-4\n155 MB 01WAVE 2-W-4\n155 MB 01WAVE 2-W-4\n155 MB 01WAVE 2-W-3\n155 MB 01WAVE 2-W-3\n155 MB 01WAVE 2-W-3\n155 MB 01WAVE 2-W-3\n155 MB 01WAVE 2-W-3\n155 MB 01WAVE 2-W-3\n155 MB 01WAVE 2-W-3\n155 MB 01WAVESZ W-4\n155 MB 01WAVESZ W-4\n155 MB 01WAVESZ W-4\n155 MB 01WAVESZ W-4\n155 MB 01WAVESZ W-4\n155 MB 01WAVESZ W-4\n155 MB 01WAVESZ W-4\n155 MB 01WAWESZ W-4\n155 MB 01WAVESZ W-4\n155 MB 01WAVESZ W-4](.emu-210-50m-19701-1000-10/6b9c717343129d21bc56bbbe2922723b093f0d89dce26b55af1e99a00c833eed.jpg) 8. RF Cable routing. ![ANT 4\nANT 5\nANT 6\nANT 3\nANT 2\nANT 1](.emu-210-50m-19701-1000-10/09c9713f7c2e004d887eb71bf5b034bea28d7521696de061ca27a8ee0c5a14d2.jpg) 9. Install the thermal conductive aluminum block and tighten the M2.5 screw and two M3 screws (torque value = 3.5-4kgf.cm). ![Close-up of a mechanical component with red annotations highlighting features, showing screws and metal parts (no text or symbols present)](.emu-210-50m-19701-1000-10/1030339769b59a2afb8a9cf7b4d431748e34b18178a2679215941c9abf427d12.jpg) The thermal conductive aluminum block has release paper on both sides, which needs to be removed before installation. ![Two views of a metallic electronic component with blue and purple bands, being handled by fingers (no text or symbols visible)](.emu-210-50m-19701-1000-10/6f28b176ec2116f8a33c9351f1ef3bf9feb9e0c8907b495fdb099efc76255df6.jpg) 10.Replace the top cover and original screws. # 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.  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 $5 \%$ to $5 0 \%$ .  It is recommended that the device be installed in Information Technology Rooms that are in accordance with Article 645 of the National Electrical Code and NFPA 75.  When installing/mounting or uninstalling/removing device:  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.  This apparatus is powered by adapter or DC source. Please ensure the adapter or DC source has a grounded connection.  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 shows a yellow triangular warning sign containing a large black exclamation point in the center. Below the triangle, the word 'CAUTION:' is printed in black capital letters.](.emu-210-50m-19701-1000-10/b1ba9a1b333d56a47d9a79b59c5785e720e23414e741a2ed2e8380c8fbdd5d65.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. Terminal block wires should be fixed tightly by an authorized technician with the recommendation wire range: 16-24, str, sol, wire type: copper.  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. ![Yellow triangular warning sign with black smoke symbol indicating hot weather](.emu-210-50m-19701-1000-10/957b7547c33d9b9c236155e4e401635ce4bb7411270e72154d54349d1bfdd100.jpg) # BURN HAZARD Touching this surface could result in bodily injury. To reduce risk, allow the surface to cool before touching. # RISQUE DE BRÛLURES Ne touchez pas cette surface, cela pourrait entraîner des blessures. Pour éviter tout danger, laissez la surface refroidir avant de la toucher. # Consignes de Sécurité Importantes Pour la sécurité de l'utilisateur, veuillez lire et suivre toutes les instructions, avertissements, mises en garde et notes marqués dans ce manuel et sur l'appareil associé avant de manipuler/ d'utiliser l'appareil, afin d'éviter toute blessure ou tout dommage.  Lisez attentivement ces consignes de sécurité  Conservez le manuel de l'utilisateur pour pouvoir le consulter ultérieurement Lisez la section Spécifications de ce manuel pour des informations détaillées sur l'environnement d'exploitation recommandé  L'appareil peut être utilisé à une température ambiante de 5ºC à $5 0 ^ { \circ } C .$ .  Il est recommandé d'installer l'appareil dans Information Salles technologiques conformes à l'article 645 du Code national de l'électricité et NFPA 75. 1 Lorsque l'installation/le montage ou la désinstallation/le retrait du périphérique est requis: Lorsque l'installation/le montage ou la désinstallation/le retrait du périphérique est necessaire:  Mettez l'appareil hors tension et débranchez tous les cordons/câbles d'alimentation  Réinstallez tous les couvercles de châssis avant de rétablir l'alimentation  Pour éviter les chocs électriques et/ou d’endommager l’appareil:  Tenez l'appareil à l'écart de toute source d'eau ou de liquide  Tenez l'appareil à l'écart d'une forte chaleur ou d'une humidité élevée  Maintenez l'appareil correctement ventilé (n'obstruer ou ne couvrez pas les ouvertures de ventilation)  Utilisez toujours les réglages de tension et de source d'alimentation recommandés  Installez et utilisez toujours l'appareil près d'une prise de courant facilement accessible  Fixez le cordon d'alimentation (ne placez aucun objet sur le cordon d'alimentation)  Installez/fixez et utilisez l'appareil uniquement sur des surfaces stables et/ou sur les fixations recommandées  Cet appareil est alimenté par un adaptateur ou une source DC. Veuillez vous assurer que l'adaptateur ou la source DC est relié à la terre s'il dispose d'une mise à la terre de protection. Si l'appareil ne doit pas être utilisé pendant de longues périodes, éteignez-le et débranchez-le de sa source d'alimentation N'essayez jamais de réparer l'appareil, qui ne doit être réparé que par un personnel technique qualifié à l'aide d'outils appropriés  Une batterie de type Lithium peut être fournie pour une alimentation de secours ininterrompue ou d'urgence. ![A yellow triangular warning sign with a black border containing a black exclamation mark. Below the triangle, the text 'CAUTION:' is printed in black capital letters on a white background.](.emu-210-50m-19701-1000-10/029d8f2121dbbdf71833b560c48aace64749da4a89500ecc1a668019c1923d06.jpg) 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.  L'appareil doit être entretenu par des techniciens agrees lorsque:  Le cordon d’alimentation ou la prise est endommagé(e)  Un liquide a pénétré à l'intérieur de l'appareil  L'appareil a été exposé à une forte humidité et/ou de la buée  L'appareil ne fonctionne pas ou ne fonctionne pas selon le manuel de l'utilisateur  L'appareil est tombé et/ou a été endommagé et/ou présente des signes évidents de dommage Débranchez le cordon d'alimentation avant de desserrer les vis à oreilles et serrez toujours les vis à oreilles avec un tournevis avant de mettre le système en marche  Le fil du bornier doit être fixé fermement par un technicien agréé et recommandé pour la gamme de fils : 16-24, str, sol, type de fil: Cu  Il est recommandé d'installer l'appareil uniquement dans une salle de serveurs ou une salle informatique où l'accès est:  Réservé au personnel de service qualifié ou aux utilisateurs familiarisés avec les restrictions appliquées à l'emplacement, aux raisons de ces restrictions et toutes les précautions requises  Uniquement autorisé par l'utilisation d'un outil, d'une serrure et d'une clé, ou d'un autre moyen de sécurité, et contrôlé par l'autorité responsable de l'emplacement ![Warning sign with yellow triangle and black smoke symbol indicating hot weather](.emu-210-50m-19701-1000-10/c5544711c192d00ce0cec8d77c4cf2785141d4ab2be72c61849876370504d959.jpg) # RISQUE DE BRÛLURES Ne touchez pas cette surface, cela pourrait entraîner des blessures. Pour éviter tout danger, laissez la surface refroidir avant de la toucher. This page intentionally left blank. # Getting Service Ask an Expert: https://www.adlinktech.com/en/Askanexpert # 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. [🔗 Link to the original document](.emu-210-50m-19701-1000-10/emu-210-50m-19701-1000-10.pdf)