01The Problem
Industrial machinery needs the same amount of time on the wire every cycle. Standard Ethernet cannot promise that: a packet waits in a switch queue and on the OS scheduler, so its arrival moves with load. EtherCAT removes both, one frame traverses the whole bus and each slave handles its data in hardware as the frame passes through.
02Our Approach
- 01EtherCAT master bring-up on TI Sitara (AM572x/AM437x) using the PRU-ICSS interface
- 02Acontis EC-Master integration under TI-RTOS; cycle timing driven by the application
- 03Slave-side development with Beckhoff SSC on TMS320F28388D, object dictionary and PDO mapping
- 04ESI/ENI configuration, EEPROM programming and bus bring-up diagnostics
- 05Latency, jitter and packet-loss characterization across cycle rate, payload size and slave count
03Measured on Our Bench
Published measurements are taken on our own bench; the setup and method sit next to the number
To evaluate your Industrial Protocols (EtherCAT) needs on your own platform, schedule an embedded architecture audit or scope your platform class with the system requirements calculator.
Schedule Architecture Audit
Deterministic fieldbus is the backbone of industrial systems
Let's assess your motion control topology and design an EtherCAT architecture.
Schedule Architecture Audit