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 (1)
| Label | Occurrences |
|---|---|
| CANopen canonical | 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 NERFINISHED ⓘ |
| category | industrial network protocol ⓘ |
| competesWith |
DeviceNet
NERFINISHED
ⓘ
EtherCAT NERFINISHED ⓘ PROFIBUS NERFINISHED ⓘ PROFINET NERFINISHED ⓘ |
| 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
GENERATED
ⓘ
Network Management message GENERATED ⓘ Process Data Object GENERATED ⓘ Service Data Object GENERATED ⓘ Synchronization message GENERATED ⓘ Time stamp message GENERATED ⓘ |
| hasErrorControlMechanism |
heartbeat
ⓘ
life guarding ⓘ node guarding ⓘ |
| hasSafetyProfile | CiA 304 NERFINISHED ⓘ |
| hasSpecification |
CiA 301
NERFINISHED
ⓘ
CiA 302 NERFINISHED ⓘ CiA 303 NERFINISHED ⓘ CiA 304 NERFINISHED ⓘ CiA 305 NERFINISHED ⓘ CiA 306 NERFINISHED ⓘ CiA 307 NERFINISHED ⓘ CiA 309 NERFINISHED ⓘ CiA 410 NERFINISHED ⓘ EN 50325-4 NERFINISHED ⓘ |
| hasVariant |
CANopen FD
NERFINISHED
ⓘ
CANopen Lift NERFINISHED ⓘ CANopen Safety NERFINISHED ⓘ |
| introducedIn | 1990s ⓘ |
| maintainedBy | CAN in Automation NERFINISHED ⓘ |
| originatedIn | Europe NERFINISHED ⓘ |
| relatedTo |
DeviceNet
NERFINISHED
ⓘ
J1939 NERFINISHED ⓘ |
| specifiedIn | CiA 301 NERFINISHED ⓘ |
| standardizedBy | CiA NERFINISHED ⓘ |
| supports |
distributed control systems
ⓘ
master-slave communication ⓘ multi-master communication ⓘ real-time communication ⓘ |
| supportsBitRate |
1 Mbit/s
GENERATED
ⓘ
10 kbit/s GENERATED ⓘ 125 kbit/s GENERATED ⓘ 20 kbit/s GENERATED ⓘ 250 kbit/s GENERATED ⓘ 50 kbit/s GENERATED ⓘ 500 kbit/s GENERATED ⓘ |
| supportsConfiguration |
dynamic configuration
ⓘ
static configuration ⓘ |
| supportsDeviceProfile |
CiA 401 I/O modules
GENERATED
ⓘ
CiA 402 drives and motion control GENERATED ⓘ CiA 404 measurement devices GENERATED ⓘ CiA 406 encoders GENERATED ⓘ CiA 408 fluid power GENERATED ⓘ CiA 417 lifts GENERATED ⓘ CiA 418 building automation GENERATED ⓘ CiA 419 building automation GENERATED ⓘ |
| supportsMapping | PDO mapping GENERATED ⓘ |
| supportsMedium |
fiber optic
ⓘ
twisted pair cable ⓘ wireless bridge ⓘ |
| supportsRedundancy | network redundancy mechanisms ⓘ |
| supportsSafetyExtension | CANopen Safety GENERATED ⓘ |
| 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 NERFINISHED ⓘ PDO NERFINISHED ⓘ 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 (1)
Full triples — surface form annotated when it differs from this entity's canonical label.