Terminology
Back to Top-
Get a better understanding of CAN terminology
The Kvaser CAN Dictionary explains key terminology related to Controller Area Network (CAN) systems, including protocol types, physical layers, and error-handling mechanisms. It covers standard and extended CAN, higher-layer protocols like CANopen and J1939, and technical terms like DLC, error frames, and synchronization. This resource is ideal for understanding CAN technology in automotive and industrial applications. For more details, visit Kvaser CAN Dictionary.
-
Changing terminology from t programming to t script
We recently updated the terminology from ‘t programming’ to ‘ t script‘. The change highlights the embedded scripting capability of the language, which allows users to directly interact with hardware events and control CAN bus communication at a low level. This shift in terminology emphasizes its use as a powerful tool for automating and customizing tasks in embedded systems, leveraging a C-like syntax for simplicity and efficiency​. Due to this recent change of terminology, previous documents and publications might still have the ‘t program’ or ‘t programming’ terminology in it, while newer publications will use ‘t script’ or ‘scripting capabilities’.Â
-
CAN Terminology changes
CAN has undergone many updates since it was launched in 1986. As a result, CAN in Automation (CiA), the international users’ and manufacturers’ group, has introduced new terms to describe the different CAN protocols now available:
- CANclassic (abbreviated to CAN CC)
- CANflexible data rate (abbreviated to CAN FD)
- CANextended data-field length (abbreviated to CAN XL)
CiA also specifies and maintains two application protocols that run on CAN:
- CANopen (application running on CANCC)
- CANopen FD (application running on CANFD)
Throughout the Kvaser website, when the term CAN is used, we refer to CAN classic. Similarly, when CANopen is mentioned, we refer to CANopen Classic.