Working with CanEasy > Create a workspace > Import of a CanEasy Configuration

Via File "Import->CanEasy configuration", you can import an XML file (file extension .ceconfig) to automatically create a CanEasy workspace.

Content of a CanEasy configuration file:

•DBC files

•ARXML files

•Database XML files

•Diagnosis files

•BAP files

•Signal values

•Attributes

•Environment variable values

•RichPanels

General information

•Each configuration section is independent and optional. That way, you can for example just define signal values inside of a configuration.

•Invalid configuration entries will be ignored and displayed in the report window.

•Paths should be set relative to the configuration file to enable moving projects easily and importing them on different computers.

DBC files (configuration.busses.bus.dbc)

Description:

This section handles bus creation and import of DBC files. A bus can be created from multiple DBC files.

Section: configuration.busses.bus

Attributes:

id	Name of the bus
type	Type of the bus (CAN, LIN, ETH)

Section: configuration.busses.bus.dbc

Attributes:

id	Path to the DBC file (absolute or relative to the configuration file)

ARXML files (configuration.arxmlfiles.arxmlfile)

Description:

This section imports a database from arxml file.

Section: configuration.arxmlfiles.arxmlfile

Attributes:

id	Path to the ARXML file (absolute or relative to the configuration file)

Databaes XML files (configuration.xmlfiles.xmlfile)

Description:

This configuration section imports CanEasy database from xml file.

Section: configuration.xmlfiles.xmlfile

Attributes:

id	Path to the XML file (absolute or relative to the configuration file)

Diagnose files (configuration.busses.bus.diag)

Description:

This configuration imports a diagnostic file below an ECU.

Section: configuration.busses.bus.diag

Attributes:

id	Path to the diagnostic file (absolute or relative to the configuration file)
variant	Name of the ECU variant to be imported
ecu	Name of the ECU under which the imported services will be inserted

BAP files (configuration.busses.bus.bap)

Description:

This configuration imports BAP files below an ECU.

Section: configuration.busses.bus.bap

Attributes:

id	Path to the BAP file or complete directory (absolute or relative to the configuration file)
ecu	Name of the ECU under which the BAP files are imported

Signal values (configuration.signals | configuration.signalsexs)

Description:

A signal value can be assigned to a particular signal in the "signals" section .

The section "signalsexs" enables setting a value for multiple signals via a regular expression.

Section: configuration.signals.signal

Attributes:

id	String reference to signal
value	Physical value to be set

Section: configuration.signalsexs.signalex

Attributes:

id	Regular expression to identify signals
value	Physical value to be set

Attributes (configuration.attributes)

Description:

An attribute can be created using the "attributes" section.

Note: Existing attributes will be overwritten.

Section: configuration.attributes.attribute

Attributes:

id	Name of the attribute
type	Type of the attribute (Integer, Double, String)
dbref	String reference to the database element in which the attribute is to be created

Environment variable values (configuration.envvars)

Description:

Via the section "envvars", you can assign a value to an environment variable.

Section: configuration.envvars.envvar

Attributes:

id	String reference to the environment variable
value	Value to be set

VBA projects (configuration.vbaprojects)

Description:

A VBA project can be loaded using the "vbaprojects" section.

Note:

If the project exports an "OnProjectLoaded" macro, this macro is called immediately after loading.

This enables accessing special settings that are unavailable in the configuration file and implement them in VBA.

Section: configuration.vbaprojects.vbaprojects

Attributes:

id	Path to VBA file to be imported (absolute or relative to the configuration file)

VSTA projects (configuration.vstaprojects.vstaproject)

Description:

This configuration section loads VSTA projects

Section: configuration.vstaprojects.vstaproject

Attributes:

id	Path of the VSTA project to be imported (absolute or relative to the configuration file)

BSKD projects (configuration.bskdprojects)

Description:

A BSKD project can be loaded via the "bskdprojects" section.

Section: configuration.bskdprojects.bskdproject

Attributes:

id	Path to the BSKD batch file (absolute or relative to the configuration file)
value	Name of BSKD Project

User-Plug-ins (configuration.plugins)

Description:

A user plug-in can be loaded via the "plugins" section.

Please refer plug-ins by their names only (eg "CRCPlg.plu"). This ensures that the plug-in version corresponding to the used CanEasy version is loaded.

Section: configuration.plugins.plugin

Attributes:

id	Path or name of the user plug-in

RichPanels (configuration.panels)

Description:

A RichPanel can be loaded via the "panels" section.

Section: configuration.panels.panel

Attributes:

id	Path to the RichPanel file (absolute or relative to the configuration file)

General properties (configuration.properties)

Description:

Using the section "properties", several parameters can be set within CanEasy.

Section: configuration.properties.property

Attributes:

id	Name of property
value	Value of property

Overview of supported properties:

crc_signals	Regular expression to identify checksum signals
crc_use_id	Must be set to use message ID as part of checksum
crc_table	Encrypted table for CRC calculation
crc_table_unsafe	Unencrypted table for CRC calculation
sqc_signals	Regular expression to identify sequence counter signals
remove_attribute	Attribute name to be deleted after importing the DBC files

Example of a CanEasy Configuration

<?xml version="1.0" encoding="ascii"?>

</bus>

</busses>

</xmlfiles>

</arxmlfiles>

</signals>

</signalexs>

</attributes>

</envvars>

</vbaprojects>

</vstaprojects>

</bskdprojects>

</properties>

</plugins>

</panels>

</configuration>