INCA V7.3 Tutorial EN
INCA V7.3 Tutorial EN
INCA V7.3 Tutorial EN
Tutorial
Copyright
The data in this document may not be altered or amended without special noti-
fication from ETAS GmbH. ETAS GmbH undertakes no further obligation in rela-
tion to this document. The software described in it can only be used if the
customer is in possession of a general license agreement or single license.
Using and copying is only allowed in concurrence with the specifications stip-
ulated in the contract.
Under no circumstances may any part of this document be copied, reproduced,
transmitted, stored in a retrieval system or translated into another language
without the express written permission of ETAS GmbH.
© Copyright 2020 ETAS GmbH, Stuttgart
The names and designations used in this document are trademarks or brands
belonging to the respective owners.
INCA V7.3 - Tutorial R01 EN - 03.2020
Content
1 Introduction 7
2 INCA Basics 9
2.1 Concepts 10
3 Preparation 15
4.1 Objectives 17
4.3 Tasks 17
4.3.1 Create a New Database 18
4.3.2 Create a Top Folder in the Database 18
4.4 Questions 19
4.5 Summary 19
5.1 Objectives 20
5.3 Tasks 21
5.3.1 Create a Workspace 21
5.3.2 Create and Assign a Project 22
5.3.3 Configure the Project Hardware 26
5.4 Questions 32
5.5 Summary 32
6.1 Objectives 33
6.3 Tasks 33
6.3.1 Create and Assign an Experiment 33
6.4 Questions 49
6.5 Summary 49
7 Lesson: Measuring 50
7.1 Objectives 50
7.3 Tasks 50
7.3.1 Load the Lambda Calibration Experiment 50
7.3.2 Start and Stop a Measurement without Recording 50
7.3.3 Analyzing Measurements in the YT-Oscilloscope 51
7.3.4 Create a Recorder for Manual Recordings 55
7.3.5 Make a Recording Using a Fixed Recording Interval 59
7.3.6 Creating a Recorder for an Automated Measurement 60
7.3.7 Perform Recordings 63
7.4 Questions 67
7.5 Summary 67
8 Lesson: Calibration 68
8.1 Objectives 68
8.3 Tasks 69
8.3.1 Add Calibration Variables to the Experiment 69
8.3.2 Switch Between the Reference and Working Datasets 72
8.3.3 Download the Current Version of the Calibration Data to the ECU 73
8.3.4 Show Process Point 74
8.3.5 Perform the Calibration Task 75
8.3.6 Save the New Calibration Dataset 79
8.3.7 Edit Several Calibration Variables and Activate them at Once 79
8.4 Questions 84
8.5 Summary 84
9.1 Objectives 85
9.3 Tasks 85
9.3.1 Start the CDM 86
9.3.2 Compare Calibration Datasets 89
9.3.3 List Calibration Datasets 90
9.3.4 Copy Calibration Datasets 90
9.4 Questions 94
9.5 Summary 94
10.1 Objectives 95
10.3 Tasks 95
10.3.1 Export the Database 95
10.3.2 Create an Empty Database 96
10.3.3 Import the Exported Database into the Empty Database 96
10.3.4 Reuse Elements of Experiments 98
10.3.5 Manage Database Objects 98
11 Answers 107
Figures 112
1 Introduction
This tutorial teaches the INCA novice all elementary steps applicable to two typ-
ical tasks performed with INCA: measurement and calibration. The tutorial does
not require any knowledge of INCA.
WARNING
Calibration activities influence the behavior of the ECU and the systems con-
trolled by the ECU. This may result in unexpected behavior of the vehicle and
thus can lead to safety critical situations.
Only well trained personnel should be allowed to perform calibration activities.
WARNING
Sending out CAN messages influences the behavior of the CAN bus network
and the systems connected to it. This may result in unexpected behavior of
the vehicle and thus can lead to safety critical situations.
Only well trained personnel should be allowed to perform CAN message send-
ing activities.
ETAS GmbH cannot be made liable for damage which is caused by incorrect
use and not adhering to the safety instructions.
l Enter string means enter the literal string. Generally, items written like
this are literal, with the following exception:
l Enter <INCA-drive>\INCA\exp1.txt means "substitute the drive
where INCA is installed for <INCA-drive> when entering the string." So if
INCA is installed on the c: drive this instruction means "Enter c:\INCA\-
exp1.txt."
l The INCA main window, the window you see after starting up INCA, is
referred to as the Database Manager throughout the tutorial.
It is recommended that you use a mouse to interact with the graphical user inter-
face that is presented in the instructions in this tutorial. Besides this method,
INCA allows you to access the same functionality using accelerator key codes
(e.g. <SHIFT> + <F3>) or toolbars (icons).
2 INCA Basics
INCA is a measuring, calibration, and diagnostic system that provides com-
prehensive measuring support. INCA aids you in all essential tasks during con-
trol unit calibration, evaluates the measured data, and documents the calibration
results.
INCA lets you read measured data from the control unit and the engine in par-
allel. The program helps you determine measured engine data such as lambda,
different temperatures and voltage values, etc. With INCA, you don't just get a
tool that will adapt to a variety of different control units, but also a system that
will optimize a wide range of different vehicle components.
INCA is an "open system". Consistent implementation of the ASAM-MCD stand-
ard and support for data exchange formats that are established in this envir-
onment allow this program to be used for any ECU interfaces (can be
customized to any manufacturer's control units) and to be integrated in existing
data processing infrastructures.
INCA consists of a measurement and calibration core system which can be
enhanced by various add-ons and customized extensions (e.g. INCA-MIP,
INCA-QM-BASIC, INCA-FLEXRAY) that can be integrated in INCA. In addition to
that, INCA offers open interfaces which allow for the adaptation of INCA core
capabilities as well as the remote control of INCA by other applications.
2.1 Concepts
This section introduces the main concepts and procedures used in the tutorial:
Measurement task
The state of the engine is assessed using sensors. A sensor measures
an engine parameter and makes the value available to the ECU as a num-
ber. The measurement task consists of sampling all sensor values over a
certain period of time, and recording them. The resulting record doc-
uments the engine behavior for a certain set of calibration values.
Calibration task
It is the task of the ECU (Electronic Control Unit) to control the engine so
it exhibits a desired behavior. The ECU uses a feedback process to do
this: it measures the state of the engine using sensors, and then changes
the state of the engine towards the desired behavior using actuators. The
new state is measured and adjusted again and again, until an equilibrium
is reached. Calibration is the process of adjusting the feedback para-
meters in such a way that the car exhibits the desired behavior when the
equilibrium state is reached. Because the state of the car changes as it is
driven, there are many of these equilibrium states, usually called process
points. A car is non-linear system, and the control algorithm cannot rely
on mathematics to determine the feedback values. Instead it looks up
the required actuator settings in a set of tables, using the sensor values
as lookup criterion. The calibration task consists of setting the values in
the tables. The same ECU can have different valid sets of calibration val-
ues implementing a different behavior, one set for a fast car, for example,
and another set for an economical car.
Memory Emulation
Classically, the ECU memory consists of read-only memory for cal-
ibration data. This means that the calibration data can't be changed dir-
ectly. You use hardware, such as the ES1000 system in combination with
INCA, to bridge the ECU's read-only memory with random access
memory. The calibration data are then loaded into the INCA random
access memory, enabling calibrators to change the data on the fly
without having to change the contents of the actual ECU memory.
Some modern ECUs use the CAN bus protocol, which provides cal-
ibration support. If CAN calibration support is implemented in the ECU pro-
gram, it is possible to change the ECU data on the fly without having to
emulate the ECU memory. To make CAN possible the ECU contains a
programmable semi-permanent memory, the contents of which remains
available after a power cycle.
Process point
For any curve or map, the process point is the current lookup value
passed to the ECU. The process point changes with the value of the
measure variable used as lookup criterion into the curve or map. The pro-
cess point can be visualized on the map; in a tabular calibration editor the
cell holding the current lookup value is 'selected'. As the process point
changes, the selection moves across the cells of the table.
Workspace
A workspace is the umbrella combining the experiment, the project, and
the hardware configuration into a consistent file set you can save and
load between calibration sessions.
Experiment
An experiment is a predefined set of windows filled with those variables
and maps needed to perform a certain calibration or measurement task.
An experiment is stored in the database and allows you to quickly set up
INCA for a certain task by loading it.
Project
A project consists of the definition of all values related to calibration, and
a dataset reflecting a certain version of the ECU program and calibration
values. The project is stored in two files: a *.a2l and a *.hex file, and ref-
erenced in the database.
The a2l description file (*.a2l) contains the physical description of the
data and/or parameters of the control unit program, e.g.:
l Structural information
l Memory size
l Address ranges (e.g. of each measured signal and parameter)
l Names of the measured signals and parameters
The hex file (*.hex, *.s19; Intel hex or Motorola format) contains the
control unit program consisting of the code and the data. The contents of
this file can be directly loaded into the control unit and executed by the
respective processor.
Hardware Configuration
The hardware configuration defines the hardware used for a certain task
and, for application hardware, the project to be used and the cor-
responding dataset.
Dataset
The values making up the characteristics, curves and maps are stored in
permanent memory in the ECU, and accessed by the ECU processor. A
set of calibration values stored in the database is called a dataset. Data-
sets are versioned; a certain version corresponds to a certain calibrated
behavior. Datasets are stored in *.hex or *.s19 files and referenced in the
database.
INCA provides the Memory Page Manager to manage different datasets
(working and reference datasets). This is a versatile tool which you can
use to copy memory contents in any direction. For example, it allows you
to read data versions into and from the control unit or copy data from the
working data version to the reference data version or vice versa.
The different datasets of the working page and reference page are stored
separately in INCA as the working dataset and the read-only reference
dataset. Read-only datasets are identified by a red frame.
When loading the first HEX file, the code portion is mapped to the control
unit project (transparent to the user). The data portion of this HEX file is
stored as the so-called "Master" dataset. The master dataset is then
used to also create the required working dataset.
User profile
A user profile is a collection of settings for a certain user determining the
look and feel of the INCA user interface. A profile can be saved and loaded
between sessions. This allows users to quickly configure the INCA user
interface settings to fit their requirements. Profile settings include start
behavior, window size, window arrangement, paths and many more.
Fig. 2-3 shows a functional block diagram of INCA. INCA interfaces with the
ECU and can directly access its memory. A graphical user interface allows the
user to interact with the ECU.
3 Preparation
Before starting with the tutorial you must prepare the system.
You must have an INCA system installed and running on the computer you want
to use for the tutorial. INCA can be started from an icon on the desktop, or from
the Start menu.
Note
The tasks in the tutorial can be performed in demo mode, meaning you do not
need any actual hardware. The hardware is simulated by the ETK Test Device
and the VADI Test Device. The devices are installed along with the INCA soft-
ware; you do not have to install them separately.
1.
Disk drive or root directory containing the corresponding folder
4.1 Objectives
You will ready the INCA system for the Lambda calibration task by setting up the
database you need to carry out the task.
4.3 Tasks
After starting INCA you see the user interface (see image in the next chapter
Create a New Database), the Database Manager. The top left field, Database
Objects, that shows the database tree structure is referred to as the navigator
field in this tutorial. The navigator field shows all elements in the current data-
base. The structure you see reflects the database structure, not the hierarchical
structure outlined in the concepts chapter. You can expand and collapse folders
in the database by clicking the + and - icons, and select objects in the folders by
clicking them, like in Windows Explorer.
The other fields provide information about the object currently selected in the
navigator field.
The bottom left field is used for general comments about the item which is
selected in the field above.
The right side of the Database Manager is variable. Which fields are displayed
here, as well as the information in them, also depends on the type of object
selected in the navigator field.
After this, the navigator field is empty except for the item DEFAULT, which is a
default and empty folder. The second field in the status bar along the bottom of
the screen indicates which database is active: DB:<Tutorial>.
The top folder is displayed in the navigator field as shown in the screen shot
above. Below the top folder you create the other folders in the other lessons of
the tutorial.
4.4 Questions
Answer the following questions to test your understanding of the subject matter
presented in this lesson.
1. The right side of the Database Manager always contains the
same fields.
A. True
B. False
2. Arrange the following steps in the correct order:
A. Create database structure
B. Create database
C. Create top folder
4.5 Summary
In this lesson you learned how to create a new database with its top folder.
5.1 Objectives
In this lesson you set up a workspace for Lambda calibration. The workspace
contains an experiment as well as a project with its hardware configuration. In
addition, you learn to configure the hardware module by adding an auxiliary meas-
urement device.
Project
A project consists of the definition of all values related to calibration, and
a dataset reflecting a certain version of the ECU program and calibration
values. The project is stored in two files: a *.a2l and a *.hex file, and
referenced in the database.
The a2l description file (*.a2l) contains the physical description of the
data and/or parameters of the control unit program, e.g.:
l Structural information
l Memory size
l Address ranges (e.g. of each measured signal and parameter)
l Names of the measured signals and parameters
The hex file (*.hex, *.s19; Intel hex or Motorola format) contains the
control unit program consisting of the code and the data. The contents of
this file can be directly loaded into the control unit and executed by the
respective processor.
Hardware Configuration
The hardware configuration defines the hardware used for a certain task
and, for application hardware, the project to be used and the cor-
responding dataset.
Dataset
The values making up the characteristics, curves and maps are stored in
permanent memory in the ECU, and accessed by the ECU processor. A
set of calibration values stored in the database is called a dataset. Data-
sets are versioned; a certain version corresponds to a certain calibrated
behavior. Datasets are stored in *.hex or *.s19 files and referenced in
the database. These files are binary images of the ECU memory, and
beside the calibration data they also contain the ECU program itself.
5.3 Tasks
The name OneETK is chosen to reflect the environment used in this tutorial: a
setup with a single ETK. An ETK is a parallel interface to the ECU used by INCA.
If the new workspace is selected you see some empty fields on the right side of
the Database Manager that contains the experiments, projects, and hardware
for the workspace. To be able to fill these fields with the appropriate experiment,
project, and hardware, you must first create them.
In order to be able to use a database object in your workspace, you must assign
it explicitly to the workspace.
In this lesson you create the project and the hardware description. In the next les-
son you create the experiment.
Note that only the description, not the calibration dataset, is shown
as a separate database item in the database navigator field. If you
select the new project description 0400 in the navigator field you
see all calibration datasets valid for this description in the Datasets
field on the right-hand side of the Database Manager. Continue
with assigning the newly created project to the OneETK work-
space:
8. Select OneETK workspace in the Workspace folder.
9. Select Project → Add Project/Dataset.
The "Select project and working data" dialog appears.
10. Select the 0400 project in the navigator field on the left-hand side of
the dialog.
11. Select the master dataset 0400 in the Datasets field on the right-
hand side of the dialog.
If you do not explicitly assign a device and close this dialog with
Cancel, an offline device is assigned by default after selecting a
project/dataset. This hardware is intended as a placeholder if you
do not select a device right now and want to prepare your exper-
iment at first.
You see:
l The Experiment field at the top contains the experiment assigned to the
workspace. Because you have not assigned an experiment yet, this field
is empty. You assign an experiment in Lesson: Setting up an experiment.
l Two boxes in the Project/Device field.
The left box has three entries indicating the currently used project data.
l The top entry (0400) is the name of the project description.
l The next entry (WP: 0400_1) is the name of the currently used working
dataset (WP means working page and refers to a 'page' of memory with
the working dataset). Note that you have neither created a working data-
set, nor assigned the name 0400_1. Because a project must have a
working dataset, 0400_1 was created and named automatically by INCA
using the master dataset you loaded earlier as a basis (the use of working
and reference datasets is explained in Lesson: Calibration).
l The last entry (RP: 0400) is the currently used reference dataset (RP
means Reference Page), referring to a read-only copy of the master data-
set.
l The right frame contains the Virtual System:1 entry, the system cur-
rently used. Under the ETKC:1 entry is the hardware module currently
used. Since a project in INCA must always have a hardware module, we
have selected this hardware module temporarily. The hardware module
doesn't represent any actual hardware, and is called a virtual hardware
module.
Note
The TS test system simulates a real hardware. The test system can be used
to measure simulated measured values and change calibration variables
without using real hardware. However, the test system does not perform any
raster check and is, therefore, not suitable for preparing a real experiment. It is
used solely for exercise purposes.
In this tutorial you add the ETK Test Device hardware to the OneETK work-
space.
To configure the project hardware
1. Select the ETKC:1 hardware module in the right frame of the Pro-
ject/Device field in the Database Manager.
2. Select Device → <new device>.
3. INCA analyzes the project and displays the Add new device for
project dialog, with a list of hardware interfaces and associated
devices.
The list is based on specifications given in the project description
file.
4. Select the ETK test device listed under the TS test sys-
tem interface, and click OK.
Now, if you select the OneETK workspace again, you see that the current hard-
ware module has changed to ETK test device:1, and that the same device
is listed for the TS test system:1 interface in the Hardware field. The virtual
system has been replaced by the new device, and has disappeared.
The hardware module you have defined can access the ECU using the defin-
itions given in the project description file. Often, however, you want to use addi-
tional measurements from hardware components external to the ECU. Because
these modules aren't specified in the project description file, you must provide
the description of the values returned by the modules yourself. This task is
called 'configuring the device'. As an example, you now add the VADI analog-to-
digital converter, which resides in the ES1000 rack, to the project hardware mod-
ule.
Note
If real INCA hardware is connected to the computer, you can also have INCA
automatically search for available devices by using the menu option Hard-
ware → Search for hardware. In this tutorial, however, the devices are sim-
ulated, and are added manually.
6. Select VADI test device from the list, and click OK.
7. You return to the Hardware Configuration Editor. The entry VADI
test device:1 (1) is added to the devices listed in the Hard-
ware devices field.
If you now select the VADI test device:1 (1), the right-hand side of the
Hardware Configuration Editor shows the parameters for the new device. The
form with the Parameters tab allows you to set parameters for the entire mod-
ule. The form with the Info tab gives information about the device. The form with
the Channels tab allows you to configure the individual channels of the VADI
device.
For this tutorial, keep the default values, created automatically when you added
the device, for all the parameters of the VADI device.
Note the STOP icons displayed in front of the devices listed in the Hardware
devices field of the Hardware Configuration Editor. The stop sign means that
the device is specified, but not yet active. To activate the devices, you must ini-
tialize them. When you initialize devices, INCA attempts to establish a con-
nection to all the devices specified in the hardware module. For those devices
where the initialization was successful, the icon changes to a sign with an up
arrow to indicate the device is active.
Note
In this tutorial, you can initialize the devices even though no actual hardware is
connected to the computer because the devices are simulated. In a real work-
space, in which you are using real and non-simulated hardware, you can suc-
cessfully initialize and enable these devices only if they are connected and
have a current firmware status. The firmware status is displayed in the Hard-
ware status dialog window or in the bottom toolbar of the experiment.
Additional information about the hardware status is available in the online help
of the Hardware Configuration Editor under "Hardware Status Display".
Note
If the hardware is not automatically initialized, automatic ini-
tialization might be switched off. This is useful in cases such as
preparing workspace and/or experiment offline, when you don't
need to access the hardware. To enable automatic hardware ini-
tialization, go to the Database Manager and select Experiment
→ Experiment without full HW access.
5.4 Questions
Answer the following questions to test your understanding of the subject matter
presented in this lesson.
1. A workspace contains only a hardware description for the current
experiment.
A. True
B. False
2. Which of the following items are part of the project description file:
A. Memory layout of the ECU.
B. Most recent calibration dataset.
C. Master dataset.
D. Format of the characteristic, curves and maps.
E. Format of the variables returning sensor val-
ues.
3. Match the tasks below with the appropriate user interface element
used to perform them:
Tasks:
A. Add a new device.
B. Set the acquisition rate of an auxiliary meas-
urement device.
C. Initialize hardware.
D. Create a project folder.
E. Load a project description file.
User Interface elements:
A. Database Manager
B. Hardware Configuration Editor
5.5 Summary
In this lesson you created the 0400 project, loaded its project description, as
well as a master dataset. You configured the hardware used to access the pro-
ject ECU, as well as the auxiliary VADI device.
6.1 Objectives
In this lesson you learn how to add variables and windows to an experiment and
how to configure them.
Variable
The term variable is used as a collective name for both measure vari-
ables and all types of calibration variables.
Measurement Variables
In general, a measure variable is a value passed by a sensor, and can be
used as a lookup value for calibration variables.
Moreover, it is possible to measure derived or calculated characteristics,
or, with corresponding settings, also calibration variables.
6.3 Tasks
Note
INCA 7.1 uses a new oscilloscope for experiments. The experiment created in
this tutorial already uses this oscilloscope automatically. Experiments created
in older INCA versions can be converted so that the new oscilloscope can also
(exclusively) be used in these. This tutorial indicates when this is possible
using appropriate notes.
Note
The experiment you have created is automatically assigned the
symbol for experiments using the new oscilloscope ( ).
Experiments that support the old oscilloscope are assigned a
modified symbol ( ) so that they can be differentiated.
Note
If you are running an experiment from an older INCA version for the first time, a
dialog box will appear for automatically converting the experiment for the new
oscilloscope. Confirm this dialog box with Yes if you would like to exclusively
edit this experiment in INCA 7.1 in the future. Additional information on using
experiments in different INCA versions can be found in our online help.
The Sources field at the left-hand side of the window lists all hardware devices
in the hardware configuration of the current workspace. When you select a cer-
tain device, the variables list on the right hand side lists all characteristics,
curves, and maps accessed through the device.
Note
Only the icons of variables actually used are described in the tutorial. The com-
plete description of the icons is located in the online help.
Each entry in the variables list is preceded by three icons providing some inform-
ation on the variable.
The first icon shows whether it is a measure or calibration variable:
Measurement
Calibration
The second icon indicates the type of the variable, i.e. whether it is for instance a
scalar, a curve or a map.
Scalar
Boolean (logical)
Vector
Matrix
Curve
Map
Axis
ASCII
Curve axis
Multi-dimensional map
The third icon indicates your access rights for the variable.
Readable and writable
Readable only
In this lesson you use only measure variables, which have a red square as their
first icon.
1. Expand the ETK Test Device:1 entry in the "Sources" field of
the "Variable Selection" dialog.
2. Expand the tree structure of the Functions entry.
A list of functions appears.
3. Select LambdaRegelung from the list.
The entries in the Variables field are now limited to those measure
and calibration variables associated with the Lambda control func-
tion.
4. Scroll through the list and select the variable B_FRMAX.
The following symbol assigned to the variables indicates that they
will be added to the experiment.
You may have noticed that the list of variables contains many entries that are
not of interest to the measurement you are setting up. This makes the process
of searching for the appropriate variables tedious. In this lesson you are only
interested in measure variables and INCA provides a built-in filter allowing you to
limit the list of variables to show only measure variables. In the lesson covering
the calibration task you use another filter, limiting the list to only calibration ele-
ments such as characteristics and maps. Before selecting the rest of the meas-
urement variables, turn on the filter for measured values:
To use filters for variable selection
1. Select Variables → Variable Selection.
The Variable Selection dialog opens. Please note that B_FRMAX is
marked with a blue rectangle. This indicates that the variable is
already being used in the experiment.
Note
When you use the alphabetical filter to search for variables, you can also use
wildcards (e.g. *,?). With these wildcards, you can search for variables where
you only know parts of their names.
Rasters are used to determine the intervals in which measure values are meas-
ured. Which rasters are available is defined in the ECU's projection description
file. You can record only a certain number of measure variables in one raster.
The raster filling display indicates whether further variables can be measured in
the desired raster.
To assign a raster upon variable selection
1. Select Variables → Variable Selection.
The Variable Selection dialog opens.
2. In the Sources field, click on the entry ETK Test Device:1.
3. Select the following variables from the variables list using the fil-
ters:
LR_P_Anteil
LR_I_Anteil
FR
FLR_AP
4. Remove your entries from the alphabetical filter.
You can see in the variables list that Raster_A is being selected for
all of the four variables. In the information at the bottom on the right
you can see that the raster filling level for Raster_A is 3%.
You change the raster of a variable by moving the check mark in
the raster matrix in the column of the corresponding raster (see
also Fig. 4-6).
6. For the variables FR and FLR_AP, select Raster_B.
7. For the variables LR_P_Anteil and LR_I_Anteil, select
Raster_C.
8. Click OK.
The variables that you have selected in this session are displayed
in a new Measure window [2].
Note
If you do not assign the variable to a window upon selecting it, it is displayed in
a standard window. In "Lesson: Settings and user profiles" on page 101, you
learn how to define a standard window for a variable.
Up until now, all variables are presented in measure windows and in identical lay-
out: the variable name display, followed by the corresponding numeric value.
This display type is appropriate for some variables, but you may want to display
other variables in a different format, e.g. in an Oscilloscope or a Measure table.
Oscilloscopes, for example, present the chronological progression of variables
graphically, thus allowing for a varied view of analog and digital variables in mul-
tiple display ranges.
To define during the variable selection in which window a variable is displayed
1. Select Variables → Variable Selection.
The Variable Selection dialog opens.
2. In the Sources window, click on ETK-Testdevice:1.
3. From the variables list, select the following variables with the help
of the filter:
B_LR
B_VL
TVLRH
TVLR
USVK
4. Delete your entries from the alphabetical filter.
Note
There are restrictions towards possible combinations of variable types for win-
dow types. A detailed description of all combinations and restrictions goes bey-
ond the scope of this tutorial. The online help of INCA describes which
combinations of variable types to window types are possible.
In the experiment, the variables are now distributed across Measure window
[1], Measure window [2] and the YT-Oscilloscope. The YT-Oscilloscope
enables a more detailed view of the variables than the measure window. It is
divided into an analog (top) and digital (bottom) area and can be controlled using
its toolbar. The variables contained therein are located in the signal list (right).
As long as the experiment contains only a few elements, you can distribute the
variables via the context menu of the variables onto the respective windows as
outlined above. But this approach is generally very confusing for extensive exper-
iments. In this case, it is better to select the variables in the list of variables and
to arrange them in the Display Configuration.
TVLR2
TVLRH2
8. Drag the variables TVLR2 and TVLRH2 from Measure window [3]
to the YT-Oscilloscope entry and deposit them there.
The variables were moved into the YT-Oscilloscope.
9. Click on the following icon in the toolbar to activate the filter for
Boolean variables:
14. In the context menu of Measure window [2], select Change Wid-
get To → Measure Table.
15. Measure window [2] is converted into a measure table-type win-
dow.
The conversion from a measure window-type window to a meas-
ure table-type window can be recognized by the symbol preceding
the window name changing from to . The term "Measure
window" in the tree structure refers, however, to the name of the
window and is therefore not altered by INCA. That is why you
rename your window to a more suitable name.
16. Highlight Measure window [2] and select Rename in the context
menu. Then replace the current name with the new name, Meas-
ure table.
17. Move the following variables from Measure window [1] to Meas-
ure table [2]:
DTVKA
FRPS
RTV
USVK
18. Highlight Layer_1 and select Rename in the context menu. Then
Note
Elements that were selected in the variable selection, but have
not yet been added to the experiment, are identified by a gray bar.
Note that the display of the bit signals in Measure window [1] has
changed.
c. Click on the right value (the maximum y-axis value) and replace
it with 500.
d. Confirm the changes with <E NTER>.
3. Click OK to return to the experiment environment.
Observe the change to the y-axis for the TVLRH variable in the YT-
Oscilloscope.
Note
You can also change the axis range using the scroll function of
your mouse. To do so, move your mouse pointer over the desired
axis, press and hold <CTRL> and move the scroll wheel of the
mouse up or down.
Note
The first variable axis in the signal list is used as the shared axis. If necessary,
observe the order of the variables before assigning them to a shared axis. You
can change the order by clicking on a variable and dragging it to a new location
within the list using your mouse.
The experiment is now saved and you can load it at any time by selecting the
OneETK workspace in the Database Manager and selecting Experiment →
Open. You can also load another experiment by selecting Experiment → Open
in the Experiment window.
INCA stores not only the variables, but also their formats and the exact size and
location of the windows in which they are displayed. Practice changing the size
of the Measure window [1] and moving it. Re-save the experiment to apply the
new layout.
6.4 Questions
Answer the following questions to test your understanding of the subject matter
presented in this lesson.
1. All numerical variables must be displayed in the same window.
A. True
B. False
2. You can display several variables in a single "YT-Oscilloscope" win-
dow.
A. True
B. False
3. A workspace can have more than one experiment assigned to it.
A. True
B. False
6.5 Summary
You set up the LambdaControl experiment for the measurement task by
selecting the variables to be measured, and changing their display formats. You
also changed the display range of a "YT-Oscilloscope" window. You changed the
window layout and saved the experiment so you can load it later as a shortcut.
7 Lesson: Measuring
Learning time: 45 minutes
7.1 Objectives
In this lesson you make measurements, and record the results. A Recorder Man-
ager is available, which helps you in managing individual recordings and starting
them according to current needs.
In this lesson, you will use the Recorder Manager to create one recorder for
manual recordings, one for recordings with fixed duration and one for automated
recordings. For the automated recordings, you will also specify triggers used for
starting and stopping the recording process.
7.3 Tasks
To start measuring
1. Select Measurement → Start Visualization.
When using this feature routinely, it is more convenient to use the accelerator
key code <F11> to start a measurement.
To stop measuring
1. Select Measurement → Stop Measuring.
When using this feature routinely, it is more convenient to use the accelerator
key code <F9> to stop a measurement.
Note
This does not stop the measurement. When reinstating the dis-
play in the oscilloscope, the display position automatically jumps
to the current point in time of the measurement.
enlargement.
To add a cursor
1. In the oscilloscope window toolbar, click on Cursor ( ) → Add
cursor.
A cursor will appear in the center of the time axis. In addition, a
column is added in the signal list which shows the signal values
where the cursor is.
2. Double-click on the split bar left of the signal list to enlarge it and
make the additional column visible.
3. Move the mouse over the cursor until it is highlighted.
4. Drag the cursor to the desired location on the time axis.
Note
Observe the tool tips at the intersection of signals and cursor
when the latter is moved.
Note
It is best to add a border line before starting the experiment recording. Other-
wise, recording will restart after it has been added.
2. In the toolbar, click on the following icon to filter the variables that
have already been selected.
The variable list shows all variables that are already part of the
experiment.
3. Select the following variables from the list:
B_FRMIN
B_FRMAX
B_LR
FLR_AP
FR
FRPS
LR_I_Anteil
LR_P_Anteil
RTV
TVLR
TVLRH
USVK
4. Click OK.
The variables are now listed in the variables list of the recorder.
11. Hold <Ctrl> pressed and click on the following comment fields:
&[USER]
&[VEHICLE]
12. Click on the following button to move the selected comment fields
from the Available Comments column to the Used Comments
column.
15. Disable the check box Show Output File Properties dialog after
recording.
To define the trigger conditions
1. In the "Recorder Configuration", select the "Triggers" tab.
2. Open the drop-down list in the Start Trigger field and select the
entry MANUAL.
Recorder_Manual starts if F5 is pressed during the recording.
3. Click OK to go back to the Manage Recorders dialog.
To define event markers for the default recorder
Note
Use the event markers to manually identify events in the "Default Recorder"
during a measurement.
To analyze the engine behavior before and after the transition marked by the trig-
ger event you need to record measurement values both before and after the trig-
ger event occurs. INCA enables you to do this by continuously storing the values
it measures in a buffer, even if you are not recording at the time. The time inter-
val to be recorded before the trigger event happens is called pretrigger time, the
interval that is recorded after the trigger event happens is called posttrigger time.
The relation between the start trigger, pretrigger time, and posttrigger time is
illustrated in Fig. 7-2.
Fig. 7-2: Relation between start trigger and pretrigger and posttrigger times.
Instead of specifying a posttrigger interval, you can also specify a trigger to stop
the measurement (e.g. engine speed to drop below 300 rpm). If both a posttrig-
ger time and a stop trigger are specified whichever occurs first prevails.
To make a recording using a start trigger and a fixed duration
1. Create a new recorder (see "Create a Recorder for Manual Record-
ings" on page 55).
2. Rename this recorder to Recorder_Trigger.
3. Add the same variables as in the previous example (see "Create a
Recorder for Manual Recordings" on page 55).
Note
You can also select recorder variables, copy them to a clipboard,
and insert them in other recorders.
The trigger editor is used for defining trigger conditions. All existing
trigger definitions are collected in a list and can be set as start or
stop triggers at a later time.
3. In the Name field at the top of the dialog box, you can set a name
for the condition. This name can be used to define additional trig-
gers. Change the default name TriggerSignal to
TVLRover450.
4. To select variables for the formula, click the following icon in the
toolbar:
All trigger conditions you have defined using different names are lis-
ted in the Defined Triggers field. After collecting several con-
ditions in this field, you can later on quickly activate a certain
condition as start trigger or end trigger by selecting it in the
Recorder Configuration on the "Triggers" tab. The selected con-
dition will then be used as the current condition for recording.
11. Click OK to go back to the Recorder Configuration.
12. In the Start trigger drop-down list, select the TVLRover450 trig-
ger condition.
13. In the Pre-Start Trigger Time (Sec) field, enter a value of 2
seconds.
14. In the Recording Duration (Sec) field, enter a value of 5 seconds.
default recorder. The default recorder can be renamed, but it cannot be deleted.
To enable recorders
1. Start in the "Manage Recordes" dialog and select Recorder_
Manual.
2. Select Enable Recorder (Space) from the context menu.
In the Enabled column, the symbol changes from to .
3. Select Recorder_Period.
4. Select Enable Recorder (Space) from the context menu.
In the Enabled column, the symbol changes from to .
5. Select Recorder_Trigger.
6. Select Enable Recorder (Space) from the context menu.
In the Enabled column, the symbol changes from to .
To start recording for all enabled recorders
You have two options for starting the measurement. Using the first method, you
can start all enabled recorders, including the default recorder; using the other
method, you can start all enabled recorders, excluding the default recorder.
You are in the Experiment Environment.
1. Select Measurement → Start recording (F12).
This initiates the following events:
a. *DefaultRecorder starts recording immediately.
b. Recorder_Manual waits for the manual trigger.
c. Recorder_Period starts recording immediately. After 30
seconds, the recording of Recorder_Period stops. The
recorded values are saved in the output file Tutorial2.dat.
If a file Tutorial2.dat already exists, it will be overwritten.
d. Recorder_Trigger waits for the trigger condition to be ful-
filled. As soon as the value of the variable TVLR exceeds 450,
the recording will be started.
4. Click Save.
To start recordings for all enabled recorders apart from the default recorder
1. In the Experiment Environment, select Measurement → Start Visu-
alization <F11>.
The individual recorders react as described in the previous section.
2. Press the <F5> key to start recording with Recorder_Manual.
To stop the recordings
The recording with Recorder_Period has already been automatically
stopped after 30 seconds.
1. Select Measurement → Stop Measuring <F9>.
This initiates the following events:
a. The recording of Recorder_Manual is finished. The recorded
values are saved in the output file
Tutorialyyyy-mm-dd.dat (whereby yyyy-mm-dd cor-
responds to the current date). If a file with this name already
exists, it will be overwritten.
b. The recording of Recorder_Trigger is finished. The recor-
ded values are saved in the output file Tutorial302.dat. If a
file with the name Tutorial302.dat already exists, the new
file will be named Tutorial303.dat.
7.4 Questions
Answer the following questions to test your understanding of the subject matter
presented in this lesson.
1. How many conditions can you define for a start trigger?
A. 1
B. 2
C. Many
2. How many conditions can be made to apply simultaneously for a
start trigger?
A. 1
B. 2
C. Many
3. If a stop trigger has been defined, the posttrigger time is ignored.
A. True
B. False
4. If a start trigger is activated, the recording duration setting is
ignored.
A. True
B. False
5. Which command starts recording with the default recorder?
A. Start visualization
B. Start recording
7.5 Summary
In this lesson you measured the variables defined for the Lambda Control
experiment. You made a manual recording, a recording with fixed duration and a
triggered recording and saved all results into a file.
8 Lesson: Calibration
Learning time: 80 minutes
8.1 Objectives
In this lesson you display and calibrate the calibration elements associated with
the Lambda control experiment. You learn to use and manipulate calibration
datasets. For calibration you use tabular as well as graphical calibration editors,
and change single values as well as ranges of values.
For modifying several calibration variables and activating them at once, you will
learn how to work with calibration scenarios.
B. The ECU uses look-up tables to determine the required value of an actu-
ator setting as a function of measure variables (see Calibration Task). If
one variable is used to look up one output value, the table is called a
curve, because it can be represented graphically as an xy-curve.
C. A look-up table using two or more measure variables to find one output
value is called a map, because of the analogy to an elevation map; think
of the input variables as the coordinates, and the output value as the elev-
ation of a certain location on the map.
Maps that derive the output value from three or more input values are
called multi-dimensional maps.
Process point
For any curve or map, the process point is the current lookup value
passed to the ECU. The process point changes with the value of the
measure variable used as lookup criterion into the curve or map. The pro-
cess point can be visualized on the map; in a tabular calibration editor the
cell holding the current lookup value is 'selected'. As the process point
changes, the selection moves across the cells of the table.
Dataset
The values making up the characteristics, curves and maps are stored in
permanent memory in the ECU, and accessed by the ECU processor. A
set of calibration values stored in the database is called a dataset. Data-
sets are versioned; a certain version corresponds to a certain calibrated
behavior. Datasets are stored in *.hex or *.s19 files and referenced in the
database. These files are binary images of the ECU memory, and beside
the calibration data they also contain the ECU program itself.
Calibration Scenario
Using the Calibration Scenario Editor, you can configure several cal-
ibration scenarios within the Experiment Environment. Each scenario con-
tains a set of calibration variables. These can be calibrated individually
from each other. Afterwards you can easily activate complete scenarios
on the ECU, i.e. when switching to that scenario, a complete set of cal-
ibration variables gets modified on the ECU at once. This feature allows
you to compare the behavior of variables that belong together, thereby
optimizing data in an efficient way. Such a set of calibration scenarios
including the corresponding settings is called a calibration scenario con-
figuration. In addition to that, it is also possible to save individual cal-
ibration scenarios in external files (e.g. CVX) for data exchange.
8.3 Tasks
l There is a filter you can use to select calibration elements in the variables
list of the "Variable Selection "dialog. Apply the filter by clicking the icon
for calibration variables in the toolbar of the "Variable Selection" dialog.
l When selecting calibration variables in the "Variable Selection" dialog you
can mix characteristics, curves, and maps freely.
Using the skills you acquired in Lesson: Setting up an experiment to add the fol-
lowing characteristic values. Use the filters from the toolbar and the alphabetic
filter.
1. Add the following scalar arith. elements:
FRMAX
FRMIN
2. Add the following curve:
TSPERN
3. Add the following maps:
KFRP
KFRI
KFRTV
Note that the following editors have been added to the experiment:
Both characteristics are presented in the Calibration window [1]. The curve is
displayed in graphical and tabular form in the Combined Editor [2]. The maps
are presented in graphic and tabular form in the Combined Editor [3] . By setting
a different variable using the combo box at the top, you can switch maps in the
Combined Editor [3].
As you may have noticed by now, the experiment is very confusing. In the next
lesson, you will learn how to divide the display of the experiment into layers by
using the display configuration in the Variable Selection dialog.
To divide the experiment into layers
1. Select Variables→Display Configuration.
The "Variable Selection" dialog opens on the "Display Con-
figuration" tab.
2. In the toolbar, click on the following icon to add a new layer:
9. Move and scale the editors so that all can be viewed very well.
WARNING
Calibration activities influence the behavior of the ECU and the systems con-
trolled by the ECU. This may result in unexpected behavior of the vehicle and
thus can lead to safety critical situations.
In the following exercise, you first enter new values for the TSPERN curve in the
table and then refine the calibration using the graphical display.
To calibrate the TSPERN curve
1. Maximize the window of the Combined editor [2].
2. Change the values in the cells using the same methods as for
changing parameter values:
x=0: z=0.5
x=100: z= 1.2
x=200: z=1.3
x=300: z=1.2
x=400: z=1.35
x=500: z=1.35
3. Change the value for x=500 by reducing the x-value from 500 to
450
The curve now appears in its new shape, according to the values
you entered in the table. Note that the curve is not smooth.
To smoothen the curve using the graphical area of the editor
1. Click the little triangle on the curve representing the value of
TSPERN at x=300.
A colored mark indicates you can now change the value for x=300.
2. Drag the triangle to a new position on the chart so the curve looks
smooth.
Note
When calibrating the arith. elements, also consider the Diff counter in the
upper area of the experiment. It counts the total number of performed changes
in bytes, thus allowing a quick overview of the differences between the ref-
erence and working page.
4. Enter 1.1 in the edit box and click OK to go back to the Combined
editor.
All selected values were increased by 10%.
TSPERN
KFRP
KFRI
KFRTV
4. Click OK.
The variables are added to the calibration scenario configuration.
To create an external calibration scenario
1. In the "Scenario" menu, select New scenario.
A new scenario with the name Scenario-01 is created.
2. In the "Save" menu, select Save configuration.
3. Select Rename scenario from the context menu of the new scen-
ario.
The "Rename scenario" dialog box opens.
4. Enter CalScen_Data as its new name.
5. Click OK.
Note
When you perform the calibration task online, the values are enabled on the
ECU immediately upon activating the scenario.
Note
Only those calibration variables that are part of the scenario are written to the
data exchange file. If you save the external scenario in an existing file, all pre-
viously saved variables get deleted.
8.4 Questions
Answer the following questions to test your understanding of the subject matter
presented in this lesson.
1. How many curves can you calibrate in a single combined editor in
3D display?
A. 1
B. 2
C. Many
2. How many parameter values can you calibrate in a single oper-
ation?
A. 1
B. 2
C. Many
3. How many map values can you change in a single operation?
A. 1
B. 2
C. Many
4. Which of the following descriptions best describes changing the
display format of a calibration element?
A. Use the menu of the calibration editor to get a
list of displayed calibration elements and their
format settings. Change the setting for the
appropriate calibration element.
B. Move the calibration element to a new win-
dow. Before the new window is displayed, you
can set the format to the desired format.
C. Right-click the element and select the desired
format from a context menu.
8.5 Summary
In this lesson you added the calibration elements for the Lambda control exper-
iment to the Experiment window. You know the difference between reference
and working page. You calibrated characteristics, a curve, and some maps by
applying changes to both individual values and ranges of values.
Moreover you have created a scenario by means of the Calibration Scenario
Editor in order to activate several calibrations at once. You have saved the cal-
ibrated variables in a data exchange file to be able to use them elsewhere.
9.1 Objectives
You can use the Calibration Data Manager for managing calibration datasets.
You document your calibration task, save the results in a data exchange file,
compare different datasets and merge different datasets into a new reference
dataset.
Dataset
The values making up the characteristics, curves and maps are stored in
permanent memory in the ECU, and accessed by the ECU processor. A
set of calibration values stored in the database is called a dataset. Data-
sets are versioned; a certain version corresponds to a certain calibrated
behavior. Datasets are stored in *.hex or *.s19 files and referenced in the
database. These files are binary images of the ECU memory, and beside
the calibration data they also can contain the ECU program itself.
9.3 Tasks
When performing calibrations over the course of a project it is useful to be able
to manipulate and compare different versions of the calibration dataset you are
working on. With the CDM you are able to perform these tasks. The CDM can be
started from the Database Manager, and runs in its own application window,
just like the Experiment window.
For working in the CDM, you can distinguish between two main use cases. For
the calibrator it is useful to document his work and save it to a data exchange
file. The task of the responsible calibrator consists of merging the different cal-
ibration datasets into a new dataset.
The CDM offers three main possible actions: List, Compare, and Copy. All three
actions which you can perform with the CDM have similar user interfaces. It is
best to start the CDM and look at its layout.
2. click
or
<CTRL>+<F11>.
The "CDM" appears.
3. In the Action drop-down list, select List.
The Action field in the top-right corner of the CDM shows for which action it is
configured. The labels of the buttons at the bottom right of the window change
accordingly. Now it is displaying List.
The result of an action is always a file. The file path is displayed in the title bar. If
you generate a new configuration, INCA generates this path automatically by
using the system variable ${EcuProjectPath}\.
4. Click on Browse.. to select a permanent directory for your output
files.
The Directories dialog appears.
5. Browse to the ..\ETASData\INCA\CDM\.. directory.
6. Click OK.
7. In the field Output base name, enter Tutorial and click
<E NTER>.
The result file path in the title bar has changed to reflect the changes you made.
To be able to use a single file path for output files with the same name, INCA
adds an action control code to the file name, e.g. Tutorial_CPY.TXT. The
action control codes are _LST, _CPY and _CMP for the copy and compare
actions, respectively.
8. Select the Copy option from the Action list field and look at the
changes to the output file name in the title row.
INCA added the action control code _CPY to the name.
9. Change back to the List action.
The Format field below the Action field specifies the output format for the file to
which INCA exports the result of the action. Selecting a certain format determ-
ines the extension of the output file.
10. Click the arrow button of the Format combo box, and select HTML
from the drop-down list. Observe the changes to the output file
name in the title row. The file name should now read <INCA
base>\ETASData\INCA\cdm\Tutorial_LST.HTM
The Variables to process group below the Format field contains a list box with
the variables the action is applied to. The label above the list box shows how
many variables of a total number of variables available in the project are selec-
ted for the action.
To select a source dataset
1. Select Datasets → Select source dataset.
The "Select source dataset" dialog appears.
2. Expand the tree structure of the Tutorial database and navigate
to the folder Project _0400. Select the project 0400.
The datasets 0400 and 0400_1 appear in the right half of the dia-
log in the Datasets field.
3. Select the 0400_1 dataset in this field, then click OK to get back
to the CDM.
To add variables
1. Select Variables → Add.
The "Variable Selection" dialog opens. Further information on the
Variable Selection dialog can be found in Lesson: Setting up an
experiment.
2. Using the procedures that you learned in Lesson: Calibration,
select the following calibration variables:
FRMAX
FRMIN
TSPERN
KFRP
KFRI
KFRTV
3. Click OK to return to the CDM.
The fields List source and All datasets in the CDM define the datasets that
serve as source and destination for the action to be performed. Their use
depends on which action is performed, and is explained below, in the sections
dealing with the individual actions.
The Results group in the bottom-left corner contains six custom controls that
look like LEDs. Each of these controls reports on a specific aspect of the per-
formed action, e.g. errors or warnings. The number to the right of the LED indic-
ates how many errors, warnings, etc. were reported for the aspect related to the
control. The status of these controls is continually updated as the action pro-
gresses. Click any of the LED controls to review details about the aspect related
to the control.
Note
You can also call up the application data manager directly from
within an experiment. Steps 89 to 89 in this tutorial are then auto-
matically performed for the reference and working pages of the
experiment. Please see our online help for additional information
about this process.
10. Select Copy from the context menu of the dataset 0400.
11. Select Paste from the context menu of the Datasets list box.
A new dataset named 0400_2 is generated and added to the list
of datasets. The dataset is selected.
12. Click OK to return to the CDM.
In the following steps you can use the new datasets for copying
the calibrated variables into it.
13. Select Add all from the context menu of the Variables to process
list box.
The six variables that have been calibrated as well as auxiliary vari-
ables are added to the list box.
14. Change the entry in the field Output base name into Tutorial_
copy.
15. Click on the Copy all button in the lower right.
The "Results" window (bottom left) displays that there are 225 new
labels. These are the additional calibration variables in the target
dataset, but not in the cdfx file.
16. Click on the red controls and view the reports on the individual res-
ults.
17. Close the reports.
If the new dataset is okay, set it to write-protected. This will prevent any unin-
tended changes. Moreover you can use it as a new reference dataset for further
calibration activities.
To activate write-protection for a dataset
1. Select Freeze working data from the context menu of the des-
tination dataset 0400_2.
A dialog box opens which prompts you to enter a name for the
write-protected dataset.
2. Enter 0410 and press <Enter>.
The dataset is now protected against further modifications. Since
a write-protected dataset cannot be modified, a new destination
dataset 0410_1 has been created.
To copy the contents from further data exchange files, replace the file in the
Copy source list box by the desired data exchange file and repeat the copy
action.
It is possible to apply actions in the Calibration Data Manager to several des-
tination datasets at once.
For exercise purposes, compare the dataset from an application engineer with
the original reference dataset and your newly created reference dataset.
To compare two destination datasets with a source dataset
1. In the Action drop-down list, select Compare.
2. In the Format drop-down list, select HTML.
3. Select the dataset 0400 as source dataset.
9.4 Questions
Answer the following questions to test your understanding of the subject matter
presented in this lesson.
1. Which of the following actions can be performed using the CDM?
A. Database import.
B. Copying a dataset.
C. Writing calibrations of variables into an HTML
file.
D. Database export into a CVX file.
E. Listing all calibration variables and their values
into a CVX file.
2. Which actions are available in the Actions field of the CDM?
A. Copy, list, compare.
B. Export, Import.
C. Add, remove, duplicate.
3. Which dataset will be overwritten in a copy action?
A. Source dataset.
B. First destination dataset.
C. Second destination dataset.
9.5 Summary
In this lesson you have learned how you can use the Calibration Data Manager
and its actions to manage and edit your calibration datasets.
10.1 Objectives
You can use the Calibration Data Manager for managing calibration datasets.
You document your calibration task, save the results in a data exchange file,
compare different datasets and merge different datasets into a new reference
dataset.
Database Objects
Database objects are all elements of the INCA database that are listed in
the Database Objects list box. Examples are workspaces, experiments
and projects.
10.3 Tasks
In this lesson you export the data you created in INCA and import them into a
new database. You learn how to manage your data within the database.
4. The "Export file" dialog appears. Change the file name in the File
name field to Tutorial-copy.exp64.
5. Click Save to export the file and to return to the "Database Man-
ager".
Deactive the option Replace objects with same object ID. This
makes sure that the imported objects will be inserted as copies
of the original objects, even if the original objects are part of the
database.
Activate the option Import in selected path of database. This
makes sure that the imported objects will be placed into the
selected folder.
Activate the option Keep folder structure from the export file.
This makes sure that the original folder structure will be kept,
instead of placing the objects flat into one folder.
6. Click OK.
7. The Import dialog box appears. Make sure all entries in the list
box are selected and click OK.
8. The "Import results" dialog appears, listing the items that have
been imported. This dialog is for your information only; no action is
required. Click OK to return to the Database Manager.
The imported items are created in the Tutorial-copy database. The folder
structure is the same as the folder structure of the tutorial database.
Using the import and export function of the Database Manager, you cannot only
write complete databases to an export file, but also individual database objects
such as workspaces, experiments, projects and datasets. Moreover, it is pos-
sible to reuse elements of experiments such as layers and measure and cal-
ibration windows within the INCA database or to export and import them.
Note
Further information on the export and import functionality is provided in video
tutorials which you can access via the INCA help menu: ? → Video Tutorials.
10.4 Questions
Answer the following questions to test your understanding of the subject matter
presented in this lesson.
1. Which of the following elements are stored in the file resulting from
a database export?
A. Project hardware configuration
B. Folder structure
C. Experiment window layout
D. Project master dataset
E. Project working dataset
F. Changes to the calibration elements
2. How can you reuse database objects within the Database Man-
ager?
A. Drag the database object to another place.
B. Copy and paste a database object.
C. Export and import a database object.
3. How should a database be structured?
A. Top folder → Workspace, Experiment, Project
B. Top folder → Subfolder → database object
10.5 Summary
In this lesson you exported a database and reimported it into a new database.
Moreover you learned how to reuse database objects and elements of exper-
iments.
11.1 Objectives
In this lesson, you customize several settings in INCA, and save them in a user
profile.
You also learn how to exchange user-specific settings with colleagues using the
import and export function.
11.3 Tasks
4. A list with the options Yes and No appears. Select Yes to enable
the use of user profiles, and click OK to go back to the "Database
Manager".
Select the tabs to get an overview of the various possibilities. In the remainder of
this section you change several of these settings as an exercise.
First, change the appearance of INCA. You change a font properties and disable
maximizing of windows so new windows you open are not automatically max-
imized. Note that all settings you make in the user profile change the appear-
ance of all INCA windows.
To change the appearance of INCA
1. Select the Experiment tab from the User options dialog.
2. A list with several options appears. Click the cell to the right of the
cell with the value Adjust font in the variable views
if the view size is changed.
A list with the options Yes and No appears.
3. Select No.
With this setting you have defined that in standard measure windows in the
Experiment Environment, only fixed font sizes are used which do not depend
upon the window size.
4. Select the General tab.
5. Using the same method as before, change the setting for Max-
imized windows to No.
Another change that could be useful if you usually calibrate calibration elements
of a certain type is to change the type of calibration editor that is used directly
after you select the element in the Variable Selection dialog. In this exercise,
you define the Table Editor as Default Calibration Editor for arithmetic values.
11.4 Questions
Answer the following questions to test your understanding of the subject matter
presented in this lesson.
1. An entry enclosed in brackets (< >) in an option table means there
is no value assigned to the setting.
A. True
B. False
2. When creating a new user profile all settings are empty.
A. True
B. False
3. Arrange the following steps in the correct order:
A. Change to a new user
B. Turn on the One file for each item setting
C. Click the "Export Import" tab
D. Save the user profile
E. Enable the use of user profiles
F. Create a new user
4. How many user profiles can you define?
A. 1
B. 2
C. Many
5. How many user profiles can you define for one user?
A. 1
B. 2
C. Many
11.5 Summary
You created a new user and created a profile for this user. You imported user
options of a colleague. You familiarized yourself with the various user options
you can use for customization. You customized the profile by changing the
appearance of INCA and changing the default calibration editor for arithmetic val-
ues. You saved and exported your user profile.
11 Answers
11 Further Reading
Unless otherwise stated, the following additional documents are provided with
the basic INCA installation and can be found in one of the INCA folders Manu-
als or Help. Further documents might be provided with INCA add-on products.
Specifications
l CVX (Calibration Values Exchange)5.
1. The INCA online help is automatically installed together with INCA and can be accessed via the
YouTube channel. You can access an overview and the videos themselves via the INCA? menu.
3. The Tool API documentation is automatically installed together with the Tool API component
umentation).
5. This document can be obtained from the ETAS download center (type: specification).
1. The CDF specification is available for download on the web pages of the ASAM Association for
ETAS Headquarter
ETAS GmbH
Figures
Fig. 2-1: INCA System Overview 9
Fig. 7-2: Relation between start trigger and pretrigger and posttrigger times. 61