All Case Studies

Industrial Protocols & Motion Control

Lab Verified

EtherCAT Master Architecture with a 3.8µs Cycle Time

P99 cycle jitter <4µs · Distributed clock sync <100ns · PREEMPT_RT

NXP i.MX8M Plus · PREEMPT_RT Linux · IgH EtherCAT Master

8µs → 3.8µsEtherCAT Cycle
<100nsSlave Sync Error
<4µsFrame Latency
0Missed Cycles / Hour
Platformi.MX8M Plus · Cortex-A53 + PREEMPT_RT
ProblemStandard Ethernet stack could not guarantee a deterministic cycle
InterventionIgH master + PREEMPT_RT isolation + distributed clocks (DC)
Result3.8µs cycle · <100ns sync · hot-connect support

01Problem

Problem: Why Standard Ethernet Wasn't Enough

In multi-axis servo topologies, axis-to-axis synchronization requires the entire bus to align to a single time base. TCP/IP transport introduces ~1ms of non-deterministic latency, which makes coordinated motion profiles impossible. Proprietary fieldbus hardware means vendor lock-in and added cost. The goal: build a microsecond-class, predictable EtherCAT master line on standard Ethernet PHY hardware.

  • 01~1ms variable latency over the TCP/IP stack — unusable for axis coordination
  • 02Cycle jitter was uncontrollable under the stock kernel scheduler — soft-IRQs and RCU callbacks interrupted the critical path
  • 03Slave local clocks drifted within a ±5µs band — position error accumulated in multi-axis interpolation
  • 04Hot-connect scenarios (adding/removing devices on the line) required restarting the master state machine
  • 05Drive profiles (CiA 402) and object dictionary management lived in a hand-written, hard-to-maintain layer

02System Context

ProcessorNXP i.MX8M Plus — 4× Cortex-A53 @ 1.8GHz
KernelLinux 6.1 LTS + PREEMPT_RT patch
Master stackIgH EtherCAT Master (evaluated comparatively against SOEM)
Bus topologyMulti-axis servo + I/O modules — line topology
SynchronizationEtherCAT Distributed Clocks (DC) — reference-slave based
Drive profileCoE — CiA 402 (CANopen over EtherCAT)
MeasurementHardware timestamps + oscilloscope cycle measurement, P99 reporting

03Root Cause Analysis

  1. 01The NIC driver ran in NAPI polling mode: interrupt coalescing added 3–8µs of variable latency to EtherCAT frames
  2. 02The EtherCAT master thread ran in the general-purpose CFS scheduler class — no RT priority, no core isolation (isolcpus)
  3. 03Distributed clock start-up calibration was skipped: slave clock offsets were never compensated before cyclic data hit the bus
  4. 04PDO mapping was left at defaults — unused objects were transported every cycle, inflating frame time
  5. 05Kernel soft-IRQ handlers (including networking) shared the master's core — creating worst-case missed-cycle risk

04What We Changed

01

Dedicated core on PREEMPT_RT: master thread moved to SCHED_FIFO 99, isolated via isolcpus + IRQ affinity

Cycle jitter pulled into a deterministic band — P99 <4µs

02

Migration to IgH EtherCAT Master with the NIC driver in EtherCAT-specific polling mode

Coalescing-induced variable latency eliminated — cycle time down from 8µs to 3.8µs

03

Distributed clock (DC) calibration: reference-slave election + offset/drift compensation added to the start-up sequence

Slave sync error dropped from ±5µs to <100ns

04

PDO maps trimmed per axis; CiA 402 state machine standardized over CoE

Smaller frames; the drive layer collapsed into a single maintainable profile

05

Hot-connect support: bus rescan and reconfiguration made incremental without stopping the cyclic exchange

Motion line stays uninterrupted while devices are added or removed

05Measured Results

MetricBeforeAfterΔ
EtherCAT cycle time8µs3.8µs−53%
Slave sync error±5µs<100ns−98%
Network latency (command path)~1ms (TCP)<4µs≈ −99.6%
Missed cycles (1h, full load)not measurable*0

06Business Value

A deterministic fieldbus is the backbone of multi-axis machinery. Microsecond-class cycles and nanosecond-class synchronization translate into higher interpolation rates, smoother motion profiles and less mechanical wear — on standard Ethernet hardware.

  • 01Standard Ethernet PHY instead of proprietary fieldbus silicon — BOM cost and supply flexibility preserved
  • 02Architecture ready for IEC 62443-compliant network segmentation — a base for industrial security audits
  • 03CiA 402 standardization made drive replacement vendor-independent
  • 04Hot-connect allows line maintenance without stopping production
  • 05The same master architecture extends to PROFINET/CANopen bridging scenarios

To evaluate your Industrial Protocols & Motion Control needs on your own platform, schedule an embedded architecture audit or scope your platform class with the system requirements calculator.

Methodology Note

  • Cycle times measured with hardware timestamps and an oscilloscope; P99 values reported — not averages
  • Test condition: 1 hour of uninterrupted operation under full PDO load
  • * Missed-cycle count in the 'before' configuration was not meaningfully measurable — jitter was entirely out of band
  • All comparisons ran on identical hardware and identical bus topology
  • Project details remain confidential under NDA — client identity anonymized
  • Raw measurement data and the methodology document are available on request

Facing similar determinism issues on your motion control bus?

Free technical assessment — let's review the latency and determinism challenges in your system together.

All performance data obtained in our own lab under reproducible conditions. Project-specific details remain confidential under NDA. Methodology document available on request.