- 0USD 0.00
- CAN HardwareBy Kvaser
- CAN SoftwarePartner Directory
- About CAN
- SupportKvaser Help Support
- Kvaser Career00
- About Us
- Kvaser Career
This course has provided an introduction to the Classical CAN bus. We have discussed the physical layer, the message structure, error frames, and more.
This information describes CAN as it was known from the original adoption in 1986 until 2011 – what is now being called “Classical CAN”. In 2011, however, Bosch began development of a new iteration of CAN – dubbed “CAN FD”. The “FD” stands for “flexible data rate”.
Since 2011, CAN FD has been adopted as the next generation of CAN, seeing continued refinement in SAE specification meetings and implementation by chip and tool makers.
To learn more about CAN FD – what it is and what it can accomplish – please continue on to take the course: “CAN FD” [COMING SOON].
You may also be interested to learn more about “Higher Layer Protocols”. As we’ve seen, the CAN standard defines the hardware (“the physical layer” – there are several) and the communication on a basic level (“the data link layer”). But, in essence, the CAN protocol itself simply specifies how to transport small packets of data from point A to point B using a shared communications medium. In order to manage the communication within a system, a higher layer protocol (HLP) is required.
Higher Layer Protocols can be standardized for widespread use, or proprietary.
To learn more about CAN FD, visit the CAN FD page.
To learn more about Higher Layer Protocols, visit the Kvaser education page.