Edition 08/2010

Release Notes

AVL CRUISE
VERSION 2010.0.2

AVL List Gmbh 2010. All right reserved

Release Notes

CRUISE v2010.0.2

AVL LIST GmbH

Hans-List-Platz 1, A-8020 Graz, Austria
http://www.avl.com
AST Local Support Contact: www.avl.com/ast-worldwide

Revision

Date

Description

Document No.

A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V

15-Jun-1998
17-Mar-1999
30-Mar-2000
22-Apr-2001
21-Mar-2002
23-May-2003
10-Oct-2003
01-Dec-2004
17-Jan-2005
29-April-2005
30-June-2005
25-Nov-2005
30-Nov-2006
22-June-2007
30-April-2008
09-June-2008
30-Oct-2008
10-Dec-2008
03-Jul-2009
01-Jul-2010
16-Aug-2010
27-Aug-2010

Release Notes v1.0

Release Notes v1.1
Release Notes v1.2
Release Notes v2.0
Release Notes v2.1
Release Notes v2.2
Release Notes v2.2.1
Release Notes v2.99
Release Notes v3.0
Release Notes v3.0.1
Release Notes v3.0.2
Release Notes v3.0.3
Release Notes v3.1
Release Notes v3.1.1
Release Notes v2008
Release Notes v2008.0.1
Release Notes v2008.0.2
Release Notes v2008.1
Release Notes v2009
Release Notes v2010
Release Notes v2010.0.1
Release Notes v2010.0.2

04.0102.0387
04.0102.0408
04.0102.0417
04.0102.0425
04.0102.0433
04.0102.0449
04.0102.0451
04.0102.0460
04.0102.0469
04.0102.0471
04.0102.0475
04.0102.0478
04.0102.0491
04.0102.0501
04.0102.2008
04.0102.2008.1
04.0102.2008.2
04.0102.2008.3
04.0102.2009
04.0102.2010
04.0102.2010.1
04.0102.2010.2

Copyright 2010, AVL

All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored
in a retrieval system, or translated into any language, or computer language, in any form or by any
means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior
written consent of AVL.
This document describes how to run the CRUISE software. It does not attempt to discuss all of
concepts of vehicle simulation that are required to obtain successful solutions. It is the users
responsibility to determine if he/she has sufficient knowledge and understanding of vehicle
simulation to apply this software appropriately.
This software and document are distributed solely on an "as is" basis. The entire risk as to their
quality and performance is with the user. Should either the software or this document prove
defective, the user (and not AVL or its distributors) assumes the entire cost of all necessary
servicing, repair, or correction. AVL and its distributors will not be liable for direct, indirect,
incidental, or consequential damages resulting from any defect in the software or this document,
even if they have been advised of the possibility of such damage.

Release Notes

CRUISE v2010.0.2

Table of Contents
1. General __________________________________________________________1-1
1.1. Remarks ____________________________________________________________________1-1

2. Add-On 2010.0.2__________________________________________________2-1
2.1. Enhancements and Bug-Fixes _________________________________________________2-1
2.1.1. CRUISE sFunction compiled for MatLab 64 bit Version_______________________2-1
2.1.2. Checking in CRUISE licenses if MatLab/Simulink model fails _________________2-1
2.1.3. Missing title for components Terminal and External Battery ________________2-1
2.1.4. English/German GUI labeling ______________________________________________2-1

3. Add-On 2010.0.1__________________________________________________3-1
3.1. Database ____________________________________________________________________3-1
3.1.1. Original Date and Time saved with BLOBs __________________________________3-1
3.1.2. References in Database____________________________________________________3-1
3.2. Main Fixed Bugs _____________________________________________________________3-2
3.2.1. Hub Component with CarMaker/TruckMaker _______________________________3-2
3.2.2. Cruise Boost Co-Simulation________________________________________________3-2
3.2.3. Component frame delay on Japanese XP ____________________________________3-2
3.2.4. Selection visible at Sub-Systems not saved _________________________________3-2
3.2.5. Friction Coefficient Track Dependent _______________________________________3-2
3.2.6. Deleted Obligatory Channel in Description of Databus Table __________________3-2

4. Release 2010 _____________________________________________________4-1

4.1. Highlights ___________________________________________________________________4-1
4.2. New Components ____________________________________________________________4-1
4.2.1. BOOST RT ______________________________________________________________4-1
4.2.2. External Battery _________________________________________________________4-3
4.2.3. CarSim __________________________________________________________________4-4
4.2.4. nD-Table ________________________________________________________________4-5
4.2.5. DC Link _________________________________________________________________4-6
4.2.6. dSPACE _________________________________________________________________4-8
4.2.7. DC Link Control_________________________________________________________4-10
4.3. Changes in Components _____________________________________________________4-11
4.3.1. Flange__________________________________________________________________4-11
4.3.2. Function________________________________________________________________4-12
4.3.3. CVT Control ____________________________________________________________4-13
4.3.4. DCT Control ____________________________________________________________4-13
4.3.5. Extension of DC Converter _______________________________________________4-14
4.3.6. Torque Converter________________________________________________________4-14

27-Aug-2010

CRUISE v2010.0.2

Release Notes

4.3.7. Vehicle _________________________________________________________________4-15

4.3.8. KULI 8.xx ______________________________________________________________4-15
4.3.9. Flowmaster 7.7 __________________________________________________________4-15
4.4. Changes in Tasks and Task Components_______________________________________4-15
4.4.1. Shifting Map Generation Wizard __________________________________________4-15
4.4.2. Elasticity with Speed_____________________________________________________4-17
4.4.3. Shifting according to Desired Gear ________________________________________4-17
4.5. Changes in Calculation Center ________________________________________________4-18
4.5.1. CMC Calculation ________________________________________________________4-18
4.5.2. System Variation ________________________________________________________4-22
4.5.3. Solvers _________________________________________________________________4-22
4.5.4. Extension of Electrical System ____________________________________________4-22
4.6. Changes in Post-Processor ___________________________________________________4-22
4.6.1. Support of IMPRESS Chart and Concerto __________________________________4-22
4.6.2. Scroll-back of time line in Online Monitor __________________________________4-24
4.7. Others _____________________________________________________________________4-24
4.7.1. Map Preprocessor________________________________________________________4-24
4.7.2. XML Input Data_________________________________________________________4-25
4.7.3. Online Help in Vehicle Editor _____________________________________________4-26
4.7.4. New Cruise Installation Possibilities _______________________________________4-26
4.8. Main Fixed Bugs ____________________________________________________________4-27
4.8.1. Graphical User Interface _________________________________________________4-27
4.8.2. Calculation Kernel _______________________________________________________4-27
4.8.3. Others__________________________________________________________________4-27

ii

27-Aug-2010

Release Notes

CRUISE v2010.0.2

List of Figures
Figure 3-1: References in Database.................................................................................................. 3-1
Figure 4-1: Boost RT window ........................................................................................................... 4-2
Figure 4-2: CarSim window .............................................................................................................. 4-4
Figure 4-3: nD-Table window ........................................................................................................... 4-5
Figure 4-4: DC Link window ............................................................................................................ 4-7
Figure 4-5: dSPACE window ............................................................................................................ 4-9
Figure 4-6: DC Link Control window..............................................................................................4-10
Figure 4-7: Speed Governor.............................................................................................................4-11
Figure 4-8: Additional C-Code .........................................................................................................4-12
Figure 4-9: C-Code Parser ...............................................................................................................4-13
Figure 4-10: Clutch Disengagement Characteristic in DCT Control.............................................4-13
Figure 4-11: DC/DC Converter windows.........................................................................................4-14
Figure 4-12: Temperature depending K-Factor..............................................................................4-15
Figure 4-13: Road Gradient From Data Bus...................................................................................4-15
Figure 4-14: GSP Wizard .................................................................................................................4-16
Figure 4-15: Elasticity with Speed ..................................................................................................4-17
Figure 4-16: Shifting according to Desired Gear ............................................................................4-17
Figure 4-17: CMC Window...............................................................................................................4-19
Figure 4-18: Platforms for which CMC can be used.......................................................................4-19
Figure 4-19: System Variation.........................................................................................................4-22
Figure 4-20: IMPRESS Chart with Cruise Results ........................................................................4-23
Figure 4-21: Concerto with Cruise Results .....................................................................................4-24
Figure 4-22: Map Preprocessor........................................................................................................4-25

27-Aug-2010

iii

Release Notes

CRUISE v2010.0.2

1. GENERAL
This document provides an overview of the changes from CRUISE Version 2010.0.1 to
CRUISE Version 2010.0.2. The most important extensions and enhancements are listed
and briefly described.

1.1. Remarks
Note: Full compatibility is given to the components in CRUISE
Version 2010.0.1.

27-Aug-2010

When editing of an existing project from CRUISE Version 2010.0.1, the

TeimOrbit Reporter appears and reports the new data blocks of some
components. Save or run the project to update these components to
Version 2010.0.2.

1-1

Release Notes

CRUISE v2010.0.2

2. ADD-ON 2010.0.2
2.1. Enhancements and Bug-Fixes
2.1.1. CRUISE sFunction compiled for MatLab 64 bit Version
CRUISE sFunction library was created for Matlab 64 bit version
(matlab\work\cruiseInterfaceRTW.mexw64)

2.1.2. Checking in CRUISE licenses if MatLab/Simulink model

fails
CRUISE sFunction was modified so that in case of model error in MatLab/Simulink,
CRUISE-Exit() function is being called, which, among other things, takes care of releasing
the occupied CRUISE licenses.

2.1.3. Missing title for components Terminal and External

Battery
Module title for the components Terminal and External Battery in the vehicle editor is
now set to 'Comment'.

2.1.4. English/German GUI labeling

In German version some GSP-Optimization Labels were set to empty strings. This has
been corrected. CarSim license item was named CarSim Interface instead of MSC
CarSim.

27-Aug-2010

2-1

Release Notes

CRUISE v2010.0.2

3. ADD-ON 2010.0.1
3.1. Database
3.1.1. Original Date and Time saved with BLOBs
While copying BLOBs (e.g. Blackbox.dll) from file system to Database and back, the
original time and date of the file was lost and the Database recognized the BLOB as a new
object although no changes were made. Now the original creation time and date is saved
along with the BLOB and the problem described does not occur any more.

3.1.2. References in Database

When choosing the new option References in Database in the context menu of Database
objects, a window appears, viewing all models and projects where the object is used.
The view is in form of a tree with the object as root node. Other objects of the tree can be
selected and loaded with the button load from database. The loaded object then becomes
the new root node.
Actually loaded objects are marked bold in the tree. They can be opened by pressing the
open button.
Double-click on an object in the tree makes this object to the new root node.
To view the references of all versions of an object, the menu option view | all versions of
can be activated.

Figure 3-1: References in Database

27-Aug-2010

3-1

CRUISE v2010.0.2

Release Notes

3.2. Main Fixed Bugs

3.2.1. Hub Component with CarMaker/TruckMaker
Due to the internal calling sequence of the control components torque oscillations could
have occured in the hub, if CRUISE was used in the co-simulation with
CarMaker/TruckMaker. This has been corrected.

3.2.2. Cruise Boost Co-Simulation

Cruise-Boost co-simulation Segmentation Fault error due to wrong memory access in
cyclerun.

3.2.3. Component frame delay on Japanese XP

Depending on timing of side-events (font search, fly-by-help pop-up, etc.) on Japanese XP,
component frame was frozen or delayed while dragging the component from the
component library to the vehicle editor. This bug was improved but not completely fixed.
The workaround: if fly-by-help is deactivated in tools | extras | system configuration, the
problem disappears completely.

3.2.4. Selection visible at Sub-Systems not saved

For certain selection of sub-system options (visible and active) the selection was not saved.
This has been corrected.

3.2.5. Friction Coefficient Track Dependent

Columns for friction coefficient right and friction coefficient left were switched in GUI.
Now they are switched back.

3.2.6. Deleted Obligatory Channel in Description of Databus

Table
If a channel declared as obligatory was deleted from the Description of Databus Table, it
still remained active and obligatory in the Databus frame. This caused an error message by
model check. Now the deleted channels are not considered in the model check.

3-2

27-Aug-2010

Release Notes

CRUISE v2010.0.2

4. RELEASE 2010
4.1. Highlights
Boost RT Interface (refer to 4.2.1)
GSP Wizard (refer to 4.4.1)
Cruise Model Compiler (refer to 4.5.1)
dSPACE (refer to 4.2.6)
XML Input Data (refer to 4.7.2)
Map Preprocessor (refer to 4.7.1)
System Variation (refer to 4.5.2)
External Battery (refer to 4.2.2)
DC Link (refer to 4.2.5)
Extended Electrical Interface (refer to 4.5.4)
Support of IMPRESS Chart and Concerto (refer to 4.6.1)

4.2. New Components

4.2.1. BOOST RT
The new component BOOST RT serves as an interface to AVL BOOST RT.
The Cruise combustion Engine can be replaced by this component so that Cruise simulates
together with a detailed Boost RT engine model.
BOOST RT is a real-time capable, system-level, engine simulation tool dedicated for the
investigation of transient operating conditions offline in desktop applications and online in
HiL environments. BOOST RT is an engine simulation package running on the time scale
of seconds using transient and steady-state 0D and quasi-dimensional component models.
BOOST RT offers two different approaches to describe the engine. These are:
1. Crank angle resolved description of cylinders (including ports) within the
framework of time resolved and mean value based gas-path, thermal, mechanical
and control network elements

27-Aug-2010

4-1

CRUISE v2010.0.2

Release Notes

2. Surrogate engine modeling using Support Vector Machines to predict arbitrary

engine quantities (air delivery, torque, wall heat losses, exhaust enthalpy flow,
emissions, fuel consumption,...) trained on arbitrary data (engine speed, intake
pressure, EGR rate, injected fuel,...) from either test-bed measurements or highly
resolved BOOST Cycle Simulation models

Figure 4-1: Boost RT window

4.2.1.1. Properties
Output

If activated a result output for this component is made.

Output of Boost RT

For no components
no result output of components of Boost RT model
As defined in components
result output of Boost RT components are depending on the
Output settings in their Properties sections in the Boost RT
model
For all components
Result output for all components of Boost RT model

4.2.1.2. User Defined Variables

Boost RT Project File

The path to the Boost RT project file can be

selected in a file selection dialog. At the same
place there must also be the dbf and stc file of
the Boost RT model. The gas property file is
expected to be in a sub-folder inc\brt.

[-]

C BRT , prj

4.2.1.2.1. Description of Data Bus

The channels (inport/outport) for the transfer of variables can be activated or deactivated
in Description of Data Bus. In this folder 100 inports and 100 outports could be selected.
By inserting a new channel a description for each channel could be entered and the unit
for the variable which should be transferred could be chosen. An additional column defines
if the selected data bus connection is optional or required (default: optional).

4-2

27-Aug-2010

Release Notes

CRUISE v2010.0.2

4.2.1.3. Equation System

The Boost RT component serves as an interface to the program AVL Boost RT. In the
Boost RT model an analogue interface component Cruise Model exists. The data transfer
between Cruise and Boost RT is done through these two interface components and their
Databus channels.

4.2.1.4. Creation of Boost RT Files with Boost RT GUI

In the Boost RT model, insert the component Cruise Model and connect it
mechanically with the Engine

Make the necessary Databus connections between Boost components and interface
component Cruise Model

In component Cruise Model, set Mode switch to export

Choose Simulation | Run | Model Creation

Boost RT creates a special Case.EXPORT-folder where the created dbf, stc and
prj file is put in. The gas property file is copied into a sub-folder inc\brt.

Note: Creation of Boost RT files for usage within a Cruise model will
be possible from the next Boost RT release 2010 on.

4.2.2. External Battery

The interface to External Battery is based on the existing Interface of CRUISE to
MATLAB/SIMULINK and contains an electrical pin. A Battery model created and
parameterized under SIMULINK has to be first compiled to a so called Dynamic Link
Library (DLL) under Windows before being connected to the whole computational
electrical system of CRUISE.
The input and output variables will be transferred by means of inports and outports.
These ports create the interface to the MATLAB Module and are available at the
CRUISE Data Bus. As the simulations of both systems place at the same time in this case,
the integration steps of the two programs will have to be harmonized by a suitable
selection of the step width.
Interface Restrictions
According to the physical parameter by which the electrical system is controlled the first
inport and the first outport must be held for the physical variables (current and voltage).
Voltage guided electrical system: Cruise model transfers current to external Battery
and this last one returns voltage. That means the current terminal voltage is a returned
value from the external Battery.
Fixed Channels:
INPORT[0]

electrical current. This is directly transferred via electrical pin.

OUTPORT[0] external voltage from the Battery model. This voltage is also linked directly
into Cruise electrical system via electrical pin.

27-Aug-2010

4-3

CRUISE v2010.0.2

Release Notes

Current guided electrical system: in this case, input variable to the external battery is
terminal voltage and output variable is electrical current.
INPORT[0]

Terminal voltage. This is transferred to interface via electrical pin.

OUTPORT[0] delivered electrical current from the Battery model. This current is also
transferred into Cruise electrical system via electrical pin.

4.2.2.1. Properties
Switch Output
A result output for this component is made if this switch is activated.

4.2.2.2. User Defined Variables

C EQH , Lib

Name of Battery model Library

[-]

(can be selected in a file selection dialog)

4.2.3. CarSim
The CarSim component defines the interface in Co-Simulation between Cruise powertrain
models calculated with the SAM calculation task and the CarSim simulation package.
In every time step, Cruise data (selected by the user) goes to the CarSim application
through Data Bus input channels Cruise to CarSim, and from there, data comes back to
Cruise through output channels 'CarSim to Cruise' which can be connected to the other
Cruise components.
This interface allows user to easily establish a working Cruise powertrain model for Cruise
CarSim Co-Simulation.
Please refer to the Interfaces Manual for more information.

Figure 4-2: CarSim window

4-4

27-Aug-2010

Release Notes

CRUISE v2010.0.2

4.2.3.1. Properties
Output

If activated a result output for this component is made.

4.2.4. nD-Table
The component N-Dimensional Lookup Table interpolates a user-defined function which
can be up to five dimensions. It has five Data Bus inputs for the independent function
variables and five Data Bus outputs for the interpolated function value. In the case of less
than five input connected, the leftover Data Bus are ignored.
The type of data and the units can be selected by a special input dialog. Please note that all
data coming via the Data Bus are in SI units. The conversion to the defined unit in the
Lookup Table is then done in the component.
The component N-Dimensional Lookup Table serves for the input of general maps. These
maps can have from one to five independent input values. The output map must be
rectangular, this means that for each combination of the input values there must be an
output value.
Extrapolation is allowed according to the settings of the calculation project.

Figure 4-3: nD-Table window

27-Aug-2010

4-5

CRUISE v2010.0.2

Release Notes

4.2.4.1. Properties
Output

If activated a result output for this component is made.

Index Search Method

Evenly Spaced
If the input data are evenly spaced, i.e. 10, 20, 30. , it is
possible to achieve the greatest speed by selecting this
method to calculate the index solution.
This method is also applicable using irregularly input
vectors, but a creation of an interpolated matrix with evenly
spaced input values will follow. Solution is performed using
linear interpolation.
Binary
Original data of the output map are used. Binary search
algorithm is used in order to find the correspondent output
value. Solution is performed using linear interpolation.
This method might lead to slow performances in calculation
time of models that rely heavily on lookup tables.

4.2.4.2. User Defined Variables

Settings

In this tab it is possible to fill in general properties of input

vector and output matrix.
Name
Text edit box which contains the name of the desired input
or output curve.
Interval (only for input vectors)
Define the range of each input vector.
There are two possible syntaxes:
1) for evenly spaced values; example: values from 1
to 10 with step size 2 insert 1-10:2
2) for irregularly spaced values; example generic
values insert 1; 2.1; 2.5; 2.8; 4;
Unit
Definition of the proper unit for each vector.

Table Editor

Table of output values may be filled in as a vector.

On the left side all values combinations of the input vectors
are shown and the corresponding output must be set.

4.2.5. DC Link
This component, Direct Current Link, serves to couple vehicle electrical systems to voltage
sources like batteries. The component is especially required for coupling Cruise electrical
components to the testing environment systems like HiL or MiL (InMotion, etc.).
The component enables to build up a net voltage by launching and shut down it by turning
off electrical driving. Both processes (build up/cut down of net voltage) are carried out by

4-6

27-Aug-2010

Release Notes

CRUISE v2010.0.2

means of a buffer capacity inside of component which enables a smooth link of voltage
less network to high voltage energy storage systems (like battery).

Figure 4-4: DC Link window

4.2.5.1. Properties
Output

If activated a result output for this component is made.

4.2.5.2. User Defined Variables

The type of data and the units can be selected by a special input dialog. Please note that all
data coming via

C DCL

Capacity

[As/V]

The Capacity is the nominal capacity of buffer capacitor.

Q DCL , init

Initial Charge

[%]

The Initial Charge is the charge of capacitor at beginning of the calculation. It is defined as
percentage of the maximum Charge.

Q DCL , Max

Maximum Charge

[Ah]

The Maximum Charge is maximum capacity of buffer capacitor.

R DCL , Ch arg e

Pre-Charge Resistance

[Ohm]

The Pre-Charge Resistance is resistance during charging process the capacitor.

R DCL , Disch arg e

Discharge Resistance

[Ohm]

The Discharge Resistance is resistance during discharging the buffer capacitor.

R DCL , Line

Line Resistance

[Ohm]

The Line Resistance is the ohmic resistance of DC Link Device.

27-Aug-2010

4-7

CRUISE v2010.0.2

Release Notes

4.2.5.3. Electrical Connection

U DCL , In

Actual Input Voltage

[V]

I DCL , In

Actual Input Current

[A]

U DCL , Out

Actual Output Voltage

[V]

I DCL , Out

Actual Output Current

[A]

4.2.5.4. Computation Criteria

There Three main operating modes:
Pre-charging mode; in this phase the voltage Net will be built up to level of the
connected voltage source.
Full operating mode; in this phase the net system is completely connected to the voltage
source (like battery).
Discharging mode; in this phase the electrical system is switched off. The net voltage
has also to be cut down again.

4.2.6. dSPACE
This feature is using CMC (Cruise Model Compiler) to create library that can be linked
with S-function in Matlab/Simulink for the purpose of building dSPACE RTA for DS1006
from Matlab environment. It can be found under CMC section of Cruise and it is selected
by changing Platform/Compiler option to dSPACE.
CMC files hold all the information about the model. These files are created, compiled for
dSPACE and linked with proper Cruise library. To be able to interact with Cruise model
and exchange some information (control signals, monitoring signals...) between Cruise and
Matlab/DS1006/MicroAutoBox, user should have Interface component placed inside a
model, before running the build. Only Folder 1 and Task 1 will be accessible from outside.
Supported tasks are simulation ones: Cycle Run, Full Load Acceleration, Cruising and
Brake/Coast/Thrust. Recommended solvers are fixed step ones: Simulation 3:FSS BogackiShapine +, Simulation 4: FSS Bogacki-Shapine and Simulation 5:FSS Heun.
This interface opens a variety of possibilities to the user, for example, modeling of a
Testbed configuration in MATLAB using dSPACE specific and dSPACE supported
blocksets of Matlab/Simulink with interface to Cruise where only some selected
components of interest (e.g. Gear Box) are simulated.

4-8

27-Aug-2010

Release Notes

CRUISE v2010.0.2

Figure 4-5: dSPACE window

4.2.6.1. Properties
Output

If activated a result output for this component is made.

4.2.6.2. User Defined Variables

Interface Label

27-Aug-2010

The interface has to be named with an

unambiguous label.

[-]

CCI ,label

4-9

CRUISE v2010.0.2

Release Notes

4.2.7. DC Link Control

This component, Direct Current Link Control, serves to control switches inside of DC Link
Device. The thresholds, for switching from one state to another state are pre definable
variables. In this connection it has two data bus input connections for independent switch
thresholds and Data Bus output as Set Status Switch for switching the DC Link device.
The type of data and the units can be selected by a special input dialog. Please note that all
data coming via the Data Bus are in SI units. The conversion to the defined unit is then
done in the component

Figure 4-6: DC Link Control window

4.2.7.1. Properties
Output

If activated a result output for this component is made.

4.2.7.2. User Defined Variables

The type of data and the units can be selected by a special input dialog. Please note that all
data coming via

t DCC

Activation Time

[s]

For the activation of the DC Link a minimum time required before starting.

Thes DCL ,1 2

Switch 12 Threshold

[Unit]

This threshold means that the switching from first phase (pre-charging DC Link) to the
second one (full operating) is done if the set value from data bus exceeds the value defined
here.
Attention: Threshold default Set Value is time, i.e. when time is selected as threshold
parameters then it is not necessary to make connection at data bus.

4-10

27-Aug-2010

Release Notes

Thes DCC , 23

CRUISE v2010.0.2

Switch 23 Threshold

[Unit]

This threshold means that the switching from the second phase (fully operation) to the
Third one (Discharging of DC Link) is done if the set value from data bus exceeds the value
defined here.
Attention: Threshold default Set Value is time, i.e. when time is selected as threshold
parameters then it is not necessary to make connection at data bus.

4.2.7.3. Computation Criteria

There are three main operating modes of DC Link Control:
After the activation time the status is switched form 0 to -1 (starting pre-charging mode,
i.e. build up voltage net)
Switching 12 Criteria
When time or another input set value (from Data Bus) exceeds the defined threshold value
then the Status is switched to 1 (i.e. full operation).
Switching 23 Criteria
When time or another input set value (from Data Bus) is exceeds the defined threshold
value then the status is switched to -2 (discharging mode, i.e. cut down voltage net).

4.3. Changes in Components

4.3.1. Flange
Speed Governor via Flange Component
The Flange component has a new selection switch Control Variable which can be set to
Speed. In this mode the system speed can be controlled. The desired speed comes through
the new Databus input channel Speed.

Figure 4-7: Speed Governor

27-Aug-2010

4-11

CRUISE v2010.0.2

Release Notes

In speed control mode it is still possible to switch to torque mode. This can be done with
the additional Databus input channel Priorization Level:

0 torque mode

1 speed mode

In a Cruise model there should be maximum one Flange component in speed control mode.

4.3.2. Function
Extra C-Code
A switch in the 'Function' component properties allows additional C-code inputs which will
be merged together during the simulation. It can be added up to 5 additional code
segments with up to 4000 characters.

Figure 4-8: Additional C-Code

C-Code Parser
There is a check button on the C-Code data sheet in the component 'Function' where a
separate validation check of the entered C-code can be performed.

4-12

27-Aug-2010

Release Notes

CRUISE v2010.0.2

Figure 4-9: C-Code Parser

4.3.3. CVT Control

Extension of cvt control (addition of control as algebraic constraint) and more accurate
updates for cvt (in simulation and quasi-stationary calculation).

4.3.4. DCT Control

DCT Control closing
A closing procedure is implemented for the DCT control component. Now together with
launch characteristic a closing characteristic can be selected and the DCT clutch (even or
odd) will be opened following the selected trajectory.

Figure 4-10: Clutch Disengagement Characteristic in DCT Control

27-Aug-2010

4-13

CRUISE v2010.0.2

Release Notes

4.3.5. Extension of DC Converter

The DC/DC Converter component has been extended with a new selection switch Desired
Voltage Controller and a resistance option for losses. The resistances can be defined either
as constant value or as characteristic dependent on any input variable from Data bus.
With the new Voltage Controller the voltage at one side of DC/DC converter can be easily
controlled at target one according to the current operating mode

Figure 4-11: DC/DC Converter windows

4.3.6. Torque Converter

Temperature-depending K-Factor
K Factor option in the Torque converter has a possibility to input data function of the
temperature. There is a dynamic multiple page creation where it is possible to set up to 5 k
factor curves.
(Possibility of doing the same for the other options in the next future)

4-14

27-Aug-2010

Release Notes

CRUISE v2010.0.2
Figure 4-12: Temperature depending K-Factor

4.3.7. Vehicle
Road Gradient From Data Bus
When the new properties window button Road Gradient From Data Bus is activated, the
Vehicle gets the gradient value through the new Databus input channel Road Gradient
External.

Figure 4-13: Road Gradient From Data Bus

4.3.8. KULI 8.xx

Cruise supports Kuli versions 8.x also.

4.3.9. Flowmaster 7.7

It is now possible to start Flowmaster without special extra settings in Cruise.

4.4. Changes in Tasks and Task Components

4.4.1. Shifting Map Generation Wizard
GSP Wizard is a very efficient method to generate gear shift patterns. It is a trade-off
between fuel economy and driving performance:

Upshift is done when driving performance is also available in the next Gear or the
maximum engine speed is achieved

In the middle and lower area the fuel economy is taken into account by using best
points of BSFC map

Up-/downshifting points are fixed along the optimum section considering a free
definable hysteresis

27-Aug-2010

4-15

CRUISE v2010.0.2

Release Notes

Figure 4-14: GSP Wizard

4.4.1.1. GSP Wizard Settings

Input Parameters from BSFC (Brake Specific Fuel Consumption):

Opti

Partial Load:

[%]

It corresponds to the determined optimal engine

data. Data provided from BSFC.

N Opti , Min

Minimum Engine Speed:

It corresponds to the NVH speed limit.

N Opti

Engine speed:
It is speed of the optimum point in terms of fuel
consumption (provided from BSFC).

TOpti

Engine torque:
It is corresponding to the optimum point in
terms of fuel consumption (provided from
BSFC).

v Hyst

Tolerance Minimum:

[%]

Hysteresis between Downshift and Upshifting

points. It is the smallest allowed offset velocity
between both points.

Input Parameters Drivability Upper/Kick Area:

Kd , Fl

Downshift 2 1: Kickdown/Full Load:

[-]

Ratio of Kickdown point to full load point for

Downshift 2 1.

Dr

4-16

Overlapping:

[%]

27-Aug-2010

Release Notes

CRUISE v2010.0.2

overlap of vehicle driving ranges of the

adjoining gear steps in percentage

t Offset [i ]

Offset Time [Upshift ( )-Kickdown ( )]:

[s]

Offset time between upshifting point (full load)

from current gear to the next gear and the
kickdown from next gear to the current gear.

vOffset [i ]

Offset velocity [Downshift ( )]Kickdown ( )]:

[km/h]

Offset velocity between downshift point (full

load) from next gear to the current gear and
kickdown from current gear to the lower gear.

4.4.2. Elasticity with Speed

It is now possible to define a starting engine speed instead of velocity, as well as speed
measuring points.

Figure 4-15: Elasticity with Speed

4.4.3. Shifting according to Desired Gear

In every task where it is possible to connect the shifting process in the cockpit databus
Target Gear now it is necessary to select Gear Selection both for
upshifting/downshifting.

Figure 4-16: Shifting according to Desired Gear

27-Aug-2010

4-17

CRUISE v2010.0.2

Release Notes

4.5. Changes in Calculation Center

4.5.1. CMC Calculation
Cruise Model Compiler (CMC) feature enables you to build all input data into Cruise
Kernel from the selected model.
Model should be prepared using Cruise GUI as usual and after that it is possible to proceed
to the Calculation Center where new executables with build-in data will be created.
After adjusting few settings, CMC create stage is started by clicking on the Start
calculation icon.
It is possible to create CMC executable or library for Windows, Linux and dSpace platform.
Depending on selected CMC-Mode options, the resulting output is cmc.exe, libcmc.lib,
cmc.dll (Windows) or cmc.exe, libcmc.a, cmc.so (Linux). Output files will be located in the
'path_to_my_model\inc\cmc\cmc_output' folder.
Once created, CMC executable or library can be copied where needed and used in the same
way Cruise Kernel would be used. Significant difference is that the calculation is limited to
the model which was used to create CMC executable or library. The only way to alter
certain specific input data is through xml files, but this is possible only if it was anticipated
during the creation of the CMC executable or library.
There are two main categories of CMC executables and libraries:
1) without output
2) with output
Without output version is very useful if CMC will be used on the real time platforms which
don't have the usual input capabilities.
With output version is useful when you want to give somebody to view the results of a
certain model, and you don't want to enable viewing the model itself and/or changing of
input data.

4.5.1.1. Using CMC

Once the model is prepared you can proceed to create CMC executable or library.
To start CMC feature go to Calculation Center on the Desk tab and select CMC option:
Desk Calculation Center CMC.

4-18

27-Aug-2010

Release Notes

CRUISE v2010.0.2

Figure 4-17: CMC Window

Since CMC feature is possible to use for several platforms, first step has to be selecting
working platform.

Figure 4-18: Platforms for which CMC can be used

Windows VisualC 9.0
Requirement to use CMC is having installed Visual C++ Express Edition building tools,
which can be found here:
http://www.microsoft.com/express/Downloads/
Downloading and installing it is straightforward, just follow Microsoft instructions.
Once you have done it, CMC for Windows is ready to use.

27-Aug-2010

4-19

CRUISE v2010.0.2

Release Notes

If you are not satisfied with the default settings, before you start building new CMC
executable, you should adjust the settings on the CMC page:
CMC-Mode
Combo box CMC-Mode lets you choose whether your resulting executable or library will
produce result output or not.
Create Executable
Create Static Library
Create Dynamic Library
These checkboxes enables you to select which output files CMC will produce. For example,
if you only need cmc.exe, uncheck the other two boxes.
Allow Dynamic Library Loading
You will find this option useful if you build a model for a platform which doesn't allow any
input from file system. In such a case, it is not possible to dynamically load any library.
Since some model components load libraries dynamically, you should check this option and
CMC will than stop creation of new executable if it detects dynamic loading. You should
than look at your model and prepare it in a way that it doesn't load any dynamic libraries
(dll). After repairing the model, restart CMC. This early detection will save you time.
Run Full Calculation
This option also serves to save your time. When this is checked, during creation stage CMC
will run complete calculation of your model. This is useful if you want to recheck
correctness of your model while creating CMC executable or library. On the other hand, if
your model is very big and calculation is long, you might want to leave this unchecked. In
that case CMC will detect all input data, but will skip calculation.
Show Libraries in Explorer
When this option is checked, Windows Explorer will be started in the folder where CMC
has put created files. If you do not need this, uncheck it.
Active online monitor
If you like to view the execution of your model, you should check this option. It is only
useful when Run Full Calculation is also checked.

Matlab S-function
There are no additional requirements compared to the Windows Visual C9.0 requirements,
when it comes to pure file preparation for Cruise S-function. For the Cruise S-function
model usage, proper Matlab installation is required.
End product of the calculation, is cmc.dll that is loaded in precompiled Cruise S-function.
During build procedure other relevant files are also placed into a working directory.
If you are not satisfied with the default settings, before you start new S-function build of
the current model, you should adjust the settings on the CMC page. All the setting
descriptions are Windows VisualC 9.0 related. Three new options are available: Task,
Folder and Matlab. Task and Folder are necessary for running Cruise from S-function,
because only one task and one folder can be run when Cruise is used externally. Matlab

4-20

27-Aug-2010

Release Notes

CRUISE v2010.0.2

checkbox is used to create dummy model for dSPACE. When this option is activated
Matlab is started and CreateSFModel function is executed.

dSpace
Additional requirements compared to Windows Visual C9.0 platform for using dSPACE
builder from CMC are installed dSPACE tools with GNU C Compiler. End product of the
calculation, is library that can be linked with Cruise S-function in Matlab/Simulink during
the build process for dSPACE DS1006 RT system.
Library is created in two steps:
1. CMC is called, and CMC .c files of a current model are created. These files contain all
the input data of a selected model.
2. CMC .c files are compiled with dSPACE compiler and linked with Cruise library for
dSPACE that comes with Cruise installation.
If you are not satisfied with the default settings, before you start building new dSPACE
library of the current model, you should adjust the settings on the CMC page. All the
setting descriptions are Windows VisualC 9.0 related. LoadLib option is by default turned
off, because only static link is supported by dSPACE. CMC-Mode is by default set to w/o
output because no file manipulation functions are available on dSPACE. Three new
options are available: Task, Folder and Matlab. Task and Folder are necessary for running
Cruise from S-function, because only one task and one folder can be run when Cruise is
used externally. Matlab checkbox is used to create dummy model for dSPACE. When this
option is activated Matlab is started and CreateModel function is executed. For more
information refer to the Cruise on dSPACE user guide.

27-Aug-2010

4-21

CRUISE v2010.0.2

Release Notes

4.5.2. System Variation

In the System Variation a list of all the models systems appears where a subset can be
selected for calculation. The results can be viewed similar to Component Variation.

Figure 4-19: System Variation

4.5.3. Solvers

adaptation of simulation2 for DAE

mixed discretization for fixed step solvers

4.5.4. Extension of Electrical System

A system can be added as constraints (combined solution in contrast to embedded) for
simulation. Also now mixed mode, combined embedded solution is needed due to
constraints linking two networks.

4.6. Changes in Post-Processor

4.6.1. Support of IMPRESS Chart and Concerto
To simplify data analysis and visualisation of CRUISE results in AVL Concerto, CRUISE
creates the required "structure.ppf" files (that describes the locations of single calculation,
variations and their variants) and "result.ppd" files (that describe the result channels).
To open CRUISE results in Concerto, the user has to create a new "Data Source" of the
type "AST Simulation" in Concerto's Data Explorer, that points to a folder that contains a
valid "structure.ppf". For single calculations and variations this means the "version" folder

4-22

27-Aug-2010

Release Notes

CRUISE v2010.0.2

of a project, for single variants of a variation the case-set folder (e.g.

"\variations\case_1.set_1").

Note: Concerto will support CRUISE results from it's next major
release.

Note: GIDAS output format has to be selected in CRUISE

Figure 4-20: IMPRESS Chart with Cruise Results

27-Aug-2010

4-23

CRUISE v2010.0.2

Release Notes

Figure 4-21: Concerto with Cruise Results

4.6.2. Scroll-back of time line in Online Monitor

After the calculation or during pause of calculation it is now possible to scroll back the
time line.

4.7. Others
4.7.1. Map Preprocessor
For some maps there is an option to display how the map will be approximated in the
calculation done by Cruise kernel, accessed by clicking the Approximated Map button
below the map table. It is similar to the standard Trimap3D viewer used for displaying
maps, but modified with some additional features.
Below the menu and toolbar Approximation Viewer window has three sections. Middle and
right section are same as in Trimap3D viewer, displaying a 3D representation of the data
in the middle, and a scale explaining what values colors represent along with a navigation
pane on the right. The difference is the panel on the left side of the window which has the
approximation and interpolation settings. By modifying approximation settings (explained
in previous chapters) and pressing the update button the map approximation map will be
recalculated and redisplayed accordingly. There is also possibility to interpolate on the
approximated map along with the option to choose extrapolation method. Important to
note is that any changes made in the viewer are also applied in the actual map settings and
thus affect the kernel calculation in the same way.
Except for this addition of approximation and interpolation parameters Approximation
Viewer has two more differences to the standard Trimap3D viewer. In the view menu

4-24

27-Aug-2010

Release Notes

CRUISE v2010.0.2

there is an option Original Points which allows displaying the representation of the
original map in the same picture as the approximated one. The other difference is that
table view accessed via toolbar shows both approximated and original points, as well as
absolute and relative differences for the original points. These two features offer visual and
numerical comparison of those two data sets and thus the estimation of just how good the
approximation is with corresponding settings, which allows finding the best combination of
settings for the given map.

Figure 4-22: Map Preprocessor

4.7.2. XML Input Data

There is a possibility to create an XML input file from the Data Favorites, simply by
clicking the XML button in the toolbar and then saving the generated file. Alternatively
there is an option to create the XML file while saving the model but that brings a risk of
overwriting the modified data when starting the calculation since the model is saved at
that point. It is important to save it as it is, both the structure and the name values of
course can, and at some point probably should, be changed. That XML file can then be
used as an additional source of data to the standard dbf file, if something is defined in it
that is used instead of the data from the dbf. Note that it is not meant to replace dbf, but
to supplement it for some of the values.
Most notable use for this functionality is in combination with CMC, where usually all the
data is already in the memory when starting the project and there is no possibility to
change some of it, other than using XML. There are of course restrictions to what can be
changed in this manner, in order to prevent abuse. If there is need for XML input on
execution of a CMC model an XML file with all the objects (attributes, properties, maps
etc.) that need to be changeable has to be present while compiling the model. At that point
a list of allowed objects is created and at execution all others existing in the XML file are
ignored. The XML file needs to be named same as the project was while compiling. For
example if we were building our standard model Man_FWD whose project file is named

27-Aug-2010

4-25

CRUISE v2010.0.2

Release Notes

Man_FWD.prj then the XML file created would have been Man_FWD.xml, at CMC
execution only such a file would be considered and any other ignored.

4.7.2.1. Visualizing and Editing Favorites XML

When Favorites XML file is opened in the browser, the associated XML Stylesheet
(CruiseFavorites.xsl) is called and information contained in the Favorites XML is
formatted and presented as a Web Page. All values contained between <value></value>
tags in the Favorites XML are open for editing.
By pressing "Modify XML" button at the bottom of the Web Page, a new modified XML file
is created in the new browser window (or tab).
Due to differences in how XML is handled in Internet Explorer and Firefox there are two
procedures how to save modified XML file.
For Internet Explorer
Save it by using File|SaveAs... menu option in the new browser window and taking into
account following:

selected Save as type should be - Text File

given filename must have xml extension

Initially the displayed page in the browser window is pure text, but the internal structure
is XML tree. To see XML tree use View|Source from browser's menu.
For Firefox
There is no possibility to save the modified XML directly from the browser, so user should
use Copy&Paste from browser window to some ASCII editor (i.e. Notepad), and then save
XML from there using SaveAs... option.

4.7.3. Online Help in Vehicle Editor

Help option is now also available in the context menu of each Cruise component in the
Vehicle Editor.

4.7.4. New Cruise Installation Possibilities

In the Cruise Installation Routine, the following options are available:
x

Server Installation

One central CRUISE installation will be set up.

Should the installation folder be write protected for a single user, user specific CRUISE
files (projects, config etc.) will be created in the local folder "My
Documents\AVL\Cruise\vNr".
Recommended for single user computers, where the user has the administrator rights.
o

4-26

Private Installation

27-Aug-2010

Release Notes

CRUISE v2010.0.2

User specific CRUISE files will be created in the local folder "My
Documents\AVL\Cruise\vNr", no matter if the central installation is write protected or not.
Recommended for multi user computers, where the users have no administrator rights.
o

Common Installation

User specific CRUISE files will be created in the local folder "all users\AVL\Cruise\vNr" for
all users, no matter if the central installation is write protected or not. Recommended for
the team computers, where several users have no administrator rights but want to share
common files such as projects, config etc.

4.8. Main Fixed Bugs

4.8.1. Graphical User Interface
4.8.1.1. GSP Generation
When adding GSP-Generation, loading task from a standard GSP model and then deleting
unused GSP Settings 2, Cruise crashed. This has been fixed now.

4.8.1.2. Online Monitor

Databus connection to Online Monitor from different layers works now correctly.

4.8.1.3. Component Variation

When adding a second component in a Variation Package the first is automatically set to
basic, deleting the first selection. This has been fixed.

4.8.1.4. Cruise Window Title

Cruise window title should always show the project and the version name of the loaded
model. In case a separate file was loaded in some of the CRUISE editors (e.g. summary.log
in the CRUISE text editor) the widow title changed. This has been fixed now.

4.8.2. Calculation Kernel

4.8.2.1. Engine
Fuel Shut-Off
Fuel Shut-Off did not work correctly when the idle speed was higher than the upper
hysteresis of the shut-off speeds. This is corrected now.
Note: solution of this bug in some cases may influence fuel consumption results.

4.8.3. Others
4.8.3.1. cf Unit in Torque Converter
Changing kp*m*10^6/(1/min)^2 to kp*m*10^-6/(1/min)^2

27-Aug-2010

4-27

CRUISE v2010.0.2

Release Notes

It was done in Kernel and in GUI-Unit-System. It was possible to change it to the correct
unit in GUI, but it was not changed per default and not for the old models
Now it is set as a GUI default (for new and old models) and the users will get the warning
about unit change when they open the old models.

4-28

27-Aug-2010