[Vlog] Want to Understand CAN Interface and CAN NM Layers? The Layered Architecture of CAN BUS Protocol Stack has All the Answers
This is the second video of our video series on CAN Bus Protocol Stack.
Did you miss out the first video, watch it here https://www.youtube.com/watch?v=qp667nRFHBc
In our first video on CAN Bus software stack, we discussed the need for such an in-vehicle networking protocol and how CAN BUS Protocol Software works.
However, the complete understanding of CAN Bus software can be acquired only when you dissect its layered architecture.
For an automotive application to fetch vehicle data or to interact with other applications, a gamut of software modules is required.
CAN BUS Software stack is a bundle of all such modules that make it an invisible hero of the in-vehicle networking (ECU communication).
In this video, we will learn about several of these CAN Bus software modules in brief.
Interested in detailed understanding of the CAN Bus software architecture? Check out our blog /blog/embedded-blog/what-is-can-protocol-stack-why-its-critical-software-solution-for-ecu-communication
Our Latest CAN Bus Protocol Stack Video Will Cover:
- Overview of the CAN BUS software architecture
- Application Layer of the CAN Bus Protocol Stack
- CAN Network Management (NM) Layer and CAN Interface (IF) Layer (CAN Software Stack)
- UDS (ISO 14229) Based Flash Bootloader
- ISO Transport Protocol (ISO 15765) Layer
- CAN Drivers
As CAN Bus software is at the heart of ECU communication, automotive embedded engineers should have its crystal clear understanding. This video is great way to start building this understanding.
Even for the business managers and decision makers, this video will aid in understanding the pain points of their customers.