没有合适的资源?快使用搜索试试~ 我知道了~
AN-IND-1-001_CANoe_CANalyzer_as_Diagnostic_Tools.pdf
1.该资源内容由用户上传,如若侵权请联系客服进行举报
2.虚拟产品一经售出概不退款(资源遇到问题,请及时私信上传者)
2.虚拟产品一经售出概不退款(资源遇到问题,请及时私信上传者)
版权申诉
0 下载量 23 浏览量
2024-03-03
09:48:25
上传
评论
收藏 1.38MB PDF 举报
温馨提示
试读
40页
AN-IND-1-001_CANoe_CANalyzer_as_Diagnostic_Tools
资源推荐
资源详情
资源评论
CANoe and CANalyzer as Diagnostic Tools
Version 1.9
2022-08-02
Application Note AN-IND-1-001
Author
Vector Informatik GmbH
Restrictions
Public Document
Abstract
This application gives an introduction into working with diagnostics in
CANoe/CANalyzer. It presents the basic technical aspects and possibilities with the
Diagnostic Feature Set, complements the help file of CANoe/CANalyzer and may be
used as a tutorial.
Table of Contents
1.0 Overview ........................................................................................................................................ 3
1.1 Introduction .......................................................................................................................... 3
1.2 Diagnostic components ........................................................................................................ 4
1.3 “Built-in” diagnostic channel vs. TP modeling library and CAPL Callback Interface ........... 6
2.0 Diagnostics in CANoe and CANalyzer ........................................................................................ 7
2.1 Transport Protocol support .................................................................................................. 7
2.2 Diagnostic Descriptions ....................................................................................................... 8
2.2.1 CDD – CANdela Diagnostic Description .............................................................................. 8
2.2.2 ODX – Open Diagnostic Data Exchange ............................................................................. 8
2.2.3 MDX – Multiplex Diagnostic Data Exchange ....................................................................... 8
2.2.4 Basic Diagnostic Description (UDS or KWP) ....................................................................... 8
2.2.5 Standard Diagnostic Description.......................................................................................... 9
2.3 Additional Descriptions ........................................................................................................ 9
2.4 Trace Window ....................................................................................................................10
2.5 Diagnostic Feature Set ......................................................................................................11
2.5.1 Diagnostic Console (window) .............................................................................................11
2.5.2 Diagnostic Console (Diagnostic Feature) ..........................................................................12
2.5.3 Fault Memory window ........................................................................................................12
2.5.4 Variant Coding (Diagnostic Feature)..................................................................................13
2.5.5 Diagnostic Session Control window ...................................................................................13
2.5.6 OBD-II window ...................................................................................................................14
2.5.7 ECU Control .......................................................................................................................14
2.5.8 ECU, gateway or tester simulations using CAPL ...............................................................15
2.5.9 Test modules using CAPL (CANoe only) ...........................................................................15
2.5.10 Test Units (CANoe only) ....................................................................................................15
2.5.11 Symbol Explorer for diagnostics objects and parameters .................................................15
2.5.12 Autocomplete Input Assistance for diagnostics .................................................................16
2.5.13 Functional Group Requests ...............................................................................................16
2.6 Access to diagnostics features via COM (CANoe only).....................................................16
2.7 Basic Diagnostic Editor ......................................................................................................16
2.8 Security Access handling ...................................................................................................17
2.9 Authentication and encryption ............................................................................................17
3.0 First steps ....................................................................................................................................17
3.1 Usage of Diagnostic Descriptions ......................................................................................18
3.1.1 Add a Diagnostic Description .............................................................................................18
3.1.2 Configure the Diagnostic Description ................................................................................18
3.2 Usage of Diagnostic Console, Session Control and Fault Memory window ......................19
CANoe and CANalyzer as Diagnostic Tools
Copyright © 2022 - Vector Informatik GmbH 2
Contact Information: www.vector.com or +49-711-80 670-0
3.2.1 Send a diagnostic request and receive a response ...........................................................20
3.2.2 Read fault memory .............................................................................................................20
3.2.3 Functional Group Requests ...............................................................................................20
3.2.4 Change the session and security level ..............................................................................20
3.3 Display diagnostic data ......................................................................................................20
3.3.1 Diagnostic data in State Tracker, Data and Graphics window ..........................................21
3.3.2 Diagnostic data in panels ...................................................................................................21
4.0 Using CAPL for Diagnostics ......................................................................................................22
4.1 Common techniques for Simulation and Tester .................................................................22
4.1.1 Usage of the CAPL Browser ..............................................................................................22
4.1.2 Work with parameters ........................................................................................................23
4.2 ECU diagnostics simulation ...............................................................................................24
4.2.1 Necessary preparations .....................................................................................................24
4.2.2 Add a Network Node to the Simulation Setup ...................................................................26
4.2.3 Add a database in case of LIN and FlexRay .....................................................................26
4.2.4 Add a Diagnostic Description and assign it to the network node .......................................26
4.2.5 Configure the Network Node in Simulation Setup .............................................................26
4.2.6 Add the CAPL Callback Interface ......................................................................................28
4.2.7 Debug level ........................................................................................................................28
4.2.8 Add a diagnostics request event handler ...........................................................................28
4.2.9 Create a diagnostic response ............................................................................................28
4.3 CANoe/CANalyzer as Diagnostic Tester ...........................................................................29
4.3.1 Set the diagnostic target ....................................................................................................29
4.3.2 Create a diagnostic request ...............................................................................................29
4.3.3 Add a diagnostics response event handler ........................................................................29
4.3.4 Negative Response handling .............................................................................................29
4.4 Combine Test Feature Set and Diagnostic Feature Set ....................................................30
4.4.1 Timeout handling................................................................................................................30
4.4.2 Automated diagnostic tests with CANoe ............................................................................31
4.5 Using CAPL in the Measurement Setup ............................................................................34
5.0 Advanced examples ....................................................................................................................34
5.1 ECU simulation of “Response Pending” ............................................................................34
5.2 Modifying the length of a diagnostic object ........................................................................35
5.3 Fill diagnostic content ........................................................................................................35
5.4 Fault injection .....................................................................................................................35
5.4.1 Make request length illegal ................................................................................................35
5.4.2 Introduce errors on transport protocol level .......................................................................36
5.5 Access a node via a gateway simulation ...........................................................................36
6.0 Common mistakes ......................................................................................................................37
7.0 Abbreviations ..............................................................................................................................39
8.0 References ...................................................................................................................................40
9.0 Additional Resources .................................................................................................................40
10.0 Contacts .......................................................................................................................................40
CANoe and CANalyzer as Diagnostic Tools
Copyright © 2022 - Vector Informatik GmbH 3
Contact Information: www.vector.com or +49-711-80 670-0
1.0 Overview
1.1 Introduction
Diagnostics is used to configure, maintain, support, control and extend an ECU before or after it is
installed in a system, e.g. a vehicle. It is usually performed in a request – response scheme: a tester
(client) sends a request to an ECU (or even more than one ECU) and the ECU (server) responds by
sending a “positive diagnostic response” containing the requested information, or a “negative
response” indicating the reason for the negative response.
The purpose of this application note is to give a general introduction into working with diagnostics in
the Vector tools CANoe and CANalyzer. The basic technical aspects and possibilities (“first steps”)
with the Diagnostic Feature Set will be presented. Examples are used to get the test engineer started
with testing diagnostics in CANoe/CANalyzer.
This document is a complement to the help in CANoe/CANalyzer and should be used as a tutorial to
learn the “first steps” of the Diagnostic Feature Set. For more detailed information about the
Diagnostic Feature Set, please refer to the CANoe/CANalyzer help file and sample configurations,
both of which come with a standard CANoe/CANalyzer installation.
Note
The functionality described below refers to CANoe and CANalyzer version 16 SP3 (unless
otherwise noted – please see the general limitations of CANalyzer in chapter 2.0). The
term “CANoe/CANalyzer” stands for both applications, while the term “CANoe” describes
functionality only available with CANoe.
For older program versions application notes can be requested from the Vector support
(cf. chapter 10.0).
CANoe and CANalyzer as Diagnostic Tools
Copyright © 2022 - Vector Informatik GmbH 4
Contact Information: www.vector.com or +49-711-80 670-0
1.2 Diagnostic components
The following table lists the names of the components relevant for diagnostics in CANoe/CANalyzer,
how to activate them and where to find more information.
Component
Description
Activation
More Information
Transport Protocol (TP)
modeling libraries
Implementation of the
respective Transport
Protocol for CANoe
simulation nodes
See chapter 2.1
See chapter 2.1
ISO TP Observer
Displays TP information
in the Trace Window for
the CAN frames used
by the ISO TP
Menu: “Configuration->
Diagnostics/ISO TP
configuration”, page
“ISO TP Observer”
Help: “ISO TP
Observer”
KWP 2000 Observer
Extension of the ISO
TP Observer that
interprets the
transported data
according to Keyword
Protocol 2000
Like ISO TP Observer,
check box
“Interpretation
according to KWP2000”
Help: “ISO TP
Observer”
Diagnostics Observer
Extension of the ISO
TP Observer, interpret
the transported data
according to the
available diagnostic
specification(s)
Menu: “Configuration->
Diagnostics/ISO TP
configuration”,
corresponding network
in which Diagnostic
Descriptions can be
loaded
Help: “Administrate
Diagnostic
Descriptions”
Diagnostic Console
(window)
Should not be used
anymore, use
Diagnostic Feature
“Diagnostic Console”
instead
By assigning a
Diagnostic Description
to any of the available
networks a
corresponding
Diagnostic Console is
made available
Help: “Diagnostic
Console”
Fault Memory window
Direct access to an
ECU’s fault memory
By assigning a
Diagnostic Description
containing a fault
memory model to any
of the available
networks a
corresponding Fault
Memory window is
made available
Help: “Fault Memory
Window”
Diagnostic Session
Control (deprecated,
predecessor of
Diagnostic Feature
“ECU Control”)
Should not be used
anymore, use
Diagnostic Feature
“ECU Control” instead
By assigning a
Diagnostic Description
to any of the available
networks a
corresponding
Diagnostic Session
Control is made
available
Help: “Diagnostic
Session Control”
Diagnostic Window
Combining several
Diagnostic Features
within one window
By assigning Diagnostic
Descriptions to any of
the available networks
(see Diagnostics
interpreter above), the
corresponding
Help: “Diagnostic
Window”
CANoe and CANalyzer as Diagnostic Tools
Copyright © 2022 - Vector Informatik GmbH 5
Contact Information: www.vector.com or +49-711-80 670-0
Component
Description
Activation
More Information
Diagnostic Features
can be configured as
part of a Diagnostic
Window
Diagnostic Console
(Diagnostic Feature)
Direct sending of
requests defined in a
Diagnostic Description,
display of responses
(successor of
Diagnostic Console
window)
By assigning Diagnostic
Descriptions to any of
the available networks,
the Diagnostic Feature
“Diagnostic Console”
can be configured as
part of a Diagnostic
Window
Help: “Diagnostic
Console (Diagnostic
Feature)”
Variant Coding
(Diagnostic Feature)
Interactively read, write,
and compare variant
coding data of an ECU
By assigning Diagnostic
Descriptions containing
variant coding services
to any of the available
networks, the
Diagnostic Feature
“Variant Coding” can be
configured as part of a
Diagnostic Window
Help: “Variant Coding
(Diagnostic Feature)”
ECU Control
(Diagnostic Feature)
Successor of the
Diagnostic Session
Control: Authentication
and Deauthentication,
easy switching of the
session state (e.g.
Default, Extended,
Programming),
unlocking ECUs
By assigning a
Diagnostic Description
to any of the available
networks, a
corresponding ECU
Control is made
available together with
other Diagnostic
Features such as
Diagnostic Console and
Variant Coding
Help: “ECU Control
(Diagnostic Feature)”
Diagnostic Parameters
window
Configure diagnostic
response parameters to
for which the
corresponding
diagnostic requests can
be sent interactively or
cyclically so that the
parameters are
displayed both in the
Diagnostic Parameters
window and the other
Analysis Windows (e.g.
State Tracker, Data
Window and Graphics
Window)
Always available,
diagnostic response
parameters can only be
added if at least one
Diagnostic Description
was assigned to any of
the available networks
Help: “Diagnostic
Parameters window”
OBD-II Window
Support of On-Board
Diagnostics
By choosing the
addressing mode (11
bit Normal or 29 bit
NormalFixed) at the
page “OBD-II
Functionality” (Menu:
“Configuration->
Diagnostics/ISO TP
configuration”)
Help: “Administrate
Diagnostic
Descriptions”, “OBD
Window”
CAPL extensions for
Specialized CAPL
The extended CAPL
Help: “Diagnostic CAPL
剩余39页未读,继续阅读
资源评论
车载诊断技术
- 粉丝: 3855
- 资源: 616
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功