CAN Bus
A serial communication bus standard widely used in automotive electronics that employs differential signaling and offers strong resistance to electromagnetic interference; it is used for communication among vehicle ECUs, sensors and actuators.
Timeline (last 90 days)
CAN bus (Controller Area Network) is a widely used serial communication bus standard in automotive electronics that uses differential signal transmission, and a raw CAN frame contains only an ID and a payload of up to 8 bytes.
In the project architecture, a Raspberry Pi decodes raw signals from the VCU over the CAN bus, downsamples them to about 10Hz, and then publishes them via the MQTT protocol to the phone in the cockpit.
The native app directly uses the car's SoC, memory and network modules, can stay resident in the background, start with the vehicle, and access vehicle CAN bus data (such as speed, steering angle and driving mode).
On an articulated bus, the CAN bus is responsible for connecting the articulation angle sensor, steering wheel angle sensor, vehicle speed sensor, and modules such as braking and engine control into a real-time network, with data broadcast at millisecond-level latency.
An articulation angle sensor continuously monitors the angle between the front and rear sections; once it exceeds a safety threshold, the system limits engine power or triggers an alarm to prevent the vehicle from folding.
Typical implementations of real-time control rely on real-time operating systems (such as FreeRTOS, Linux with the PREEMPT_RT patch), deterministic communication (such as EtherCAT, CAN bus), and periodic control loops (commonly 100Hz–1kHz).
The CAN bus has no native authentication or encryption mechanism, and any node that can physically or logically access the bus can send arbitrary messages.
Anomalies on the CAN bus are often not reflected in individual messages but are hidden in the patterns of how message sequences evolve over time.
The paper employs a lightweight Transformer encoder to learn the temporal evolution of CAN signals, leveraging the attention mechanism to capture long-range temporal dependencies and contextual associations.
The CAN bus was originally designed by Bosch in the 1980s for intra-vehicle communication, adopting a broadcast-based multi-master architecture that relies on message IDs rather than addresses to filter information.
4 more timeline events
All Facts (14)
CAN bus (Controller Area Network) is a widely used serial communication bus standard in automotive electronics that uses differential signal transmission, and a raw CAN frame contains only an ID and a payload of up to 8 bytes.
50%UnverifiedIn the project architecture, a Raspberry Pi decodes raw signals from the VCU over the CAN bus, downsamples them to about 10Hz, and then publishes them via the MQTT protocol to the phone in the cockpit.
50%UnverifiedThe native app directly uses the car's SoC, memory and network modules, can stay resident in the background, start with the vehicle, and access vehicle CAN bus data (such as speed, steering angle and driving mode).
50%UnverifiedOn an articulated bus, the CAN bus is responsible for connecting the articulation angle sensor, steering wheel angle sensor, vehicle speed sensor, and modules such as braking and engine control into a real-time network, with data broadcast at millisecond-level latency.
50%UnverifiedAn articulation angle sensor continuously monitors the angle between the front and rear sections; once it exceeds a safety threshold, the system limits engine power or triggers an alarm to prevent the vehicle from folding.
50%UnverifiedTypical implementations of real-time control rely on real-time operating systems (such as FreeRTOS, Linux with the PREEMPT_RT patch), deterministic communication (such as EtherCAT, CAN bus), and periodic control loops (commonly 100Hz–1kHz).
50%UnverifiedThe CAN bus has no native authentication or encryption mechanism, and any node that can physically or logically access the bus can send arbitrary messages.
50%UnverifiedAnomalies on the CAN bus are often not reflected in individual messages but are hidden in the patterns of how message sequences evolve over time.
50%UnverifiedThe paper employs a lightweight Transformer encoder to learn the temporal evolution of CAN signals, leveraging the attention mechanism to capture long-range temporal dependencies and contextual associations.
50%UnverifiedThe CAN bus was originally designed by Bosch in the 1980s for intra-vehicle communication, adopting a broadcast-based multi-master architecture that relies on message IDs rather than addresses to filter information.
50%UnverifiedCAN bus uses a CSMA/CA (Carrier Sense Multiple Access with Collision Avoidance) mechanism, arbitrating priority through message IDs, where the highest-priority node wins the bus and other nodes automatically yield.
50%UnverifiedPure time-triggered systems have no natural collision arbitration mechanism by design, unlike event-triggered systems (such as CAN bus) that handle collisions through priority arbitration.
50%UnverifiedIn desktop-level projects, CAN bus or SPI bus can provide millisecond-level deterministic communication.
50%UnverifiedThe project's controller uses an ESP32 and simultaneously employs two CAN buses, one implemented via the ESP32's native TWAI interface and the other extended via SPI.
50%