EDS / DCF¶

CANopen device object dictionary and configuration description formats.

Identity¶

CANopen device object dictionary and configuration description formats.

What This Protocol Teaches¶

• EDS/DCF is the object dictionary made portable.
• It teaches how to inspect object dictionary entries, data types, access rights without mistaking field extraction for meaning.
• It keeps observer inference separate from system truth.

Operational Context¶

EDS / DCF for CANopen appears in industrial, canopen contexts and is modeled in the atlas at the description-file layer(s). The binder treats it as an inspection surface: what evidence appears, what timing matters, and what outside authority is required before assigning meaning.

draft-structure-only: this is not yet a final-copy binder page. It has an atlas-grounded teaching hook and source notes, but still needs a stronger worked trace, page-specific ambiguity case, and reviewer-validated visual before promotion.

A Concrete Artifact¶

; synthetic CANopen object dictionary fragment
[6040]
ParameterName=Controlword
DataType=0x0006
AccessType=rw

Synthetic offline sample for explanation; not a real operational trace or live-system instruction.

Worked Decode¶

1. Read [6040] as a CANopen object-dictionary index in a synthetic description fragment.
2. ParameterName=Controlword names an object under dictionary authority, not a live command.
3. DataType=0x0006 and AccessType=rw describe metadata that must not be converted into operational guidance here.
4. Profile/version provenance determines whether the object description matches captured evidence.

Field Layout / Anatomy¶

Visual Model¶

Timing And Authority¶

Timing and authority depend on the device-description-format role: scheduled, polled, arbitrated, transmitted, or logged evidence should not be read as the same kind of truth. Semantic authority is external to the raw artifact unless the artifact is itself a description or capture format; even then, provenance determines whether the description should be trusted.

Bytes rarely explain themselves. Name the source that defines meaning before naming engineering values: standard metadata, label table, DBC, PGN/SPN definition, object dictionary, register map, DID catalog, LDF, ARXML, channel metadata, or vendor profile.

Failure And Ambiguity¶

• Access metadata is documentation, not permission to operate a device.
• Object meaning changes with device profile and vendor extension.
• Dictionary/version mismatch can make object names plausible but wrong.

Observer Lesson¶

A passive observer can usually infer artifact boundaries, repeated structure, cadence, missingness, and candidate state transitions. The observer usually cannot prove physical truth, application intent, complete system state, or engineering-unit meaning without semantic authority and timing provenance.

Python Model¶

schoolbus does not parse this format in this wave. This page records source posture, passive inspection questions, and metadata boundaries only. Runtime support would require a separate approved plan with concrete synthetic artifacts, tests, and source-checked parser boundaries.

Local Teaching Notes¶

The artifact and diagrams are synthetic teaching material. The page intentionally omits conformance timing tables, electrical design detail, proprietary configuration, and exhaustive standard behavior.

Source Confidence¶

Source confidence is medium for scope and terminology, with semantic claims limited to public metadata, public source notes, and synthetic teaching artifacts.

Source Notes¶

References¶

Public Sources¶

• CAN in Automation
• CANopen overview and CiA 301 family — canonical-standard.
• Tooling references
• canopen-python — CANopen automation/testing.