CANopen
E1029498
CANopen is a higher-layer communication protocol and device profile specification built on top of the CAN bus, widely used for automation and embedded control networks.
All labels observed (7)
| Label | Occurrences |
|---|---|
| CANopen canonical | 5 |
| CANopen Safety | 2 |
| CAN in Automation | 1 |
| CANopen FD | 1 |
| CANopen Lift | 1 |
| CiA 301 | 1 |
| CiA 410 | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T13241721 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CANopen Context triple: [CAN bus, relatedStandard, CANopen]
-
A.
CoE (CAN application protocol over EtherCAT)
CoE (CAN application protocol over EtherCAT) is a communication profile that encapsulates CANopen services and objects for use over EtherCAT networks, enabling standardized device configuration and data exchange.
-
B.
EtherCAT
EtherCAT is a high-performance industrial Ethernet protocol designed for real-time control in automation systems.
-
C.
CAN bus
CAN bus is a robust automotive serial communication network standard that allows microcontrollers and devices to communicate with each other without a host computer, widely used in vehicles and industrial systems.
-
D.
FSoE (FailSafe over EtherCAT)
FSoE (FailSafe over EtherCAT) is a safety communication protocol that enables the transmission of fail-safe control data over standard EtherCAT networks in compliance with functional safety standards.
-
E.
DeviceNet
DeviceNet is an industrial fieldbus network protocol used primarily for connecting industrial controllers with I/O devices, drives, and other automation components over a robust, real-time communication network.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: CANopen Target entity description: CANopen is a higher-layer communication protocol and device profile specification built on top of the CAN bus, widely used for automation and embedded control networks.
-
A.
CoE (CAN application protocol over EtherCAT)
CoE (CAN application protocol over EtherCAT) is a communication profile that encapsulates CANopen services and objects for use over EtherCAT networks, enabling standardized device configuration and data exchange.
-
B.
EtherCAT
EtherCAT is a high-performance industrial Ethernet protocol designed for real-time control in automation systems.
-
C.
CAN bus
CAN bus is a robust automotive serial communication network standard that allows microcontrollers and devices to communicate with each other without a host computer, widely used in vehicles and industrial systems.
-
D.
FSoE (FailSafe over EtherCAT)
FSoE (FailSafe over EtherCAT) is a safety communication protocol that enables the transmission of fail-safe control data over standard EtherCAT networks in compliance with functional safety standards.
-
E.
DeviceNet
DeviceNet is an industrial fieldbus network protocol used primarily for connecting industrial controllers with I/O devices, drives, and other automation components over a robust, real-time communication network.
- F. None of above. chosen
Statements (99)
| Predicate | Object |
|---|---|
| instanceOf |
communication protocol
ⓘ
fieldbus protocol ⓘ higher-layer protocol ⓘ |
| basedOn | CAN bus ⓘ |
| category | industrial network protocol ⓘ |
| competesWith |
DeviceNet
ⓘ
EtherCAT ⓘ PROFIBUS ⓘ PROFINET ⓘ |
| defines |
application profiles
ⓘ
boot-up behavior ⓘ communication profiles ⓘ device profiles ⓘ device states ⓘ error control mechanisms ⓘ network management ⓘ object dictionary ⓘ |
| hasAddressSpace | 127 nodes per network ⓘ |
| hasCommunicationObject |
Emergency message
ⓘ
Network Management message ⓘ Process Data Object ⓘ Service Data Object ⓘ Synchronization message ⓘ Time stamp message ⓘ |
| hasErrorControlMechanism |
heartbeat
ⓘ
life guarding ⓘ node guarding ⓘ |
| hasSafetyProfile | CiA 304 ⓘ |
| hasSpecification |
CiA 301
ⓘ
CiA 302 ⓘ CiA 303 ⓘ CiA 304 ⓘ CiA 305 ⓘ CiA 306 ⓘ CiA 307 ⓘ CiA 309 ⓘ CiA 410 ⓘ
linked to:
CANopen
EN 50325-4 ⓘ |
| hasVariant |
CANopen FD
ⓘ
linked to:
CANopen
CANopen Lift ⓘ
linked to:
CANopen
CANopen Safety ⓘ
linked to:
CANopen
|
| introducedIn | 1990s ⓘ |
| maintainedBy |
CAN in Automation
ⓘ
linked to:
CANopen
|
| originatedIn | Europe ⓘ |
| relatedTo |
DeviceNet
ⓘ
J1939 ⓘ |
| specifiedIn |
CiA 301
ⓘ
linked to:
CANopen
|
| standardizedBy | CiA ⓘ |
| supports |
distributed control systems
ⓘ
master-slave communication ⓘ multi-master communication ⓘ real-time communication ⓘ |
| supportsBitRate |
1 Mbit/s
ⓘ
10 kbit/s ⓘ 125 kbit/s ⓘ 20 kbit/s ⓘ 250 kbit/s ⓘ 50 kbit/s ⓘ 500 kbit/s ⓘ |
| supportsConfiguration |
dynamic configuration
ⓘ
static configuration ⓘ |
| supportsDeviceProfile |
CiA 401 I/O modules
ⓘ
CiA 402 drives and motion control ⓘ CiA 404 measurement devices ⓘ CiA 406 encoders ⓘ CiA 408 fluid power ⓘ CiA 417 lifts ⓘ CiA 418 building automation ⓘ CiA 419 building automation ⓘ |
| supportsMapping | PDO mapping ⓘ |
| supportsMedium |
fiber optic
ⓘ
twisted pair cable ⓘ wireless bridge ⓘ |
| supportsRedundancy | network redundancy mechanisms ⓘ |
| supportsSafetyExtension |
CANopen Safety
ⓘ
linked to:
CANopen
|
| supportsService |
firmware update over CAN
ⓘ
remote configuration ⓘ remote diagnostics ⓘ |
| supportsTopology |
linear bus
ⓘ
tree topology ⓘ |
| usedIn |
building automation
ⓘ
embedded control systems ⓘ industrial automation ⓘ machine tools ⓘ maritime applications ⓘ medical devices ⓘ off-road vehicles ⓘ railway applications ⓘ |
| uses |
CAN identifiers
ⓘ
EMCY ⓘ NMT ⓘ PDO ⓘ SDO ⓘ SYNC ⓘ TIME object ⓘ communication objects ⓘ object dictionary ⓘ |
| usesAddressing | node ID ⓘ |
| usesDataLinkLayer | CAN ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: CANopen Description of subject: CANopen is a higher-layer communication protocol and device profile specification built on top of the CAN bus, widely used for automation and embedded control networks.
Referenced by (12)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: CANopen
linked to: CANopen
linked to: CANopen
linked to: CANopen
linked to: CANopen
linked to: CANopen
linked to: CANopen