Crosscutting concepts, deployment, quality, and glossary¶
This page groups the short arc42 tail sections: deployment (§7), crosscutting concepts (§8), quality requirements (§10), and the glossary (§12). The decisions pointer (§9) is on Architectural decisions; risks (§11) are on Risks and technical debt.
7. Deployment view¶
All seven toolchain crates live in No deployment-time changes: the toolchain is a build-time
artefact. The only runtime consequence is that
|
8. Crosscutting concepts¶
The crosscutting axes are owned by section 1 (quality goals) and
section 2 (constraints). The two persistent runtime concepts —
the EsiDevice trait and the per-device Identity const — both
live in ethercat-esi-rt (runtime tr... (BB_0063) and are referenced from generated code,
adapters, and dispatch registries alike. They are the contract
the rest of the toolchain orbits.
10. Quality requirements¶
The quality goals in section 1 (Build-time determinism (sam... (QG_0010) through Trait stability for ecosyst... (QG_0013)) define the qualities. The verification artefacts in Device-driver codegen — verification exercise each one.
12. Glossary¶
EtherCAT Slave Information — an XML file describing a single
EtherCAT device’s identity, PDOs, mailbox, distributed clocks,
and object dictionary. Schema is published by ETG
( |
Slave Information Interface — the on-device EEPROM that
carries a binary subset of the ESI data, readable over the
EtherCAT bus by the master. |
Process Data Object — a fixed-length packed set of OD entries exchanged on every EtherCAT cycle. RxPDO = master → device (outputs); TxPDO = device → master (inputs). |
CANopen over EtherCAT — mailbox protocol carrying CANopen SDO writes (e.g. PDO assignment writes to 0x1C12 / 0x1C13). |
The indexed (16-bit index + 8-bit sub-index) catalogue of readable / writable objects on a CANopen or CoE device. Inherited by EtherCAT from CANopen (CiA 301). |
An SDO write sequence declared inside an ESI |