CAN & LIN communication protocols  and AUTOSAR

Explore CAN as a two-wire, bus-based, message-oriented protocol without a clock, enabling multi-master communication with identifiers for message types, where collisions may occur and speed depends on bus length.

Explore the outstanding features of the can protocol, including priority-based nondestructive arbitration, differential signaling, standard and extended frame formats, and robust error handling across the data link and physical layers.

Understanding the differences between standard and extended frame formats in CAN, including identifiers, data length code, dominant bits, and when to extend the format to accommodate more data.

Explore how CAN and LIN networks resolve simultaneous access through arbitration, where dominant bits determine bus ownership and nondestructive publication prevents data loss in multinode transmissions.

Learn how arbitration resolves bus conflicts, and how error frames and overload frames detect message and bit errors through CRC checks, acks, dominant bits, and stuffing.

Explore fault confinement in CAN communication within AUTOSAR, focusing on how repeated transmission attempts, interceptions, and message reinforcement control bus activity.

Explore how to interface a microcontroller with a CAN bus, including node integration, bus arbitration with dominant and recessive signals, ISO standard considerations, and practical programming implications.

Explore lin network communication, detailing how a master initiates the bus, slaves respond, and synchronized frames with PIV identifiers govern data transmission and slot-based scheduling.

Explore LIN identifiers and frame structure, detailing eight-bit identifiers, data bytes, and how 64 identifiers enable 16 streams, with diagnostic data reserved for user defined extension.

The lecture explains calculating the protected identifier (PID) in the LIN protocol, noting the content is defined by the application developer and demonstrating parity bit generation from the identifier.

Explore checksum calculation in CAN and LIN communication, contrasting classical and enhanced methods that protect data by summing bits and bytes, with practical examples.

Explore enhanced checksum calculation for CAN and LIN communication, comparing it to the classical method and outlining stepwise value additions used to derive the final checksum.

Explore the four to five frame types in can and lin protocols, including unconditional frames with unique responses, diagnostic frames, and master frames, illustrating how frames and responses are matched.

Learn to build a can network using an ARM LPC1768 controller with MCP2551 transceiver, covering hardware setup, USB connectivity, and online or offline compiling.

Practice creating a project in the online compiler, compiling, building, and deploying a program via mbed APIs, including connecting the hardware and downloading the build.

Debug and deploy mbed APIs by compiling and downloading a bin file to hardware, dumping data, and observing LED blinking patterns to verify firmware behavior.

Debug and deploy mbed APIs within the CAN and LIN AUTOSAR context, showing how to connect with API outputs, manage variables, and display episodes on the embed homepage.

Connect analog sensors to channels via the analog input API, configure digital outputs and inputs with their APIs, and use the bus API to operate multiple pins together.

Explore debugging and deploying mbed APIs to manage multiple digital inputs and outputs, connect to motors, and build a network with input-change handling and deliberate delays.

Explains debugging and deploying mbed APIs for a can network project, using an online compiler and embed mode, and builds a two-node can bus with a counter displayed on canvas.

Debug and deploy mbed APIs using an online compiler, understand the CAN code and API, and implement a two-part project with a MCP2551 transceiver, canvas display, and serial output.

Learn how to implement basic can code and set up an MCP2551 transceiver network circuit, wire the pins, and transmit and receive can messages with identifiers.

Explore transmitter and receiver node programming in CAN and LIN networks within AUTOSAR, wiring transceivers, configuring pins 29 and 30, and validating bus communication.

Analyze how CAN data is captured and viewed in the Tera Term software tool, including how the signal is printed and interpreted to understand the data flow.

Learn how to send switch status over a CAN bus by configuring signals, wiring hardware, and validating transmitted data while monitoring zero status and message flows.

Explore bus master, a freeware tool for CAN and LIN protocol analysis, cam node simulation, CAN network simulation, and test automation for diagnostics.

Create a controller area network database in BusMaster to map messages to signals, with IDs and signal ranges, then analyze and transmit signals on the bus.

Analyze CAN bus data using Tera Term via the serial port on the mbed LPC1768, performing signal and message analysis, and simulate bottlenecks with a bus monitor.

Install BusMaster to support can and lin communication within autosar workflows, download the latest version, and complete setup steps for seamless integration.

Build a can network with bus master, create a can database for door, seat belt, wheel speed, and dashboard signals, and simulate nodes that control lamp and buzzer.

Learn to create an abs can node and simulate a can network using bus master, configure events, and send wheel speed messages every second to verify the bus.

Explore simulating a bcm node in a CAN bus environment, sending door status and seat belt status every second, and preparing dashboard module to compute vehicle speed and control indicators.

The lecture demonstrates simulating a dashboard issue in can network by evaluating seat belt and door status and wheel speed to trigger buzzer and lamp via message events.

Explore MATLAB and Simulink for modeling, analyzing, and simulating dynamic systems using block-level models. Learn model-based design to develop embedded control and signal processing algorithms without programming language knowledge.

Learn how to set up Matlab and Simulink hardware support packages for model-based embedded design, including installing support for Raspberry Pi and Arduino, with internet connectivity and login steps.

Explore how to install and access Simulink Arduino blocks, navigate digital and analog input/output blocks, motor control, can bus interfaces, sensors, and IoT blocks to build and simulate Arduino projects.

Build a CAN network using Simulink on an Arduino platform to drive two CAN nodes with an MCP2515 controller and a seven-segment display, wiring a sensor to show gear information.

Interface the MCP2515 CAN controller with an Arduino Uno using the SPI interface, configure CAN arbitration and error handling, and wire the exact pins for reliable CAN bus communication.

Explain pin connection details for the MCP2515 can controller with Arduino Uno, including grounding and power, and introduce can simulation models (plasma and receiver) to observe data on the canvas.

Explore FlexRay, a high-performance automotive network with dual wires and a redundant channel that surpasses CAN and LIN in speed and determinism, enabling drive-by-wire systems.

Discover how Autosar standardizes automotive software architecture as an open system for developing ECU applications, enabling reuse, interoperability, and reduced development time across OEMs, suppliers, and vendors.

Explore Autosar terminologies and automotive software architecture, covering microcontrollers, hardware and software drivers, internal versus external devices, and CAN and LIN protocols for communication between electronic controls.

Explore Autosar terminologies by examining interfaces, abstraction layers, and a generic API that accesses hardware, and learn how handlers, managers, and libraries support CAN networks.

Explore the automotive application scope of Autosar, detailing CAN and LIN networks, sensors and actuators, microcontroller constraints, and real-time program execution from flash memory.

Explore the three major layers of the basic software architecture, where swcs communicate through middleware and sensor data flows through the BMW model to Audi.

Explore microcontroller drivers that provide memory, communication, and timer interfaces, enabling a software layer mapped to hardware devices and supporting hardware abstraction in CAN and LIN and AUTOSAR.

Access the microcontroller abstraction layer to reach internal registers via the application, then ADI and DSW models, through the angle layer, delivering hardware independent access to basic software modules.

The ecu abstraction layer provides uniform access to can interface, memory, and io, hiding hardware details behind a driver API and enabling hardware independent software.

Explore how the AUTOSAR service layer delivers operating system functionality, vehicle network communication and management, memory and diagnostic services (including the diagnostic communication manager, DCM) to support applications.

Explore the AUTOSAR service layer architecture, from hardware access by the OS to the runtime and application layers, and examine the diagnostic event manager, DCM, and network management security states.

Explore complex device driver in AUTOSAR, extending standardized ECU architecture to support non standardized device dialogues. See how complex devices integrate non standardized functions like ABS and ESP within constraints.

Examine the non-autosar workflow and its contrast with autosar, detailing how dbc and lda files flow between oems and suppliers, and how software components are wired and distributed across ecus.

Explore Autosar templates and software component, resource, and system descriptions that guide ecu executable generation within OEM and Tier 1 workflows.

Learn how blind-spot detection uses lidar and ultrasonic sensors and software components to trigger a light or buzzer, via intra-ECU and inter-ECU communication.

Explore AUTOSAR interfaces: generic interfaces for software component communication; abstraction layer interfaces; and standardized interfaces predefined by AUTOSAR for accessing service layer capabilities.

Discover how bsw drivers power the blind spot detection system, enabling can and can bus communication across the microcontroller abstraction layer, digital input/output, can driver model, and interface model.

Explore Autosar compliant project development by generating xml, c, and h files and implementing the temperature controller, allied control, and coil control software components with ports, interfaces, runnables, and mappings.

Create and name three application software components for an Autosar project using the tool: temperature control, LED control, and coil control, then explore adding ports in the next video.

Add ports to software components by distinguishing provided and required ports, name them with P_ prefixes, and connect components using sender-receiver and client-server interfaces for LED, coil, and temperature control.

Declare basic data types and variables to enable data exchange via sender-receiver interfaces. Configure boolean LED on/off and unsigned int variables for on/off and temp read across devices.

Create AUTOSAR port interfaces to enable communication between software components using sender-receiver and client-server interfaces. The video demonstrates configuring interfaces, operations, and implementation data types, naming conventions, and wiring ports.

Create and configure runnables within Autosar software components, assign ports and data axes, and implement synchronous server calls in the Cordoba tool to enable inter-component communication.