For developing complex system architectures
- Support of graphical modeling for AUTOSAR systems
- Exchange and integration of software descriptions to improve OEM/supplier processes
- Convenient coupling with TargetLink®
- Integration of software architectures into ECUs and
RTE generation - Early detection of functional errors and verification
of distributed systems
NEW: SystemDesk 3.1
General |
- Modeling according to the current AUTOSAR version R3.2
- Even more convenient coupling with dSPACE TargetLink, e.g., by automated container management
- Support of update scenarios by smart reimport mechanisms
- Convenient handling of growing projects by several new usability features like multiselection and detecting of unreferenced elements
- Enhanced verification of SystemDesk models by code coverage analysis
- Improved options for setting up your dSPACE tool chain by the new product packages
|
Modeling |
- Support of AUTOSAR 3.2, AUTOSAR 3.1 and AUTOSAR 3.0
- Improved reimport
- Signal mapping of data elements of composition ports
- Modeling extensions (e.g., compatibility of partial record types, SWAddrMethods, memory sections and units)
|
| Simulation |
- Processor-in-the-loop (PIL) simulation
- Direct connection of virtual ECUs
|
TargetLink coupling |
- Automated container management
- Usability improvements such as displaying active workflow rules
|
RTE Generation |
- Multiple instantiation of software components
- Faster RTE generation
- RTE and COM generation for complex signals transferred via bus
- Further RTE extensions, e.g., support of memory mapping and mixed compu methods
|
Simulation |
- Code coverage analysis using CTC++ from Testwell with results displayed on an HTML page
- Analysis and display of RAM/ROM consumption
|
| Handling |
- Multiselection in the Project Manager and the Package Manager
- Detecting unreferenced elements and finding where elements are used
- Importing and exporting SystemDesk diagrams via XML files
|
Description
Why Model-Based Development?
Automotive software is
becoming more and more complex. This holds true for functionalities
distributed over several electronic control units (ECUs) and for single
ECUs. Better tool support is therefore needed on the system level and
the architecture level as well.
Model-based development of ECU
software and the graphical representation of the components and their
communica-tion improves the overall understanding of even complex
systems. Furthermore, the formalization of the components enable their
distribution to different developers. The automotive software
development process can also be improved by reusing application software
components. This allows manufacturers and suppliers to utilize software
modules that were already tested, thereby minimizing potential software
hazards and cutting the development workload.
Key Benefits
SystemDesk
is a software architecture tool supporting the development of
distributed automotive electrics/electronics (E/E) systems and
subsystems:
- Designing functional networks and software architectures
- Modeling systems according to the AUTOSAR standard
- Formalizing hardware topologies and network communication
- Integrating ECU code
- Generating an AUTOSAR Run-time Environment (RTE)
- Simulating a single software component or an entire ECU network offline
- Simulating a single software component or an entire ECU network
- Process support such as scripting, connection to requirement management systems, and libraries for storing reusable objects
AUTOSAR Support
SystemDesk supports the AUTOSAR standard. For example, software components can be described according to AUTOSAR, or existing components can be imported into SystemDesk for further processing. SystemDesk provides an RTE generator for generating AUTOSAR production C code.
SystemDesk RTE Generation Module
Application Areas
The SystemDesk RTE Generation Module is an add-on to SystemDesk which generates optimized RTE code. The RTE abstracts the software component layer from any implementation details of the basic software and from the hardware. It is responsible for communication between software components (SWCs) and implements the OS tasks. When the tasks and the COM signals of the ECU have been configured, the C code for the RTE implementation can be generated.
Key Benefits
As a core aspect of AUTOSAR-compliant development, the RTE enables software components to be reused in different ECUs and supports component-based, distributed development. RTE generation uses code generation features, such as optimization techniques, to minimize memory and resource consumption.
SystemDesk V-ECU Generation Module
Application Areas
The SystemDesk V-ECU Generation Module lets you model and generate virtual ECUs. The generation of non-optimized AUTOSAR RTE code is included. The built simulation system can be simulated with the dSPACE Offline Simulator.
A virtual ECU can consist of just a single software component (SWC) containing multiple functions and also of a complex AUTOSAR software architecture containing several connected SWCs. As well as simulating at the architecture level, you can simulate a single electronic control unit (ECU) model and also whole system models with several ECUs, including the specified bus communication.
Virtual ECUs can also be connected to Simulink plant models outside of SystemDesk. The resulting simulation system can be simulated with the dSPACE Offline Simulator in combination with ControlDesk Next Generation.
Further Information
Related Topics
Support
Training
Contact Information