理论 · 选型与比对Theory · Selection

推荐的解决方案Recommended Solutions

先把原理与取舍讲清楚Principles and trade-offs first

这一栏不堆产品,只做选型与原理的横向比对。本期把 EtherCAT 主站的实现路线放在一起看——系统型、软件型、硬件型到底差在哪,帮你早期选对方向;确定路线后,再交给我们的模块去落地。No product pitches here — just a side-by-side of EtherCAT master implementations: system, software and hardware masters, so you pick the right direction early; once set, hand it to our modules to build.

Topic 02 · EtherCAT 主站EtherCAT Master

EtherCAT 主站方案横向比对EtherCAT Master: a side-by-side

系统型(TwinCAT / CODESYS)、软件型(SOEM / IgH)、硬件型(讯成 ECM-XF)——把实现形态、实时性、开发门槛与成本一张表说清。System (TwinCAT / CODESYS), software (SOEM / IgH) and hardware (NextW ECM-XF) masters — implementation shape, real-time, dev threshold and cost in one table.

先说清楚:什么是 EtherCAT 主站?First, what is an EtherCAT master? EtherCAT 是实时工业以太网。主站负责"编排"整个网络:以固定周期发出一帧数据,从站芯片在帧"飞过"自己时就地读出/写入属于自己的那一段(飞读飞写, processing on the fly),再用分布式时钟(DC)让所有从站微秒级同步。主站要干的事包括:组帧、拓扑扫描、PDO/SDO 映射、DC 同步、状态机管理、故障诊断。主站"怎么实现",直接决定实时抖动、开发门槛、成本与平台锁定。 EtherCAT is a real-time industrial Ethernet. The master orchestrates the whole network: it issues one frame each cycle, slaves read/write their slice "on the fly" as the frame passes, and Distributed Clocks (DC) sync every slave to microseconds. The master builds frames, scans topology, maps PDO/SDO, runs DC sync, manages state machines and diagnoses faults. HOW the master is implemented decides real-time jitter, dev threshold, cost and lock-in.
EtherCAT 主站三种实现路线对比框图

下面把三种路线拆开看:它们的"主站栈"分别跑在哪里、实时性从哪来、又各自要你付出什么。Let's open the three routes: where the master stack runs, where real-time comes from, and what each asks of you.

系统型 · SystemSystem · IDE

TwinCAT / CODESYSTwinCAT / CODESYS

主站栈内置于一整套开发环境:在 Windows(TwinCAT 实时内核)或各类控制器(CODESYS Control 运行时)上,拓扑自动扫描、在线诊断、运动控制(NC / SoftMotion)开箱即用。适合"买成熟工具、最快出活"的团队。The master stack ships inside a full IDE: on Windows (TwinCAT real-time kernel) or various controllers (CODESYS Control runtime), topology auto-scan, online diagnostics and motion (NC / SoftMotion) work out of the box. For teams that "buy mature tooling and ship fastest".

软件型 · SoftwareSoftware · OSS

SOEM / IgHSOEM / IgH

开源主站栈跑在通用硬件上:SOEM(MIT,C,用户态,可上 Linux/Windows/裸机 MCU,轻量)与 IgH(GPLv2,Linux 内核模块,配 PREEMPT_RT/Xenomai 实时性高)。免费、源码可见,但实时调度与维护要你自己扛。Open-source stacks on general hardware: SOEM (MIT, C, user-space, Linux/Windows/bare-metal MCU, lightweight) and IgH (GPLv2, Linux kernel module, high real-time with PREEMPT_RT/Xenomai). Free and visible, but you own real-time scheduling and upkeep.

硬件型 · HardwareHardware · ASIC

讯成 ECM-XFNextW ECM-XF

一颗主站芯片把协议栈与 DC 固化在硬件里,主控 MCU 只通过 SPI(≤96MHz)下配置、取过程数据,无需实时。最小周期 125µs、最多 128 从站、内置 CoE/FoE 与 GPIO/QEI/ADC/DAC,工业级 −40~+105℃。适合要确定性、又不想养实时软件的 PLC / 机器人 / CNC。One master chip freezes the stack and DC in hardware; the host MCU only pushes config and pulls process data over SPI (≤96MHz) — no real-time needed. 125µs min cycle, 128 slaves, built-in CoE/FoE and GPIO/QEI/ADC/DAC, industrial −40~+105℃. For deterministic PLC / robot / CNC without babysitting real-time software.

一张表看差异(选型层面参考,非具体型号 datasheet):One table for the differences (selection-level reference, not a vendor datasheet):

路线Route 代表Examples 主站栈在哪Stack runs on 实时性 / 抖动Real-time 开发门槛Dev effort 许可 / 费用License 平台依赖Lock-in 典型场景Use cases
系统型System TwinCAT(倍福)
CODESYS
实时内核 + IDE 内置RT kernel + built-in IDE 优(工具保底)Excellent (tooling) 低,可视化配置Low, visual 商业授权Commercial 生态 / 工具绑定Vendor / tool 标准 PLC、产线设备Standard PLC, lines
软件型Software SOEM(MIT)
IgH(GPLv2)
通用 Linux / MCUGeneric Linux / MCU 看平台与调度Depends on platform 中–高,自担实时Mid–High, own RT 开源免费Free / OSS 低,源码自持Low, own code 嵌入式、OEM、定制Embedded, OEM
硬件型Hardware 讯成 ECM-XF
ECM-XFU / XFL
独立主站芯片Dedicated chip 优(协议栈固化)Excellent (frozen) 低,宿主免实时Low, host no RT 芯片采购Chip cost 芯片厂商Chip vendor PLC / 机器人 / CNCPLC / robot / CNC
客观提示(非广告):A fair note (not an ad): 三类没有绝对优劣,只有适配。系统型最快出活但有授权与生态绑定;软件型免费灵活但要养一支能搞定实时与内核兼容的团队;硬件型把实时"冻结"在芯片里、宿主 CPU 最轻松,代价是引入一家芯片厂商并要学它的宿主接口与驱动库。具体周期、从站数、温度与封装以原厂手册为准(如讯成 ECM-XF User Manual、Beckhoff / CODESYS 文档、SOEM / IgH 仓库 README)。 None is strictly better — only fit. System masters ship fastest but bind you to a license/ecosystem; software masters are free and flexible but need a team that owns real-time and kernel compat; hardware masters freeze real-time into silicon and spare the host CPU, at the cost of a chip vendor and its host API/driver library. Exact cycle, slave count, temperature and package per the vendor manuals (NextW ECM-XF User Manual, Beckhoff / CODESYS docs, SOEM / IgH READMEs).
落到我们这边:Where we come in: 无论你选哪条主站路线,我们都能把"主站 + 从站节点"做成一个可交付的整体:用 ECM-XF 搭确定性主站控制器,或在嵌入式 Linux 上移植 SOEM;从站侧我们已经有基于 AX58101 的 EtherCAT 分支器(把链路分发到机器人头/臂/躯干/腿)与基于 AX58100 的一拖四电机驱动。主站调度 + 我们的从站,就是一套完整的运动 / IO 节点。欢迎邮件聊具体需求。 Whichever master route you pick, we can build the "master + slave nodes" into one deliverable: an ECM-XF deterministic master controller, or SOEM ported onto embedded Linux; on the slave side we already have the AX58101 EtherCAT junction (splitting the link to a robot's head/arms/torso/legs) and the AX58100 1-to-4 motor drive. Master scheduling plus our slaves = a complete motion / IO node. Email us about your needs.
Capabilities

我们能把这些方案落地We build these into hardware

从一颗元件到一台整机,每一道工序都可控、可测、可交付。From a single component to a finished device — every step is controllable, testable and deliverable.

SMT 贴片与回流焊SMT & Reflow

精密贴片、回流焊与波峰焊工艺,支撑高良率组装。Precision placement, reflow & wave soldering for high-yield assembly.

快速打样Rapid prototyping

从原理图到样机快速落地,缩短想法到实物的距离。From schematic to working prototype, fast — shorten the idea-to-product gap.

测试与品控Test & QC

功能测试、老化与来料检验,让每一台都可靠。Functional test, burn-in and incoming inspection for reliability.

自有供应链Supply chain

自有渠道直采,元件齐全、响应快、交期稳。Direct sourcing through our own channels — broad parts, fast response, steady lead time.

Let's talk

把想法变成可交付的硬件Turn ideas into shippable hardware

无论选型咨询还是具体方案,留下信息,我们直接对接。Whether a selection consult or a concrete build, leave a note and we'll reach out.