EtherCAT reference connector¶
A second concrete connector instantiating the framework’s contracts. This
cluster :satisfies: Connector framework (FEAT_0030).
A second concrete connector instantiating the framework’s contracts:
|
The connector crate shall expose |
The |
A single |
The gateway shall transition the EtherCAT bus to the OP state before accepting envelope traffic from the plugin side. |
The connector shall accept a static PDO-mapping description per
SubDevice at build time, declared by the application crate via
|
The gateway shall apply the configured PDO mapping by issuing SDO writes
to the sync-manager assignment indices |
The gateway shall accept a configurable cycle duration via
|
When the gateway misses one or more cycle ticks, it shall skip the missed ticks rather than queue them for catch-up execution. |
The connector shall perform Distributed Clocks bring-up only when
|
The gateway shall report |
When the working counter on a completed cycle is below the expected
value, the gateway shall transition |
The EtherCAT gateway shall host the ethercrab TX/RX task on a tokio
runtime contained inside |
The outbound (taktora-executor → tokio) and inbound (tokio →
taktora-executor) bridges between the plugin and the gateway sidecar
shall be bounded channels with configurable capacity in
|
When the outbound bridge channel is full, |
When the inbound bridge channel is full, the gateway shall
(1) increment the per-channel inbound-drop counter exposed via
|
The gateway shall open the EtherCAT network interface via a Linux raw
socket, requiring the |
When a plugin publishes a value through |
After each cycle’s |
The gateway shall maintain a registry mapping each open
|
|
When Implementation status (2026-06-06). Deferred. |
When A failed |
|
The health state machine shall emit, during a recovery episode, exactly the transitions:
|
When transitioning the bus from SAFE-OP to OP — during both bring-up and recovery — the gateway shall request the OP state without blocking and shall continue cyclic process-data exchange until every SubDevice reports OP. While waiting, the gateway shall periodically acknowledge latched AL errors (AL Control with the error-acknowledge bit plus a renewed OP request) and shall fail the attempt after a bounded number of exchanges. Rationale. SM-watchdog couplers — canonically the WAGO
750-354, whose ESI declares |
When Rationale. The spawned task is the only owner of the bring-up
error; dropping it leaves the connector in |
For every Rationale. Safety assumption Output-slave watchdog enabl... (AOU_0016) requires an output
slave’s SM watchdog to be enabled with a timeout ≤ FTTI/2 (≤ 50 ms),
because on a framework-invariant abort the master stops emitting
process-data frames and the slave watchdog is the sole mechanism
that drives outputs to their safe state (Abort on framework-invarian... (ADR_0065)). The ESC
powers up with a 100 ms window — twice the bound — and ESI files
carry no timeout data, so the master must program these registers
itself, exactly as IgH ( |
|