- Beginning of the page
Designing and Developing Automotive Networks and Networked ECUs
Vector tools and services to support you in designing and developing networks and networked ECUs – especially for simulation, analysis and testing of network communication and for model-based electric/electronic development from architecture design to series production.
The development of distributed systems begins with partitioning of the overall system, followed by the definition of the network communication and concluding with the implementation of individual ECU functions.
Vector's refined tools and complex services support you in designing, simulating, analyzing and testing network communication.
Consistent use of uniform development tools helps you avoid incompatibility losses. You can promptly detect and correct potential problems, even during evaluation and integration phases. Development processes for distributed systems involve OEM and supplier engineers working together on the same project.
In this context the defined database serves as a foundation for development. It ensures that all communication-related parameters of an individual ECU or an entire network are always available in an up-to-date and redundancy-free form throughout development.
Design, Management and Documentation of Electric/Electronic Systems
Only one highly integrated engineering environment from requirements to soft- and hardware architecture to the wiring harness:
Development, Test and Analysis of Entire ECU Networks and Individual ECUs
Only one comprehensive software tool for all development and testing tasks:
- Analysis of network communication
Simulation of entire networks and remaining bus simulation
Stimulation to detect and correct error situations early in the development process
Easy automated testing of ECUs and entire networks
Model-Based E/E Development with PREEvision
From Architecture Design to Series Production
PREEvision offers a comprehensive modeling language to describe all aspects of E/E systems. All engineers involved in the development process find tailored diagrams and editors for their work. And all in one integrated tool. What’s special about PREEvision: Everybody involved works in the same development environment, with the same data, in the same data model. In here, the complete e/e system is designed, managed and documented. For optimum collaboration within globally dispersed teams, PREEvision offers multiple functions.
E/E Development for Future Vehicle Innovations
An integrated, model-based approach from architecture design to series production
The development of modern electric/electronic (E/E) architectures is a challenge today more than ever. Numerous development criteria must be taken into account, and classic vehicle domains need to be linked to new functions in the areas of driver assistance and autonomous driving. Completely new functions that are no longer limited to just the vehicle, but are also provided as services in the "IT backend" outside the vehicle, are emerging here.
The introduction of service-oriented architectures and powerful domain computers, Ethernet to on-board communication, connectivity gateways and, last but not least, increasing safety and security requirements represent profound and radical changes for every development organization. To master these complex development tasks successfully as a team, a development platform and E/E database, which can be implemented in different ways, are required.
Translation of a German publication in "ATZ elektronik", issue 6/2016
Universal Management of Requirements in Functional Development
MAN Diesel & Turbo SE uses PREEvision as its requirements management tool in the functional development of fourcycle engines. Around 50 engineers work in parallel on current and future generations of controllers.
They define the interfaces between functions and establish parameters for later engine calibration. PREEvision currently manages around 1500 individual requirements for approx. 20 primary engine functions (I/O, parameters, test specifications). In productive application cases, requirements management, the test specification and the software architecture are currently generated by toolkit elements that are later reused.