Skip to content

CANopen

CAN-based higher-layer protocol with object dictionaries, PDO/SDO, network management, and device profiles.

Status Examples Runtime example Source posture
draft-structure-only synthetic/passive docs-only atlas metadata plus public/tooling cross-checks

Identity

CAN-based higher-layer protocol with object dictionaries, PDO/SDO, network management, and device profiles.

What This Protocol Teaches

  • CANopen is what happens when CAN gets an industrial object dictionary.
  • It teaches how to inspect object dictionary, PDO, SDO without mistaking field extraction for meaning.
  • It keeps observer inference separate from system truth.

Operational Context

CANopen appears in industrial, automotive, embedded contexts and is modeled in the atlas at the application, network-management 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 status

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 SDO upload request
0x600+0x05  40 40 60 00 00 00 00 00

Synthetic

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

Worked Decode

  1. Read 0x600+0x05 as a synthetic observed CANopen COB-ID pattern for node 0x05.
  2. 40 40 60 00 ... is SDO-shaped payload evidence, not an instruction to read an object.
  3. Index 0x6040 and subindex 0x00 require an object dictionary and device profile before naming meaning.
  4. The page can teach object-dictionary authority without promoting live SDO workflows.

Field Layout / Anatomy

Element Shape Inspection meaning
object dictionary artifact-specific evidence Inspect with timing and source context before naming meaning.
PDO artifact-specific evidence Inspect with timing and source context before naming meaning.
SDO artifact-specific evidence Inspect with timing and source context before naming meaning.
NMT artifact-specific evidence Inspect with timing and source context before naming meaning.
heartbeat artifact-specific evidence Inspect with timing and source context before naming meaning.
semantic authority external source Dictionary, profile, map, or integration document that turns evidence into named meaning.
timing context cadence / gap / slot / timestamp Freshness and ordering evidence for observer reconstruction.

Visual Model

flowchart LR raw["Raw evidence"] --> structure["Field structure"] structure --> timing["Timing / cadence"] timing --> authority["Semantic authority"] authority --> inference["Observer state hypothesis"]

Timing And Authority

Timing and authority depend on the higher-layer-protocol 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.

Semantic authority

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

  • Object indexes need an object dictionary and profile before meaning.
  • An SDO-shaped observed payload must not become a live operation recipe.
  • Node IDs can be reused, remapped, or hidden behind gateways.

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

No current runtime example is claimed for this draft page. Keep reader claims at the artifact and source level until a separate implementation plan adds a tested model.

Local Teaching Notes

Simplification

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 high for scope and terminology, with semantic claims limited to public metadata, public source notes, and synthetic teaching artifacts.

Source Notes

Field Value
Governance tier Tier 2 Field Note
Canonical source status yes
Public explainer status no
Open-source tool status yes
Sample-data status none listed; use synthetic teaching artifacts
Confidence high
Citation specificity document-metadata-level
Canonical source(s) CANopen overview and CiA 301 family (CAN in Automation; CiA 301 family; public-metadata/paywalled-spec; metadata-only)
Public explainer/tooling source(s) none listed in atlas
Open-source tool references canopen-python: CANopen automation/testing
python-can: CAN log inspection and offline lab context
can-utils: CAN capture/log-format context

References

Public Sources