| (functional) controller |
virtual device controlling other virtual devices (e.g. lift door controller) |
| (functional) unit |
virtual device controlled by another virtual device (e.g. lift door unit) |
| CAN bridge |
functional element that links two CAN network segments using the same CAN data link layer communication services, the physical layers can be different |
| CAN FD |
data link layer compliant to ISO 11898-1 supporting CBFF (Classical Base Frame Format) and CEFF (Classical Extended Frame Format) as well as FBFF (FD Base Frame Format) and FEFF (FD Extended Frame Format) |
| CAN switch |
functional element that links more than two network segments using the same data link layer communication services, the physical layer can be different |
| CAN transceiver |
component that implements a Physical Media Attachment sub-layer compliant to ISO 11898-2, ISO 11898-3, ISO 11992-1, or SAE 2411 |
| CAN/CAN FD bus |
Classical CAN/CAN FD network segment using bus topology with short stubs |
| CAN/CAN FD controller |
entity implementing the Classical CAN/CAN FD data link layer as stand-alone component or integrated in a micro-controller, an FPGA, or a gate array |
| CAN/CAN FD node |
entity implementing the Classical CAN/CAN FD data link layer, the physical signaling sub-layer, and a PMA |
| CAN/CAN FD repeater |
functional element that links two or more network segments using the same physical layer with the very same bit-timing |
| CANopen FD |
application layer and communication profile as specified in CiA 1301 |
| CANopen FD network system |
communication system comprising one or more CANopen FD network segments connected by means of CAN/CAN FD bridges/switches or CANopen/CANopen FD router |
| CANopen Safety |
safety-related application layer extention as specified in EN 50325-5 (formerly CiA 304) |
| CANopen/CANopen FD field device |
electronic unit comprising printed circuit board, firmware, software, and an optional enclosure as well as one or more CANopen/CANopen FD nodes |
| CANopen/CANopen FD network segment |
Classical CAN/CAN-FD based communication system comprising cabling, connectors, and CANopen/CANopen FD field devices |
| CANopen/CANopen FD node |
entity implementing the CANopen FD application layer services as specified in CiA 301/CiA 1301 |
| CANopen/CANopen FD router |
functional element that links two or multiple CANopen/CANopen FD network segments using the same network layer communication services, the datalink and physical layer can be different |
| CiA application profile |
set of communication interfaces of virtual devices building a logical network system for a dedicated application (e.g. lift control system) |
| CiA device profile |
communication interface of a logical device |
| classic CANopen |
application layer and communication profile as specified in CiA 301 respectively EN 50325-4 |
| Classical CAN |
data link layer compliant to ISO 11898-1 supporting CBFF (Classical Base Frame Format) and CEFF (Classical Extended Frame Format) only |
| COB (communication object) |
dedicated application layer service and corresponding protocol |
| EMCY (Emergency) |
COB providing status information of the CANopen/CANopen FD EMCY FSA (finite state automaton) and detailed information about detected communication and application errors |
| EMCY consumer |
CANopen/CANopen FD functional element receiving EMCY messages from other CANopen/CANopen FD nodes |
| EMCY producer |
CANopen/CANopen FD functional element transmitting the EMCY message |
| frame |
entity of the CAN data link layer protocol |
| frame field |
sub-part of frame (e.g. control field, data field, CRC field, ACK field) |
| functional element |
hardware and/or software entity implementing a specific functionality |
| gateway |
funtional element that links two or more network segments using different application layer communication services |
| Heartbeat |
COB providing the NMT slave FSA status as a confirmation of the requested transistion and implicitely the availability of the CANopen device on the network |
| Heartbeat consumer |
CANopen/CANopen FD functional element receiving Heartbeat messages from other CANopen/CANopen FD nodes |
| Heartbeat producer |
CANopen/CANopen FD functional element transmitting the Heartbeat message |
| interface profile |
communication interface of a CANopen field device with gateway functionality |
| Layer Setting Services (LSS) |
services and protocols to configure the CAN bit-rate, the node-ID, and the network-ID as specified in CiA 305 or CiA 1305 |
| logical device |
functional entity within a CANopen or CANopen FD field device using 800h parameters of the device profile area of the CANopen/CANopen FD object dictionary |
| logical network system |
network system not mapped to physical network segments |
| message |
entity of the application layer protocol |
| NMT (network management) |
COB send by the NMT master entity to NMT slave entities controlling the transitions of the NMT slave FSA |
| node |
entity implementing OSI layer services and protocols |
| packet |
entity of the network layer protocol |
| parameter field |
sub-part of a structured parameter |
| PDO (Process Data Object) |
COB providing process data such as commands, status information, or measured data |
| PDO consumer |
CANopen/CANopen FD functional element receiving PDO messages from other CANopen/CANopen FD nodes |
| PDO producer |
CANopen/CANopen FD functional element transmitting PDO messages |
| PMA (physical media attachment) |
sub-layer of the OSI physical layer normally implemented in transceiver circuitry transforming TxD signals into network line signals respectively network line signals into RxD signals |
| SDO (Service Data Object) |
COB reading or writing to CANopen object dictionary entries |
| SDO/USDO client |
requestor of an SDO/USDO service reading or writing to object dictionaries |
| SDO/USDO server |
responder to an SDO/USDO read or write service request |
| segment |
entity of the transport layer protocol |
| Signal Improvement Circuitry (SIC) |
circuitry that suppresses ringing as specified in CiA 601-4 |
| SYNC (synchronization) |
COB triggering synchronous PDOs and synchronous data acquisition as well as synchronous actuation in different CANopen nodes |
| SYNC consumer |
CANopen/CANopen FD functional element receiving the SYNC message |
| SYNC producer |
CANopen/CANopen FD functional element transmitting the SYNC message |
| TIME (global network time) |
COB providing a global network time information |
| TIME consumer |
CANopen/CANopen FD functional element receiving the TIME message |
| TIME producer |
CANopen/CANopen FD functional element transmitting the TIME message |
| USDO (Universal Service Data Object) |
COB reading or writing to CANopen FD object dictionary entries inlcluding remote access to CANopen FD field devices in other network segments |
| virtual device |
functional entity within a logical device compliant to a CiA application profile |