CAN bus: what it means.
A CAN controller handles communication and arbitration, while a transceiver connects logic-level signals to the physical bus. TI describes a differential twisted-pair network in which nodes receive broadcast messages and determine which ones to process. (Texas Instruments: CAN transceivers)
The controller is not the same part as the transceiver, even when integration combines them. A higher-level application protocol is another layer. Review each layer instead of treating the two signal wires as a complete communications specification. (Texas Instruments: CAN transceivers)
Put the definition to work.
Separate the CAN controller, transceiver, and higher-level application protocol when reading a design. Do not apply the data-rate limits of one CAN variant to every CAN implementation. (Texas Instruments: CAN fundamentals)
Questions to ask next.
Use these questions as a reading checklist, not as a device-selection recommendation. Exact manufacturer documentation takes priority over a general definition.
- Controller, transceiver and application layers
- Physical network and termination requirements
- Variant, timing and network load
For the broader explanation, explore the electronics inside robots. This page defines the term; the companion guide connects it to the rest of the system.
Common CAN bus questions.
What happens if nodes try to send together?
CAN uses arbitration so the higher-priority message continues while another sender stops and retries when the bus is available. Implementation and network conditions still require evaluation. (Texas Instruments: CAN transceivers)