Migrated DIDs in CANdelaStudio 17 May Need Manual Adaptation
2022-03-15
Support Note SN-IDG-1-003
Author(s)
Steeb, Helmut
Restrictions
Public Document
Table of Contents
1
2
3
4
5
6
Overview ........................................................................................................................................2
Context ...........................................................................................................................................2
Some relevant data constellations ..............................................................................................2
3.1
No DIDs in the CANdelaStudio 16 DIDs tree node ..............................................................2
3.2
Identifier of CANdelaStudio 16 DID vs. Diagnostic Instance differs ....................................2
3.3
Diagnostic Instances with same name ................................................................................2
3.4
CANdelaStudio 16 DID without Diagnostic Instance ...........................................................2
3.5
CANdelaStudio 16 DID without Diagnostic Class ................................................................2
How to handle the New Diagnostic Class from migration ........................................................3
4.1
Context .................................................................................................................................3
4.2
Scope: Documents and Templates ......................................................................................3
4.3
Your options for the new Diagnostic Class ..........................................................................3
4.4
How to modify the range of allowed Identifiers ....................................................................3
4.5
How to rename a Diagnostic Class Template ......................................................................4
Background ...................................................................................................................................4
5.1
DIDs in UDS .........................................................................................................................4
5.2
DIDs in CANdelaStudio up to CANdelaStudio 16 ................................................................4
5.3
DIDs in CANdelaStudio 17 ...................................................................................................5
Contacts .........................................................................................................................................5
Migrated DIDs in CANdelaStudio 17 May Need Manual Adaptation
1
Overview
This Support Note describes the manual adaption, which you might need for migrated DIDs in
CANdelaStudio 17.
2
Context
CANdelaStudio 17 simplifies the handling of UDS DIDs.
For the future, this avoids inconsistent data and operations in the DIDs tree node vs. under
Supported Diagnostic Classes.
The transition (up migration) to this simplified model may need manual adaptation, for few specific
data constellations of CANdelaStudio 16 and before.
3
Some relevant data constellations
3.1 No DIDs in the CANdelaStudio 16 DIDs tree node
If your CANdelaStudio 16 document does not have DIDs in the DIDs tree node of a Variant/Library,
you are done.
3.2 Identifier of CANdelaStudio 16 DID vs. Diagnostic Instance differs
If a CANdelaStudio 16 DID in the DIDs tree node has a different Identifier than the respective
Diagnostic Instance, you will get a hint in the output window.
CANdelaStudio 17 will use the Identifier of the Diagnostic Instance, ignoring that from the DIDs tree
node.
3.3 Diagnostic Instances with same name
If you have in CANdelaStudio 16 two DID Diagnostic Instances with the same name in Diagnostic
Classes relevant for UDS DIDs - this can occur in different Diagnostic Classes only, like
Configuration and Periodic Data - then CANdelaStudio 17 will detect them as DIDs and report an
error for the duplicate name.
3.4 CANdelaStudio 16 DID without Diagnostic Instance
If the CANdelaStudio 16 DID in the DIDs tree node does not have a corresponding Diagnostic
Instance, you can use it in Fault Memory but not read it directly by a 0x22 Service, then
CANdelaStudio 17 will represent it by a new de-activated Diagnostic Instance. Up migration
determines the Diagnostic Class for the new Diagnostic Instance by heuristics.
Background
Each Diagnostic Class Template defines the range of allowed Identifiers, using a
reference to a Text Table.
3.5 CANdelaStudio 16 DID without Diagnostic Class
As a special variation of the previous constellation:
If no CANdelaStudio 16 Diagnostic Class Template allows the Identifier of the DID from the
CANdelaStudio 16 DIDs tree node, but the DID is used e.g. in Fault Memory, then up migration
creates a new Diagnostic Class Template called DIDs,
>
>
in the Variant, creates a Diagnostic Class DIDs for the new Diagnostic Class Template,
and puts a new de-activated DID Diagnostic Instance into that Diagnostic Class.
Copyright © 2022 - Vector Informatik GmbH
Contact Information: www.vector.com or +49-711-80 670-0
2
Migrated DIDs in CANdelaStudio 17 May Need Manual Adaptation
For details, see CANdelaStudio 17 online help [MIGR17-R610].
Note
CANdelaStudio 16 contained the DID in the DIDs tree node (on Variant level),
CANdelaStudio 17 contains the DID in another DIDs tree node (now under Supported
Diagnostic Classes).
After the migration, you may want to adapt the new Diagnostic Class, see the following chapter:
4
How to handle the New Diagnostic Class from migration
4.1 Context
>
>
>
>
In CANdelaStudio 17, a DID is represented by a Diagnostic Instance, without exception.
Each Diagnostic Instances lives in a Diagnostic Class,
so for the DIDs, you need some Diagnostic Class, anyway.
Up migration creates the new Diagnostic Class if no existing Diagnostic Class allows the
existing CANdelaStudio16 Identifiers.
4.2 Scope: Documents and Templates
>
>
CANdelaStudio applies this migration change for each individual CANdela document (CDD) with
a relevant data constellation.
Recommendation: adapt the CANdela template (CDDT) accordingly.
4.3 Your options for the new Diagnostic Class
>
>
>
Accept the new Diagnostic Class.
Recommendations:
> Restrict the range of allowed Identifiers for this Diagnostic Class (after migration, it has no
restriction) → see How to modify the range of allowed Identifiers below.
> Optionally rename the Diagnostic Class, like DIDs (Fault Memory only),→ see How to
rename a Diagnostic Class Template below.
Let up migration put the Diagnostic Instance into an existing Diagnostic Class
> In CANdelaStudio 16, extend the range of allowed Identifiers of an existing Diagnostic
Class, → see How to modify the range of allowed Identifiers below.
> Then again migrate the file to CANdelaStudio17, which will place the Diagnostic Instance
into the existing Diagnostic Class.
Manually put the Diagnostic Instance into an existing Diagnostic Class
> In CANdelaStudio 17, extend the range of allowed Identifiers of an existing Diagnostic
Class, → see How to modify the range of allowed Identifiers below.
> Then manually move the Diagnostic Instances from the Diagnostic Class DIDs to the
extended existing Diagnostic Class,
> finally remove the Diagnostic Class Template DIDs (in Expert View).
4.4 How to modify the range of allowed Identifiers
Step by Step
>
>
>
>
>
>
The set of Identifiers allowed in a Diagnostic Class is defined by a Text Table in the
list of Data Types.
In a Diagnostic Instance, the button right to the Identifier opens the property dialog
of the respective Text Table.
Navigate to the list of Data Types.
Select the respective Text Table.
Open the Propery Dialog via context menu Properties.
Modify the list of Text Table entries as desired, click OK.
Copyright © 2022 - Vector Informatik GmbH
Contact Information: www.vector.com or +49-711-80 670-0
3
Migrated DIDs in CANdelaStudio 17 May Need Manual Adaptation
4.5 How to rename a Diagnostic Class Template
Step by Step
>
>
>
>
5
Open a CDD or CDDT file in Expert View.
Expand the tree node Diagnostic Class Templates.
On the Diagnostic Class Template in the tree, open the Property Dialog via context
menu Properties.
Modify the name as desired, click OK.
Background
5.1 DIDs in UDS
Figure 1 – DIDs in UDS
A Data Identifier (DID) in UDS involves the following:
>
>
>
Identifier: a 2 byte value that identifies (represents) data.
Data Record: the identified data is called Data Record in UDS, either a single object (e.g. Air
Inlet Door Position), or a collection of objects.
UDS Services actually use the Identifier and the Data Record. In all Services that use a given
DID, the data must be identical (same size, same meaning). Except for a special case:
dynamically defined dataIdentifiers.
5.2 DIDs in CANdelaStudio up to CANdelaStudio 16
In CANdelaStudio up to CANdelaStudio 16, the DID list in a Variant contained the data only (no
Services), which were optionally used from Diagnostic Instances (with Services) under Supported
Diagnostic Classes, e. g.
>
>
in a 0x22 UDS Service, or
in snapshot data in a 0x19 0x04 Fault Memory UDS Service.
Copyright © 2022 - Vector Informatik GmbH
Contact Information: www.vector.com or +49-711-80 670-0
4
Migrated DIDs in CANdelaStudio 17 May Need Manual Adaptation
Figure 2 – DIDs in CANdela (up to CANdelaStudio 16)
5.3 DIDs in CANdelaStudio 17
>
>
>
In CANdelaStudio 17, the CANdela data model represents a UDS DID by a Diagnostic Instance
under Supported Diagnostic Classes, typically with a 0x22 UDS Service.
The DID list in a Variant just shows a view of these DID Diagnostic Instances.
The DID Diagnostic Instances are optionally used from other Diagnostic Instances, typically in
snapshot data in a 0x19 0x04 Fault Memory UDS Service.
Figure 3: DIDs in CANdela since CANdelaStudio 17
6
Contacts
For support related questions please address to the support contact for your country
https://www.vector.com/int/en/company/contacts/support-contact/.
Copyright © 2022 - Vector Informatik GmbH
Contact Information: www.vector.com or +49-711-80 670-0
5