Product |
Details |
ASM 9.3 and ModelDesk 5.1 |
- Probabilistic sensor model for radar applications
- Improvements of scenario definition (bumper-to-bumper, distances, length of road/route)
- Integration of vehicle start procedure for BEV demo
|
AutomationDesk 6.1 |
- New XML file format for the serialization of projects and libraries:
- Improved readability: Element names in AutomationDesk used for element names in the XML file and separation of functionality and visualization information in different files
- Collaboration support: Fine-grained import and export down to single blocks as preparation for detailed versioning
- Ease of use: Implicit migration to the new XML format without migration effort
- Enhanced editor for Python code:
- Improved debugging: Visualization of syntax errors and invalid references to data objects plus comprehensive debugging support in tooltips
- Improved usability: Local dialogs for Find & Replace with instant highlighting of found items
|
Bus Manager 6.3 (ConfigurationDesk 6.3) |
- Support of global time synchronization
- Support of static container PDUs
- Enhanced support of secure onboard communication (SecOC)
- Support of AUTOSAR 4.4.0
- CAN frame gateway (for convient use of gateways without Simulink®)
|
ConfigurationDesk 6.3 |
- Column width changeable with mouse action
- Automation interface enhancements:
- Clear build results
- Determination of all working views containing a particular element
|
ControlDesk 7.0 |
- Bus Navigator: Wireshark decoder support for Ethernet monitoring
- Ethernet Bus Monitoring device: Support for signals of UDP Ethernet PDUs
- Support of AUTOSAR 4.4 for PC Bus Interfaces (CAN, CAN FD, LIN, and Ethernet)
- ECU Diagnostics: Support of CAN FD
|
dSPACE FlexRay Configuration Package 4.3 |
- Minor enhancements and bug fixes
|
ECU Interface Base Package 2.5 |
- Extended SCALEXIO support: Support for XCP on CAN and CAN FD with SCALEXIO systems
|
MotionDesk 4.4 |
- Advanced lighting: approx. 100 vehicles equipped with light objects
- Status monitoring and control of SensorSim instances in MotionDesk
|
Platform API Package 3.1 |
- Use of XIL MAPort in VMware to access VEOS simulation platforms and execute multiple simulations and test executions in parallel
- MAPort-based stimulation and execution of Real-Time Testing scripts on 64-bit virtual processing units (VPUs) in VEOS
|
Real-Time Testing 4.1 |
- Use of Real-Time Testing in VMware to access VEOS simulation platforms
- Execution of Real-Time Testing scripts on 64-bit VEOS VPUs
|
RTI CAN Blockset 3.4.8 |
- Minor enhancements and bug fixes
|
RTI CAN MultiMessage Blockset 5.2 |
- Support of AUTOSAR 4.4.0
- Minor enhancements and bug fixes
|
RTI LIN MultiMessage Blockset 3.2 |
- Support of AUTOSAR 4.4.0
- Minor enhancements and bug fixes
|
RTI FPGA Programming Blockset 3.7 |
- Support of new FPGA boards:
- DS6601 FPGA Base Board
- DS6602 FPGA Base Board
- Remote FPGA build:
- Use of seperate PCs to execute the FPGA build so that the PC used for modeling is not blocked
- The build process can be observed with a dedicated tool
|
Sensor Simulation 1.1 |
- Support of fish-eye lenses (>180°) and high-order polynoms
- Multiple instances on single GPUs for optimizing GPU utilization
- Optimization of shared memory interface in terms of speed and bandwidth
- Definition and enhancements to sensor material attributes for about 1,000 objects to address radar and lidar sensor simulation
- Improved Sensor Simulation demo project to represent more capabilities of sensor simulation
- Support of radar and lidar simulation modules, V-ESI unit (solutions)
|
SYNECT 2.7 |
- Validation:
- To save HIL time, the test execution can be separated from the postexecution test result evaluation
- Global execution queues make it possible to distribute test executions from all running projects on all available simulation systems
- Option to associate execution plans with a test cases query. Therefore, the set of test cases to be executed can be dynamically determined at the actual test execution time
|
SystemDesk 5.3 |
- Import of multicore OS configurations
- Integration of basic software modules expecting a multicore OS
- Further supported Microcontroller Abstraction Layer (MCAL) modules for VEOS: Icu, Gpt, Wdg, Adc
- Initialization of NV Data for V-ECUs on MCAL level
- Support of Adaptive AUTOSAR features, such as data types, service interfaces, manifest files, etc.
- Support of AUTOSAR R4.4.0, R4.3.1, R4.3.0, R4.2.2, R4.2.1, R4.1.3, R4.1.2, R4.1.1, R4.0.3, and R4.0.2
|
VEOS 4.4 |
- Multicore support: Possibility to create V-ECUs for multicore ECUs
- Further supported MCAL modules for VEOS: Icu, Gpt, Wdg, Adc
- Execution of Real-Time Testing scripts on 64-bit VEOS VPUs.
|
|
|
MATLAB® support |
- R2017b
- R2018a
- R2018b
- R2019a
|
Operating system support |
- Windows® 10 Enterprise 2016 LTSB (64-bit)1)
- Windows® 7 SP1 (64-bit)
|