Skip to main content
Version: 1.1.1

LXMASTER Features

This page lists the full set of LXMASTER features organized by category. Use the filter pills to focus on a specific status.

StatusMeaning
AvailableFully implemented and ready to use in the current release.
In developmentActively being worked on; not yet in a release.
PlannedConfirmed on the roadmap; work has not started.
Not plannedNot currently on the roadmap.
12Available
7In development
0Planned
19Not planned

Core EtherCAT communication

FeatureStatusNotes
EtherCAT state machine (INIT / PRE-OP / SAFE-OP / OP)AvailableFull ESM with AL status + status-code handling, error-ack retry, and BOOT state support.
Service commands (APRD / FPRD / BRD / LRD / LWR / LRW / ARMW / FRMW)AvailableFull EtherCAT command set driven by the configurator and the cyclic path.
Raw EtherCAT frame types (EtherType 0x88A4)AvailableStandard raw EtherCAT frames on the wire.
Error handling and fault reportingAvailablePer-cycle working-counter watchdog, link/topology break localisation, AL monitoring, on_bus_fault callback.
IRQ field in EtherCAT datagramNot plannedAL-event IRQ mask is generated in the ENI, but the datagram IRQ field is not consumed; state changes are detected by polling AL Status.
Device emulation flag awarenessNot plannedSimple and complex slaves are handled, but no special error-ack skipping for device-emulation slaves.
VLAN taggingNot plannedOptional per the EtherCAT spec; not implemented.
UDP frame typesNot plannedOptional per the EtherCAT spec; not implemented.

Process data

FeatureStatusNotes
Cyclic PDO exchangeAvailableProcess data packed into segmented LWR/LRD frames per group; driven by a single real-time cyclic task.
Multiple cyclic tasks (multi-rate)Not plannedThe backend supports multi-group process data, but only a single cyclic task is exposed. Wire on demand.
Frame repetitionNot plannedNot implemented.

Network configuration

FeatureStatusNotes
ENI file loading and validationAvailableRuntime loads and validates an ENI; online bus scan reads live SII/identity. Both paths are available.
Network configuration comparison at bootAvailableSlave count, VendorId, ProductCode, and revision rules are compared on bring-up.
Explicit device identificationNot plannedENI Identification ADO not parsed; needed for hot-connect and cable-swap detection.
Station alias addressingNot plannedAlias address is read from hardware but addressing still uses the configured address.
EEPROM read / write / reloadIn developmentFull EEPROM access (read, write, reload, dump) is available in the backend but not yet surfaced through the public API.

Mailbox

FeatureStatusNotes
Mailbox protocol supportAvailableMailbox pool, queue, post/fetch, and sync-manager setup.
Resilient mailbox layer (link-counter + retransmit)AvailableLink-counter toggle (wraps 1–7) and retransmit queue are fully implemented.
Cyclic mailbox polling (unsolicited input data)In developmentCyclic mailbox handler exists in the backend but is not wired in the public API.
Multiple mailbox channelsNot plannedOptional per the spec; not implemented.

CoE — CANopen over EtherCAT

FeatureStatusNotes
SDO upload / download (normal + expedited)AvailableUsed throughout for PDO assignment, CiA402 objects, and ENI InitCmd replay.
Segmented SDO transferAvailableTransparent handling of segmented uploads and downloads of any size.
SDO complete accessIn developmentBackend supports complete access but callers do not yet use it.
SDO information service (object dictionary listing)In developmentOD listing is available in the backend but not exposed through the public API.
CoE Emergency messagesNot plannedEmergency messages are decoded internally into the error log but not yet surfaced as application callbacks.
PDO transmission via CoENot plannedOptional; expose on demand.

Mailbox protocols (EoE / FoE / SoE / AoE / VoE)

FeatureStatusNotes
EoE — Ethernet over EtherCATIn developmentIP config, fragmented send/recv, and reassembly are in the backend; not yet exposed through the public API.
EoE virtual switch + OS endpointNot plannedNeeds a host-side L2 switch / TAP bridge to the OS IP stack.
FoE — File over EtherCAT (firmware up/download)In developmentFull FoE get_file/put_file with password and progress hook is in the backend; not yet exposed through the public API.
BOOT state for firmware updateIn developmentBOOT state exists; needs wiring in the bring-up sequence for firmware update use cases.
SoE — Servo drive profile over EtherCAT (IDN)Not plannedSoE read_idn/write_idn/map_idns is in the backend; not yet exposed through the public API.
AoE — ADS over EtherCATNot plannedRouting slot exists; no AoE service module. Needs new code.
VoE — Vendor-specific over EtherCATNot plannedRouting slot exists; no VoE handler. Optional.

Distributed Clocks

FeatureStatusNotes
DC configuration and synchronisationAvailablePropagation-delay measurement, reference clock selection, alignment, SYNC0/SYNC01 setup, and master-side PI drift controller.
Continuous propagation-delay re-measurementNot plannedMaster–DC drift is compensated, but periodic re-measurement of propagation delay is not yet emitted.
Sync window monitoring (hard per-cycle fault)Not plannedSystem-time-difference is gated at OP entry and traced in OP, but no hard per-cycle fault threshold is enforced.

Advanced bus features

FeatureStatusNotes
Slave-to-slave data copy via masterNot plannedNo master-side routing of one slave's inputs to another's outputs. Required for Safety-over-EtherCAT.
Master object dictionary (ETG.5001)Not plannedNo master-local OD.

Device profiles and feature packs

Feature packStatusNotes
Motion control — CiA402 drive profileAvailableFull CiA402 drive profile: control/status word, CSP/CSV/CST operating modes, DC sync. The primary purpose of LXMASTER.
Digital I/O — CiA401 profileAvailableDigital and analog I/O modules via the IoModule facade.
Encoder — CiA406 profileAvailableEncoder devices via the Encoder facade.
Custom device profilesAvailableUsers can implement IDeviceProfile / IMotionProfile / IIoProfile to support any EtherCAT device.
Cable redundancyIn developmentRing-topology plumbing exists in the backend; break-localisation and facade wiring remain.
Motion control — SERCOS / SoE drive profileNot plannedSoE transport is available; no SERCOS drive profile layer on top.
Hot connect (dynamic topology)Not plannedNo hot-connect groups or identify commands.