CANoe and CANalyzer as Diagnostic Tools
Copyright © 2022 - Vector Informatik GmbH 19
Contact Information: www.vector.com or +49-711-80 670-0
Second, you need to choose the “Interface” for this Diagnostic Description. Such a diagnostic interface
contains the communication parameters for a specific network. There may be even more than one
appropriate diagnostic interface for a specific network type defined in a diagnostic description (e.g. for
the network type CAN: “Normal 11bit” and “Extended 29bit free” addressing). On the other hand, an
appropriate diagnostic interface for the chosen network type might be missing in your diagnostic
description. In such a case, CANoe/CANalyzer will generate appropriate default interfaces for this
diagnostic description, indicated by the prefix “{generated}”. For such a generated interface, you need
to define important communication parameters like timeout values or transport protocol parameters in
the “Diagnostics/ISO TP” configuration dialog manually by you own.
For Standard Diagnostic Descriptions or file based Diagnostic Descriptions like CDD, ODX/PDX or
MDX, there are additional settings:
> “Variant” can be modified if the Diagnostic Description contains several different variants and
determines the default variant to be used for interpretation in the trace. CANoe distinguishes
between the “default” variant and the “active” variant. The “active” variant can be dynamically
changed during an active measurement while the “default” variant becomes active at the start
of (a) measurement. This setting will determine the set of services you see in the Diagnostic
Console, e.g. if the “Common” variant is chosen, the user might not find services that are only
present for other variants.
> “Language” determines the language used for interpretation of the diagnostic services,
provided that the Diagnostic Description contains such information.
> “Target group” additionally restricts the set of services which can be accessed by the user to
those services intended for a specific user group, based on the definition in the Diagnostic
Description. If it is set to “(Display all services)”, there is no limitation.
> “Usage of the Diagnostic Description” defines how the diagnostic description is intended to be
used. By default, the Diagnostic Description is used for interpretation in the trace. If you select
“Diagnostics Tester”, you can additionally choose how the requests should be sent by the
tester (to a single ECU via physical addressing or as Functional Group Requests; the latter
possibility requires that all ECUs on the network implement the contents of the Diagnostic
Description as a common subset). Selecting “Simulation by:” (only available for CANoe) will let
you choose the node implementing the simulation code for this Diagnostic Description and
enable the simplified simulation for it, i.e. CANoe will send positive responses for requests
defined in this Diagnostic Description, as long as there are no “on diagRequest” handlers in
this node covering those requests.
Selecting an interface here will determine which TP parameters are available for configuration:
> The “Interface” list shows the interfaces defined in the Diagnostic Description. Each interface
defines an addressing mode and address parameters that are used as default. Note that the
addressing mode of an interface cannot be changed – chose a different interface instead.
> If the “VAG Addons packet“ (version 1.10 or later) is installed, it is possible to select the
interface called "VWTP 2.0 (CANoe)". You then have to enter the correct TP parameters on
the page “Transport Layer (VW TP 2.0)”.
> If the Diagnostic description was added to an Eth network, the corresponding parameters can
be defined on the page “DoIP/HSFZ Settings” or “Socket Adaptor Settings”, depending on the
chosen diagnostic interface (DoIP or AUTOSAR Socket Adaptor).
> If a node from a LIN database file is selected, the corresponding parameters can be defined
on the page “LIN settings”.
> If a node from a FlexRay database is selected, the FlexRay TP parameters can be defined in
the page “FrTP Parameter”.
> Since for MOST ECUs, only interpretation of the diagnosis messages is possible, there are no
dedicated MOST TP parameters for MOST nodes.
For further details of the configuration dialog please refer to the help.
3.2 Usage of Diagnostic Console, Session Control and Fault Memory window
When you add a Diagnostic Description to your CANoe/CANalyzer configuration and choose “OK”, the
available Diagnostic Windows for that Diagnostic Description will automatically become visible.