New Features and Migration

dS

dSPACE Release

New Features and Migration

For RCP and HIL Software

Release 5.3 – March 2007

How to Contact dSPACE

How to Contact dSPACE Support

dSPACE recommends that you use dSPACE Support Wizard to contact dSPACE support. It is available:• On your dSPACE DVD at \Diag\Tools\dSPACESupportWizard.exe• Via Start – Programs – dSPACE Tools (after installation of the dSPACE software) • At http://www.dspace.com/goto?supportwizard

You can always find the latest version of dSPACE Support Wizard here.

Software Updates and Patches

dSPACE strongly recommends that you download and install the most recent patches for your current dSPACE installation. Visit http://www.dspace.com/goto?support for software updates and patches.

Mail: dSPACE GmbH Technologiepark 25 33100 Paderborn Germany

Tel.: +49 52 51 16 38-0

Fax: +49 52 51 6 65 29

E-mail: [email protected]

Web: http://www.dspace.com

Technical Support: [email protected]+49 52 51 16 38-941 http://www.dspace.com/goto?support

Important Notice

This document contains proprietary information that is protected by copyright. All rights are reserved. Neither the documentation nor software may be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine-readable form, in whole or in part, without the prior written consent of dSPACE GmbH.

© Copyright 2007 by:dSPACE GmbHTechnologiepark 2533100 PaderbornGermany

This publication and the contents hereof are subject to change without notice.

ConfigurationDesk, ControlDesk, TargetLink and CalDesk are registered trademarks of dSPACE GmbH in the United States or other countries, or both. Other brand names or product names are trademarks or registered trademarks of their respective companies or organizations.

mailto:[email protected]

http://www.dspace.com

mailto:[email protected]

http://www.dspace.com/goto?support

http://www.dspace.com/goto?supportwizard

http://www.dspace.com/goto?support

I■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■

Contents

About This Document 5

General New Features 7Supported MATLAB Releases ....................................................7Supported Operating Systems ..................................................8New Key Features ....................................................................8

New Features of dSPACE Release 5.3 (RCP and HIL Software) 11

New Features of the RTI Bypass Blockset.................................12New Features of the RTI CAN MultiMessage Blockset .............13New Features of the RTI FlexRay Configuration Package .........13New Features of the RTI LIN MultiMessage Blockset................14New Features of ConfigurationDesk .......................................16New Implementation Features of RapidPro System Used as I/O Subsystem..............................................................................17New Implementation Features of RapidPro System Used as a Prototyping ECU.....................................................................18New Features of Automotive Simulation Models and ModelDesk.............................................................................18New Features of ControlDesk .................................................20New Features of AutomationDesk ..........................................20

Migrating from Previous Releases 23Migrating the Implementation Software .................................24Migrating Automotive Simulation Models ..............................24How to Migrate ModelDesk Projects ......................................27Migrating Applications Created with ConfigurationDesk 1.1.2 or Earlier to ConfigurationDesk 1.2.............................................29Migrating to Real-Time Testing 1.1 .........................................31Migrating Simulink Models for Using CAN Monitoring ...........31Migrating from dSPACE Release 5.1 or Earlier.........................31

Index 33

3 ▲■■■■■■■■■■■■■■■■■■■

New Features and Migration March 2007

Contents ▲■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■I■■■■■■■■■■■■■■■■■■■■■■▼

4 ■■■■■■■■■■■■■■■■

New Features and Migration March 2007■■▼

I■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■

About This Document

Content This document provides you with a brief overview of the major new features of the RCP (rapid control prototyping) and HIL (hardware-in-the-loop) software of dSPACE Release 5.3 since the previous release.

dSPACE Release 5.3 contains all the software from dSPACE on one DVD:

n RCP and HIL software

"RCP and HIL software" is a software item containing several dSPACE software products, for example RTI, ControlDesk, AutomationDesk, ConfigurationDesk, MotionDesk, ModelDesk.

n CalDesk 1.4.1

n TargetLink 2.2

This document does not describe the new features of CalDesk and TargetLink.

Where to go from here Information in other sections

New Features of dSPACE Release 5.3 (RCP and HIL Software)Describing the key features, and a summary of the major enhancements made since the previous release.

11

Migrating from Previous ReleasesProviding you with information on the changes you may have to perform when you migrate from previous releases to dSPACE Release 5.3.

23

5 ▲■■■■■■■■■■■■■■■■■■■


About This Document ▲■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■I■■■■■■■■■■■■■■■■■■■■■■▼

6 ■■■■■■■■■■■■■■■■

CalDesk and TargetLink

dSPACE Calibration System New Features and MigrationProvides a brief overview of the major new features of the dSPACE Calibration System, information on the changes you may have to make when you migrate from a previous release, and information on the limitations that apply to CalDesk.

TargetLink New Features and MigrationProvides a brief overview of the major new features of TargetLink 2.2 and information on the changes you may have to make when you migrate from a previous release.


I■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■

General New Features

Objective All the new features of all the dSPACE products in dSPACE Release 5.3 are described.

Where to go from here Information in this section

Supported MATLAB Releases

Supported MATLAB releases

The software of dSPACE Release 5.3 offers full compatibility with the following releases of MATLAB from The MathWorks:

n MATLAB R2006b

n MATLAB R2006a+

n MATLAB R14SP3

The RTI FlexRay Blockset of dSPACE Release 5.3 does not support MATLAB R2006a+, and R2006b.

The software of dSPACE Release 5.3 does not support MATLAB R13SP1+ and MATLAB R13SP2.

For detailed information on compatibility, refer to www.dspace.com/goto?Compatibility on the dSPACE Web site.

Supported MATLAB Releases 7

Supported Operating Systems 8

New Key Features 8

7 ▲■■■■■■■■■■■■■■■■■■■


www.dspace.com/goto?Compatibility

General New Features ▲■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■I■■■■■■■■■■■■■■■■■■■■■■▼

8 ■■■■■■■■■■■■■■■■

Supported Operating Systems

Supported operating systems

The software of dSPACE Release 5.3 supports the following operating systems:

n Windows 2000 with Service Pack 4

n Windows XP (32-bit version) with Service Pack 2

Windows XP Professional x64 Edition and Windows Vista are not supported by dSPACE Release 5.3.

New Key Features

Implementation: key feature summary

The new key features of the implementation software are:

RTI CAN MultiMessage Blockset

n Support of raw data monitoring with the CAN Navigator

n Create S-function for some RTICANMM blocks

n Default signal values according to the DBC or LDF file available for user-defined default settings

RTI LIN MultiMessage Blockset

n Create S-function for selected RTILINMM blocks only

n Options for setting a LIN bus to sleep mode

n Monitor reception of a wake-up command

n Monitor the checksum values of selected RX frames

n New frame manipulation options: Frame length and dynamic LIN frame checksum

n Default signal values according to the DBC or LDF file available for user-defined default settings

n Counter during TX timeout

RTI Bypass Blockset

n New Gateway block provides a gateway functionality for XCP on CAN

n Support of the DS2202, DS2210, and DS2211 I/O boards.

n Support of the Toshiba TMP1984 processor with DCI-GSI1

dSPACE FlexRay Configuration Package

n Support of the following FlexRay modules:


■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■▼ General New Features ▲■■■■■■■■■■■■■■■■■■I

o DECOMSYS::FlexRay(MFR4200) supported with DECOMSYS::FlexIM2+ or DECOMSYS::FlexIM4+, with V9.x

o DECOMSYS::FlexIM(V11 IP-Core) supported with DECOMSYS::FlexIM4+ with V11.x

o DS4340 (with PFR4300) (produced by DSPACE)

The FlexRay modules can be installed on a DS4501 (connected to a DS1005 or DS1006) and in MicroAutoBox 1401/1505/1506 and 1401/1505/1507.

n Support of physical data types for sending and receiving signals

ASM models and ModelDesk

n The ASM vehicle dynamics model has new geometric suspensions (McPherson strut, rigid axle, and semi-trailing arm) and table-based suspensions to simulate asymmetric suspensions. The parameter values can be specified using ModelDesk.

n ModelDesk has an automation interface. This allows you to change parameter values, select roads, and specify maneuvers using scripts.

Experiment and test: key feature summary

The new key features of the experiment and test software are:

AutomationDesk

n Real-time testing for DS1005 processor board

n Real-time testing can run on a CPU of multiprocessor systems (based on DS1005 or DS1006 processor boards)

n AutomationDesk-Automation Server is able to run real-time tests

MTest

n Support of CTE for specification of reference data

ControlDesk

n The CAN Navigator has new key features:

o You can monitor raw data of CAN messages on a CAN bus.

o You can specify filters for monitoring selected CAN messages of a CAN controller.

New Features and Migration March 2007 9 ▲■■■■■■■■■■■■■■■■■■■

General New Features ▲■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■I■■■■■■■■■■■■■■■■■■■■■■▼

10 ■■■■■■■■■■■■■■■■


I■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■

New Features of dSPACE Release 5.3 (RCP and HIL Software)


New Features of the RTI Bypass Blockset 12

New Features of the RTI CAN MultiMessage Blockset

13

New Features of the RTI FlexRay Configuration Package

13

New Features of the RTI LIN MultiMessage Blockset 14

New Features of ConfigurationDesk 16

New Implementation Features of RapidPro System Used as I/O Subsystem

17

New Implementation Features of RapidPro System Used as a Prototyping ECU

18

New Features of Automotive Simulation Models and ModelDesk

18

New Features of ControlDesk 20

New Features of AutomationDesk 20

11 ▲■■■■■■■■■■■■■■■■■■■


New Features of dSPACE Release 5.3 (RCP and HIL Software) ▲■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■I■■■■■■■■■■■■■■■■■■■■■■▼

12 ■■■■■■■■■■■■■■■■

New Features of the RTI Bypass Blockset

Gateway block The RTI Bypass Blockset contains the RTIBYPASS_GATEWAY_BLx block. It provides a gateway functionality for XCP on CAN. The gateway functionality provides arbitrated access from the dSPACE prototyping system and an external calibration tool, or from two external tools, to the same ECU at the same time, even if only one XCP service instance is implemented on the ECU.

Using the Gateway block allows you, for example, to use CalDesk and the RTI Bypass Blockset in parallel.

New supported hardware The RTI Bypass Blockset now supports the

n DS2202 HIL I/O Board



In connection with a DS1005 or DS1006 processor board, these boards can be used for service-based bypassing of ECU control functions via CCP and XCP on CAN.

Working with models from RTI Bypass Blockset versions 2.0 and 2.1

dSPACE Release 5.3 comes with the RTI Bypass Blockset 2.2.2. It is compatible with earlier blockset versions 2.x. However, the format of the data dictionary was changed compared to RTI Bypass Blockset versions 2.0 and 2.1. The data dictionaries of Simulink models built with blockset versions 2.0 and 2.1 are automatically converted to the format used by RTI Bypass Blockset 2.2.2.

If you have a model that was saved with RTI Bypass Blockset 2.2.2 and want to use it with RTI Bypass Blockset version 2.0 or 2.1, you must first delete the model’s data dictionary (the name and path of the data dictionary can be found in the Info block) and import the ASAM-MCD 2MC (A2L) file again. The RTI Bypass Blockset then automatically creates a data dictionary according to the appropriate format.


■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■▼ New Features of dSPACE Release 5.3 (RCP and HIL Software) ▲■■■■■■■■■■■■■■■■■■I

New Features of the RTI CAN MultiMessage Blockset

Create S-function for some RTICANMM blocks

The RTICANMM GeneralSetup block now provides an option that lets you create S-functions for some of the RTICANMM blocks in the current model. The blocks can be easily selected from a list.

Default signal value according to the DBC file available for user-defined default settings

When you set the default values of TX signals individually, you can now either enter a decimal value as the default value, or specify that the signal keeps the default value specified in the DBC file.

Support of CAN monitoring with the CAN Navigator

The RTI CAN MultiMessage Blockset now supports CAN monitoring with ControlDesk´s CAN Navigator (see New Features of ControlDesk on page 20). To enable the CAN Navigator to monitor CAN buses, you must allow CAN monitoring and specify the host service to be used in the RTICANMM GeneralSetup block.

New Features of the RTI FlexRay Configuration Package

Supported hardware The RTI FlexRay Configuration Package supports the following dSPACE real-time systems:

n Modular system based on a DS1005 with a DS4501

n Modular system based on a DS1006 with a DS4501

n MicroAutoBox 1401/1505/1506 and 1401/1505/1507

Each system must be equipped with FlexRay IP modules of one of the following types:

n DECOMSYS::FlexRay(MFR4200) supported with DECOMSYS::FlexIM2+ or DECOMSYS::FlexIM4+, with V9.x

n DECOMSYS::FlexIM(V11 IP-Core) supported with DECOMSYS::FlexIM4+ with V11.x

n DS4340 (with PFR4300) (produced by DSPACE)

Physical data types The FlexRay Configuration Blockset supports physical data types for sending and receiving signals. You can select whether the coded data type or physical data type is used for signal encoding in the RTIFLEXRAYCONFIG READ and RTIFLEXRAYCONFIG WRITE blocks. You can specify the default data type for signal encoding in the Code Generation dialog of the FlexRay Configuration Tool.



14 ■■■■■■■■■■■■■■■■

Related topics

New Features of the RTI LIN MultiMessage Blockset

Ports of the RTILINMM ControllerSetup block

The RTI LIN MultiMessage Blockset now lets you create the following inports and outports for the RTILINMM ControllerSetup block:

n Baudrate (inport): To specify the baud rate to be used for the LIN bus.

n Breaklength (inport): To specify the break length.

n Breakdelimiter (inport): To specify the break delimiter.

n Termination (inport): To switch termination during run time.

n Baudrate (outport): To output the baud rate of the last received frame.

In addition, you can activate the generation of constant blocks with default values for the inports. If enabled, constant blocks are added to the model and connected to the input ports of the RTILINMM ControllerSetup block. By default, each constant block is assigned to the corresponding value specified on the Controller page of the RTILINMM ControllerSetup block.

Create S-function for some RTILINMM blocks

The RTILINMM GeneralSetup block now provides an option that lets you create S-functions for some of the RTILINMM blocks in the current model. The desired blocks can be easily selected from a list.

Sleep options The RTI LIN MultiMessage Blockset now lets you specify options for setting a LIN bus to sleep mode. You activate the sending of a sleep command for the master node. You can specify whether going to sleep is possible without sending a sleep command, or whether setting the LIN bus to sleep mode always requires a sleep command to be sent. If desired, the trigger of the sleep event (sleep command or bus timeout) can be watched via TRC variable and/or outport in the model.

In addition, the RTI LIN MultiMessage Blockset lets you create a bus state outport that has a value of 0 when the bus is sleeping, otherwise the value is 1.

References

• Code Generation ( FlexRay Configuration Tool Reference)

• RTIFLEXRAYCONFIG READ ( FlexRay Configuration RTI Reference)

• RTIFLEXRAYCONFIG WRITE ( FlexRay Configuration RTI Reference)

ST M

ST M

ST M



Event port for wake-up request

The RTI LIN MultiMessage Blockset now lets you watch if a wake-up command was received. The information can be made available via TRC variable and/or outport in the model.

Output of RX frames checksums

You can now use checksum ports for RX frames. The checksum values of the selected RX frames are provided at the RX Data outport.

You can also enable checksum displays for RX frames. Entries for RX frames checksums are included in the generated TRC file. You can then display RX frames checksums in ControlDesk.

New frame manipulation options

Frame length manipulation You can modify the lengths of TX and RX frames during run time. The frame lengths can be modified either via TRC file or via inport.

Additionally, you can activate the dynamic frame length option. If dynamic frame length is enabled, you can change the length of a TX frame for a time period of n transmissions in the corresponding ControlDesk message layout.

Dynamic LIN frame checksum You can manipulate the LIN frame checksums. If LIN frame checksum manipulation is enabled, the checksum of the selected LIN frame(s) is increased by an offset value for a specified number of times.

Default signal values according to the DBC or LDF file available for user-defined default settings

When you set the default values of TX signals individually, you can now either enter a decimal value as the default value, or specify that the signal keeps the default value specified in the DBC file or LDF file.

Counter during TX timeout You can specify the default number of timeouts for each TX frame. The RTILINMM MainSetup block now lets you choose the behavior of the counter during timeout. You can specify to stop the counter or to calculate it (simulation of lost frames) while a frame is timed out



16 ■■■■■■■■■■■■■■■■

New Features of ConfigurationDesk

New supported RapidPro hardware

As of ConfigurationDesk 1.2, the new SC-TC 8/1 (DS1638) signal conditioning module is supported. This is an 8-channel module for connecting thermocouples and is suitable for the following RapidPro use scenarios:

n RapidPro system used as I/O subsystem

n RapidPro system used as stand-alone prototyping ECU

Platform Manager ConfigurationDesk now provides a Platform Manager. This gives you access to connected hardware without creating a project or an application beforehand.

The features of the new Platform Manager are:

n Display of all the hardware components of your connected RapidPro system in a hierarchical tree structure: The Platfom Manager gives you detailed information on the hardware topology (including the hardware TopologyID), the SC and PS modules used, their configuration settings, and other hardware details, for example, their serial numbers.

n Diagnostic handling: Connected hardware components which provide diagnostic features are displayed in the Platform Manager with symbols giving information on their diagnostic status.

n Monitoring: Signal values (logical states and voltages) of specific channels and system values (for example, temperatures) are displayed.

n Editing reminders: Some RapidPro modules provide user-configurable circuits on their board to affect the channels behavior. Reminders for components which are mounted can be edited and stored via Platform Manager.

n Switching the processor of the RapidPro system to different operation modes (execution mode, idle mode)

For more details on the Platform Manager, refer to Platform Manager

( ConfigurationDesk Configuration Reference).

Accessing the RapidPro hardware

With ConfigurationDesk 1.2 a new device driver with new features is used.

In contrast to former versions of ConfigurationDesk, the RapidPro system can be accessed simultaneously by CalDesk and ConfigurationDesk. RapidProUpdate.exe and Down1603.exe still require exclusive access.

ST M



For details on the new bevavior, refer to Using ConfigurationDesk and

CalDesk Simultaneously ( ConfigurationDesk Configuration Guide).

New Implementation Features of RapidPro System Used as I/O Subsystem

Basic I/O Request-read of measurement results

The following blocks provide an additional read mode for retrieving measurement results:

n RPCU_BIT_IN_TPU_BLx

n RPCU_PW2D_TPU_BLx

n RPCU_PW2D_MIOS_BLx

n RPCU_F2D_TPU_BLx

n RPCU_F2D_MIOS_BLx

The RapidPro system writes a new result to the DPMEM only when requested by the RCP system.This is helpful if the frequency of the measured signal is high, as it avoids an unnecessary load on the CPU of the RapidPro system.

Temperature measurement with SC-TC 8/1

The implementation software (RTI RapidPro Control Unit Blockset) now provides blocks to measure temperatures with the new RapidPro SC-TC 8/1 (DS1638) signal conditioning module.

For an overview of these blocks, refer to Measuring Temperatures with

the SC-TC 8/1 Module ( RapidPro System – I/O Subsystem MPC565 RTI Reference).

The new device driver is not compatible with previous CalDesk and ConfigurationDesk versions.

n ConfigurationDesk 1.2 is only compatible with CalDesk 1.4.1 (part of Release 5.3) and not with prior versions of CalDesk.

n CalDesk 1.4.1 is only compatible with ConfigurationDesk 1.2 (part of Release 5.3) and not with prior versions of ConfigurationDesk.

ST M

ST M



18 ■■■■■■■■■■■■■■■■

New Implementation Features of RapidPro System Used as a Prototyping ECU

Temperature measurement with SC-TC 8/1

The RTLib1603 now provides functions to measure temperatures with the new RapidPro SC-TC 8/1 (DS1638) signal conditioning module.

For an overview of these functions, refer to Functions for Implementing Temperature Measurement with SC-TC 8/1 Module

( RapidPro System – Prototyping ECU MPC5554 RTLib Reference).

New Features of Automotive Simulation Models and ModelDesk

ASM Vehicle Dynamics Blockset

The ASM Vehicle Dynamics Blockset now includes geometrical suspension models. Common suspension types are implemented as exact analytical equations, which are solved during each simulation step. Table-based suspensions have also been extended to simulate asymmetric suspensions.

The following blocks of the ASM Vehicle Dynamics Blockset are new. The block parameters can be specified via ModelDesk.

MC_PHERSON_STRUT block A McPherson strut for independent front suspension can be configured via user-definable linkage points. The kinematic behavior of the McPherson strut is calculated over the whole range of input data, for example, angle of rotation and steering rod displacement.

ST M



SEMI_TRAILING_ARM block A semi-trailing arm for independent rear suspension can be configured via user-definable linkage points. The kinematic behavior of the semi-trailing arm is calculated over the whole range of input data, for example, angle of rotation.

RIGID_AXLE block A rigid axle for dependent rear suspension can be configured via user-definable linkage points. The kinematic behavior of the rigid axle is calculated over the whole range of input data, for example, angle of rotation around vehicle roll axis and vertical displacement of axle.

ModelDesk ModelDesk comes with the following new features:

n ModelDesk has an automation interface. The ModelDesk automation interface allows you to control ModelDesk using scripts. You can implement scripts to change parameter values, select roads, and specify maneuvers. For details, refer to

Automating ModelDesk ( ModelDesk Guide).

n ModelDesk automates MotionDesk. When ModelDesk downloads a road, the MotionDesk scene is updated automatically.

n ModelDesk supports the new geometric suspension models (McPherson strut, rigid axle, and semi trailing arm) and table-based suspensions.

ST M



20 ■■■■■■■■■■■■■■■■

Related topics

New Features of ControlDesk

CAN Navigator With the CAN Navigator, you can monitor and log raw data of CAN messages on a CAN bus. The CAN Navigator supports unfiltered and filtered CAN monitoring.

Unfiltered CAN monitoring This is a simple way of monitoring all the CAN messages of a CAN controller.

Filtered CAN monitoring You can specify filters for monitoring selected CAN messages of a CAN controller. Each CAN controller has its own filters. Each filter can contain one or more filter items.

IDF files You can convert IDF files that are larger than 2 GB.

Related topics

New Features of AutomationDesk

MTest MTest is based on AutomationDesk. It comes with the following new features:

n The test frames can be updated recursively.

n The inports and outports of the effective test interface can be reset to the settings of the potential test interface separately.

n All inports or outports can be included in or excluded from the effective test interface by a single click.

n Mapping information is kept when the test interface changes.

n Initialization scripts can be selected at test sequences.

n Vector signals can be imported via MAT files.

n The interpolation of test signals can be switched on and off.

Basics

• Migrating Automotive Simulation Models on page 24

HowTos

• How to Migrate ModelDesk Projects on page 27

Basics

• Handling CAN Messages ( ControlDesk Experiment Guide)• Migrating Simulink Models for Using CAN Monitoring on page 31

ST M



n Multiple CTE test sequences can be imported with identical settings with a single click. Only new or modified test sequences are imported.

n Simulation properties can be set for all test sequences simultaneously.

n In addition to systematic test data, systematic reference data can be specified via the Classification Tree Editor for Embedded Systems (CTE/ES from RazorCat Development GmbH).

n Subreports can be generated for each executed test element separately automatically.

For further information, refer to AutomationDesk MTest Guide and AutomationDesk MTest Reference.

Real-time testing Real-time testing comes with the following new features:

n Support of the DS1005 processor board.

n Real-time testing can be used on a CPU in a multiprocessor system (based on DS1005 or DS1006 processor boards). In this case, only local data of the CPU is accessible in real-time tests. If data of another CPU has to be accessed, data transfer to the testing CPU has to be modeled via IPC blocks.

n Real-time testing is available in an operator version. You can run real-time tests using the operator version. However, you must have a developer version for BCG file creation.

Related topics HowTos

• Migrating to Real-Time Testing 1.1 on page 31



22 ■■■■■■■■■■■■■■■■


I■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■

Migrating from Previous Releases

Objective After you install dSPACE Release 5.3, it may be necessary to carry out additional steps.


Migrating the Implementation SoftwareYou must note some points when you migrate the implementation software to dSPACE Release 5.3 from the previous release.

24

Migrating Automotive Simulation ModelsYou must note some points when you migrate the Automotive Simulation Models.

24

How to Migrate ModelDesk ProjectsIf you work with ModelDesk 1.1, it is strongly recommended to migrate each ModelDesk project that was developed with a former ModelDesk version. Otherwise data loss at parameter sets might occur.

27

Migrating Applications Created with ConfigurationDesk 1.1.2 or Earlier to ConfigurationDesk 1.2Working with ConfigurationDesk 1.2 requires the migration of applications that were created with former ConfigurationDesk versions.

29

Migrating to Real-Time Testing 1.1BCG files created with real-time testing 1.0 cannot be directly used in real-time testing 1.1.

31

23 ▲■■■■■■■■■■■■■■■■■■■


Migrating from Previous Releases ▲■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■I■■■■■■■■■■■■■■■■■■■■■■▼

24 ■■■■■■■■■■■■■■■■

Migrating the Implementation Software

Objective Note the following points when migrating from a previous release to dSPACE Release 5.3:

Migrating Simulink models When a Simulink model containing RTI blocks from a previous release is opened under dSPACE Release 5.3, it is migrated automatically. However, the following warning may appear in the MATLAB Command Window:

Warning: In instantiating linked block ’<BlockPath>’for parameter ’<BlockParameterName>’.

You can ignore this warning, because it does not affect the functionality of your Simulink model.

Migrating Automotive Simulation Models

Migrating to ASM 1.3 From ASM 1.2 Projects developed using ASM 1.2 are automatically migrated when you open the related Simulink model from MATLAB.

From ASM 1.0 or ASM 1.1 You can migrate your projects developed using ASM 1.0 or ASM 1.1 by calling a command in the MATLAB Command Window:

>> asm_migrate_manual

Migrating Simulink Models for Using CAN MonitoringReal-time application compiled from Simulink models build with previous releases cannot be used for CAN monitoring.

31

Migrating from dSPACE Release 5.1 or EarlierTo migrate from dSPACE Release 5.1 or earlier to dSPACE Release 5.3, you have to migrate step by step via the intervening dSPACE Releases.

31


■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■▼ Migrating from Previous Releases ▲■■■■■■■■■■■■■■■■■■I

This updates your project including, for example, initializing new parameters and establishing new connections to block inputs or outputs. More detailed information on the changes in the components of ASM is given below.

Migrating to ASM Environment Blockset 1.1

ROAD block The road matrix is now an S-function parameter, not a value of a Constant block. This reduces peaks in turnaround time.

MANEUVER_SCHEDULER block The maneuver matrices are now S-function parameters, not values of a Constant block. This reduces peaks in turnaround time.

GEAR_SHIFTER block The startup behavior of the vehicle has been improved, and the parameter default values have been modified. The following table shows the modified parameters and their new default values.

Migrating to ASM Engine Diesel Blockset 1.2.1

COMBUSTION_TORQUE_CI block A new output for modulated combustion torque for every single cylinder is now available in ASMSignalBus. This is helpful in analyzing the combustion torque generation for each cylinder and checking the firing order.

Migrating to ASM Gasoline Basic Blockset 1.2.1

SOFT_ECU_GASOLINE block The calculation of cylinder crankshaft angles (starting with 0 at TDC) have been corrected. There was a mismatch in calculating it by the given firing order.

If the changes in the blocks conflict with the model behavior in the project, you can also replace the new blocks by the old ones, see the Former versions subsystems in the relevant ASM component library.

Parameter Unit New Value (Recommended)

Old Value

Map_Pos_Clutch_Pedal_StartUp.x [s] [0 0.2 0.4 0.6 0.8 1 1.2 1.4 1.6 1.8 2 2.02 2.04 2.06 2.08 2.1 2.12 2.14 2.16 2.18]

[0 0.2 0.4 0.6 0.8 1 1.2 1.4 1.6 1.8 2 2.02 2.04 2.06 2.08 2.1 2.12 2.14 2.16 2.18]

Map_Pos_Clutch_Pedal_StartUp.v [%] [100 95 90 85 80 70 60 50 40 20 0 0 0 0 0 0 0 0 0 0]

[100 100 95 95 95 90 85 70 55 44 0 0 0 0 0 0 0 0 0 0]

Const_n_Engine_StartUp_Set [rpm] 1100 1000

Const_I_Gain_StartUp [] 0.02 0.1

Const_P_Gain_StartUp [] 0.04 0.1



26 ■■■■■■■■■■■■■■■■

Migrating to ASM Gasoline Blockset 2.0.1

SOFT_ECU_GASOLINE block The calculation of cylinder crankshaft angles (starting with 0 at TDC) are corrected. There was a mismatch in calculating it by the given firing order.

Migrating to ASM Drivetrain Basic Blockset 1.1.1

TORQUE_CONTROLLER block A new feedforward controller has been implemented in parallel to the PI-controller for better control of the engine torque. A new parameter was introduced, and the new input n_Engine[rpm] has to be connected. The new parameter is parameterized by an existing variable:

MDL.Environment.DriverBasic.LongControl.Map_Trq_Engine_Inv

GEARBOX_MT and GEARBOX_AT block The effect of braking nearvehicle standstill has been improved. The slope of braking torque near standstill is calculated automatically from the transmission output inertia and numeric stability criterion.

Migrating to ASM Turbocharger Blockset 1.1.1

SHAFT_TC block The turbocharger shaft block has been extended with a new parameter for maximum speed. The parameter is initialized automatically by migration. To set the parameter manually in MATLAB, simply define it in the following way (value in rpm):MDL.EngineDiesel.AirPath.Turbocharger.ShaftTC.Const_n_TC_Max.v = 200000;

Migrating to ASM Vehicle Dynamics Blockset 1.1

Steering block A new outport has been added to match the new structure in the suspension subsystem. The new outport is Displ_SteeringRod[m].

Obsolete blocks Some blocks were made obsolete by the new structure of the suspension subsystem (see New Features of Automotive Simulation Models and ModelDesk on page 18). Some obsolete blocks have been renamed and moved to the Former Version subsystem in the relevant ASM component library. The functionalities of these blocks have not changed. The following table shows the blocks:

Previous Block Name New Block Name

RELATIVE_VELOCITIES_FRONT RELATIVE_VELOCITIES_FRONT_1_0

RELATIVE_VELOCITIES_REAR RELATIVE_VELOCITIES_REAR_1_0

SUSPENSION_FORCES_FRONT SUSPENSION_FORCES_FRONT_1_0

SUSPENSION_FORCES_REAR SUSPENSION_FORCES_REAR_1_0

SUSPENSION_KINEMATICS_FRONT SUSPENSION_KINEMATICS_FRONT_1_0

SUSPENSION_KINEMATICS_REAR SUSPENSION_KINEMATICS_REAR_1_0

VEHICLE_MOTION VEHICLE_MOTION_1_0

VEHICLE_MOVEMENT_INFO VEHICLE_MOVEMENT_INFO_1_0



Two obsolete blocks were moved to the Common Suspension Blocks subsystem. The functionalities of these blocks have not changed:

n SUSPENSION_COMPLIANCE_FRONT

n SUSPENSION_COMPLIANCE_REAR

How to Migrate ModelDesk Projects

Objective If you work with ModelDesk 1.1, it is strongly recommended to migrate each ModelDesk project that was developed with a former ModelDesk version. Otherwise data loss at parameter sets might occur. Migration is needed for both manual control of ModelDesk and remote control of ModelDesk via automation interface.

Preconditions n The Simulink model of the ModelDesk project should be migrated beforehand, see Migrating Automotive Simulation Models on page 24.

n The SDF file must be migrated. You must have built new real-time code for the migrated Simulink model.

Method To migrate ModelDesk projects

1 Open MATLAB.

2 In the MATLAB Command Window, enter

asm_migrate_mod11

A dialog appears to inform you that you have to select the path of the ModelDesk project to be migrated.

3 Click OK to close the dialog.

A folder browser appears.

4 In the folder browser, select the folder of the ModelDesk project. In this folder, a Pool subfolder must exist. See the following example.



28 ■■■■■■■■■■■■■■■■

If you select the wrong folder or cancel the selection, error messages are displayed.

If you have selected the correct ModelDesk project path, ModelDesk parameter sets are automatically migrated to version 1.1. Backups of the folders Suspension Kinematics Front, Suspension Kinematics Rear and Body Geometry and Mass are generated first. Afterwards, the Const_TrackWidth_Front, Const_Pos_z0, Const_TrackWidth_Rear, and Const_WheelBase parameters are read from the Body Geometry and Mass.xml file and written to the related Suspension Kinematics.xml file. Then these parameters are deleted in theBody Geometry and Mass.xml file.

Each migration step is logged in the MATLAB Command Window.

5 Start ModelDesk and open the project to be migrated.

ModelDesk’s Project Manager will display a dialog which declares that the project was generated with an older version of ModelDesk.

6 Click No to open the project and continue migration.

7 In the Project Navigator open the context menu of the Simulation Model item and choose Update Model.

The Simulink model is updated.

8 Save the project.

9 If one of the parameters transferred automatically from ‘Body Geometry and Mass’ to ‘Suspension Kinematics’ is incorrect, open the Suspension Kinematics page in ModelDesk and change the parameter values manually. The old values are stored in the backup file of the Body Geometry and Mass.xml file in the ..\Pool\Parameter\VehicleDynamics\Body Geometry and Mass BackupVS10 folder.

Result The ModelDesk project is migrated.



Migrating Applications Created with ConfigurationDesk 1.1.2 or Earlier to ConfigurationDesk 1.2

Objective Applications created with ConfigurationDesk 1.1.2 or earlier are not compatible with ConfigurationDesk 1.2.

Upward compatibility ConfigurationDesk can convert these applications to achieve upward compatibility. Downward compatibility is not implemented.

Migrating an old project/application

When you open a project that contains an old application, or when you import an old application, ConfigurationDesk prompts you to convert the application:

If you cancel the conversion, the application and its old subfolders are shown in the Project Manager, but disabled. You cannot modify the application. Its hardware topology is not loaded. However, you can restart conversion via Activate in the application’s context menu.

After an old project has been loaded and converted, you can configure its applications and add new ones.

Application Created with ... Compatible with ConfigurationDesk 1.1.2 or Earlier

Compatible with ConfigurationDesk 1.2 or Later

ConfigurationDesk 1.1.2 or earlier

Yes Yes, after migration

ConfigurationDesk 1.2 or later No Yes



30 ■■■■■■■■■■■■■■■■

Creating application based on old hardware data

When you are creating a new application and the Project Wizard prompts you to add the hardware topology, you can use an old HTF file as the data source. ConfigurationDesk converts the file automatically to a compatible HTF file.

When the Project Wizard prompts you to add the configuration settings, you cannot use an old HCF file as the data source but only a CDS file.

Files affected by migration An old application (ConfigurationDesk 1.1.2 or earlier) comprises a hardware topology file (HTF file) and, perhaps, a hardware configuration file (HCF file), which depends on whether configuration settings were specified. During migration, ConfigurationDesk converts an HTF file to a new HTF file. An HCF file is copied instead, and the copy is converted to a CDS file. The project’s folder structure is not affected by migration. Thus, all files are stored in the same subfolders as before.

CDL files (application) and CDP files (project) are also modified during migration.

Old HTF files do not comprise the parameters of the user-configurable circuits, and neither do HTF files migrated this way.

If you only have an old HCF file which is not part of a project or an (exported) application, you must contact dSPACE Support to convert the HCF file to a CDS file.

For ConfigurationDesk 1.1.2 or earlier, the parameters of the user-configurable circuits of a module are stored in HCF files. Since ConfigurationDesk 1.2 these parameters are stored in HTF files. In consequence, if an application is converted that does not comprise an HCF file, the parameters of the user-configurable circuits are lost.



Migrating to Real-Time Testing 1.1

Objective BCG files created with real-time testing 1.0 cannot be directly used in real-time testing 1.1.

Signature of BCG files Because real-time testing 1.1 has an operator version, the BCG files are given a special signature when they are created. The signature is not contained in BCG files created with real-time testing 1.0. These BCG files can therefore not be started with real-time testing 1.1. For an existing BCG file the signature is automatically included the first time an RTT-sequence is created from the BCG file using the developer version of real-time testing 1.1.

Migrating Simulink Models for Using CAN Monitoring

CAN monitoring CAN monitoring is only possible if the Simulink models use the RTI CAN MultiMessage Blockset 1.5 of dSPACE Release 5.3. You must enable the CAN monitoring and recompile the Simulink models built with a previous blockset version. CAN monitoring is enabled in the RTICANMM GeneralSetup block (see Main Page (RTICANMM

GeneralSetup) ( RTI CAN MultiMessage Reference)).

Migrating from dSPACE Release 5.1 or Earlier

Objective To migrate from dSPACE Release 5.1 or earlier to dSPACE Release 5.3, you have to migrate step by step via the intervening dSPACE Releases.

Example For example, if you want to migrate from dSPACE Release 5.0 to dSPACE Release 5.3, you have to follow the migration steps given in:

1. New Features and Migration of dSPACE Release 5.1

2. New Features and Migration of dSPACE Release 5.2

3. Finally, the migration steps given in Migrating from Previous Releases on page 23.

ST M



32 ■■■■■■■■■■■■■■■■

Previous release documents

The New Features and Migration documents for previous releases are available via Internet and on the dSPACE DVD:

n Download them from /www.dspace.com/goto?migration.

n Read them from the dSPACE DVD (see the %dSPACE_ROOT%\Doc folder). The PDF files are called NewFeaturesAndMigrationxx.pdf, where xx stands for the release number.


/www.dspace.com/goto?migration

■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■▼ Index ▲■■■■■■■■■■■■■■■■■■I

Index

A

AutomationDesknew features 20

Automotive Simulation Modelsnew features 18

C

ConfigurationDeskmigration to Version 1.2 29new features 16

ControlDesknew features 20

K

key features 8

M

migratingAutomotive Simulation Models 24from dSPACE Release 5.1 or earlier 31implementation software 24ModelDesk projects 27real-time testing 1.1 31

migrationto ConfigurationDesk 1.2 29

ModelDesknew features 19

MTestnew features 20

N

new featuresAutomationDesk 20Automotive Simulation Models 18ConfigurationDesk 16ControlDesk 20ModelDesk 19MTest 20real-time testing 21RTI Bypass Blockset 12RTI CAN MultiMessage Blockset 13RTI FlexRay Configuration Package 13RTI LIN MultiMessage Blockset 14RTLib1603 18

R

real-time testingnew features 21

RTI Bypass Blocksetnew features 12

RTI CAN MultiMessage Blocksetnew features 13

RTI FlexRay Configuration Packagenew features 13

RTI LIN MultiMessage Blocksetnew features 14

RTLib1603new features 18

S

supported MATLAB releases 7supported operating systems 8


Index ▲■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■I■■■■■■■■■■■■■■■■■■■■■■▼

34 ■■■■■■■■■■■■■■■■


New Features and Migration

Documents

Transcript of New Features and Migration