Networks for Data Communication

Specialized internal communications networks interconnect components inside automobiles, buses, trains, industrial or agricultural vehicles or aircrafts. Special requirements for vehicle control such as assurance of message delivery, of non-conflicting messages, of minimum time of delivery, of low cost, and of EMF noise resilience, as well as redundant routing and other characteristics mandate the use of less common networking protocols. Protocols include Controller Area Network (CAN), Local Interconnect Network (LIN),  Media Oriented System Transport (MOST), FlexRay and others. Also conventional computer networking technologies such as Ethernet and TCP/IP are established in automotive engineering by now. For aircrafts Vector offers implementations of AFDX and ARINC 429.


Key visual CAN / CAN FD Solution

CAN (Controller Area Network) technology is used in the automotive, industrial automation and aerospace industries, in which OEMs and suppliers are confronted with many types of challenges. Vector supports you with professional CAN (FD) software tools, network interfaces, AUTOSAR basic software and worldwide services.

More Information


MOST (Media Oriented System Transport) is a serial communication system for transmitting audio, video and control data via fiber-optic cables. This multifunctional, high-performance multimedia network technology based on synchronous data communication requires professional software tools and hardware interfaces.

More Information


Development engineers and technicians need flexible read and write access to variables and memory contents for the optimum parameterization of ECUs. For this purpose, the CAN Calibration Protocol (CCP) was developed in the 1990s as an OEM-independent standard. After additional bus systems such as LIN, MOST and FlexRay became established in ECU networking, CCP reached its limits due to the restriction to the CAN bus, which led to the development of the XCP protocol. Like CCP, the "Universal Measurement and Calibration Protocol" (XCP) originated from ASAM and was standardized in the year 2003. Vector played a key role in its release. As a two-layer protocol, it consistently splits the XCP protocol from the transport layers, and it takes a Single-Master/Multi-Slave approach.

More Information about CAN-based protocols and XCP