Faq For CAN Communication?

CAN Controller Area Network industrial communication

CAN — Controller Area Network is a message-based, multi-node serial communication system designed to allow electronic controllers to exchange data reliably over a shared bus. Originally developed for automotive electronics, CAN is now also widely used in machines, mobile equipment, medical systems, motion control and many industrial communication applications.

In simple terms: devices on a CAN network do not normally send data by saying “this message belongs only to device 5.” Instead, a CAN frame carries an identifier. Every node can see the message and decides through its acceptance filters whether that message is relevant. The identifier also determines the frame's arbitration priority.

How did CAN originate?

Bosch began developing a new serial bus system in 1983 to improve communication between electronic control units in vehicles. The technology was publicly introduced at the SAE congress in February 1986 under the name Controller Area Network.

CAN later became an international standard through ISO 11898, first published in 1993. Its use expanded far beyond passenger cars into industrial machines, elevators, transportation systems and embedded control equipment.

Is CAN a master-slave network?

Not at the basic CAN data-link layer. When the bus is idle, any CAN controller may attempt to transmit. This is why CAN is commonly described as a multi-master communication system.

A higher-level application running on CAN can still define a controller, manager or master-like role. For example, a PLC may logically manage an automation system, but the underlying CAN arbitration mechanism itself is not based on one permanent bus master.

Why does CAN use message identifiers instead of simple device addresses?

CAN is fundamentally message-oriented. The CAN identifier describes the priority and, at the application level, usually the meaning or class of the message rather than acting as a universal destination address.

For example, an intelligent sensor can publish a pressure or temperature message on the network. A PLC, display, data logger or another controller can all receive the same frame if their acceptance filters are configured for that identifier.

The meaning assigned to each identifier is defined by the application or by a higher-level protocol such as CANopen; basic CAN does not provide a universal process-data register map.

What are 11-bit and 29-bit CAN identifiers?

Classical CAN supports two identifier formats:

Base / Standard Frame: 11-bit identifier.
Extended Frame: 29-bit identifier.

The standard 11-bit format provides 2048 possible identifier values. The extended frame provides a much larger identifier space for applications that require additional message classification.

How does CAN arbitration work?

Two or more nodes may begin transmitting when the bus becomes idle. CAN resolves this situation using non-destructive bitwise arbitration.

In CAN logic, a dominant bit is 0 and a recessive bit is 1. Every transmitter monitors the actual bus level while sending its identifier.

If a node transmits recessive 1 but observes dominant 0, it knows another frame has higher priority and immediately stops transmitting. The winning frame continues without being corrupted.

This means that, during normal arbitration, a numerically lower CAN identifier has higher priority.

This priority mechanism can be useful in an industrial control system where fast machine-state messages need higher bus priority than less urgent diagnostic information.

What is inside a Classical CAN frame?

A Classical CAN data frame contains several defined fields, including:

Start of Frame
Arbitration Field / Identifier
Control Field
Data Length Code
Data Field
CRC Field
ACK Field
End of Frame

Classical CAN carries up to 8 bytes of application data in one data frame. Applications requiring larger transfers can use a higher-layer segmentation mechanism or a newer CAN format such as CAN FD.

What does the CAN ACK field mean?

A CAN node that receives a frame correctly can transmit a dominant bit during the ACK slot. If the transmitter observes that dominant ACK level, it knows that at least one other CAN controller successfully received the frame at protocol level.

ACK does not mean that the application executed the command. It only confirms that at least one node accepted the CAN frame as valid.

Does CAN correct communication errors?

CAN has very strong error detection, error signalling, retransmission and fault-confinement mechanisms, but it should not be described as a conventional forward-error-correction system that mathematically reconstructs corrupted data bits.

CAN controllers use several mechanisms to identify faults:

Bit Monitoring: The transmitter compares the bus level with the bit it attempted to send.
Bit Stuffing Check: Violations of the CAN bit-stuffing rules are detected.
CRC Check: The receiver verifies the frame's cyclic redundancy check.
Form Check: Fixed-format areas of the CAN frame are monitored.
ACK Check: The transmitter checks whether another node acknowledged the frame.

When an error is detected, CAN nodes can transmit an Error Frame, causing the damaged message to be rejected. The sender can then automatically retransmit the message according to the controller's CAN protocol operation.

What are Error Active, Error Passive and Bus-Off?

CAN controllers maintain transmit and receive error counters. These counters prevent a faulty node from continuously disrupting the entire network.

Error Active: The node operates normally and can actively signal detected errors.

Error Passive: After accumulating sufficient errors, the node's ability to disturb normal network traffic is restricted.

Bus-Off: A severely faulty transmitter eventually removes itself from active bus communication.

This fault-confinement mechanism is one of the important reasons CAN has remained useful in machines and distributed electronic control systems.

What are CAN_H and CAN_L?

High-speed CAN commonly uses a two-wire differential physical layer. The two communication conductors are called CAN_H and CAN_L.

The receiver evaluates the voltage difference between the two conductors rather than relying on one signal wire referenced directly to ground. Differential signalling provides good immunity to common-mode electrical interference.

This is valuable in machinery containing contactors, VFDs, servo amplifiers and other fast-switching power electronics. Correct shielding, grounding and cable routing are still necessary; differential signalling cannot compensate for every poor EMC installation.

How is a CAN bus terminated?

A high-speed CAN network is normally arranged as a linear bus, with approximately 120 Ω termination at the two physical ends of the main trunk.

A 120 Ω resistor should not be installed at every node. With two normal end terminators connected in parallel, an unpowered network will often measure close to 60 Ω between CAN_H and CAN_L, provided other circuits do not significantly affect the measurement.

Long uncontrolled star branches and excessive stubs can cause signal reflections. At higher bit rates, branch lengths become especially important.

Does a CAN bus provide device power?

Basic CAN does not define device power distribution. CAN_H and CAN_L are communication conductors, not the normal power supply for the controller or field device.

Industrial CAN nodes may receive 24 VDC from an industrial power supply. Certain higher-level systems built on CAN can define additional power conductors or connector rules, but this is not a feature of the basic CAN data-link protocol itself.

How fast can Classical CAN operate?

Classical high-speed CAN supports nominal bit rates up to 1 Mbit/s. The usable rate in a real installation depends on total cable length, transceiver design, topology, oscillator tolerance and timing configuration.

As a general rule, longer CAN networks require lower bit rates. Propagation delay matters because all nodes participating in arbitration must observe consistent bus states within each bit time.

For this reason, a universal CAN distance should not be quoted without also specifying the intended bit rate and network topology.

What is the difference between CAN and CANopen?

CAN defines the lower-level frame, arbitration and error-management mechanisms. It does not by itself specify that a particular drive speed value must appear under a particular message identifier.

CANopen is a higher-layer communication system built on CAN. It adds standardized concepts such as the Object Dictionary, PDOs, SDOs, NMT services and device profiles.

A product marked “CAN” is therefore not automatically a CANopen device. Raw CAN communication and CANopen communication need to be distinguished during system integration.

How is CAN used with industrial sensors?

Intelligent industrial sensors can transmit pressure, temperature, angle, load or position information directly through CAN or a CAN-based higher-layer protocol.

A conventional 24 V PNP or NPN proximity sensor, however, is not automatically a CAN node. It normally connects to a PLC or remote-I/O input, and the controller can then distribute that information over the CAN network.

Can encoders communicate over CAN?

Yes, when the encoder supports a CAN-based interface. Some absolute encoders are available with CANopen communication and can provide digital position information directly to the control system.

A conventional incremental A/B/Z encoder is different. Its electrical encoder output signal may be TTL, HTL or RS-422 differential signalling without being CAN communication.

An RS-422 line-driver encoder produces pulse pairs such as A/A− and B/B−. A CANopen encoder instead transmits digital position information inside CAN messages.

Is CAN used in servo systems?

CAN-based protocols are used with servo systems for status monitoring, parameter access, position or velocity commands and general drive control.

CANopen servo drives are common in many motion-control architectures. Applications requiring extremely short cycle times and tightly synchronized multi-axis operation may instead use faster dedicated motion networks such as EtherCAT.

Is CAN used with VFDs and motor control?

CAN or CANopen-compatible AC drives and VFDs can exchange run commands, speed references, status words, motor-current information, fault codes and parameters with a PLC or motion controller.

The presence of a CAN transceiver alone does not guarantee interoperability. The controller and drive still need compatible higher-layer communication, bit rate and message or object mapping.

How is CAN used with PLC and HMI systems?

A CAN or CANopen-equipped PLC can communicate with remote I/O, servo drives, encoders and other intelligent field equipment over one bus.

Operating information can then be presented on an HMI panel. The HMI does not necessarily require its own CAN port; the PLC or a gateway can make CAN network data available through another communication interface.

The same process and alarm information can be forwarded to a SCADA system through a PLC, controller or protocol gateway.

Is CAN used in robotics?

CAN-based communication can be found in mobile robots, AGVs, auxiliary robot axes and many other industrial robotics subsystems.

A robot's primary high-performance servo network may use another technology, while the gripper, sensors, auxiliary axis or peripheral equipment communicates through CAN or CANopen. Mixed-network machines are common in industrial automation.

How can motors, switchgear and electrical noise affect CAN?

Differential CAN signalling provides good noise immunity, but poor EMC installation can still cause errors.

The CAN cable should not be routed for long distances directly beside high-current motor cables, contactor outputs or switchgear power conductors.

In cabinets containing large VFDs or servo amplifiers, correct twisted-pair cable, grounding, shielding and separation between communication and power wiring are important for stable operation.

What is CAN FD?

CAN FD — CAN with Flexible Data-rate was introduced by Bosch in 2012 to extend the data capacity and throughput of Classical CAN.

A Classical CAN frame carries up to 8 data bytes, while CAN FD supports up to 64 data bytes in one frame. CAN FD can also switch to a higher bit rate during the data phase when the network and transceivers support it.

This improves efficiency for larger process data, firmware transfer, diagnostics and other applications that would otherwise require many Classical CAN frames.

What is CAN XL?

CAN XL is the third major generation of CAN data-link technology. It preserves CAN concepts such as non-destructive arbitration while substantially increasing data throughput and payload capacity.

Current CAN XL specifications support data-phase rates up to 20 Mbit/s and frame payloads up to 2048 bytes.

CAN XL is intended to reduce the performance gap between CAN FD and Ethernet-class embedded networking while retaining important CAN bus-access characteristics.

Is CAN a cybersecurity or functional-safety protocol?

No. CAN's CRC, arbitration and fault-confinement mechanisms improve communication reliability, but they should not be confused with cybersecurity or certified machine safety.

Basic Classical CAN frames do not inherently provide encryption or cryptographic source authentication. Systems requiring secure communication need appropriate higher-layer security mechanisms.

Similarly, safety-related functions must be implemented through appropriate safety architectures and certified protocols rather than assuming that CAN's error detection alone creates a safe control system.

Why does a CAN network fail to communicate?

Start with the physical bus. Check CAN_H and CAN_L wiring, cable continuity, termination and the power supply to every node.

Next verify that every node uses the same nominal bit rate and compatible bit timing. A 500 kbit/s controller cannot correctly communicate with another node configured for 250 kbit/s on the same bus.

If physical communication exists but the required process data is missing, inspect identifier filters, application message mapping or, in a CANopen system, node ID, PDO, SDO and NMT configuration.

Continuous Error Frames can point to incorrect termination, excessive stub length, electrical noise, ground-potential problems, bit-rate mismatch or a faulty CAN transceiver.

Also check the 24 VDC power supply. A field module repeatedly resetting because of low or unstable supply voltage can look like a communication fault even when the CAN wiring itself is correct.

Practical CAN troubleshooting checklist

1. Are CAN_H and CAN_L connected to the correct terminals?

2. Is approximately 120 Ω termination installed at both physical ends of the main bus?

3. Are all nodes configured for the same bit rate?

4. Is the network arranged as a suitable linear bus with short stubs?

5. Are node supply voltages stable?

6. Are CAN identifiers, filters or CANopen node settings correct?

7. Have Error Active, Error Passive and Bus-Off diagnostics been checked?

8. Is CAN cabling separated correctly from motor, VFD and high-power switching wiring?

Related CAN and Industrial Communication Guides

CANopen · Industrial Communication · EtherCAT · Modbus · ControlNet

Related Field and Automation Pages

PLCs · HMI Panels · SCADA · Sensors · Encoders · Servo Systems · Motion Control · Industrial Robotics · AC Drives and VFDs · Power Supplies · Switchgear · Controllers


Refine Search