Manual

XL log Config
CANcaseXL log Configuration
Version 4.0
English
Imprint

Vector Informatik GmbH

Ingersheimer Straße 24
D-70499 Stuttgart

The information and data given in this user manual can be changed without prior notice. No part of this manual may be reproduced in
any form or by any means without the written permission of the publisher, regardless of which method or which instruments, electronic
or mechanical, are used. All technical information, drafts, etc. are liable to law of copyright protection.
© Copyright 2009, Vector Informatik GmbH
All rights reserved.
Manual Introduction

Table of contents

1 Introduction 3
1.1 About this user manual 4
1.1.1 Access helps and conventions 4
1.1.2 Certification 4
1.1.3 Warranty 5
1.1.4 Support 5
1.1.5 Registered trademarks 5

2 General information 7
2.1 Disclaimer 8
2.2 Overview 8
2.3 Supported file formats 9
2.4 Supported bus types 11
2.5 Requirements 11
2.6 Installation 11

3 Getting started 13
3.1 Adding a simple filter 14
3.2 Adding a filter by symbolic message 16
3.3 Adding a simple trigger 21
3.4 Adding a trigger AND group 23

4 Main menu 27
4.1 File 28
4.2 Configuration 28
4.3 Device 30
4.4 Tools 30
4.4.1 CANape/CANgraph 33
4.4.2 Options 33
4.5 Window 34
4.6 Help 34

5 Tool bar 35
5.1 Device selection and project saving 36

6 Tree view 37
6.1 General 38
6.1.1 Device Information 38
6.1.2 Available Log Devices 38
6.2 Main Configuration 39
6.2.1 Overview 39
6.2.2 Channel 1/2 40
6.3 Log Configuration 41
6.3.1 Databases 41

© Vector Informatik GmbH Version 4.0 -I-

Table of contents Manual

6.3.2 Filters 42
6.3.3 Triggers 46
6.3.4 CCP/XCP 57

7 File Manager 61
7.1 Device Flash Drive 62
7.2 Local Drive 69

8 Property panel 71
8.1 Miscellaneous information 72

9 Status bar 73
9.1 Value display format 74

10 Hints 75
10.1 Hexa decimal values 76

11 Appendix A: Address table 77

- II - Version 4.0 © Vector Informatik GmbH

Manual Introduction

1 Introduction

In this chapter you find the following information:

1.1 About this user manual page 4

Access helps and conventions
Certification
Warranty
Support
Registered trademarks

© Vector Informatik GmbH Version 4.0 -3-

Introduction Manual

1.1 About this user manual

1.1.1 Access helps and conventions

To find information The user manual provides you the following access helps:
quickly ¼ At the beginning of each chapter you will find a summary of the contents,
¼ In the header you can see in which chapter and paragraph you are ((situated)).

Conventions In the two following charts you will find the conventions used in the user manual re-
garding utilized spellings and symbols.

Style Utilization
bold Blocks, surface elements, window- and dialog names of the soft-
ware. Accentuation of warnings and advices.
[OK] Push buttons in brackets
File | Save Notation for menus and menu entries
Windows Legally protected proper names and side notes.
Source code File name and source code.
Hyperlink Hyperlinks and references.
<STRG>+<S> Notation for shortcuts.

Symbol Utilization
This symbol calls your attention to warnings.

Here you can find additional information.

Here is an example that has been prepared for you.

Step-by-step instructions provide assistance at these points.

Instructions on editing files are found at these points.

This symbol warns you not to edit the specified file.

1.1.2 Certification

Certified Quality Vector Informatik GmbH has ISO 9001:2000 certification. The ISO standard is a glob-
Management System ally recognized standard.

-4- Version 4.0 © Vector Informatik GmbH

Manual Introduction

1.1.3 Warranty

Restriction of We reserve the right to change the contents of the documentation and the software
warranty without notice. Vector Informatik GmbH assumes no liability for correct contents or
damages which are resulted from the usage of the user manual. We are grateful for
references to mistakes or for suggestions for improvement to be able to offer you
even more efficient products in the future.

1.1.4 Support

You need support? You can get through to our support at the phone number
+49 711 80670-200 or by fax
+49 711 80670-555
E-Mail: [email protected]

1.1.5 Registered trademarks

Registered All trademarks mentioned in this user manual and if necessary third party registered
trademarks are absolutely subject to the conditions of each valid label right and the rights of par-
ticular registered proprietor. All trademarks, trade names or company names are or
can be trademarks or registered trademarks of their particular proprietors. All rights
which are not expressly allowed, are reserved. If an explicit label of trademarks,
which are used in this user manual, fails, should not mean that a name is free of third
party rights.
¼ Windows, Windows XP, Windows 2000 are trademarks of the Microsoft Corpora-
tion.

© Vector Informatik GmbH Version 4.0 -5-

Manual General information

2 General information

In this chapter you find the following information:

2.1 Disclaimer page 8

2.2 Overview page 8
2.3 Supported file formats page 9
2.4 Supported bus types page 11
2.5 Requirements page 11
2.6 Installation page 11

© Vector Informatik GmbH Version 4.0 -7-

General information Manual

2.1 Disclaimer

Information The application of this product can be dangerous. Please use it with care.

With this software it is possible for you to influence or control a networked electronic
system. Your actions can therefore lead to severe personal damages or damages to
property. For this reason, only persons, who have understood the possible conse-
quences of their actions with this software or persons, who have been specially
trained for the use of this software, may use this software.
In case other persons use this software, Vector Informatik GmbH hereby expressly
gives notice that Vector’s warranty shall be limited to the correction of defects, and
Vector Informatik GmbH hereby expressly disclaims any liability over and above the
refunding of the price paid for this software.
Should you integrate this product into a higher-level system by using the product´s
automation interface, please note that the warranty of Vector Informatik GmbH shall
be limited to the correction of defects, and Vector Informatik GmbH hereby expressly
disclaims any liability over and above the refunding of the price paid for this software,
since Vector does not have any influence on the implementations of the higher-lever
system, which may be defective.
Furthermore, Vector Informatik shall in no event be held liable for any user-defined
scripts, regardless of whether or not you turn off this disclaimer when using this prod-
uct in the batch mode.
Should you not agree with the above named limitations, please send the software
back to us at our costs within one (1) month after delivery. We will then immediately
refund the price you have paid.

2.2 Overview

About XL log Config XL log Config enables the configuration of CANcaseXL log devices and offers a wide
range of settings. You may set baud rates, logging triggers and filters and manage
logging files on the SD card. XL log Config also supports trigger and filter access by
symbolic names defined in CANdb databases.
Main features are:
¼ Customizable filters for CAN and LIN messages
¼ Customizable triggers
¼ Support of databases
¼ Support of CCP/XCP
¼ File Management

To become familiar with the capabilities of the tool, have a short look on this overview
and try the first step by adding a simple filter (see chapter Adding a simple filter on
page 14).

-8- Version 4.0 © Vector Informatik GmbH

Manual General information

The XL log Config The window of XL log Config is divided into five parts:
window ¼ (1) Main menu (see chapter Main menu on page 27)
¼ (2) Tool bar (see section Tool bar on page 35).
¼ (3) Tree view (see chapter Tree view on page 37)
¼ (4) Property panel (see chapter Property panel on page 71)
¼ (5) Status bar (see chapter Status bar on page 73)

Please see the specific sections for detailed information.

2.3 Supported file formats

Used and supported XL log Config can handle the following file formats:
file formats

.XCF XL log Config project file. The project file contains all settings made in XL log
Config and additional information like file history, file paths and so forth in
plain text.
Furthermore the project file contains a compressed binary XL log Config con-
figuration which is read directly by the CANcaseXL log. The logger mode
cannot be accessed without a valid XCF file on the SD card.

.XLP This file is saved with the project file if the backup function is activated in
Tools | Options… and menu Configuration | Write to device… or Write to
folder... was selected. This file contains the used database information of the
project and is necessary to read back by Configuration | Read from
device… or Read from folder... to rebuild the databases.

.XLX Binary CANcaseXL log log file, which can be converted to BLF, MDF or XLS.

© Vector Informatik GmbH Version 4.0 -9-

General information Manual

.BLF The BLF Log file is a binary logging format supported by CANape, CANoe or
CANalyzer. This format can be converted from .XLX format using XL log
Config.

.MDF The MDF format is standardized and supported by CANape, CANoe, CANa-
lyzer and other measuring applications. This format can be converted from
.XLX format using XL log Config.

.XLS Tab divided ASCII log file. This format can be converted from .XLX format
using XL log Config.

.XCT XL log Config project file of previous XL log Config V1.1. This format is only
supported for backward compatibility.

File formats overview PC CANcaseXL log

XL Log Config
Hardware / Firmware
c onversion

write read/ read/ read write r ead

write write

BLF XLX
XCF
and other binary
project file log file
log files
USB

read XCF

project file

CANape, CANgraph,
CANoe, CANalyzer

Note: The configuration file must be saved as xllogcfg.xcf on the SD card; oth-
erwise the configuration will not be loaded.

Note: Please note, that the CANcaseXL log supports FAT16 for SD cards only. The
file count is limited to 512 files.

Warning: By unplugging the power supply while messages are received, the mes-
sages are lost within the last second.

Warning: The SD card should not be removed while logging. In order to swap the SD
card, stop logging, replace the SD card and restart the logging.

- 10 - Version 4.0 © Vector Informatik GmbH

Manual General information

2.4 Supported bus types

Networks The CANcaseXL log is able to log data from CAN, LIN and as well as J1708. Since
two channels can be used, the following combinations are valid:
¼ 2x CANpiggy
¼ 2x LINpiggy
¼ 1x CANpiggy and 1x LINpiggy

¼ 2x CANpiggy J1708
¼ 1x CANpiggy and 1x CANpiggy J1708
¼ 1x LINpiggy and 1x CANpiggy J1708
The specific bus types have to be selected in Main Configuration (see section Main
Configuration on page 39).

2.5 Requirements

Hardware CPU Pentium III or higher

requirements
Memory 128 MB RAM or more
Operating system Windows 2000 SP4 or XP SP2

Optional Hardware CANcaseXL log for online configuration

Software Optional Software CANdb++ (can be found on the Vector Driver Disk)
requirements CANape/CANgraph 6.1 SP2 or higher

2.6 Installation

Follow the instructions below to install the XL log Config.

1. Execute the setup, which is found on the Installation CD:
\Drivers\CANcaseXL\Tools\XL_log_Config_Setup.exe or from Autostart
menu of the driver disk Hardware | CANcaseXL / log | Setup XL log Config.
2. Please follow the instructions found there to complete the installation.

© Vector Informatik GmbH Version 4.0 - 11 -

General information Manual

3. After successfully installation, XL log Config can be found (if chosen during instal-
lation) on the desktop Start | Programs | Vector CANcaseXL log | CANcaseXL
log Configuration.

- 12 - Version 4.0 © Vector Informatik GmbH

Manual Getting started

3 Getting started

In this chapter you find the following information:

3.1 Adding a simple filter page 14

3.2 Adding a filter by symbolic message page 16
3.3 Adding a simple trigger page 21
3.4 Adding a trigger AND group page 23

© Vector Informatik GmbH Version 4.0 - 13 -

Getting started Manual

3.1 Adding a simple filter

Example: The following example describes how to insert a simple filter which is used
in the logger mode of the CANcaseXL log. The filter settings block all received mes-
sages except for the specific message which is logged.
This example does not require a CANcaseXL log, since off-line configuration is used.
To configure the CANcaseXL log, it must be connected to the PC with a USB cable.

1. Open CANcaseXL log Config.

2. Open node Log configuration in the tree view.
3. Click on Filters.

4. Select CAN ID in the combo box in the Property panel.

5. Click [Add]. A filter settings dialog pops up.

6. Set Condition type to ID value, below enter the value 10 for decimal or 0xA for
hex decimal value.
7. Select Channel 1 in the combo box Source channel.

- 14 - Version 4.0 © Vector Informatik GmbH

Manual Getting started

8. Click [OK]. The filter is listed in the list view now.

9. Now change the DEFAULT filter from Pass to Stop in order to block all incoming
CAN and LIN messages. You can double click either the green icon in column #
or the item in column Action. It is also possible to change the action by right
clicking on the DEFAULT filter followed by Stop filter.
10. Now change the just added filter action to Pass. This makes sure that only CAN

© Vector Informatik GmbH Version 4.0 - 15 -

Getting started Manual

messages with ID 10 get through and are logged.

11. Write the configuration to a connected CANcaseXL log by selecting the desired
CANcaseXL log device from the tool bar’s combo box followed by the menu Write
to device… or clicking the SD card button in the rightmost of the tool bar.
12. Disconnect the CANcaseXL log from USB to boot the logger mode.
13. With these settings, all received messages are logged which are of type CAN with
the specified ID 10.

3.2 Adding a filter by symbolic message

Example: The following example describes how to insert a filter by symbolic mes-
sage which is used in the logger mode of the CANcaseXL log. The filter settings block
all received messages except for the specific symbolic message which is logged.
This example does not require a CANcaseXL log, since off-line configuration is used.
To configure the CANcaseXL log it must be connected to the PC with a USB cable.

1. Open CANcaseXL log Config.

2. Open node Log configuration in the tree view.
3. Click on Databases.

- 16 - Version 4.0 © Vector Informatik GmbH

Manual Getting started

4. Click [Add…] and select a CANdb file containing the symbolic names.

5. The database is listed in the list view now.

6. Skip to node Filters and add a filter Symbolic name. A dialog pops up which
displays the just added database.

© Vector Informatik GmbH Version 4.0 - 17 -

Getting started Manual

7. Open node Messages in this dialog and select a symbolic name for the message.

- 18 - Version 4.0 © Vector Informatik GmbH

Manual Getting started

8. Click [OK].
9. The filter is now listed in the list view of Filters. In column condition the name of
the filter is displayed. Additionally the message ID and the origin database is
shown in brackets)
10. Change the DEFAULT filter to Stop and the just added filter to Pass.

© Vector Informatik GmbH Version 4.0 - 19 -

Getting started Manual

11. Now you can change the channel assignment of column Chan by double clicking
it or by a right click followoed by Modify channel assignment.

12. The symbolic name of the added filter can be changed every time by double click-
ing it and selecting another symbolic name from the dialog.
13. Write the configuration to a connect CANcaseXL log by selecting the desired
CANcaseXL log device from the tool bar’s combo box followed by the menu Write
to device… or clicking the SD card button in the most right of the tool bar.
14. Disconnect the CANcaseXL log from USB to boot the logger mode.
15. With these settings, all received messages are logged which are of type CAN with
the specified ID of the symbolic name (here ID 3703).

- 20 - Version 4.0 © Vector Informatik GmbH

Manual Getting started

3.3 Adding a simple trigger

Example: The following example describes how to insert a trigger which is used in
the logger mode of the CANcaseXL log. The trigger lets the CANcaseXL log beep if a
valid message is received.
This example does not require a CANcaseXL log, since off-line configuration is used.
To configure the CANcaseXL log it must be connected to the PC with a USB cable.

1. Open CANcaseXL log Config.

2. Open node Log configuration in the tree view.
3. Click on Triggers.

4. Select On CAN ID in the combo box.

5. Select Single trigger in the second combo box

6. Click [Add].
7. Set Level sensitive to == in the dialog which pops up.
8. Enter value 10. This setting will trigger to all received CAN messages with ID 10.
9. Set ID type to Standard ID.

© Vector Informatik GmbH Version 4.0 - 21 -

Getting started Manual

10. Click [OK].

11. Change the trigger action to Beep by few double clicks on the trigger item in col-
umn Action or alternatively by a right click followed by Modify action | Beep.

12. Edit the trigger comment if desired by a double click or alternatively by a right
click followed by Edit comment...
13. Write the configuration to a connected CANcaseXL log by selecting the desired
CANcaseXL log device from the tool bar’s combo box followed by the menu Write
to device… or clicking the SD card button in the most right of the tool bar.
14. Disconnect the CANcaseXL log from USB to boot the logger mode.

- 22 - Version 4.0 © Vector Informatik GmbH

Manual Getting started

15. Now, the CANcaseXL log will beep on every received event which is a CAN
message with ID 10.

3.4 Adding a trigger AND group

Example: The following example describes how to insert a trigger AND group which
is used in the logger mode of the CANcaseXL log. The trigger lets the CANcaseXL
log beep if all conditions in the AND group are valid.
This example does not require a CANcaseXL log, since off-line configuration is used.
To configure the CANcaseXL log it must be connected to the PC with a USB cable.

1. Open CANcaseXL log Config.

2. Open node Log configuration in the tree view.
3. Click on Triggers.

4. Click with the right mouse button into the list view and select New group | AND
group.

5. Enter value 10 in Message ID.

6. Set Message ID type to Standard ID.
7. Set Bus type to CAN bus.

© Vector Informatik GmbH Version 4.0 - 23 -

Getting started Manual

8. Click [OK].
9. The AND group is displayed in the list view.
10. Change the trigger action to Beep.

11. Now click with the right mouse button onto the just added AND group and select
Add trigger action | CAN bus | On CAN DLC.

- 24 - Version 4.0 © Vector Informatik GmbH

Manual Getting started

12. Select Level sensitive == and enter the value 4.

13. Click [OK].
Write the configuration to a connected CANcaseXL log by selecting the desired
CANcaseXL log device from the tool bar’s combo box followed by the menu Write
to device… or clicking the SD card button in the most right of the tool bar.
14. Disconnect the CANcaseXL log from USB to boot the logger mode.
15. Now the CANcaseXL log will beep on every received event which
¼ is a CAN message with ID 10 AND and
¼ with a DLC of 4.

© Vector Informatik GmbH Version 4.0 - 25 -

Manual Main menu

4 Main menu

In this chapter you find the following information:

4.1 File page 28

4.2 Configuration page 28
4.3 Device page 30
4.4 Tools page 30
CANape/CANgraph
Options
4.5 Window page 34
4.6 Help page 34

© Vector Informatik GmbH Version 4.0 - 27 -

Main menu Manual

4.1 File

Menu items

New projects… Clears all settings and restores to default values.

Open project… Opens a project which was previously saved.

Save project Saves the project with the current project name. The project is saved in XCF or XCT
file format.

Save project as… Saves the project with a new project name. The project is saved in XCF file format
and it is used for the start up configuration in logger mode. The alternative XCT file
format can be used for testing purposes and manually editing, but it is not readable
for startup in logger mode.

Exit Closes the application.

4.2 Configuration

Menu items

Write to device… If the CANcaseXL log is connected to the PC by a USB cable, this option writes the
current project to the SD card.
If Tools | Options... | Archive databases to device and Tools | Options... |
Archive CANgraph/CANape project respectively is set to Yes, the databases and
CANgraph/CANape project are stored to the SD card, too.

Write to folder… Same as Write to device… but related to any local drive.

Use from device If the CANcaseXL log is connected to the PC by a USB cable, this option reads the

- 28 - Version 4.0 © Vector Informatik GmbH

Manual Main menu

configuration from the inserted SD card. This is useful in cases, if additional filters or
triggers has to be added and resaved back to the device. This setting can be auto-
mated by Tools | Options… | Configuration auto sensing.

Restore If the CANcaseXL log is connected to the PC by a USB cable, this option reads the
from device… configuration, the archived databases and CANgraph/ CANape project (if available)
from the inserted SD card.
The following options are available in the dialog:
¼ Restore project to following folder
Path where the logger configuration (project) should be saved.
¼ Restore also CANdb files
If activated the databases are saved in the same folder as specified for the logger
configuration (project).
¼ Restore CANgraph/CANape project to following folder
Path where the CANgraph/CANape project should be saved

Restore Same as Read from device… but related to any local drive.
from folder…

Check Checks the configuration for valid settings, e.g. if used piggybacks fit to configured
channels and so forth.

Preview CAN Displays the complete list of passed or stopped CAN IDs, depending on the configu-
standard ID filter ration in Filters (see chapter Filters on page 42).

Preview LIN Displays the complete list of passed or stopped LIN IDs, depending on the configura-
standard ID filter tion in Filters (see chapter Filters on page 42).

Device Mode / The CANcaseXL log can be operated in the following logging modes:
Ring buffer configu-
ration
¼ Normal mode
The data is logged on the SD card as long free space is available. The logging
will stop automatically, if the SD card is full.
Trigger 1 Trigger 2 Trigger 3

pre post pre post pre post free spac

The pre-trigger time is limited to 320 kB.

¼ Multiple file Ring buffer

The data is logged continuously on the SD card. Each new trigger will create a
separate logging range (separate file) with a previously specified buffer range.
The less the buffer range is selected, the more triggers can be logged. If the SD
card is full, the whole logging process will stop. While the ringbuffer is closed and
a new one is opened, few messages might be lost.
Trigger 1 Trigger 2

pre post pre post free space

2 2
2 Ring buffer
2 Ring buffer
t t
The pre- and post-trigger times are limited by the size of the ring buffer only:
pre-trigger size = ring buffer size – post-trigger size

© Vector Informatik GmbH Version 4.0 - 29 -

Main menu Manual

On device start a new file is generated within the free space (means new ring
buffer range).

4.3 Device

Menu items

Real time clock Opens a dialog for real time clock settings. Press [Update] button to write the current
PC time to the CANcaseXL log device. The device must be connected to the PC by a
USB cable and selected in the list box in the tool bar.

Format SD card Formats the inserted SD card of the currently selected CANcaseXL log device. File
system is FAT16.

Update firmware Programs a new logger mode firmware if available, which is delivered with XL log
Conf.

4.4 Tools

Menu items

CANape Allows interaction with CANape. See chapter CANape/CANgraph on page 33 for fur-
ther details.

CANgraph Allows interaction with CANgraph. See chapter CANape/CANgraph on page 33 for
further details.

CANape / CANgraph Detects if CANgraph/CANape is installed and displays several information.

information

Generate This feature requires at least CANape 6.1 SP2 and an ASAP2 file for an ECU. See
CCP database… below, which steps can be taken to edit an ASAP2 file to create the database in off-
line mode.
The checkbox CANape Debuging Mode opens a CANape window containing de-
tailed information while creating a database.

- 30 - Version 4.0 © Vector Informatik GmbH

Manual Main menu

Generation in online mode with an ECU

1. Ensure, that your ECU is connected and running. For testing purpose you can
start CCPsim (please ask support for a CCPsim version without Seed&Key). Be
sure, that CANape and CCPsim are assigned to a virtual channel in Vector Hard-
ware Config, e.g. CANape CAN1 assigned to Virtual channel 1, CCPsim CAN1
assigned to Virtual channel.
2. Click Tools | Generate CCP database… in XL log Config. A dialog appears.
3. Open an ASAP2 file. CANape should access the ECU then.
4. Click on [Select Signals].

5. A CANape dialog opens, where the signals can be chosen and applied.
6. Close the CANape dialog.
7. The selected signals appear in the list of the dialog. Furthermore the acquisition
rate can be changed for each signal. Click [OK].
8. A dialog will appear that the database generation succeeded. Click [OK].
9. The generated database will be listed in tree view Log Configuration |
Databases.

Generation in offline mode without an ECU

In order to generate a CCP database without an ECU being connected (online),

the following steps are necessary:
1. Open the CANape project, where the ASAP2 file is part of it.
2. In the settings for Driver installation, click tab DAQ list.

© Vector Informatik GmbH Version 4.0 - 31 -

Main menu Manual

3. Disable Automatic Detection.

4. Insert new DAQ list with ECU-specific First PID and Count of ODT.
Following lines will be added in the A2L file:
/begin SOURCE
"DAQ List" 0 0
/begin QP_BLOB 0
LENGTH 12
FIRST_PID 1
/end QP_BLOB
/end SOURCE
5. Click Tools | Generate CCP database… in XL log Config. A dialog appears.
6. Open an ASAP2 file.
7. Click on [Select Signals].

8. A CANape dialog opens, where the signals can be chosen and applied.
9. Close the CANape dialog.
10. The selected signals appear in the list of the dialog. Furthermore the acquisition
rate can be changed for each signal. Click [OK].
11. A dialog will appear that the database generation succeeded. Click [OK].
12. The generated database will be listed in tree view Log Configuration |
Databases.

Converts files from Converts logging files (XLX) located on PC or on SD card to BLF, MDF and XLS or
copies them only to a location.

Options… General XL log Config options. See chapter Options on page 33 for further informa-
tion.

- 32 - Version 4.0 © Vector Informatik GmbH

Manual Main menu

4.4.1 CANape/CANgraph

CANape/CANgraph XL log Config is able to interact with CANape or CANgraph via the menu entries in
Tools | CANape or Tools | CANgraph as follows:

Start with current Opens CANape/CANgraph with the CANape/CANgraph configuration set in Tools |
configuration… Options… For this no assigned database is necessary.

Quickview device log Use this option to view the current log files on the SD card in CANape/CANgraph in a
files… single window. This option needs the same databases as were used for the logging,
because the log file content is displayed relating to signal names.

Replace device log This option replaces the first measurement file in CANape Graph with the selected
files… logging file, while keeping the whole view configuration unchanged.

4.4.2 Options

¼ CANgraph/CANape config
Path to a CANgraph/CANape configuration file which should be used together
with XL Log Config.
¼ CANgraph/CANape project
Path to a CANgraph/CANape project folder which should be used together with
XL Log Config.
¼ Archive databases to device
If this option is switched to Yes, all databases are combined in one file and stored
if Configuration | Write to device… or Configuration | Write to folder… is
selected. This setting is useful to use the database information on other PCs.
¼ Archive CANgraph/CANape project
If this option is switched to Yes, the specified CANgraph/CANape project is
combined with the current configuration and stored if Configuration | Write to
device… or Configuration | Write to folder… is selected. This setting is usefull
to use the CANgraph/CANape project on other PCs.
¼ Show only log files in File Manager
When this option is switched to Yes, only log files are visible otherwise all files
with other extensions are shown.
¼ - Log file extension
Here the file extensions of the log files can be specified (default: .xlx). This option
can only be used, if Show only log files in File Manager is set to YES.
¼ Default log file prefix
Prefix to be added to the log files.
¼ Display file notes in File Manager
It is possible to display additional file notes (e.g. title of the session, see Main
Configuration | Overview) in the File Manager either for the local drive only, for
the local drive and the device or never. In order to improve the performance of the
File Manager it is recommended to select On local drive.
¼ Default select all log files
Selects all available log files when entering the conversion dialog.
¼ Configuration auto sensing
This enables the config tool to read the configuration automatically, if an installed
and connected CANcaseXL log is selected (see also Configuration | Use from

© Vector Informatik GmbH Version 4.0 - 33 -

Main menu Manual

device…).
¼ Tray icon operation
Modes for tray icon.
¼ Disable balloon info
If this option is switched to Yes no balloon tips will be shown in the tray menu.
¼ New visual style
Changes the style of the list view.
¼ Border color, Skin color 1, Skin color 2, Feature list color
Color settings for the user interface in RGB
¼ Enable dialog time out
If this option is switched to Yes critical dialogs will have a time out before a button
click is possible.
¼ Show values as (F2)
This is equivalent to a click on Dec or Hex in the status bar and displays the val-
ues in the list view in the according format.
¼ Accept disclaimer
If set to YES, the disclaimer at startup will not be shown anymore.

4.5 Window

Menu items

Hide in tray Hides the window in the tray bar. In order to unhide the window, double-click on the
XL log Conf icon in the tray bar.

Refresh Refreshes the window contents.

4.6 Help

Menu items

Index Opens the online help.

Check for updates Opens the Vector driver web page.

About Information about XL log Config (version number).

- 34 - Version 4.0 © Vector Informatik GmbH

Manual Tool bar

5 Tool bar

In this chapter you find the following information:

5.1 Device selection and project saving page 36

© Vector Informatik GmbH Version 4.0 - 35 -

Tool bar Manual

5.1 Device selection and project saving

Screenshots

List box The list box shows all connected CANcaseXL log devices. If no device is plugged
only offline work is possible. Select a device for online configuration.

Tool bar buttons The left button is equivalent to main menu File | Save project

The right button is equivalent to main menu Configuration | Write to device…

CANape/CANgraph The buttons next to the list box are equivalent to Tools | CANape | Quickview
Quickview device log files… and Tools | CANgraph | Quickview device log files… and
enables to view log inside CANape or CANgraph.

- 36 - Version 4.0 © Vector Informatik GmbH

Manual Tree view

6 Tree view

In this chapter you find the following information:

6.1 General page 38

Device Information
Available Log Devices
6.2 Main Configuration page 39
Overview
Channel 1/2
6.3 Log Configuration page 41
Databases
Filters
Triggers
CCP/XCP

© Vector Informatik GmbH Version 4.0 - 37 -

Tree view Manual

6.1 General

6.1.1 Device Information

Device Information

If this tree node is selected miscellaneous details about the selected CANcaseXL log
device are displayed in the property panel (right part of the window):
¼ Device
Name of the currently selected CANcaseXL log device with its hardware index
(one based).
¼ Serial number
Serial number of the currently selected CANcaseXL log device.
¼ Driver version
Displays the driver version installed on the current PC
¼ Logging firmware version
This will display the firmware version of the selected CANcaseXL log device.
¼ Supported memory card
Displays the supported memory cards.
¼ Supported file system
Displays the supported file system for memory cards.
¼ Capacity
Capacity of the inserted memory card.
¼ Free space
Free disk space of the inserted memory card.
¼ Files
Displays the number of log files stored on the inserted memory card.
¼ Configured
Notifies if the CANcaseXL log device is already configured.
¼ Device clock
Displays the current clock settings.
¼ Channel 1
Displays the inserted piggyback type of channel 1.
¼ Channel 2
Displays the inserted piggyback type of channel 2.

6.1.2 Available Log Devices

Available Log De-

vices

If this tree node is selected, the property panel displays all connected CANcaseXL log
devices. The serial number of the log device is displayed in brackets. Additional the
currently selected device is marked with “(selected)”.

- 38 - Version 4.0 © Vector Informatik GmbH

Manual Tree view

Note: If no CANcaseXL is connected to the PC, the message No logger device

available is displayed.

6.2 Main Configuration

6.2.1 Overview

Overview

If this tree node is selected, the status of the selected CANcaseXL log device is dis-
played in the property panel. If the configuration of the device is not valid, several
errors or warnings are displayed.
¼ ID
Automatically generated session ID. The ID is displayed for project files and log
files in the File Manager. This ID helps to check which project file was used for a
specific log file.
¼ Short Description
Session name, which will appear in column Note of the File Manager.
¼ Long Description
A long session description, only for project file purpose.
¼ Error and warning expressions
This is a setting for the logger mode. Any errors or warnings can either be notified
by LEDs only (see User Manual CANcaseXL/log, section 2.4.2 Additional LEDs)
or by the piezo buzzer or both.
¼ Ring buffer configuration
Opens the dialog for ring buffer configuration. See section Configuration/Device
Mode / Ring buffer configuration on page 28 for further details.
¼ Current configuration status
Warnings or errors are displayed, if there is a problem with the current settings.
Otherwise valid configuration will be reported.

Note: If no piggyback is inserted into the CANcaseXL log device, the following error
will be displayed depending on the channel:
Error: Channel xy is configured for CAN Bus, but no piggyback is inserted.

© Vector Informatik GmbH Version 4.0 - 39 -

Tree view Manual

6.2.2 Channel 1/2

Channel 1
Channel 2

If this tree node is selected, channel settings of the selected CANcaseXL log device
can be made in the property panel. The button [Edit…] opens the channel dialog with
the following settings:

Channel 1/2
dialog settings

Baudrate [baud] Click the […] button to select from pre-defined

baudrates or enter a user defined baudrate.
Bus Timing Register The two Bus Timing Registers defines how an
individual bit of the serial bit stream is assembled
on the bus. Please refer to the data sheet for the
CAN controller for the values that should be en-
tered here. Enter the values in hexadecimal num-
bers.

Sampling Point [%] Sets the sampling point for CAN signals. Have a
look on the CAN protocol for further details.

Silent mode If enabled, the CANcaseXL log device sends no

acknowledge messages when data is received.
Please note that the Silent Mode has to be deacti-
vated for the Send Message trigger action (see
section Triggers on page 46).

Button [Driver…] Opens the Vector Hardware Config.

Info: The baudrate for J1708 is set to 9600 baud and cannot be changed. The inter
character bit time is set to 2 by default.

- 40 - Version 4.0 © Vector Informatik GmbH

Manual Tree view

6.3 Log Configuration

6.3.1 Databases

Databases

If this tree node is selected, the property panel contains a list view, where databases
can be added, edited or removed. In order to configure filters or triggers by symbolic
signals, at least one CANdb database must be added with [Add… ] before. The list
view contains the following information:

Info: It is not allowed to add a J1708 database here. J1708 databases are only re-
quired for CANoe to interpret the log files with J1708 data and to display them cor-
rectly in the trace windows of CANoe.

List view columns

Filename Name of the database.

A double-click on the file name opens the database
editor for editing. Ensure that CANdb++ is already
installed (found on the installation CD).
Channel Selected channel(s) which is (are) used with the
added database.
A double-click on it opens the channel selection
dialog.

Location Location of the stored database.

A double-click opens the file browser with the
database location.

Note Information about the added database. E.g. if a

databases with XCP commands is added, it will be
displayed as XCP setup present.

© Vector Informatik GmbH Version 4.0 - 41 -

Tree view Manual

Filename Name of the database.

A double-click on the file name opens the database
editor for editing. Ensure that CANdb++ is already
installed (found on the installation CD).
List view The database list view is right click sensitive and offers a context menu as follows:
context menu

Add database… Adds an existing CANdb database to the current

configuration.

Edit database… Opens selected CANdb database in CANdb++.

Modify channel assignment Changes channel assignment.

Remove Removes the selected CANdb database.

Note: The enabled menu entries depend on the selected item/column in the list view.

6.3.2 Filters

Filters

If this tree node is selected, CAN and/or LIN messages can be passed or stopped in
logger mode in the property panel. The right part of the window contains the following
filter information in a list view:

Info: Filters on J1708 messages are not allowed.

- 42 - Version 4.0 © Vector Informatik GmbH

Manual Tree view

List view columns

# Red icon means message is stopped and not

logged to SD card. Green icon means message is
passed and logged to SD card. A double-click
changes the state.

Event The set filter type. A double click opens the filter
type dialog.

Chan Channel to which the filter is applied to. A double-

click opens the channel dialog.

Condition The set filter condition, e.g. CAN ID == 10. A dou-

ble-click opens the condition dialog, if available.

¼ Condition type
ID value: a single ID is filtered.
ID range: an ID range is filtered.
¼ Source channel
Channel to which the filter should be applied
to.
¼ Allowed ID type
Standard ID, Extended ID.
¼ ID value
The ID which should be filtered.
¼ Last ID value
The last ID, which should be filtered.
This text box is only active if filter condition is
set to ID range.
Action Action for the filtered message (Pass or Stop). A
double-click changes the state.

© Vector Informatik GmbH Version 4.0 - 43 -

Tree view Manual

Note: All CAN and LIN messages are passed by default.

Caution: Filters are processed first, triggers after. It is not possible, to use a filtered
message for a trigger condition.

List View The Filters list view is right click sensitive and offers a context menu as follows:
context menu

New filter Inserts a new filter of the selected type (see be-
low).

Modify channel assignment Changes channel assignment.

Modify condition Changes trigger condition (see below).

Pass filter Passes the specified message (logged).

Stop filter Blocks the specified message (not logged).

Data reduction filter Reduces the data logged on SD card by ignoring

messages in a defined interval. Example: Change
value to 100 will log only every 100th message to
the SD card.

This dialog can also be opened by a double-click

on column Action in the list view.

Delete Deletes the selected filter.

- 44 - Version 4.0 © Vector Informatik GmbH

Manual Tree view

Note: The menu entries depend on the selected item/column in the list view.

Filter types

DEFAULT Assigned to all messages and events.

Symbolic message Filters a message by a symbolic name. In order to

use symbolic names, at least one CANdb database
must be added (see tree node Databases)

CAN ID Filters a defined CAN ID.

LIN ID Filters a defined LIN ID.

Sync pulse Filters all Sync Pulses from synchronization line.

CAN Error frame Filters all error frames.

CAN Bus load Filters all bus load messages.

CAN non-message Filters all non-messages, like transceiver events.

Note: The CAN Bus load is measured twice per second for each channel. The LIN
Bus load is measured twice per second for each channel.

Filter conditions Pass Passes the specified message (logged).

Stop Blocks the specified message (not logged).

© Vector Informatik GmbH Version 4.0 - 45 -

Tree view Manual

6.3.3 Triggers

Triggers

If this tree node is selected, triggers can be specified in the property panel. Triggers
can be used to control the start and stop of the logging session or to send a CAN
message. It is also possible to place triggers in AND groups for combined conditions.
The start and stop range of an event logging can be affected by setting the pre and a
post time in the property panel. This means if a Single trigger event occurs not only
the event itself is logged, but also a specified time before and after of the event.
Pre trigger time Event Post trigger time

Resulting logging time t

¼ Pre trigger time

Logging start when the Single trigger (see trigger types) occurs.
¼ Post trigger time
Logging follow-up time when Single trigger (see trigger types) occurs.

Note: The pre-trigger time is linked to the available memory of the CANcaseXL log
(not SD card) and it is displayed in the Pre/Port trigger configuration dialog which can
be opened in the Property panel by clicking [edit…].

Info: Triggers on J1708 messages/signals are not allowed.

Caution: Triggers are processed after the filters. It is not possible, to use a filtered
message for a trigger condition.

Pre / Post-Trigger
configuration

- 46 - Version 4.0 © Vector Informatik GmbH

Manual Tree view

Warning: The most important setting in this dialog is Average messages per
second which is needed for the pre-trigger time calculation. Ensure that this value fits
to the expected message rates on the bus. The higher this value is set the lower the
pre-trigger time can be specified. If the real message load (while logging) exceeds the
specified value, the pre-trigger time will be shortened.

Note: If any entered values exceed the available memory the settings can be
optimized to the highest possible values by clicking the button [Optimize].

In order to add a trigger:

1. Select the trigger event in the left list box on the property panel.
2. Select the trigger type in the right list box on the property panel.
3. Click [Add…], a new dialog will appear, depending on the selected trigger event.
4. Make your settings.

Dialog
Modify conditions

The dialog consists of the list box Level sensitive, the text boxes Value and High
limit value, a list box ID type, a checkbox Raw values, an option for Value changes
and Edge sensitive (slope). This elements are described as follows:

Level sensitive The following options are available:

== Trigger occurs, when the received ID or DLC is equal to text box Value.
Trigger occurs, when the received ID or DLC is NOT equal to text box
!= Value.

< Trigger occurs, when the received ID or DLC is less than text box
Value.

© Vector Informatik GmbH Version 4.0 - 47 -

Tree view Manual

<= Trigger occurs, when the received ID or DLC is less/equal than text box
Value.
> Trigger occurs, when the received ID or DLC is more than text box
Value.
>= Trigger occurs, when the received ID or DLC is more/equal than text
box Value.
IN_RANGE Trigger occurs, when the received ID or DLC is between text box Value
and text box High limit value.
!IN_RANGE Trigger occurs, when the received ID or DLC is NOT between text box
Value and textbox High limit value.

Value Enter the value for the desired condition here.

High limit value If Level sensitive is set to IN_RANGE or !IN_RANGE, this value means the last value
in a range.
ID type Standard ID or Extended ID. This depends on your setup and the CAN messages you
receive.
Raw values When trigger event is On Symbolic signal, raw values can be used for a specific
trigger.

Value Changes The trigger will occur on any value change.

Edge sensitive The trigger will occur when one of the following conditions is set and valid:
(slope) ¼ Positive edge, reach threshold
trigger occurs, when the received value increases and reaches exactly the
configured Value.
¼ Positive edge, exceed threshold
trigger occurs, when the received value increases and exceeds the threshold as
set in Value.
¼ Negative edge, reach threshold
trigger occurs, when the received value decreases and reaches exactly the
configured Value.
¼ Negative edge, exceed threshold
trigger occurs, when the received value decreases and exceeds the threshold as
set in Value.

List view columns

Event Displays the set event type.

Channel to which the trigger is applied to. A double-
Chan click on it lets you change the settings.

- 48 - Version 4.0 © Vector Informatik GmbH

Manual Tree view

Condition Specified condition of the trigger. A double click

opens a settings dialog.

Type Trigger type. See below further details about trigger

types. A double-click switches between the trigger
types.
Action The specified action when trigger occurs. A double-
click switches between the trigger actions.
Comment A user comment. A double-click lets you edit a com-
ment for the trigger.

List view The list view is right click sensitive and offers a context menu as follows:
context menu

New trigger Adds a new trigger as described above.

New group Adds a new AND group depending on a CAN or LIN

ID. Further group items can be added by right-click
the AND group Add trigger condition…

Modify channel assignment Modifies channel assignment.

Modify condition Modifies the trigger condition as described above.

Modify type Modifies the trigger type as described below.

Modify action Modifies the trigger action as described below.

Edit comment… Modifies the trigger comment as described above.

Delete Deletes the selected trigger.

Note: The menu entries depend on the selected item/column in the list view.

© Vector Informatik GmbH Version 4.0 - 49 -

Tree view Manual

Trigger events

All events Trigger if any event occurs.

On CAN ID Trigger if a CAN message with a specified ID is re-

ceived.

On CAN DLC Trigger if a CAN message with a specified DLC is

received.

On CAN data Trigger if specified CAN data is received.

On LIN ID Trigger if a LIN message with a specified ID is re-

ceived.

On LIN DLC Trigger if a LIN message with a specified DLC is

received.

On LIN data Trigger if specified LIN data is received.

- 50 - Version 4.0 © Vector Informatik GmbH

Manual Tree view

On Symbolic message Trigger if specified symbolic message is received.

This dialog will appear if On Symbolic message is

selected. A message from a previous added data-
base can be selected there.

On Symbolic signal Trigger if specified symbolic signal inside a symbolic

message is received and its condition is valid.

This dialog appears if On Symbolic signal is se-

lected . A signal from a previous added database can
be selected there. After the selections has been
made, the dialog Modify conditions appears.
On CAN Error frame Trigger if an Error frame is received.

© Vector Informatik GmbH Version 4.0 - 51 -

Tree view Manual

On Start Trigger immediately after boot.

On Sync pulse Trigger if sync pulse from synchronization line is re-

ceived.

On CAN Busload Trigger if defined percentage is reached.

On LIN CRC error Trigger if a LIN CRC error occurs.

On LIN RX error Trigger if a LIN Receive error occurs.

On LIN TX error Trigger if a LIN Transmit error occurs.

On LIN Sync error Trigger if a LIN Sync error occurs.

On LIN sleep Trigger if a LIN sleep occurs.

On LIN wakeup Trigger if a LIN wakeup occurs.

On trigger count Trigger if the number of occurred triggers matches

the defined condition.

Trigger types

Single trigger Triggers always, when trigger condition is valid.

Starts logging on SD card with set pre and post trig-
ger times. Logging can only be stopped by a hard-
ware reset
Single trigger once Same as Single trigger but only one time.
Logging on Starts logging on SD card. Logging will stop when a
Logging off action occurs or by a hardware reset.
This feature is not available for Multiple file Ring
buffer.
Logging off Stops logging if it was started by a Logging on ac-
tion before. This feature is not available for Multiple
file Ring buffer.
Logging off + Stops logging if it was started by a Logging on ac-
post-trigger time tion before with additional logging follow-up time.
This feature is not available for Multiple file Ring
buffer.
End measurement Stops the measurement. No further logging will be
done. This feature is not available for Multiple file
Ring buffer.

- 52 - Version 4.0 © Vector Informatik GmbH

Manual Tree view

Trigger action None No action will be done when the trigger occurs.
Sync pulse A sync pulse is generated when the trigger occurs.
Beep A beep on the piezo summer will be generated when
the trigger occurs
Beep and sync pulse Combination of Beep and Sync pulse (see above).
Send message… Sends a specified CAN message when the defined
trigger occurs. This trigger action is only available in
the context menu (right click on the list view Modify
action | Send message…). Please note that the
Silent Mode has to be deactivated before (see
section Channel 1/2 on page 40).

© Vector Informatik GmbH Version 4.0 - 53 -

Tree view Manual

CCP/XCP command… Sends a specified CCP/XCP command. E.g. this

setting can be used to connect to an ECU or to start
requesting data, if it was set to No in the CCP/XCP
Property Panel CONNECT on power-up:

This trigger action is only available in the context

menu (right-click on the list view Modify action |
CCP/XCP command…).
Available commands:
¼ None
No command is sent.
¼ CONNECT
If the trigger occurs, the CANcaseXL log tries to
connect to the specified (database) ECU.
¼ DISCONNECT
If the trigger occurs, the CANcaseXL log discon-
nects from specified (database) ECU, if possible.
¼ START
If the trigger occurs, the CANcaseXL log starts
measurement (DAQ list must be configured and
initialized before).
¼ STOP
If the trigger occurs, the CANcaseXL log stops
measurement, if possible.
¼ INIT
Re-Initialization of DAQ list for CCP/XCP meas-
urement.

- 54 - Version 4.0 © Vector Informatik GmbH

Manual Tree view

Trigger AND Groups Trigger AND groups can be used to combine several trigger conditions. The group is
created by a click on the Triggers list view with the right mouse button New group… |
AND group. The following dialog appears.

Message ID When an AND group is inserted, it can be either message ID dependent or ID

independent. Instead of specifying a message ID a symbolic name can be chosen
with the button [Symbolic]. Ensure, that at least one database is listed in Log
Configuration | Databases.

ID independent In certain cases it might be not needed to check for a specified message ID. For this
AND group purpose change the trigger condition of the AND group (first AND group item) to
Don’t care.
Additional conditions For further conditions click with the right mouse button onto the new created AND
group and select Add trigger condition followed by your desired condition.

© Vector Informatik GmbH Version 4.0 - 55 -

Tree view Manual

AND group validation An AND group contains one ore more additional conditions which are checked
sequential for their truth, started with the condition of the AND group main item (first
item), followed by all inserted items in the AND group. If one if the items is invalid no
trigger will be fired.

Example 1: AND group with ID 0x100 and

- On CAN data[0] == 255
- Symbolic Signal 1 (ID 0x200) > 20
- Symbolic Signal 2 (ID 0x100) == 32
The whole AND group is checked only, when a CAN message with ID 0x100 is re-
ceived. Afterwards the first data byte is checked for value 255, and then the last
known value of Symbolic Signal 1 (ID 0x200) is checked for greater 20. Please note:
Values are stored internally for this purpose. If no known value is available the AND
group validation will abort and no trigger will be fired. Otherwise if the last known
value of Signal 1 is greater 20, finally the Signal 2 (with 0x100) is checked. In this
case the value to be checked is the CAN message itself (ID 0x100). If Signal 2 of this
message is exactly 32 a trigger will be fired here, else not.

Example 2: AND group with Don’t care and

- DLC == 5
- Symbolic Signal 1 (ID 0x200) > 20
- Symbolic Signal 2 (ID 0x100) == 32
The whole AND group is checked only, when a message with ID 0x100 or ID 0x200 is
received. Afterwards the DLC is checked for value 5, and then the last known (or just
received) value of Symbolic Signal 1 (ID 0x200) and Symbolic Signal 2 (ID 0x100)
are checked. If the current message signal and the last known value respectively are
not valid, the AND group validation aborts.

Example 3: AND group with Don’t care and

- DLC == 5
- On CAN data[0] == 255
The whole AND group is checked when any message is received. Afterwards the
DLC is checked for value 5 and then the first data byte is checked for value 255.

Example 4: AND group with ID 0x300 and

- DLC == 5
- Symbolic Signal 1 (ID 0x200) > 20
- Symbolic Signal 2 (ID 0x100) == 32
The whole AND group is checked only, when a message with ID 0x300 was received.
Afterwards the DLC is checked for value 5, and then the last known value of
Symbolic Signal 1 (ID 0x200) is checked for greater 20. Please note: Values are
stored internally for this purpose. If no known value is available the AND group valida-
tion will abort and no trigger will be fired. Otherwise if the last known value of Signal 1
is greater 20, finally the Symbolic Signal 2 (0x100) is checked. If Signal 2 is exactly
32 a trigger will be fired here, else not.

- 56 - Version 4.0 © Vector Informatik GmbH

Manual Tree view

6.3.4 CCP/XCP

CCP/XCP

The CANcaseXL log is able to measure ECU related data over the CCP or XCP. In
order to do this, a database must be created and supplemented with CCP/XCP com-
mands. This supplement can be done in CANape only. After the database has been
created, it has to be added in the CCP/XCP list view.

Note: In order to generate a database containing CCP/XCP commands, check the

following requirements please:

¼ An existing CANape configuration must exists

¼ A working ECU must be available in CANape (online measurements)
¼ Select the desired ECU measurement signals in CANape
¼ Check the ECU settings in CANape
Tools | Device configuration… | Edit,
click [Next] followed by [Driver settigs].
Open tab Other and activate Generate a CANalyzer database.
Open tab General and click [Extended driver settings…].
Scroll down to CANDB_CCP_CONF and set it to Yes.
¼ Start and stop the measurement to generate the database.

Info: Polling of measurement signals is not supported.

Info: A database can also be generated using an A2L file (ASAP2). Detailed informa-
tion can be found in Tools | Generate CCP Database (see chapter Tools on page
30).

Global settings The property panel has two options as follows:

¼ CONNECT on power-up
If set to yes, the CANcaseXL log tries to connect to the specified (database) ECU
when it is switched on.
¼ On communication error
If the communication to the ECU is broken, the logging can be either stopped or
continued.

List view column

© Vector Informatik GmbH Version 4.0 - 57 -

Tree view Manual

Filename Filename of the database.

Channel Channel where the database is assigned to.
Init delay Delay in ms after the CANcaseXL log has been
switched to logger mode. Afterwards the CCP/XCP
commands are sent.
Cmd timeout Time segment in which the ECU has to respond to a
CCP/XCP command.
Status check Enables the cyclically CCP/XCP check of the config-
ured ECU.
Execute cfg Enables/disables the transmission of the CCP/XCP
commands from the database.
Path Location of the database.

List view The list view is right click sensitive and offers a context menu as follows:
context menu

Add database… Adds a new database. Ensure that this database

contains CCP/XCP commands.
Edit database… Opens CANdb++ editor for editing. Ensure that
CANdb++ was installed previously. An installation
file is found on the installation CD.
Disable/Enable CCP/XCP Disables or enables the CCP/XCP feature of the
feature added database. The database itself is still acces-
sible.
Edit assigned parameters… Opens the dialog for CCP/XCP configuration.
Modify channel assignment… Modifies the channel assignment where the data-
base is assigned to.
Remove Removed the database from the list view.

Note: The menu entries depend on the selected item/column in the list view.

- 58 - Version 4.0 © Vector Informatik GmbH

Manual Tree view

Modify CCP/XCP
This dialog can be opened by a right-click on the list view Edit assignment
configuration
parameters… or by a double-click on an item:
¼ Init delay
¼ Cmd timeout
¼ Status check

Dialog

Init delay [ms] Delay in ms after the CANcaseXL log has been
switched to logger mode. Afterwards the CCP/XCP
commands are sent.
Connection retry delay [ms] Time between a failed connection and next retry.
Command timeout Time segment in which the ECU has to respond to a
CCP/XCP command.
Status check method Enables the cyclically CCP/XCP check of the config-
ured ECU device.
Execute configuration Enables/Disables the transmission of the CCP/XCP
commands from the database.

© Vector Informatik GmbH Version 4.0 - 59 -

Manual File Manager

7 File Manager

In this chapter you find the following information:

7.1 Device Flash Drive page 62

7.2 Local Drive page 69

© Vector Informatik GmbH Version 4.0 - 61 -

File Manager Manual

7.1 Device Flash Drive

Description

If this tree node is selected, files on the SD card can be accessed and converted into
different file formats. The list view on the right part of the window looks like this:

Info: J1708 message can be converted to BLF format only.

List view columns

Filename Name of stored file.

Size Size of the file.

Type Type of file, e.g. Log data.

Modified Date of last modification.

Note Comment of logging session (see chapter
Overview on page 39).

Log file conversion The conversion is done in the logging file conversion dialog which can be opened with
click on the [Convert…] button or by a right-click in the list view, followed by Logging
file conversion….
The log file conversion can be accessed also by Tool | Convert files from....

- 62 - Version 4.0 © Vector Informatik GmbH

Manual File Manager

Dialog

Filename Name of stored file.

Size Size of the file.

Modified Date of last modification.

Destiniation Filename preview of the converted log file.

File prefix Prefix of the converted log file.

Source folder Location of the log file to be converted.

Destionation folder Location for converted log files.
Convert to Desired conversion.
Delete source files when done If checked the source file will be deleted.
Overwrite destination files If checked, existing files will be overwritten.
Close dialog on finish Closes the dialog, after conversion has been fin-
ished.
[Advanced…] Enables advanced converting settings. See next
below for further details. The context depends on
the selected output format (setting Convert to).

Advanced converter The following tables shows the available settings depending in the selected output
settings format:

© Vector Informatik GmbH Version 4.0 - 63 -

File Manager Manual

XL Log native Multiple files mode Enables the splitting of one log file into multiples
by:
¼ No splitting
¼ By trigger
¼ By channel
¼ By size
¼ By event count
Trigger reason always written A comment will appear in the split file with the rea-
son of splitting (trigger or channel).

Time-stamp 0 reference This option enables the resetting of the events’

time stamps.
¼ Start of the logging (file)
First event of the log file will get time stamp 0.
¼ Specific time
All time stamps will be offset to the specified
time.
¼ Start each split file from zero
First event of the log files will get time stamp 0.

Vector binary log file - No advanced settings available.

MDF log file Multiple output files Allows to merge multiple log files to a single one
(gap 1µs).

XL Log text file Time columns ¼ Append units

Setting for the time format for the first and sec-
ond column. If this checkbox is enabled, the
unit (related to the selected time format) is ap-
pended to the value.
¼ Absolute
Switches between relaltive and absolute time
stamps.
Content display ¼ Hexadecimal view
The log file contents can be displayed as
decimal or hexadecimal values by ena-
bling/disabling this checkbox.
¼ Byte order
The byte order of the messages can be chosen
in the list box.
¼ Separated columns
This checkbox allows splitting each value into
separate columns, instead grouping them in
one column.

- 64 - Version 4.0 © Vector Informatik GmbH

Manual File Manager

XL Log text file Time columns ¼ Append units

Setting for the time format for the first and sec-
ond column. If this checkbox is enabled, the
unit (related to the selected time format) is ap-
pended to the value.
¼ Absolute
Switches between relaltive and absolute time
stamps.
Other options ¼ Add header
This setting includes the header for each col-
umn on the first line of the converted file.
¼ Include only data messages
The converted file will contain only CAN or LIN
messages, if this checkbox is enabled. Errrors,
sync pulses are not displayed.
¼ Column separator
With this option the separator between the
columns can be selected.

© Vector Informatik GmbH Version 4.0 - 65 -

File Manager Manual

Signal text file File header and footer ¼ Date/Time

The date and the clock time of the log file are
entered in the first line.
¼ Comment
Appends the comment of the log file session.
Table ¼ First data line
The first line with measurement values is out-
put at the earliest at the line entered here.
Blank lines may be inserted before this line.
¼ Decimal delimiter
The decimal point character (.) is used for out-
putting measurement values. A comma is used
for outputting measurement values.
¼ Type of values
PHY values: The raw values of the log file are
converted according the conversion rules and
entered into the ASCII file.

HEX values: The raw values of the log file are

entered as hexadecimal values into the ASCII
file.

DEC values: The raw values of the log file are

entered as decimal values into the ASCII file.
¼ String separator
Apostrophe: Strings (e.g. comments, Write
window outputs or calibration operations) are
enclosed by apostrophes.

Quotation mark: Strings are enclosed by quo-

tation marks.Info: When an exported file is to
be loaded into Excel, these string separators
can be removed via the option Text qualifier in
step 2 of the Text Import Wizard.
Column separator ¼ with fixed width/column with
The columns of the ASCII file are all of the
same width. Minimum width of a column of
measurement values in number of characters.
If the column width entered here is not enough,
the output is not truncated. Info: To create an
optimally configured file for the export to MS
Excel (minimal file size), please select 0 (zero)
for the column width and the semicolon as col-
umn separator.
¼ with column separator/column separator
The columns of the ASCII file are separated
from each other by a specific separator sym-
bol, i.e. they are of different widths. Delimiter
symbol between measurement value columns.
Here the user inputs the character to be used,
e.g. of a spreadsheet calculation, to separate
the individual columns. Multiple characters can
also be entered.

- 66 - Version 4.0 © Vector Informatik GmbH

Manual File Manager

Number format ¼ Precision

This setting defines the number of digits after
the decimal point in both decimal and expo-
nential notation. If the option Dec./Exp. is se-
lected this setting defines the number of all dig-
its, before and after the decimal point. Possible
values are 0 15.
¼ Decimal representation
All the values are represented in decimal for-
mat.
¼ Dec./Exp. Representation
All values which could be represented with the
defined precision are displayed in decimal for-
mat. All other values are displayed with the ex-
ponential notation. If the value is an integer no
digits after the decimal point are displayed.
¼ Exponential representation
The values are displayed as exponential num-
bers.
Signal names ¼ Extended names
When this option is activated, the name of the
ECU will be added to the name of the signal as
a prefix, separated by a dot (e.g. ecu1.signal1,
ecu2.signal1). This option is useful in case you
measure signals of the same name from differ-
ent ECUs.
¼ Standard names
The name of the measurement signal is the
variable name.
¼ Display names
The Display Name is an alternative name for a
database object that is used in the display win-
dows. This name does not need to be unique,
since it is not referenced. The display name
can be set in the Database Editor in the field
Display name. The name is optional; if no
name is entered here, the variable name is
used for all displays. Info: Since the Display
name does not need to be unique the same
name can appear for different signals. Caution:
In this case the log file created via a re-import
by the ASCII import converter contains some
signals with the same signal name. If these
signals are saved in a configuration they can-
not be restored uniquely the next time the con-
figuration is loaded.

© Vector Informatik GmbH Version 4.0 - 67 -

File Manager Manual

Time ¼ Time column

The first column contains the point in time
when the measurement was made (in sec-
onds) for all successive values in the line.
¼ From
Entry in seconds of the time beginning from
which the measurement values are to be out-
put. The measurement time is known when
each value was measured. Conversion is only
made for values whose measurement time is
greater than or equal to the start time. The
start time can be entered with a resolution of
one millisecond.
¼ To
Point in time in seconds up to which measure-
ment values should be output. Info: The de-
fault setting "0.000 - 0.000" indicates that the
entire measurement time will be converted.
Only the point is accepted as decimal separa-
tor.
¼ Display
Relative: The time column starts with zero.

Absolute time: The time column starts with the

current system time. Info: When a fixed column
width is set, this value must be at least 15
characters for this display option.

Absolute date: The time column starts with the

current system time and current date. Info:
When a fixed column width is set, this value
must be at least 25 characters for this display
option.
Time grid ¼ Without time grid
Repeat values: The log file can contain meas-
urement values of multiple signals recorded at
different time intervals. If this flag is set, the
previous value is repeated in place of a miss-
ing measurement value. Otherwise, blank
characters are output.
¼ With time grid
Width in s: Value of the time grid (in seconds).
Interpolation: If this flag is set, a signal value
whose new time due to resampling lies be-
tween 2 original times will be calculated using
linear interpolation. Info: Digital signals are
generally not interpolated

- 68 - Version 4.0 © Vector Informatik GmbH

Manual File Manager

Output file ¼ Column title

print: Prints the column title.

in header file: The title line with the column

captions is saved in a separate header file.

with phys. unit: The physical unit of the signal

is output in the title line in each case with the
column captions. (Only when the title is acti-
vated).
¼ Extension of the output file
Enter the file extension here.

7.2 Local Drive

Local Drive

This displays all logged files on the local drive and allows the conversion into different
file formats. See chapter Device Flash Drive on page 62 for further information.

© Vector Informatik GmbH Version 4.0 - 69 -

Manual Property panel

8 Property panel

In this chapter you find the following information:

8.1 Miscellaneous information page 72

© Vector Informatik GmbH Version 4.0 - 71 -

Property panel Manual

8.1 Miscellaneous information

Displayed details

The property panel displays miscellaneous information and details and allows several
settings depending on the selection in the tree view.

- 72 - Version 4.0 © Vector Informatik GmbH

Manual Status bar

9 Status bar

In this chapter you find the following information:

9.1 Value display format page 74

© Vector Informatik GmbH Version 4.0 - 73 -

Status bar Manual

9.1 Value display format

Hex/Dec switch

The right part of the status bar contains the entry Dec (or Hex) which can be switched
by a click. This changes the value representation in the list views.

Note: The Hex/Dec switch does not affect all list view items, since partly HEX and
DEC are displayed simultaneously. Physical values are always displayed in DEC.

- 74 - Version 4.0 © Vector Informatik GmbH

Manual Hints

10 Hints

In this chapter you find the following information:

10.1 Hexa decimal values page 76

© Vector Informatik GmbH Version 4.0 - 75 -

Hints Manual

10.1 Hexa decimal values

Note: Decimal values can be typed as usual. Hex decimal values can be specified
like 0x123 or 0x1A

Note: Standard ID values can be typed as usual. Extended IDs can be specified like
100x (dec) or 0x492x (hex).

- 76 - Version 4.0 © Vector Informatik GmbH

Manual Appendix A: Address table

11 Appendix A: Address table

Vector Informatik GmbH Vector Informatik GmbH

Ingersheimer Straße 24
D-70499 Stuttgart
Phone : +49 (711) 80670-0
Fax : +49 (711) 80670-110
[email protected]
http://www.vector-informatik.de

Vector CANtech, Inc. Vector CANtech, Inc.

Suite 550
39500 Orchard Hill Place
USA-Novi, Mi 48375
Phone : +1 (248) 449 9290
Fax : +1 (248) 449 9704
[email protected]
http://www.vector-cantech.com

Vector Japan Co., Ltd. Vector Japan Co., Ltd.

Seafort Square Center Bld. 18F
2-3-12, Higashi-shinagawa, Shinagawa-ku
J-140-0002 Tokyo
Phone : +81 3 (5769) 7800
Fax : +81 3 (5769) 6975
[email protected]
http://www.vector-japan.co.jp

Vector France SAS Vector France SAS

168, Boulevard Camélinat
F-92240 Malakoff
Phone : +33 (1) 4231 4000
Fax : +33 (1) 4231 4009
[email protected]
http://www.vector-france.com

VecScan AB VecScan AB
Theres Svenssons Gata 9
SE-41755 Göteborg
Phone : +46 (31) 76476-00
Fax : +46 (31) 76476-19
[email protected]
http://www.vecscan.com

Vector Korea IT Inc. Vector Korea IT Inc.

Daerung Post Tower III, 508
182-4 Guro-dong, Guro-gu
Seoul 152-790
REPUBLIC OF KOREA
Phone : +82(0)2 2028 0600
Fax : +82(0)2 2028 0604
[email protected]
www.vector-korea.com

© Vector Informatik GmbH Version 4.0 - 77 -

Appendix A: Address table Manual

Vector GB Limited Vector GB Limited

Rhodium
Blythe Valley Park
Solihull, Birmingham
B90 8AS, UK
Phone : +44 (0) 754 9001197
[email protected]
http://www.vector-gb.co.uk

- 78 - Version 4.0 © Vector Informatik GmbH

Get more Information!

Visit our Website for:

> News
> Products
> Demo Software
> Support
> Training Classes
> Addresses

www.vector-worldwide.com