File extension

Type

Description

*.csm

workspace

In a .csm file, called the workspace, all information describing the state of CanEasy at the time of storage is saved.

These include, for example, the path to the data base, current window positions, created panels, traces, etc.

*.candb

database

In this file, all properties, as well as the structure of the data base, are stored. Older CanEasy versions use the file extension .dat (still supported).

*.dbc

communication matrix

File format by Vector Informatik. Description files of a communication matrix for vehicle networks. Communication matrices are available for most motor vehicles from the relevant supplier in .dbc format.

*.plu

user plug-in

The functionality of CanEasy can be extended via plug-ins. For more information, see the chapter plug-ins.

*.celog

recording

In a .celog file, all information (messages) received and sent by CanEasy on the bus when running a simulation are stored in a compressed format.

A recording can be stored or loaded from the context menu of the tree entries "record" or "replay".

*.asc

recording

An .asc file stores similar information as a .celog file, with the difference that this information is stored in text format.

Also see: Converting an ASCII file

*.trc

trace window

In a .trc file, properties and settings of a trace window are stored. The properties include, for example, the compilation of various messages in the trace.

The configuration can be saved from the context menu of the respective trace window or loaded via the context menu of the core application.

*.plt

signal plot

In a .plt file, the properties and settings of a signal plot are stored. The properties include, for example, the color of graphs, size, and the compilation of the various signals in the plot.

The configuration can be saved from the context menu of the respective signal plot or loaded via the context menu of the core application.

*.pnl

user panel

In a .pnl file, the properties and settings of a user panel are stored. Properties include, for example, font and background color, as well as the compilation of the various signals and messages in the panel.

The configuration can be saved from the context menu of the respective user panel or loaded via the context menu of the core application.

*.xcp

XCP database

In this file, all properties as well as the structure of the XCP database are saved. All imported A2L data is stored as binary data.

*.ldf

LIN network file

The .LDF file format contains information about a complete LIN bus. It defines the various nodes, messages and signals. Their interdependencies as well as the different schedules for transmission control are stored. The LDF file format was specified by the LIN consortium to facilitate developers the accurate planning of a LIN bus.

*.ncf

LIN nodes file

The .NCF file format contains all the information about a LIN slave. Unlike the LIN network file, no scheduler and timing data is included in this format. The node file can be obtained from a LIN network file. With these files, a LIN node can be implemented. The format is part of the LIN specification.

*.env

environment variables file

This file stores information about environment variables that can be imported or exported from CanEasy. Also see environment variables.

*.lic

licence file till CanEasy 4.0

<%APPLNAME% requires a license file. The file is either included with the software or can be obtained from the CanEasy support. A demo version of the software can be downloaded from www.caneasy.de.

The license file contains information on all activated options and the license type. The file must not be saved manually inside the CanEasy program directory.

*.v2c

license file since CanEasy 4.0

To install a license in offline mode (no internet connection) CanEasy needs a license file. This license file can be obtained from the CanEasy support.

The license file includes information about the available options and the license type. The license file is needed only once for installing the license.

*.ceconfig

CanEasy configuration file

Importing a ceconfig file the creation of a workspace can be automated. See Import of CanEasy configuration.

*.xml

Datenbase XML file

The complete data base (as well as individual sub-elements) can be exported to or imported from an XML file.

*.cdb

Datenbase binary file

The complete data base (as well as individual sub-elements) can be exported to or imported from a compressed binary file.