Connectivity software

managementsimulationcontrol

The enormous growth in connectivity, assistants, comfort functions, infotainment features and many other functions, such as semi-autonomous/autonomous driving or software updates over-the-air, which has been taking place for some time, is clearly visible within vehicle electronics. Not only is the degree of networking of the control units in the vehicle increasing, but the vehicle itself is increasingly networking with its environment, often referred to as V2X communication (vehicle-to-X - communication). The prerequisites for this are high-performance E/E vehicle architectures (electric/electronic). These are largely based on heterogeneous networking concepts. Depending on the domain (powertrain, comfort, infotainment, backbone...) or sub-segment (sensors, actuators...), different bus systems and transmission protocols are used. This places enormous demands on the test equipment for individual ECUs or for an ECU network. Operating an ECU or a network outside the vehicle is not possible without a residual bus simulation. All signals, information and protocols necessary for the fault-free operation of the DUT must be made available on the different bus systems. Current vehicles have more than 100 ECUs connected to different bus systems such as LIN, CAN/CAN FD/CAN XL, FlexRay or Automotive Ethernet. On the one hand, complex ECUs require several thousand signals whose sources are located on different bus systems. On the other hand, higher protocols such as transport protocols for diagnostics, network management, SecOC (Secure Onboard Communication), SOME/IP (Scalable Service-Oriented Middleware over IP) are required.