CAN Kingdom is a communications protocol running on top of CAN. It is designed as a fieldbus. Unlike other CAN high level protocols, it makes no attempt to follow the OSI model. The network is mostly distributed, as the nodes may run autonomously except that a "King" or master controller is needed to configure the network. A major design philosophy behind CAN Kingdom is that the system designer is fully aware of the capabilities of the nodes.
| Property | Value |
|---|
| dbpprop:abstract
|
- CAN Kingdom is a communications protocol running on top of CAN. It is designed as a fieldbus. Unlike other CAN high level protocols, it makes no attempt to follow the OSI model. The network is mostly distributed, as the nodes may run autonomously except that a "King" or master controller is needed to configure the network. A major design philosophy behind CAN Kingdom is that the system designer is fully aware of the capabilities of the nodes. A node designer, on the other hand, needs to know nothing about the other nodes: a node merely provides services to the network, and it is up to the system designer to activate a node's services or not through runtime configuration.
|
| dbpprop:hasPhotoCollection
| |
| rdf:type
| |
| rdfs:comment
|
- CAN Kingdom is a communications protocol running on top of CAN. It is designed as a fieldbus. Unlike other CAN high level protocols, it makes no attempt to follow the OSI model. The network is mostly distributed, as the nodes may run autonomously except that a "King" or master controller is needed to configure the network. A major design philosophy behind CAN Kingdom is that the system designer is fully aware of the capabilities of the nodes.
|
| rdfs:label
| |
| owl:sameAs
| |
| skos:subject
| |
| foaf:page
| |
| is owl:sameAs
of | |
![[RDF Data]](/statics/sw-cube.png)
